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

Abstract

The invention provides a building management device, a building management system, and an ID registration method in the building management device, which can more simply realize addition or change of a user ID related to transfer of user authority in a management system while ensuring safety. A building management device (1) receives a new ID addition request based on an operation of a registered user who logs in the building management device with a registered ID. The building management device (1) transmits an authentication code to the destination of the new user associated with the new ID related to the addition request. A building management device (1) registers a new ID in the building management device (1) when an authentication code is input by a registered user who logs in the building management device (1).

Description

Technical Field

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

[0002] In a management system for managing a building or other management object, a user who is granted management authority for the management object logs into the management system using his / her own user ID and password to perform management tasks. When the user who is the source of authority transfer is transferred or absent, the user who is the target of authority transfer transfers the authority granted to his / her own user ID to inherit the management tasks.

[0003] For example, Patent Document 1 discloses a method for transferring authority in a user password authentication system in which a user can simply and securely transfer part of his authority to another user. According to the prior art disclosed in Patent Document 1, the user to whom the authority is transferred receives an authentication ticket from the user from whom the authority is transferred, and sends the authentication ticket back to the management system, which performs authentication through the management system, thereby enabling management services to be performed with the transferred authority.

[0004] Patent Document 1: Japanese Patent Application Publication No. 2006-221506 Summary of the invention

[0005] Problems to be solved by the invention

[0006] However, in the above-mentioned prior art, the issuance process of the authentication ticket involved in the transfer of authority is completed only by the operation of the user of the authority transfer source. Therefore, it is impossible to confirm whether the authentication ticket for transferring authority to the correct transfer object is correctly issued. Therefore, in the case where the authentication ticket is mistakenly issued to the wrong transfer object, there is a problem of having to reissue the authentication ticket to the correct transfer object. In addition, there is a security risk that the user who is mistakenly issued the authentication ticket may perform unauthorized management business by impersonation.

[0007] The present invention has been made in view of the above background, and an object of the present invention is to more easily realize the addition or change of a user ID involved in the transfer of authority of a user in a management system while ensuring security.

[0008] Means for solving problems

[0009] As a method for solving the above-mentioned problems, a building management device for managing a building comprises: an ID storage unit, which stores authentication information including an ID of a user who can log in to the building management device and information related to authentication elements; a login ID determination unit, which accepts input of the authentication information and determines whether login based on the ID can be performed according to whether the accepted authentication information is registered in the ID storage unit; an ID registration acceptance unit, which accepts an additional request for a new ID based on an operation of a registered user, and the registered user has logged in to the building management device using the registered ID registered in the ID storage unit; an authentication code sending unit, which sends an authentication code to the destination of a new user associated with the new ID involved in the additional request accepted by the ID registration acceptance unit; and a registration processing unit, which registers the new ID in the ID storage unit when the registered user who has logged in to the building management device enters the authentication code sent from the authentication code sending unit.

[0010] Effects of the Invention

[0011] According to the present invention, it is possible to more easily realize the addition or change of a user ID related to the transfer of authority of a user in a management system while ensuring security. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 It is a diagram showing the structure of a building management system according to an embodiment.

[0013] Figure 2 It is a diagram showing the structure of an ID addition and change screen according to an embodiment.

[0014] Figure 3 It is a diagram schematically illustrating the ID addition and change process according to the embodiment.

[0015] Figure 4A This is a flowchart showing the ID addition and change processing according to the implementation method.

[0016] Figure 4B This is a flowchart showing the ID addition and change processing according to the implementation method.

[0017] Figure 4C This is a flowchart showing the ID addition and change processing according to the implementation method. DETAILED DESCRIPTION

[0018] Hereinafter, an embodiment of the present invention will be described in detail based on the accompanying drawings. This embodiment is only an example for implementing the present invention and does not limit the technical scope of the present invention. Each element and its combination described in this embodiment may not all be necessary for the solution means of the invention.

