JP2016139967A - Call incoming notification method, call incoming notification program, and call incoming notification device - Google Patents

Call incoming notification method, call incoming notification program, and call incoming notification device Download PDF

Info

Publication number
JP2016139967A
JP2016139967A JP2015014357A JP2015014357A JP2016139967A JP 2016139967 A JP2016139967 A JP 2016139967A JP 2015014357 A JP2015014357 A JP 2015014357A JP 2015014357 A JP2015014357 A JP 2015014357A JP 2016139967 A JP2016139967 A JP 2016139967A
Authority
JP
Japan
Prior art keywords
terminal device
step
device
incoming call
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
JP2015014357A
Other languages
Japanese (ja)
Inventor
山村 一之
Kazuyuki Yamamura
一之 山村
Original Assignee
富士通株式会社
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, Fujitsu Ltd filed Critical 富士通株式会社
Priority to JP2015014357A priority Critical patent/JP2016139967A/en
Publication of JP2016139967A publication Critical patent/JP2016139967A/en
Application status is Pending legal-status Critical

Links

Images

Abstract

PROBLEM TO BE SOLVED: To provide a call incoming notification method, program, and device that preferentially make a terminal device worn by a user ring.SOLUTION: A call incoming notification method includes: a step S1301 of collecting, from a plurality of terminal devices, utilization situation information including biological information or terminal state information showing a terminal device's state such as whether or not the device is worn, whether or not a screen is being viewed, and whether or not the device is being grasped; a step S1302 of granting, on the basis of the utilization situation information, priority to terminal devices to be notified of call incoming; a step S1303 of determining a terminal device to be notified of the call incoming by maximizing the terminal device's priority; and a step S1304 of notifying the determined terminal device.SELECTED DRAWING: Figure 13

Description

  The present invention relates to an incoming call notification method, an incoming call notification program, and an incoming call notification apparatus.

  In recent years, multi-devices that share services and contents among a plurality of terminal devices are becoming popular.

  By the way, in a conventional terminal device, an incoming notification such as a mail is transmitted from the server to the terminal device when the server to which the Push notification is set receives the incoming notification. The incoming call notification is notified from the server to the terminal device using a number set in a SIM (Subscriber Identity Module) card inserted in the terminal device.

JP 2012-129834 A JP 2009-164780 A JP 2002-84575 A

  When multiple terminal devices are linked, such as a multi-device, when the server receives an incoming call notification for any of the multiple terminal devices, the server unconditionally notifies all the linked terminal devices. Send.

  For this reason, the plurality of terminal devices that have received the notification ring all at once without considering the usage state of the terminal device by the user. Further, in this case, for example, the terminal device located at a place away from the user rings, which is not preferable from the viewpoint of power saving.

  In one aspect, it is an object to provide an incoming call notification method, an incoming call notification program, and an incoming call notification apparatus that can cause a terminal device worn by a user to ring preferentially.

  According to one aspect, there is an incoming notification method by a computer, wherein the computer collects usage status information including any one of biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices. Based on the usage status information, a terminal device that notifies an incoming call is determined, and the determined terminal device is notified.

  The above procedure may be a function unit that realizes the above procedure and a program that is executed by a computer as each procedure.

  The terminal device worn by the user can be preferentially ringed.

