CN1075306C - Method that enables users to change call performance in real time - Google Patents

Abstract

In accordance with the present invention, a telephone user of a telecommunications system can control the routing or processing of incoming calls by entering changes in real time using a conventional push-to-talk telephone. The real-time update network control point (RTUNCP) is accessed by a user and contains an input step of controlling the input of changes made by the user. After a subscriber who wants to make changes in the RTUNCP has completed an input, the TRUNCP forwards the changes to the SUBNCP that controls the handling of incoming calls to the telephone number associated with the subscriber based on subscriber data stored in the subscriber network control point (SUBNCP). According to the change, the SUBNCP data corresponding to the subscriber is modified, thereby processing the incoming call according to the changed subscriber data.

Description

Method that enables users to change call performance in real time

Background of the invention

The present invention relates generally to communication systems supporting user-definable telephony features, and more particularly to methods for certain changes in communication systems in real-time by user-controlled call routing or incoming call usage capabilities.

The existing communication network in the United States can provide effective call processing for local calls and long-distance calls. Communication switches (such as AT&T 5ESS switches) can accommodate many local call users. The user has limited control over certain optional features, such as the ability to selectively activate and deactivate the "call waiting" feature once initially placed in service to the user by the user's Local Exchange Company (LEC) . For example, a user who uses the same telephone line for voice and modem communications can disable the call waiting feature before commencing communication with a modem, so that during modem communications, when the call waiting feature attempts to alert the user to an incoming call While talking, minimize possible interference.

The PSTN uses Common Channel Inter-Office Signaling (CCIS) to allow information to be transferred within the network. The long-distance telecommunications network may include multiple gateway switches (such as AT&T 4ESS ^TM switches), which are used to connect local telephone companies and provide long-distance services to LEC users. The toll network may also include a signal transfer point (STP) coupled to the network port switch and the network control point (NCP). These STPs facilitate the transmission of information and signaling between offices. These NCPs provide distributed intelligence in the form of databases that store data and records that facilitate the interaction of network elements and store capability and function definitions associated with telephone numbers. For example, long-distance toll-free calling using the 800-XXX-XXXX number sequence known in the United States can use the data stored for a dialed 800 number to determine the actual phone number destination of the incoming call. A user may request a change in the destination telephone number associated with the user's 800 service by calling a long distance representative and telling the representative the change required. The requested change is logged in the shift log by the agent. Usually, long-term personnel who are familiar with network instructions will register the change in the duty record.

US Patent No. 4,313,035 proposes a method of using the public switched telephone network to provide nationwide personal location telephone services for called users. Each user has a unique personal location number for the user to initiate a change in the manner in which a call is handled and is connected to the user by a calling party using the personal location service capability. Only one database is used to store personal location data corresponding to all users.

US Patent No. 4,611,094 describes a method of enabling a customer to determine the telephone service offered in certain areas. Based on the called party parameters stored in the network control point, the called action point of the exchange provides the call processing of the incoming call.

EA-A-0510411 discloses a method and arrangement for handling an incoming telephone call after the call has been received at a subscriber. Subscriber specific equipment for terminating a received call is connected to a database providing additional call handling instructions. Based on the information obtained in the database, incoming calls received by the user equipment can be handled in different ways and can be tailored to the requirements of the user terminating the call.

Summary of the invention

The purpose of the present invention is to provide an improved method, so that the user can modify the incoming call route or process the incoming call in real time through the long-distance network. This is an advantage over normal long-distance networks where user-initiated changes need to be communicated to an agent for later access.