[0019] In the following description, the same reference numerals are attached to the same structures in principle, and repeated descriptions are omitted. The number of each component in the following description is not limited unless otherwise noted.

[0020] In the following description, the processing performed by the program is sometimes described. The computer uses a processor (such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)) to perform processing determined by the program using a memory, a storage device, a communication port, etc. Therefore, the main body of the processing performed by executing the program can also be set as a processor. The functional unit that performs the processing is realized by the processor executing the program.

[0021] In the following description, the case where the user logs in to the building management device using the email address as the ID is described. However, it is also possible to log in to the building management device using an ID different from the email address containing characters, numbers, and symbols. In this case, it is assumed that the email address is associated with the ID.

[0022] (Configuration of Building Management System S According to Embodiment)

[0023] Figure 1 The diagram shows the structure of a building management system S according to the embodiment. The building management system S includes a building management device 1, a terminal 2a communicably connected to the building management device 1 via a network N1, and a terminal 2b communicably connected to the building management device 1 via a network N2.

[0024] The communication method of the networks N1, N2 and the terminals 2a, 2b can be any of wired and wireless. In addition, the networks N1 and N2 can be any of a public network, a virtual closed network and a dedicated line network. The networks N1 and N2 can be the same network or different networks.

[0025] Terminal 2a is a first user terminal, which is a computer capable of communicating with the building management device 1 via the network N1. Terminal 2b is a second user terminal, which is a computer capable of communicating with the building management device 1 via the network N2. The computer may be any of portable, mobile and fixed types. In addition, the computer may be any of a personal computer, a tablet computer and a smart phone. In the present embodiment, terminal 2a is a terminal operated by a user with a registered ID (user A), and terminal 2b is a terminal (smart phone) operated by a user with a new ID (user B), but the present invention is not limited thereto.

[0026] The building management device 1 includes an ID storage unit 11, a login ID determination unit 12, an ID registration acceptance 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. In addition, in this embodiment, only the structure of the building management device 1 related to the present invention is illustrated and described, and the illustration and description of the management functions of the elevator, escalator, air conditioner, etc. generally provided in the building management device 1 are omitted.

[0027] The ID storage unit 11 stores an ID storage table 11T. Figure 3 ) in which a login ID 111, a password 112, a deletion flag 113, management target building information 114, and an authentication code 115 are correspondingly registered for each user allowed to log in to the building management device 1.

[0028] Login ID 111 is an ID of a user who is allowed to log in to the building management device 1, and uses an email address. Password 112 is input by the user together with the login ID when logging in to the building management device 1, and is information to ensure the legitimacy of the logged-in user. Login ID 111 and password 112 are examples of user authentication information.

[0029] The deletion flag 113 uses "false" to indicate that the corresponding record is valid, and uses "true" to indicate that the corresponding record is invalid.

[0030] The management target building information 114 is an example of authority information given to the user of the corresponding login ID 111, and in the present embodiment, the identification information of the building that the corresponding user is responsible for managing is stored.

[0031] The authentication code 115 is a code sent to authenticate a new login ID when a user who logs in to the building management device 1 with the corresponding login ID 111 adds a new login ID or changes the login ID. In the authentication code 115, "-" is stored before sending, and the authentication code is stored when sending.

[0032] The login ID determination unit 12 receives the ID and password of the registered user registered in the ID storage unit 11 input from the terminal 2a via the network N1. The login ID determination unit 12 determines whether the received ID and password are registered in the ID storage unit 11, and determines that the login based on the ID is permitted if they are registered, and determines that the login based on the ID is not permitted if they are not registered. When the login is permitted, the login ID determination unit 12 receives the operation of the building management device 1 from the terminal 2a of the permitted user via the network N1, and requests the corresponding functional unit to process.

