SERVICE DEVICE FOR A FIRE PROTECTION SYSTEM, CORRESPONDING FIRE PROTECTION SYSTEM, SYSTEM FOR OPERATING A FIRE PROTECTION SYSTEM AND ASSOCIATED METHOD

Description

[0001] The present invention relates to a service device for a fire protection system, a corresponding fire protection system, a system for operating such a fire protection system with a service device, and a method for operating a fire protection system using the service device.

[0002] In this context, a fire protection system is understood to be any type of system that can be used for the purpose of (preventive) fire protection in buildings, halls, rooms, or similar structures. Such fire protection systems may include, for example, but are not limited to, fire alarm systems, fire extinguishing systems, spark extinguishing systems, smoke extraction systems, and / or a combination thereof. Fire protection systems within the meaning of the invention are, in particular, systems comprising a central unit and one or more peripheral devices and / or components that are in communicative contact with the central unit.

[0003] In a specific embodiment, the fire protection system is in particular a fire alarm system. Fire alarm systems typically comprise a fire alarm control panel (or a fire alarm and extinguishing control panel) as the central device and, as an example of one or more peripheral devices, one or more fire detectors, which may be designed as fire gas or smoke gas detectors, as smoke detectors, as flame detectors, as spark detectors and / or as heat detectors, as well as alarm devices, which may be designed as horns, sirens, round or flashing lights or similar.

[0004] In response to the detection of a (potential) fire, the fire alarm control panel receives a corresponding signal from one or more fire detectors. The fire alarm control panel then triggers a hazard warning from the fire alarm system. As a reaction to this warning, a fire suppression system, which is in communication with the fire alarm system, particularly its central unit, can be activated. Furthermore, the central unit of the fire alarm system can also initiate other measures, such as triggering the alarm, alerting the fire department, activating escape route controls, closing fire doors, or similar actions.In this way, fire incidents such as fires or ignition points within the protected area of ​​the fire protection system can be detected early, even if no one is present in the protected area at the time of the fire. This can potentially prevent the fire from spreading further.

[0005] The extinguishing systems triggered by the fire alarm system can be, for example, but not exclusively, sprinkler systems, water mist extinguishing systems, foam extinguishing systems, gas extinguishing systems, powder extinguishing systems, or similar systems, which are primarily used to extinguish a fire. However, the term "extinguishing system" can also include fire prevention systems, such as inerting systems or similar systems for active fire prevention.

[0006] Fire extinguishing systems are permanently operational systems that distribute an extinguishing agent such as water, foam, gas, or powder to contain or extinguish fires that have already started. They consist of a pipe system with corresponding outlet openings, such as sprinklers or nozzles, through which an extinguishing agent, for example, water, gas, or powder, can be applied to a fire in order to contain the fire until the fire department arrives to extinguish it (completely). In the best-case scenario, the extinguishing system can extinguish the fire independently.

[0007] The triggering mechanism of the extinguishing system can be mechanical, for example, by sealing the outlet openings with a glass ampoule or a fusible link designed to be destroyed by high temperatures, thereby releasing the extinguishing agent. In some embodiments, the extinguishing system can also be triggered manually, for example, by actuating a switch or opening a shut-off valve. In the fire protection systems according to the invention, the extinguishing system is typically triggered by the fire alarm system when it detects a (potential) fire event automatically or manually. The combination of a fire alarm system and an extinguishing system is hereinafter also referred to as a fire protection system.

[0008] It is of utmost importance that fire protection systems operate with high reliability and are also reliably capable of detecting (potential) fires and initiating appropriate measures. Therefore, it is the operator's responsibility to regularly inspect and / or maintain such fire protection systems.

[0009] Such inspections and / or maintenance are carried out by a user on site. It may happen that the fire protection system is located in a remote and / or difficult-to-access location. In such cases, short-notice inspections and / or maintenance visits are either impossible or extremely difficult to carry out. If a malfunction occurs, it can only be rectified with considerable time and effort, meaning that in such cases, the fire protection systems must essentially react autonomously. However, autonomous fault rectification is not always sufficient, and the deployment of maintenance personnel may still be necessary.

[0010] It is therefore advantageous to perform certain inspections and / or maintenance procedures remotely. According to current technology, this requires that the fire protection systems to be inspected / maintained in this way be designed from the outset for such remote inspection and / or maintenance. This presents further difficulties, because firstly, remote monitoring can only be carried out for fire protection systems specifically designed for this purpose, and secondly, individual components and / or peripheral devices in such fire protection systems can only be removed and / or added with considerable effort, as they would then have to be redesigned for remote monitoring.

[0011] In this context, WO 2011 / 076184 A1 describes a communication device that enables remote monitoring and / or maintenance of a security system, while also offering a modular design and thus retrofitting capability. This communication device is essentially "connected upstream" to the existing system, allowing the communication device and the system to operate independently, essentially acting autonomously. However, the functionalities of the communication device described in WO 2011 / 076184 A1 are limited to providing a communication link between a security system and a remote user. The communication device described in WO 2011 / 076184 A1 therefore merely acts as a "communication tunnel" for transmitting information from the security system to the user.While this enables remote verification, further functions, such as user-dependent access restrictions, cannot be guaranteed by the communication device of WO 2011 / 076184 A1.

[0012] US Patent 2008 / 084291 A1 concerns a method, a device, a remotely controlled accessory, and an authentication server for facilitating operations such as the authenticated testing of life safety equipment with components including a control panel and sensors. The life safety equipment must be tested in accordance with a fire safety regulation. An access procedure is performed to identify the equipment and the test requirements and to establish a communication session between the equipment and an authentication server during an authenticated test. Another access procedure is performed to enable access to a remote device to facilitate the authenticated test and to establish a communication session between the remote device and an alarm system or authentication server, etc.Information related to the impending activation of one of the sensors is received by the remote device. Information associated with the sensor's activation, when detected by the alarm system, is reported to the authentication server, and the reported activation information is then forwarded to the remote device. Authentication information associated with the activated sensor is received by the remote device, and an authenticated report is forwarded to the remote device once all alarm condition sensors have been tested according to the established procedures.

[0013] EP 3 095 098 A1 relates to a system and method for testing fire detection and alarm devices of a fire alarm system. The system includes a central operating system that establishes a connection between a control panel of the fire alarm system and a mobile computer operated by a technician. During a field test, the technician activates the fire detection or alarm devices of the fire alarm system. The activated devices signal the control panel, generating event data. This event data is sent from the control panel to the operations center for storage. The operations center then sends the event data to a mobile computer operated by a technician. The technician can then verify that the devices are physically intact, have not been tampered with, are functioning correctly, and are located in their designated positions.

[0014] EP 3 264 385 A1 concerns systems and methods for installing, commissioning, testing, and maintaining a fire alarm control panel via a mobile device. Some methods may include receiving a first signal from a fire alarm control panel, wherein the first signal contains identification information of the fire alarm control panel; transmitting a second signal containing the identification information to a server device; receiving a third signal containing a second piece of information from the server device; and displaying the second piece of information on a user interface device, wherein the second piece of information contains information for the installation, commissioning, testing, or maintenance of the fire alarm control panel.

[0015] For fire protection systems, however, it is desirable that a variety of different users with varying access rights can remotely access information about the system. According to current best practices, access rights are typically divided into four standardized authorization levels: the installer of the fire protection system, certified maintenance personnel, experienced users of the fire protection system (such as a suitably trained fire safety officer), and finally, inexperienced users.

[0016] If the user is an employee of a fire protection system installer who regularly checks the fire protection system, in particular to compare certain actual values ​​of the fire protection system and of peripheral devices contained therein with the expected target values, and / or to identify possible malfunctions at an early stage, and to carry out corresponding revisions in the event of such malfunctions and / or deviations, the user receives comprehensive access to as many aspects of the fire protection system as possible.

[0017] On the other hand, a user might also be a dispatcher who is certified and assigned to maintain the fire protection system. It is generally not desirable for a dispatcher to receive detailed information about the actual and / or target values ​​of the fire protection system and / or peripheral devices, nor detailed information about malfunctions and their possible causes. What is typically of interest to the dispatcher is which materials are needed for maintenance and what configuration of the fire protection system to expect. This allows the dispatcher to identify the workload and materials required without having to travel to the site beforehand, thus making maintenance more efficient and time-saving. Therefore, the user only has access to the portion of the system information—that is, the information about the fire protection system—that is relevant to these aspects.

[0018] Finally, a user can also be, for example, the customer themselves. A distinction is made here between the experienced user – in particular, the customer's fire safety officer – and the inexperienced user – for example, a customer employee with no experience in fire protection. In the case of the experienced user, they may be particularly interested in whether the fire protection system and its peripheral devices are operational and what their current status is. The experienced user is therefore granted access to the relevant system information. The inexperienced user, on the other hand, cannot work with the system information and should not be able to make any changes to the fire protection system's settings. Therefore, the inexperienced user is not granted access to the system information.

[0019] The data to be provided to each user can therefore vary. Often, while the data provided to all users is based on the same system information supplied by the fire protection system's central unit, it must be filtered and / or processed differently depending on the user. It is particularly advantageous to provide a system that allows for more individually configurable access rights for users—while still respecting, but independent of, the normative authorization levels—thus enabling a more granular assignment of access and roles to individual users. This makes it possible to establish role-based access permissions.

[0020] Against this background, an object of the invention is to provide a system for operating a fire protection system that overcomes the problems described above. In particular, an object of the invention is to provide communication between a fire protection system and a user's terminal device, by means of which the user can be adequately informed about the status of the fire protection system and / or the peripheral devices located therein. A further object of the invention is to provide a system that makes it possible to configure the access rights of individual users with a higher level of detail.

[0021] According to the invention, this problem is solved in a first aspect, according to independent claim 1, by a service device for a fire protection system comprising a communication device configured to communicate with a central device of the fire protection system via a first bidirectional communication link and to communicate with at least one user terminal device via a second bidirectional communication link in order to allow the user terminal device access to at least some system information of the fire protection system, and at least one computing device configured to receive the system information from the central device and to process it for transmission to the at least one user terminal device, and to receive at least one user input from the user terminal device in response to the transmitted system information.and to adjust the system information of the fire protection system based on at least one user input.

[0022] To solve the above problem, a service device is provided which can act as an additional data processing component between a central device of the fire protection system, in particular a central device of a fire alarm system, and at least one user terminal device.

[0023] The service device includes a communication device, such as a transmitter-receiver, configured to communicate bidirectionally with both the central device and the user terminal. This means the communication device is configured to establish an initial bidirectional communication link between itself and a corresponding central communication device of the central unit. Preferably, the service device is located at the site of the fire protection system. Communication between the service device's communication device and the central unit's communication device can be wired or wireless. Preferably, communication between the service device and the central unit is wireless.In some embodiments, wired communication can be provided as an alternative or additional option, particularly via a dedicated connection in the central device. Communication between the communication unit of the service device and the user terminal device is preferably wireless, but can also be wired. In some embodiments, communication between the communication unit and the user terminal device takes place, in particular, via a mobile network using a known mobile communication technology. In other embodiments, communication takes place via a different network.

[0024] The term "user terminal" as used below refers in particular to a laptop, mobile phone, smart glasses, or other terminal device that allows a user to view the transmitted system information. The user terminal is specifically configured to generate a graphical representation of the provided and processed system information in order to display it to the user.

[0025] In the following, the term "system information" refers to all types of data that describe the fire protection system and / or its peripheral devices and / or components. In particular, system information can include factory data, i.e., data that provides information about the hardware used, such as module designations, serial numbers, and the like. Alternatively or additionally, system information can also include operational data used for the operational configuration of the fire protection system, such as logic settings and configurable (changeable) parameters of the fire protection system and its associated peripheral devices. Alternatively or additionally, system information can also include supplementary data generated by the peripheral devices during the operation of the fire protection system, such as runtime data.At least some of this runtime data can also be used as status information, i.e., as data that is indicative of the (operational) state of the fire protection system.

