JP2801969B2 - Phone number list cleaning device and cleaning method - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to a cleaning device for automatically performing a process of deleting an invalid telephone number from a telephone number list included in a customer list such as a so-called telemarketing using a personal computer or the like, and a cleaning device. Related to the cleaning method.

2. Description of the Related Art In a variety of business using a telephone, a customer's telephone number list is extremely important information, and management that does not reduce the value of the information is performed as needed by deleting unnecessary telephone numbers from the list. There is a need. Of course, the customer information on the list also includes fluid information, such that the registered phone number will not be used at some point, will be changed to another new phone number, or originally The wrong phone number may be registered. Such invalid telephone numbers must be removed from the list, and a process for replacing the transferred new telephone numbers with the old telephone numbers in the list is necessary.

In the past, some business was performed for each customer according to the telephone number list, and the list was deleted / updated while checking the response from each customer.

The conventional method of deleting / updating a list along with the execution of a business according to a telephone number list may cause enormous waste or irrationalness depending on the contents of the actual business. In other words, performing an operation even for an invalid customer that needs to be deleted may cause wasteful expenses or inconvenience non-customers. In addition, for the transferred customer, the duties of the old telephone number place and the new telephone number place are performed twice, which wastes time and money.

DISCLOSURE OF THE INVENTION An object of the present invention is to provide a cleaning apparatus and a cleaning method that can efficiently and automatically perform a process of deleting an invalid number in a telephone number list using a personal computer or the like without performing actual work. It is in.

Therefore, in the present invention, by utilizing the advanced bearer service provided by ISDN which is integrally interconnected with the conventional telephone network, the telephone number list cleaning process can be performed with high accuracy and high speed. I made it. That is, the telephone number list cleaning device and the cleaning method of the present invention are a system using a computer such as a personal computer, and have the following requirements (1) to (5).

(1) Connected to the ISDN and executes a circuit-switched call control procedure specified in ITU-T Recommendation Q.931 as a calling terminal.

(2) A telephone number is read in order from a telephone number list to be cleaned, the telephone number is set as a called number, and a "call setting" message in which unrestricted digital information (or restricted digital information) is specified as a transmission capability is transmitted to the network. To send to.

(3) When the call of the transmitted "call setup" message is accepted and a "call" message or a "response" message is transferred from the network, a "disconnection" message is immediately transmitted to the network to execute a disconnection recovery sequence. At the same time, the telephone number in the “call setting” message is determined as a valid number.

(4) If a "disconnect" message is transmitted from the network without accepting the transmitted "call setting" message, the disconnection recovery sequence is immediately executed, and the "disconnect" message from the network is attached. The reason indication of the information element is picked up, and it is determined whether the telephone number of the "call setting" message is treated as a valid number or an invalid number according to the contents of the reason indication.

(5) Create a new list that distinguishes between telephone numbers determined as valid numbers and telephone numbers determined as invalid numbers.

Further, in the present invention, in addition to the above requirements, when the content of the reason indication transferred from the network is "change of the other party's subscriber number", the reason information is entered in the diagnostic information field attached to the reason indication. A system that picks up a new telephone number that has been picked up and replaces the telephone number in the “call setup” message with the picked up new telephone number to create a new list can be realized. Further, depending on the contents of the reason display, it is appropriate to suspend the determination of validity / invalidity of the telephone number and to enter the telephone number in the reserved number list. In this case, the most appropriate cleaning process can be performed by performing the most reexamination.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a hardware configuration of a system for implementing a telephone number list cleaning device according to an embodiment of the present invention.

FIG. 2 is a flowchart showing an outline of a main part of the cleaning process in the system of FIG.

BEST MODE FOR CARRYING OUT THE INVENTION ==== Basic Configuration and Operation of System ==== FIG. 1 shows a system configuration according to an embodiment of the present invention. Here, a general personal computer 1 is used as an ISDN terminal. The personal computer 1 includes a CPU 2, a memory 3, a hard disk device 4, a floppy disk device 5, a display device 6, a keyboard 7, an ISDN communication board 8, and the like. This personal computer 1 is connected to ISDN via an ISDN communication board 8 and a line connection device (DSU) 10. As is well known, I
SDN and the telephone network are interconnected together.

