WO2020184500A1

WO2020184500A1 - Program, method for creating learning model, wearable device, information processing device, and information processing method

Info

Publication number: WO2020184500A1
Application number: PCT/JP2020/009937
Authority: WO
Inventors: 良太三島
Original assignee: 株式会社カネカ
Priority date: 2019-03-14
Filing date: 2020-03-09
Publication date: 2020-09-17
Also published as: JPWO2020184500A1

Abstract

Provided are a program and the like that are capable of notifying the types of fetal movements that occur in a pregnant woman.　A fetal movement sensor detects a fetal movement that occurs in a pregnant woman, and a determination is made as to the presence or absence of a fetal movement and the type of the fetal movement when there is a fetal movement, on the basis of a detection signal from the fetal movement sensor. A terminal that has acquired fetal movement information relating to the determined fetal movement, identifies the type of the fetal movement on the basis of the acquired fetal movement information, and outputs a control signal to execute a process corresponding to the identified type. Thus, processes corresponding to the types of the fetal movement are executed.

Description

Program, learning model generation method, wearable device, information processing device and information processing method

This disclosure relates to a program, a learning model generation method, a wearable device, an information processing device, and an information processing method.

Pregnant women can be aware of pregnancy due to changes in their own physical condition and physical condition, but it is difficult for a partner to be aware of pregnancy, and the temperature difference between the pregnant woman and her partner in the feeling of pregnancy and awareness of becoming a parent It's difficult to fill. Therefore, a technique has been proposed that allows the partner to feel pregnant by sharing the occurrence of fetal movement between the pregnant woman and the partner. For example, in Patent Document 1, the fetal movement of a pregnant woman is monitored, and when the fetal movement occurs, fetal movement information indicating that the fetal movement has occurred is transmitted to a terminal owned by the partner, thereby indicating that the fetal movement has occurred. A system that can be shared with partners is disclosed.

Japanese Unexamined Patent Publication No. 2018-171265

In the system disclosed in Patent Document 1, it is possible to share the occurrence of fetal movement between the pregnant woman and the partner, but it is difficult to share what kind of fetal movement has occurred.

The present disclosure has been made in view of such circumstances, and the purpose thereof is to provide a program, etc. that can notify not only the occurrence of fetal movement but also what kind of fetal movement has occurred. To do.

The program according to the present disclosure acquires fetal movement information related to the fetal movement of a pregnant woman, identifies the type of fetal movement based on the acquired fetal movement information, and outputs a control signal for controlling processing according to the specified fetal movement type. Let the computer perform the process to be performed.

In the present disclosure, by performing processing according to the type of fetal movement, it is possible to notify the type of fetal movement that has occurred according to the executed processing. Therefore, it is possible to grasp what kind of fetal movement has occurred even in a family member such as a partner.

It is a schematic diagram which shows the structural example of the fetal movement notification system. It is a block diagram which shows the configuration example of the terminal for a pregnant woman and the terminal for notification destination. It is a schematic diagram which shows the structural example of the DB stored in the terminal for a pregnant woman and the terminal of a notification destination. It is a schematic diagram which shows the configuration example of DB stored in the notification destination terminal. It is a flowchart which shows an example of the processing procedure performed by a pregnant woman terminal. It is a schematic diagram which shows the structural example of the trained model. It is a block diagram which shows the structural example of the learning apparatus. It is a flowchart which shows an example of the procedure of the learning process by a learning apparatus. It is a flowchart which shows an example of the processing procedure performed by the notification destination terminal. It is a schematic diagram which shows the structural example of DB stored in the terminal for a pregnant woman. It is a schematic diagram which shows the configuration example of DB stored in the notification destination terminal. It is a flowchart which shows an example of the processing procedure performed by the pregnant woman terminal of Embodiment 2. It is a flowchart which shows an example of the processing procedure performed by the notification destination terminal of Embodiment 2. It is a schematic diagram which shows the display example of the image of a fetus. It is a schematic diagram which shows the structural example of a pressurizing tool. It is a flowchart which shows an example of the processing procedure performed by the pregnant woman terminal of Embodiment 5. 6 is a flowchart showing another example of the processing procedure performed by the pregnant woman terminal of the fifth embodiment. 6 is a flowchart showing another example of the processing procedure performed by the pregnant woman terminal of the fifth embodiment. It is a flowchart which shows an example of the processing procedure performed by the pregnant woman terminal of Embodiment 6. It is a schematic diagram which shows the structural example of the fetal movement notification system of Embodiment 7. It is a schematic diagram which shows the structural example of the DB stored in the terminal for a pregnant woman and the terminal of a notification destination. It is a schematic diagram which shows the configuration example of DB stored in the notification destination terminal. It is a flowchart which shows an example of the notification processing procedure of fetal movement information. It is a schematic diagram which shows the screen example in the terminal for pregnant women. It is a schematic diagram which shows the screen example in the terminal for pregnant women. It is a schematic diagram which shows the screen example in the terminal for pregnant women. It is a schematic diagram which shows the screen example in the terminal for pregnant women. It is a schematic diagram which shows the screen example in the notification destination terminal. It is a schematic diagram which shows the screen example in the notification destination terminal. It is a flowchart which shows an example of the update processing procedure of a papameter by a notification destination terminal. It is a flowchart which shows another example of the notification processing procedure of fetal movement information. It is a schematic diagram which shows the screen example of the message sending and receiving application. It is a schematic diagram which shows the screen example of the message sending and receiving application. It is a flowchart which shows another example of the notification processing procedure of fetal movement information. It is a schematic diagram which shows the structural example of the fetal movement notification system of Embodiment 8. It is a block diagram which shows the configuration example of a server and a system user terminal. It is a schematic diagram which shows the configuration example of DB stored in a server. It is a schematic diagram which shows the configuration example of DB stored in a server. It is a schematic diagram which shows the relationship of each apparatus of the fetal movement notification system of Embodiment 8. It is a flowchart which shows an example of the process process of providing fetal movement information. It is a block diagram which shows the structural example of the terminal for pregnant women of Embodiment 9. It is a flowchart which shows an example of the processing procedure performed by the pregnant woman terminal of Embodiment 9. It is a flowchart which shows an example of the notification processing procedure of the fetal movement information of Embodiment 10. It is a schematic diagram which shows the screen example in the terminal for pregnant women.

The program of the present disclosure, the method of generating the learning model, the wearable device, the information processing device, and the information processing method will be described in detail below based on the drawings showing the embodiments thereof.

(Embodiment 1)
FIG. 1 is a schematic diagram showing a configuration example of a fetal movement notification system. The fetal movement notification system of the present embodiment is a system that monitors the fetal movement of a pregnant woman and notifies that the fetal movement has occurred when the fetal movement has occurred and what kind of fetal movement has occurred. The fetal movement notification system of the present embodiment includes a fetal movement sensor 10 for detecting fetal movement of a pregnant woman, a terminal for pregnant women 20, a notification destination terminal 30, and the like. The fetal movement sensor 10 and the pregnant woman terminal 20 are configured to be communicable, and directly transmit and receive information. The pregnant woman terminal 20 and the notification destination terminal 30 can be connected to a network N such as the Internet, and transmit and receive information via the network N.

The fetal movement sensor 10 is provided on, for example, an abdominal band, a pregnant woman's band, a belly band, etc. (hereinafter, collectively referred to as a pregnant woman's band 10a) worn by a pregnant woman on the abdomen, so as to detect fetal movement when the pregnant woman wears the pregnant woman's band 10a. It is a configured sensor. The fetal movement sensor 10 has, for example, a plurality of pressure sensors, and detects fetal movement by detecting the movement (change in pressure from the inside of the abdomen) that appears on the abdominal surface of a pregnant woman due to fetal movement (movement of the fetus). As the pressure sensor, for example, a sensor that detects a pressure change by using a sensor element such as a piezoelectric element, a capacitance element (capacitor), or a piezoresistive element can be used. The sensor element is formed, for example, in the shape of a rectangular surface so that it can be expanded and contracted in the surface direction. Further, it may be configured to detect a pressure change (information on fetal movement) by using an ultrasonic sensor (echo sensor) using an ultrasonic element, a small stethoscope, an acceleration sensor, or the like. Further, a plurality of types of these sensors may be combined to collect fetal movement information, and the detection accuracy can be improved by combining a plurality of types of sensors. The fetal movement sensor 10 has a transmission unit that transmits a detection result of fetal movement, specifically, a detection result (detection signal) by each pressure sensor to an external device by, for example, wireless communication. The fetal movement sensor 10 of the present embodiment transmits a detection result of fetal movement (detection signal by each pressure sensor) to the pregnant woman terminal 20. The pregnant woman band 10a illustrated in FIG. 1 is a band-shaped pregnant woman band, and is attached to the abdomen of a pregnant woman by, for example, attaching hook-and-loop fasteners provided at both ends. However, the fetal movement sensor 10 may be provided on a tubular pregnant woman's band, or may be configured in a sheet shape to be attached to the abdomen of the pregnant woman. Further, the fetal movement sensor 10 may be connected to the pregnant woman terminal 20 via a cable and may transmit the detection result to the pregnant woman terminal 20 by wired communication via the cable. Further, the fetal movement sensor 10 may be configured to detect not only fetal movement but also fetal heart rate, pulse rate and the like.

The pregnant woman terminal 20 is a terminal carried by the pregnant woman or a terminal located in the vicinity of the pregnant woman, and is a smartphone, a tablet terminal, a personal computer, or the like. The pregnant woman terminal 20 receives a signal (output data) output from the fetal movement sensor 10, generates information on fetal movement (fetal movement information) based on the received signal, and transmits the information to the notification destination terminal 30 and the like. .. The notification destination terminal 30 is, for example, a terminal used by a pregnant woman's husband, a partner, or the like, such as a smartphone, a tablet terminal, or a personal computer. Further, the notification destination terminal 30 may be a wearable device such as a smart watch or a smart speaker. The notification destination terminal 30 receives the fetal movement information transmitted by the pregnant woman terminal 20, and performs a process of notifying the user of the notification destination terminal 30 of information on the fetal movement based on the received fetal movement information. An application program for realizing the fetal movement notification system of the present embodiment is installed in the pregnant woman terminal 20 and the notification destination terminal 30, and the

terminals

20 and 30 are installed in the fetal movement notification system by executing this application program. Performs various related information processing.

FIG. 2 is a block diagram showing a configuration example of the pregnant woman terminal 20 and the notification destination terminal 30. The pregnant woman terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, a sensor communication unit 26, a reading unit 27, and the like, and these units are connected to each other via a bus. ing. The control unit 21 includes one or a plurality of processors such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). The control unit 21 appropriately executes the control program 22P stored in the storage unit 22 to perform various information processing, control processing, and the like that the pregnant woman terminal 20 should perform.

The storage unit 22 includes a RAM (RandomAccessMemory), a flash memory, a hard disk, an SSD (SolidStateDrive), and the like. The storage unit 22 stores in advance various data and the like necessary for executing the control program 22P and the control program 22P executed by the control unit 21. Further, the storage unit 22 temporarily stores data or the like generated when the control unit 21 executes the control program 22P. Further, the storage unit 22 stores a fetal movement notification application (fetal movement notification application program) 22a for realizing the fetal movement notification system of the present embodiment and a fetal movement history DB (database) 22b described later. The fetal movement history DB 22b may be stored in an external storage device connected to the pregnant woman terminal 20, or may be stored in a storage device capable of communicating with the pregnant woman terminal 20 via the network N, a storage server in the cloud, or the like. Good. The fetal movement notification application 22a may be downloaded by the control unit 21 from an external device via the network N via the communication unit 23 and stored in the storage unit 22. Further, the fetal movement notification application 22a may be one that the control unit 21 reads from the portable storage medium 2a by the reading unit 27 and stores it in the storage unit 22.

The communication unit 23 is an interface for connecting to the network N by wired communication or wireless communication, and transmits / receives information to / from an external device via the network N. The input unit 24 receives an operation input by the user and sends a control signal corresponding to the operation content to the control unit 21. The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 21. The input unit 24 and the display unit 25 may be a touch panel integrally configured. The sensor communication unit 26 is an interface for performing wired communication or wireless communication with the fetal movement sensor 10, receives a signal output from the fetal movement sensor 10 (fetal movement detection result), and controls the received signal. Send to 21.

The reading unit 27 reads information stored in a portable storage medium 2a including a CD (Compact Disc) -ROM, a DVD (Digital Versatile Disc) -ROM, a USB (Universal Serial Bus) memory, and an SD (Secure Digital) card. .. The control program 22P and data stored in the storage unit 22 may be read by the control unit 21 from the portable storage medium 2a via the reading unit 27 and stored in the storage unit 22. Further, the control program 22P and the data stored in the storage unit 22 may be downloaded by the control unit 21 from an external device via the network N via the communication unit 23 and stored in the storage unit 22.

The notification destination terminal 30 has a notification unit 36 instead of the sensor communication unit 26, and has the same configuration as the pregnant woman terminal 20 except that the storage unit 32 stores the processing DB 32c. The description of is omitted. Further, the fetal movement notification application 22a stored in the pregnant woman terminal 20 is a pregnant woman application, and the fetal movement notification application 32a stored in the notification destination terminal 30 is a notification destination application, which is a different program. However, it may be configured so that it can be used as a pregnant woman application 22a or a notification destination application 32a by setting different setting contents for a common program.

The notification unit 36 includes, for example, a vibrator, and notifies the user of the notification destination terminal 30 of a predetermined situation (the occurrence of fetal movement and the type of fetal movement) by vibrating the vibrator according to an instruction from the control unit 31. .. The notification unit 36 is configured so that a plurality of patterns of vibration can be generated by a vibrator. Preferably, by generating a movement close to the fetal movement, the feeling of sharing between the pregnant woman and the partner can be strengthened. At that time, it is possible to improve the reproducibility of fetal movement by using not only a vibrator but also an actuator, a motor, or the like. The notification unit 36 may be configured to notify a predetermined situation by lighting or blinking a lamp, sounding a buzzer, outputting a message by a speaker, displaying an image by the display unit 35, or the like. Further, the lamp lighting or blinking process and the buzzer ringing process may be configured to enable processing of a plurality of patterns. The types of fetal movements are, for example, fetal movements that occur when the fetus is hiccuping, fetal movements that occur when the fetus is pushing the pregnant woman's abdomen with her hands, fetal movements that occur when the fetus is kicking the pregnant woman's abdomen with her feet, and the fetus is rotating. There are occasional fetal movements, fetal movements that occur when the fetus is hiccuping, and so on. Therefore, the message output by the speaker and the image displayed by the display unit 35 may be a plurality of patterns of messages and images according to the type of fetal movement, respectively, and the plurality of patterns of messages and images are stored in advance in the storage unit 32. It may be stored in. The message according to the type of fetal movement is, for example, "hiccups" or "kicking with the foot", and the image according to the type of fetal movement can be imagined, for example, that the fetus is hiccuping. Images and images that allow you to imagine that the fetus is kicking with your feet.

FIG. 3A is a schematic diagram showing a configuration example of

DB

22b and 32b stored in the pregnant woman terminal 20 and the notification destination terminal 30, and FIG. 3B is a schematic diagram showing a configuration example of DB 32c stored in the notification destination terminal 30. .. In the present embodiment, the fetal movement history DB 22b stored in the pregnant woman terminal 20 and the fetal movement history DB 32b stored in the notification destination terminal 30 have the same configuration, and FIG. 3A shows the fetal

movement history DB

22b and 32b. FIG. 3B shows the processing DB 32c. The fetal

movement history DBs

22b and 32b store information about the fetal movement detected by the fetal movement sensor 10. The fetal

movement history DB

22b, 32b shown in FIG. 3A includes a fetal movement ID column, a date and time column, a duration column, a type column, and the like. The fetal movement ID sequence stores the identification information assigned to each fetal movement detected by the fetal movement sensor 10. The date and time column stores the date and time when the fetal movement sensor 10 detects the fetal movement in association with the fetal movement ID. The detection date and time of fetal movement is represented by, for example, a time (year / month / day / hour / minute / second), and is transmitted from the fetal movement sensor 10 together with the detection result (detection signal of the pressure sensor). The fetal movement sensor 10 has a clock that indicates the time, and when a detection signal is output from any of the pressure sensors, the output detection signal and the time (date and time information) at that time are used for pregnant women. Send to terminal 20. The duration column and the type column respectively store the duration of each fetal movement and the type of each fetal movement in association with the fetal movement ID. The duration and type of fetal movement is information specified based on the detection result from the fetal movement sensor 10.

The fetal movement ID stored in the fetal movement history DB 22b of the pregnant woman terminal 20 is issued and stored by the control unit 21 when the control unit 21 of the pregnant woman terminal 20 receives the detection result from the fetal movement sensor 10. Further, as for the date and time stored in the fetal movement history DB 22b of the pregnant woman terminal 20, when the control unit 21 receives the detection result from the fetal movement sensor 10, the date and time information received together with the detection result is stored by the control unit 21. Further, the duration and type stored in the fetal movement history DB 22b of the pregnant woman terminal 20 are stored by the control unit 21 each time the control unit 21 specifies based on the detection result received from the fetal movement sensor 10. When the information about one fetal movement is stored in the fetal movement history DB 22b, the pregnant woman terminal 20 collectively transmits the information about one fetal movement to the notification destination terminal 30. The stored contents of the fetal movement history DB 32b of the notification destination terminal 30 are stored by the control unit 31 when the control unit 31 receives information on the fetal movement from the pregnant woman terminal 20 via the network N. The stored contents of the fetal

movement history DB

22b, 32b are not limited to the example shown in FIG. 3A, and the fetal

movement history DB

