Management system, authority management method and program

Abstract

To provide a management system, an authority management method and a program that allow a device associated with a facility, to be freely operated by using a terminal of a user of the facility.SOLUTION: A control part 704 of a management server in a management system includes: a management group specification part for specifying a management group on the basis of management identification information that is identification information of a management group to which a device associated with a predetermined facility belong, according to facility use information related to the use of the predetermined facility; an authority assigning part for assigning at least a part of a use authority of the device belonging to the management group, to a prescribed user, on the basis of the specified management identification information; and an instruction control part for validating an instruction from the prescribed user to whom at least a part of the use authority has been assigned, with regard to an instruction related to at least a part of the use authority.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present disclosure relates to a management system, an authority management method, and a program. [Background technology]

[0002] For example, Patent Document 1 discloses a technique in which the range within which an air conditioner's operation can be controlled by remote control is restricted in stages according to predetermined conditions. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2007-024420 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the technology disclosed in Patent Document 1, the range of operation control is limited according to a predetermined condition, so that there is a risk that the user cannot freely operate the equipment using the personal terminal. However, in a lodging facility or the like, a user of the lodging facility may take home a remote control for operating the in-room equipment (television, air conditioner, etc.), so it is desirable for the user to be able to freely operate the in-room equipment of the lodging facility using the personal terminal. One aspect of the present disclosure aims to provide a management system, an authority management method, and a program that enable the user of the facility to freely operate the equipment associated with the facility using the terminal of the facility user. [Means for solving the problem]

[0005] A management system of one embodiment of the present disclosure includes a management identification information identification unit that identifies management identification information, which is identification information of a management group to which an apparatus associated with a specified facility belongs, based on facility usage information regarding the use of the specified facility, an authority granting unit that grants at least a portion of the usage authority of the apparatus belonging to the management group to a specified user based on the identified management identification information, and an instruction control unit that validates instructions from the specified user to which at least a portion of the usage authority has been granted, with regard to instructions regarding at least a portion of the usage authority.

[0006] An authority management method of one aspect of the present disclosure includes the steps of: identifying a management identification information, which is identification information of a management group to which an apparatus associated with a specified facility belongs, based on facility usage information regarding the use of the specified facility; granting at least a portion of the usage authority of the apparatus belonging to the management group to a specified user based on the identified management identification information; and validating instructions from the specified user to which at least a portion of the usage authority has been granted, with respect to instructions regarding at least a portion of the usage authority.

[0007] A program of one embodiment of the present disclosure causes a computer to perform the following functions: identify management identification information, which is identification information of a management group to which equipment associated with a specified facility belongs, based on facility usage information regarding the use of the specified facility; grant at least a portion of the usage authority of the equipment belonging to the management group to a specified user, based on the identified management identification information; and validate instructions from the specified user to which at least a portion of the usage authority has been granted, with respect to instructions regarding at least a portion of the usage authority. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an example of an overall configuration of a management system. [Diagram 2] FIG. 2 is a diagram illustrating an example of an electrical configuration of a first user terminal. [Diagram 3] FIG. 2 is a diagram illustrating an example of an electrical configuration of a service server. [Figure 4] 2 is a diagram illustrating an example of a functional configuration of a control unit of the service server. FIG. [Diagram 5] FIG. 11 illustrates an example of a management identification information table. [Figure 6] FIG. 11 is a diagram showing an example of reservation information. [Figure 7] FIG. 2 is a diagram illustrating an example of an electrical configuration of a management server. [Figure 8] 2 illustrates an example of a functional configuration of a control unit of the management server; FIG. [Figure 9] FIG. 4 is a diagram illustrating an example of reservation management information according to the first embodiment. [Figure 10] FIG. 13 illustrates an example of a management group table. [Figure 11] 1 is a timeline illustrating an example of processing executed in the management system of the first embodiment. [Figure 12] 11 is a flowchart illustrating an example of a process executed by the management server of the first embodiment. [Figure 13] FIG. 13 illustrates an example of a management group table. [Figure 14] FIG. 1 illustrates an example of an overall configuration of a management system. [Figure 15] FIG. 2 is a diagram illustrating an example of an electrical configuration of a relay device. [Figure 16] FIG. 13 illustrates an example of a connection destination management table. [Figure 17] FIG. 13 is a diagram illustrating an example of reservation management information according to the second embodiment. [Figure 18] 13 is a timeline illustrating an example of a process executed in the management system of the second embodiment. [Figure 19] 13 is a flowchart illustrating an example of a process executed by the management server of the second embodiment. [Figure 20] FIG. 11 is a diagram showing an example of reservation information. [Figure 21] FIG. 13 is a diagram illustrating an example of reservation management information according to a third embodiment. [Figure 22] 13 is a timeline illustrating an example of a process executed in the management system of the third embodiment. [Figure 23] 13 is a flowchart illustrating an example of a process executed by the management server of the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, the same or equivalent elements are denoted by the same reference numerals, and duplicated descriptions will be omitted.

[0010] First embodiment The physical configuration, electrical configuration, and functional configuration of the management system 100 will be described with reference to Figs. 1 to 10. Fig. 1 is a diagram showing an example of the overall configuration of the management system 100. Fig. 2 is a diagram showing an example of the electrical configuration of the first user terminal 102. Fig. 3 is a diagram showing an example of the electrical configuration of the service server 120. Fig. 4 is a diagram showing an example of the functional configuration of the control unit 303. Fig. 5 is a diagram showing an example of the management identification information table 500. Fig. 6 is a diagram showing an example of the reservation information 600. Fig. 7 is a diagram showing an example of the electrical configuration of the management server 101. Fig. 8 is a diagram showing an example of the functional configuration of the control unit 704. Fig. 9 is a diagram showing an example of the reservation management information 900. Fig. 10 is a diagram showing an example of the management group table 1000.

[0011] 1, the management system 100 includes a management server 101, a first user terminal 102, a second user terminal 103, a device 110, and a service server 120. The management server 101, the first user terminal 102, the second user terminal 103, the device 110, and the service server 120 are connected to a network 130. For example, the network 130 is the Internet or a LAN (Local Area Network).