A list of telephone numbers to be cleaned is provided in a predetermined format recorded on a floppy disk. The disk is set in the floppy disk device 5 and a cleaning instruction is given by designating a list name from the keyboard 7. Then, the CPU 2 reads the specified telephone number list from the floppy disk and stores it in the memory 3, and starts the cleaning process shown in the flowchart of FIG.

First, one telephone number is picked up from a telephone number list according to a predetermined order, and execution of a call setting sequence is started (step 100 → 200). In the call setting sequence, first, a "call setting" message in which the telephone number read from the list is set as the called number and unrestricted digital information is specified as the transmission capability is transmitted to the network (step 20).
1). The call setup sequence 200 proceeds according to the circuit-switched call control procedure specified in detail in ITU-T Recommendation Q.931. Since the control procedure of the circuit-switched call is described in detail in various documents, it will not be described in detail in this specification, but a typical sequence proceeds as follows.

The network that has received the "call setting" message from the calling terminal sends a "call setting accepted" message notifying the B channel to be used to the calling terminal, and sends a "call setting" message to the called terminal. With this, various performances required of the receiving terminal are specified. The receiving terminal checks the performance, and the receiving terminal that has confirmed conformity returns a "call" message to the network (the receiving terminal is in a calling state). This "call" message is sent from the network to the originating terminal. When a response such as off-hook is made at the receiving terminal, a "response" message is sent from the receiving terminal to the network to the calling terminal, and a "response confirmation" message is sent from the calling terminal to the network and from the network to the receiving terminal. Can be Thus, the "call setting" message is accepted and the line is connected.

Also, the call requested by the calling terminal may not be accepted for various reasons. In that case, the network sends a "disconnect" message to the originating terminal and performs a disconnect recovery sequence. At this time, in the reason display item of the information element attached to the "disconnect" message sent from the network to the calling terminal, the reason why the call is not accepted is notified in the form of a reason number.

==== Reason indication of "disconnection" message ==== In ITU-T Recommendation Q.931, the type and number of the reason indication attached to the "disconnection" message are defined as follows.

1. Normal class << Reason number 1 missing number >> This reason display indicates that although the number was valid in format, it cannot be reached at the destination requested by the calling user because the number is currently missing.

<< Reason No. 2 No Route to Designated Transit Network >> This cause indicates that the source device of the cause has received a request to route the call through a special unrecognizable transit network. The source device of this cause is either a non-existent transit network or, if present, a special transit network that does not service the destination device of this cause. Therefore, it does not recognize the relay network.

<< Reason No. 3 No route to the other party >> This reason display indicates that the network to which the call has been routed cannot receive the call and thus cannot deliver the call to the called user.

<< Reason No. 6 Channel Unavailable >> This reason display indicates that the channel selected as a result of the channel selection is unavailable to the transmitting terminal.

<< Reason number 7 Incoming call to the channel for which the call has been set >> This reason display indicates that the user has an incoming call, and the incoming call is a similar call (for example, an X.25 virtual call in packet mode) and the user has already received the incoming call. Indicates that it is connected to the set channel.

<< Reason No. 16 Normally Disconnected >> This reason display indicates that the call is disconnected when one of the users involved in the call requests a call disconnection restoration. Under normal conditions, the source of this cause is not the net.

<< Reason No. 17 Received User Busy >> This reason display indicates that the called user cannot accept another call. In this case, the user equipment must ensure communication integrity for incoming calls.

<< Reason No. 18 No response to the called user >> This reason display indicates that the other user is not ringing within the allotted time (timer T303 or T310 defined in this specification expires) specified for the call setup message. Use this when not sending back a message indicating "or" response. "

<< Reason No. 19 Calling user called / No response >> This reason display is used when there is a notification of a call but no response is received within the specified time. This cause is not necessarily caused by the Q.931 procedure, but may be caused by a timer in the network.

<< Reason No. 20 No Subscriber >> This cause may indicate that the mobile station has been logged off (by a signaling procedure over the wireless bus) or that radio communication is not possible with the terminating mobile station (eg failure, out of service or power loss). ).