22b, 32b may have different configurations. For example, the detection result (detection signal by the pressure sensor) itself received from the fetal movement sensor 10 for each fetal movement may be stored in the fetal movement history DB 22b of the pregnant woman terminal 20. When storing the detection result from the fetal movement sensor 10, it is stored in a predetermined area of the storage unit 22, an external storage device connected to the pregnant woman terminal 20, or an external storage device that the pregnant woman terminal 20 can communicate with. May be good. In this case, the fetal movement history DB 22b may store information for reading the detection result from the fetal movement sensor 10 (for example, a file name indicating a storage location of the detection result). Further, the time zone (wearing start time and wearing end time) when the pregnant woman wears the fetal movement sensor 10 may be stored in the fetal movement history DB 22b of the pregnant woman terminal 20. For example, when the fetal movement sensor 10 has a power button, the fetal movement sensor 10 transmits the time at this point (wearing start time) to the pregnant woman terminal 20 when the power button is turned on and the operation is started. Further, when the power button is turned off and the operation is completed, the fetal movement sensor 10 transmits the time at this point (wearing end time) to the pregnant woman terminal 20. The pregnant woman terminal 20 sets the wearing start time and the wearing end time received from the fetal movement sensor 10 as the fetal movement history DB 22b. In this case, the information of each fetal movement stored in the fetal movement history DB 22b is stored for each wearing time zone.

The processing DB 32c stores information on notification processing executed by the notification unit 36 according to the type of fetal movement. The processing DB 32c shown in FIG. 3B includes a processing ID string, a type column, and a processing information string. The process ID column stores the identification information assigned to each process. The type column stores the types of fetal movements that can be discriminated in advance in the fetal

movement notification applications

22a and 32a in association with the processing ID. The processing information column stores information indicating the notification processing that can be executed by the notification unit 36 in association with the processing ID. As the information indicating the notification process, for example, the process code assigned to each notification process may be used. The processing ID and the type of fetal movement are stored in advance in the processing DB 32c. The processing information is stored or changed (updated) by the control unit 31 when, for example, on the registration screen based on the fetal movement notification application 32a, the user specifies (inputs) notification processing according to each type via the input unit 34. To. As the default process, information on different notification processes may be stored in the process DB 32c in advance. In the example shown in FIG. 3B, notification processing in which the vibration pattern by the vibrator is different for each of the four types of fetal movements is registered, but the present invention is not limited to this example. The different notification processes may be processes in which the lamp lighting or blinking pattern is different, processes in which the buzzer sounds are different, audio output of different messages by the speaker, display of different images by the display unit 35, and the like.

In the pregnant woman terminal 20 having the above-described configuration, when the control unit 21 executes (activates) the fetal movement notification application 22a, it starts receiving the detection result transmitted from the fetal movement sensor 10. Then, the control unit 21 determines the presence or absence of fetal movement based on the detection result received from the fetal movement sensor 10, and if there is fetal movement, determines the type of fetal movement. When determining the presence or absence of fetal movement and the type of fetal movement if there is fetal movement, the control unit 21 stores the determined fetal movement information (fetal movement information) in the fetal movement history DB 22b and transmits the determined fetal movement to the notification destination terminal 30. The destination information of the notification destination terminal 30 is registered in the fetal movement notification application 22a, and the control unit 21 transmits the fetal movement information to the notification destination terminal 30 using the destination information registered in the fetal movement notification application 22a. When the notification destination terminal 30 executes (activates) the fetal movement notification application 32a, the control unit 31 starts receiving the fetal movement information transmitted from the pregnant woman terminal 20. Then, the control unit 31 identifies the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20, and causes the notification unit 36 to execute the notification process according to the specified type. By such a process, it is possible to notify the user of the notification destination terminal 30 that the fetal movement is detected by the fetal movement sensor 10 and the type of the detected fetal movement.

The processing performed by the pregnant woman terminal 20 will be described below based on the flowchart. FIG. 4 is a flowchart showing an example of a processing procedure performed by the pregnant woman terminal 20. The process shown in FIG. 4 is realized by the control unit 21 executing the control program 22P and the fetal movement notification application 22a stored in the storage unit 22. In the present embodiment, the control unit 21 performs the following processing by executing the control program 22P and the fetal movement notification application 22a, but some of the processing may be realized by a dedicated hardware circuit.

The control unit (acquisition unit) 21 has determined whether or not the detection result (detection signal) output from the fetal movement sensor 10 has been acquired by the sensor communication unit 26 (S11), and has not acquired the detection signal. If it is determined (S11: NO), it waits until it is acquired. When it is determined that the detection signal from the fetal movement sensor 10 has been acquired (S11: YES), does the control unit (determination unit) 21 include a signal based on fetal movement in this detection signal based on the acquired detection signal? It is determined whether or not (S12). When it is determined that the fetal movement is not included (S12: NO), the control unit 21 returns to the process of step S11 and determines the type of the fetal movement when it is determined that the fetal movement is included (S12: YES). (S13).

In steps S12 to S13, the control unit 21 includes, for example, a process of determining whether or not the detection signal from the fetal movement sensor 10 includes a fetal movement-based signal by a template matching technique, and a fetal movement-based signal. For example, a process of determining the type of fetal movement is performed. Specifically, for each type of fetal movement, a template based on the signal waveform (pressure fluctuation) of a general detection signal acquired by each pressure sensor of the fetal movement sensor 10 when each type of fetal movement occurs is stored in advance in the storage unit 22. Remember in. Then, the control unit 21 detects whether or not the detection signal acquired from the fetal movement sensor 10 has a signal waveform that matches any of the templates, and if the matching signal waveform is detected, a signal based on the fetal movement is included. Further, the type associated with the matching template is determined to be the detected type of fetal movement. The types of fetal movements are, for example, fetal movements that occur when the fetus is hiccuping, fetal movements that occur when the fetus is pushing (punching) the abdomen of the pregnant woman with their hands, and fetal movements that occur when the fetus is kicking the abdomen of the pregnant woman with their feet. There are fetal movements, fetal movements that occur when the fetus is rotating, and fetal movements that occur when the fetus is hiccuping. Further, in steps S12 to S13, the control unit 21 may, for example, perform an FFT (Fast Fourier Transform) or the like with respect to a detection signal from the fetal movement sensor 10 (a signal waveform of a pressure fluctuation indicating a time change of the pressure detected by the pressure sensor). A frequency conversion process may be performed to convert into a frequency component, and based on the frequency component, it may be determined whether or not a signal based on fetal movement is included and the type of fetal movement.

Next, the control unit 21 calculates the duration of the detected fetal movement based on the detection signal (detection signal of the pressure sensor) used when determining the type of fetal movement (S14). In step S14, the control unit 21 extracts a signal determined to be a signal based on fetal movement from the detection signal acquired from the fetal movement sensor 10, and calculates the duration of the extracted signal. The control unit 21 has acquired the detection signal from the fetal movement sensor 10 as well as date and time information indicating the detection date and time (acquisition date and time) of the detection signal. Therefore, the control unit 21 calculates the time from the detection date and time at the start timing of the signal determined to be the signal based on the fetal movement to the detection date and time at the end timing as the duration.

The control unit 21 issues a fetal movement ID, determines the issued fetal movement ID, the detection date and time at the start timing of the signal determined to be a signal based on the fetal movement, the duration calculated in step S14, and the determination in step S13. It is stored (accumulated) in the fetal movement history DB 22b as fetal movement information in association with the type of fetal movement (S15). The control unit 21 transmits the fetal movement information stored in the fetal movement history DB 22b from the communication unit 23 to the notification destination terminal 30 (S16), and ends the process. The control unit 21 repeats the processes of steps S12 to S16 each time the detection signal is acquired from the fetal movement sensor 10. As a result, it is determined whether or not the fetal movement has occurred based on the detection signal output from the fetal movement sensor 10, and if it does occur, the type of the fetal movement is determined, and the information regarding the determined fetal movement is transmitted to the pregnant woman terminal 20. It is accumulated and transmitted to the notification destination terminal 30.

In steps S12 to S13 during the process shown in FIG. 4, the control unit 21 determines whether or not the detection signal from the fetal movement sensor 10 includes a signal based on the fetal movement, and a process of determining the type of fetal movement. May be performed using, for example, a trained model which is a neural network constructed by machine learning processing. In this case, a learned model configured by inputting the detection signal from the fetal movement sensor 10 and outputting the presence / absence and type of fetal movement is stored in the storage unit 22 in advance, and this learned model is used to determine the presence / absence and type of fetal movement. Use a model. The trained model is, for example, a deep learning model learned by using a deep learning algorithm, and a recurrent neural network (RNN: Recurrent Neural Network) as shown in FIG. 5 can be used. FIG. 5 is a schematic diagram showing a configuration example of the trained model. The trained model uses, for example, the detection signals of the respective pressure sensors included in the fetal movement sensor 10 as inputs, and outputs the type of fetal movements and no fetal movements determined from the input detection signals.

The trained model shown in FIG. 5 is composed of an input layer, an intermediate layer, and an output layer. The input layer has m (m ≧ 2) input nodes, and a time-series signal waveform which is a detection signal by each pressure sensor of the fetal movement sensor 10 is input to each input node. That is, as many input nodes as the number of pressure sensors included in the fetal movement sensor 10 are provided. When the detection signal by the pressure sensor corresponding to each input node of the input layer is input, the input detection signal is input to the intermediate layer respectively. The intermediate layer has a plurality of fully connected layers, and the node of each layer calculates the output value based on the input data by using the weighting coefficient and the function of each layer, and the calculated output value is used as the node of the subsequent layer. Enter in. The intermediate layer finally gives each output value to each output node of the output layer by sequentially inputting the output value of the node of each layer to the node of the subsequent layer. The output layer has n (n ≧ 2) output nodes, and each output node outputs a discrimination probability (output information) for each of a preset type of fetal movement and no fetal movement. That is, only the number of types that can be discriminated by the trained model + 1 is provided as the output node. For example, the output node 1 outputs the discrimination probability for no fetal movement, and the output node 2 outputs the discrimination probability for no fetal movement. Output the discrimination probability. The discrimination probability output by each output node indicates that the type of fetal movement and no fetal movement associated with each output node may be appropriate for the input detection signal. The output value of each output node of the output layer is, for example, a value of 0 to 1.0, and the total of the discrimination probabilities output from the n output nodes is 1.0 (100%).

When the trained model is used, the control unit 21 inputs the detection signal (detection signal of each pressure sensor) acquired from the fetal movement sensor 10 to the input layer of the trained model, and the output value from the output layer of the trained model. To get. Then, the control unit 21 specifies, for example, the type of fetal movement or no fetal movement associated with the output node having the maximum output value from the trained model, and determines the presence / absence and type of fetal movement based on the specific result.

The trained model uses the detection signal detected by the fetal movement sensor 10 for each type of fetal movement and the teacher data including the information indicating each type (presence / absence information and type information), and the detection obtained by the fetal movement sensor 10. This model is trained to output the presence / absence and type of fetal movement when a signal (detection signal of each pressure sensor) is input. Further, the trained model may be subjected to learning processing using teacher data including a detection signal detected by the fetal movement sensor 10 in a state where fetal movement has not occurred and information (presence / absence information) indicating that fetal movement has not occurred. Good. Specifically, the trained model is trained using the teacher data in which the detection signal by the fetal movement sensor 10 and the information indicating the type of fetal movement or no fetal movement (correct answer label) are set as one set. In the trained model, when the detection signal included in the teacher data is input, the output value from the output node corresponding to the type of fetal movement indicated by the correct answer label included in the teacher data or no fetal movement approaches 1.0, and other factors. Learn so that the output value from the output node of is close to 0. The trained model optimizes data such as coefficients and thresholds of functions that define predetermined operations performed on input values. As a result, a learned model trained to output information on the presence / absence and type of fetal movement is obtained based on the detection signal by the fetal movement sensor 10.

The trained model may be downloaded and stored in the storage unit 22 after being trained by a learning device composed of a personal computer, a server computer, or the like, and may be read and stored from a portable storage medium that stores the trained model. It may be stored in the unit 22. The trained model performs a predetermined calculation on the input value and outputs the calculation result, and data such as the coefficient and the threshold of the function that defines this calculation is stored in the storage unit 22 as the trained model. Will be done.

Here, the learning process of the learning device and the learning model by the learning device will be described. FIG. 6 is a block diagram showing a configuration example of the learning device. The learning device 50 includes a control unit 51, a storage unit 52, a communication unit 53, an input unit 54, a display unit 55, a reading unit 56, and the like, and each of these units is connected to each other via a bus. Since each of the control unit 51, the storage unit 52, the communication unit 53, the input unit 54, the display unit 55, and the reading unit 56 is the same as each of the

terminals

20 and 30, the description thereof will be omitted. The storage unit 52 of the learning device 50 is a teacher for learning the learning model 52a before learning of the learned model, the learning program 52b for executing the learning process of the learning model 52a, and the learning model 52a as described above. The teacher data DB 52c in which the data is accumulated is stored. In the teacher data DB 52c, a detection signal by the fetal movement sensor 10 is stored in association with information (correct label) indicating each type of fetal movement and no fetal movement. The correct label may be the type of fetal movement determined by the pregnant woman's own senses, or may be the type of fetal movement determined by a specialist such as a doctor.

FIG. 7 is a flowchart showing an example of the procedure of the learning process by the learning device. The process shown in FIG. 7 is realized by the control unit 51 executing the control program 52P and the learning program 52b stored in the storage unit 52. When the learning program 52b is executed, the control unit 51 of the learning device 50 acquires one teacher data from the teacher data DB 52c (S21). The teacher data includes information indicating the type of fetal movement or no fetal movement (correct label) and a detection signal by the fetal movement sensor 10. The control unit 51 performs a learning process of the learning model 52a based on the acquired teacher data (S22). Specifically, when the control unit 51 inputs the detection signal included in the teacher data into the learning model 52a, the control unit 51 outputs from the output node corresponding to the type of fetal movement indicated by the correct answer label included in the teacher data or no fetal movement. The training model 52a is trained so that the value approaches 1.0 and the output values from the other output nodes approach 0.

The control unit 51 determines whether or not the processing based on all the teacher data stored in the teacher data DB 52c has been completed (S23), and if it is determined that the processing has not been completed (S23: NO), step S21. Return to processing. The control unit 51 acquires one unprocessed teacher data (S21), and performs learning processing based on the acquired teacher data (S22). When it is determined that the processing based on all the teacher data is completed (S23: YES), the control unit 51 ends the learning process of the learning model 52a. As a result, the learning model 52a can be trained so as to output information on the presence / absence and type of fetal movement based on the detection signal by the fetal movement sensor 10, and the learned learning model 52a can be obtained.

The trained model may use a convolutional neural network (CNN) in addition to the RNN, or may be configured by using another machine learning algorithm. For example, when the detection signal from the fetal movement sensor 10 (detection signal from the pressure sensor) is subjected to frequency conversion processing to be converted into a frequency component detection signal, and the presence / absence and type of fetal movement are determined based on the frequency component. , CNN can be used to construct a trained model in which the detection signal of the frequency component is input and the presence / absence and type of fetal movement are output. In addition, a plurality of trained models may be created for each number of weeks of pregnancy, such as the first trimester of pregnancy up to 15 weeks, the second trimester of 16 to 27 weeks of pregnancy, and the second trimester of pregnancy after 28 weeks of pregnancy. In this case, when determining the presence or absence and type of fetal movement using the trained model, one of a plurality of trained models is selected according to the number of weeks of pregnancy of the pregnant woman to be determined, and the selected trained model is used. Judgment processing is performed. In this case, a determination process using a trained model appropriately trained according to the number of weeks of gestation is possible, and the presence or absence and type of fetal movement can be determined more accurately.

Next, the processing performed by the notification destination terminal 30 will be described based on the flowchart. FIG. 8 is a flowchart showing an example of a processing procedure performed by the notification destination terminal 30. The process shown in FIG. 8 is realized by the control unit 31 executing the control program 32P and the fetal movement notification application 32a stored in the storage unit 32. In the present embodiment, the control unit 31 performs the following processing by executing the control program 32P and the fetal movement notification application 32a, but some of the processing may be realized by a dedicated hardware circuit.

The control unit (fetal movement information acquisition unit) 31 has determined whether or not the fetal movement information transmitted from the pregnant woman terminal 20 has been acquired by the communication unit 33 (S31), and has determined that the fetal movement information has not been acquired. In the case (S31: NO), it waits until it is acquired. When the control unit 31 determines that the fetal movement information from the pregnant woman terminal 20 has been acquired (S31: YES), the control unit 31 stores the acquired fetal movement information in the fetal movement history DB 32b (S32). The control unit 31 acquires fetal movement information including the fetal movement ID, the detection date and time of the fetal movement, the duration of the fetal movement, and the type of fetal movement from the pregnant woman terminal 20, and associates each information included in the acquired fetal movement information with the fetal movement. It is stored in the history DB 32b. As a result, the fetal movement information regarding the fetal movement determined by the pregnant woman terminal 20 based on the detection signal from the fetal movement sensor 10 is stored (accumulated) in the fetal movement history DB 32b of the notification destination terminal 30.

The control unit (specific unit) 31 identifies the type of fetal movement from the fetal movement information stored in the fetal movement history DB 32b (S33). In the present embodiment, since the type of fetal movement is transmitted from the terminal 20 for pregnant women, the control unit 31 identifies the type of fetal movement by reading out the type of fetal movement stored in the fetal movement history DB 32b. Next, the control unit 31 determines the processing according to the specified type of fetal movement (S34). In the present embodiment, the type of fetal movement and the processing corresponding to each type are registered in the processing DB 32c in association with each other, and in step S34, the control unit 31 performs the processing corresponding to the specified type of fetal movement in the processing DB 32c. Determined based on.

