ITGE20110061A1 - SECURITY SYSTEM FOR TUNNELS - Google Patents

Description

DESCRIPTION of the Industrial Invention entitled: Safety system for tunnels

TEXT OF THE DESCRIPTION

The invention relates to a safety system for tunnels, in particular for railway networks or the like, which system comprises an emergency communication subsystem, said emergency communication subsystem comprises a local network installed in the tunnel, which network is provided with a certain number of nodes, each of which is physically placed in a niche of a plurality of niches provided in the tunnel, each node being connected to a VOIP-type emergency communication device, so-called Help Point, and said local network tunnel having at least one connection interface to at least one server for emergency telephony and public address, or public address, and at least one connection interface to at least one operator console, said emergency communication device allows the transmission and receiving acoustic messages through said network to and from said emergency telephony server and the sound system and / or said at least one operator console, each emergency communication device having an identification code of the device and an IP address, and each niche having an identification number relating to the position of said niche in the gallery and related to the other niches provided in said tunnel.

The emergency communication devices, which in the following description are more generically called Help Points, are part of the emergency communication subsystem associated with tunnels, in particular in the railway field. Their functions are as follows:

allow anyone inside the tunnel to make a call to an operational control center to request assistance in the event of danger or accident, said operational control center being an operational office usually located in the main station of the line and connected to various tunnels of the line, which manages the first phase of emergencies, as well as operational offices located in the triage area, intended to manage emergencies for a single tunnel, locally; allow the rescue personnel to make a hands-free call to a given niche in the tunnel;

allow the operator who is in said operating centers to make public announcements, to give instructions or information to those who are in the gallery;

allow the operator who is in said operating centers the possibility of listening to the environment, in order to hear what is happening inside the tunnel.

The Help Point is usually installed inside the tunnel, or externally, near its entrance, and is therefore made in such a way as to be able to operate in severe environmental conditions.

It must also be made in compliance with all applicable standards, in order to guarantee the safety of the user and maintenance personnel (electrical insulation, fireproof materials).

Although the Help Point is not normally considered an essential subsystem for security, it nevertheless requires high availability.

To guarantee the functions of the aforementioned Help Points once these Help Points have been physically installed in the tunnel and connected to the local network of the tunnel, the individual Help Points must be initialized to properly set the IP addresses and the configuration of the IP parameters and to assign to each niche a specific Help Point device with a specific IP address and a specific IP configuration.

In this way, when a Help Point is activated, information is also given regarding the point in which said device is inside the tunnel, which allows specific operations to be carried out, such as the emission of driving announcements from acoustic signaling devices, for example in time sequence, to indicate the correct exit path from the tunnel or other special functions depending on the position of a specific Help Point within the tunnel.

The purpose of the present invention is to provide a safety system for tunnels of the aforesaid type in which the installation procedures can be improved and made less expensive in terms of time and costs, and safer for the assistance personnel.

A further object of the present invention is to provide a safety system for tunnels with a higher level of reliability and availability than currently known systems.

The invention achieves the aforementioned purposes thanks to a safety system for tunnels, in particular for railway networks or the like, which system comprises an emergency communication subsystem, said emergency communication subsystem comprises a local network installed in the tunnel, the which network is provided with a certain number of nodes, each of which is physically placed in a niche of a plurality of niches provided in the tunnel, each node being connected to a VOIP-type emergency communication device, so-called Help Point, and said local tunnel network having at least one connection interface to at least one server for emergency telephony and public address, and at least one connection interface to at least one operator console, said emergency connection device allows transmission and reception of acoustic messages through said network to and from said server for the emergency telephony and sound diffusion and / or at least one operator console;

each emergency communication device having a device identification code and an IP address, and each niche having an identification number relating to the position of said niche in the tunnel and related to the other niches provided in said tunnel;

and in which means are provided for automatic initialisation of each of the emergency communication devices, relative at least to the univocal association of the device identification code, the IP address and the niche identification code of the niche in which the device is installed.

According to a particular embodiment, said means are in the form of a so-called DHCP server, and of an initialization manager which reads the ID code of the device and the ID code of the niche.

The Niche ID Code and Device ID Code can be set prior to physically installing the emergency communication device in a given Niche.

As a further improvement, each niche can be identified with the ID code of the physical node for connection to the local network of the tunnel, at least one node being provided in each of said niches of the tunnel.

According to an executive variant, the identification code of the niche is provided in a system configuration plan or table saved as a system configuration file in a memory of the emergency communication devices or of an initialization / configuration server, together with a program system initialisation performed by the emergency communication devices or by the initialisation / configuration server once the emergency communication devices are installed and operationally connected to the tunnel LAN.

The niche identification code can also be saved in a niche identification label physically placed in a corresponding niche, since said label can be read by means provided on the emergency communication devices able to read the niche identification number of the niche in which said niche is installed. emergency communication device, and to use this information for 1 <1> initialization / system configuration.

According to a specific form of reflection, the tag is an RFID tag, the emergency communication devices being provided with means for reading / writing data from / into the memory of the RFID tag.

A further way to initialize the emergency devices can consist in the insertion of the ID code of the niche by the assistance personnel who provide for the physical installation of the emergency communication devices, using the input means provided on the emergency communication devices .

One type of input means can be constituted by a numeric or alphanumeric keypad provided at each emergency communication device, or a microphone adapted to receive coded acoustic signals, such as DTMF coded signals for the transmission of the ID codes of the niches through the device emergency communication.

The different embodiments described above can also be provided in combination with each other, so as to provide a method of verifying the correctness of the information retrieved or used.

According to a particular embodiment, each emergency communication device is connected to the local network of the tunnel through a switch, each switch (106) is provided in correspondence with a niche and is provided with an IP address and at least one port to which it is connected said emergency communication device;

Each emergency communication device comprises at least one VOIP communication module operating according to a so-called Session Initialization Protocol (SIP), at least one so-called SIP server being provided in the network;

Said at least one VOIP module being made up of DHCP Clients that request configuration information relating to the IP configuration, the SIP ID, the SIP Server and finally, if applicable, an NTP server and an SNMP server;

being connected to the network a DHCP server, which server automatically generates for each emergency communication device connected to the local LAN of the tunnel, the corresponding ID code and / or the IP address and the IP configuration information required by the network protocol, said IP addresses and said IP configuration information being generated starting from basic information relating to the tunnel number, the niche number, the switch address and the switch ports to which the VOIP module is connected and to which it is addressed the SIP server.

Further details regarding the system and network structure and the self-configuration phases will be reported in the following detailed description.

According to a further embodiment, each emergency configuration device comprises a control unit which executes a control logic program and which control unit is connected to a switch port and requests configuration information relating to the IP configuration, to the NTP server and the SNMP server, said information being also automatically obtained from a DHCP server starting from the IP address of the switch or from the ID code of the emergency communication device.

With the above described generic combination of features and individual improvements or variants, a completely automatic initialization and configuration of said emergency communication devices, i.e. of said Help Points, is made possible without the need for the intervention of a assistance operator who initiates initialization by physically accessing each of the Help Points installed in a gallery.

The process is extremely accurate and error free, and can be done extremely quickly. Furthermore, in the event of an update of the tunnel emergency system, by adding, replacing or eliminating some of the emergency communication devices, this update is carried out in an extremely simple, quick and safe way, in particular for the service personnel, who are not required to stay in the tunnel niche any longer than is necessary for the physical installation of each device, which reduces the risk of accidents.

According to a further object of the emergency system for tunnels according to the present invention, said emergency system is equipped with one or more of said emergency devices, each of which has means for guaranteeing operation even in the event of a breakdown. This happens thanks to a 2oo2 configuration, in particular of the power supply and / or of the audio amplifier for the diffusion of sound messages.

A further improvement provides for a double network in the tunnel, while at least part of the emergency communication devices provided in the tunnel are connected to a network, the remaining part of said emergency communication devices provided in the tunnel being connected to the second network;

Both networks being connected to the same servers that manage communications within the tunnel.

Further improvements of the present invention are disclosed in the dependent claims.

The characteristics of the present invention and the advantages deriving from it will be described in greater detail in the following description of an embodiment of an emergency system for tunnels according to the present invention.

Figure 1 illustrates a schematic view of a tunnel safety system according to the present invention.

Figure 2 illustrates a schematic block diagram of an emergency communication device, so-called Help Point.

Figure 3A illustrates the emergency communication system according to Fig. 2 inserted in a cabinet in the form of a column.

Figure 3B illustrates the human-machine interfaces from outside the front side of the cabinet shown in Figure 3A.

Figure 4 illustrates a block diagram of the telecommunication subsystem of an emergency communication device according to Figures 2 and 3.

Figures 5 to 7 illustrate block diagrams of three respective different power supply subsystems.

Figures 8 to 10 show block diagrams of further details of the power supply subsystems.

Figure 11 illustrates the block diagram of a switch provided in the emergency communication device.

