Database Update System

Abstract

Supports the creation of a database of fire alarm equipment managed on a server. [Solution] A database creation system for creating a database related to terminal devices of a fire alarm system, which is stored in a fire receiver, includes a server and a communication terminal. The server includes storage means for storing the database and a program for creating the database, first transmission means for transmitting screen data showing a screen for creating the database to the communication terminal, and creation means for creating the database in accordance with the program based on the data transmitted from the communication terminal. Meanwhile, the communication terminal includes display means for displaying a screen shown by the screen data transmitted by the server, input means for inputting data related to the terminal device, and second transmission means for transmitting the data input by the input means to the server.

Description

[Technical field]

[0001] The present invention relates to a technique for creating a database relating to a fire alarm system. [Background technology]

[0002] Conventionally, in order to display the location where a fire has been detected, a fire receiver stores the address of a terminal device such as a fire detector in association with information indicating the installation location of the terminal device. This information needs to be updated when the installation location of the terminal device is changed or when the name of a room in a property is changed. Therefore, a technique for updating this information has been proposed.

[0003] For example, Patent Document 1 proposes a technique for generating correspondence data that associates the address of a terminal device with information indicating the installation location of the terminal device on a personal computer, and writing the correspondence data to the EEPROM of a fire control device connected to the personal computer by a cable. This technique allows the correspondence data to be rewritten more quickly than the conventional updating method of requesting the fire control device manufacturer to create the correspondence data, obtaining a semiconductor memory with the correspondence data written in it, and installing it in the fire control device. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-109154 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, when using the technology described in Patent Document 1, it is possible to create corresponding data for each computer, so it is possible that multiple corresponding data will exist for one fire control receiver. In other words, it is expected that it will be difficult to centrally manage the corresponding data.

[0006] The present invention has been made in consideration of the above circumstances, and has an object to support the creation of a database relating to fire alarm systems, which is managed in a server. [Means for solving the problem]

[0007] In order to solve the above problems, a fire receiver in one embodiment of the present invention is a fire receiver equipped with a tag that displays or records its own identification information and the identification information of the server to which the identification information is sent, and the identification information of the fire receiver displayed or recorded on the tag is displayed or stored in correspondence with the identification information of the property in which the fire receiver is installed when the tag is read by a communications terminal. Effect of the Invention

[0008] According to the present invention, it is possible to assist in the creation of a database relating to fire alarm systems, which is managed in a server. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a configuration of a database creation system 1. [Diagram 2] 2 is a block diagram showing an example of the configuration of a fire alarm system 5. FIG. [Diagram 3] 2 is a block diagram showing an example of a hardware configuration of a fire receiver 51. FIG. [Figure 4] FIG. 5 is a diagram showing an example of a terminal device information DB 5121. [Diagram 5] FIG. 2 is a diagram showing an example of the appearance of a fire receiver 51. [Figure 6] 2 is a block diagram showing an example of a hardware configuration of a server 2. FIG. [Figure 7] FIG. 2 is a diagram showing an example of a user information DB 221. [Figure 8] FIG. 2 is a diagram showing an example of a property information DB 222. [Figure 9]FIG. 13 is a diagram showing an example of a terminal device information DB 223. [Figure 10] 2 is a block diagram showing an example of a hardware configuration of a communication terminal 3. FIG. [Figure 11] 2 is a block diagram showing an example of a functional configuration realized in a server 2 and a communication terminal 3. FIG. [Figure 12] 11 is a sequence chart showing an example of a property information registration operation. [Figure 13] FIG. 13 is a diagram showing an example of a property information input screen. [Figure 14] 11 is a sequence chart showing an example of a property information registration operation. [Figure 15] 11 is a sequence chart showing an example of a database update operation. [Figure 16] FIG. 13 is a diagram illustrating an example of an installation location editing screen. [Figure 17] FIG. 13 is a diagram showing an example of a linkage destination editing screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] 1. Embodiment 1-1.Configuration 1-1-1. Configuration of database creation system 1 The database creation system 1 according to this embodiment is a system for creating a database relating to terminal devices of a fire alarm system, which is stored in a fire receiver. FIG. 1 is a diagram showing an example of the configuration of the database creation system 1. As shown in FIG. 1, the database creation system 1 has a server 2 and a communication terminal 3. The server 2 and the communication terminal 3 are connected by a communication line 4. The communication line 4 is configured, for example, by a telephone network, a mobile communication network, or the Internet, or a combination of these. Although only one communication terminal 3 is connected to the communication line 4 shown in FIG. 1, multiple communication terminals 3 may be connected.

[0011] 1-1-2. Configuration of fire alarm system 5 First, the configuration of the fire alarm system 5 according to this embodiment will be described. The fire alarm system 5 is installed in a building, and when a detector detects heat or smoke, a fire receiver rings a district bell to notify people in the building of a fire. FIG. 2 is a block diagram showing an example of the configuration of the fire alarm system 5. As shown in FIG. 2, the fire alarm system 5 has an R-type (Record type) fire receiver 51, a transmitter 52, and fire detectors 53-1, 53-2, . . . , 53-n (hereinafter, referred to as fire detector 53 when there is no need to distinguish between them). The transmitter 52 and the fire detector 53 are connected to the fire receiver 51.

[0012] The fire alarm system 5 also includes repeaters 54-1 to 54-4 (hereinafter, referred to as repeaters 54 when there is no need to distinguish between them), a smoke exhauster 55, a shutter 56, a fire door 57, and district bells 58-1 and 58-2 (hereinafter, referred to as district bell 58 when there is no need to distinguish between them). The smoke exhauster 55, the shutter 56, the fire door 57, and the district bell 58 are each connected to the fire receiver 51 via the repeater 54, and are controlled by the repeater 54 based on a control signal transmitted by the fire receiver 51. Of the devices shown in FIG. 2, the devices other than the fire receiver 51 are examples of the "terminal device" according to the present invention.

