Information Processing Method and Information Processing System

Abstract

A server (2) is provided with: a first reception unit (221) that receives, from a device (4) installed in a building, operation data of the device (4); a second reception unit (222) that receives, from a user terminal (1) corresponding to a user of the device 4, usage application information indicating an application for use of the device (4); a transmission unit (223) that transmits approval request information to an owner terminal (3) corresponding to an owner of the device (4) upon reception of the use application information; a third reception unit (224) that receives, from the owner terminal (3), approval information indicating an approval for use of the device (4); and a setting unit (225) that sets, upon reception of the approval information, restrictions on access by the owner to device data which includes the operation data and / or data generated on the basis of the operation data.

Description

Technical Field

[0001] The present disclosure relates to a technology for managing devices installed in a building.

Background Art

[0002] Patent Document 1 discloses a technology in which an access management table having access permission information for each device for each user is provided in a home network, and access from a user's operation terminal to a device is restricted according to the type of user or the location of the user.

[0003] However, the technology of Patent Document 1 does not assume a case where the user and the owner are different for the devices connected in the home network. Therefore, there is a problem that the user's device data is unconditionally provided to the owner of the device, and the privacy of the user cannot be protected.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

[0005] The present disclosure has been made to solve such problems, and provides a technology capable of protecting the privacy of a user even when the user and the owner are different for the devices installed in a building.

[0006] An information processing method according to an aspect of the present disclosure is an information processing method to be executed by a computer, which receives operation data of equipment installed in a building from the equipment, receives usage application information indicating a usage application of the equipment from a user terminal corresponding to a user of the equipment, transmits approval request information to an owner terminal corresponding to an owner of the equipment in response to the reception of the usage application information, receives approval information indicating approval of the usage of the equipment from the owner terminal, and sets a restriction on access by the owner to equipment data including at least one of the operation data or data generated based on the operation data in response to the reception of the approval information.

[0007] According to the present disclosure, even when the user and the owner are different with respect to the equipment installed in the building, the privacy of the user can be protected.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0009] (Findings Leading to the Present Disclosure) Generally, a rental service that rents a building such as a house or a room equipped with devices to a lessee (user) is known. In such a rental service, the lessor (owner) who rents out the building provides the service to the lessee (user) while managing a large number of devices installed in the building. Here, the devices to be managed are, for example, electrical appliances having a communication function and housing equipment devices, which are so-called IoT (Internet of Things) devices.

[0010] In a rental service, the maintenance or troubleshooting of the installed equipment is the responsibility of the owner. On the other hand, if equipment data such as the daily operation data of the equipment is provided to the owner, the user can receive various services such as maintenance of the equipment using the equipment data and automation of repair requests in case of failure. However, for this purpose, the user is required to provide the equipment data to the owner.

[0011] However, if all equipment data is unconditionally provided to the owner, there is a problem that even equipment data that the user does not want is provided to the owner, and the privacy regarding the user's life is not protected.

[0012] In the above-mentioned Patent Document 1, access to the user's equipment is restricted according to the user type and the operation location, but a case where the user and the owner are different for the equipment is not assumed, and there is no disclosure regarding restricting the owner's access to the equipment. Therefore, in Patent Document 1, the owner's access to the equipment data is permitted, and the user's privacy cannot be protected.

[0013] The present disclosure has been made to solve such problems, and aspects of the present disclosure will be described below.

[0014] An information processing method according to an aspect of the present disclosure is an information processing method to be executed by a computer, which receives operation data of equipment installed in a building from the equipment, receives usage application information indicating a usage application of the equipment from a user terminal corresponding to a user of the equipment, and in response to receiving the usage application information, transmits approval request information to an owner terminal corresponding to an owner of the equipment, receives approval information indicating approval for the usage of the equipment from the owner terminal, and in response to receiving the approval information, sets a restriction on access by the owner to equipment data including at least one of the operation data or data generated based on the operation data.

[0015] According to this configuration, in response to the reception of approval information by the owner terminal, access restrictions by the owner to device data including at least one of operation data or data generated based on the operation data are set. Thereby, it is possible to prevent the device data from being unconditionally provided to the owner and protect the user's privacy.

[0016] Also, according to this configuration, in response to the reception of device usage application information from the user terminal, approval request information is transmitted to the owner terminal, and approval information for device usage is received from the owner terminal. Therefore, it is possible to prevent the device from being used by a user who has not obtained the owner's approval.

[0017] In the above information processing method, the access restriction may include setting permission for the user to access the device data.

[0018] According to this configuration, since permission for the user to access the device data is set, the user can check their own living patterns from the device data or check the usage status of the device.

[0019] In the above information processing method, the data generated based on the operation data includes statistical data based on the operation data, and the access restriction may include permitting the owner to access only the statistical data among the operation data and the statistical data.

[0020] According to this configuration, since only the statistical data is permitted to be accessed by the owner, the operation data of the device itself is not provided to the owner, and the user's privacy can be protected. Also, since the statistical data is provided to the owner, the device can be managed.

[0021] In the above information processing method, the approval information includes first approval information for the use of the device and second approval information for the use of other devices installed in the building other than the device related to the use application. When the use application information of the other devices is received after the reception of the approval information including the second approval information, the approval request information for the other devices may not be transmitted, and the access restriction for the other devices may be set.

[0022] According to this configuration, the approval information includes first approval information for the use of the device and second approval information for the use of other devices installed in the building other than the device related to the use application. Therefore, the owner can approve the user's use applications for the device related to the use application and other devices together by the approval related to the second approval information.

[0023] Also, when the use application information of other devices is received after the reception of the approval information including the second approval information, the access restriction of the owner for the other devices can be set without transmitting the approval request information for the other devices to the owner terminal.

[0024] In the above information processing method, the transmission of the approval request information includes transmitting a list of the other devices to the owner terminal, and the list of the other devices may be presented to the owner via the owner terminal.

[0025] According to this configuration, since the list of other devices is presented to the owner, the owner can grasp the other devices to be approved together.

[0026] In the above information processing method, further, request information for a list of the devices is received from the user terminal, and in response to the request information, a list of the devices is transmitted to the user terminal. The list of the devices is presented to the user via the user terminal, and in the reception of the use application information, the use application information of the devices included in the list of the devices may be received.

[0027] According to this configuration, since a list of devices is presented to the user, the user can collectively apply for the use of the devices included in the device list.

[0028] In the above information processing method, further, the type of data included in the device data is transmitted to the user terminal, the type is presented to the user via the user terminal, and a permission setting type that is the type of data for which the owner permits the access among the types is received from the user terminal, and the access by the owner to the device data may be restricted according to the permission setting type.

[0029] According to this configuration, the type of data included in the device data is presented to the user, and a permission setting type that is the type of data for which the owner permits the access among the presented types is received from the user terminal. Therefore, the user can set the type of data for which the owner permits the access among the presented data types.

