Building management device, building management system, and id registration method in building management device

Abstract

To more easily achieve the addition or modification of a user ID related to the transfer of a user authority in a management system while guaranteeing security.SOLUTION: A building management device 1 accepts an addition request of a new ID based on the operation of a registered user who has logged into the building management device with a registered ID. The building management device 1 also transmits an authentication code to a new user associated with the new ID related to the addition request. In addition, the building management device 1 registers the new ID in the building management device 1 when the authentication code is entered by the registered user who has logged into the building management device 1.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a building management device, a building management system, and an ID registration method in a building management device. [Background technology]

[0002] In a management system that manages buildings and other managed objects, a user who has been granted management authority for the managed object logs into the management system using his / her own user ID and password to perform management tasks. Here, when the user who delegated the authority is transferred or absent, the user who delegated the authority delegates the authority granted to his / her user ID to the new user to take over the management tasks.

[0003] For example, Patent Document 1 discloses a method for delegating authority in a user password authentication system, which allows a user to easily and safely delegate part of his / her authority to another user. According to the conventional technology disclosed in Patent Document 1, the user to whom the authority is delegated receives an authentication ticket from the user who delegates the authority, returns the authentication ticket to the management system, and is authenticated by the management system, thereby enabling the user to perform management tasks with the delegated authority. [Prior art documents] [Patent documents]

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

[0005] However, in the above-mentioned conventional technology, the process of issuing an authentication ticket related to the transfer of authority is completed only by the operation of the user who is the source of the transfer of authority. Therefore, it is not possible to confirm whether the authentication ticket for transferring authority to the correct transfer destination has been correctly issued. Therefore, if an authentication ticket is mistakenly issued to an incorrect transfer destination, it is troublesome to reissue the authentication ticket to the correct transfer destination. In addition, there is a security risk that a user who has been mistakenly issued an authentication ticket may perform unauthorized management tasks by impersonating another user.

[0006] The present invention has been made in consideration of the above background, and aims to more easily realize the addition or change of user IDs related to the delegation of user authority in a management system while ensuring security. [Means for solving the problem]

[0007] As one aspect for solving the above problem, a building management device for managing a building includes an ID storage unit that stores authentication information including an ID of a user who can log in to the building management device and information related to an authentication element; a login ID determination unit that receives an input of the authentication information and determines whether or not a login is possible using the ID based on whether the received authentication information is registered in the ID storage unit; an ID registration reception unit that receives a request to add a new ID based on an operation of a registered user who has logged in to the building management device with a registered ID registered in the ID storage unit; an authentication code transmission unit that transmits an authentication code to a destination of a new user linked to the new ID related to the addition request received by the ID registration reception unit; and a registration processing unit that registers the new ID in the ID storage unit when the authentication code transmitted from the authentication code transmission unit is input by the registered user who has logged in to the building management device. Effect of the Invention

[0008] According to the present invention, it is possible to easily realize addition or modification of a user ID related to delegation of user authority in a management system while ensuring security. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing the configuration of a building management system according to an embodiment. [Diagram 2] FIG. 13 is a diagram showing the configuration of an ID addition / change screen according to the embodiment. [Diagram 3] FIG. 4 is an explanatory diagram illustrating an outline of an ID addition / change process according to the embodiment. [Figure 4A] 11 is a flowchart showing an ID addition / change process according to the embodiment. [Figure 4B] 11 is a flowchart showing an ID addition / change process according to the embodiment. [Figure 4C] 11 is a flowchart showing an ID addition / change process according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. This embodiment is merely an example for realizing the present invention, and does not limit the technical scope of the present invention. Not all of the elements and their combinations described in this embodiment are essential to the solution of the invention.

[0011] In the following description, the same components are generally designated by the same reference numerals, and repeated description will be omitted. The number of each component in the following description is not limited unless otherwise noted.

[0012] In the following explanation, the processing performed by a program may be described. A computer performs processing defined by a program using a processor (e.g., a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit)) while using memory, storage, communication ports, etc. Therefore, the processor may be the entity that performs processing by executing a program. The processor executes a program to realize a functional unit that performs processing.

