MXPA99008025A - Incoming call routing - Google Patents

Abstract

The purpose of the present invention is to be able to route incoming calls in an efficient manner. The problem described with how to route incoming calls in an efficient manner is solved by diverting the incoming call to a service node which further diverts the call to a specific node in dependance of the telephone number of the called party in combination with other characteristics.

Description

INCOMING CALLING TECHNICAL FIELD OF THE INVENTION The present invention relates to telecommunications in general and more particularly to voice communication on the Internet. DESCRIPTION OF THE RELATED TECHNIQUE Since the Internet is becoming increasingly popular, we tend to spend more and more time in front of our computers while we are connected to the Internet. The most common way to connect to the Internet is through the use of a modem and the connection times are much longer than the usual time required in a traditional voice conversation. In the case of users in their homes, the use of the telephone line for connection to the Internet can create conflicts since most of the subscribers have only one line that should serve both the computer communication and the voice communication . In Swedish patent application SE-9602212-4, a method is presented for allowing a subscriber to make and receive voice calls during an ongoing Internet session. In the Swedish patent application SE-9603932-6, the method presented in SE-9602212-4 is further developed and additional problems are solved. The general idea of the aforementioned requests is that a user, connected to the Internet through a modem using their usual telephone line, registers with a service that uses a special application on their computer. The service connects the user's telephone number to a special number that activates an IN service that when a call is made to the user said calls is redirected to the special number. When the IN service is activated, it activates a gateway that connects through the Internet or the IP-based network of the service provider, with the application on the user's computer and alerts the user who can answer the call. Similarly, a user can make an outbound call using the gateway to act as a bridge between the IP-based Internet and PSTN. In this situation, it seems, from a PSTN network perspective, as if the gate were making a call and should be charged. A solution to this problem is presented in document SE-9603932-ß. None of the aforementioned applications presents specific methods for routing incoming calls to the client in such a way as to optimize the use of the networks, both of the telecommunications network and of the IP-based network. COMPENDIUM OF THE INVENTION The present invention presents a method and a network to solve the problem with the routing of incoming calls to increase the use of the networks. The object of the present invention is therefore to route incoming calls efficiently. The problem described above, which refers to how to route incoming calls efficiently, is solved by diverting the incoming call to a service node that further diverts the call to a specific node that depends on the telephone number of the party receiving the call in combination with other characteristics. With more details, the problem described above is solved by diverting the telephone number of the user telephone to a service node in such a way that the incoming calls are diverted to said service node. When said service node detects an incoming call it analyzes the dialed number A, the location of the user associated with said number A and the location, or other characteristics, of the multiple nodes and diverts the incoming call according to said analysis. One of the advantages of the present invention is that the network is used efficiently. Another advantage is that the travel time of the IP packets can be minimized and consequently the disturbances in the quality of the service can be reduced. Other advantages will be apparent to a person skilled in the art taking into account the following detailed description. A further scope of application of the present invention will be apparent from the following detailed description.

However, it will be understood that the preferred embodiments of the invention are provided by way of illustration only, since various changes and modifications within the scope of the present invention will be apparent to those skilled in the art from this detailed description. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 shows the interfaces for the telephone toilet. Figure 2 shows a more detailed view of the network configuration. Figure 3 shows a network configuration for the routing of incoming calls. Figure 4 shows a network configuration of another preferred embodiment. DESCRIPTION DETAIL OF THE PREFERRED MODALITIES Figure 1 represents the telephone doubler network and its external interfaces with external networks, users and units.

