JP2007183890A - Living condition monitoring system, apparatus, method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To determine whether abnormality occurs or not by using power consumption for each individual, and to notify the occurrence of abnormality. <P>SOLUTION: A living condition monitoring system in which a client terminal installed on a user's home side is communicated to a server through a communication network in a communicable manner, is equipped with: a means for, in the server, receiving data obtained by patterning a user's daily power consumption state and a daily power consumption state received from a client terminal installed in the vicinity of a user's home and storing the received data in a database; a means for comparing the patterned data with the power consumption data received from the client terminal and stored and extracting a difference; a means for determining the detection of abnormality occurrence when the extracted difference is compared with a predetermined threshold data and the difference exceeds the threshold; and a means for notifying the detection of abnormality occurrence to a previously determined destination. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a living situation monitoring system, apparatus, method, and program for monitoring the daily living situation of a user such as an elderly person living alone and notifying the outside when an abnormality is found, and in particular, the user's power usage To detect abnormalities by comparing the amount of daily load data with user patterns, and by comparing daily load data with inrush current patterns that appear when various devices are powered on The present invention relates to a living situation monitoring system, apparatus, method, and program that make it possible to determine the above.

  Conventionally, as shown in FIG. 1, a power information company F11 has a user information database F14 including a user's power usage amount as a technique for determining remote monitoring of an elderly person living alone, etc. based on the power usage status. When the user F13 consumes power, the power is supplied from the power company F11 through the switchboard F12. The amount of electric power used by each user is obtained by taking the value measured by the person in charge at the user's home into the user database. Therefore, real-time information is not collected for each user, but only the past information can be known as the life situation of the user, and it is not possible to cope with the occurrence of an abnormal situation requiring an emergency. Moreover, although it is possible to determine that it is abnormal when the daily load curve of the electric power consumption shows a constant value every day, it is not effective because the determination is too late.

