JP4704208B2 - Neighbor notification program and neighbor notification method - Google Patents

Description

  The present invention relates to a neighbor notification program and a neighbor notification method, and more particularly to a neighbor notification program and a neighbor notification method for notifying a monitor of neighbor information of a monitored person.

In recent years, child kidnapping and injury cases have occurred frequently, and various devices have been made to prevent such crimes. For example, there is a child assist system that notifies a parent of location information of a child and transmits a message of the parent to the child in order to confirm safety when the child is out (for example, see Patent Document 1). In addition, there is a cram school management system that gives a child an IC (Integrated Circuit) card to notify whether the child has arrived at a specific location (for example, Patent Document 2). In addition, there is a child crime prevention reporting method for registering child behavior information, determining whether the child has arrived at the school at a predetermined time, and reporting to the parents and the school (for example, Patent Document 3).
JP 2003-168194 A JP 2002-261969 A JP 2005-182468 A

  However, in Patent Documents 1 to 3, the monitor (guardian) can know only the position information of the monitored person (child), and what kind of person the monitored person is with or is not together. There was a problem of not knowing.

  The present invention has been made in view of the above points, and by notifying the monitor of information on the neighbors of the monitored person, what kind of neighbors the monitor has around the monitored person. It is an object of the present invention to provide a neighbor notification program and a neighbor notification method.

  In the neighbor notification program for notifying the monitor of the information of the neighbor of the monitored person, the computer carries the computer from the monitored terminal that detects the wireless ID tag possessed by the neighbor, Tag information receiving means for receiving tag information of a radio ID (Identification) tag and storing it in tag information storage means; from neighbor information storage means for storing neighbor information of the neighbor corresponding to the tag information , Neighbor information acquisition means for acquiring the neighbor information corresponding to the tag information received by the tag information receiving means, and message transmission for transmitting a message including the neighbor information to a monitor terminal possessed by the monitor Means, when the same tag information is stored in the tag information storage means for a predetermined time, in the message, the monitored person and the neighbor having the tag information Neighbor notification program for causing the information adding means for including information indicating being in cord functions as, is provided.

Further, in the neighbor notification method of the neighbor notification device for notifying the monitor of information on the neighbor of the monitored person, a wireless ID tag possessed by the monitored person and possessed by the monitored person by tag information receiving means The tag information of the wireless ID tag is received from the monitored person terminal for detecting the tag, stored in the tag information storage means, and the neighbor information acquisition means corresponding to the tag information by the neighbor information acquisition means. The neighbor information corresponding to the tag information received by the tag information receiving means is obtained from the neighbor information storage means in which information is stored, and the tag is stored in the tag information storage means for a predetermined time by the information adding means. If the information is stored, the message including the neighbor information includes information indicating that the monitored person is with the neighbor having the tag information, and the message transmission means. , And transmits the message to the monitoring terminal to the monitored person possessed neighbor notification method, wherein there is provided that.
Thereby, the neighbor information of the neighbors around the monitored person is notified to the monitor.

  In the neighbor notification program of the present invention, tag information of a wireless ID tag possessed by neighbors around the monitored person is received from the monitored person terminal. Then, the neighbor information corresponding to the received tag information is acquired from the neighbor information storage means, and a message including the acquired neighbor information is transmitted to the monitor terminal of the monitor.

  Accordingly, the neighbor information of neighbors around the monitored person is notified to the monitor, so that the supervisor can know what kind of neighbors are around the monitored person. In addition, it is possible to know that there are no neighbors around the monitored person.

Hereinafter, the principle of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram for explaining the outline of the neighbor notification program. In the figure, a computer 1, a monitored person terminal 2, a monitoring person terminal 3, and wireless ID tags 4a and 4b are shown. The monitored person terminal 2 is a terminal possessed by the monitored person. The monitor terminal 3 is a terminal possessed by a monitor who monitors the monitored person. The wireless ID tags 4a and 4b are wireless ID tags possessed by neighbors in order to detect what kind of person is around the monitored person.

  The computer 1 has the functions of tag information receiving means 1a, neighbor information acquiring means 1c, and message sending means 1d by executing the neighbor notification program. The computer 1 also has a neighbor information storage unit 1b that stores neighbor information of neighbors corresponding to the tag information of the wireless ID tags 4a and 4b possessed by the neighbors. The tag information is the tag ID of the wireless ID tags 4a and 4b, and the neighbor information is the name of the neighbor. For example, if the names of neighbors possessing the wireless ID tags 4a and 4b are A and B and the tag IDs are A1 and B1, A and A1 and B and B1 are associated with the neighbor information storage means 1b. It is remembered.

The monitored person terminal 2 acquires the tag information when the wireless ID tags 4a and 4b approach the predetermined range. The monitored person terminal 2 wirelessly transmits the acquired tag information to the computer 1.
The tag information receiving unit 1 a of the computer 1 receives tag information from the monitored person terminal 2.

The neighbor information acquisition unit 1c acquires the neighbor information corresponding to the received tag information from the neighbor information storage unit 1b.
The message transmission unit 1 d transmits a message including the neighbor information acquired by the neighbor information acquisition unit 1 c to the supervisor terminal 3. The neighbor information is, for example, the name of the neighbor as described above. Therefore, the message indicates that there are A and B around the monitored person, for example. Thereby, the monitor can know what kind of person is around the monitored person.

  When the tag information receiving unit 1a does not receive the tag information of the wireless ID tags 4a and 4b from the monitored person terminal 2, the neighbor information acquiring unit 1c receives the neighbor information from the neighbor information storing unit 1b. can not get. In this case, the message indicates that there are no neighbors around the monitored person.

  Thus, the tag information of the wireless ID tags 4a and 4b possessed by the neighbors around the monitored person is received from the monitored person terminal 2. And the neighbor information corresponding to the received tag information is acquired from the neighbor information storage means 1b, and a message including the acquired neighbor information is transmitted to the monitor terminal 3 of the monitor.

  Accordingly, the neighbor information of neighbors around the monitored person is notified to the monitor, so that the monitor can know what kind of neighbor is in the vicinity of the monitored person. In addition, it is possible to know that there are no neighbors around the monitored person. Moreover, the guardian can be relieved by being able to know what kind of neighbors are around the monitored person.

Next, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 2 is a diagram illustrating a system configuration example of the neighbor notification device. The neighbor notification device 10 shown in the figure is managed by the management center 10a. The neighbor notification device 10 is connected to the networks 50a and 50b. The networks 50a and 50b are separately shown in the figure, but are connected to each other to form one network. The networks 50a and 50b are, for example, the Internet.

  The neighbor notification device 10 acquires information on the child terminals 30 to 34 existing around from the child terminals 30 to 34. The neighbor notification device 10 detects, based on information received from the children's terminals 30 to 34, what kind of children are present around a certain child or no one is present in the vicinity. To do. The neighbor notification device 10 transmits the detected result to the guardian's terminal 40 possessed by the guardian of the child.

  The child terminals 30 to 34 are terminals owned by a child monitored by a guardian. The child terminals 30 to 34 communicate wirelessly with, for example, a base station, and exchange information with the neighbor notification device 10 via the network 50a.

  The child terminals 30 to 34 have a built-in wireless ID tag. The wireless ID tag emits radio waves including information on a unique tag ID (tag number). The child terminals 30 to 34 sense radio waves from the radio ID tags of the child terminals 30 to 34 existing in the vicinity, and transmit the tag numbers included in the sensed radio waves to the neighbor notification device 10.

  The reach of radio waves emitted by the wireless ID tag is determined. Therefore, for example, the child terminal 30 can receive only the radio waves of the wireless ID tags of the child terminals 31 to 33 existing within the range 60 shown in the figure. On the other hand, the child terminal 30 cannot receive the radio wave of the wireless ID tag of the child terminal 34 existing outside the range 60.

  The guardian's terminal 40 is a terminal possessed by a child guardian. For example, the guardian's terminal 40 communicates wirelessly with a base station and exchanges information with the neighbor notification device 10 via the network 50b. For example, a mobile phone can be applied to the guardian's terminal 40.

  The child terminals 30 to 34 sense radio waves from surrounding wireless ID tags, and acquire the tag numbers of the wireless ID tags of the child terminals 30 to 34 existing in the surroundings. For example, the child terminal 30 acquires the tag number of the wireless ID tag of the child terminals 31 to 33. The child terminal 30 transmits the acquired tag number of the wireless ID tag to the neighbor notification device 10.

  The neighbor notification device 10 acquires information (for example, name) of a child (a child who owns the child terminals 31 to 34) existing around the child who owns the child terminal 30 from the received tag number. And the neighbor notification apparatus 10 transmits the information of the child who exists around the child to the guardian of the child who possesses the child terminal 30.

Thereby, the guardian of the child who owns the child terminal 30 can recognize that there is a child who possesses the child terminals 31 to 33 around his child.
If the child terminals 31 to 33 do not exist within the range 60 and the child terminal 30 cannot acquire the tag numbers of the surrounding child terminals 31 to 34, the neighbor notification device 10 The guardian is notified that no one exists around the terminal 30 for use. Thereby, the guardian can recognize that no one is around his / her child.

  The guardian's terminal 40 may also incorporate a wireless ID tag. In this case, the guardian's terminal 40 is also detected by the neighbor notification device 10 as a person around the child.

  Moreover, the child terminals 30 to 34 can also request the neighbor notification device 10 not to notify the guardian of surrounding information when receiving the tag number of the guardian of the child. When the neighbor notification device 10 receives this request from the child terminals 30 to 34, the neighbor notification device 10 stops notifying the guardian of information around the child. This is because when the guardian is near his child, the guardian does not need to know information around the child.

  In addition, the neighbor notification device 10 determines whether or not there is a guardian of the child around the child based on the tag number received from the child terminals 30 to 34, and notifies the guardian of the information around the child. Can also be stopped.