It is a 1st figure explaining the communication system of this embodiment. It is a 2nd figure explaining the communication system of this embodiment. It is a figure explaining the hardware constitutions of an incoming call notification server. It is a figure explaining the hardware constitutions of a terminal device. It is a figure which shows an example of a user information table. It is a figure which shows an example of a notification setting table. It is a figure which shows an example of a device status table. It is a figure which shows an example of a device information table. It is a figure which shows an example of a notification destination device table. It is a figure which shows an example of an account table. It is a figure explaining the function of an incoming call notification server. It is a flowchart explaining the process of a user registration part. It is a flowchart explaining the whole operation | movement of an incoming call notification server. It is a flowchart explaining the process of a utilization condition information acquisition part. It is a 1st flowchart explaining the process of a priority provision part. It is a 2nd flowchart explaining the process of a priority provision part. It is a flowchart explaining the process of an authentication result determination part and a notification destination specific part. It is a flowchart explaining the process of a notification part and a retry process part. It is a flowchart explaining the reception process of notification confirmation. It is a 1st flowchart explaining the process of the information acquisition process part in a terminal device. It is a 2nd flowchart explaining the process of the information acquisition process part in a terminal device. It is a 1st flowchart explaining the process of the authentication process part in a terminal device. It is a 2nd flowchart explaining the process of the authentication process part in a terminal device.

  Embodiments will be described below with reference to the drawings. FIG. 1 is a first diagram illustrating a communication system according to the present embodiment.

  In the communication system 100 of the present embodiment, the incoming call notification server 200 is connected to, for example, a mail server 1, an SNS (Social Networking Service) server 2, a telephone server 3, and the like. In the communication system 100, the terminal devices 300-1, 300-2, 300-3, and 300-4 share account information and synchronize information between the terminal devices. That is, the terminal devices 300-1, 300-2, 300-3, and 300-4 are linked. In the following description, the terminal devices 300-1, 300-2, 300-3, and 300-4 are simply referred to as the terminal device 300 when not distinguished from each other.

  When the incoming notification server 200 of this embodiment receives a notification of an incoming call from any of the mail server 1, the SNS server 2, and the telephone server 3 to the terminal device 300, the user of the terminal device 300 becomes aware of the user. The terminal device 300 determined to be attached to is identified. Then, the incoming call notification server 200 notifies the specified terminal device 300 of the incoming call.

  More specifically, the incoming call notification server 200 according to the present embodiment receives the incoming call notification from the mail server 1, the SNS server 2, the telephone server 3, etc., for each terminal device 300, the user's biometric information and the terminal device. Usage status information including terminal status information indicating the status of 300 is acquired.

  Then, the incoming call notification server 200 determines whether the user is looking at the screen of the terminal device 300, whether the user is operating the terminal device 300, whether the user is holding the terminal device 300, based on the usage status information. The usage status of the terminal device 300 by the user, such as whether or not the terminal device 300 is worn, is determined.

  From these determination results, the incoming call notification server 200 gives priority to each terminal device 300 so that the priority of the terminal device 300 that the user seems to wear is high, and the priority is the highest. An incoming call is notified to the high terminal device 300.

  Therefore, in the present embodiment, an incoming call can be preferentially notified from the terminal device worn by the user and ringed. Note that the operation of the terminal device 300 when receiving an incoming call notification is not limited to ringing. The terminal device 300 that has received the incoming notification may ring, display a message indicating that there has been an incoming notification, or turn on the LED 37 according to the setting.

  Next, the communication system 100 of the present embodiment will be described with reference to FIG. FIG. 2 is a second diagram for explaining the communication system of the present embodiment.

  The communication system 100 according to the present embodiment includes an incoming call notification server 200 and terminal devices 300-1, 300-2, ..., 300-N. Each of the incoming call notification server 200 and the terminal devices 300-1, 300-2,..., 300-N is connected via a communication network or the like.

  The terminal devices 300-1 to 300-N of the present embodiment are grouped by common account information. In the example of FIG. 2, the number of groups of the terminal devices 300-1 to 300-N is one, but is not limited to this. The incoming call notification server 200 according to the present embodiment can communicate with an arbitrary number of groups of terminal devices.

  The incoming call notification server 200 of the present embodiment includes a user information table 210, a notification setting table 220, a device status table 230, a device information table 240, a notification destination device table 250, and an account table 260, and an incoming call notification processing unit 270. Have. The incoming call notification processing unit 270 of the present embodiment controls incoming calls for the terminal devices 300-1 to 300-N.

  Details of each table included in the incoming call notification server 200 and the incoming call notification processing unit 270 will be described later.

  The terminal device 300 according to the present embodiment includes an information acquisition processing unit 310 and an authentication processing unit 320. Further, the terminal device 300 has a log file 330. The information acquisition processing unit 310 acquires usage status information for each terminal device 300 in response to a request from the incoming notification server 200 and transmits the usage status information to the incoming notification server 200. The information acquisition processing unit 310 stores information indicating the state of the terminal device 300 in the log file 330 and holds the information.

  The authentication processing unit 320 performs authentication that identifies the user of the terminal device 300. In the present embodiment, for example, when the terminal device 300 is a smartphone, the user may be authenticated when an operation for releasing the screen lock of the smartphone is received.

  The log file 330 according to the present embodiment stores various events detected by the terminal device 300 in association with event occurrence times. The log file 330 according to the present embodiment may store, for example, events that occur during a predetermined number of seconds set in advance. In addition, various events of the present embodiment may occur when values are detected by various sensors included in the terminal device 300.

  Next, the hardware configuration of the incoming call notification server 200 and the terminal device 300 according to the present embodiment will be described with reference to FIGS. FIG. 3 is a diagram illustrating the hardware configuration of the incoming call notification server.

  The incoming call notification server 200 of the present embodiment includes a CPU (Central Processing Unit) 21, a communication device 22, an input device 23, a drive device 24, an output device 25, and a storage device 26, which are mutually connected by a bus.

  The CPU 21 controls the overall operation of the incoming call notification server 200. The communication device 22 is used for connecting to a communication network. The input device 23 is used for inputting various data. The input device 23 is, for example, a mouse or a keyboard. The output device 25 is used for outputting various data. The output device 25 is, for example, a display.

  The storage device 26 includes a RAM (Random Access Memory) 27, a ROM (Read Only Memory) 28, and a hard disk 29.

  The incoming call notification program is at least a part of various programs that control the incoming call notification server 200. The incoming call notification program is provided, for example, by distributing the recording medium 30 or downloading from the network. The recording medium 30 on which the incoming notification program is recorded is information such as a CD-ROM, a flexible disk, a magneto-optical disk, etc., a recording medium for recording information optically, electrically or magnetically, a ROM, a flash memory, etc. Various types of recording media, such as a semiconductor memory that electrically records data, can be used.

  When the recording medium 30 on which the incoming notification program is recorded is set in the drive device 24, the incoming notification program is installed in the ROM 28 from the recording medium 30 via the drive device 24. The communication program downloaded from the network is installed in the hard disk 29 via the communication device 22.

  The hard disk 29 stores the installed incoming notification program and also stores necessary files, data, and the like. The RAM 27 reads and stores an incoming call notification program from the hard disk 29 when the computer is started up. The CPU 22 implements various processes as will be described later in accordance with the incoming call notification program stored in the RAM 27.

  FIG. 4 is a diagram illustrating the hardware configuration of the terminal device.

  The terminal device 300 according to this embodiment includes a CPU 31, a communication device 32, a sensor 33, an acoustic device 34, a storage device 35, a display operation device 36, an LED (Light Emitting Diode) 37, and an imaging device 38.

  The CPU 31 controls the overall operation of the terminal device 300. The communication device 32 is used for connecting to a communication network.

  The sensor 33 includes an acceleration sensor 41, a gyro sensor 42, a temperature sensor 43, a pulse sensor 44, a proximity sensor 45, a touch sensor 46, and an electrostatic sensor 47. The acceleration sensor 41 detects the acceleration when the terminal device 300 moves. The gyro sensor 42 detects an angular velocity when the terminal device 300 is moving. The temperature sensor 43 detects the temperature of the terminal device 300. The pulse sensor 44 detects the pulse of a person wearing the terminal device 300. The proximity sensor 45 detects an object that is close to the display operation device 36 of the terminal device 300. The touch sensor 46 detects whether or not the display operation device 36 is being operated. The electrostatic sensor 47 detects whether or not the user is holding the terminal device 300.

  The acoustic device 34 is, for example, a speaker or a microphone. The storage device 35 has a RAM 48 and a ROM 49. The display operation device 36 has a display function and is used for data input. The display operation device 36 is, for example, a touch panel. The LED 37 may blink, for example, when an incoming call notification is received.

  The imaging device 38 includes an in camera 50 provided on the same surface as the display operation device 36 and an out camera 51 provided on a surface opposite to the surface provided with the display operation device 36.

  The CPU 31 reads out and executes a program stored in the ROM 49, thereby realizing various processes described later.

  Note that the sensor 33 illustrated in FIG. 4 is an example of the sensor included in the terminal device 300, and the terminal device 300 may not include all the sensors illustrated in FIG.

  Next, each table included in the incoming call notification server 200 according to this embodiment will be described with reference to FIGS.

  FIG. 5 is a diagram illustrating an example of the user information table. The user information table 210 of this embodiment is a table provided for each user. The user information table 210 according to the present embodiment includes an ID, a user name, a user ID, a user password, an unregistered device, and a related table ID as information items.

  The value of the item “ID” indicates a table ID for identifying the user information table 210. The value of the item “user name” indicates the name of the user, the value of the item “user ID” indicates the ID of the user, and the value of the item “user password” indicates the password of the user. . The user ID and user password of the present embodiment are used when logging in to a service provided by the communication system 100.

  The value of the item “unregistered device” indicates whether the user has a terminal device that is not registered in the incoming call notification server 200. The value of the item “related table ID” indicates the table ID of the notification setting table 220 related to the user information table 210 and the table ID of the device status table 230.

  FIG. 6 is a diagram illustrating an example of the notification setting table. The notification setting table 220 of the present embodiment is a table provided for each user, and indicates settings related to notification of incoming calls. The notification setting table 220 of this embodiment includes information items such as ID, notification destination setting, notification setting when status determination is not possible, retry time, maximum number of retries, re-notification setting after notification, user-specific notification setting, and usage. Person information table ID.

  The value of the item “ID” indicates a table ID for identifying the notification setting table 220. The value of the item “notification setting destination” indicates the terminal device 300 that notifies an incoming call. Specifically, the value of the item “notification setting destination” indicates whether all terminal devices 300 are notified of incoming calls or only the terminal devices 300 that are worn are notified.

  The value of the item “notification setting when state determination is impossible” indicates notification setting when the state of the terminal device 300 cannot be specified. Specifically, the value of the item “notification setting when status determination is not possible” indicates whether the incoming call notification is retried according to the specified retry time and the number of times, all devices are notified, or the specified terminal device 300 is notified. Whether to notify only. Note that the value of the item “notification setting when status determination is impossible” includes information specified by the terminal device 300 that is the notification destination.

  The value of the item “retry time” indicates a time until a retry is performed when a retry is designated. The value of the item “maximum retry count” indicates the maximum value of the number of times to retry.

  The value of the item “re-notification setting after notification” indicates whether or not re-notification is performed when the user has not confirmed the notification after notification of an incoming call.

  The value of the item “user specification notification setting” indicates whether a user is specified. Further, the value of the item “user specification notification setting” indicates whether or not to retry when the user cannot be specified. In this embodiment, for example, when the user is authenticated in the terminal device 300, the user is specified.

  The value of the item “user information table ID” indicates the table ID of the corresponding user information table 210.

  FIG. 7 is a diagram illustrating an example of the device state table. The device state table 230 of the present embodiment is provided for each terminal device 300, and includes identification information that identifies the terminal device 300, biometric information of the user, terminal state information that indicates the state of the terminal device 300, and the terminal device 300. And the priority given to.

  The device status table 230 of the present embodiment includes information items such as ID, ICCID (IC Card IDentifier), terminal IMEI (International Mobile Equipment Identity), user authentication status, temperature sensor status, gyroscope, acceleration sensor status, camera determination, It has a pulse sensor state, an electrostatic sensor state, a device liquid crystal screen state, a touch sensor utilization state, a proximity sensor state, a liquid crystal state, a busy state, and a determination result.

  In the device state table 230 of the present embodiment, the values of the items “ID”, “ICCID”, and “terminal IMEI” are identification information that identifies the terminal device 300.

  In the device state table 230, the items “user authentication state”, “temperature sensor state”, “gyro, acceleration sensor state”, “camera determination”, “pulse sensor state”, “electrostatic sensor state”, “device liquid crystal” Each value of “screen state”, “touch sensor use state”, “proximity sensor state”, “liquid crystal state”, and “busy state” is use state information.

  Furthermore, the values of the items “temperature sensor state”, “camera determination”, “pulse sensor state”, and “electrostatic sensor state” are biological information acquired from the user. In addition, each of the items “user authentication state”, “gyro and acceleration sensor state”, “device LCD screen state”, “touch sensor use state”, “proximity sensor state”, “liquid crystal state”, and “busy state” The value is terminal state information indicating the state of the terminal device 300.

  The value of the item “determination result” is a value indicating the priority of the terminal device 300.

  The value of the item “ID” indicates a table ID for identifying the device state table 230. The value of the item “ICCID” is identification information recorded on a SIM (Subscriber Identity Module) card. The value of the item “terminal IMEI” is a number unique to the terminal device 300.

  The value of the item “user authentication state” indicates the result of user authentication performed by the terminal device 300 and the date and time. That is, the value of the item “user authentication state” indicates whether or not the screen lock is released by the operation of releasing the screen lock of the terminal device 300 and the date and time when the operation was performed. When the value of the item “user authentication state” is “authenticated”, it indicates that the screen lock is released by the operation. When the value of the item “user authentication state” is “unauthenticated”, it indicates that the screen lock was not released by the operation.

  The value of the item “temperature sensor state” indicates the temperature detected by the temperature sensor. The value of the item “temperature sensor state” is used, for example, for determining whether or not the terminal device 300 is worn on the user's body.

  The value of the item “gyro, acceleration sensor state” indicates the inclination of the terminal device 300 obtained from the acceleration sensor 41 and the gyro sensor 42. The user's movement can be determined from the value of the acceleration sensor 41. The inclination is indicated by acceleration and rotational speed in the X, Y, and Z directions.

  The value of the item “camera determination” indicates a result of image analysis of whether a person is viewing the screen displayed on the display operation device 36 of the terminal device 300 using the imaging device 38 of the terminal device 300. The image analysis is, for example, face recognition processing. Specifically, when the value of the item “camera determination” is “recognition”, it indicates that the terminal device 300 has recognized the face of the person who is viewing the screen in the image of the imaging device 38. That is, this state indicates that the user is looking at the screen of the display operation device 36 of the terminal device 300. Similarly, when the value of the item “camera determination” is “recognition is impossible”, this indicates that the user is not viewing the screen of the display operation device 36 of the terminal device 300.

  The value of the item “pulse sensor state” indicates the number of pulses detected by the pulse sensor 44. The value of the item “pulse sensor state” is used, for example, for determining whether or not the terminal device 300 is worn on the user's body.

  The value of the item “electrostatic sensor state” is detected by the electrostatic sensor 47. The value of the item “electrostatic sensor state” indicates a determination result as to whether or not the user is holding (holding) the terminal device 300. The electrostatic sensor 47 is provided on the side surface of the terminal device 300.

  The value of the item “device liquid crystal screen state” indicates whether or not a screen is displayed on the display operation device 36. The value of the item “touch sensor usage state” indicates whether or not the display operation device 36 is used. Specifically, when the value of the item “touch sensor usage state” is “in use”, this indicates that the user is operating the display operation device 36 of the terminal device 300. In addition, when the value of the item “touch sensor use state” is “not used”, it indicates that the user is not operating the display operation device 36.

  The value of the item “proximity sensor state” indicates whether or not the proximity sensor 45 is operating. Specifically, when the value of the item “proximity sensor state” is ON, the proximity sensor 45 is operating, indicating that there is an object in proximity to the terminal device 300. When the value of the item “proximity sensor state” is OFF, it indicates that the operation of the proximity sensor 45 is stopped and there is no object close to the proximity sensor 45.

  The value of the item “liquid crystal state” indicates whether the liquid crystal screen of the terminal device 300 is lit or not lit.

  The value of the item “busy state” indicates whether the terminal device 300 is busy. For example, when the value of the item “busy state” is “busy” and the value of the item “proximity sensor state” is on, the user is talking with the terminal device 300 close to the ear. I know that there is. Further, when the value of the item “busy state” is “busy” and the value of the item “proximity sensor state” is off, for example, the user does not bring the terminal device 300 close to the ear and the speaker function or the like It turns out that it is in the state of using and calling.

  The value of the item “determination result” indicates the priority of the notification destination of the terminal device 300 given as a result of determination as a notification destination candidate in the incoming call notification server 200. The initial value of the item “judgment result” is 0.

  As described above, the usage status information of the present embodiment includes the user's biological information including the user's body temperature, pulse, face recognition processing result, capacitance change due to the user's hand, and the like. Furthermore, the usage status information of this embodiment includes terminal status information including an authentication result by the terminal device 300, a tilt and a moving speed of the terminal device 300, a display state of the screen in the display operation device 36, and whether or not the call function is used. including.

  FIG. 8 is a diagram illustrating an example of the device information table. The device information table 240 of this embodiment is provided for each terminal device 300. The device information table 240 of this embodiment includes, as information items, ID, device type, MAC (Media Access Control) address, terminal name, IP (Internet Protocol) address, user information table ID, and device status table ID. .

  The value of the item “ID” indicates a table ID for identifying the device information table 240. The value of the item “device type” indicates the type of the terminal device 300. Specifically, the value of the item “device type” indicates any one of a smartphone, a tablet computer, and a wearable terminal.

  The value of the item “MAC address” indicates the MAC address of the terminal device 300. The value of the item “terminal name” indicates the name of the terminal device 300. The value of the item “IP address” indicates the IP address of the terminal device 300. The value of the item “user information table ID” indicates the table ID of the corresponding user information table 210, and the value of the item “device state table ID” indicates the table ID of the corresponding device state table 230.

  FIG. 9 is a diagram illustrating an example of a notification destination device table. The notification destination device table 250 of this embodiment is provided for each terminal device 300. The notification destination device table 250 of this embodiment includes, as information items, a device information table ID, a notification completed flag, a retry count, a confirmed flag, and an initial notification flag.

  The value of the item “device information table ID” is the table ID of the device information table 240. The value of the item “notified flag” indicates whether an incoming call has been notified. Specifically, when the value of the “item“ notified flag ”is 1, it indicates that notification has been made, and when it is 0, it indicates that notification has not been made.

  The value of the item “number of retries” indicates the number of times the incoming notification has been retried. The value of the item “confirmed flag” indicates whether the user has confirmed the notification. Specifically, when the value of the item “confirmed flag” is 1, it indicates that it has been confirmed, and when it is 0, it indicates that it has not been confirmed. The value of the item “initial notification flag” indicates whether or not the incoming notification is the first time. Specifically, when the value of the item “initial notification flag” is 1, it indicates that it is the first time, and when it is 0, it indicates that it is not the first time.

  FIG. 10 is a diagram illustrating an example of an account table. The account table 260 of this embodiment is referred to in order to identify a user who has received an incoming call when the incoming call notification server 200 receives an incoming call notification request. The account table 260 of the present embodiment has a user ID, a user password, a telephone number, and a mail address as information items, and is associated with values indicated by the respective items.

  Next, the function of the incoming call notification server 200 of this embodiment will be described with reference to FIG. FIG. 11 is a diagram illustrating the function of the incoming call notification server.

  The incoming call notification server 200 of this embodiment includes an incoming call notification processing unit 270. The incoming call notification processing unit 270 is realized by the CPU 21 executing an incoming call notification program.

  The incoming call notification processing unit 270 of this embodiment includes a user registration unit 271, a usage status information acquisition unit 272, a priority assignment unit 273, a notification destination identification unit 274, an authentication result determination unit 275, a notification unit 276, and a retry processing unit 277. And a table updating unit 278.

  The user registration unit 271 of this embodiment performs user registration processing for the communication system 100 of this embodiment. The usage status information acquisition unit 272 performs processing for acquiring usage status information from each terminal device 300. The priority assigning unit 273 assigns a priority for each terminal device 300 according to the usage status information. The notification destination specifying unit 274 performs processing for specifying the terminal device 300 that is the notification destination of incoming calls based on the priority for each terminal device 300.

  The authentication result determination unit 275 performs processing for determining the result of user authentication in the terminal device 300. The notification unit 276 performs processing for notifying the terminal device 300 that has been identified of an incoming call. The retry processing unit 277 performs a process of retrying a process for notifying an incoming call notification. The table updating unit 278 updates each table included in the incoming call notification server 200.

  Next, the processing of the user registration unit 271 of the incoming call notification server 200 will be described with reference to FIG. FIG. 12 is a flowchart for explaining the process of the user registration unit.

  When receiving an incoming request from the terminal device 300 or a general computer (step S1201), the incoming call notification server 200 of the present embodiment displays an input screen for inputting a user ID and password on the terminal device 300 or the computer. Then, the incoming call notification server 200 determines whether or not the input user ID and password are registered by the user registration unit 271 (step S1202). More specifically, the user registration unit 271 determines whether there is a user information table 210 in which the user ID and password received together with the login request match.

  If it is registered in step S1202, the process proceeds to step S1207, which will be described later. If registration has not been completed in step S1202, the user registration unit 271 changes the screen to be displayed from the login screen to the user registration screen (step S1203). Subsequently, the user registration unit 271 issues a user ID and password on the user registration screen (step S1204).

  Subsequently, the incoming call notification server 200 creates the user information table 210 by using the table update unit 278, and updates the user ID and password (step S1205). Next, the table update unit 278 creates a notification setting table 220 associated with the user information table 210 (step S1206).

  Subsequently, the incoming call notification server 200 causes the user registration unit 271 to display a setting menu screen on the terminal device 300 or the computer that has made the login request (step S1207). The setting menu screen of the present embodiment may be, for example, a screen for selecting either the setting related to the terminal device 300, the setting related to use, or the end of the setting process.

  When the end of the setting process is selected on the menu screen (step S1208), the user registration unit 271 ends the user registration process.