The control unit 31 executes the determined process (S35). For example, when the determined process is the vibration process of the first pattern (pattern 1) by the vibrator, the control unit 31 notifies (controls) the execution of the vibration process of the first pattern by the vibrator. Output to. When the determined process is the blinking process of the first pattern by the lamp, the control unit 31 outputs a control signal instructing (controlling) the execution of the blinking process of the first pattern by the lamp to the notification unit 36. When the determined process is the ringing process of the first pattern by the buzzer, the control unit 31 outputs a control signal instructing (controlling) the execution of the ringing process of the first pattern by the buzzer to the notification unit 36. When the determined process is the voice output process of the first message by the speaker, the control unit 31 outputs a control signal instructing (controlling) the execution of the voice output process of the first message by the speaker to the notification unit 36. To do. When the determined process is the display process of the first image by the display unit 35, the control unit 31 notifies (controls) the execution of the display process of the first image by the display unit 35. Output to. In the case of image display processing by the display unit 35, the control unit 31 may directly output the control signal to the display unit 35 and instruct the display unit 35 to display the image.

The control unit 31 repeats the processes of steps S32 to S35 each time the fetal movement information is acquired from the pregnant woman terminal 20. As a result, the notification destination terminal 30 can perform notification processing according to the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20, and the user of the notification destination terminal 30 can perform the executed notification processing. Not only the fetal movement has occurred, but also the type of fetal movement that has occurred can be grasped.

In the present embodiment, the user of the notification destination terminal 30 can be notified of the type of fetal movement determined based on the detection signal detected by the fetal movement sensor 10 attached to the abdomen of the pregnant woman. Therefore, it is possible to grasp the occurrence of fetal movement and the type of fetal movement that has occurred in the family such as the husband and partner of the pregnant woman, and to share the occurrence of fetal movement and the type of fetal movement that has occurred between the pregnant woman and the family. Further, since the type of fetal movement can be notified to the user of the notification destination terminal 30 at the timing when the pregnant woman feels the fetal movement, the shared feeling of the fetal movement is increased, and it is expected that the communication between the pregnant woman and the family is increased.

In the fetal movement notification system of the present embodiment, the fetal movement information determined based on the detection signal from the fetal movement sensor 10 is stored in the storage unit 22 (fetal movement history DB 22b) of the pregnant woman terminal 20 and the storage unit 32 (fetal movement) of the notification destination terminal 30. The configuration is not limited to the configuration stored in the history DB 32b). For example, the fetal

movement history DBs

22b and 32b may be stored in an external storage device such as a cloud storage server and shared between the pregnant woman terminal 20 and the notification destination terminal 30. By storing the history of fetal movement information determined based on the detection signal from the fetal movement sensor 10 in the pregnant woman terminal 20, the notification destination terminal 30, or an external storage device, not only the timing when the pregnant woman feels fetal movement but also the timing Notification processing according to the type of fetal movement can be reproduced based on each fetal movement information at an arbitrary timing. For example, the control unit 31 of the notification destination terminal 30 receives the designation of an arbitrary date and time (detection date and time of fetal movement) via the input unit 34, reads the type of fetal movement corresponding to the specified date and time from the fetal movement history DB 32b, and reads it out. A control signal instructing the execution of the notification process according to the type of fetal movement is output to the notification unit 36. As a result, for example, the user of the notification destination terminal 30 can cause the notification destination terminal 30 to execute the notification processing according to the type of fetal movement that has occurred in the past at an arbitrary timing, and can feel the movement of the fetus closely. .. Further, in the fetal

movement history DBs

22b and 32b shown in FIG. 3A, a pregnancy week number sequence for storing the number of pregnancy weeks at the time when the fetal movement sensor 10 detects the fetal movement may be provided in association with the fetal movement ID. In this case, when reproducing the notification process according to the type of fetal movement based on the fetal movement information accumulated in the fetal movement history DB 32b, it is possible to reproduce each period such as early pregnancy, middle pregnancy, and late pregnancy.

The fetal movement notification system of the present embodiment is not limited to the configuration in which the pregnant woman terminal 20 performs a process of determining the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10. For example, a server may be provided instead of the pregnant woman terminal 20, and the server may perform a process of determining the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10. In this case, the fetal movement sensor 10 is provided with an interface for connecting to the network N, and transmits a detection signal (detection signal) output from each pressure sensor to the server via the network N. Then, the server receives the detection signal output from the fetal movement sensor 10 via the network N, and performs the same processing as the processing performed by the pregnant woman terminal 20 of the present embodiment, and based on the received detection signal, the presence or absence of fetal movement and Determine the type. The server may be a server computer, a personal computer, or the like, and a plurality of servers may be provided. Further, the server may be realized by a plurality of virtual machines provided in one server, or may be realized by using a cloud server. In the configuration in which the detection signal from the fetal movement sensor 10 is transmitted to the server via the network N in this way, the detection signal output from the fetal movement sensor 10 may be transmitted to the server via the pregnant woman terminal 20. .. In this case, the pregnant woman terminal 20 acquires the detection signal from the fetal movement sensor 10 and transmits the acquired detection signal to the server via the network N. Then, the server receives the detection signal from the fetal movement sensor 10 from the pregnant woman terminal 20, and determines the presence / absence and type of fetal movement based on the received detection signal. Even in these configurations, the same effect as that of the present embodiment can be obtained.

Further, the fetal movement sensor 10 may perform the processing performed by the pregnant woman terminal 20 of the present embodiment. In this case, when the detection signals are output from the plurality of pressure sensors, the fetal movement sensor 10 performs the same processing as the processing performed by the pregnant woman terminal 20 of the present embodiment, and the fetal movement sensor 10 is based on the output detection signals. Determine the presence / absence and type. Then, the fetal movement sensor 10 transmits the fetal movement information regarding the determined fetal movement to the notification destination terminal 30 via the network N. In this case, the notification destination terminal 30 performs notification processing according to the type of fetal movement based on the fetal movement information received from the fetal movement sensor 10, so that the user of the notification destination terminal 30 has a fetal movement and the fetal movement that has occurred. You can notify the type.

Further, the notification destination terminal 30 may perform the processing performed by the pregnant woman terminal 20 of the present embodiment. In this case, the fetal movement sensor 10 transmits the detection signal (detection signal) output from each pressure sensor to the notification destination terminal 30 via the network N. The notification destination terminal 30 receives the detection signal output from the fetal movement sensor 10 via the network N, and performs the same processing as the processing performed by the pregnant woman terminal 20 of the present embodiment, and the fetal movement is based on the received detection signal. Determine the presence / absence and type. Then, the notification destination terminal 30 notifies the user of the notification destination terminal 30 that the fetal movement has occurred and the type of the fetal movement that has occurred by performing the notification processing according to the determined type of fetal movement. In the case of the above configuration, the fetal movement sensor 10 includes an interface for connecting to the network N. When the notification destination terminal 30 performs the processing performed by the pregnant woman terminal 20 of the present embodiment, the fetal

movement history DBs

22b and 32b store the detection signal output from the fetal movement sensor 10 instead of the type of fetal movement. It may be configured to be used. In this case, the control unit 31 of the notification destination terminal 30 can read the detection signal stored in the fetal movement history DB 32b, and can determine the presence / absence and type of fetal movement based on the read detection signal. Further, the control unit 31 receives the designation of an arbitrary date and time (detection date and time of fetal movement) via the input unit 34, reads out the detection signal stored in the fetal movement history DB 32b in association with the designated date and time, and detects the read out. The presence / absence and type of fetal movement are determined based on the signal, and a control signal instructing execution of notification processing according to the determined type of fetal movement is output to the notification unit 36. Even in such a configuration, the user of the notification destination terminal 30 can cause the notification destination terminal 30 to execute the notification processing according to the type of fetal movement that has occurred in the past at an arbitrary timing.

In the fetal movement notification system of the present embodiment, the notification destination terminal 30 can communicate with the own terminal 30 in addition to the configuration in which the notification unit 36 (processing unit in the own terminal 30) of the own terminal 30 performs the notification processing. The notification processing terminal may be configured to perform notification processing. The notification processing terminal can be configured by using, for example, a wearable device worn by the user of the notification destination terminal 30, a terminal such as a key chain type that can be carried by the user, a smart speaker, or the like. The notification processing terminal can execute at least one of notification processing such as vibration by a vibrator, lighting or blinking of a lamp, sounding of a buzzer, voice output of a message by a speaker, and display of an image by a display unit. It is configured. When vibration is used, it is possible to strengthen the shared feeling between the pregnant woman and the partner by generating a movement close to the fetal movement. At that time, it is possible to improve the reproducibility of fetal movement by using not only a vibrator but also an actuator, a motor, or the like. For example, in the case of a portable terminal, the fetal movement can be reproduced for each type by incorporating a vibrator, an actuator, a motor, etc. and expanding and contracting the surface of the terminal. Furthermore, by making it a key chain type, it can be miniaturized and easily carried. Therefore, in this case, the processing information registered in the processing DB 32c includes not only the notification processing by the notification unit 36 but also the notification processing by the notification processing terminal. The control unit 31 of the notification destination terminal 30 determines the processing according to the type of fetal movement received from the pregnant woman terminal 20 based on the processing DB 32c, and if the determined processing is the notification processing by the notification processing terminal, it is determined. Outputs a control signal that instructs (controls) the execution of notification processing to the notification processing terminal. The notification processing terminal has a function of an execution unit that executes processing according to the type of fetal movement by performing processing (notification processing) according to a control signal received from the notification destination terminal 30. As a result, it is possible to notify the occurrence of fetal movement and the type of fetal movement caused by the notification processing in the notification processing terminal other than the notification destination terminal 30.

Further, for each type of fetal movement, both the notification processing by the notification unit 36 of the notification destination terminal 30 and the notification processing by the notification processing terminal may be associated and registered in the processing DB 32c. Then, the control unit 31 of the notification destination terminal 30 receives a switching instruction of the terminal (notification unit 36 or the notification processing terminal) to be notified from the user via, for example, the input unit 34, and the terminal corresponding to the received switching instruction. May execute the notification process. Specifically, the control unit 31 has a process of outputting a control signal for instructing (controlling) execution of the notification process to the notification unit 36 in the notification destination terminal 30 and a process of outputting the control signal to the notification processing terminal. The switching instruction is received, and the control signal is transmitted to the notification unit 36 or the notification processing terminal according to the received switching instruction. In this case, even when the same type of fetal movement occurs, the notification processing by the notification unit 36 and the notification processing by the notification processing terminal can be switched according to the switching instruction from the user, improving the convenience of the user. Can be made to.

(Embodiment 2)
A fetal movement notification system that performs notification processing according to the type of detected fetal movement and displays fetal image data (echo image) taken by an ultrasonic examination or the like on a day close to the detection date of the fetal movement will be described. Since the fetal movement notification system of the present embodiment is realized by the

same devices

10, 20, and 30 as the fetal movement notification system of the first embodiment, the description of the same configuration will be omitted. In the present embodiment, the storage unit 22 of the pregnant woman terminal 20 stores the image DB 22c described later, and the fetal movement history DB 32b stored by the storage unit 32 of the notification destination terminal 30 is slightly different from the first embodiment.

FIG. 9A is a schematic diagram showing a configuration example of DB 22c stored in the pregnant woman terminal 20, and FIG. 9B is a schematic diagram showing a configuration example of DB 32b stored in the notification destination terminal 30. FIG. 9A shows the image DB 22c, and FIG. 9B shows the fetal movement history DB 32b. The image DB 22c stores, for example, information about an image input (registered) via the input unit 24 on the image registration screen by the fetal movement notification application 22a. The image DB 22c shown in FIG. 9A includes an image ID string, a shooting date sequence, an image data string, and the like. The image ID column stores the identification information assigned to each registered image. The shooting date sequence stores the day when each image was shot in association with the image ID. Note that the shooting date sequence may store the shooting date and time including not only the shooting date of the image but also the shooting time. The image data string stores image data of the fetus taken by, for example, an ultrasonic examination in a hospital, in association with the image ID. In addition to being stored in the image DB 22c, the image data may be stored in a predetermined area of the storage unit 22 or an external storage device connected to the pregnant woman terminal 20. In this case, the image data string stores information for reading the image data (for example, a file name indicating a storage location of the image data). Each piece of information stored in the image DB 22c is stored by the control unit 21 when the control unit 21 of the pregnant woman terminal 20 acquires image data via, for example, the input unit 24. The image ID is issued and stored by the control unit 21, and the shooting date assigned to the image data is extracted and stored by the control unit 21. When the pregnant woman terminal 20 of the present embodiment transmits the information on the fetal movement stored in the fetal movement history DB 22b to the notification destination terminal 30, the image data of the shooting date close to the detection date and time of the fetal movement is read from the image DB 22c and together with the fetal movement information. It is transmitted to the notification destination terminal 30.

The fetal movement history DB 32b stored in the notification destination terminal 30 of the present embodiment shown in FIG. 9B has the same configuration as the fetal movement history DB 32b of the first embodiment shown in FIG. 3A, and further includes an image data string. The image data string stores the image data of the fetus acquired from the pregnant woman terminal 20 in association with the fetal movement ID. In addition to being stored in the fetal movement history DB 32b, the image data may be stored in a predetermined area of the storage unit 32 or an external storage device connected to the notification destination terminal 30. In this case, the image data string stores information for reading the image data (for example, a file name indicating a storage location of the image data). The image data stored in the fetal movement history DB 32b is stored by the control unit 31 when the control unit 31 receives the fetal movement information from the pregnant woman terminal 20.

FIG. 10 is a flowchart showing an example of a processing procedure performed by the pregnant woman terminal 20 of the second embodiment. The process shown in FIG. 10 is obtained by adding steps S41 and S42 between steps S15 and S16 during the process shown in FIG. The control unit 21 of the pregnant woman terminal 20 of the present embodiment performs the same processing as in steps S11 to S15 shown in FIG. 4, and image data on the same shooting date as the detected fetal movement is stored in the image DB 22c. Whether or not it is determined (S41). When it is determined that the image data on the same shooting date as the detection date is stored (S41: YES), the control unit 21 reads this image data from the image DB 22c (S42) and notifies the fetal movement information together with the read image data. It is transmitted to the destination terminal 30 (S16). On the other hand, when it is determined that the image data of the shooting date same as the detection date of the fetal movement is not stored (S41: NO), the control unit 21 skips the process of step S42 and sends only the fetal movement information to the notification destination terminal 30. Transmit (S16). As a result, if there is not only information on the detected fetal movement but also image data on the same shooting date as the detection date of the fetal movement, this image data can also be transmitted to the notification destination terminal 30. The image data transmitted by the pregnant woman terminal 20 to the notification destination terminal 30 is not limited to the image data taken on the same day as the fetal movement detection date, for example, within one week before and after the fetal movement detection date. It may be image data taken on a day close to the detection date of fetal movement.

FIG. 11 is a flowchart showing an example of a processing procedure performed by the notification destination terminal 30 of the second embodiment. The process shown in FIG. 11 is obtained by adding steps S43 and S44 after step S35 during the process shown in FIG. The control unit 31 of the notification destination terminal 30 of the present embodiment performs the same processing as in steps S31 to S35 shown in FIG. 8, stores the fetal movement information and image data received from the pregnant woman terminal 20 in the fetal movement history DB 32b, and at the same time, stores the fetal movement information and the image data in the fetal movement history DB 32b. Notification processing (vibration by vibrator, etc.) is performed according to the type of fetal movement. The control unit 31 determines whether or not the image data is received from the pregnant woman terminal 20 together with the fetal movement information (S43), and if it is determined that the image data is received (S43: YES), the image received and stored in the fetal movement history DB 32b. The data is read out, and the read image data is displayed on the display unit 35 (S44).

FIG. 12 is a schematic diagram showing a display example of an image of a fetus. The display screen shown in FIG. 12 displays the number of weeks of gestation and the type of fetal movement, and further displays an echo image based on the image data of the fetus taken by the ultrasonic examination in the hospital. As the echo image, for example, a 2D echo image of a flat image, a 3D echo image of a stereoscopic still image, a 4D echo image of a stereoscopic moving image, or the like can be used. As a result, when the fetal movement information acquired from the pregnant woman terminal 20 includes image data, the image was taken on the day when the fetal movement was detected or on a day close to the day when the fetal movement was detected, together with the notification processing according to the type of the fetal movement. It is possible to display the image of the fetus based on the image data. Therefore, the user of the notification destination terminal 30 can better recognize the existence of the fetus.

On the other hand, when it is determined that the image data is not received together with the fetal movement information (S43: NO), the control unit 31 skips the process of step S44 and ends the process. As a result, when the image data is not included in the fetal movement information acquired from the pregnant woman terminal 20, only the notification processing according to the type of fetal movement can be performed. In addition to the fetal photograph (echo image), for example, an image according to the number of weeks of pregnancy, an image according to the type of fetal movement, and the like may be displayed on the display unit 35. In this case, an image according to the number of weeks of pregnancy, an image according to the type of fetal movement, and the like are stored in advance in the storage unit 32, and the control unit 31 performs notification processing according to the type of fetal movement, and such Performs image display processing. With such a configuration, even if there is no image data of the fetus taken on the detection date of the fetal movement or a day close to the detection date, an image that can image the fetus or the fetal movement is displayed. It can be expected that the shared feeling of fetal movement will increase. Further, by performing notification processing (vibration by a vibrator, etc.) according to the type of fetal movement in addition to displaying an image that allows the image of the fetus or fetal movement, the user of the notification destination terminal 30 can use the number of weeks of pregnancy and the type of fetal movement. Can be more conscious and can more recognize the existence of the fetus.

Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, the user of the notification destination terminal 30 can be notified of the occurrence of the fetal movement and the type of the fetal movement that has occurred, and the ultrasonic examination taken on a day close to the day (detection date) in which the fetal movement has occurred. Image data can be displayed. Therefore, the user of the notification destination terminal 30 can know not only the type of fetal movement but also the state of the fetus from the image data obtained by the ultrasonic examination.

(Embodiment 3)
A fetal movement notification system that extracts a detection signal based on true fetal movement from a detection signal output from the fetal movement sensor 10 and determines the type of fetal movement based on the detection signal based on true fetal movement will be described. The fetal movement notification system of the present embodiment includes

devices