Next, a hardware configuration example of the neighbor notification device 10 and the child terminal 30 illustrated in FIG. 2 will be described. First, a hardware configuration example of the neighbor notification device 10 will be described.
FIG. 3 is a diagram illustrating a hardware configuration example of the neighbor notification device. The neighbor notification device 10 is configured by a computer such as a server. As shown in the figure, the entire neighbor notification device 10 is controlled by a CPU (Central Processing Unit) 11. A random access memory (RAM) 12, a hard disk drive (HDD) 13, a graphic processing device 14, an input interface 15, and a communication interface 16 are connected to the CPU 11 via a bus 17.

  The RAM 12 temporarily stores at least part of an OS (Operating System) program and application programs to be executed by the CPU 11. The RAM 12 stores various data necessary for processing by the CPU 11.

The HDD 13 stores an OS, application programs, and various data.
A monitor 18 is connected to the graphic processing device 14. The graphic processing device 14 displays an image on the monitor 18 in accordance with a command from the CPU 11.

  A keyboard 19 and a mouse 20 are connected to the input interface 15. The input interface 15 transmits signals sent from the keyboard 19 and the mouse 20 to the CPU 11 via the bus 17.

The communication interface 16 exchanges data with the networks 50a and 50b in accordance with instructions from the CPU 11.
Next, a hardware configuration example of the child terminal 30 shown in FIG. 2 will be described.

  FIG. 4 is a diagram illustrating a hardware configuration example of the child terminal. As shown in the figure, the entire device of the child terminal 30 is controlled by a CPU 30a. The CPU 30a is connected to a storage unit 30b, a wireless ID tag sensor unit 30c, a wireless ID tag unit 30d, a control button 30e, an LED 30f, and a communication unit configured by a storage device such as a ROM (Read Only Memory) or a RAM via a bus 30h. The part 30g is connected.

  The storage unit 30b stores an OS program and application programs to be executed by the CPU 30a. The storage unit 30b stores various data necessary for processing by the CPU 30a.

The wireless ID tag sensor unit 30c receives radio waves from wireless ID tags mounted on the other child terminals 31 to 34.
The wireless ID tag unit 30d has a wireless ID tag. As described above, the wireless ID tag has a unique tag number. As the wireless ID tag, for example, there is an active tag system of 315 MHz band. This wireless ID tag has a built-in battery and can exchange information by itself. The reach of radio waves is several tens of meters. In addition, the wireless ID tag includes a UHF band high output type. The frequency of the radio wave is 950 MHz, and the reach of the radio wave is about 5 m.

  The control button 30e is a button that is pressed when the child wants to notify the guardian of information about his / her neighbors. The CPU 30a periodically acquires the tag number of the neighbor's wireless ID tag by the wireless ID tag sensor unit 30c and transmits it to the neighbor notification device 10, but the child arbitrarily notifies the guardian of the neighbor's information. You may want to In this case, the child can arbitrarily transmit surrounding information (neighbor information) to the neighbor notification device 10 by pressing the control button 30e.

  The LED 30f displays a message from the guardian's terminal 40 possessed by the guardian. For example, it is assumed that the lighting of the LED 30f corresponds to the message “Please go home”. When the guardian wants the child to go home, he / she operates the guardian's terminal 40 so that the LED 30f is lit. The CPU 30a turns on the LED 30f according to an instruction from the guardian's terminal 40, and the child can recognize that the child must go home by turning on the LED 30f. Similarly, the guardian can turn off the LED 30f by operating the guardian's terminal 40.

The communication unit 30g performs wireless communication with the base station according to an instruction from the CPU 30a, and exchanges information with the neighbor notification device 10 via the network 50a.
In addition, although the hardware structural example of the child terminal 30 was demonstrated above, the child terminals 31-34 also have the same hardware structure.

  Further, in the case of a child who does not require safety confirmation (neighbor information), the child terminals 30 to 34 have only the wireless ID tag portion 30d. This child is detected only as the neighbor information of the child whose safety needs to be confirmed.

Moreover, the terminals 30 to 34 for children preferably have shapes that are easy for children to carry. For example, it is preferable to use a card shape so as to be in a school bag or a pocket of clothes.
In addition, as described above, in the case of a child who does not require safety confirmation, the child terminals 30 to 34 can be configured only by the wireless ID tag unit 30d, and thus can be reduced in size and more easily carried.

Further, the child terminals 31 to 34 can be configured by adding the wireless ID tag sensor unit 30c and the wireless ID tag unit 30d to an information terminal such as a mobile phone.
Next, various information managed by the neighbor notification device 10 will be described. First, the guardian information managed by the neighbor notification device 10 will be described.

  FIG. 5 is a diagram illustrating a data configuration example of the guardian information DB. The guardian information DB (database) 71 shown in the figure is constructed in the HDD 13 of the neighbor notification device 10, for example. The guardian information DB 71 stores guardian information for notifying child neighbor information.

As shown in the drawing, the guardian information DB 71 has columns of a management number, name, mobile number, email address, safety confirmation child tag number, third party commission, and third party commission management number.
In the management number column, the management number assigned to the guardian who receives the neighbor information of the child is stored. The management number is given, for example, when a guardian and a child join the service of the management center 10a.

The name column stores the name of the guardian who receives notification of the child's neighbor information.
In the mobile number column, the telephone number of the guardian's terminal 40 possessed by the guardian is stored.
The mail address column stores the mail address of the guardian's terminal 40 possessed by the guardian. By sending the child's neighbor information to the e-mail address, the child's neighbor information can be notified to the guardian.

  In the safety confirmation child tag number column, the tag number of the child who wants to notify the guardian's neighborhood information is stored. For example, the tag number of the wireless ID tag of the child terminals 30 to 34 possessed by the child of the guardian is stored.

  The third party consignment field stores information on whether or not to notify the third party of the child's neighbor information. For example, if information indicating “invalid” is stored in this field, the neighbor information of the child is not notified to the third party, but is notified to the guardian. On the other hand, if information indicating “valid” is stored, the neighbor information of the child is notified to the third party, not the guardian. Thus, by notifying the third party of the child's neighbor information, for example, even if the guardian cannot monitor the child, it can be monitored by the third party. The third party who should notify the neighbor information is designated by the guardian when the guardian makes a contract to receive this service, for example.

The third party commissioned management number column stores a third party management number to be notified of the child's neighbor information.
For example, in the illustrated example, the management number of “Taro Suzuki” is “2”. The mobile phone number of the guardian's terminal 40 possessed by “Taro Suzuki” is “xxx-xxxx-2223”. The email address is 'xx @ xxxxxxx'. The tag number of the wireless ID tag of the child who wants to notify the neighbor information of “Taro Suzuki” is “000C”. The third party consignment is “valid”, and the person who wants to notify the neighbor information is “Takahashi Hajime” whose management number is “3”.

Next, personal information managed by the neighbor notification device 10 will be described.
FIG. 6 is a diagram illustrating a data configuration example of the personal information DB. The personal information DB 72 shown in the figure is constructed in, for example, the HDD 13 of the neighbor notification device 10. The personal information DB 72 stores personal information of a person who receives the service of the management center 10a and personal information of a person who possesses only a wireless ID tag (a person who is registered only as a neighbor).

As shown in the figure, the personal information DB 72 has columns of management number, name, ID tag number, communication number, guardian management number, and special ID tag number.
A management number assigned to a person registered in the personal information DB 72 is stored in the management number column.

In the name column, the names of persons registered in the personal information DB 72 are stored.
In the column of the ID tag number, only the tag number of the wireless ID tag of the child terminals 30 to 34 possessed by the child, the tag number of the wireless ID tag of the guardian terminal 40 possessed by the guardian, and the wireless ID tag only Stores the tag number of the owner.

  In the communication number column, a number for communicating with the child terminals 30 to 34 possessed by the child is stored. For example, the neighbor notification device 10 can transmit the predetermined information to the child terminals 30 to 40 by transmitting the predetermined information to the number stored in the communication number column.

In the parental control number column, the management number of the parental guardian of the child is stored. In the case of a guardian, a management number assigned to the guardian is stored.
The special ID tag number column stores the tag number of the wireless ID tag that stops the notification of the neighbor information. In this special ID tag number column, for example, the tag number of the wireless ID tag of the guardian's terminal 40 possessed by the guardian of the child is stored. Therefore, for example, if the child terminals 30 to 34 receive the tag number in the special ID tag number column, the neighbor notification device 10 stops the notification of the neighbor information to the guardian. That is, when the tag number of the special ID tag number is detected by the child terminals 30 to 34, it is determined that there is a guardian near the child, and the notification of the neighbor information to the guardian is stopped. To do.

  For example, in the illustrated example, “Fujitaro” and “Fuji Hanako” are children of “Fuji Yoko” shown in FIG. The management number of “Fujitaro” is “1”. The management number of “Fuji Hanako” is “2”. The tag number for 'Fujitaro' is '000A'. The tag number of 'Fuji Hanako' is '000B'. The communication number for ‘Fujitaro’ is ‘xxx-xxxx-1111’. The communication number for ‘Fuji Hanako’ is ‘xxx-xxxx-1234’.

  The guardian management number for ‘Fujitaro’ and ‘Fuji Hanako’ is ‘1’. Here, from the guardian information DB 71 shown in FIG. 5, since the guard with management number “1” is “Fuji Yoko”, the guardians of “Fuji Taro” and “Fuji Hanako” are “Fuji Yoko”. It turns out that it is.

  The special ID tag numbers for ‘Fujitaro’ and ‘Fuji Hanako’ are ‘001E’. Here, it is assumed that the tag number of the guardian's terminal 40 possessed by “Fuji Yoko” is “001E”. In this case, when the child terminals 30 to 34 possessed by “Fuji Taro” and “Fuji Hanako” detect “001E”, the neighbor notification device 10 is a guardian of “Fuji Taro” and “Fuji Hanako”. Stops notification of neighbor information to a certain Yoko Fuji. That is, when the guardian is near the child, the neighbor notification device 10 does not notify the guardian of the neighbor information.

  The personal information DB 72 can function as a neighbor information DB. That is, the neighbor notification device 10 can obtain information (for example, name) of people around the monitored child by referring to the personal information DB 72.

  Further, as an additional function, anonymous information may be stored in the personal information DB 72 so that the name of the child can be notified anonymously as neighbor information to be notified to the guardian. Moreover, you may make it store age so that the guardian can also be notified of the age of the person who exists around as neighbor information.

  Next, grouping management information managed by the neighbor notification device 10 will be described. Parents may want to manage multiple children in groups. For example, a parent may want to know if a child is acting with a group or acting apart from the group. In this case, the neighbor notification device 10 manages the child based on the grouping management information, and can notify the guardian of whether or not the child is acting away from the group.

  FIG. 7 is a diagram illustrating a data configuration example of the grouping management information DB. The grouping management information DB 73 shown in the figure is constructed in the HDD 13 of the neighbor notification device 10, for example. The grouping management information DB 73 stores information on children managed in groups.

  As shown in the figure, the grouping management information DB 73 has columns for a management number, a guardian management number, an intra-group radio ID tag number 1, an intra-group radio ID tag number 2,..., And an intra-group radio ID tag number n. is doing.