On the menu screen,
When the setting related to use is selected (step S1208), the user registration unit 271 displays a use setting screen on the terminal device 300 or the computer that has made the login request (step S1209). The usage setting screen of the present embodiment may be, for example, a screen that allows the user information to be updated or the notification destination setting to be updated.

  When update of user information is selected on the use setting screen (step S1210), the table updating unit 278 updates the user information table 210 according to the setting content (step S1211), and the process returns to step S1208.

  When update of the notification destination setting is selected on the usage setting screen (step S1210), the table update unit 278 updates the value of each item of the notification setting table 220 according to the setting content (step S1212), and step The process returns to S1208.

  When the setting related to the terminal device 300 is selected on the menu screen (step S1208), the user registration unit 271 displays the registration / update screen of the terminal device 300 on the terminal device 300 or the computer that has made the login request. (Step S1213).

  The registration / update screen of the present embodiment may be, for example, a screen for selecting either registration of a new terminal device 300 or update of information of the terminal device 300.

  When updating of information of the terminal device 300 is selected on the registration / update screen (step S1214), the user registration unit 271 accepts a change to the value of the item included in the device information table 240 (step S1215). Subsequently, the table update unit 278 updates the device information table 240 in accordance with the accepted change (step S1216), and proceeds to step S1208.

  When registration of the terminal device 300 is selected on the registration / update screen (step S1214), the user registration unit 271 acquires a device type and a terminal name input by the user. In addition, the user registration unit 271 acquires the MAC address transmitted from the terminal device 300 (step S1217).

  Subsequently, the table update unit 278 creates the device information table 240 and sets the table ID of the user information table 210 to the value of the user information table ID of the device status table (step S1218). At this time, the table updating unit 278 may store the value acquired in step S1216 in the device information table 240.

  Subsequently, the table updating unit 278 creates a device state table 230 associated with the registered terminal device 300 (step S1219), and the process proceeds to step S1208.

  In the present embodiment, the user information table 210, the notification setting table 220, and the device information table 240 are created by the above processing.

  Next, the overall operation of the incoming call notification server 200 of this embodiment will be described with reference to FIG.

  FIG. 13 is a flowchart for explaining the overall operation of the incoming call notification server. Note that the processing in FIG. 11 is processing for notifying the terminal device 300 of the user who has been registered by the user registration unit 271 of the incoming call.

  The incoming call notification server 200 of this embodiment acquires usage status information from each terminal device 300 by the usage status information acquisition unit 272 (step S1301). Subsequently, the incoming call notification server 200 executes a process of assigning a priority for each terminal device 300 according to the usage status information by the priority assigning unit 273 (step S1302).

  Next, the incoming call notification server 200 determines the result of user authentication by the terminal device 300 using the authentication result determination unit 275, and the terminal that is the notification destination of incoming calls according to the authentication result using the notification destination specifying unit 274. The device 300 is specified (step S1303).

  Subsequently, the incoming call notification server 200 notifies the specified terminal device 300 of the incoming call by the notification unit 276 (step S1304).

  Details of each step shown in FIG. 13 will be described below. FIG. 14 is a flowchart illustrating the processing of the usage status information acquisition unit. The process of FIG. 14 shows the details of the process of step S1301 of FIG.

  The incoming call notification server 200 of this embodiment accepts incoming call notification requests from various servers (step S1401). The various servers include, for example, a mail server 1, an SNS (Social Networking Service) server 2, a telephone server 3, and the like.

  Subsequently, the incoming call notification server 200 uses the usage status information acquisition unit 272 to refer to the account table 260 to identify the user ID to be notified, and acquires the user information table 210 corresponding to the identified user ID. (Step S1402).

  Next, the usage status information acquisition unit 272 acquires a device information table 240, a notification destination device table 250, and a device status table 230 related to the user information table 210 from the user information table 210 (step S1403). Specifically, the usage status information acquisition unit 272 acquires the device information table 240 including the ID of the user information table 210, and acquires the notification destination device table 250 having the ID of the device information table 240. In addition, the usage status information acquisition unit 272 acquires the device status table 230 whose ID matches the device status table ID included in the user information table 210.

  Subsequently, the usage status information acquisition unit 272 initializes the device status table 230 and the notification destination device table 250 (step S1404).

  Subsequently, the usage status information acquisition unit 272 determines whether or not an unregistered terminal device 300 is detected (step S1405). More specifically, the usage status information acquisition unit 272 receives identification information for identifying the terminal device 300 from the terminal device 300, and the ICCID value and the terminal IMEI value are stored in the device state table 230. It is determined whether there is a terminal device 300 that is not present.

  If an unregistered terminal device 300 is not detected in step S1405, the process proceeds to step S1408 described later.

  When the unregistered terminal device 300 is detected in step S1405, the table update unit 278 sets the value of the unregistered device in the user information table 210 to “present” (step S1406). Subsequently, the notification unit 276 notifies the unregistered terminal device 300 of the incoming call (step S1407). Note that the notification unit 276 of the present embodiment may transmit an email urging the user to register an unregistered terminal device 300.

  Subsequently, the usage status information acquisition unit 272 determines whether or not the notification destination setting value is “notify all devices” in the notification setting table 220 associated with the user information table 210 (step S1408). ).

  If “notify all devices” is set in step S1408, the notification unit 276 notifies all terminal devices 300 of the incoming call, and proceeds to an end process (step S1409). The usage status information acquisition unit 272 initializes the device status table 230 and the notification destination device table as end processing (step S1410), and ends the processing.

  If “notify to all devices” is not set in step S1408, the usage status information acquisition unit 272 issues a usage status information acquisition request to all the terminal devices 300 registered in the device information table 240 (step S1411). ).

  Subsequently, the usage status information acquisition unit 272 receives items from the terminal device 300 that are included in the device status table 230, such as a user authentication status, a temperature sensor status, a gyroscope, an acceleration sensor status, a camera determination, a pulse sensor status, and an electrostatic sensor. Each value of the state, the device liquid crystal screen state, the touch sensor use state, the proximity sensor state, the liquid crystal state, and the busy state is acquired (step S1412).

  Subsequently, the usage status information acquisition unit 272 stores the acquired value in the device status table 230 associated with the device information table 240 corresponding to the terminal device 300 for each terminal device 300 (step S1413). Subsequently, the incoming call notification server 200 ends the process of the usage status information acquisition unit 272 and proceeds to a process of determining the usage status of each terminal device 300 (step S1414), and thus proceeds to step S1501 of FIG.

  FIG. 15 is a first flowchart illustrating the processing of the priority assigning unit. The process shown in FIG. 15 shows the details of the process in step S1302 of FIG.

  Whether or not the incoming call notification server 200 according to the present embodiment has executed the processing after step S1502 described later for all the registered terminal devices 300 by the priority assigning unit 273 following step S1414 in FIG. Is determined (step S1501).

  If the process is executed for all the terminal devices 300 in step S1501, the incoming call notification server 200 proceeds to step S1601 in FIG.

  In step S1501, when the processing is not executed for all the terminal devices 300, the priority notification unit 200 sets the value of the item “camera determination” in the device state table 230 to “recognition” by the priority assignment unit 273. It is determined whether or not (step S1502). That is, the priority assigning unit 273 determines whether the user is looking at the terminal device 300.

  In step S1502, if “not recognized”, the priority level assigning unit 273 proceeds to step S1504 described later.

  If “recognition” is obtained in step S1502, the priority assigning unit 273 adds 1000 to the initial value of the item “determination result” in the device state table 230 (step S1503).

  Subsequently, the priority assigning unit 273 determines whether or not the value of the item “touch sensor use state” in the device state table 230 is “in use” (step S1504). That is, the priority assigning unit 273 determines whether or not the user of the terminal device 300 is operating the touch panel of the terminal device 300.

  If it is not “in use” in step S1504, the priority assigning unit 273 proceeds to step S1506, which will be described later.

  If “in use” in step S1504, the priority assigning unit 273 adds 100 to the value of the item “determination result” in the device state table 230 (step S1505).

  Subsequently, the priority assigning unit 273 determines whether or not the value of the item “electrostatic sensor state” in the device state table 230 is “holding the terminal device” (step S1506). If it is not “holding the terminal device” in step S1506, the priority level assigning unit 273 proceeds to step S1508, which will be described later.

  When “holding the terminal device” is set in step S1506, the priority assigning unit 273 adds 10 to the value of the item “determination result” in the device state table 230 (step S1507).

  Subsequently, the priority assigning unit 273 detects the tilt of the terminal device 300 from the value of the item “gyro / acceleration sensor state” of the device state table 230, and the value of the item “device liquid crystal screen state” is turned on. It is determined whether or not (step S1508). That is, the priority assigning unit 273 determines whether or not the terminal device 300 is inclined and the screen is displayed on the display / operation device 36. The case where the terminal device 300 is inclined and the screen is displayed is, for example, the case where the screen is displayed on the display operation device 36 of the terminal device 300 leaning on a stand or the like.

  In step S1508, when the condition that there is an inclination and the screen is displayed is satisfied, the priority assigning unit 273 returns to step S1507.

  In step S1508, when the condition that there is an inclination and the screen is displayed is not satisfied, the priority assigning unit 273 proceeds to step S1509.

  The priority assigning unit 273 can detect the value of the item “pulse sensor” in the device state table 230, and can acquire the value of the pulse sensor from 5 seconds before the usage status information acquisition request is transmitted to the terminal device 300. It is determined whether or not it can be performed (step S1509). That is, the priority assigning unit 273 determines whether or not the user's pulse can be detected from 5 seconds before the timing at which the usage status information acquisition request is transmitted to the terminal device 300. In the present embodiment, by providing a period for detecting a pulse (5 seconds), the pulse sensor 44 temporarily detects a pulse for some reason, and the user is wearing the terminal device 300. Can be distinguished. The period for detecting the pulse is not limited to 5 seconds, and may be any period as long as the above-described distinction can be made.

  In step S1509, when the value of the pulse sensor 44 can be acquired, the priority assigning unit 273 adds 1 to the value of the item “determination result” in the device state table 230 (step S1510).

  If the value of the pulse sensor 44 can be acquired in step S1509, the priority assigning unit 273 proceeds to step S1511 described later.

  The priority assigning unit 273 determines whether the value of the item “temperature sensor” in the device state table 230 can be acquired and the temperature is within a predetermined range set in advance (step S1511). Here, the predetermined range set in advance is a temperature range that is close to a human body temperature. That is, the priority assigning unit 273 determines whether or not the terminal device 300 is worn on the user's body.

  In step S1511, if the condition that the value of the temperature sensor 43 can be detected and the value is within the predetermined range is satisfied, the process proceeds to step S1510. In step S1511, when the value of the temperature sensor 43 can be detected and the condition that the value is within the predetermined range is not satisfied, the process proceeds to step S1512 described later.

  The priority assigning unit 273 can detect the value of the item “acceleration sensor” in the device state table 230 and detect the user's running or walking until five minutes before the usage status information acquisition request is transmitted to the terminal device 300. It is determined whether or not it is possible (step S1512). That is, the priority assigning unit 273 determines whether or not the user has been walking or running from 5 minutes before receiving the usage status information acquisition request. In the present embodiment, by providing a period (5 minutes) for detecting walking or running, the user is moving while wearing the terminal device 300 when the acceleration sensor 41 detects a temporary movement. Can be distinguished from the case. In addition, 5 minutes is an example, and the period for detecting walking or running may be a period in which the above-described distinction can be performed.

  In step S1512, when the value of the acceleration sensor 41 can be acquired and the condition that the user is walking or running from 5 minutes before receiving the usage status information acquisition request is satisfied, the priority assigning unit 273 determines whether or not the step S1510 Proceed to

  In step S1512, when the value of the acceleration sensor 41 can be acquired and the condition that the user is walking or running from 5 minutes before receiving the usage information acquisition request is not satisfied, the priority assigning unit 273 Terminal device 300 is selected (step S1513), and the process returns to step S1501.

  FIG. 16 is a second flowchart illustrating the processing of the priority assigning unit. The process of FIG. 16 performs a process of lowering the priority of the terminal device 300 than the other terminal devices 300 when the terminal device 300 is busy. In the present embodiment, by performing this process, it is avoided that the terminal device 300 that is in a state where it is difficult to confirm an incoming call during a call is selected as a notification destination of the incoming call.

  In step S1501 of FIG. 15, when the processing after step S1502 is completed for all the terminal devices 300, the priority assigning unit 273 determines whether the processing after step S1602 has been performed for all the terminal devices 300. (Step S1601).

  In step S1601, if all the terminal devices 300 perform the processing from step S1602 onward, the incoming call notification server 200 proceeds to step S1701 in FIG.

  In step S1601, when the processing after step S1602 is not performed, the priority assigning unit 273 has the value of the item “determination result” of the device state table 230 corresponding to the terminal device 300 to be processed being 10 or more. It is determined whether or not (step S1602). When the value of the item “judgment result” is 10 or more, the usage status of the terminal device 300 by the user includes at least one of “watching”, “having”, and “operating” It is.

  In step S1602, when the value of the item “determination result” is not 10 or more, the priority assigning unit 273 selects another terminal device 300 (step S1603), and returns to step S1601.

  In step S1602, when the value of the item “determination result” is 10 or more, the priority level assigning unit 273 indicates that the value of the item “proximity sensor state” in the device state table 230 is “on” and the item “busy” It is determined whether or not the value of “status” is “ON” (step S1604). That is, the priority assigning unit 273 determines whether or not the user is talking on the terminal device 300.

  If it is determined in step S1604 that the call is not in progress, the priority assigning unit 273 proceeds to step S1603. In step S1604, when a call is in progress, the priority assigning unit 273 has a value of 1 or more for the item “determination result” in the device state table 230 corresponding to the terminal device 300 other than the terminal device 300 that is the processing target. It is determined whether or not (step S1605). That is, the priority assigning unit 273 determines whether there is a terminal device 300 to which priority is given in addition to the terminal device 300 to be processed.

  In step S1605, when there is no other terminal device 300 to which priority is given, the priority assignment unit 273 proceeds to step S1603.

  In step S <b> 1605, when there is another terminal device 300 to which priority is given, the priority assignment unit 273 displays the item “in the device state table 230 of the terminal device 300 to be processed (terminal device 300 during a call)”. The value of “judgment result” is set to 0 (step S1606), and the process proceeds to step S1603. That is, the priority assigning unit 273 lowers the priority of the terminal device 300 during a call compared to the other terminal devices 300.

  FIG. 17 is a flowchart illustrating the processing of the authentication result determination unit and the notification destination specifying unit. The process of FIG. 17 shows the details of the process of step S1303 of FIG.

  In the incoming call notification server 200 according to the present embodiment, when the notification destination specifying unit 274 satisfies the condition of step S1601 in FIG. 16, the device status table 230 associated with the user information table 210 is stored in the item “determination result”. The values are arranged in descending order (step S1701). Subsequently, the notification destination specifying unit 274 provides a variable n and sets n = 0 (step S1702).

  Subsequently, the notification destination specifying unit 274 compares the value of the item “device information table ID” of the notification destination device table 250 associated with the user information table 210 or compares all the device state tables 230. It is determined whether or not (step S1703).

  If the condition is satisfied in step S1703, the process proceeds to step S1801 in FIG.

  If the condition is not satisfied in step S1703, the notification destination specifying unit 274 refers to the nth device state table 230 from the top of the device state table 230 rearranged in step S1701 (step S1704).

  Subsequently, the notification destination specifying unit 274 determines whether or not the value of the item “user specification notification setting” in the notification setting table 220 associated with the user information table is “use” (step S1705). ).

  If it is not “use” in step S1705, the notification destination specifying unit 274 proceeds to step S1707 described later.

  If “use” is determined in step S1705, the authentication result determination unit 275 determines whether the value of the item “user authentication state” in the device state table 230 is “authenticated” (step S1706).

  If “authenticated” in step S 1706, the notification destination specifying unit 274 matches the value of the item “device information table ID” of the notification destination device table 250 with the device information associated with the nth device state table 230. The ID of the table 240 is set (step S1707).

  In the present embodiment, in the process of step S1707, the device that is the notification destination of the incoming call is specified as the terminal device 300 corresponding to the device information table 240.

  If it is not “authenticated” in step S1706, the notification destination specifying unit 274 holds information indicating that there is an unauthenticated terminal device 300 in the storage area (step S1708).

  Subsequently, the notification destination specifying unit 274 adds 1 to the value of the variable n (step S1709) and returns to step S1703.

  As described above, the incoming call notification server 200 according to this embodiment includes the terminal device 300 having the largest value of the item “evaluation result” in the device state table 230 indicating the priority of each terminal device 300 among the plurality of terminal devices 300. Is identified as the terminal device 300 that is the notification destination. Furthermore, when using the authentication result in the terminal device 300, the incoming call notification server 200 of the present embodiment has the largest item “evaluation result” among the terminal devices 300 that have been authenticated by the user. The device 300 is identified as the notification destination terminal device 300.

  FIG. 18 is a flowchart for explaining processing of the notification unit and the retry processing unit. FIG. 18 shows details of the processing in step S1304 shown in FIG.

  When the condition of step S1703 in FIG. 17 is satisfied, the incoming call notification server 200 according to the present embodiment determines whether or not the value of the item “device information table ID” of the notification destination device table 250 is set by the notification unit 276. (Step S1801). If it is not set in step S1801, the process proceeds to step S1805 described later.

  If it is set in step S1801, the notification unit 276 notifies the terminal device 300 identified from the device information table 240 corresponding to the value of the item “device information table ID” (step S1802). Subsequently, the notification unit 276 sets the value of the item “notified flag” in the notification destination device table 250 to “notified” (step S1803). At this time, the notification unit 276 sets the value of the item “initial notification flag” to “1”.

  Subsequently, the notification unit 276 determines whether or not the value of the item “Re-notification after notification” is “Re-notify” in the notification setting table 220 associated with the user information table 210 ( Step S1804). If “notify again” is not set in step S1804, the process proceeds to step S1812 described below.

  If “notify again” in step S1804, the retry processing unit 277 determines whether or not the value of the item “first notification flag” in the notification destination device table 250 is 1 (step S1805). That is, the retry processing unit 277 determines whether or not the notification performed in step S1802 is the first notification.

  If the value of the item “initial notification flag” is 1 in step S 1805, the retry processing unit 277 sets the item “maximum retry count” in the notification setting table 220 to the value of the item “retry count” in the notification destination device table 250. Set the value of. Then, the retry processing unit 277 sets the value of the item “initial notification flag” in the notification destination device table 250 to 0 (step S1806), and proceeds to step S1808 described later.

  In step S1805, when the value of the item “initial notification flag” is not 1, the retry processing unit 277 sets and sets the value of the item “retry time” of the notification setting table 220 in the timer of the incoming call notification server 200. Retry processing is performed after the retry time (step S1807). The retry process of the present embodiment is a process of notifying the specified terminal device 300 again.

  Subsequently, the retry processing unit 277 sets the value of the item “device information table ID” in the notification destination device table 250, the value of the item “retry count” is 1 or more, and the item “confirmed flag”. It is determined whether or not the value of 0 is 0 (unconfirmed) (step S1808). In step S1808, it is determined whether the user has not confirmed the notification even though the notification retry process is performed once or more for the identified terminal device 300.

  If the condition is satisfied in step S1808, the retry processing unit 277 notifies the terminal device 300 specified by the device information table 240 corresponding to the value of the item “device information table ID” in the notification destination device table 250 (step S1808). S1809).

  Subsequently, the retry processing unit 277 subtracts 1 from the value of the item “number of retries” in the notification destination device table 250 (step S1810). Then, the incoming call notification server 200 proceeds to step S1411 in FIG. 14, and returns to the process of acquiring usage status information.

  In other words, the incoming call notification server 200 according to the present embodiment specifies the terminal device 300 that is the notification destination based on the usage status information when the notification is not confirmed despite the incoming call notification retry process being performed in the terminal device 300. Repeat from the process to do.

  If the condition is not satisfied in step S1808, the retry processing unit 277 determines whether the value of the item “retry count” in the notification destination device table 250 is 0 (step S1811). In step S1811, when the value of the item “retry count” is 0, the incoming call notification server 200 initializes the device state table 230 and the notification destination device table 250 (step S1812), and ends the process of notifying the incoming call.

  If the value of the item “number of retries” is not 0 in step S1811, the retry processing unit 277 determines whether information indicating the terminal device 300 that has not been authenticated is stored in the storage area (step S1813). .

  If the information indicating the terminal device 300 that has not been authenticated is stored in the storage area in step S1813, the retry processing unit 277 determines that the value of the item “user authentication status” in the device status table 230 is “unauthenticated”. The apparatus 300 is notified of the authentication request (step S1814), and the process proceeds to step S1810.

  The setting of the value of the item “confirmed flag” in the notification destination device table 250 will be described below with reference to FIG. FIG. 19 is a flowchart for explaining notification confirmation reception processing.

  The table updating unit 278 of this embodiment receives a notification indicating that the notification has been confirmed from the terminal device 300 that has made the notification after transmitting the notification of the incoming call from the incoming notification server 200 to the terminal device 300 (step S1901).

  Subsequently, when receiving a confirmed notification from the terminal device 300, the table updating unit 278 changes the value of the notification destination device table item “confirmed flag” from “0” to “1” (step S1902).

  As described above, the incoming call notification server 200 according to the present embodiment, when the notification is not confirmed in the terminal device 300 that has notified the incoming call, again after the retry time set in the notification setting table 220. Retry from the process specified by the terminal device 300. Therefore, in this embodiment, it can suppress that a user misses the notification of an incoming call.

  The incoming call notification server 200 according to the present embodiment makes an authentication request to the terminal device 300 when the user authentication is not performed in the terminal device 300. Therefore, in the present embodiment, an incoming call can be notified after the user is authenticated in the terminal device 300, and the incoming call can be prevented from being notified to anyone other than the user of the terminal device 300.

  Next, processing on the terminal device 300 side of the present embodiment will be described. FIG. 20 is a first flowchart illustrating the process of the information acquisition processing unit in the terminal device.

  When receiving the usage status information acquisition request from the incoming call notification server 200, the terminal device 300 according to the present embodiment acquires the value of each item included in the usage status information by the information acquisition processing unit 310 and sends it to the incoming call notification server 200. Send.

  In the terminal device 300 of the present embodiment, the information acquisition processing unit 310 receives a usage status information acquisition request from the incoming call notification server 200 (step S2001).

  The processing from step S2002 to step S2006 described next is processing in which the terminal device 300 transmits the value of the item “camera determination” in the device state table 230 to the incoming call notification server 200.

  The information acquisition processing unit 310 acquires image data with the in-camera 50 provided in the terminal device 300 (step S2002). Subsequently, the information acquisition processing unit 310 starts processing for recognizing a human face from the acquired image data (step S2003). The process for recognizing a human face is a known face recognition process or the like.

  Subsequently, the information acquisition processing unit 310 determines whether or not a human face can be recognized from the image data (step S2004). If the information acquisition processing unit 310 recognizes it in step S2004, the value “recognition” is set as a value to be transmitted to the incoming call notification server 200 (step S2005).

  If it is not recognition in step S2004, the information acquisition processing unit 310 sets the value “unrecognized” as a value to be transmitted to the incoming call notification server 200 (step S2006).

  The processing from step S2007 to step S2010 described below is processing in which the terminal device 300 transmits the value of the item “electrostatic sensor state” in the device state table 230 to the incoming call notification server 200.

  The information acquisition processor 310 acquires the capacitance value of the electrostatic sensor 47 (step S2007). Subsequently, the information acquisition processing unit 310 determines whether or not the capacitance exceeds a predetermined threshold (step S2008).

  When the threshold value is exceeded in step S2008, the information acquisition processing unit 310 sets the value “holding the terminal” as a value to be transmitted to the incoming call notification server 200 (step S2009).

  In step S2008, when the threshold value is not exceeded, the information acquisition processing unit 310 sets a value “not holding the terminal” as a value to be transmitted to the incoming call notification server 200 (step S2010).

  The processing from step S2011 to step S2012 to be described next is processing in which the terminal device 300 transmits the value of the item “touch sensor state” in the device state table 230 to the incoming call notification server 200.

  The information acquisition processing unit 310 refers to the log file 330 and determines whether or not the touch panel event of the display operation device 36 has been recorded in the past 5 seconds (step S2011). If an event is recorded in step S2011, the information acquisition processing unit 310 sets the value “in use” as a value to be transmitted to the incoming call notification server 200 (step S2012).

  When no event is recorded in step S2011, the information acquisition processing unit 310 sets the value “not used” as a value to be transmitted to the incoming call notification server 200 (step S2013). In this embodiment, since the log file for the past 5 seconds is referred to, for example, when the user accidentally touches the touch panel, a short-time contact is prevented from being erroneously determined as “in use”. it can.

  The processing from step S2014 to step S2016 described next is processing in which the terminal device 300 transmits the values of other items in the device state table 230 to the incoming call notification server 200.

  The information acquisition processing unit 310 refers to the log file 330, acquires the values of the acceleration sensor 41 and the gyro sensor 42 for the past 5 seconds, and sets the values to be transmitted to the incoming call notification server 200 (step S2014).

  Subsequently, the information acquisition processing unit 310 obtains information indicating whether the liquid crystal screen is lit or not lit, information indicating whether the terminal device 300 is busy, the value of the pulse sensor 44, and the value of the temperature sensor 43. Each is acquired and set as a value to be transmitted to the incoming call notification server 200 (step S2015).

