HK40038887B - Method for allocating a smoke alarm to be registered and a corresponding smoke alarm management system - Google Patents

Description

The invention relates to a method for assigning a smoke detector to be registered and a corresponding smoke detector management system. A method for assigning a household appliance to a user profile by means of a mobile device is known, for example, from US 2015 / 339634 A1. Another method for assigning a smoke detector to a user profile by means of a mobile device is known from WO 2015 / 054254 A1. A method for assigning an Internet of Things device to a user is known from US 2018/0324170 A1.

The installation of smoke alarms is required by law in many places. In general, maintenance and inspection of installed smoke alarms are provided every 12 months to ensure that they are functional in the event of an emergency. However, a traditional on-site inspection is time and cost-intensive. Remote maintenance, e.g. verification of functional suitability, e.g. by an appropriate smoke alarm management system, is therefore desirable, so that the on-site inspection only needs to be carried out if the smoke alarm actually fails or the smoke alarm is replaced.

However, this requires a secure and reliable registration or allocation of the smoke detectors to the respective users or user profiles of the smoke detector management system, for example to avoid the allocation of the respective smoke detector to the wrong user or user profile, as otherwise a reference to a necessary smoke detector exchange cannot be properly delivered or a smoke detector cannot be detected as defective.

A method for linking a smoke detector to a user of a smoke detector management system is known from DE 10 2014 014 106 A1 whereby the smoke detector is assigned to the user by the user sending several confirmation data to the smoke detector management system at a time interval specified by the smoke detector management system via controls mounted on the smoke detector, i.e. the assignment is done by the user pressing a control, such as a button, of the smoke detector several times at the right time.

Err1:Expecting ',' delimiter: line 1 column 360 (char 359)

The present invention is therefore intended to provide a method for the assignment of a smoke detector to be registered to a user profile of a smoke detector management system which achieves a safe, reliable and simple assignment. This task is solved by the method of claim 1.

Accordingly, a procedure for assigning a smoke detector to be registered to a user profile of a smoke detector management system is established, which consists of the following steps: a data connection between the smoke detector and a server of the smoke detector management system, whereby the smoke detector is directly connected to the server via narrowband Internet of Things, and transmits first identification data of the smoke detector to be registered to the server via the data connection between the smoke detector and the server, whereby the first identification data has an alphanumeric code uniquely assigned to the smoke detector;Establishes a data connection between a mobile device and the server;Logs in to the user profile via the mobile device using user identification data uniquely assigned to the user profile;Transmits second identification data of the user profile via the user profile of the registered smoke detector to the corresponding identification data server;Inserts the identification data of the first or second device and the identification data of the user profile via the mobile device and the second or third user profile;

The method according to the invention is characterised in particular by the fact that a login to the user profile is made by means of the mobile device using the user identification data and second identification data are transmitted from the smoke detector to the mobile device. The subsequent transmission of the second identification data by the mobile device to the server thus allows the server to clearly assign the smoke detector to the logged-in user profile. The server can have at least one communication interface for data exchange with at least one smoke detector and the mobile device at least one. The smoke detector and the mobile device can interface for data exchange and/or data exchange with the server. The smoke detector/smoke detector management system of the server can therefore be particularly advantageous and can result in a cloud-based management system.

After identifying the smoke detector and assigning the smoke detector to the user profile, position and/or address data can be assigned to the smoke detector assigned to the user profile. For example, the smoke detector may have a GNSS module for capturing position data. The address data may be, for example, a country, a city, a street address, a building number, a floor number, a room number or similar and/or any combination thereof. The position and/or address data can be assigned to the server-side storage. However, it is also provided that the smoke detector has a data storage unit for storing the respective data. If the smoke detector is assigned a location/address, these data can be accessed and/or modified.It may be provided that, after the smoke detector has been assigned to a user profile, the respective position and/or address data are stored on the server and/or the smoke detector and subsequently assigned to the smoke detector. However, it may also be provided that the respective position and/or address data are stored on the server and/or the smoke detector before the smoke detector is identified and assigned to the smoke detector after the smoke detector is identified. It may be provided that the storage of the position and/or address data for several smoke detectors is not sequential but essentially parallel, for example by means of an appropriate data format or a benchmark list. In particular, if the smoke detectors are to be assigned to a single filter, it may be provided that the location and/or address data for several smoke detectors are not sequential but essentially parallel, for example by means of an appropriate data format or a benchmark list.This allows for a flexible and convenient allocation of location and/or address data, since the smoke detectors only need to be linked to the data already stored and the need to store separate data sets for each individual smoke detector is eliminated. Similarly, the installation of several smoke detectors can be facilitated by having their location and/or address already determined before they are installed. The allocation of address data to the smoke detectors is particularly advantageous as it allows the smoke detectors to be conveniently divided into groups. For example, several smoke detectors can be allocated to the same street address and building but differ in room number.

