JP6438197B2 - Portable terminal device and portable terminal program - Google Patents

Description

  The present invention relates to a mobile terminal device having an incoming call rejection function and a mobile terminal program.

Various mobile terminal devices such as a mobile phone having a call function by wireless communication, a so-called PHS, and a smartphone are widely used.
In this portable terminal device, various functions for responding to an incoming call from a specific telephone number that is considered to be annoying for the user have been proposed in order not to be bothered by annoying calls.
For example, in Patent Document 1, as a method of rejecting an incoming call from a specific caller in a mobile phone terminal, a technique for storing a telephone number to be rejected in the incoming call rejection list of a terminal owned by the terminal user is proposed. ing.
Further, in Patent Document 2, a nuisance telephone database is formed by collecting nuisance telephone number information from a large number of subscriber telephones, and the “safety” is set when an incoming call is received from an unknown telephone number using the database via the Internet. Has been proposed that can prompt the user to pay attention to the user terminal.

JP 2012-147123 A JP 2012-109842 A

However, in the technology described in Patent Document 1, a telephone number for simply rejecting an incoming call is stored in a terminal each time, and a general “safety level and risk level” determined by others for the telephone number. "Cannot be confirmed.
Further, in the technology described in Patent Document 2, a nuisance call database server can be used to confirm the safety level of a telephone that a user has placed at the time of incoming call, and an incoming call rejection telephone registered with a telephone connected to the user terminal. The user could not know the degree of danger to the number, and the user's awareness of crisis management was not improved. Also, every time there is an incoming call, the user terminal needs to connect to a server that has built a nuisance call database via the Internet.

  It is an object of the present invention to easily recognize whether or not a telephone number registered as a call rejection in a mobile terminal device is a nuisance call for others.

(1) In the first aspect of the invention, a registration unit that registers a telephone number that is a target of call rejection as a call rejection number, a call reception unit that receives a connection request from another device, and the connection request Caller number acquisition means for acquiring a caller number of another device, call rejection means for rejecting a call when the acquired caller number is the registered call rejection number, annoyance exceeding a predetermined level is registered the determined nuisance telephone number is a telephone, the unwanted call DB acquisition means risk to acquire the set unwanted call DB corresponding to each annoying telephone number, the the call rejection number the unwanted call DB depending on whether or not registered, unwanted calls and unwanted call determining means for determining whether the corresponding to the number, and call rejection count for the call rejection number, the unwanted calls DB at set risk and based on There are, clearly the total risk determining means for determining an overall risk, when displaying the call rejection number you the registration, if the incoming call rejection number is determined to be relevant to the nuisance calls is the fact And a display control unit that performs display according to the determined overall risk level as an indication to that effect .
(2) In the invention described in claim 2 , the total risk determination means uses the number of incoming call rejections weighted to be smaller as the incoming date is older, as the number of incoming call rejections for determining the total risk. The mobile terminal device according to claim 1 is provided.
(3) In the invention according to claim 3 , there is provided a deletion means for deleting the registered incoming call rejection number as an object of incoming call rejection, and the deletion means has a high risk of the incoming call rejection number being the deletion target. The mobile terminal device according to claim 1 , wherein the higher the total risk level or the higher the overall risk level, the greater the amount of user operation required for erasure.
(4) In the invention according to claim 4, when the incoming call rejection number by the display control means is displayed, when the incoming call rejection display includes an incoming call rejection number or a list of registered incoming call rejection numbers is displayed. The mobile terminal device according to any one of claims 1 to 3 is provided.
(5) The invention according to claim 5 further comprises reporting means for reporting an incoming call rejection number newly registered by the registration means to a nuisance call DB server, wherein the nuisance call DB acquisition means includes a plurality of portable terminal devices. The nuisance call DB is acquired from the nuisance call DB server that creates the nuisance call DB based on the reported call rejection number. The claim according to any one of claims 1 to 4 , A portable terminal device is provided.
In the invention described in (6) according to claim 6, wherein the reporting means further wherein the reporting a call rejection number there is an incoming call rejection by call blocking means, according to claim 5, characterized in that the mobile A terminal device is provided.
(7) In the invention described in claim 7 , the reporting means reports the incoming call rejection by the incoming call rejection means every predetermined number of times, and provides the mobile terminal device according to claim 6 .
(8) In the invention according to claim 8 , a registration function for registering a telephone number as a call rejection target as a call rejection number, a call reception function for receiving a connection request from another device, and the connection request A caller ID acquisition function for acquiring a caller ID of another device, an incoming call rejection function for rejecting an incoming call when the acquired caller ID is the registered incoming call rejection number, and an inconvenience exceeding a predetermined level. is registered the determined nuisance telephone number is a telephone, and the annoying phone number set risk factors corresponding a nuisance calls DB obtaining function for obtaining a nuisance calls DB, the the call rejection number the unwanted call DB depending on whether or not registered, nuisance and nuisance calls determination function of determining whether or not appropriate to the phone number, and call rejection count for the call rejection number, the unwanted calls DB at set risk and based on There are, clearly the total risk determination function of determining the overall risk, when displaying the call rejection number you the registration, if the incoming call rejection number is determined to be relevant to the nuisance calls is the fact The display control function is a portable terminal program for causing a computer to realize the display control function, wherein the display control function displays according to the determined overall risk level as an indication to that effect. Provide a mobile terminal program .

  According to the present invention, when displaying the registered incoming call rejection registration number, if it is determined that the incoming call rejection number also corresponds to the nuisance call, the fact is clearly indicated, so the telephone number registered for incoming rejection However, it can be easily recognized whether or not it falls under the nuisance call for others.

It is explanatory drawing about the nuisance telephone DB construction system which constructs | assembles the nuisance telephone DB which the portable terminal device in this embodiment acquires. It is a functional block diagram showing each function of the nuisance telephone DB server. It is explanatory drawing showing the content of the unwanted telephone DB. It is a functional block diagram showing each function of the portable terminal device. It is explanatory drawing about the registration content of an incoming call rejection list memory | storage part. It is explanatory drawing showing the memory content of the troublesome telephone DB memory | storage part. It is a hardware block diagram of a portable terminal device. It is the flowchart showing the operation | movement at the time of the incoming call rejection registration in a portable terminal device, and the operation | movement of the nuisance DB construction process in a nuisance telephone DB server. It is a flowchart in the case of connecting to a nuisance call DB server from a mobile terminal device and acquiring a nuisance call DB. It is a flowchart of the process which connects with a nuisance telephone DB server from a portable terminal device, and acquires a nuisance telephone DB. It is a flowchart in the case of transmitting the nuisance call DB from the nuisance call DB server side to the mobile terminal device. It is explanatory drawing about the transition between each representative state and each state of a portable terminal device. It is explanatory drawing about the screen transition of the incoming call rejection registration from a call log. It is a flowchart when there is an incoming call to the mobile terminal device. It is explanatory drawing showing the display in the case of an incoming call from a caller number that is not registered in the incoming call rejection list or the phone book, and the screen transition of incoming call rejection registration. It is explanatory drawing about the screen display during a telephone call, and the transition screen of an incoming call rejection registration. It is explanatory drawing showing the screen in the middle of a talk display. It is explanatory drawing of the incoming call rejection number deletion screen which requests | requires deletion of an incoming call rejection number. It is explanatory drawing of an incoming call rejection list screen and its transition screen. It is explanatory drawing of the modification regarding the clarification method of the junk call in an incoming call rejection list screen. It is explanatory drawing about a screen transition in the case of deleting an incoming call rejection number. It is explanatory drawing showing the incoming call rejection list memory | storage part in the case of determining a risk taking into consideration the frequency | count of incoming call rejection.

Hereinafter, preferred embodiments of the mobile terminal device and the mobile terminal program of the present invention will be described in detail with reference to FIGS. 1 to 22.
(1) Outline of Embodiment A mobile terminal device according to the present embodiment includes a mobile terminal device having an incoming call rejection function for rejecting an incoming call from a caller number that matches a pre-registered incoming call rejection number. It is targeted.
Here, the contents of the incoming call rejection are determined for each portable terminal device. For example, if you do not specify the incoming call only (output ringtone, vibration, display incoming call), leave the line connected without specifying the incoming call, connect the line without specifying the incoming call, and reply message , When disconnecting immediately after connecting the line without clearly indicating the incoming call, when sending a rejection signal to the exchange without clearly indicating the incoming line and connecting the line.
In either case, the incoming call history may or may not be saved. However, in the embodiment to be described, a process that requires the incoming call history is intended for a portable terminal device having a function of saving the incoming call history. And

In the mobile terminal device of the present embodiment, when displaying the “incoming call rejection list” registered by the user on the mobile terminal device, the phone number registered for incoming call rejection (the incoming call rejection number) is not limited to itself, It is determined whether or not the telephone number is recognized as a nuisance call by a large number of users (nuisance call), and the fact is clearly indicated in the incoming call rejection number corresponding to the nuisance call.
To determine whether the number is a nuisance call or not, download the nuisance call DB from a nuisance call DB (database) server that manages a database of telephone numbers determined to be nuisance calls from information provided by multiple users. Then, when an incoming call occurs in the portable terminal device, it is determined by whether or not the caller telephone number exists in the stored unwanted telephone DB.