In addition, as a conventional power consumption monitoring, in Patent Document 1, a device for detecting the amount of current used by a device and its application are applied to detect abnormality of the device and predict the life, thereby contributing to normal use of the device. Proposes a technology that provides a system, a system that prevents the breaker from being interrupted due to exceeding the power supply allowance when multiple devices are used, and a system that detects and deals with abnormal usage of the devices.
JP-A-9-145743

  However, it is unrealistic to detect the abnormality of the power usage in real time by collecting the power usage manually performed by the person in charge every day, which is difficult in terms of human resources.

  In addition, in the technique proposed in Patent Document 1, an abnormality of the device can be detected by detecting the amount of current used by the device, but the detected content is notified to the outside via a communication network. Or comparing the detected content with the inrush current of the device to identify the power-on of the device.

  The present invention has been made in view of the above-described circumstances, and measures the amount of power used at a user's home, notifies the external server of the content, and changes in the amount of power used received by the external server. If it is determined that an abnormality has occurred and it can be determined that an abnormality has occurred, notification to a predetermined destination is made.In addition, the device can be turned on using the inrush current pattern unique to the device depending on the amount of power received. It is an object of the present invention to provide a living situation monitoring system, apparatus, method, and program that can specify the time of day and the like.

  In order to achieve the above object, a living situation monitoring system according to the present invention is a living situation monitoring system in which a living situation monitoring server for monitoring an individual's living situation and a client terminal are communicably connected via a communication network. Daily load data storage that receives the daily load pattern data corresponding to the user and the daily power usage status received from the client terminal and stores them in the daily load database Means, daily load pattern data corresponding to the user, daily load pattern comparing means for comparing the daily load data received and stored from the client terminal and extracting the difference, the extracted difference, and a predetermined usage An abnormality detection means for determining that an abnormality has been detected when the threshold is exceeded by comparing with the daily response difference threshold data corresponding to the person, When the abnormality is detected, characterized by comprising an abnormality occurrence notification means for notifying a predetermined destination, the.

  In the present invention, the life status monitoring server includes user-responsive daily load pattern data in which the usage status of the user's power is patterned, and user-responsive daily load differential threshold data indicating that an abnormality has occurred in the user's life. And the difference between the daily load data of the power usage received from the client terminal and the user corresponding daily load pattern data is created, and the difference exceeds the user corresponding daily load difference threshold data. In this case, it can be determined as abnormal and can be notified to the outside, so that related parties such as the user's family can support living alone with peace of mind.

  Preferably, the daily load pattern data is created based on past results, or is created in advance according to the daily life for the user.

  In the present invention, the daily load pattern data indicating the daily routine life necessary for determining the abnormality is created in advance according to the past performance of the user or the life of the user, thereby detecting the abnormality. It can correspond to.

  More preferably, a daily load pattern correction unit that corrects the user-supported daily load pattern data by taking statistics of the daily load data of a predetermined period in the past and creates new user-supported daily load pattern data. It is good to comprise so that.

  In the present invention, the daily load pattern data corresponding to the user can be corrected based on the user's life situation that changes with time, so the life situation is always determined using pattern data that is close to the current life. Can be high accuracy.

  It is also preferable that the abnormality occurrence notification means is configured to notify the occurrence of an abnormality according to the selection contents of whether or not to notify the occurrence of an abnormality in correspondence with the destination registered for each user.

  According to the present invention, when an abnormality is detected, it is possible to notify a person concerned of the user, so that a person concerned such as the user's family can be relieved.

  Furthermore, it is preferable that the notification of the occurrence of abnormality is configured to be performed using at least one of telephone, FAX, and e-mail.

  In the present invention, it is possible to immediately notify the user that an abnormality has occurred using a telephone, FAX, e-mail, etc., so that it is possible to quickly cope with the abnormality.

  Preferably, external information input means for inputting information from the outside using a specific protocol via a communication network, and monitoring start time and end time input using the external information input means are acquired and stored. The daily load pattern comparison means, the abnormality occurrence detection means, and the abnormality occurrence notification means are configured to operate only within the period.

  In the present invention, by allowing information to be input from the outside using a specific protocol such as HTTP via a communication network, the contents input from the outside can be taken into the database, and the monitoring start time / end Since the time can be input to the system from the outside, the user's parties can enjoy the convenience of being able to monitor the living state of the user wherever they are.

  More preferably, the schedule database for storing the daily schedule of the user and the daily schedule of the user are registered or edited in the schedule database using a specific communication protocol from the outside via a communication network. And a schedule registration editing means.

  In the present invention, since the user's schedule information can be input or edited from the outside via the communication network, the convenience of being able to register the schedule from a distance on behalf of the user is utilized. It can be given to the person concerned and the user.

  In addition, it is preferable to include a scheduled time warning unit that issues a warning when the time registered in the daily schedule of the user is reached or before the registered time is reached.

  In the present invention, when the time of the registered schedule is approaching, or it is possible to give a warning such as an alarm to the user at that time, the user should perform work such as taking medicines according to the schedule. It will be possible to assist in doing it correctly.

  Furthermore, it is preferable that the schedule database for storing the daily schedule of the user includes an area for storing preference information indicating the degree of preference of the user for each item to be registered.

  According to the present invention, it is possible to register a schedule including the degree of preference. Therefore, it is possible to perform an operation according to the user's preference such as changing a warning method according to the registered preference. In addition, signs of abnormalities in the elderly can be detected early by detecting changes in preferences.

  More preferably, an inrush current pattern database that stores an inrush current pattern that is seen when a device that uses power is turned on for each device, and a user's daily load data that is stored in the daily load database. And an inrush current determination means for specifying the power-on time of the corresponding device by comparing the contents of the above and the inrush current pattern.

  According to the present invention, by checking the inrush current pattern, it is possible to know the power-on status of the electrical equipment performed by the user. It is possible for external parties of users to determine whether or not they are doing.

  In order to achieve the above object, a living situation monitoring apparatus according to the present invention is a living situation monitoring apparatus that monitors a living situation configured to be communicable via a communication network, and uses daily power of a user. Compare daily load data with user-patterned status, daily load data storage means for storing measured daily power usage in daily load database, daily load data with user response, and daily load data And daily load pattern comparison means for extracting the difference,

  When the detected difference is detected, an abnormality detection means for determining that an abnormality has been detected when the extracted difference is compared with predetermined user-corresponding daily load difference threshold data and the threshold is exceeded; And an abnormality occurrence notification means for notifying a predetermined destination.

  Further, daily load pattern correction means for correcting the user corresponding daily load pattern data by taking statistics of the daily load data of a predetermined period in the past and creating new user corresponding daily load pattern data, It is also preferable that it is comprised so that it may contain.

  More preferably, an inrush current pattern database that stores an inrush current pattern that is seen when a device that uses power is turned on for each device, and a user's daily load data that is stored in the daily load database. And the inrush current pattern, the inrush current determining means for specifying the power-on time of the corresponding device is provided.

  In order to achieve the above object, a living situation monitoring method according to the present invention includes a living situation monitoring server that monitors an individual's living situation via a communication network, and an individual living situation monitoring in which a client terminal is communicably connected. Daily life data storage step of receiving daily power usage status received from the client terminal and storing it in the daily load database, and pattern of the daily power usage status of the user A daily load pattern comparison step of extracting the difference by comparing the daily load data corresponding to the user and the daily load data received and stored from the client terminal, the extracted difference, and a predetermined user response date An abnormality detection step for comparing the load difference threshold data and determining that an abnormality has occurred when the threshold is exceeded, and detecting the occurrence of the abnormality When it, characterized in that it comprises an abnormality occurrence notification step of notifying the predetermined destination, a.

  Preferably, the user's date stored in the daily load database is referenced with reference to an inrush current pattern database that stores an inrush current pattern that is seen when a device that uses power is turned on. An inrush current determination step for identifying the power-on time of the corresponding device by comparing the content of the load data with the inrush current pattern.

  In order to achieve the above object, a living situation monitoring program according to the present invention is a program that operates on a computer that monitors an individual's living situation, and receives a daily usage situation of power received from a client terminal. The daily load data storage process to be stored in the daily load database, the daily load data corresponding to the user that patterns the daily power usage of the user, and the daily load data received and stored from the client terminal are compared. A daily load pattern comparison process for extracting a difference, and an abnormality occurrence detection process for comparing the extracted difference with predetermined user-specific daily load difference threshold data and determining an abnormality occurrence when the threshold is exceeded And an abnormality occurrence notification process for notifying a predetermined destination when the occurrence of the abnormality is detected on a computer. .

  According to the present invention, it is possible to check a user's living situation from the outside via a communication network, to perform monitoring by designating a time zone to be monitored, daily load pattern data for each user and daily day. Comparing load data can detect abnormalities, register user schedules, identify electrical appliances that have been turned on, etc. You can watch the user's life with peace of mind.

  Embodiments of the present invention will be described below. FIG. 2 shows a schematic configuration diagram of the present invention. In addition to the conventional configuration of FIG. 1, a communication network 4 and a user participant F21 are added. In FIG. 1, instead of the user information DB F14, a DB 22 such as a user information DB is provided. It is provided in the electric power company F11. The electric power company F <b> 11, the user F <b> 13, and the user related person F <b> 21 are connected via the communication network 4 so that they can communicate with each other. In addition, F22, which is a DB such as a user information DB, stores power usage by user, daily load curve data, inrush current transition, and the like.

  The amount of power used by the user F13 is fed from the power company F11 to the user F13 through the switchboard F12, and is measured at the user's home in real time, for example, and installed in the power company F11 via the communication network 4. The server stores the received power usage amount for each user in F22 which is a DB such as a user information DB. Further, for example, the user F21 who is a user such as a child of the user can monitor the power usage amount of the user F13 via the communication network 4 and can write the schedule of the user F13. It is configured.

  FIG. 3 is a diagram showing a connection configuration, a network configuration, and a schematic configuration of the devices according to the first embodiment of the present invention. The living situation monitoring system 1 includes a living situation monitoring server 2 that monitors a user's living situation via a communication network 4, a client terminal 5 installed in a user's home that uses the system, a user's family, and the like. The external terminal 6 used by the related parties is connected to be communicable.

  At the user's home, a client terminal 5 and a power usage measuring device 8 are installed. The power usage acquired by the power usage measuring device 8 in real time is notified to the client terminal 5 and the client terminal 5 communicates. The life status monitoring server 2 is notified via the network 4, the life status monitoring server 2 has various functions to detect anomalies, and the occurrence of anomalies such as the user's family determined in advance via the communication network 4 It performs actions such as for related parties.

  FIG. 4 shows a functional block diagram of the living situation monitoring system 1 according to the first embodiment of the present invention. In this figure, the living situation monitoring system 1 is managed by a company such as a care center that manages the living situation of individuals or groups, a power company that supplies power to the user's home, or a service provider. Operated.

  The living situation monitoring system 1 includes a transmission / reception unit 12 for transmitting / receiving data via the communication network 4, a central processing unit 13 for processing data received from the transmission / reception unit 12, and other various processes, It comprises a storage unit 14 for storing data, an input unit 15 for inputting / outputting data to / from the central processing unit 13 and a display unit 16. The input unit 15 and the display unit 16 are parts having a man-machine interface function. The transmission / reception unit 12 has a communication protocol function.

  The living situation monitoring system 1 in the present embodiment includes an input unit 15 and a display unit 16, but input / output to the system is performed from the outside via a serial line or a communication network 4 (not shown). It is also possible.

  Further, the central processing unit 13 is a transmission / reception processing means (function) 131 that exchanges data with the transmission / reception unit 12, and an input / output processing means (function) 132 that exchanges data with the input unit 15 or the display unit 16. Information registration means (function) 133 for registering information such as user information, threshold information, destination information, inrush current pattern received via the input / output processing means (function) 132 or the transmission / reception processing means 131, from the user's home The daily load data storage means (function) 134 for storing the notified power usage amount in the daily load database (DB) 143, compares the stored user power usage amount with the user's daily load pattern data, and calculates the difference. Daily load pattern comparison means (function) 135 to be extracted, daily load pattern data with different power usage for each user is corrected based on past data Daily load pattern correction means (function) 136, the difference with the extracted daily load pattern data is compared with the user corresponding daily load difference threshold data 144 storing the threshold information for each user, and exceeds a predetermined threshold. An abnormality occurrence detection means (function) 137 that considers an abnormality to occur when an abnormality occurs, an abnormality occurrence notification means (function) 138 that notifies that an abnormality has occurred at a predetermined destination when an abnormality occurrence is detected, a user's family, etc. The external information input means (function) 139 that enables the input of information when the user wants to monitor the status of the user via the communication network 4 is registered, and the user schedule is registered or corrected. Schedule registration / editing means (function) 13A having a function, scheduled time for issuing a warning to the user when the date and time registered in the schedule is reached or approaching Notification means (function) 13B and inrush current determination means (function) 13C for determining whether or not an inrush current indicating a characteristic current pattern for each device is found in the daily load data when the device is turned on. .

  In addition, the storage unit 14 stores a user information database (DB) 141 that stores information about a user who is to monitor a living situation using the living situation monitoring system 1, and a usage pattern of the user's power. Daily load pattern data 142 for user to be stored, daily load database (DB) 143 for storing changes in daily power consumption as data, difference between daily load pattern data for each user and target daily load data User corresponding daily load difference threshold data 144 for storing a threshold value when an abnormality occurs when the threshold value is exceeded, a monitoring time zone database (DB) for storing a monitoring period registered as a period to be monitored by the user's family, etc. 145, a schedule database (DB) 146 for storing the daily schedule registered by the user's family for each user, the device power And a rush current pattern database (DB) 147 that stores a pattern of the rush current indicating a pattern of current having a feature for each device when turning on the.

  The client terminal 5 is a terminal installed in the home of a user who uses a service provided by the living situation monitoring system 1. The client terminal 5 is connected between a transmission / reception unit 52 for transmitting / receiving data via the communication network 4, a central processing unit (not shown) that processes data from the transmission / reception unit 52, and a central processing unit. It is an interface part between the input unit 55 for inputting / outputting data and the display unit 56 and the power usage measuring device 8 for measuring power, and receives the power usage measured from the power usage measuring device 8, It is comprised from 57 which is the electric power control part IF which issues a control command to the usage-amount measuring apparatus 8. FIG. In the present embodiment, the client terminal 5 and the power usage measuring device 8 are configured separately, but may be integrated and exist as one device.

  The external terminal 6 is a terminal used to access the living situation monitoring system 1 via the communication network 4 to check the user's schedule, and to register / edit the schedule. It is a terminal such as a personal computer that is installed at a support company that checks and provides support.

  The external terminal 6 transmits / receives data between the transmission / reception unit 62 for transmitting / receiving data, the central processing unit 63 for processing data from the transmission / reception unit 62, and the central processing unit 63 via the communication network 4. An input unit 65 that performs input / output and a display unit 66 are included.

  The communication network 4 is a communication that connects the schedule management server 2, the client terminal 5, and the external terminal 6 using a dedicated communication network laid by the user or an IP protocol that defines a line borrowed from a communication carrier. It is a net. For example, ADSL (Asymmetric Digital Subscriber Line), FTTH (Fiber To The Home), CATV (Community Antenna TeleVision), Wide Area LAN (Local Area Network), Power Line Communications (Power Line Communications), etc. can be used. It is.

  FIG. 5 shows a data configuration example of the user information DB 141 that stores various types of information of users who use the living situation monitoring system 1. In the user information DB 141, for each user, “user ID”, “password”, “name”, “address”, “phone number”, “e-mail address” and “power usage status” of the user, age "Attribute information" such as sex and gender, "preference information" such as likes / dislikes going out / AV equipment likes / dislikes air-conditioning equipment / hates TV programs are stored.

  FIG. 6 is a data configuration example of the user-corresponding daily load pattern data 142. Data such as an appropriate amount of power used as a pattern is stored in a column in which the daily time zone is divided every 30 minutes for each user. The break is 10 minutes in addition to every 30 minutes. It may be determined by specifying an appropriate value for operation such as every hour or every hour. In addition, each column may have not only power consumption but also a usage increase as a vector.

  FIG. 7 shows a data configuration example of the daily load DB 143. For each user, the power usage amount of the user is stored every 30 minutes for each date.

  FIG. 8 is a data configuration example of the user-specific daily load difference threshold data 144. FIG. 8 (1) shows a data configuration when a threshold is determined and registered as a whole system regardless of the user, and FIG. 8 (2) is a data configuration example when a threshold is set for each user. . In the present embodiment, an allowable increase / decrease value from the daily load pattern data is registered. When the daily load pattern data is registered as a vector, this data is also registered as a vector.

  FIG. 9 shows a data configuration example of the monitoring time zone DB 145. A monitoring time zone for monitoring a user registered by a related person such as a user's family is configured to be able to register the time to be registered for each user and for each day. In the present embodiment, the monitoring time zone of the user “Ichiro Io” on December 15, 2005 is “07: 00-09: 30”, “12: 00-14: 00”, “18:00”. Three time zones “−19: 30” are registered. Further, information on the parties related to the registered user may be registered.

  FIG. 10 is a data configuration example of the schedule DB 146. In the present embodiment, contents to be performed in the time zone are registered in a frame in which one day is divided every 30 minutes for each user. For example, “walking” is registered for “13: 00-13: 30” on October 15, 2005 of the user “Ichiro Io”.

  FIG. 11 is a data configuration example of the inrush current pattern DB 147. Inrush current patterns are registered for each device. In the present embodiment, when the device is a “rice cooker”, it is “pattern ζ”, the peak value from the steady current is “peak value # 4 from the steady current”, and the width of the peak value is “Peak value width # 4” is registered.

  FIG. 12 is a data configuration example of a notification destination for storing a destination to be notified when an abnormality is detected in the use of “electricity” at the user's home. Multiple notifiers can be registered for each user. For each notifier, "customer ID", "name", "address", "phone number", "FAX number", "e-mail address" "Notification methods" such as "", "password", "questionnaire", telephone / FAX / e-mail, etc. are registered.

  FIG. 13 is an example of a daily load curve showing the amount of daily power usage of the user. In this embodiment, the plotting is performed every hour, but it is also possible to collect and plot the power consumption by determining an optimum value such as every 30 minutes or every 10 minutes.

  The living situation monitoring system 1 according to the first embodiment is configured as described above, and the operation thereof will be described below using a flowchart and the like.