A user 101 is the person who uses the telephone doubler at home. The user 101 is also the subscriber of the service. An ISDN 102 (Integrated Services Digital Network) is used as a gateway for a PSTN 103 (Public Switched Telephone Network). An SP 104 (Service Provider) is the system, organization and persons responsible for the successful operation of the telephone doubler 105. Likewise, in Figure 1, the internal structure of the telephone doubler is shown. The client 106 is the part of the telephone doubler located in the user's premises. A register 108 is a node within the gate that is common to all users of the telephone doubler service. This node is known as a record in the rest of this document. A VG 107 (Voice Gate) is the unit that processes all calls and voice transmission. A VG 107 can handle several calls simultaneously. Figure 1 also identifies external interfaces to the network and nodes. An Ul 109 (User Interface) is the interface between the user 101 and the client 106. A PRI 110 (ISDN Primary Rate Interface) is the interface used between the VG 107 and the ISDN 102. An IMO 111 (Interface of Operation and Maintenance) is the interface between SP 104 and register 108 and VG 107. A CLGI 112 (Client Gate Interface) is the interface between client 106 and register 108 respectively the client and VG 107. A REGI 113 (Registry Interface) is the interface between register 108 and VG 107. With reference to Figure 2, client 201 is using a personal computer (Not illustrated), connected to ISP 207 (Access Server) of the ISP ( Internet Service Provider) in the POP (Point of Presence) of the Internet service provider through a modem 202 and PSTN 203. The personal computer receives an IP address through the Internet service provider. This is normally done dynamically when connected to the point of presence. In the currently preferred mode, the Internet service provider and ISP 104 is the same organization or service provider. The VG 203, 204 is connected to the ISP IP network, typically the same ES 205, 206 (Internet Switched) as the point of presence. Several VGs 203, 204 may be connected to a POP. Each VG 203, 204 is connected to ISDN 208 through PRI 209, 210. A registration node 211, 212 can handle several VGs 203, 204. The registration node 211, 212 can be physically placed remotely. The VG 203, 204 and the registry 211, 212 are typically exposed connected to each other through a structural IP network 213 of the Internet service provider. The registration node 211, 212 is usually duplicated for reasons of redundancy. Several routers are indicated with an R in FIG. 2. In FIG. 3, a client 301 is connected to an IP network 302 of service providers. For its connection, it employs a modem 303 and the network 304 of PSTN. The PSTN network 304 is connected to the ISDN network 305 which in turn is connected to the IP network of service providers through a modem set 306. The service provider IP network is also connected to the Internet 307 through a router 308. A subscriber 309 makes a call to the client 301 in the PSTN network 304 but will obviously obtain a busy tone if the client 301 has not diverted its phone. The client 301 has diverted his telephone to an IN service located in an SCP 310. This could also be a separate SSP and SCP but for this mode an SSCP is sufficient. Two VGs 311 and 311 (Voice Gateways) connect the ISDN 305 network to the IP network of service providers. The SSCP is constantly updated with the load situation in different VGs and diverts the incoming call to VG 312 which at that time is the VG that has the lowest load. Through this procedure, the IP packets supplied from VG 312 to the client 301 will have a minimum delay. Figure 4 shows a modality for diverting on the basis of geographical location. In this situation, it is preferable to have the longest part of the call in the PSTN network such that SSCP 401 forwards the incoming call from subscriber 401 to VG 403 closest to the client 404. The central registration nodes can serve several distributed voice gate modules and form a wide-area distributed gate. Wide Area Distribution Issues To the extent that the gateway contains a single set of VGs placed within the POP access server, it is easy to ensure sufficient IP performance between modems and VGs (all devices are located in the same LAN environment). A single ISDN group number will also be sufficient to serve all VGs. When the telephone doubler service is increased to form a wide-area gateway, each POP has one or several VGs, served by a central registry node. This ensures that voice traffic is guaranteed with minimal latency and disruption since voice traffic is avoided through the routers. Customer data The customer has the following information: Telephone number, which consists of country code, area code (Optional in markets such as, for example, Denmark, where area codes are not used), and local number. For example: "46-08-6678054" • Authentication data which, in the present preferred embodiment, is an ONF (one-way function) applied to the concatenation of country code, area code, local number and key (optional) , persistent) • Client IP address (volatile).

