JPH08204826A - Method for informing reject frequency in incoming reject service - Google Patents

Abstract

PURPOSE: To attain a reject frequency information method in incoming reject service capable of counting the incoming reject frequency of embarrassing calls and judging the existence of embarrassing calls. CONSTITUTION: When a contracted subscriber dials a prescribed telephone number '144' for incoming reject service from his (or her) own telephone set 53, guidance for receiving a succeeding dial is sent from a switchboard 52 to the subscriber. Then the subscriber dials a prescribed telephone number '4' for reject frequency informing processing. At the time of receiving the telephone number '4', the switchboard 52 reads out the number of incoming reject calls stored in a current month counter and a preceding month counter from incoming reject number data corresponding to the subscriber concerned and sends the number of incoming reject calls to the subscriber as guidance. The subscriber can obtain the number of rejected incoming calls from the number of incoming reject calls and utilize the information for the updating of succeeding incoming reject service.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of notifying the number of rejects in an incoming call rejection service for notifying the number of incoming calls rejected in an incoming call rejection service and a nuisance nuisance call termination service.

[0002]

2. Description of the Related Art A nuisance call termination service is an effective telephone service for repelling, for example, a prank call or a relatively unfavorable call that is made relatively frequently, such as investment or financial relations. According to the request of a person, the contract is registered and set for each telephone subscriber.
Then, when the telephone subscriber has registered the nuisance call end service, the call rejection number data as shown in FIG. 9 is provided corresponding to the identification information such as the telephone number of the telephone subscriber. The telephone number of the other party who should reject the incoming call is stored in the rejection number data.

That is, the call rejection number data shown in FIG. 9 is stored as a maximum registration number, which is the number of call rejection parties that can be registered, a current registration number, which is the number of call rejection parties currently registered, and a rejection ID. In the example shown in FIG. 9, 6 is set as the maximum number of registrations and 4 is registered as the current number of registrations. A memory area corresponding to the number of registrations is provided, and the telephone number of the call rejection partner is stored in this memory area.

When a telephone subscriber who has made a contract for the nuisance call termination service receives an incoming call, it is determined whether or not the calling subscriber who originated the incoming call is an incoming call rejection party. Check from the telephone number of the call rejection party stored in the rejection number data. If the result of this check is that the telephone number of the calling subscriber who originated this incoming call does not correspond to any of the telephone numbers of the call recipients in the call rejection number data, the call is rejected and the call is rejected. If the calling subscriber's telephone number corresponds to any of the telephone numbers of the call rejection parties in the call rejection number data, the call is judged to be the call rejection party and the incoming call is accepted. It refuses and gives a rejection guidance.

[0005]

In the conventional nuisance call termination service described above, the telephone subscriber who has contracted for this service will not receive nuisance call from the call rejection party set in the call rejection number data. Is preferable, but because the subscriber does not have any nuisance call, the nuisance call is not received, or the nuisance call is still present but the nuisance call is rejected by this service. In addition, since it is unknown whether or not a nuisance call will be made, there is a problem that it is not possible to accurately determine whether or not the service should be continued when the contract of the service is renewed.

The present invention has been made in view of the above,
It is an object of the present invention to provide a method of notifying the number of rejections in an incoming call rejection service that can count the number of rejections of nuisance calls and determine whether there is a nuisance call.

[0007]

In order to achieve the above object, the method of notifying the number of rejects in the call rejection service of the present invention is such that the exchange rejects the call corresponding to at least the identification information of the subscriber who has contracted to reject the call. Equipped with incoming call rejection number data that stores the identification information of the target subscriber, and when an incoming call is made to a subscriber who contracted the incoming call rejection, the incoming call rejection number data of the incoming call rejection number data corresponding to the identification information of the contracted subscriber Comparing the identification information of the subscriber and the identification information of the incoming call,
The number of times the incoming call rejection number data is rejected in the incoming call rejection service that determines that the incoming call is an incoming call that should be rejected if they match and controls the incoming call to not connect to the contract subscriber. Is provided, and when an incoming call is received from the telephone number of the incoming call refusal target in the exchange, the incoming call is controlled so as not to be connected to the contract subscriber, and the rejection number counter is counted up, When the exchange receives an incoming call of a predetermined service number corresponding to the rejection number notification request, the subscriber is requested to input identification information, and the received identification information is used to search the incoming call rejection number data. When there is incoming call rejection number data with the same identification information, the rejection number counter value is acquired, and the acquired rejection number counter value is transmitted to the subscriber. It is the gist of.

[0008]