[0030] In the above information processing method, the type transmitted to the user terminal may include the type of data for which the access by the owner is permitted among the device data.

[0031] According to this configuration, the user can set the type of data for which the owner permits the access from among the types of data for which the access by the owner is permitted.

[0032] In the above information processing method, the permission setting type includes a maintenance type that is the type of data used for the maintenance of the device, and the access restriction may include permitting the access by the owner to the data corresponding to the maintenance type.

[0033] According to this configuration, the user can set whether to permit the access by the owner to the data of the maintenance type.

[0034] In the above information processing method, further, according to whether or not the owner is permitted to access data corresponding to the maintenance type, an incentive given to the user is determined, the incentive is transmitted to the user terminal, and the incentive may be presented to the user via the user terminal.

[0035] According to this configuration, since an incentive is given to the user according to whether or not the owner is permitted to access data corresponding to the maintenance type, it is possible to give the user an incentive to permit the owner to access such data. As a result, the possibility that the owner is permitted to access data corresponding to the maintenance type increases, and the management of the device becomes easier.

[0036] In the above information processing method, the permission setting type is received from the user terminal, and according to the permission setting type, access by the owner to the device data of other devices installed in the building other than the device related to the usage application may be restricted.

[0037] According to this configuration, since the access restriction by the owner of other devices is set according to the permission setting type set for the device related to the usage application, the setting of the permission setting type for the device related to the usage application can also be applied to other devices, and the setting of the permission setting type can be performed collectively.

[0038] In another aspect of the present disclosure, an information processing system includes: a first receiving unit that receives operation data of equipment installed in a building from the equipment; a second receiving unit that receives usage application information indicating a usage application of the equipment from a user terminal corresponding to a user of the equipment; a transmitting unit that transmits approval request information to an owner terminal corresponding to an owner of the equipment in response to the reception of the usage application information; a third receiving unit that receives approval information indicating approval of the usage of the equipment from the owner terminal; and a setting unit that sets a restriction on access by the owner to equipment data including at least one of the operation data or data generated based on the operation data in response to the reception of the approval information.

[0039] The present disclosure can also be realized as an information processing program that causes a computer to execute each characteristic configuration included in such an information processing method. Needless to say, such a computer program can be distributed via a computer-readable non-transitory recording medium such as a CD-ROM or a communication network such as the Internet.

[0040] Note that each of the embodiments described below shows a specific example of the present disclosure. The numerical values, shapes, components, steps, order of steps, etc. shown in the following embodiments are merely examples and are not intended to limit the present disclosure. In addition, among the components in the following embodiments, components not described in the independent claims indicating the most general concept are described as optional components. Also, in all embodiments, the respective contents can be combined.

[0041] (Embodiment 1) FIG. 1 is a block diagram showing an example of the configuration of an equipment management system 100 according to Embodiment 1 of the present disclosure. The equipment management system 100 includes a user terminal 1, a server 2 (an example of an information processing system), an owner terminal 3, and equipment 4. The user terminal 1 to the equipment 4 are communicably connected to each other via a network NT. The network NT is a wide-area communication network including, for example, an Internet communication network and a mobile phone communication network.

[0042] The user terminal 1 is composed of a mobile terminal such as a smartphone and a tablet computer, or a stationary personal computer. Specifically, the user terminal includes a processor such as a CPU, a memory, an input device, a display, and a communication circuit. The user terminal 1 is, for example, possessed by a user. The user is, for example, a resident of a building where the device 4 is installed.

[0043] The owner terminal 3 is composed of a mobile terminal such as a smartphone and a tablet computer, or a stationary personal computer. Specifically, the owner terminal 3 includes a processor such as a CPU, a memory, an input device, a display, and a communication circuit. The owner terminal 3 is possessed by the owner. The owner is, for example, the owner of a building where the device 4 is installed. The owner also owns the devices installed in the building.

[0044] The building is, for example, a rental apartment or a rental house rented by the owner to the user.

[0045] The device 4 includes electrical appliances and home equipment installed in the building. The device 4 is an IOT device that can be connected to the network NT via a communication circuit. The owner also rents the device 4 to the user. The electrical appliances are, for example, electrical appliances such as refrigerators, televisions, washing machines, microwave ovens, ovens, and recorders. The home equipment is, for example, a hot water supply system, an air conditioner, and a floor heating system.

[0046] The server 2 is, for example, a cloud server including one or more computers. The server 2 includes a memory 21, a processor 22, and a communication circuit 23. The memory 21 is a storage device such as a solid state drive or a hard disk drive. The memory 21 includes a device data DB (database) 211 and a device management DB (database) 212.

[0047] FIG. 2 is a diagram showing an example of the data configuration of the device data DB 211. The device data DB 211 is composed of a plurality of records that store device data 2111. The device data 2111 is the log data of device 4. Specifically, the device data 2111 includes a device ID, a type, an access right, and a value.

[0048] The device ID is an identifier of device 4 and includes, for example, the manufacturing number of device 4. The type is information indicating the type of the device data 2111 registered in the corresponding record. The types of the device data 2111 include installation information, operation data, and statistical data.

[0049] The installation information includes, for example, the model number, installation location, and installation date and time of device 4. The operation data is raw log data directly obtained from device 4 and includes, for example, error information, failure information, device control information, and operation history information. The statistical data is processed log data obtained by statistically processing the operation data and includes, for example, the average number of operations and average power consumption during a predetermined period. Since the operation data is raw log data, it may be data related to the user's privacy that can identify the user's lifestyle pattern, etc. On the other hand, since the statistical data is statistically processed log data, it is data that is difficult to identify the user's lifestyle pattern. Note that among the operation data or the data obtained by processing the operation data, the data related to the user's privacy is also referred to as utilization data.

[0050] The access right field stores the owner ID of the owner who has the right to use the device data 2111 registered in the corresponding record and the user ID of the user. The use of the device data 2111 includes, for example, viewing the device data 2111. The owner ID is an identifier of the owner and includes, for example, at least one of the owner's name and a pre-set password. The user ID is an identifier of the user and includes, for example, at least one of the user's name and a pre-set password.

[0051] For example, for the installation information of the device data 2111 on the first line regarding device A1 (device 4 with device ID "A1"), the access rights are with owner O1 (owner with owner ID "O1") and user U1 (user with user ID "U1"). On the other hand, the device data 2111 on the second line indicates that user U1 has access rights to the operation data of device A1, while owner O1 does not have access rights.

[0052] The value field stores values indicating the specific content of the device data 2111 registered in the corresponding record. For example, if the type of the corresponding device data 2111 is installation information, the model number, installation location, and installation date and time are stored in the value field. Also, if the type of the corresponding device data 2111 is operation data, for example, raw log data such as "February 1, 2021, 18:00:00, power on" and "February 1, 2021, 18:01:00, set temperature changed to 24 degrees", as well as the acquisition date and time, are stored in the value field. Further, if the type of the corresponding device data 2111 is statistical data, for example, statistically processed log data such as the average power consumption per month or the average power consumption per year, as well as the calculation date and time, are stored in the value field.