• Guest Name 1 registration. Host Name 2 registration, • Primary VG IP address (volatile). • Secondary VG IP address (volatile). • Rejection of incoming calls (volatile) All this data can be obtained in the communication start announcement procedure except the telephone number and the authentication data. The combination of country code, area code and local number identifies each subscriber uniquely. The IP address attribute of VG also represents the status of the client: a zero address indicates completion, all other addresses indicate operation. Registration data Subscriber registration Both registration nodes contain an identical collection of subscriber records with the following attributes: • Phone number (Password, persistent, consisting of country code, area code and local number). • Authentication data an ONF applied to the phone number concatenated with a key (persistent) • Status. Activated or deactivated. • Client IP address (primary key, volatile) • User ID (optional) • Primary VG (volatile) • Secondary VG (volatile) • Number of communication start announcements (persistent) • Number of incoming calls (persistent) • Number of outgoing calls (persistent) • First communication start announcement (persistent) • Last communication start announcement (persistent) The client IP address attribute also represents the state of the subscriber record (one IP address zero represents completion, any other address represents operation). E.164 - IP address association When a user is connected to the Internet, the client's IP address is registered in the subscriber record on both registration nodes. Since both the telephone number and this IP address are keys, an IP address association of E. 164 is maintained between the telephone number and the IP address in the subscriber record. Registration configuration data The following data is configurable in the registry: Data that are identical in both registration nodes: • User-supplied mode, automatic or manual. • Automatic end period (optional, must be greater than the time out of PPP inactivity) • Number of key retries • Automatic removal period (optional) • Country code • Truncal prefix (optional) • Mail server SMTP (for alarm handling based on email) • Mail receiver (list of email addresses that will receive alarms) • Time synchronization guest • Host name for time synchronization guest Data that are Unique to each record name are the following: • Redundant registry node guest name (optional) • FTP account in redundant registration node • Emergency number Data that can be the same in both nodes: • Guests with access to the WWW server • Guests with FTP server access. VG registration The gate configuration is defined by means of a VG registration set. This set of records is saved by the registry, and updated in certain events such as start and shutdown of VGs. • IP address (password) • Name • Primary customer networks (only customers in these networks are served by this VG during normal operation) • Secondary client networks (customers in these networks can be served by this VG when another VG failure) • Maximum number of participating users • Primary currently participating users • Currently participating secondary users VG configuration data The VG maintains a set of configuration data that are unique to each VG: • Dialing prefix • Registration IP addresses. Optionally two, in case of redundant registration. • Monitoring interval • Number extraction method (number making the call (A), number receiving the call (B) or redirecting number) • Guests with access to the FTP server • Network charge Ad communication and completion announcement functions Purpose To be possible for a user to be connected to the point of presence ( POP) of the Internet service provider, by using your telephone line, and continue to be able to use this line and number for incoming and outgoing telephone calls. The following addresses are important in these functions: • User's phone number • Client's IP address • The ISDN number of the gate Generalities The communication and completion start announcement functions come in two types, depending on the attribute's environment in order to authenticate the registry settings. The automatic delivery mode allows the user to use the service if their IP address corresponds to any client network attribute of the VG registers. In this case, the authentication of the point of presence is trusted, and once approved, the user is trusted. In this mode you can only use a charge in IP addresses and therefore load the network. We can not trust the phone number indicated by the user. The other mode, which is a manual mode, means that the user must be registered in the system by some administrative procedure in the system, see the subscriber management function. In order to use the service in this mode, users must go through an authentication procedure also in the telephone doubler system. The authentication procedure is based on the challenge response mechanism (reference to Computer Communications Security, Warwick Ford, Prentice Hall, ISBN 0-13-799453-2). As an ONF, the MD5 algorithm (RSA Data Security, Inc., MD5 Message-Digest Algorithm) can be used. ONF (X + Y) refers to the application of the one-way function to the concatenated X + Y series. Communication start announcement in automatic delivery mode This use case can be registered only if the customer status is terminated. Before this use case, it is considered that the user has established a call transfer or (better) a busy call transfer to the ISDN number of the VG. This can be done with a telephone device or in another way (there is no programmatic support for this in the product). In another modality, the call transfer is handled automatically by the service. The client checks that the user's Internet session is in an active state. The client saves its own IP address in the customer's IP address attribute of the client, for reference for other use cases (outgoing call setup and termination). The client connects to the registry and transfers the user's phone number. The registry retrieves the client's IP address as a parameter for the outgoing TCP session. Note that the client IP address will be different between phone doubler sessions if DHCP is in use. The registry selects a VG and transfers its IP address to the client. The selection of a VG is done through the registry in the following way: (1) select the VG records for which the user's IP address corresponds to the VG primary client network attribute, (2) select the registry of VG that has the biggest difference between the maximum of participating users and the primary participating users, (3) check that the maximum limit of participating users is not exceeded by the selected VG, (4) check that the selected VG is not disabled. The attribute of the currently primary participants of the selected VG record is increased. The registry reviews the existence of a subscriber registry with the established telephone number. A review is made to determine that the client's IP address is not associated with any phone number in the registry at this point. A review is made that the subscriber registration status is enabled and finalized. The subscriber record is updated (the client's IP address, number of participants, and attributes of the last communication start announcement are updated). The PSTM-IP association is established in this way, and previous revisions ensure that it is not ambiguous in both directions. The attribute of currently participating users of the VG registry is increased. The IP address of VG ~ is set on the client. The client disconnects from the registry. If the Internet session is not active, the user is informed to start a session on the Internet and try to announce a communication start again. If the record is not accessible, the user is informed of this situation and asked to try again later. The functions of incoming and outgoing calls will not be available until the client has successfully participated. The use case is finished. If the client IP address is not acceptable in accordance with any of the client network parameters in the VG records, the use case is terminated. No information is presented to the user, since this exception may be the case of illegal use. If, due to lack of resources, no VG is available, the user is informed of that situation. The client is disconnected from the registry and the use case is terminated.

If there is no subscriber record for the telephone number provided by the customer, a new subscriber record is created. The following attributes are filled: telephone number, customer IP address, first communication start announcement. Clear defaults are filled in for the other attributes. After this, the current use case can be carried out. In another mode, a new subscriber record is not created but the use case is terminated. If, before this use case, the customer's IP address is associated with a user's telephone number in the registry, this association is obviously invalid. The forced termination use case is executed repeatedly for each telephone number of that type, until no association of the client IP address to any user telephone number remains. After this, the current use case can be carried out. If the subscriber record indicates that the user is already participating (from any client IP address), the use case of forced signage is executed. After this, the present use case can be carried out. If the subscriber's status is disabled, the user is denied access and the use case ends. Manual mode of announcement of initiation of communication The difference in this case is that the user must be defined by the service provider before announcement of communication initiation. Next, the case is described automatically. The client first requests the start of the communication start announcement procedure by signaling this to the record. In this message the phone number is transferred. The registry reviews that a subscriber record, with this telephone number as a key, exists and recovers a non-repetitive value (NRV) and associates this non-repetitive value with the subscriber. This non-repeating value is sent to the client that responds later with ONF (ONF (phone number + password) + NRV). The repetitive value can be, for example, the current time in milliseconds. ONF (phone number + password) is either brought from the client configuration or calculated as a result of a quick key dialog with the user. The user defines the mechanism used. The registry takes the authentication data (AD) in the subscriber record, then compares 0NF (AD + NRV) with the value received from the client. If these values are equal, the user is authenticated and an authentication failure counter is set to zero. If the user is non-existent, the user is informed that he must contact the service provider to be registered. When an authentication failure occurs, the authentication failure counter is incremented. If this counter exceeds a number of key retries, the user is disabled.

If the user is already participating, he is informed of this situation. In all other parts, the exceptions of the automatic step follow. Completion, automatic mode The client checks that his status is classified as a communication initiation announcement. The user is presented with a reminder to cancel their call transfer arrangement. Unfortunately, the cancellation of Call Transfer can not take place until the end of the Internet session (out of reach of the telephone bender product). A forced end use case is executed. The client disconnects from the registry. If the client's status is not a communication initiation announcement, the use case is terminated without additional action (the client's closure may occur). If the record is not accessible, the use case ends. The closing of the client can be carried out. This will cause an invalid association between the user's phone number and the client's IP address, which will last until its cancellation through a use case of communication initiation announcement., automatic termination or incoming call setup. Completion, manual mode The client checks that his state is participating. The user is presented with a reminder to cancel their call transfer setting. Unfortunately, the cancellation of the call transfer can not be carried out until the termination of the Internet association (outside the reach of the phone doubler product.) The forced termination use case is made, the client is disconnected from the registry. the client's status is not a communication initiation announcement, the use case is terminated without additional action (the customer's closing can be carried out) .If the record is not accessible, the use case ends. This can lead to an invalid association between the user's phone number and the client's IP address, which will last until its cancellation through a use case of communication initiation announcement, automatic termination or call setting. Incoming Forced Completion Other use cases that are based on this are: announcement of communication initiation, termination, establishment of incoming call, termination automatic connection The association between the user's phone number and the client's IP address is broken (subscriber registration is updated). In the VG registers, which correspond to primary and secondary VG subscriber registration, the primary and secondary users currently participating are decreased. The log record is updated. Automatic completion This use case is made periodically in the registry, without manual intervention. The purpose is to remove incorrect information from subscriber records. The periodic character is provided by the period attribute of automatic completion of the record. It should be reasonably short since it is the way how an accidentally disconnected user is protected and can announce a communication start again. However, it must be longer than the time out of PPP inactivity, in order not to interfere with this function of the Internet service ISPs. Examine each subscriber record and complete the following steps: If the status of the subscriber record is communication initiation announcement, verify that the client is currently alive by connecting to it. If the client is not alive, execute the forced end use step for this subscriber. If the customer is alive but their phone number does not correspond to the phone number attribute in the subscriber record, send a number inconsistency in the automatic completion alarm and execute the forced termination use case for the subscriber indicated by Subscriber registration If the client has not participated for a very long time (in accordance with the automatic removal period defined in the record), the subscriber's record is removed. Relationship between client UI and use cases The UI of the client is closely related to the cases of use of announcement of communication initiation and termination. When the client is initialized, it will establish a connection with the IP network of ISPs, if it is not already done previously by another application. The use case of communication start announcement will be made automatically afterwards. The client Ul will also provide a menu choice or button through which the user can request a communication initiation announcement. • This is convenient, for example, if the initial communication start announcement failed for some reason. When the client finishes, the end use case is executed automatically. Incoming call function The incoming call feature makes it possible for the user to be connected to the point of presence (POP), using their telephone line, and can still receive telephone calls on this line and number. Part A is the party making the call to the user's telephone number, which is diverted to the ISDN group number of a VG group. In another modality, the user's telephone number can be diverted to a service of IN. Addresses The following addresses are important in this function: • The user's phone number • The client's IP address • The telephone number of part A • The ISDN number of the voice gate Use cases Incoming call setup Part A dials the party's phone number B, which is transferred to the UAN (Universal Access Number). The call originates from the PRI interface. During the call establishment, the telephone number of part B is extracted from the Q.931 signaling in PRI. The type of number to extract is configured in the number extraction method. If the truncal prefix parameter is present, its value is appended before the number B. The country code parameter is then appended to the number B.