<< Reason No. 21 Rejection of Communication >> This reason indication is used to indicate that the device that transmitted this cause indication is neither busy nor inconsistent, and can accept the call, but does not accept the call.

<< Reason No. 22 Change of Other Subscriber Number >> This reason indication is to notify the calling user when the called number indicated by the calling user is no longer assigned. At this time, the new called number is included in the diagnostic information field.

<< Reason No. 26 Disconnection recovery of user not selected >> This reason display indicates that the user could not obtain an incoming call.

<< Reason No. 27 Failure of partner terminal >> This reason display indicates that a call to the partner user requested by the calling user could not be received because the interface on the receiving side was not functionally normal. This “function is not normal” means that the signaling message does not reach the partner user. For example, a failure of the physical layer or the data link layer of the partner user interface, or a case where the user device is offline.

<< Reason number 28 invalid number format (incomplete number) >> This reason display indicates whether the incoming number is in an invalid format or not.
Or, it indicates that an incoming call cannot be made to the partner user due to incompleteness.

<< Reason No. 29 Facility rejected >> This cause is returned when the facility requested by the user cannot be provided on the network.

<< Reason number 30 Response to status inquiry >> This reason display indicates that the "status inquiry" message was generated when the "status inquiry" message was received before the message was generated. Display "message.

<< Reason No. 31 other normal class >> This reason display is used only to report a normal status when it cannot be expressed for other reasons in the normal class.

2. Resource unavailable class << Reason number 34 No available lines / channels >> This cause indicates that there is currently no suitable line / channel available to handle the call.

<< Reason No. 38 Network Failure >> This reason display indicates that the network is not functionally normal and the condition is likely to last for a relatively long time. For example, there is a case where it is unlikely to be accepted even if the call is immediately re-issued.

<< Reason No. 41 Temporary Failure >> This reason display indicates that the network is not functionally normal and the state is unlikely to continue for a long time. For example, there is a case where the user can request a re-call almost immediately.

<< Reason No. 42 Switching Unit Congestion >> This reason indication is used to indicate that the switching apparatus causing this reason is congested with high traffic.

<< Reason No. 43 Discarding access information >> This reason indication indicates to the partner user that the network has requested access information (user / user information, low-layer compatibility, high-layer compatibility or sub-address indicated in detailed information). Indicates that it was not delivered. A special type of discarded access information may be included in the diagnostic information.

<< Reason No. 44 Requested line / channel unavailable >> This reason indication is returned when the line or channel notified by the requesting terminal cannot be provided by the interface on the partner side.

<< Reason No. 47 Other Resource Unavailable Class >> This cause is used to report as a network congestion event only when no other reason in the network congestion class can be applied.

3. Service unavailable class << reason number 49 QOS unavailable >> This cause is used to report that the required QOS (as defined in Recommendation X.213) is not provided (eg, throughput or If no propagation delay is provided).

<< Reason No. 50 Requested Facility Not Contracted >> This cause indicates that the requested supplementary service is not provided by the network because the user has not completed the necessary administrative procedures for the network providing the facility.

<< Reason No. 57 Transmission Capability Not Permitted >> This reason display is a transmission capability realized by the device that generated the reason display, but indicates that the user has requested a transmission capability not permitted to the user.

<< Reason No. 58 Currently Unavailable Transmission Capability >> This reason display is a transmission capability realized by the device that generated the reason display, but indicates that the user has requested a transmission capability that is currently unavailable.

<< Reason No. 63 Unavailable Class for Other Services or Options >> This cause is used to report a service unavailable event only when no other cause for the service unavailable class is applicable.

4. Service not provided class << Reason number 65 Unprovided transmission capability designation >> This cause indicates that the device that transmitted the cause does not support the requested transmission capability.

<< Reason No. 66 Unprovided Channel Type Designation >> This reason display indicates that the device that transmitted the cause display does not support the requested channel type.

<< Reason No. 69 Unprovided Facility Request >> This cause indicates that the device that transmitted this cause does not provide the requested supplementary service.

<< Reason No. 70 Restricted digital information transmission capability >> If a device requests unrestricted digital information transmission capability, the device transmitting this cause displays only the restricted digital information transmission capability of the requested transmission capabilities. Indicates that it is supported.