[0026] The processing of system information can be understood, in particular, as processing depending on the user to whom the processed system information is provided. If the user is the installer, the system information is processed differently than if the user is a dispatcher or a customer. The user can be identified, in particular, via their user device. In some embodiments, identification may involve entering an access code and / or password when connecting the user device to the service device. Alternatively or additionally, identification may also include the acquisition of biometric data, such as a fingerprint or iris pattern, and identification based on this biometric data.Alternatively or additionally, the user can also be identified via a property of the user's terminal device and / or a subscriber identification module used within it. In some embodiments, identification can be independent of the user's terminal device.

[0027] Alternatively or additionally, processing the system information can include creating a log and / or a summary. In other embodiments, processing the system information can also include evaluating the system information to determine whether the fire protection system meets parameters specified by guidelines, such as approval and / or safety standards, or whether it operates within the limit values ​​specified by guidelines. In some embodiments, processing can also involve comparing the measured (actual) values ​​with corresponding target values ​​of the status information determined during operation, which, as part of the system information, is indicative of the condition of the fire protection system and / or the peripheral devices and / or components it contains.In any case, it is intended that the processing will be carried out in such a way that the system information is compiled for the respective user according to the role assigned to him / her.

[0028] If the user is, for example, the installer, logging can include, in particular, the logging of system information data relating to specific, guideline-defined testing activities—a type of maintenance log. Alternatively or additionally, such logging can include the comparison between measured (actual) values ​​and corresponding reference values ​​of the variable parameters in the status information, which are indicative of the condition of the fire protection system and / or its components and / or peripheral devices—a type of status log.In some embodiments, the evaluation of system information can serve, in particular, as a real-time check of the fire protection system, whereby the values ​​of the system information parameters, especially the status information parameters, are provided to the user in real time, and real-time messages, for example in the event of malfunctions or similar occurrences, are displayed. The processing can also include processing the system information, especially the status information, in such a way that the user is provided with documentation about the fire protection system, its historical development, and possible predictions for the future.

[0029] If the user is the dispatcher, the logging and / or summarization can include, in particular, a summary of the condition check and / or a summary of previous inspection and / or maintenance logs to give the dispatcher an overview of the workload required for the next maintenance / repair. In some embodiments, the user can also receive a summary and / or a list of the suggested materials required for maintenance based on the evaluation. Additionally, an evaluation result can be displayed so that the user can verify whether the list is complete. In some embodiments, the processing can also include generating an overview of the current configuration of the fire protection system—or of its individual components and / or peripheral devices.

[0030] If the user is an end customer, data processing can include, in particular, a summary of the current status of the fire protection system, or of its components and / or peripheral devices. In some embodiments, processing can also include filtering, so that the user is only shown the system information that might be of interest to them. In some embodiments, this applies in particular—in the case of a real-time display—to system information that deviates from the norm, especially status information that deviates from its reference values. In some embodiments, processing can also include the creation of test logs, maintenance logs, and / or maintenance reports. It is preferred that this logging includes less detailed information than, for example, in the case of the installer.The processing can further include summarizing the past values ​​of one or more parameters of the system information, in particular the status information. In some embodiments, the processing can also include evaluating and indicating and / or predicting an expected malfunction and / or a tendency for certain malfunctions.

[0031] The user terminal preferably includes a user input device for receiving user input. This device transmits the user input via the second bidirectional communication link to the communication device of the service unit, which in turn forwards the input to the computing unit. The computing unit is configured to process the user input and adjust the system information of the fire protection system accordingly.

[0032] In some embodiments, the user input includes in particular an operating log entry by a service technician, and the adaptation of the system information includes in particular adding this operating log entry to the test and / or maintenance logs and / or maintenance reports and / or other types of logging generated by the computing device on the basis of the system information, in particular the status information.

[0033] In some embodiments, the user input can also specify additional materials required for maintenance, and the computing system can be configured to determine which maintenance work is required based on these materials. In some embodiments, the adjustment based on user input can also include processing and / or providing additional system information. In some embodiments, the adjustment of system information can also include adjusting the configuration of one or more system parameters of the fire protection system and / or the peripheral devices and / or components located therein, so that a user can configure the fire protection system remotely, for example, because the user has recognized that such a configuration is necessary.The scope of the configuration and / or adjustment of the system information and / or system parameters may depend in particular on the respective user or their access rights and may be individually adjusted by the service device - i.e., independently of the four authorization levels specified by the standard.

[0034] In a preferred embodiment, the second bidirectional communication link is established to connect the communication device to the at least one user terminal device via a server component.

[0035] According to one embodiment, the communication device of the service device is configured to communicate with a server component, which in turn is configured to communicate with the user terminal. This means that bidirectional communication between the service device and the user terminal (or terminals) takes place via the server component. The server component can be configured to check the access rights of the user terminal on the one hand and the access rights of the service device on the other, and to allow access only if the check is successful. Alternatively or additionally, the server component can be configured to check the identification of the user terminal and / or the service device and to verify whether a specific user terminal is authorized to communicate with a specific service device.Here too, the server component can be configured to establish a connection only upon successful identification. This can increase security against unauthorized access.

[0036] In some embodiments, the server component can include, in particular, a data storage unit in which the system information can be stored. In this case, final storage of the system information in the service device is not necessary. Finally, at least part of the processing of the system information by a computing unit of the server component can also be taken over by the service device, especially if the server component includes a data storage unit for storing past system information. This has the advantage, firstly, of reducing the requirements placed on the service device, especially its internal storage unit.Secondly, storing system information on a server component allows the service device to be replaced, particularly in the event of a failure and / or malfunction, without first needing to transfer the data stored on it. Instead, a new service device can directly access the system information and other data stored on the server component and thus continue operating based on the state of the previously used service device.

[0037] According to a further preferred embodiment, the first communication link and / or the second communication link comprises an encrypted communication link.

[0038] In some embodiments, the bidirectional communication link between the central communication unit of the central device and the communication unit of the service device can be encrypted. Alternatively or additionally, the bidirectional communication link between the communication unit of the service device and the user terminal device can be encrypted. For this purpose, the service device, the central device, and the user terminal device can each include a cryptographic unit by means of which the system information is encrypted and then transmitted using known methods. In some embodiments, only the central device and the service device, or only the user terminal device and the service device, can include a cryptographic unit if only one of the two bidirectional communication links of the service device is to be encrypted.

[0039] The keys used to encrypt the initial bidirectional communication link between the central communication device and the communication device can also be used to authenticate the service device to the central device. In particular, the key can contain an authentication parameter that authenticates the service device to the central device and thus, for example, defines the service device's access rights.

[0040] Alternatively or additionally, the keys used to encrypt the second bidirectional communication link between the service device and the user terminal can also serve for authentication, allowing both the user terminal to authenticate itself to the service device and vice versa. In some embodiments, only the user terminal authenticates itself to the service device. Here, too, authentication can be performed via a corresponding authentication parameter within the encryption key. The authentication process can also be used to identify the user.

[0041] In some embodiments, the key can also be used to ensure that the software installed on the service device and / or the central device is licensed for the respective user. In some embodiments, this can be achieved by replacing the key after the expiration of a valid software license period and only providing a new key, or extending the previous key, upon re-purchase of the license. Preferably, this new key is directly provided to the user's terminal device used by the user who purchased the license.

[0042] It is further preferred that the service device also includes an identification device configured to transmit identification data of the service device to the central device and / or at least one user terminal device.

[0043] In some embodiments, the service device is also identified by a dedicated identification device. For this purpose, the service device includes a means by which it can identify itself, preferably by transmitting a corresponding identification number. This identification preferably takes place vis-à-vis the central unit of the fire protection system. Alternatively or additionally, the service device can also identify itself to one or more user terminal devices via the ID number.

[0044] In some embodiments, the identification device may also be configured to receive an identification number from the user terminal device and / or the central device, so that identification is bidirectional. In some embodiments, the identification number may also be transmitted only by the user terminal device and / or the central device, and the service device is not identified.

[0045] In some embodiments, the service device also includes a storage device for storing system information.

[0046] In some embodiments, the service device is equipped with a storage device, such as volatile and non-volatile memory. This storage device preferably serves to store system information. In some embodiments, the system information can be stored only on the service device. Alternatively or additionally, the system information can also be stored in a data storage device of the server component. In some embodiments, certain system information can be stored only in the storage device of the service device and certain system information only in the data storage device of the server component. In some embodiments, redundant storage takes place in the storage device of the service device and in the data storage device of the server component.This increases the flexibility of the system, as the service device in particular can be replaced without much effort, as well as the security of the storage, since if one storage device is destroyed, the information is still available in another storage device.

[0047] In a further development, the computing device is also configured to detect a difference between the system information stored in the storage device and the system information provided by the central device, and to adjust the system information in the storage device in response to this difference.

[0048] Not all system information is subject to temporal variations. Some system information, such as factory data, has (or should have) constant values ​​over a longer period or permanently. In this case, retransmitting a value for such system information, deleting the previous value, and saving the new (same) value again represents an unnecessary use of system capacity. To avoid such a waste of resources and reduce the amount of data to be transmitted, the computing unit of the service device is preferably configured to determine a difference between the system information stored in the storage device and the system information provided by the central device—that is, to determine which values ​​of which system information have changed.The computer is further configured to retrieve and rewrite to the storage device only those system information whose values ​​have changed. All other system information is not rewritten, optionally with a note indicating that it has remained constant.

[0049] According to further training, the computing device is set up to detect the difference when the first communication link between the central device and the service device is established.

[0050] In some embodiments, this comparison of system information and the associated determination of any differences preferably takes place during each (re-)establishment of the first communication connection between the central communication unit of the central device and the communication unit of the service device. This ensures that the service device saves the current state of the system information each time it reconnects to the central device.

[0051] In some embodiments, the storage device is further configured to store a first software identification of software data, wherein the computing device is further configured to read a second software identification from the central device via the first communication link, which is indicative of the software data on the central device, to compare the first software identification and the second software identification, and in response to a determination that the first software identification and the second software identification differ, to transmit the software data to the central device (200) via the first communication link.

[0052] The service device may also be configured to check the firmware version of the central device or a module contained therein and, if necessary, to update it.

[0053] For this purpose, the service device's storage unit is configured to store an initial software identification. In this context, an initial software identification is understood to be, in particular, an identification number that is indicative of a software version of software data. Software data, as defined here, refers to the data and codes that constitute the firmware. The initial software identification preferably specifies a current version of the software data.

[0054] A second software identification also refers specifically to an identification number that is indicative of a software version of software data. The software version specified by the second software identification is the version of the software data as it is currently installed and active on the central device or the corresponding module.

[0055] Preferably, when establishing the first bidirectional communication link between the central device and the service device, the first and second software identifications are compared by the service device's computing unit. If the software version specified by the second software identification, i.e., the version active on the central device or a module thereof, differs from the software version specified by the first software identification, the service device's computing unit is preferably configured to transmit the current software data to the central device via the bidirectional communication link using the communication unit. The software data can then be used to update the software version at the central device.

[0056] It is preferred that the current version of the software data is stored in the server component's data storage. This means that the service device retrieves this current software data from the server component's data storage and then transmits it to the central device. This ensures that the firmware is updated when the service device starts. The update can be triggered manually or automatically.

[0057] In some embodiments, this transmission includes first sending a request to determine whether a software version update is desired. In some embodiments, the service device transmits this request to the user terminal, and the user terminal generates an indication—which may be haptic, audible, visual, or similar—that an update is recommended. The user can then accept this request, resulting in the transmission of the software data, or decline it. In the latter case, the update is not performed. Alternatively or additionally, the service device may be configured to transmit this request to the central device. The central device may be configured to automatically check the request and, if an update is possible, accept it to initiate the update.Alternatively or additionally, the central device can be configured to issue an indication, which may be haptic, acoustic, visual, or similar, thus prompting a user of the central device to respond to the request. Here too, the update is executed in response to confirmation from the user.

[0058] The first and second software identifiers can also be provided in a manner other than through corresponding identification numbers. The only important point here is that the format of the first and second software identifiers allows for comparison between the two. Therefore, it is preferable to provide the first and second software identifiers in the same format.

[0059] In some embodiments, the service device further includes an indication device which is configured to issue an indication when the reception of the system information is complete.