[0033] The ID registration accepting unit 13 accepts a request for adding a new ID via the network N1, the request for adding a new ID being based on an operation of a registered user logging into the building management device 1 with a registered ID registered in the ID storage unit 11 input from the terminal 2a. The request for adding a new ID includes items such as "registered ID", "new ID", "additional change of distinguishing information", and "resetting of password", for details, see Figure 2 The ID registration accepting unit 13 transfers the request for adding a new ID to the authentication code transmitting unit 14 .

[0034] The authentication code sending unit 14 sends the authentication code to the destination (via the terminal 2b of the network N2) of the new user associated with the new ID involved in the additional request accepted by the ID registration acceptance unit 13. In the present embodiment, since the ID uses an email address, the "destination of the new user associated with the new ID" becomes the email address represented by the ID. In the case where the ID uses a method other than an email address, the email address is associated with the ID as the destination of the user, so the "destination of the new user associated with the new ID" also becomes the email address. In addition, it is not limited to an email address, and it can also be destination information that can send and receive communication messages via the network, such as other destination information such as the MSISDN (Mobile Station International Subscriber Directory Number, so-called telephone number) of SMS (Short Message Service).

[0035] When the registered user who has logged in to the building management device 1 using the registered ID inputs the authentication code sent from the authentication code sending unit 14 from the terminal 2a via the network N1, the registration processing unit 15 registers the new ID involved in the additional request in the ID storage unit 11. At this time, the authentication code can be transmitted from the user of the operation terminal 2b to the user of the operation terminal 2a by any communication means.

[0036] (Structure of ID Addition and Change Screen 21 of Embodiment)

[0037] Figure 2 This is a diagram showing the structure of the ID addition and change screen 21 of the embodiment. When the user operating terminal 2a logged in to the building management device 1 sends a request to add a new ID to the building management device 1, the screen data is sent through the ID registration receiving unit 13, and the ID addition and change screen 21 is displayed on a display device (not shown) connected to the terminal 2a.

[0038] The ID additional change screen 21 has a user name display field 22, a corresponding user ID, i.e., a registered ID display field 23, a new ID input field 24, a new ID (for confirmation) input field 25, an additional change classification information designation field 26, a password reset designation field 27, and an authentication code transmission button 28. In addition, the ID additional change screen 21 has an authentication code input field 29, a return button 30, and an update / exit button 31.

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

[0040] The new ID input column 24 accepts input of a new ID used when adding or changing an object ID by a corresponding user who has logged in to the building management device 1. The new ID (for confirmation) input column 25 similarly accepts input of a new ID for confirmation of the new ID input to the new ID input column 24. In addition, when an ID other than an e-mail address is used as an ID, an input column for communication destination information such as an e-mail address associated with the ID input together with the ID is provided.

[0041] The addition and change classification information designation column 26 can be selected from ID addition 261 and ID change 262. When ID addition 261 is selected, a new ID is added as the addition and change classification information, and ID addition is specified to maintain the validity of the registered ID without invalidating it. When ID change 262 is selected, a new ID is added as the addition and change classification information, and ID change is specified to invalidate the registered ID in order to use the added new ID instead of the registered ID.

[0042] The password reset designation field 27 allows selection from not resetting the password 271 and resetting the password 272. When not resetting the password 271 is selected, the password of the registered ID is used as the password of the new ID to be added, so the password is not reset. When resetting the 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.

[0043] When the user A of the registered ID who operates the terminal 2a that sends the request to add the new ID presses the authentication code sending button 28, the authentication code sending unit 14 sends the authentication code to the email address (terminal 2b) indicated by the new ID input to the new ID 24. The authentication code to be sent to the email address indicated by the new ID is input into the authentication code input field 29.

[0044] When the user of the registered ID who operates the terminal 2a that transmits the request to add a new ID presses the return button 30, the ID addition change screen 21 is terminated and the screen to which the ID addition change screen 21 is transferred is displayed.

[0045] When the user of the registered ID who operates the terminal 2a that sends the request to add a new ID presses the update / exit button 31, the input information to the ID addition and change screen 21 is sent to the registration processing unit 15 of the building management device 1. The input information is the information input to each of the registered ID 23, the new ID 24, the additional change classification information designation column 26, the password reset designation column 27, and the authentication code input column 29. Thereafter, the user of the registered ID exits from the building management device 1.