According to the method of notifying the number of rejections in the call rejection service of the present invention, when the subscriber who contracted the call rejection receives a call from the telephone number of the call rejection target, the call is not connected to the contracted subscriber. In addition to counting up the refusal number counter, when there is a refusal number notification request, the refusal number counter value is acquired, and the acquired refusal number counter value is transmitted to the contract subscriber for notification.

[0009]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a flow chart showing an incoming call process in the method of notifying the number of rejections in the incoming call rejection service according to an embodiment of the present invention. As shown in the figure, in the present embodiment, when an incoming call occurs to a nuisance call subscriber who has contracted for the nuisance call exception service, it is checked whether or not the incoming call is a telephone subscriber who is a call rejection target. (Step S11).

This check is performed within the telephone number of the other party to whom the incoming call should be rejected, which is stored in the rejection ID of the incoming call rejection number data shown in FIG. 2 of this embodiment corresponding to the incoming call rejection number data shown in FIG. 9 described above. Is based on whether or not there is a telephone number of the calling subscriber who originated the incoming call. That is, when the telephone number of the calling subscriber who originates the incoming call corresponds to any of the telephone numbers of the call rejection parties stored as the rejection ID in the call rejection number data shown in FIG. It is judged that the calling subscriber who originated the incoming call is a subscriber for which the incoming call is rejected, the incoming call is rejected, the number of times the incoming call is rejected is counted up, and this count value is shown in FIG. It is stored in the number data (step S12). Then, the rejection guidance is sent to the telephone subscriber of the incoming call (step S
13). The incoming call rejection number data shown in FIG. 2 is provided for each telephone subscriber who has contracted for the incoming call rejection service.

In the check in step S11, if the calling subscriber who originated the incoming call is not the telephone subscriber for which the incoming call is rejected, the incoming call is connected (step S).
14). Needless to say, the above processing is achieved by the control processing device of the telephone exchange.

The incoming call rejection number data shown in FIG. 2 will be described in more detail. The incoming call rejection telephone data shown in the figure is stored in the storage device of the telephone exchange, and stores the maximum number of registrations, the current number of registrations, and the rejection ID similar to the conventional incoming call rejection number data shown in FIG. In addition to having items, it has storage items of a final registration position, a cyclic counter, a previous month counter, and a current month counter.

The previous month counter and the current month counter are parts for storing the number of incoming call rejections counted up in step S12 of the processing of FIG. Also, the final registration position indicates the position on the storage device that was registered last among the telephone numbers of the call rejection parties of the current registration number, and the telephone number of the call rejection party to be registered next is this final registration. It will be stored in the next position.

Further, the cyclic counter clears the contents of the previous month counter at the beginning of each month, moves the contents of the current month counter to the cleared memory location, and after this move, clears the contents of the current month counter and clears the contents. It is used for clearing each counter for storing the new month count value in the specified memory location and controlling the movement of the count value. Details of this will be described later with reference to FIG. It should be noted that in FIG. 2, only one line or one telephone number of the call rejection party stored as the rejection ID is shown, but in reality, the storage capacity corresponding to the maximum registration number is sufficient. It is provided. When the current number of registrations is less than or equal to the maximum number of registrations, the incoming call rejection partner telephone numbers are sequentially registered from the beginning, but when the number of maximum registrations is exceeded, the oldest number is overwritten.

FIG. 3 is a diagram showing a memory configuration for storing the incoming call rejection number data shown in FIG. As shown in FIG. 3A, a call rejection number list is constructed, and each call rejection number data in this call rejection number list is shown in FIG.
As shown in (b), the maximum registration number, the current registration number, the final registration position, the cyclic counter, the previous month counter,
It is stored as a counter this month. FIG. 3 (b)
As shown in, the previous month counter and this month counter each consist of 7 bits, and the cyclic counter has 2 bits.
Bits are allocated.

Next, with reference to FIG. 4, a process of registering a telephone number to be rejected in the call rejection number data will be described.

As shown in FIG. 4, it is assumed that a malicious call originates from a subscriber's telephone. It is assumed that the telephone number of the malicious call subscriber is not yet registered as the telephone number of the incoming call rejection party in the incoming call rejection number data of the telephone subscriber contracting the incoming call rejection service.

The malicious call originated from the malicious call subscriber arrives at the telephone of the contract subscriber from the originating exchange through the destination exchange. In this case, the originating exchange sends the originating ID of the malicious call subscriber to the terminating exchange. When a malicious call arrives at the subscriber's telephone, the subscriber responds to the malicious call and talks to the other party of the malicious call. , This call is disconnected, and immediately thereafter, an operation for registering the telephone number of the call rejection target in the call rejection number data, for example, the telephone number "144" is dialed to activate the call rejection service.