[1. Registration of information]
FIG. 14 is a flowchart showing a processing procedure of an “information registration routine” for registering information used in the living situation monitoring system 1. This operation is performed by the information registration unit 133, and the processing will be described below with reference to FIG. Registration of information such as user information, threshold information, destination information, and inrush current pattern is performed directly using a keyboard or a screen connected to the input unit 15 and the display unit 16 of the living situation monitoring server 2.

  Connect using a personal computer as a terminal using a serial line (not shown), or connect to the network via an in-house LAN (Local Area Network) or communication network 4 and log in to make settings It is also possible to do. When setting information via a network, it is desirable to enhance security to encrypt ID and password transmission and data transmission / reception information. Hereinafter, a processing procedure in the case of performing registration using a keyboard directly connected to the living situation monitoring server 2 will be described with reference to FIG.

  First, a login request is made to the living situation monitoring system 1 (actually connected to the living situation monitoring server 2) by operating the keyboard (S141b). The living situation monitoring server 2 receives the login request (S141a), and requests an ID and password for logging in to the system (S142a). The ID / password request is displayed on a monitor screen or the like via the display unit 16 (S142b), and the contents of the ID / password input by the operator are notified to the living situation monitoring server 2 (S143b), and the living situation monitoring server 2 Receives information (S143a).

  The living situation monitoring server 2 acquires the user ID and password information in the user information DB 141, and determines whether or not the received ID / password matches (S144a). If the ID / password does not match, the process returns to step S142a and the above process is repeated again. When the ID / password matches, the living situation monitoring server 2 transmits a work selection screen or the like (S145a). Registration of various information can be selected on this screen.

  The received selection screen is displayed on the operator's monitor screen (S144b), and the registration work for selecting any information such as user information, threshold information, destination information, and inrush current pattern is selected as the content selected by the operator. (S145b). The information registration unit 133 that has received the request (S146a) creates an input screen for the above-described user information, threshold information, destination information, information related to the inrush current pattern, and the like, and is handled by the operator through the display unit 16. It is displayed on the screen (S147a).

  The operator inputs user information, threshold information, destination information, information related to the inrush current pattern, and the like using the keyboard while viewing the screen (S146b). The input information is notified to the information registration unit 133 via the input unit 15 (S147b). The information registration unit 133 (S148a) inputs the user information, threshold information, destination information, information related to the inrush current pattern, etc., respectively, into the user information DB 141, the destination information data, and the user corresponding daily load difference threshold. Data 144 is registered in the inrush current pattern DB 147 (S149a).

  Next, the information registration unit 133 creates a screen for selecting whether to continue or end the input, and displays the screen on the screen (S14Aa). By looking at the screen displayed on the screen (S148b), the information selected by the operator is notified from the input unit 15 to the information registration means 133 (S149b, S14Ba). The received content is determined (S14Ca), and if the end is selected, this routine ends. When continuation is selected (no route of S14Ca), the process returns to step S147a and the above operation is repeated until the end of the process is selected.

  In the present embodiment, it is configured to determine whether to end or continue the input in step S14Aa. However, in the case of registration contents that must be continuously performed, the above-described S14Aa to S14Aa are used. The operation described in 14Ca is not performed, and the operation immediately returns to step S147a to transmit the screen for inputting input information. In addition, when registration of input information is completed, other procedures such as transition to another screen may be performed.