The VG connects to the registry and searches for the subscriber record of the telephone number of part B. The client's IP address is retrieved from this record. The VG is disconnected from the registry. A connection is established with the client, using the IP address from the registry. The client indicates an incoming call to the user through the Ul. The telephone number of part A is not presented.

Any of the following use cases are then possible: • Incoming call response • Incoming call rejection • Part A hangs the incoming call during ring activation • Time out of incoming call ISDN during ring activation If VG it is disabled, it is pointed out that part B is occupied in PRI and the use case ends.

If the telephone number of part B is not provided in PRI, the call can not be handled. Part B is later mentioned as congestion in PRI and ends the use case. If VG does not connect to the registry and the registry is redundant, this use case continues with the use of the other registry. If the VG does not connect with the registry, where it is indicated that part B is occupied in PRI and the use case ends. If there is no subscriber record for the number B provided, the call can not be handled. The VG is disconnected from the registry, part B is indicated as occupied in PRI, and the use case ends. If the telephone number of part B is not associated with an IP address, the VG is disconnected from the register and part B is designated as occupied in PRI. The use case is then finished. This exception will occur in the case of a user who has finished and has not canceled his call transfer. If the establishment of a connection to the client at the indicated IP address fails, part B is signaled as occupied in PRI. Then the current use case ends. If the connection to the client is successful, but if the customer's telephone number is not equal to the telephone number of part B, part B is designated as occupied in PRI. The present use case is then terminated.

