DE69833833T2 - Credit Status Check System for Transaction Processing System and Related Test Method - Google Patents

Description

Field of invention

The The present invention relates to a transaction processing system, which comes from a computer network including connection devices like an ATM for Client loans and a bank, in particular a credit status test system for automatic checking a credit status using a phone number that is regarding a customer is registered.

technical background

It is for Financial institutions such as customer financial transactions important, a credit status to examine a customer which asks for funding, so the likelihood of to minimize uncollectible receivable. Therefore, if the Institutions have a loan agreement with a customer, this basic personal Verify customer information, including an address, a complete Name, phone number, date of birth and gender, furthermore employment situation and income of the customer. This verified personal Information becomes common when signing a loan contract registered in a customer database of the institution to request by to be referred to an employee.

These Kind of personal Information must maintained properly become. In other words, such changes in the information, like the address or phone number directly through the customer database be reflected. Otherwise, inconvenience when checking a Credit status of a customer will occur, resulting in an uncollectible Lead loan can.

Systems known in the art are systems arranged to perform credit card evaluation in an ISDN network. EP 486 204 For example, reference is made to a system that performs credit card checks on a customer credit card number using the D channel of an ISDN device.

In the field of telemarketing, methods are known for cleaning up a telephone number list in a customer list in order to delete invalid telephone numbers from the telephone number list using a personal computer and an ISDN device, see EP 777 372 ,

Various activities have been through various financial institutions including banks and customer loan financiers are taking to the customer database update properly, by finding the credit information of the customers. It is obvious that continuous review of customer credit information with sufficient time and work efficiently an uncollectible one Can prevent loans. Such a continuous tracking of Customer credit information is not sufficient in view of the costs required for the audit generally practicable.

SUMMARY THE INVENTION

It It is an object of the present invention to provide a credit information checking system to provide for the immediate and simple testing of a Credit status of a customer is able by a phone number which is recorded with a view to the customer, this is done by a computer system which performs the test procedure automatically.