[0012] The service server 120 manages information related to reservations for facility use (such as the name of the reserved facility and the period of use). For example, the facility is an accommodation facility (such as a hotel, inn, private lodging, or private lodging). The management server 101 manages the usage authority for using the device 110 associated with the facility. The device 110 acquires control information via the network 130 and operates based on the acquired control information. The control information includes instructions for causing the device 110 to execute a function provided in the device 110. For example, the device 110 is a home appliance equipped with communication means. The home appliance is, for example, a television, an air conditioner, or the like.

[0013] The first user terminal 102 is used by a first user 141 who uses the facility, and is, for example, a smartphone, a tablet, a PC (Personal Computer), etc. The second user terminal 103 is used by a second user 142 who manages the device 110, and is, for example, a smartphone, a tablet, a PC, etc.

[0014] As illustrated in FIG. 2, the first user terminal 102 includes a storage unit 201, a communication unit 202, an operation unit 203, a display unit 204, a control unit 205, and the like. The storage unit 201 is a recording medium capable of storing various data, programs, and the like, and is, for example, a hard disk drive. The communication unit 202 is, for example, an interface for connecting to the network 130 and communicating. The operation unit 203 and the display unit 204 are, for example, a touch panel display. The control unit 205 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like, and controls the first user terminal 102. The electrical configuration of the second user terminal 103 is similar to that of the first user terminal 102, and therefore a detailed description thereof will be omitted.

[0015] 3, the service server 120 includes a storage unit 301, a communication unit 302, a control unit 303, and the like. The storage unit 301 is a recording medium capable of storing various data, programs, and the like, and is, for example, a hard disk drive. The communication unit 302 is, for example, an interface for connecting to and communicating with the network 130. The control unit 303 includes a CPU, RAM, ROM, and the like, and is responsible for controlling the service server 120.

[0016] As illustrated in FIG. 4, the control unit 303 includes a facility use information acquisition unit 401, a management identification information specification unit 402, a reservation information generation unit 403, and the like. The facility use information acquisition unit 401 acquires facility use information. The facility use information is information related to the use of a specific facility, and includes facility identification information, period information, and notification destination information. The facility identification information is information for identifying a facility, such as a facility name and a room number of the facility. The period information indicates an authorization period. The authorization period is a period during which the use authority to operate the device 110 can be granted to a first user 141 different from the administrator (second user 142) of the device 110. The notification destination information indicates a notification destination to which a connection request destination described later is notified, and indicates, for example, an email address of a user (for example, the first user 141) who has made a reservation to use the facility. The management identification information specification unit 402 specifies management identification information based on the facility use information. The management identification information is identification information of a management group to which a device corresponding to a specific facility belongs. The management group is information that manages the usage authority to operate the device 110. The reservation information generating unit 403 generates reservation information 600 (see FIG. 6). The reservation information 600 includes management identification information, period information, and notification destination information.

[0017] FIG. 5 is a diagram showing an example of a management identification information table 500. The management identification information table 500 shown in FIG. 5 includes facility identification information and management identification information in association with each other. For example, the management identification information table 500 shown in FIG. 5 includes facility identification information "Building 501_Room 510" and management identification information "group521" in association with each other. The facility identification information "Building 501_Room 510" indicates "Room 510" in "Building 501". The management identification information "group521" indicates that the management identification information of the management group to which the device 110 associated with "Room 510" in "Building 501" belongs is "group521".

[0018] An example of a method for generating the management identification information table 500 will be described below. For example, a facility manager inputs information identifying the facility (e.g., a building name "Building 501" and a room number "Room 510") to the service server 120. The control unit 303 of the service server 120 generates facility identification information "Building 501_Room 510" based on the input information identifying the facility. Furthermore, the control unit 303 generates management identification information "group 521" corresponding to the facility identification information "Building 501_Room 510".

[0019] If the management identification information table 500 is not stored in the storage unit 301, the control unit 303 associates the acquired facility identification information with the generated management identification information and generates the management identification information table 500. On the other hand, if the management identification information table 500 is stored in the storage unit 301, the control unit 303 associates the acquired facility identification information with the generated management identification information and registers them in the management identification information table 500.

[0020] FIG. 6 is a diagram showing an example of reservation information 600. The reservation information 600 includes management identification information, an authorization period, and notification destination information in association with each other. For example, the reservation information 600 illustrated in FIG. 6 includes management identification information "group521", period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59", and notification destination information "userb@xxx.com" in association with each other. This indicates that for the management group of management identification information "group521", it is possible to change the use authority of the device 110 corresponding to the management group from "September 1, 2020, 16:00:00" to "September 2, 2020, 9:59:59", and that the connection request destination is notified to "notification destination:userb@xxx.com".

[0021] An example of a method for generating the reservation information 600 will be described below. For example, when reserving the use of a facility, the first user 141 inputs information for identifying the facility (for example, the building name "Building 501" and the room number "Room 510"), information indicating the period for using the facility, and notification destination information into a facility use reservation screen provided by the service server 120. The facility use information acquisition unit 401 acquires facility use information including the facility use information "Building 501_Room 510", the period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59", and the notification destination information "userb@xxx.com" based on the input information. In this case, the management identification information identification unit 402 refers to the management identification information table 500 illustrated in FIG. 5, and identifies the management identification information "group521" based on the facility identification information included in the facility use information. Then, the reservation information generating unit 403 generates reservation information 600 including the management identification information “group521”, the period information “2020.09.01.16:00:00 to 2020.09.02.9:59:59”, and the notification destination information “userb@xxx.com”. The reservation information generating unit 403 stores the generated reservation information 600 in the storage unit 301.

[0022] 7, the management server 101 includes a storage unit 701, a communication unit 702, a timer 703, a control unit 704, and the like. The storage unit 701 is a recording medium capable of storing various data, programs, and the like, such as a hard disk drive. The communication unit 702 is an interface for connecting to the network 130 and communicating, and the like. The timer 703 detects the current date and time. The control unit 704 includes a CPU, RAM, ROM, and the like, and is responsible for controlling the management server 101.

[0023] As illustrated in FIG. 8, by the control unit 704 executing a program, various functional blocks such as a reservation information acquisition unit 801, a management group identification unit 802, a reservation management information generation unit 803, a connection request destination notification unit 804, a user identification unit 805, an authority granting unit 806, an authority management unit 807, and an instruction control unit 808 are realized.