Subsequently, when the terminal device 300 has authenticated the user within 24 hours, the information acquisition processing unit 310 sets the value “authenticated” as a value to be transmitted to the incoming call notification server 200. Further, the information acquisition processing unit 310 sets the value “unauthenticated” to the incoming call notification server 200 when the user is not authenticated within 24 hours or when the screen lock of the terminal device 300 is not released. To be transmitted (step S2016).
Subsequently, the information acquisition processing unit 310 transmits the value transmitted to the incoming call notification server 200 acquired in each step to the incoming call notification server 200 (step S2017).

  The terminal device 300 according to the present embodiment transmits the usage status information to the incoming call notification server 200 through the above processing.

  Next, generation in the log file 330 by the information acquisition processing unit 310 in the terminal device 300 will be described. FIG. 21 is a second flowchart illustrating the process of the information acquisition processing unit in the terminal device.

  The information acquisition processing unit 310 according to the present embodiment determines whether or not the terminal device 300 is powered off (step S2101). In step S2101, when the power is turned off, the information acquisition processing unit 310 ends the process.

  In step S2101, when the power is not turned off (when the power is turned on), the information acquisition processing unit 310 waits for an event signal from the touch panel, the acceleration sensor 41, and the gyro sensor 42 provided in the display operation device 36 ( Step S2102).

  The information acquisition processing unit 310 determines whether an event has been received from the touch panel (step S2103). Note that the event in step S2103 is that the touch panel detects contact with the touch panel.

  If an event is received in step S2103, the information acquisition processing unit 310 writes the event information on the touch panel and the time when the event is received (event occurrence time) in the log file 330 (step S2104). The event information is information indicating that an event has occurred on the touch panel.

  If no event is received in step S2103, the information acquisition processing unit 310 determines whether or not an event has been received from the acceleration sensor 41 and the gyro sensor 42 (step S2105). If an event is received in step S2105, the information acquisition processing unit 310 stores the values acquired from the acceleration sensor 41 and the gyro sensor 42 and the event occurrence time in the log file 330 (step S2106).

  If no event is received in step S2105, the information acquisition processing unit 310 determines whether or not the size of the log file 330 exceeds a prescribed size (step S2107).

  If the specified size is exceeded in step S2107, the information acquisition processing unit 310 leaves the event from the current time to 5 seconds before and deletes the previous event and event occurrence time data (step S2108). In this embodiment, the time is 5 seconds ago, but the amount of data left in the log file 330 is not limited to this. The log file 330 of the present embodiment has an amount of data that can be used to determine whether the event that has occurred is caused by the use of the user's terminal device 300 or is caused by an erroneous operation or an accident. It only has to be stored.

  If the specified size is not exceeded in step S2107, the information acquisition processing unit 310 waits until there is a next event (step S2109), and returns to step S2101.

  Next, processing of the authentication processing unit 320 in the terminal device 300 will be described. FIG. 22 is a first flowchart illustrating the processing of the authentication processing unit in the terminal device. FIG. 22 illustrates processing of the authentication processing unit 320 when the terminal device 300 receives an authentication request from the incoming call notification server 200 when the terminal device 300 is a smartphone or a tablet-type terminal.

  The terminal device 300 receives an authentication request from the incoming call notification server 200 (step S2201). Subsequently, the terminal device 300 performs authentication by the authentication processing unit 320 (step S2202). Specifically, the authentication processing unit 320 receives a screen lock release operation by the user and performs a screen lock release process. Subsequently, the authentication processing unit 320 determines whether or not the user has been authenticated (step S2203).

  If the user is not authenticated in step S2203, the next time the usage status information acquisition request is received, the value of “unauthenticated” is set as a value to be transmitted to the incoming call notification server 200 (step S2204), and the process is terminated. .

  When the usage status information is authenticated in step S2203, the authentication processing unit 320 transmits the authentication result as “authenticated” to the incoming call notification server 200 (step S2205). Subsequently, the terminal device 300 receives a notification of an incoming call that has been put on hold in the incoming call notification server 200 (step S2206), and ends the process.

  FIG. 23 is a second flowchart illustrating the processing of the authentication processing unit in the terminal device. FIG. 23 shows processing of the authentication processing unit 320 when the terminal device 300 receives an authentication request from the incoming call notification server 200 when the terminal device 300 is a wearable terminal.

  The terminal device 300 acquires the value of the temperature sensor 43 or the pulse sensor 44 by the information acquisition processing unit 310 (step S2301). Subsequently, the terminal device 300 determines whether or not the value acquired in step S2301 has changed to a value within a predetermined range by the authentication processing unit 320 (step S2302). The predetermined range is a range that is close to a human body temperature or a human pulse, and is a preset range.

  In step S2302, when the value changes to a value within the predetermined range, the authentication processing unit 320 determines that the user has started wearing the terminal device 300, and requests authentication from the user (step S2303). Then, the process proceeds to step S2305 to be described later.

  If it does not change within the predetermined range in step S2302, the authentication processing unit 320 determines that the user is not wearing the terminal device 300, and sets the authentication result of the terminal device 300 to “unauthenticated” (step S2302). S2304).

  Subsequently, when the user authenticates, the authentication processing unit 320 sets the authentication result as a value to be transmitted to the incoming call notification server 200 when receiving a use status information acquisition request next time (step S2305).

  In the present embodiment, when the terminal device 300 is a wearable terminal, by performing processing as shown in FIG. 23, the user is requested to authenticate when the terminal device 300 is mounted, and the user When the terminal device 300 is not attached, the terminal device 300 is not authenticated. Therefore, when the user does not wear the terminal device 300, the terminal device 300 can be prevented from being left in an authenticated state, and confidentiality can be maintained.