[0053] Figure 3 is a diagram showing an example of the data configuration of the device management DB212. The device management DB212 is composed of a plurality of records that store device management information 2121. The device management information 2121 is information indicating the relationship between the building where each device 4 is installed, the owner, and the user. Specifically, the device management information 2121 includes fields for device ID, building ID, owner ID, and user ID. The device ID, owner ID, and user ID are the same as those in the device data DB211. The building ID is an identifier of the building, such as the name and address of the building.

[0054] For example, the device management information 2121 on the first line indicates that for device A1, it is installed in building H1 (building with building ID "H1"), the owner is owner O1, and the user is user U1.

[0055] Returning to FIG. 1. The processor 22 is composed of an integrated circuit such as a CPU. The processor 22 includes a first receiving unit 221, a second receiving unit 222, a transmitting unit 223, a third receiving unit 224, and a setting unit 225.

[0056] The first receiving unit 221 receives the operation data of the device 4 installed in the building from the device 4 using the communication circuit 23. The first receiving unit 221 stores the received operation data in the device data DB211 as new device data 2111. In this case, the first receiving unit 221 may register the device ID included in the header of the received operation data in the device ID field, register information indicating the operation data in the type field, register the owner ID of the owner or the user ID of the user having the access right corresponding to the operation data in the access right field, and register the value of the operation data in the value field.

[0057] The second receiving unit 222 receives, using the communication circuit 23, usage application information indicating a usage application for the device 4 from the user terminal 1 corresponding to the user of the device 4. The usage application is an application for a non - privileged user to obtain permission from the owner of the device 4 for usage. The usage application information includes, for example, a user ID and a device ID.

[0058] In response to the reception of the usage application information by the second receiving unit 222, the transmitting unit 223 transmits, using the communication circuit 23, approval request information to the owner terminal 3 corresponding to the owner of the device 4. The approval request information is information for notifying the owner that a usage application has been made for the device 4 owned by the owner from a certain user. Here, the transmitting unit 223 acquires the owner ID of the owner of the device 4 indicated by the device ID included in the usage application information from the device management DB212, and transmits the approval request information to the owner terminal 3 indicated by the acquired owner ID.

[0059] The third receiving unit 224 receives, via the communication circuit 23, approval information indicating approval for the use of the device 4 from the owner terminal 3. The approval information is information indicating that the owner has approved the user's application for the device 4 for which the application has been made. The approval information includes the device ID of the approved device 4, the owner ID of the approving owner, and the user ID of the approved user.

[0060] In response to the reception of the approval information by the third receiving unit 224, the setting unit 225 sets the access rights of the owner and the user to the device data 2111. The setting of the access rights includes restricting access for the owner and permitting access for the user.

[0061] Specifically, based on a predetermined setting rule, the setting unit 225 sets the access rights of the owner and the user for each type of the device data 2111 of the device 4 for which the use application has been made. As the setting rule, for example, for the device data 2111 whose type is installation information and the device data 2111 whose type is statistical data, access by the owner and the user is permitted, and for the device data 2111 whose type is operation data, access by the owner is restricted and access by the user is permitted. Alternatively, the access rights of the owner and the user may be determined based on the setting content input to the owner terminal 3 by the owner at the time of approval. Note that, instead of the operation data, access by the owner to the usage data may be restricted.

[0062] The communication circuit 23 is a communication circuit for connecting the server 2 to the network NT. The communication circuit 23 receives, for example, use application information, transmits approval request information, and receives approval information.

[0063] FIG. 4 is a flowchart showing an example of the processing of the device management system 100 in the first embodiment. Here, a case where the user U1 applies for use of the device A1 owned by the owner O1 will be described as an example.

[0064] In step S101, the user terminal 1 receives an input of a usage application for device A1 from user U1. For example, user U1 may input a usage application by starting an application of the device management system 100 on the user terminal 1, displaying a usage application screen on the display, and inputting necessary items. The necessary items include at least the user ID of user U1 and the device ID of device A1. For example, user U1 may input the device ID by photographing a QR code (registered trademark) attached to the housing of device A1 with the camera of the user terminal 1.

[0065] In step S102, the user terminal 1 generates usage application information based on the input usage application, and transmits the generated usage application information to the server 2.

[0066] In step S201, the second receiving unit 222 of the server 2 receives the usage application information. In step S202, the transmitting unit 223 acquires the device management information 2121 of device A1 for which the usage application has been made from the device management DB 212. In step S203, the transmitting unit 223 checks whether an owner ID is registered in the acquired device management information 2121. Here, it is assumed that "O1" is registered as the owner ID. For example, for device 4 purchased by the user himself / herself, the owner ID is not registered in the device management information 2121. Also, the device management information 2121 acquired at this stage has, for example, a blank user ID field or the user ID of a user who has previously used device A1 registered therein. When the usage application of user U1 is approved, the user ID field with a blank or the user ID of the previous user registered therein is updated to the user ID "U1".

[0067] In step S204, the transmitting unit 223 transmits approval request information including the owner ID "O1" and the building ID "H1" included in the acquired device management information 2121, and the user ID "U1" and the device ID "A1" included in the usage application information, to the owner terminal 3 indicated by the owner ID.

[0068] In step S301, the owner terminal 3 receives approval request information. In step S302, the owner terminal 3 displays the approval request information on the display. The displayed approval request information includes, for example, user ID "U1", device ID "A1", building ID "H1", and the like.

[0069] In step S303, the owner terminal 3 receives an approval input from the owner O1. Here, the owner O1 views the display content of the displayed approval request information and determines whether the user is a legitimate user. If it is determined that the user is a legitimate user, the owner O1 inputs approval to the owner terminal 3. On the other hand, if it is determined that the user is not legitimate, the owner O1 inputs non-approval to the owner terminal 3. Note that when non-approval is input, information indicating that the usage application has not been approved is transmitted to the user terminal 1 of the user U1 via the server 2. Also, when approval is input, the owner O1 may input the access rights of the owner and the user for each type of device data 2111.

[0070] In step S304, the owner terminal 3 that has received the approval inputs transmits the approval information to the server 2. Note that when the access rights of the owner O1 and the user U1 are input by the owner O1 at the time of inputting approval, the approval information includes the input setting content.

[0071] In step S205, the third receiving unit 224 of the server 2 receives the approval information. In step S206, the setting unit 225 determines the access rights between the owner O1 and the user U1. Here, according to the above-described setting rules, the access rights of the owner and the user for each type of device data 2111 are determined. Note that when the access rights of the owner and the user for each type of device data 2111 are input by the owner O1 at the time of inputting approval, the setting unit 225 may determine the access rights of the owner and the user for each type of device data 2111 according to the input setting content.