Figures 12 and 13 show respectively the VOIP module for emergency calls, so-called SOS module and the VOIP module for generic announcements, so-called PA module, both provided in the emergency communication device.

Fig. 14 illustrates the control unit provided in the emergency communication device.

Fig. 15 illustrates the switch provided in the emergency communication device.

Fig. 16 illustrates a schematic view of the combination of devices which allows the self-configuration of some parameters of the safety system for tunnels.

Fig. 17 illustrates the structure of the IP address of the emergency communication devices provided in the tunnel.

Figure 18 illustrates an example of automatic IP configuration of Help Points.

Figure 19 is a schematic view of a tunnel comprising a safety system for tunnels according to the invention, in particular with a vehicle for the automatic assignment of the niche ID to the Help Points installed in said niche.

According to the above description, as is also evident from the figures, in particular from figure 1, the safety system for tunnels according to the present invention comprises a certain number of emergency communication devices, connected via network to server units which allow sending messages to each of said emergency communication devices and receiving messages from said emergency communication devices, as well as enabling communication between two or more of said emergency communication devices.

The network is a typical Ethernet Lan network and the emergency communication devices are configured as Clients, while the exchange of sound messages takes place using so-called VOIP protocols.

Each emergency communication device is installed in a niche inside the tunnel. Each gallery niche or part of the gallery niches are provided with an emergency communication device. Each tunnel niche constitutes a node of the network to which the emergency communication device is connected.

Each node and each niche have identification codes different from those of the other niches or niches which also define the position of the node and of the niche inside the tunnel with respect to the other niches or niches.

According to the present invention, automatic initialisation means are provided for each of the emergency communication devices, relative at least to the univocal association of the device identification code, the IP address and the niche identification code of the niche in which the device is installed.

Various embodiments are possible.

According to a first embodiment, each emergency communication device can be provided with a memory in which the identification code of the device and the IP address of said device are stored.

emergency communication, as well as the identification code of the niche in which said emergency communication device is intended to be installed.

A server connected to the local network of the tunnel, to which the emergency communication devices are also connected, reads the information stored in each emergency communication device and correctly carries out the initialization and configuration of each emergency communication device according to the parameters required by the network communication protocols.

The term server must be understood as a software run by one or more electronic devices. The hardware device can be concentrated in a single computer or distributed over several hardware units, each of which runs a certain program to conduct part of the server's functions.

According to an alternative, it is possible to provide a single centralized server with a configuration file saved in a memory, in which file the identification number, the niche number, the IP address and the other configuration parameters relating to each of the emergency communication devices and the niche in which said emergency communication devices are intended to be installed. The aforementioned information is used by a server running an automatic initialisation program when one or more of the emergency communication devices are physically installed in the associated niche and physically connected to the local network of the tunnel.

In order to enhance security, in combination with said file saved in a memory of the initialisation server, each emergency communication device can be provided with a memory in which its identification code and / or IP address are stored. said device, and the initialization server queries each emergency device connected to the network before initialization to identify the emergency communication devices present and then check the correspondence of the devices installed with those listed in the initialization file.

Still, according to a further executive variant, in order to initialize the network, in particular to correctly assign each communication device to a certain niche in which it is installed by associating each ID code or IP address of each emergency device to the ID code of the niche in a certain gallery in which said emergency communication devices are installed, during the installation of the device, an identification label of the niche can be placed in the niche, independently of the emergency communication device. This label is in the form of a readable data carrier device, which can be interrogated by the emergency communication device and, once interrogated, sends an ID code saved in a memory of the label to said emergency communication device, which in turn, it sends the information of the ID code of the niche received from the label, together with the ID code of the device and / or the IP address of the device.

The aforementioned label can be of any type and in particular it can be of the so-called RFID type.

This execution variant can be provided in combination with the first or second embodiment and be adopted as a cross-check for the data stored in the emergency communication devices and / or in the initialization file of the initialization server, in order to be able to check that the assignment of a certain ID code of a certain niche to a certain emergency communication device having a certain ID code and / or IP address in the memory of the emergency communication device or in the initialization file corresponds to the actual installation conditions , in particular that each emergency communication device with a certain ID code and / or a certain IP address is actually installed in the niche having the ID code indicated by the information saved in the emergency communication device and / or in the initialization file.

Still, as a further variant, the initialisation means are means which are transported by an assistance operator or a vehicle from one niche to another, and which transmit the initialisation data, such as the niche identification code, to the initialisation server via the emergency communication device, by means of the data input means of the emergency communication device.

Among the aforesaid usable data input means are the so-called DTMF tone generators, through which it is possible to insert the ID code of the niche in the emergency communication device and send it to the initialisation server. In this case, a care worker walks from one niche to another with a DTMF code generator to manually enter the DTMF tones corresponding to the niche in which a given emergency communication device has been installed.

Naturally, other means may be used, for example a railway vehicle provided with data transmission means to a receiver of the emergency communication device and with means suitable for determining the niche number and for generating a niche identification code which is transmitted to the receiver of the niche. emergency communication device when the vehicle is at the niche level. The niche identification code received from the emergency communication device installed in the niche is then used as described above in combination with the other embodiments, and for example sent to the initialisation server by the emergency communication device together with the respective identification code and / or IP address.

The vehicle niche identification means can be, for example, means suitable for measuring the distance traveled by the vehicle inside the tunnel starting from a given reference point, such as the entrance to the tunnel, and in combination with a map of the gallery itself. Based on the map, the niche identification means can establish the distance of each niche from the reference point. This calculated distance value is compared with the distance traveled by the vehicle from the reference point of a given niche, so that it can be assumed that the vehicle is in correspondence with the niche when said vehicle has traveled a calculated distance and, in correspondence of said distance, the transmission of the code from the vehicle to the emergency communication device is performed.

As a further refinement, it is possible to equip the vehicle with a receiver and each emergency communication device with a transmitter for exchanging data confirming that the vehicle is in a niche, and that an installed emergency communication device is installed in said niche and is operational and has also correctly received the niche identification code.

As a further refinement, the emergency communication device can also send feedback data to the vehicle, to indicate that the niche ID code has been further transmitted and correctly received by the init server.

Many other different ways of implementing the invention can be envisaged, which also depend on the specific architecture of the tunnel safety system and of the emergency communication devices.

Although most of the various options relating to the method of carrying out the inventive teaching are evident to those skilled in the art, Figure 19 shows a schematic view of the last embodiment described, which includes the automatic assignment of the niche identification code.

Figure 19 illustrates a tunnel in which two lines are provided, each one that can be traveled by a railway vehicle 52. On board the vehicle there are means for measuring the distance traveled starting from a reference point, which in the specific example is the tunnel entrance, referring to the direction of travel of the vehicle. Therefore, three niches are illustrated for each line, respectively NI, N3, N5 and N2, N4, N6. For each niche, the distance LI, L2, L3, L4, L5, L6 from the tunnel entrance is known thanks to the gallery plan. The vehicle that measures the distance traveled from the respective tunnel entrance is therefore able to determine the position of the niche with respect to the tunnel entrance and other niches. This information is used to generate a niche identification number and transmit this niche identification number to a receiving unit 51 placed in each niche separately from the Help Point 1 or on said Help Point 1. The receiver 51 receives the data relating to the niche identification code where it is installed and forwards the data to Help Point 1 to be used further for 1 <1> initialization / automatic configuration of the system.

It is also possible to equip the means 51 with transmitting means and the vehicles 52 with receivers, for the exchange of feedback information from the Help point 1 relative to the reception of the niche identification code.

It is possible to carry out a cross-check by equipping the system Help Points 1 or other servers of the system with a map of the tunnel, in which the niche identification numbers are set in a preventive phase, which allows the comparison between the niche identification code transmitted by the vehicle. and the one defined by the project.

An example of a specific safety system for tunnels according to the present invention will be described below, with the aid of figures 1 to 18.

Figure 1 shows a schematic view of a tunnel safety system according to the present invention.

The tunnel safety system of this example includes various subsystems, including:

The lighting and power subsystem (LFM)

The emergency communication subsystem The integrated supervision subsystem (SPVI) The emergency communication system, which hereinafter is briefly referred to as "Help Point" and is indicated with 1, is located within the Emergency Communication subsystem and, more specifically, within the Emergency Telephony and Public Address 10 (EmT) subsystem. It interacts with the following non-human actors within the EMT Emergency Telephony and Public Address:

The SOS & PA 2 server (SOS Server and Public Address), installed in the Operational Control Center 200 or in an operational office 201 located in the triage area, is designed to manage emergencies for a single tunnel. Said Operational Control Center is usually located in the main station of the line and is connected to various tunnels of the line, in order to manage the first phase of emergencies;

a series of operator consoles 3 located in said Operational Control Center or in said operational office located in the triage area;