[0060] An indication device can be understood as any type of device that provides a user with a perceptible indication that the system information to be provided has now been fully received. This indication can be haptic, audible, and / or visual. In some specific embodiments, the indication device is configured to provide both a visual and an audible indication. Alternatively or additionally, the indication device can be configured to transmit the indication to the user's terminal device, which is then configured to issue a corresponding notification.

[0061] In some embodiments, the system information includes at least one of the following: Data that includes information about at least one component of the fire protection system, and / or data that includes information about a setting of the fire protection system, and / or data that includes information about an operating state of the fire protection system.

[0062] As mentioned in the introduction, system information can be understood as all information about the fire protection system. In particular, system information can include data relating to at least one hardware component of the fire protection system. The term "component" is to be understood broadly here and encompasses both the individual peripheral devices of the fire alarm system, such as the various fire detectors, pumps, temperature sensors, circuit arrangements, and similar items, which can be identified as part of the system information, for example, by their serial numbers, and the components of the central unit, such as the individual modules that can be inserted into the central unit to perform specific tasks. This hardware-related data will also be referred to as "factory data" in the following.

[0063] Alternatively or additionally, the system information can also include data concerning the settings of the fire protection system. This includes, in particular, the adjustable parameters of the fire protection system and / or its peripheral devices, which can be set and, if necessary, adjusted during the configuration of the fire protection system. Furthermore, this data can also include logic settings of the logic elements of the fire protection system. Hereinafter, this data will also be referred to more generally as "operating data."

[0064] Alternatively or additionally, the system information can also include data concerning the operating status of the fire protection system. This data, also referred to as "runtime data" or "status information," pertains to supplementary data generated during operation that allows conclusions to be drawn about the operating status of the fire protection system. Parameters of the status information include, for example, the pressure of a pump or the pressure in the pipe system, the power consumption of the central unit, values ​​indicative of sensor contamination, and / or temperature data and / or similar information.

[0065] According to some embodiments, the computing device is further configured to check at least one user input and, in response to the check, to generate a check indication for transmission to the user terminal device.

[0066] In some embodiments, the service device's computing unit is configured to check and validate user input made in response to the displayed system information. Specifically, the computing unit is configured to check during validation whether the user input is permissible. In some embodiments, checking whether the user input is permissible means verifying whether the input relates to an aspect over which the user making the input has access and is authorized to influence it. For example, the installer of the fire protection system typically has more aspects to which they can make user inputs than the end customer.

[0067] The validation of user input can also be understood as checking whether the input is permissible in terms of content. In some designs, for example, the user can modify the adjustable parameters via user input, but these modifications may not comply with predefined limits. In this case, the computer system can, through this check, prevent the parameters from being adjusted based on user input that is not permissible for the fire protection system.

[0068] In the case of valid user input, the service device can issue a positive indication to the user via the user's terminal device, which includes, in particular, confirmation that the system information has been updated. In the case of invalid user input, the service device can issue an indication that the user input is not valid and / or an indication that the changes have not been made. Other indications are conceivable.

[0069] In some embodiments, receiving the at least one user input includes authentication of the user's terminal device. In some embodiments, the computing unit is further configured to determine the access authorization of the user's terminal device and / or to filter the system information transmitted to the user's terminal device based on that access authorization.

[0070] It can be advantageous for the service device to receive information about the user's terminal device's access rights to the central device and / or the server component. For this purpose, the service device preferably includes an authentication device as part of the computing unit, which is configured to authenticate the central device and / or the server component upon receiving system information. This allows the user to verify whether the system information has been transmitted correctly and completely by the correct central device and / or server component.

[0071] Alternatively or additionally, the authentication device can be configured to verify the validity of a license and, based on this verification, decide whether the user's device can access the service device and / or the server component. Access can be denied if the license has expired and granted if the license is valid or has been renewed. In this case, the central device can be configured to automatically recognize the service device upon establishing the first communication connection and provide it with all system information. Furthermore, the authentication device is configured to request a license key from the user's device upon establishing the second communication connection. In response to this request, the user's device transmits its license key via the second communication connection.The license key is then checked by the authentication system. If it is valid, the user's device is granted access to the service device. If it is invalid, access is denied. This denial may include a message indicating that the license key is no longer valid and may need to be renewed.

[0072] In some embodiments, the license key is provided to the user's device by an external server. For this to work, the user must connect to the external server and request the license key. The license key can then be provided permanently or for a limited time. In the latter case, the license key must be extended and / or renewed after a certain period. In some embodiments, this period is between one year and one day, in particular between 100 days and one day, and in particular 30 days. The external server can be provided, in particular, by the installer of the fire protection system and / or the server component. In some embodiments, the external server can also be provided as part of the server component, in which case the user's device has only limited access to the server component without a valid license key.

[0073] In some embodiments, user device authentication can serve not only to grant or deny access, but also to determine the scope of access for the user. In these embodiments, the computing unit is specifically configured to determine the user's access rights based on the authentication performed by the authentication unit and then to filter the system information according to these access rights. Thus, only specific system information is displayed to certain users. This has the advantage that the user is not overwhelmed with unnecessary information, and it also prevents unauthorized users from gaining access to, for example, the configuration data and logic settings of the fire protection system.

[0074] In a further embodiment, the communication device is configured to communicate with the fire protection system via the first bidirectional communication link in order to receive status information from the fire protection system that is indicative of a state of the fire protection system, wherein the computing device is configured to retrieve one or more comparison values ​​for the status information from the storage unit, to evaluate one or more values ​​of the status information based on a comparison with the one or more comparison values ​​for the status information and, based on the evaluation, to generate at least one status indication for the fire protection system.

[0075] In this embodiment, the service device receives status information via the communication link with the fire protection system, in particular the central device of the fire protection system, which is indicative of the state of the fire protection system.

[0076] The status information allows, in particular, conclusions to be drawn about the condition of the fire protection system, especially the condition of the components of a central unit, such as modules, and / or peripheral devices. The term "status information" refers specifically to the basic data that allows a statement to be made as to whether a peripheral device is still functioning correctly. Alternatively or additionally, the status information can also relate to information about the condition of a central unit and / or its components, such as the current power consumption of the central unit or an individual module within it, the battery charge level (determined via the battery resistance) of a battery in the central unit, and similar information.

[0077] This status information can be evaluated, particularly by the computing unit. The computing unit can be configured to generate a status indication based on this evaluation.

[0078] For this purpose, the computing unit is configured to retrieve one or more comparison values ​​from a memory. This memory can be configured as an internal storage device of the service unit, in which the comparison values ​​are stored. Alternatively or additionally, the service unit can also be configured to retrieve the comparison values ​​from an external memory, for example, via the communication unit, which then forwards the comparison values ​​to the computing unit. The external memory can, in particular, be configured as part of a server component, with the communication unit configured to access the external memory via a network. In other embodiments, the external memory can also be implemented as an external database that is connected directly to the service unit, either wirelessly or via cable.

[0079] The term "calibration values" refers specifically to target values ​​for the individual parameters contained in the status information. Calibration values ​​are therefore the values ​​that should be present for the respective status information to ensure that the peripheral devices—and thus the fire protection system—are functioning as specified. If the calibration values ​​deviate from the determined values, it can be concluded that problems and / or malfunctions have occurred in one or more of the peripheral devices within the fire protection system.

[0080] The calibration values ​​can be determined theoretically or empirically. This means that the calibration values ​​can either be calculated and written to memory as target values, or they can comprise the actual values ​​previously determined for the system and / or the fire protection system, which are stored in memory as calibration values. This means that if it has been established in the past that the system and / or the fire protection system is functioning, it can be assumed that the values ​​available at that time are suitable as calibration values ​​that are indicative of a functioning system.

[0081] The computer uses the calibration values, in particular, to evaluate the status information contained in the system information, based on a comparison between the actually determined values ​​of the status information parameters and the calibration values. This means the computer is configured to determine how far the current actual value deviates from the target value and to output a corresponding status indication that provides information about the condition of the fire protection system. The status indication is configured to show whether the fire protection system is functioning without malfunctions or whether malfunctions and / or faults can be detected for specific components. The status indication can be output to a user.

[0082] In some embodiments, the communication device is further configured to communicate with the central device of the fire protection system via the first bidirectional communication link, wherein the central device is in communicative connection with at least one peripheral device of the fire protection system.

[0083] The central unit can also be configured to communicate with at least one peripheral device of the fire protection system. For this purpose, the central unit can communicate with the peripheral devices either via the central communication unit, which also serves for communication with the service unit, and / or via a dedicated central peripheral unit within the central unit. In the latter case, the central peripheral unit should then be configured to communicate with the central communication unit in order to transmit the information received from the peripheral devices to the service unit.

[0084] The term "peripheral device" encompasses any type of sensor, detector, alarm (hazard detector, fire alarm), alarm device, emergency call system, or actuator, control and switching device for activating or deactivating devices such as fire suppression systems or air conditioning systems. Fire detectors can be automatic fire detectors, such as smoke detectors, heat detectors, flame detectors, spark detectors, fire gas detectors, or aspirating smoke detection systems. Fire detectors can also be designed as manual call points.

[0085] According to the invention, the following peripheral devices are provided in particular: Fire detectors, such as automatic fire alarms or manual fire alarms, as well as hazard detectors for recording event messages, fire alarms and faults, and / or limit switches used for position detection of, for example, ball valves, gate valves, butterfly valves, or similar devices, and / or pressure switches, and / or float switches for level measurements in, in particular, compressed air water tanks, unpressurized water tanks and / or other extinguishing fluid storage vessels, and / or temperature switches, for example, for monitoring the ambient temperature within the fire alarm system and / or the fire protection system; and / or pump pressure switches, for example, for starting pump motors in the event of a pressure drop in the extinguishing fluid-carrying pipeline network and / or in a fitting; and / or gas sensors; and / or actuators, such as horns, flashing lights, valves or similar devices.

[0086] This communication link between the central unit and the service unit, and between the central unit and peripheral devices, enables the transmission of status information indicative of the central unit's condition to the service unit, and conversely, the transmission of status information indicative of the peripheral devices' condition to the service unit. This allows for a comprehensive evaluation of the status information and thus a particularly accurate assessment of the fire protection system's condition.

[0087] In some embodiments, comparing one or more values ​​of the condition information with one or more comparison values ​​includes determining a threshold value for a deviation, wherein the computing device is further configured to generate a deviation indication when the threshold value is exceeded or fallen below, and to integrate the deviation indication into the condition indication. In one modification, the computing device is configured to output a maintenance indication in response to the deviation indication.

[0088] The target values ​​of the fire protection system are usually not limited to a single value, but rather range within a spectrum defined by corresponding upper and lower limits. These limits can be determined by guidelines. Alternatively or additionally, they can be calculated or empirically determined.

[0089] In some embodiments, these upper and lower limits are stored in the memory unit. The service device's computing unit is configured to read these limits and determine which limits should be used for each parameter within the status information. The computing unit is then configured to determine the value of the respective parameter within the status information and compare it with the upper and lower limits. If the parameter value is within the limits, the computing unit determines that everything is within the specifications. However, if the value exceeds the upper limit or falls below the lower limit, the computing unit determines that a deviation from the norm exists. In this case, the computing unit is configured to generate a deviation indication.The deviation indicator thus shows that a deviation exists for a specific value, meaning the value is no longer within the specified range. This deviation indicator can then be displayed haptically, graphically, and / or audibly. In some embodiments, the deviation indicator is specifically implemented as an alarm.

[0090] In some embodiments, particularly in the case of a graphical output of the deviation indication, this includes an indication of which value—or values—is affected by the deviation and whether the limit value has been exceeded or fallen below. In some embodiments, the deviation indication also includes an indication of the possible cause of the deviation.

[0091] In some embodiments, the computing unit is further configured to issue a maintenance indication in response to the deviation indication, i.e., a notification that maintenance of the fire protection system is necessary. The computing unit can, in particular, issue the maintenance indication to the central communication device, i.e., cause the communication device to transmit the maintenance indication to the central communication device. Alternatively or additionally, the computing unit can also issue the maintenance indication to a user terminal device, i.e., cause the communication device to transmit the maintenance indication to the user terminal device. The user terminal device preferably includes a graphical user interface on which a graphical representation of the maintenance indication can be displayed.