It may be envisaged that some of the steps of the procedure are carried out in different order, for example, the second identification data of the smoke detector to be registered may be transmitted first to the mobile device and/or the second identification data and/or user identification data may be transmitted by the mobile device to the smoke detector management system server before the first identification data of the smoke detector are transmitted to the smoke detector management system server.

The smoke detector can detect smoke by measuring the concentration of suitable smoke components or combustion gases, e.g. carbon monoxide, by temperature measurement and/or optical detection and trigger an alarm. The smoke detector can have an acoustic indicator, e.g. a siren or a loudspeaker, to trigger the alarm. It is also conceivable that the alarm can be triggered additionally or instead optically, e.g. by LEDs. The smoke detector can include a GNSS sensor module for location or position measurement and/or location location information. The smoke detector can detect additional sensors for monitoring the surroundings, e.g. a heater or an infrared sensor, and/or a smoke detector for monitoring the smoke field.

The user identification data may include a user name, a pin, an alphanumeric code, an e-mail address, an electronic fingerprint or fingerprint, an electronic signature and/or a photo. The first and/or second identification data of the smoke detector have a clearly assigned alphanumeric code. In addition, the first and/or second identification data may contain information regarding the type of smoke detector or manufacturer, location, address or postal data of the smoke detector.

The connection of the smoke detector to be registered to the smoke detector management system server and the transmission of the first identification data may be carried out, for example, by pressing a button on the smoke detector, but it may also be provided that the first identification data is transmitted from the smoke detector to the server by the smoke detector itself after the connection to the server has been established.

Logging in can be done via a computer program, app or GUI stored on the mobile device. After logging in, for example, a user can tell the server that a smoke detector should be added to the logged-in user profile. If a computer program, app or GUI is used to log in, the second identification data can be transmitted from the computer program, app or GUI to the server. In an execution form, the first identification data can be transmitted to the server after a connection is established between the smoke detector and the mobile device.

It may be provided that the first and second identification data are identical.

This can facilitate the identification of the smoke detector to the logged-in user profile, since a comparison of the first and second identification data or a check for a match may be avoided.

The mobile device may be wirelessly connected to the server, preferably via a mobile network, preferably via narrowband Internet of Things (Narrowband IoT), at least during the transmission of the data concerned. The smoke detector may have a suitable module, such as a SIM card. It may be provided that both the smoke detector and the mobile device are connected to the server in the same way, e.g. both via narrowband Internet of Things (Narrowband IoT). This ensures that only the network selected for the registration of the smoke detector is available, while two different connections may be available on different networks.

Since the smoke detector is directly connected to the server, no additional gateway is needed. It can be ensured that the mounting point of the smoke detector does not have to be in the reception and transmission area of another gateway. This can facilitate the mounting and assignment of the smoke detector to be registered.

The second identification data can be transferred to the mobile device either: The use of a QR code on the smoke detector or a pictogram or alphanumeric code on or with the smoke detector or using an image recognition software or a wireless connection between the smoke detector and the mobile device.

If a computer program, app or GUI is used for logging in, the computer program, app or GUI may, after logging in and/or communicating a registration intent to the server, for example, prompt the user to scan a QR code affixed to the smoke detector or to enter an alphanumeric code. It may also be provided that the mobile device automatically detects the smoke detector if it is in sufficient proximity. The smoke detector and/or mobile device may be configured to automatically transmit the second identification data. It may be provided that the user must confirm the second identification data collected from the mobile device.