The Sounders subsystem 4, consisting mainly of a series of sounders 104 directly connected to the audio amplifiers of the Help Point;

the fiber optic cable (FOC) 5, placed along the tunnel;

The local network (LAN) of the tunnel 6.

Furthermore, each Help Point 1 interacts with the Lighting and Power Supply subsystem 8 (LFM) and with the Integrated Supervision subsystem 7 (SPV).

The Lighting and Power subsystem 8 (LFM) has three interfaces with the Help Points 1:

the electrical interface 308, designed to supply electricity to the Help Points 1;

the Ethernet interface 108, designed to allow the Lighting and Power Supply subsystem 8 (LFM) to access the tunnel network 6 through the LAN Switch of the Help Point and to send diagnostic information;

the fiber optic patch 208 (fiber optic patch, FOP), designed to allow the Lighting and Power subsystem 8 to access the fiber optic cable 5.

The tunnel Ethernet LAN 6 and the fiber optic cable LAN 5, connected to the local networks 210, 211 in the operational control centers 200 and in the operational offices located in the triage area 201 by means of network equipment 200.

The SOS & PA server 2, the operator consoles 3 and other units of the local networks in the Emergency Telephony & Public Address (Emt) subsystems in the Operational Control Center 200 and in the operational offices located in the triage area 201, also connected by means of equipment network 221.

The networks 210 and 211 of the operational control center 200 and the operational offices 201 of the triage areas are connected by long-distance communication networks, indicated in fig. 1 from 230, 231.

The networks of the operational offices of the triage areas also include interfaces with external equipment, generically indicated with 240.

Furthermore, at the operational control center 200 and the operational offices of the triage area 201, a network management system 12 is connected to the corresponding networks 210 and 211.

In the Operations Control Center 200, an additional NTP server 13 is provided, connected to network 210. This NTP server 14 (Network Time Protocol server) is the primary one. Optionally, it is possible to provide a secondary external NTP server 14 connected to the network 201 of the Operational Control Center.

From the point of view of the architectural level, illustrated in particular in Figures 1 to 4, the configuration of the Help Points 2 can be divided into four main levels:

the Telecommunications level (TLC) comprising cards and / or electrical and electronic components and operating at low voltage

the Electrical Power level: comprising the boards and / or electrical and electronic components and operating at high voltage

the level Optical distribution frame (ODF): comprising all optical components

the cabinet level: comprising the mechanical and connection layout of the Help Point cabinet.

On the basis of the aforementioned subdivision, as will become clearer in the following description, in combination with figure 3, the physical architecture of the cabinet is divided into three zones (TLC, Power supply, ODF). The TLC zone and the Power Supply zone are not separated from each other, but are separated from the ODF zone. Therefore, in the remainder of this document, the terms "level" and "zone" will be synonymous.

Figure 2 illustrates the scheme of the general architecture of the Help Points 1, with the respective levels of logical design, and all the related interfaces with other subsystems.

As shown in Figure 2, the TLC layer provides all the network and communication functions of Help Point 1 and is mainly composed of:

VoIP communication modules 101, 102 network equipment 106

network amplifiers 103, 104

a programmable logic controller 105 human-machine interfaces 107

temperature sensors 108

The Power Level provides electrical power to all equipment in the TLC level.

The ODF level provides the sectioning and joining equipment for the tunnel's fiber optic cables.

The equipment belonging to the respective TLC, Power Supply and ODF levels are respectively located within the TLC, Power Supply and ODF zones within the Help Point cabinet, with the exception of the temperature sensors, which are shared between the TLC and Power Supply zones.

The TLC level consists of the following components:

a VoIP SOS 101 module, which is a first VOIP module for emergency calls made by the Help Point with the Human-Machine Interfaces provided at the Help Point, such as a microphone or alphanumeric keyboards or other interfaces

a VoIP module PA 102, which is a second VOIP module for generic public announcements, so-called Public Address module

a Switch 106 that can be connected to the LAN of the tunnel

two audio amplifiers

the amplification of the audio signals to be broadcast through the sounders 104 of a first and second subsystem of sounders powered respectively by the first and second amplifier

a programmable logic microcontroller / zPLC 105

human-machine interfaces 107, such as

109 silkscreen signs or symbols on the Help Point cabinet

a metal key switch 110

a red plastic SOS button 111

an SOS (omnidirectional) microphone 112

a PA (directional) microphone 113

a loudspeaker 114

Red / green LED 115

Name / number plate (niche number, mileage identification number)

temperature sensors, including in particular

a first Time sensor: placed in the TLC area of the Help Point cabinet

a second Temp2 sensor: placed in the Power Supply area of the Help Point cabinet. The SOS 101 module has the task of managing SOS calls or assistance calls and the Help Point alarm functions.

The PA 102 module has the task of managing the sessions of Public Announcements.

The SOS 101 module and the PA 102 module are completely independent from each other.

Each amplifier 103, 104 is responsible for operating different groups of horns 104 (Group # 1 and Group # 2) of the Horn subsystem 4 during Public Announcements sessions.

The Human Machine Interface 107 acts as an interface between human users and the Help Point.

The programmable logic microcontroller 105 has the task of collecting diagnostic data from the equipment of the TLC and Power Supply level.

Switch 106 acts as a link to tunnel LAN 5 via the ODF layer equipment.

In the TLC level of the Help Point, other electronic modules can be used to create functional extensions, such as:

an electronic module for diagnostics on the horns connected to the Help Point audio amplifiers;

an electronic module for the use of audio amplifiers in a parallel redundant configuration.

These electronic modules are represented briefly by box 116 of Figure 4.

The TLC level components are all located in the TLC area of the HP cabinet (the upper part of the cabinet), with the sole exception of the Temp2 temperature sensor, which is located in the Power Supply area. The TLC zone of the cabinet is not separated from the Power Supply zone.

The equipment of the TLC level receives from the Power Supply level:

the power supply for each component

diagnostic information on the power supply status.

The switch 106 of the TLC layer receives from the ODF layer the optical cables used to connect the Help Point to the tunnel LAN 5, 6.

The TLC level provides the Sounders subsystem 4 directly with the audio signal for Public Address sessions.

The TLC layer provides the Ethernet connection directly to the Lighting and Power subsystem 8 to allow the Lighting and Power subsystem 8 to access the tunnel LAN 5, 6 through the switch 106 of the Help Point.

The Power Supply level consists of the following components:

isolation transformer 117

power relay 118 in case a double 230 V AC power supply line is available from the Lighting and Power subsystem.

119 switches for the following components of the TLC level and Power Supply:

CBO for the Isolation Transformer (230V AC) CB1 for the 120 power supply (230V AC) CB2 for the 121 power supply (230V AC) CB3 for the SOS 101 module (24 V DC)

CB4 for PA 102 module (24 V DC)

CB5 for Switch 106 (24V DC)

CB6 for the / xPLC 105 (24V DC)

two electric power supplies 120, 121 in parallel configuration:

120 power supply: 230V AC input / 24V AC and 24V DC output

121 power supply: 230V AC input / 24V AC and ± 24V DC output

The components of the Power Supply level are all arranged in the Power Supply area of the Help Point cabinet (central part of the cabinet).

Figures 5 to 7 illustrate block diagrams of three respective different power supply subsystems.

Figure 5 illustrates the Power Supply level if a single 230VAC power line is available from the Lighting and Power Subsystem 8. Isolation Transformer 117 ensures proper isolation from the external 230VAC power supply.

Two 230 V AC / 24 V DC power supplies 120, 121 are used to power:

the SOS 101 module, the PA 102 module, the Switch 106, the pPLC 105, the Human Machine Interface 107 of the TLC level (+ 24V DC redundant)

Audio Amplifiers 103, 104 of the TLC level (+ 24V DC).

If one of the power supplies fails, a diagnostic alarm is transmitted at μΡΙιΟ 105 of the TLC level.

Figure 6 illustrates the Power Supply level in case a single 230 VAC power supply line is available from the Lighting and Power subsystem 8. The configuration is identical to the one described above, but the dual input must be managed through a power relay 118 included in the Help Point, which switches to the second line in the event of a power failure in the first.

Figure 7 illustrates the Power Supply level if two power lines are available, one 230 V AC and one 24 DC, from the Lighting and Power subsystem 8. In this case, an additional switch (CB7) is used to power the SOS 101 module, the PA 102 module, the Switch 206, the programmable logic microcontroller (pPLC) 105, the human-machine interface 107 (HMI) with additional external 24V DC power supply. Audio Amplifiers 103, 104 are not powered with external 24 V DC.

The optical distribution box (ODF) 122 has the task of dissecting and joining the fiber optic cable inside the tunnel. It also provides the fiber optic patch (FOP), suitable for allowing the Lighting and Power subsystem 8 to access the fiber optic cable 5 (FOC).

The ODF level is composed of the ODF 122, whose components are all placed in the ODF area of the HP cabinet (see figures 3A and 3B).

The tunnel fiber optic cable 5 is sectioned and spliced inside the ODF 122.

The optical fibers of the FOC 5 are spliced directly to:

the patches of the fiber optic link (FOP) 208: the fiber optic link 208 between the Help Point 1 and the Lighting and Power subsystem 8 is used to directly connect the Lighting and Power subsystem 8 to the optical break-out cable of the tunnel for the exclusive use of the Lighting and Power subsystem 8 (LFM) through the fiber optic link 208 (FOP))