«Reason number 79 Other service or option not provided class» This cause is used to report service not provided only when no other reason for the service not provided class is applicable.

5. Invalid message class << Reason number 81 Invalid call number used >> This cause indicates that the device that transmitted the cause
Indicates that a message with a call number different from the one currently used between network interfaces has been received.

<< Use of Reason No. 82 Invalid Channel Number >> This cause indicates that the device which transmitted the cause has received a request to use a channel number which is not activated. For example, a case where the user device or the network attempts to use the channel numbers 13 to 23 even though the user has subscribed to channels 1 to 12.

<< Reason code 83 No specified suspended call identification number used >> This cause indicates that an attempt was made to resume a call with a different call identification number from the one used for the suspended call. .

<< Reason number 84: Using suspended call identification number >> This cause indicates that the network has received a request to suspend a call, but this suspension request has already been used as a suspended call identification in the interface area where call resumption may take place. Indicates that a call identification (including the case where nothing is performed) was included.

<< Reason No. 85 No Suspended Call >> This cause indicates that the network has received a request to resume the call. However, the call identification included in the call resumption request indicates that it is not currently being used for a suspended call in the interface area where call resumption may occur.

<< Reason No. 86 Disconnected call has been canceled. >> This cause indicates that the network has received a resume request, but this resume request includes the call identification once notified as a suspended call. Indicates that disconnection has already been recovered (by user disconnection or timeout).

<< Reason No. 87 User is not a CUG member >> Refer to supplementary service specifications << Reason No. 88 Terminal attribute mismatch >> This cause is a low-layer or high-layer match that cannot be matched by the device that sent the cause. Indicates that a call setup request having a consistency attribute (eg, data rate) has been received.

<< Reason number 91 Invalid transit network selection >> This reason indication indicates that the transit network identification was received, but is in an incorrect format, as defined separately.

<< Reason No. 95 Other Invalid Message Class >> This cause is used to report an invalid message class event only when no other reason for the invalid message class is applicable.

6. Procedure error (eg unrecognized message) class << Reason number 96 Insufficient required information element >> This cause is an information element (required) that must be present in the message when the device that sent the cause displays the message. Information element).

<< Reason No. 97 Message type not defined or not provided >> This cause is a message that the device that sent the cause displays an undefined message or an unrecognized message type that is defined but not provided. Indicates that the received message has been received.

<< Reason No. 98 Message mismatch with call state or message type undefined >> This cause is used to check whether the message transmitted by the device that sent this cause during the specified call state is not an acceptable message during processing. Indicates that a "status display" indicating a call state that has not been performed has been received.

<< Reason number 99 Information element undefined >> This cause is used when the information element identifier of the device that sent the cause is undefined, or when a message containing an information element that is not provided even if it is defined is received. .
It should be noted that the information element is limited to a case where the device which has transmitted the reason is not necessary for processing the message.

<< Invalid reason 100 information element content >> This cause is an information element provided by the device that transmitted the cause, but one or more fields of the information element are codes that are not provided. Is received.

<< Reason number 101 Call state and message mismatch >> This reason display is used when the received message does not match the call state.

<< Reason No. 102 Recovery by Timer Expiration >> This reason display indicates that the procedure has been started by expiration of the timer in accordance with the error processing procedure of the present Layer 3 specification.

<< Reason number 111 Other procedure error class >> This reason indication is used to report a procedure error event only when other reasons of the procedure error class cannot be applied.

7. Interworker class << Reason number 127 Other interworking class >> This cause indicates that interworking in the network has occurred in which there is no cause to operate. Thus, the exact cause for the message to be sent cannot be ascertained.

==== Flow of Control of Cleaning Process ==== In the cleaning process of the present invention, FIG.
As shown in the flowchart of FIG.
In step, if the call of the sent “call setup” message is accepted and a “call” message or a “answer” message is transferred from the network, the process exits from step 202 or step 203 to step 301 → 302 → 303. Then, a "disconnection" message is immediately sent to the network to execute a disconnection recovery sequence, and the telephone number in the "call setting" message is determined to be a valid number and entered in a valid list. This completes the confirmation process for this telephone number.