Before the smoke detector is assigned, an authorisation request may be sent from the server to the mobile device. If a computer program, app or GUI is used for log-in, this authorisation request may be communicated to the user by the computer program, app or GUI. It may be provided that the registration or assignment of the smoke detector to the user profile can only be completed or completed if the user confirms the authorisation request.

After the smoke detector has been assigned to a user profile, the smoke detector may be assigned to at least one other user profile, either by analogy with the above procedure or by modifying the allocation data stored on the server.

where there is a change in the allocation data stored on the Smoke Detector Management System server, it may be provided that the user whose user profile has been allocated to the smoke detector logs in and, for example, assigns or shares another user profile with the associated smoke detector via the computer program, app or GUI. It may be provided that, after allocation to a user profile, the assigned smoke detector is allocated to a smoke detector group and/or smoke detector subgroup. It may be provided that, after allocation to a smoke detector group and/or smoke detector subgroup, the allocation to a smoke detector group and/or smoke detector group is made, other user profiles may be allocated to at least one of the assigned smoke detectors via the mobile device server and may also be provided for the allocation of the data to be modified by means of a separate allocation.

The smoke detector can periodically transmit status data and/or operating data and/or first identification data and/or second identification data to the server after being assigned. The status data can include, for example, status messages of the smoke detector, such as whether it is active or an alarm is present, which firmware is played or includes a sensor state or battery state if applicable. For example, if an object is located near the smoke detector or is placed near it, the smoker can capture it and communicate with the server via a possible environmental sensor. The evaluation of the status data can be done by the server or smoke detector.The data transmitted to the server can be stored on the server in such a way that it is accessible to the user profile associated with the smoke detector. It can be provided that the transmitted data can be accessed by the mobile device, preferably by means of the computer program, the app or the GUI. It is preferable that the data transmitted from the smoke detector to the server be transmitted at least once every 24 hours, preferably at least once every 12 hours.In particular, it may be provided that in the event of an alarm, the smoke detector does not wait until the next periodic transmission time but immediately transmits the relevant data to the server.

Err1:Expecting ',' delimiter: line 1 column 409 (char 408)

The invention also relates to a smoke detector management system having at least one smoke detector and at least one server, whereby at least one user profile is stored on the server, whereby the server is connected to at least one smoke detector for data exchange, whereby the server is preferably cloud-based, whereby the server is configured to store data received from the smoke detector and make it accessible to a user profile assigned to the smoke detector, whereby the server has a communication interface configured to establish a direct narrowband connection via Internet of Things with a device to be registered and a data connection with a mobile device, whereby the server is configured to generate the first identifier by means of which the registered smoke detector receives a unique identifier, and whereby the second identification is recommended to be transmitted by the first communication interface to the registered smoke detector, and whereby the server is configured to receive the first identifier by means of a unique identifier, which is recommended to be transmitted by the second communication interface to the registered smoke detector, and the second identification is recommended to be transmitted by the first communication interface to the registered smoke detector, which is recommended to be transmitted via the second identification code.

The mobile device can be connected to the server wirelessly, preferably via a mobile network and particularly preferably via narrowband Internet of Things (Narrowband IoT).

The server may be connected to at least one computer device for data exchange, where the computer device may be configured to download, manipulate, add new data to or access data from or access data received from the respective smoke detector and stored on the server using user profile uniquely identifying user identification data. The computer device may be a mobile device, such as a laptop, smartphone, PDA or tablet. The computer device may be another server, a desktop PC, a UI, a microcontroller, an integrated circuit, an FPGA or similar, or run on a wired server. The computer may be connected to a computer server, a computer or a GUI.