10, 20, and 30 similar to the fetal movement notification system of the first embodiment, and further includes an acceleration sensor for detecting the movement of the pregnant woman. The description of the same configuration as that of the first embodiment will be omitted. The acceleration sensor may be provided in, for example, the fetal movement sensor 10, and the fetal movement sensor 10 may be configured to transmit the detection signal by the acceleration sensor to the pregnant woman terminal 20 together with the detection signals from the plurality of pressure sensors. Further, for example, the acceleration sensor may be mounted on the pregnant woman terminal 20, and the pregnant woman may carry the pregnant woman terminal 20 to detect the movement of the pregnant woman by the acceleration sensor of the pregnant woman terminal 20. An acceleration sensor used in a pedometer or the like provided in the pregnant woman terminal 20 may be used.

In the fetal movement notification system of the present embodiment, the pregnant woman terminal 20 performs the same processing as the processing shown in FIG. In step S11 during the process shown in FIG. 4, the control unit 21 determines whether or not the detection signal from the fetal movement sensor 10 including the detection signal from the acceleration sensor has been acquired. When the acceleration sensor is not provided in the fetal movement sensor 10, the control unit 21 acquires the detection signal from the acceleration sensor separately from the detection signal from the fetal movement sensor 10. Further, in step S12 in FIG. 4, when the control unit 21 determines the presence / absence and type of fetal movement based on the detection signal from the fetal movement sensor 10, the control unit 21 detects from the fetal movement sensor 10 based on the detection signal from the acceleration sensor. A signal based on true fetal movement (detection signal) is extracted from the signal. Then, the control unit 21 determines the presence / absence and type of fetal movement based on the extracted detection signal. For example, the control unit 21 determines whether or not the pregnant woman is moving based on the detection signal from the acceleration sensor, and the detection signal detected by the fetal movement sensor 10 during the period when it is determined that the pregnant woman is not moving is a signal based on the true fetal movement. Extract as. When the pregnant woman is moving, the detection signal from the fetal movement sensor 10 is likely to include a signal based on the movement of the pregnant woman. Therefore, the detection signal detected by the fetal movement sensor 10 during the period when it is determined that the pregnant woman is moving. Is not a signal based on true fetal movement, and is not used for determining the presence or absence of fetal movement and its type. The process of determining the presence / absence and type of fetal movement based on the detection signal from the fetal movement sensor 10 is the same as that of the first embodiment.

Further, in steps S12 to S13 during the process shown in FIG. 4, the control unit 21 uses the trained model as shown in FIG. 5 to perform fetal movement based on the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor. The presence / absence and type may be determined. In this case, a learned model in which the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor are input and the presence / absence and type of fetal movement are output is stored in the storage unit 22. In the trained model of the present embodiment, the detection signal by the corresponding pressure sensor and the detection signal by the acceleration sensor are input to each input node of the input layer, and each output node of the output layer is preset. The discrimination probability for each type of fetal movement and no fetal movement is output. That is, in the trained model of the present embodiment, the number of input nodes of the input layer is +1 (for inputting the detection signal from the acceleration sensor) of the pressure sensors included in the fetal movement sensor 10. When the trained model is used, the control unit 21 inputs the detection signal from the fetal movement sensor 10 (detection signal of each pressure sensor) and the detection signal from the acceleration sensor to the input layer of the trained model, and the trained model Get the output value from the output layer. Then, the control unit 21 specifies, for example, the type of fetal movement or no fetal movement associated with the output node having the maximum output value, and determines the presence / absence and type of fetal movement based on the specific result.

The trained model of the present embodiment uses the detection signal detected by the fetal movement sensor 10 for each type of fetal movement, the detection signal detected by the acceleration sensor, and the teacher data including information indicating each type, and uses the fetal movement sensor 10 When the detection signal from and the detection signal from the acceleration sensor are input, it is learned to output the presence / absence and type of fetal movement. Specifically, the trained model is trained using teacher data in which a detection signal by the fetal movement sensor 10, a detection signal by the acceleration sensor, and information (correct answer label) indicating the type of fetal movement or no fetal movement are set as one set. To do. The correct label here may also be the type of fetal movement determined by the pregnant woman's own senses, or may be the type of fetal movement determined by a specialist such as a doctor. In the trained model, when the detection signals by the fetal movement sensor 10 and the acceleration sensor included in the teacher data are input, the output value from the output node corresponding to the type of fetal movement indicated by the correct answer label included in the teacher data or no fetal movement is obtained. Learn so that it approaches 1.0 and the output values from other output nodes approach 0. As a result, a trained model trained to output information on the presence / absence and type of fetal movement is obtained based on the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor. Also in this embodiment, the learning device for learning the learning model and the learning process by the learning device are the same as those in the first embodiment, and thus the description thereof will be omitted.

In the fetal movement notification system of the present embodiment, the notification destination terminal 30 performs the same processing as the processing shown in FIG. As a result, also in the present embodiment, the notification destination terminal 30 can perform notification processing according to the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20. Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, among the detection signals detected by the fetal movement sensor 10, a signal that is not a signal based on true fetal movement, such as a signal based on the movement of a pregnant woman, is removed, and the fetal movement is based on the detection signal based on true fetal movement. By determining the presence / absence and type of fetal movement, the presence / absence and type of fetal movement can be determined more accurately. Further, the configuration of the present embodiment can be applied to the fetal movement notification system of the second embodiment, and the same effect can be obtained when applied to the fetal movement notification system of the second embodiment.

(Embodiment 4)
A fetal movement notification system that reproduces the fetal movement detected by the fetal movement sensor 10 will be described. The fetal movement notification system of the present embodiment includes

devices

10, 20, and 30 similar to the fetal movement notification system of the first embodiment, and can be attached to the abdomen of a person to apply a force to an appropriate position of the abdomen of the person. The pressurizing tool (pressurizing device) 40 is included. The description of the same configuration as that of the first embodiment will be omitted. FIG. 13 is a schematic view showing a configuration example of the pressurizing tool 40. The pressurizing tool 40 is provided in the same band as the pregnant woman's band 10a, and is configured so that the pressurizing tool 40 can pressurize the abdomen when a non-pregnant woman wears the band on the abdomen. The pressurizing tool 40 has a plurality of devices configured to pressurize the abdomen of the wearer by, for example, filling with air, and the plurality of devices include, for example, a plurality of pressures provided in the fetal movement sensor 10. They are arranged in the same arrangement as the sensors. The pressurizing tool 40 has an interface for communicating with, for example, the notification destination terminal 30. Further, the pressurizing tool 40 may be configured in a sheet shape to be attached to the abdomen of a person, similarly to the fetal movement sensor 10.

In the fetal movement notification system of the present embodiment, the pregnant woman terminal 20 performs the same processing as the processing shown in FIG. 4, and the notification destination terminal 30 performs the same processing as the processing shown in FIG. As a result, also in the present embodiment, the notification destination terminal 30 can perform notification processing according to the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20. Further, in the present embodiment, the pregnant woman terminal 20 transmits the detection signal from each pressure sensor included in the fetal movement sensor 10 as it is to the notification destination terminal 30 via the network N. Then, the notification destination terminal 30 of the present embodiment is attached to each device of the pressurizing tool 40 provided at a position corresponding to each pressure sensor based on the detection signal from each pressure sensor received from the pregnant woman terminal 20. On the other hand, a control signal for instructing (controlling) the execution of the pressurizing process based on the detection signal is output. As a result, each device of the pressurizing tool 40 can be made to perform the pressurizing process based on the detection signal by the fetal movement sensor 10. The control unit 31 of the notification destination terminal 30 determines the strength of the pressurization process to be executed by each device of the pressurizing tool 40 corresponding to each pressure sensor according to the strength of the fetal movement based on the detection signal from each pressure sensor. Control. That is, the control unit 31 controls the pressurization process by each device of the pressurizing tool 40 so that the stronger the pressure from the inside of the abdomen of the pregnant woman detected by each pressure sensor, the stronger the pressurizing process. Each device of the pressurizing tool 40 receives a control signal output from the notification destination terminal 30 and performs a pressurizing process based on the received control signal to perform a motion similar to the fetal movement detected by the fetal movement sensor 10. It can be reproduced by the pressurizing tool 40.

The arrangement position of each device of the pressurizing tool 40 and the arrangement position of each pressure sensor of the fetal movement sensor 10 do not have to correspond to each other. For example, when the fetal movement sensor 10 is attached to the abdomen of a pregnant woman, position information indicating the position of each pressure sensor on the abdomen of the pregnant woman is registered in advance. Then, the notification destination terminal 30 determines which pressure sensor the detection signal received from the pregnant woman terminal 20 is from, and determines the position indicated by the position information corresponding to the determined pressure sensor by fetal movement. Identify the position where the force is applied to the belly. Then, the notification destination terminal 30 instructs (controls) the execution of the pressurizing process based on the received detection signal to each device of the pressurizing tool 40 provided at the position corresponding to the specified position. Output. As a result, in the abdomen of the user wearing the pressurizing tool 40, a movement similar to the fetal movement can be reproduced at a position corresponding to the position where the force is applied to the abdomen of the pregnant woman by the fetal movement.

Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, the movement similar to the fetal movement detected by the fetal movement sensor 10 can be reproduced by the pressurizing tool 40 attached to the abdomen of a person other than the pregnant woman. Therefore, a man or a woman who has no experience of being pregnant can experience the fetal movement in a simulated manner by using the pressurizing tool 40, and can be used for education of medical workers and the like. Further, the configuration of the present embodiment can be applied to the fetal movement notification system of the second and third embodiments, and the same effect can be obtained when applied to the fetal movement notification system of the second and third embodiments.

(Embodiment 5)
Among the fetal movements detected based on the detection signal by the fetal movement sensor 10, the fetal movement notification system capable of limiting the fetal movements notified to the notification destination terminal 30 will be described. Specifically, a fetal movement notification system for notifying the notification destination terminal 30 of only the fetal movement felt by the pregnant woman will be described. The fetal movement notification system of the present embodiment has the same configuration as the fetal movement notification system of the third embodiment. That is, the fetal movement notification system of the present embodiment includes the

devices

10, 20, and 30 of the first embodiment and an acceleration sensor that detects the movement of the pregnant woman. The description of the same configuration as in the first and third embodiments will be omitted.

FIG. 14 is a flowchart showing an example of a processing procedure performed by the pregnant woman terminal 20 of the fifth embodiment. The process shown in FIG. 14 is obtained by adding step S51 between steps S15 and S16 during the process shown in FIG. The control unit 21 of the pregnant woman terminal 20 of the present embodiment performs the same processing as steps S11 to S15 shown in FIG. 4, and determines the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10. Then, the determined information on the fetal movement is stored in the fetal movement history DB 22b. In the pregnant woman terminal 20 of the present embodiment, the control unit 21 acquires the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor. Further, in steps S12 and S13, the control unit 21 of the present embodiment determines the presence / absence and type of fetal movement based only on the detection signal from the fetal movement sensor 10. The control unit 21 may determine the presence / absence and type of fetal movement based on the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor.

The control unit 21 determines whether or not the fetal movement related to the fetal movement information stored in the fetal movement history DB 22b is the fetal movement (notification target) to be notified to the notification destination terminal 30 (S51). In step S51, the control unit 21 identifies the acceleration and moving speed of the pregnant woman (pregnant woman terminal 20) based on, for example, a detection signal from the acceleration sensor, and whether or not the specified acceleration or moving speed is within a predetermined reference. To judge. For example, when the pregnant woman is exercising or moving by a car or the like, the minimum value of the acceleration or the moving speed is set as a predetermined threshold value, and the predetermined threshold value or more is stored in the storage unit 22 as a predetermined reference. Then, the control unit 21 determines whether or not the acceleration or movement speed of the pregnant woman is equal to or higher than the predetermined threshold value based on the detection signal from the acceleration sensor, and if it is equal to or higher than the predetermined threshold value, the fetal movement detected here is determined. It is judged that the pregnancy is not subject to notification because it is highly likely that the fetal movement is not felt by the pregnant woman. On the other hand, if the acceleration or movement speed of the pregnant woman is less than a predetermined threshold value, it is determined that the fetal movement detected here is likely to be the fetal movement felt by the pregnant woman and is subject to notification. Further, for example, when the fetal movement is detected, the control unit 21 displays a message indicating that the fetal movement has been detected on the display unit 25 to notify the pregnant woman, and the pregnant woman notifies the pregnant woman via the input unit 24 to the notification destination terminal 30. It may be configured to accept instructions as to whether or not to notify. In this configuration, when the control unit 21 receives an instruction to notify the notification destination terminal 30, it determines that the fetal movement detected here is the notification target, and should not notify the notification destination terminal 30. When the instruction of is received, it is judged that the fetal movement detected here is not the notification target.

When the control unit 21 determines that the fetal movement related to the fetal movement information stored in the fetal movement history DB 22b is the fetal movement to be notified to the notification destination terminal 30 (S51: YES), the control unit 21 communicates the fetal movement information stored in the fetal movement history DB 22b. It is transmitted from the unit 23 to the notification destination terminal 30 (S16). On the other hand, when the control unit 21 determines that the fetal movement related to the fetal movement information stored in the fetal movement history DB 22b is not the fetal movement to be notified to the notification destination terminal 30 (S51: NO), the process of step S16 is skipped and processed. To finish. By the above-mentioned processing, in the present embodiment, even if the fetal movement is detected based on the detection signal by the fetal movement sensor 10, it is determined that the fetal movement that the pregnant woman is likely to feel or that the pregnant woman should be notified. Only the fetal movement can be notified to the notification destination terminal 30. Therefore, fetal movements that are likely not felt by the pregnant woman and fetal movements that the pregnant woman determines should not be notified are not notified to the notification destination terminal 30, so that the number of fetal movements to be notified (shared) can be limited, and notification of fetal movements can be made. It is possible to avoid inadvertently increasing the number of times.

In the fetal movement notification system of the present embodiment, the notification destination terminal 30 performs the same processing as the processing shown in FIG. As a result, also in the present embodiment, the notification destination terminal 30 can perform notification processing according to the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20. Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, even when the fetal movement is detected based on the detection signal from the fetal movement sensor 10, it is possible to switch whether or not to notify the notification destination terminal 30. Therefore, by notifying the fetal movement information to be notified to the notification destination terminal 30 and not notifying the fetal movement information that does not need to be notified, it is possible to avoid an increase in the number of executions of the notification process performed on the notification destination terminal 30. The configuration of the present embodiment can be applied to the fetal movement notification system of the second embodiment, and the same effect can be obtained when applied to the fetal movement notification system of the second embodiment. Further, in the configuration of the present embodiment, it is possible to apply the modification described in each of the above-described embodiments.

The pregnant woman terminal 20 of the present embodiment stores all the fetal movement information detected based on the detection signal from the fetal movement sensor 10 in the fetal movement history DB 22b. Therefore, a server may be provided on the network N, and the fetal movement information collected by each pregnant woman terminal 20 may be transmitted to the server and stored. With such a configuration, the server can collect fetal movement information detected from a large number of pregnant women, and it is conceivable that such fetal movement information will be used by, for example, medical personnel, researchers, and the like. .. Therefore, it is possible to configure a system in which only the necessary fetal movement information is notified to the notification destination terminal 30 and all the fetal movement information is transmitted to the server.

In the present embodiment, in a configuration in which the pregnant woman terminal 20 receives an instruction from the pregnant woman via the input unit 24 as to whether or not each fetal movement information should be notified, a plurality of times received from the pregnant woman via the input unit 24. Based on the instructions, a criterion for determining whether or not to be notified may be generated thereafter. FIG. 15 is a flowchart showing another example of the processing procedure performed by the pregnant woman terminal 20 of the fifth embodiment. In the process shown in FIG. 15, steps S61 and S62 are added between steps S15 and S16 during the process shown in FIG. 4, and steps S63 to S65 are added after step S16.

The control unit 21 of the terminal 20 for pregnant women determines the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10 by performing the same processing as in steps S11 to S15 shown in FIG. Information on fetal movement is stored in the fetal movement history DB 22b. The control unit 21 acquires the detection signal from the fetal movement sensor 10 and the detection signal from the acceleration sensor. The control unit 21 generates a notification screen for notifying that fetal movement has occurred (fetal movement has been detected) and displays it on the display unit 25 (S61). The fetal movement notification screen displays a message indicating that the fetal movement has been detected, and an OK button and a cancel button for instructing whether or not the fetal movement should be notified to the notification destination terminal 30. The control unit 21 determines whether or not this fetal movement should be notified, depending on whether the OK button is operated or the cancel button is operated via the input unit 24 (S62).

When the control unit 21 determines that the fetal movement related to the fetal movement information stored in the fetal movement history DB 22b should be notified (S62: YES), the control unit 21 notifies the fetal movement information stored in the fetal movement history DB 22b from the communication unit 23. It is transmitted to the terminal 30 (S16). Then, the control unit 21 stores the detection signal acquired from the fetal movement sensor 10 and the detection signal acquired from the acceleration sensor in the storage unit 22 (S63), and stores a predetermined number of detection signals in the storage unit 22. It is determined whether or not the memory is stored (S64). When it is determined that a predetermined number of detection signals have been stored (S64: YES), the control unit 21 determines whether or not the detected fetal movement should be notified based on the stored predetermined number of detection signals. A determination criterion is generated and stored in the storage unit 22 (S65). In step S65, the control unit 21 uses the average value and the minimum value of the detection signals from the fetal movement sensor 10 and the acceleration sensor when receiving the instruction to be notified from the pregnant woman, and uses the fetal movement sensor 10 and the acceleration in the subsequent processing. Based on the detection signal from the sensor, a criterion for determining whether or not the detected fetal movement should be notified is generated. As a result, a judgment standard according to each pregnant woman is set based on the degree of the detection signal from the fetal movement sensor 10 and the acceleration sensor when the pregnant woman gives an instruction to the notification target in the past. Therefore, by determining whether or not the detected fetal movement should be notified by using such a judgment criterion, it is not necessary for the pregnant woman to instruct whether or not to be notified in the subsequent processing, and the operability Is improved.