In the incoming call rejection list, an icon is displayed as an indication to that effect on an incoming call rejection number corresponding to a nuisance call.
In the present embodiment, a case where additional information such as risk information indicating the degree of inconvenience or the degree of danger is given to a troublesome telephone (telephone number) in the troublesome telephone DB will be described. When displaying the incoming call rejection list, in addition to / changing the icon indicating that it is also applicable to a nuisance call, an icon (risk level icon or alphanumeric character) is displayed.
In addition to the icons, the nuisance call clarification method can be “change the character color”, “change the background color”, “change the font”, etc. according to the degree of danger.

In the present embodiment, the management form of the corresponding incoming call rejection number in the incoming call rejection list is changed according to the risk / nuisance level based on the additional information of the nuisance call.
For example, when deleting an incoming call rejection number from the incoming call rejection list, it is judged whether it corresponds to an unsolicited call with a high degree of risk, and the procedure for deleting it according to the degree of risk is made stricter or deleted. Increase the number of confirmations. In addition, the incoming call rejection number corresponding to the nuisance call with the highest risk rank cannot be deleted.
In addition, there is a limit on the number of rejected calls registered in the mobile terminal device. If there is a request for registration for rejecting incoming calls when the limit is already registered, it is necessary to delete the registered incoming rejection number There is. At that time, a nuisance call having a risk level of a predetermined rank or higher (the highest risk level in the present embodiment, but not limited to this) is not included in the deletion target list. Or when displaying a deletion object list | wrist, you may make it display in order with low risk.

  According to this embodiment, the user can recognize that the incoming call rejection number registered in the “incoming call rejection list” is a telephone number that is recognized as a nuisance call for many people.

When there is an incoming call, the mobile terminal device changes the process for the incoming call according to the telephone number of the caller.
That is, if the caller's phone number is registered in the user's phonebook, the normal incoming call processing (output of ringtone and display of caller information) is performed, and the phone number registered in the incoming call rejection list If so, incoming call rejection processing is performed.
On the other hand, when the caller telephone number is not registered in the user's phone book or the incoming call rejection list, the mobile terminal device checks the downloaded nuisance call DB and if there is a matching phone number. Indicates that it is a “phone number that may be a nuisance call”.
If the incoming call is from a telephone number that is not registered in any of the user's telephone directory, incoming call rejection list, and unwanted telephone DB, an incoming call process is performed to output the ringtone and display the telephone number.

(2) Details of the embodiment.
FIG. 1 shows a nuisance call DB construction system for constructing a nuisance call DB acquired by a mobile terminal device according to the present embodiment.
In this nuisance telephone DB construction system, a nuisance telephone DB server 800 that collects and distributes the nuisance telephone DBs that are targets of the present embodiment, and a voice / packet switching network 400 as a communication network that performs voice and data communication, The other company's voice network 500, a plurality of base stations 420 that connect the mobile terminal device to any one of the communication line networks, and mobile terminal devices 100a, 100b that connect to the base stations in the communicable area and perform communication and data communication. 100c... And a fixed telephone 600 connected to the communication network by wire.

  Of the mobile terminal devices 100a, 100b, 100c..., The target of the present embodiment is a mobile terminal device subscribed to a service contract by the nuisance telephone DB construction system. In the description of the present embodiment, it is assumed that the mobile terminal device 100c and the fixed phone 600 in FIG. 1 are not subscribed and the other mobile terminal devices 100a, 100b,. In the embodiment, the portable terminal device 100 will be described as indicating the subscribed portable terminal devices 100a and 100b.

The mobile terminal device of the present embodiment is a mobile terminal device having a call function and an incoming call rejection registration function. For example, various mobile terminal devices such as a mobile phone, a so-called PHS, a smartphone, and a Voice (Internet over Internet Protocol) terminal. Is the target.
Further, as communication network, various communication network such as PHS network, 3G network, and 4G network that can be connected to each other are targeted.

FIG. 2 is a functional configuration diagram showing each function of the nuisance call DB server 800.
The nuisance call DB server 800 includes a network communication unit 810, a control unit 820, a nuisance call DB storage unit 830, and a registration information storage unit 840.
The network communication unit 810 functions as a communication unit, and performs modulation and demodulation for a communication line so that the network communication unit 810 communicates with the mobile terminal device 100 subscribing to the nuisance telephone DB construction system via the voice / packet switching network 400. Communicate.

The control unit 820 includes functional units such as an incoming call rejection number reception unit 821, a point calculation unit 822, a risk level assignment unit 823, a communication control unit 824, and a nuisance call DB transmission unit 825.
Although not shown, the control unit 820 includes a CPU, and includes a ROM that stores various programs and data and a computer system that includes various hardware such as a RAM that is used as a work area. The CPU is stored in the ROM. The function in each functional unit such as the incoming call rejection number receiving unit 821 is realized by executing a nuisance call management program or the like.

The incoming call rejection number receiving unit 821 receives the incoming call rejection number received from the mobile terminal device 100 by the network communication unit 810 as rejection information, and supplies it to the point calculation unit 822.
The point calculation unit 822 calculates the point for each incoming call rejection number transmitted from each mobile terminal device 100. In this embodiment, the report (number of transmissions) of incoming call rejection registration is counted as a point.

The risk level assigning unit 823 performs authorization (registration) as a nuisance call and assigns / changes the risk level / nuisance level based on the number of points for each incoming call rejection number calculated by the point calculation unit 822. When this registration, assignment, or change is made, that fact is reported to the communication control unit 824.
The communication control unit 824 instructs the nuisance call DB transmission unit 825 to transmit the nuisance call DB in response to a request from the mobile terminal device 100 or a report of the nuisance call DB change.
The nuisance call DB transmission unit 825 transmits the nuisance call DB (difference) to the mobile terminal device 100 via the network communication unit 810 according to an instruction from the communication control unit 824.

FIG. 3 is an explanatory diagram showing the contents of the nuisance call DB stored in the nuisance call DB storage unit 830.
As shown in FIG. 3, the nuisance call DB stores a telephone number (nuisance call number) reported as a nuisance call from the mobile terminal device 100, the number of reports, the degree of risk, and the update date and time.
The nuisance telephone number is a telephone number reported from the mobile terminal device 100 as an incoming call rejection number.
The number of reports represents the number of mobile terminal devices 100 in which each nuisance telephone number is registered as an incoming call rejection number, and the number of times is counted up every time there is an incoming call rejection registration report from each mobile terminal device 100.
The degree of danger represents the degree of danger for each nuisance telephone number, and is classified by pointing the number of reports. This risk level is provided to the portable terminal device 100 as additional information of the nuisance telephone number.
In this embodiment, the number of reports 11 to 50 is classified as low, the number of reports 51 to 200 is medium, and the number of reports 201 or more is classified as high. Since the number of reports of 10 or less is outside the scope of provision to the mobile terminal device 100, no danger level is given.
Note that the number of risk categories and the number of reports for each category are examples, and other values are set as thresholds, and whenever the number of reports exceeds the threshold for each category, the risk level for the nuisance telephone number is set. It may be changed.

In the update date and time, the date and time when the risk level was updated is stored.
That is, for a nuisance telephone number that does not have a rank of danger (indicated by a cross), the date and time when the nuisance telephone number was added, that is, the first incoming call rejection report was made and the telephone number was registered as a nuisance telephone number. The date and time is saved.
On the other hand, for junk phone numbers with low, medium, and high risk levels, the date and time when the risk level was changed from no rank (×) to low, low to medium, and medium to high is stored. The
In addition, you may make it preserve | save the date when the frequency | count of the report of the said troublesome telephone number was added (changed) in an update date.

  In the present embodiment, the nuisance telephone number and the degree of danger are transmitted to the portable terminal device 100 among the nuisance telephone DB data stored in the nuisance telephone DB storage unit 830. All nuisance telephone numbers and risk levels are transmitted at the first transmission, and updated difference data is transmitted at subsequent transmissions.

Returning to FIG. 2, the registration information storage unit 840 stores user information regarding a user (mobile terminal device 100) who is subscribed to the nuisance telephone DB construction system.
As the user information, a user identification number, a telephone number of the mobile terminal device 100 (not required when used as an identification number), a mail address of the mobile terminal device 100, a user registration date, and other information are stored.
In this user information, as will be described later, in order to transmit the difference data of the nuisance call DB to the mobile terminal device 100, the version information of the nuisance call DB that has already been transmitted and / or the nuisance call DB is finally transmitted. The transmission date and time are saved.
The nuisance call DB server 800 constructs the nuisance call DB by collecting the telephone numbers registered as call rejection targets in the mobile terminal devices 100 registered as users.