patches to Switch 106 of the TLC level: these patches are used to connect Switch 106 directly to the tunnel LAN 6.

The cabinet level is illustrated in figures 3a and 3B and has the task of:

house all the components of the TLC, Power Supply and ODF levels, and connect them to each other;

guarantee an appropriate protection of the Help Point from the infiltration of dust and liquids;

ensure proper electrical insulation of the Help Point;

ensure an appropriate heat exchange between the internal components and the external environment.

The Cabinet level consists of the Help Point 300 cabinet, divided into three zones:

the TLC 301 zone (upper part)

the Power Supply zone 302 (central part)

the ODF 302 zone (lower part, separated from the others)

base plate

The equipment belonging to the respective TLC, Power Supply and ODF levels are arranged respectively within the TLC, Power Supply and ODF zones within the Help Point cabinet, with the sole exception of the Temp2 temperature sensor (TLC level), which is located in the Power supply zone.

Figure 3A and Figure 3B represent the three zones of the cabinet (with all the equipment arranged in the respective zones), with all the interfaces to other subsystems highlighted.

The plinth is used to position the cabinet on the ground, respecting the minimum radius of curvature of the cables coming from other subsystems that connect to the three zones of the HP cabinet (in particular of the FOP that connects with the ODF zone).

Regardless of the optional functions of the Power Supply level described above, the Power Supply 120 and the Power Supply 121 operate in a redundancy configuration for the 24 VDC output. A fault on a Power Supply does not therefore compromise the operation of all the other equipment present in the Help Point, with the exception of the connected Audio Amplifier, which fails to supply ± 24V DC from the faulty power supply 120 or 121. All functions of the system remain available, although the Public Announcements sessions are only available through the horns connected to the other Audio Amplifier connected to the non-faulty Power Supply.

Figures 8 to 15 illustrate in greater detail the various components of the Help Point, whose functions and configurations will be described in more detail below.

The power relay illustrated in figure 8 is provided when, to obtain greater availability of the Help Point, an optional secondary power supply line is used, coming from a second power supply. If an external power supply of 2 x 230 V AC is envisaged, the power relay is used to manage the double input: the passage to the second line occurs in the absence of voltage in the first.

The optional 118 power relay is located in the Power Supply area of the Help Point cabinet, physically separated from the other areas.

In case the external Lighting and Power subsystem 8 has a single 230 V AC power supply, the optional Power Relay 118 is not necessary. In this case, the CBO circuit breaker will be used as an interface between the isolation transformer and the external power supply line, as seen in figures 5 and 7.

The power relay 118 has an interface towards the isolation transformer 117 (power supply level).

Isolation Transformer 117 is used to ensure correct isolation from the external 230 V AC power supply (of the Lighting and Power Supply subsystem 8).

The isolation transformer is placed in the Power Supply area of the Help Point cabinet. It is physically separated from other equipment by a separating cover.

The isolation transformer is installed on the separator plate between the Power / TLC zone and the ODF zone.

The role of the Isolation Transformer is to supply 230 V AC power to the entire Help Point, ensuring appropriate isolation from the Lighting and Power Supply subsystem 8 through the interface Pl.l provided by the CBO or the Power Relay).

The isolation transformer has an interface to the following HP equipment (see figure 9):

119 CBO switch (Power supply level)

Power relay 118

switches 119 CB1 and CB2

Therefore, the isolation transformer interfaces with the switch 119 (interface Pl.l) through the switch 119 CBO or the power relay 118.

The isolation transformer is placed in the Power Supply area shown in figure 3A.

The installation of the isolation transformer is specified below.

Power supplies 120, 121 are shown in Figure 10.

The power supplies have an interface to the following HP equipment:

119 switches: CB1 / CB2 (power supply level), 230 V AC

119 switches: CB3 / CB4 / CB5 / CB6 (Power Supply level), 24V DC

Audio Amplifiers 103, 104 (TLC level), 24V DC.

/ xPLC 105 (TLC level)

The Power Supplies supply electricity to the TLC equipment through the switches 119 indicated above.

An output decoupling diode is provided for parallel connection of the outputs of the 24 V DC power supplies.

An alarm relay contact is also available, for the transmission of diagnostic information on each Power Supply 120, 121 to the PLC 105.

The Power Supplies are located in the Power Supply area shown in Figure 3A.

According to figure 11, in Help Point 1 there is a switch 119 for each component of the TLC zone:

CBO for Isolation Transformer 117 (230V AC)

CB1 for the 120 (230V AC) power supply CB2 for the 121 (230V AC) power supply CB3 for the 101 SOS module (+ 24V DC)

CB4 for the PA 102 module (+ 24V DC)

CB5 for Switch 106 (+ 24V DC)

CB6 for the / iPLC 105 (+ 24V DC)

The aforementioned Switches have interfaces to the PI .1 Power Supply interface which faces the Light and Forza 8 subsystem.

The role of the Pi.1 interface is to supply the 230 V AC power supply of the Luce and Forza 8 subsystem to the Help Point.

If the power relay is available in the HP, the interface Pl.l is delegated to the power relay.

Switches are primarily used to provide protected electrical power to all TLC level equipment. The switches protect the electrical circuit from damage caused by overloads or short circuits.

CBO is used to protect the entire Help Point and as a switch-disconnector for the main external power supply.

CBO is used in HP following a specific customer request.

The Switches are located in the Power Supply area shown in Figure 3A.

The SOS 101 module is shown in Figure 12 and is designed based on the following criteria:

10 SIP standards

11 broadband codec support (G722) advanced audio functions

simple configuration

The SOS 101 module has the task of managing SOS calls or assistance calls and Alarms. It supports full duplex conversation for these calls. Preferably, the module is configured with automatic response functions. The SOS protocol is used in the SOS module.

At least the following audio codecs are available in the SOS module:

G722 (default codec, audio band up to 7 kHz)

G711 (audio band up to 4 kHz)

However, it is possible to enable other codecs (for example Speex) in the SOS module, with a simple modification of the software configuration.

It is also possible to foresee a <1> equalization of the audio signal sent to the loudspeaker during SOS calls and / or assistance calls to make it more intelligible. An AEC is available inside the SOS module to eliminate the acoustic echo generated during a call, between the loudspeaker and the SOS or PA microphone.

Ambient noise can also be suppressed during SOS calls and / or assistance calls.

The SOS module is able to send diagnostic information related to its status.

Pressing the SOS 111 button is acquired by the SOS 101 module, and immediately starts an SOS call. According to a preferred setting, this SOS call must reach the Operator Console within 1 sec, and this time includes:

SOS 101 module: SOS button signal acquisition

SOS 101 module: processing and initiation of a new SOS call to the Operator Console 3

HP 106 switch: SOS call routing through tunnel LAN 6

Tunnel LAN 6: Network delay

SOS & PA server 2: routing of the SOS call to the Operator Console 3

Tunnel LAN 6: Network delay

Operator console 3: ring

The Help Point is responsible only for the first 3 phases of those listed above.

The SOS 101 module manages all SOS calls and / or assistance calls and Alarms and acts as a SIP Client to the SOS & PA server 2 through the switch 106 of the Help Point and the tunnel LAN 6.

The SOS 101 module acts as a normal SIP softphone compared to the SOS & PA 2.11 server. SOS 101 module manages two internal SIP lines, configurable according to the associated function.

Different SIP lines are used to differentiate the functions of the SOS 101 module and to apply different configurations to each function. In this way, the sensitivity of the microphones and the audio equalization can be configured independently for each SOP line of the SOS module: for example, the Alarm function may require a different microphone sensitivity compared to the assistance calls and SOS functions. .

The following table shows two different configuration examples for SIP lines:

A web server and a TFTP / FTP client are available on the SOS 101 module for configuring via the Ethernet interface.

In response to audio performance requirements, a further refinement is a specialized hardware solution for audio processing, which consists of an additional audio DSP or an advanced CPU with DSP functionality on the SOS 101 module.

According to another feature, an additional RS422 serial interface (opto-isolated) can be made available on the SOS 101 module to expand the I / O capacity of the module with external cards. The maximum connection distance obtainable between the SOS module and the external card with this interface is at least 100 m.

Similarly, an additional serial interface (console port) is available for configuration.

The SOS module can be configured to automatically close a call, during communication, in the absence of RTP traffic within a certain number of seconds (configurable).