[0013] In the following explanation, a case will be described in which a user logs in to a building management device using an email address as an ID. However, a user may log in to a building management device using an ID that is different from an email address and that includes letters, numbers, and symbols. In this case, it is assumed that the ID is linked to the email address.

[0014] (Configuration of the building management system S according to the embodiment) 1 is a diagram showing the configuration of a building management system S according to an embodiment. The building management system S includes a building management device 1, a terminal 2a communicatively connected to the building management device 1 via a network N1, and a terminal 2b communicatively connected to the building management device 1 via a network N2.

[0015] The communication form of the networks N1, N2 and the terminals 2a, 2b may be either wired or wireless. The networks N1 and N2 may be either a public network, a virtual closed network, or a dedicated network. The networks N1 and N2 may be the same network or different networks.

[0016] The terminal 2a is a first user terminal and is a computer capable of communicating with the building management device 1 via the network N1. The terminal 2b is a second user terminal and is a computer capable of communicating with the building management device 1 via the network N2. The computer may be any of a portable type, a mobile type, and a stationary type. The computer may also be any of a personal computer, a tablet, a smartphone, and the like. In this embodiment, the terminal 2a is a terminal operated by a user of a registered ID (user A), and the terminal 2b is a terminal (smartphone) operated by a user of a new ID (user B), but is not limited to this.

[0017] The building management device 1 has an ID storage unit 11, a login ID determination unit 12, an ID registration reception unit 13, an authentication code transmission unit 14, and a registration processing unit 15. The ID storage unit 11 stores an ID storage table 11T. Note that in this embodiment, only the configuration of the building management device 1 related to the present invention is illustrated and described, and illustrations and descriptions of management functions such as elevators, escalators, and air conditioning that are generally provided in the building management device 1 are omitted.

[0018] The ID storage unit 11 stores an ID storage table 11T. In the ID storage table 11T (FIG. 3), a login ID 111, a password 112, a deletion flag 113, managed building information 114, and an authentication code 115 for each user permitted to log in to the building management device 1 are registered in association with each other.

[0019] The login ID 111 is an ID of a user permitted to log in to the building management device 1, and is an email address. The password 112 is entered by the user together with the login ID when logging in to the building management device 1, and is information that ensures the legitimacy of the logged-in user. The login ID 111 and password 112 are examples of user authentication information.

[0020] The deletion flag 113 indicates that the corresponding record is valid when it is "false" and indicates that the corresponding record is invalid when it is "true".

[0021] The managed building information 114 is an example of authority information given to the user of the corresponding login ID 111, and in this embodiment, identification information of the building that the corresponding user is in charge of managing is stored.

[0022] The authentication code 115 is a code that is transmitted to authenticate a new login ID when a new login ID is added or a login ID is changed by a user who has logged in to the building management device 1 with the corresponding login ID 111. Before transmission, "-" is stored in the authentication code 115, and this authentication code is stored when the authentication code is transmitted.

[0023] The login ID determination unit 12 accepts, via the network N1, the ID and password of a registered user that are registered in the ID storage unit 11 and that are input from the terminal 2a. The login ID determination unit 12 judges whether the accepted ID and password are registered in the ID storage unit 11, and if they are registered, determines to permit login with this ID, and if they are not registered, determines to disallow login with this ID. If the login ID determination unit 12 permits login, it accepts an operation on the building management device 1 via the network N1 from the terminal 2a of the permitted user, and requests processing from the relevant functional unit.

[0024] The ID registration acceptance unit 13 accepts, via the network N1, a request to add a new ID based on an operation by a registered user who has logged in to the building management device 1 with a registered ID that has been entered from the terminal 2a and registered in the ID storage unit 11. The request to add a new ID includes items such as "registered ID," "new ID," "addition / change category information," and "password reset," the details of which will be described later with reference to FIG. 2. The ID registration acceptance unit 13 transfers the request to add a new ID to the authentication code transmission unit 14.

[0025] The authentication code sending unit 14 sends an authentication code to the destination (terminal 2b via network N2) of the new user linked to the new ID related to the addition request accepted by the ID registration accepting unit 13. In this embodiment, since an email address is used for the ID, the "destination of the new user linked to the new ID" is the email address indicated by the ID. If an email address other than an email address is used for the ID, an email address is linked to the ID as the user's destination, so the "destination of the new user linked to the new ID" is also an email address. Note that the destination is not limited to an email address, and may be other destination information capable of sending and receiving communication messages via a network, such as an MSISDN (Mobile Station International Subscriber Directory Number, a so-called phone number) of SMS (Short Message Service).