[0024] The reservation information acquisition unit 801 acquires the reservation information 600 from the service server 120. The management group identification unit 802 identifies the management group based on the management identification information. The reservation management information generation unit 803 generates reservation management information 900 (see FIG. 9 ) based on the reservation information 600. The connection request destination notification unit 804 notifies the destination indicated by the destination information of the connection request destination to a specific device. When a connection request is made to a specific device, the user identification unit 805 identifies a specific user to whom the authority to use the device 110 is to be granted based on the connection request. The authority granting unit 806 grants at least a part of the authority to use the device 110 belonging to the management group to the specific user based on the management identification information identified by the management identification information identification unit 402. Specifically, the authority granting unit 806 grants at least a part of the authority to use the device 110 to the specific user for the authority granting period indicated by the period information. When the authority granting unit 806 grants at least a part of the authority to use the device 110 to a specific user, the authority management unit 807 prohibits the user having at least a part of the authority to use the device 110 from being changed until a specific condition is satisfied. The instruction control unit 808 validates an instruction from a specific user to whom at least a part of the authority to use the device 110 has been granted, regarding an instruction regarding at least a part of the authority to use the device 110.

[0025] Fig. 9 is a diagram showing an example of reservation management information 900. The reservation management information 900 shown in Fig. 9 includes management identification information, period information, connection request destination information, and notification destination information. The connection request destination information is information indicating the destination of a connection request to a predetermined device (e.g., the management server 101) different from the device 110, and is, for example, a URL (Uniform Resource Locator) for connecting to the predetermined device.

[0026] 9 includes management identification information "group521", period information "2020.09.01.16:00:00~2020.09.02.9:59:59", connection request destination information "http: / / aaa.bbb", and notification destination information "userb@xxx.com" in association with each other. The period information "2020.09.01.16:00:00~2020.09.02.9:59:59" indicates that the authorization period is from "September 1, 2020, 16:00:00" to "September 2, 2020, 9:59:59". Moreover, the reservation management information 900 illustrated in FIG. 9 indicates that, for the management group with the management identification information "group521", the connection request destination information "http: / / aaa.bbb" is to be notified to the notification destination information "userb@xxx.com".

[0027] An example of a method for generating the reservation management information 900 will be described below. It is assumed that the reservation information acquisition unit 801 acquires the reservation information 600 including the management identification information "group521", the period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59", and the notification destination information "userb@xxx.com". In this case, the reservation management information generation unit 803 generates the connection request destination information "http: / / aaa.bbb". For example, the connection request destination information "http: / / aaa.bbb" indicates, as the connection request destination, a URL corresponding to the management identification information "group521" among a plurality of URLs accessible to the management server 101.

[0028] The reservation management information generating unit 803 generates reservation management information 900 including the management identification information "group521", the period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59", the connection request destination information "http: / / aaa.bbb", and the notification destination information "userb@xxx.com". The reservation management information generating unit 803 stores the generated reservation management information 900 in the storage unit 701.

[0029] FIG. 10 is a diagram showing an example of a management group table 1000. The management group table 1000 includes a management group for each management identification information. The management group includes, for each management identification information, a management user ID, one or more pieces of device identification information, an authorized user ID, function information, and granted permission information in association with each other. The device identification information is information for identifying the device 110, and is, for example, an Internet Protocol (IP) address, a Media Access Control (MAC) address, a product number of the device 110, a number set in the device 110 by the second user 142, or the like. The function information is information for identifying a function provided in the device 110 (for example, a function name). The management user ID is information for identifying the second user 142 who manages the device 110 corresponding to the associated device identification information (for example, a user name). The authorized user ID is information for identifying a user who has the use authority to cause the device 110 to execute a function corresponding to the function information associated with the management identification information (for example, a user name).

[0030] The granted permission information is information that indicates whether it is permitted to change the user who has usage rights for the function corresponding to the associated function information. "Granted permission information: allowed" indicates that it is permitted to change the user who has usage rights for the function corresponding to the associated function information. "Granted permission information: not allowed" indicates that it is not permitted to change the user who has usage rights for the function. "Granted permission information: granted" indicates that usage rights for the function have been granted to a user other than the user of the administrative user ID.

[0031] The management group table 1000 illustrated in FIG. 10 includes a management group associated with the management identification information "group521" and a management group associated with the management identification information "group211". For example, the management group of the management identification information "group521" includes the device identification information "aa.bb.ccc.ddd" and the device identification information "ab.bc.cde.efg". Furthermore, the management group of the management identification information "group521" includes the management user ID "user_A", the device identification information "aa.bb.ccc.ddd", the function information "func_P, func_Q", the grant permission information "granted", and the authorized user ID "user_A" in association with each other. This indicates that the device 110 of the device identification information "aa.bb.ccc.ddd" has the functions corresponding to the function information "func_P, func_Q". Furthermore, the management group indicates that the authority to use the functions corresponding to the function information “func_P, func_Q” is given to the user “user_A”, and that the user “user_A” manages the device 110.

[0032] Also, in the management group of management identification information "group521", the function indicated in function information "func_R" is associated with the permission information "not allowed" and the authorized user ID "user_A". This indicates that the device 110 of device identification information "aa.bb.ccc.ddd" has the function indicated in function information "func_R", the user "user_A" has the authority to use the function, and the authority to use the device 110 is not granted to users other than "user_A". The same applies to device identification information "ab.bc.cde.efg", and a detailed description will be omitted.

[0033] An example of a method for generating the management group table 1000 will be described below. For example, the administrator (second user 142) of the device 110 registers the facility identification information "Building 501_Room 510" of the facility associated with the device 110, the device identification information "aa.bb.ccc.ddd", the device identification information "ab.bc.cde.efg", and the management user ID "user_A" in the management server 101. The control unit 704 of the management server 101 requests the service server 120 for management identification information associated with the facility identification information "Building 501_Room 510". The control unit 303 of the service server 120 refers to the management identification information table 500 (see FIG. 5) stored in the storage unit 301, and notifies the management server 101 of the management identification information "group521". The control unit 704 associates the management identification information "group521", the device identification information "aa.bb.ccc.ddd", the device identification information "ab.bc.cde.efg", and the management user ID "user_A" to generate an initial state management group. In the initial state management group, the authorized user ID is the same as the management user ID. In addition, in the initial information management group, function information and granted permission information are not registered.

