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

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a cleaning apparatus and a cleaning method for automatically performing a process of deleting an invalid telephone number from a telephone number list included in a customer list such as so-called telemarketing using a personal computer or the like. About.

[0002]

2. Description of the Related Art In a variety of business operations using telephones, a telephone number list of a customer is extremely important information, and management that does not reduce the value of the information such as deleting unnecessary telephone numbers from the list. Must be performed at any time.
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 a telephone number list, and the list was deleted / updated while checking the response from each customer.

[0004]

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.

The present invention has been made in view of the above-mentioned conventional problems, and has as its object to efficiently and automatically execute 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 an object of the present invention to provide a cleaning device and a cleaning method which can be performed in an efficient manner.

[0006]

SUMMARY OF THE INVENTION Accordingly, the present invention provides an ISDN that is integrally interconnected with a traditional telephone network.
Utilizing the advanced bearer service provided by the company, the telephone number list cleaning process is now performed with high accuracy and speed. That is, the telephone number list cleaning device of the present invention is configured using a computer such as a personal computer, and has the following requirements (1) to (6) .

(1) Connected to the ISDN, the ITU-T Recommendation Q. The calling terminal executes the circuit switching call control procedure specified in 931.

(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 voice or audio as a transmission capability is transmitted to the network.

(3) When the call of the transmitted "call setting" 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 disconnect the network. A recovery sequence is executed, and the telephone number in the “call setup” message is determined as a valid number.

(4) If a "disconnect" message is transferred from the network without accepting the call of the transmitted "call setting" message, a disconnection recovery sequence is immediately executed, and a "disconnect" message from the network is executed. Then, 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 content of the reason display of the information element attached to the information element.

(5) A new list is created which distinguishes between telephone numbers determined as valid numbers and telephone numbers determined as invalid numbers.

(6) The cause indication transferred from the network
If the content of the
The information entered in the diagnostic information field accompanying the reason
Pick up a new phone number and
A new phone that picks up the phone number in the message
Create a new list with the numbers replaced. 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. If the inspection is performed again, the cleaning process can be performed more appropriately.

[0013]

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 as an ISDN terminal
use. 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. The personal computer 1 is connected to an ISDN via an ISDN communication board 8 and a line connection unit (DSU) 10. As is well known, the ISDN and the telephone network are interconnected integrally.

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, 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 (steps 100 → 200). In the call setting sequence, first, a "call setting" message in which "telephone number" or "3.1 KHz audio" is designated as a transmission capability with a telephone number read from the list as a destination number is transmitted to the network (step). 201). In this call setup sequence 200, ITU-T Recommendation Q. 93
It proceeds according to the circuit-switched call control procedure specified in detail in 1. 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 which 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.

Further, there are cases where the call requested by the calling terminal cannot 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 “Disconnect” Message ==== Recommendation I.Q. In 931, the type and number of the reason display attached to the "disconnection" message are defined as follows.

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

<< Reason No. 2 No route to the designated transit network >> This cause is displayed when the source device of the cause is
Indicates that a request has been received 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 request and 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 channel selection is unavailable to the transmitting terminal.

<< Reason No. 7 Incoming call to channel in which call has been set >> This reason display indicates that there is an incoming call to the user, and the incoming call is a similar call (for example, an X.25 virtual call in packet mode). Indicates that is connected to the already 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 recovery. 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 Called User Response >> This cause is displayed within the allotted time specified by the partner user for the call setup message (expiration of timer T303 or T310 defined in this specification). Used when not returning a message indicating "ringing" or "answer".

<< Reason No. 19 Calling user called / no response >> This reason display is used when a call is notified but no response is notified within a specified time thereafter. 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 is indicated by the mobile station (by a signal procedure through a radio bus).
Indicates that the mobile station has been logged off or that radio communication cannot be performed with the destination mobile station (for example, failure, out of service area, or power outage).

<< Reason No. 21 Rejection of Communication >> This reason display indicates that the device which transmitted the reason display is neither busy nor inconsistent, and can accept the call, but does not accept the call. Used.

<< Reason No. 22 Change of Subscriber Number >> This reason display 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 Unselected User >> This reason display indicates that the user could not obtain an incoming call.

<< Reason No. 27 Failure of the partner terminal >> This reason display indicates that an incoming call to the partner user requested by the calling user could not be performed because the interface on the receiving side was not functionally normal. This "functionally incorrect"
This 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 No. 28 Invalid Number Format (Incomplete Number) >> This reason display indicates that an incoming call cannot be made to the other user because the incoming number is in an invalid format or incomplete.

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

<< Reason No. 30 Response to Status Inquiry >> This reason is displayed when the reason for generating the "status inquiry" message is that the "status inquiry" message was received before generating the message. It is included in this "status display" message.

<< Reason No. 31 Other Normal Class >> This reason display is used only for reporting a normal state when the normal class cannot be expressed for other reasons.

2. Resource Unavailable Class << Reason Number 34 No Available Line / Channel >> 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 that the state 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 Discard Access Information >> This reason display indicates 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 to the other user. A special type of discarded access information may be included in the diagnostic information.