[0072] In step S207, the setting unit 225 registers the determined access right in the device data DB211. For example, in device A1, the setting unit 225 registers the owner O1 and user U1 in the access right field for installation information and statistical data, and registers only user U1 in the access right field for operation data. As a result, the viewing of operation data by the owner O1 is restricted, and the privacy of the user is protected. Also, the owner O1 can view the installation information and statistical data to appropriately manage device A1. Furthermore, the user U1 can view the operation data, installation information, and statistical data to confirm their own living patterns.

[0073] In step S208, the setting unit 225 transmits the application completion information to the user terminal 1 of user U1. The application completion information is information that notifies the user that the usage application has been approved by the owner.

[0074] In step S103, the user terminal 1 receives the application completion information. In step S104, the user terminal 1 displays the application completion information on the display. The displayed application completion information includes the approved device ID. As a result, the user U1 can confirm that the use of device A1 has been approved.

[0075] FIG. 5 is a flowchart showing an example of the processing of the device management system 100 when the server 2 receives operation data.

[0076] In step S401, device 4 generates operation data. Device 4 may generate operation data, for example, periodically or when an event occurs. The event occurs, for example, triggered by an operation of device 4 by the user and a change in the setting content by device 4 itself. In step S402, device 4 transmits the operation data to the server 2.

[0077] In step S221, the first receiving unit 221 of the server 2 receives operation data. In step S222, the first receiving unit 221 registers the operation data as device data 2111 in the device data DB211. When registering the device data 2111 in the device data DB221, the first receiving unit 221 may include the access rights of the user and the owner set by the setting unit 225 in the device data 2111.

[0078] Note that the first receiving unit 221 may calculate statistical data from the operation data, for example, when the accumulated amount of the operation data increases by a certain amount or periodically, and register it in the device data DB211 as the device data 2111. When the first receiving unit 221 receives installation information, it may register the installation information in the device data DB211 as the device data 2111. The installation information is transmitted from the device 4, for example, at the time of initial registration of the device 4. The initial registration of the device 4 is performed, for example, when the device 4 is installed in a building. As described above, the process of FIG. 5 is repeated, and the device data 2111 is accumulated in the device data DB211.

[0079] FIG. 6 is a flowchart showing an example of the process of the device management system 100 when a user makes a viewing application to the server 2. Here, the case where the user U1 views the device data 2111 about the device A1 will be described as an example. Further, it is assumed that the user U1 has access rights to the installation information, operation data, and statistical data.

[0080] In step S121, the user terminal 1 receives an input of a viewing application for the device data 2111. For example, the user U1 may start the application of the device management system 100 on the user terminal 1, display the viewing application screen on the display, and input the necessary items to input the viewing application. The necessary items include at least the user ID of the user U1 and the device ID of the device A1. In addition, the necessary items may include the period of the device data 2111 desired to be viewed and the type of the device data 2111.

[0081] In step S122, the user terminal 1 generates browsing application information based on the input browsing application, and transmits the generated browsing application information to the server 2.

[0082] In step S241, the first receiving unit 221 of the server 2 receives the browsing application information. In step S242, the transmitting unit 223 refers to the device data DB211 and checks the access right of the user U1 for the device A1. Here, the transmitting unit 223 checks that the user U1 has the access rights to the installation information, operation data, and statistical data for the device A1.

[0083] In step S243, the transmitting unit 223 acquires the device data 2111 of the device A1 from the device data DB211. Here, the transmitting unit 223 acquires the device data 2111 whose types are installation information, operation data, and statistical data.

[0084] In step S244, the transmitting unit 223 transmits the acquired device data 2111 to the user terminal 1.

[0085] In step S123, the user terminal 1 receives the device data 2111. In step S124, the user terminal 1 displays the device data 2111 on the display. Here, the device data 2111 to be displayed includes the device data 2111 whose types are installation information, operation data, and statistical data. If the period and type are input by the user U1 in the browsing application, the device data 2111 of the input period and type is displayed on the display. Thereby, the user U1 can browse the device data 2111 of the desired period among the device data 2111 for which the user U1 has the access right.

[0086] FIG. 7 is a flowchart showing an example of the processing of the device management system 100 when the owner makes a viewing application to the server 2. Here, the case where the owner O1 views the device data 2111 for the device A1 will be described as an example. Further, it is assumed that the owner O1 has access rights to the installation information and statistical data, but does not have access rights to the operation data.

[0087] In step S321, the owner terminal 3 receives an input of a viewing application for the device data 2111. For example, the owner O1 can input a viewing application by starting the application of the device management system 100 on the owner terminal 3, displaying a viewing application screen on the display, and inputting the necessary items. The necessary items include at least the owner ID of the owner O1 and the device ID of the device A1. In addition, the necessary items may include the period of the device data 2111 that the user wishes to view and the type of the device data 2111.

[0088] In step S322, the owner terminal 3 generates viewing application information based on the input viewing application, and transmits the generated viewing application information to the server 2.

[0089] In step S251, the first receiving unit 221 of the server 2 receives the viewing application information. In step S252, the transmitting unit 223 refers to the device data DB211 and checks the access right of the owner O1 for the device A1. Here, the transmitting unit 223 checks that the owner O1 has access rights to the installation information and statistical data for the device A1, and the access right to the operation data is restricted for the owner O1.

[0090] In step S253, the transmitting unit 223 acquires the device data 2111 of the device A1 from the device data DB211. Here, the transmitting unit 223 acquires the device data 2111 whose type is the installation information and statistical data.

[0091] In step S254, the transmitting unit 223 transmits the acquired device data 2111 to the owner terminal 3.

[0092] In step S323, the owner terminal 3 receives the device data 2111. In step S324, the owner terminal 3 displays the device data 2111 on the display. Here, the device data 2111 to be displayed includes the device data 2111 whose types are installation information and statistical data. In addition, when the period and type are input by the owner O1 in the viewing application, the device data 2111 of the input period and type is displayed on the display. Thereby, the owner O1 can confirm the device data 2111 of the desired period among the device data 2111 having the access right.

[0093] As described above, according to the device management system 100 in the first embodiment, since the owner's access to the device data 2111 is restricted, it is possible to prevent the device data 2111 from being unconditionally provided to the owner, and to protect the user's privacy.

[0094] In addition, in response to the reception of the usage application information of the device 4 from the user terminal 1, the approval request information is transmitted to the owner terminal 3, and the approval information for the usage of the device 4 is received from the owner terminal 3. Therefore, it is possible to prevent the device 4 from being used by a user who has not obtained the approval of the owner.

[0095] (Second Embodiment) The second embodiment is characterized in that the owner of the building can collectively approve a plurality of devices owned in the building to the users. FIG. 8 is a block diagram showing an example of the configuration of the device management system 100A in the second embodiment. In the second embodiment, the same components as those in the first embodiment are denoted by the same reference numerals, and the description thereof is omitted.