[0034] When an initial state management group is generated, the second user terminal 103 associates the device identification information, the grant permission information, and the function information, and transmits them to the management server 101. For example, the second user 142 uses the second user terminal 103 to associate the device identification information "aa.bb.ccc.ddd", the grant permission information "OK", and the function information "func_P, func_Q", and registers them in the management server 101. The control unit 704 associates the device identification information "aa.bb.ccc.ddd", the grant permission information "OK", and the function information "func_P, func_Q", and registers them in the generated management group. Similarly, the second user 142 uses the second user terminal 103 to associate the device identification information "aa.bb.ccc.ddd", the grant permission information "NOT OK", and the function information "func_R", and registers them in the management server 101. The control unit 704 associates the device identification information "aa.bb.ccc.ddd", the grant permission information "not allowed", and the function information "func_R" and registers them in the generated management group. Similarly, the second user 142 uses the second user terminal 103 to associate the device identification information "ab.bc.cde.efg", the grant permission information "allowed", and the function information "func_S" and registers them in the management server 101. The control unit 704 associates the device identification information "ab.bc.cde.efg", the grant permission information "allowed", and the function information "func_S" and registers them in the generated management group.

[0035] If the management group table 1000 is not stored in the storage unit 701, the control unit 704 generates a management group table 1000 including the generated management group, and stores the generated management group table 1000 in the storage unit 701. On the other hand, if the management group table 1000 is stored in the storage unit 701, the control unit 704 registers the generated management group in the management group table 1000.

[0036] Various processes executed by the management system 100 will be described with reference to Fig. 11 to Fig. 13. Fig. 11 is a timeline showing an example of processes executed by the management system 100. Fig. 12 is a flowchart showing an example of processes executed by the management server 101. Fig. 13 is a diagram showing an example of a management group table 1000 in which part of the usage authority for the device 110 with device identification information "aa.bb.ccc.ddd" is given to the user "user_B".

[0037] A process of granting the first user 141 the right to use the device 110 will be described with reference to Fig. 11. In the following description, a case will be described in which the service server 120 provides a facility use reservation screen for making a reservation for use of a facility. At the time of starting the process illustrated in Fig. 11, the storage unit 701 stores a management group table 1000.

[0038] 11 is started, an authorized user ID that is the same as the management user ID is registered in the management group table 1000 for the function information "func_P, func_Q, func_R, func_S" associated with the management group identification information "group521". Also, at the time when the processing illustrated in Fig. 11 is started, the storage unit 301 stores a management identification information table 500. Furthermore, the management identification information table 500 includes management identification information included in the management group table 1000 stored in the storage unit 701 and facility identification information in association with each other.

[0039] At time T1101, the first user terminal 102 transmits facility use information to the service server 120. For example, when the first user 141 reserves the use of a facility (e.g., an accommodation facility), the first user 141 inputs the facility use information (facility identification information, period information, notification destination information indicating the email address of the first user 141, etc.) into a facility use reservation screen provided by the service server 120 using the first user terminal 102.

[0040] At time T1102, the service server 120 notifies the management server 101 of the reservation information. Specifically, the management identification information specifying unit 402 refers to the management identification information table 500 and specifies the management identification information based on the notified facility use information. The reservation information generating unit 403 generates reservation information 700 including the specified management identification information, period information included in the acquired facility use information, and notification destination information included in the acquired facility use information. The control unit 303 notifies the management server 101 of the generated reservation information 700.

[0041] At time T1103, the management server 101 generates reservation management information 900 based on the notified reservation information 700. At time T1104, the management server 101 notifies the first user terminal 102 of the connection request destination information included in the generated reservation management information 900.

[0042] At time T1105, the first user terminal 102 transmits a connection request including the user ID of the first user 141 to the notified connection request destination. Time T1105 is within the authorization period included in the notified facility usage information. At time T1106, the management server 101 grants at least a portion of the authorization to use the device 110 to the first user 141 who has made the connection request to a specific device.

[0043] As a result, in the management system 100 of this embodiment, the user to whom the authority to use the device 110 is granted is not specified in advance, and at least a part of the authority to use the device 110 can be granted to the first user 141 who has issued a connection request to a specific device. Furthermore, in the management system 100, if a user other than the administrator of the device 110 has no intention of using the device 110, the user does not request a connection to the specific device, and therefore the authority to use the device is not granted to the user. Therefore, in the management system 100, the authority to use the device 110 can be prevented from being unnecessarily granted to anyone other than the administrator.

[0044] For example, when the user ID of the first user 141 is granted the authority to use the device 110, the first user terminal 102 becomes able to transmit control information for operating the device 110 to the device 110 by an application program for operating the device 110. As a result, the management system 100 allows the first user 141 to freely operate the functions of the device 110 for which the authority to use has been granted, using the first user terminal 102.

[0045] At time T1107, the first user terminal 102 transmits the user ID of the first user 141 to whom usage authority has been granted, and control information for the device 110 to the management server 101. The control information includes device identification information of the device 110 to be controlled, function information, and information indicating the control content.

[0046] The instruction control unit 808 refers to the management group table 1000 and determines whether the acquired control information is valid based on the device identification information included in the acquired control information, the function information included in the acquired control information, and the user ID of the sender of the control information. Specifically, the instruction control unit 808 determines whether the user ID of the sender of the acquired control information is an authorized user ID associated with the acquired function information and device identification information. If the user ID of the sender of the control information is the authorized user ID, the instruction control unit 808 determines that the acquired control information is valid. On the other hand, if the user ID of the sender of the control information is not the authorized user ID, the instruction control unit 808 determines that the acquired control information is not valid.

[0047] If the acquired control information is valid at time T1108, the instruction control unit 808 transmits the control information to the device 110 corresponding to the device identification information included in the control information. When the device 110 acquires the control information, it controls the device 110 based on the acquired control information. On the other hand, if the acquired control information is not valid at time T1108, the instruction control unit 808 notifies the first user terminal 102, which is the sender of the control information, that the control information is not valid.