[0026] When the authentication code transmitted from the authentication code transmission unit 14 is input from the terminal 2a via the network N1 by a registered user who has logged in to the building management device 1 with a registered ID, the registration processing unit 15 registers the new ID related to the addition request in the ID storage unit 11. At this time, the authentication code may be transmitted from the user operating terminal 2b to the user operating terminal 2a by any communication means.

[0027] (Configuration of ID addition / change screen 21 according to the embodiment) 2 is a diagram showing the configuration of an ID addition / change screen 21 according to the embodiment. When a user who has logged in to the building management device 1 operates the terminal 2a to send a request to add a new ID to the building management device 1, screen data is sent by the ID registration acceptance unit 13 and the ID addition / change screen 21 is displayed on a display device (not shown) connected to the terminal 2a.

[0028] The ID addition / change screen 21 has a user name display field 22, a registered ID display field 23 which is the ID of the corresponding user, a new ID input field 24, a new ID (for confirmation) input field 25, an addition / change category information specification field 26, a password reset specification field 27, and an authentication code send button 28. The ID addition / change screen 21 also has an authentication code input field 29, a back button 30, and an update / logout button 31.

[0029] The user name display field 22 displays the user name, the name of the company, etc. of the user who has logged in to the building management device 1. The registered ID display field 23 displays the registered ID registered in the ID storage unit 11 of the user who has logged in to the building management device 1.

[0030] The new ID input field 24 accepts input of a new ID used when a user who has logged in to the building management device 1 adds or changes a target ID. The new ID (for confirmation) input field 25 similarly accepts input of a new ID for confirmation of the new ID input in the new ID input field 24. When an ID other than an email address is used, an input field is provided for communication destination information, such as an email address to be linked to the ID, which is input together with the ID.

[0031] The addition / change category information designation field 26 allows a selection between ID addition 261 and ID change 262. When ID addition 261 is selected, ID addition is specified as the addition / change category information, which adds a new ID and maintains the validity of the registered ID without invalidating it. When ID change 262 is selected, ID change is specified as the addition / change category information, which adds a new ID and invalidates the registered ID so that the added new ID can be used in place of the registered ID.

[0032] In the password reset specification field 27, it is possible to select from "Do not reset password" 271 and "Reset password" 272. When "Do not reset password" 271 is selected, the password of the registered ID is used as it is as the password of the new ID to be added, so the password is not reset. When "Reset password" 272 is selected, the password of the new ID to be added is changed from the password of the registered ID, so the password is reset.

[0033] When the authentication code send button 28 is pressed by user A of the registered ID operating terminal 2a that has sent the request to add a new ID, an authentication code is sent from the authentication code sending unit 14 to the email address (terminal 2b) indicated by the new ID entered in new ID 24. The authentication code sent to the email address indicated by the new ID is entered in the authentication code input field 29.

[0034] When the back button 30 is pressed by the user of the registered ID operating the terminal 2a that has sent the request to add a new ID, the ID addition / change screen 21 is terminated and the screen from which the ID addition / change screen 21 was transitioned is displayed.

[0035] When the update / logout button 31 is pressed by a user of a registered ID operating the terminal 2a that sent the request to add a new ID, the information entered into the ID addition / change screen 21 is sent to the registration processing unit 15 of the building management device 1. The input information is the information entered into each of the fields: registered ID 23, new ID 24, addition / change category information field 26, password reset field 27, and authentication code input field 29. The user of the registered ID then logs out from the building management device 1.

[0036] (Outline of ID addition / change processing according to embodiment) 3 is a schematic explanatory diagram of the ID addition / change process according to the embodiment, and will be used to explain changes in information in the ID storage table 11T registered in the ID storage unit 11 that accompany an ID change.

[0037] 3, user A with a registered ID attempts to log in to the building management device 1 using the login ID 111 "AAA@BBB.com" and password "YYYY". Since the combination of login ID 111 "AAA@BBB.com" and password "YYYY" is registered in ID storage table 11T of ID storage unit 11, user A is authenticated and logs in to the building management device 1. The registration information for user A in ID storage table 11T at this time is as shown in record 116.