FIG. 4 is a functional configuration diagram illustrating each function of the mobile terminal device 100.
The mobile terminal device 100 includes a wireless communication unit 110, a display unit 120, a call unit 130, a key operation unit 140, an information storage unit 160, and a control unit 200.
The wireless communication unit 110 functions as a communication unit that connects to a communication line network to perform a call or data communication, and performs modulation, demodulation, or the like according to a communication method employed by the mobile terminal device 100 such as PHS communication or 3G communication. As a result, communication with other portable terminal devices 100, fixed telephones 600, and the like is performed.

The display unit 120 functions as a display unit that displays various types of information, and includes, for example, a liquid crystal display.
The display unit 120 displays an operation screen corresponding to various functions necessary for the portable terminal, such as outgoing and incoming calls, registration of incoming call rejection in the present embodiment, and display of a registered incoming call rejection list.
For example, when a call is made using the telephone function, the call destination telephone number input by the user from the numeric keypad of the key operation unit 140 is displayed or registered in the telephone number or telephone number book when an incoming call is received. If it is, the name is displayed. In addition, when using the mail function, the contents of the mail address and the mail text are displayed, and when using the camera function, images before and after photographing are displayed.
The display unit 120 displays a registered incoming call rejection list, and when the incoming call rejection number displayed in the list is a number registered in the unwanted call DB of the unwanted call DB storage unit 161. The risk level indicating that is displayed.

  The calling unit 130 functions as a calling unit that makes a call by inputting and outputting voices, and includes a microphone 131 that inputs voice and a speaker 132 that outputs voice, as will be described later.

The key operation unit 140 functions as input means for performing various input operations, and includes function keys including a numeric keypad, an on-hook key, and an off-hook key.
Note that the key operation unit 140 is a touch panel arranged on the display screen in the case where the various operation buttons are configured by hard keys, in addition to a large display unit 120 such as a smartphone. All or part of the operation keys (input keys) may be configured as soft keys. In this case, the display unit 120 displays operation keys (all or part of the numeric keys and function keys) to be received by the touch panel, and the position coordinates of the finger or the like touching the touch panel and the display position of the operation keys are displayed. The touch (pressing) of the operation key is detected.

The information storage unit 160 includes an incoming call rejection list storage unit 162, a telephone directory storage unit 163, a nuisance call DB storage unit 161, and other storage units not shown.
In the incoming call rejection list storage unit 162, telephone number information for incoming call rejection registered as an incoming call rejection number by the incoming call rejection registration in the present embodiment is registered.
When there is an incoming call, the mobile terminal device 100 checks whether the other party's telephone number is an incoming call rejection number existing in the incoming call rejection list storage unit 162, and if there is an incoming call, rejects the incoming call. That is, no ring tone is output or incoming calls are not displayed.

FIG. 5 shows the contents registered in the incoming call rejection list storage unit 162.
As shown in FIG. 5, in the incoming call rejection list storage unit 162, as the telephone number information for each incoming call rejection number, the incoming call rejection number, the last incoming date, the number of rejections, database registration, risk level, non-erasure, and the like Information is stored.
The incoming call rejection number is a telephone number registered by the user as an incoming call rejection target in the mobile terminal device 100.
As for the last incoming date, the incoming date (year / month / day) is updated when there is an incoming call from the corresponding incoming call rejection number, and the registered date is stored when the incoming call rejection is registered. Note that not only the date but also the time may be stored. Further, not only the last date (time) but also a predetermined number of incoming histories that go back from the last date may be stored.
The number of rejections is the number of incoming calls from the incoming call rejection number after registering the incoming call rejection.

The database registration is data indicating whether or not an incoming call rejection number that is an object of incoming call rejection is also registered in the nuisance call DB storage unit 161 described below with reference to FIG. In FIG. 5, “o” and “x” are displayed according to the presence / absence of registration, but the registration flag ON / OFF is stored as data.
The degree of danger is data indicating the degree of danger / nuisance of the incoming call rejection number registered in the database. As the risk level, the risk level stored in the nuisance call DB storage unit 161 corresponding to each incoming call rejection number is stored. However, the risk level may not be stored in the incoming call rejection list storage unit 162, and the corresponding risk level may be read from the nuisance call DB storage unit 161 using the incoming call rejection number as a search key.

Non-erasing defines a response when an operation for deleting the incoming call rejection number from the incoming call rejection list storage unit 162 is performed. In this embodiment, if non-erasure is “◯”, erasure cannot be performed, and if “x”, erasure is possible. Whether it is non-erased (whether erasure is permitted) is determined in accordance with the level of risk corresponding to the incoming call rejection number.
In this embodiment, the incoming call rejection number having a high risk level is locked for deletion, and the user cannot delete the incoming call rejection list from the incoming call rejection list. (For example, a deletion password request and an input operation set exclusively for deletion can be deleted).

  In FIG. 5, “◯” that cannot be erased and “x” that can be erased are defined for non-erasing, but different correspondences may be defined according to the degree of risk. For example, “Erase not allowed” that does not allow any erasure, “Danger notice” that prompts each screen to confirm whether or not to delete it, and displays the degree of danger every time the operation screen is changed during erasure, You may prescribe | regulate to "normal deletion" etc. which display and confirm a danger only at the end.

  As other information, the date and time when the incoming call rejection number is registered in the incoming call rejection list storage unit 162 is stored.

  Returning to FIG. 4, the telephone directory storage unit 163 stores a telephone directory such as a telephone number, a mail address, and an address of a call destination registered by a user operation by the telephone directory function in addition to the telephone number of the mobile terminal device 100. Remembered.

The nuisance call DB storage unit 161 stores the nuisance call DB acquired from the nuisance call DB server 800.
FIG. 6 shows the contents stored in the nuisance call DB storage unit 161.
As shown in FIG. 6, the nuisance call DB storage unit 161 stores the nuisance call number and the risk among the data of the nuisance call DB stored in the nuisance call DB storage unit 830 of the nuisance call DB server 800. Obtained and saved. In the present embodiment, a nuisance call DB (annoyance phone number and risk level) is periodically downloaded from the nuisance call DB server 800 (initially all data and thereafter difference data).
In order to download the difference data, the mobile terminal device 100 stores the previous download date and time and transmits it to the nuisance call DB server 800 at the next download. In addition, version information is added to each nuisance call DB / difference data that the nuisance call DB server 800 transmits to each mobile terminal device 100, and the mobile terminal device 100 transmits the current version information at the time of download. Good. Furthermore, the nuisance call DB server 800 manages version information of the nuisance call DB / difference data that has been transmitted to each mobile terminal device 100, and when there is a request from the mobile terminal device 100, the latest version of the difference data is obtained. You may make it transmit.

  The other storage units (not shown) of the information storage unit 160 store outgoing / incoming history data and data corresponding to various functions such as a schedule management function and a camera function provided in the mobile terminal device 100.

Returning to FIG. 4, the control unit 200 includes a wireless communication control unit 210, a nuisance call DB management unit 220, an outgoing / incoming call history management unit 230, an incoming call rejection processing unit 240, an incoming call rejection list management unit 250, a selection information transmission unit 260, an incoming call. A rejection list display control unit 270 is provided, which controls various communications such as outgoing and incoming calls (voice, data) by the mobile terminal device 100, and controls registration and deletion of incoming rejection.
The control unit 200 determines whether or not the caller's telephone number is registered as an incoming call rejection number in the incoming call rejection list storage unit 162 when an incoming call is received by each of these units. Does not process incoming calls for incoming calls. That is, when the caller's telephone number is registered as an incoming call rejection number, the control unit 200 performs mute of the ringtone (by user setting or / and vibration) and suppresses off-hook and is registered. If not, the incoming call processing is performed and the telephone number of the caller is temporarily stored.
Further, the control unit 200 transmits the incoming call rejection number registered by the user to reject the incoming call to the nuisance call DB server 800 and downloads the difference data of the nuisance call DB from the nuisance call DB server 800.

  The wireless communication control unit 210 performs control of outgoing and incoming calls in the wireless communication unit 110 and control of communication with the nuisance call DB server 800 (mainly report of incoming call rejection registration and download of the nuisance call DB).

  The nuisance call DB management unit 220 updates the nuisance call DB storage unit 161 according to the difference data of the nuisance call DB downloaded by the wireless communication control unit 210. That is, when the nuisance telephone number included in the downloaded difference data does not exist in the nuisance telephone DB storage unit 161, the nuisance telephone DB management unit 220 newly stores the nuisance telephone number and the degree of danger and exists. If so, the corresponding risk is updated.

The outgoing / incoming history management unit 230 manages the date and time and number of outgoing / incoming calls for each telephone number and for each incoming call rejection number as a history of outgoing calls from the mobile terminal device 100 and incoming calls received by the mobile terminal device 100.
The incoming call rejection processing unit 240 determines whether or not the caller's telephone number is registered in the incoming call rejection list storage unit 162 for an incoming call received by the mobile terminal device 100, and the incoming call from the registered telephone number is received. If there is, reject the incoming call.
The incoming call rejection list management unit 250 manages new registration and deletion of incoming call rejection numbers for the incoming call rejection list stored in the incoming call rejection list storage unit 162, and stored data for each incoming call rejection number (see FIG. 5). Management of updates, etc.
When the incoming call rejection number is newly registered, the selection information transmission unit 260 transmits the incoming call rejection number to the nuisance call DB server 800 via the wireless communication control unit 210.