Furthermore, according to another feature, if the SOS and / or assistance call does not reach the requested user, in particular the SOS & PA 2 server, or if the call is automatically closed, the SOS module will emit a busy signal through 1 ' speaker.

The SOS module has interfaces to the following Help point devices:

CB3 switch (power supply level)

PA 113 microphone (TLC level)

SOS microphone 112 (TLC level) Γ metal key switch 110 (TLC level)

SOS button 109 (TLC level)

^ PLC 105 (TLC level)

speaker 114 (TLC level)

SOS 115 LED (TLC level)

Switch 106 (TLC level)

The SOS module can be activated by: the temporary SOS button 109 (TLC -HMI level) for an SOS call: in this way the communication is initiated, which remains active even if the SOS button is released

the key switch 110 (TLC - HMI level) for an assistance call: in this way, communication is initiated, which is interrupted if 1 <1> key switch is returned to the neutral position

SOS button 109 key switch 110 (TLC - HMI level) for a conference call between Help Points: in this way, communication is initiated, which is interrupted if the key switch is returned to the neutral position

an incoming call from an Operator Console 3

Both the SOS button 109 and the key switch 110 constitute simple activation contacts of the SOS 101 module.

The SOS module also manages a multicolored LED 115 located on the front side of the Cabinet 300 to provide local diagnostic information on the SOS and / or on the assistance and / or alarm functions.

The multicolored SOS LED lights up according to the glove shown in the following table:

State Color

Off Module not powered

Green Module functioning normally Green flashing SOS or assistance call or Alarm in progress

Red Module functioning in degraded condition (e.g. generic fault) Generic red Module unable to register on the SOS & PA 2 Server

Table 4: SOS LED states

According to a further feature, three buttons are available on the SOS module to locally adjust the speaker output gain:

: to turn up the volume

-: to decrease the volume

Enter: to confirm the volume setting. When you perform an operation on the volume buttons, a beep will sound from the speaker.

The SOS module has the ability to:

INPUT: manage two independent microphones (not simultaneously)

OUTPUT: activate a speaker

The SOS microphone (non-directional) is compulsorily used for the Alarm function.

Both the SOS microphone and the PA microphone can be used for SOS / PA calls: the choice of the microphone to be used for SOS / SC calls must be made during the test phase.

Thanks to its diagnostic functions, the SOS 101 module can transmit at least the following diagnostic information about its status:

al ^ PLC 105 (contacts)

no power input on the SOS module SOS call or assistance or Alarm in progress SIP registration on the SOS & PA 2 server

Keep-alive

to the integrated supervision subsystem 7, along the tunnel LAN 5, 6 through Switch 106 (Simple Network management Protocol (SNMP))

SOS call request

SOS call in progress

request for assistance call

assistance call in progress

alarm in progress

SIP registration on the SOS & PA server

The following parameters can be configured in the SOS module via the Ethernet interface (TFTP / FTP / HTTP):

IP, SM and Gateway address of the SOS module (if already assigned by a DHCP server or manually)

SIP user ID and password of the SOS module (for each SIP line)

Audio gain control of the SOS module microphone sensitivity (for each SIP line) audio equalization of the SOS module (for each SIP line)

Codec (G.711 or G.722)

IP address of the SIP gateway

SOS call number

assistance call number

SNMP agent configuration

NTP Client configuration

RTP / multicast timeout for call drop

Diai Pian

niche identification number and progressive distance of the niche from a pre-established reference point (PK)

The software / firmware of the SOS module can be configured and updated through:

web access on a single SOS module (HTTP) an external TFTP / FTP server serving the TFTP / FTP Client of several SOS modules (like in normal IP phones)

All the parameters listed above can be configured in the SOS module also through the Console port. Furthermore, through the Console port, it is possible to assign an IP address and the SM even if these have not yet been set.

A software routine, implemented in the SOS module, can be activated during the bootstrap of the module for the automatic assignment of the SIP / SNMP / NTP parameters, by extracting the information from the IP address of the module.

The SOS module is placed in the TLC area shown in Figure 3A.

The PA module is shown in Figure 13 and is designed on the basis of the following criteria:

10 SIP standards

11 broadband codec support (G722)

support of standard PA and advanced PA advanced audio functions

simple configuration

It is based on the same hardware as the SOS module, with different software.

The PA 102 module is responsible for managing local and remote PA sessions.

The module is configured with automatic response for a PA session initiated by an Operator Console 3.

At least the following audio codecs are available in the PA module:

G722 (default codec, audio band up to 7 kHz)

G711 (audio band up to 4 kHz)

However, it is possible to enable other codecs (for example Speex) in the PA module, with a simple change of the software configuration.

It is also possible to provide an equalization of the audio signal sent to the audio amplifiers during a PA session to make it more intelligible.

Inside the PA module there is an AEC to eliminate the acoustic echo generated during a PA session, between the horns connected to the audio amplifier and the PA 113 microphone.

The Larsen effect during PA sessions is minimized by the PA module (a minimum SPL of 85 dB must be achieved in each type of tunnel).

Ambient noise can also be eliminated during local PA sessions.

A PA session (local and remote) introduces no additional noise.

The PA module is capable of sending diagnostic information related to its status.

The PA module manages all PA sessions:

Standard remote PA (SIP based)

Standard local PA without authorization on a single section of tunnel (based on SIP)

Advanced remote PA (based on Alstom protocol) Advanced local PA without authorization on one or more sections of tunnel (based on Alstom protocol) The PA module acts as a SIP Client to the SOS & PA 2 Server through the Help Point switch 106 and the gallery 6.

The PA module acts as a normal SIP softphone compared to the SOS & PA 2 server.

The PA module manages two SIP internal lines. The second SIP line is RFU.

Different SIP lines are used to differentiate the functions of the PA module and to apply different configurations to each function.

Furthermore, the internal Diai Pln of the PA module is customizable: it is possible to call different SIP numbers according to the activated function.

Custom software (PA client) is also available in the PA module for managing advanced PA sessions and receiving audio streaming related to:

an enhanced local authorized PA session an enhanced remote PA session

coming from the SOS & PA server 2.

An NTP client is available on the PA module to synchronize the date and time with a clock server.

A web server and a TFTP / FTP client are also available on the PA module for configuring via the Ethernet interface.

The requirements in terms of audio performance can be such that a specialized hardware solution for audio processing is required. In this case, an additional audio DSP or an advanced CPU with DSP functionality can be provided on the PA module.

According to another feature, an additional RS422 serial interface (opto-isolated) is available on the PA module to expand the I / O capacity of the module with external cards. The maximum connection distance obtainable between the PA module and the external card with this interface is at least 100 m.

Similarly, an additional serial interface (console port) is available for configuration.

The PA module is able to automatically close a call, during communication, in the absence of RTP / multicast traffic within a certain number of seconds (configurable).

The PA 102 module has interfaces to the following HP equipment:

CB4 switch (power supply level)

PA 3 microphone (TLC level)

SOS 112 microphone

metal key switch 110 (TLC level)

/ iPLC 105 (TLC level)

Audio Amplifiers 103, 104 (TLC level)

PA 115 LED (TLC level)

Switch 106 (TLC level)

The PA 102 module can be activated by: the key switch 110 (TLC level - HMI) for a local PA session: this starts the PA session, which is interrupted if the key switch 110 is returned to position neutral

a remote PA session from an Operator Console 3

The key switch 110 provides simple contacts for activating the PA module.

The PA module is equipped with local diagnostic LEDs 115 placed directly on the module. The PA module also manages a multi-colored LED located on the front of the cabinet 300 to provide local diagnostic information about PA sessions. The multicolored PA LED lights up as shown in the following table:

State Color

Off Module not powered

Green Module functioning normally

Green Local PA session or remote PA session in progress flashing

Red Module functioning in degraded condition (eg.

generic fault)

Red Module unable to register on the generic SOS & PA Server

To locally adjust the output gain to audio amplifiers, there are three buttons on the PA module:

: to turn up the volume

-: to decrease the volume

Enter: to confirm the volume setting.

When you perform an operation on the volume buttons, a beep will sound from the audio amplifiers.

The PA module has the ability to:

INPUT: manage two independent microphones (not simultaneously)

OUTPUT: activate two audio amplifiers

The PA (directional) microphone is used for local PA sessions.

The Emergency Boost function is managed by a customized application on the PA module, which estimates the noise level present in the tunnel through the SOS (non-directional) microphone.

The Voice Guide function is managed by the PA Client on the PA module.

The audio DSP can mainly be used for:

equalize the audio signal sent to the audio amplifiers

implement an AEC based on specific hardware implement a band elimination filter (preferably adaptive) to avoid the Larsen effect.

The PA module features balanced audio outputs. Using shielded balanced audio cables allows you to connect amplifiers to the PA module to protect audio signals from electromagnetic interference.

The PA module is able to send at least the following diagnostic information relating to its status:

al / xPLC (contacts)

no power input on the PA module PA session in progress

SIP registration on the SOS & PA server

Keep-alive

to the integrated supervision subsystem (SPVI) 7, along the tunnel LAN 6 through Switch 106 (SNMP protocol)

local PA session required

local PA session in progress

remote PA session request

remote PA session in progress

SIP registration on the SOS & PA server

The following parameters can be configured in the PA module via the Ethernet interface (TFTP / FTP / HTTP):

IP, SM and Gateway address of the PA module (if already assigned by a DHCP server or manually)

PA module SIP user ID and password (for each SIP line)

Audio gain control of the PA module microphone sensitivity (for each SIP line) audio equalization of the PA module (for each SIP line)

Codec (G.711 or G.722)

IP address of the SIP gateway

PA call number

SNMP agent configuration

NTP Client configuration

RTP / multicast timeout for call drop

Diai Pian

thresholds for emergency enhancement

niche identification number and progressive distance of the niche from a pre-established reference point (PK)

The software / firmware of the PA module can be configured and updated through:

web access on a single PA module (HTTP) an external TFTP / FTP server serving the TFTP / FTP Client of several PA modules (as in normal IP phones)

All the parameters listed above can be configured in the PA module also through the Console port. Furthermore, through the Console port, it is possible to assign an IP address and the SM even if these have not yet been set.

A software routine, implemented in the PA module, can be activated during the bootstrap of the module for the automatic assignment of the SIP / SNMP / NTP parameters, by extracting the information from the IP address of the module.

The PA 102 module is placed in the TLC zone illustrated in Figure 3A.

The programmable logic microcontroller module (JÌPLC) 105 is shown in figure 14 and is designed on the basis of the following criteria: availability of various I / O

simple configuration

standard protocol for diagnostic information

The μPLC 105 has the task of collecting local diagnostic information on Help Point 1 from the relay contacts. The information collected can be monitored remotely.

According to a specific embodiment, the μΡΙ ^ 105 is equipped with the following characteristics:

IEEE 802.3 interface (Ethernet)

RS232 / RS422 interface

standard programming language possibility to download data remotely

MTBF> 80,000 h

Discrete I / O

The μΡΙιΟ is fully compatible with the software drivers available on the SCADA supervision system (Supervisory Control And Data Acquisition) 70 used in the integrated Supervision subsystem 7 (fig. 1). The exchange of diagnostic information takes place via SNMP messages.

The event "SOS button 109 pressed" in the Help Point is acquired by the μPLC 105 and transmitted to the integrated supervision subsystem 7 within a predetermined time. This arrival time could be for example equal to 1 sec.

This time includes:

μPLC 105: SOS button signal acquisition

μΡLC 105: processing and transfer of the event to the Integrated Supervision subsystem 7 (SPVI) Switch 106: routing of the event through the tunnel LAN 6

Tunnel LAN 6: network delay Integrated supervision subsystem (SPVI): reception of the event

The μPLC 105 monitors the temperature of the Power Supply and TLC zones inside the cabinet 300 through two Tempi and Temp2 temperature sensors.

Each sensor will have two configurable thresholds: above and below these thresholds, an alarm will be activated, which will be transmitted to the Supervisory Control and Data Acquisition 70 system through the / iPLC 105.

Temporary alarms are not transmitted to the SPVI 7 system. A temporary alarm is a non-critical alarm, in which the time between alarm activation and restoration of normalcy is less than a configurable interval (for example 30 sec).

The ^ PLC has interfaces to the following external subsystems:

PI.5: serial connection with the Luce e Forza 8 system

The μPLC 105 has the task of collecting local diagnostic information from the internal equipment of Help Point 1.

The diagnostic information is sent to the Integrated Supervision subsystem (SVPI) 7 through the Help Point switch 106, using the Simple Network Management Protocol (SNMP).

An NTP Client is available on the ^ PLC 105 to synchronize the date and time with a clock server.

A web server and a TFTP / FTP client are also available on the JÌPLC for configuring via the Ethernet interface.

An additional RS422 serial interface (opto-isolated) can be available on the / xPLC to expand the I / O capacity of the module with external cards. The maximum connection distance obtainable between the PA 102 module and the external card with this interface is at least 100 m. This interface can serve as a serial link with the Lighting and Power Supply subsystem 8.

An additional serial interface (console port) may be available for configuration.

The ^ PLC has interfaces to the following equipment:

CB6 switch (power supply level)

power relay 118 (power supply level)

Audio Amplifiers 103, 104 (TLC level) SOS 101 module (TLC level)

PA 102 module (TLC level)

Times and Temp2 (TLC level)

Power Supplies 120, 121 (Power Supply Level)

Electronic module 116 (TLC level)

Switch 106 (TLC level)

door microswitch (TLC level)

The / xPLC is able to collect at least the following inputs from the Help Point 1 equipment:

lack of power input line 1 if a double external power supply is available from the Lighting and Power subsystem 8

lack of power input line 2 in case a double external power supply is available from the Power 8 Lighting subsystem

Contact Alarm Power Supply 120, (from Power Supply 120)

Contact Alarm Power Supply 121, (from Power Supply 121)

no power input on the SOS 101 module (from the SOS module)

no power input on the PA 102 module (from the PA module)

generic fault Audio Amplifier 103 (from Audio Amplifier 103)

generic failure of Audio Amplifier 104 (from Audio Amplifier 104)

no power input on Audio Amp 103 (from Audio Amp 103)

no power input on Audio Amp 104 (from Audio Amp 104)

open circuit power line horns 1 (from Audio Amplifier 103) open circuit power line horns 2 (from Audio Amplifier 104) short circuit power line horns 1 (from Audio Amplifier 103) short circuit power line horns 2 (from Audio Amp 104) horn power line overload 1 (from Audio Amp 103) horn power line overload 2 (from Audio Amp 104)

fault on a single horn, line 1 (from Electronic Module, 116)

fault on a single horn, line 2 (from Electronic Module 116)

door open alarm: TLC zone (from the microswitch on the TLC door)

tray alarm open: Power supply zone (from the microswitch of the Power supply zone, optional)

door open alarm: ODF zone (from the microswitch on the ODF door)

SOS call request (from SOS button 109) assistance call request (from metal key switch 110)

PA session request (from metal key switch 110)

SOS and / or assistance call or Alarm in progress (from SOS 101 module)

PA session in progress (from module PA 102) SIP registration of SOS module on IPBX (from module SOS 101)

PA module SIP registration on IPBX (from PA 102 module)

keep-alive contact SOS 101 module (from SOS 101 module)

keep-alive contact module PA 102 (from module PA 102)

reserve

reserve

temperature sensor 1 (from Tempi)

temperature sensor 2 (from Temp2)

reserve for temperature sensor

reserve for analog input

This diagnostic information is sent to the Integrated Supervision Subsystem (SPVI) 7, along the tunnel LAN 6 through Switch 106.

The following parameters can be configured in the μPLC 105 via 1 <1> Ethernet interface (TFTP / FTP / HTTP):

IP, SM and Gateway address of the / iPLC (if already assigned by a DHCP server or manually)

thresholds for temperature alarms relating to Times and Temp2

interval for temporary alarms

alarm masking matrix (to mask the alarms that should not be sent to the SPVI) SNMP agent configuration

NTP Client configuration

niche identification number and progressive distance of the niche from a pre-established reference point (PK)

The μΡΙιΟ module software / firmware can be configured and updated through:

web access on a single pPLC (HTTP) module a TFTP / FTP server serving several / xPLC modules (as in typical network equipment)

All the parameters listed above can be configured in the ^ PLC 105 also through the Console port. Furthermore, through the Console port, it is possible to assign an IP address and the SM even if these have not yet been set.

A software routine, implemented in the μΡΏΟ, can be activated during the bootstrap of the module for the automatic assignment of SNMP / NTP parameters, by extracting the information from the IP address of the module.

The μΡΙιΟ is equipped with local diagnostic LEDs placed directly on the module. The / iPLC can also manage a multi-color LED for local diagnostic information on the status of the HP II The multi-color LED can be activated according to the following table:

State Color

Off Module not powered

Green Module functioning normally

Green SOS / SC call, PA or AL session in progress flashing

Red Module functioning in degraded condition (eg.

generic failure, amplifier failure, SOS / PA module failure, SOS / PA module not registered on the server)

The fiPLC is placed in the TLC zone illustrated in Figure 3A.

The Switch is shown in Figure 15 and is intended to act as a link to the tunnel LAN.

According to this example, the Ethernet switch installed inside the Help Point can guarantee the following characteristics:

Management of

8 ports at 100 Mb / s

2 x 1 Gb / s ports on SM optical fiber (LC connectors)

mounting on DIN rails

2 x 24 V DC power supply

VLAN support

compliance with IGMP Snooping and RSTP

low latency time (maximum 5 με on the 100Mb / s link)