<< Reason No. 44 Requested Line / Channel Unavailable >> This reason display 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 reason indication is used to report as a network congestion event only when another reason in the network congestion class cannot be applied.

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

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

<< 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 indicates that the user has requested a transfer capability that is a transfer capability realized by the device that generated the reason display but is currently unavailable.

<< Reason No. 63 Unavailable Class of Other Service or Option >> This reason indication is used to report a service unavailable event only when other cause indications of the service unavailable class cannot be applied.

4. Service not provided class << reason number 65 unprovided transmission capability designation >> This reason indication indicates that the device which transmitted the cause indication does not support the requested transmission capability.

<< Specification of Reason Number 66 Unprovided Channel Type >> This reason display indicates that the device which transmitted the cause display does not support the requested channel type.

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

<< Reason No. 70 Restricted Digital Information Transmission Capability >> This reason is displayed when a device requests unrestricted digital information transmission capability. Indicates that only transmission capability is supported.

<< Reason number 79 Other service or optional non-provided class >> This reason display is used to report the non-provided service only when other reasons of the non-provided class are not applicable.

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

<< Reason number 82 Invalid channel number used >>
This cause indicates that the device that transmitted the cause has received a request to use a channel number that has not been 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 No. 83 No Specified Suspended Call Identification Number Unused >> This reason indication indicates that a call having a call identification number different from the call identification number used for the interrupted call was attempted to be resumed. Indicates that

<< Reason number 84 Interrupted call identification number in use >>
This cause indicates that the network has received a request to suspend the call, which is already in use as a suspended call identification in the interface area where call resumption may occur. ).

<< Reason No. 85 No Suspended Call >> This cause indicates that the network has received a call resumption request. 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 Designated interrupted call disconnection has been restored >>
This cause indicates that the network has received a resume request, which contains the call identification once signaled as a suspended call, and that the suspended call has already been cleared (due to remote user disconnection or timeout). Indicates that it is.

<< Reason No. 87 User is not a CUG member >> Refer to supplementary service specifications << Reason No. 88 Terminal attribute mismatch >> This reason indication is a low layer compatibility and a high layer consistency that the device which transmitted the reason indication cannot conform. , Or other consistency attributes (eg =
(Data rate).

<< Reason No. 91 Invalid Relay Network Selection >> This reason display indicates that the relay network weir has been received, but is in an incorrect format as defined separately.

<< Reason No. 95 Other Invalid Message Class >> This reason display is used to report an invalid message class event only when another reason of the invalid message class cannot be applied.

6. Procedure error (eg, unrecognized message) class << reason number 96 required information element shortage >>
This indicates that the information element (essential information element) that must be present in the message was insufficient when the device that transmitted the reason indication received the message.

<< Reason No. 97 Message Type Undefined or Unprovided >> This reason indication cannot be recognized such that the device that transmitted the reason indication is an undefined message or defined but not provided in the device. Indicates that a message with the message type was received.

<< Reason No. 98 Message mismatch with call state or message type undefined >> This cause is not a message that the device that has transmitted the cause indicates that the message received during the specific call state in the process is acceptable. Or a "status display" indicating an inconsistent call status has been received.

<< Reason No. 99 Information Element Not Defined >> In this reason indication, a message including an information element which is undefined even if the information element identifier of the device which transmitted the cause indication is undefined or received is received. Used in cases. 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.

<< Reason number 100 Information element content invalid >> This reason indication is an information element provided by the device which transmitted the cause indication, but is a code not provided by one or more fields of the information element. Indicates that an information element has been received.

<< Reason No. 101 Call Status and Message Mismatch >> This reason display is used when the received message does not match the call status.

<< Reason No. 102 Recovery by Timer Expiration >> This reason display indicates that the procedure has been started due to the expiration of the timer according to the error processing procedure of the layer 3 specification.

<< Reason No. 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 classes >>
This cause indicates that interworking has occurred in the network where 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, as shown in the flowchart of FIG.
In step 2, when the call of the sent "call setup" message is accepted and the "call" message or the "response" 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.

In the call setting sequence 200, when the call of the sent "call setting" message is not accepted and the "disconnect" message is transferred from the network, the process exits from step 204 to step 401 → 402. , Immediately execute the disconnection recovery sequence,
The reason indication of the information element attached to the "disconnect" message from the network is picked up, and according to the content of the cause indication,
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 No. 17 Received User Busy << Reason No. 18 No Called User Response >><< Reason No. 19 Called User Calling / No Answer >><< Reason No. 20 No Subscriber >><< Reason No. 21 Communication Rejected >><< Reason No. 27 Remote Terminal Failure << Reason No. 49 QOS Unavailable >><< Reason No. 50 Request 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 number 65 Unprovided transmission capability designation》 《Reason number 66 Unprovided channel type designation》 《Reason number 69 not provided Facility request >><< Reason number 70 Restricted digital information transmission capability >><< Reason number 79 Other service or optional unprovided class >><< Reason number 88 Terminal attribute mismatch >> Is recognized as a valid number, and the telephone number is entered in a valid list (step 403 → 404).

(B) Number change If the reason indication picked up in step 402 is "Reason number 22 Other party number change", a new telephone number written in the diagnostic information field of the reason indication is picked up. A new telephone number picked up from the telephone number in the “call setup” message is entered in the valid list (step 403 → 405 → 40).
6).