[0048] At time T1109 after the authorization period has elapsed, the management server 101 transfers the usage authority granted to the user ID of the first user 141 to the user with the administrative user ID. In other words, when the authorization period has elapsed, the management server 101 returns the usage authority of the device 110 to the administrator of the device 110. This allows the management server 101 to return the usage authority of the device 110 associated with the facility to the administrator of the device 110 without having the administrator of the device 110 perform an operation to return the usage authority.

[0049] 12, a description will be given of the processing executed by the management server 101 at time points T1103, T1104, T1106, and T1109 illustrated in Fig. 11. When the service server 120 notifies the management server 101 of the reservation information 600 (time point T1102) and the management server 101 acquires the reservation information 600, the control unit 704 starts the processing illustrated in Fig. 12.

[0050] In S1201, the reservation information acquisition unit 801 acquires the reservation information 600 including the management identification information, the period information, and the notification destination information. In S1202, the management group identification unit 802 refers to the management group table 1000 and identifies the management group based on the management identification information included in the reservation information 600 acquired in S1201.

[0051] In S1203, the reservation management information generating unit 803 generates reservation management information 900. Specifically, the reservation management information generating unit 803 generates the reservation management information 900 including the management identification information included in the reservation information 600, the authorization period included in the reservation information 600, the connection request destination information, and the notification destination information included in the reservation information 600 (time point T1103). In S1204, the connection request destination notifying unit 804 notifies the notification destination indicated in the notification destination information included in the reservation management information 900 generated in S1203 of the connection request destination (such as a URL) indicated by the connection request destination information (time point T1104).

[0052] In S1205, the authority management unit 807 determines whether the date and time measured by the timer 703 is within the authority grant period corresponding to the acquired reservation management information 900. Specifically, the authority management unit 807 determines whether the date and time measured by the timer 703 is within the authority grant period indicated by the period information included in the reservation management information 900. If the date and time is within the authority grant period corresponding to the reservation management information 900 (S1205: YES), the control unit 704 transitions the process to S1206.

[0053] In S1206, the user identification unit 805 determines whether or not a connection request has been made to the connection request destination notified in S1204. If there is no connection request to the connection request destination (S1206: NO), the control unit 704 continues the process by returning the process to S1205. On the other hand, if there is a connection request to the connection request destination (S1206: YES), the control unit 704 transitions the process to S1207.

[0054] In S1207, the user identification unit 805 determines whether authorization is permitted for the management group of the management identification information corresponding to the connection request in S1206. Specifically, the user identification unit 805 refers to the management group table 1000 and determines whether the management group of the management identification information corresponding to the connection request includes function information of "grant permission information: permitted". If the management group includes function information of "grant permission information: permitted", the user identification unit 805 determines that authorization is permitted. On the other hand, if the management group does not include function information of "grant permission information: permitted", the user identification unit 805 determines that authorization is not permitted.

[0055] If authorization is not permitted for the management group of the management identification information corresponding to the connection request (S1207: NO), the control unit 704 continues the process by returning the process to S1205. On the other hand, if authorization is permitted for the management group of the management identification information corresponding to the connection request (S1207: YES), the control unit 704 shifts the process to S1208.

[0056] In S1208, the user identification unit 805 identifies the user ID of the first user 141 who made the connection request based on the connection request. In S1209, the authorization unit 806 refers to the management group table 1000, and registers the user ID identified in S1208 as the authorized user ID associated with the function information for which authorization has been granted for the management group of the management identification information corresponding to the connection request (time point T1106). For example, it is assumed that the user ID identified in S1208 is "user_B". In this case, for example, the authorization unit 806 changes the authorized user ID to "user_B" for the function information "func_P, func_Q" for which authorization permission information is "allowed" associated with the device identification information "aa.bb.ccc.ddd" in the management group table 1000 shown in FIG. 10 (see FIG. 13). Similarly, the authority granting unit 806 changes the authorized user ID to "user_B" for the function information "func_S" for which the grant permission information associated with the device identification information "ab.bc.cde.efg" is "allowed" in the management group table 1000 shown in Fig. 10 (see Fig. 13). In this way, in the management system 100, when a connection request is made to a specific device during a designated authority granting period, the management system 100 can grant the user who made the connection request (e.g., the first user 141) authority to use the device 110 for one or more devices 110 associated with the facility.

[0057] The authority management unit 807 prohibits a change of a user having at least a part of the use authority until the authority granting period corresponding to the reservation management information 900 has elapsed. Specifically, the authority management unit 807 refers to the management group table 1000 and changes the grant permission information associated with the changed authorized user ID to "granted". For example, as shown in FIG. 13, in the management group table 1000, "grant permission information: allowed" associated with the device identification information "aa.bb.ccc.ddd" and the device identification information "ab.bc.cde.efg" is changed to "grant permission information: granted". Then, the control unit 704 continues the process by returning the process to S1205.

[0058] If it is not within the authorization period corresponding to the reservation management information 900 (S1205: NO), the authorization management unit 807 judges whether or not the authorization period corresponding to the reservation information 600 has elapsed (S1210). If the authorization period has not elapsed (S1210: NO), the control unit 704 continues the process by returning the process to S1205. On the other hand, if the authorization period has elapsed (S1210: YES), the control unit 704 transitions the process to S1211.

[0059] In S1211, the authority management unit 807 changes the authorized user ID to the management user ID for the management group of the management identification information corresponding to the connection request (time point T1109). Furthermore, the authority management unit 807 permits a change of users who have usage authority for the management group. Specifically, the authority management unit 807 refers to the management group table 1000, and changes the "granted permission information: granted" for the management group to "granted permission information: allowed." As a result, the authority management unit 807 makes it possible to grant usage authority to users other than the user of the management user ID for the function associated with the granted permission information.

[0060] For example, suppose that the device 110 with the device identification information "aa.bb.ccc.ddd" is an air conditioner equipped with a speaker. Furthermore, suppose that the air conditioner has a function "func_P=power on", a function "func_Q=temperature setting", and a function "func_R=audio output". In this case, the management group table 1000 illustrated in FIG. 13 indicates that the permissions for "power on" and "temperature setting" are given to a user with an authorized user ID "user_B". On the other hand, the management group table 1000 illustrated in FIG. 13 indicates that the permissions for "audio output" are given to a user with an authorized user ID "user_A".