When the incoming call rejection service is activated, the exchange sends guidance to the contracting subscriber regarding whether or not to register the telephone number of the malicious call subscriber, which is currently applied to the contracting subscriber, in the incoming call rejection number data. Since the message is transmitted, the contracted subscriber dials a predetermined service number in response to this inquiry, for example, "2". Registered in the rejection number data.

As described above, when the telephone number of the malicious call telephone subscriber is registered in the call rejection number data corresponding to the contract subscriber, thereafter, the malicious call telephone subscriber becomes the contract subscriber. Even if a telephone call is made to the subscriber, the malicious call does not arrive at the contract subscriber, so the contract subscriber is not bothered by the malicious call.

Next, with reference to FIG. 5, a description will be given of the processing when the malicious call subscriber registered in the call rejection number data as described above, that is, the call rejection partner subscriber receives a call to the contract subscriber. To do.

As shown in FIG. 5, the telephone subscriber who originates the above-mentioned malicious call, that is, the incoming call rejection partner subscriber registered in the incoming call rejection number data rejects the incoming call from his own telephone 51 through the telephone exchange 52. When a telephone call is made to the telephone 53 of the service contract subscriber, the control processing unit (not shown) of the telephone exchange 52 is provided with the telephone number or subscriber identification information of the call rejection party subscriber corresponding to the contract subscriber. Check the incoming call rejection phone number or identification information registered in the incoming call rejection number data.

As a result of this comparison, when it is determined that there is an incoming call from the incoming call rejection partner subscriber, the exchange 52 does not make an incoming call to the contract subscriber, and the telephone receiver 51 of the incoming call rejection partner subscriber.
The guidance that the incoming call was rejected to
The current month counter of the contracted subscriber's incoming call rejection number data is incremented by +1 to count the number of rejections.

Next, with reference to FIG. 6, a description will be given of a rejection number notification process in which the contract subscriber receives the rejection number of times from the exchange.

As shown in FIG. 6, when the contract subscriber dials a predetermined telephone number for the call rejection service, for example, "144", from his or her telephone 53, the guidance for receiving the next dial from the exchange 52 is contracted. Since it is sent to the subscriber, the contracted subscriber dials a predetermined telephone number for the rejection number notification processing, that is, a predetermined telephone number for effect confirmation, for example, "4". Upon receiving the telephone number, the exchange 52 reads the number of call rejection calls accumulated in the counter of the current month and the counter of the previous month from the call rejection number data corresponding to the contract subscriber, and subscribes to the contract using the number of call rejection calls as guidance. Send to the person. The contracted subscriber can know how many incoming calls are rejected by listening to the number of incoming call rejection calls, and can be useful for the next update of the incoming call rejection service.

FIG. 7 shows the processing when the incoming call rejection party subscriber shown in FIG. 5 receives an incoming call to the contract subscriber, and the processing shown in FIG. 6 in which the contract subscriber receives the incoming call rejection count from the exchange. Is shown as one drawing.

Next, the operation of the cyclic counter will be described with reference to FIG.

As described above, the cyclic counter is provided for clearing the previous month counter and the current month counter at the beginning of each month, and for controlling the process of transferring the contents of the current month counter to the previous month counter, and is composed of 2 bits. It is what

As shown in FIG. 8, this cyclic counter can take four states of 00, 01, 10, and 11, and each of these four states represents the month of the year. That is, "00" represents December, April and August, "01" represents January, May and September, "10" represents February, June and October, and "11". March, July, 1
Each state of the cyclic counter indicates three months, such as January, and which month is actually represented depends on which one of the three months from the current date that the switch internally has. You can see if it represents the moon. That is, assuming that the current date inside the exchange now is, for example, July and the state of the cyclic counter is "10" as shown by the thick frame in the figure, the state of the cyclic counter is " The exchange is configured to judge that "10" represents June of February, June, and October represented by "10".

The state of the cyclic counter representing the month as described above represents the month in which the previous month counter and the current month counter were cleared last time. For example, in the case of "10" described above, the previous month is shown. This shows that the counter and the counter of the current month were cleared last time in June. In this case, it is assumed that the date and time newly moves to July. In reality, when the call rejection number data provided with the cyclic counter is first accessed by the exchange in July, for example, there is a call from the call rejection target subscriber, When the rejection number data is accessed, or when the contracting subscriber accesses the rejection number data for the purpose of notification of the number of rejected calls, the exchange sets the cyclic counter status "1".
0 ”identifies that the previous month counter and the current month counter were last cleared in June.