Also, in the call setting sequence 200, the call of the transmitted "call setting" message is
When the message is transferred, the process exits from step 204 to the process from step 401 to step 402, immediately executes the disconnection recovery sequence, and picks up the reason display of the information element attached to the `` disconnect '' message from the network, In accordance with the contents of the reason display, a determination is made as to whether the "call setting" message is valid / invalid or on hold for the telephone number.

(A) Effective number The reason indication picked up in step 402 is as follows: <Reason number 3 No route to the other party><< Reason number 7 Incoming call to the channel for which the call has been set >><< Reason number 16 Normal disconnection >><< Reason number 17 "Receiver busy"<< Reason # 18 No callee response >><< Reason # 19 Calling user ringing / no response >><< Reason # 20 no subscriber >><< Reason # 21 Rejected communication >><< Reason # 27 Remote terminal failure >> Reason No. 49 QOS Unavailable >><< Reason No. 50 Requested Facility Not Contracted >><< Reason No. 57 Transmission Capability Not Allowed >><< Reason No. 58 Currently Unavailable Transmission Capability >><< Reason No. 63 Other Service or Option Unavailable Class >> Reason No. 65 Unprovided transmission capability designation >><< Reason No. 66 Unprovided channel type designation >><< Reason No. 69 Unprovided facility request >><< Reason No. 70 Restricted digital information transmission capability 《Reason number 79 Other service or option unprovided class》 《Reason number 88 Terminal attribute mismatch》 If any of the above, the telephone number in the “call setup” message is recognized as a valid number and the telephone Write the number in the valid list (step 403 → 404).

(B) Number change If the reason display picked up in step 402 is "reason number 22 other party number change", the new telephone number entered in the diagnostic information field of the reason display is picked up and the "call" A new telephone number picked up from the telephone number in the "setting" message is entered in the valid list (steps 403 → 405 → 406).

(C) Invalid number If the reason indication picked up in step 402 is any of << reason number 1 missing number >><< reason number 2 no route to designated transit network >><< reason number 6 channel unavailable >> The telephone number in the “call setting” message is recognized as an invalid number, and the telephone number is entered in the invalid list (steps 403 → 405 → 407 → 408).

(D) Judgment suspension If the reason display picked up in step 402 is not any of the reason numbers checked in steps 403, 405, and 407, the telephone number in the “call setting” message is used as both a valid number and an invalid number. Without making a determination, the information is entered in the hold list (steps 403 → 405 → 407 → 409).

As described above, if the investigation processing has been completed for a certain telephone number, the process proceeds to step 501, where it is checked whether or not the processing has been completed for all of the telephone numbers to be cleaned, and if the processing has not been completed. If it is, the process returns to the first step 100 and the above processing is performed for the next telephone number. If all items have been processed, go to step 50
Proceed to 2 to output a new list in a predetermined format.

==== Actual Operational Status ==== A typical telephone number list to be cleaned according to the present invention is a list of telephone numbers included in a customer list such as telemarketing. In Japan at present, most of the telephone numbers included in this type of list are analog telephone network subscriber numbers, and the number of ISDN (INS64) subscriber numbers has been increasing little by little recently.
When such a current telephone number list is cleaned by the mechanism described above, the cleaning device of the present invention
The following response is sent to the ISDN exchange (network).

(A) When the called telephone number is a valid subscriber number of the analog telephone network This number is the largest. The device of the present invention is called "call setup".
Since the call is made with the message specifying unrestricted digital information as the transmission capability, the network returns a "disconnection" message with "Reason number 3 No route to partner". Therefore, the cleaning device enters the telephone number in the valid list. What should be noted here is that no call is made to the telephone to be investigated in making this investigation and determination. In other words, from the point of view of the person being investigated, there is no hassle of forcing an unnecessary call to be answered.

(B) If the called telephone number is changed, regardless of whether it is an analog telephone network or an ISDN subscriber number, the network attaches "Reason number 22 Change subscriber number". "Disconnect" message is returned. In response to this, the present cleaning device picks up a new telephone number entered in the diagnostic information field of the reason display and enters the new number in the valid list.