[2. Registration of power consumption]
FIG. 15 is a flowchart showing a processing procedure of an operation performed by the “daily load data storage routine” in which the living state monitoring server 2 receives the power usage amount used by the user and stores it in the daily load DB 143. This operation is performed by the daily load data storage unit 134, and the process will be described below with reference to FIG.

  When the power usage is received from the power measurement unit IF 57 from the power usage measuring device 8 that measures the power usage in real time (S151b), the client terminal 5 sends the received power usage to the living situation monitoring server 2. Transmit (S152b). The living situation monitoring server 2 receives the information (S151a) and checks the content (S152a). If there is a problem in the check result, an error is notified and a retransmission request is made (S154a), and the process ends.

  The client terminal 5 that has received the error notification (S153b) returns to step S152b and transmits the received power consumption again. If there is no problem with the received data, a successful reception notification is made (S153a), the received data is stored in the user's daily load DB 143 (S155a), and the process is terminated.

  In this embodiment, the amount of power used is periodically acquired, and the received data is transmitted in that cycle. However, after the received data is temporarily stored in the client terminal 5, the life situation is longer. It is also possible to notify the monitoring server 2.

[3. Comparison of daily load data]
FIG. 16 is a flowchart showing the processing procedure of the “daily load data comparison routine” that compares the received power usage amount of the user with the daily load pattern data corresponding to the user and extracts the difference. This operation is performed by the daily load pattern comparison unit 135, and the process will be described below with reference to FIG.

  First, the daily load data of the user is acquired from the daily load DB 143 (S161). Next, user's pattern data is acquired from the user corresponding daily load pattern data 142 (S162). The acquired values are compared, the difference is output to the buffer (S163), and the “daily load pattern correction routine” is activated to correct the daily load pattern data currently used (S164). Next, it is determined whether or not the daily load data of all users has been processed (S165). If not completed, the next user is designated (S166), and the process returns to step S161 to perform the above operation for all the uses. Repeat until the person finishes.

  After the processing of all users is completed, an “abnormality detection routine” is activated to detect whether or not an abnormality has occurred for each user (S167). After returning from the “abnormality occurrence detection routine”, a user is designated to determine whether an abnormality has occurred (S168), and if there is no abnormality, the process proceeds to step S16A. If an abnormality has occurred, the “abnormality occurrence notification routine” is activated to notify a predetermined destination (S169), and the process proceeds to step S16A.

  Next, it is determined whether or not the processing for all users has been completed (S16A). If the processing has not been completed, the next user is designated (S16B), and the process returns to step S168 to process all users. The above processing is repeated until is finished. If all users' processes are complete, the process ends (yes route of S16A).