The management number assigned to each group is stored in the management number column.
The parental management number column stores the parental management number for notifying the neighbor information of the group managed children.

The group radio ID tag number 1, the intra-group radio ID tag number 2,..., And the intra-group radio ID tag number n store the tag numbers of children managed in groups.
For example, in the example of the figure, the guardian management numbers of the group management number “1” are “3” and “4”. Therefore, it can be seen from the management numbers “3” and “4” in the parental information DB 71 shown in FIG. 5 that the parental guardian of the group is “Kazutaka Takahashi” and “Jiro Tanaka”.

  The in-group wireless ID tag numbers 1 to 3 are “000A”, “000C”, and “000D”. Therefore, it can be seen from the ID tag number of the personal information DB 72 shown in FIG. 6 that the group-managed child is “Fujitaro” “Ichiro Suzuki” “Hideki Takahashi”.

  Next, information logged by the neighbor notification device 10 will be described. The neighbor notification device 10 logs the tag number transmitted from the child terminals 30 to 34 for each child. Thus, the tag numbers of the child terminals 30 to 34 existing around the child can be known, and the names of the children existing around the child can be known from the personal information DB 72 shown in FIG.

  FIG. 8 is a diagram illustrating a data configuration example of the log DB. The log DB 74 shown in the figure is constructed in, for example, the HDD 13 of the neighbor notification device 10. The log DB 74 stores the tag number of the wireless ID tag detected by the child terminals 30 to 34 possessed by the monitored child.

As shown in the figure, the log DB 74 has columns for sequence number, date, time, and neighbor wireless ID tag number.
A sequence number indicating the order in which the tag numbers are received from the child terminal is stored in the sequence number column. The sequence number is given by incrementing by one in the order in which the tag numbers are received.

In the date column, the date when the tag number is received from the child terminal is stored.
The time when the tag number is received from the child terminal is stored in the time column.
The tag number received from the child terminal is stored in the neighborhood wireless ID tag number column.

  For example, in the example of the figure, it can be seen that the neighbor notification device 10 stores the tag number in the log DB 74 every 3 minutes. It can be seen that the sequence number “2” received the tag numbers “000B” and “000C” at the time “15:03” of “2005/8/29”. In other words, at the time “15:03” of “2005/8/29”, there were children with tag numbers “000B” and “000C” around the children managed by the log DB 74. I understand.

Note that “-” in the figure indicates that the tag number has not been received. That is, in the case of “−”, it indicates that there was no person around the child.
Next, a screen example of neighbor information displayed on the display device included in the guardian's terminal 40 will be described.

  FIG. 9 is a diagram illustrating an example of neighbor information displayed on the guardian's terminal when a child is acting alone. The screen 81 in the figure shows a screen example displayed on the guardian's terminal 40 when 'Fujitaro' is acting alone.

  If the neighbor notification device 10 detects that there is no person around ‘Fujitaro’ for a predetermined time, it determines that ‘Fujitaro’ is acting alone. That is, if the tag number is not received from the child terminal of “Fujitaro” even after the predetermined time has elapsed, the neighbor notification device 10 determines that “Fujitaro” is acting alone.

The neighbor notification device 10 transmits the determined neighbor information to the guardian's guardian terminal 40 and causes the display device of the guardian's terminal 40 to display the screen 81.
FIG. 10 is a diagram illustrating an example of neighbor information displayed on the guardian's terminal when a child is acting with another child. The screen 82 in the figure shows a screen example displayed on the guardian's terminal 40 when “Fujitaro” is acting with “Fuji Hanako” “Hideki Takahashi” “Tatsuya Yamaguchi”.

  When the neighbor notification device 10 detects that “Fuji Taro”, “Hideki Takahashi” and “Tatsuya Yamaguchi” are present around “Fuji Taro” for a predetermined time, “Fuji Taro” is around it. Judged acting with 'Hanako Fuji, Hideki Takahashi' Tatsuya Yamaguchi '. That is, when the neighbor notification device 10 continues to receive the tag number of “Fuji Hanako” “Hideki Takahashi” “Tatsuya Yamaguchi” from the child terminal of “Fuji Taro” for a predetermined time, “Fuji Taro” Judged acting with Fuji Hanako "Hideki Takahashi" Tatsuya Yamaguchi.

The neighbor notification device 10 transmits the determined neighbor information to the guardian's guardian terminal 40 and causes the display device of the guardian's terminal 40 to display the screen 82.
FIG. 11 is a diagram showing an example of neighbor information displayed on the guardian's terminal when there are people around the child but not acting together. The screen 83 in the figure shows an example of a screen displayed on the parent terminal 40 when “XXXX” and “YYYY” exist around “Fujitaro” but are not acting together. Yes.

  The neighbor notification device 10 detects that “XXXX” YYYY ”exists around“ Fujitaro ”, but if the existing time has not elapsed for a predetermined time,“ Fujitaro ” Determines that “XXXX” YYYY ”is around but is not acting together. That is, the neighbor notification device 10 receives the tag number “XXXX” YYYY from the child terminal of “Fujitaro”, but if the reception time has not passed the predetermined time, There is' XXXX 'YYYY' around 'Taro', but it is judged that they are not acting together.

The neighbor notification device 10 transmits the determined neighbor information to the guardian's guardian terminal 40 and causes the display device of the guardian's terminal 40 to display the screen 83.
When the tag number of “XXXX” YYYY ”is continuously received for a predetermined time, the neighbor notification device 10 uses“ XXXX ”YYYY” as described in FIG. Will be determined to be acting together.

  FIG. 12 is a diagram illustrating an example of neighbor information displayed on the guardian's terminal when there is no person around the child but not acting alone. The screen 84 in the figure shows an example of a screen displayed on the guardian's terminal 40 when there is no person around “Taro Fuji”.

  The neighbor notification device 10 determines that there is no person around 'Fuji Taro' when there is no person around 'Fuji Taro' but the state has not yet passed for a predetermined time. That is, the neighbor notification device 10 does not receive the tag number from the child terminal of “Fujitaro”, but if the state has not elapsed for a predetermined time, Judge that there is no one.

The neighbor notification device 10 transmits the determined neighbor information to the guardian's guardian terminal 40 and causes the display device of the guardian's terminal 40 to display the screen 84.
When a predetermined time has elapsed without receiving the tag number, the neighbor notification device 10 determines that “Taro Fuji” is acting alone as described in FIG.

  FIG. 13 is a diagram illustrating an example of neighbor information displayed on the guardian's terminal when a group-managed child is acting away from the group. The screen 85 in the figure shows an example of a screen displayed on the guardian's terminal 40 when the group-managed 'Fuji Taro' is acting alone.

  If the neighbor notification device 10 detects that there is no child group-managed with “Fujitaro” around “Fujitaro” for a predetermined time, “Fujitaro” is acting away from the group. Judge. However, when a person outside the group exists around, the neighbor information of the person is displayed. That is, if the neighbor notification device 10 does not receive the tag number of another child managed by the group from the child terminal of “Fujitaro” even after a predetermined time has elapsed, “Fujitaro” Judge that you are acting away from

The neighbor notification device 10 transmits the determined neighbor information to the guardian's guardian terminal 40 and causes the display device of the guardian's terminal 40 to display the screen 85.
Next, the transmission timing of the neighbor information (notification message) transmitted from the neighbor notification device 10 to the guardian's terminal 40 and the contents thereof will be described.

FIG. 14 is a diagram showing a log DB for explaining a notification message transmission timing and its contents. It is assumed that the log DB 91 shown in the drawing shows a log example of “Fujitaro”.
The neighbor notification device 10 may automatically transmit a notification message to the guardian's terminal 40 or may transmit a notification message in response to an inquiry from the guardian. When the neighbor notification device 10 automatically transmits the notification message, the neighbor notification device 10 transmits the notification message only when the child is in a situation to warn the guardian, for example, acting alone.

  First, automatic notification when 'Fujitaro' is not group-managed will be described. The neighbor notification device 10 edits the following notification message based on the log DB 91 and transmits it to the guardian's terminal 40.

  At 15:03, it can be seen that 'Fuji Hanako' and 'Ichiro Suzuki' are around 'Fujitaro'. Therefore, the neighbor notification device 10 does not edit the notification message and does not transmit it to the guardian's terminal 40.

  The tag numbers “000B” and “000C” shown in the log DB 91 in FIG. 14 are known as “Fuji Hanako” and “Ichiro Suzuki” from the personal information DB 72 in FIG. Further, it can be seen from the personal information DB 72 of FIG. 6 that the management number (guardian management number) of the guardian who should notify the neighbor information of “Fujitaro” is “1”. From the guardian information DB 71 of FIG. 5, it can be seen that the guardian who should notify the neighbor information of “Fujitaro” is “Fuji Yoko”. You can also find the contact email address of 'Fuji Yoko'.

  At 15:06, it can be seen that there is 'Fuji Hanako', 'Ichiro Suzuki' and 'Tatsuya Yamaguchi' around 'Fujitaro'. Therefore, the neighbor notification device 10 does not transmit a notification message to the guardian's terminal 40. Note that the tag number “000E” is “Tatsuya Yamaguchi” from the personal information DB 72 of FIG.

  Similarly, from 15:09 to 15:15, “Fujitaro” is surrounded by “Ichiro Suzuki”, “Tatsuya Yamaguchi” and “Hideki Takahashi”, so the neighbor notification device 10 protects the notification message. It does not transmit to the terminal 40 for people. Note that the tag number “000D” is “Hideki Takahashi” from the personal information DB 72 of FIG.

  At 15:18, there is no person around 'Fuji Taro', but the neighbor notification device 10 does not transmit a notification message to the guardian's terminal 40. This is because, as described above, the neighbor notification device 10 determines that “Fujitaro” is acting alone after a predetermined time has elapsed. The current situation is a situation in which it is judged that there is no one around 'Fujitaro'.

  In the following description, if the neighbor notification device 10 is in a state where no one is around the child for 3T (T indicates the period of logging by the neighbor notification device 10), the child is acting alone. Assume that

  At 15:21 there are no people around 'Fujitaro'. Since only 2T has passed when there is no person around 'Taro Fuji,' the neighbor notification device 10 does not transmit a notification message to the guardian's terminal 40.

  At the time of 15:24, as shown in the figure, since there was no person around 'Fujitaro' for 3T, the neighbor notification device 10 notifies that 'Fujitaro' is acting alone. Edit the message. Then, the neighbor notification device 10 transmits the edited notification message to the guardian's terminal 40.