If the marker to reject incoming calls is set on the client, part B is designated as occupied in PRI and the use case is terminated. If the programmatic of the client is occupied, part B is designated as occupied in PRI and the use case ends. If the client can not assign any audio device, a message is presented to the user. This message informs you that there is an incoming call, and that you have two options (1) to terminate the application that uses the audio and take the call, or (2) to reject the call. If (2) is selected, part B is marked as occupied in PRI and the use case ends. If (1) is selected, another attempt is made to establish the call. If this attempt also fails because the audio device is not free, the same message and the same options are repeatedly presented. Incoming call response This use case may occur only after the successful establishment of the incoming call. The user chooses to answer the call. The client updates its status message. Voice transmission begins. Incoming call rejection This use case occurs only after the successful establishment of an incoming call. Part B is designated as occupied in PRI. All resources that were assigned for the call are released in the client and the VG. The VG disconnects from the client. Part A hangs an incoming call during the ringer's period of operation. This use case may occur only after a successful establishment of an incoming call. This use case is provoking from PRI. All the resources that were assigned for the call are released in the client and the VG. The user is informed that part A has hung up. The VG disconnects from the client. Time out of incoming call ISDN during the ringer's period of operation This use case may occur only after the successful establishment of the incoming call. This use case is caused from PRI. It happens after a moment if part B (that is, the telephone doubler user) does not act, and part A does not hang. All the resources that were assigned for the call are released in the client and the VG. The user is informed that the call was disconnected. The VG disconnects from the client. Part B hangs up the incoming call during communication This use case may occur only after a successful response of the incoming call, that is, when a voice transmission has been established. All the resources that are assigned to the call are released in the client and the VG, and it is posted in PRI.