[4. Correction of daily load pattern data for users]
FIG. 17 shows the daily load pattern statistics of the past predetermined period, and corrects the user-supported daily load pattern data to create new user-supported daily load pattern data. It is a flowchart which shows the process sequence of operation | movement of a routine. This operation is performed by the daily load pattern correction unit 136, and the process will be described below with reference to FIG.

  First, data is added so that past data of unit time is totaled and averaged (S171), and the above addition processing is performed on all previously determined past data (S172, S173). Next, an average value of all the target data is calculated and registered in the user corresponding daily load pattern data 142 as new pattern data of the calculation target unit time. The above operation is processed for all the unit times for one day, and the user corresponding daily load pattern data 142 is updated. This process is performed for all users (S164).

  In this embodiment, the daily load data of the user's power is always obtained, but may be processed, for example, once every 10 times.

[5. Abnormality detection]
FIG. 18 is a flowchart showing a processing procedure of an “abnormality occurrence detection routine” for detecting whether or not an abnormality has occurred in the power consumption for each user. This operation is performed by the abnormality occurrence detection unit 137, and the process will be described below with reference to FIG.

  First, the difference stored in the buffer is compared with the user corresponding daily load difference threshold data 144 (S181). It is determined whether or not the threshold has been exceeded (S182). If the threshold has not been exceeded, nothing is done and the process proceeds to step S184. If the threshold has been exceeded, the user ID that has exceeded the threshold is output to the buffer (S183). Then, the process proceeds to step S184. Next, it is determined whether or not the processing for all users has been completed (S184). If the processing has not been completed, the next user is designated and the process returns to step S181 until all user processing is completed. Repeat the above process. When the processing of all the trading companies is completed (yes route in S184), the processing ends.

[6. Notification of abnormal occurrence]
FIG. 19 is a flowchart showing a processing procedure of an “abnormality occurrence notification routine” for notifying a destination registered in advance by a method registered in advance when an abnormality is detected in the power usage amount of the user. This operation is performed by the abnormality notification unit 138, and the process will be described below with reference to FIG.

  First, the destination notification method registered for the user is acquired from the destination information shown in FIG. 12 (S191), and within the monitoring start time and end time registered by the target notification destination to be processed. It is determined whether or not notification is selected (S192). If it is not within the monitoring time zone, the process ends. If the notification is selected within the monitoring time zone, the process proceeds to step S193. Next, the process branches according to the notification method (S193). In this embodiment, four types of notification are registered as notification methods: “telephone”, “FAX” notification, “electronic mail” notification, and “WEB notification”. First, when notifying by “telephone”, an audio file is generated to notify that the amount of power used deviates from the pattern and shows an abnormal value (S194), and the obtained address is called, and the address is created when the address is answered. The audio information is played (S195), and the process proceeds to step S196.

  In the case of notification by “FAX”, a document indicating that the amount of power used indicates an abnormal value is created (S198), other necessary FAX information is created (S199), and the acquired destination FAX is created. When the destination responds, the created FAX information is transmitted by the FAX protocol (S19A), and the process proceeds to step S196. When notifying by “e-mail”, a sentence indicating that the amount of power used indicates an abnormal value is created (S19B), and the created file is attached to the acquired destination and sent to the mail (S19C). .

  In the case of “WEB notification”, a document indicating that the amount of power used indicates an abnormal value is created, the file is placed in a location where it can be referred to by a URL (S19D), and the acquired e-mail address is set. The URL that can refer to the created file is included in the e-mail and sent (S19E), and the process proceeds to step S196.

  Next, in step S196, it is determined whether or not the processing for all the destinations of the user has been completed. If not, the next destination is designated and the process returns to step S191, and the above processing is performed until the processing for all destinations is completed. repeat. If all destinations have been processed (yes route in S196), the process ends.

  In step S192, it is immediately determined whether or not it is within the monitoring time zone. First, it is determined whether or not the target notification destination is registered for monitoring, and then the registration is performed. A process of determining whether the time is within the monitoring time period may be used. When no abnormality has occurred, a notification that no abnormality has occurred is sent.