(C) When the called telephone number is an unused number Regardless of whether it is an analog telephone network or an ISDN subscriber number, the network is “Disconnected” with “Reason number 1 missing number”. "The message is returned. In response to this, the cleaning device enters the telephone number in the invalid list.

(D) When the outgoing telephone number is a valid ISDN subscriber number In this case, the exchange changes according to the situation of the partner equipment. When a call is made at the receiving terminal (partner) by the "call" message from the present cleaning device, and when the other party answers the call, the process proceeds to step 301 in the flowchart of FIG. To start the disconnection recovery sequence and enter the telephone number in the valid list. Also, even when a “disconnect” message is returned from the network, the reason number is set to ♯7, ♯16, ♯17, ♯18, ♯19, ♯20, ♯21, ♯27, as described above. , ♯4
If the phone number is any of 9, 50, 57, 58, 63, 65, 66, 70, or 79, enter the telephone number in the valid list, and the reason number is 2 or 6 If so, enter the telephone number in the invalid list, otherwise enter the hold list.

For each reason number, "valid", "invalid", "pending"
It may be considered that the description in the embodiment may not be the best one to determine the classification. A closer examination of the ISDN subscriber's usage and the response of the network to it will make it more appropriate to classify certain reasons as "valid" rather than "pending" or to classify them as "invalid". It can be appropriate. The present invention does not prevent such elastic operation.

As described above in detail, according to the present invention, an invalid telephone number is automatically determined without performing any actual business (some interaction with a customer) based on a telephone number list to be cleaned. It can be deleted efficiently and can be automatically replaced with a changed new phone number. In other words, by executing a business even for an invalid customer that needs to be deleted, it is possible to eliminate inconveniences such as wasteful expenses and inconvenience to non-customers.

In particular, a significant advantage of the present invention is that the validity of a telephone with a valid telephone number of the analog telephone network, which will be the largest in number, can be investigated without ringing the calling bell at all. Therefore, from the viewpoint of the person to be investigated, there is no annoyance of forcibly answering useless calls. In addition, both ISDN subscribers, which are rapidly spreading to ordinary households recently, and ordinary analog telephone network subscribers, can be processed quickly without any distinction on the list of telephone numbers to be cleaned.

Claims (5)

(57) [Claims] An apparatus for cleaning a telephone number list, comprising a computer such as a personal computer and having the following requirements (1) to (5). (1) Connected to the ISDN and executes a circuit-switched call control procedure specified in ITU-T Recommendation Q.931 as a calling terminal. (2) A telephone number is read in order from a telephone number list to be cleaned, the telephone number is set as a called number, and a "call setting" message designating non-restricted digital information as a transmission capability is transmitted to the network. (3) When the call of the transmitted "call setup" message is accepted and a "call" message or a "response" message is transferred from the network, a "disconnection" message is immediately transmitted to the network to execute a disconnection recovery sequence. At the same time, the telephone number in the “call setting” message is determined as a valid number. (4) If a "disconnect" message is transmitted from the network without accepting the transmitted "call setting" message, the disconnection recovery sequence is immediately executed, and the "disconnect" message from the network is attached. The reason indication of the information element is picked up, and it is determined whether the telephone number of the "call setting" message is treated as a valid number or an invalid number according to the contents of the reason indication. (5) Create a new list that distinguishes between telephone numbers determined as valid numbers and telephone numbers determined as invalid numbers. 2. The method according to claim 1, wherein when the content of the reason indication transferred from the network is "change of the other party's subscriber number", the new information entered in the diagnostic information field attached to the cause indication. A telephone number list cleaning device, which picks up a telephone number and creates a new list in which the telephone number in the "call setting" message is replaced with a new telephone number. 3. The telephone number according to claim 1, wherein the determination of validity / invalidity of the telephone number is suspended depending on the contents of the reason indication, and the telephone number is entered in a reserved number list. Wrist cleaning equipment. 4. A telephone number list cleaning apparatus according to claim 1, wherein said restricted digital information is designated as said transmission capability of said "call setting" message. 5. A method for cleaning a telephone number list, comprising cleaning and updating the telephone number list using the cleaning device according to claim 1.