The VG disconnects from the client. Part A hangs an incoming call during communication This use case can only occur after the successful answering of the incoming call, that is, when the voice transmission has been established. This use case is caused from PRI. All the resources that were assigned for the call are released in the client and the VG. The user is informed that part A has hung (the VG does not wait for user confirmation of this message). The VG disconnects from the client. Outgoing call function To allow a user to make outgoing telephone calls to PSTN / ISD while connected through their telephone line to the point of presence (POP) of ISPs. The following addresses are important in this function: • The telephone number of part B • The IP address of part A To understand how these addresses are handled, please see the configuration management function. Use cases The client carries out a very limited number analysis of the number of B. Establishment of outgoing call It is required that the client's status be of announcement of initiation of communication. Part A dials the telephone number of part B. No number analysis is performed on the client. The client checks that his current IP address in accordance with what is reported by the operating system, is equal to the client IP address attribute previously saved by the client. The client reviews the existence of a free audio device on the client's platform and reserves it. A connection is established with the VG that was assigned to the client at the time of the communication initiation announcement. A revision is made in the sense that the client's IP address can be served by the VG. The dialed number is transferred to the VG. A very limited number analysis is carried out in the following way: if the truncal prefix parameter of the VG is not empty. It is checked that the main digits of the dialed number correspond with the truncal prefix. If the dialing parameter is present, its value is appended before the dialed number. An ISDN call is established with the called number.

