PROCEDURE AND SYSTEM FOR ENSURING EMERGENCY COMMUNICATION

Abstract: The present invention relates to data communication networks. In particular, the present invention relates to a procedure and a system for ensuring successful emergency communication in a data communication network in which the terminal devices (4a, 4c) are connected to the local exchange via an access node (3) consistent with the V5 standard. In the procedure of the invention, in the event of a failure of the V5 interface used by a subscriber, the subscriber's emergency traffic is directed to emergency lines created locally in the access node. The emergency line is optionally connected to a specified location, such as the teleoperator's customer service.

Description: PROCEDURE AND SYSTEM FOR ENSURING EMERGENCY COMMUNICATION The present invention relates to data commu¬ nication networks. In particular, the present inven- tion relates to a procedure as defined in the preamble of claim 1 and to a system as defined in the preamble of claim 9 for ensuring emergency communication in an access node connected to a data communication network and having a number of subscriber lines or subscribers connected to it for the connection of terminal equip¬ ment to the data communication network. Furthermore, the present invention relates to a procedure for the testing of the emergency communication feature, as de¬ fined in the preamble of claim 7. There are at least two commonly known methods for connecting subscribers to an exchange in a data communication network. In the first method, the sub¬ scriber is connected via a subscriber line directly to the exchange or to an access module connected to it. In the second method, the subscriber is connected to an access network, whose access node is connected to the exchange. Open interfaces (V5.1 and V5.2) between an access network and a local exchange are defined in the ETSI (European Telecommunications and Standards Institute) standards of the ETS 300 324 and ETS 300 347 series. V5 interfaces enable subscribers belonging to a physically separate access network to be con¬ nected to a telephone exchange using a standard inter¬ face. A dynamic concentrator interface V5.2, consis- tent with the standards ETS 300 347-1 and 347-2, con¬ sists of one or more (1 - 16) PCM (Pulse Code Modula¬ tion) cables. One PCM cable comprises 32 channels, each of which with a transfer speed of 64 kbit/s, i.e. 2048 kbit/s in all. The V5.2 interface supports ana- logue telephones as used in the public telephone net¬ work, digital, such as ISDN (Integrated Services Digi- tal Network) basic and system connections as well as other analogue or digital terminal equipment based on semi-fixed connections. A static multiplexer interface V5.1, consis- tent with the standards ETS 300 324-1 and 324-2, con¬ sists of one PCM cable with a transfer speed of 2048 kbit/s. The V5.1 interface supports the same sub¬ scriber types as the V5.2 interface, except for the ISDN system connection. The terminal equipment can be connected to the access ports of the access node. One or more V5 interfaces can be connected to an access node. The ac¬ cess ports are created in the V5 interface by linking an unambiguous address of each port with a given ad- dress of the V5 interface. In the local exchange, this address is created as a V5 subscriber. In other words, each access port has an address which is linked with a V5 address and uses a given time slot or given time slots for signalling to the local exchange. The purpose of a system for ensuring emer¬ gency communication is to make sure that calls to emergency numbers of subscribers connected to an ac¬ cess node can be set up even when the V5 interface be¬ tween the access node and the exchange is out of or- der. The V5.1 and V5.2 standards contain no definition of systems for ensuring emergency communication in case of failure. In this situation, the problem is that, at present, all communication, including emer¬ gency communication, via a specific V5 interface of a given subscriber is hindered when the V5 interface fails. One possibility for ensuring emergency commu¬ nication in case of failure of a V5 interface assigned to a subscriber is to create in the telephone exchange to which the V5 interface is connected a separate emergency address for each subscriber for communica¬ tion during the failure situation. However, the prob- 49231 PC17FI97/00393 lem with this system is the high capacity required in the exchange, because in this case the exchange must have a double subscriber address range as compared with the number of subscribers. In addition, such an arrangement would significantly increase the size of the interface database of the access node. The object of the present invention is to eliminate the problems described above. A specific ob¬ ject of the invention is to present an effective pro- cedure for ensuring emergency communication in an ac¬ cess node in the event of a failure of the V5 inter¬ face used by a subscriber. A further object of the present invention is to present a feature currently missing in the access node that makes it possible to ensure subscribers' emergency communication as long as the access node is in operation. As for the features characteristic of the in¬ vention, reference is made to the claims. In the procedure of the present invention for ensuring emergency communication in a data communica¬ tion network comprising a number of telephone ex¬ changes interconnected via trunk cables and an access node connected to at least one of the exchanges, a number of terminal devices used by subscribers to set up connections over the data communication network are connected to the access node, preferably via sub¬ scriber cables. Further, in the procedure of the in¬ vention, signalling consistent with the V5 standard, which is defined in the standards mentioned above, is used in the connection between the access node and the telephone exchange, which is a standard V5 interface. In the procedure of the invention, an emer¬ gency line is created in the access node by using lo¬ cal operation control commands. The emergency line is generally created in conjunction with the installation and start-up of the access node. In this application, 'emergency line' means an access node subscriber line to which emergency communication is directed when the link between the access node and the local exchange is broken. Emergency communication is preferably con¬ trolled by using the internal group switch of the ac- cess node. Further, at least one emergency number is created for the emergency line of the access node by using local access node commands. In the event of a failure of the V5 interface used by a terminal device, a call from the terminal device to an emergency number is connected locally by means of the internal group switch of the access node. In the access node, the control of emergency lines and numbers in a failure situation is effected using MML (Man Machine Language) commands. As compared with prior art, the present in¬ vention has the advantage that, using the procedure of the invention, emergency communication of subscribers connected to an access node can be effectively and re¬ liably guaranteed even in the event of a failure of the V5 interface used by the subscriber. In a preferred embodiment of the present in¬ vention, when a new connection is being set up, the status of the V5 interface used by the subscriber is monitored in the access node, and if, based on this monitoring, the V5 interface is found to be out of or¬ der, a predetermined connection setup mode is entered in which the connection is set up locally in the ac¬ cess node. In a preferred case, at the monitoring stage, the status of the V5 interface used by the sub- scriber, i.e. information as to whether the interface is in working order or not, is read from a file used to store status data relating to each V5 interface, i.e. data indicating failure and restoration of the control channel of the V5 interface. A failure situa- tion in a V5 interface occurs when the signalling con¬ nection from the subscriber to the local exchange fails. In a preferred embodiment, the emergency line is connected via a permanent link to a location prede¬ termined by the teleoperator, such as an exchange room, the teleoperator's customer service or the like. In addition, a permanent link can be provided from the emergency line to a mobile telephone, a pager or equivalent. When the teleoperator receives via a data network supervision system or equivalent a message about malfunction of one or more V5 interfaces in an access node, service can be provided via the emergency line connected to the exchange room. In practice, this means that a terminal device connected to the emer¬ gency line is attended by a human operator, and calls made to emergency numbers by subscribers connected to the cranky V5 interface will produce a ring in this terminal device and the subscribers can communicate their emergency message via this line. If the call to the emergency number fails to be set up, the sub¬ scriber is given a corresponding notice, a sound sig- nal or the like, informing the subscriber about the problem in telephone traffic. The invention also relates to a procedure for testing the operation of emergency lines and/or emer¬ gency numbers created in an access node. The testing procedure is used to ensure that emergency communica¬ tion via the access node really works. In the testing procedure of the invention, at least two emergency lines are provided in the access node, so that a con¬ nection to an emergency number can be set up from one of the emergency lines. The signalling programmes automatically perform a check to see whether the V5 access port calling an emergency number has a V5 ad¬ dress and whether the calling line has been created as an emergency line for failure situations. If it is es- tablished in the access node that the call setup mes¬ sage to an emergency number comes from an emergency line of the access node, then the access node will work in a manner corresponding to operation in a fail¬ ure situation and the call is connected to the dialled emergency number. Further, if the connection setup to the emergency line is successful, this is an indica- tion that the emergency communication feature is op¬ erational. Further, a connection can be set up from the emergency lines in both directions, in other words, first from the first emergency line to the sec¬ ond one and then from the second emergency line to the first one, thus making sure that both emergency lines are in working order. A further advantage of the checking procedure is that the emergency lines can be tested without interrupting normal telephone traffic through the access node. Further, in the system of the invention for ensuring emergency communication in a data network comprising a number of telephone exchanges intercon¬ nected via trunk cables and an access node which is connected to at least one of the exchanges and to which are connected a number of terminal devices used by subscribers to set up connections over the data communication network, signalling according to the V5 standard is used in the connection between the access node and the telephone exchange, which is a V5 inter- face consistent with the V5 standard. According to the invention, the access node comprises an emergency line created using the local operation control commands of the access node and an emergency number created using the local operation control commands of the access node, and calls to the emergency number are connected to the emergency line. Moreover, the access node of the invention comprises means, preferably an internal group switch within the access node, which group switch is preferably a fully digital, full-scale sin- gle-phase time-shared switch without rejection, by which calls made by subscribers to emergency numbers are directed to the emergency line when the V5 inter- face used by the subscriber is out of order. In the following, the invention is described by the aid of a few examples of its embodiments by re¬ ferring to the attached drawing, in which Fig. 1 presents a prior-art signalling ar¬ rangement for a normal call over a V5 interface; Fig. 2 presents a system according to the present invention; and Fig. 3 represets a signalling arrangement in an access node for a call to an emergency number ac¬ cording to the present invention. Fig. 1 presents an example of the signalling in the case of a prior-art ISDN call over a V5 inter¬ face. When the subscriber picks up the headphone (step 1) , LAPD signalling (data link layer protocol in ISDN channel D) is started. The access node (AN) 3 acti¬ vates the terminal device (step 2) and sends a message indicating activation of the terminal device to the telephone exchange (LE) 1 (step 3) , using the control protocol. Once activated, the terminal device 4c sends a SETUP message over channel D of the subscriber ca¬ ble. On receiving the SETUP message, the access node identifies (step 5) the corresponding V5 interface and the V5 subscriber address of the subscriber cable (which in fact is a third-layer address, L3 address, consistent with the OSI architecture (Open Systems In¬ terconnection) ) on the basis of the subscriber cable. Moreover, the access node adds a V5 header to the SETUP message and sends it via the Ds channel of the corresponding V5 interface to the telephone exchange 1. The LAPD signalling itself is passed as such over the V5 interface via the signalling channel reserved for the subscriber. Thus, the V5 interface software in the access node 3 does not interfere with the contents of messages in any way. In the telephone exchange 1, the V5 header is removed (step 6) and the SETUP mes¬ sage is transmitted further to an ISDN call setup con- trol stage, where it is terminated. Based on the first SETUP message, the local exchange selects the V5 time slot to be used, and this information is given to the access node 3 together with the L3 address (step 7). The access node 3 identifies the subscriber cable on the basis of the L3 address received and, via its lo¬ cal group switch, connects (step 8) the B channel of the subscriber cable to the V5 interface time slot re¬ served for it. Further, the access node 3 sends (step 9) to the telephone exchange 1 a message confirming completion of the connection. The telephone exchange 1 sends the standard ISDN call control messages relating to call setup to the terminal device via the access node over the Ds channel reserved for the subscriber cable (step 10) . The system presented in Fig. 2 comprises an access node 3 with a number of subscribers 4a, 4c con¬ nected to it. The access node 3 operates between an exchange 1 and the subscribers 4a, 4c and connects subscribers to a telephone exchange in a data communi¬ cation network in the manner illustrated by Fig. 1. The access node 3 is connected via a V5.2 interface 5, which comprises 1 - 16 PCM cables (2 Mbit/s), to the exchange terminal (ET) 10 of the terminal exchange 1, which is provided with the functions required by the V5 interface. The access node can also be connected to the telephone exchange 1 via a V5.1 interface. To en¬ sure successful emergency communication, the access node comprises at least one emergency line 6 created for emergency communication and connected to a speci¬ fied terminal device via a connection preferably car¬ ried out by an operator. A number of emergency numbers are created in the access node 3. For each emergency number, preferably one or more emergency lines are created. Due to the requirements pertaining to the ac¬ cess node, generally no other numbers except emergency numbers are created in it. In the access node 3, one emergency number at a time can be created, and for each emergency line 6, one to six emergency numbers can be created. When the emergency lines are being created, the lines are given with a logical location number so that the command gives the access module number only once, because the series attribute of the emergency numbers in a pre¬ ferred embodiment is limited to one access module. From the series attribute being limited to one access module it also automatically follows that all emer¬ gency lines under a given emergency number must be in¬ cluded in the same access module. In an embodiment, it is possible to create a maximum of 20 emergency num¬ bers for one emergency line, yet the total number of emergency numbers is preferably not more than 20. Moreover, the maximum length of an emergency number is 12 digits. Further, an emergency number cannot be cre¬ ated as a normal subscriber line, and on the other hand a normal subscriber cannot be assigned a line created as an emergency line. In a preferred embodiment of the present in¬ vention, the maximum number of emergency calls that can be active at the same time is 4, which depends on the number of emergency lines. In a further embodi- ment, the push-button dialling receiver of the access node limits the number of analogue emergency calls at the setup stage to 64. It must be noted, however, that if the subscriber uses pulse dialling, the push-button dialling receiver is released immediately at the be- ginning of the dialling, permitting a larger number of emergency calls at the setup stage. In the case of digital emergency calls, no push-button dialling re¬ ceiver is needed. Next, referring to Fig. 3, the call setup procedure in the case of an ISDN call to an emergency number according to a preferred embodiment of the in¬ vention will be described. The programme modules pre- sented in the signal chart 3 are used as follows. MB1PRB is a program used for the transmission of LAPD frames, which maintains specific information about the routing direction of signalling in each port and per- forms the connection of time slots in the access mod¬ ule. PRLPGM is an ISDN 2 nd -layer programme for access node failure situations, which monitors the condition of the Ds channel of the V5 interface and reports changes in the status of the interface. IS3PRS is an ISDN 2 n -layer programme for access node failure situa¬ tions, which allocates a module cable for an ISDN sub¬ scriber. CDNPRB takes care of actual call setup in emergency communication, connection and disconnection of the speech path, connection of messages and reser- vation and release of push-button dialling receivers. SWICOP is a programme controlling the local group switch 7 of the access node. ZASPRB takes care of ana¬ logue subscriber signalling. An outgoing ISDN (2B+D) emergency call in the event of a failure of the V5 in- terface used by the subscriber is as follows. When the subscriber picks up the headphone to call an emergency number, LAPD signalling (data link layer communication protocol in ISDN channel D) is started by the MP1PRB module. IS3PRB acknowledges the activation request. Next, 2-layer connection consistent with the OSI model is set up by means of the PRLPGM and IS3PRB modules. Call setup is now started, and at this point the pro¬ cedure differs from normal ISDN call setup; as there is no connection to the local exchange, no V5 inter- face header is included in the message. Further, mod¬ ule IS3PRB checks that the required parameters are in order. When the subscriber dials a number, it is ana¬ lyzed by the appropriate programme to establish whether the subscriber is calling an emergency number existing in the access node concerned. If the call is found to be addressed to such an emergency number, then the call setup procedure is continued and the subscriber is given the necessary sound signals to in¬ dicate that the system is trying to set up a connec¬ tion to the emergency number. When the emergency num¬ ber responds, i.e. when the called subscriber picks up the headphone or performs some other action to answer the calling subscriber's call attempt, a talking con¬ nection is set up. A call setup process as described above can also be carried out from an emergency line created in the access node by making a call from it to an emer¬ gency number. This makes it possible to test the emer¬ gency lines to make sure that the emergency lines and the access node control system for calls to local emergency numbers are in working order. Let it be further noted that, in call setup in a failure situation, the emergency line busy test, number analysis and call termination can be carried out in the access node in many known ways, as can the call setup process described above. It should be fur- ther noted that the example described above can also be applied to environments other than ISDN, e.g. an analogue environment. The invention is not restricted to the exam¬ ples of its embodiments described above, but many variations are possible within the framework of the inventive idea defined by the claims.