[0061] For example, the first user terminal 102 associated with a user with an authorized user ID "user_B" transmits control information for controlling the "power on" or "temperature setting" functions of the device 110 to the management server 101 (time point T1107). Because the user authorized to use these functions is "user_B", the instruction control unit 808 controls the "power on" or "temperature setting" functions of the device 110 based on the transmitted control information. Therefore, the management system 100 allows a user using a facility to freely operate one or more devices 110 associated with the facility using the user's personal terminal, without requiring the administrator of the device 110 to perform an operation to specify a user authorized to use the device 110.

[0062] On the other hand, when the second user terminal 103 associated with the user with the administrative user ID "user_A" transmits control information for controlling the "power on" or "temperature setting" functions of the device 110 to the administrative server 101, the instruction control unit 808 determines that the received control information is invalid because the user with the authority to use these functions is "user_B". This enables the administrative server 101 to prevent the user with the administrative user ID "user_A" from operating the "power on" or "temperature setting" functions of the device 110.

[0063] Also, for example, the second user terminal 103 associated with the management user ID "user_A" transmits control information for controlling the function of "audio output" of the device 110 to the management server 101. Since the user having the authority to use this function is "user_A", the instruction control unit 808 controls the function of "audio output" of the device 110 based on the transmitted control information. As a result, in a state in which the user with the authorized user ID "user_B" is granted the authority to use "power on" and "temperature setting", the management server 101 can control the audio output from the device 110 based on the instruction of the user with the management user ID "user_A". As a result, even in a state in which the authority to use the device 110 is granted to a user different from the administrator, the management system 100 of this embodiment can allow the administrator of the device 110 to operate some of the functions of the device 110 based on the instruction from the administrator of the device 110.

[0064] Second Embodiment The physical configuration, electrical configuration, and functional configuration of a management system 1400 of this embodiment will be described with reference to Figs. 14 to 17. Fig. 14 is a diagram showing an example of the overall configuration of the management system 1400. Fig. 15 is a diagram showing an example of the electrical configuration of a relay device 1401. Fig. 16 is a diagram showing an example of a connection destination management table 1600. Fig. 17 is a diagram showing an example of reservation management information 1700. In the following embodiments, configurations and processes having substantially the same functions as those of the first embodiment are referred to by the same reference numerals, and descriptions thereof will be omitted, and only differences from the first embodiment will be described.

[0065] 1 is that the management system 1400 illustrated in Fig. 14 includes a relay device 1401. In the management system 1400, the device 110 and the relay device 1401 are connected to a network 1410. For example, the network 1410 is a local area network (LAN) in a facility where the device 110 is located. The relay device 1401 is a predetermined device that belongs to the same network 1410 as the device 110, and relays communication between the network 1410 and the network 130.

[0066] 15, the relay device 1401 includes a storage unit 1501, a communication unit 1502, a control unit 1503, and the like. The storage unit 1501 is a recording medium capable of storing various data, programs, and the like, and is, for example, a hard disk drive. The communication unit 1502 is, for example, an interface for connecting to and communicating with the network 130. The control unit 1503 includes a CPU, RAM, ROM, and the like, and is responsible for controlling the relay device 1401.

[0067] The electrical configuration of the management server 101 of this embodiment is as shown in Fig. 7. Moreover, the functional configuration of the control unit 704 of this embodiment is as shown in Fig. 8. When a connection request is made to a predetermined device (relay device 1401) belonging to the same network 1410 as the device 110, a user identification unit 805 of this embodiment identifies a predetermined user who is to be granted the authority to use the device 110 based on the connection request.

[0068] Fig. 16 is a diagram showing an example of a connection destination management table 1600. The connection destination management table 1600 shown in Fig. 16 includes management identification information and connection request destination information. In the connection destination management table 1600, the connection request destination information is information indicating a connection destination for connecting to the relay device 1401, and is, for example, an address of the relay device 1401. The address of the relay device 1401 is a unique address for communicating with the relay device 1401, and examples of the address include a MAC address and an IP address.

[0069] For example, the second user 142 who is the administrator of the device 110 inputs the management identification information and the connection request destination information including the address of the relay device 1401 to the management server 101 using the second user terminal 103. The control unit 704 generates the connection destination management information by associating the management identification information with the input connection request destination information including the address of the relay device 1401. If the connection destination management table 1600 is not stored in the storage unit 701, the control unit 704 generates the connection destination management table 1600 including the generated connection destination management information, and stores the generated connection destination management table 1600 in the storage unit 701. On the other hand, if the connection destination management table 1600 is stored in the storage unit 701, the control unit 704 registers the generated connection destination management information in the connection destination management table 1600.

[0070] Fig. 17 is a diagram showing an example of reservation management information 1700. As shown in Fig. 17, in the reservation management information 1700 of this embodiment, the connection request destination information indicates a connection destination for connecting to the relay device 1401, similar to the connection request destination information included in the connection destination management table 1600.

[0071] For example, assume that the reservation information 600 including the management identification information "group521" and the period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59" is acquired. In this case, the reservation management information generating unit 803 refers to the connection destination management table 1600 and identifies the connection request destination information "11.123.234.345.456" associated with the management identification information "group521". The reservation management information generating unit 803 generates reservation management information 1700 including the management identification information "group521", the period information "2020.09.01.16:00:00 to 2020.09.02.9:59:59", and the connection request destination information "11.123.234.345.456". The reservation management information generating unit 803 stores the generated reservation management information 1700 in the storage unit 701 .

[0072] 18 and 19, various processes executed by the management system 1400 will be described. Fig. 18 is a timeline showing an example of processes executed by the management system 1400. Fig. 19 is a flowchart showing an example of processes executed by the management server 101 of this embodiment.

[0073] The process of granting the first user 141 the authority to use the device 110 will be described with reference to Fig. 18. At the start of the process illustrated in Fig. 18, the storage unit 701 prestores the connection destination management table 1600. Time points T1801 and T1802 illustrated in Fig. 18 are similar to time points T1101 and T1102 illustrated in Fig. 11, and therefore detailed description thereof will be omitted.

[0074] At time T1803, the reservation management information generating unit 803 generates the reservation management information 1700. At time T1804, which is within the authorization period, the first user terminal 102 transmits a connection request including the user ID of the first user 141 to the relay device 1401. Time T1804 is within the authorization period included in the notified facility use information.