[0046] (Overview of ID addition and change processing in embodiment)

[0047] Figure 3 This is a diagram for explaining the outline of the ID addition and change process according to the embodiment. Figure 3 The following describes changes in information in the ID storage table 11T registered in the ID storage unit 11 that occur in response to an ID change.

[0048] First, in Figure 3 In step S101 shown, user A who has registered an ID attempts to log in to the building management device 1 using the login ID 111 "AAA@BBB.com" and the password "YYYY". The combination of the login ID 111 "AAA@BBB.com" and the password "YYYY" has been registered in the ID storage table 11T of the ID storage unit 11, so user A is authenticated and logs in to the building management device 1. The registration information of user A in the ID storage table 11T at this time is shown in the record 116.

[0049] Next, in step S102, the authentication code transmission unit 14 transmits the authentication code to the destination of user B associated with the new ID in response to the request for adding the new ID of user A. The authentication code transmission unit 14 stores the authentication code transmitted to the destination of user B in the column of the authentication code 115 of the record 116 of user A in the ID storage table 11T.

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

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

[0052] Furthermore, since the request to add a new ID indicates 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 .

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

[0054] In addition, Figure 3 In the description, the ID change is described in which the record 116 is invalidated by setting the delete flag 113 of the record 116 to "true". The ID addition is the same as the ID change except that the process of setting the delete flag 113 of the record 116 to "true" is not performed in the ID change process.

[0055] (ID addition and change processing of implementation method)

[0056] Figure 4A , Figure 4B and Figure 4C This is a flowchart showing the ID addition and change processing according to the implementation method.

[0057] First, in Figure 4A In step S11, the login ID determination unit 12 ( Figure 1 ) receives a login request from user A using authentication information including a registered ID and password via a login screen (not shown) displayed on a display screen (not shown) of the terminal 2a, and permits the login. Next, in step S12, the ID registration accepting unit 13 of the building management device 1 receives a process in which user A, whose login was accepted in step S11, presses an "ID addition change button" by operating a menu screen (not shown) displayed on the display screen of the terminal 2a.

[0058] Next, in step S13, the ID registration accepting unit 13 displays the ID additional change screen 21 ( Figure 2 ) is displayed on the display screen of terminal 2a.

[0059] Next, in step S14, the ID registration accepting unit 13 accepts input of a new ID or the like on the ID addition and change screen 21 and a button 28 (send authentication code) via the terminal 2a. Figure 2 When the authentication code sending button 28 is pressed, input information such as a new ID is sent from the terminal 2a to the building management device 1.

[0060] Next, in step S15, the ID registration receiving unit 13 ( Figure 1 ) checks the input information input and sent 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 whether there are no uninput items in the input information, whether there is no registered ID that matches the new ID, whether the new ID matches the new ID (for confirmation), etc. If the ID registration acceptance unit 13 checks OK, the processing is transferred to step S17, and if the check is NG, the processing is transferred 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 urging the terminal 2a to input again, and the processing returns to step S14.

[0061] In step S17, the authentication code transmitting unit 14 ( Figure 1 ) generates a 4-digit random number authentication code, for example, and stores it in the ID storage table 11T ( Figure 3 ) in the column of the authentication code 115 of the record 116 of the corresponding registered ID.

[0062] Next, in step S18, the authentication code transmission unit 14 transmits the authentication code generated in step S18 to the terminal 2b in which the mail address associated with the new ID is set.

[0063] Next, in step S19, the registration processing unit 15 ( Figure 1 ) determines whether the time t1 elapsed from the sending of the email in step S18 is less than the predetermined time Th1. The registration processing unit 15 transfers the processing to step S21 when t1≤Th1 (step S19: Yes), and transfers the processing to step S20 when t1>Th1 (step S19: No). The case where t1>Th1 includes the case where the authentication code is not delivered to the terminal 2b and the authentication code is not input into the ID addition and change screen 21, for example, due to an error in the type of the new ID (email address).