[0013] Fire receiver 51 is a device that, upon receiving a fire signal from transmitter 52 or fire detector 53, issues a message informing of the occurrence of a fire and activates a terminal device via repeater 54. Fig. 3 is a block diagram showing an example of a hardware configuration of fire receiver 51. As shown in Fig. 3, fire receiver 51 has control unit 511, storage unit 512, display unit 513, input unit 514, terminal device interface unit 515, card interface unit 516, and printer unit 517.

[0014] The control unit 511 includes a central processing unit (CPU), a read only memory (ROM), and a random access memory (RAM). The CPU loads a program stored in the ROM into the RAM and executes it. The storage unit 512 is a storage device such as an electrically erasable programmable ROM (EEPROM), and stores a terminal device information DB 5121 described later. The display unit 513 is a display device such as a liquid crystal display, and displays, for example, a message notifying an occurrence of a fire. The input unit 514 is an input device such as a switch, and is used to operate the fire receiver 51. The terminal device interface unit 515 exchanges fire signals and control signals with the terminal device. The card interface unit 516 is a card reader / writer, and transfers data to and from a Compact Flash (CF) card C inserted in a card slot. The printer unit 517 prints a log of events such as an alarm, which is stored in the storage unit 512.

[0015] Fig. 4 is a diagram showing an example of a terminal device information database (hereinafter referred to as "terminal device information DB") 5121 stored in storage unit 512. Terminal device information DB 5121 is a database for managing information on terminal devices connected to fire receiver 51. Each record constituting terminal device information DB 5121 is composed of fields for "address", "type", "serial number", "manufacturing year", "installation location", "status" and "linkage destination", as shown in Fig. 4.

[0016] Here, the "address" field stores an address, which is identification information uniquely assigned to the terminal device. The "linkage destination" field stores the address of a terminal device that operates in conjunction with the operation of the terminal device. For example, in the example of terminal device information DB5121 shown in FIG. 4, address "005" is associated as the linkage destination of the "smoke detector" indicated by address "001", which indicates that when the "smoke detector" indicated by address "001" transmits a fire signal, the "district bell" indicated by address "005" will ring.

[0017] When the control unit 511 receives a fire signal from the transmitter 52 or the fire detector 53, it refers to the terminal device information DB 5121 to identify the installation location of the terminal device, and displays the installation location on the display unit 513. The control unit 511 also refers to the terminal device information DB 5121 to identify the terminal device that is the link destination of the terminal device that transmitted the fire signal, and transmits a control signal to the repeater 54 that controls the link destination terminal device. The control unit 511 also transmits an interrogation signal to the fire detector 53, and when a response signal is returned in response to the interrogation signal, it registers information indicative of the serial number, manufacturing year, and status of the fire detector 53, which is included in the response signal, in the terminal device information DB 5121.

[0018] FIG. 5 is a diagram showing an example of the appearance of the fire receiver 51. A tag T showing a two-dimensional code is attached to the outer surface of the housing of the fire receiver 51. This two-dimensional code is a code representing the identification information of the fire receiver 51 and the identification information of the server 2. More specifically, it is a code representing the model name, manufacturing year, and serial number of the fire receiver 51, and the URL (Uniform Resource Locator) or email address of the server 2. This two-dimensional code is read by the communication terminal 3 and used in the property information registration operation described later. Note that, although a two-dimensional code is adopted in this embodiment, a one-dimensional code such as a barcode may be adopted instead of the two-dimensional code. Also, in this embodiment, the two-dimensional code represents the model name, manufacturing year, and serial number as the identification information of the fire receiver 51, but it may represent only the serial number. Also, instead of the tag T, an IC tag for recording the identification information of the fire receiver 51 and the identification information of the server 2 may be attached to the outer surface of the housing of the fire receiver 51.

[0019] 5 is merely an example, and the tag T may be attached to another position on the outer surface of the housing of the fire receiver 51. If the fire receiver 51 has an opening and closing door, the tag T may be attached to the inside of the opening and closing door. The tag T may be attached to the fire receiver 51 as a sticker. The tag T may be attached to the fire receiver 51 via a string or packaging material. For example, the tag T may be attached to a box in which the fire receiver 51 is packed.

[0020] Next, the fire detector 53 is, for example, a heat detector, smoke detector, or flame detector, and is a device that transmits a fire signal together with its own address to the fire receiver 51 when it detects the outbreak of a fire. When the fire detector 53 receives a question signal from the fire receiver 51, it has a function of returning a response signal indicating its own serial number, manufacturing year, and status to the fire receiver 51. The transmitter 52 has a button that is operated by the person who discovers the fire, and is a device that transmits a fire signal together with its own address to the fire receiver 51 when the button is operated.

[0021] 1-1-3.Hardware configuration of Server 2 The server 2 constituting the database creation system 1 is a computer device for creating a database (specifically, terminal device information DB 5121) related to the terminal devices of the fire alarm system 5, which is stored in the fire receiver 51. FIG. 6 is a block diagram showing an example of a hardware configuration of the server 2. As shown in FIG. 6, the server 2 has a control unit 21, a storage unit 22, and a communication unit 23. The control unit 21 has a CPU, a ROM, and a RAM. The CPU loads a program stored in the ROM or the storage unit 22 into the RAM and executes it. The storage unit 22 is a storage device such as a hard disk, and stores a program for creating a database stored in the fire receiver 51 (hereinafter referred to as a "DB creation program 224") as well as a group of databases described later. The storage unit 22 does not necessarily need to be built into the server 2, and may be installed outside the housing of the server 2 and accessed by the control unit 21 via the communication line 4. The communication unit 23 is a network card, and the server 2 communicates with the communication terminal 3 using this communication unit 23.