As described above, the notification message is automatically notified when the child should warn the guardian, for example, 'Fujitaro' is acting alone.
From 15:27 to 15:33, since “Tatsuya Yamaguchi” “Hideki Takahashi” exists around “Fujitaro”, the neighbor notification device 10 does not transmit the notification message to the guardian's terminal 40.

As described above, the notification message is automatically notified when 'Fujitaro' is not group-managed.
Next, automatic notification when “Fujitaro” is group-managed will be described. Assume that “Fujitaro” is group-managed as shown in the grouping management information DB 73 of FIG. In other words, it is assumed that “Fujitaro” constitutes a group of “Ichiro Suzuki (tag number 000C)” and “Hideki Takahashi (tag number 000D)”.

The neighbor notification device 10 edits the following notification message based on the log DB 91 in FIG. 14 and the grouping management information DB 73 in FIG. 7 and transmits the notification message to the guardian's terminal 40.
At 15:03, 15:06, it can be seen that there is “Ichiro Suzuki” of the same group around “Fujitaro”. Therefore, the neighbor notification device 10 does not edit the notification message and does not transmit it to the guardian's terminal 40.

  At 15:09 and 15:12, it can be seen that there are “Ichiro Suzuki” and “Hideki Takahashi” of the same group around “Fujitaro”. Therefore, the neighbor notification device 10 does not edit the notification message and does not transmit it to the guardian's terminal 40.

  At 15:15, there are no children in the same group around 'Fujitaro', but there is 'Tatsuya Yamaguchi'. Therefore, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” exists around “Fujitaro” but is acting away from the group. Then, the neighbor notification device 10 transmits the edited notification message to the guardian's terminal 40.

As described above, the notification message is automatically notified when a situation that should be notified to the guardian is reached, such as “Fujitaro” has left the group.
At 15:18, there is no person around “Fujitaro”, but the neighbor notification device 10 does not transmit a notification message to the guardian's terminal 40. This is because the time spent alone in “Fujitaro” has not passed 3T.

  At 15:21, there is no person around 'Fujitaro', but the neighbor notification device 10 does not transmit a notification message to the guardian's terminal 40. This is because the time spent alone in Fujitaro has not passed 3T.

  At 15:24, since there is no person around “Taro Fuji” for 3T, the neighbor notification device 10 edits a notification message that “Taro Fuji” is acting alone. Then, the neighbor notification device 10 transmits the edited notification message to the guardian's terminal 40.

As described above, the notification message is automatically notified when a situation that should warn the guardian, such as “Fujitaro” acting alone, is performed.
At 15:27, it can be seen that there are no children of the same group around “Fujitaro” but “Tatsuya Yamaguchi” is present. Therefore, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” exists around “Fujitaro” but is acting away from the group. Then, the neighbor notification device 10 transmits the edited notification message to the guardian's terminal 40.

  At the time of 15:30 and 15:33, since “Hideki Takahashi” of the same group exists around “Fujitaro”, the neighbor notification device 10 does not transmit the notification message to the guardian's terminal 40.

As described above, the notification message is automatically notified when 'Fujitaro' is group-managed.
Next, a case where a notification message is transmitted in response to an inquiry from a guardian will be described. First, an inquiry notification when 'Fujitaro' is not group-managed will be described. The neighbor notification device 10 edits the following notification message based on the log DB 91 and transmits it to the guardian's terminal 40.

  It is assumed that there is an inquiry from a guardian at each time point shown below. Also, if the child stays with another child for 2T, it is determined that the child is with (acts with) the other child.

  At 15:03, it can be seen that 'Fuji Hanako' and 'Ichiro Suzuki' are around 'Fujitaro'. It has been 2T for the time that “Fuji Hanako” and “Ichiro Suzuki” are around “Fujitaro”. Therefore, the neighbor notification device 10 edits a notification message that “Fujitaro” is with “Fuji Hanako” and “Ichiro Suzuki” and transmits the notification message to the guardian's terminal 40.

  At 15:06, it can be seen that there is 'Fuji Hanako', 'Ichiro Suzuki' and 'Tatsuya Yamaguchi' around 'Fujitaro'. As for 'Tatsuya Yamaguchi', 2T hasn't passed around 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message that “Fujitaro” is with “Fuji Hanako” and “Ichiro Suzuki” and transmits the notification message to the guardian's terminal 40.

  At 15:09, it can be seen that there is 'Ichiro Suzuki' 'Hideki Takahashi' around 'Fujitaro'. As for 'Hideki Takahashi', 2T has not been around for 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message that “Fujitaro” is with “Ichiro Suzuki” and transmits it to the guardian's terminal 40.

  At 15:12, it can be seen that there is 'Hideki Takahashi' around 'Fujitaro'. As for ‘Hideki Takahashi’, 2T has passed around ‘Fujitaro’. Therefore, the neighbor notification device 10 edits a notification message indicating that “Fujitaro” is with “Hideki Takahashi” and transmits it to the guardian's terminal 40.

  At 15:15, it can be seen that there is 'Tatsuya Yamaguchi' around 'Fujitaro'. However, for Tatsuya Yamaguchi, 2T hasn't been around for two years. Therefore, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” is around “Fujitaro” but is not acting together, and transmits the notification message to the guardian's terminal 40.

  At 15:18 there are no people around 'Fujitaro'. Therefore, the neighbor notification device 10 edits a notification message indicating that there is no one around 'Fujitaro' and transmits it to the guardian's terminal 40.

  At 15:21, there are no people around 'Fujitaro'. Therefore, the neighbor notification device 10 edits a notification message indicating that there is no one around ‘Fujitaro’ and transmits it to the guardian's terminal 40.

  At 15:24, there is nobody around “Taro Fuji” for 3T. Therefore, the neighbor notification device 10 determines that 'Fujitaro' is acting alone, edits a notification message to that effect, and transmits it to the guardian's terminal 40.

  At 15:27, it can be seen that there is 'Tatsuya Yamaguchi' around 'Fujitaro'. However, for Tatsuya Yamaguchi, 2T hasn't been around for two years. Therefore, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” is around “Fujitaro” but is not acting together, and transmits the notification message to the guardian's terminal 40.

  At 15:30, you can see that there is 'Hideki Takahashi' around 'Fujitaro'. As for 'Hideki Takahashi', 2T has not been around for 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message indicating that “Hideki Takahashi” is around “Fujitaro” but is not acting together, and transmits it to the guardian's terminal 40.

  At 15:33, it can be seen that there is 'Hideki Takahashi' around 'Fujitaro'. As for ‘Hideki Takahashi’, 2T has passed around ‘Fujitaro’. Therefore, the neighbor notification device 10 edits a notification message indicating that “Fujitaro” is acting with “Hideki Takahashi”, and transmits it to the guardian's terminal 40.

As described above, the notification message is inquired when 'Fujitaro' is not group-managed.
Next, an inquiry notification when 'Fujitaro' is managed in a group will be described. Assume that “Fujitaro” is group-managed as shown in the grouping management information DB 73 of FIG. The neighbor notification device 10 edits the following notification message based on the log DB 91 in FIG. 14 and the grouping management information DB 73 in FIG. 7 and transmits the notification message to the guardian's terminal 40.

  At 15:03, it can be seen that 'Fuji Hanako' and 'Ichiro Suzuki' are around 'Fujitaro'. It has been 2T for the time that “Fuji Hanako” and “Ichiro Suzuki” are around “Fujitaro”. Therefore, the neighbor notification device 10 edits a notification message indicating that “Taro Fuji” is acting together with “Hanako Fuji” and “Ichiro Suzuki” and transmits the notification message to the guardian's terminal 40.

  At 15:06, it can be seen that there is 'Fuji Hanako', 'Ichiro Suzuki' and 'Tatsuya Yamaguchi' around 'Fujitaro'. As for 'Tatsuya Yamaguchi', 2T hasn't passed around 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message indicating that “Taro Fuji” is acting together with “Hanako Fuji” and “Ichiro Suzuki” and transmits the notification message to the guardian's terminal 40.

  At 15:09, it can be seen that there is 'Ichiro Suzuki' 'Hideki Takahashi' around 'Fujitaro'. As for 'Hideki Takahashi', 2T has not been around for 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message indicating that “Fujitaro” is acting with “Ichiro Suzuki” and transmits it to the guardian's terminal 40.

  At 15:12, it can be seen that there is 'Hideki Takahashi' around 'Fujitaro'. As for ‘Hideki Takahashi’, 2T has passed around ‘Fujitaro’. Therefore, the neighbor notification device 10 edits a notification message that “Fujitaro” is acting with “Hideki Takahashi” and transmits it to the guardian's terminal 40.

  At 15:15, it can be seen that there is 'Tatsuya Yamaguchi' around 'Fujitaro'. “Tatsuya Yamaguchi” is not group-managed with “Fujitaro”. Accordingly, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” is around “Fujitaro” but is acting away from the group members, and sends it to the guardian's terminal 40. Send.

  At 15:18 there are no people around 'Fujitaro'. Therefore, the neighbor notification device 10 edits a notification message indicating that there is no one around 'Fujitaro' and transmits it to the guardian's terminal 40.

  At 15:21, there are no people around 'Fujitaro'. Therefore, the neighbor notification device 10 edits a notification message indicating that there is no one around 'Fujitaro' and transmits it to the guardian's terminal 40.

  At 15:24, there is nobody around “Taro Fuji” for 3T. Therefore, the neighbor notification device 10 determines that 'Fujitaro' is acting alone, edits a notification message to that effect, and transmits it to the guardian's terminal 40.

  At 15:27, it can be seen that there is 'Tatsuya Yamaguchi' around 'Fujitaro'. “Tatsuya Yamaguchi” is not group-managed with “Fujitaro”. Accordingly, the neighbor notification device 10 edits a notification message indicating that “Tatsuya Yamaguchi” is around “Fujitaro” but is acting away from the group members, and sends it to the guardian's terminal 40. Send.

  At 15:30, it can be seen that there is “Hideki Takahashi” of the same group around “Fujitaro”. As for 'Hideki Takahashi', 2T has not been around for 'Taro Fuji'. Therefore, the neighbor notification device 10 edits a notification message indicating that “Hideki Takahashi” is around “Fujitaro” but is not acting together, and transmits it to the guardian's terminal 40.

  At 15:33, it can be seen that there is “Hideki Takahashi” of the same group around “Fujitaro”. As for ‘Hideki Takahashi’, 2T has passed around ‘Fujitaro’. Therefore, the neighbor notification device 10 edits a notification message that “Fujitaro” is acting with “Hideki Takahashi”, and transmits it to the guardian's terminal 40.

