Private automatic branch exchange system
19 claims: 2 independent, 17 dependent
- 1A private automatic branch exchange system connected through a communication line (61) to an ISDN public network (101), comprising:a switching network (131a) for switching between said communication line (61) connected to said ISDN public network (101) and an extension line (62) accommodated by said private automatic branch exchange system;and a control means (63), operatively connected to said switching network, for controlling the switching operation of said switching network, and comprising means for transmitting incoming information to said extension line;characterized in that;said control means comprises: means for adding a line accessing number (α) indicating the address of the communication line (61), to a calling party public network address (#B) in an incoming call information (ii) received through said communication line so as to form incoming information.
- 6An extension terminal (132b) accommodated in a private automatic branch exchange for transferring a call identification information for identifying a calling person to a called person when a call is set up, wherein said extension terminal comprises:a call identification information registering means (624), which enables a user to register a call identification register information;and characterised in that said extension terminal comprises: a detection means which compares the call identification information transferred from the exchange with the call identification register information which has been already registered in the call identification register information registering means at the incoming call and detects the call identification register information in the call identify information;and a call-incoming information change means (612) for changing a call-incoming information depending on whether or not the call identification register information, which has been already registered in the call identification register information registering means, is detected in the detection means.
Independent claims2
96 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
(1) Field of the Invention
0001The present invention relates to a private automatic exchange (PBX) system for controlling a calling party address in an Integrated Systems Digital Network (ISDN public network), and more particularly, to a connecting system between a terminal connected to an ISDN public network and an extension terminal accommodated by a PBX system.
0002To connect an ISDN public network and a PBX system, it is required to be able to deal with an extension terminal accommodated by the PBX system on an equal basis with a terminal connected to the ISDN.
(2) Description of the Related Art
0003In a conventional PBX system, as described later in more detail with reference to the drawings, when a call is effected from a terminal connected to the ISDN public network to an extension terminal accommodated by the PBX system, the extension terminal receives the calling party address from the calling party terminal through the ISDN public network and a PBX network in the PBX system. The called party extension terminal, however, could not identify whether the received calling party address is from a terminal connected to the ISDN network or from another extension terminal accommodated by the PBX system. This was inconvenient for the user of the PBX system. Namely, for example, if the user is away from the called party extension terminal when a call is made to the extension terminal, after the termination of the call, if the user wants to return the call to the person at the calling party terminal, the user cannot call back to the calling party terminal because the user has no way of knowing whether the calling party was from the ISDN network or from another extension terminal accommodated by the PBX system.
0004Hitachi Review Vol. 37 no. 1, Feb. 1988 shows at pages 31-36 features corresponding to those of the preamble of claim 1. Proceedings of the 6th International Conference on Computer Communications, London 1982 p. 345-350 shows two ways of transmitting extension numbers from a private network to a public network. International Switching Symposium, Phoenix, 15-20 March 1987, Vol. 4, p. 899-906 shows how the identity of a caller is transmitted to the person being called, via ISDN.
SUMMARY OF THE INVENTION
0005Accordingly, an object of the present invention is to provide a private automatic branch exchange system which can distinguish whether an incoming call received by an extension terminal accommodated by the PBX system is a call from an another extension terminal accommodated by the PBX system or a call from a terminal connected to the ISDN public network.
0006Another object of the present invention is to provide a private automatic branch exchange system which can effect a call back from an extension terminal accommodated by the PBX system to a terminal, which previously originated a call to the extension terminal, connected to the ISDN public network.
0007There is provided, according to the present invention, a private automatic branch exchange system as set out in claim 1.
0008Another aspect of the invention is set out in claim 6.
BRIEF DESCRIPTION OF THE DRAWINGS
0009The above objects and features will be more apparent from the following description of the preferred embodiments with reference to the drawings, wherein: <ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 is a diagram showing a conventional connecting system in an ISDN, for explaining the background of the invention;</li><li>Fig. 2 is a diagram showing a conventional call connection sequence;</li><li>Fig. 3 is a diagram showing the contents of the messages in respective steps in the public network connection sequence;</li><li>Fig. 4 is a block diagram of a system including a PBX system and an ISDN public network for explaining a conventional call receiving operation by an extension terminal accommodated by the PBX system;</li><li>Fig. 5 is a block diagram of a system including a PBX system and an ISDN public network for explaining a conventional call back operation from an extension terminal accommodated by the PBX system;</li><li>Fig. 6 is a block diagram showing a connecting system between an ISDN public network and a PBX system for explaining the principle of a first embodiment of the present invention;</li><li>Fig. 7 is a block diagram showing the construction of a PBX system in the first embodiment of the present invention;</li><li>Fig. 8 is a block diagram showing in detail an extension terminal accommodated by the PBX system and a digital line circuit (DLC) in the PBX system according to the first embodiment of the present invention;</li><li>Fig. 9 is a diagram showing a call connection sequence between the ISDN public network and the PBX system in the first embodiment of the present invention;</li><li>Fig. 10 is a flowchart for explaining the operation of the control unit connected to a PBX network according to the first embodiment of the present invention;</li><li>Fig. 11 is a diagram explaining addresses in a main memory in the PBX system according to the first embodiment of the present invention;</li><li>Fig. 12 is a diagram explaining the contents of a memory in the extension terminal according the first embodiment of the present invention;</li><li>Fig. 13 is a flowchart for explaining a display operation of a calling party address according to the first embodiment of the present invention;</li><li>Fig. 14 is a flowchart for explaining a saving and call back operation according to the first embodiment of the present invention; and</li><li>Fig. 15 is a block diagram showing in detail an extension terminal accommodated by the PBX system and a digital line circuit (DLC) in the PBX system according to the second embodiment of the present invention.</li></ul>
DESCRIPTION OF THE PREFERRED EMBODIMENT
0010For better understanding of the present invention, the background and the conventional connecting system between a terminal connected to an ISDN public network and an extension terminal accommodated by a PBX system will first be described with reference to Figs. 1 to 5.
0011Note, throughout the specification, the same reference numberss represent the same parts.
0012Figure 1 is a diagram showing a conventional connecting system in an ISDN public network, for explaining the background of the invention. In Fig. 1, 101 is an ISDN (CO), and 102 to 105 are ISDN terminals (TE<sub>a1</sub> , TE<sub>a2</sub> , TE<sub>b1</sub> , TE<sub>b2</sub>), respectively. In an ISDN public network, eight ISDN terminals at a maximum can be connected to each subscriber line which is a bus . Each ISDN terminal has a main address or, in other words, a subscriber line number for identifying the subscriber line and, in addition, a subaddress for identifying the ISDN terminal.
0013In the conventional example shown in Fig. 1, a subscriber line A is provided with a subscriber line number #A and subaddresses #① or #② for identifying the ISDN terminal (TE<sub>a1</sub> or TE<sub>a2</sub>) 102 or 103 connected to the subscriber line A. Similarly, a subscriber line B is provided with a subscriber line number #B and subaddresses #① or #② for identifying the ISDN terminal (TE<sub>b1</sub> or TE<sub>b2</sub>) 104 or 105 connected to the subscriber line B.
0014(i), (ii), (iii) and (iv) represent signals including call setup messages for setting up calls. In each call setup message passing through the ISDN public network, there are four fields for transmitting address information, i.e., a calling party address (or in other words a calling party main address), a calling party subaddress, a called party address (or in other words a called party main address), and a called party subaddress. By setting appropriate data in these fields, a call setup is effected.
0015Figure 2 is a diagram showing a call connecting sequence in a public network, and Fig. 3 is a diagram showing contents of messages in respective steps in the public network connecting sequence.
0016Assuming that, in Fig. 1, a call is originated from the ISDN terminal (TE<sub>a1</sub>) 102 to the ISDN terminal (TE<sub>b2</sub>) 105, this case is practically described as an example with reference to Fig. 2 and Fig. 3.
0017First, when a person lifts the ISDN terminal (TE<sub>a1</sub>) 102 off hook to call the ISDN terminal (TE<sub>b2</sub>) 105, the call setup message (i) as illustrated in Fig. 1 is setup, and the call setup message (i) then sent to the ISDN public network (CO) 101 (see Fig. 2, ①). Namely, the calling party address in this case is the subscriber line number #A; the calling party subaddress is the subaddress #① identifying the ISDN terminal (TE<sub>a1</sub>) 102; the called party address is the subscriber line number #B identifying the destination subscriber line B; and the called party subaddress is the subaddress #② identifying the destination ISDN terminal (TE<sub>b2</sub>) 105. The call setup message (i) further includes, as shown in Fig. 3, (a), a message indicating the type of message. In this case, the type of message indicates that the message (i) is a call setup message.
0018When the ISDN public network (CO) 101 receives the call setup message, it recognizes that the destination subscriber line is #B and transmits a call setup message which is the same as the call setup message (i) as shown in Fig. 1 to the subscriber line #B (see Fig. 2, ②). Then, the ISDN public network (CO) 101 returns a call proceeding message as shown in Fig. 3, (b) to the calling party ISDN terminal (TE<sub>a1</sub>) 102 (see Fig. 2, ③), and then transmits an alert message (see Fig. 3, (C)), received from the called party terminal (TE<sub>b2</sub>) 105, to the calling party terminal (TE<sub>a1</sub>) 102. At the calling party terminal (TE<sub>a1</sub>) 102, in response to the reception of the alert message, a person is informed of the alert state by its being displayed or by a sound (see Fig. 2, ④). On the other hand, at the called party terminal (TE<sub>b2</sub>) 105, simultaneous with the transmission of the alert message to the ISDN public network (CO) 101, a ringing tone is generated (see Fig. 2, ⑤).
0019The subscriber line #B receives the alert message in accordance with a predetermined ISDN sequence. Since the called party subaddress in this example is #② , only a person at the ISDN terminal (TE<sub>b2</sub>) 105 responds to the ringing tone by lifting the receiver off hook so that a connection message as shown in Fig. 3, (d) is transmitted from the terminal (TE<sub>b2</sub>) 105 to the ISDN public network (CO) 101 (see Fig. 2, ⑥). The ISDN public network (CO) 101, when receiving the connection message, transmits it to the calling party terminal (TE<sub>a1</sub>) 102. The calling party terminal (TE<sub>a1</sub>) 102 then stops the alert display or sound, and a connection is established between the calling party terminal (TE<sub>a1</sub>) 102 and the called party terminal (TE<sub>b2</sub>) 105.
0020A disconnection, a release, and a release complete after the end of the communication are carried out by⑦, ⑧ and ⑨ in Fig. 2. The contents of the messages in the disconnection, release, and release complete are illustrated in Fig. 12, (e), (f), and (g).
0021In the above-described connection through the ISDN public network, a call back connection is possible as described in the following, and therefore the connection system is very convenient for the user.
0022Namely, by storing the calling party address and the calling party subaddress received by the called party terminal into a memory unit provided in the called party terminal, and by displaying the stored contents on a display unit or the like, the user, who was away from the called party terminal when the incoming call was terminated at the called party terminal, can immediately recognize the calling party address and subaddress on the display on the like. Therefore, by setting the displayed address and subaddress into a call setup message to be called back from the called party terminal to the original calling party terminal, the user at the called party terminal can call back the person at the original calling party terminal.
0023In a connecting system between an ISDN public network and ISDN PBX system, however, the above-described call back connection is not so easy, as described in more detail in the following with reference to Figs. 4 and 5.
0024Fig. 4 is a block diagram of a system including a PBX system and an ISDN for explaining a conventional call receiving operation by an extension terminal accommodated by the PBX system. Referring to Fig. 4, an example will be described in which a call is effected from a terminal (TE<sub>b2</sub>) 105 connected to an ISDN public network (CO) 101 to an extension terminal (TE<sub>a1</sub>) 132 accommodated through an extension line #a by a PBX system. In the figure, the subscriber line number of the PBX 131 is #A, and the extension line number of the PBX is #a. In a ISDN PBX, eight extension terminals at the maximum can be connected to the extension line #a. The public network (CO) 101, the terminal (TE<sub>b1</sub>) 104, and the terminal (TE<sub>b2</sub>) 105 are the same as those shown in Fig. 1.
0025First, when a person takes the ISDN terminal (TE<sub>b2</sub>) 105 off hook to call the extension terminal (TE<sub>a1</sub>) 132, the call setup message (i) as illustrated in Fig. 1 is setup, and then the call setup message (i) is sent to the ISDN public network (CO) 101. Namely, the calling party address in this case is the subscriber line number #B; the calling party subaddress is the subaddress #② for identifying the ISDN terminal (TE<sub>b2</sub>) 105; the called party address is the subscriber line number #A for identifying the destination subscriber line A connected between the PBX 131 and the ISDN public network 101; and the called party subaddress is #a#① which is a combination of a number #a of the called party extension line accommodated by the PBX 131 and a number #① of the called party extension terminal accommodated by the PBX 131. In fig. 4 also, the call setup message is represented by (i). The contents of the call setup message are similar to that shown if Fig. 3, but the called party subaddress is different as can be seen from the above description. When the ISDN public network (CO) 101 receives the call setup message (i), it recognizes that the destination subscriber line is #A and transmits a call setup message (ii) which is the same as the call setup message (i) to the PBX 131.
0026The PBX 131 then analyzes the called party subaddress and takes out from the subaddress the extension line number #a to form a call setup message (iii) having the called party address #a and a called party subaddress #① which is obtained by deleting the extension line number #a from the called party subaddress received from the ISDN public network (CO) 101. The PBX 131 then transmits the thus obtained called party subaddress #① to the extension line a.
0027The extension terminal (TE<sub>a1</sub>) 132 compares its own address with the called party subaddress #①, and if they coincide, it generates a ringing tone. When a person who hears the ringing tone takes the receiver off hook, a connection is established between the terminal (TRE<sub>b2</sub>) 105 and the extension terminal (TE<sub>a1</sub>) 132.
0028Fig. 5 is a block diagram of a system including a PBX system and an ISDN for explaining a conventional call originating operation by an extension terminal accommodated by the PBX system. Referring to Fig. 5, an example will be described in which a call is effected from an extension terminal (TE<sub>a1</sub>) 132 accommodated by the PBX 131 through the ISDN public network (CO) 101 to an ISDN terminal (TE<sub>b2</sub>) 105. In this case, first, the extension terminal (TE<sub>a1</sub>) 132 sets a setup message (i) and transmits it to the PBX 131. The setup message (i) in this case has, as illustrated in the figure, a calling party address #a which is the extension line number; a calling party subaddress is the subaddress #① for identifying the extension terminal (TE<sub>a1</sub>) 132; a called party address α#B which is a combination of a line accessing number α for identifying the communication line A connected between the PBX 131 and the ISDN public network (CO) 101 and the subscriber line number #B for identifying the destination subscriber line B connected to the destination terminal (TE<sub>b2</sub>) 105; and a called party subaddress #② for identifying the destination terminal (TE<sub>b2</sub>). In Fig. 4 also, the call setup message is represented by (i).
0029When the PBX 131 receives the call setup message (i) from the extension terminal (TE<sub>a1</sub>) 132, the PBX 131 analyzes the called party address in the call setup message. If the line accessing number α is found in the call setup message, the PBX 131 recognizes that the destination terminal is not an extension terminal accommodated by the PBX 131 but is a terminal connected to the ISDN public network (CO) 101. The PBX 131 then edits a call setup message (ii) and transmits it to the ISDN public network (CO) 101. Namely, the call setup message (ii) has, in this case, a called party address #B which is the number of the subscriber line B connected to the ISDN terminal (TE<sub>b2</sub>) 105 and which is obtained by subtracting the line accessing number α from the called party address α#B received from the extension line; a called party subaddress #② for identifying the terminal (TE<sub>b2</sub>) 105 and which is received from the extension line; a calling party address #A which is the subscriber line number of the communication line connected between the PBX 131 and the ISDN public network (CO) 101; and a calling party subaddress #a#① which is a combination of the calling party subaddress #① received from the extension line and the number #a of an extension line connected to the calling party extension terminal (TE<sub>a1</sub>) 132 accommodated by the PBX 131. Thus, from the extension terminal connected to the extension line accommodated to the PBX 131, the ISDN terminal (TE<sub>b2</sub>) 105 connected to the subscriber line B which is connected to the ISDN public network (CO) 101 can be called. When the terminal (TE<sub>b2</sub>) 105 responds to the call, the connection between the extension terminal (TE<sub>a1</sub>) 132 and the ISDN terminal (TE<sub>b2</sub>) 105 is established.
0030There is, however, a problem in the above-mentioned conventional connecting system, as briefly mentioned before. Namely, when a call is effected from the ISDN terminal (TE<sub>b2</sub>) 105 to the extension terminal (TE<sub>a1</sub>) 132 as described with reference to Fig. 4, the extension terminal (TE<sub>a1</sub>) 132 only receives the calling party address #B. It should be noted that another extension terminal accommodated to the PBX 131 may also have the same address #B as the above-mentioned calling party address #B. Therefore, the called party extension terminal (TE<sub>a1</sub>) 132 can not identify whether the received calling party address is from a terminal connected to the ISDN public network or from another extension terminal accommodated by the PBX system. Therefore, if the user is away from the called party extension terminal when a call is terminated at the extension terminal, and after the termination of the call, if the user wants to call back the person at the calling party terminal, the user cannot effect the call back of the calling party terminal because the user does not know the line access number #A for accessing the communication line connected between the PBX system and the ISDN public network.
0031Now an embodiment of the present invention will be described with reference to Figs. 6 to 14.
0032Fig. 6 is a block diagram showing a connecting system between an ISDN and a PBX system for explaining the principle of a first embodiment of the present invention. In Fig. 6, an ISDN PBX system 60 is connected through a communication line 61 to an ISDN public network (CO) 101. The PBX system 60 includes a switching network 131a for switching between the communication line 61 connected to the ISDN public network 131a and an extension line 62 accommodated to the ISDN PBX system 60, a control unit (CC) 63 connected to the switching network, for controlling the switching operation of the switching network, and an extension terminal (TE<sub>a1</sub>) 132a accommodated by the PBX system 60 and connected through the extension line 62 to the switching network 131a. The control unit (CC) 63 operates to add a line accessing number α to a calling party address #B in an incoming call information (ii) from the ISDN public network (CO) 101 and received by the switching network 131a through said communication line 61. The line accessing number α can be used when a call is originated from the extension terminal (TE<sub>a1</sub>) 132a through the switching network 131a and through the communication line 61 to the ISDN public network (CO) 101. The control unit 63 forms an information α#B provided with the line accessing number α and transmits the information α#B to the extension terminal, when the incoming call information (ii) from the communication line is received by the switching network 131a.
0033Namely, in Fig. 4, different from the conventional constitution shown in Fig. 4, to the calling party address information #B in the call setup message (ii) transmitted from the ISDN public network (CO) 101 to the switching network 131a, the line accessing number α is provided to form a new calling party address, and the new calling party address is inserted into a calling party address section in a call setup message (iii) to be transmitted from the switching network 131a to the extension terminal (TE<sub>a1</sub>) 132a. The other portions except for the above mentioned difference are the same as the portions in the conventional constitution shown in Fig. 4. That is, the subscriber line number of the switching network 131a is #A, and the extension line number of the extension line 62 accommodated by the PBX system 60 is #a. In a ISDN PBX, eight extension terminals at the maximum can be connected to the extension line 62. The public network (CO) 101, the terminal (TE<sub>b1</sub>) 104, and the terminal (TE<sub>b2</sub>) 105 and the same as those shown in Fig. 4.
0034First, when a person takes the ISDN terminal (TE<sub>b2</sub>) 105 off hook to call the extension terminal (TE<sub>a1</sub>) 132a, the call setup message (i) as illustrated in Fig. 6 is setup, and then the call setup message (i) is sent to the ISDN public network (CO) 101. Namely, the calling party address in this case is the subscriber line number #B; the calling party subaddress is the subaddress #② for identifying the ISDN terminal (TE<sub>b2</sub>) 105; the called party address is the subscriber line number #A for identifying the destination subscriber line 61 connected between the PBX switching network 131a and the ISDN public network (CO) 101; and the called party subaddress is #a#① which is a combination of a number #a of the called party extension line 62 accommodated by the PBX system 60 and a number #① of the called party extension terminal (TE<sub>a1</sub>) 132a accommodated by the PBX system 60. The call setup message (i) is the same as that shown in Fig. 4.
0035When the ISDN public network (CO) 101 receives the call setup message (i), it recognizes that the destination subscriber line is #A and transmits a call setup message (ii) which is the same as the call setup message (i) to the switching network 131a.
0036The PBX switching network 131a then analyzes the called party subaddress and takes out from the subaddress the extension line number #a to form a call setup message (iii) having the called party address #a and a called party subaddress #① which is obtained by deleting the extension line number #a from the called party subaddress received from the ISDN public network (CO) 101. The PBX switching network 131a then transmits the thus obtained called party subaddress #① to the extension line 62.
0037The extension terminal (TE<sub>a1</sub>) 132a compares its own address with the called party subaddress #①, and if they coincide, the terminal 132a generates a ringing tone. When a person who hears the ringing tone takes the receiver off hook, a connection is established between the terminal (TE<sub>b2</sub>) 105 and the extension terminal (TE<sub>a1</sub>) 132a.
0038Since the calling party address in the setup message (iii) received by the extension terminal (TE<sub>a1</sub>) 132a includes the line access number α for identifying the communication line connected between the switching network 131a and the ISDN public network (CO) 101, and by displaying the line number α on a display for example, the user at the extension terminal (TE<sub>a1</sub>) 132a can recognize that the incoming call is not a call from another extension terminal accommodated by the PBX system 60 but is a call from a terminal connected to the ISDN public network 101.
0039To call back from the called party extension terminal (TE<sub>a1</sub>) 132a to the calling party terminal (TE<sub>b2</sub>) 105, it is sufficient to send back a message, having a destination address and a destination subaddress which are respectively the calling party address α#B and the calling party subaddress #② in the call setup message (iii), from the called party extension terminal (TE<sub>a1</sub>) 132a to the calling party terminal (TE<sub>b2</sub>) 105.
0040The communication line 61 is formed by a central office line connected between the ISDN public network (CO) 101 and the switching network 131a.
0041The communication line 61 may alternatively be a private line connected between the ISDN public network (CO) 101 and the switching network 131a.
0042The incoming call information (ii) is a call setup message.
0043The extension terminal (TE<sub>a1</sub>) 132a includes a display unit for displaying the line accessing number α and the calling party address #B when the extension terminal (TE<sub>a1</sub>) 132a receives an incoming message (iii) transmitted from the switching network 131a.
0044The incoming message (iii) is transmitted by the use of one channel in a plurality of channels in a subscriber line connected between the switching network 131a and the extension terminal (TE<sub>a1</sub>) 132a.
0045The plurality of channels are 2B + D channels.
0046The channel for transmitting the incoming message (iii) is a control channel D in the 2B + D channels.
0047The extension terminal (TE<sub>a1</sub>) 132a includes a storage unit for storing the incoming message (iii), a plurality of function keys for instructing predetermined functions, and a terminal control unit operatively connected to the storing unit, the function keys, and the display unit, for controlling the storing unit, the display unit, and the function keys, whereby by using the line accessing number in the calling party information in the incoming message (iii) read from the storing unit, a call back can be automatically carried out from the destination extension terminal (TE<sub>a1</sub>) 132a to the calling party terminal.
0048The storage unit for storing the incoming message has a plurality of storage areas corresponding to the function keys.
0049The extension terminal (TE<sub>a1</sub>) 132a comprises a detecting unit for detecting one of the function keys being pushed, a reading unit for reading the line accessing number α and the calling party address information #B stored in a memory area corresponding to the pushed function key, and a transmitting unit for transmitting the read line accessing number α and the read calling party address information #B to the switching network 131a, whereby, when a call back is carried out from the extension terminal (TE<sub>a1</sub>) 132a to the calling party which previously called the extension terminal (TE<sub>a1</sub>) 132a, the switching network 131a receives the line accessing number α and the calling party address information #B, and transmits them to the calling party corresponding to the line accessing number α.
0050During a communication between the extension terminal (TE<sub>a1</sub>) 132a and the calling party through the switching network 131a, when the extension terminal (TE<sub>a1</sub>) 132a detects that one of the function keys is pushed, the calling party address information temporarily stored in the storage unit is transferred from a temporary storage memory area to a memory area corresponding to the pushed key.
0051When a call is to be originated from the extension terminal (TE<sub>a1</sub>) 132a, if the detecting unit detects that the function key is pushed, the calling party address is read from the memory area corresponding to the specified function key and transmitted to the calling party.
0052The extension terminal (TE<sub>a1</sub>) 132a identifies a line number provided to the calling party information in the incoming message received by the switching network 131a, and, depending on whether the identified line number is for an extension line accommodated by the PBX system or for an external communication line connected between the switching network 131a and the ISDN public network (CO) 101, the extension terminal (TE<sub>a1</sub>) 132a generates different ringing tones.
0053Figure 7 is a block diagram showing the detailed construction of the switching network 131a in the system shown in Fig. 6. In the figure, 71 is a network (NW), 72 is a digital extension line circuit (DLC) or in other words a line circuit for ISDN terminals, 73 is a communication line trunk (TRK), 74 is a common control unit (CC) which is the same as the control unit (CC) 63 in Fig. 6, and 75 is a main memory (MM).
0054The common control unit (CC) 74 receives a call setup message from the communication line trunk (TRK) 73, provides the line accessing number α to the calling address #B in the received call setup message, carries out other editing processes, and transmits the call setup message through the digital extension line circuit (DLC) 72 to the extension line 62.
0055Fig. 8 is a block diagram showing the constitution of the extension terminal (TE<sub>a1</sub>) 132a and the digital extension line circuit (DLC) 72. In the extension terminal (TE<sub>a1</sub>) 132a in the figure, 801 is a telephone hand set (H), 802 is a speech path circuit (SP), 803 is a code (C/D), 804 is a data terminal (DTE), 805 is a level converter (LV), 806 is a data speed converter (RA), 807 is a display unit (DSP), 808 is a switch (SW), 809 is a controller (CTL), 810 is a frame assembling/disassembling part (FC), 811 is a driver (DV), 812 is a receiver (R), 813 is a power source (POW), 814 is a hook switch (HS), 815 is a function key, and 816 is a memory.
0056On the display unit (DSP) 807, the calling party address from the switching network (NW) 71 is directly displayed. The calling party address from the switching network (NW) 71 is also stored in the memory 816, and its contents can be displayed later on the display unit (DSP) 807. By seeing the number on the display unit (DSP) 807, the user can determine whether the incoming call is from another extension terminal accommodated to the PBX system 60 or from a terminal connected to the ISDN public network 101. Further, a call back can be carried out to the original calling party by operating the key 815 so as to form a destination address and a destination subaddress which are respectively the same as the calling party address and the calling party subaddress being displayed on the display part (DSP) 807.
0057In the digital extension line circuit (DLC) 72, 820 is a frame assemble/disassemble circuit (FC), 821 is a driver (D), 822 is a receiver (R), and 823 is an interface part (INF).
0058The line between the digital extension line circuit (DLC) 72 and the extension terminal (TE<sub>a1</sub>) 132a is a digital subscriber line referred to as 2B + D. Here, the B channels are data channels and the D channel is a control signal channel.
0059Figure 9 is a diagram showing a call connection sequence between the ISDN public network (CO) 101 and the PBX network. In Fig. 9, the difference from the conventional public network sequence shown in Fig. 2 resides only in that there is a PBX switching network between the called party extension terminal and the ISDN public network. In the PBX system 60, the calling party address received from the ISDN public network is processed ad described before and the call setup message is then transmitted to the called party extension terminal.
0060Namely, assume that, in Fig. 6, a call is originated from the ISDN terminal TE<sub>b2</sub>) 105 to the extension terminal (TE<sub>a1</sub>) 132a. First, when a person takes the ISDN terminal (TE<sub>b2</sub>) 105 off hook to call the extension terminal (TE<sub>a1</sub>) 132a, the call setup message (i) as illustrated in Fig. 6 is setup, and then the call setup message (i) is sent to the ISDN public network (CO) 101 (see Fig. 9, ①). When the ISDN public network (CO) 101 receives the call setup message, it recognizes that the destination subscriber line is the communication line 61 and transmits a call setup message which is the same as the call setup message (i) as shown in Fig. 6 to the subscriber line 61. The PBX switching network 131a receives the call setup message (ii) through the communication line 61, and forms the call setup message (iii) as shown in Fig. 6. The call setup message (iii) is then sent to the extension terminal (TE<sub>a1</sub>) 132a (see Fig. 9, ②′). Then, the ISDN public network (CO) 101 returns a call proceeding message (B) as shown in Fig. 3 to the calling party ISDN terminal (TE<sub>B2</sub>) 105 (see Fig. 9, ③), and then transmits an alert message (C) (see Fig. 3), received from the called party extension terminal (TE<sub>a1</sub>) 132a, to the calling party terminal (TE<sub>b2</sub>) 105. At the calling party terminal (TE<sub>b2</sub>) 105, in response to the reception of the alert message, a person is informed of the alert state by displaying it or by sound (see Fig. 9, ④). On the other hand, at the called party extension terminal (TE<sub>a1</sub>) 132a, simultaneous with the transmission of the alert message to the ISDN public network (CO) 101, a ringing tone is generated (see Fig. 9, ⑤).
0061The communication line 61 receives the alert message in accordance with a predetermined ISDN sequence. Since the called party subaddress in this example is #②, only a person at the extension terminal (TE<sub>a1</sub>) 132a responds to the ringing tone by taking the receiver off hook, so that a connection message (d) as shown in Fig. 3 is transmitted from the extension terminal (TE<sub>a1</sub>) 132a through the switching network 131a to the ISDN public network (CO) 101 (see Fig. 9, 6 ). The ISDN public network (CO) 101, when receiving the connection message, transmits it to the calling party terminal (TE<sub>b2</sub>) 105. The calling party terminal (TE<sub>b2</sub>) 105 then stops the alert display or sound, and a connection is established between the calling party terminal (TE<sub>b2</sub>) 105 and the called party extension terminal (TE<sub>a1</sub>) 132a.
0062A disconnection , a release, and a release completion after the end of the communication are carried out by 7, 8, and 9 in Fig. 9. The contents of the messages in the disconnection, release, and release completion are illustrated in Fig. 3, (e), (f), and (g).
0063A call back connection according to the embodiment of the present invention can be effected as follows.
0064Namely, by storing the calling party address including the line accessing number α and the calling party subaddress received by the called party terminal, in the memory unit (M) 816 provided in the called party terminal, and by displaying the stored contents on the display unit (DSP) 807 or the like, the user, who was away from the called party terminal when the incoming call is terminated at the called party terminal, can immediately recognize whether the calling party is from the ISDN public network or from another extension terminal accommodated by the PBX system. So, by setting the displayed address including the line accessing number and subaddress into a call setup message to be transmitted from the called party terminal to the original calling party terminal, the user at the called party terminal can call back the person at the original calling party terminal.
0065Fig. 10 is a flowchart explaining the operation of the common control unit (CC) 74 connected to the switching network 131a as shown in Fig. 7. In Fig. 10, at step 101 the common control unit (CC) 74 receives a call setup message, such as the call setup message (ii), from the communication line trunk (TRK) 73.
0066At step 102, from the called party subaddress #a#① in the call setup message received from the communication line trunk (TRK) 73, the called party extension line number #a is taken out and the taken out number #a is inserted as a called party address into the setup message (iii) to be transmitted to the called party digital extension line circuit (DLC) 72.
0067At step 103, the called party subaddress #① in the received call setup message (ii) is inserted as a called party subaddress into the setup message (iii) to be transmitted to the called party digital extension line circuit (DLC) 72.
0068At step 104, the line accessing number α is added to the head of the calling party address #B received from the communication line trunk (TRK) 73, and the combined number α#B is inserted as a calling party address into the setup message (iii) to be transmitted to the called party digital extension line circuit (DLC) 72.
0069At step 105, the calling party subaddress #② in the call setup message received from the communication line trunk (TRK) 73 is inserted as a calling party subaddress into the setup message (iii) to be transmitted to the called party digital extension line circuit (DLC) 72.
0070At step 106, the other processes necessary for editing the setup message (iii) are carried out.
0071Finally, at step 107, the setup message (iii) is transmitted to the called party digital extension line circuit (DLC) 72.
0072Thus, the transmission of the call setup message is completed.
0073Fig. 11 is a diagram explaining the processes on the main memory (MM) 75 shown in Fig. 7. From the figure, it can be seen that the call setup message (ii) from the communication line trunk (TRK) 73 is changed to the call setup message (iii) in the PBX system, and is transmitted to the called party digital extension line circuit (DLC) 72.
0074Fig. 12 is a diagram explaining the contents of the memory (M) 816 in the extension terminal (TE<sub>a1</sub>) 132a shown in Fig. 8. As shown in the figure, the memory (M) 816 includes two buffer memories (BF1) 121 and (BF2) 122, and a plurality of saving memories (SA#1 to SA#n) 123 -1 to 123 -n for saving data to be used for effecting the call back functions. The buffer memory (BF1) 121 stores the received setup message, and the buffer memory (BF2) 122 stores a setup message used for the call back operation. The saving memories (SA#1 to SA#n) 123 -1 to 123 -n respectively correspond to the function keys.
0075Fig. 13 is a flowchart explaining the display operation by the controller (CTL) 809 shown in Fig. 12. Referring to Fig. 13, at step 131, the controller (CTL) 809 receives the call setup message (iii) from the switching network (NT) 71 and stores it into the buffer memory (BF1) 121. Then at step 132, the calling party address and the calling party subaddress in the call setup message are read from the buffer memory (BF1) 121 and are displayed on the display unit (DSP) 307. From the displayed date, the user can recognize whether the calling party is from the ISDN public network or from another extension terminal accommodated by the PBX system.
0076Fig. 14 is a flowchart explaining a save and a call back operation by the controller (CTL) 809 shown in Fig. 12. Referring to Fig. 14, when a function key #i in the key 815 is pushed at step 141, a discrimination is made of whether or not the extension terminal 132a is under communication at step 142.
0077If it is under communication, at step 143, the calling party address and the calling party subaddress stored in the buffer (BF1) 121 are saved into the saving memory (SA#i) 123 -i corresponding to the pushed function key, and the process is finished.
0078If the extension terminal 132a is not under communication at step 142, then, at step 144, the calling party address and the calling party subaddress stored in the saving memory (SA#i) 123 -i are copied to the buffer memory (BF2) 122.
0079Then, at step 145, the address and the subaddress of the extension terminal (TE<sub>a1</sub>) 132a are stored as a calling party address and a calling party subaddress into the buffer memory (BF2) 122 for the call back operation.
0080Then, at step 146, necessary information as a call setup message for the call back operation is edited.
0081At step 147, the data in the buffer memory (BF2) 122 is transmitted through the switching network 71 and the ISDN public network (CO) 101 to the original calling party terminal (TE<sub>b2</sub>) 105.
0082Thus, the call back function can be effected according to the first embodiment of the present invention.
0083Fig. 15 is a block diagram showing an extension terminal accommodated by the PBX system 60, according to another embodiment of the present invention. In Fig. 15 and in Fig. 8, the same parts are represented by the same reference numbers. In Fig. 15, 612 is a controller, 613 is a memory (MEM), 621 and 622 are ringing tone signal resources, 623 is a register key, 624 is a calling party registered identifying information registering part (REG), 625 is a ringing tone signal switch control part (RSW), 627 is a ringing tone signal switching part, and 608 is a speaker.
0084An extension terminal 132b receives from the network switch 71 calling party identifying information for identifying a calling party when a call connection is set up. The calling party identifying information is for example the calling party address #B and the calling party subaddress #② in the call setup message (ii) shown in Fig. 6.
0085The calling party registered identifying information registering part (REG) 624 previously stores calling party registered identifying information by a predetermined registering operation carried out by a user of the extension terminal 132b. The calling party registered identifying information is for example the line accessing number α for identifying the communication line 61 shown in Fig. 6.
0086The controller 612 compares the calling party identifying information with the calling party registered identifying information. Depending on whether or not the calling party registered identifying information is detected in the calling party identifying information, a call indicating sound for informing the user of the fact of the incoming call is changed.
0087According to the still another embodiment, both the incoming indicating sound is generated and the calling party information is displayed.
0088In more detail, the calling signal sources 621 and 622 generate specific calling signals R1 and R2 having different frequencies or different intermittent frequencies. The calling signal R1 or R2 is supplied to the speaker 608 so that the user can hear a different call indicating sound.
0089When the user wants to identify whether the incoming call is from another extension terminal accommodated to the PBX system or from the communication line connected to the ISDN public network (CO) 101, the user may operate the registering key 623 and can input from the key board 815 the calling party registered identifying information α for example "0".
0090The controller (CTL) 612, after detecting the operation of the registering key 623, drives the calling party registered identifying information registering part (REG) 624. The driven part (REG) 624 stores the calling party registered identifying information α from the keyboard 815 into a registering area 626 in the memory (MEM) 613, as well as displaying it on the display unit (DSP) 610 so that the user can recognize that the calling party registered identifying information is α.
0091In such a situation, when the received calling party identifying information includes the number α in a predetermined position, the calling signal R1 is sent to the speaker 608. Whereas, if the received calling party identifying information does not include the number α in a predetermined position, the calling signal R2 is sent to the speaker 608.
0092From the foregoing description, it will be apparent, according to the present invention, when a connection is set up from an ISDN public network to an extension terminal accommodated by a PBX system, since a line accessing number α for identifying a communication line connected between the PBX switching network and the ISDN public network is added to a calling party address to be received by the extension terminal accommodated to the PBX system, the user at the extension terminal can recognize whether an incoming call is from the ISDN public network or from another extension terminal so that the service for the user is improved.
0093Further, by forming a callback setup message in which the calling party address and the calling party subaddress received by the extension terminal accommodated by the PBX system are inserted as a destination address and a destination subaddress, and by sending the call back setup message from the external terminal to the PBX switching network, the user at the extension terminal can call back the original calling party terminal regardless of whether the calling party terminal is connected to the ISDN public network or the calling party terminal is another extension terminal accommodated to the PBX system. Therefore, even in the connecting system between the ISDN public network and the PBX system, a call back operation is possible so that the service is also improved from this point.
0094Still further, by previously registering desired calling party registered identifying information for identifying a calling party which the user wants to distinguish, the user can distinguish the desired calling party before responding to an incoming call by hearing the incoming call ringing sound. Accordingly, the extension terminal becomes very convenient.
Contents4
14 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14
Every citation, both ways
| Reference | Relation |
|---|---|
| HITACHI REVIEW. vol. 37, no. 1, February 1988, TOKYO JP pages 31 - 36; M. GILSTRAP ET AL: 'A Terminal Family for the Hitachi HCX5000 PBX' | Non-patent |
| PROCEEDINGS OF THE SIXTH INTERNATIONAL CONFERENCE ON COMPUTER COMMUNICATIONS, 7-10 SEPTEMBER 1982, PAGES 345-350, LONDON GB S. YOSIDA ET AL: 'A Modular Integrated EPABX for the Office of the Future' | Non-patent |
| PROCEEDINGS, INTERNATIONAL SWITCHING SYMPOSIUM, 15-20 MARCH 1987, VOL. 4 PAGES 899-906, PHOENIX US J.A. NEWALL AL: 'The Role of Customer Premises Equipment in ISDN' | Non-patent |
| CONFERENCE ON COMMUNICATIONS EQUIPMENT AND SYSTEMS, 20-22 APRIL 1982, PAGES 8- 13, LONDON GB G.P. OLIVER: 'The Integrated Services Digital Network' | Non-patent |
12 members in 6 offices; this record represents the family
Priority claims8
| Document | Office | Kind | Date |
|---|---|---|---|
| 11169888 | Japan | A | |
| 11169888 | Japan | – | |
| 22790488 | Japan | A | |
| 22790488 | Japan | – | |
| JP19880111698 | – | – | – |
| JP19880227904 | – | – | – |
| 11169888 | – | – | – |
| 22790488 | – | – | – |
Members12
| Document | Office | Kind | |
|---|---|---|---|
| EP0341687A2 | European Patent Office (EPO) | A2 | |
| JPH01284060A | Japan | A | |
| AU3400489A | Australia | A | |
| JPH0276357A | Japan | A | |
| US5008884A | United States of America | A | |
| AU612026B2 | Australia | B2 | |
| EP0341687A3 | European Patent Office (EPO) | A3 | |
| CA1320555C | Canada | C | |
| JPH0654929B2 | Japan | B2 | |
| EP0341687B1This record | European Patent Office (EPO) | B1 | |
| DE68927507D1 | Germany | D1 | |
| DE68927507T2 | Germany | T2 |
23 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | |
| No opposition filedOpposition26N | 26N | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | |
| Fr: translation filedET | ET | |
| Corresponds to:REF | REF | |
| Designated contracting statesAK | AK | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOS IGRAGRAH | GRAH | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOS IGRAGRAH | GRAH | |
| Despatch of communication of intention to grantORIGINAL CODE: EPIDOS AGRAGRAG | GRAG | |
| First examination report despatched17Q | 17Q | |
| Request for examination filed17P | 17P | |
| Designated contracting statesAK | AK | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | |
| Designated contracting statesAK | AK | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI |
Numbers
- Publication
- 0341687
- Publication, DOCDB
- 0341687
- Publication, EPODOC
- EP0341687
- Application
- 89108387
- Application, DOCDB
- 89108387
- Application, EPODOC
- EP19890108387
Titles3
- German
- Nebenstellenanlagesystem
- English
- Private automatic branch exchange system
- French
- Système à central téléphonique privé
Classification
- CPC, 2
- H04Q11/0428
- H04M3/533
- IPC, 2
- H04M3 533
- H04Q11 04
Designated states3
- Contracting states, 3
- Germany
- France
- United Kingdom