[0092] This allows for continuous monitoring of the fire protection system without the need for user interaction. The user is only informed when a potential fault or malfunction is automatically detected by the system.

[0093] In some embodiments, the communication device is further configured to transmit the status indication to the user terminal device via the second bidirectional communication link.

[0094] The service device can further be configured to transmit the status indication generated by the computing unit to the user's terminal device via its communication device and a bidirectional communication link. The status indication can then be displayed to the user on the terminal device. In some embodiments, the transmission of the status indication also includes the transmission of the status information, whereby the status information can be filtered, if necessary, depending on the user's authorization, meaning that not all status information is transmitted. The user's terminal device is specifically configured to generate a graphical representation of the status indication and to display this graphical representation to the user.

[0095] In some embodiments, the computing device is further configured to store the state information in the storage unit.

[0096] It is preferred that the computing unit be configured to store the status information received via the communication device in the internal or external storage unit after evaluation, optionally together with the generated status indication and a corresponding timestamp. Storing the status information, particularly with a timestamp, makes it possible to generate a history of the status information—and thus a status history of the fire protection system—over an extended period. This allows the long-term trend of the status information values ​​to be viewed. This can enable predictions about the condition of the fire protection system, especially about potentially occurring future malfunctions.

[0097] In some embodiments, the computing device is further configured to perform the evaluation of the status information based on user input.

[0098] It is preferred that the computing device be configured to consider user input when evaluating the status information. In this case, the user input may, in particular, be additional information about the status, such as the information that a specific peripheral device has been replaced, removed, or added—and therefore different values ​​are now present. In other embodiments, however, the user input may also be confirmation that the status information meets the user's expectations. In some embodiments, for example, the user can specify that a peripheral device should be replaced. The computing device will then include a corresponding note in the status indication when it is generated.

[0099] In some embodiments, the state information includes at least one of the following: Information that is indicative of the functionality of at least one alarm unit of the fire protection system; and / or information that is indicative of the condition of locking elements of the fire protection system; information that is indicative of the condition of switching elements of the fire protection system; and / or information that is indicative of the condition of the central device of the fire protection system.

[0100] The status information can include, in particular, parameters—or information—that indicate whether a detection unit, as a potential peripheral device of the fire protection system, is functioning correctly. Detection units typically include sensors for detecting fire characteristics. These sensors can become contaminated and / or damaged over extended periods. In a specific embodiment, the status information includes one or more values ​​indicating whether the detection units are still functioning reliably. This determination is preferably based on a comparison between the status information value (actual value) and a corresponding reference value (target value). In some embodiments, the actual values, which are indicative of contamination, can be stored over a longer period to monitor their development.This allows for early detection of a shift in the value, especially towards the limit value at which functionality is no longer possible.

[0101] The status information can also include parameters—or information—that indicate whether closure elements, such as dampers or similar devices, are functioning as peripheral components of the fire protection system and, if applicable, are in the specified position. For example, a parameter value in the status information can indicate the opening degree of a closure element. In a functioning fire protection system, each closure element must be in a specific position, which is linked to a specific opening degree. If a closure element's value deviates from this specified opening degree beyond certain tolerance limits, a malfunction can be assumed. Here, too, it is possible to record the values ​​over a long period in order to predict any trends for the individual closure elements and, if necessary, replace them before the permissible tolerance limits are exceeded.

[0102] The status information can also include parameters indicating the current switching position of the fire protection system's switching elements and / or whether any individual switching elements have shifted or deviated from their position. In a fire protection system, each switching element has a predefined position for its unactivated state. It must be verified that this position is actually maintained. Only in this way can it be ensured that the fire protection system functions correctly in the event of a fire. Here, too, the switching position of the individual switching elements can be tracked over time to identify potential trends.

[0103] The status information can further include parameters that indicate the status of the central unit of the fire protection system and / or its components, such as corresponding modules. Such a parameter could be, for example, the power consumption of the central unit and / or the resistance of a battery within the central unit. A change in the power consumption and / or resistance value could indicate a malfunction in the connected devices. This is because such devices might have a higher or lower power consumption and thus represent a changed load. Preferably, for status monitoring using the parameters mentioned above, the quiescent current of the central power supply (i.e., the power supply unit) of the central unit is determined and monitored over an extended period.If the quiescent current shows a shift, for example an increase, this either means that the fire protection system has been expanded with certain components, or that one or more components are malfunctioning. Therefore, a potential malfunction can also be predicted by observing the development of values ​​for a specific parameter within the status information over a longer period.

[0104] In some embodiments, the computing device is configured to receive at least one user identification from the at least one user terminal device and to authenticate the at least one user terminal device based on the at least one user identification.

[0105] User identification, in this context, refers to any type of identification used to identify the user device assigned to a specific user. For example, user identification can include a device identification number (DIN) of the user device. In other embodiments, user identification can also include a MAC address or a unique identifier generated, for example, based on the device ID and a user ID. In other embodiments, a subscriber identity module (SIM) or an electronic subscriber identity module (eSIM) can be used to authenticate the user device—or the corresponding user.

[0106] The term "authentication" here refers to the process of first identifying the user and then determining their authorization level, i.e., which system information should be made available to the user. In other words, authentication determines whether system information should be transmitted and, if so, which system information the user is permitted to receive.

[0107] This type of user identification and authentication ensures that only authorized users have access to relevant system information. Furthermore, it allows for a more granular subdivision of existing authorization levels, enabling the definition of more specific access permissions. This facilitates the implementation of individual and role-specific access rights for the fire protection system.

[0108] In some embodiments, the service device's communication unit is configured to transmit system information to the user's terminal device in response to its authentication. The authentication performed by the computing unit is thus preferably used to identify the user and determine which system information should be transmitted in this particular case and how it should be processed. This enables user-specific delivery of the relevant information.

[0109] In some embodiments, the service device further comprises an access restriction device configured to permit access by the at least one user terminal device to the central device if the at least one user terminal device can be authenticated and to prevent access if the at least one user terminal device cannot be authenticated.

[0110] Preferably, the service device includes an access control mechanism configured not only to restrict or grant access to system information based on authentication—that is, to provide specific users with only certain system information—but also to grant, restrict, and / or completely block access to the central unit of the fire protection system itself, particularly for configuring it, activating / deactivating specific functions, and similar tasks, based on authentication. For example, authentication by the service device's computing unit may reveal that the user is an installer of the fire protection system. In this case, the user receives unrestricted access to the central unit and its configuration.If authentication reveals that the user is a dispatcher, access to the settings of the central unit that need to be changed for maintenance work performed by the dispatcher can be restricted. However, if authentication reveals that the user is a customer, access to the central unit can be completely blocked unless the customer is intended to make changes to the fire protection system.

[0111] In some embodiments, the service device further comprises a verification device, wherein the communication device is further configured to communicate with a server component via a third bidirectional communication link, and the verification device is configured to receive access verification from the at least one user terminal device and, in response to the access verification, to cause the communication device to establish the third bidirectional communication link. In a further embodiment, the communication device is configured to transmit the system information to the at least one user terminal device by means of the server component.

[0112] In some embodiments, the service device can be configured to communicate with a server component, such as a cloud. For this purpose, the service device's communication unit is preferably configured to establish an additional bidirectional communication link with a server communication unit of the server component. Providing such a server component has the advantage that some of the service device's functionalities, such as storing system information in memory, can be offloaded to the server component, thereby reducing the capacity requirements of the service device. In some embodiments, however, the system information can also be stored both in a memory unit of the service component and in a data store of the server component to enable redundant storage of the relevant system information.

[0113] In any case, it is necessary to ensure that a user is authorized to use the server component. For this purpose, the service device includes a verification unit configured to verify that a user—identified by the user's terminal device—is authorized to use the server component. To this end, the verification unit is configured to receive access verification from the user's terminal device. The user's terminal device is configured to transmit this access verification to the service device's communication unit. The communication unit then transmits the access verification to the verification unit to verify the user. In some embodiments, user identification includes or is equivalent to access verification. In some embodiments, access verification may also be a dedicated signal.

[0114] The verification unit is configured to determine, based on access verification, whether the user has authorization to access the server component. If so, the verification unit enables the bidirectional communication link between the service device's communication unit and the server component's communication unit, allowing the user to utilize the server component's functionalities. If, however, the user lacks authorization, the verification unit does not grant access, and the unauthorized user cannot access the server component.

[0115] The verification mechanism is therefore configured to restrict, and in particular prevent, access to the server component by the service device with which the user communicates, especially if the user is not authorized to use the server component. In some embodiments, the user can obtain authorization, in particular by obtaining a server license that allows the user to use the server component. In some embodiments, the server license is time-limited. Alternatively or additionally, it can also be a permanently granted server license.

[0116] In some embodiments, the service device and the user terminal can also be configured to communicate not exclusively directly, but alternatively or additionally via the server component, after user verification and the corresponding authorization of the communication link between the service device and the server component. In this case, the server communication device of the server component is specifically configured to establish an additional bidirectional communication link to the user terminal. Communication between the service device and the user terminal can then take place directly and / or via the server component. Communication via the server component has the advantage that the server component can take over some of the functionalities of the service device without significantly increasing the data volume to be transmitted.

[0117] In some embodiments, at least one user identification includes an identity module of the user's terminal device.

[0118] The user device is preferably a mobile phone or a tablet. Such mobile phones or tablets are typically equipped with an identity module, in particular a subscriber identity module. (Subscriber Identity Module, SIM) Equipped for a mobile network. The subscriber identification module allows the user's terminal device to be identified on the mobile network. This functionality can also be used to identify the user by the service device. That is, the service device's computing unit is configured to identify the user using the (subscriber) identification module.

[0119] In some embodiments, the identity module, in particular the subscriber identity module, is set up as a programmable module. This allows software-based programming of the user identification.

[0120] In some embodiments, the service device further comprises an identification device which is configured to transmit identification data of the service device to the at least one user terminal device.

[0121] It is preferred that the service device identifies itself to the user terminal device. In some embodiments, the service device further comprises an identification device configured to transmit identification data to the user terminal device for the purpose of identifying the service device. In this embodiment, communication of system information and the like via the bidirectional communication link between the communication device of the service device and the user terminal device is only permitted once both the user terminal device and the service device have been authenticated by the user terminal device, i.e., once bidirectional identification has taken place. In some embodiments, the identification data is an identification number of the service device.This identification number can be processed by the identification device in such a way that it can be used by the user's terminal device to identify the service device and then transmitted to the terminal device. One advantage of this is that it is possible to subsequently determine which user terminal devices and which service devices were used in the system.

[0122] In some embodiments, the identification device can also be configured to identify the user terminal device based on user identification, either as an alternative or in addition to the computing device. Furthermore, in some embodiments, the identification device can be configured to identify the central unit and / or the server component. Other applications of the identification device are conceivable. This increases security.

[0123] In some embodiments, the computing device is further configured to generate a state log based on an evaluation of the system information, including the state information, and to store it in a storage unit.

[0124] Evaluating system information, including status data, can specifically involve creating a status log. This status log allows for determining whether the fire protection system meets parameters specified by guidelines, such as approval and / or safety standards, or whether it operates within the limit values ​​specified by guidelines. The status log is designed to compile system information for each user according to their assigned role.

[0125] If the user is, for example, the installer, the status logging can include, in particular, a log of those system information parameters that relate to specific testing activities prescribed by guidelines—in other words, a type of maintenance log. Alternatively or additionally, such a log can include a comparison of actual and target values ​​of variable parameters of the fire protection system or operating parameters of its components, such as peripheral devices or similar, and thus represent a type of test log.

[0126] If the user is the dispatcher, the condition log can include, in particular, a summary of previous inspection or maintenance logs to give the dispatcher an overview of the workload required for the next maintenance / repair. In some versions, the user can also be provided with a condition log based on the evaluation, which includes a list of the materials suggested for the maintenance. In some versions, the condition log can additionally include an evaluation result, so that the user can check whether the list is complete.