[0075] At time T1805, the relay device 1401 notifies the management server 101 of the user ID of the first user 141 included in the connection request. At time T1806, the authority granting unit 806 grants at least a part of the authority to use one or more devices 110 to the notified first user 141 for the management group of the management identification information included in the reservation management information 1700 corresponding to the connection request destination information (the address of the relay device 1401). The processing from time T1807 to time T1809 illustrated in Fig. 18 is similar to the processing from time 1107 to time T1109 illustrated in Fig. 11, and therefore detailed description will be omitted.

[0076] The processing executed by the management server 101 at time T1803 and time T1806 illustrated in Fig. 18 will be described with reference to Fig. 19. Note that the processing of S1201 and S1202 is as described above, and detailed description thereof will be omitted.

[0077] When the management group specification unit 802 specifies a management group based on the management identification information (S1202), the reservation management information generation unit 803 refers to the connection destination management table 1600 and acquires connection request destination information indicating the address of the relay device 1401 associated with the management identification information of the specified management group (S1901). The relay device 1401 is connected to the same network 1410 as the device 110 included in the management group specified in S1202.

[0078] In S1902, the reservation management information 1700 including the address of the relay device 1401 acquired in S1901 is generated (time T1803). The control unit 704 moves the process to S1205. The process of S1205 is as described above, and therefore a detailed description thereof will be omitted.

[0079] If it is the authorization period corresponding to the reservation management information 1700 (S1205: YES), the user identification unit 805 judges whether or not a connection request has been made to the relay device 1401 corresponding to the connection request destination information included in the reservation management information 1700 generated in S1902 (S1903). For example, it is assumed that a label or the like on which the address of the relay device 1401 is written is placed in a facility (for example, a guest room of a lodging facility) corresponding to the facility usage information, and the first user 141 in the room can view the label or the like. In this case, the first user 141 can input the address of the relay device 1401 to the first user terminal 102 while in the facility. As a result, the first user terminal 102 can transmit a connection request to the relay device 1401.

[0080] When a connection request is made to the relay device 1401 (S1903: YES) and authorization is permitted for the management group of the management identification information corresponding to the connection request (S1207: YES), the user identification unit 805 identifies the user ID of the first user 141 who is the connection request source based on the connection request to a predetermined connection request destination (S1208). Then, in S1209, the authorization granting unit 806 refers to the management group table 1000 and registers the user ID identified in S1208 as the authorized user ID associated with the function information for which authorization is permitted for the management group of the management identification information corresponding to the connection request destination information (the address of the relay device 1401) (time T1806). As a result, when the first user terminal 102 can connect to the relay device 1401 within the facility corresponding to the facility usage information, the management server 101 grants at least a part of the use authorization of the device 110 to the user ID of the first user 141 associated with the first user terminal 102. On the other hand, if there is no connection request to the relay device 1401 (S1903: NO), the control unit 704 continues the process by returning the process to S1205. Note that the processes from S1207 to S1211 are as described above, and therefore detailed description thereof will be omitted.

[0081] Third embodiment A third embodiment will be described. Fig. 20 is a diagram showing an example of reservation information 2000. Fig. 21 is a diagram showing an example of reservation management information 2100. Fig. 22 is a timeline showing an example of processing executed by the management system 100 of this embodiment. Fig. 23 is a flowchart showing an example of processing executed by the management server 101 of this embodiment.

[0082] The facility use information acquisition unit 401 of this embodiment acquires facility use information including facility identification information, period information, notification destination information, and user information. The user information indicates a specific user (e.g., the first user 141) to whom the authority to use the device 110 is granted.

[0083] The reservation information acquisition unit 801 of this embodiment acquires reservation information 2000 (see FIG. 20) including management identification information, period information, notification destination information, and user information. The reservation management information generation unit 803 of this embodiment generates reservation management information 2100 (see FIG. 21) including management identification information, period information, connection request destination information, notification destination information, and user information. The authority granting unit 806 of this embodiment grants at least a part of the authority to use the device 110 to a predetermined user corresponding to the user information included in the facility usage information.

[0084] 20 further includes user information "user_B". This indicates that the user with the user ID "user_B" is designated in advance as the person to whom the authority to use the device 110 is granted. Furthermore, the reservation management information 2100 illustrated in FIG. 21 further includes user information "user_B".

[0085] With reference to FIG. 22, a process of granting the first user 141 the right to use the device 110 in the management system 100 of this embodiment will be described.

[0086] At time T2201, the first user terminal 102 transmits facility use information including user information to the service server 120. For example, when the first user 141 makes a reservation for use of a facility, the first user 141 uses the first user terminal 102 to input facility use information including user information indicating the first user's user ID into a facility use reservation screen provided by the service server 120. The service server 120 generates reservation information 2000 including the user information based on the input facility use information. At time T2202, the service server 120 notifies the management server 101 of the reservation information 2000 including the user information. At time T2203, the management server 101 generates reservation management information 2100 including the user information. At time T2204, the management server 101 notifies the first user terminal 102 of the connection request destination information included in the generated reservation management information 2100.

[0087] At time T2205, the first user terminal 102 transmits a connection request to the notified connection request destination. Time T2205 is assumed to be within the authorization period included in the notified facility use information. At time T2206, the management server 101 grants at least a part of the authorization to use one or more devices 110 to the user ID indicated by the user information for the management group of the management identification information transmitted to the connection request destination. In this way, the management server 101 of this embodiment can grant at least a part of the authorization to use one or more devices 110 associated with the facility to the first user 141 designated in advance when reserving the use of the facility. The process from time T2207 to time T2209 is similar to the process from time T1107 to time T1109 illustrated in FIG. 11, and therefore a detailed description thereof will be omitted.

[0088] 22. The process executed by the management server 101 at time T2203, time T2204, time T2206, and time T2209 shown in Fig. 22 will be described with reference to Fig. 23. When the service server 120 notifies the management server 101 of the reservation information 2000 (time T2202) and the management server 101 acquires the reservation information 2000, the control unit 704 starts the process shown in Fig. 23.

[0089] In S2301, the reservation information acquisition unit 801 acquires the reservation information 2000 including the management identification information, the period information, the notification destination information, and the user information. Then, the control unit 704 shifts the process to S1202. The process of S1202 is as described above, and therefore a detailed description thereof will be omitted.