[0096] The memory 21A of the server 2A includes a device data DB 211 and a device management DB 212A. FIG. 9 is a diagram showing an example of the data configuration of the device management DB 212A in the second embodiment. The device management DB 212A is composed of a plurality of records that store device management information 2121A. The device management information 2121A further includes a batch presence / absence field with respect to the device management information 2121. Information indicating that the owner has batch-approved the device 4 is registered in the batch presence / absence field. In the example of FIG. 9, for devices A1, A2, and A3 owned by the owner O1 installed in the building H1, the owner O1 has been batch-approved for the user U1.

[0097] Referring back to FIG. 8. The processor 22A includes a first reception unit 221, a second reception unit 222, a transmission unit 223, a third reception unit 224A, and a setting unit 225A.

[0098] The third reception unit 224A receives the batch approval information of the device 4 from the owner terminal 3 using the communication circuit 23. The batch approval information includes first approval information and second approval information.

[0099] The first approval information is information for approving the use of the device 4 for which a usage application has been made. The second approval information is information for approving the use of other devices 4 installed in buildings other than the device 4 for which a usage application has been made. That is, the batch approval information is information for batch-approving the device 4 for which a usage application has been made and other devices 4 other than the device 4. Here, the batch approval information may include a device list of other devices 4.

[0100] When the setting unit 225A receives the usage application information of other devices 4 after receiving the batch approval information, it does not transmit approval request information for other devices 4, but sets the access rights of the owner and user for other devices 4.

[0101] FIG. 10 is a flowchart showing an example of the processing of the device management system 100A in Embodiment 2. Here, a case where user U1 applies for use of device A1 owned by owner O1 will be described as an example. Steps S1001, S1002, S2001, and S2002 are the same as steps S101, S102, S201, and S202 in FIG. 4.

[0102] In step S2003, the transmission unit 223 checks whether the owner ID is registered in the device management information 2121A acquired from the device management DB 212A, and also checks whether information indicating batch approval is registered.

[0103] If the information indicating batch approval is not registered (NO in step S2004), the transmission unit 223 transmits approval request information to the owner terminal 3 (step S2005). The approval request information transmitted here includes a device list of other devices 4 owned by the owner O1 installed in the same building as the device 4 other than the device A1 related to the use application (devices A2 and A3).

[0104] In step S3001, the owner terminal 3 receives the approval request information. In step S3002, the owner terminal 3 displays the approval request information on the display. The approval request information to be displayed includes, for example, the user ID "U1", the device ID "A1", and the building ID "H1". In addition, information requesting the owner O1 for batch approval of the device A1 and other devices 4 (devices A2 and A3) installed in the building H1 is displayed. The information requesting the owner O1 for batch approval includes, for example, a device list for asking the owner O1 whether to approve devices A2 and A3 in batch.

[0105] In step S3003, the owner terminal 3 receives a batch approval input from the owner O1. Here, when the owner O1 confirms the display content of the approval request information and determines to perform batch approval for the devices A1 to A3 with respect to the user U1, the owner O1 inputs the batch approval to the owner terminal 3. Note that the owner O1 may select any one of the devices A2 and A3 as the device 4 for batch approval with the device A1.

[0106] In step S3004, the owner terminal 3 that has received the batch approval transmits the batch approval information to the server 2. Note that when the access rights of the owner O1 and the user U1 are input for each of the devices A1 to A3 at the time of input of the batch approval, the batch approval information includes the input setting content.

[0107] In step S2006, the third receiving unit 224 of the server 2 receives the batch approval information. Here, the third receiving unit 224 registers information indicating that batch approval has been made in the batch presence / absence field for each device management information 2121A of the devices A1 to A3. Thereby, hereafter, when there is a usage application for either of the devices A2 and A3, a batch approval request is not transmitted to the owner O1.

[0108] In step S2007, the setting unit 225A determines the access rights of the owner O1 and the user U1 with respect to the device A1. The details of the determination of the access rights are the same as those in the first embodiment.

[0109] In step S2004, when information indicating that batch approval has been made is registered in the device management information 2121A of the device 4 related to the usage application (YES in step S2004), steps S2005 and S2006 are skipped and the process proceeds to step S2007. As a case where it is determined YES in step S2004, for example, in the usage application related to the device A1, after batch approval for the devices A1 to A3 has been made by the owner O1, a case where a usage application for the device A2 or the device A3 is made by the user U1 corresponds.

[0110] Steps S2008, S2009, S1003, and S1004 are the same as steps S207, S208, S103, and S104 in FIG. 4.

[0111] As described above, according to Embodiment 2, the owner can collectively approve the user's usage applications for the device 4 (device A1) related to the second approval information and other devices (devices A2, A3).

[0112] Also, when usage application information for other devices 4 (devices A2, A3) is received after receiving the collective approval information for devices A1 to A3, the access rights of the owner and access to other devices 4 can be set without transmitting approval request information for other devices 4 to the owner terminal 3.

[0113] (Embodiment 3) Embodiment 3 is characterized in that a user can collectively submit usage applications for a plurality of devices 4 installed in a building. FIG. 11 is a block diagram showing an example of the configuration of a device management system 100B according to Embodiment 3. In this embodiment, the same components as those in Embodiments 1 and 2 are denoted by the same reference numerals, and the description thereof is omitted.

[0114] The server 2B includes a memory 21A, a processor 22B, and a communication circuit 23. The processor 22B includes a first reception unit 221, a second reception unit 222B, a transmission unit 223B, a third reception unit 224B, and a setting unit 225B.

[0115] The second reception unit 222B receives, using the communication circuit 23, request information for a device list from the user terminal 1. The device list is information indicating a plurality of devices 4 for which a user can collectively submit usage applications.

[0116] The transmission unit 223B transmits a device list to the user terminal 1 in response to the reception of the request information by the second reception unit 222B. The device list is presented to the user via the user terminal 1.

[0117] The second receiving unit 222B is batch use application information for batch processing of use applications for a plurality of devices 4 included in the device list, and receives the batch use application information transmitted from the user terminal 1 using the communication circuit 23.

[0118] The third receiving unit 224B receives the batch approval information transmitted from the owner terminal 3.

[0119] The setting unit 225B collectively sets the access rights of the users and owners of the plurality of devices 4 related to the batch use application based on the batch approval information.

[0120] FIG. 12 is a flowchart showing an example of the processing of the device management system 100B according to Embodiment 3. Here, a case where the user U1 makes a batch use application for the devices A1 to A3 owned by the owner O1 will be described as an example.

[0121] In step S1101, the user terminal 1 receives an input of a request for a device list by the user U1. Here, the user U1 may start the application of the device management system 100, display a request screen for the device list on the display, and input a request for the device list by inputting necessary items. The necessary items include at least the user ID of the user U1 and the building ID of the building H1. In step S1102, the user terminal 1 transmits the request information to the server 2.