[0127] If the user is an end customer, the condition logging can include, in particular, the current status of the fire protection system and / or its peripheral devices. In some embodiments, the condition logging can also include test logs and / or maintenance logs and / or maintenance reports. It is preferred that these logs contain less detailed information than, for example, those of the installer. Furthermore, creating the condition log can include summarizing the past values ​​of one or more system information items, especially the status information.

[0128] In some embodiments, the computing device is configured to generate an evaluation result based on the evaluation of the state information, and the communication device is further configured to transmit the evaluation result, in particular together with the state information, via the third bidirectional communication link to the data storage of the server component, wherein the evaluation result is associated with a timestamp indicating when the state information was received.

[0129] In this context, an evaluation result is understood to be, in particular, a summary of the evaluation of the state information at a given point in time, namely the point in time at which this state information was received and evaluated. That is, the evaluation result includes a result of the evaluation for each parameter in the state information that was evaluated. In some embodiments, this may mean that the evaluation result determines that the values ​​of all parameters in the state information are within the specified range. However, in other embodiments, the evaluation result may also include one or more parameters in the state information whose values ​​deviate from the specified range. In this case, the evaluation result may state that the values ​​for parameters a to c are within the specified range, but not for parameters d and e.Alternatively or additionally, the evaluation result can also include a status indication that can be output to a user. This status indication is configured to show whether the fire protection system is functioning without malfunctions, or whether malfunctions and / or faults can be detected at specific locations. If, as mentioned above, the values ​​of parameters d and e are not within the specified range, the evaluation result can, for example, include a status indication that alerts a user to this deviation.

[0130] The evaluation result is preferably transmitted to the server component, whose data storage is configured to save the result. To track when the evaluation of the status information yielded the corresponding result, the result is timestamped. The result, along with the timestamp, is then written to the data storage. This process is preferably repeated at regular intervals. This allows the temporal development of the evaluation results to be tracked. This enables the identification of trends and developments in the fire protection system over a longer period and, potentially, the early prediction of developing faults and / or malfunctions.

[0131] In some embodiments, the status information is indicative of a state of at least one peripheral device of the fire protection system, wherein the evaluation result is further associated with a device index that is indicative of the respective peripheral device.

[0132] In some embodiments, the state information includes, in particular, values ​​for parameters that are indicative of the state of one or more peripheral devices. In this case, the evaluation result generated based on this state information can, in addition to a timestamp, also be associated with at least one device index, where the device index is indicative of the respective peripheral device for which the state information was received. Specifically, if the evaluation result includes the state information of peripheral devices A and B, this evaluation result is associated with the device indices of peripheral devices A and B in such a way that the evaluation result allows the result of the evaluation for peripheral device A to be uniquely assigned to peripheral device A, and the result of the evaluation for peripheral device B to be uniquely assigned to peripheral device B.In this way, the evaluation results provide a quick overview of the status of each peripheral device. Furthermore, the additional use of the timestamp allows the development of each peripheral device over time to be monitored based on the evaluation results.

[0133] In some embodiments, the user terminal can be used, in particular, to select a specific peripheral device and to provide the results for that specific peripheral device as a function of time from the time-stamped evaluation results. This allows for peripheral-device-specific provision of the status, especially in the form of a graphical representation.

[0134] In some embodiments, the computing unit is configured to generate a status log of the fire protection system based on the status information and the timestamp. In a further development, the status log comprises one or more status indications, deviation indications, and / or maintenance indications.

[0135] The service device's computing unit is also configured to create a status log. This status log is understood to mean, in particular, a summary of the evaluation results over time. This means that the timestamp associated with an evaluation result is used to summarize the temporal progression of the evaluation results over an extended period.

[0136] In some embodiments, the device index associated with a corresponding peripheral device can also be included in the generation of the status log. For example, the device index can be used to create a filter that allows the temporal evolution of the status results for a specific peripheral device to be provided by filtering out the other results. In other embodiments, the device index can also be used to select, for example, two identical peripheral devices and create a status log in which the states of the two peripheral devices are compared. Furthermore, additional indices, such as module identification numbers or similar, can be included in the generation of the status log, allowing a filter to be established specifically for these components and the corresponding status information to be filtered.This allows for a simplified and clearer overview of the condition of the fire protection system.

[0137] It is preferred that the status log be made available to the user. This can be done, on the one hand, via the user's device's display, which is configured, for example, to graphically represent the status log. This allows the user to view the status log remotely.

[0138] Alternatively or additionally, the status log can also be made available to the user via a central display unit of a central device. This central display unit can also be configured to generate and display a graphical representation of the status log. In this case, the user can view the status log on the central device.

[0139] In some embodiments, the condition logging also includes condition indication, deviation indication and / or maintenance indication.

[0140] The service device's computing unit can be configured to generate and output a status indication, a deviation indication, and / or a maintenance indication based on the evaluation of status information. The output is preferably provided to a user of the fire protection system. This output can be haptic, graphical, and / or audible.

[0141] The status indicator here refers to an indication of whether the fire protection system is functioning without malfunctions, or whether malfunctions and / or faults can be detected at specific locations. The status indicator can therefore be issued both when no fault is present and when a fault is present. In some embodiments, the status indicator is non-specific and simply indicates with a "yes / no" response whether the fire protection system is functioning without malfunctions or not. In other embodiments, however, the status indicator can be more specific and, for example, indicate where a fault is suspected.

[0142] The deviation indication specifically addresses situations where, during a comparison of the values ​​for certain parameters of the status information, it is determined that they deviate from the reference values ​​to an unacceptable degree. The deviation indication thus shows that a deviation exists for a specific value and that the value no longer falls within a predefined interval and / or deviates from a predefined specific reference value. In some embodiments, the deviation indication is preferably output in the form of an alarm. In other embodiments, the output can include a graphical or audible indication of which value—or values—is affected by the deviation and, if the deviation is outside the limits of a predefined interval, whether a limit has been exceeded or fallen below.In some embodiments, the deviation indication also includes a hint as to what the cause of the deviation may be.

[0143] In some embodiments, the computing unit is further configured to issue a maintenance indication in response to the deviation indication, i.e., a notification that maintenance of the fire protection system is necessary. The computing unit can, in particular, issue the maintenance indication to the central communication device, i.e., cause the communication device to transmit the maintenance indication to the central communication device. Alternatively or additionally, the computing unit can also issue the maintenance indication to a user terminal device, i.e., cause the communication device to transmit the maintenance indication to the user terminal device. The user terminal device preferably includes a graphical user interface on which a graphical representation of the maintenance indication can be displayed.

[0144] It is preferred that the output indicators, or a reference to their output, be stored in the server component's data storage, so that it is possible to trace which indicators were output by the service device even after the fact. This storage is preferably also done with a corresponding timestamp. If a status log is then generated based on the evaluation result and the timestamp, the references to the output indicators, also associated with their corresponding timestamps, are inserted into the status log. Preferably, the references to the indicators are integrated into the graphical representation of the status log so that the user can view them.

[0145] In some embodiments, the computing device is configured to receive a service path specification that indicates the order in which the state information should be evaluated, and to evaluate the state information according to the service path specification.

[0146] It can be advantageous to check certain parameters in the status information before checking other parameters, especially if there is a dependency between the individual parameters, for example, such that a deviation of one parameter from the norm would result in a deviation of another parameter. To prevent a fault from going undetected—because a deviation has already been found elsewhere—and / or to prevent incorrect conclusions from being drawn regarding the functionality of the fire protection system (because one parameter deviates from the norm due to the deviation of another parameter, even though the parameter in question has no influence on the fault), it is advisable to define a "service path" in such cases, i.e., to specify the order in which the parameters in the status information should be checked sequentially.This allows the important parameters to be identified early on, thus increasing the efficiency of the evaluation.

[0147] In a further aspect, according to independent claim 10, the invention relates to a fire protection system comprising a central device, wherein the central device (200) is configured to be communicatively connected with a service device as described above.

[0148] In a further aspect, according to independent claim 11, the invention relates to a system for operating a fire protection system comprising at least one service device according to one of the embodiments described above, at least one central device comprising a central computing unit, and at least one user terminal device, wherein the service device is configured to communicate with the central computing unit of the central device via the first communication link.

[0149] In a further aspect, the invention relates to a system for operating a fire protection system comprising a service device, a central device (for example, a central device of a fire alarm system), and at least one user terminal device. The central device may include a central processing unit. A central processing unit is understood to be, in particular, a computing unit within the central device that serves to perform data processing within the central device.

[0150] In some preferred embodiments, the central computing unit is designed, in particular, as a central card that is integrated into the central device or otherwise communicatively connected to it. In these cases, the first bidirectional communication link can preferably be established by a communication link between the central card and the service device. For this purpose, the service device can be connected to the central card either wirelessly or by means of a cable.

[0151] In one embodiment of the system, the service device is set up as an internal service module of the central device.

[0152] In some embodiments, the service device is designed as a type of box that can be externally connected to a central device, for example, via the central card. In other embodiments, however, the service device can also be designed as a module that is installed internally within the central device. The advantage of an internal module of the central device lies particularly in the fact that the first bidirectional communication link between the central device and the service device runs internally and is thus better protected against unauthorized access.

[0153] According to a further embodiment of the system, the central device comprises a central storage device for storing a second software identification that is indicative of the software data on the central device, wherein the at least one user terminal device is configured to receive a request to transmit software data from the service device and, in response to the request, to allow the transmission of the software data from the service device to the central device, wherein the central device is further configured to receive the software data transmitted by the service device.

[0154] In some embodiments, the second software identification, which is indicative of the version of the software data currently located on the central device and / or in one of its modules, is stored in a central storage device of the central device and transmitted to the service device upon request for comparison purposes. If the service device determines that the version of the software data indicated by the second software identification differs from that indicated by the first software identification, the service device generates a corresponding request to the user terminal, requesting permission to transfer the current software data to the central device. The user terminal is preferably configured to output the request to a user. The user can then evaluate and, if necessary, confirm the request.If the request is confirmed, the service device is configured to transmit the software data to the central device. The central device can then update its software data accordingly.

[0155] Alternatively or additionally, the service device can also send a request to the central device and, in response to its confirmation, initiate the transmission of the software data.

[0156] In one embodiment, the at least one user terminal device comprises a graphical user interface, wherein the graphical user interface is configured to display a graphical representation of the system information.

[0157] Such a graphical user interface can be implemented, in particular, as a web interface that allows access to individual aspects of the system information and, for example, enables users to switch between these aspects. This allows the display to be made particularly clear and user-friendly.

[0158] According to one embodiment, the system comprises at least one peripheral device of the fire protection system, wherein the system information is indicative of a state of the at least one peripheral device of the fire protection system, and wherein the service device is configured to generate, based on an evaluation of the system information, at least one state indication of a state of the at least one peripheral device and / or the fire protection system.

[0159] In a further aspect, according to independent claim 14, the invention relates to a method for operating a fire protection system, in particular for maintaining and / or checking a fire protection system, wherein the method comprises the following steps: transmitting system information via a first bidirectional communication link from a central device of the fire protection system to a service device, processing the system information by the service device, transmitting at least part of the system information via a second bidirectional communication link to at least one user terminal device in order to allow the user terminal device access to at least that part of the system information of the fire protection system, receiving at least one user input from the user terminal device in response to the transmitted system information, and adapting the system information of the fire protection system based on the at least one user input.

[0160] According to one embodiment, the method further comprises: receiving, by the central device, system information from one or more peripheral devices of the fire protection system, wherein the system information is indicative of a current state of one or more peripheral devices of the fire protection system; evaluating, by a computing unit of the service device, the system information and generating a status indication based on the evaluation. In a further development, the method further comprises: transmitting the status indication from the service device to the at least one user terminal device and outputting, by the at least one user terminal device, the status indication to a user.

[0161] The method according to the invention takes advantage of the benefits and preferred embodiments of the service device and the system according to the invention. The preferred embodiments and further developments of the service device and the system for operating a fire protection system are therefore also preferred embodiments and further developments of the method, for which reason reference is made to the above explanations.