In particular, a smoke detector can be associated with several user profiles and/or user profile groups. In other words, users assigned to the user profile group can access at least one user profile on the same smoke detector. Users who are not assigned to the user profile group cannot access the user profile of the user groups assigned to smoke detectors. In most cases, users are so integrated that several user profiles are assigned to the same user profile group and several user profiles are assigned to the smoke detector group.B. can share access to the same smoke detectors. However, it can also be provided that a user profile group includes only one user profile with a smoke detector associated with the user profile. A user profile can be associated with several user profile groups. If a user profile associated with one user profile group is associated with another user profile group, it can be provided that the user profile can be associated with the user profiles of the other user profile group.it may be provided that this smoke detector is also automatically assigned to all other user profiles in the user profile group, or that the user and/or an administrator may assign to the smoke detector assigned to it only selected user profiles, resulting in a further user group consisting of the user profile or administrator and the selected user profiles.

At least one of the user profiles associated with a user profile group may have administrator rights at least in relation to the user profile group. It may be provided that only the administrator may add or remove user profiles to a user profile group. It may be provided that only the administrator may manipulate the respective settings and operating parameters of the smoke detectors associated with the user profiles of the user profile group, or grant or restrict such rights to certain user profiles of the user profile group. It may be provided that the administrator may allow or restrict access to the user profiles associated with the user profile group to the smoke detectors or the data received from the smoke detectors, as appropriate.

The number of user profile levels may be unlimited in principle, the classification, promotion or degradation of the respective user profiles to a given hierarchical level may be provided only by user profiles assigned to a higher hierarchical level, and super-administrators or system administrators may be provided who have administrator rights over several or even all user profile groups stored on the server.

The smoke detector management system may have an evaluation unit capable of identifying an alarm and/or maintenance incident from the data transmitted by the smoke detector, whereby in the event of an alarm the server may send an alarm message and/or in the event of maintenance a maintenance message to the user profiles assigned to the smoke detector. The alarm message may also be sent by the smoke detector to the server and by the server to the user profiles assigned to the smoke detector. It may also be provided that the alarm message is sent only to the administrator of the respective user profile group assigned to the smoke detector or to user profiles specified by the administrator. The alert message may be sent to a user profile, in particular by:Err1:Expecting ',' delimiter: line 1 column 143 (char 142)that an alert occurs when the smoke detector's smoke inlet chamber is blocked or contaminated, for example by dust collections, or when a threshold is exceeded. Preferably, the alert message shall be tailored to the alert. For example, if address data is stored, the alert message may contain it. It may be provided that the alert message contains at least part of the data transmitted by the relevant smoke detector or communicates it in an appropriate manner.

The evaluation unit can, for example, evaluate the condition of each smoke detector using the status data transmitted by the smoke detector and determine whether or to what extent the respective smoke detector needs to be serviced or replaced. Alternatively or additionally, the smoke detector management system may also have a separate maintenance evaluation unit for this purpose. If it is determined that the smoke detector needs to be serviced or replaced, a maintenance message may be communicated to the user profile assigned to the smoke detector and/or to the administrator or to the user profile subgroup assigned by that user profile. In particular, provision may be made for the message to be communicated to a computer connected to a type of fuel filter, such as a battery replacement unit.The service message may include failure of one or more smoke detector sensors, replacement of the smoke detector and/or disconnection of the smoke detector from the server over a period of time. Preferably, the service message is tailored to the maintenance event. For example, if address data is stored, the service message may contain it. The service message may contain at least part of the data transmitted by the relevant smoke detector or communicate it in an appropriate manner. It may also be provided that the evaluation unit and/or, where applicable, the maintenance evaluation unit with the stored maintenance data is in a state of readiness for a maintenance or replacement point. The user profile may be assigned to the user profile or assigned to a user profile by the administrator.Preferably the maintenance evaluation unit may be identical to the evaluation unit, and provision may be made for the forecast to be communicated to computer equipment connected to the user profile.

The evaluation unit and/or maintenance unit may be run as software and/or may correspond to or run on the server of the smoke alarm management system. However, it may also be provided that the evaluation unit and/or maintenance unit correspond to or run on another computer device connected to the server. It may also be imagined that the evaluation unit and/or maintenance unit correspond to or run on the computer device, i.e. the evaluation is not performed on the server but locally by the user's devices connected to the server.