Claims: CLAIMS 1. Procedure for ensuring emergency communi¬ cation in a data communication network comprising com¬ prising a number of telephone exchanges interconnected via trunk cables and an access node connected to at least one of the exchanges, to which access node are connected a number of terminal devices used by sub¬ scribers to set up connections over the data communi¬ cation network, in which procedure signalling accord- ing to the V5 standard is used in the connection be¬ tween the access node and the telephone exchange, which connection is an access node V5 interface con¬ sistent with the V5 standard, c h a r a c t e r i z e d in that, in the event of a failure of the V5 interface used by a terminal device, a call from the terminal device to an emergency number is connected locally to an emergency line created beforehand in the access node. 2. Procedure as defined in claim 1, c h a r - a c t e r i z e d in that when a new connection is being set up, the status of the V5 interface used by the terminal device is monitored in the access node; and if, based on this monitoring, the V5 inter- face is found to be out of order, a predetermined con¬ nection setup mode is entered in which the connection is set up locally in the access node. 3. Procedure as defined in claim 1 or 2, c h a r a c t e r i z e d in that data relating to the status of each V5 interface, i.e. data indicating failure and restoration of the control channel of each V5 interface, is stored in a specific file in the ac¬ cess node. 4. Procedure as defined in any one of the preceding claims 1 - 3, c h a r a c t e r i z e d in that the status data stored in a specific file for each V5 interface is utilized when a new connection is being set up. 5. Procedure as defined in any one of the preceding claims 1 - 4, c h a r a c t e r i z e d in that the emergency line is connected via a permanent link to a location predetermined by the teleoperator, such as an exchange room, the teleoperator's customer serv¬ ice or the like. 6. Procedure as defined in any one of claims 1 - 5, c h a r a c t e r i z e d in that, if the connec¬ tion fails to be set up, the subscriber is given a corresponding notice, a sound signal or the like. 7. Procedure for testing the operation of a procedure as defined in any one of the preceding claims, c h a r a c t e r i z e d in that from one of two emergency lines created in advance, a connection is set up to an emergency number and the signalling programmes of the access node auto¬ matically perform a check to see whether the V5 access port in question has a V5 address; a check is made to establish whether the calling line has been created as an emergency line for failure situations; if a connection to the emergency line is suc- cessfully set up, this is an indication that the emer¬ gency lines are operational. 8. Procedure as defined in claim 7, c h a r ¬ a c t e r i z e d in that a connection is be set up from the emergency lines in both directions, i.e. from the first emergency line to the second one and from the second emergency line to the first one. 9. System for ensuring emergency communica¬ tion in a data network comprising a number of tele¬ phone exchanges (1, la) interconnected via trunk ca- bles (2) and an access node (3) which is connected to at least one of the exchanges and to which are con¬ nected a number of terminal devices (4a, 4b, 4c) used by subscribers to set up connections over the data communication network, in which system signalling ac¬ cording to the V5 standard is used in the connection between the access node and the telephone exchange, which connection is an access node V5 interface (5) consistent with the V5 standard, c h a r a c t e r ¬ i z e d in that the access node comprises an emergency line (6) created using the local operation control commands of the access node; an emergency number created using the local operation control commands of the access node, and calls to the emergency number are connected to the emergency line; and means (7) by which calls made by subscribers to emergency numbers are directed to the emergency line when the V5 interface used by the subscriber is out of order. 10. System as defined in claim 9, c h a r ¬ a c t e r i z e d in that the system comprises means (8) connected to the emergency line for setting up a con¬ nection to a specified terminal device (4b) via the emergency line.

Inventors: YRJAENAE MARTTI, YRJAENAE, MARTTI
Applicants: NOKIA TELECOMMUNICATIONS OY, YRJAENAE MARTTI, YRJAENAE, MARTTI
Application year: 1997
Main classification: H04M11
IPC codes: H04L12, H04M3, H04M11