As described above, the notification message is inquired when 'Fujitaro' is group-managed.
In the above example, one of the group members (“Fujitaro”) is designated. When the group management number (management number shown in FIG. 7) is designated by the guardian, the neighbor notification device 10 sequentially edits the notification messages of all the group members and transmits them to the guardian.

  Next, the operation of the neighbor notification device 10, the child terminals 30 to 34, and the guardian terminal 40 when the notification message is automatically notified, and the neighbor notification device when the guard message is notified by an inquiry from the guardian 10, operation | movement of the terminals 30-34 for children and the terminal 40 for guardians are demonstrated using a sequence diagram and a flowchart.

First, the operations of the neighbor notification device 10, the child terminals 30 to 34, and the guardian terminal 40 in the case of automatically notifying the notification message will be described.
FIG. 15 is a sequence diagram of a neighbor notification device, a child terminal, and a guardian terminal when automatic notification message notification is performed.

[Step S1] The CPU 30a of the child terminal 30 senses the wireless ID tags of the surrounding child terminals 31 to 34 by the wireless ID tag sensor unit 30c.
[Steps S2 and S3] The CPU 30a of the child terminal 30 transmits the sensed tag number of the wireless ID tag to the neighbor notification device 10 via the communication unit 30g.

[Step S <b> 4] The CPU 11 of the neighbor notification device 10 receives the tag number sensed by the child terminal 30 via the communication interface 16.
[Step S5] The CPU 11 of the neighbor notification device 10 stores the received tag number in the log DB 74 built in the HDD 13. The CPU 11 of the neighbor notification device 10 constructs a log DB 74 for each child. The CPU 11 of the neighbor notification device 10 stores the received tag number in the corresponding child log DB 74.

  [Step S6] The CPU 11 of the neighbor notification device 10 performs notification message processing for automatically generating a notification message to notify the guardian. The notification message process will be described in detail below using a flowchart.

  [Step S7] The CPU 11 of the neighbor notification device 10 transmits the notification message generated by the notification message processing to the guardian's terminal 40 via the communication interface 16.

[Step S8] The guardian's terminal 40 receives the notification message transmitted from the neighbor notification device 10 and displays it on the display device.
Note that the child terminal 30 periodically performs sensing and notifies the neighbor notification device 10 of the tag number. Further, the other child terminals 31 to 34 also periodically perform the sensing similarly to the child terminal 30 and transmit the tag number to the neighbor notification device 10.

  Thus, the neighbor notification device 10 periodically receives the tag numbers from the child terminals 30 to 34 and stores them in the log DB 74 managed for each child. Then, when the situation around the child becomes a situation in which the notification message should be transmitted to the guardian, for example, the child is acting alone, the notification message is automatically generated and transmitted to the guardian's terminal 40. .

Next, the notification message process in step S6 of FIG. 15 will be described in detail.
FIG. 16 is a flowchart of notification message processing.
[Step S11] The CPU 11 of the neighbor notification device 10 determines whether the sensor result has been updated. That is, the CPU 11 of the neighbor notification device 10 determines whether the log DB 74 has been updated. If the log DB 74 has been updated, the process proceeds to step S12. If the log DB 74 is not updated, the process ends.

  [Step S12] The CPU 11 of the neighbor notification device 10 expands certain log information in the log DB 74 in, for example, the work area of the RAM 12. The constant log information refers to the amount of information that can be used to determine whether a child is acting alone. For example, in the case of the example described with reference to FIG. 14, since it is determined that the child is acting alone if there is no other child around for 3T, the information before 3T from the present is constant log information. And will be deployed in the work area.

  [Step S13] The CPU 11 of the neighbor notification device 10 determines whether or not the child is acting alone based on the log information developed in the work area. When determining that the child is acting alone, the CPU 11 of the neighbor notification device 10 generates a notification message to that effect. In addition, the process of step S13 is demonstrated in detail below using a flowchart.

  [Step S14] The CPU 11 of the neighbor notification device 10 determines whether or not it is determined in step S13 that the child is acting alone. If it is determined in step S13 that the child is acting alone, the process proceeds to step S17. If it is determined that the child is not acting alone, the process proceeds to step S15.

  That is, when the child is acting alone, the process proceeds to a notification message transmission process in order to transmit a notification message to that effect to the guardian. On the other hand, when the child is not acting alone, the process proceeds to the determination of whether or not the group is managed. When the group is managed, it is determined whether the child is acting with the group or acting away.

  [Step S15] The CPU 11 of the neighbor notification device 10 determines whether or not the child is a group-managed child. If the child is group-managed, the process proceeds to step S16. If the child is not group-managed, the process proceeds to step S17.

  [Step S16] The CPU 11 of the neighbor notification device 10 determines whether or not the child is moving away from the group based on the log information developed in the work area and the grouping management information DB 73. When the CPU 11 of the neighbor notification device 10 determines that the child is acting away from the group, the CPU 11 generates a notification message to that effect. In addition, the process of step S16 is demonstrated in detail below using a flowchart.

  [Step S17] The CPU 11 of the neighbor notification device 10 determines whether or not the time for sending the notification message has come. If it is time to transmit the notification message, the process proceeds to step S18. If it is not time to transmit the notification message, the process proceeds to step S19.

  [Step S18] The CPU 11 of the neighbor notification device 10 transmits the notification message generated in steps S13 and S16 to the guardian's terminal 40 via the communication interface 16. In addition, the process of step S18 is demonstrated in detail below using a flowchart.

  [Step S19] The CPU 11 of the neighbor notification device 10 increments a counter for counting the transmission time by one. The reason for counting the transmission time is to prevent the same notification message from being repeatedly transmitted to the guardian in a short time.

  As described above, the neighbor notification device 10 determines whether or not the child is acting alone. Also, it is determined whether or not the child is acting away from the group. Then, the notification message is transmitted to the guardian's terminal 40.

Next, the processes of steps S13, S16, and S18 of FIG. 16 will be described in detail in order. First, the single person determination process in step S13 of FIG. 16 will be described.
FIG. 17 is a flowchart of the person determination process.

[Step S21] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the log information for 3T in the log DB 74 read into the work area.
[Step S22] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been detected from the log information of the work area. That is, it is determined whether or not there is a person around the child depending on whether or not the tag number has been detected. If the tag number can be detected, that is, if it is determined that there is a person around the child, it is not necessary to send a notification message to that effect to the guardian, so the processing ends. If the tag number has not been extracted, the process proceeds to step S23.

  [Step S23] The CPU 11 of the neighbor notification device 10 determines whether or not the tag number detection has been completed in all the log information of the work area. When the tag number detection is completed in all the log information of the work area, the process proceeds to step S24. If detection of the tag number has not ended, the process proceeds to step S21 in order to detect the next tag number.

  [Step S24] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that the child is acting alone. The generated notification message is transmitted to the guardian's terminal 40 in step S18 of FIG.

Thus, the neighbor notification device 10 determines whether or not the child is acting alone based on the log information in the log DB 74 developed in the work area.
Next, the group determination process in step S16 in FIG. 16 will be described.

FIG. 18 is a flowchart of the group determination process.
[Step S31] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the current (latest) information of the log information read to the work area.

  [Step S32] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been detected from the log information of the work area. If the tag number can be detected, the process proceeds to step S33. If the tag number cannot be detected, the process proceeds to step S35.

  [Step S33] The CPU 11 of the neighbor notification device 10 determines whether or not the detected tag number is a group member with reference to the grouping management information DB 73. When the detected tag number is a group member, the child is acting together with the group member, so that it is not necessary to generate a notification message, and the process ends. If the detected tag number is not a group member, the process proceeds to step S34.

  [Step S34] The CPU 11 of the neighbor notification device 10 recognizes that the detected tag number is not a member of the group but is a person around the child. In step S31, the next tag number is detected.

  [Step S35] In step S34, the CPU 11 of the neighbor notification device 10 converts the tag number recognized as a person around the child into a name with reference to the personal information DB 72.

  [Step S36] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that there is a person who is away from the group but is not in the group. The generated notification message includes the name obtained in step S35, and is transmitted to the parent terminal 40 in step S18 of FIG.

  As described above, the neighbor notification device 10 determines whether or not the child has left the group and there are people outside the group based on the log information in the log DB 74 and the grouping management information DB 73 developed in the work area. To do.