[7. Registration of monitoring time zone]
FIG. 20 is a flowchart showing the processing procedure of the operation of an “external information input routine” for inputting information from the outside via a communication network using a specific protocol. This operation is performed by the external information input unit 139, and the processing will be described below with reference to FIG.

  First, a specific communication protocol such as HTTP is activated to enable communication (S201a). Next, the client terminal 6 accesses by specifying a URL or the like using a specific protocol such as HTTP (S201b). Receiving access (S202a), the living situation monitoring server 2 creates and transmits a screen for designating the start and end of the date and time for each user (S203a). The external terminal 6 displays the received content on the screen (S202b), and notifies the start / end time and the like input by an operator such as the user's family (S203b).

  Receiving the start / end time (S204a), the living situation monitoring server 2 stores the start and end of the acquired date and time of monitoring for each user (S205a), and the reception is performed normally and the data is written normally. A “reception OK” message indicating that this has been received is transmitted (S206a). The external terminal 6 that has received “reception OK” displays a screen indicating that the data has been registered normally (S204b).

  In this embodiment, the description of the process for checking the received data for error is saved, but the received data is checked for error, and if an error occurs in the received data, a retransmission request is made. Further, when accessing the URL, it is required to input an ID and a password. For example, it is possible to access by inputting the ID and password shown in FIG.

[8. Register and edit user schedule]
FIG. 21 shows a processing procedure of an operation of a “schedule registration edit routine” for registering or editing a user's daily schedule in the schedule DB 146 using a specific communication protocol from the outside via a communication network. It is a flowchart. This operation is an operation performed by the schedule registration editing means 13A, and the processing will be described below with reference to FIG. In the present embodiment, HTTP is used as a specific communication protocol.

  First, a URL for performing registration / editing of a schedule is specified using HTTP as a communication protocol, and the living situation monitoring server 2 is accessed (S211b). Receiving access (S211a), the living situation monitoring server 2 transmits a login screen, a user selection screen, and the like (S212a). The external terminal 6 that has received the screen information (S212b) transmits the ID and password entered by an operator such as the user's family (S213b). The living situation monitoring server 2 that has received the information such as the ID and password checks the contents (S214a), and if there is an error, notifies the error (S219a) and returns to step S212a. The external terminal 6 that has received the error notification displays an error (S214b) and returns to step S212b.

  If there is no error (yes route in S214a), a schedule registration screen that can be registered and edited with the user's schedule is transmitted (S215a). The external terminal that has received the screen information displays the screen (S215b), and transmits the contents input by the operator to the living situation monitoring server 2 (S216b). The living situation monitoring server 2 that has received the content entered by the operator registers the received content in the schedule DB (S217a), notifies that the schedule has been successfully registered (S218a), and ends the processing. The external terminal 6 that has received the normal registration displays the success on the screen (S217b) and ends the process.

  In this embodiment, the process of checking the normality of the content received in steps S216a and S217a is saved, but if the check is not normal, the error is notified to the external terminal 6 and correct again. It works to prompt you to enter a value. In the case of the present embodiment, since the notification destination can be specified as the user's related person, the ID and password when the user's family logs in to the living situation monitoring system 1 is the notification shown in FIG. The content is the same as the destination. However, the notification destination may be not only the person concerned with the user but also the attending physician or the person in charge of the care center.

[9. Scheduled time warning]
FIG. 22 is a flowchart showing a processing procedure of an operation of a “scheduled time warning routine” for giving a warning notification at or before the time registered in the user's daily schedule. This operation is performed by the scheduled time warning means 13B, and the process will be described below with reference to FIG. Since the “scheduled time warning routine” needs to operate in units of time, it is periodically started.

  First, it is determined whether or not there is a schedule scheduled by the user when activated (S221). If there is no scheduled schedule, the process proceeds to step S224. If there is a schedule, the contents of the schedule are acquired (S222), a “warning routine” is started to notify the user (S223), and the process proceeds to step S224. In step S224, it is determined whether or not the processing for all users has been completed. If not, the next user is designated (S225), the process returns to step S221, and the processing for all users is completed. Repeat the above operation until When all the users' processes are completed, the CPU sleeps until the next cycle (S226).

  Although the flowchart for the “Warning” routine is not shown, it is possible to give a warning by activating an alarm device connected to the screen, speaker, or serial line of the client terminal 5 at the user's house. It is. Furthermore, as shown in FIG. 18, it is also possible to notify a mobile phone owned by the user by e-mail notification or automatic call transmission.