[0022] 7 is a diagram showing an example of a user information database (hereinafter referred to as "user information DB") 221 stored in the storage unit 22. The user information DB 221 is a database for managing information on users who are permitted to access the server 2. Here, the users specifically refer to installers and inspectors of the fire alarm system 5.

[0023] Each record constituting the user information DB221 is composed of the fields of "Registration Date", "Company Information", and "Person in Charge Information", as shown in Fig. 7. The "Registration Date" field stores the date on which the record was registered in the user information DB221. "Company Information" specifically consists of the fields of "Company Name", "Address", "Telephone Number", and "Email Address". "Person in Charge Information" specifically consists of the fields of "Name", "Telephone Number", "Email Address", "ID", "Password", and "Qualified Person Number".

[0024] The information stored in the "ID" and "password" fields is used for user authentication in the property information registration operation and database update operation described later. The "Qualification Number" field stores the license number of the fire protection equipment engineer. By making it a term, users who can access server 2 can be limited to those who have a certain technical level. Each of the above user information is entered by the administrator of server 2 when an ID and password are issued to a user.

[0025] FIG. 8 is a diagram showing an example of a property information database (hereinafter referred to as "property information DB") 222 stored in the storage unit 22. The property information DB 222 is a database for managing information on a property in which a fire receiver 51 is installed. The property information DB 222 is used, for example, to identify a notification destination when notifying a notice of maintenance of the fire receiver 51. As shown in FIG. 8, each record constituting the property information DB 222 is composed of fields of "property information" and "fire receiver information". The "property information" is specifically composed of fields of "property name" and "address". The property name and address are examples of property identification information. The "fire receiver information" is specifically composed of fields of "model name", "manufacturing year", and "serial number". The property information and the fire receiver information are registered in a property information registration operation described later.

[0026] The storage unit 22 stores an update history table (not shown) for recording the update history of the property information DB 222. Each record in the update history table is composed of fields for "update content," "update date and time," and "updater." The "updater" field stores the user's ID. A new record is added to the update history table every time the contents of the property information DB 222 are updated.

[0027] FIG. 9 is a diagram showing an example of the terminal device information database (hereinafter referred to as "terminal device information DB") 223 stored in the storage unit 22. The terminal device information DB 223 is a database for managing information on terminal devices for each property. Each table constituting the terminal device information DB 223 is created for each property, and the records constituting each table are composed of the fields of "address", "type", "serial number", "manufacturing year", "installation location", "status" and "linkage destination" as shown in FIG. 9. This configuration is the same as each record of the terminal device information DB 5121 stored in the fire receiver 51. The information on these terminal devices can be updated by a database update operation described later.

[0028] 1-1-4. Hardware configuration of communication terminal 3 The communication terminal 3 constituting the database creation system 1 is a computer device for accessing the server 2 and creating the terminal device information DB 5121 stored in the fire receiver 51 by using the DB creation program 224 stored on the server 2. Specifically, the communication terminal 3 is a mobile terminal such as a mobile PC (Personal Computer), a mobile phone, a smartphone, or a tablet terminal. Note that, although the communication terminal 3 is assumed to be a mobile terminal in this embodiment, it may be a stationary computer device. FIG. 10 is a block diagram showing an example of the hardware configuration of the communication terminal 3. As shown in FIG. 10, the communication terminal 3 has a control unit 31, a storage unit 32, a display unit 33, an input unit 34, a reading unit 35, a card interface unit 36, and a communication unit 37.

[0029] The control unit 31 includes a CPU, a ROM, and a RAM. The CPU loads a program stored in the ROM or the storage unit 32 into the RAM and executes it. The storage unit 32 is a storage device such as a flash memory, and stores a web browser. The display unit 33 is a display device such as a liquid crystal display, and displays a screen indicated by screen data transmitted by the server 2. The input unit 34 is an input device such as a touch panel, and is used to input property information and data related to the terminal device of the fire alarm system 5. The reading unit 35 is an imaging device such as a CMOS image sensor, and is used to read codes such as barcodes and two-dimensional codes. The card interface unit 36 ​​is a card reader / writer, and transfers data between the CF card C inserted in the card slot. The card interface unit 36 ​​is an example of the "second storage control means" and the "reading means" according to the present invention. The communication unit 37 is a network card, and the communication terminal 3 communicates with the server 2 using this communication unit 37.

[0030] 1-1-5. Functional configuration of server 2 and communication terminal 3 Fig. 11 is a block diagram showing an example of the configuration of functions realized in the server 2 and the communication terminal 3. The group of functions shown in the figure particularly relates to a property information registration operation and a database update operation, which will be described later. The functions of the first transmission means 211, the creation means 212, the first storage control means 213, the sixth transmission means 214, and the writing means 215 realized in the server 2 are realized by the CPU of the control unit 21 executing the DB creation program 224. The functions of the second transmission means 311, the third transmission means 312, the fourth transmission means 313, the receiving means 314, and the fifth transmission means 315 realized in the communication terminal 3 are realized by the CPU of the control unit 31 executing a web browser.