[0122] In step S2101, the second receiving unit 222B of the server 2 receives the request information. In step S2102, the transmitting unit 223B acquires the device management information 2121A of the devices 4 installed in the building H1 from the device management DB 212A. Here, the transmitting unit 223B acquires only the device management information 2121A that includes information indicating that batch approval is possible among the device management information 2121A of the devices installed in the building H1. In the present embodiment, the information indicating that batch approval is possible is assumed to be registered in advance in the device management DB 212 under the permission of the owner O1. Here, the device management information 2121A of each of the devices A1 to A3 is acquired.

[0123] In step S2103, the transmitter 223B checks whether the owner ID is registered in each of the device management information 2121A of the acquired devices A1 to A3. Here, it is assumed that the owner ID of the owner O1 is registered in each of the device management information 2121A of the acquired devices A1 to A3.

[0124] In step S2104, the transmitter 223B generates a device list including devices A1 to A3. In step S2105, the transmitter 223B transmits the device list to the user terminal 1 of the user U1.

[0125] In step S1103, the user terminal 1 receives the device list. In step S1104, the user terminal 1 displays the device list. The device list displayed here includes information about devices A1 to A3.

[0126] In step S1105, the user terminal 1 accepts an input of a batch usage application from the user who has browsed the device list. Here, a batch usage application for devices A1 to A3 is input.

[0127] In step S1106, the user terminal 1 transmits batch usage application information indicating the input batch usage application to the server 2. Here, the batch usage application information includes a device list including the device IDs of devices A1 to A3 and the user ID of the user U1.

[0128] In step S2106, the second receiver 222B of the server 2 receives the batch usage application information. In step S2107, the transmitter 223B transmits batch approval request information to the owner terminal 3. Here, the batch approval request information includes a device list indicating the device IDs of devices A1 to A3 related to the batch usage application and the user ID of the user U1. Also, the batch approval request information is transmitted to the owner terminal 3 of the owner O1 confirmed in step S2103.

[0129] In step S3101, the owner terminal 3 receives batch approval request information. In step S3102, the owner terminal 3 displays the batch approval request information on the display. The displayed batch approval request information includes a device list of devices A1 to A3 and the user ID of user U1, etc.

[0130] In step S3103, the owner terminal 3 accepts an input for batch approval. Here, the owner O1 browses the display content of the displayed batch approval request information and determines whether the user is a legitimate user. If it is determined that the user is a legitimate user, the owner O1 inputs batch approval to the owner terminal 3. Note that if a non-approval of batch approval is input, information indicating that the usage application has not been approved is transmitted to the user terminal 1 of user U1 via the server 2.

[0131] In step S3104, the owner terminal 3 that has received the batch approval inputs transmits the batch approval information to the server 2.

[0132] In step S2108, the third receiving unit 224B of the server 2 receives the batch approval information. In step S2109, the setting unit 225B determines the access rights for the owner and the user. Here, the setting unit 225B collectively sets the access rights for the owner and the user for each of devices A1 to A3.

[0133] In step S2110, the setting unit 225B registers the determined access rights in the device data DB211. For example, in each of devices A1 to A3, the setting unit 225B registers the owner O1 and the user U1 in the access right field for installation information and statistical data, and registers only the user U1 in the access right field for operation data.

[0134] Steps S2111, S1107, and S1108 are the same as S208, S103, and S104 in FIG. 4.

[0135] According to the third embodiment in this way, since the device list is presented to the user, the user can collectively apply for the use of the devices 4 included in the device list.

[0136] (Embodiment 4) Embodiment 4 allows the user to select the type of device data that permits access to the owner, and gives an incentive to the user according to the selection result. FIG. 13 is a block diagram showing an example of the configuration of the device management system 100C according to Embodiment 4 of the present disclosure. In Embodiment 4, the same components as those in Embodiments 1 to 3 are denoted by the same reference numerals, and the description thereof is omitted.

[0137] The processor 22C of the server 2C includes a first reception unit 221, a second reception unit 222C, a transmission unit 223C, a third reception unit 224, a setting unit 225C, and an incentive determination unit 226.

[0138] In response to the reception of the usage application information by the second reception unit 222, the transmission unit 223C transmits permission request information to the user terminal 1 using the communication circuit 23. The permission request information is information for inquiring the user about the type of data that permits access to the owner among the types of data included in the device data 2111. In this embodiment, the user is allowed to select the type of device data 2111 that permits access to the owner from among the types of device data 2111 for which access to the owner is pre-permitted. As the type of device data 2111 for which access to the owner is pre-permitted, a type related to the maintenance information of the device 4 (maintenance type) is adopted. The maintenance type includes, for example, installation information, error information, failure information, and device control information that constitute operation data, and statistical data. Therefore, the user selects the type of device data 2111 that permits access to the owner from among these maintenance types.

[0139] The second reception unit 222C receives, from the user terminal 1, a permission setting type that is the type of device data 2111 that permits access to the owner, selected by the user who has viewed the permission request information.

[0140] When the third receiving unit 224 receives the approval information, the setting unit 225C sets the access right of the owner to the device data 2111 according to the permission setting type received by the second receiving unit 222C. The setting of the access right includes the restriction of access by the owner and the permission of access by the owner.

[0141] The incentive determination unit 226 determines the incentive given to the user according to whether the access to the data corresponding to the maintenance type by the owner is permitted. The incentive determination unit 226 transmits the determined incentive to the user terminal 1. The incentive is presented to the user via the user terminal 1.

[0142] In this embodiment, a discount on the building's common expenses is adopted as the incentive. The incentive determination unit 226 calculates the discounted common expenses according to the expense rule indicated by the expense rule information 213 stored in the memory 21C. As the expense rule, for example, a rule that the discount rate increases as the number of permission setting types increases can be adopted. Here, a case where the user U1 applies to use the device A1 owned by the owner O1 will be taken as an example for explanation.

[0143] FIG. 14 is a flowchart showing an example of the processing of the device management system 100C in Embodiment 4. Steps S1201, S1202, S2301, and S2302 are the same as steps S101, S102, S201, and S202 in FIG. 4.

[0144] In step S2303, the transmission unit 223C of the server 2C transmits the permission request information to the user terminal 1 of the user U1. The permission request information includes a list of the maintenance types of the device A1 and the owner ID of the owner O1.

[0145] In step S1203, the user terminal 1 receives the permission request information and displays it on the display. FIG. 16 is a diagram showing the display screen G1 of the permission request information. The display screen G1 displays a message prompting the selection of a maintenance type user who permits access to the owner. Also, the name of the owner O1 of the device A1 is displayed on the display screen G1.