[10. Judgment of inrush current]
FIG. 23 shows the operation of the “inrush current determination routine” for specifying the power-on time of the corresponding device by comparing the contents of the user's daily load data stored in the daily load database with the inrush current pattern. It is a flowchart which shows the process sequence of. This operation is performed by the inrush current determination means 13C, and the process will be described below with reference to FIG.

  First, when the power consumption measuring device 8 that periodically monitors the power usage status detects a large change in the current consumption (S231c), it notifies the occurrence of a large change in the current consumption through an interrupt process or the like. (S232c) to complete the process. The client terminal 5 that has received the information transmits the received current consumption data to the living situation monitoring server 2 (S231b), and ends the process. In addition to notifying the client terminal 5 by an interrupt or the like when a large change occurs as described above, the client terminal 5 may be notified in a normal cycle.

  The living situation monitoring server 2 that has received the current consumption data (S231a) first determines whether the comparison processing for all the devices has been completed (S232a). If completed (yes route in S232a), the process ends without doing anything. If the comparison processing for all the devices has not been completed, the inrush current pattern DB 147 is used to determine the device for determining the received data (S233a, S234a), and if they do not match, the next device is designated (S235a), Returning to step S232a, the above operation is repeated until the comparison processing for all devices is completed. If they match, the matched device is output (S236a), and the process ends. Thereafter, processing such as notifying the output destination of information on the device and the like is performed.

  Matching means that the peak value and its width from the steady current value at the time of measurement are measured, and if those values satisfy the peak value and width of the inrush current of the device shown in FIG. It is judged that it matches.

When the power consumption measuring device 8 detects a change in the current consumption by the above operation, the client terminal 5 is notified, and the client terminal 5 notifies the living state monitoring server 2 of the received information, so that the device The inrush current due to the connection can be detected. In the present embodiment, the operation that the user regularly performs such as turning on the rice cooker or turning on the TV to watch a favorite TV program is registered within the monitoring time zone, By determining whether or not there is an inrush current detected when the device is turned on, it is possible to know whether or not an abnormality has occurred in the user, and to notify the notification destination. On the notification destination side, if the power-on operation normally performed by the user is not performed, it can be determined that an abnormality has occurred and a countermeasure such as calling can be taken.
The first embodiment of the present invention is configured and operates as described above.

  According to the present invention, for example, it is possible to determine the living status of an elderly person living alone, based on the power usage status, and when it is determined that an abnormality has occurred, a notification is made to a predetermined destination. It is possible to flexibly respond to each user by configuring so that the judgment criteria for the occurrence of abnormality can be changed, and the specific pattern of inrush current can be specified for the device that the user has turned on Since it can be estimated by using it, it becomes possible for a related person such as a user's family to provide assistance while confirming the life of a family such as an elderly person living alone.

  For example, if an elderly person living alone falls asleep and falls into physical condition, the pattern of power consumption will deviate from the time he fell asleep, and the rice cooker is always turned on at a fixed time to eat. It is possible to detect abnormalities by not seeing the inrush current pattern that can always be seen, etc., and by responding to notification destinations such as mobile phones and mobile phone e-mail addresses that can be contacted immediately Can be performed quickly.

  Next, a second embodiment will be described below. FIG. 24 is a functional block diagram of the living situation monitoring apparatus 7 according to the second embodiment. In the present embodiment, the living situation monitoring device 7 is installed at the user's home, and all the functions described in the first embodiment are incorporated in the living situation monitoring device 7, and that portion is the first. This is different from the embodiment. This embodiment is the same as the client terminal 5 of the first embodiment having the function of the living situation management server of the first embodiment.

   The difference from the first embodiment is that only a user, a system administrator, a user related person, etc. log in to the living situation monitoring apparatus, so that the content registered in the user information DB 741 is small. Thus, the user-responsive daily load pattern data 742, the daily load DB 743, the monitoring time zone DB 745, the schedule DB 746, and the like are sufficient for the individual user. Also, the various means are different in that processing such as search for the number of users is unnecessary.

In addition, with the first and second embodiments, the living situation monitoring device shown in the second embodiment is installed at the user's house, and the living situation monitoring device server is also installed at the electric power company, etc. When a malfunction is detected in the operation of the living situation monitoring apparatus server, the living situation monitoring apparatus can operate alone. In this case, it can be realized by providing operation modes such as a single mode and a joint operation mode in the living situation monitoring apparatus, and providing a function for maintaining the consistency of various databases included in the living situation monitoring apparatus and the living situation monitoring server.
The second embodiment of the present invention is configured and operates as described above.

  According to the present embodiment, the living situation monitoring device alone at the user's home can perform the same operation as in the first embodiment, so that the central living situation monitoring server in the first embodiment becomes inoperable. Even if it falls, it can operate.

It is a block diagram at the time of acquiring the electric power consumption of the conventional user. It is a conceptual diagram of the living condition monitoring system concerning the 1st Embodiment of this invention. It is the schematic of the network structure of the living condition monitoring system concerning the 1st Embodiment of this invention. It is a functional block diagram of a schedule management server, a client terminal, and an external terminal of the living situation monitoring system according to the first embodiment of the present invention. It is a data structural example of user information DB of FIG. 4 and FIG. It is a data structural example of the user corresponding daily load pattern data of FIG. 4 and FIG. It is a data structural example of daily load DB of FIG. 4 and FIG. It is a structural example of the user corresponding daily load difference threshold value data of FIG. 4 and FIG. It is a data structural example of monitoring time slot | zone DB of FIG. 4 and FIG. It is a data structural example of schedule DB of FIG. 4 and FIG. It is a data structural example of the inrush current pattern DB of FIG. 4 and FIG. It is a data structural example of the notification destination in the 1st Embodiment of this invention. It is an example of the daily load curve of the electric power consumption in the 1st Embodiment of this invention. It is a flowchart which shows the process sequence of the operation | movement which the information registration means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the daily load data storage means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the daily load pattern comparison means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the daily load pattern correction | amendment means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the abnormality occurrence detection means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the abnormality occurrence notification means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the external information input means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the schedule registration edit means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the scheduled time warning means of FIG. 4 and FIG. 24 performs. It is a flowchart which shows the process sequence of the operation | movement which the inrush current determination means of FIG. 4 and FIG. 24 performs. It is a functional block diagram of the living condition monitoring apparatus concerning the 2nd Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Living situation monitoring system 4 Communication network 5 Client terminal 6 External terminal 7 Living situation monitoring apparatus 8 Electric power consumption measuring device 12, 52, 62, 72 Transmission / reception part 13, 53, 63, 73 Central processing part 14, 74 Storage part 15, 55, 65, 75 Input unit 16, 56, 66, 76 Display unit 131, 731 Transmission / reception processing unit 132, 732 Input / output processing unit 133, 733 Information registration unit 134, 734 Daily load data storage unit 135, 735 Daily load Pattern comparison means 136, 736 Daily load pattern correction means 137, 737 Abnormality detection means 138, 738 Abnormality notification means 139, 739 External information input means 13A, 73A Schedule registration editing means 13B, 73B Scheduled time warning means 13C, 73C Inrush Current determination means 141, 741 User information ( Database) DB
142, 742 Daily load pattern data for users 143, 743 Daily load (database) DB
144, 744 User corresponding daily load difference threshold data 145, 745 Monitoring time zone (database) DB
146, 746 Schedule (database) DB
147,747 Inrush current pattern (database) DB
57 Power Measurement Unit IF