The incoming call rejection list display control unit 270 displays a list of registered incoming call rejection numbers in response to an operation for displaying the incoming call rejection list by the user. Specifically, while the mobile terminal device 100 is waiting, a list of telephone numbers that have been registered for call rejection so far is displayed on the screen by selecting the reference of the call rejection list registered by the user by menu operation. The
When the incoming call rejection list display control unit 270 displays the incoming call rejection list as a list, the database registration data of the incoming call rejection list storage unit 162 determines whether there is a telephone number that matches the nuisance telephone number DB. Judgment is made based on whether there is (Yes), and if so, an icon indicating that the corresponding incoming call rejection number matches the beginning (or at the end) (indicating that it also corresponds to an unwanted call) indicate.
In addition to icons, “change character color”, “change background color”, “change font”, etc., can be used for the call rejection number corresponding to “Yes”.

FIG. 7 illustrates a hardware configuration of the mobile terminal device 100.
The mobile terminal device 100 includes a first wireless communication unit (RF) 110, an input key 140, a functioning display 120, a microphone 131, a speaker 132, a CPU 201, a RAM 202, a ROM 203, and an information storage unit 160 as hardware configurations. Yes.
Further, when the mobile terminal device 100 is a 3G terminal using a 3G line, the mobile terminal device 100 further includes a SIM card insertion slot (not shown) for inserting a SIM card as its hardware configuration.

CPU201-ROM203 function as the control part 200 in FIG. 4 which displayed the portable terminal device 100 by the function structure.
The CPU 201 uses the RAM 202 as a work area, and based on various programs stored in the ROM 203, the incoming call rejection registration, incoming call rejection from the telephone number registered for incoming call rejection, list display of incoming call rejection registration, Performs various processes related to incoming call rejection such as data transmission / reception, and processes corresponding to various functions (calling, data transmission, Internet connection, imaging, reproduction of music and video data, etc.) as a normal mobile terminal device 100 I do.

The microphone 131 and the speaker 132 function as a calling unit in FIG.
The input key 140 functions as a key operation unit, and the display 120 functions as a display unit.

Next, each process by the portable terminal device 100 and the nuisance call DB server 800 configured as described above will be described.
FIG. 8 is a flowchart showing the operation of the incoming call rejection registration in the mobile terminal device 100 and the operation of the troublesome DB construction process in the troublesome telephone DB server 800. In FIG. 8, one mobile terminal device is described, but all the mobile terminal devices 100 that are registered (or contracted) are targets, and the nuisance telephone DB server 800 includes all these mobile terminals. A nuisance DB is constructed based on transmission data from the terminal device 100.

The control unit 200 of the mobile terminal device 100 monitors whether the user has performed an incoming call rejection operation (step 11). The scene where this incoming call rejection operation is performed will be described in the transition explanation of the operation screen in FIG.
When an incoming call rejection operation is performed by the user (step 11; Y), the control unit 200 registers the target telephone number as a nuisance telephone number in the incoming call rejection list of the incoming call rejection list storage unit 162 (step 12). The target phone number includes a phone number entered by the user from the numeric keypad, a call destination phone number saved in the RAM 202, a caller phone number at the time of incoming call, a phone number selected in the display of outgoing call history and incoming call history, etc. Is applicable.

After registering in the incoming call rejection list in step 12 and when no incoming call rejection operation is performed by the user (step 11; N), the control unit 200 determines whether or not the timer has expired (step 13). .
In this embodiment, the set time T of the timer is set to 24 hours, but another time S may be set, and the set time T may be changed by the user.
Also, the start time of the timer is arbitrary, but is set to midnight in this embodiment. The user may be able to change the start time.

If the timer has not expired (step 13; N), the control unit 200 returns to step 11 and continues to monitor the incoming call rejection operation.
On the other hand, when the timer has expired (step 13; Y), the control unit 200 reads the incoming call rejection number newly registered within the current timer period from the incoming call rejection list storage unit 162, and identifies its own device identification number (for example, And the telephone number of the own device) to the nuisance call DB server 800 (step 14), and the process is terminated.
In addition, when the newly registered incoming call rejection number is read within the current timer period, the control unit 200 determines from the date and time registered in the incoming call rejection number. A flag to be distinguished may be stored in the incoming call rejection list, and an incoming call rejection number with an untransmitted flag of 1 may be read and transmitted, and a flag corresponding to the transmitted incoming call rejection number may be set to an untransmitted flag 0.

  On the other hand, the control unit 820 of the nuisance call DB server 800 monitors whether or not a newly registered incoming call rejection number has been received from the mobile terminal device 100 (step 21).

When the incoming call rejection number is received (step 21; Y), the control unit 820 adds 1 to the point corresponding to the incoming call rejection number (telephone number) (step 22).
That is, if the incoming call rejection number is a telephone number that has already been reported from another mobile terminal device 100 and is already stored in the nuisance call DB storage unit 830, the control unit 820 sets the number of reports corresponding to the number. Count up once.
On the other hand, when the received call rejection number is not registered in the nuisance call DB storage unit 830, that is, when this is the first report, the control unit 820 receives the call refusal number received this time in the nuisance call DB storage unit 830. Is reserved, and the number of reports is 1.
If there are a plurality of incoming call rejection numbers received from the mobile terminal device 100, the process of step 22 is performed for each of them.

Next, the control unit 820 determines whether or not the total point of each incoming call rejection number updated (point up) in step 22 has exceeded a predetermined threshold (step 23).
When the threshold value is exceeded (step 23; Y), the control unit 820 changes the risk level of the incoming call rejection number in the nuisance call DB storage unit 830 and changes the update date / time to the date / time when the current risk level is changed ( Step 24), the process ends.
Here, there are a plurality of predetermined threshold values depending on the set risk level. In this embodiment, the threshold value for each risk level is set to 10 for low, 50 for medium, and 200 for high. The risk is changed to the corresponding risk when the number of times of each threshold is exceeded. For example, when the number of reports is counted up from 50 to 51, the risk level is changed from low to medium.
For an incoming call rejection number whose degree of risk does not exceed the threshold, the processing is terminated as it is.

Next, processing in which the mobile terminal device 100 acquires the nuisance call DB from the nuisance call DB server 800 will be described with reference to FIGS. 9 to 11.
FIG. 9 is a flowchart when the mobile terminal device 100 is connected to the nuisance call DB server 800 to acquire the nuisance call DB.
The control unit 200 of the mobile terminal device 100 requests the nuisance call DB server 800 to transmit the nuisance call DB (step 31). This request is made by a user operation, when a predetermined operation is performed (for example, when an incoming call rejection list display operation is performed or an incoming call rejection registration operation is performed). Is called.
Further, when requesting transmission of the nuisance call DB, the control unit 200 transmits the identification number of the user (or the mobile terminal device 100) to the nuisance call DB server 800. As this identification number, a user ID, a telephone number, a terminal ID, or other number that identifies the user or the mobile terminal device 100 is used. When the user ID is used, the user ID determined at the time of user registration in the nuisance telephone DB construction system that is the target of the present embodiment is used.

In the nuisance call DB server 800, the control unit 820 monitors whether or not a nuisance call DB transmission request is received from the mobile terminal device 100 (step 41).
When the transmission request is received (step 41; Y), the control unit 820 determines whether or not the transmission request is from an authorized user (step 42). As to whether or not this is a regular user, it is determined whether or not the identification number transmitted from the portable terminal device 100 in the transmission request is registered in the registration information storage unit 840. If it is registered, it is determined that the user is a regular user. . In addition, when the telephone number of the portable terminal device 100 is registered in the registration information storage unit 840 and the identification numbers registered corresponding to the telephone number match, it is determined that the user is an authorized user. It may be.

If the user is not an authorized user (Step 42; N), the control unit 820 returns to Step 41 and continues monitoring the reception of the transmission request.
On the other hand, when it is a transmission request from an authorized user (step 42; Y), the control unit 820 transmits the difference data of the nuisance call DB to the mobile terminal device 100 (step 43), and ends the processing for the transmission request. .
The control unit 820 adds a difference in the nuisance call DB updated after the last difference transmission date and time stored in the registration information storage unit 840 corresponding to the identification number, that is, newly added after the last difference transmission date and time. The nuisance telephone number and its risk level, and the nuisance telephone number whose risk level has been changed and the post-change risk level are extracted as difference data.