In the disclosed technology, forms such as the following supplementary notes are conceivable.
(Appendix 1)
An incoming call notification method by a computer, wherein the computer
Collecting usage status information including any one of biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices,
An incoming call notification method for determining a terminal device that notifies an incoming call based on the usage status information and notifying the determined terminal device.
(Appendix 2)
The computer is
In accordance with the usage status information, calculate a priority for each terminal device,
The incoming call notification method according to appendix 1, wherein the terminal apparatus having the highest priority is determined as a terminal apparatus that notifies the incoming call.
(Appendix 3)
The computer is
Based on the usage status information, whether the user is looking at the screen of the terminal device, whether the user is operating the terminal device, whether the user is holding the terminal device, Whether or not the user wears the terminal device, and determines the usage status of the terminal device by the user,
The incoming call notification method according to supplementary note 2, wherein the priority is calculated according to a result of the determination.
(Appendix 4)
The computer is
Based on the usage status information, it is determined whether or not user authentication is performed in the terminal device with the highest priority,
When the user is authenticated, the terminal device with the highest priority is determined as the terminal device that notifies the incoming call,
If the user is not authenticated, the terminal device having the second highest priority next to the terminal device having the highest priority is determined as the terminal device that notifies the incoming call. The incoming call notification method described.
(Appendix 5)
The computer is
The priority of the terminal device that is determined that the user is holding the terminal device and the call function is in use based on the usage status information is made lower than the priority of the other terminal devices. Or the incoming call notification method of 4.
(Appendix 6)
The biological information is
Information indicating the temperature of the terminal device, information indicating the pulse of the user of the terminal device, information indicating a result of performing the face recognition process of the user by the terminal device, static information provided on the side of the terminal device Including information indicating the change in capacitance,
The terminal status information is
Information indicating the result of the user authentication process by the terminal device, information indicating the tilt of the terminal device, information indicating the moving speed of the terminal device, and display state of the screen on the display operation device of the terminal device The incoming call notification method according to any one of appendices 1 to 5, which includes information and information indicating whether or not the call function of the terminal device is used.
(Appendix 7)
Collecting usage status information including any one of biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices,
An incoming call notification program for causing a computer to execute a process of determining a terminal device to notify an incoming call based on the usage status information and notifying the determined terminal device.
(Appendix 8)
A usage status information acquisition unit that collects usage status information including biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices;
An incoming call notification device comprising: a notification unit that determines a terminal device that notifies an incoming call based on the usage status information and notifies the determined terminal device.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