[0064] In step S20, the registration processing unit 15 adds the ID change screen 21 ( Figure 2) is output to the terminal 2a, and the process returns to step S14. In step S20, the registration processing unit 15 notifies the terminal 2a operated by the user A who has registered the ID, so as to confirm that the email address of the new user associated with the new ID is correct and re-enter the additional request.

[0065] In step S21, the registration processing unit 15 receives input of an authentication code and an update / exit button 31 ( Figure 2 ) is pressed.

[0066] Then, in Figure 4B In step S22, the registration processing unit 15 checks the input information including the authentication code input to the ID addition and change screen 21 and sent in step S21, and determines whether the input information is correct. The registration processing unit 15 checks whether there are no uninput items in the input information, whether the authentication code is consistent with the authentication code stored in the ID storage unit 11, etc. If the check is OK, the registration processing unit 15 transfers the process to step S23, and if the check is NG, the process is transferred to step S28.

[0067] Next, in step S23 , the registration processing unit 15 executes a logout process via the login ID determination unit 12 to log out the user A having registered the ID from the building management device 1 .

[0068] In step S24, the registration processing unit 15 stores the ID in the ID storage table 11T ( Figure 3 ) to create a record 117 of a new ID. Next, in step S25, the registration processing unit 15 determines whether the additional change distinguishing information included in the request for adding a new ID sent from the terminal 2a in step S14 is an ID addition or an ID change. If the additional change distinguishing information is an ID change (step S25: Yes), the registration processing unit 15 transfers the processing to step S26, and if the additional change distinguishing information is an ID addition (step S25: No), the registration processing unit 15 transfers the processing to step S27.

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

[0070] 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 change processing. Furthermore, when the new ID addition request received in step S14 specifies resetting the password, the registration processing unit 15 notifies the terminal 2b of the link information of the URL (Uniform Resource Locator) for resetting the password. When step S27 is completed, the processing transfers to Figure 4C Step S31. The URL link information for resetting the password is an example of the resetting information. The resetting method is not limited to the case of using the URL link information.

[0071] On the other hand, in step S28, since there is an error in the input information or the authentication code, the registration processing unit 15 outputs an error message to the terminal 2a urging re-input. Next, in step S29, the registration processing unit 15 determines whether the cumulative number of times N of the error message output in step S28 is less than the predetermined number of times Th2. If N≤Th2, the registration processing unit 15 returns the process to step S21 ( Figure 4A ) and urges re-input, and when N>Th2, the processing is transferred to step S29.

[0072] In step S30, the registration processing unit 15 outputs to the terminal 2a that the ID change screen 21 ( Figure 2 ) Enter the correct authentication code and a timeout error message will be displayed, ending the ID addition and change processing.

[0073] On the other hand, Figure 4C In step S31, the registration processing unit 15 determines whether the request for adding a new ID accepted in step S14 includes a request for resetting the password (a password resetting is specified). If the request for adding a new ID includes a request for resetting (step S31: Yes), the registration processing unit 15 transfers the process to step S32. On the other hand, if the request for adding a new ID does not include a request for resetting (step S31: No), the registration processing unit 15 transfers the process to step S34.

[0074] In step S32, the registration processing unit 15 determines whether the URL for resetting the password sent to the terminal 2b in step S27 has been clicked. If the URL has been clicked (step S32: Yes), the registration processing unit 15 transfers the process to step S33, and if the URL has not been clicked (step S32: No), the process returns to step S30.

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

[0076] 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 a 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 user login is performed, but description thereof is omitted.

[0077] (Effects of Embodiments)

[0078] In the above embodiment, when a user with a registered ID who has logged into the building management device 1 requests to add a new ID, an authentication code for authenticating the new ID is sent to a terminal on the new ID side associated with the new ID. Then, the terminal on the registered ID side accepts input of the authentication code received by the terminal on the new ID side. Therefore, it is possible to easily add and change an ID and ensure a sufficient security level.