Next, the notification message transmission process in step S18 of FIG. 16 will be described.
FIG. 19 is a flowchart of the notification message transmission process.
[Step S41] The CPU 11 of the neighbor notification device 10 determines whether or not the notification of the child neighbor information is set as a group. If the group is set, the process proceeds to step S42. If no group is set, the process proceeds to step S43.

[Step S42] The CPU 11 of the neighbor notification device 10 acquires the management number of the child's guardian from the guardian management number of the grouping management information DB 73.
[Step S43] The CPU 11 of the neighbor notification device 10 acquires the management number of the child's guardian from the guardian management number of the personal information DB 72.

  [Step S44] The CPU 11 of the neighbor notification device 10 refers to the guardian information DB 71 by the guardian management number obtained in Step S42 or Step S43, and acquires the guardian's mail address.

[Step S45] The CPU 11 of the neighbor notification device 10 transmits a notification message to the mail address of the guardian via the communication interface 16.
In this way, the guardian who transmits the notification message is specified, and the notification message is transmitted.

  The above is the description of the operation when the notification message is automatically notified. Next, an operation when a notification message is transmitted in response to an inquiry from a guardian will be described using a sequence diagram and a flowchart.

FIG. 20 is a sequence diagram of the close-kin notification device and the guardian terminal when a notification message is sent in response to an inquiry.
[Step S51] The guardian's terminal 40 accepts an operation from the guardian and requests the neighbor notification device 10 for the neighbor information of the child.

  [Step S52] The CPU 11 of the neighbor notification device 10 receives a request for neighbor information from the guardian's terminal 40 via the communication interface 16. The CPU 11 of the neighbor notification device 10 receives the tag number or group management number of the child who notifies the neighbor information from the guardian's terminal 40.

  [Step S53] The CPU 11 of the neighbor notification device 10 performs notification message processing for generating a notification message to notify the guardian. The notification message process will be described in detail below using a flowchart.

  [Step S54] The CPU 11 of the neighbor notification device 10 transmits the notification message generated by the notification message processing to the guardian's terminal 40 via the communication interface 16.

[Step S55] The guardian's terminal 40 receives the notification message transmitted from the neighbor notification device 10 and displays it on the display device.
In this manner, the guardian can arbitrarily recognize what kind of person is present around the child by inquiring the neighbor notification device 10 about the child's neighbor information.

  Although not shown, the child terminals 30 to 34 periodically sense surrounding wireless ID tags and transmit the tag numbers of the wireless ID tags to the neighbor notification device 10. The neighbor notification device 10 stores the tag number received from the child terminals 30 to 34 in the log DB 74 for each child.

Next, the notification message processing in step S53 of FIG. 20 will be described in detail.
21 and 22 are flowcharts of the notification message process. The flowchart of the notification message process is divided into two parts shown in FIGS.

  [Step S61] The CPU 11 of the neighbor notification device 10 determines whether or not a group management number has been designated from the guardian's terminal 40. If the group management number is designated, the process proceeds to step S62. If the group management number is not designated, that is, if the tag number of the child is transmitted from the guardian's terminal 40, the process proceeds to step S63.

  [Step S62] The CPU 11 of the neighbor notification device 10 refers to the grouping management information DB 73 according to the designated group management number, and sequentially extracts the tag numbers of the children managed in groups one by one.

  [Step S63] The CPU 11 of the neighbor notification device 10 acquires from the personal information DB 72 the child information corresponding to the tag number extracted in Step S62 or the child tag number received from the guardian terminal 40. The CPU 11 of the neighbor notification device 10 develops certain log information in the corresponding child log DB 74 in the work area based on the acquired child information.

  [Step S64] The CPU 11 of the neighbor notification device 10 determines whether or not the child is acting alone based on the log information developed in the work area. When determining that the child is acting alone, the CPU 11 of the neighbor notification device 10 generates a notification message to that effect. Note that the processing in step S64 is the same as the flowchart of the one-person determination processing described in FIG.

  [Step S65] The CPU 11 of the neighbor notification device 10 determines whether or not it is determined in step S64 that the child is acting alone. If it is determined in step S64 that the child is acting alone, the process proceeds to step S77. If it is determined that the child is not acting alone, the process proceeds to step S66.

  That is, when the child is acting alone, the process proceeds to a notification message transmission process in order to transmit a notification message to that effect to the guardian. On the other hand, when the child is not acting alone (when the state of alone has not passed for a predetermined time (for example, 3T)), the process proceeds to whether or not there is a person around and further acts away from the group. Proceed to the process of whether or not.

  [Step S66] The CPU 11 of the neighbor notification device 10 determines whether or not there is a person around the child depending on whether or not a tag number exists in the current log information (latest log information). . If there is no person around the child, the CPU 11 of the neighbor notification device 10 generates a notification message indicating that there is no person around the child. The process of step S66 will be described in detail below using a flowchart.

  [Step S67] The CPU 11 of the neighbor notification device 10 determines whether or not it is determined in step S66 that there is a person around the child. If it is determined in step S66 that there are no people around the child, the process proceeds to step S77 in order to transmit a notification message indicating that there are no people around the child. If it is determined that there are people around the child, the process proceeds to step S68.

  [Step S68] The CPU 11 of the neighbor notification device 10 determines whether or not a group of children is set. If the child is set as a group, the process proceeds to step S72. If no group is set for the child, the process proceeds to step S69.

  [Step S69] The CPU 11 of the neighbor notification device 10 determines whether there are people around the child but not acting together. In other words, as described above, even if there is a person around the child, if there is no person around the child for a predetermined time (for example, 2T), there are people around the child but they are acting together. Judge that there is no. The process of step S69 will be described in detail below using a flowchart.

  [Step S70] If the CPU 11 of the neighbor notification device 10 determines in step S69 that there is a person around the child but is not acting together, the process proceeds to step S77. When it determines with acting together, it progresses to step S71.

  [Step S71] The CPU 11 of the neighbor notification device 10 acquires information on a person who is acting together, and generates a notification message indicating that the person is acting together. In addition, the process of step S71 is demonstrated in detail below using a flowchart.

  [Step S72] The CPU 11 of the neighbor notification device 10 determines whether or not the child is moving away from the group based on the log information developed in the work area and the grouping management information DB 73. When the CPU 11 of the neighbor notification device 10 determines that the child is acting away from the group, the CPU 11 generates a notification message to that effect. Note that the processing in step S72 is the same as the flowchart of the group determination processing described in FIG.

  [Step S73] The CPU 11 of the neighbor notification device 10 determines whether or not it is determined in step S72 that the child is acting away from the group. If it is determined in step S72 that the child is acting away from the group, the process proceeds to step S77. If it is determined that the child is not acting away from the group, the process proceeds to step S74.

  [Step S74] The CPU 11 of the neighbor notification device 10 determines whether or not there are people in the group around the child and acting together. That is, it is determined whether or not there are people in the group around the child for a predetermined time (for example, 2T). If staying together for a predetermined time, it is determined that the child and the person in the group are acting together. If it is not together for a predetermined time, it is determined that a person in the group is in the vicinity but is not acting together. The process of step S74 will be described in detail below using a flowchart.

  [Step S75] If the CPU 11 of the neighbor notification device 10 determines in step S74 that there is a group of people around the child but is not acting together, the process proceeds to step S77. When it determines with acting together, it progresses to step S76.

  [Step S76] The CPU 11 of the neighbor notification device 10 acquires information on people in the group acting together, and generates a notification message indicating that the child is acting together with the people in the group. The process of step S76 will be described in detail below using a flowchart.

[Step S77] The CPU 11 of the neighbor notification device 10 transmits a notification message to the guardian's terminal 40.
[Step S78] The CPU 11 of the neighbor notification device 10 determines whether or not a group management number has been designated from the guardian's terminal 40. If the group management number is designated, the process proceeds to step S79. If no group management number is specified, the process is terminated.

  [Step S79] The CPU 11 of the neighbor notification device 10 determines whether or not the processing in the previous step has been completed for all group members of the group management number designated from the guardian terminal 40. If all group members have been processed, the process ends. If all the group members have not been processed, the process proceeds to step S62, and the next group member is processed.

In this way, the neighbor notification device 10 grasps the situation around the child in response to a request from the guardian. Then, the notification message is transmitted to the guardian's terminal 40.
Next, the processes of steps S66, S69, S71, S74, and S76 in FIG. 22 will be described in detail in order. First, the presence / absence determination process of the surrounding people in step S66 of FIG. 22 will be described.

FIG. 23 is a flowchart of the presence / absence determination process of surrounding people.
[Step S81] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the current information of the log information read to the work area.

  [Step S82] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been detected from the current log information in the work area. If the tag number can be detected, it is determined that there is a person around the child and the process is terminated. If the tag number could not be extracted, the process proceeds to step S83.

  [Step S83] The CPU 11 of the neighbor notification device 10 determines whether or not the tag number detection has been completed in all the log information at the current time. If the detection of the tag number is completed in all the log information at the current time, the process proceeds to step S84. If the detection of the tag number is not completed in all the log information at the current time, the process proceeds to step S81, and the tag number in the next log information is detected.

[Step S84] The CPU 11 of the neighbor notification device 10 generates a notification message that there is no one around the child.
As described above, the neighbor notification device 10 determines whether or not there is a person around the child depending on whether or not the tag number is present in the current log information, and there is no person around the child. If not, a notification message that no one is around the child is generated.

Next, a determination process in which there are people around step S69 in FIG. 22 but not acting together will be described.
FIG. 24 is a flowchart of a determination process in which there are people around but are not acting together.