[0090] When the management group specification unit 802 specifies a management group (S1202), the reservation management information generation unit 803 generates reservation management information 2100 including the user information included in the reservation information acquired in S2301 (S2302, time point T2203). Then, the control unit 704 shifts the process to S1204. The processes from S1204 to S1207 are as described above, and detailed explanations are omitted. When authorization is permitted for the management group of the management identification information corresponding to the connection request (S1207: YES), the control unit 704 shifts the process to S2303.

[0091] In S2303, the authority granting unit 806 refers to the management group table 1000, and registers the user ID indicated by the user information as the authorized user ID associated with the function information for which authority has been granted for the management group of the management identification information corresponding to the connection request (time point T2206). Furthermore, the authority management unit 807 prohibits a change of the user having at least a part of the usage authority until the authority granting period corresponding to the reservation management information 2100 has elapsed. Then, the control unit 704 continues the process by returning the process to S1205. Note that the processes from S1207 to S1211 are as described above, and detailed explanations will be omitted.

[0092] Therefore, in the management system 100 of this embodiment, when a first user 141 reserves use of a facility, the first user 141 can freely operate one or more devices 110 associated with the facility using the first user terminal 102 within a specified authorization period by notifying the service server 120 of his / her own user ID.

[0093] In the above description, the first user terminal 102 transmits the facility usage information to the service server 120. However, a terminal other than the first user terminal 102 may transmit the facility usage information to the service server 120.

[0094] Each process executed in the above-mentioned embodiment is not limited to the process mode exemplified in each embodiment. The above-mentioned functional blocks may be realized using either a logic circuit (hardware) formed in an integrated circuit or the like, or software using a CPU. For example, the processes executed in each functional block of the control unit 704 of the management server 101 may be partially executed by another computer, or all of the processes may be shared and executed by multiple computers. Each process executed in the above-mentioned embodiment may be executed by multiple computers. [Explanation of symbols]

[0095] 100 Management system, 101 Management server, 102 First user terminal, 103 Second user terminal, 110 Equipment, 120 Service server, 130 Network, 141 First user, 142 Second user, 201 Storage unit, 202 Communication unit, 203 Operation unit, 204 Display unit, 205 Control unit, 301 Storage unit, 302 Communication unit, 303 Control unit, 401 Facility use information acquisition unit, 402 Management identification information specification unit, 403 Reservation information generation unit, 500 Management identification information table, 600 Reservation information, 701 Storage unit, 702 Communication unit, 703 Timer, 704 Control unit, 801 Reservation information acquisition unit, 802 Management group specification unit, 803 Reservation management information generation unit, 804 Connection request destination notification unit, 805 User specification unit, 806 Authorization unit, 807 Authority management unit, 808 instruction control unit, 900 reservation management information, 1000 management group table, 1401 relay device, 1410 network, 1501 storage unit, 1502 communication unit, 1503 control unit, 1600 connection destination management table, 1700 reservation management information, 2000 reservation information, 2100 reservation management information

Claims

1. a management identification information specification unit that specifies management identification information, which is identification information of a management group to which a device associated with the specified facility belongs, based on facility usage information related to usage of a specified facility, the management identification information including notification destination information indicating a notification destination associated with a user who uses the facility; and a connection request destination notifying unit that notifies the notification destination indicated by the notification destination information of connection request destination information indicating a connection request destination for making a connection request to the device belonging to the management group indicated by the management identification information; an authority granting unit that grants, based on the connection request to the connection request destination, at least a part of the authority to use the device belonging to the management group indicated by the management identification information corresponding to the connection request destination, to the user corresponding to the notification destination; an instruction control unit that validates an instruction from the user to which at least a portion of the usage authority is granted, regarding an instruction related to at least a portion of the usage authority; A management system comprising:

2. The management system according to claim 1 , further comprising a user identification unit that, when a connection request is made to a predetermined device, identifies the predetermined user based on the connection request.

3. The management system according to claim 2 , wherein when the connection request is made to the predetermined device that belongs to the same network as the device, the user identification unit identifies the predetermined user based on the connection request.

4. The facility usage information includes user information indicating the predetermined user, The management system according to claim 1 , wherein the authority granting unit grants at least a part of the authority to use the device to the predetermined user corresponding to the user information.

5. The facility usage information includes period information indicating an authorization period, The management system according to any one of claims 1 to 3, wherein the authority granting unit grants at least a portion of the authority to use the device to the specified user for the authority granting period indicated by the period information.

6. The management system according to any one of claims 1 to 5, further comprising an authority management unit that, when the authority granting unit grants at least a portion of the usage authority of the device to the specified user, prohibits changing the user who has at least a portion of the usage authority until specified conditions are satisfied.

7. 1. A computer-implemented method for rights management, comprising: Identifying management identification information, which is identification information of a management group to which a device associated with the specified facility belongs, based on facility usage information related to the use of a specified facility, the facility usage information including notification destination information indicating a notification destination associated with a user using the facility; notifying the notification destination indicated by the notification destination information of connection request destination information indicating a connection request destination for making a connection request to the device belonging to the management group indicated by the management identification information; granting, based on the connection request to the connection request destination, at least a part of the authority to use the device belonging to the management group indicated by the management identification information corresponding to the connection request destination to the user corresponding to the notification destination; a step of validating an instruction from the user to which at least a portion of the usage authority is granted, regarding an instruction regarding at least a portion of the usage authority; Permission management methods, including:

8. On the computer, A function of identifying management identification information, which is identification information of a management group to which a device associated with the specified facility belongs, based on facility usage information related to the use of a specified facility, the facility usage information including notification destination information indicating a notification destination associated with a user using the facility; a function of notifying a notification destination indicated by the notification destination information of connection request destination information indicating a connection request destination for making a connection request to the device belonging to the management group indicated by the management identification information; a function of granting at least a part of the authority to use the device belonging to the management group indicated by the management identification information corresponding to the connection request destination, to the user corresponding to the notification destination, based on the connection request to the connection request destination; a function of validating an instruction from the user to which at least a portion of the usage authority is granted, regarding an instruction regarding at least a portion of the usage authority; A program that executes the following.

Images