[0079] In addition, in the above-mentioned embodiment, the ID storage table 11T ( Figure 3 ) and the authority information of the record 116 associated with the registered ID in the ID storage table 11T, and the new record 117 is registered in the ID storage table 11T in association with the new ID. Therefore, the authority transfer to the new user can be easily and reliably implemented.

[0080] In addition, in the above-mentioned embodiment, in the ID storage table 11T ( Figure 3 ) in the record 116 of the registered ID. Therefore, the ID change is performed by the same process as the addition of a new ID, so the ID change can be implemented simply and reliably.

[0081] In the above-described embodiment, the password associated with the added new ID is changed from the password of the registered ID of the copy source by resetting, so that the security level of the password can be maintained or improved when adding an ID or changing an ID.

[0082] In the above-described embodiment, by simply adding or changing the ID distinction information to specify either ID addition or ID change, a new ID can be created that faithfully transfers the authority information of the registered ID, or the ID can be changed safely without accidentally changing the authority information.

[0083] In addition, in the above-mentioned embodiment, when the input of the authentication code is not accepted until the predetermined time has passed since the authentication code was sent, a notification is made to confirm that the destination of the new user associated with the new ID is correct and the additional request is re-entered. Therefore, as long as the destination information associated with the new ID is wrong, the additional processing of the new ID will not be completed. Therefore, especially when the ID is replaced by an email address, the occurrence of an undesirable situation such as the transfer of authority to a wrong ID can be avoided, and high security can be ensured.

[0084] (Variation Example)

[0085] In the above-mentioned embodiment, it is assumed that the authority information of the management target building information 114 is managed by associating it with each user in the ID storage table 11T of the ID storage unit 11. However, it is not limited to this, and it is also possible to manage the users with authority by associating them with each building. In this case, instead of the management target building information 114 of the ID storage table 11T, an authority management table is used for managing the users with authority by associating them with each building. Furthermore, when adding a new ID, the user of the new ID is added in the authority management table in such a way that the new ID is associated with each building to which the authority is granted.

[0086] Furthermore, in the above-described embodiment, password authentication using a password (knowledge information) as an authentication element for ensuring the legitimacy of a login user who inputs an ID into the building management device 1 and attempts to log in is exemplified. However, this is not limiting, and the knowledge information may also be a PIN code, a secret question and answer. Furthermore, the authentication method is not limited to the method using knowledge information, and may be a biometric authentication using biometric information such as fingerprints and faces, or other authentication methods using information held by a mobile phone, an IC card, or the like. When other authentication methods are used, information related to the authentication element used for authentication is stored in the ID storage table 11T instead of the password 112 (for example, fingerprint information in the case of fingerprint authentication, and the phone number of the destination of the short message in the case of SMS authentication using a mobile phone as information held by the mobile phone, etc.). In addition, on the ID addition and change screen 21 ( Figure 2 ) is replaced with a password reset designation column 27 and a column for accepting instructions for resetting biometric information and owned information. Figure 4C In step S27, a URL for resetting the biometric information and the owned information is sent by e-mail, and in steps S32 to S34, resetting of the biometric information and the owned information is accepted.

[0087] The present invention is not limited to the building management device 1 for managing a building as in the above-mentioned embodiment, but can be widely applied to systems having management objects (for example, elevator systems, escalator systems, air conditioning systems, factory management systems, and management systems of other management objects).

[0088] The present invention is not limited to the above-mentioned embodiments, and can be implemented using any constituent elements without departing from the scope of the main purpose. The above-described embodiments and modifications are only examples, and the present invention is not limited to these contents as long as the features of the invention are not impaired. In addition, various embodiments and modifications are described above, but the present invention is not limited to these contents. Other modes considered within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention.