On the other hand, after making a transmission request (step 31), the mobile terminal device 100 monitors whether or not a nuisance call DB is transmitted from the nuisance call DB server 800 based on the transmission request (step 32).
When the nuisance call DB is transmitted (step 32; Y), the control unit 200 of the mobile terminal device 100 stores the received nuisance call DB in the nuisance call DB storage unit 161 (step 33). That is, if the nuisance telephone number included in the received nuisance call DB does not exist in the nuisance call DB storage unit 161, the control unit 820 newly secures an area for the nuisance telephone number and stores the degree of risk. To do. If the nuisance telephone number exists in the nuisance call DB storage unit 161, the risk level is changed (updated) to the risk level of the received nuisance call DB.

The control unit 200 ends the process after storing the received nuisance call DB (step 33), but may indicate to the user that the nuisance call DB has been updated.
As an explicit method, when a nuisance telephone number is added, “added to database” is displayed, and when the risk level is changed, a display such as “risk level UP” is displayed on the screen.
Further, the explicit timing may be when the nuisance call DB is updated or when the user performs an operation for displaying the incoming call rejection list.

FIG. 10 is a flowchart of processing for connecting to the nuisance call DB server 800 from the mobile terminal device 100 and obtaining the nuisance call DB.
In the processing described with reference to FIG. 9, the case where a transmission request is made to the nuisance call DB server 800 when a predetermined specific operation is performed on the mobile terminal device 100 has been described.
On the other hand, in the process of FIG. 10, the mobile terminal device 100 makes a transmission request every predetermined time S. In the present embodiment, 24 hours are set as the predetermined time S, but other time intervals such as two days or one week may be used, and each mobile terminal device 100 can change the predetermined time S by the user. You may do it.

The control unit 200 of the mobile terminal device 100 monitors whether or not the timer for the predetermined time S has expired (step 30), and continues monitoring if the timer has not expired (step 30; N).
On the other hand, when the timer for the predetermined time S has expired (step 30; Y), the control unit 200 requests the nuisance call DB server 800 to transmit the nuisance call DB (step 31).
Hereinafter, the processes of the mobile terminal device 100 and the nuisance call DB server 800 are the same as those described with reference to FIG.
In this example, the timer for the predetermined time S is reset after the control unit 200 determines that the timer has expired, but is received after making a transmission request (step 31) or from the unwanted telephone DB server 800. It is also possible to reset after updating the unwanted telephone DB (step 33).

FIG. 11 is a flowchart when the nuisance call DB is transmitted from the nuisance call DB server 800 side to the mobile terminal device 100.
The control unit 820 of the nuisance call DB server 800 determines whether or not the risk level has been changed (step 51). The change of the risk level is based on step 24 described with reference to FIG.
When the degree of risk is changed (step 51; Y), the control unit 820 transmits the nuisance call DB (changed amount) to each mobile terminal device 100 stored in the registration information storage unit 840 (step 52). The process is terminated.

Here, the control unit 820 transmits the changed nuisance call DB to each mobile terminal device 100 as follows.
The control unit 820 uses SMS (Short Message Service) to send the nuisance call DB server 800 to the nuisance call DB server 800 for receiving the nuisance call DB to the mobile terminal device 100 of each telephone number stored in the registration information storage unit 840. Send a message requesting a connection.
In response to this message, the control unit 820 transmits the change in the nuisance call DB to the mobile terminal device 100 connected to the nuisance call DB server 800.

Further, when the e-mail address of each portable terminal device 100 is stored in the registered information storage unit 840, the change in the nuisance call DB may be transmitted as an attached file of each e-mail.
When an email address is stored only for some of the mobile terminal devices 100, it is transmitted as an attached file to the mobile terminal device 100 in which the email address is stored, and is transmitted to the mobile terminal device 100 that is not stored by SMS. It may be.

On the other hand, the control unit 200 of the mobile terminal device 100 monitors whether or not the nuisance call DB (changed part) is transmitted from the nuisance call DB server 800 (step 32).
When the nuisance call DB (changed amount) is transmitted (step 32; Y), the control unit 200 of the mobile terminal device 100 stores the received nuisance call DB (changed amount) in the nuisance call DB storage unit 161. (Step 33). That is, when the nuisance telephone number included in the received nuisance call DB does not exist in the nuisance call DB storage unit 161, the control unit 200 newly secures an area for the nuisance telephone number and stores the degree of risk. To do. If the nuisance telephone number exists in the nuisance telephone DB storage unit 161, the risk level is changed (updated) to the changed risk level.
Note that, as described with reference to FIG. 9, it may be clearly indicated to the user that the nuisance call DB has been updated.

In the example described with reference to FIG. 11, the case where the nuisance call DB server 800 transmits the change to the all portable terminal devices 100 as the nuisance call DB each time the degree of risk is changed has been described.
This may be transmitted every time there is a predetermined number n (n> 1), not every time there is one change.
In addition, if only the predetermined number n is changed, the first change before reaching the predetermined number n may not be reflected in the nuisance call DB of each mobile terminal device 100 for a long time. You may make it transmit the change part of a nuisance telephone DB, when either one conditions of change and progress of predetermined time are satisfy | filled.

Next, screen transition when performing incoming call rejection registration in each state of the mobile terminal device 100 will be described.
FIG. 12 shows typical states of the mobile terminal device 100 and transitions between the states.
As shown in FIG. 12, the mobile terminal device 100 is in a standby state, a call history, an incoming call, a outgoing call, a call, and an end-call display state.
Specifically, a normal standby screen is displayed during standby, and a call history is displayed by a user operation from this standby state. The incoming call rejection registration from the call history display screen will be described with reference to FIG.
Further, when there is an incoming call in the standby state, the state shifts to a state where the incoming call is being received, and the state is shifted to a state where the end of call is being displayed or a call is being made according to the user operation during the incoming call. The process during an incoming call will be described with reference to FIG. 14, and the incoming call rejection registration from the display screen during an incoming call will be described with reference to FIG.

On the other hand, when the user performs a call operation from the standby screen, a call-in-progress display is made, and a call-in-progress display is made by the off-hook operation of the caller, and then the process proceeds to the end-call display. The incoming call rejection registration from the display screen during a call will be described with reference to FIG. 16, and the incoming call rejection registration from the display screen during the end of call display will be described with reference to FIG.
This state transition is an example, and is displayed and transitioned according to the function of each mobile terminal device 100.

FIG. 13 shows a screen transition of incoming call rejection registration from the call history.
When the user of the mobile terminal device 100 is on standby and performs a call history display operation, a call history display screen is displayed as shown in FIG. In this call history display screen, call histories are displayed in order from the newest, and depending on whether the call target selected on the screen is an outgoing call or an incoming call, an incoming “call” or “incoming” icon is displayed.
In the example of FIG. 13A, when the history of “Danger Hanako” is selected, the selected history object is distinguished by being surrounded by a frame, and the selected history object is due to an incoming call. Is displayed in distinction by the dark “incoming” icon at the top. Note that the “call” icon may be displayed in a different manner by being displayed lightly.

As shown in FIG. 13A, an operation button is displayed at the bottom of the call history display screen, and when the “return” button is selected, the previous operation screen (in this case, the standby screen) is displayed. Returning, when the “select” button is selected, details of the selected call history are displayed.
On the other hand, when the “menu” button is selected, a submenu screen is displayed as shown in FIG. On this submenu screen, possible operations are displayed in a list in correspondence with the selected incoming call history (telephone number).
When “No. 6” is selected on this submenu screen, the control unit 200 of the mobile terminal device 100 uses the incoming call history telephone number selected on the screen of FIG. After registering in 162, the screen returns to the standby screen.
It is also possible to display a registration completion screen indicating that it has been registered in the incoming call list for a predetermined time, for example, 5 seconds after completion of incoming call rejection registration, and then return to the standby screen. On the registration completion screen, information such as the target phone number and the name corresponding to the phone number is displayed if there is data, and the incoming call rejection registration is completed. "Is displayed.

FIG. 14 is a flowchart showing processing when the mobile terminal device 100 receives an incoming call.
When there is an incoming call, the control unit 200 of the portable terminal device 100 acquires the caller's telephone number (caller number) and stores it in the RAM 202 (step 61).
Then, the incoming call rejection list storage unit 162 is examined as to whether or not the acquired caller number is present in the incoming call rejection list (step 62).
If the caller ID is present in the incoming call rejection list (step 62; Y), the control unit 200 performs an incoming call rejection process (step 63) for the incoming call, and then ends the process.

When the caller number does not exist in the incoming call rejection list (step 62; N), the control unit 200 determines whether or not the caller number is registered in the phone book of the phone book storage unit 163 (step 64).
When the caller number is registered in the phone book (step 64; Y), the control unit 200 displays the phone book information (step 65), and proceeds to step 69.
On the phonebook information display screen, it is displayed according to the contents registered in the phonebook. For example, if the registered caller's name (or nickname) and the phone number are grouped, the group name and outgoing The original telephone type (a distinction between a fixed telephone, a mobile phone, etc.) etc. is displayed.