[0038] Next, in step S102, the authentication code sending unit 14 sends an authentication code to the destination of user B linked to the new ID in response to a request to add a new ID by user A. The authentication code sending unit 14 stores the authentication code sent to the destination of user B in the column of authentication code 115 of record 116 of user A in the ID storage table 11T.

[0039] Next, in step S103, when the registration processing unit 15 accepts input of an authentication code by user A, it determines whether the authentication code input by user A matches the authentication code stored in the authentication code 115 of the record 116 of the ID storage table 11T.

[0040] If the authentication codes match, the registration processing unit 15 creates record 117 as shown in step S104. Record 117 sets login ID 111 to a new ID "CCC@BBB.com", and copies the values ​​of password 112, deletion flag 113, managed building information 114, and authentication code 115 from record 116 for user A in ID storage table 11T. Also, in record 117, the column for authentication code 115 is set to "-".

[0041] Since the request to add a new ID indicates an ID addition, the registration processing unit 15 sets the deletion flag 113 of the registered ID to "true" (delete) and deletes the record 116, as shown in step S105.

[0042] Furthermore, the registration processing unit 15 may change the password 112 in the record 117 corresponding to the user B who is a new user in response to a request for resetting the password.

[0043] 3, the ID change has been described in which the deletion flag 113 of the record 116 is set to "true" to invalidate the record 116. The ID addition is similar to the ID change, except that the process of setting the deletion flag 113 of the record 116 to "true" is not executed.

[0044] (ID addition / change process according to the embodiment) 4A, 4B, and 4C are flowcharts showing the ID addition and change process according to the embodiment.

[0045] First, in step S11 of Fig. 4A, the login ID determination unit 12 (Fig. 1) of the building management device 1 accepts a login request from user A using authentication information including a registered ID and password via a login screen (not shown) displayed on the display screen (not shown) of terminal 2a, and permits the login. Next, in step S12, the ID registration acceptance unit 13 of the building management device 1 accepts that user A, whose login was accepted in step S11, has pressed the "ID ADD / CHANGE BUTTON" by operating a menu screen (not shown) displayed on the display screen of terminal 2a.

[0046] Next, in step S13, the ID registration acceptance unit 13 displays the ID addition / change screen 21 (FIG. 2) on the display screen of the terminal 2a.

[0047] Next, in step S14, the ID registration acceptance unit 13 accepts, via the terminal 2a, input of a new ID and the like into the ID addition / change screen 21 and pressing of the authentication code send button 28 (FIG. 2). When the authentication code send button 28 is pressed, the input information such as the new ID is sent from the terminal 2a to the building management device 1.

[0048] Next, in step S15, the ID registration acceptance unit 13 (FIG. 1) of the building management device 1 checks the input information entered and transmitted to the ID addition / change screen 21 in step S14, and determines whether the input information is correct. The ID registration acceptance unit 13 checks the input information for any unentered items, for any registered IDs that match the new ID, and for whether the new ID matches the new ID (for confirmation). If the check is OK, the ID registration acceptance unit 13 moves the process to step S17, and if the check is NG, the process moves to step S16. In step S16, since there is an error in the input information, the ID registration acceptance unit 13 outputs an error message to the terminal 2a to prompt re-entry, and returns the process to step S14.

[0049] In step S17, the authentication code transmission unit 14 (Figure 1) of the building management device 1 generates an authentication code, for example a four-digit random number, and stores the generated authentication code in the authentication code 115 column of the record 116 of the corresponding registered ID in the ID storage table 11T (Figure 3).

[0050] Next, in step S18, the authentication code sending unit 14 sends the authentication code generated in step S18 to the terminal 2b to which the email address associated with the new ID has been set.

[0051] Next, in step S19, the registration processing unit 15 (FIG. 1) of the building management device 1 judges whether the elapsed time t1 from the e-mail transmission in step S18 is equal to or less than a predetermined time Th1. If t1≦Th1 (step S19 YES), the registration processing unit 15 proceeds to step S21, and if t1>Th1 (step S19 NO), the registration processing unit 15 proceeds to step S20. Cases where t1>Th1 include cases where the authentication code was not delivered to the terminal 2b and the authentication code was not entered into the ID addition / change screen 21 due to, for example, a typing error in the new ID (email address).