When the control unit 21 determines that the fetal movement related to the fetal movement information stored in the fetal movement history DB 22b should not be notified (S62: NO), the control unit 21 skips the processes of steps S16 and S63 to S65 and ends the process. .. When the control unit 21 determines that the storage unit 22 does not store a predetermined number of detection signals (S64: NO), the control unit 21 skips the process of step S65 and ends the process.

Further, in the present embodiment, a learned model for determining the presence / absence and type of fetal movement based on the detection signal from the fetal movement sensor 10 is obtained based on the information on fetal movement received from the pregnant woman by the pregnant woman terminal 20 via the input unit 24. It may have a configuration to be relearned. FIG. 16 is a flowchart showing another example of the processing procedure performed by the pregnant woman terminal 20 of the fifth embodiment. The process shown in FIG. 16 is obtained by adding steps S81 to S83 and S16 in place of steps S62, S16 and S63 to S65 in the process shown in FIG.

The control unit 21 of the pregnant woman terminal 20 performs the same processing as in steps S11 to S15 and S61 shown in FIG. Specifically, the control unit 21 determines the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10, stores the determined information on the fetal movement in the fetal movement history DB 22b, and the fetal movement has occurred ( A notification screen for notifying (that fetal movement has been detected) is generated and displayed on the display unit 25. The fetal movement notification screen here is for selecting a message indicating that the fetal movement has been detected and the type of fetal movement detected, a correct answer button to be operated when it is determined that the notified fetal movement type is correct, and other types. Type button and display. The type button is provided for each type to be discriminated in advance. When the correct answer button is operated via the input unit 24, the control unit 21 determines that the type of fetal movement detected here is the correct answer, and operates any of the type buttons via the input unit 24. If so, accept the correct type of fetal movement detected here. The correct type here is the type felt by the pregnant woman.

The control unit 21 determines whether or not the type of fetal movement has been accepted via the type button (S81), and if it determines that the type of fetal movement has been accepted (S81: YES), the type of fetal movement determined in step S13. Is incorrect, and teacher data based on the accepted type is generated (S82). Specifically, the control unit 21 generates teacher data including the detection signal acquired from the fetal movement sensor 10 in step S11 and the information (correct answer label) indicating the type of fetal movement received in step S81. Then, the control unit 21 performs a learning process of retraining the trained model using the generated teacher data (S83). Specifically, when the control unit 21 inputs the detection signal included in the teacher data into the trained model, the output value from the output node corresponding to the type of fetal movement indicated by the correct answer label included in the teacher data is 1. Retrain the trained model so that it approaches 0 and the output values from the other output nodes approach 0.

When the control unit 21 determines that the type of fetal movement is not accepted (S81: NO), that is, when the correct answer button is operated on the fetal movement notification screen, the processing of steps S82 and S83 is skipped. Then, the control unit 21 transmits the fetal movement information stored in the fetal movement history DB 22b from the communication unit 23 to the notification destination terminal 30 (S16), and ends the process. By the above-mentioned processing, it is possible to relearn the trained model for discriminating the type of fetal movement from the detection signal from the fetal movement sensor 10 based on the type of fetal movement determined by the pregnant woman herself. Therefore, it is possible to generate a trained model that can obtain a discrimination result according to the feeling of a pregnant woman. The re-learning process of the trained model described above may be performed after the teacher data has been accumulated to some extent. By using such a learned model according to the feeling of the pregnant woman, it is possible to accurately notify the notification destination terminal 30 of the type of fetal movement felt by the pregnant woman in the subsequent processing.

(Embodiment 6)
The fetal movement notification system in which the usage fee of the system is variable according to the length of time that the pregnant woman wears the fetal movement sensor 10 will be described. Since the fetal movement notification system of the present embodiment is realized by the

same devices

10, 20, and 30 as the fetal movement notification system of the first embodiment, the description of the same configuration will be omitted. In the present embodiment, a server connected to the network N is provided, and the fetal movement information collected by each pregnant woman terminal 20 is stored in the server. The server may be a server computer, a personal computer, or the like, and a plurality of servers may be provided. Further, the server may be realized by a plurality of virtual machines provided in one server, or may be realized by using a cloud server.

The pregnant woman terminal 20 of the present embodiment performs the same processing as that of the above-described first embodiment, and further performs the following processing. Since the notification destination terminal 30 of the present embodiment performs the same processing as that of the first embodiment, the description thereof will be omitted. FIG. 17 is a flowchart showing an example of a processing procedure performed by the pregnant woman terminal 20 of the sixth embodiment. In FIG. 17, the processing performed by the pregnant woman terminal 20 is shown on the left side, and the processing performed by the server is shown on the right side. The pregnant woman terminal 20 of the present embodiment has a predetermined time once a day, a predetermined time once a week, and an appropriate execution timing such as after a predetermined number of fetal movement information is accumulated in the fetal movement history DB 22b. The process of transmitting the fetal movement information accumulated in the fetal movement history DB 22b to the server is performed. Therefore, the control unit 21 of the pregnant woman terminal 20 determines whether or not the execution timing has arrived (S71), and if it determines that the execution timing has not arrived (S71: NO), waits until the execution timing arrives. When it is determined that the execution timing has arrived (S71: YES), the control unit 21 reads the fetal movement information from the fetal movement history DB 22b (S72) and transmits the read fetal movement information to the server (S73). In addition to the fetal movement ID, date and time, duration, and type, the fetal movement history DB 22b also stores the detection signal acquired from the fetal movement sensor 10 as fetal movement information, and in step S72, the control unit 21 determines the fetal movement ID, date and time, and continuation. Fetal movement information including time, type, and detection signal from the fetal movement sensor 10 is read out. Further, each fetal movement information stored in the fetal movement history DB 22b is provided with additional information indicating whether or not the fetal movement information has been transmitted to the server, and in step S72, the control unit 21 is based on the additional information. Only the fetal movement information that has not been transmitted to the server is read from the fetal movement history DB 22b. It is assumed that the destination information of the server is stored in the storage unit 22 or the fetal movement notification application 22a in advance.

When the server receives the fetal movement information transmitted from the pregnant woman terminal 20, the server stores the received fetal movement information in a predetermined DB (not shown) (S74). The predetermined DB has the same configuration as the fetal movement history DB 22b as shown in FIG. 3A. The server calculates the time (wearing time) that the user (pregnant woman) of the pregnant woman terminal 20 has been wearing the fetal movement sensor 10 based on the fetal movement information stored in the predetermined DB (S75). For example, the server calculates the detection time of the fetal movement by the fetal movement sensor 10 based on the detection date and time related to the detection signal from the fetal movement sensor 10, and sets the calculated detection time as the wearing time of the fetal movement sensor 10. The server specifies information such as a usage fee for using the fetal movement notification system and a coupon that can be used at a predetermined store or the like according to the calculated wearing time (S76). For example, the server stores the system usage fee, which is cheaper as the wearing time of the fetal movement sensor 10 is longer, the display data of the coupon obtained as the wearing time is longer, and the like in a storage unit (not shown). Then, the server reads the calculated system usage fee and coupon display data according to the wearing time from the storage unit, and specifies the system usage fee and coupon information for the pregnant woman.

The server transmits the specified system usage fee and coupon information to the pregnant woman terminal 20 that has transmitted the fetal movement information (S77). For example, the server generates screen information for displaying the specified system usage fee and coupon information and transmits it to the pregnant woman terminal 20. When the control unit 21 of the pregnant woman terminal 20 receives the system usage fee and coupon information (charge information) transmitted from the server, the received system usage fee and coupon information are displayed on the display unit 25, for example (S78). .. As a result, the system usage fee and coupon information according to the time when the pregnant woman was wearing the fetal movement sensor 10 can be notified to the pregnant woman. The system usage fee notified from the server can be paid by, for example, a credit card payment based on the credit card information registered in the server in advance. Further, the coupon information notified from the server can be serviced by presenting the coupon information display screen at a predetermined store, for example.

Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, various services such as discounting the system usage fee and distribution of coupons that can be used at a predetermined store can be received according to the wearing time of the fetal movement sensor 10. Therefore, it is possible to encourage the pregnant woman to wear the fetal movement sensor 10, and by lengthening the wearing time of the fetal movement sensor 10, more fetal movement information can be collected. The configuration of the present embodiment can be applied to the fetal movement notification system of the second embodiment, and the same effect can be obtained when the fetal movement notification system of the second embodiment is applied. Further, in the configuration of the present embodiment, it is possible to apply the modification described in each of the above-described embodiments.

(Embodiment 7)
The fetal movement notification system that determines the type of fetal movement by itself when a pregnant woman feels fetal movement and notifies that the fetal movement has occurred and the type of fetal movement determined by herself will be described. FIG. 18 is a schematic diagram showing a configuration example of the fetal movement notification system of the seventh embodiment. The fetal movement notification system of the present embodiment includes a pregnant woman terminal 20 and a notification destination terminal 30. Since the pregnant woman terminal 20 and the notification destination terminal 30 of the present embodiment have the same configuration as the pregnant woman terminal 20 and the notification destination terminal 30 of the first embodiment, the description of the same configuration will be omitted. In the present embodiment, the storage units 22 and 32 of the pregnant woman terminal 20 and the notification destination terminal 30 are replaced with the fetal

movement notification applications

22a and 32a and the fetal

movement history DB

22b and 32b of the first embodiment, and the fetal

movement sharing applications

22d and 32d. And the shared

history DBs

22e and 32e are stored. The fetal movement sharing application 22d stored in the pregnant woman terminal 20 is a pregnant woman application, and the fetal movement sharing application 32d stored in the notification destination terminal 30 is a notification destination application, which is a different program but for a common program. It may be configured to be used as a pregnant woman application 22d or a notification destination application 32d by setting different setting contents. That is, it may be configured to operate as the pregnant woman application 22d when the use by the pregnant woman is set, and to operate as the notification destination application 32d when the use by the pregnant woman's partner is set. Further, the storage unit 32 of the notification destination terminal 30 stores the application execution history DB 32f, which will be described later.

FIG. 19A is a schematic diagram showing a configuration example of

DB

22e and 32e stored in the pregnant woman terminal 20 and the notification destination terminal 30, and FIG. 19B is a schematic diagram showing a configuration example of DB 32f stored in the notification destination terminal 30. .. FIG. 19A shows the shared

histories DB

22e and 32e, and FIG. 19B shows the application execution history DB 32f. In the present embodiment, the shared

history DBs

22e and 32e stored in the pregnant woman terminal 20 and the notification destination terminal 30 have the same configuration. The shared

history DBs

22e and 32e store information related to fetal movement notified by the pregnant woman terminal 20 to the notification destination terminal 30. The shared

history DBs

22e and 32e shown in FIG. 19A include a history ID column, a date and time column, a type column, and the like. The history ID column stores the identification information assigned to each fetal movement notified from the pregnant woman terminal 20 to the notification destination terminal 30. The date and time column stores the date and time when the pregnant woman terminal 20 transmits the fetal movement information to the notification destination terminal 30 in association with the history ID. The transmission date and time of fetal movement information is represented by, for example, a time (year / month / day / hour / minute / second). The type column stores the type of each fetal movement in association with the fetal movement ID. The type of fetal movement is information input by the pregnant woman via the input unit 24. The history ID stored in the shared history DB 22e of the pregnant woman terminal 20 is issued and stored by the control unit 21 when the control unit 21 of the pregnant woman terminal 20 receives the type of fetal movement via the input unit 24. .. Further, as for the date and time stored in the shared history DB 22e of the pregnant woman terminal 20, the date and time information that the control unit 21 receives the type of fetal movement via the input unit 24 is stored by the control unit 21. Further, the type stored in the shared history DB 22e of the pregnant woman terminal 20 is stored by the control unit 21 when the control unit 21 receives it via the input unit 24.

When the control unit 21 receives the type of one fetal movement via the input unit 24, the pregnant woman terminal 20 stores information on one fetal movement in the shared history DB 22e, and then stores information on one fetal movement. Are collectively transmitted to the notification destination terminal 30. The stored contents of the shared history DB 32e of the notification destination terminal 30 are stored by the control unit 31 when the control unit 31 receives information regarding fetal movement from the pregnant woman terminal 20 via the network N. The stored contents of the shared

history DBs

22e and 32e are not limited to the example shown in FIG. 19A, and the shared

history DBs

22e and 32e may have different configurations. For example, impressions, comments, messages, etc. input from the pregnant woman or the notification destination user may be stored in the shared

history DB

22e, 32e via the pregnant woman terminal 20 or the notification destination terminal 30 for each fetal movement.

The application execution history DB 32f stores information regarding the execution status of the fetal movement sharing application 32d on the notification destination terminal 30. In the present embodiment, when the fetal movement sharing application 32d is executed using the notification destination terminal 30, and when the function realized by the fetal movement sharing application 32d is executed (used), the points corresponding to the executed functions are executed. Is added. Therefore, the application execution history DB 32f stores additional points indicating the execution status of the function by the fetal movement sharing application 32d. The application execution history DB 32f shown in FIG. 19B includes an execution date / time column, an execution point sequence, a record viewing point sequence, a consultation point sequence, other point columns, a total point sequence, and the like. The execution date / time column stores the date and time when the control unit 31 of the notification destination terminal 30 executes the fetal movement sharing application 32d, or the date and time when the function realized by the fetal movement sharing application 32d is executed. The execution point sequence stores predetermined points (5 points in FIG. 19B) in association with the execution date and time when the control unit 31 executes the fetal movement sharing application 32d. The record viewing point sequence stores predetermined points (5 points in FIG. 19B) in association with the execution date and time when the control unit 31 executes the record viewing function realized by the fetal movement sharing application 32d. The consultation point sequence stores predetermined points (10 points in FIG. 19B) in association with the execution date and time when the control unit 31 executes the consultation function realized by the fetal movement sharing application 32d. The other point sequence stores a predetermined point in association with the execution date and time when the control unit 31 executes another function realized by the fetal movement sharing application 32d. In addition, other functions include, for example, a function of providing bean knowledge about pregnancy, a function of giving a quiz about pregnancy, and the like. The total point column stores the total points up to the time of the execution date and time in association with the execution date and time. When a predetermined point is stored in any of the execution point row, the record viewing point row, the consultation point row, or the other point row, the stored predetermined point is added to the immediately preceding total point row. The points are memorized. The stored contents of the application execution history DB 32f are not limited to the example shown in FIG. 19B. The points given when each function is executed by the fetal movement sharing application 32d are determined in advance for each function and set in the fetal movement sharing application 32d.

Below, when the pregnant woman feels fetal movement, the pregnant woman and the user of the notification destination terminal 30 (for example, a partner of the pregnant woman) are notified of the occurrence of fetal movement by using the pregnant woman terminal 20 to notify the notification destination terminal 30. The process of sharing the occurrence of FIG. 20 is a flowchart showing an example of a fetal movement information notification processing procedure, FIGS. 21A to 22B are schematic views showing a screen example in the pregnant woman terminal 20, and FIGS. 23A and 23B are schematic views showing a screen example in the notification destination terminal 30. It is a figure.

In the pregnant woman terminal 20 of the present embodiment, when the pregnant woman feels fetal movement, the pregnant woman activates the fetal movement sharing application 22d and determines the type of fetal movement felt by herself. For example, fetal movement (kick) that occurs when the fetus is kicking the abdomen of the pregnant woman with the foot, fetal movement (punch) that occurs when the fetus is pushing the abdomen of the pregnant woman by hand, fetal movement (rotation) that occurs when the fetus is rotating, It is determined whether the fetal movement (hiccups) occurs when the fetus is hiccups or the fetal movement (pees) occurs when the fetus is peeing. When the fetal movement sharing application 22d is activated (executed), the control unit 21 of the pregnant woman terminal 20 displays an initial screen as shown in FIG. 21A on the display unit 25 (S91). The initial screen shown in FIG. 21A has a message input field 25a for inputting a message to be transmitted to the notification destination terminal 30 registered in advance. In the message input field 25a, a stamp selection button 25b for instructing the selection of the stamp image to be transmitted to the notification destination terminal 30 is displayed. Further, the initial screen has a button for receiving an execution instruction of each function realized by the fetal movement sharing application 22d. For example, the initial screen is a record button 25c for instructing the execution of a record viewing function that displays information on fetal movement transmitted from the pregnant woman terminal 20 to the notification destination terminal 30 in the past, and a predetermined SNS for consultation or information exchange. It has a consultation button 25d for instructing the execution of the consultation function to access (Social Networking Service), and a setting button for instructing the setting of various setting conditions related to the execution of the fetal movement sharing application 22d. In addition, the initial screen displays the schedule of the maternity examination. Further, the initial screen has an advertising column 25e for displaying advertising information of manufacturers and stores of clothing for pregnant women and clothing for babies, medical institutions, pharmaceutical manufacturers, supplement manufacturers, and the like.

When a pregnant woman wants to convey her feelings of fetal movement to her partner and share it, she can enter a message in the message input field 25a and send it to the notification destination terminal 30, or send a stamp image prepared in advance in the fetal movement sharing application 22d to the notification destination. It can be transmitted to the terminal 30. When the pregnant woman wants to transmit the stamp image and share the fetal movement, the pregnant woman operates the stamp selection button 25b on the initial screen. The control unit 21 of the pregnant woman terminal 20 determines whether or not the selection of the stamp image is instructed according to whether or not the stamp selection button 25b is operated (S92), and the selection of the stamp image is instructed. If it is determined that the stamp selection button 25b is not operated (S92: NO), the process waits until the stamp selection button 25b is operated.

When it is determined that the stamp selection button 25b is operated to instruct the selection of the stamp image (S92: YES), the control unit 21 displays the stamp list as shown in FIG. 21B on the display unit 25 (S93). In the example shown in FIG. 21B, stamp images expressing each of "KICK", "PUNCH", "ROTATION", "HICCUP", and "PEE" as the type of fetal movement are displayed. The pregnant woman determines one stamp image showing the type of fetal movement that she feels, and selects it via the input unit 24. When the control unit 21 determines whether or not the selection (for example, tap operation) for any of the stamp images in the stamp list has been accepted (S94) and has not accepted the selection (S94: NO), The display of the stamp list is continued (S93). When the control unit 21 determines that the selection for any of the stamp images has been accepted (S94: YES), the control unit 21 issues a history ID, the issued history ID, the time (date and time information) at this time, and the selected stamp. The type of fetal movement corresponding to the image is associated with the fetal movement information and stored in the shared history DB 22e (S95). Then, the control unit 21 transmits the fetal movement information stored in the shared history DB 22e to the notification destination terminal 30 (S96). The shared history DB 22e may store the stamp image information (information for displaying the stamp) selected by the pregnant woman. In this case, the control unit 21 stores the stamp image information stored in the shared history DB 22e. The fetal movement information including the fetal movement information may be transmitted to the notification destination terminal 30. Further, when a message is input to the message input field 25a on the initial screen, the control unit 21 includes the input message in the fetal movement information and stores it in the shared history DB 22e, and stores the fetal movement information including the message in the notification destination terminal 30. Send to.

When the record button 25c is operated on the initial screen, the control unit 21 of the pregnant woman terminal 20 reads the fetal movement information stored in the shared history DB 22e and has transmitted the fetal movement information (information about the fetal movement) to the notification destination terminal 30 in the past. ) Is displayed. FIG. 22A shows a screen example of past fetal movement information. In the example shown in FIG. 22A, the date and time stored in the shared history DB 22e corresponds to the stamp image corresponding to the type stored in the shared history DB 22e. It is displayed with. With such a screen, the pregnant woman can confirm the fetal movement information transmitted to the notification destination terminal 30 in the past, that is, the information regarding the fetal movement that she / she felt in the past at a later date. Further, when the consultation button 25d is operated on the initial screen, the control unit 21 of the pregnant woman terminal 20 accesses a predetermined SNS and displays a screen as shown in FIG. 22B. On the screen shown in FIG. 22B, an input field for inputting what the pregnant woman wants to consult or exchange information with, and a "consult" button for transmitting the input message are displayed. With such a screen, the pregnant woman can consult or post what she wants to consult with an expert, or what she wants someone to ask.