[0162] The invention is described in more detail below with reference to the accompanying figures and preferred embodiments. These figures show: Fig. 1 a schematic representation of a system for operating a fire protection system of a first embodiment, Fig. 2 a schematic representation of a system for operating a fire protection system according to a modification of the first embodiment, and Fig. 3 a flowchart of a method for maintaining and / or checking a fire protection system according to an embodiment, Fig. 4 a schematic representation of a system for operating a fire protection system according to a second embodiment, Fig. 5 a schematic representation of a system for operating a fire protection system according to a modification of the second embodiment, Fig. 6 a flowchart of a method for condition monitoring of a fire protection system according to an embodiment, Fig. 7 a schematic representation of a system for operating a fire protection system according to a third embodiment, Fig.Fig. 8 a schematic representation of a system for operating a fire protection system according to a modification of the third embodiment, Fig. 9 a flowchart of a method for authenticating a user in a system for operating a fire protection system according to one embodiment, Fig. 10 a schematic representation of a system for operating a fire protection system according to a fourth embodiment, Fig. 11 a schematic representation of a system for operating a fire protection system according to a modification of the fourth embodiment, and Fig. 12 a flowchart of a method for monitoring the condition of a fire protection system according to one embodiment.

[0163] The Figure 1 Figure 1 shows a system 1 according to the invention for operating a fire protection system 10 comprising a service device 100, a central device 200 of the fire protection system 10, a server component 300 and a user terminal device 400.

[0164] The service device 100 comprises a communication device 101, a computing device 102, an identification device 103, a storage device 104, and an indication device 105. The computing device 102 further comprises an authentication device 110.

[0165] The fire protection system 10 comprises a central device 200 and a multitude of peripheral devices 601, which are communicatively connected to the central device 200 (not shown). Even if in the schematic representation of the Fig. 1 Although only three peripheral devices 601 are shown, the fire protection system can include 10 more or fewer peripheral devices 601.

[0166] The central device 200 comprises a central communication unit 201, a central computing unit 202, a central display unit 203, and a central storage unit 204. The central communication unit 201 is communicatively connected to the communication unit 101 of the service device 100 via a bidirectional communication link 501. The central communication unit 201 is also connected to the central computing unit 202 and the central storage unit 204 via a communicative link located in the central device 200. This allows system information stored in the central storage unit 204 to be transferred to the service device 100. In some embodiments, the central computing unit 202 is configured to process the system information itself and only then transmit it to the service device 100.Alternatively or additionally, the central computing unit 202 can also be configured to transmit the system information directly to the service device 100 without processing, but also to process it for display on the central display unit 203 and transmit it to the central display unit 203 for display.

[0167] Service device 100 is configured to receive system information via the bidirectional communication link 501. To this end, communication device 101 first establishes the bidirectional communication link 501 to the central communication device 201. Communication device 101 receives an identification number from identification device 103 to identify service device 100 and transmits this number to the central communication device 201, which in turn forwards it to the central computing device 202. The central computing device 202 uses the identification number to identify service device 100 and, in response to the identification, provides the system information that is (temporarily) stored in the central storage device. This information is then transmitted to communication device 101 via the central communication device 201.When the transmission is complete, this is registered by the communication unit 101. This prompts the indication unit 105 to issue a corresponding indication of the complete transmission of the system information. In the specific example of the... Fig. 1 The indication is a visual as well as an acoustic indication.

[0168] The communication device 101 then forwards the received system information to the computing device 102. In the specific embodiment of the Fig. 1 This system information includes, in particular, status information, i.e., data that is indicative of the (operational) state of the fire protection system 10 and the components and / or peripheral devices 601 located therein. This status information is generated, in particular, during the operation of the fire protection system 10.

[0169] The computing unit 102 is configured to process this system information, including the status information, for transmission to the user terminal device 400. For this purpose, the communication unit 101 is configured to communicate with a server communication unit 301 of the server component 300 via a bidirectional communication link 503 in order to access the data storage 302 of the server component 300. In the specific embodiment of the Fig. 1The data storage unit 302 contains a series of target values ​​as comparison values ​​for the values ​​of the corresponding parameters in the status information. The computing unit 102 is configured to read these target values ​​from the data storage unit 302, in particular to retrieve them via the bidirectional communication link 503, and to evaluate the runtime data based on the target values. The computing unit 102 is further configured to transmit the appropriately processed system information, optionally together with an evaluation result and / or a status indication, to the user terminal 400 via a bidirectional communication link 502.

[0170] In some embodiments, the user terminal 400 is first authenticated when the bidirectional communication connection 502 between the service device 100 and the user terminal 400 is established. For this purpose, the computing unit 101 includes an authentication unit 110. In the exemplary embodiment according to Fig. 1Authenticating the user device 400 includes, in particular, verifying that the user of the user device 400 possesses a valid license key. After the communication connection 502 is established, the authentication device 110 sends a request for a license key. In response to the request, the user device 400 transmits a corresponding license key, preferably via the communication connection 502, which is then checked by the authentication device 110. If the license key is successfully verified, i.e., if it is valid, the authentication device 110 issues a positive authentication indication and the communication is enabled.If the license key fails the verification, meaning it is no longer valid, authentication device 110 issues a negative authentication message, and the user is denied access to the service device and therefore to the system information it provides. This negative authentication message may be displayed on the user's device, prompting them to request a new license key and / or renew their existing one. This ensures that users with a valid license can only access the system information.

[0171] The user terminal 400 comprises a graphical user interface 401 that allows a user to view the processed system information and, in response, to make at least one user input. In the specific embodiment of the Fig. 1For example, based on an evaluation of the status information in the system data, the user is notified that a pump within fire protection system 10 is no longer operating at sufficient pressure. This notification can preferably be conveyed to the user in the form of a status indication, including a deviation indication. Optionally, the user also receives a maintenance indication that the pump needs to be repaired or replaced.

[0172] Furthermore, the user who has received the maintenance indication on their user terminal 400 can optionally enter a user input confirming that the maintenance indication has been received and, if applicable, indicating that the possible problem with the pump will now be resolved by appropriate maintenance or inspection.

[0173] Based on this user input, the transmitted system information is then adjusted. In particular, it is recorded that the user has been informed about the possible pump malfunction and, if applicable, what measures should be taken. These additionally entered comments are then saved as part of the adjusted system information. In the implementation of the Fig. 1This storage preferably takes place in the data storage 302 of the server component 300. In other embodiments, however, the storage can also take place in a storage device 104 located on the service device 100. Storage in the data storage 302 of the server component 300 is advantageous, however, because, firstly, the storage device 104 located in the service device 100 can be relieved of its load, and secondly, the storage allows the use of a different service device than the service device 100. Thus, even in the event of a malfunction of the service device 100, all data relating to the fire protection system 10 can be accessed immediately.Finally, storage in the data storage 302 of the server component 300 is also advantageous insofar as, for example, the operator of the server component 300, who may be the installer of the fire protection system 10, can access the server component directly, i.e. without service device 100, in order to subject the data to further evaluation.

[0174] In the embodiment according to the Fig. 1System 1 for operating the fire protection system 10 comprises a service device 100, which is configured to communicate directly with the central device 200, the server component 300, and the user terminal 400 via the communication device 101. Although not shown, the central communication device 201, the communication device 101, and the server communication device 301 each include a cryptographic device for encrypting the data exchanged between the communication devices. This improves the security of the data transmission.

[0175] The Figure 2 shows a system 1' for operating a fire protection system 10 according to a modification of the first embodiment of the Fig. 1 . Here too, System 1' again comprises a service device 100, a central device 200, a server component 300 and a user terminal 400, all of which, as in connection with Fig. 1The described functionality works as follows, where the same reference numbers denote the same components. Since these functionalities correspond to the execution according to... Fig. 1 Since this corresponds to the above, a further detailed explanation is omitted here.

[0176] Therefore, the following will only address the differences between System 1 according to Fig. 1 and System 1' according to the modification in Fig. 2 received. In the specific embodiment of the Fig. 2The service device 100 communicates with the user terminal 400 via communication link 101 through the server component. This means that instead of direct communication via the bidirectional communication link 502 between the service device 100 and the user terminal 400, communication is established via the server component 300. The service device 100 communicates with the server component via the bidirectional communication link 503, and the server component communicates with the user terminal via the bidirectional communication link 504. In other words, the communication link between the service device 100 and the user terminal 400 is formed by communication link 503 and communication link 504.This enables the provision of some, partly optional, functionalities, such as the storage of system information and / or the identification of the user from the service device 100 to the server component 300, thus reducing the system requirements for the service device 100.

[0177] Even if the service device 100 is in system 1 and 1' according to the embodiments of the Fig. 1 and the Fig. 2 Although the service device 100 is shown as an external component, it should be mentioned here that it can also be configured as an internal module of the central device 200 without requiring any adjustments to the described functionalities. The service device 100 according to the invention can therefore be designed either as an internal (pluggable) module of the central device 200 or as a connectable, external element.

[0178] The Figure 3Figure 10 schematically shows a flowchart of a method according to the invention for operating a fire protection system 10, in particular for maintaining and / or checking a fire protection system 10. In step 1000, the bidirectional communication link 501 is established between communication device 101 of the service device 100 and central communication device 201 of the central device 200. This setup optionally includes identifying and / or authenticating the service device.

[0179] In step 2000, the communication unit 101 of the service device receives the system information from the central communication unit 201 of the central device 200 and forwards it to the computing unit 102 in step 3000. In step 3001, the computing unit 102 prepares the system information for transmission to the user terminal 400. In the specific embodiment of the Fig. 3The user of the user terminal device is an installer, and the processing accordingly includes an evaluation of the system information to determine whether all system tests have been carried out correctly and confirm the system's operational capability.

[0180] In step 4000, the processed system information is transmitted to the user terminal 400+. In the specific embodiment of the Fig. 3 The transmission process initially involves establishing a bidirectional communication link between service device 100 and user terminal 400 and corresponding authentication, as in connection with the Fig. 1 described.

[0181] Following the receipt of the processed system information, the user terminal 400 generates a graphical representation of the system information in step 4001 and displays it to the user of the user terminal 400. In step 4002, the user makes at least one user input in response to the displayed system information. The user terminal 400 receives this user input and transmits it, optionally together with an association to the corresponding system information, to the communication device 101 of the service device 100.

[0182] In step 5000, the communication device 101 receives the user input and transmits it to the computing device 102, which adjusts the system information in step 600 based on the user input and optionally writes the adjusted system information to a memory location. This memory location can be, in particular, the memory device 104 of the service device and / or the data storage 302 of the server component.

[0183] The Figure 4 Figure 1 shows a system 1 according to the invention for operating a fire protection system 10 according to a second embodiment. The system 1 comprises a service device 100, a central device 200 of the fire protection system 10, a server component 300 and a user terminal device 400.

[0184] The general system architecture of system 1 according to the second embodiment corresponds to that of system 1 according to the first embodiment, as described in connection with Fig. 1described. Here too, the service device 100 comprises a communication device 101, a computing device 102, an identification device 103, a storage device 104 and an indication device 105.

[0185] The fire protection system 10 comprises a central device 200 and a multitude of peripheral devices 601, which are communicatively connected to the central device 200 via a bidirectional communication link 505. Even if in the schematic representation of the Fig. 4 Although only a single peripheral device 601 is shown, the fire protection system can include 10 more or fewer peripheral devices 601.

[0186] The central device 200 comprises a central communication device 201, a central computing device 202, a central display device 203, a central storage device 204 and, additionally, a central power supply 205.

[0187] The central communication unit 201 is communicatively connected to the communication unit 101 of the service unit 100 via a bidirectional communication link 501. Within the central unit 200, the central communication unit 201 is connected via a first communicative link to the central computing unit 202, which in turn is connected to the central storage unit 204 and via a second communicative link to the central power supply 205. This internal communication allows the central communication unit 201 to collect status information about the state of the central unit 200 in order to transmit this information, as part of the system information, to the communication unit 101 of the service unit via the bidirectional communication link 501.This status information can, for example, be transmitted from the central power supply 205 to the central communication unit 201 and may relate to, for example, the current power consumption of the central device 200 and / or a component thereof, such as a module, and / or the internal resistance of the batteries within the central device 200 and / or the modules. Based on the current power consumption and / or the internal resistance, it is possible, in particular, to infer defects within the fire protection system 10.