Further details of the invention are explained in the following figures: Figure 1a schematic representation of an embodiment of a method according to the invention for assigning a smoke detector to be registered;Figure 2a schematic representation of an embodiment of a smoke detector management system according to the invention;Figure 3a view of a GUI showing a user profile;Figure 4a view of a GUI showing a distribution of rights of different user profiles assigned to a user profile group;Figure 5a view of a GUI showing an overview of smoke detectors assigned to a user profile;Figure 6a view of a GUI showing messages communicated to a user profile, in particular an alarm message in case of an alarm.

The smoke detector 2 to be registered is connected to the server 3 of the smoke detector management system 1 in such a way that data can be exchanged between the smoke detector 2 to be registered and the server 3. The mobile device 4 is connected to the server 3 in such a way that data can be exchanged between the mobile device 4 and the server 3. Preferably, smoke detectors 2 and server 3 and mobile device 4 and server 3 are wirelessly connected, e.g. via a mobile network, preferably via narrowband Internet of Things (narrowband IoT). The smoke detector 2 to be registered transmits initial identification data to the server 6 3.The connection of the smoke detector 2 to the server 3 and the initiation of the transmission of the first identification data 6 can be done, for example, by a user through an operation element of the smoke detector, e.g. a button or a button. The user can log in to his user profile 11 stored on the server 3 via an app or GUI stored on the mobile device 4 and, via the GUI, inform the server 3 that a smoke detector 2 is to be added to his user profile 11. Second identification data 7 can then be transmitted from the smoke detector 2 to the mobile device 4. The transmission of the second identification data 7 can be done in this way.The mobile device 4 can then transmit the second identification data 7 received by the smoke detector 2 and the user identification data 5 uniquely identifying the user profile 11 to server 3. The server 3 can then identify the smoke detector 2 to be registered, e.g. by further comparing the first and second identification data and using the user identification data 5 to assign the smoke detector 2 to the user profile 11. The now assigned smoke detector 2 can now be configured by the user, for example in the GUI and, if necessary, by the user.The address data 17 may have been stored on server 3 before the smoke detector 2 is assigned to the user profile 11 and before the data connection between smoke detector 2 and server 3 is established, for example.

Err1:Expecting ',' delimiter: line 1 column 841 (char 840)

After its assignment, the smoke detector 2 may communicate status data and/or operation data and/or measurement data to the server 3 at periodic intervals. It may also be provided that the first and/or second identification data are transmitted together with the status and/or measurement data to allow easy assignment of the data received by the server 3 to the respective user profiles 11 The data received may be evaluated on the server side, for example to identify an alarm and/or a maintenance incident.

Smoke detector 8 can exchange data with server 3. For example, the smoke detector 8 can transmit measurement data or status data to server 3. The server 3 can send to the smoke detector 8 e.g. firmware updates. The server 3 is preferably cloud-based. Smoke detector 8 and server 3 are connected via Narrowband Internet of Things (Narrowband IoT). The smoke detector may have a suitable module, such as a SIM card, for this purpose. This allows the smoke detector to be positioned flexibly, since it can be positioned without the need for wires.This eliminates the need for an intermediate gateway between smoke detector 8 and server 3, which further facilitates the installation, exchange and maintenance of smoke detectors 8. In an embodiment, however, at least one of the smoke detectors 8 can be wired to server 3. Furthermore, a smoke detector 2 to be registered and a mobile device 4 used for registration are shown in Figure 2, both connected to server 3 for data exchange to perform the registration procedure described above.the data stored on server 4 from the smoke detector 8 associated with user profile 11. A stationary device 13 can also be used for the same purpose, i.e. the user can also access server 3 or his user profile 11 from stationary device 13. The mobile device 4 can be e.g. a smartphone, PDA, tablet or laptop. The stationary device 13 can be e.g. a desktop PC, a workstation or the like.