DESCRIPTION OF SYMBOLS 100 Communication system 200 Incoming notification server 210 User information table 220 Notification setting table 230 Device status table 240 Device information table 250 Notification destination device table 260 Account table 270 Incoming notification processing unit 272 Usage status information acquisition unit 273 Priority assignment unit 274 Notification Point identification unit 275 Authentication result determination unit 276 Notification unit 277 Retry processing unit 300 Terminal device 310 Information acquisition processing unit 320 Authentication processing unit 330 Log file

Claims (5)

  1. An incoming call notification method by a computer, wherein the computer
    Collecting usage status information including any one of biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices,
    An incoming call notification method for determining a terminal device that notifies an incoming call based on the usage status information and notifying the determined terminal device.
  2. The computer is
    In accordance with the usage status information, calculate a priority for each terminal device,
    The incoming call notification method according to claim 1, wherein the terminal apparatus having the highest priority is determined as a terminal apparatus that notifies the incoming call.
  3. The computer is
    Based on the usage status information, whether the user is looking at the screen of the terminal device, whether the user is operating the terminal device, whether the user is holding the terminal device, Whether or not the user wears the terminal device, and determines the usage status of the terminal device by the user,
    The incoming call notification method according to claim 2, wherein the priority is calculated according to a result of the determination.
  4. Collecting usage status information including any one of biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices,
    An incoming call notification program for causing a computer to execute a process of determining a terminal device to notify an incoming call based on the usage status information and notifying the determined terminal device.
  5. A usage status information acquisition unit that collects usage status information including biometric information and terminal status information indicating the status of the terminal device from a plurality of terminal devices;
    An incoming call notification device comprising: a notification unit that determines a terminal device that notifies an incoming call based on the usage status information and notifies the determined terminal device.