compliance with IEC 62439

SNMP diagnostics, remote configuration web browser

local diagnostics via LED

easily expandable

MTBF of the switch> 120,000 h with the exception of the LAN ports used by the hosts in the niche (referred to the general failure of the entire switch with loss of all its functions)

MTBF doors> 50,000 h

The use of a 9/125 μιη singlemode fiber allows LAN switches to be connected at a maximum distance of 20 km, without the interposition of other equipment.

The switch has interfaces to the following external subsystems:

PI.5: Ethernet interface with the Lighting and Power subsystem 8

The Switch has the task of connecting all the necessary equipment of the Help Point with the tunnel LAN through the ODF and therefore with the SOS & PA 2 server and with the SPVI 7 subsystem.In addition, the Switch constitutes the data interface between the Help Point and the cabinet of the Lighting and Power subsystem, used to connect the Lighting and Power subsystem 8 to the tunnel LAN.

The Switch can be configured as a DHCP Relay Agent with Option 82 (RFC3046) enabled. Option 82 is used by the Relay Agent to insert additional information into the client's DHCP request.

The Switch has interfaces to the following HP equipment:

CB5 switch (power supply level)

SOS 101 module (TLC level)

PA 102 module (TLC level)

jiPLC 105 (TLC level)

ODF (ODF level)

The switch also has the DHCP relay agent information option (option 82) which allows a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding DHCP packets originating from the switch. Client to a DHCP server. The DHCP server can then use this information to implement procedures for assigning IP addresses or other parameters.

This option can be used to assign an IP address to a host connected to a Switch port regardless of the host's MAC address, based on the procedures of an option 82-enabled external DHCP server.

The Switch is placed in the TLC area illustrated in Figure 3A.

According to a further refinement, the Help Points can include an additional electronic unit 116. This unit can be provided as an optional component, connected to the Audio Amplifiers, capable of:

diagnose a fault in a buzzer connected to the output line of an Audio Amplifier, detecting it through an impedance measurement on the line

allow the Audio Amplifiers to operate in parallel redundant configuration, activating all the horns connected to Help Point 1

The Electronic Module has an isolation of 4 kV towards the output line of an Audio Amplifier.

It provides diagnostic contacts for alarms. The impedance thresholds for activating the alarms can be configured both locally and remotely.

The Electronic Module has interfaces to the following equipment and the following subsystems: CB6 switch (power supply level)

Audio Amplifiers (TLC level) Horn subsystem (T3 interface)

/ xPLC (TLC level)

The CB6 switch supplies power (24V DC) to the Electronic Module.

The Electronic Module transmits diagnostic information on the lines to the horns to the PLC through contacts. The Electronic Module makes available, through contacts, at least the following diagnostic signals:

buzzer fault on line 1

buzzer fault on line 2

The Electronic Module is connected to the output stage of the amplifiers for:

diagnose the faults of the horns connected to the Help Point

provide a parallel connection between the amplifiers with the Horn subsystem.

The Electronic Module is placed in the TLC area illustrated in Figure 3A.

With reference to Figures 16 and 17, the above-described Help Point, which has a switch with support functions of option 82, which is part of the safety system for tunnels according to the invention, allows to carry out self-configuration processes of the system.

Help Point Switch 106 can be configured to allow use of Switch Option 82 (DHCP Relay). As already indicated in the previous description, this option allows you to perform automatic configuration processes of the Help Points 1 and the security system for tunnels.

The main information to be configured in relation to a Help Point are:

SOS 101 module:

IP configuration

SIP ID

SIP server (master and reserve)

NTP server (master and reserve)

SNMP server (master and reserve)

PA 102 module:

IP configuration

SIP ID

SIP server (master and reserve)

NTP server (master and reserve)

SNMP server (master and reserve)

μPLC 105:

IP configuration

NTP server (master and reserve)

SNMP server (master and reserve)

The IP configuration for each of the above modules or units can be derived from a request from the host (the equipment itself) to a DHCP Server that supports Option 82 via the DHCP Relay Agent.

Option 82 information is entered by the DHCP Relay Agent when forwarding DHCP packets originating from Clients to the DHCP server. The server, recognizing the option of the Relay Agent information, can use this information to implement procedures for assigning IP addresses or other parameters. The DHCP Server literally retransmits the option to the relay agent in server-client responses, and the relay agent removes the option before forwarding the response to the Client.

In summary, the devices (SOS 101 module, PA 102 module, ^ PLC 105), configured as DHCP Client, transmit a request to the DHCP Client. The request is intercepted by the DHCP Relay Agent (Switch 106 with option 82 enabled) which adds information (Option 82) about itself (Remote ID sub-option) and the specific port on which the request was received (Circuit ID sub-option ). Based on this information, the DHCP server assigns the IP parameters to the hosts. Figure 6 represents the information exchanged after a DHCO request from a DHCP Client.

Assuming that the HP number and IP address of the switch are known (directly related to each other), and that Option 82 is active, it is possible to implement a procedure on the DHCP Server that assigns IP parameters to all the aforementioned HP equipment based on the following criteria:

gallery number

HP number (or Switch number)

Switch port

Figure 17 schematically illustrates this IP address.

Help Point 1 is equipped with a switch 106 with a relay agent and option 82 support. The Switch 106 communicates with a DHCP server 40 with option 82 as well as a DHCP client. DHCP Client Host A sends a DHCP request to Switch 106. Switch 106 intercepts the DHCP request packet and inserts the relay agent information option into that packet. At this point, the DHCP request is forwarded to the DHCP server 40 with the Option 82 field. The DHCP server 40 checks the remote ID, 1 <1> circuit ID or both to assign IP addresses and implement procedures and transmits in unicast the response to the relay agent, which forwards the packet to Host A.

Assuming that all the devices present in the Help Point are configured with the correct IP parameters, it is possible that these devices will automatically configure themselves for the other parameters.

For SOS 101 and PA 102 module, the SIP ID and SIP server can be configured automatically by extracting the information from the IP address.

For the JÌPLC 105, the SNMP server can be configured automatically by extracting the information from the IP address.

Figure 18 illustrates the entire process that can be implemented to automatically assign parameters to Help Point 1.

Figure 18, on the left side, shows the DHCP server 12 with option 82 active, the SOS & PA server, together with the SNMP and NTP server and a switch 106 with order number 1 and a DHCP Relay option 82. The SOS & PA server, together with the SNMP and NTP servers, appear housed in the same computer. The aforementioned devices are part of the operational control center 200 or the operational office of the triage area 201 indicated in figure 1. Switch 106 has two ports, Port 1 and Port 2, which are dedicated to interfacing with the LAN of gallery. The gallery number is 1; Switch 106 with number 1 has communication ports for the local network, including the DHCP server 40 and the SOS & PA server, together with the SNMP and NTP servers indicated with 41 in figure 18. From switch 2 to switch N / 2 + 1, with the exception of switch N / 2, all are provided in a single Help Point 1. Each switch is equipped with communication ports with the LAN 6 of gallery 1 and with communication ports with the DHCP hosts represented by the VoIP SOS 101 module, by the VoIP module PA 102 and by the programmable logic microcontroller 105 provided in each Help Point.

Switch n / 2 is a switch that closes the DHCP LAN ring.

Figure 18, in the top row on the left side, shows the DHCP Option 82 table structure for switches 2 to N. For each switch, the IP address structure of each DHCP Client 101, 102, is shown. 105, in relation to the switch port to which the Client is connected.

Since each Help Point has the same DHCP Clients connected to its switch 106, in each Help Point the same module 101, 102, 105 is connected to the same port number as the other Help Points. The VoIP SOS 101 module is connected to port 4, the VoIP PA 102 module is connected to port 6 and the / iPLC 105 is connected to port 8. In the lower left of the figure, the generic structure of the IP addresses is shown, in the form of table, where X is a value that can be given in a personalized way. Below the IP address is the same representation mode for the SIP ID code structure.

Starting from the configuration of the switch 2 ports and from the IP addresses of the individual DHCP Clients 101, 102, 105 connected to said switch ports (top left in Figure 18), for each of said modules 101, 102, 105, i.e. respectively the VoIP SOS 101 module connected to port 4, the VoIP PA 102 module connected to port 6 and the / xPLC 105 connected to port 8, the corresponding configuration obtained automatically is indicated in a table 401, 402, 405 connected by arrows to the corresponding SOS 101 VoIP module, PA 102 VoIP module and / iPLC 105.

According to the invention, for example, the custom number x of the IP address or of a further data area of the IP address and of the SIP ID, can be dedicated to the niche identification number or code. This data area might also be expected in the switch data table. In this way, each IP address of the SOS 101 module, and / or of the PA 102 module and / or of the / zPLC 105 and / or also of the switch 106 will include information on the niche in which the Help Point 1 including these units is installed, as well as on its position in the tunnel, and with respect to the other Help Points 1 provided in the safety system for tunnels in other niches of the tunnel itself. This position information is significant in relation to the ability to establish the position from which a given assistance message or an SOS or alarm message was generated and transmitted, and also to establish where and with which synchronization the announcements or messages are to be transmitted to the gallery. generic answers. Information relating to the installation niche of a Help Point can be collected according to one or more of the methods and with the devices described above.