On the other hand, when the control unit 31 of the notification destination terminal 30 receives the fetal movement information transmitted by the pregnant woman terminal 20 in step S96, the control unit 31 stores the received fetal movement information in the shared history DB 32e (S97). As a result, the fetal movement information related to the fetal movement input by the pregnant woman using the pregnant woman terminal 20 is stored (accumulated) in the shared history DB 32e of the notification destination terminal 30. After that, the control unit 31 performs the same processing as steps S33 to S35 in FIG. 8 (S98 to S100) based on the fetal movement information stored in the shared history DB 32e, and determines the type of fetal movement received from the pregnant woman terminal 20. Execute the corresponding process. As a result, the notification destination terminal 30 can perform notification processing (for example, vibration processing by a vibrator) according to the type of fetal movement notified from the pregnant woman terminal 20 using the stamp image (notification information), and the notification destination terminal 30 can perform the notification processing. Thirty users can grasp not only the fetal movement that occurred in response to the executed notification process, but also the type of the fetal movement that occurred.

Further, the control unit 31 of the notification destination terminal 30 displays a notification screen on the display unit 35 for notifying that the fetal movement information has been received from the pregnant woman terminal 20 (S101). FIG. 23A shows an example of a notification screen, and on the screen shown in FIG. 23A, a stamp image corresponding to the type of fetal movement notified from the pregnant woman terminal 20 is displayed. Information on the stamp image according to the type of fetal movement may be transmitted from the pregnant woman terminal 20, and in this case, the control unit 31 sends the stamp image based on the stamp image information received from the pregnant woman terminal 20. It may be shown. Further, the notification screen shown in FIG. 23A has a "close" button for ending the display of the notification screen and a "open" button for instructing the activation of the fetal movement sharing application 32d.

The control unit 31 receives an instruction to start the fetal movement sharing application 32d by operating the "open" button on the notification screen. Therefore, the control unit 31 determines whether or not the activation of the fetal movement sharing application 32d is instructed (S102), and when it is determined that the activation is not instructed (S102: NO), that is, the "close" button is pressed. When it is operated, the display of the notification screen is terminated and the above-described processing is terminated. When it is determined that the start of the fetal movement sharing application 32d is instructed (S102: YES), the control unit 31 starts (executes) the fetal movement sharing application 32d and displays the start screen as shown in FIG. 23B on the display unit 35. (S103). When the fetal movement sharing application 32d is started, the control unit 31 stores the start date and time (execution date and time) and the execution point (predetermined point) at that time in the application execution history DB 32f, and further stores the memory. The execution points are added to and stored in the total points corresponding to the immediately preceding execution date and time (that is, the total points up to that point). The screen shown in FIG. 23B has the same configuration as the initial screen of the pregnant woman terminal 20 shown in FIG. 21A, and has a message input field 35a, a stamp selection button 35b, a record button 35c, a consultation button 35d, a setting button, and an advertisement field 35e. Etc. That is, the activation screen of the notification destination terminal 30 has a button for receiving an execution instruction of each function realized by the fetal movement sharing application 32d. In addition, the activation screen shown in FIG. 23B displays a stamp image according to the type of fetal movement notified from the pregnant woman terminal 20, and also displays a daddy meter 35f (graph) indicating the daddy level (papa-ness) of the partner. .. The daddy meter 35f indicates the degree of awareness (daddy level) as a daddy specified according to the latest total points stored in the application execution history DB 32f. As a result, the daddy level according to the time when the partner uses (executes) the fetal movement sharing application 32d, the number of times of use, and the like can be displayed on the notification destination terminal 30.

FIG. 24 is a flowchart showing an example of the update processing procedure of the papameter 35f by the notification destination terminal 30. In the notification destination terminal 30 of the present embodiment, when the "open" button is operated on the notification screen shown in FIG. 23A, or when the icon of the fetal movement sharing application 32d displayed on the display screen is operated, the fetal movement sharing application 32d Accepts the start instruction of. When the control unit 31 of the notification destination terminal 30 receives the activation instruction of the fetal movement sharing application 32d, the control unit 31 activates (executes) the fetal movement sharing application 32d (S141). When the fetal movement sharing application 32d is executed, the control unit 31 stores the execution points in the application execution history DB 32f and updates the total points based on the stored execution points (S142). The control unit 31 generates a papameter 35f according to the updated total points based on the updated total points (S143), and displays an initial screen as shown in FIG. 23B including the generated papameter 35f. (S144).

The initial screen (FIG. 23B) when the notification destination terminal 30 executes the fetal movement sharing application 32d has the same configuration as the initial screen (FIG. 21A) when the pregnant woman terminal 20 executes the fetal movement sharing application 22d. The same function can be realized through the initial screen. On the initial screen of the notification destination terminal 30, a stamp image corresponding to the type of fetal movement notified from the pregnant woman terminal 20 and a daddy meter 35f are displayed. Therefore, the control unit 31 determines whether or not the execution instruction of any of the functions realized by the fetal movement sharing application 32d is accepted via the initial screen (S145), and if it is determined that the execution instruction is accepted (S145: YES). ), The function that has received the execution instruction is executed (S146). For example, when the record button is operated, the control unit 31 executes a process of displaying (browsing) fetal movement information notified from the pregnant woman terminal 20 in the past.

When any of the functions is executed, the control unit 31 stores points (record viewing points, consultation points, and other points) corresponding to the executed functions in the application execution history DB 32f, and totals points based on the stored points. Update (S147). Further, the control unit 31 generates a daddy meter 35f according to the updated total points based on the updated total points, and updates the daddy meter 35f displayed on the screen to the generated daddy meter 35f (S148). .. When it is determined that the function execution instruction by the fetal movement sharing application 32d is not accepted (S145: NO), the control unit 31 skips the processes of steps S146 to S148. The control unit 31 performs the processes of steps S146 to S148 each time the function execution instruction by the fetal movement sharing application 32d is received. As a result, the points stored in the application execution history DB 32f are updated each time the user (pregnant woman's partner) of the notification destination terminal 30 executes the fetal movement sharing application 32d and each time each function of the fetal movement sharing application 32d is used. The daddy meter 35f, which indicates the daddy level according to the updated points, is also updated. By the above-mentioned processing, it is possible to present the daddy level according to the usage status of the partner's fetal movement sharing application 32d, and it is possible to encourage the partner to become aware of becoming a father.

In the present embodiment, the type of fetal movement felt by the pregnant woman can be notified to the user (family such as husband or partner) of the notification destination terminal 30 and shared. Further, since the user of the notification destination terminal 30 is notified at the timing when the pregnant woman feels the fetal movement, the shared feeling of the fetal movement is increased, and the communication between the pregnant woman and the family can be expected to increase. Further, in the present embodiment, the pregnant woman selects the type of fetal movement that she / she feels by selecting the stamp image using the pregnant woman terminal 20. At that time, in addition to selecting the stamp image, the pregnant woman may input the start date and time and end date and time of the fetal movement, or the start date and time and duration of the fetal movement via the fetal movement sharing application 22d of the pregnant woman terminal 20. Further, the start date and time and end date and time of the fetal movement input by the pregnant woman, or the start date and time and the duration may be stored in the shared history DB 22e, or may be transmitted to the notification destination terminal 30 together with the stamp image. As a result, the date and time when the fetal movement occurred, the continuous time, and the like can be shared between the pregnant woman and the user of the notification destination terminal 30, and an increase in conversation about the fetal movement can be expected. Furthermore, by accumulating the date and time when the fetal movement occurred, the frequency and type of the fetal movement that occurred in a certain period can be grasped, and it can also be used as a fetal movement counter. The frequency of fetal movements over a certain period can be used to determine the health status of the fetus, and the health status of the fetus determined from the frequency of fetal movements can be notified to the pregnant woman.

In the present embodiment, as the stamp image transmitted from the pregnant woman terminal 20 to the notification destination terminal 30, for example, a different image may be used for each number of weeks of pregnancy or months of pregnancy. In this case, for example, for each number of weeks of pregnancy or months of pregnancy, a set of stamp images expressing a fetus having a size and shape corresponding to the number of weeks of pregnancy or the number of months of pregnancy is prepared. In addition, each set of stamp images for each number of weeks of pregnancy or months of pregnancy includes a plurality of stamp images according to the type of fetal movement. Further, since the type of fetal movement felt by a pregnant woman differs depending on the number of weeks of pregnancy or the number of months of pregnancy, the number of stamp images included in the set according to the number of weeks of pregnancy or the number of months of pregnancy may differ. Pregnant women can use it by downloading a set of stamp images according to their own number of weeks of pregnancy or months of pregnancy to the pregnant woman terminal 20 for a fee or free of charge. FIG. 25 is a flowchart showing another example of the fetal movement information notification processing procedure. The process shown in FIG. 25 is the process shown in FIG. 20 in which step S111 is added between steps S92 and S93. The same steps as in FIG. 20 will be omitted.

In the notification process of fetal movement information shown in FIG. 25, the control unit 21 of the pregnant woman terminal 20 performs the same process as steps S91 and S92 in FIG. Then, when the control unit 21 determines that the stamp selection button 25b is operated to instruct the selection of the stamp image (S92: YES), the control unit 21 determines the number of weeks of pregnancy of the pregnant woman (user of the pregnant woman terminal 20) at this time. Identify (S111). The number of weeks of pregnancy can be calculated based on, for example, the expected date of delivery registered when the fetal movement sharing application 22d is installed on the terminal 20 for pregnant women and various information is initially set, or the number of weeks of pregnancy at that time. Further, the control unit 21 may display an input field for inputting the number of weeks of pregnancy on the display unit 25 and accept the number of weeks of pregnancy by input from the pregnant woman, for example, from a terminal in a medical institution via network N or. The number of weeks of gestation may be obtained via the storage medium 2a.

When the control unit 21 specifies the number of weeks of pregnancy, the control unit 21 reads out a set of stamp images corresponding to the specified number of weeks of pregnancy, displays a stamp list as shown in FIG. 21B on the display unit 25 (S93), and performs subsequent processing. I do. As a result, by preparing a set of stamp images according to the number of weeks of pregnancy in advance, a list of sets of stamp images according to the number of weeks of pregnancy of a pregnant woman can be displayed. Therefore, the pregnant woman selects a desired stamp image (a stamp image according to the type of fetal movement that she feels) from the stamp images displayed in the list, thereby selecting a stamp image according to the number of weeks of pregnancy and the type of fetal movement. Yes, the notification destination terminal 30 can be notified. In addition to the stamp image according to the number of weeks of pregnancy, the stamp image according to the number of months of pregnancy may be transmitted by preparing the stamp image according to the number of months of pregnancy.

It is also conceivable to use a stamp image that reflects the result of the pregnancy examination as the stamp image transmitted from the pregnant woman terminal 20 to the notification destination terminal 30. In this case, for example, a set of stamp images expressing that the fetal position is the head position, a set of stamp images expressing that the fetal fetal position is the breech position, and the fetal head being lowered in the latter half of pregnancy. Prepare a set of stamp images that express the above. In addition, each set of stamp images includes a plurality of stamp images according to the type of fetal movement. Then, the pregnant woman can use it by downloading a set of stamp images according to the result of the pregnant woman examination (fetal condition) to the pregnant woman terminal 20 for a fee or free of charge. Even in such a configuration, the pregnant woman terminal 20 and the notification destination terminal 30 can share the fetal movement by performing the process shown in FIG. 25. With such a configuration, in step S111, the control unit 21 of the pregnant woman terminal 20 identifies the state of the fetus (result of the pregnant woman examination) at the time when the selection of the stamp image is instructed (S111). A set of stamp images corresponding to the identified fetal condition is read out, and a stamp list as shown in FIG. 21B is displayed on the display unit 25 (S93). The result of the pregnant woman examination may be received, for example, by displaying an input field for inputting the result of the pregnant woman examination on the display unit 25 and inputting from the pregnant woman. Further, the pregnant woman terminal 20 may acquire the result of the pregnant woman examination from a terminal in a medical institution via the network N or via the storage medium 2a, for example.

By the above processing, it is possible to send and receive stamp images that better reflect the condition of the fetus. By preparing a stamp image that reflects the number of weeks or months of pregnancy and the result of the pregnancy examination, a stamp image corresponding to the number of weeks or months of pregnancy and the result of the pregnancy examination can be obtained. It may be configured to be able to send and receive. In addition, a stamp image for the first trimester of pregnancy before the fetal movement is felt may be prepared, and a predetermined notification process (for example, vibration process by a vibrator) is performed on the notification destination terminal 30 that receives such a stamp image from the pregnant woman terminal 20. By doing this, it is expected that communication between pregnant women and their partners will increase even in the early stages of pregnancy.

In the present embodiment, the fetal

movement sharing applications

22d and 32d may be linked with message transmission / reception applications such as LINE (registered trademark), chat, and e-mail. 26A and 26B are schematic views showing a screen example of a message transmission / reception application. Note that FIG. 26A shows a screen example of the pregnant woman terminal 20, and FIG. 26B shows a screen example of the notification destination terminal 30. As shown in FIG. 26A, the pregnant woman terminal 20 can send and receive a message to and from the notification destination terminal 30 by using the message sending / receiving application, and a stamp image as shown in FIG. 21B on the message sending / receiving application. Can also be sent and received. The example shown in FIG. 26A shows a state in which the stamp image of "KICK" and the message of "kicked" are transmitted to the notification destination terminal 30 (daddy). Based on the stamp image transmitted from the pregnant woman terminal 20 to the notification destination terminal 30 using the message transmission / reception application in this way, the control unit 21 of the pregnant woman terminal 20 has information on the fetal movement (type of fetal movement, etc.) input by the pregnant woman. (Fetal movement information) may be extracted and stored in the shared history DB 22e. As a result, not only the fetal movement information transmitted to the notification destination terminal 30 using the fetal movement sharing application 22d but also the information on the fetal movement transmitted to the notification destination terminal 30 using another application such as the message transmission / reception application is stored in the sharing history DB 22e. it can. Further, the control unit 21 extracts information (fetal movement information such as the type of fetal movement) transmitted by the pregnant woman from the message transmitted by the pregnant woman terminal 20 to the notification destination terminal 30 using the message transmission / reception application, and shares the history. It may be stored in DB22e.

Further, as shown in FIG. 26B, the notification destination terminal 30 can return a message and a stamp image to the pregnant woman terminal 20 by using the message transmission / reception application. The example shown in FIG. 26B shows a state in which the message "I'm going home soon" is transmitted from the notification destination terminal 30 to the pregnant woman terminal 20. When the notification destination terminal 30 transmits a message or stamp image to the pregnant woman terminal 20 using the message transmission / reception application in this way, the control unit 31 sets points (for example, other points) stored in the application execution history DB 32f. You may add. As a result, based on not only the message transmitted to the pregnant woman terminal 20 using the fetal movement sharing application 32d but also the message transmitted to the pregnant woman terminal 20 using another application such as the message sending / receiving application on the notification destination terminal 30. However, the points stored in the application execution history DB 32f are added, and the daddy level can be raised.

FIG. 27 is a flowchart showing another example of the notification processing procedure for fetal movement information. In the notification process shown in FIG. 27, when the pregnant woman feels fetal movement, she activates a message sending / receiving application (message application) and determines the type of fetal movement that she feels. The control unit 21 of the pregnant woman terminal 20 activates (executes) the message transmission / reception application (S121), and displays the initial screen (not shown) of the message transmission / reception application on the display unit 25. The control unit 21 determines whether or not the stamp image selection is instructed via the initial screen (S122), and if it determines that the stamp image selection is not instructed (S122: NO), waits. When it is determined that the selection of the stamp image is instructed via the initial screen (S122: YES), the control unit 21 displays a stamp list as shown in FIG. 21B on the screen of the message transmission / reception application (S123).

The control unit 21 determines whether or not the selection for any of the stamp images (stamp images according to the type of fetal movement) in the stamp list has been accepted (S124), and when it is determined that the selection has not been accepted (S124). S124: NO), the display of the stamp list is continued (S123). When the control unit 21 determines that the selection for any of the stamp images has been accepted (S124: YES), the control unit 21 transmits the selected stamp image to the notification destination terminal 30 (S125). The control unit 21 specifies the type of fetal movement associated with the stamp image based on the selected stamp image (S126). Then, the control unit 21 issues a history ID and stores the issued history ID, the time (date and time information) at this time, and the specified fetal movement type in the shared history DB 22e as fetal movement information (S127). .. In addition, the information of the stamp image (information for displaying the stamp) selected by the pregnant woman may be stored in the shared history DB 22e.