If it is not registered in the incoming call rejection list or the telephone directory, the control unit 200 further determines whether or not the caller number exists in the nuisance call DB storage unit 161 (step 66).
When the caller number exists in the nuisance call DB (step 66; Y), the control unit 200 displays the nuisance call (step 68). On the other hand, when the caller number does not exist (step 66; N), the incoming call number Display is performed (step 67), and the process proceeds to step 69.
Annoying phone call display and incoming phone number display will be described later with reference to FIG.

  Except for the case of incoming call rejection (step 63), the control unit 200 performs incoming call response processing corresponding to the user operation in the display corresponding to each step (step 69), and ends the processing.

FIG. 15 shows screen transitions for annoying phone call display, incoming phone number display, and incoming call rejection registration for incoming calls from caller numbers not registered in the incoming call rejection list or the telephone directory.
FIG. 15A shows an incoming call screen (nuisance call display) when it is not registered in the incoming call rejection list or the phone book but is registered in the unwanted telephone DB. As shown in this figure, a display for notifying that there is a possibility of a nuisance call such as “it is a suspicious number of a nuisance call” is displayed on the display screen together with the caller number.
FIG. 15B shows an incoming call screen (incoming call number display) in the case where it is not registered in the incoming call rejection list, the telephone directory, or the unwanted telephone DB. As shown in this figure, the caller number is displayed on the display screen.

At the bottom of both screens of FIGS. 15A and 15B, a “reject” button for performing a reject operation for the caller ID during the incoming call is displayed. When this “reject” button is selected by the user, the control unit 200 displays a submenu screen for rejection as shown in FIG. 5C, and displays a menu for rejecting an incoming call and registration for rejecting the incoming call. The
When the first incoming call rejection is selected on this submenu screen, the control unit 200 rejects the incoming call for the current incoming call and ends the call.
On the other hand, when the second incoming call rejection registration is selected, the control unit 200 rejects the incoming call this time and ends the call, and registers the caller number in the incoming call rejection list storage unit 162.
Note that the end of the talk may be ended after the end screen is displayed in FIG.

FIG. 16 shows a screen display during call and a transition screen for incoming call rejection registration.
FIG. 16A shows the screen during a call.
This in-call screen is displayed when the other party goes off-hook with respect to the outgoing call from the mobile terminal device 100 as described with reference to FIG. 12 and when the mobile terminal device 100 goes off-hook in the incoming call processing during the incoming call.
On the screen during a call, a display indicating that the call is in progress, “calling”, a telephone number of the other party (excluding an incoming call when the caller ID is not displayed), and a call time are displayed.

When the “reject” button at the bottom of the screen is selected by the user on this call screen, the control unit 200 displays a screen for a submenu for rejection as shown in FIG. The rejection registration menu is displayed.
When the first rejection is selected on the submenu screen, the control unit 200 ends (ends) the current call.
On the other hand, when the second rejection registration is selected, the control unit 200 ends the current call (end call) and registers the telephone number of the other party in the incoming call rejection list storage unit 162.
Note that the end of the talk may be ended after the end screen is displayed in FIG.

FIG. 17 shows a screen during the end of conversation display.
FIG. 17A shows an end call display screen when communication is cut off from a call, outgoing call, or incoming call with the other party stored in the telephone directory storage unit 163. In this case, the control unit 200 displays the message “disconnected” indicating that the communication has been disconnected, and the display of the communication partner registered in the telephone directory storage unit 163 (if registered) for a predetermined time (for example, 3 seconds). ) After displaying, move to the standby screen.

  On the other hand, when the call is an end of a call, outgoing call, or incoming call with a partner not stored in the phone book storage unit 163, as shown in FIG. 17 (b), registration in the phone book, incoming call rejection registration, or registration A screen for selecting one of the following is displayed. In this screen, the control unit 200 registers the telephone number targeted for a call or the like in the phone book storage unit 163 when the phone book registration is selected by the user, and receives the incoming call rejection list storage unit when the incoming call rejection registration is selected. If it is registered in 162 and not registered is selected, it is finished as it is, and a standby screen is displayed.

FIG. 18 shows an incoming call rejection number deletion screen for requesting deletion of an incoming call rejection number.
This incoming call rejection number deletion screen is displayed when a new incoming call rejection registration operation is performed from each of the states described in FIG. 12 when the maximum number of incoming call rejection registrations (for example, 100) has already been reached. It is a screen.
In order to perform new incoming call rejection registration, it is necessary to delete any of the registered incoming call rejection numbers, so the control unit 200 displays an incoming call rejection number deletion screen.
In this incoming call rejection number deletion screen, the control unit 200 displays one deletion candidate from the order of the telephone number data with the oldest incoming call date among the incoming call rejection numbers that also exist in the nuisance call DB storage unit 161.
In this display, as shown in FIG. 18, since the incoming call rejection list is full, a comment that it is necessary to delete for new registration, and the final incoming date, telephone number, Displays the number of rejected calls.

On the incoming call rejection number deletion screen in the present embodiment, as shown in FIG. 18, “Yes”, “No”, and “Next candidate” buttons are displayed as operation buttons for the displayed deletion candidates.
When “Yes” is selected, the control unit 200 deletes the displayed incoming call rejection number from the incoming call rejection list, and when “No” is selected, the new registration is canceled (cancelled), and the “next candidate” is displayed. When selected, the next deletion candidate information is displayed.

The control unit 200 automatically displays the deletion candidates as they are after they are displayed as deletion candidates in the order of the telephone number data with the oldest incoming call date among the call rejection numbers that are also present in the nuisance call DB storage unit 161. It may be deleted.
In addition, the deletion candidates are ordered from the oldest arrival date to the oldest, but in addition, the registration date may be the oldest or the number of times the incoming call was rejected. The user may set whether to determine the order.
Furthermore, in the above-described embodiment and the modification, the case where the incoming call rejection number that also exists in the nuisance call DB storage unit 161 is the target of the deletion candidate has been described, but the entire incoming call rejection list is the target. May be.

Next, a list display of incoming call rejection numbers by user operation will be described.
FIG. 19 shows an incoming call rejection list screen and its transition screen.
When the user performs an operation for referring to the registered incoming call rejection list from the waiting menu, the control unit 200 displays an incoming call rejection list screen as shown in FIG.

On this incoming call rejection list screen, the incoming call rejection numbers registered by the user for incoming call rejection are displayed in a list in a predetermined order. At the time of this list display, the control unit 200 determines whether or not the incoming call rejection number to be displayed is also registered in the nuisance call DB storage unit 161 from “database registration” (see FIG. 5) of the incoming call rejection list storage unit 162. If it is determined and registered, it is clearly indicated that the incoming call rejection number also corresponds to a nuisance call. As shown in FIG. 19A, the control unit 200 displays an icon (stray) indicating that the call is a nuisance call at the head of the corresponding incoming call rejection number.
In addition to the icon (stray), other icons may be displayed to indicate that the call is a nuisance call. In addition to the icon, “change character color”, “change background color”, “change font”, etc. You may make it show clearly.

  As the predetermined list order, for example, any one of the order of arrival date, the order of registration date, the order of telephone number, the order of risk in the nuisance telephone number database, and the order of the number of rejected incoming calls can be selected. Sorted and displayed in the order selected by.

As shown in FIG. 19A, the incoming call rejection number selected by operating the cursor movement key is clearly indicated (indicated by a square frame in the figure).
In this state, when the “detail” button on the screen is selected, the control unit 200 displays a detail screen corresponding to the selected incoming call rejection number, as shown in FIGS.
The detailed screen of FIG. 19B is a screen when the incoming call rejection number is also registered in the nuisance call DB, and the control unit 200 displays the number of incoming calls rejected, the degree of danger, Display phone number, registration date, last call date, etc.
On the other hand, the detailed screen of FIG. 19C is a screen when the incoming call rejection number is not registered in the nuisance call DB, and the control unit 200 indicates that “no nuisance call DB is not registered” instead of the degree of risk. Is displayed.

FIG. 20 shows a modified example related to the method of clearly indicating an unwanted call on the incoming call rejection list screen.
In the present embodiment shown in FIG. 19, a case has been described in which an icon (stray) that clearly indicates that the call is a nuisance call is displayed at the beginning of the corresponding incoming call rejection number, but in the modification shown in FIG. An icon indicating the degree of danger of the incoming call rejection number stored in the incoming call rejection list storage unit 162, that is, an icon for each degree of danger may be displayed.
FIG. 20A displays (danger), (medium), and (low) as risk level icons corresponding to the risk levels “high”, “medium”, and “low” corresponding to the incoming call rejection number, respectively. However, “danger”, “danger”, and “danger” may be used as icons according to the degree of danger.
Moreover, you may make it display a danger level with an alphanumeric character etc., FIG.20 (b) is an example which displayed the icon which shows that a danger level is so large that a number is large.