[0052] In step S20, the registration processing unit 15 outputs an error message to the terminal 2a indicating that the authentication code input to the ID addition / change screen 21 (FIG. 2) has timed out, and returns the process to step S14. In step S20, the registration processing unit 15 notifies the terminal 2a operated by the user A of the registered ID to confirm that the email address of the new user associated with the new ID is correct and to re-input the addition request.

[0053] In step S21, the registration processing unit 15 accepts, via the terminal 2a, input of an authentication code into the ID addition / change screen 21 by a user of a registered ID and pressing of the update / logout button 31 (FIG. 2).

[0054] 4B, the registration processing unit 15 checks the input information including the authentication code that was entered and transmitted to the ID addition / change screen 21 in step S21, and determines whether the input information is correct. The registration processing unit 15 checks whether the input information includes any items that have not been entered, whether the authentication code matches the authentication code stored in the ID storage unit 11, etc. If the check is OK, the registration processing unit 15 proceeds to step S23, and if the check is NG, the registration processing unit 15 proceeds to step S28.

[0055] Next, in step S23, the registration processing unit 15 executes a logout process via the login ID determination unit 12, and logs out user A, who has a registered ID, from the building management device 1.

[0056] In step S24, the registration processing unit 15 copies the record 116 of the corresponding registered ID in the ID storage table 11T (FIG. 3) to create a record 117 of the new ID. Next, in step S25, the registration processing unit 15 determines whether the addition / change category information included in the request to add a new ID sent from the terminal 2a in step S14 is ID change among ID addition and ID change. If the addition / change category information is ID change (step S25 YES), the registration processing unit 15 proceeds to step S26, and if the addition / change category information is ID addition (step S25 NO), the registration processing unit 15 proceeds to step S27.

[0057] In step S26, the registration processing unit 15 sets the deletion flag 113 in the record 116 of the corresponding registered ID to "true" to invalidate the registered ID.

[0058] In step S27, the registration processing unit 15 notifies the terminal 2b of the email address associated with the user B of the new ID of the completion of the ID addition and change process. Furthermore, if a password reset is specified in the request to add a new ID accepted in step S14, the registration processing unit 15 notifies the terminal 2b including link information of a URL (Uniform Resource Locator) for password reset. When step S27 ends, the process proceeds to step S31 in FIG. 4C. The link information of the URL for password reset is an example of reset information. The reset method is not limited to using URL link information.

[0059] On the other hand, in step S28, the registration processing unit 15 outputs an error message to the terminal 2a to prompt re-entry because there is an error in the input information or authentication code. Next, in step S29, the registration processing unit 15 judges whether the cumulative number N of error message outputs in step S28 is equal to or less than a predetermined number Th2. If N≦Th2, the registration processing unit 15 returns the process to step S21 (FIG. 4A) to prompt re-entry, and if N>Th2, moves the process to step S29.

[0060] In step S30, the registration processing unit 15 outputs a timeout error message to the terminal 2a indicating that the correct authentication code has not been entered into the ID addition / change screen 21 (FIG. 2) within a prescribed number of times, and ends the ID addition / change process.

[0061] 4C, the registration processing unit 15 determines whether or not the request to add a new ID received in step S14 includes a password reset request (password reset is specified). If the request to add a new ID includes a reset request (YES in step S31), the registration processing unit 15 proceeds to step S32. If the request to add a new ID does not include a reset request (NO in step S31), the registration processing unit 15 proceeds to step S34.

[0062] In step S32, the registration processing unit 15 determines whether the URL for resetting the password transmitted to the terminal 2b in step S27 has been clicked. If the URL has been clicked (step S32 YES), the registration processing unit 15 proceeds to step S33, and if the URL has not been clicked (step S32 NO), the registration processing unit 15 returns to step S30.

[0063] In step S33, the registration processing unit 15 displays a password reset screen (not shown) on the display screen of the terminal 2b. Next, in step S34, the registration processing unit 15 accepts a password reset for the new ID via the terminal 2b, and resets (changes) the password.