On the other hand, when the control unit 31 of the notification destination terminal 30 receives the stamp image from the pregnant woman terminal 20, the control unit 31 identifies the type of fetal movement associated with the stamp image based on the received stamp image (S128). Then, the control unit 31 associates the time (date and time information) at this time point with the specified type of fetal movement and stores it in the shared history DB 32e as fetal movement information (S129). At this time, the control unit 31 may issue a history ID and store the date and time information and the type of fetal movement in association with the history ID. As a result, fetal movement information based on the stamp image transmitted from the pregnant woman terminal 20 to the notification destination terminal 30 using the message transmission / reception application is stored (stored) in the shared history DB 32e of the notification destination terminal 30. After that, the control unit 31 performs the same processing as in steps S34 to S35 in FIG. 8 based on the type of fetal movement identified in step S128 (S130 to S131), and the stamp image transmitted via the message transmission / reception application. The process according to the type of fetal movement notified from the pregnant woman terminal 20 is executed.

Further, the control unit 31 of the notification destination terminal 30 displays a notification screen on the display unit 35 for notifying that the stamp image has been received from the pregnant woman terminal 20 via the message transmission / reception application (S132). Here, a notification screen as shown in FIG. 23A is displayed. The control unit 31 determines whether or not the start of the message transmission / reception application is instructed via the notification screen (S133), and if it is determined that the activation is instructed (S133: YES), the control unit 31 activates the message transmission / reception application (S133: YES). Execute) and display the startup screen of the message sending / receiving application (S134). As a result, the stamp image transmitted from the pregnant woman terminal 20 using the message transmission / reception application can be displayed on the notification destination terminal 30 using the message transmission / reception application, and the user of the notification destination terminal 30 can be notified. When the control unit 31 of the notification destination terminal 30 activates the fetal movement sharing application 32d, the stamp image (for the type of fetal movement) received from the pregnant woman terminal 20 using the message transmission / reception application on the screen as shown in FIG. 23B. The corresponding image) can be displayed. In the above-described configuration, the pregnant woman terminal 20 may store the message transmitted to the notification destination terminal 30 using the message transmission / reception application in the sharing history DB 22e as fetal movement information, and the notification destination terminal 30 is the message transmission / reception application. The message received from the pregnant woman terminal 20 may be stored in the shared history DB 32e as fetal movement information. In this case, similarly to the fetal movement information transmitted / received via the fetal movement sharing application 22d, the fetal movement information transmitted / received via the message transmission / reception application can be stored in the shared

history DBs

22e and 32e and can be confirmed later as past fetal movement information. .. Further, in the notification destination terminal 30, the message is stored in the application execution history DB 32f even when the message is transmitted using the message transmission / reception application, as in the case where the message is transmitted to the pregnant woman terminal 20 using the fetal movement sharing application 32d. You can update the points (papa level). In this case, regardless of the application to be used, points can be given according to the behavior of the user of the notification destination terminal 30 (sending a message to the pregnant woman).

In the present embodiment, the numerical value indicated by the daddy meter 35f displayed when the fetal movement sharing application 32d of the notification destination terminal 30 is executed is managed by, for example, a server, and the numerical value of the daddy meter 35f in each notification destination terminal 30 is managed. When the value exceeds a predetermined value, information such as a coupon or a gift that can be used at a predetermined store or the like may be provided to the notification destination terminal 30. In this case, the use of the fetal movement sharing application 32d by the user of the notification destination terminal 30 is promoted. Further, also in the present embodiment, the fetal movement information transmitted from the pregnant woman terminal 20 to the notification destination terminal 30 is stored in a shared history DB provided in an external storage device such as a cloud storage server, and is stored in the pregnant woman terminal. It may be configured to be shared between 20 and the notification destination terminal 30. Further, in the present embodiment, the transmission / reception of the stamp image performed between the pregnant woman terminal 20 and the notification destination terminal 30 may be performed via, for example, a server.

In the present embodiment, the stamp image transmitted from the pregnant woman terminal 20 to the notification destination terminal 30 or the vibration pattern in the vibration processing may be customized according to, for example, the operation of the pregnant woman on the pregnant woman terminal 20. For example, when a stamp image customization function is provided in the fetal movement sharing application 22d and a pregnant woman performs operations such as tap operation, double tap operation, flick operation, and swipe operation on the stamp image on the stamp image customization screen, You may customize it to a stamp image that expresses the movement according to the rhythm of the operation. Thereby, for example, in the stamp image of "KICK", it is possible to create a stamp image in which the foot of the fetus is kicked at a movement and speed according to the rhythm of operation. In this case, it is possible to create a stamp image that more closely reproduces the movement of the fetal movement felt by the pregnant woman, and it is possible to create a stamp image that reproduces the movement that the creator of the existing stamp image does not know. Since it is possible to create a stamp image that simulates the actual movement of the fetal movement in this way, it is possible to send and receive stamp images according to the pregnant woman, and the feeling of sharing the fetal movement between the pregnant woman and the partner increases. Can be expected. Further, the vibration pattern customization function may be provided in the fetal movement sharing application 22d. In this case, for example, a vibration pattern expressing movements according to the number of operations, rhythm, strength, long press, etc., according to various operations (tap operation, flick operation, etc.) performed by the pregnant woman within a certain period of time. You may create it. The customized vibration pattern is transmitted from the pregnant woman terminal 20 to the notification destination terminal 30, and the notification destination terminal 30 performs vibration processing with the received vibration pattern to obtain the customized vibration pattern in the pregnant woman terminal 20. Vibration can be realized. The movement of the fetal movement differs for each pregnant woman, and even for the same pregnant woman, it differs depending on the condition of the fetus. Therefore, by sharing the fetal movement with a vibration pattern that matches the movement of the fetal movement at that time, the fetal movement is shared. You can increase the feeling.

(Embodiment 8)
In the fetal movement notification system of the sixth embodiment, the fetal movement notification system having a configuration in which the server provides the fetal movement information (fetal movement detection information) collected from the pregnant woman terminal 20 to a system user such as a medical institution or a medical device manufacturer will be described. FIG. 28 is a schematic diagram showing a configuration example of the fetal movement notification system of the eighth embodiment. The fetal movement notification system of the present embodiment includes a server 60 and a system user terminal 70 in addition to the fetal movement sensor 10, the pregnant woman terminal 20, and the notification destination terminal 30. Since the fetal movement sensor 10, the pregnant woman terminal 20, and the notification destination terminal 30 have the same configuration as the fetal movement notification system of the first embodiment, the description thereof will be omitted. The server 60 and the system user terminal 70 can be connected to the network N. The server 60 is a server computer, a personal computer, or the like, and a plurality of servers 60 may be provided. Further, the server 60 may be realized by a plurality of virtual machines provided in one server, or may be realized by using a cloud server. The system user terminal 70 (provided terminal) is a terminal used by a user who wants to use the fetal movement notification system, and is a personal computer, a tablet terminal, or the like. Users who want to use the fetal movement notification system include, for example, medical institutions where pregnant women are undergoing maternity examinations, medical device manufacturers who want to use fetal movement information collected by the fetal movement notification system, and the like.

FIG. 29 is a block diagram showing a configuration example of the server 60 and the system user terminal 70. The server 60 includes a control unit 61, a storage unit 62, a communication unit 63, an input unit 64, a display unit 65, a reading unit 66, and the like, and these are connected to each other via a bus. Since each of these parts 61 to 66 has the same configuration as each of the parts 21 to 25 and 27 of the pregnant woman terminal 20, detailed description of these configurations will be omitted. In addition to the control program 62P, the storage unit 62 of the server 60 stores the fetal movement information DB 62a that stores the fetal movement information collected from the pregnant woman terminal 20 and the user information DB 62b that stores the information of the user who uses the fetal movement notification system. And remember. The system user terminal 70 includes a control unit 71, a storage unit 72, a communication unit 73, an input unit 74, a display unit 75, and the like, and these are connected to each other via a bus. Since each of these parts 71 to 75 has the same configuration as each part 21 to 25 of the pregnant woman terminal 20, detailed description of these configurations will be omitted.

30A and 30B are schematic views showing a configuration example of

DB

62a and 62b stored in the server 60. FIG. 30A shows the fetal movement information DB 62a, and FIG. 30B shows the user information DB 62b. The fetal movement information DB 62a is provided for each pregnant woman (pregnant woman terminal 20) and stores information on fetal movement detected by the fetal movement sensor 10 in association with the pregnant woman ID. The fetal movement information DB 62a shown in FIG. 30A includes a fetal movement ID string, a date / time sequence, a duration sequence, a sensor detection signal sequence, and the like. The fetal movement ID sequence stores the identification information assigned to each fetal movement detected by the fetal movement sensor 10. The date and time column stores the date and time when the fetal movement sensor 10 detected the fetal movement in association with the fetal movement ID, and the duration column stores the time when the fetal movement continued. The sensor detection signal sequence stores the detection signal output by the fetal movement sensor 10 in association with the fetal movement ID. Each information stored in the fetal movement information DB 62a is information transmitted from the pregnant woman terminal 20, and is stored by the control unit 61 each time the control unit 61 receives information on the fetal movement from the pregnant woman terminal 20 via the network N. To. The storage content of the fetal movement information DB 62a is not limited to the example shown in FIG. 30A, and for example, the type of fetal movement determined by the pregnant woman terminal 20 may be stored.

The user information DB 62b stores user information registered in advance in order to use the fetal movement notification system. The user information DB 62b shown in FIG. 30B includes a user ID column, a user name column, a purpose of use column, a usage fee column, and the like. The user ID column stores the identification information assigned to each user. The user name column stores the user's name or name in association with the user ID, and the user purpose column stores the purpose for which the user uses the fetal movement notification system. The usage fee column stores the system usage fee set for the user in association with the user ID. The system usage fee includes a provision fee according to the fetal movement information provided by the system user terminal 70 from the server 60. The user ID stored in the user information DB 62b is issued and stored by the control unit 61 when the control unit 61 acquires new user information via the input unit 64 or the communication unit 63. Information other than the user ID stored in the user information DB 62b is stored by the control unit 61 when the control unit 61 acquires it via the input unit 64 or the communication unit 63. The stored content of the user information DB 62b is not limited to the example shown in FIG. 30B, and various information about the user may be stored.

FIG. 31 is a schematic diagram showing the relationship between each device of the fetal movement notification system of the eighth embodiment. In the present embodiment, the server 60 collects information on the fetal movement of the pregnant woman (fetal movement information) collected by the pregnant woman terminal 20, and provides the pregnant woman with a coupon or a discount on the system usage fee according to the collected fetal movement information. Further, the server 60 provides the fetal movement information requested by the medical institution or the medical device maker, and collects the system usage fee according to the provided fetal movement information.

FIG. 32 is a flowchart showing an example of a procedure for providing fetal movement information. The process shown in FIG. 32 is obtained by adding the processes of steps S151 to S156 to the processes of steps S71 to S78 shown in FIG. In FIG. 32, the processing performed by the pregnant woman terminal 20 is shown on the left side, the processing performed by the server 60 in the center, and the processing performed by the system user terminal 70 on the right side. In the present embodiment, the pregnant woman terminal 20 and the server 60 perform the same processing (S71 to S78) as the processing shown in FIG. 17, and the fetal movement information collected by each pregnant woman terminal 20 is the fetal movement of the server 60. It is stored in the information DB 62a. Further, the server 60 transmits the coupon information and the like corresponding to the collected fetal movement information to the pregnant woman terminal 20. Thereby, the coupon information according to the time when the pregnant woman used the fetal movement sensor 10 (detection time by the fetal movement sensor 10) or the number of times of use (detection number of times) can be provided to the pregnant woman. In the present embodiment, the fetal movement information of each pregnant woman stored in the server 60 can be used by a user registered in advance, and the server 60 uses the accumulated fetal movement information in the system in response to a request from the user. Provided to the person terminal 70. The system user terminal 70 is, for example, a terminal at a medical institution where a pregnant woman is undergoing a maternity examination, or a terminal at a medical device manufacturer who wants to use the fetal movement information collected by the server 60.

The server 60 of this embodiment has a function as a web server, and a website for accepting requests for collected fetal movement information is open to the public via network N. When requesting fetal movement information from the server 60, the control unit 71 of the system user terminal 70 accesses the server 60 and receives a request screen for requesting the fetal movement information. The control unit 71 of the system user terminal 70 displays the received request screen on the display unit 75, and receives a request for fetal movement information from the request screen via the input unit 74. For example, when the user of the system user terminal 70 is a doctor at a medical institution where the pregnant woman goes to the hospital, the system user terminal 70 determines the predetermined pregnant woman according to the instruction from the doctor via the input unit 74. Accept requests for fetal movement information for the period. The fetal movement information here is used for a pregnant woman's examination, and the doctor who has acquired the fetal movement information diagnoses whether or not there is an abnormality in the fetal condition based on the fetal movement information. Further, when the user of the system user terminal 70 is an employee of a medical device manufacturer conducting research on fetal movement information, the system user terminal 70 follows an instruction from the employee via the input unit 74. Accepts requests for fetal movement information for pregnant women of a given number of weeks of pregnancy. The fetal movement information here is used, for example, in research for manufacturing a new medical device using the fetal movement information.

Therefore, the control unit 71 of the system user terminal 70 determines whether or not the request for fetal movement information has been accepted via the input unit 74 (S151), and if it determines that the request has not been accepted (S151: NO), Wait until it is accepted. When it is determined that the request for fetal movement information has been accepted (S151: YES), the control unit 71 requests the designated fetal movement information from the server 60 (S152). The control unit 61 of the server 60 reads the fetal movement information requested from the system user terminal 70 from the fetal movement information DB 62a (S153). For example, when the fetal movement information of a predetermined pregnant woman for a predetermined period is requested, the control unit 61 reads out the fetal movement information for the designated pregnant woman during the specified period. When the fetal movement information of a predetermined number of weeks of pregnancy is requested, the control unit 61 reads out the fetal movement information of the number of weeks of pregnancy specified for each pregnant woman. In this case, by storing the fetal movement information including the number of weeks of pregnancy in the fetal movement information DB 62a, the fetal movement information of the designated number of weeks of pregnancy can be read out. When the system user terminal 70 requests fetal movement information, the control unit 61 receives information about the system user from the system user terminal 70, and can authenticate the user by using the received information. In this case, the requested fetal movement information may be read from the fetal movement information DB 62a.

The control unit 61 specifies the system usage fee for the system user who has requested the fetal movement information based on the user information DB 62b (S154). The control unit 61 transmits the read fetal movement information and the specified usage fee to the system user terminal 70 that has requested the fetal movement information (S155). For example, the server 60 transmits a file storing the requested fetal movement information and screen information for displaying the system usage fee to the system user terminal 70. The control unit 71 of the system user terminal 70 receives the fetal movement information transmitted from the server 60 and the screen information for displaying the system usage fee, and stores the received fetal movement information and the screen information (system usage fee). It is stored in the unit 72 (S156). The control unit 71 may display the system usage fee on the display unit 75 based on the received screen information. Further, the system usage fee notified from the server 60 may be paid by credit card payment based on the credit card information of the system user registered in advance in the server 60, for example.

Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, the fetal movement information collected by the server 60 from each pregnant woman terminal 20 can be provided to the system user who needs the fetal movement information. In addition, the administrator who manages the fetal movement notification system can collect the system usage fee from the system user. The configuration of the present embodiment can be applied to the fetal movement notification system of the second embodiment, and the same effect can be obtained when the fetal movement notification system of the second embodiment is applied. Further, in the configuration of the present embodiment, it is possible to apply the modification described in each of the above-described embodiments.

(Embodiment 9)
It has a configuration in which a trained model for discriminating the presence / absence and type of fetal movement based on a detection signal from the fetal movement sensor 10 is relearned based on the type of fetal movement received from the pregnant woman via the input unit 24 by the pregnant woman terminal 20. The terminal 20 for pregnant women will be described. In addition, this embodiment is a modification of the terminal 20 for a pregnant woman performing the process shown in FIG. The fetal movement notification system of the present embodiment has the same configuration as the fetal movement notification system of the first embodiment. That is, the fetal movement notification system of the present embodiment includes the

devices

10, 20, and 30 in the first embodiment. The description of the same configuration as that of the first embodiment will be omitted.

FIG. 33 is a block diagram showing a configuration example of the pregnant woman terminal 20 according to the ninth embodiment. Since the pregnant woman terminal 20 of the present embodiment has the same configuration as the pregnant woman terminal 20 of the first embodiment shown in FIG. 2, the description of the configuration will be omitted. The storage unit 22 of the pregnant woman terminal 20 of the present embodiment is, in addition to the control program 22P, the fetal movement notification application 22a, and the fetal movement history DB 22b, the fetal movement discrimination model 22M which is a learned model configured as shown in FIG. 5, for example. Remember. The fetal movement discrimination model 22M receives the detection signal from the fetal movement sensor 10 (detection signal by each pressure sensor) as an input, and outputs the type of fetal movement and no fetal movement determined from the input detection signal.