Preferably, the user can access his user profile 11 via a computer device, e.g. mobile device 4 and/or stationary device 13, by means of a computer program, app or GUI. Figures 3 to 6 show an example of a suitable GUI. The GUI allows the user to add, remove and/or manage smoke detectors and view the data transmitted by the smoke detector. Figure 3 shows, for example, an overview of the 11 smoke detectors assigned to a user profile 8.Err1:Expecting ',' delimiter: line 1 column 599 (char 598)In the example illustrated in the figures, the smoke detector subgroups 17 are determined by the smoke detector address data 17. In the example illustrated, a smoke detector subgroup 17 thus includes all smoke detectors installed in the same building 8. Of course, smoke detectors 8 can also be divided into more or less smoke detector subgroups or groups; for example, all smoke detectors 8 installed on one floor of a building could be divided into another subgroup or subgroup.However, the classification of smoke detectors into fewer smoke detector groups or sub-groups may be made either in addition to or instead of other criteria. It may be possible to group smoke detectors, for example, exclusively or additionally by type designation or manufacturer, for example to facilitate management or, for example, in the case of maintenance messages, to send them exclusively to companies specialising in the respective manufacturer or type of smoke detector. It may be advantageous to make the data transmitted by the smoke detector 8 available to other users or user profiles 11 as well. At least one or all smoke detectors8, smoke detector group 16 and/or smoke detector group 17 may be assigned to a filter group 10 or correspond to one of these.The user profile group 10 corresponds to the group of user profiles 11 that can access some or all of the data of the user profile 8 and/or the user profile group 16 and/or the user profile group 17 associated with the user profile group 8 and/or the user profile group 17. As shown in Figure 4, a group administrator can add or remove user profiles 11 from user profile group 10. This can be done in particular by simply adding the user identification data 5 corresponding to a user profile 11. The administrator can grant or withdraw individual access rights 15 to each user profile 11 of the user profile group 10. This allows the administrator to determine which user profile 11 can access which user profile 8 and/or which user profiles 11 can access.Err1:Expecting ',' delimiter: line 1 column 219 (char 218)Unless otherwise provided, the user profile 11 may be the administrator who added the group 16 to the first smoke detector 8 by the method of the invention.

Figure 5 shows another example of the smoke detectors assigned to a group of 16 smoke detectors, which allows the user profile 11 to see, for example, the battery status or status of the respective smoke detectors.

Figure 6 shows an example of notifications transmitted to a user profile 11 In the event of an alarm, an alarm message 12 may be sent to the user profiles 11 associated with the smoke detector 8 reporting the alarm or to the user profiles 11 with the respective rights of the user profile group 10 associated with the alarm, but notifications may also be sent, as shown in Figure 6, e.g. installation or maintenance events or warnings regarding changes in the smoke detector status, e.g. sensor failure or battery life, or to the computer or device associated with the user profile 11 or device, e.g. mobile phone, e-mail or home phone number 13

Claims (15)

1. A method for assigning a smoke detector (2) to be registered to a user profile (11) of a smoke detector management system (1), comprising the following steps:

   - Establishing a data connection between the smoke detector (2) and a server (3) of the smoke detector management system (1), the smoke detector (2) being connected directly to the server (3) via narrowband Internet of Things, and transmitting first identification data (6) of the smoke detector (2) to be registered to the server (3) via the data connection between the smoke detector (2) and the server (3), the first identification data (6) having an alphanumeric code uniquely assigned to the smoke detector (2);

   - Establishing a data connection between a mobile device (4) and the server (3);

   - Logging into the user profile (11) by means of the mobile device (4) using user identification data (5) uniquely assigned to the user profile (11);

   - Transmitting second identification data (7) of the smoke detector (2) to be registered from the smoke detector (2) to be registered to the mobile device (4);

   - Transmitting the second identification data (7) to the server (3) by the mobile device (4), or transmitting the second identification data (7) and the user identification data (5) to the server (3) by the mobile device (4); and

   - Identifying the smoke detector (2) by means of the first and second identification data (6; 7) and assigning the smoke detector (2) to the logged-in user profile (11) or the user profile (11) corresponding to the user identification data (5).