[Step S91] The CPU 11 of the neighbor notification device 10 sequentially searches the tag number of the wireless ID tag from the log information read to the work area.
[Step S92] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been extracted from the log information of the work area. If the tag number can be detected, the process proceeds to step S93. If the tag number cannot be detected, the process proceeds to step S96.

  [Step S93] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number exists in the previous log information (log information in the previous cycle). If the tag number exists, the process proceeds to step S94. If the tag number does not exist, the process proceeds to step S95. That is, it is determined whether the people around the child are together for a predetermined time (for example, 2T). If the children are not together for a predetermined time (if the tag number is not present), the child determines that he / she is with another person but is not acting together, and proceeds to step S95. On the other hand, if the children are together for a predetermined time (if the tag number exists), the child determines that he / she is acting with other children, and proceeds to step S94 to end the processing of the flowchart in the figure. .

  [Step S94] The CPU 11 of the neighbor notification device 10 determines whether or not the presence or absence of the tag number has been checked in the past log information for a predetermined time (predetermined time). If the presence or absence of the tag number is checked in the log information for a certain time, the process is terminated. If the check of the presence / absence of the tag number is not completed in the log information for a fixed time, the process proceeds to step S93.

  [Step S95] The CPU 11 of the neighbor notification device 10 recognizes that the person with the extracted tag number is around the child who should be notified of the neighbor information, but is not acting together. In step S91, the next tag number is extracted.

  [Step S96] In step S95, the CPU 11 of the neighbor notification device 10 converts the tag number recognized as a person around the child into a name with reference to the personal information DB 72.

  [Step S97] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that there are people around the child but they are not acting together. The generated message includes the names of people around the child and is transmitted to the guardian's terminal 40 in step S77 in FIG.

Thus, the neighbor notification device 10 determines that there are people around the child but they are not acting together.
Next, the information acquisition process of the person who is together in step S71 of FIG. 22 will be described.

FIG. 25 is a flowchart of information acquisition processing for people who are together.
[Step S101] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the log information read to the work area.

  [Step S102] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been detected from the log information of the work area. If the tag number can be detected, the process proceeds to step S103. If the tag number could not be extracted, the process proceeds to step S106.

  [Step S103] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number exists in the previous log information (log information in the previous cycle). If the tag number exists, the process proceeds to step S104. If the tag number does not exist, the process proceeds to step S101. That is, it is determined whether the people around the child are together for a predetermined time (for example, 2T).

  [Step S104] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number is checked in past log information for a predetermined time (a predetermined time). If the presence or absence of the tag number is checked in the log information for a certain time, the process proceeds to step S105. When the log information for a certain time has not been checked for the presence of the tag number, the process proceeds to step S103.

  [Step S105] The CPU 11 of the neighbor notification device 10 recognizes the person with the extracted tag number as a person who is with the child. In step S101, the next tag number is extracted.

  [Step S106] The CPU 11 of the neighbor notification device 10 determines whether the tag number of the person who is with the child has been detected. If the tag number of the person with the child is detected, the process proceeds to step S107. If the tag number of the person with the child cannot be detected, the process is terminated.

  [Step S107] The CPU 11 of the neighbor notification device 10 converts the tag number recognized as a person with the child in step S105 into a name with reference to the personal information DB 72.

  [Step S108] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that the child is with another person. The generated message includes the name converted in step S107, and is transmitted to the guardian's terminal 40 in step S77 of FIG.

As described above, the neighbor notification device 10 acquires information about a person who is with a child and generates a notification message.
Next, the group action determination process in step S74 of FIG. 22 will be described. In the group behavior determination process, a determination process is performed in which a person in the group is around the child but is not acting together.

FIG. 26 is a flowchart of the group action determination process.
[Step S111] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the log information read to the work area.

  [Step S112] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been detected from the log information of the work area. If the tag number can be detected, the process proceeds to step S113. If the tag number cannot be detected, the process proceeds to step S117.

  [Step S113] The CPU 11 of the neighbor notification device 10 determines whether or not the detected tag number belongs to a group member. If the detected tag number belongs to a group member, the process proceeds to step S114. If the detected tag number is not that of a group member, the process proceeds to step S111, and the next tag number is detected.

  [Step S114] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number exists in the previous log information (log information in the previous cycle). If the tag number exists, the process proceeds to step S115. If the tag number does not exist, the process proceeds to step S116. That is, it is determined whether the group members around the children are together for a predetermined time (for example, 2T). If it is not together for a predetermined time (if no tag number exists), it is determined that there are group members around the child but not acting together, and the process proceeds to step S116. On the other hand, if they are together for a predetermined time (if a tag number exists), it is determined that the child is acting with the group member, and the process proceeds to step S115.

  [Step S115] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number is checked in past log information for a predetermined time (a predetermined time). If the presence or absence of the tag number is checked in the log information for a certain time, the process is terminated. If the check of the presence / absence of the tag number is not completed in the log information for a certain time, the process proceeds to step S114.

  [Step S116] The CPU 11 of the neighbor notification device 10 recognizes that the group member with the detected tag number is around a child who should be notified of neighbor information, but is not acting together. In step S111, the next tag number is detected.

  [Step S117] The CPU 11 of the neighbor notification device 10 converts the tag number recognized as being around the child but not acting in Step S116 into a full name with reference to the personal information DB 72. .

  [Step S118] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that there are group members around the child but not acting together. The generated message includes the name converted in step S117, and is transmitted to the guardian's terminal 40 in step S77 of FIG.

As described above, the neighbor notification device 10 determines that there are group members around the child but not acting together.
Next, the group member information acquisition process in step S76 of FIG. 22 will be described.

FIG. 27 is a flowchart of information acquisition processing for group members who are together.
[Step S121] The CPU 11 of the neighbor notification device 10 sequentially detects the tag number of the wireless ID tag from the log information read to the work area.

  [Step S122] The CPU 11 of the neighbor notification device 10 determines whether the tag number has been extracted from the log information of the work area. If the tag number can be detected, the process proceeds to step S123. If the tag number cannot be detected, the process proceeds to step S127.

  [Step S123] The CPU 11 of the neighbor notification device 10 determines whether or not the detected tag number belongs to a group member. If the detected tag number belongs to a group member, the process proceeds to step S124. If the detected tag number is not that of a group member, the process proceeds to step S121, and the next tag number is detected.

  [Step S124] The CPU 11 of the neighbor notification device 10 determines whether or not a tag number exists in the previous log information (log information in the previous cycle). If the tag number exists, the process proceeds to step S125. If the tag number does not exist, the process proceeds to step S121. That is, it is determined whether the group members around the children are together for a predetermined time (for example, 2T). If the children are together for a predetermined time (if the tag number is present), the child is determined to be acting with the group member, and the process proceeds to step S125. On the other hand, if it is not together for a predetermined time (if no tag number exists), it is determined that the child is not acting with the group member, and the process proceeds to step S121.

  [Step S125] The CPU 11 of the neighbor notification device 10 determines whether or not the presence or absence of the tag number has been checked in the past log information for a predetermined time (a predetermined time). If the presence or absence of the tag number is checked in the log information for a certain time, the process proceeds to step S126. If the check of the presence / absence of the tag number is not completed in the log information for a fixed time, the process proceeds to step S124.

  [Step S126] The CPU 11 of the neighbor notification device 10 recognizes that the group member with the detected tag number is acting with the child whose neighbor information should be notified. Then, the process proceeds to step S121, and the next tag number is detected.

  [Step S127] The CPU 11 of the neighbor notification device 10 determines whether or not the tag number of the group member acting with the child has been detected. If the tag number of the group member acting with the child is detected, the process proceeds to step S128. If the tag number of the person acting with the child cannot be detected, the process is terminated.

  [Step S128] In step S126, the CPU 11 of the neighbor notification device 10 converts the tag number recognized as a group member with the child into a full name with reference to the personal information DB 72.

  [Step S129] The CPU 11 of the neighbor notification device 10 generates a notification message indicating that the child is acting with the group member. The generated message includes the name converted in step S128, and is transmitted to the guardian's terminal 40 in step S77 of FIG.

As described above, the neighbor notification device 10 acquires information on the group members acting together with the child and generates a notification message.
The above is the description of the operation when the notification message is notified in response to the inquiry from the guardian.

  Next, the operation of stopping and resuming the monitoring of children by a special tag number will be described. For example, when the guardian is near his child, it is not necessary to notify the guardian of the child's neighbor information. Therefore, the tag number of the wireless ID tag held by the parent (hereinafter referred to as a special tag number) is registered in the child terminal of the child, and when the child terminal receives the special tag number, the notification of the neighbor information is stopped. The neighbor notification device 10 is notified as follows. Hereinafter, this operation will be described using a sequence diagram.

FIG. 28 is a sequence diagram of the neighbor notification device, the child terminal, and the guardian terminal that stops the notification of the neighbor information.
[Step S131] The guardian's terminal 40 receives an operation from the guardian and transmits the tag number (special tag number) of the wireless ID tag that the guardian's terminal 40 has to the neighbor notification device 10. In the following, the tag number of the guardian's terminal 40 is “000E” (“Fuji Yoko” tag number).

  [Step S132] The CPU 11 of the neighbor notification device 10 is transmitted from the guardian's terminal 40 to the special ID tag number column of “Fuji Taro” Fuji Hanako ”(the child of“ Fuji Yoko ”) in the personal information DB 72. Store special tag number.

  [Step S133] The CPU 11 of the neighbor notification device 10 transmits the special tag number “000E” stored in the personal information DB 72 to the child terminal owned by “Taro Fuji” “Hanako Fuji” via the communication interface 16. To do.

  [Step S134] The CPU 30a of the child terminal stores the received special tag number in the storage unit 30b. After that, when receiving the special tag number stored in the storage unit 30b, the CPU 30a of the child terminal stops transmission of the sensed tag number to the neighbor notification device 10 and stops monitoring (notification of neighbor information). Stop).

[Step S135] The CPU 30a of the child terminal notifies the neighbor notification device 10 that the special tag number has been stored via the communication unit 30g.
[Step S136] The CPU 11 of the neighbor notification device 10 notifies the parent terminal 40 that the child terminal has stored the special tag number via the communication interface 16.

  [Steps S137, S138] The CPU 30a of the child terminal senses a surrounding wireless ID tag by the wireless ID tag sensor unit 30c, and transmits the tag number to the neighbor notification device 10 via the communication unit 30g.

  Note that the wireless ID tags 101a to 101c shown in the figure are wireless ID tags of the guardian's terminal 40 possessed by “Yoko Fuji”. The sensor ranges 102a to 102c indicate ranges that can be sensed by a child terminal of 'Fuji Taro' and 'Fuji Hanako'. If the wireless ID tags 101a to 101c move to the right side of the sensor ranges 102a to 102c in the figure, the wireless ID tag sensor unit 30c of the child terminal of “Fuji Taro” Fuji Hanako ”will become the wireless ID tag of“ Fuji Yoko ”. It can be sensed.