[0089] For example, a part of each function of each device in the above-mentioned embodiment can be set in another device or other functional unit, or the functions of other devices or other functional units can be set in the same device or the same functional unit. That is, the dispersion and integration of the processing functions of each function can be appropriately changed based on the processing load and execution efficiency.

[0090] Explanation of symbols

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

Claims

1. A building management device for managing a building, characterized in that: The building management device comprises: an ID storage unit storing authentication information including an ID of a user who can log in to the building management device and information related to authentication elements; a login ID determination unit that receives input of the authentication information and determines whether login based on the ID can be performed based on whether the received authentication information is registered in the ID storage unit; an ID registration accepting unit that accepts a request for adding a new ID based on an operation of a registered user who has logged in to the building management device using a registered ID registered in the ID storage unit; an authentication code transmitting unit that transmits an authentication code to a destination of a new user associated with the new ID involved in the additional request accepted by the ID registration accepting unit; as well as A registration processing unit registers the new ID in the ID storage unit when the registered user who has logged in to the building management device inputs the authentication code transmitted from the authentication code transmission unit.

2. The building management device according to claim 1, characterized in that: The registration processing section copies the authority information associated with the registered ID in the ID storage section, and registers the copy in the ID storage section in association with the new ID.

3. The building management device according to claim 2, characterized in that: The registration processing unit invalidates the registered ID in the ID storage unit.

4. The building management device according to claim 2 or 3, characterized in that: The ID registration accepting unit accepts the addition request and a reset request for resetting information related to the authentication element associated with the new ID based on an operation by the registered user, The registration processing unit registers the new ID in the ID storage unit, and when accepting the resetting request, sends resetting information for resetting the information related to the authentication elements to the destination of the new user, and resets the information related to the authentication elements associated with the new ID based on the input of the resetting information.

5. The building management device according to claim 1, characterized in that: The ID registration receiving unit receives the addition request and input of addition / change classification information indicating whether the addition request is an addition or a change of the ID. The registration processing unit determines which category of addition and change of the ID the additional change distinguishing information represents. If the additional change distinguishing information represents the category of addition of the ID, the registered ID is not invalidated and its validity is maintained. If the additional change distinguishing information represents the category of change of the ID, the registered ID is invalidated.

6. The building management device according to claim 1, characterized in that: The registration processing unit notifies the user to confirm that the destination of the new user associated with the new ID is correct and re-enters the addition request when the authentication code is not input within a predetermined time period after the authentication code transmission unit transmits the authentication code.

7. A building management system comprising: 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, characterized in that: The building management device comprises: an ID storage unit storing authentication information including an ID of a user 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 login based on the ID can be performed according to whether the received authentication information is registered in the ID storage unit; an ID registration accepting unit that accepts a request for adding a new ID based on an operation of a registered user who has logged in to the building management device using the registered ID registered in the ID storage unit via the first user terminal; an authentication code transmitting unit configured to transmit an authentication code to the second user terminal, the second user terminal being set with a destination of a new user associated with the new ID involved in the additional request accepted by the ID registration accepting unit; as well as A registration processing unit registers the new ID in the ID storage unit when the registered user who has logged in to the building management device via the first user terminal inputs the authentication code transmitted from the authentication code transmission unit.

8. An ID registration method performed by a building management device for managing a building, characterized in that: The building management device 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 authentication elements. The ID determination unit of the building management device receives input of the authentication information and determines whether login based on the ID is possible based on whether the received authentication information is registered in the ID storage unit. The ID registration accepting unit of the building management device accepts a request for adding a new ID based on an operation of a registered user who has logged in to the building management device using a registered ID registered in the ID storage unit. The authentication code transmitting unit of the building management device transmits an authentication code to a destination of a new user associated with the new ID involved in the additional request accepted by the ID registration accepting unit, The registration processing unit of the building management device registers the new ID in the ID storage unit when the registered user who has logged in to the building management device inputs the authentication code transmitted from the authentication code transmission unit.

Images