As a result, the exchange was newly added in July,
It can be seen that the counter is not cleared and the count value is not moved as described above. Therefore, the exchange starts the process of clearing the counter and moving the count value. In this processing, the exchange first clears the count value of the previous month counter, moves the count value of the current month counter to the cleared memory location, and sets the count value of the current month counter up to now as the count value of the previous month counter. At the same time, the count value of the counter of this month is cleared and preparations are made to newly store the count value of July in this memory location. Also, thereafter, the cyclic counter is advanced from 10 to 11.

If the month indicated by the cyclic counter is more than two months old, both the previous month counter and the current month counter are cleared. Also, always manage until 4 months ago, and if there is no access for more than 4 months, it will be divided.

As described above, by using the cyclic counter to manage the clearing and movement of the previous month counter and the current month counter, for example, when a flag for controlling the initialization of the rejection count counter is provided for each month. In comparison, the memory area can be reduced.

In the above embodiment, the case where a telephone number or the like is used to register the contracted subscriber of the incoming call rejection service and the incoming call rejection partner subscriber has been described, but the present invention is not limited to the telephone number. The identification information of each subscriber, such as the accommodation position information on the exchange, may be used.

[0036]

As described above, according to the present invention,
When a subscriber who has contracted to reject a call receives a call from a telephone number that is the target of the call rejection, the call is controlled so that the call is not connected to the contracted subscriber, and the reject count counter is incremented to notify the reject count. If there is, the rejection number counter value is acquired, and the acquired rejection number counter value is sent to the contracting subscriber for notification, so that the contracting subscriber can reduce the number of nuisance calls after making a contract for the call rejection service. The effect of whether or not it can be accurately known, and the next update of the service can be appropriately performed.

[Brief description of drawings]

FIG. 1 is a flowchart showing an incoming call process in a method of notifying the number of rejections in an incoming call rejection service according to an embodiment of the present invention.

FIG. 2 is a diagram showing the contents of incoming call rejection number data provided for each subscriber who subscribes to the incoming call rejection service.

3 is a diagram showing a memory configuration for storing the incoming call rejection number data shown in FIG. 2. FIG.

FIG. 4 is an explanatory diagram showing a process of registering a telephone number of an incoming call rejection target in the incoming call rejection number data shown in FIG.

FIG. 5 is an explanatory diagram showing a process when a malicious caller registered in the incoming call rejection number data, that is, an incoming call rejection partner subscriber receives an incoming call to the contract subscriber.

FIG. 6 is an explanatory diagram showing a rejection number notification process in which the contract subscriber receives the rejection number from the exchange.

FIG. 7 is a flowchart showing a process when an incoming call is rejected from the incoming call rejection partner subscriber shown in FIG. 5 and a rejected number notification process shown in FIG. It is explanatory drawing shown as drawing.

FIG. 8 is an explanatory diagram showing the contents and operation of a cyclic counter.

FIG. 9 is a diagram showing the contents of conventional call rejection number data.

[Explanation of symbols]

 51 Telephones of the subscribers who are rejected by the call 52 Telephone exchanges 53 Telephones of subscribers who have contracts for the call rejection service

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kazuki Yonezawa 1-1-6 Uchisaiwaicho, Chiyoda-ku, Tokyo Nihon Telegraph and Telephone Corporation

Claims (1)

[Claims] 1. The exchange includes at least incoming call rejection number data in which identification information of a subscriber for whom an incoming call is rejected is stored in correspondence with the identification information of a subscriber who has contracted for an incoming call rejection. When a call is generated, the identification information of the call rejection target subscriber of the call rejection number data corresponding to the identification information of the contracted subscriber is compared with the identification information of the incoming call. Is a call that should be rejected and controls the call not to connect to the contract subscriber. In the call rejection service, a rejection number counter that stores the number of times the call is rejected is stored in the call rejection number data. When the exchange receives an incoming call from a telephone number for which the incoming call is rejected, the incoming call is controlled so as not to connect to the contract subscriber, and the rejection counter is counted up. When the exchange receives an incoming call of a predetermined service number corresponding to the rejection number notification request, it requests input of the identification information of the subscriber, retrieves the incoming call rejection number data with the received identification information, When there is call rejection number data with the same identification information, the rejection count counter value is acquired, and the acquired rejection count counter value is transmitted to the subscriber. Notification method.