Source: http://www.google.com/patents/US4873717?dq=FRAIOLI
Timestamp: 2014-03-14 22:53:55
Document Index: 366958062

Matched Legal Cases: ['art. 8', 'art. 9', 'art. 10', 'art. 11', 'art. 12', 'art. 19']

Patent US4873717 - Call coverage arrangement - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA call coverage arrangement in which coverage personnel are informed of the switch-hook status of covered terminals by way of a single two-part indicator on the coverage terminal. The two-part indicator indicates switch-hook status for any one of a number of covered terminals. The first part of the indicator...http://www.google.com/patents/US4873717?utm_source=gb-gplus-sharePatent US4873717 - Call coverage arrangementAdvanced Patent SearchPublication numberUS4873717 APublication typeGrantApplication numberUS 07/206,467Publication dateOct 10, 1989Filing dateJun 14, 1988Priority dateJun 14, 1988Fee statusPaidAlso published asCA1335458CPublication number07206467, 206467, US 4873717 A, US 4873717A, US-A-4873717, US4873717 A, US4873717AInventorsWayne A. Davidson, John P. Ernst, Marybeth Herkes, Ram Kuppuswami, Timothy A. Satalich, John J. Stanaway, Jr.Original AssigneeAmerican Telephone And Telegraph Company, At&T Bell LaboratoriesExport CitationBiBTeX, EndNote, RefManPatent Citations (8), Non-Patent Citations (4), Referenced by (19), Classifications (11), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetCall coverage arrangementUS 4873717 AAbstract A call coverage arrangement in which coverage personnel are informed of the switch-hook status of covered terminals by way of a single two-part indicator on the coverage terminal. The two-part indicator indicates switch-hook status for any one of a number of covered terminals. The first part of the indicator identifies the covered terminal and the second part defines the switch-hook status of the identified terminal. The arrangement is flexible in providing coverage for additional terminals and in providing coverage via forwarding from any termianl, since there is no need to assign and dedicate status indicators to particular terminals.
We claim: 1. In an arrangement comprising a switching system interconnecting a plurality of terminals, a method for providing call coverage for calls to a directory number shared by a first one of said terminals and a second one of said terminals, said first terminal including a two-part indicator comprising a first part for identifying any one of said terminals and a second part for defining switch-hook status of at most one of said terminals said first terminal also including a first plurality of call appearances with at least one of said first plurality of call appearances assigned said directory number, said second terminal including a second plurality of call appearances, said method comprisingin response to an incoming call for said directory number, determining switch-hook status of said second terminal, transmitting said determined switch-hook status to said first terminal, in response to receipt of said determined switch-hook status, said first terminal using said two-part indicator to provide an indication for use in answering said call at said first terminal such that said first part identifies said second terminal and said second part defines said determined switch-hook status of said second terminal as identified by said first part, and while performing said step of using said two-part indicator, alerting at said at least one cell appearance at said first terminal in response to said call for said directory number. 2. A method in accordance with claim 1 wherein said first terminal further includes an alpha-numeric display to display call information, said display comprises said first part of said two-part indicator, and each of said first plurality of call appearances at said first terminal is assigned a unique identifier, wherein said step of using said two-part indicator comprisesdisplaying the unique identifier for said at least one call appearance at said first terminal in said display for use in identifying said call as being intended for said second terminal and using said second part to define said determined switch-hook status of said second terminal. 3. A method in accordance with claim 2 further comprisingsaid switching system obtaining an originating directory number for said incoming call, transmitting said originating directory number to said first terminal, and while performing said step of using said two-part indicator, displaying said originating directory number in said display. 4. A method in accordance with claim 3, wherein said switching system stores name data associating a name with each of a plurality of directory numbers including said originating directory number, said method further comprisingreading said name data to determine the name associated with said originating directory number, transmitting said determined name to said first terminal, and while performing said step of using said two-part indicator, displaying said determined name in said display. 5. A method in accordance with claim 4, wherein said display also comprises said second part of said two-part indicator, wherein said step of using said second part further comprisesindicating in said display said determined switch-hook status such that one of off-hook and on-hook is indicated by the presence of a character string in said display and the other of off-hook and on-hook is indicated by the absence of said character string in said display. 6. A method in accordance with claim 4, wherein said display also comprises said second part of said two-part indicator, wherein said step of using said second part further comprisesindicating in said display said determined switch-hook status such that an off-hook condition is indicated by displaying one string of characters in said display and an on-hook condition is indicated by displaying another string of characters in said display. 7. A method in accordance with claim 1 further comprisingsaid first terminal transmitting answer signaling for said call, after transmitting said answer signaling, said first terminal receiving a message containing updated switch-hook status for said second terminal, and in response to receipt of said message containing said updated switch-hook status, said first terminal using said two-part indicator to indicate said updated status such that said first part identifies said second terminal and said second part defines said updated switch-hook status of said second terminal as identified by said first part. 8. A method in accordance with claim 7, said method further comprisingsaid first terminal transmitting answer signaling for said cell, after transmitting said answer signaling, said first terminal transmitting a request to said switching system for information about said call, in response to said request, said switching system determining updated switch-hook status for said second terminal, after determining said updated switch-hook status, said switching system transmitting said updated switch-hook status to said first terminal, in response to receipt of said updated switch-hook status, said first terminal using said two-part indicator to indicate said updated status such that said first part identifies said second terminal and said second part defines said updated switch-hook status of said second terminal as identified by said first part. 9. A method in accordance with claim 1 further comprisingsaid first terminal discontinuing use of said two-part indicator in providing said indication for use in answering said call at said first terminal, after said discontinuing step, determining updated switch-hook status of said secon terminal and transmitting said updated switch-hook status to said first terminal, in response to receipt of said updated switch-hook status, said first terminal using said two-part indicator to indicate said updated status such that said first part identifies said second terminal and said second part defines said updated switch-hook status of said second terminal as identified by said first part. 10. A method in accordance with claim 1 further comprisingin response to receipt of a new call at said first terminal, said first terminal discontinuing use of said two-part indicator in providing said indication for use in answering said incoming call at said first terminal and using said two-part indicator to provide an indication for use in answering said new call at said first terminal, in response to a request from said first terminal to return to said incoming call, determining updated switch-hook status of said second terminal and transmitting said updated switch-hook status to said first terminal, in response to receipt of said updated switch-hook status, said first terminal using said two-part indicator to indicate said updated status such that said first part identifies said second terminal and said second part identifies said updated switch-hook status of said second terminal identified by said first part. 11. A method in accordance with claim 1 further comprisingsaid first terminal transmitting answer signaling for said call, after transmitting said answer signaling, said first terminal transmitting hold signaling to place said call on hold, after transmitting said hold signaling, said first terminal discontinuing use of said two-part indicator in providing said indication for use in answering said call at said first terminal, in response to a request from said first terminal requesting retrieval of said call from hold, determining updated switch-hook status of said second terminal and transmitting said updated switch-hook status to said first terminal, in response to receipt of said updated switch-hook status, said first terminal using said two-part indicator to indicate said updated status such that said first part identifies said second terminal and said second part defines said updated switch-hook status of said second terminal as identified by said first part. 12. A method in accordance with claim 1, wherein said switching system stores call appearance data for said second terminal defining call status at said second plurality of call appearances, wherein said step of determining said second terminal switch-hook status comprisesreading said call appearance data for said second terminal, determining said second terminal switch-hook status as on-hook when said read call appearance data defines none of said second plurality of call appearances as having a call status corresponding to an off-hook condition, and determining said second terminal switch-hook status as off-hook when said read call appearance data defines at least one of said second plurality of call appearances as having a call status corresponding to an off-hook condition. 13. A method in accordance with claim 1, wherein said switching system stores switch-hook data defining the switch-hook status of said second terminal, wherein said step of determining switch-hook status of said second terminal comprisesreading said switch-hook data, determining said second terminal switch-hook status as off-hook when said read switch-hook data defines said switch-hook status as off-hook, and determining said second terminal switch-hook status as on-hook when said read switch-hook data defines said switch-hook status as on-hook. 14. A method in accordance with claim 1 wherein said first terminal further includes an alpha-numeric display to display call information, wherein said display comprises said first part of said two-part indicator, said method further comprisingtransmitting to said first terminal said directory number, and wherein said step of using said two-part indicator comprises displaying said directory number in said display to identify said call as being intended for said second terminal and using said second part to define said determined switch-hook status of said second terminal. 15. A method in accordance with claim 1 wherein said first terminal further includes an alpha-numeric display to display call information, said method further comprisingsaid switching system obtaining an originating directory number for said incoming call, transmitting said originating directory number to said first terminal, and while performing said step of using said two-part indicator, displaying said originating directory number in said display. 16. A method in accordance with claim 1 wherein said first terminal further includes an alpha-numeric display to display call information, said display comprises said first part of said two-part indicator, and said switching system stores name data associating a name with each of a plurality of directory numbers including said directory number of said second terminal, said method further comprisingin response to said incoming call, reading said name data to determine the name associated with said directory number of said second terminal, transmitting said determined name to said first terminal, and wherein said step of using said two-part indicator comprises, in response to receipt of said determined name, displaying said determined name in said display to identify said call as intended for said second terminal and using said second part to define said determined switch-hook status of said second terminal. 17. A method in accordance with claim 1 wherein said first terminal further includes an alpha-numeric display to display call information, and said switching system stores name data associating a name with each of a plurlity of directory numbers, said method further comprisingobtaining an originating directory number for said incoming call, wherein said originating directory number is one of said plurality of directory numbers, in response to said incoming call, reading said name data to determine the name associated with said originating directory number, transmitting said determined name to said first terminal, and while performing said step of using said two-part indicator, displaying said determined name in said display. 18. A method in accordance with claim 1 wherein said first terminal includes another plurality of call appearances and shares said directory number with said second terminal, said first terminal further includes an alpha-numeric display to display call information, said display comprises said second part of said two-part indicator, and said step of using said two-part indicator comprisesusing said first part to identify said second terminal, and indicating in said display said determined switch-hook status of said second terminal as identified by said first part. 19. A method in accordance with claim 18, wherein said step of indicating said determined switch-hook status further comprisesindicating an off-hook condition by displaying one string of characters in said display, and indicating an on-hook condition by displaying another string of characters in said display. 20. A method in accordance with claim 18 wherein said step of indicating said determined switch-hook status further comprisesindicating one of off-hook and on-hook by the presence of a character string in said display, and indicating the other of off-hook and on-hook by the absence of said character string in said display. 21. A method in accordance with claim 20 wherein said character string is an asterisk.
TECHNICAL FIELD This invention relates to telecommunication call processing, and more particularly, to call coverage arrangements in integrated services digital network (ISDN) systems.
BACKGROUND AND PROBLEM Telecommunication arrangements for businesses encourage productivity by enabling terminals to originate and terminate calls simultaneously. For example, calls may be offered to a terminal when the user of the terminal is dialing a directory number or is active on another call. This eliminates the need for call waiting service and provides the user flexibility in choosing the call to handle next. In such an arrangement, each terminal has visual indicators, referred to as call appearances, for informing the user about the status of each call. Several, or even all, of the call appearances on a terminal may represent the same directory number. Furthermore, terminals may share call appearances. Calls alerting at a call appearance may be answered at any of the terminals that share the call appearance. However, the directory number for the call appearance is primary for at most one terminal. The concept of primary directory number associates a directory number with a terminal and the individual who uses that terminal.
SOLUTION These deficiences are eliminated and a technical advance is achieved consistent with the principles of the invention in a call coverage arrangement in which coverage personnel are advantageously informed of the switch-hook status of covered terminals by way of a single two-part indicator on the coverage terminal. The two-part indicator indicates switch-hook status for significantly any one of a number of covered terminals. The first part of the indicator identifies the covered terminal and the second part defines the switch-hook status of the identified terminal. The arrangement is flexible is providing coverage for additional terminals and in providing coverage via forwarding from any terminal, since there is no need to assign and dedicate status indicators to particular terminals. Illustratively, call handling is further enhanced by providing additional call information at the coverage terminal such as the calling and called party names.
DETAILED DESCRIPTION The principles of the invention are described in the context of a distributed control, integrated services digital network (ISDN) switching system 100 (FIG. 1). An integrated services digital network is defined as a network evolved from the telephony integrated digital network that provides end-to-end digital connectivity to support a wide range of services, including voice and non-voice services, to which users have access by a limited set of standard multipurpose customer interfaces. System 100 is connectable to analog or digital terminals, however, only digital ISDN terminals 181 through 184 and 191 through 193 are shown in FIG. 1. (Although not shown in FIG. 1, system 100 is also connectable via trunks to terminals associated with other switching systems.) System 100 includes a number of switching modules (SMs) each associated with a different subset of terminals. For example, switching module 110 is associated with terminals 181 and 191, switching module 120 is associated with terminals 182, 183, 192, and 193, and switching module 130 is associated with terminal 184. Each switching module includes a control unit or switching module processor (SMP) for controlling connections to and from its associated subset of terminals. Switching module 110, for example, includes control unit 111. Similarly, switching modules 120 and 130 include control units 121 and 131, respectively.
A flow chart for a call processing program used to determine the switch-hook status is shown in FIG. 4. The process executing this call processing program is associated with a process control block for a call that is related to the terminal for which status has been requested. Execution begins with block 501 in which the location of the terminal equipment data block corresponding to the terminal is determined. The process executing the program locates the terminal equipment data block by following the link from the process control block to a D-Channel application linkage block containing information for the call. The owner field of the D-Channel application linkage block defines the terminal equipment data block for the terminal. Execution proceeds to block 502 where the terminal type of the terminal is determined. The terminal type of a terminal is defined by a cpe.sub.-- type field in the terminal equipment data block. The terminal type is either terminal management (TMF) or non-terminal management (nonTMF). For a terminal management terminal, system 100 manages the status of the buttons on the terminal and determines the selected call appearance for the terminal. Non-terminal management terminals perform these functions for themselves. The message signaling between terminal management terminals and a switching system is described in U.S. Pat. No. 4,741,026 issued to L. A. Baxter, et al. To perform the additional functions required for a terminal management terminal, system 100 maintains additional data about the status of the terminal. Thus, the data available to determine whether a given terminal is off-hook differs depending on whether the terminal is a terminal management terminal.
If the cpe.sub.-- type field in the terminal equipment data block indicates that the terminal is a terminal management terminal, execution proceeds with block 503. The switch-hook status of the terminal is determined by reading the switch.sub.-- hook attribute in the terminal equipment data block. The switch.sub.-- hook attribute indicates whether the terminal is on-hook or off-hook and execution ends at block 504 or block 505. Processing is completed at this point for terminal management terminals.
If the check of the cpe.sub.-- type field made in block 502 indicates that the terminal is a non-terminal management terminal, execution proceeds with block 506. Each of the D-Channel application blocks are checked until all the blocks have been checked or a block corresponding to a call for which the terminal is considered off-hook is found. The search through the D-Channel application blocks begins with the block directly linked to the terminal equipment data block and continues through the list of blocks. If block 506 is executed and all the D-Channel application blocks in the list have been checked, execution proceeds to block 507 and the terminal is determined to be on-hook. Otherwise, whenever block 506 is executed and there are still D-Channel application linkage blocks remaining to be searched, execution begins with block 509 where the isdn.sub.-- state field in the D-Channel application linkage block is checked to determine if a call is active at some occurrence of the call appearance. An isdn.sub.-- state of call.sub.-- active, outgoing.sub.-- call.sub.-- proceeding, or call delivered indicates that a call is active at some occurrence of the call appearance but not necessarily at this terminal. The states indicate that one terminal sharing the call appearance is off-hook on an incoming or outgoing call or attempting an outgoing call. If the isdn.sub.-- state field does not contain one of these specified values, execution proceeds to block 506 where the process will be repeated for the next D-Channel application linkage block in the list.
If the isdn.sub.-- state field contains one of the specified values, execution proceeds to block 510 where if a process control block exists, an isdn.sub.-- data field in the process control block is checked to determine if the related call is a data call. Whether a process control block exists is determined from the pcbla.sub.-- key field in the D-Channel application linkage block. If the pcbla.sub.-- key field is set to "NULL," no process control block exists and processing continues with block 506 where the process will be repeated for the next D-Channel application block in the list. Otherwise, the pcbla.sub.-- key field identifies the block. The terminal is defined as off-hook only for voice calls. Thus, if a process control block exists and the isdn.sub.-- data field is set to "YES" indicating that the call is a data call, execution proceeds to block 506 where the process will be repeated for the next D-Channel application block in the list.
The following discussion explains how process TTP1, a terminating terminal process that is controlling one side of an incoming call at call appearance CA1 of directory number DN1, uses the data discussed above and the call processing program defined by the flow chart in FIG. 4 to determine the switch-hook status of terminal 181. First, process TTP1 follows the link from its process control block, PCBLA703, to block DALB403 (FIG. 3). By examining the owner field of block DALB403, process TTP1 determines that block TEDB381 contains the terminal equipment data for terminal 181. Process TTP1 reads the cpe.sub.-- type field of block TEDB381 to determine whether terminal 181 is a terminal management terminal or a non-terminal management terminal. For the present example, the cpe.sub.-- type field in block TEDB381 defines terminal 181 as a non-terminal management terminal. Thus, process TTP1 begins to search through the D-Channel application linkage blocks owned by block TEDB381 for any block corresponding to a call at terminal 181 for which terminal 181 would be considered off-hook. Process TTP1 first examines block DALB403. The isdn.sub.-- state of block DALB403 is call.sub.-- received so process TTP1 moves to the next D-Channel application linkage block, DALB402. The isdn.sub.-- state of block DALB402 is call.sub.-- active so process TTP1 locates the process control block associated with the call to examine the isdn.sub.-- data field. The pcbla.sub.-- key field of DALB402 is set to "NULL" indicating that no process control block exists. Process TTP1 continues on to the next D-Channel application linkage block, DALB401. The isdn.sub.-- state of block DALB401 is call.sub.-- active. Process TTP1 locates the process control block associated with the call to examine the isdn.sub.-- data field. The pcbla.sub.-- key field of DALB402 is set to TTP2 so process TTP1 examines the isdn.sub.-- data field for the process control block whose key, process identifier (pid), is set to TTP2. The isdn.sub.-- data field is set to "NO," so process TTP1 checks the shared and associated fields in the business, residence custom services data block linked to block DALB401, block BRCSDB501. If both the shared and associated fields in block BRCSDB502 are set to "YES," the call appearance is only tracking a call that is primary at another occurrence of the shared call appearance. In the present example, the shared and associated fields of block BRCSDB501 are both set to "NO," so process TTP1 determines that terminal 181 is off-hook.
The following describes how process TTP3, a terminating terminal process for an incoming call at call appearance CA2 of directory number DN2 of terminal 184, determines the switch-hook status for terminal 184. FIG. 5 shows the block TEDB384 and associated data stored in memory 137 of control unit 131 for terminal 184, a terminal management terminal. As described above for process TTP1 and terminal 181, process TTP3 finds the terminal equipment data block associated with terminal 184, block TEDB384. Proces TTP3 reads the cpe.sub.-- type field in block TEDB384. Since the cpe.sub.-- type of terminal 184 is terminal management, process TTP3 determines the switch-hook status of terminal 184 by reading the switch.sub.-- hook attribute in block TEDB384. In the present example the switch.sub.-- hook attribute indicates that terminal 184 is on-hook.
The display capabilities for call coverage terminals in a key-system group are now described with reference to an exemplary incoming call to directory number DN1. A translation of the called directory number DN1 results in a determination of the system 100 port connected to terminal 181 since terminal 181 is the lead terminal for key-system group 170 (FIG. 1) having shared directory number DN1. As a result of the translation, a MGLN.sub.-- TERMREQ message (FIG. 6) is received by a routing and terminal allocation (RTA) system process RTASP111. Process RTASP111 reads busy/idle data in memory 117 to determine if an idle call appearance is available for directory number DN1. Assume that call appearance CA1 of DN1 is available. Assume also that terminal 181 is active on call appearance CA3 of directory number DN1 and call appearance CA2 of directory number DN2 is active at terminal 184. Lamps 285 and 286 indicate that active calls are associated with these call appearances. The status of these two call appearances is defined by block DALB401 and block DALB402 (FIG. 3). Process RTASP111 changes the status of call appearance CA1 from idle to busy in the busy/idle data in memory 117 and creates terminating terminal process TTP1 (FIG. 6). In addition, process RTASP111 allocates data blocks DALB403 and BRCSDB503 (FIG. 3).
RTASP111 sends an MGLN.sub.-- TERM message to proces TTP1. The MGLN.sub.-- TERM message contains information about the call, including the calling number and a call type field, e.g., outgoing call external, outgoing call internal, incoming call external, incoming call internal. Outgoing call external indicates that the call is an outgoing call to a terminal outside the business customer group. Outgoing call internal indicates that the call is an outgoing call to a terminal within the business customer group. Incoming call external indicates that the call is an incoming call from a terminal outside the business customer group. Incoming call internal indicates that the call is an incoming call from a terminal within the busines customer group. In the present example, the call type is incoming call external. Process TTP1 allocates block DISPDB603 and stores the calling number and the call type in block DISPDB603. FIG. 3 shows the busy/idle call appearance data, terminal equipment data block, D-channel application linkage blocks, business, residence custom services data blocks, and display data blocks related to terminal 181 and stored in memory 117.
In the present example, the name display feature is not activated. After setting the timer, process TTP1 prepares a SETUP message to send to terminal 181. Process TTP1 formats the data stored in block DISPDB603 into an ASCII test string in the following way. The call type field is translated into a three character ISDN Call Identification (ICI) code. The ISDN call identification code is used as a shorthand method of informing the terminal user of the type of call. Possible ICI code values include but are not limited to the following: OuX (Outgoing call eXternal), OuI (Outgoing call Internal), InX (Incoming call eXternal), and InI (Incoming call Internal). The calling number stored in block DISPDB603 is translated into ASCII. The call appearance at which the call is offered is also indicated in the ASCII string. In this example, the "1=" at the beginning of the ASCII string indicates that the display information corresponds to a call at the first call appearance, call appearance CA1 for directory number DN1. Process TTP1 includes the ASCII string of display data in the SETUP message and sends the SETUP message to terminal 181. In response to the SETUP message containing the display data, terminal alerts, returns CALL.sub.-- PROC or ALERTING messages to process TTP1. While alerting in response to the SETUP message, terminal 181 displays the text string from the SETUP message in display 281 (FIG. 7).
The display capabilities for call coverage terminals in an arrangement in which call coverage is provided through the use of call forwarding are now described with reference to an exemplary incoming call to directory number DN3. Terminal 182, the terminal for which directory number DN3 is a primary directory number, has activated the Call Forwarding No Answer feature. This feature forwards calls that are not answered within a prespecified amount of time. In the present example the amount of time in which the call must be answered is 7 seconds. A translation of called directory number DN3 results in a determination of the system 100 port connected to terminal 182 since directory number DN3 is the primary directory number for terminal 182. As a result of the translation, a MGLN.sub.-- TERMREQ message (FIG. 12) is received by a routing and terminal allocation (RTA) system process RTASP112. Process RTASP112 reads busy/idle data in memory 127 (FIG. 1) to determine if an idle call appearance is available. Assume that call appearance CA1 is available. Assume also that terminal 182 is active on a call at call appearance CA1 for directoy number DN1. RTASP112 determines that the call forwarding no answer feature is activated for terminal 182. RTASP112 creates a terminating terminal process TTP3 and sends an MGLN.sub.-- TERM message (FIG. 12) to process TTP3. The MGLN.sub.-- TERM message contains the calling number and a indication that call forwarding no answer is activated for terminal 182. Process TTP3 sends a SETUP message (FIG. 12) to terminal 182 to offer the incoming call to the terminal. Process TTP3 sets a timer, T1, for 7 seconds.
Assume, for example, that timer T1 expires before terminal 182 has accepted the call. In response to the expiration of timer T1, process TTP3 begins to format a RT.sub.-- GEN message to use in forwarding the call. The call is to be forwarded to directory number DN4. Process TTP3 places the directory number to which the call is to be forwarded, the calling number, and called number in the RT.sub.-- GEN message. Process TTP3 performs the switch--hook determination procedure for a non-terminal management terminal discussed above to determine if terminal 182 is off-hook. Process TTP3 determines that terminal 182 is off-hook so process TTP3 includes in the RT.sub.-- GEN message a call type no.sub.-- answer.sub.-- off-hook indicating that the call was forwarded because the call was not answered at the called terminal and that the called terminal was off-hook on another call appearance. If process TTP3 had determined that the terminal was on-hook, process TTP3 would have included a call type of no.sub.-- answer.sub.-- on-hook indicating the call was forwarded because there was no answer at the called terminal. The RT.sub.-- GEN message (FIG. 13) is sent to a routing and terminal allocation system process RTASP112. A translation of the forward-to directory number DN4 results in a determination of the system 110 port connected to terminal 183 since directory number DN4 is the primary directory number for terminal 183. Process RTASP112 reads busy/idle data in memory 127 to determine if an idle call appearance is available for directory number DN4. Assume that call appearance CA1 is available. Process RTASP112 changes the status of call appearance CA1 from idle to busy in the busy/idle data in memory 127 and creates terminating terminal process TTP4. In addition, process RTASP112 allocates and initializes data blocks DALB407 and BRCSDB507. Process RTASP112 sends an MGLN.sub.-- TERM message (FIG. 13) to process TTP4. The MGLN.sub.-- TERM message contains information about the call, including the calling directory number, the directory number from which the call was forwarded (called number), and the call type. Process TTP4 allocates a display data block DISPDB607 and stores the calling number, directory number DN18; the called number, directory number DN3; and call type information in block DISPDB607.
Next, process TTP4 sends a SETUP message (FIG. 13) to terminal 183. Terminal 183 responds to the SETUP message by alerting and returning CALL.sub.-- PROC or ALERTING messages to process TTP1.
When either timer NAMETIMER expires or the calling and called name information is received from database processor 800, process TTP4 begins to format an INFO message to send to terminal 183. If the calling and called name information has been received, process TTP4 stores the calling and called name in DISPDB607. Process TTP4 formats the display information from DISPDB607, including the name information if it has been obtained, into an ASCII string. If the call type in the display data block is no.sub.-- answer.sub.-- off-hook, indicating that the call was forwarded because the call was not answered and the terminal was off-hook, an ICI code of "OnL", an abbreviation for on-line, is included in the text string. If the call type in the display data block is no.sub.-- answer.sub.-- on-hook, indicating that the call was forwarded because the call was not answered and the terminal was on-hook, an ICI code of "CFN", an abbreviation for call forwarding no-answer, is included in the text string. In the present example, the call type in DISPDB607 is no.sub.-- answer.sub.-- off-hook so an ICI code of "OnL" is included in the test string. Process TTP4 sends an INFO message (FIG. 14) to terminal 183 and includes the text string for the display information in the INFO message. If neither the calling name nor the called name feature were active, process TTP4 would have included this display information in the SETUP message. Terminal 183 displays the text string in display 283 while alerting in response to the call. Based on the ICI code, coverage personnel can determine whether the called party is busy on another call.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4296282 *Jun 30, 1980Oct 20, 1981Bell Telephone Laboratories, IncorporatedIncoming call identification arrangementUS4374308 *Apr 30, 1981Feb 15, 1983Siemens CorporationI-Use indication in a telephone keysetUS4436962 *Mar 30, 1982Mar 13, 1984Bell Telephone Laboratories, IncorporatedCall coverage arrangementUS4567324 *Oct 11, 1983Jan 28, 1986Gte Business Communication Systems, Inc.Secretarial telephone station for use with a secretarial answering systemUS4741026 *May 29, 1986Apr 26, 1988American Telephone And Telegraph Company, At&T Bell LaboratoriesMessage signaling arrangement between a switching system and user terminalsUS4790004 *Dec 10, 1986Dec 6, 1988American Telephone And Telegraph Company, At&T Information SystemsImplied principal busy status indicator for covered callsUS4791662 *Jul 23, 1987Dec 13, 1988American Telephone And Telegraph Company, At&T Bell LaboratoriesControlling key-system groups from a distributed control switching systemJPS64561A * Title not available* Cited by examinerNon-Patent CitationsReference1 *AT&T System 85 Features Reference Manual, AT&T 555 102 301, Issue 1, Apr. 1986, pp. 99 1 through 99 2.2AT&T System 85 Features Reference Manual, AT&T 555-102-301, Issue 1, Apr. 1986, pp. 99-1 through 99-2.3SESS Program, AT&T 5D5-900-301, Sep. 1985, pp. V-94 through V-105.4 *SESS Switch ISDN Basic Rate Interface Specification 5E4 Generic Program, AT&T 5D5 900 301, Sep. 1985, pp. V 94 through V 105.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS5309028 *Jul 14, 1992May 3, 1994At&T Bell LaboratoriesCall coverage arrangement in an ISDN switching systemUS5381468 *May 11, 1992Jan 10, 1995Canon Kabushiki KaishaTelephone exchange including less display elements than channelsUS5390241 *Dec 18, 1992Feb 14, 1995At&T Corp.Shared line appearance across a plurality of switching systemsUS5394464 *Mar 1, 1994Feb 28, 1995At&T Corp.Progressive automatic activation and automatic resetting of call coverageUS5471525 *Sep 23, 1994Nov 28, 1995Hitachi Telecom Technologies, Ltd.Line status display system for telephone exchange systemUS5526416 *Nov 16, 1992Jun 11, 1996Dezonno; Anthony J.Automatic call distribution system with an ISDN compatible call connection system and methodUS5530931 *Oct 20, 1994Jun 25, 1996Telefonaktiebolaget L M EricssonMethod and apparatus for providing a look ahead feature for enhanced call forwarding in a telecommunications systemUS5570420 *Mar 1, 1994Oct 29, 1996Bell Communications Research, Inc.Customer premise equipment network integratorUS5572585 *Mar 14, 1994Nov 5, 1996Canon Kabushi KaishaCommunication system and call processing methodUS5579383 *Jun 20, 1995Nov 26, 1996Lucent Technologies Inc.Calling terminal controlled call coverageUS5600654 *May 25, 1995Feb 4, 1997Lucent Technologies Inc.Multiple call offering method for use with an analog station and an ISDN station that share a directory numberUS5699419 *Dec 20, 1994Dec 16, 1997Lucent Technologies Inc.Analog multibutton telephone keysetsUS5828741 *Aug 22, 1996Oct 27, 1998Samsung Electronics Co., Ltd.System and method for providing a multi-number plan for use with a general telephone and a key telephone in a key telephone systemUS6647107 *May 27, 1999Nov 11, 2003AlcatelMulti-user answering system and methodUS6856678 *Apr 2, 2001Feb 15, 2005Siemens AktiengesellschaftMethod for updating call redirection destinations in a communication networkUS6912273 *Dec 28, 2000Jun 28, 2005Siemens Communications, Inc.PBX switch incorporating methods and apparatus for automatically detecting call appearance values for each primary directory number on a basic rate interfaceUS8630400 *Aug 6, 2009Jan 14, 2014Nec CorporationTelephone relay system, telephone relay apparatus, recording medium and data processing methodUS20100040223 *Aug 6, 2009Feb 18, 2010Shinya AraoTelephone relay system, telephone relay apparatus, recording medium and data processing methodEP0503412A2 *Feb 29, 1992Sep 16, 1992Neumann Elektronik GmbHKey-controlled multi-line telephone system for alternate, simultaneous or loud-speaking and communication* Cited by examinerClassifications U.S. Classification379/157, 379/165, 379/164, 379/214.1, 379/142.1, 379/207.1, 379/207.5, 379/207.8International ClassificationH04Q11/04Cooperative ClassificationH04Q11/0428European ClassificationH04Q11/04SLegal EventsDateCodeEventDescriptionMar 29, 2001FPAYFee paymentYear of fee payment: 12Mar 10, 1997FPAYFee paymentYear of fee payment: 8Feb 23, 1993FPAYFee paymentYear of fee payment: 4Jun 14, 1988ASAssignmentOwner name: AMERICAN TELEPHONE AND TELEGRAPH COMPANY, 55O MADIFree format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNORS:DAVIDSON, WAYNE A.;ERNST, JOHN P.;HERKES, MARYBETH;AND OTHERS;REEL/FRAME:004896/0361Effective date: 19880613Owner name: BELL TELEPHONE LABORATORIES, INCORPORATED, 600 MOURotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google