[0064] Next, in step S35, the login ID determination unit 12 displays a login screen (not shown) on the display screen of the terminal 2b. Next, in step S36, the login ID determination unit 12 accepts a login request from the user with a new ID via the login screen (not shown) displayed on the display screen of the terminal 2b. After step S35, general processing after the user logs in is executed, but a description thereof will be omitted.

[0065] (Effects of the embodiment) In the above embodiment, when a user of a registered ID who has logged in to the building management device 1 requests the addition of a new ID, an authentication code for authenticating the new ID is transmitted to a terminal on the new ID side that is linked to the new ID. Then, input of the authentication code received on the terminal on the new ID side is accepted on the terminal on the registered ID side. This makes it possible to easily add or change IDs while ensuring a sufficient level of security.

[0066] In the above embodiment, the authority information of the record 116 linked to the registered ID in the ID storage table 11T (FIG. 3) is copied, linked to a new ID, and registered in the ID storage table 11T as a new record 117. This makes it possible to transfer authority to a new user simply and reliably.

[0067] In the above embodiment, the record 116 of the registered ID is invalidated in the ID storage table 11T (FIG. 3). Therefore, the ID change is performed in the same process as adding a new ID, so that the ID change can be performed simply and reliably.

[0068] In addition, in the above-described embodiment, the password associated with the added new ID is changed by resetting it from the password of the registered ID that was the source of the duplication, thereby making it possible to maintain and improve the password security level when adding or changing an ID.

[0069] In addition, in the above-described embodiment, by simply specifying either ID addition or ID change using the addition / change category information, it is possible to create a new ID that faithfully transfers the authority information of a registered ID, or to safely change the ID without inadvertently changing the authority information.

[0070] In the above embodiment, if the input of the authentication code is not accepted within a predetermined time after the authentication code is sent, the user is notified to confirm that the destination of the new user associated with the new ID is correct and to re-input the addition request. Therefore, as long as the destination information associated with the new ID is incorrect, the process of adding the new ID is not completed. This makes it possible to avoid the inconvenience of delegating authority to an incorrect ID, particularly in cases where an email address is used as an ID, and ensures high security.

[0071] (Modification) In the above embodiment, it is assumed that the authority information of the managed building information 114 is associated with each user and managed in the ID storage table 11T of the ID storage unit 11. However, this is not limited to this, and it is also possible to manage each authorized user in association with each building. In this case, instead of the managed building information 114 in the ID storage table 11T, an authority management table is used in which authorized users are associated with each building and managed. When a new ID is added, the user of the new ID is added to the authority management table so that the new ID is associated with each building to which the authority is granted.

[0072] In the above embodiment, password authentication is exemplified, in which a password (knowledge information) is used as an authentication element to guarantee the legitimacy of a login user who inputs an ID into the building management device 1 and attempts to log in. However, the invention is not limited to this, and the knowledge information may be a PIN code or a secret question and answer. The authentication method is not limited to the knowledge information, and may be biometric authentication using biometric information such as a fingerprint or face, or other authentication methods using possession information such as a mobile phone or IC card. When other authentication methods are used, information related to the authentication element used for authentication (for example, fingerprint information in the case of fingerprint authentication, or a telephone number to which a short message is to be sent in the case of SMS authentication using a mobile phone as possession information) is stored in the ID storage table 11T instead of the password 112. In addition, the ID addition / change screen 21 (FIG. 2) is provided with a field for receiving an instruction to reset biometric information or possession information instead of the password reset designation field 27. To reset the biometric information or possession information, a URL for resetting the biometric information or possession information is sent by email in step S27 of FIG. 4C, and the resetting of the biometric information or possession information is accepted in steps S32 to S34.

[0073] The present invention is not limited to the building management device 1 that performs building management as in the above-described embodiment, but can be widely applied to systems with managed objects (e.g., elevator systems, escalator systems, air conditioning systems, plant management systems, and other management systems for managed objects).

[0074] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the features of the invention are not impaired. In addition, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention.

[0075] For example, some of the functions of each device in the above-described embodiments may be provided in other devices or other functional units, or functions provided in other devices or other functional units may be provided in the same device or the same functional unit. In other words, the distribution and integration of the processing functions of each function can be appropriately changed based on the processing load and execution efficiency. [Explanation of symbols]