Claims (14)

A living situation monitoring system in which a living situation monitoring server that monitors an individual's living situation via a communication network and a client terminal are communicably connected,
Daily load pattern data corresponding to users, which is a pattern of the daily power usage of users,
Daily load data storage means for receiving daily power usage status received from the client terminal and storing it in the daily load database;
A daily load pattern comparing means for comparing the user corresponding daily load pattern data and the daily load data received and stored from the client terminal to extract a difference;
An abnormality occurrence detection means for comparing the extracted difference with a predetermined user corresponding daily load difference threshold data and determining that an abnormality has occurred when the threshold is exceeded;
An abnormality occurrence notifying means for notifying a predetermined destination when the occurrence of the abnormality is detected;
A living situation monitoring system characterized by comprising: Daily load pattern correction means for correcting the user-supported daily load pattern data by taking statistics of the daily load data of a predetermined period in the past and creating new user-supported daily load pattern data;
The living situation monitoring system according to claim 1, further comprising:   3. The life according to claim 1, wherein the abnormality occurrence notification unit performs abnormality occurrence notification according to a selection content of whether or not to notify abnormality occurrence in correspondence with a destination registered for each user. Condition monitoring system. An external information input means for inputting information from the outside using a specific protocol via a communication network;
A monitoring time zone database that acquires and stores the monitoring start time and end time input using the external information input means,
4. The living situation monitoring system according to claim 1, wherein the daily load pattern comparison unit, the abnormality occurrence detection unit, and the abnormality occurrence notification unit operate only during the period. A schedule database that stores users' daily schedules;
A schedule registration editing means for registering or editing a user's daily schedule in the schedule database using a specific communication protocol from outside via a communication network;
The living situation monitoring system according to any one of claims 1 to 4, further comprising: A scheduled time warning means for performing a warning notification when the time registered in the daily schedule of the user is reached or before the registered time is reached;
The living condition monitoring system according to any one of claims 1 to 5, further comprising:   The schedule database for storing the daily schedule of the user includes an area for storing preference information indicating a degree of preference of the user for each item to be registered. The described living situation monitoring system. An inrush current pattern database that stores, for each device, an inrush current pattern that is seen when a device that uses power is turned on;
Inrush current determination means for identifying the power-on time of the corresponding device by comparing the content of the user's daily load data stored in the daily load database and the inrush current pattern, The living situation monitoring system according to any one of claims 1 to 7, characterized in that: A living situation monitoring device for monitoring a living situation configured to be communicable via a communication network,
Daily load data for users that pattern the usage status of users' daily power,
Daily load data storage means for storing the measured daily power usage in the daily load database;
Daily load pattern comparing means for extracting the difference by comparing the daily load data with the user corresponding daily load data;
An abnormality occurrence detection means for comparing the extracted difference with a predetermined user corresponding daily load difference threshold data and determining that an abnormality has occurred when the threshold is exceeded;
An abnormality occurrence notifying means for notifying a predetermined destination when the occurrence of the abnormality is detected;
A living situation monitoring device characterized by comprising: Daily load pattern correction means for correcting the user-supported daily load pattern data by taking statistics of the daily load data of a predetermined period in the past and creating new user-supported daily load pattern data;
The living condition monitoring apparatus according to claim 9, comprising: An inrush current pattern database that stores, for each device, an inrush current pattern that is seen when a device that uses power is turned on;
Inrush current determination means for identifying the power-on time of the corresponding device by comparing the content of the user's daily load data stored in the daily load database and the inrush current pattern, The life situation monitoring device according to claim 9 or 10, characterized in that A living situation monitoring server that monitors an individual's living situation via a communication network, and a living situation monitoring method that monitors an individual's living situation in which a client terminal is communicably connected,
Daily load data storage step for receiving daily power usage status received from the client terminal and storing it in the daily load database;
A daily load pattern comparison step of extracting a difference by comparing the daily load data corresponding to the user's daily power usage and the daily load data received and stored from the client terminal;
An abnormality occurrence detection step of comparing the extracted difference with a predetermined user corresponding daily load difference threshold data and determining that an abnormality has occurred when the threshold is exceeded;
An abnormality occurrence notification step of notifying a predetermined destination when the occurrence of the abnormality is detected;
A living situation monitoring method characterized by comprising: Referring to the inrush current pattern database that stores the inrush current pattern that is seen when a device that uses power is turned on for each device, the daily load data of the user stored in the daily load database Inrush current determination step for identifying the time of power-on of the corresponding device by comparing the content and the inrush current pattern;
The living condition monitoring method according to claim 12, comprising: A program that runs on a computer that monitors personal life
Daily load data storage processing for receiving daily power usage status received from the client terminal and storing it in the daily load database;
A daily load pattern comparison process that extracts a difference by comparing the daily load data that is received from the client terminal and stored, and the user corresponding daily load data that is a pattern of the daily power usage of the user;
An abnormality occurrence detection process in which the extracted difference is compared with a predetermined user corresponding daily load difference threshold data and the abnormality occurrence is determined when the threshold is exceeded.
An abnormality occurrence notification process for notifying a predetermined destination when the occurrence of the abnormality is detected;
A living situation monitoring program characterized by operating a computer on a computer.

Images