If the network charging parameter is true, the user's telephone number is signaled with a number A provided to the user in PRI. If the current client IP address differs from the previously saved client IP address attribute, the client's status is set to finalized. The user is advised to announce again the beginning of the communication, and the use case is terminated. This situation may arise if a user announces a communication start, the PPP connection goes down, and a new PPP connection is established with a direct client IP address. If the client can not assign any audio device, the user is informed of the reason and is asked to close any application that uses the audio devices and then retry. If the connection to the VG can not be established, or if the status of the VG is deactivated, the client attempts to connect to the secondary VG. If this fails, the user is advised to close the client and reinitialize it (based on the hypothesis that the user will receive another more appropriate VG). The audio device is released and the use case ends. If the client IP address is not accepted by the VG, a rejected IP address is sent in the outgoing call alarm. The audio device is released and the use case ends. If the VG has no free capacity, the user is informed of this situation and is advised to try again later. A capacity alarm exceeded by VG is provided. The audio device and the use case ends. If the truncal prefix parameter of the VG is not empty and the leading digits of the dialed number do not correspond to the truncal prefix, a check is made to determine if the dialed number is an emergency number. If it is an emergency number, the use case continues. Otherwise, the user is informed that the number has an illegal format and the use case is terminated. If the number of calls can not be reached, the user is informed of the reason (busy, congestion, etc.).

The audio device is released and the use case ends.

Answer to exit call This use case may occur only after the success of an exit call setup use case. Part B decides to answer the call. The client updates its status message. Voice transmission begins. Outgoing call rejection This use case may occur only after the success of the outgoing call setup use case.

Part B chooses to reject the call (as can happen if part B uses a GSM phone). The VG observes a busy signal in PTI. All the resources that were assigned for the call are released in the client and the VG. The user is informed that party B rejected the call (the VG does not wait for user confirmation of this message). The VG disconnects from the client. Part A hangs the outgoing call during the ring tone. This use case may occur only after the success of the outgoing call set-up use case. The user hangs before part B has acted. All the resources that were assigned for the call are released in the client and the VG. The status message in the client is reset in the unoccupied message. The VG disconnects from the client. Outside call ISDN outgoing time during ring operation This use case may occur only after the success of the outgoing call set-up use case. This use case is caused from PRI. It happens after a moment if part B does not act, and if part A does not hang. All the resources that are assigned for the call are released in the client and the VG. The user is informed that the call was disconnected by ISDN. The VG disconnects from the client. Part A hangs out during the talk This is the way how successful calls are usually terminated. This use case may occur only after a successful response to the call of departure, that is, when a voice transmission has been established. All the resources that are assigned to the call are released in the client and the VG. The client status message is reset in the idle message. "The VG is disconnected from the client The outbound call ISDN is disconnected during the talk This use case occurs only infrequently.

This use case may occur only after the success of the outgoing call response, that is, when voice transmission has been established. Part B hangs up. After a moment, the ISDN network disconnects the call (the VG observes this in PRI). All the resources that were assigned for the call are released in the client and the VG. The user is informed that the call was disconnected by part B (the VG does not wait for confirmation by the user of this message). The VG disconnects from the client.

Subscriber management function To make it possible to manage the subscribers of the service. It is expected that the need for service will be small, and that it will consist of occasional removal of a subscriber record for which the key has been served.

Use cases Automatic subscriber removal Subscriber registration of a user who does not announce a communication start for a very long period of time is deleted from the registry. See the case of use of automatic completion in the paragraph of Handling of Faults. This will limit the table of subscribers in the registry which will consist of a reasonably active telephone doubler user. A user removed from the registry can announce a communication start again at any time. Subscriber provision A management system can add specific users through the OMI FTP interface. A human administrator can remove a specific user through the OMI HTTP interface. Changes made in a registration mode are repeated in the redundant registration node. Subscriber Removal A management system can remove a specific user through the OMI STP interface.