[0031] The first transmitting means 211 of the server 2 transmits to the communication terminal 3 screen data showing a screen for creating a database related to the terminal devices of the fire alarm system 5, which is stored in the fire receiver 51. The display unit 33 of the communication terminal 3 displays a screen shown by the screen data transmitted by the server 2. The second transmitting means 311 of the communication terminal 3 transmits data input by the input unit 34 to the server 2. The creation means 212 of the server 2 creates the above-mentioned database, which is stored in the fire receiver 51, based on the data transmitted from the communication terminal 3, in accordance with the DB creation program 224 stored in the control unit 21. The memory unit 22 of the server 2 stores the created database.

[0032] The third transmitting means 312 of the communications terminal 3 transmits the identification information of the fire receiver 51 represented by the code read by the reading unit 35 to the server 2 whose identification information is represented by the read code. The fourth transmitting means 313 of the communications terminal 3 transmits the identification information of the property in which the fire receiver 51 is installed to the server 2. This identification information of the property is input by the input unit 34. The first storage control means 213 of the server 2 stores the identification information of the fire receiver 51 and the identification information of the property transmitted by the communications terminal 3 in the storage unit 22 in association with each other.

[0033] The sixth transmitting means 214 of the server 2 transmits the database to be stored in the fire receiver 51 to the communication terminal 3. The receiving means 314 of the communication terminal 3 receives the database from the server 2. The card interface unit 36 ​​of the communication terminal 3 stores the database received by the receiving means 314 in a storage medium. In addition, the card interface unit 36 ​​reads data relating to the terminal device stored in the storage medium from the fire receiver 51 when the storage medium is attached to the fire receiver 51 and the database stored in the storage medium is stored in the fire receiver 51. The fifth transmitting means 315 of the communication terminal 3 transmits the data read by the card interface unit 36 ​​to the server 2. The writing means 215 of the server 2 updates the database stored in the storage unit 22 based on the data relating to the terminal device transmitted from the communication terminal 3.

[0034] 1-2.Operation Next, the operation of the database creation system 1 will be described. Specifically, first, the operation when the installer of the fire alarm system 5 registers property information in the property information DB 222 of the server 2 after installing the fire receiver 51 in the building (hereinafter referred to as "property information registration operation") will be described. Two patterns of this operation will be described, one in which a web page is used, and the other in which both email and a web page are used. Next, the operation when the inspector of the fire alarm system 5 updates the terminal device information DB 5121 stored in the fire receiver 51 (hereinafter referred to as "database update operation") will be described.

[0035] 1-2-1. Property information registration operation (when using the web page) 12 is a sequence chart showing an example of a property information registration operation using a web page. After installing the fire receiver 51 in a building, the installer of the fire alarm system 5 reads the two-dimensional code of the fire receiver 51 using the communication terminal 3 (step Sa1). The communication terminal 3 decodes the read two-dimensional code to identify the model name, manufacturing year, and serial number of the fire receiver 51, as well as the URL of the server 2. The communication terminal 3 then requests the server 2 to send a page specified by the URL (step Sa2). This page request includes information indicating the model name, manufacturing year, and serial number of the fire receiver 51 identified by decoding the two-dimensional code.

[0036] When the server 2 receives the page request from the communications terminal 3, it transmits screen data showing a login screen to the communications terminal 3 (step Sa3). This login screen has input fields for inputting an ID and a password. When the communications terminal 3 receives the screen data from the server 2, it displays the login screen on the display unit 33 and waits for the user to input an ID and a password. When it receives input of an ID and a password from the user (step Sa4), the communications terminal 3 notifies the server 2 of the input ID and password (step Sa5).

[0037] When the server 2 receives the ID and password from the communication terminal 3, the server 2 performs user authentication (step Sa6). Specifically, the server 2 judges whether or not the pair of ID and password notified from the communication terminal 3 is registered in the user information DB221 (in other words, whether or not the user is a qualified person). If the result of this judgment shows that the pair of ID and password is registered in the user information DB221, the server 2 recognizes that the user of the communication terminal 3 is a user who has access rights, and transmits screen data showing a property information input screen to the communication terminal 3 (step Sa7). On the other hand, if the result of this judgment shows that the pair of ID and password is not registered in the user information DB221, the server 2 denies the user of the communication terminal 3 access to the property information DB222.

[0038] When the communication terminal 3 receives the screen data from the server 2, it displays a property information input screen on the display unit 33 and waits for the user to input property information. FIG. 13 is a diagram showing an example of the property information input screen. The screen shown in the figure has input fields F1 to F4 for inputting user information, property information, fire receiver information, and remarks. Specifically, it has an input field F1 for inputting "company name", "registration date", "person in charge name", "company telephone number", "company email address", "person in charge telephone number", and "person in charge email address" as user information. It also has an input field F2 for inputting "property name", "zip code", "prefecture", "city, ward, town, village", and "subsequent address" as property information. It also has an input field F3 for inputting "model name" and "serial number" as fire receiver information. The screen also has a "register" button B1 and a "cancel" button B2, and when the register button B1 is selected, the input information is transmitted to the server 2.

[0039] The user information and the fire receiver information may be input in advance in the server 2 before the screen data showing the property information input screen is transmitted to the communication terminal 3. This is because the user information has already been registered in the user information DB 221 before the screen data is transmitted to the communication terminal 3, and the fire receiver information has been notified to the server 2 from the communication terminal 3 in the above step Sa2.

[0040] When the communication terminal 3 receives information input by the user (step Sa8), it transmits the input information to the server 2 (step Sa9). When the server 2 receives the input information from the communication terminal 3, it registers the input information in the property information DB 222 (step Sa10). Specifically, the server 2 associates the property information input by the user (specifically, the property name and address) with the fire receiver information (specifically, the model name, manufacturing year, and serial number) and stores them in the property information DB 222. Note that in this embodiment, both the property name and address information are transmitted from the communication terminal 3 to the server 2 as property identification information, but it is also possible to transmit only one of them.