In accordance with the illustrative embodiment of the present invention, the Real Time Updating (RTU) NCP provides a single point of contact for all subscribers seeking to initiate call changes (eg, handle incoming calls to a subscriber's 800 number). The user initiates the change by dialing a predetermined 800 number associated with the RTU NCP. The RTU NCP is preferably associated with the user by a voice system (e.g. associated with a gateway exchange) to urge the user to enter user identification data and account number, telephone number and personal identification number (PIN) to be affected, and indication of change to be made. Data for call parameters. User-entered data should preferably be validated as consisting of the proper format and range of choices allowed. After completing the interaction between the subscriber and the RTU NCP, the latter transmits the change data to an NCP which maintains a call control record of the telephone number associated with the change, the Subscriber NCP (SUB NCP). After the modified data has been entered into the subscriber's control record at the SUB NCP, all subsequent calls to the subscriber's telephone number to which the change applies will be processed in accordance with the change entered by the subscriber. Therefore, the user can make changes in real time and control the handling of calls received by the user.

Brief description of the drawings

FIG. 1 depicts a block diagram of a communication network supporting the steps of the method according to the invention.

A detailed description

The communication network described in FIG. 1 includes local telephone companies 10 and 12, and LECs 10 and 12 are connected to a network port switch 18 forming a long-distance part of the network through communication channels 14 and 16 respectively. The local telephone company 10 supports a plurality of telephone subscribers associated with telephones 20A-20N (for ease of description, the telephones 20A-20N are referred to as primary subscribers). Central office 22 supports these users and may include a communications switch such as an AT&T 5ESS switch. Similarly, local telephone company 12 supports its subscribers via telephones 24A-24N (also referred to as primary subscribers) and central office 26 .

Another local telephone company 28 supports subscribers associated with telephones 30A-30N and includes a central office 32 . The LEC 28 is connected to the network port switch 34 through the communication channel 36 . Network port switches 18 and 34 (such as AT&T 4ESS switches) are coupled by communication channel 38. These switches are also coupled to the rest of the communication network via communication channels 40 and 42 . Voice systems 44 and 46 are coupled to Ethernet switches 18 and 34, respectively. The speech system includes speech recognition capabilities and speech synthesis capabilities to enable delivery of predetermined voice messages to a user and to provide speech recognition of user-generated voice messages.

In the depicted embodiment, Ethernet switches 18 and 34 are connected to a signal transfer point (STP) 48 by communication channels 50 and 52, respectively. The STP may include an AT&T No. 2 Signal Transfer Point (2STP), which acts like a stored program control system. STP functions like a relay point in a Common Channel Inter-Office Signaling (CCIS) network that carries control information and signaling between network elements. This STP 48 is connected to another STP 54 via a communication channel 56 . STPs 48 and 54 are also coupled to the rest of the communication network via communication channels 58 and 60, respectively.

A network control point (NCP) group 62 includes two substantially identical NCPs 64 and 66. An NCP is a database facility such as the AT&T 2 Direct Services Dial Network Control Point (2DSD NCP). Usually, NCPs are configured in pairs in the network and consist of primary and secondary units that store the same data records. The function of the primary NCP is a redundant There is minimal chance of data loss and invalidation. NCPs 64 (also sometimes referred to as first database) and 66 (also sometimes referred to as first pairing database) are connected to STP 48 via communication channels 68 and 70, respectively. Communication channel 72 connects NCPs 64 and 66 so that data can be transferred directly between them. In the described embodiment, the group of NCPs 62 is referred to as a real-time update (RTU) NCP, which will be described in more detail below.

Each of the plurality of NCP groups 74A-74N includes a respective NCP 76A-76N (also sometimes called a second database) and 78A-78N (sometimes also called a second pair database). Each of NCPs 76 and 78 is coupled to a unique transfer point in the network via communication channels 80A-80N and 82A-82N. In this embodiment, these NCP groups are called Subscriber (SUB) NCPs. Each user that needs to be supported by the long-distance system database is supported by a corresponding account record stored in a SUB NCP. For example, a user who activates the 800 long-distance toll-free number service has the same account record stored in the first-level and second-level matching (mate) SUB NCPs, where the first-level and second-level matching SUB NCPs are used to control calls to the user The actual destination address (phone number) of . Each of the primary and secondary paired SUB NCPs are interconnected via respective communication channels 84A-84N.

Embodiments of the present invention are particularly (but not exclusively) applicable to enable users of a certain service (such as 800 long-distance toll-free service) to change the processing performance of incoming calls in real time using ordinary push-button phones. For example, a business user of an 800 service can usually route incoming calls to a primary call answering center. A user may have a secondary call answering center that is only used during peak load periods. Embodiments of the invention enable authorized users of 800 business subscribers to make changes in real time so that incoming calls to 800 are routed if an unexpected event, such as fire or weather, renders the primary call processing center unable to process incoming calls To a secondary call center that is properly staffed to handle the normal capacity booked at the primary call center.

Obviously, the user can change the additional call processing performance in real time. For example, an incoming call may receive different treatment based on the date and/or time of the call, the caller's phone number, and combinations of these factors. The data indicating these criteria and stored in the SUBNCP can be changed in real time by the user, causing corresponding changes to be made in the processing of incoming calls.

The flow chart shown in Table I provides all steps related to real-time modification according to the embodiment of the present invention. These steps describe real-time changes to 800 telephone service inputs by a user. The steps shown in Table I should be considered in conjunction with Figure 1 to obtain an intuitive link between network components and these steps.

Table I

(1) User 20A wishes to enter a real-time change in the destination of an inbound call to his 800-aaa-bbbb number (SN) from the first call processing center to the second call processing center, i.e. from the first phone number to the second phone number .

(2) Subscriber 20A dials a predetermined 800 number (PN) established by the long distance provider to receive this real-time change.

(3) The user's local central office C022 determines the route of the PN call to the relevant network outlet switch 18 .

(4) The network egress switch 18 uses global name forwarding (GTT) to determine the address of the target NCP (that is, NCP64). The network switch 18 sends a change start message to the NCP 64 through the STP 48 name, and the NCP 64 is a part of the RTUNCP group 62 . STP48 forming part of the RTUNCP group 62 to

(5) NCP 64 contains a RTU entry program relevant to PN. The entry program is a structured prompting and input process that controls prompting to the user, receiving responses from the user, and acknowledging the responses.

(6) In response to the change initiation information, NCP64 controls the voice system 44 to send voice reminders to the user, and receives responses made by the user such as user account number, personal identification number (PIN), SN related to the change, etc., and communicates with the user Other data related to specific changes such as a new phone number that will be the target of future inbound calls to that SN. The program validates the information entered by the user and the changes requested.

(7) After confirming and accepting the requested change, NCP64 stores the update file containing the requested change and relevant user information, and generates a corresponding backup file, which is stored in the RTUNCP pair.

(8) Subsequently, the NCP64 sends a first update message to the network port switch 18 through the STP48. The first update message contains an update file.

(9) After receiving the first update message, the network outlet switch 18 uses GTT to determine the address of the SUB NCP relevant to the applicable SN of these changes, and by STP 48 and 54, send the second update file that also includes the update file to NCP76A. Update news.

(10) SUB NCP 76A, updates the control record corresponding to the SN with the information in the second update message to reflect these changes.

(11) After these changes have been entered in the control record in SUB NCP 76A, SUBNCP 76A causes the corresponding backup subscriber record in SUB NCP pair 78A to be updated.

(12) Subsequently, the SUB NCP 76A makes an update complete message sent to the user, confirming the changes input by STP 54 and 48, network port switch 18, voice system 44 and C022. This completes the live change process.

(13) After completing the above steps, the call sent to SN will be processed according to the update control record stored in NCP 76A.

The above-described embodiments of the present invention may be compared to the normal process for entering changes to 800 call services. In a conventional network, a user who wants to change the destination of a call to an 800 telephone number needs to call a network representative and verbally describe the desired change. After the network representative confirms the user's identity, the requested change will be recorded. Usually, another person who understands the NCP protocol and is connected to the long-distance network through a computer will receive the record containing the requested change and send the appropriate command to cause the user's control record in the SUB NCP to be updated. In this example, two people employed by the network are used to implement the input of the change. Obviously, the potential for error increases with the number of people and steps involved in the process. At the same time, the time to implement the required changes will take a certain amount of time. The present invention minimizes the possibility of error and provides a real-time implementation of user updates.

The following is the detailed call process according to the described embodiment of the present invention. Assume that user 20A wants to enter a real-time change of the destination of an inbound call to the user's 800 number (SN). The user dials a subscription 800 number (PN) established to receive these real-time changes. The subscriber's central office 22 determines the route of the PN call to the relevant egress switch 18, which is called the originating office ingress switch (OAS). The OAS then completes the ten-digit global name translation of the PN number, identifying the CCIS component address to use, which in this case is NCP64. The (BEGIN) message may be conveyed with a Signaling System No. 7 Transaction Capability Application Part (SS7 TCAP) message.

After NCP64 receives the BEGIN message, it will enter the RTU entry program stored in the NCP 64 to control the real-time user update process. NCP 64 transmits a message to voice system 44 through STP 48 and network outlet switch 18, notifying the user to request input of user account. Because the user's originating telephone number and the address of the Ethernet switch 18 are provided as part of the BEGIN message sent to the NCP 64, the NCP 64 is able to address or route the message. After entering the user's account number, the network port switch 18 transmits the message to the NCP 64. Subsequently, NCP 64 sends another message sent by STP 48 and Ethernet port switch 16 to voice system 44, notifying the user to input his PIN. The PIN input by the user is transmitted to the NCP 64 by the network port switch 18 . The NCP 64 then transmits another message to the voice system 44 notifying the user to enter the 800 number to be updated. After inputting the 800 numbers to be updated, these numbers are collected by the central office 22 and transmitted to the NCP 64 through the network switch 18. The NCP then sends a message to voice system 44 informing the user to enter the required telephone number that will route the 800 number call. After the user has entered a new telephone number, the central office 22 transmits the message to the NCP 64 through the network port switch 18. So, NCP64 has now obtained complete information about an update request directly from this user.

The NCP 64 preferably contains or has access to a database corresponding to the entered account number to verify the validity of the change of the entered PIN verification request by corresponding to the PIN number stored in the database. The database is also checked to verify that the 800 number to be modified corresponds to the 800 number associated with the account number in the database. Preferably another database stored in or accessible by the NCP is referenced to confirm the destination number requested by the user. For example, the rate will not allow a destination phone number change from an intrastate number to an interstate number. Clearly, such a database could include other rule constraints or validity features to validate requested changes. If the requested change is not permitted, the NCP will notify the user by having the voice system 44 indicate that the requested target number is not permitted and ask the user to select another target number or call a network representative to provide assistance with the change Terminate the process.

After collecting user messages and confirming the requested changes, the NCP 64 will send an SS7 TCAP BEGIN message from the OAS with the node address contained in the original BEGIN message. The user's 800 number will be located in the dialed number area of the TCAP message, and the message will contain the new call destination number as a parameter. After receiving the BEGIN message from NCP64, the OAS will forward the ten-digit GTT to the user's 800 number to form the node address (NCP76A) of the NCP containing the user's customer account record, and send a BEGIN message to the identified NCP . After the NCP 76A receives the BEGIN message from the OAS, the NCP 76A extracts the necessary information required for record updating from the BEGIN message, and stores it in an update register. The NCP 76A uses the user's 800 number to access the user's customer record stored in the NCP 76A. The new target number entered by the user is placed in the user's customer record, preferably in a separate RTU area, rather than simply replacing the existing stored target number stored in a separate area of the customer account record. On a later date, after a period of time sufficient to confirm that the new target number entered by the user is appropriate from the validation and user point of view, a maintenance procedure may be used if the target number field is replaced by the RTU field from the same customer record. Assuming a certain number exists in a certain zone, an incoming 800 call is routed to the phone number stored in the RTU zone. Otherwise, the incoming call will be routed to the normal destination number field stored in the customer's account record.

Subsequently, NCP 76A sends an update message to partner NCP 78A, which takes similar steps, that is, modifies the reserved customer record in the same manner as NCP 76A. Subsequently, NCP 76A sends a TCAP END message indicating success or failure back to NCP 64. After NCP64 receives END message from NCP 76A, depending on the success of the change of request, the program that RTU enters in NCP64 will determine the notification that will be made to the user by voice system 44. Since the customer call has now ended, the customer call can be disconnected and, if successful, an update has been entered at this point, and subsequent calls can be made to the customer's 800 number.

Embodiments of the invention present the advantages of the invention. Enter an update number when the user enters a live change. Intercommunication with the user allows the user to enter changes with normal touch-tone telephone time. The input change is effective in real time, so that the flexibility of the user is increased, the change can be made effectively, and the change condition can be determined. Although the described embodiment shows changes to the target number, it will be apparent to those skilled in the art that various changes to the call handling and handling parameters that can be controlled by the user account record can be made by the user in a similar manner. kind of change.

While embodiments of the invention have been described above, the scope of the invention is defined by the claims that follow.

Claims (7)

1. method that makes the telephone service user can change the call treatment performance of communication network in real time is characterized in that described method comprises following step:

For first user who seeks the change of call treatment performance, in described communication network, select route, and described calling is made to described first user from described first user to the calling of first database;

Confirm that described first user has the right that the described call treatment performance to the calling of pointing to described first user changes;

After successfully having confirmed described first user's described right, accept and store the data of described first user input, described data are specified will make change to a call treatment performance, and described data are stored in described first database;

Whether judge the described data of storing in described first database corresponding to effective change of call treatment performance is carried out in described first user's calling, described judgement is carried out according to previously stored information in described first database;

The described data of storing in determining described first database are corresponding to after carrying out effective change of call treatment performance to described first user's calling, automatically described first database of described data from described communication network sent to second database in the described communication network, described second database contains the call processing record that a control is handled described first user's calling;

According to described data, revise the described call processing record in described second database, change by the described call treatment performance that described first user seeks with real-time enforcement.

2. the method for claim 1 is characterized in that, described affirmation also comprises:

Point out described first user to import a password, and

By described password and the password of before distributing to described first user are compared the password that confirms first user input.

3. method as claimed in claim 2 is characterized in that, described prompting comprises:

From described first database to a voice system send one with the described first user-dependent prompting message, and

One voice prompt request is provided to described first user from described voice system.

4. the method for claim 1 is characterized in that, the described calling of described first database from described first user to described communication network is a calling that telephone number carries out to arbitrary first user.

5. the method for claim 1 is characterized in that, it also comprises:

Described data are sent to the first paired data storehouse from described first database, the losing of the described data that occur when preventing that in first database and the first paired data storehouse one from breaking down.

6. the method for claim 1 is characterized in that, described forwarding step comprises:

Described data are sent to a converting means from described first database, to determine second database corresponding with described first user's telephone number.

7. the method for claim 1, it is characterized in that it also comprises such step, promptly, described data are sent to the second paired data storehouse from described second database, in order to prevent a loss of data that occurs when breaking down in second database and the second paired data storehouse.

Images