[0146] Furthermore, a list of selectable maintenance types is displayed on the display screen G1. Here, installation information, error information, failure information, device control information, and statistical data are displayed as selectable maintenance types. Furthermore, check boxes 1601 corresponding to each maintenance type are provided on the display screen G1. The user U1 inputs a check mark to the check box 1601 corresponding to the maintenance type that permits the owner O1 to access among these maintenance types. Thereby, the user U1 can select the permission setting type.

[0147] In step S1204, the user terminal 1 receives the selection of the permission setting type by the user U1 who has viewed the display screen G1. In step S1205, the user terminal 1 transmits the permission setting type information indicating the selected permission setting type to the server 2C.

[0148] In step S2304, the second receiving unit 222C of the server 2C receives the permission setting type information. In step S2305, the incentive determination unit 226 acquires the cost rule information 213 from the memory 21C. In step S2306, the incentive determination unit 226 determines a discount rate corresponding to the number of maintenance types selected by the user indicated by the permission setting type information with reference to the cost rule information 213, multiplies the determined discount rate by the default common cost of the building to calculate a discount amount, subtracts the discount amount from the default common cost, and calculates the common cost.

[0149] In step S2307, the incentive determination unit 226 transmits the benefit cost information indicating the calculated benefit cost to the user terminal 1. The benefit cost information includes, for example, the discounted benefit cost, the default benefit cost, and the discount amount.

[0150] In step S1206, the user terminal 1 receives the benefit cost information. In step S1207, the user terminal 1 displays the benefit cost information on the display. Thereby, the user U1 can confirm the incentive given to himself / herself.

[0151] FIG. 15 is a flowchart following FIG. 14. In FIG. 15, the same reference numerals are given to the same processes as in FIG. 4. The difference from FIG. 4 in FIG. 15 is in step S206A. In step S206A, the setting unit 225C determines the access rights for the owner and the user. Here, regarding the access rights of the owner, the setting unit 225C permits the access of the owner for the maintenance type selected by the user indicated by the permission setting type information, and restricts the access of the owner for other maintenance types. Note that the setting unit 225C may permit or restrict the access of the owner according to a preset setting rule for types other than the maintenance type among the types of the device data 2111.

[0152] As described above, according to the fourth embodiment, the type of the device data 2111 is presented to the user, and the permission setting type, which is the type of the data for which the access by the owner is permitted among the presented types, is received from the user terminal 1. Therefore, the user can set the type of the data for which the access by the owner is permitted among the presented data types. Thereby, while respecting the user's intention, the user's privacy can be protected.

[0153] Furthermore, since an incentive is given to the user according to whether or not the owner's access to the data corresponding to the maintenance type is permitted, it is possible to give the user an incentive to permit the owner's access to such data. As a result, the possibility that the owner's access to the data corresponding to the maintenance type is permitted increases, and the management of the device becomes easier.

[0154] (Embodiment 5) Embodiment 5 restricts access by the owner of another device 4 installed in the same building as the device 4 according to the permission setting type in the device 4 related to the usage application. In Embodiment 5, since the block diagram and the flowchart are the same as those in Embodiment 4, FIGS. 13, 14, and 15 are used.

[0155] In this embodiment, the permission setting type is set from the usage data. The usage data includes, for example, device control information and operation history information that constitute the operation data. The device control information and the operation history information included in the usage data may be data obtained by processing the received operation data in addition to the operation data received from the device 4.

[0156] In this embodiment, the setting unit 225C sets a restriction on the owner's access to the device data 2111 of another device 4 owned by the same owner other than the device 4 related to the usage application and installed in the building according to the permission setting type.

[0157] Next, with reference to FIGS. 14 and 15, the processing of the device management system 100C in Embodiment 5 will be described. Here, a case where the user U1 makes a usage application for the device A1 owned by the owner O1 will be described as an example.

[0158] In step S1203, the user terminal 1 displays a display screen for the display of permission request information as follows. FIG. 17 is a diagram showing a display screen G2 of permission request information in Embodiment 5. On the display screen G2, a list of data types for which it is possible to permit the owner O1 to access the usage data of the device A1 owned by the owner O1 is displayed.

[0159] Specifically, the display screen G2 displays a column R1 of device control information and a column R2 of device history information. The column R1 of device control information lists the detailed data types (detailed types) of device control information. Here, for the sake of convenience of explanation, the detailed types of device control information are listed in a simplified manner such as C1, C2, C3, ···. Also, in the column R2 of device history information, the detailed types of device history information are listed in a simplified manner such as D1, D2, D3.

[0160] The display screen G2 displays a checkbox 1701 corresponding to each detailed type. The user U1 inputs a check mark to the checkbox 1701 corresponding to the detailed type for which the owner O1 is permitted to access among these detailed types. Thereby, the user U1 can select the permission setting type for the device A1.

[0161] In step S1204, the user terminal 1 receives the selection of the permission setting type by the user U1 who has viewed the display screen G1. In step S1205, the user terminal 1 transmits permission setting type information indicating the selected permission setting type to the server 2C.

[0162] Thereafter, the processes shown in FIGS. 14 and 15 are performed, and approval information is transmitted from the owner terminal 3 of the owner O1 who has input approval. When the approval information is received by the third receiving unit 224, the setting unit 225C determines the access rights for the owner and the user (step S206A). Here, the setting unit 225C sets the access rights of the owner O1 and the user U1 for the device A1 according to the permission setting type information for the device A1, and also sets the access rights for the owner O1 and the user U1 for the other devices A2 and A3 in the building H1 owned by the owner O1.

[0163] Specifically, for the detailed types of devices A2 and A3 that have the same attributes as the detailed type for which the user U1 has permitted access to the device A1 for the owner O1, the setting unit 225C permits access to the owner O1. On the other hand, for the detailed types of devices A2 and A3 that have the same attributes as the detailed type for which the user U1 has restricted access to the device A1 for the owner O1, the setting unit 225C restricts access to the owner O1. Regarding the access rights of the user U1, the setting unit 225C may be set based on a predetermined setting rule or the setting content of the owner O1 at the time of approval.

[0164] As described above, according to the fifth embodiment, since the access by the owner of other devices 4 is restricted according to the permission setting type set for the device 4 related to the usage application, the setting of the permission setting type for the device 4 related to the usage application can also be applied to other devices 4, and the setting of the permission setting type can be performed collectively.

[0165] In step S1204 of the fifth embodiment, the user terminal 1 may display, on the display of the user terminal 1, the detailed types for which access to the owner O1 is permitted with respect to the devices A2 and A3 under the control of the transmission unit 232C.

[0166] FIG. 18 is a diagram showing a display screen G3 displayed on the display of the user terminal 1 when presenting the detailed types determined for other devices A2 and A3 to the user U1. This display screen G3 is displayed on the user terminal 1, for example, when the operation by the user U1 to select the detailed type for the device A1 is completed on the display screen G2.