[0076] S: building management system, 1: building management device, 2, 2a, 2b: terminals, 11: ID storage unit, 12: login ID determination unit, 13: ID registration reception unit, 14: authentication code transmission unit, 15: registration processing unit.

Claims

1. A building management device for managing a building, comprising: an ID storage unit that stores authentication information including IDs of users who can log in to the building management device and information related to authentication elements; a login ID determination unit that receives an input of the authentication information and determines whether or not login using the ID is permitted based on whether the received authentication information is registered in the ID storage unit; an ID registration receiving unit that receives a request to add a new ID based on an operation of a registered user who has logged in to the building management device with a registered ID registered in the ID storage unit; an authentication code sending unit that sends an authentication code to a destination of the new user associated with the new ID related to the addition request accepted by the ID registration accepting unit; a registration processing unit that registers the new ID in the ID storage unit when the authentication code transmitted from the authentication code transmission unit is input by the registered user who has logged in to the building management device; A building management device comprising:

2. The building management device according to claim 1, The registration processing unit: The authority information linked to the registered ID in the ID storage unit is copied, and the new ID is linked to the authority information and registered in the ID storage unit. A building management device comprising:

3. The building management device according to claim 2, The registration processing unit: The registered ID is invalidated in the ID storage unit. A building management device comprising:

4. The building management device according to claim 2 or 3, The ID registration reception unit receiving, together with the addition request, a reset request for resetting information related to the authentication element associated with the new ID based on an operation of the registered user; The registration processing unit: The new ID is registered in the ID storage unit, and when the reset request is accepted, reset information for resetting information related to the authentication element is transmitted to a destination of the new user, and the information related to the authentication element linked to the new ID is reset by input based on the reset information. A building management device comprising:

5. The building management device according to claim 1, The ID registration reception unit Accepting an input of addition / change category information indicating whether the addition request is for adding or changing the ID together with the addition request; The registration processing unit: Determining whether the addition / change category information indicates an addition or change category of the ID; If the added / changed classification information is an additional classification of the ID, the registered ID is not invalidated but is maintained valid; If the added / changed category information is a category of a change in the ID, the registered ID is invalidated. A building management device comprising:

6. The building management device according to claim 1, The registration processing unit: When the input of the authentication code is not accepted within a predetermined time after the authentication code is transmitted by the authentication code transmission unit, the new user is notified to confirm that the destination of the new user associated with the new ID is correct and to re-input the addition request. A building management device comprising:

7. A building management system including a building management device for managing a building, and a first user terminal and a second user terminal capable of communicating with the building management device via a network, The building management device includes: an ID storage unit that stores authentication information including IDs of users who can log in to the building management device and information related to authentication elements; a login ID determination unit that receives the authentication information input via the first user terminal and determines whether or not login using the ID is permitted based on whether the received authentication information is registered in the ID storage unit; an ID registration receiving unit that receives a request to add a new ID based on an operation of a registered user who logs into the building management device with a registered ID registered in the ID storage unit via the first user terminal; an authentication code sending unit that sends an authentication code to the second user terminal to which a destination of a new user associated with the new ID related to the addition request accepted by the ID registration accepting unit is set; a registration processing unit that registers the new ID in the ID storage unit when the authentication code transmitted from the authentication code transmission unit is input by the registered user who has logged in to the building management device via the first user terminal; A building management system comprising:

8. 1. An ID registration method executed by a building management device for managing a building, comprising: the building management device has an ID storage unit that stores authentication information including IDs of users who can log in to the building management device and information related to authentication elements; an ID determination unit of the building management device receives an input of the authentication information, and determines whether or not to permit login using the ID based on whether the received authentication information is registered in the ID storage unit; an ID registration reception unit of the building management device receives a request to add a new ID based on an operation of a registered user who logs in to the building management device with a registered ID registered in the ID storage unit; an authentication code transmission unit of the building management device transmits an authentication code to a destination of a new user associated with the new ID related to the addition request accepted by the ID registration acceptance unit; A registration processing unit of the building management device registers the new ID in the ID storage unit when the authentication code transmitted from the authentication code transmission unit is input by the registered user who has logged in to the building management device. An ID registration method comprising the steps of:

Images