Next, a case where a specific incoming call rejection number is deleted from the incoming call rejection list screen will be described. In addition, when determining the overall risk described later, it is possible to apply the total risk instead of the risk described below.
FIG. 21 shows the screen transition when the incoming call rejection number is deleted.
When one of the incoming call rejection numbers displayed in the list is selected on the incoming call rejection list screen shown in FIGS. 19 and 20 and the “detail button” at the lower part of the screen is selected, the control unit 200 selects FIG. A menu screen pops up as shown in a).
When the second sort is selected on the pop-up menu screen of FIG. 21, sort items are displayed, and the incoming call rejection numbers are displayed in the order of the selected sort items. When the third new rejection is selected, a screen for newly registering an incoming call rejection is displayed, and the telephone number input (or selected from the history) is registered in the incoming call rejection list.

  On the other hand, when the number 1 deletion is selected on the pop-up menu screen, the control unit 200 determines that the incoming call rejection number to be deleted has a high risk level due to the nuisance call DB (the risk level “high” in this embodiment). ”, But“ high ”and“ medium ”may be applicable), the deletion lock is applied, and as shown in FIG.

As a modified example, as shown in FIG. 21C, for an incoming call rejection number with a high risk level due to the nuisance call DB, the control unit 200 pops up a screen informing that the risk level is high. It may be deleted when “Yes” is selected by the user.
In addition to the example shown in FIG. 21 (c), the notice sentence is a display that actively encourages users not to delete such as "This is a high-risk telephone number. It is recommended not to delete." May be.
Although not shown, when deletion of a call rejection number with a high degree of risk is permitted, the number of confirmation operations may be increased more than a normal data deletion operation, or a special operation (for example, password input) may be performed. You may make it request.

Further, the pop-up message displayed according to the degree of danger may be changed.
For example, the message or background color is changed or the message content is changed according to the degree of danger.

Further, the number of pop-ups, that is, the number of steps until erasure may be changed according to the degree of danger.
For example, as shown in the following (a) to (b), when deleting a phone number having a high degree of risk, a confirmation message is popped up many times. In this case, the display in “” is a pop-up screen display, and the right arrow → indicates that an operation indicating a positive (erase) intention (selection of “Yes” button or “Execution” key) has been performed.
(A) Low risk: “Delete” → Delete (b) Medium risk: “Delete” → “It also applies to unwanted phone numbers. Are you sure you want to delete?” → Delete (c) Risk High: “Erase” → “This also applies to unwanted phone numbers. Do you want to delete it?” → “This is a high-risk phone number. Are you sure you want to delete it?” → Delete The higher the incoming call rejection number, the more the operation amount of the user necessary for erasure increases, and the erasure can be made difficult.

As described above, according to the present embodiment, not only registration of incoming call rejection, but also display of the incoming call rejection list and deletion operation of the incoming call rejection number are performed based on the unwanted telephone DB downloaded from the unwanted telephone DB server 800. I have to.
Thereby, the user can easily recognize that the incoming call rejection number registered by himself / herself is a telephone number that is recognized as a nuisance call for many people.
Also, deletion of incoming rejection numbers (nuisance calls) with a high degree of risk is weighted more than the deletion of incoming rejection numbers with a low degree of danger or incoming rejection numbers that are not in the unwanted telephone DB, or Since deletion is impossible, the user can surely recognize the degree of danger and annoyingness of the number.

Next, a description will be given of a first modification in which the degree of risk for each incoming call rejection number is determined.
In the embodiment, the case where the risk level of the nuisance call DB acquired from the nuisance call DB server 800 is used as it is as the risk level of the incoming call rejection list storage unit 162 has been described, but in this modification, the risk level of the nuisance call DB is used. In addition, the risk is determined in consideration of the number of times each incoming call is rejected.

FIG. 22 shows the incoming call rejection list storage unit 162 when the degree of risk is determined in consideration of the number of incoming call rejections.
In this first modified example, as shown in FIG. 22A, the overall risk is determined from the rank of the risk by the nuisance call DB and the rejection frequency rank by the number of times the mobile terminal device 100 rejects the incoming call.
The nuisance call DB rank is determined to ranks “3”, “2”, and “1” according to the risk levels “high”, “medium”, and “low” of the nuisance call DB.
On the other hand, as shown in FIG. 22 (b), the rejection number rank is 1 to 10 times rank “1” and 11 to 50 times rank “2” according to the number of call rejections of each call rejection number. "Rank" 3 "is determined 51 times or more.
Then, the total value of the value of the nuisance call DB rank and the value of the rejection frequency rank becomes the overall risk of 1 to 6 finally digitized.
This total risk (numerical value) is displayed as an icon at the head of the corresponding incoming call rejection number in the incoming call rejection list, as shown in FIG.
However, as shown in FIG. 20A, from the total value of the nuisance call DB rank and the rejection frequency rank, 1 and 2 are the overall risk “low”, 3 and 4 are the overall risk “medium”, 5 6 may be displayed as the overall risk “high”.

FIGS. 22C and 22D show the second modification in the case of determining the rejection frequency rank. This 2nd modification performs further modification on the premise of the 1st modification.
In this second modification, the number of incoming call rejections is weighted according to the incoming call date and time (multiplied by a coefficient) for each incoming call so that the older incoming call rejection is less likely to be reflected in the rank.
That is, as shown in FIG. 22 (c), the coefficient when the incoming call rejection date is old is determined to be 0.2, the coefficient when it is medium is 0.5, and the coefficient when it is new is determined to be 1. Here, incoming calls one year or older from the incoming call rejection list display date are “old”, incoming calls from the incoming call rejection list display three months ago are “new”, and incoming calls during that period are “medium”. Is optional.
Then, as illustrated in FIG. 22D, when there are four incoming calls, the number of times each incoming call is multiplied by a coefficient corresponding to the incoming call rejection date is calculated, and the total value 1.9 is calculated. This is the number of rejections for the incoming call rejection number.

  According to the first and second modified examples described above, not only the risk level of the nuisance call DB but also the number of incoming calls rejected is reflected in the total risk level. Therefore, the total risk level suited to the user of the mobile terminal device 100 Can be displayed or deleted.

In the first and second modified examples, since the risk level of the nuisance call DB is set only when a person other than the user rejects the call similarly to the user, the call rejection that does not exist in the nuisance call DB. For the number, regardless of the number of incoming call rejections in the mobile terminal device 100, the overall risk is “0”.
However, the rank based on the number of incoming calls rejected may be determined in consideration of the risk being assigned by the difference data of the unwanted telephone DB at a later date.
Also, for the incoming call rejection number that does not exist in the nuisance call DB, the variation described in FIG. 22 may be applied to determine the value of the rejection frequency rank as the total risk.

As described above, in the present embodiment, when displaying the “rejection list” of the call rejection numbers registered by the user for rejecting the call in the mobile terminal device 100, each call rejection number is acquired from the nuisance call DB server 800. It is compared with each nuisance telephone number included in the nuisance telephone DB, and the fact is clearly indicated (for example, a matching icon is displayed) in the matching incoming call rejection number.
In addition, when additional information such as risk information is added to the nuisance telephone number of the acquired nuisance telephone DB, in addition to the display indicating that they match when the incoming call rejection list is displayed on the mobile terminal device 100 / Display icons for changing the risk level (risk level icons, alphanumeric characters, etc.).
Also, using the acquired nuisance call DB, the degree of danger for the call rejection number that matches the nuisance call number is determined, and the management form (display form, delete operation form) in the call rejection list for each telephone number Is changing.

For this reason, according to the described embodiment, the user easily determines whether or not the incoming call rejection number (phone number) in the “incoming call rejection list” registered by the user is included in the “nuisance call DB”. be able to.
Then, whether or not the telephone number registered for call rejection in his / her mobile terminal device 100 is a telephone number “a number of users who have subscribed to the nuisance telephone DB construction system recognize that it is a nuisance telephone”. Can be recognized.

The embodiments of the present invention have been described above. However, the present invention is not limited to the described embodiments, and may have other configurations.
For example, in the described embodiment, the mobile terminal device that performs a telephone call or communication by wireless communication has been described. However, the incoming call rejection number described in the embodiment is also applied to various terminal devices such as a fixed telephone connected by wire. The registration function, the rejection list display function of the incoming call rejection number, the function of receiving and storing the nuisance call DB through communication with the nuisance call DB server 800, and the like can be applied.

In the described embodiment, the nuisance call DB server 800 counts the number of registered call rejections in a mobile terminal device that has already been subscribed to a specific telephone number, and nuisance calls according to the number of call rejection registrations. Although registration to the DB and setting of the risk level / nuisance level are performed, not only the number of registered call rejection numbers but also the rank of the risk level, each mobile terminal device 100 rejects an incoming call You may make it consider the frequency | count of refusal.
In this case, in the mobile terminal device 100, in addition to registration of the incoming call rejection number, incoming call rejection for the registered incoming call rejection number is also set as a report target (incoming call rejection report) to the nuisance call DB server 800. The incoming call rejection report in the mobile terminal device 100 may be reported to the nuisance telephone DB server 800 every time an incoming call is rejected, and is reported every predetermined number of times (for example, every 5 times or 10 times). It may be.