[0041] According to the operation described above, the property information DB222 of the server 2 can be accessed by reading the two-dimensional code of the fire receiver 51 with the communication terminal 3, thereby eliminating the burden on the user of having to enter the URL of the server 2, etc., when registering property information in the property information DB222.

[0042] 1-2-2. Property information registration operation (when using email and web page) FIG. 14 is a sequence chart showing an example of a property information registration operation using email and a web page. When the installer of the fire alarm system 5 installs the fire receiver 51 in the building, the installer reads the two-dimensional code of the fire receiver 51 using the communication terminal 3 (step Sb1). The communication terminal 3 decodes the read two-dimensional code to identify the model name, manufacturing year, and serial number of the fire receiver 51, as well as the email address of the server 2. In this operation using email, the email address of the server 2 is encoded in the two-dimensional code instead of the URL of the server 2. Then, the communication terminal 3 sends an email to the server 2 requesting the URL of a property information input screen (step Sb2). This email describes information indicating the model name, manufacturing year, and serial number of the fire receiver 51 identified by decoding the two-dimensional code.

[0043] When the server 2 receives an email from the communication terminal 3, it performs user authentication (step Sb3). Specifically, the server 2 judges whether or not the email address indicating the sender described in the email received from the communication terminal 3 is registered in the user information DB 221 (in other words, whether or not the user is a qualified person). If the result of this judgment shows that the email address is registered in the user information DB 221, the server 2 recognizes that the user of the communication terminal 3 is a user who has access rights, and sends an email describing the URL of a property information input screen to the communication terminal 3 (step Sb4). On the other hand, if the result of this judgment shows that the email address is not registered in the user information DB 221, the server 2 denies the user of the communication terminal 3 access to the property information DB 222.

[0044] When the communications terminal 3 receives an email from the server 2 and accepts an operation from the user to select a URL described in the email, the communications terminal 3 transmits a page request to the server 2 requesting a page specified by the URL (step Sb5). When the server 2 receives the page request from the communications terminal 3, the server 2 transmits screen data showing a property information input screen to the communications terminal 3 (step Sa7). The processes after this are similar to steps Sa7 to Sa10 shown in FIG. 12 above, and therefore will not be described.

[0045] According to the operation described above, the two-dimensional code of the fire receiver 51 is read by the communication terminal 3 to send an email to the server 2, and the property information DB222 of the server 2 can be accessed by selecting the URL described in the reply email, eliminating the burden on the user of having to enter the URL of the server 2 when registering property information in the property information DB222. In addition, since user authentication is performed based on the user's email address, input of an ID and password is omitted compared to the operation using only the above-mentioned web page.

[0046] 1-2-3.Database update operation 15 is a sequence chart showing an example of a database update operation. In this operation, an inspection company of the fire alarm system 5 edits the terminal device information DB223 stored on the server 2 using the communication terminal 3, and updates the terminal device information DB5121 stored in the fire receiver 51 based on the edited data.

[0047] First, the communications terminal 3 transmits a page request to the server 2 (step Sc1). When the server 2 receives the page request from the communications terminal 3, it transmits screen data showing a login screen to the communications terminal 3 (step Sc2). This login screen has input fields for inputting an ID and a password. When the communications terminal 3 receives the screen data from the server 2, it displays the login screen on the display unit 33 and waits for the user to input an ID and a password. When the communications terminal 3 receives input of an ID and a password from the user (step Sc3), it notifies the server 2 of the input ID and password (step Sc4).

[0048] When the server 2 receives the ID and password from the communication terminal 3, the server 2 performs user authentication (step Sc5). Specifically, the server 2 judges whether or not the pair of ID and password notified from the communication terminal 3 is registered in the user information DB 221 (in other words, whether or not the user is a qualified person). If the result of this judgment is that the pair of ID and password is registered in the user information DB 221, the server 2 recognizes that the user of the communication terminal 3 is a user who has access rights, and transmits screen data showing a property search screen to the communication terminal 3 (step Sc6). This property search screen has an input field for inputting the property name or the serial number of the fire receiver 51 as a search key. On the other hand, if the result of the above judgment is that the pair of ID and password is not registered in the user information DB 221, the server 2 denies the user of the communication terminal 3 access to the terminal device information DB 5121.

[0049] When the communication terminal 3 receives the screen data from the server 2, it displays a property search screen on the display unit 33 and waits for the user to input a search key. When the communication terminal 3 receives the search key input by the user (step Sc7), it notifies the server 2 of the input search key (step Sc8). When the server 2 receives the search key notification from the communication terminal 3, it identifies a table corresponding to the notified search key in the terminal device information DB 223 (step Sc9). For example, if the search key notified from the communication terminal 3 is the property name "E Building" or the serial number "2001" of the fire receiver 51 (see FIG. 8), the server 2 identifies the table for the property name "E Building" shown in FIG. 9.

[0050] When the table is specified, the server 2 generates screen data showing an editing screen based on the specified table and transmits it to the communication terminal 3 (step Sc10). FIG. 16 is a diagram showing an example of an editing screen. FIG. 16 is a diagram showing an example of an editing screen for editing the installation location of a terminal device in particular. The screen shown in the figure has input fields F5 to F7 for inputting "Address", "Type", and "Installation Location". The screen also has a list box L1 for switching the editing screen. The screen also has an "End Input" button B3, a "Write to Card" button B4, and a "Cancel" button B5.