Claims (21)

CLAIMS 1. Safety system for tunnels, in particular for railway networks or similar, which system comprises an emergency communication subsystem, said emergency communication subsystem comprises a local network (5, 6) installed in the tunnel, which network is provided with a certain number of nodes, each of which is physically placed in a niche of a plurality of niches provided in the tunnel, each node being connected to an emergency communication device (1) of the VOIP type, so-called Help Point, and called local tunnel network (5, 6) presenting at least one connection interface to at least one server for emergency telephony and public address (2) and at least one connection interface to at least one operator console, called emergency communication device (1) enabling the transmission and reception of acoustic messages through said network to and from said emergency telephony server and the sound system (2) and / or at least one operator console (3), each emergency communication device (1) having a device identification code and an IP address, and each niche having an identification number relating to the position of said niche in the tunnel and related to the other niches provided in said tunnel. characterized by the fact that means (12, 40, 106) are provided for the automatic initialisation of each of the emergency communication devices (1), in relation at least to the univocal association of the device identification code, the IP address and the niche identification code of the niche in which it is installed the device. 2. System according to Figure 1, in which said means are in the form of a so-called DHCP server, and of an initialization manager (12, 40) which reads the ID code of the device and the ID code of the niche, while the emergency communication (1) are DHCP Clients. System according to claim 1 or 2, wherein the knee ID code and the device ID code are set in the emergency communication devices (1) or in a server, prior to the physical installation of the emergency communication devices (1 ) in a certain niche. System according to one or more of the preceding claims, in which each niche is identified with the ID code of the physical node for connection to the local network of the tunnel (5, 6), at least one node being provided in each of said niches of the tunnel. 5. System according to one or more of the preceding claims, in which the identification code of the niche is provided in a system configuration plan or table saved as a system configuration file in a memory of the emergency communication devices (1) or an initialization / configuration server (12, 40) together with a system initialization program executed by the emergency communication devices (1) or by the initialization / configuration server (40) once the emergency communication devices are installed and operationally connected to the tunnel LAN (5, 6). 6. System according to one or more of the preceding claims, in which a niche identification label, in which the niche identification code is saved, is placed in each of the niches, regardless of the emergency communication device installed in said niche, each device of emergency communication having means for interrogating and retrieving the ID code of the knuckle saved in the label, said niche identification code being used for automatic system initialization / configuration. System according to claim 6, wherein the tag is an RFID tag, the emergency communication devices (1) being provided with means for reading / writing data from / into the memory of the RFID tag. 8. System according to one or more of the preceding claims, in which the ID code of the niche is entered by the assistance personnel who physically install the emergency communication devices, using the input means provided on the communication devices of emergency. System according to claim 8, wherein said input means are a numeric or alphanumeric keyboard, provided at each emergency communication device. System according to claim 8, wherein said input means are a microphone, placed on the emergency communication device (1), adapted to receive coded acoustic signals, such as DTHM coded signals generated by a DMTF code generator. 11. System according to one or more of the preceding claims, in which each emergency communication device is provided with a receiver for data signals, a vehicle being provided comprising a generator of niche identification codes and a transmitter of said niche identification codes adapted to transmit a particular niche identification code to the emergency communication device (1) installed therein. System according to claim 11, in which the niche identification code generator is provided with means for determining the niche identification code on the basis of distance measurements relating to the length of the section traveled by the vehicle starting from a certain reference point, said means generating a niche identification code and transmitting said niche identification code each time the measured distance corresponds to the theoretical distance of a given niche with respect to said reference point. System according to claim 12, in which each emergency communication device (1) is provided with receiving and transmitting means suitable for receiving the data relating to the niche identification code and for transmitting feedback signals relating to the confirmation of the correct reception of the data. 14. System according to one or more of the preceding claims in which: each emergency communication device (1) is connected to the local network of the tunnel (5, 6) through a switch (106), each switch (106) is provided in correspondence with a niche and is provided with an IP address and at least a door to which said emergency communication device is connected; each emergency communication device comprises at least one VOIP communication module (101, 102) operating according to a so-called Session Initialization Protocol (SIP); The said at least one Voip module being DHCP clients requesting configuration information relating to the IP configuration, to the SIP ID, to the SIP Server, and eventually if provided to a NTP Server and a SNMP server; a DHCP server (40) being connected to the network (5, 6) which server generates automatically for each emergency communication device (1) connected to the locai tunnel Lan (5, 6), the corresponding ID code and / or the IP address and the IP configuration information needed by the network protocol, the said IP addresses and the said IP configuration information being generated from basic information relating to the Tunnel number, the niche number, the switch address and the switch ports to which the Voip module is connected and the SIP server adresses. 15. A System according to claim 14, in which each emergency communication device (1) comprises a first VOIP module (101) for carrying out emergency and / or Service calls, so called SOS Voip module and an independent second VOIP module (102) for generic announcements, a so called PA module, both operating according to a so called Sesslon inltlalizatlon protocol (SIP); said first and said second Independent VOIP module (101, 102) being configured as DHCP Client and being each separately connected to a different port of a switch (106) which connects said modules to the local tunnel LAN (5, 6); the tunnel local LAN (5, 6) being connected to a management server Lan (12), comprising at least one DHCP server (40); at least one SIP server being also connected to the local tunnel LAN (5, 6) so as to communicate with the VoIP modules (101, 102); the DHCP server (40) being equipped with automatic IP configuration functions and each switch being provided with a corresponding DHCP relay; the DHCP server by generating and transmitting the IP address and IP configuration information to the VoIP modules (101, 102) based on the IP addresses of the server, the IP addresses or the ID code of the switch and at least the port connecting the module to the switch (106) as well as on the basis of at least the gallery and / or niche identification number. System according to claim 15, wherein each emergency communication device further comprises a programmable logic microcontroller (105) which is independently connected by said VoIP modules (101, 102) to a different port of the switch (106), said programmable logic microcontroller (105) being also configured as a DHCP Client, and being subject to automatic IP configuration by the DHCP server (40) like the VoIP modules (101, 102). System according to claim 14, wherein at least one of said VoIP modules (101, 102) or both are independently connected to two different audio amplifiers (103, 104) each operating independently of the other and connected to different horns of two different horn subsystems. 18. System according to claim 14 or 15 in which each VoIP module (101, 102) and / or said programmable logic microcontroller (105) are powered by a power supply (120, 121), two independent power supply lines being provided for the electric power supplies which are automatically connected to the input of said electric power supply alternately with each other in case of failure of one of said power lines, by an emergency power relay (118). 19. Safety system for tunnels, in particular for railway networks or similar, which system comprises an emergency communication subsystem, said emergency communication subsystem comprises a local network (5, 6) installed in the tunnel, which network is provided with a certain number of nodes, each of which is physically placed in a niche of a plurality of niches provided in the tunnel, each node being connected to an emergency communication device (1) of the VOIP type, so-called Help Point, and called local tunnel network (5, 6) presenting at least one connection interface to at least one server for emergency telephony and public address (2) and at least one connection interface to at least one operator console, called emergency communication device allows the transmission and reception of acoustic messages through said network to and from said server for emergency telephony and d iffusion sound and / or at least one operator console, characterized by the fact that said emergency communication device comprises a so-called VoIP module (101, 102), said at least one VoIP module (101, 102) being powered by a power supply (120, 121), in turn powered by two independent power lines, the which independent power supply lines are automatically connected to the input of said electric power supply alternately with each other in case of failure of one of said power supply lines, by an emergency power relay (118). 20. Safety system for tunnels, in particular for railway networks or similar, which system comprises an emergency communication subsystem, said emergency communication subsystem comprises a local network (5, 6) installed in the tunnel, which network is provided with a certain number of nodes, each of which is physically placed in a niche of a plurality of niches provided in the tunnel, each node being connected to an emergency communication device (1) of the VOIP type, so-called Help Point, and called local tunnel network (5, 6) presenting at least one connection interface to at least one server for emergency telephony and public address (2) and at least one connection interface to at least one operator console, called emergency communication device allows the transmission and reception of acoustic messages through said network to and from said server for emergency telephony and d iffusion sound and / or at least one operator console, characterized by the fact that said emergency communication device comprises at least one VoIP module (101, 102), said at least one VoIP module (101, 102) having an output connected by means of two independent audio amplifiers (103,104), each of said amplifiers powering one of the two subsystems of independent sounders each comprising at least one sounder. 21. System according to claim 20 or 21, characterized in that said system is provided in combination with the characteristics of one or more of claims 1 to 18.