[0188] Furthermore, the central communication unit 201 can be configured to receive status information indicative of the condition of the peripheral devices 601. For this purpose, the peripheral devices 601 can be configured to communicate directly with the central communication unit 201. Alternatively or additionally, the peripheral devices 601 can also communicate with the central device 200 via the central computing unit 202 or a dedicated communication link to transmit the status information. This status information can, for example, relate to the degree of contamination of a sensor in a peripheral device 601, such as a detector.

[0189] The central communication unit 201 is configured to transmit status information, as part of the system information, to the communication unit 101 of the service device 100 via the bidirectional communication link 501. For this purpose, the communication unit 101 first establishes the bidirectional communication link 501, whereby the service device 100 can optionally identify itself to the central device 200, as described in the context of Fig. 1described. In some embodiments, the bidirectional communication link 501 remains permanently maintained after initial setup in order to transmit system information, including status information, from the central communication unit 201 to the communication unit 101. This allows continuous monitoring of the fire protection system's status by monitoring and, optionally, evaluating the status information on the service device 100 and / or the associated user terminal 400.

[0190] The communication device 101 transmits the status information to the computing device 102. In the specific embodiment of the Fig. 4The status information pertains in particular to the current power consumption within the central device. The computing unit 102 is configured to instruct the communication unit 101 to retrieve a target value for power consumption from the data storage 302 of the server component 300 via a bidirectional communication link 503 with a server communication unit 301 of the server component 300. Alternatively, the computing unit 102 can also be configured to retrieve the target value from the storage unit 104 of the service device 100, if such a value is stored there.

[0191] The computer 102 thus receives one or more reference values ​​that are indicative of the central device 200's past power consumption and can use these reference values ​​to evaluate the value transmitted with the current status information. For example, the computer 102 can detect an increase in power consumption and generate a corresponding status indication showing that the power consumption of the central device 200 has increased. The user can then check whether the increase in power consumption is due to the addition of, for example, peripheral devices 601 to the fire protection system 10, or whether no peripheral devices 601 have been added and the increase was therefore caused by other factors, such as an impending defect.

[0192] In the specific embodiment of the Fig. 4The service device 100 is further equipped to transmit the status indication to the user terminal device 400 via the bidirectional communication link 502.

[0193] The user terminal 400 includes a graphical user interface 401. The user terminal 400 is configured to generate a graphical representation of the status indication based on the status information and display this to the user on the graphical user interface 401. This allows the user to remotely detect any malfunctions that may have occurred or are yet to occur and to initiate appropriate countermeasures, such as repair or maintenance, replacement of components, or similar actions.

[0194] User actions for initiating countermeasures can be defined, particularly depending on the user or their role. For example, a customer whose fire protection system 10 has been installed can initiate a countermeasure that includes calling certified maintenance personnel. If the user is a dispatcher responsible for maintenance, they can, in response to the status indicator, gather the necessary materials for maintenance and / or repair, plan the work accordingly, and then initiate it. If the user is the installer, they can, for example, plan and initiate maintenance and / or repair themselves or dispatch appropriately certified maintenance personnel to carry it out. In any case, the status indicator allows the user to take the appropriate action.

[0195] The Figure 5shows a system 1' for operating a fire protection system 10 according to a modification of the second embodiment of the Fig. 4 . Here too, System 1' again comprises a service device 100, a central device 200, a server component 300 and a user terminal 400, all of which, as in connection with Fig. 4 The described functions work, with identical reference numbers denoting identical components. Therefore, the following discussion will again focus solely on the differences between System 1 according to... Fig. 4 and System 1' according to the modification in Fig. 5 received.

[0196] In the specific embodiment of the Fig. 5The communication device 101 of the service device 100 is configured to communicate directly with one or more peripheral devices via the bidirectional communication link 506. This means that the communication device 101 of the service device 100 receives status information about the status of the central device via the bidirectional communication link 501 and status information about the status of the peripheral devices 601 via the bidirectional communication link 506. This enables a time-separated transmission of the status information and thus allows for more efficient timing of the transmission.For example, the status information indicative of the state of the central device 200 can be transmitted permanently, while the status information indicative of the state of the peripheral devices 601 can be transmitted only at regular intervals, the intervals of which can be chosen, for example, depending on the requirements of the respective peripheral device 601 and / or the guidelines specified for it.

[0197] Also in the Fig. 4 and 5 The service device 100 is shown as an external component, but can also be set up here as an internal module of the central device 200 without having to adapt the described functionalities.

[0198] The Figure 6 Figure 1 schematically shows a flowchart of a method according to the invention for operating a fire protection system 10, in particular for monitoring the condition of a fire protection system 10 according to the Fig. 4In step 1000', the bidirectional communication link 501 is established between communication device 101 of service device 100 and central communication device 201 of central device 200. In step 2000', communication device 101 of service device 100 receives the status information, which is indicative of the state of the fire protection system 10, from central communication device 201 of central device 200 and forwards it to the computer device 102 in step 3000'. In step 3001', computer device 102 initiates a retrieval of the comparison values ​​for the status information from a memory. For this purpose, computer device 102 can, in particular, instruct communication device 101 to read these values ​​from the data memory 302 of the server component.

[0199] In step 3002, the computing unit 102 receives the calibration values ​​and uses them to evaluate the status information. Based on this evaluation, which may include, in particular, comparing a value of a status information with the corresponding calibration value, the computing unit 102 then generates a status indication in step 3003 and instructs the communication unit 101 to transmit this status indication, optionally together with the status information and / or the system information, to the user terminal 400 via the bidirectional communication link 502.

[0200] Following the receipt of the status indication, the user device generates a graphical representation of the status indication in step 4000', optionally together with a graphical representation of the status information and / or the system information, and displays this to the user of the user device. In step 4001', the user initiates an appropriate action in response to the status indication if the status indication suggests such an action is necessary to prevent a malfunction. This allows for early fault detection and thus preventive maintenance and / or repair of the fire protection system.

[0201] The Figure 7Figure 1 shows a system 1 according to the invention for operating a fire protection system 10 according to a third embodiment. Here too, the system 1 again comprises a service device 100, a central device 200 of the fire protection system 10, a server component 300 and a user terminal device 400 and thus resembles the system architecture of the system according to the first and second embodiments.

[0202] The service device 100 comprises a communication device 101, a computing device 102, an identification device 103, a storage device 104, and an indication device 105. Compared to the embodiments according to the Figures 1, 2, 4 and 5 The service device 100 also includes an access restriction device 106 and a verification device 107.

[0203] The user terminal 400 comprises a graphical user interface and an identity module 402, which is preferably designed as a participant identity module.

[0204] The fire protection system 10 and the server component 300 essentially correspond to the embodiments according to the Fig. 4 This means that the fire protection system 10 comprises a central device 200 and a variety of peripheral devices 601, of which in the Fig. 7 However, only one is shown again, with the peripheral devices 601 being communicatively connected to the central device 200 via a bidirectional communication link 505.

[0205] The communication device 101 of the service device 100 is configured to communicate with the central communication device 201 of the central device via a bidirectional communication link 501. Furthermore, the communication device 101 of the service device 100 is configured to communicate with the user terminal device 400 via a bidirectional communication link 502.

[0206] Unlike the first and second embodiments, in the third embodiment the service device 100 comprises an access restriction device 106, which is configured to restrict the user's access to the information from the central communication device 201 via the bidirectional communication link 502, and in particular to prevent the transmission of system information via the bidirectional communication link 502 to the user terminal device 400 as long as the user has not first been authenticated.

[0207] This means, in particular, that the user terminal 400 only receives the system information from the fire protection system 10 via the service device 100 once the user has been successfully authenticated. In the specific embodiment of the Fig. 7For this authentication, an identity module 402 is used, which issues a user identification and transmits it to the computing unit 101 of the service device 100 via the bidirectional communication link 502. The bidirectional communication link 502 is enabled for the transmission of the user identification.

[0208] The computer unit 102 is configured to receive user identification, in particular from the identity module 402, and to determine whether the user identification can be assigned to an authenticated user of the service device 100 and / or the fire protection system 10. If this is the case, the computer unit 102, by issuing a release signal, instructs the access control device 106 to open the bidirectional communication link 502 between the communication device 101 and the user terminal 400, also for the transmission of system information and / or status information. In this case, the system information is then transmitted from the service device 100, or rather from its communication device 101, to the user terminal 400 as described above.

[0209] If the user cannot be authenticated, the computing unit 102 instructs the access restriction unit 106—either actively by transmitting an explicit signal or passively by omitting the release signal—to maintain the access restriction. In this case, no system information can be transmitted from the service device 100 to the user terminal 400.

[0210] In the Figure 7The service device 100 further includes a verification device 107, which is configured to restrict and, in particular, prevent the service device 100's access to the server component 300 if the user cannot be verified. This allows verification, prior to accessing the server component 300, of whether a user has authorization to access it. Such authorization can be understood, in particular, as a server license, which the user must first acquire to use the server component 300. Only after acquiring the server license can the user then utilize the additional capacity of the server component 300.

[0211] The verification device 107 is further configured to receive access verification from the user terminal device 400, in particular via the communication device 101. In some embodiments, the access verification is implemented as part of the identity module 402. Alternatively or additionally, the access verification can also be designed as a separate signal.

[0212] Based on this access verification, the verification unit 107 determines whether the user is authorized to access the server component 300 via the bidirectional communication link 503. If so, the verification unit 107 enables the bidirectional communication link 503, allowing it to be established. The user can then utilize the functionalities of the server component 300. If not, the verification unit 107 prevents the enabling—and thus the establishment—of the bidirectional communication link 503. This prevents unauthorized users from accessing the server component 300.

[0213] The Figure 8 shows a system 1' for operating a fire protection system 10 according to a modification of the third embodiment of the Fig. 7. Here too, System 1' again comprises a service device 100, a central device 200, a server component 300 and a user terminal 400, all of which, as in connection with Fig. 7 The described functions work, with identical reference numbers denoting identical components. Therefore, the following discussion will again focus solely on the differences between System 1 according to... Fig. 7 and System 1' according to the modification in Fig. 8 received.

[0214] In the specific embodiment of the Fig. 8 The communication device 101 of the service device 100 is configured to communicate with the user terminal device directly, via the bidirectional communication link 502, and indirectly, via the server component 300, i.e., the bidirectional communication links 503 and 504. In the specific embodiment of the Fig. 8This means, in particular, that the bidirectional communication link 502 is used to transmit the user identification from the user terminal device 400, especially its identity module 402, to the communication device 101, which then transmits this user identification to the computing device 102. The computing device 102 authenticates the user terminal device 400 as described in the context of the Fig. 7 described.

[0215] If the user is identified as an authenticated user based on user identification, the computing unit 102 is configured to instruct the access restriction unit 106 to grant the user terminal device 400 access to the system information, as also described in connection with the Fig. 7described. In this case, enabling access means, in particular, enabling access of the user terminal device to the bidirectional communication link 503 and the bidirectional communication link 504. This means, in the embodiment according to the Fig. 8 The system information is not transmitted via the bidirectional communication link 502, but rather via the bidirectional communication links 503 and 504, i.e., via the server component. This allows, firstly, the user device 400 to be verified even without access to the server component 300, and secondly, it enables part of the processing and / or evaluation of the system information to be outsourced to the server component 300.

[0216] Although the service device 100 is again shown here as an external component, the third embodiment according to the Figs. 7 and 8can be set up as an internal module of the central device 200 without having to adapt the described functionalities.

[0217] The Figure 9Figure 1 schematically shows a flowchart of a method according to the invention for operating a fire protection system 10, in particular for access control of a fire protection system 10. In step 1000, the bidirectional communication link 501 is established between the communication device 101 of the service device 100 and the central communication device 201 of the central device 200 of the fire protection system 10. In step 2000, the bidirectional communication link 502 is established between the communication device 101 and the user terminal device 400. For this purpose, in step 2001, the communication device 101 receives at least one user identification from the user terminal device 400 and transmits this in step 2002 to the computing device 102, which identifies the user based on the user identification and determines in step 2003 whether the user is authenticated.