FIG. 34 is a flowchart showing an example of the processing procedure performed by the pregnant woman terminal 20 of the ninth embodiment. The process shown in FIG. 34 is obtained by adding steps S161 to S164 after NO in steps S11 and S12 in the process shown in FIG. The control unit 21 of the pregnant woman terminal 20 of the present embodiment determines the presence / absence and type of fetal movement based on the detection signal output from the fetal movement sensor 10 by performing the same processing as the processing shown in FIG. Information about the fetal movement is stored in the fetal movement history DB 22b. Further, the control unit 21 of the pregnant woman terminal 20 of the present embodiment accepts the correct answer type from the pregnant woman when the determined fetal movement type is determined to be incorrect by the pregnant woman, and uses the correct answer type as teacher data. The fetal movement discrimination model 22M (learned model) can be retrained.

On the other hand, when the control unit 21 determines in step S11 that the detection signal has not been acquired (S11: NO), or when it determines in step S12 that the detection signal does not include fetal movement (S12: NO). , It is determined whether or not the activation instruction of the fetal movement notification application 22a is accepted via the input unit 24 (S161). In the present embodiment, even when the pregnant woman terminal 20 does not detect the fetal movement based on the detection signal from the fetal movement sensor 10, when the pregnant woman feels the fetal movement, the detection from the fetal movement sensor 10 at that time. The fetal movement discrimination model 22M can be relearned as the signal is a signal related to the fetal movement felt by the pregnant woman. Therefore, when the pregnant woman feels fetal movement when the fetal movement notification screen is not displayed on the pregnant woman terminal 20, she activates the fetal movement notification application 22a using the pregnant woman terminal 20 to display the type of fetal movement that she has just felt. input.

When it is determined that the activation instruction of the fetal movement notification application 22a is not accepted (S161: NO), the control unit 21 returns to the process of step S11. When it is determined that the activation instruction of the fetal movement notification application 22a has been accepted (S161: YES), the control unit 21 activates (executes) the fetal movement notification application 22a and displays an input screen for inputting the type of fetal movement felt by the pregnant woman. It is displayed on the display unit 25 (S162). The input screen is configured so that one of the types of fetal movements such as hiccups, punches, kicks, rotations, and pees can be selected, and the control unit 21 controls one of the types of fetal movements via the input screen. Is determined (S163). When it is determined that the type of fetal movement is not accepted (S163: NO), the control unit 21 continues to display the input screen (S162). When it is determined that the type of fetal movement has been accepted (S163: YES), the control unit 21 operates the fetal movement sensor 10 to acquire a detection signal by the fetal movement sensor 10 (S164).

Then, the control unit 21 shifts to the process of step S82. That is, the control unit 21 uses the received fetal movement type as the correct answer label, and generates teacher data including information indicating the fetal movement type (correct answer label) and the detection signal acquired from the fetal movement sensor 10 (S82). Then, the control unit 21 performs a learning process for re-learning the fetal movement discrimination model 22M using the generated teacher data (S83). Here, when the detection signal included in the teacher data is input to the fetal movement discrimination model 22M, the control unit 21 has an output value of 1.0 from the output node corresponding to the type of fetal movement indicated by the correct answer label included in the teacher data. The fetal movement discrimination model 22M is retrained so that the output values from the other output nodes approach 0.

By the above-mentioned processing, the fetal movement discrimination model 22M can be relearned based on the judgment result of the pregnant woman herself. Therefore, it is possible to generate a fetal movement discrimination model 22M that can obtain a discrimination result according to the feeling of a pregnant woman. The re-learning process of the fetal movement discrimination model 22M described above may be performed after the fetal movement information is transmitted to the notification destination terminal 30, or may be performed after the teacher data has been accumulated to some extent. By using the fetal movement discrimination model 22M that matches the feeling of the pregnant woman, the type of fetal movement felt by the pregnant woman in the subsequent processing can be accurately notified to the notification destination terminal 30.

In the fetal movement notification system of the present embodiment, the notification destination terminal 30 performs the same processing as the processing shown in FIG. As a result, also in the present embodiment, the notification destination terminal 30 can perform notification processing according to the type of fetal movement based on the fetal movement information received from the pregnant woman terminal 20. In the present embodiment, not only the fetal movement detected by the pregnant woman terminal 20 based on the detection signal from the fetal movement sensor 10 but also the fetal movement felt by the pregnant woman can be notified to the notification destination terminal 30. Also in this embodiment, the same effect as that of the first embodiment can be obtained. Further, in the present embodiment, since the fetal movement discrimination model 22M can be relearned based on the judgment result of the pregnant woman, the fetal movement discrimination model 22M that can discriminate into a type more suitable for the feeling of the pregnant woman can be realized, and the fetal movement discrimination model 22M can be discriminated more appropriately. The type of fetal movement can be notified to the notification destination terminal 30.

The configuration of the present embodiment can be applied to the fetal movement notification system of the second embodiment, and the same effect can be obtained when the fetal movement notification system of the second embodiment is applied. When applied to the fetal movement notification system of the third embodiment, the fetal movement discrimination model 22M is configured to input not only the detection signal from the fetal movement sensor 10 but also the detection signal from the acceleration sensor and output the presence / absence and type of fetal movement. To. Similarly, for the fetal movement discrimination model 22M having such a configuration, the fetal movement discrimination model 22M can be relearned by using the teacher data based on the judgment of the pregnant woman. Further, in the configuration of the present embodiment, it is possible to apply the modification described in each of the above-described embodiments.

In each of the above-described embodiments, not only the presence or absence and type of fetal movement may be determined based on the detection result by the fetal movement sensor 10, but also, for example, whether or not an abnormality has occurred in the heartbeat of the fetus may be determined. For example, when the control unit 21 of the pregnant woman terminal 20 determines whether or not an abnormality has occurred in the heartbeat of the fetus and determines that there is a high possibility that an abnormality has occurred, the user and the notification destination of the pregnant woman terminal 20. It may be configured to notify the user of the terminal 30.

(Embodiment 10)
A modified example of the fetal movement notification system of the seventh embodiment will be described. In the fetal movement notification system of the present embodiment, when the pregnant woman selects a stamp image according to the type of fetal movement that she / she feels using the fetal movement sharing application 22d, the pregnant woman terminal 20 corresponds to the selected stamp image. Depending on the type of fetal movement, vibration using a vibrator or the like is performed and an annotation message is displayed. Therefore, the pregnant woman terminal 20 of the present embodiment has a notification unit (not shown) by a vibrator or the like, similarly to the notification unit 36 of the notification destination terminal 30. The notification unit of the pregnant woman terminal 20 may also be configured to light or blink a lamp, sound a buzzer, output a message by a speaker, display an image by the display unit 25, or the like, depending on the type of fetal movement. Since the fetal movement notification system of the present embodiment has the same configuration as the fetal movement notification system of the seventh embodiment except that the pregnant woman terminal 20 has a notification unit, the description of the configuration will be omitted.

FIG. 35 is a flowchart showing an example of the notification processing procedure of fetal movement information of the tenth embodiment, and FIG. 36 is a schematic view showing a screen example of the pregnant woman terminal 20. The process shown in FIG. 35 is obtained by adding steps S171 to S173 between steps S94 and S95 in the process shown in FIG. The same steps as in FIG. 20 will be omitted. Further, in FIG. 35, the illustration of steps S98 to S103 in FIG. 20 is omitted. The control unit 21 of the pregnant woman terminal 20 of the present embodiment performs the same processing as in steps S91 to S94 shown in FIG. Then, when the control unit 21 determines that the selection (for example, tap operation) for any of the stamp images has been accepted (S94: YES), as shown in FIG. 36, the annotation regarding the type of fetal movement corresponding to the selected stamp image. Display a message (S171). In the example shown in FIG. 36, an annotation message corresponding to the selected stamp image (type of fetal movement) is superimposed and displayed on the stamp list. Further, the control unit 21 determines the vibration processing according to the type of fetal movement corresponding to the selected stamp image, and executes the determined vibration processing with a vibrator or the like (S172). The type of fetal movement and the vibration processing corresponding to each type are stored in the storage unit 22 in association with each other, and the control unit 21 corresponds to the stamp image selected from the stored contents of the storage unit 22. Determine the vibration treatment according to the type of fetal movement.

The pregnant woman confirms the annotation message displayed on the pregnant woman terminal 20 and the vibration processing by the pregnant woman terminal 20, and if it is a stamp image (type of fetal movement) to be notified to the notification destination terminal 30, this stamp image is used. Select (tap operation) again and decide the stamp image to be sent. The control unit 21 determines whether or not the determination of the stamp image to be transmitted has been accepted (S173). Specifically, the control unit 21 determines whether or not the selection operation (tap operation) for the stamp image selected in step S94 has been accepted again. When it is determined that the determination of the stamp image to be transmitted is not accepted (S173: NO), the control unit 21 returns to the process of step S94 and determines whether or not the selection for another stamp image is accepted (S94). ..

When it is determined that the determination of the stamp image to be transmitted has been accepted (S173: YES), the control unit 21 performs the processes of steps S95 to S96 on the selected stamp image. The control unit 31 of the notification destination terminal 30 performs the same processing as in steps S97 to S103 shown in FIG. By the above-mentioned processing, the fetal movement information regarding the fetal movement felt by the pregnant woman is stored in the shared history DB 22e of the pregnant woman terminal 20 and the shared history DB 32e of the notification destination terminal 30. In addition, the notification destination terminal 30 performs notification processing (for example, vibration processing by a vibrator) according to the type of fetal movement (stamp image) notified from the pregnant woman terminal 20, so that the pregnant woman can be notified to the user of the notification destination terminal 30. You can notify the type of fetal movement you feel. Further, in the present embodiment, when the pregnant woman transmits the stamp image using the pregnant woman terminal 20, the pregnant woman terminal 20 performs an annotation message and vibration processing according to the stamp image (type of fetal movement) selected by the pregnant woman. Do. Therefore, the pregnant woman can grasp the notification process (vibration process) performed on the notification destination terminal 30 according to the stamp image transmitted by herself, and more share the information on the fetal movement between the pregnant woman and the user of the notification destination terminal 30. be able to.

Also in this embodiment, the fetal

movement sharing applications

22d and 32d may be linked with the message sending / receiving application. That is, when the pregnant woman terminal 20 transmits a stamp image as shown in FIG. 21B to the notification destination terminal 30 using the message transmission / reception application, the information regarding the fetal movement selected by the pregnant woman based on the transmitted stamp image. (Fetal movement information such as the type of fetal movement) may be extracted and stored in the shared history DB 22e.

The embodiments disclosed this time are to be considered as illustrative in all points and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

10 Fetal movement sensor 20 Pregnant woman terminal 21 Control unit 22 Storage unit 30 Notification destination terminal 31 Control unit 32 Storage unit 35

Display unit

22a, 32a Fetal

movement notification application

22b, 32b Fetal movement history DB
22d, 32d Fetal

movement sharing application

22e, 32e Sharing history DB

Claims

Obtain fetal movement information regarding the fetal movement of pregnant women,
The type of fetal movement is specified based on the acquired fetal movement information, and
A program that causes a computer to execute a process that outputs a control signal that controls the process according to the specified type of fetal movement.
The program according to claim 1, which outputs the control signal that controls the generation of vibration according to the type of fetal movement.
The program according to claim 1 or 2, which outputs the control signal that controls the display of an image according to the type of fetal movement.
The acquired fetal movement information or the specified type of fetal movement is stored in the storage unit in association with the acquisition date and time of the fetal movement information.
Accept the acquisition date and time
The control that controls the processing according to the type of the fetal movement specified based on the fetal movement information stored in association with the received acquisition date and time, or the type of the fetal movement stored in association with the received acquisition date and time. The program according to any one of claims 1 to 3, which causes the computer to execute a process of outputting a signal.
The image data of the fetus taken by ultrasonography and the shooting date and time of the image data are acquired.
The program according to any one of claims 1 to 4, wherein the computer executes a process of outputting the control signal for controlling the display of the image of the fetus based on the image data according to the shooting date and time.
Receives an instruction to switch between a process of outputting the control signal to a processing unit in the computer and a process of outputting the control signal to an external device capable of communicating with the computer.
The program according to any one of claims 1 to 5, which causes the computer to execute a process of outputting the control signal to the processing unit in the computer or the external device in response to the received switching instruction.
The fetal movement information includes position information indicating the position where a force is applied to the abdomen of the pregnant woman due to the fetal movement.
A pressurizing device that is attached to a person's belly and applies force to an arbitrary position on the person's belly is subjected to pressurization processing according to the type of fetal movement specified based on the fetal movement information, corresponding to the position indicated by the position information. The program according to any one of claims 1 to 6, which causes the computer to execute a process of outputting the control signal, which is controlled to be performed at a position where the computer is used.
Acquire the output data output from the fetal movement sensor that detects the fetal movement of a pregnant woman,
When the output data from the fetal movement sensor is input, the acquired output data is applied to a trained model trained to determine the presence or absence of fetal movement in the output data and the type of fetal movement if there is fetal movement. type in,
A program that causes a computer to execute a process of determining the presence or absence of fetal movement in the output data and the type of fetal movement if there is fetal movement, based on the output information from the trained model.
The trained model is trained to determine the presence or absence of fetal movement and the type of fetal movement if there is fetal movement when the output data from the fetal movement sensor and the output data from the acceleration sensor are input.
Acquire the output data output from the acceleration sensor that detects the movement of the pregnant woman,
The acquired output data from the fetal movement sensor and the output data from the acceleration sensor are input to the trained model.
The program according to claim 8, wherein the presence or absence of the fetal movement and the type of the fetal movement if there is the fetal movement are determined based on the output information from the trained model.
The program according to claim 8 or 9, wherein the computer executes a process of outputting the determined type of fetal movement to a predetermined external device as fetal movement information related to the fetal movement of a pregnant woman.
Determine whether or not to output the fetal movement information,
The program according to claim 10, wherein the computer executes a process of outputting the fetal movement information to a predetermined external device when it is determined that the information should be output.
Accepting information indicating whether the determined type of fetal movement is appropriate or another type,
When the information indicating that it is another type is received, the process of retraining the trained model is performed based on the teacher data including the information indicating the other type received and the output data from the fetal movement sensor. The program according to any one of claims 8 to 11, which is to be executed by the computer.
Acquire the usage fee or the fee information indicating the coupon information according to the detection time of the fetal movement by the fetal movement sensor calculated based on the output data output from the fetal movement sensor.
The program according to any one of claims 8 to 11, which causes the computer to execute a process of outputting the acquired charge information.
Accepting the types of fetal movements of pregnant women,
A program that causes a computer to execute a process of transmitting the received notification information according to the type of fetal movement to a predetermined terminal.
Obtain the number of weeks or months of pregnancy of the pregnant woman,
Display a plurality of stamp images according to the acquired number of weeks of pregnancy or months of pregnancy,
Accepts the selection of the stamp image according to the type of fetal movement from the displayed stamp image,
The program according to claim 14, wherein the computer is made to execute a process of transmitting the selected stamp image to the predetermined terminal.
Obtain the results of the pregnant woman's examination of the pregnant woman,
Display a plurality of stamp images according to the acquired results of the pregnant woman examination,
Accepts the selection of the stamp image according to the type of fetal movement from the displayed stamp image,
The program according to claim 14 or 15, which causes the computer to execute a process of transmitting the selected stamp image to the predetermined terminal.
The type of fetal movement of the pregnant woman is extracted from the information transmitted via the message sending application.
The program according to any one of claims 14 to 16, wherein the computer executes a process of storing the extracted type of fetal movement in a storage unit.
Accepting settings for use by the pregnant woman's partner,
When the use by the partner is set, specify the level according to the execution time or the number of executions of the own program.
The program according to any one of claims 14 to 17, which causes the computer to execute a process of displaying a graph showing the specified level on the display unit.
Fetal movement detection information including the output data output from the fetal movement sensor that detects the fetal movement of the pregnant woman and the type of the fetal movement determined based on the output data is collected.
The collected fetal movement detection information is provided to the terminal to which the information is provided.
A program that causes a computer to execute a process of outputting charge information indicating a provision charge of the provided fetal movement detection information to the terminal of the provision destination.
Coupon information according to the detection time or the number of detections of fetal movement by the fetal movement sensor calculated based on the output data output from the collected fetal movement sensor is generated.
The program according to claim 19, wherein the computer executes a process of outputting the generated coupon information to a terminal associated with the fetal movement sensor.
Teacher data including a plurality of output data output from a fetal movement sensor that detects the fetal movement of a pregnant woman, presence / absence information indicating the presence / absence of fetal movement in each output data, and type information indicating the type of fetal movement when there is fetal movement. To get and
Generation of a learning model that generates a learning model that determines the presence or absence of fetal movement in the output data and the type of fetal movement if there is fetal movement when the output data from the fetal movement sensor is input, based on the acquired teacher data. Method.
The teacher data further includes output data output from an acceleration sensor that detects the movement of the pregnant woman.
A request to generate a learning model for discriminating the presence or absence of fetal movement and the type of fetal movement if there is fetal movement when the output data from the fetal movement sensor and the output data from the acceleration sensor are input, based on the acquired teacher data. Item 21. The method for generating a learning model according to Item 21.
A fetal movement information acquisition unit that acquires fetal movement information related to the fetal movement of a pregnant woman, a specific part that identifies the type of fetal movement based on the acquired fetal movement information, and a specific unit.
A wearable device including an execution unit that executes processing according to the specified type of fetal movement.
An acquisition unit that acquires output data output from a fetal movement sensor that detects the fetal movement of a pregnant woman,
When the output data from the fetal movement sensor is input, the acquired output data is applied to a trained model trained to determine the presence or absence of fetal movement in the output data and the type of fetal movement if there is fetal movement. Input part to input and
An information processing device including a determination unit for determining the presence / absence of fetal movement in the output data and the type of fetal movement if there is fetal movement, based on the output information from the trained model.
Obtain fetal movement information regarding the fetal movement of pregnant women,
The type of fetal movement is specified based on the acquired fetal movement information, and
An information processing method in which a computer executes a process of outputting a control signal that controls a process according to the specified type of fetal movement.