[0051] Next, FIG. 17 is a diagram showing an example of an interlocking destination editing screen for setting the interlocking destination of a terminal device. FIG. 17(a) is a screen for selecting a terminal device (called an "interlocking source") for which the interlocking destination is to be set, and FIG. 17(b) is a screen for selecting the interlocking destination of the selected interlocking source. The screen shown in FIG. 17(a) has a list L2 of terminal devices for which the interlocking destination can be set among the terminal devices connected to the fire receiver 51. The screen also has an edit button B6, and when the edit button B6 is selected in a state in which one terminal device is selected in the list L2, the screen shown in FIG. 17(b) is displayed. The example of the screen shown in FIG. 17(b) shows a screen displayed when the edit button B6 is selected in a state in which the smoke detector with the address "001" is selected in the screen shown in FIG. 17(a). The screen shown in FIG. 17(a) also has a list box L1, an "End input" button B3, a "Write to card" button B4, and a "Cancel" button B5.

[0052] The screen shown in Fig. 17(b) has a list L3 of terminal devices that have already been set as linkage destinations of the terminal device selected on the screen shown in Fig. 17(a), and a list L4 of terminal devices that have not yet been set as linkage destinations and can be set as linkage destinations. When a terminal device is selected in list L4, the terminal device is registered in list L3. In other words, the selected terminal device is set as a linkage destination. The screen also has a list box L1, an "End input" button B3, a "Write to card" button B4, and a "Cancel" button B5.

[0053] When the user of the communication terminal 3 finishes the editing work (step Sc11) and selects the "End input" button B3, the communication terminal 3 transmits the edited screen data to the server 2 (step Sc12). When the server 2 receives the edited screen data from the communication terminal 3, it generates a database file (hereinafter referred to as "receiver DB file") to be stored in the fire receiver 51 based on the data, and transmits the file to the communication terminal 3 (step Sc13). After receiving the receiver DB file from the server 2, when the user selects the "Write to card" button B4, the communication terminal 3 records the receiver DB file in the CF card C inserted in the card slot of the terminal (step Sc14). In addition, the communication terminal 3 displays a message "Installing data" on the display unit 33 to notify the user that the communication terminal 3 is waiting for the completion of the update process for the fire receiver 51.

[0054] After recording the receiver DB file on the CF card C, the user of the communications terminal 3 removes the CF card C from the card slot, and inserts it into the card slot of the fire receiver 51. Then, the user operates the fire receiver 51 to update the contents of the terminal device information DB 5121. When updating the contents of the terminal device information DB 5121, the fire receiver 51 first records the current contents of the terminal device information DB 5121 (hereinafter referred to as the "old database") on the CF card C. Thereafter, the fire receiver 51 updates the contents of the terminal device information DB 5121 based on the receiver DB file stored in the CF card C.

[0055] When the update process by the fire receiver 51 is completed, the user of the communications terminal 3 removes the CF card C from the card slot of the fire receiver 51 and inserts it into the card slot of the communications terminal 3. When the CF card C is inserted into the card slot, the communications terminal 3 reads out the old database stored in the card (step Sc15) and transmits it to the server 2 (step Sc16). In addition, the communications terminal 3 changes the message "Data installation in progress" displayed on the display unit 33 to a message "Data installation completed," thereby notifying the user that the communications terminal 3 has recognized the completion of the update process for the fire receiver 51.

[0056] When the server 2 receives the old database from the communication terminal 3, it determines that the update of the terminal device information DB5121 of the fire receiver 51 is complete, and updates the terminal device information DB223 based on the edited screen data received from the communication terminal 3 in step Sc12 (step Sc17). The server 2 also updates the terminal device information DB223 based on the old database received from the communication terminal 3. Specifically, the server 2 reflects changes in the serial number, manufacturing year, and status of the fire detector 53 stored in the old database in the terminal device information DB223.

[0057] According to the above-described operation, the database stored by the fire receiver 51 is created on the server 2 and stored on the server 2, so that the database can be managed centrally. Therefore, compared to the case where the database is managed for each communication terminal 3, it is expected that the database will be prevented from being lost. In addition, even if the contractor who inspects the fire alarm system 5 is changed, the database can be easily handed over to the new contractor. In addition, even if the database stored in the fire receiver 51 is destroyed by a lightning strike, the original data is managed centrally, so that the database can be expected to be quickly restored. In addition, even if a malfunction occurs in the fire receiver 51, if the server 2 is managed by the manufacturer of the fire receiver 51, it can be quickly determined whether the malfunction is due to the setting of the database.

[0058] Furthermore, according to the above-described operation, the DB creation program 224 is stored only in the server 2 and is used only on the database creation system 1, so that even if the DB creation program 224 needs to be updated, there is no need to update the program for each communication terminal 3. Furthermore, compared to the case where the DB creation program 224 is used for each communication terminal 3, it is expected that illegal copying of the program can be prevented. Furthermore, since it is necessary to access the server 2 when using the DB creation program 224, it becomes possible for the server 2 to grasp the usage status of the program, and thus it becomes possible to charge according to the usage status of the DB creation program 224. In this case, charging may be performed for each property, for each security area of ​​the property (i.e., for each line), or for each time the server 2 is accessed.

[0059] Furthermore, according to the operation described above, when the database stored by the fire receiver 51 is updated, information indicating the serial number, manufacturing year and status of the fire detector 53 collected by the fire receiver 51 is uploaded to the server 2 and managed by the server 2, so that the administrator of the server 2 can provide guidance on maintenance of the fire detector 53 based on this information.

[0060] 2. Variations The above embodiment may be modified as follows. The following modifications may be combined with each other.