JP2015014357A 2015-01-28 2015-01-28 Call incoming notification method, call incoming notification program, and call incoming notification device Pending JP2016139967A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2015014357A JP2016139967A (en) 2015-01-28 2015-01-28 Call incoming notification method, call incoming notification program, and call incoming notification device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2015014357A JP2016139967A (en) 2015-01-28 2015-01-28 Call incoming notification method, call incoming notification program, and call incoming notification device

Publications (1)

Publication Number Publication Date
JP2016139967A true JP2016139967A (en) 2016-08-04

Family

ID=56559412

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2015014357A Pending JP2016139967A (en) 2015-01-28 2015-01-28 Call incoming notification method, call incoming notification program, and call incoming notification device

Country Status (1)

Country Link
JP (1) JP2016139967A (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008104067A (en) * 2006-10-20 2008-05-01 Sky Kk Call termination notification system, and portable communication terminal for use therein
US20140003597A1 (en) * 2012-06-27 2014-01-02 Research In Motion Limited Apparatus, system and method of call notifications to active communication devices

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008104067A (en) * 2006-10-20 2008-05-01 Sky Kk Call termination notification system, and portable communication terminal for use therein
US20140003597A1 (en) * 2012-06-27 2014-01-02 Research In Motion Limited Apparatus, system and method of call notifications to active communication devices

Similar Documents

Publication Publication Date Title
Pielot et al. An in-situ study of mobile phone notifications
US8913144B2 (en) Information communication method
US9088363B2 (en) Information communication method
US9756255B2 (en) Information communication method
US9380227B2 (en) Information communication method for obtaining information using bright line image
US9087349B2 (en) Information communication method
US9253520B2 (en) Video capture, processing and distribution system
CN102104592B (en) Session migration between network policy servers
JP2009211632A (en) Service system
AU2013367893B2 (en) Information communication method
US9405892B2 (en) Preventing spoofing attacks for bone conduction applications
US9071653B2 (en) Reducing cellular network traffic
US9955352B2 (en) Methods and systems for addressing mobile communications devices that are lost or stolen but not yet reported as such
CN105138229B (en) A kind of information processing method and electronic equipment
JP5729161B2 (en) Communication terminal, wireless device, and wireless communication system
WO2010051377A1 (en) A method and apparatus for mobile time-based ui for vip
TW201126192A (en) Centralized management of motor vehicle software applications and services
CA2418826A1 (en) Resource manager device for a satellite telecommunications system
HK1036707A1 (en) User specific automatic data redirection system
WO2011019660A3 (en) Systems and methods for enrolling users in a payment service
CN103109259A (en) Location-aware mobile connectivity and information exchange system
CN105052084B (en) Method and system based on geographical mobile distribution computing resource
JP2013538384A (en) Device Communication
JP4692251B2 (en) Computer system providing access and management method thereof
US20130042305A1 (en) Facemail

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20171215

RD03 Notification of appointment of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7423

Effective date: 20180405

RD04 Notification of resignation of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7424

Effective date: 20180410

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A821

Effective date: 20180411

A711 Notification of change in applicant

Free format text: JAPANESE INTERMEDIATE CODE: A711

Effective date: 20180725

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20181019

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20181121

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20181127

A02 Decision of refusal

Free format text: JAPANESE INTERMEDIATE CODE: A02

Effective date: 20190528