A human administrator can remove a specified user through the OMI HTTP interface. Changes made to a record node are repeated in the redundant registry node. Adding and Removing Subscriber to a Black List Subscription status is set to disabled / enabled. This can be done through HTTP and FTP. Change of subscriber key. This can be done through HTTP and FTP. Subscriber analysis A human administrator can retrieve subscriber records through the OMI HTTP interface. Authentication function The authentication scheme is described in the communication and completion start announcement function. To prohibit the illegitimate use of the service. Particularly, in order to reduce the risk that someone has the telephone number of the telephone number of another telephone doubler user at the time of the communication initiation announcement.

Collection function Collection is supported in several ways: Record logs are generated which can be recovered for the purpose of charging periodic rates or for statistical purposes.

The call logs are generated and can be retrieved for the purpose of collection on the basis of collection per call or for statistical purposes. In the manual delivery mode, users can be authenticated as legitimate users of their telephone numbers or user ID. Users can be charged based on their IP address if the collection system can determine the user of a certain IP address at a certain time. This should be based on logs of the access servers if DHCP is used. Incoming calls will be charged based on service rates in the UAN. In the manual service mode, the outgoing calls can be elaborated with a user-provided A number that can be used in the telephone network collection system to collect the outgoing calls. Performance management function To make it possible for SP to monitor and adjust the resource use of this service in the network. Input and output gate traffic is measured on the ISDN side, so there are well-known and understood tools and methods. The logbook can be used for statistical analysis of communication start and end announcement behavior. The call logs can be used as a complement to the ISDN tools to analyze the behavior of telephony. An alarm is sent if the capacity in an outgoing call has been exceeded. Having thus described the present invention, it will be apparent that said invention may vary in numerous ways. Such variations are not considered outside the spirit and scope of the present invention, and all of these modifications evident to the person skilled in the art are within the scope of the following claims.

Claims (1)

1. CLAIMS A method for routing incoming calls to a first subscriber to a specific node, said first subscriber uses a telecommunications network to connect to the Internet and said node is connected both to the Internet and to said telecommunications network, characterized in that a second subscriber calls said first subscriber in said telecommunications network, because said call is diverted to a service node, because said service node selects a specific node from several nodes connected to both the Internet and said telecommunications network according to the telephone number of said first subscriber and because said call is further diverted to said specific node. A method according to claim 1, further characterized in that said service node selects a specific node from a multiplicity of nodes connected both to the Internet and to said communications network according to further the geographic location of said specific node or according to further the signaling location of the specific node or according to the loading information coming from the multiplicity of nodes. A method according to claim 2, characterized in that said service node selects the node that will minimize the geographical distance between the first subscriber and said node or that will minimize the signaling distance between the first subscriber and said node or that will minimize the travel time for IP packets sent from said node to the first subscriber and back or that will minimize the load on said node. A method according to claim 1, characterized in that said service node is a Point of Service Control in an Intelligent Network. A method according to any of claims 1 to 5 characterized in that said multiplicity of nodes are voice gates. A node for routing incoming calls for a first subscriber to a specific node, said first subscriber uses a telecommunications network to connect to the Internet and said node is connected both to the Internet and to said telecommunications network, characterized in that said node comprises a means for receiving a call diverted from said first subscriber, because said node comprises a means to select a specific node within numerous nodes connected to both the Internet and said telecommunications network according to the telephone number of said first subscriber and because said node comprises a means for diverting said call to said specific node. A network for routing incoming calls for a first subscriber to a specific node, said first subscriber uses a telecommunications network to connect to the Internet and said node is connected both to the Internet and to said telecommunications network, characterized in that said network comprises a node of service, because said network comprises a means for diverting said call to said service node, because said service node comprises means for selecting a specific node within a multiplicity of nodes connected to both the Internet and said telecommunications network according to the number of said first subscriber's telephone and because said network comprises a means for diverting said call to said specific node.