[0061] 2-1. Variation 1 In the above embodiment, data is exchanged between the communication terminal 3 and the fire receiver 51 via the CF card C, but other storage media such as a USB (Universal Serial Bus) memory or an SD memory card may be used instead of the CF card C. Data may also be exchanged by wired or wireless communication without using a storage medium.

[0062] 2-2. Variation 2 In the above embodiment, the receiver DB file generated on the server 2 after being edited by the communication terminal 3 is installed on the fire receiver 51 via the communication terminal 3, but it may also be installed directly from the server 2 to the fire receiver 51. For example, the fire receiver 51 may be connected to the communication line 4, and the receiver DB file may be installed on the fire receiver 51 from the server 2 via the communication line 4. In this case, the old database of the fire receiver 51, which is uploaded to the server 2 via the communication terminal 3 in the above embodiment, may be uploaded directly to the server 2 via the communication line 4.

[0063] 2-3. Variation 3 In the property information registration operation according to the embodiment described above, the name and address of the property are input by the user of the communication terminal 3 and transmitted to the server 2. However, instead of these pieces of information, the location information of the communication terminal 3 may be transmitted to the server 2. Specifically, the communication terminal 3 may be provided with a GPS (Global Positioning System) receiver, and current location information identified using this GPS receiver may be transmitted to the server 2 in place of information indicating the property name and address in step Sa9 of the property information registration operation described above. The server 2 may store this current location information in the property information DB 222 instead of the property name and address, or may identify the property name and address based on the current location information and register the identified property name and address in the property information DB 222.

[0064] 2-4. Variation 4 The configuration of the fire alarm system 5 according to the above embodiment is merely an example, and a fire alarm system having another configuration may be used. For example, a P-type (Proprietary-type) fire receiver may be used instead of the R-type fire receiver 51. In addition, some of the exemplified terminal devices may not be used, and other terminal devices such as indicator lights and gas leak detectors may be used in addition to the exemplified terminal devices.

[0065] 2-5. Variation 5 The configuration of each database stored in the server 2 and the fire receiver 51 according to the above embodiment is merely an example, and databases having other configurations may be used. For example, each database may be a relational database consisting of multiple associated tables. In addition, some fields of the records constituting each database may be omitted, or new fields may be added.

[0066] 2-6. Variation 6 The configuration of the screen displayed on the communication terminal 3 in the property information registration operation and the database update operation according to the above embodiment is merely an example, and a screen having another configuration may be adopted. For example, the property information input screen displayed on the communication terminal 3 in the property information registration operation may lack some of the input fields or buttons exemplified in FIG. 13, or may further have other input fields or buttons. In addition, in the database update operation, in addition to the installation location edit screen and the linkage destination edit screen, an edit screen for editing property information and an edit screen for editing basic settings of the fire alarm system 5 (for example, the ringing time of the district bell 58, etc.) may be displayed on the communication terminal 3. In addition, the installation location edit screen and the linkage destination edit screen may lack some of the input fields, lists, or buttons exemplified in FIG. 16 or FIG. 17, or may further have other input fields, lists, or buttons.

[0067] 2-7. Variation 7 A program for realizing the functional group of the control unit 21 of the server 2 or the control unit 31 of the communication terminal 3 shown in Fig. 11 may be provided via a computer-readable recording medium. In addition, a program executed by the control unit of the fire receiver 51 may also be provided via a computer-readable recording medium. Here, the recording medium is, for example, a magnetic recording medium such as a magnetic tape or a magnetic disk, an optical recording medium such as an optical disk, a magneto-optical recording medium, a semiconductor memory, etc. In addition, these programs may be provided via a network such as the Internet.

[0068] 2-8. Variation 8 In the above embodiment, the ID and password issued to the user of the communication terminal 3 and stored in the user information DB 221 may be transmitted from the server 2 to the communication terminal 3 via the communication line 4. At this time, the ID and password may be transmitted as a response to an issuance request including company information and person in charge information transmitted from the communication terminal 3. Here, the ID and / or password is an example of "authentication information" according to the present invention.

[0069] (Additional Note)

[0070] A database creation system according to one embodiment of the present invention is a database creation system for creating a database relating to terminal devices of a fire alarm system, which is stored in a fire receiver and comprises a server and a communications terminal, wherein the server comprises a storage means for storing the database and a program for creating the database, a first transmission means for transmitting screen data showing a screen for creating the database to the communications terminal, and a creation means for creating the database according to the program based on the data transmitted from the communications terminal, and the communications terminal comprises a display means for displaying a screen indicated by the screen data transmitted by the server, an input means for inputting data relating to the terminal device, and a second transmission means for transmitting the data input by the input means to the server.

[0071] In a preferred embodiment, the communications terminal is equipped with a reading means for reading a tag that displays or records the identification information of the fire receiver and the identification information of the server, a third transmission means for transmitting the identification information of the fire receiver displayed or recorded by the tag read by the reading means to the server whose identification information is displayed or recorded by the read tag, and a fourth transmission means for transmitting identification information of a property in which the fire receiver is installed to the server, and the server is equipped with a first memory control means for storing the identification information of the fire receiver and the property identification information transmitted by the communications terminal in association with each other in the memory means.

[0072] In a further preferred embodiment, the communications terminal comprises a receiving means for receiving the database from the server, a second storage control means for storing the database received by the receiving means in a storage medium, a reading means for reading data relating to the terminal device stored in the storage medium from the fire receiver when the storage medium is attached to the fire receiver and the database stored in the storage medium is stored in the fire receiver, and a fifth transmitting means for transmitting the data read by the reading means to the server.