[0218] If this is the case ("J"), the computing unit 102 issues a release signal to the access control unit 106 in step 2004, which instructs the access control unit 106 to allow the communication of system information to the user terminal 400. In this case, the user terminal 400 receives the system information and / or status information in step 3000 that it is authorized to receive according to its access rights – for example, determined based on authentication.

[0219] If this is not the case ("N"), the computing unit 102 refrains from outputting the release signal in step 2005" and no system information is output to the user terminal 400.

[0220] The Figure 10Figure 1 schematically shows a system 1 according to the invention for operating a fire protection system 10 according to a fourth embodiment, again comprising a service device 100, a central device 200 of the fire protection system 10, a server component 300 and a user terminal device 400.

[0221] The service device 100 comprises a communication device 101, a computing device 102, an identification device 103, a storage device 104 and an indication device 105.

[0222] The fire protection system 10 comprises the central device 200 and a variety of peripheral devices 601, which are communicatively connected to the central device 200 via a bidirectional communication link 505.

[0223] The communication device 101 of the service device 100 is configured to communicate with the central communication device 201 of the central device 200 via a bidirectional communication link 501 in order to receive system information, including status information indicative of the state of the fire protection system 10 and / or the peripheral devices 601 located therein. Furthermore, the communication device 101 of the service device 100 is configured to communicate with the server component 300 via a bidirectional communication link 503.

[0224] In the embodiment according to the Fig. 10The communication device 101 of the service device 100 thus receives at least one value for a parameter of the status information that is indicative of the status of the fire protection system 10 and / or one or more of the peripheral devices 601. The communication device 101 is configured to transmit the status information to the computing device 102, which is configured to evaluate the status information and generate an evaluation result based on the evaluation. In some embodiments, this evaluation result includes, in addition to the evaluated status information, further system information.

[0225] The evaluation result is then transmitted via the bidirectional communication link 503 to the server component 300, where it is received by the server communication device 301 and subsequently prepared for insertion into the data storage 302. This preparation can include, in particular, adding a device index to the evaluation result, which indicates the respective component tested for its condition, for example, a module of the central device 200, a peripheral device 601 of the fire protection system 10, or similar, as well as a timestamp for better temporal traceability and increased protection against misuse.

[0226] This means that in system 1 of the Fig. 10The evaluation result, i.e., the evaluated status information, optionally including system information, is written to data storage 302. This allows a user, especially the installer and / or certified maintenance personnel, to regularly check the system and verify whether all maintenance work has been carried out completely and on time. This enables the automated creation of maintenance logs. In an alternative embodiment—for example, in a case without access to the server component 300—the evaluation result and / or system information can also be stored in the storage device 104 of the service device 100. This eliminates the need for a server component 300.

[0227] In any case, the evaluation result can be viewed by a user via user terminal 400 – possibly after prior authentication. In particular, user terminal 400 can be configured to generate a graphical representation of the evaluation result and / or the maintenance log and display it to the user. This gives the user an immediate overview of the current maintenance status of system 1.

[0228] Figure 11 concerns a modification of system 1 according to the Fig. 10 Here too, identical reference symbols signify identical components, whose functionalities will not be discussed in detail below. The difference between System 1 of the Fig. 10 and the system 1' of Fig. 11 The issue lies in the manner in which communication takes place between user terminal device 400 and service device 100. According to the Fig. 10The user terminal 400 communicates directly with the service device 100, or the communication unit 101, via the bidirectional communication link 502. Therefore, the user terminal 400 must access the evaluation result stored within the data storage 302 by means of the service device 100.

[0229] In contrast, the user terminal 400 communicates in the system 1' of the Fig. 11 The evaluation result is retrieved via the bidirectional communication link 504 with the server component. In this embodiment, communication—both for retrieving the evaluation result and for viewing the system information as described above—is always routed through the server component 300. This makes it possible to transfer certain evaluation and calculation processes from the service device 100 to the server component 300, thus creating a service device 100 with limited computing resources.

[0230] The Fig. 12 The diagram schematically shows the flowchart for a procedure for operating, in particular monitoring and maintaining, a fire protection system 10 in a system such as, for example, in the Fig. 10 depicted.

[0231] In step 1000, the bidirectional communication link 501 is established between communication device 101 of service device 100 and central communication device 201 of the central device 200 of the fire protection system 10. In step 1001, the peripheral devices 601 transmit corresponding status information, indicative of their state, to the central device 200 via the bidirectional communication link 505. In step 1002, the central communication device 201 transmits all system information, including the status information indicative of the state of the peripheral devices 601 and / or the central device 200, to the communication device 101 of the service device 100 for further evaluation.

[0232] In step 2000, the communication unit 101 transmits the system information thus obtained to the computing unit 102 for evaluation and the creation of an evaluation result, as well as, optionally, a status indication, deviation indication, and / or maintenance indication. In step 2001, the computing unit 102 evaluates the system information, in particular the status information, and generates an evaluation result based on this evaluation. The computing unit 102 is configured to then add a device index to this evaluation result, which specifies the corresponding component, for example, the corresponding peripheral device 601, for which corresponding status information was available and for which it was therefore possible to determine the status based on an evaluation of this status information.Furthermore, the computing unit 102 is configured to add a timestamp to the evaluation result, indicating when the status information was received. The processed evaluation result is then transmitted in step 2002 to the server component 300 via the communication unit 101 and the bidirectional communication link 503.

[0233] In step 3000, server component 300 receives the evaluation result and transmits it, along with additional information such as the device index and timestamp, to data storage 302 within server component 300. The evaluation result is stored there and can then be used for further evaluation – as a kind of current or historical value. In step 3001, server component 300 generates a status log before saving the evaluation result. This status log can be generated based on the status information, the device index, and the timestamp.

[0234] In step 4000, the evaluation result and / or the status log generated in this way is then transmitted to the user terminal 400 via a bidirectional communication link. In step 4001, the user terminal 400 creates a graphical representation of the evaluation result and / or the status log and displays it to the user on the graphical user interface. The user can then visually verify whether the maintenance was carried out correctly and what changes have occurred compared to the last maintenance cycle. Reference symbol list: System for operating a fire protection system 1, 1' Fire protection system 10 Service device 100 Communication device 101 Computer facility 102 Identification device 103 Storage device 104 Indication facility 105 Access restriction setup 106 Verification facility 107 Authentication device 110 Central device 200 Central communication facility 201 Central computing facility 202 Central display unit 203 Central storage facility 204 Central power supply 205 Server component 300 Server communication setup 301 Data storage 302 user device 400 Graphical user interface 401 Identity module 402 Communication link 501, 502, 503, 504, 505, 506 Peripheral devices 601

Claims

1. A service device (100) for a fire protection system (10), comprising a communication device (101), and at least one computing device (102), wherein the communication device (101) is configured to communicate with a central device (200) of the fire protection system (10) via a first bidirectional communication link (501), in order to receive system information from the central device (200) via the first bidirectional communication link (501) and to transmit system information to the at least one computing device (102), and wherein the communication device (101) is further configured to communicate with at least one user terminal (400) via a second bidirectional communication link (502), wherein the at least one computing device (102) is configured to process the system information, to obtain processed system information, and to make the processed system information available for transmission to the user terminal (400); and wherein the communication device (101) is further configured to grant the user terminal (400) access to at least part of the processed system information of the fire protection system (10) via the second bidirectional communication link (502), wherein the at least one computing device (102) is configured to receive at least one user input from the user terminal (400) in response to the at least part of the processed system information, and to perform adjustment of the system information of the fire protection system (10) based on the at least one user input, characterized in that the at least part of the processed system information, the user terminal (400) is granted access to, is determined based on an access authorization of a user, wherein the access authorization allows assigning the user terminal to a specific access authorization category of a plurality of access authorization categories, wherein the access authorization category allows determining which portion of the at least part of the processed system information the user terminal is granted access to.

2. The service device (100) of claim 1, wherein the second bidirectional communication link (503; 504) is configured to connect the communication device (101) with the at least one user terminal (400) via a server component (300); and / or wherein the first communication link (501) and / or the second communication link (502; 503; 504) comprises an encrypted communication link.

3. The service device (100) according to any of the previous claims, further comprising an identification device (103) that is configured to transmit identification data of the service device (100) to the central device (200) and / or to the at least one user terminal (400).

4. The service device (100) according to any of the previous claims, further comprising a memory device (400) for storing system information.

5. The service device (100) according to claim 4, wherein the memory device (400) is further configured to store a first software identification of software data, wherein the computing device (102) is further configured to: - read, via the first communication link, a second software identification from the central device (200), such second software identification being indicative of the software data on the central device (200), - compare the first software identification and the second software identification, and - in response to determining that the first software identification and the second software identification differ, to transmit the software data to the central device (200) via the first communication link.

6. The service device (100) according to any of the previous claims, further comprising an indication device configured to output an indication when the receiving of the system information by the communication device is complete.

7. The service device (100) according to any of the previous claims, wherein the system information comprises at least one of the following: - data comprising information about at least one component of the fire protection system (10), and / or - data comprising information about a setting of the fire protection system (10), and / or - data comprising information about an operating state of the fire protection system (10).

8. The service device (100) according to any of the previous claims, wherein the computing device (102) is further configured to check the at least one user input and, in response to the checking, generate a check indication for transmission to the user terminal (400).

9. The service device (100) according to any of the previous claims, wherein the computing device is further configured to determine an access authorization of the at least one user terminal (400), and to filter the system information being transmitted to the user terminal (400) based on the access authorization.

10. A fire protection system comprising a central device (200), wherein the central device (200) is configured to be communicatively connected to a service device (100) according to at least one of claims 1 to 9.

11. A system (1, 1') for operating a fire protection system (10), comprising: at least one service device (100) according to at least one of claims 1 to 9, at least one central device (200) of the fire protection system (10) comprising a central processing device (202), and at least one user terminal (400), wherein the service device (100) is configured to communicate with the central processing device (202) of the central device (200) via the first communication link (501).

12. A system (1, 1'), according to claim 11, wherein the central device (200) comprises a central memory device for storing a second software identification indicative of software data on the central device, wherein the at least one user terminal (400) is configured to receive a request for the transmission of software data from the service device (100) and, in response to the request, to allow a transmission of the software data from the service device (100) to the central device (200); wherein the central device (200) is further configured to receive the software data transmitted from the service device (100); and / or wherein the at least one user terminal (400) comprises a graphical user interface (401), wherein the graphical user interface (401) is configured to display a graphical representation of the system information.

13. System (1, 1') according to at least one of claims 11 or 12, further comprising at least one peripheral device (601) of the fire protection system (10), wherein the system information comprises state information indicative of a state of the at least one peripheral device (601) of the fire protection system (10), and wherein the service device (100) is configured to generate at least one state indication of a state of the at least one peripheral device (601) and / or the fire protection system (10) on the basis of an evaluation of the state information.

14. A method for operating a fire protection system (10), comprising the following steps transmitting system information via a first bidirectional communication link (501) from a central device (200) of the fire protection system (10) to a service device (100), receiving the system information by the service device (100), processing the system information by the service device (100), to obtain processed system information; transmitting at least part of the processed system information via a second bidirectional communication link (502) to at least one user terminal (400) to allow the user terminal (400) to access the at least part of the system information of the fire protection system (10), receiving at least one user input from the user terminal (400) in response to the at least part of the processed system, and adjusting the system information of the fire protection system (10) based on the at least one user input, characterized in that the at least part of the processed system information, the user terminal (400) is granted access to, is determined based on an access authorization of a user, wherein the access authorization allows to assign the user terminal to a specific access authorization category from a plurality of access authorization categories, wherein the access authorization category allows to determine to which portion of the at least part of the processed system information the user terminal is granted access to.

15. The method according to claim 14, further comprising: receiving system information by the central device (200), wherein the system information is indicative of a current state of the one or more peripheral devices (601) of the fire protection system (10), evaluating the system information by a computing device (102) of the service device (100), and generating a state indication of a state of the at least one peripheral device (601) and / or the fire protection system (10) by the computing device (102) based on the evaluation.

16. Use of a service device (100) according to any of claims 1 to 9 for operating a fire protection system (10).