Therefore, in steps S <b> 137 and S <b> 138, the child terminal of “Fuji Taro” “Fuji Hanako” transmits the wireless ID tag sensing result to the neighbor notification device 10.
[Step S139] As shown in the figure, the wireless ID tag 101b of 'Fuji Yoko' is within the range that can be sensed by the child terminal of 'Fuji Taro''FujiHanako'. Therefore, the child terminal of “Fujitaro” “Fuji Hanako” notifies the neighbor notification device 10 that monitoring is stopped.

[Step S140] Upon receiving the monitoring stop notification from the child terminal, the CPU 11 of the neighbor notification device 10 notifies the guardian terminal 40 accordingly.
[Step S141] As shown in the figure, the wireless ID tag 101b of “Fuji Yoko” is in a range where the child terminal of “Fuji Taro” and “Fuji Hanako” cannot sense. Therefore, the child terminal of “Fuji Taro” “Fuji Hanako” resumes sensing of surrounding wireless ID tags and notifies the neighbor notification device 10 of resumption of monitoring (resumption of notification of neighbor information). .

[Step S142] When the CPU 11 of the neighbor notification device 10 receives monitoring resumption from the child terminal, the CPU 11 notifies the guardian terminal 40 accordingly.
[Steps S143, S144] The CPU 30a of the child terminal senses a surrounding wireless ID tag by the wireless ID tag sensor unit 30c, and transmits the tag number to the neighbor notification device 10 via the communication unit 30g.

  In this way, when the guardian is near his / her child, it is not necessary to notify the guardian of the child's neighbor information, so when the child terminal receives the special tag number, The person notification device 10 is notified. As a result, when the guardian is near his / her child, the neighbor information of the child is not notified to the guardian.

  Also, the neighbor notification device 10 determines whether or not there is a guardian of the child around the child based on the tag number received from the child terminals 30 to 34, and notifies the guardian of the information around the child. Can also be stopped.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the computer should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include a hard disk device (HDD) flexible disk (FD) and a magnetic tape. Examples of the optical disc include a DVD (Digital Versatile Disc), a DVD-RAM (Random Access Memory), a CD-ROM (Compact Disc Read Only Memory), and a CD-R (Recordable) / RW (ReWritable). Magneto-optical recording media include MO (Magneto-Optical disc).

  When distributing the program, for example, a portable recording medium such as a DVD or a CD-ROM in which the program is recorded is sold. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

(Supplementary note 1) In the neighbor notification program for notifying the monitor of the information of the monitored neighbor,
Computer
Tag information receiving means for receiving tag information of the wireless ID tag from a monitored terminal that detects the wireless ID tag possessed by the neighbor and possessed by the neighbor,
Neighbor information for acquiring the neighbor information corresponding to the tag information received by the tag information receiving means from the neighbor information storage means in which the neighbor information of the neighbor is stored corresponding to the tag information. Acquisition means,
Message transmission means for transmitting a message including the neighbor information to a supervisor terminal possessed by the supervisor;
Neighbor notification program, characterized by functioning as

(Supplementary note 2)
Tag information storage means for storing the tag information;
When the tag information is stored in the tag information storage means for a predetermined time, information adding means for including information that the monitored person is with the neighbor having the tag information in the message;
The neighbor notification program according to supplementary note 1, wherein the program is made to function as:

(Supplementary note 3)
Tag information storage means for storing the tag information;
If the tag information is stored in the tag information storage means but not stored for a predetermined time, the message includes a neighbor having the tag information around the monitored person, but acts together. Information adding means to include information indicating that
The neighbor notification program according to supplementary note 1, wherein the program is made to function as:

(Supplementary note 4)
Tag information storage means for storing the tag information;
If the tag information is not stored in the tag information storage means for a certain period of time, information adding means for including information that the person being monitored is alone in the message;
The neighbor notification program according to supplementary note 1, wherein the program is made to function as:

(Supplementary Note 5) The monitored person is group-managed with the other monitored person who possesses the wireless ID tag,
The neighbor notification program according to claim 1, wherein the message includes information indicating whether or not the monitored person is acting together with the monitored person in a group.

  (Supplementary note 6) The neighbor notification program according to supplementary note 1, wherein the message transmission means transmits the message when the status of the monitored person is a status to transmit the neighbor information.

(Additional remark 7) The said message transmission means transmits the said message according to the inquiry from the said supervisor terminal, The neighbor notification program of Additional remark 1 characterized by the above-mentioned.
(Supplementary note 8) In the neighbor notification method of the neighbor notification device for notifying the monitor of the information of the monitored neighbor,
The tag information receiving means receives tag information of the wireless ID tag from the monitored terminal that detects the wireless ID tag possessed by the monitored person and possessed by the neighbor,
The neighbor corresponding to the tag information received by the tag information receiving means from the neighbor information storing means storing the neighbor information of the neighbor corresponding to the tag information by the neighbor information acquiring means. Get information,
A message transmission means for transmitting a message including the neighbor information to a supervisor terminal possessed by the supervisor;
A neighbor notification method characterized by the above.

(Supplementary Note 9) In the monitored terminal owned by the monitored person,
Tag information receiving means for receiving tag information of a wireless ID tag possessed by a neighbor;
Tag information transmitting means for transmitting the tag information to a neighbor notification device that transmits the neighbor information of the neighbor to a monitor terminal of a monitor;
Supervisor tag information storage means for storing supervisor tag information of the supervisor who monitors the monitored person;
When the supervisor tag information is received, neighbor information stop means for requesting the neighbor notification device to stop the notification of the neighbor information while stopping transmission of the tag information;
A monitored terminal, characterized by comprising:

It is a figure explaining the outline | summary of a neighbor notification program. It is a figure which shows the system structural example of a neighbor notification apparatus. It is the figure which showed the hardware structural example of the neighbor notification apparatus. It is the figure which showed the hardware structural example of the terminal for children. It is the figure which showed the data structural example of guardian information DB. It is the figure which showed the data structural example of personal information DB. It is the figure which showed the data structural example of grouping management information DB. It is the figure which showed the data structural example of log DB. It is the figure which showed an example of the neighbor information displayed on the terminal for guardians when the child is acting alone. It is the figure which showed an example of the neighbor information displayed on the terminal for guardians when a child is acting with other children. It is the figure which showed an example of the neighbor information displayed on the terminal for guardians when there are people around the child but not acting together. It is the figure which showed an example of the neighbor information displayed on the terminal for guardians when there is no person around the child but is not acting alone. It is the figure which showed an example of the neighbor information displayed on the terminal for parents when the child managed in a group is acting away from a group. It is the figure which showed log DB for demonstrating the transmission timing of a notification message, and its content. It is a sequence diagram of a neighbor notification device, a child terminal, and a guardian terminal when performing automatic notification message notification. It is a flowchart of a notification message process. It is a flowchart of a single person determination process. It is a flowchart of a group determination process. It is a flowchart of a notification message transmission process. It is a sequence diagram of a close relative notification device and a guardian terminal when a notification message is sent in response to an inquiry. It is a flowchart of a notification message process. It is a flowchart of a notification message process. It is a flowchart of the presence determination process of the surrounding people. It is a flowchart of the determination process which has people around but is not acting together. It is a flowchart of the information acquisition process of the person who is together. It is a flowchart of a group action determination process. It is a flowchart of the information acquisition process of the group member who is together. It is a sequence diagram of a neighbor notification device, a child terminal, and a guardian terminal that stops notification of neighbor information.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Computer 1a Tag information reception means 1b Neighbor information storage means 1c Neighbor information acquisition means 1d Message transmission means 2 Monitored terminal 3 Monitor terminal 4a, 4b Wireless ID tag

Claims (4)

In the neighbor notification program for notifying the monitor of information on the monitored neighbors,
Computer
Tag information receiving means for receiving tag information of the wireless ID tag from the monitored person terminal that detects the wireless ID tag possessed by the neighbor and possessed by the neighbor, and storing the tag information in the tag information storage means,
Neighbor information for acquiring the neighbor information corresponding to the tag information received by the tag information receiving means from the neighbor information storage means in which the neighbor information of the neighbor is stored corresponding to the tag information. Acquisition means,
Message transmission means for transmitting a message including the neighbor information to a supervisor terminal possessed by the supervisor;
When the tag information is stored in the tag information storage means for a predetermined time, information adding means for including information that the monitored person is with the neighbor having the tag information in the message;
Neighbor notification program, characterized by functioning as   The information adding means stores the tag information in the tag information storage means, but if the information is not stored for a predetermined time, the message includes a neighbor having the tag information around the monitored person. Include information that they are not acting together,
  The neighbor notification program according to claim 1.   The information adding means includes information indicating that the person being monitored is alone in the message when the tag information is not stored in the tag information storage means for a certain period of time;
  The neighbor notification program according to claim 1.   In the neighbor notification method of the neighbor notification device for notifying the monitor of information on the neighbor of the monitored person,
  Tag information receiving means receives tag information of the wireless ID tag from a monitored person terminal that detects the wireless ID tag possessed by the monitored person and possessed by the neighbor, and stores the tag information in the tag information storage means And
  The neighbor corresponding to the tag information received by the tag information receiving means from the neighbor information storing means storing the neighbor information of the neighbor corresponding to the tag information by the neighbor information acquiring means. Get information,
  When the same tag information is stored in the tag information storage means for a predetermined time by the information adding means, the monitored person is together with the neighbor having the tag information in the message including the neighbor information. Including information to the effect
  Sending the message to a supervisor terminal possessed by the supervisor by message sending means;
  A neighbor notification method characterized by the above.

Images