On the other hand, in the nuisance call DB server 800, the registration to the nuisance call DB and the setting of the risk / nuisance level are performed based on the report of the call rejection number registration and the call rejection report (or the number of call rejection included in the report). Do.
That is, the nuisance call DB server 800 stores the number of call rejections (total value) for each nuisance telephone number, and when there is a report of call refusal from the mobile terminal device 100, the number of call rejections for the nuisance telephone number is counted. Up.
Then, the control unit 820 of the nuisance call DB server 800 converts the number of incoming call rejections into n reports (for example, 10 times) and converts the number of incoming calls into one report of incoming call rejection registration, thereby determining the number of incoming calls. To reflect the sum of

  Further, in the embodiment described above, the case where the degree of risk or annoyance is given according to the number of mobile terminal devices registered with the incoming call rejection number has been described, but the number of mobile terminal devices registered with the incoming call rejection number When the number exceeds the predetermined number, it is possible to register in the nuisance call DB as an object of the nuisance call and not assign the risk level and the nuisance level.

  In the described embodiment and the above-described modification, the case where the nuisance call DB is constructed based on the incoming call rejection registration and the incoming call rejection report from each mobile terminal device 100 has been described. The nuisance call DB may be created based on the above.

In the embodiment described above, a newly registered nuisance telephone number, its risk level, and a change in the risk level are transmitted from the nuisance call DB server 800 to each mobile terminal device 100 as a difference in the nuisance call DB. Although the case has been described, an instruction to delete the unwanted telephone number may be included. The nuisance phone number deletion instruction is transmitted as a difference, for example, when the phone number is no longer used.
In the case where the nuisance call number deletion instruction is not used, the nuisance call DB server 800 periodically checks whether or not each nuisance call number registered in the nuisance call DB storage unit 830 is still used. To be deleted. However, the nuisance telephone number is actually deleted from the nuisance call DB storage unit 161 of each mobile terminal device 100. In the nuisance call DB server 800, the deletion for all users (all mobile terminal devices 100) is completed. Is not deleted. After the completion, it may be deleted from the nuisance call DB storage unit 830 of the nuisance call DB server 800.
The control unit 820 of the nuisance call DB server 800 deletes the nuisance call number that is the deletion target when the nuisance call DB is transmitted to the mobile terminal device 100, and indicates deletion data instead of the risk level. Send.

When there is deletion data in the received nuisance call DB, the control unit 200 of the mobile terminal device 100 deletes the nuisance telephone number associated with the deletion data. In this case, a message such as “Deleted from database” may be displayed in the same manner as described for the case where the degree of risk is changed.
When the deletion data of the nuisance telephone number is to be deleted because the telephone number is not used, the control unit 200 of the mobile terminal device 100 determines whether the nuisance telephone number is also registered in the incoming call rejection list. If it is registered, it may be deleted from the incoming call rejection list storage unit 162. In this case, the control unit 200 confirms, before deletion, that “the number of incoming call rejection target XX-XX is not currently used. Are you sure you want to delete it?” You may make it delete, and you may make it show clearly that it deleted, such as "The number XX-xx of the call rejection object was not used now, and was deleted."

  In the embodiment described above, when making a call from the mobile terminal device 100, if the call is made to the phone number input from the numeric keypad instead of the phone number selected from the phone book, the control unit 200 determines that the phone number is annoying. It may be determined whether or not it matches any of the nuisance telephone numbers registered in the telephone DB, and if they match, a pop-up message may be displayed to alert the user before making a call.

In the embodiment described above, when displaying the incoming call rejection list in the mobile terminal device 100, when the incoming call rejection number registered in the nuisance call DB is clearly indicated by displaying a risk icon or the like. Explained.
On the other hand, not only when the incoming call rejection list is displayed, but in all cases where the incoming call rejection number registered in the nuisance call DB is displayed, the control unit 200 of the mobile terminal device 100 is not limited to the embodiment and the modification example. The display described in (1) may be performed.
For example, when displaying the outgoing call history and incoming call history, a risk level icon is displayed at the head of the incoming call rejection number registered in the nuisance call DB.

Further, in all cases where the phone number is displayed, the control unit 200 of the mobile terminal device 100 can be configured to use both the case where the phone number is registered only in the incoming call rejection list, the case where only the unwanted telephone DB is registered, It may be determined whether or not any of the cases registered in the above is registered.
For example, a (reject) icon is displayed for a phone number registered only in the incoming call rejection list, and a (stray) icon is displayed for a phone number registered only in the nuisance call DB. (Reject) icon is displayed on the phone number. In the case of the latter two, when the risk level based on the nuisance call DB is determined, the color and size corresponding to the risk level may be changed.
If the telephone number is not registered in any of them, only the telephone number is displayed.

In the embodiment described above, the nuisance call DB is acquired from the nuisance call DB server 800 and stored in the nuisance call DB storage unit 161, and it is determined whether or not the incoming call rejection number exists in the stored nuisance call DB. Explained the case.
On the other hand, the nuisance call DB is not stored in the mobile terminal device 100, but the nuisance call DB server 800 is inquired whether or not the incoming call rejection number also corresponds to the nuisance call DB, and the answer result is determined. May be.

DESCRIPTION OF SYMBOLS 100 Portable terminal device 110 Wireless communication part 120 Display part 130 Calling part 140 Key operation part 160 Information storage part 161 Nuisance call DB storage part 162 Incoming call rejection list storage part 163 Phonebook storage part 200 Control part 210 Wireless communication control part 220 Nuisance call DB management unit 230 outgoing / incoming history management unit 240 incoming call rejection processing unit 250 incoming call rejection list management unit 260 selection information transmission unit 270 incoming call rejection list display control unit 800 nuisance telephone DB server 820 control unit 830 nuisance telephone DB storage unit 840 registration information storage Part

Claims (8)

A registration means for registering a telephone number to be rejected as a call rejection number;
An incoming means for receiving a connection request from another device;
Caller number acquisition means for acquiring a caller number of the other device that has made the connection request;
If the acquired caller number is the registered incoming call rejection number, incoming call rejection means for rejecting incoming calls;
A nuisance call DB acquisition means for acquiring a nuisance call DB in which a nuisance call number determined to be a nuisance call of a predetermined level or higher is registered and a risk level corresponding to each nuisance call number is set;
Nuisance call determination means for determining whether or not the incoming call rejection number corresponds to the nuisance telephone number depending on whether the incoming call rejection number is registered in the nuisance telephone DB ;
An overall risk determination means for determining an overall risk based on the number of incoming calls rejected for the call rejection number and the risk set in the nuisance call DB;
When the registered incoming call rejection number is displayed, if it is determined that the incoming call rejection number also corresponds to the nuisance call, the display control means for clearly indicating that , and
The display control means, as an indication to that effect, displays according to the determined overall risk,
The portable terminal device characterized by the above-mentioned. The overall risk determination means uses the number of incoming call rejections weighted to be smaller as the incoming date is older, as the number of incoming call rejections for determining the overall risk.
The mobile terminal device according to claim 1 . Providing a deletion means for deleting the registered call rejection number as an object of call rejection;
The deletion means increases the operation amount of the user necessary for deletion as the risk of the incoming call rejection number to be deleted is higher, or as the overall risk is higher.
Mobile terminal device according to claim 1 or claim 2, characterized in that. 2. The incoming call rejection number by the display control means is a case where an incoming call rejection number is included in an incoming call history display or a list of registered incoming call rejection numbers is displayed. The mobile terminal device according to any one of claims 1 to 3 . Report means for reporting the incoming call rejection number newly registered by the registration means to the nuisance call DB server,
The nuisance call DB acquisition means acquires the nuisance call DB from the nuisance call DB server that creates the nuisance call DB based on incoming call rejection numbers reported from a plurality of portable terminal devices.
It portable terminal device according to any one of claims of claims 1 to 4, characterized in. The reporting means further reports the incoming call rejection number in which the incoming call rejection by the incoming call rejection means has occurred,
The portable terminal device according to claim 5 . The reporting means reports the incoming call rejection by the incoming call rejection means every predetermined number of times.
The mobile terminal device according to claim 6 . A registration function for registering the phone numbers that are subject to call rejection as call rejection numbers;
An incoming call function for receiving connection requests from other devices;
A caller ID acquisition function for acquiring a caller ID of the other device that has made the connection request;
When the acquired caller number is the registered incoming call rejection number, an incoming call rejection function for rejecting incoming calls;
A nuisance call DB acquisition function for acquiring a nuisance call DB in which a nuisance call number determined to be a nuisance call of a predetermined level or more is registered and a risk level corresponding to each nuisance call number is set;
A nuisance call determination function for determining whether the incoming call rejection number is registered in the nuisance call DB or not, and whether or not the nuisance call number is also applicable;
An overall risk determination function for determining an overall risk based on the number of incoming calls rejected for the call rejection number and the risk set in the nuisance call DB;
When displaying the registered incoming call rejection number, if it is determined that the incoming call rejection number also corresponds to the nuisance call, a portable terminal for causing a computer to implement a display control function that clearly indicates that fact A program ,
The display control function, as an indication to that effect, displays according to the determined overall risk,
A portable terminal program characterized by that .

Images