[0167] The display screen G3 displays a message indicating that access rights are set for the devices A2 and A3 in the same manner as for the device A1. Further, the display screen G2 displays the detailed types for which the access of the owner O1 is permitted and the detailed types for which the access of the owner O1 is restricted for each of the devices A2 and A3. The underline indicates the detailed type for which access is restricted.

[0168] In the display screen G3, the detailed types indicated by the symbols C1, C2,... and D1, D2,... are represented using the same symbols for the detailed types having the same attributes as those of the device A1.

[0169] In this example, for the device A1, the user U1 has permitted the access of the owner O1 for the detailed types (C1, C2, D1, D2) and restricted the access of the owner O1 for the detailed types (C3, D3). Therefore, the underlines are attached to the respective detailed types (C3, D3) of the devices A2 and A3. Note that a strikethrough may be attached instead of the underline.

[0170] The user U1 who has viewed the display screen G3 can appropriately change the detailed types for which the access of the owner O1 is permitted and the detailed types for which the access is restricted for the devices A2 and A3.

[0171] For example, when restricting access to the detailed type (C1) of the device A2, the user U1 touches the display area of the detailed type (C1) of the device A2 on the display screen G3. Then, an underline is displayed for the detailed type (C1) of the device A3.

[0172] For example, when permitting access to the detailed type (C3) of device A2, user U1 touches the display area of the detailed type (C3) of device A2 on the display screen G3. Then, the underline of the detailed type (C3) of device A2 is erased.

[0173] When the confirmation or modification operation of the access rights for devices A2 and A3 with respect to the display screen G3 is completed, user U1 touches the approval button (not shown).

[0174] Thereby, for each of devices A1 to A3, the permission setting information reflecting the confirmation or modification operation of user U1 is transmitted from the user terminal 1 to the server 2C. Then, the setting unit 225C of the server 2C sets the access rights of the owner O1 for devices A1 to A3 according to the permission setting information of devices A1 to A3.

[0175] The following modification examples can be adopted in the present disclosure.

[0176] (1) In FIG. 1, all or part of each block included in the processor 22 and the memory 21C of the server 2 may be provided in the user terminal 1 or may be provided in the owner terminal 3. This also applies to the block diagrams of FIGS. 8, 11, and 13.

[0177] (2) In the second embodiment, after the batch approval for devices A1 to A3 is made by the owner, only for the usage application of another device 4 (for example, device A2) performed within a certain period, the access rights regarding the owner of device A2 may be set without transmitting the approval request information to the owner terminal 3. As the certain period, for example, an appropriate period such as one week, half a month, or one month can be adopted.

[0178] (3) In step S302 of FIG. 15, the usage application information displayed on the owner terminal 3 may include a permission setting type. Thereby, the owner O1 can confirm the detailed type for which the user U1 permits access to the owner O1. Further, the usage application information displayed in step S302 of the fifth embodiment may include the permission setting types for devices A2 and A3 owned by the owner O1 in addition to the device A1 related to the usage application. Thereby, the owner O1 can confirm the permission setting types for all the devices A1 to A3 owned in the building H1. To realize this, the transmission unit 233 may include the respective permission setting types of the devices A1 to A3 in the approval request information transmitted to the owner terminal 3.

[0179] (4) The incentive is not limited to a discount on the common benefit fee. For example, it may be a discount on the electricity bill or the giving of a coupon to the user. The coupon may be mileage points or points in an e-commerce site or a shopping mall.

[0180] (5) In the fifth embodiment, the configuration is such that the user selects the detailed type of usage data, but this is an example. For example, the user may select the type for which to permit access to the owner from among installation information, operation data, and statistical data.

Industrial Applicability

[0181] The present disclosure is useful in a rental service that rents a building equipped with devices to a user.

Claims

1. An information processing method for causing a computer to execute, comprising: Receiving operation data of equipment installed in a building from the equipment; Receiving usage application information indicating an application for using the equipment from a user terminal corresponding to a user of the equipment; In response to receiving the usage application information, transmitting approval request information to an owner terminal corresponding to an owner of the equipment; Receiving approval information indicating approval for using the equipment from the owner terminal; In response to receiving the approval information, setting a restriction on access by the owner to equipment data including at least one of the operation data or data generated based on the operation data; An information processing method.

2. The access restriction includes setting permission for the user to access the equipment data, The information processing method according to Claim 1.

3. The data generated based on the operation data includes statistical data based on the operation data, The access restriction includes permitting the owner to access only the statistical data among the operation data and the statistical data, The information processing method according to Claim 1 or 2.

4. The approval information includes first approval information for using the equipment and second approval information for using other equipment installed in the building other than the equipment related to the usage application, When receiving the usage application information of the other equipment after receiving the approval information including the second approval information, not transmitting the approval request information for the other equipment and setting the access restriction for the other equipment; The information processing method according to any one of Claims 1 to 3.

5. The transmission of the approval request information includes transmitting a list of the other equipment to the owner terminal, The list of the other equipment is presented to the owner via the owner terminal, The information processing method according to Claim 4.

6. Further, receiving request information for a list of the equipment from the user terminal, In response to the request information, transmitting the list of the equipment to the user terminal, The list of the equipment is presented to the user via the user terminal, In receiving the usage application information, receiving the usage application information of the equipment included in the list of the equipment; The information processing method according to any one of Claims 1 to 5.

7. Further, transmitting the type of data included in the equipment data to the user terminal, The type is presented to the user via the user terminal, Receiving, from the user terminal, a permission setting type which is a type of data that permits the access by the owner among the types, setting a restriction on the access by the owner to the device data according to the permission setting type, The information processing method according to any one of claims 1 to 6.

8. The type transmitted to the user terminal includes a type of data for which access by the owner among the device data is permitted. The information processing method according to claim 7.

9. The permission setting type includes a maintenance type which is a type of data used for maintenance of the device, The access restriction includes permitting access by the owner to data corresponding to the maintenance type. The information processing method according to claim 8.

10. Further, determining an incentive given to the user according to whether or not access by the owner to data corresponding to the maintenance type is permitted, transmitting the incentive to the user terminal, The incentive is presented to the user via the user terminal. The information processing method according to claim 9.

11. Receiving the permission setting type from the user terminal, setting a restriction on the access by the owner to the device data of other devices installed in the building other than the device related to the usage application according to the permission setting type. The information processing method according to claim 7.

12. A first receiving unit that receives operation data of a device installed in a building from the device, A second receiving unit that receives usage application information indicating a usage application of the device from a user terminal corresponding to the user of the device, A transmitting unit that transmits approval request information to an owner terminal corresponding to the owner of the device in response to the reception of the usage application information, A third receiving unit that receives approval information indicating approval of the usage of the device from the owner terminal, A setting unit that sets a restriction on the access by the owner to device data including at least one of the operation data or data generated based on the operation data in response to the reception of the approval information. An information processing system.

Images