[0073] In a further preferred embodiment, the communications terminal comprises a sixth transmitting means for transmitting an issuance request for authentication information to the server, the request including data indicating the license number of the fire protection equipment engineer, and the server comprises a seventh transmitting means for transmitting the authentication information to the communications terminal in response to the issuance request, and an authentication means for authenticating a user of the communications terminal based on the authentication information, and the first transmitting means transmits the screen data to the communications terminal only if authentication by the authentication means is successful.

[0074] Furthermore, a server according to one embodiment of the present invention is a server for creating a database relating to terminal devices of a fire alarm system that is stored in a fire receiver, and is characterized in that it comprises a storage means for storing the database and a program for creating the database, a transmission means for transmitting screen data showing a screen for creating the database to a communication terminal, and a creation means for creating the database in accordance with the program based on the data transmitted from the communication terminal.

[0075] In addition, a fire receiver in one embodiment of the present invention is a fire receiver equipped with a tag that displays or records its own identification information and the identification information of a server to which the identification information is sent, and the identification information of the fire receiver displayed or recorded on the tag is transmitted to the server where the identification information is displayed or recorded by the tag when the tag is read by a communication terminal, and is stored in the server in correspondence with the identification information of the property in which the fire receiver is installed, transmitted from the communication terminal.

[0076] Furthermore, a program according to one embodiment of the present invention is characterized in that it causes a computer for creating a database relating to terminal devices of a fire alarm system, which is stored in a fire receiver, to function as a storage means for storing the database and a program for creating the database, a transmission means for transmitting screen data showing a screen for creating the database to a communication terminal, and a creation means for creating the database in accordance with the program based on the data transmitted from the communication terminal.

[0077] (Effect of supplementary notes) According to the appendix, it is possible to assist in creating a database relating to fire alarm systems, which is managed in a server. [Explanation of symbols]

[0078] 1...database creation system, 2...server, 3...communication terminal, 4...communication line, 5...fire alarm equipment, 21...control unit, 22...storage unit, 23...communication unit, 31...control unit, 32...storage unit, 33...display unit, 34...input unit, 35...reading unit, 36...card interface unit, 37...communication unit, 51...fire receiver, 52...transmitter, 53...fire detector, 54...repeater, 55...smoke exhaust machine, 56...shutter, 57...fire door, 58...district bell, 211...first transmission means, 212...creation means, 213...first memory control means, 214...sixth transmission means, 215...writing means, 221...user information DB, 222...property information DB, 223...terminal device information DB, 224...DB creation program, 311...second transmission means, 312...third transmission means, 313...fourth transmission means, 314...receiving means, 315...fifth transmission means, 511...control unit, 512...storage unit, 513...display unit, 514...input unit, 515...terminal device interface unit, 516...card interface unit, 517...printer unit, 5121...terminal device information DB

Claims

1. A database updating system for centrally managing a database relating to a terminal device of a fire alarm system, the database being stored in a fire receiver, comprising: a server connected to the fire receiver or the communication terminal via a communication line and storing the database; The database stored in the server includes a first terminal device information database and a property information database; The property information database is composed of records including at least fields of the "model name" and "property information" of the fire control device, The first terminal device information database is composed of records including at least the fields of "address", "type" and "installation location" of the terminal device, similar to the second terminal device information database stored in the fire receiver, and a table composed of the records is created for each property, The server generates a database to be stored in the fire control device based on the data received from the communication terminal, The database stored in the fire receiver is updated with the database generated by the server, A database update system characterized in that, when updating of the database stored in the fire receiver is completed, the server updates the database stored in the server based on the data received from the communication terminal and the database stored in the fire receiver before the update.

2. An update history table for storing an update history of the property information database, 2. The database updating system according to claim 1, wherein a new record is added to said update history table every time the contents of said property information database are updated.

3. 3. The database updating system according to claim 2, wherein the update history table is made up of fields for "update date and time" and "updater."

4. The database stored on the server includes a user information database; The user information database is composed of fields of "company information" and "person in charge information", 4. The database updating system according to claim 3, wherein the "ID" of the "person in charge information" is used in user authentication for updating the database.

5. The database update system according to claim 4, characterized in that the database update operation includes editing a first terminal device information database stored on the server, and updating a second terminal device information database stored in the fire receiver based on the edited data.

6. A database updating system for centrally managing a database relating to a terminal device of a fire alarm system, the database being stored in a fire receiver, comprising: a server connected to the fire receiver or the communication terminal via a communication line and storing the database; The server generates a database to be stored in the fire control device based on the data received from the communication terminal, The database stored in the fire receiver is updated with the database generated by the server, The server updates the database stored in the server based on data received from the fire receiver or the communication terminal; The database stored in the server includes a first terminal device information database; The first terminal device information database is composed of records including at least fields of "address", "type" and "installation location" of the terminal device, similar to the second terminal device information database stored in the fire receiver; The database update operation includes editing a first terminal device information database stored on the server, and updating a second terminal device information database stored in the fire control device based on the edited data; A database update system characterized in that, when the server completes updating the second terminal device information database stored in the fire receiver, it updates the first terminal device information database stored in the server based on the edited data received from the communication terminal and the second terminal device information database before the update that was stored in the fire receiver.

7. The fire receiver is not connected to the communication line, the server is connected to the communication terminal via the communication line; The database generated by the server is stored in a storage medium; the storage medium is connected to the fire receiver; The database before the update stored in the fire control device is stored in the storage medium, The database stored in the fire control device is updated with the generated database stored in the storage medium; A database update system as described in any one of claims 1 to 6, characterized in that when updating of the database stored in the fire receiver is completed, the database stored in the server is updated based on the data received from the communication terminal and the database before the update stored in the storage medium.

Images