(C) Invalid number If the reason indication picked up in step 402 is one of the following: << reason number 1 missing number >><< reason number 2 no route to designated relay network >><< reason number 6 channel not available >> Identifies the telephone number in the "call setting" message as an invalid number and enters the telephone number in an invalid list (steps 403 → 405 → 407).
→ 408).

(D) Judgment suspension If the reason indication 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 a valid number. Fill in the hold list without determining it as an invalid number (steps 403 → 405 → 407 → 4
09).

As described above, when the investigation process 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 the telephone number lists to be cleaned. If not, the process returns to the first step 100 and the above processing is performed for the next telephone number. If all the processes have been completed, the process proceeds to step 502 to output a new list in a predetermined format.

==== Actual Operational Status ==== The list of telephone numbers to be cleaned according to the present invention is as follows.
A typical example 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 above-described mechanism, the following response is made between the cleaning apparatus of the present invention and the ISDN exchange (network).

(A) In the case where the called telephone number is a valid subscriber number of the analog telephone network, the number is the largest. The apparatus of the present invention uses "voice" or "3.1K" as the transmission capability in the "call setup" message.
Since the call is designated by specifying "Hz audio", the network sends a calling signal to the called terminal and at the same time returns a "call" message to the cleaning device. When the called terminal goes off-hook, the network returns a "response" message to the cleaning device. This cleaning device
When a "call" message or a "response" message is received from the network, a "disconnect" message is immediately sent 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. Therefore, a ringing tone may be heard at the called terminal for only a moment, but since the line is immediately disconnected, it is possible to minimize annoying the user of the called terminal.

(B) If the called telephone number has been changed, regardless of whether it is an analog telephone network or an ISDN subscriber number, the network sets “reason number 22: change destination subscriber number”. It returns the attached "Disconnect" message. 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 outgoing telephone number is an unused number Regardless of whether the telephone number is an analog telephone network or an ISDN subscriber number, the network is provided with << reason number 1 missing number >> A "Disconnect" message is returned. In response to this, the cleaning device enters the telephone number in the invalid list.

(D) When the Called Telephone Number is a Valid Subscriber Number of ISDN In this case, the exchange changes according to the situation of the partner equipment.
When a call is made at the receiving terminal (partner) in response to the "call" message from the cleaning device, and the partner responds to 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 "disconnection" message is returned from the network, the reason number is # 7, # 16, # 17, # 18, # 19, # 2 as described above.
0, # 21, # 27, # 49, # 50, # 57, # 5
8, # 63, # 65, # 66, # 70, # 79, enter the telephone number in the valid list. If the reason number is # 2 or # 6, enter the telephone number in the invalid list. If the reason number is other than this, fill in the hold list.

It should be noted that the classification of each of the reason numbers into "valid", "invalid" and "pending" may not be the best described in the embodiment. ISD
Investigate the usage status of the N subscribers and the response of the network to it in more detail, and it is more appropriate to classify a certain reason indication as "valid" instead of "pending" or to classify it as "invalid" May be appropriate. The present invention does not prevent such elastic operation.

[0085]

As described above in detail, according to the present invention, an invalid telephone is used without performing any actual work (some interaction with a customer) based on a telephone number list to be cleaned. The number can be deleted automatically and efficiently, and it can be automatically replaced with a changed new telephone 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, the advantage of the present invention is that the telephone with the valid telephone number of the analog telephone network, which will be the most in number, does not ring the ringing bell at all, or only rings for a moment. Since it is possible to investigate and confirm the nature, it is possible to minimize the inconvenience of forcibly answering an unnecessary call when viewed from the party to be investigated. 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.

[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 a cleaning process in the system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Personal computer 2 CPU 3 Memory 4 Hard disk device 5 Floppy disk device 6 Display device 7 Keyboard 8 ISDN communication board 10 Line connection device

Claims (3)

(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 (6) . (1) Connected to the ISDN and executes a circuit-switched call control procedure defined in ITU-T Recommendation Q.931 as a calling terminal. (2) The telephone numbers are read in order from the telephone number list to be cleaned, the telephone numbers are used as the called numbers, and a "call setting" message designating voice or audio as the 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. (6) The contents of the reason indication transferred from the network
If the message is `` Change hand subscriber number, '' the reason
New phone in the diagnostic information field
Pick up the number and before the "call setup" message
Replace the phone number with the new phone number you picked up.
Create a new list. 2. The telephone number list according to claim 1 , wherein the determination of validity / invalidity of said telephone number is suspended depending on the contents of said reason indication, and said telephone number is entered in a reserved number list. Cleaning device. 3. A method for cleaning a telephone number list, the method comprising cleaning and updating the telephone number list using the cleaning device according to claim 1 .