• [A] Netzwerk, welches im Allgemeinen von einem telefonischen integrierten digitalen Netzwerk (Integrated Digital Network (IDN) entwickelt ist, welches Ende-zu-Ende-Digitalverbindung bereitstellt, um einen weiten Bereich von Diensten bereitzustellen, einschließlich Sprach- und Nicht-Sprachdienste, auf welche Benutzer durch einen begrenzten Satz von Standardmehrzweck-Benutzemetzwerkschnittstellen Zugriff haben.

The present invention uses advanced transmitter services provided integrally with the existing public switched telephone network ISDN. For example, ISDN, Integrated Services Digital Network, is defined as follows in accordance with ITU-T Recommendation I.110, 1988:

• [A] network, which is generally developed by an integrated digital network (IDN) providing end-to-end digital connection to provide a wide range of services, including voice and non-voice services, which users have access through a limited set of standard multi-purpose user network interfaces.

In In the present description, the term "ISDN" should be used to the fullest extent so far for a specialist ordinary Talent reasonable be understood.

According to one aspect of the present invention, there is provided a credit status checking system intended to be used in conjunction with a transaction processing system, the credit status checking system including a telephone number checking apparatus comprising means for communicating with an ISDN according to an ISDN protocol the transaction processing system includes a host computer managing customer information regarding transactions collected in a database and comprising at least one automated transaction device connectable to the host computer via a communication line, the automated transaction device having information regarding a transaction, which is entered by a customer, to the host computer, wherein the host computer processes the information received from the automated transaction device regarding a transaction in the light of the corresponding customer information in the database, wherein in response to the start of a transaction transaction by entering a customer identifier by the automated transaction device, the host computer locates a customer folder corresponding to the customer identifier in the database, receives a telephone number registered with respect to the customer, and transmits the telephone number to a telephone number checker; the telephone number checking apparatus comprising: means for processing a setup sequence via the means for communicating with an ISDN, wherein the telephone number transmitted from the host computer is defined as a number of a called party; Means for determining that the phone number of a called party is invalid by analyzing a message that is automatically transmitted by the ISDN for the setup sequence; and means for notifying the host computer of the fact that the telephone number is invalid if the means for determining has determined that the number of the called party has been determined to be invalid.

Preferably is the telephone number test equipment suitable for analyzing a cause display in an information element, which is attached to a disconnect message transmitted from the ISDN becomes; if the cause display shows "Number changed", a new one To get phone number in a diagnostic field of the Cause display is included; and the host computer's new phone number communicate and the fact that the customer phone number itself has changed.

Yet Other objects and advantages of the present invention will be Those skilled in the art will readily appreciate the following description it being understood that only the preferred embodiment of the invention is simple shown and described by way of a representation of the best way that's going to run the invention is considered. As can be noted, that is Invention for different and different embodiments suitable, and their various details are varied for modifications, obviously, all of which are not of the invention differ. Accordingly, the Drawing and description in its nature as illustrative to consider and not restrictive.

SHORT DESCRIPTION THE DRAWINGS

1 FIG. 12 is a schematic diagram of a hardware composition of a transaction processing system including a credit status checker according to an embodiment of the present invention; FIG. and

2 FIG. 10 is a flowchart illustrating a basic portion of a credit status check processing operation according to the system in FIG 1 shows.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

«Basic design and operation of the present system »

1 FIG. 12 is a schematic diagram of a transaction processing system including a credit status checking system according to an embodiment of the present invention. FIG. In this embodiment, the transaction processing system includes a computer network system including a plurality of automated transaction machines 10 as connecting devices such as automated financing machines of customer loan institutions and automated counting machines of banks. The automated transaction machines 10 They are commonly installed in department stores, supermarkets and automated finance offices. A customer who has a contract with a transaction processing system is capable of the automated transaction engine 10 self-serve to receive cash.

The automated transaction machine 10 includes a statement console 11 , a card reader 12 , a cash issue 13 , a form issuing facility 14 and a connection computer 15 , The statement console 11 is provided with a display which presents various information images to the customers, and with a keyboard to enable the operation by the customers. The card reader 12 reads a badge of a customer who has a formal contract with the system. The form issuing facility 14 Issues various forms on which contents of transactions are shown. The connection computer 15 controls the entire system of the machine 10 overall, containing the statement console 11 , the card reader 12 , the cash issue 13 and the form issuer 14 , The connection computer 15 also communicates with a host computer 20 of the transaction system to exchange necessary information between them.

The host computer 20 is on a majority of automated transaction machines 10 connected via assigned lines. A database 21 in the host computer 20 collects a number of customer information including customer credit status. Database 21 collects and maintains records of the respective transactions in a centralized manner. A majority of the service connection devices 30 is also with the host computer 20 connected via assigned lines. Various tasks are performed by office workers through the operating terminal equipment 30 processed in terms of transactions. A central section for information processing of the host computer 20 that directly manages the transactions of the credit status check system of the present invention primarily includes database management means, database management 22 and as a credit information managing means, a credit information manager 23 , The database administrator 22 gives a request to the database 21 to locate the requested data, that is, the customer folders, and maintains a comprehensive management of the database 21 by, such as saving, adding, replacing, deleting the data. The Credit Information Administrator 23 In particular, it monitors and analyzes changes in customer credit status to provide timely alerts needed by the system.

A primary component of a credit status checking system of the present invention includes a telephone number checking device 40 that have associated lines with the aforementioned host computer 20 connected is. A major part of the tester 40 typically consists of a personal computer 41 that with an ISDN communication board 42 provided that via a DSU 43 connected to an ISDN network. As is well known, ISDN forms an integral communication network with a conventional ordinary telephone network that is alternately connected to it.

«Initial operation of the Credit status check system »

If a customer uses the statement console 11 the automated transaction machine 10 operated to start a special transaction and put his / her ID card into the card reader 12 gives the card reader reads 12 the data recorded on the card, such as the customer identifier and the contents of a transaction, for which the customer has sought. The information read from the ID card becomes the host computer 20 out of the machine 10 transfer. The host computer 20 checks the credit status information and the customer's transaction information stored in the database 21 stored in accordance with the transmitted data. In accordance with the test results, the host computer performs 20 various processing operations, including consent to a transaction with the customer: under the by the host computer 20 The database manager searches for completed processing 22 a customer record file corresponding to that of the automated transaction engine 10 transmitted customer identifier to find a registered telephone number of the customer. The host computer 20 then transmits the retrieved telephone number data of the tester 40 , whereby the telephone number is checked.

The personal computer 41 which is the phone number tester 40 receives the telephone number data and an instruction to perform a sequence of a telephone number check processing operation, as in 2 is shown. First, processing of a setup sequence for the telephone number to be evaluated is started (steps 100 to 200 ). In the setup sequence, the telephone number to be evaluated is first defined as a number of a called party, and a SETUP message designating unrestricted digital information as a bearer capability is generated to be sent to a network value (step 201 ). The setup sequence 200 is processed in accordance with the circuit-switched call control procedure defined in detail in ITU-T Recommendation Q.931. A detailed description of the circuit switched call control procedure is omitted in this description, as a number of sources provide a precise explanation in this regard. A typical sequence of the procedure is processed as follows.

The Network receiving a SETUP message from a calling Connection receives, sends a CALL PROCESS message to the calling terminal a selected B channel and also sends the ON-RIGHT message a called connection. Through this processing process different abilities, which for the called connection is necessary, designated. The called connection will test the capabilities to confirm which ones the called ports the required skills Fulfills. Of the called port, which is determined to be the capabilities to fulfill, sends an ALARM message to the network. (The called connection indicates alarm.) The ALARM message becomes the calling terminal sent from the network. A CONNECTION message becomes that calling port from the called port via the Network sent when the called port on a Unhook responds. A LINK RECOGNITION message is issued by the calling one Sent to the network, and from the network to the network called in response to the CONNECTION message. According to the above Sequence will accept the SETUP message and become the two ports connected.

In some cases For some reason, a call requested by the calling line can not be accepted. The network sends a TRENN message the calling port to a deletion sequence for this To carry out cases. Of the Reason why the call was not accepted becomes the calling one Connection as a cause number in a cause of an information element which is attached to the TRENN message sent by the calling user Connection from the network is sent.

«Cause in a TRENN message»

In ITU-T Recommendation Q.931 are classes and numbers of cause indications, attached to the TRENN messages are defined as follows.

1. Normal class

[Cause # 1 - Unoccupied (unassigned) number]

These Cause indicates that the called party is not reached because, though, the number of the called party in a valid format is, this is currently not occupied (not assigned).

[Cause No. 2 - None Route to the specified transit network]

These Cause indicates that the equipment sending this cause a Request has received the call through a special transit network lead, which does not recognize it. The equipment sending this cause either does not recognize the transit network because that Transit network does not exist, or because the special transit network, while it does not exist, the equipment that serves this cause sends.

[Cause No. 3 - None Route to destination destination]

These Cause indicates that the called party is not reached can because the network through which the call was routed the wished Destination not served.

[Cause No. 6 - Channel not acceptable]

These Cause indicates that the channel selected as a result of channel selection not for the calling party is acceptable.

[Cause No. 7 - call awarded and delivered in a constructed canal]

These Cause indicates that the user has been granted the incoming call and that the incoming call was connected to a channel which already for this user for similar Calls has been set up (e.g., packet mode X.25 virtual calls).

[Cause No. 16 - Deleting one normal call]

These Cause indicates that the call was deleted because one of the users, who were involved in the call, requested that the call deleted becomes. In normal situations, the source of this cause is not the network.

[Cause No. 17 - User employed]

These Cause is used to indicate that the called party is unable to accept another call because the user busy state has occurred is. In this case, it is noticed that the user equipment with the Call is compatible.

[Cause No. 18 - No user replies]

These Cause is used when a called party is not on a Call set-up message with either an alarm or a connection indicator within the associated prescribed time period responds (expiration of timer T303 or T310, which is defined in the recommendation).

[Cause No. 19 - None Response from the user (user alerted)]

These Cause is used when the called party has been alerted but not with a connection indication within a predetermined time period responds. This cause is not necessarily due to JI-Q931 procedures but can be generated by internal network timers.

[Cause No. 20 - Participants absent]

This Cause value is used when a mobile station with a signaling Procedure has been logged by a radio bus, or a radio communication not with a mobile station (due to interference, over-range, Switch-off state, and so on) can be set up.

[Cause No. 21 - call rejected]

This cause indicates that this cause sending equipment does not wish to accept this call, although it could accept this call because the equipment sending this cause is neither busy nor incompatible.

[Cause No. 22 - Number changed]

These Cause will be returned to a calling party when passing through the called party does not show the number of the called party assigned. The new number of the called party can be optional be included in the diagnostic field.

[Cause No. 26 - Not chosen Delete user]

These Cause indicates that the user did not receive the incoming call has been.

[Cause No. 27 - destination except Business]

These Cause indicates that the destination indicated by the user can not be achieved because the interface to the destination not working properly. The phrase "not working properly" denotes that a signaling message is not delivered to the remote party could be; e.g. a physical layer or data link layer failure at the remote party, or an offline state of user equipment.

[Cause No. 28 - Invalid number format (Address unvollständigt]

These Cause indicates that the called party is not reached can because the number of the called party is not in a valid format or incomplete is.

[Cause No. 29 - Facility rejected]

These Cause is returned if a device requested by the user does not pass through the network can be provided.

[Cause No. 30 - Answer on "STATUS REQUEST"

These Cause is included in the STATUS message when the reason for Generation of the STATUS message was the previous receipt of a STATUS-ANFRA-GE message.

[Cause No. 31 - Normal, not specified]

These Cause is only used to report a normal event if there is no other cause in the normal class.

2nd Class not available resources

[Cause No. 34 - No circuit / channel available]

These Cause indicates that currently no suitable circuit / channel available is to handle the call.

[Cause No. 38 - Network except Business]

These Cause indicates that the network is not working properly and that the condition is expected to be a relatively long period of time stops; e.g. is an immediate retry of the call expected not successful.

[Cause No. 41 - Temporary Error]

These Cause indicates that the network is not working properly and that the condition is not expected to last for a longer period of time; e.g. could the user want to try another call almost immediately.

[Cause No. 42 - Equipment Overload]

These Cause indicates that the switching equipment which cause this generates a period of high traffic.

[Cause No. 43 - Access information rejected]

These Cause indicates that the network does not like access information requested, can provide to the remote user, i. User-to-user information, Low layer compatibility, High layer compatibility, or subaddress as displayed in the diagnostics. It should be noted that the special kind of discarded access information is optional included in the diagnosis.

[Cause No. 44 - Inquirer Circuit / channel is not available]

These Cause is returned if the circuit or channel indicated by the request entity is not provided by the other side of the interface can be.

[Cause # 47 - Resource not available, not specified]

These Cause is only used to report network congestion if no other cause in the network congestion class applies.

3. Service or Option Not Available class

[Cause No. 49 - QOS not available]

These Cause is used to report that the requested QOS, not as provided in Communication X.213 can not (for example, transmission or transmission delay supports become.)

[Cause No. 50 - Respondents Institution not ordered]

These Cause indicates that the help service that is requested is not provided by the network, since the user the necessary procedure to the administration has not completed.

[Cause No. 57 - Transient ability not authorised]

These Cause indicates that the user has requested a transceiver capability implemented by the equipment by which this cause but the user is not authorized to use it is

[Cause No. 58 - Transceiver Capability currently not available]

These Cause indicates that the user has requested a bearer capability, which implemented by the equipment that generates this cause, which is currently not available.

[Cause No. 63 - Service or option not available, unspecified]

These The cause only becomes the report of a service or options unavailable event used if no other reason in the service or options unavailability class true.

4. Service-unimplemented class

[Cause No. 65 - Carrier Ability Not implemented]

These Cause indicates that the equipment sending this cause the requested transmitter capacity unsupported.

[Cause No. 66 - Channel type Not implemented]

These Cause indicates that the equipment sending this cause the requested channel type is not supported.

[Cause No. 69 - Respondents Facility not implemented]

These Cause indicates that the equipment sending this cause the requested additional service is not supported.

[Cause # 70 - Limited digital only Information about bearer capability is available]

These Cause indicates that equipment provides an unrestricted transmitter service has requested that but the equipment that sends this cause, only the limited Version of requested transmitter capability supported.

[Cause No. 79 - Service or option not implemented, unspecified]

These The cause only becomes the report of a service or option unimplemented event used if no other cause in the service or option non-implementing class true.

5. Invalid message class

[Cause No. 81 - Invalid Call Reference Value]

These Cause indicates that the equipment sending this cause has received a message with a call reference which currently not in use on the user network interface.

[Cause No. 82 - Invalid Channel Number]

These Cause indicates that the equipment sending this cause has received a request to use a channel which is on the Interface not for a call is activated. For example, if a user at the channels which are numbered from 1 to 12, and the user equipment or the network is trying channels 13 to 23, this cause generates.

[Cause No. 83 - It lies a deferred call, but this caller ID is not in use]

These Cause indicates that a call resume with a caller ID was tried, which is different from the one for each currently deferred call is in use.

[Cause No. 84 - Deferred Call ID in use]

This cause indicates that the network has received a deferred call request containing a caller ID (including the invalid call identity) already in use for a deferred call within the domain of interfaces over which the call could be resumed.

[Cause No. 85 - No call postponed]

These Cause indicates that the network is making a call continuation request received, which contains a call identity information element, which currently no deferred call within the domain of interfaces denotes, over which the calls can be continued.

[Cause No. 86 - call with the requested call identity was deleted]

These Cause indicates that the network is making a call continuation request received, which contains a call identity information element which shows a delayed call that has since been deleted, while he (either through network timing or by the remote user) was postponed.

[Cause No. 87 - User is not a member of CUG] See the specification of an additional service.

[Cause No. 88 - Incompatible Determination]

These Cause indicates that the equipment sending this cause has received a request to set up a call, which has a Low-layer compatibility, high-layer compatibility or others compatibility attributes (e.g., data rate) which can not be accommodated.

[Cause No. 91 - Invalid Transit Network Selection]

These Cause indicates that a transit network identification is received which does not have a correct format, which is defined separately is.

[Cause No. 95 - Invalid message, unspecified]

These The cause only becomes the report of an invalid message event used if no other cause in the Invalid Messages class applies.

6. Protocol error (e.g. unknown communication) class

[Class No. 96 - Obligatory Information element missing]

These Cause indicates that the equipment sending this cause has received a message which lacks an information element, that must be in the communication (a compulsory information element), before the message can be processed.

[Cause No. 97 - Message type nonexistent or not implemented]

These Cause indicates that the equipment sending this cause has received a message with a message type which it does not recognizes, either because this is an undefined message or a defined but not by sending this cause Equipment is implemented.

[Cause No. 98 - Notice not compatible with call status or message type nonexistent]

These Cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is one allowed for reception during call status Message or that a STATUS message has been received, which indicates an incompatible call status.

[Cause No. 99 - Information Element not existent]

These Cause indicates that the equipment sending this cause has received a message containing information elements) that are not recognized because the information element identifier (s) are not defined or defined by this cause sending equipment are implemented. However, the information element needs not in the message, so that the equipment, which sends this cause processing message.

[Cause No. 100 - Invalid Information Element Content]

These Cause indicates that the equipment sending this cause has received an information element that does not implement it Has; however, one or more fields in the information element coded in such a way, which is not by the equipment sending this cause have been implemented.

[Cause No. 101 - Notice not compatible with call state]

These Cause indicates that a message has been received, which with is incompatible with the call state.

[Cause No. 102 - Recognize a timer expiration]

These Cause indicates that a procedure is due to the expiration of a timer in conjunction with error handling procedure of the layer 3 specification was initiated.

[Cause No. 111 - protocol error, unspecified]

These Cause used only to report a log error event if no other cause in the protocol error class applies.

7. Intermediate working class

[Cause No. 127 - Interim Work, unspecified]

These Cause indicates that there was interworking with a network, which does not cause for Provides actions that it takes. Thus, the precise cause for one Message which is sent can not be determined.

«Operating sequence of the credit status check system»

As in the flowchart in 2 are shown in a telephone number checking procedure of the credit status checking system of the present invention when the network has received a call containing a SETUP message sent by the calling party and an ALARM or CONNECT message in the setup sequence 200 has sent, the step 202 or 203 until steps 302 . 302 . 404 processed. Then, the calling party immediately sends a TRENN message to the network to perform a clear sequence, and the telephone number included in this check procedure is determined to be effective. The tester 40 reports to the credit information manager 23 of the host computer 20 in that the checked telephone number was evaluated as effective.

When a TRENN message is sent through the network because the ON RIGHT message sent by the calling party is in the setup sequence 200 was not accepted, will step 204 until steps 401 . 402 processed. The calling party immediately executes a deletion sequence and picks up a cause number of the information item attached to the TRENN message sent by the network. The telephone number in the SETUP message is determined to be either effective, void or deferred in accordance with the cause.

(a) Effective phone number

• [Ursache Nr. 3 – Keine Route zur Bestimmung]
• [Ursache Nr. 7 – Anruf zugeteilt und in errichtetem Kanal geliefert]
• [Ursache Nr. 16 – Normales Löschen des Anrufs]
• [Ursache Nr. 17 – Benutzer beschäftigt]
• [Ursache Nr. 18 – Kein Benutzer antwortet]
• [Ursache Nr. 18 – Keine Antwort vom Benutzer (Benutzer alarmiert]
• [Ursache Nr. 20 – Teilnehmer abwesend]
• [Ursache Nr. 21 – Anruf zurückgewiesen]
• [Ursache Nr. 27 – Bestimmungsziel außer Betrieb]
• [Ursache Nr. 49 – QOS nicht verfügbar]
• [Ursache Nr. 50 – Angefragte Einrichtung nicht bestellt]
• [Ursache Nr. 57 – Überträgerfähigkeit nicht autorisiert]
• [Ursache Nr. 58 – Überträgerfähigkeit derzeit nicht verfügbar]
• [Ursache Nr. 63 – Dienst oder Option nicht verfügbar, unspezifiziert]
• [Ursache Nr. 65 – Überträgerfähigkeit nicht implementiert]
• [Ursache Nr. 66 – Kanaltyp nicht implementiert]
• [Ursache Nr. 69 – Angefragte Einrichtung nicht implementiert]
• [Ursache Nr. 70 – Nur begrenzter digitaler Informationsüberträger]
• [Ursache Nr. 79 – Dienst oder Option nicht implementiert, unspezifiziert]
• [Ursache Nr. 88 – Inkompatible Bestimmung]

If the cause number in step 402 is received, one of the following corresponds, the telephone number in the SETUP message is determined to be effective. The tester 40 reports to the credit information manager 23 in that the checked telephone number was evaluated as effective. /Steps 403 to 404 ).

• [Cause No. 3 - No route to determination]
• [Cause No. 7 - Call assigned and delivered in established channel]
• [Cause No. 16 - Normal deletion of the call]
• [Cause # 17 - users busy]
• [Cause No. 18 - No user answers]
• [Cause No. 18 - No response from user (user alarmed]
• [Cause No. 20 - Attendee absent]
• [Cause No. 21 - call rejected]
• [Cause No. 27 - destination out of service]
• [Cause No. 49 - QOS not available]
• [Cause No. 50 - requested facility not ordered]
• [Cause No. 57 - Carrier Capability Unauthorized]
• [Cause No. 58 - Carrier Capability Unavailable Now]
• [Cause No. 63 - service or option not available, unspecified]
• [Cause No. 65 - Carrier Capability Not Implemented]
• [Cause No. 66 - channel type not implemented]
• [Cause No. 69 - Requested facility not implemented]
• [Cause No. 70 - Limited digital information transmitter only]
• [Cause No. 79 - service or option not implemented, unspecified]
• [Cause No. 88 - Incompatible Determination]

(b) Number changed

When in step 402 recorded cause number [Cause No. 22 - Number Changed], a new telephone number included in a diagnosis information field of the cause is notified to the credit information manager 23 found (steps 403 . 405 to 406 ).

(c) Invalid telephone number

When in step 402 If the recorded cause number corresponds to one of the following, the telephone number in the SETUP message is determined to be invalid. The tester 40 reports to the credit information manager 23 that the ge checked phone number was invalid (steps 403 . 405 . 407 to 408 ). The check procedure for determining a particular telephone number as invalid may be repeated twice with an appropriate time interval so as to confirm the invalidation status of the telephone number. If the telephone number is determined to be invalid in the two consecutive attempts, the credit information manager becomes 23 of the host computer 20 notifies that the phone number has been confirmed invalid.

[Cause # 1 - Unoccupied (unassigned) number]

[Cause No. 2 - None Route to specified transit network]

[Cause No. 6 - Channel not acceptable]

(d) determination postponed

When in step 402 recorded cause number does not correspond to any of the cause numbers contained in any of the steps 403 . 405 or 407 has been described, the telephone number in the SETUP message is determined to be neither effective nor invalid. The credit information manager 23 will be notified that the provision has been postponed. (Steps 403 . 405 . 407 to 409 )

«Actual operations»

Most of the customers of such transaction systems as described herein are subscribers of a conventional analog telephone network, although the number of subscribers of ISDN, for example an INS-Net ^(TM) in Japan, is gradually increasing today. When the telephone number checking procedure is performed in this situation, the subsequent communication is typically between the tester 40 of the present invention and an ISDN exchange station, ie the network.

(CASE A) Number of the called Party is a number of an effective participant in an analogue party Telephone network

The number in this case seems to have a large majority. The tester 40 of the present invention sends a SETUP message containing unrestricted digital information called a bearer capability, and thus the network sends a TRENN message with [causes # 3 - no route to the destination]. Therefore, the tester notifies 40 the host computer 20 that the checked telephone number is effective. Attention should be paid to the fact that the called party having a telephone number to be checked is never alerted during the checking and the determination of the number. In other words, from the point of view of the called party having the number to be checked, the called party is never disturbed by an unnecessary call by which the called party would be forced to answer.

(CASE B) Number of the called Party has changed

In this case, the network returns a TRENN message containing [Cause No. 22 - Number Changed] regardless of whether the subscriber number is from an analog telephone network or ISDN. The telephone number tester 40 who received the message notifies the host computer 20 that the checked telephone number has changed.

(CASE C) The number of called party is currently not in use

It is important to know as soon as possible that this case has happened to a specific customer telephone number to determine the credit status of the customer. In this case, the network returns a TRENN message containing [Cause No. 1 - Unassigned (unassigned) number] regardless of whether the subscriber number is from an analog network or from ISDN. The tester 40 , who has received this message, notifies the host computer that the verified phone number was invalid.

(CASE D) The number of called party is a valid Subscriber number of ISDN

In this case, a mode of communication between two parties depends on the state of the device at the called party. The called party (called party) is alerted by a CALL message issued by the computer 41 is sent. If the called party responds to the attention gathering, step 301 in the flowchart in 2 processed. The tester 23 begins a deletion sequence and determines that the number of the called party is in effect. In the event that a TRENN message is returned from the network, if the cause number in the TRENN message is one of # 7, # 16, # 17, # 18, # 19, # 20, # 21, # 27, # 49 , # 50, # 57, # 58, # 63, # 65, # 66, # 70, # 79, the number of the called party is determined to be effective. If the cause number is # 2 or # 6, the number of the called party is determined invalid. If the cause number in the in TRENN message does not correspond to any of the above cause numbers, the determination of the number of the called party is deferred.

It should be noted that the criteria of classification of the called party number into the categories "effective", "invalid" or "postponed" according to the cause number need not be limited to the manner in the preferred embodiment herein. It may be more convenient to classify some causes as "effective" or "invalid" than "deferred," depending on the situation in which the present invention is implemented, for example, based on a more precise examination of the use of ISDN the participants and a response from the network to the participants. The scope of the present invention includes such flexible operations of the telephone number checking device 23 of the present invention.

«Processing steps, the a communication of test results consequences "

If the credit information manager 23 of the host computer 20 Receives the report of an effective phone number, it is not necessary for the credit manager 23 performs a special procedure in response to the report. Alternatively, the manager 23 record that the verified telephone number has been determined to be effective at least on the day on which the check was carried out.

If the credit information manager 23 of the host computer 20 the manager receives the report that the phone number has changed 23 a message containing both the changed telephone number and the corresponding old telephone number on a selected service terminal 30 ,

If the credit information manager 23 of the host computer 20 the report receives that the verified phone number is invalid, the manager shows 23 an alarm message on a selected service connection device 30 indicating that the credit status of the particular customer becomes undetermined because the customer telephone number has been determined invalid. Further, if the customer telephone number has been determined invalid, the check result may be with or for the automated transaction machine 10 provided by the customer, depending on the nature of the transaction being processed. In this case, an indicator of the control panel 11 the machine 10 Present a message to the customer, such as "Your phone number was invalid. Please speak with our employee."

In accordance with the credit status check system The present invention has made it possible to quickly and efficiently to consider, whether or not any change in the credit status of a particular customer, based on this from his / her registered telephone number by means of an automatic Ausführmittels including of a computer system, and this every time the customer has one automatic transaction machine used. It is especially useful at The examination through the phone number tester the present invention, the test without a call from each customer. When the exam to an invalid Phone number of a special customer leads, the result can be immediate be communicated to the transaction processing system. By using the test results will it be possible the reliability improve customer credit status information, and the likelihood from lowering an irrecoverable loan. Further, the transaction processing system able to change one Find out phone number without a phone call at one To make customers, which annoying the customer could fall.

Even though the invention with respect to an exemplary embodiment The same has been described and described by experts understood that the above and many other changes, Omissions and additions in this and this can be provided without departing from the area to depart from the present invention, as in the appended claims is specified.

Claims (2)

A credit status check system intended for use in conjunction with a transaction processing system, the credit status check system having a telephone number checking device ( 40 ), means ( 42 ) for communicating with an ISDN according to an ISDN protocol, wherein the transaction processing system comprises a host computer ( 20 ) that manages customer information that is stored in a database ( 21 1), and at least one automated transaction device connectable to the host computer via a communication line, the automated transaction device transmitting the information concerning a transaction entered by a customer into that host computer, said host computer containing that information, the a transaction, which is received from the automated transaction device, is processed in the database in the light of corresponding customer information, wherein in response to the start of a transaction transaction by entering a customer identifier by the automated transaction device, the host computer querying a customer's folder corresponding to the customer identifier in the database, receiving a telephone number registered with respect to the customer and the telephone number to a telephone number checking device ( 40 ) transmits; this telephone number checking device comprising: means ( 201 ) for performing a setup sequence by said means for communicating with an ISDN, wherein the telephone number transmitted by the host computer is defined as the number of a called party; Medium ( 407 ) for determining that the number of a called party is invalid by analyzing a message which is automatically transmitted by the ISDN for the setup sequence; and funds ( 408 ) for notifying the fact that this telephone number is invalid if the determining means has determined that the telephone number of the called party has been found to be invalid. A credit status check system according to claim 1, in which the means of reviewing the Phone number is suitable, a cause display in an information element to parse attached to a disconnect message, transmitted by the ISDN was when the cause display "number changed "indicates a new one To get phone number in a diagnostic field of the Cause display is included; and this host this display new phone number and the fact that the phone number of changed customer has been.