2. The method according to claim 1, wherein after identifying the smoke detector (2) and assigning the smoke detector (2) to the user profile (11), position and/or address data (17) are assigned to the smoke detector (2) assigned to the user profile (11).
3. The method according to one of claims 1 or 2, in which the first and the second identification data (6; 7) are identical.
4. The method according to any one of the preceding claims, in which the mobile device (4) is connected to the server (3) wirelessly, preferably via a mobile radio network, particularly preferably via narrowband Internet of Things, at least for the transmission of the respective data (5; 6; 7).
5. The method according to any one of the preceding claims, in which said transmitting of the second identification data (7) to the mobile device (4) either

   - comprises capturing a QR-code attached to the smoke detector (2) with the mobile device (4), or

   - comprises capturing a pictogram or alphanumeric code attached to or included with the smoke detector (2) with the mobile device (4) and applying image recognition software, or

   - is conducted via a wireless connection between smoke detector (2) and mobile device (4).
6. The method according to any one of the preceding claims, wherein an authorization request is sent from the server (3) to the mobile device (4) before associating the smoke detector (2).
7. The method according to any one of the preceding claims, in which, after the smoke detector (2) has been assigned to a user profile, the smoke detector (2, 8) is assigned to at least one further user profile (11), this further assignment being either

   - analogous to the method described in any one of claims 1 - 6, or

   - conducted via a change in the assignment data stored on the server (3).
8. The method according to any one of the preceding claims, in which the smoke detector (2, 8) periodically transmits status data (9) and/or operating data and/or the first identification data (6) and/or the second identification data (7) to the server (3) after the assignment.
9. The method according to any one of the preceding claims, in which, after the smoke detector (2, 8) has been assigned, it matches and/or synchronizes operating parameters, settings and/or firmware with the server (3) once or periodically.
10. A smoke detector management system (1), comprising at least one smoke detector (8) and at least one server (3), wherein at least one user profile (11) is stored on the server (3), wherein the server (3) is connected to the at least one smoke detector (8) for data exchange, wherein the server (3) is preferably cloud-based, wherein the server (3) is configured to store data received from the smoke detector (8) and make it accessible to a user profile (11) assigned to the smoke detector (8), the server (3) having a communication interface which is set up to establish a direct data connection via narrowband Internet of Things with a smoke detector (2) to be registered and a data connection with a mobile device (4), the server (3) being set up to store first identification data (6), which have an alphanumeric code uniquely assigned to the smoke detector (2) to be registered, from the smoke detector (2) to be registered via the communication interface, and the server (3) being set up to receive second identification data (7) from the mobile device (4) via the communication interface or to receive second identification data (7) and user identification data (5) from the mobile device (4) via the communication interface, so that the smoke detector (2) to be registered can be assigned to the user profile (11) by means of second identification data (7) received from the mobile device (4) and first identification data (6) received from the smoke detector (2) to be registered, the smoke detector (8) being assigned to the user profile (11) in accordance with the method according to one of claims 1 to 10.
11. The smoke detector management system (1) according to claim 10, wherein the mobile device (4) is connected to the server (3) wirelessly, preferably via a mobile network and particularly preferably via narrowband Internet of Things.
12. The smoke detector management system (1) according to any one of claims 10 to 11, wherein the server (3) is connected to at least one computer device (4, 13) for data exchange, wherein the computer device (4, 13) is set up to download, manipulate or add new data to the user profile (11) received from the corresponding smoke detector (8) and stored on the server (3) using user identification data (5) uniquely identifying the user profile (11).
13. The smoke detector management system (1) according to one of claims 10 to 12, wherein a plurality of user profiles (11) is stored on the server (3), wherein at least one, preferably each of the user profiles (11) is assigned to at least one of at least two user profile groups (10), wherein each user profile (11) assigned to the same user profile group (10) is assigned to the same one of the at least one smoke detectors (8).
14. The smoke detector management system (1) according to claim 13, wherein at least one of the user profiles (11) assigned to a user profile group (10) has administrator rights at least with respect to the respective user profile group (10).
15. The smoke detector management system (1) according to any one of claims 10 to 14, wherein the smoke detector management system (1) has an evaluation unit which can identify an alarm case and/or maintenance case from the data received from the smoke detector (8), wherein in the alarm case the system sends an alarm message (12) and/or in the maintenance case it sends a maintenance message to the user profiles (11) assigned to the smoke detector.