RU2673471C2 - System for remotely controlling controllable device - Google Patents

Abstract

FIELD: control systems.SUBSTANCE: system (100, 102) for remote control of controlled device (110), comprising receiver (112) configured to receive a digital command, the controllable device being configured to modify an aspect of the controllable device in response to receiving the digital command, mobile controller (120), mobile controller comprising tag reader (122) configured to connect directly to an electronic tag over first wireless channel (152) and to receive information from the tag identifying controllable device (110), and sender (124) configured to wirelessly send the digital command to the controllable device over second wireless channel (154) using the information identifying the controllable device, and access control module (130) configured to selectively allow or block the mobile controller to control the controllable device through the digital command, the access control module being configured to allow the mobile controller to control the controllable device within a control period, the control period starting upon the tag reader wirelessly connecting to the electronic tag and terminating when a control release condition is satisfied.EFFECT: enabling control of multiple individual users.14 cl, 11 dwg

Description

FIELD OF TECHNOLOGY

The invention relates to a system for remotely controlling a controlled device, the controlled device comprising a receiver configured to receive a digital command, a controlled device configured to modify an aspect of a controlled device in response to receiving a digital command.

BACKGROUND

Previously proposed systems for remote control of a managed device. For example, US Patent 6,528,954, entitled "Intelligent Electric Lamp", incorporated herein by reference, provides an intelligent electric lamp that encloses a light source and a processor for controlling a light source in its housing. The smart electric lamp also includes a receiver coupled to the processor for receiving a data signal from an external device.

An intelligent electric lamp can thus respond to a signal from another device and cause the processor to control, for example, the intensity or color of the light source. For example, an intelligent electric lamp may be part of a multimedia entertainment system in which a receiver receives a control signal to control a light source.

The disadvantage of such known systems, including an intelligent electric lamp, is that they are not quite suitable for controlling individual users.

SUMMARY OF THE INVENTION

It would be advantageous to have an improved system for remotely controlling a managed device in which individual users have the ability to control a managed device. In addition, it would be advantageous to provide a system in which multiple users can control a managed device.

A system is provided for remotely controlling a managed device. The managed device comprises a receiver configured to receive a digital command. The managed device is configured to modify an aspect of the managed device in response to receiving a digital command.

The system comprises a mobile controller and an access control module. The mobile controller comprises a tag reader configured to directly connect to the electronic tag via the first wireless channel, and receive information from the tag identifying the managed device, and a sender configured to wirelessly send a digital command to the managed device via the second wireless channel, using information identifying the managed device.

The access control module is configured to selectively enable or disable control by the mobile controller of the managed device using a digital command, the access control module is configured to enable the mobile controller to control the managed device within the control period, and the control period begins when the tag reader is electronically connected to the electronic tag , and ends when the shutdown (removal) condition is satisfied i.

The user can use his mobile controller to control the managed device. However, he can do this only then, that is, only then the mobile controller gets the ability to control the managed device when the control period has begun. To start the control period, the mobile controller must make a wireless connection with the electronic tag. Thus, it is established that the mobile controller, at least at this point in time, is close to the electronic tag. Access conflicts are thus resolved naturally; Users who are able to control the same device are likely to meet each other at, or near, the electronic tag. Indeed, the control period ends when the control disconnect condition is satisfied. In addition, when a resource can be controlled from a mobile controller, for example, a user from a smartphone, it is often undesirable for users who are not in the immediate vicinity of the resource to issue control commands for it.

The system thus provides an asymmetric way to get and turn off control. The mobile controller receives control using a narrow selector pulse, that is, an electronic tag, and disables the control based on a less stringent condition, that is, the condition for turning off the control. Preferably, the access control module is configured so that, after the end of the control period, not to start a new control period, until the tag reader wirelessly connects to the electronic tag again.

Many devices are suitable for use as a controlled device: Examples include lights, and HVAC devices (Heating, Ventilation, and Air Conditioning). The system can also be used for home automation devices such as remotely controlled blinds.

The condition for disabling the control may depend on many parameters, including properties associated with the user, for example, its so-called "role" in the access control system, time of day, etc. Two conditions turned out to be especially advantageous, in particular, for situations where multiple users may want to control the device: based on the location of the mobile controller and the length of the control period.

For example, a control deactivation condition may specify a geographic area, the access control unit is configured to obtain location information indicating a geographic location of the mobile controller, and to end a control period if the geographic location of the mobile controller is outside the geographic area.

For example, the control shutdown condition may specify a period of time, the access control module is configured to end the control period after the control period has continued for at least said time period.

Combinations of location and duration are possible, for example, by combining the condition with the operators "and" or "or". Additional variations are possible. For example, a system may require partial fulfillment of a condition (for example, 60% of the duration and / or 80% of geographic coverage; alternatively, location and duration can be scaled in advance). A correction factor for a special condition can be added, for example, 33% of the time and duration in the event of an emergency or a specific incident.

By choosing the conditions small, that is, a small area and / or a short duration, it can be established that access conflicts correspond to “physical” conflicts. That is, two users who have control, and who are likely to be close to each other, can thus directly communicate and resolve an access conflict. With this technical tool, the natural access control to the wall switch is expanded by remote control of the mobile controller. How small it is depends on the building and the normal use of the space, such as the room. For example, you can specify a geographical area as a sphere with a center, for example, the location of a managed device or electronic tag, and the radius. The radius can be less than 4 meters, 2 meters, 1 meter, or 50 cm. For example, you can set the duration of a time period to be less than 4 minutes, 2 minutes, 1 minute, or 30 seconds. The region can be an ellipsoid, for example, defined by the larger and smaller radii R1 and R2.

On the other hand, choosing conditions as large, it can be established that a person remains in control while he is likely to need it, but is freed from it when he probably does not need it. For example, the radius may be such that the mobile controller must leave the building to turn off control, or it may be more than 20 meters, 40 meters, or 100 meters. For example, the duration may be more than 2 hours, 4 hours or 8 hours. Thus, for example, an office employee can leave his workplace temporarily, for example, for a lunch break, and still have control when he returns. However, control is turned off, for example, during the night.

Other combinations of area and duration can also be selected.

The mobile controller may be a smartphone. The electronic tag can be an NFC tag, an RFID tag or an electronic tag, or a similar tag, for example, Bluetooth Smart Tag.

In an embodiment, the electronic tag is configured to communicate with a configuration server, for example, a building management system, via a third channel. The electronic tag contains a wired interface for connecting to the third channel. The configuration server is configured to store identifying information and / or control disconnection conditions in an electronic tag. In an embodiment, the access control module is contained in a mobile controller, the access control module being configured to receive a condition for disconnecting control from the electronic tag using an electronic tag reader.

The first wireless channel is a direct and short-range connection between a mobile controller, such as a mobile phone, and a tag. The first wireless channel may be NFC or, possibly, Bluetooth. The second wireless channel has a greater range than the first wireless channel. A second wireless channel connects the mobile controller and the managed device. The second wireless channel should not be direct, and should not be completely wireless. At least the second channel begins as wireless on the mobile controller. Typically, a second wireless channel connects the mobile controller to a digital communications network, connecting the mobile controller to a managed device and possibly an access control module. The third channel is located between the electronic tag and another server. The third channel is different from the first channel. The third channel is usually wired, at least at the end, where it connects to the label.

In an embodiment, the action of the first communication channel is less than 50 centimeters; for example, the electronic tag may be an NFC or RFID tag. The first communication channel, having a short action, for example, less than 50 centimeters, can also be carried out with other means, for example, with a contactless Bluetooth tag, programmed to answer only at a predetermined short distance, such as 50 cm or less.

The second wireless channel may comprise so-called Wireless Local Area Networks (WLANs), for example, as described in "IEEE 802.11." The second wireless channel may also comprise a so-called wireless personal area network (WPAN) such as IrDA, Wireless USB, or Bluetooth. The second wireless channel may also contain a so-called Cellular network, for example, Z-Wave, and ZigBee; for example, as described in "IEEE 802.15.4" or "IEEE 802.15.4g."

The mobile controller may be a mobile phone, or an electronic tablet, or a laptop, etc.

An aspect of the invention relates to a system for remotely controlling a managed device, further comprising a managed device and an electronic tag. An aspect of the invention relates to a mobile controller, electronic tag and access module used in said system.

An aspect of the invention relates to a method for remotely controlling a managed device.

An aspect of the invention relates to a computer program for remotely controlling a managed device.

The method in accordance with the invention can be implemented on a computer, as a computer-implemented method, or in specialized hardware, or in a combination of both. The executable code for the method in accordance with the invention can be stored on a computer program product. Examples of computer software products include memory devices, optical storage devices, integrated circuits, servers, network software, etc. Preferably, the computer program product comprises a non-volatile means of program code stored on a computer-readable medium for performing the method in accordance with the invention, when said software product is executed on a computer

In a preferred embodiment, the computer program comprises computer program code means adapted to perform all the steps of the method in accordance with the invention when the computer program is executed on a computer. Preferably, the computer program is implemented on a computer readable medium.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects of the invention are explained and will become apparent in connection with the embodiments described below.

In the drawings:

FIG. 1 is a block diagram illustrating a system for remotely controlling a managed device;

FIG. 2 is a block diagram illustrating a system for remotely controlling a managed device;

FIG. 3 is a block diagram illustrating two electronic tags;

FIG. 4 is a block diagram illustrating an access control module;

FIG. 5 is a block diagram illustrating the storage of publicly available information;

FIG. 6a is a schematic illustration of a system for remotely controlling managed devices;

FIG. 6b is a schematic illustration of a mobile controller;

FIG. 7a-7d are flowcharts illustrating various methods for remotely controlling a managed device.

It should be noted that elements that have the same numerical designations in different drawings have the same structural features and the same functions, or are the same signals. If the function and / or structure of such an element is explained, then there is no need to re-explain them in the detailed description.

List of numerical designations in drawings l-6b:

100 system for remote control

102 system for remote control

110 managed device

112 receiver configured to receive a digital command

114 command processor

116 device parameter memory

120 mobile controller

122 tag readers

124 sender

126 location

128 user interface controller

130 access control module

132 memory

134 processor

136 transceiver

140 electronic tag

140a electronic tag

140b electronic tag

142 memory of public information

144 personal information memory

146 processor

150 configuration server

152 first wireless channel

154 second wireless channel

156 third channel

200 building

210 floor

220 first room

222 first mark

224 first lamp

230 second room

232 second mark

234 second lamp

240 third room

312 Authorized Program Information

314 ID of the managed device

316 Control shutdown information

400 mobile controller

410 user interface engine element

DETAILED OPTIONS

Although the present invention is sensitive to an embodiment in many different forms, one or more specific embodiments are shown and described in detail below, and it is intended that the present disclosure be considered as exemplary of the principles of the invention and not intended to limit the invention shown and described specific implementation options.

In FIG. 1 shows a system 100 for remotely controlling a managed device 110.

System 100 includes a managed device 110, a mobile controller 120, and an electronic tag 140.

The managed device 110 comprises a receiver 112 configured to receive a digital command. The managed device 110 is configured to modify an aspect of the managed device in response to receiving a digital command. The controlled device shown in FIG. 1, comprises a command processor 114 and a device parameter memory 116. The processor 114 is configured to interpret the received command and to change one or more device parameters stored in the parameter memory 116. Device parameters affect or determine the aspect of the device. The remote control system described here is suitable for home and office automation. Managed devices can be home or office equipment devices. The remote control system described here is also suitable for hospitals, public building automation, etc.

Below are many examples. For example, the controllable device 110 may be a lamp. The aspect of the light that is emitted by the lamp is remotely controlled. For example, system 100 can remotely control one or more of: dimming level, light intensity, color, white level, and on / off lamp state. For example, parameter memory 116 may comprise a parameter representation, for example, light intensity. The controlled device 110 is configured to set its light intensity in accordance with the light intensity parameter stored in the parameter memory 116. If a command is received at receiver 112, then processor 114 may determine what is required, for example, to increase light intensity. The processor 114 then increases the light intensity parameter stored in the parameter memory 116, assuming that it is not maximum. The controlled device 110 then changes its light to a higher intensity. The memory 116 may be a storage device.

Other examples of controlled device 110 include the following: controlled device 110 may be a heating device. A remotely controlled aspect may be one of: intensity of heating, ambient temperature, and the like. The controlled device 110 may be a ventilation device, the aspect being the intensity of ventilation. The controlled device 110 may be an air conditioning device, the aspect being one of: air conditioning intensity, ambient temperature, and the like. The controlled device 110 may be a remotely controlled blinds, the aspect being the open / closed state of the blinds, and the like.

A digital instruction may be encoded in digital format, for example, ASN.1 or XML, and the like. Receiver 112 may be a wireless receiver, for example, a Wi-Fi receiver. Receiver 112 may be a wired receiver, such as a receiver for an Ethernet cable. Receiver 112 may be a wireless receiver, part of a cellular network, like a Zigbee receiver, IEEE802.15.4 receiver, or IEEE 802.15.4g receiver, etc.

The electronic tag 140 is associated with a managed device 110. The electronic tag is configured for direct wireless electronic communication over the first wireless channel 152 by the tag reader 122 of the mobile controller 120. For example, the electronic tag 140 may be an RFID, NFC tag, or a contactless tag, such as Smart Bluetooth. Typically, the first wireless channel 152 will be an NFC connection. The range within which a connection can be made between the mobile controller 120 and the electronic tag 140 is so small that it turns out that the mobile controller 120 is close to the tag 140. Preferably, the range is selected so that the mobile controller 120 and the electronic tag 140 to be in the same room to be in contact. In embodiments, the range of the first wireless channel 152 has been selected as less than 50 centimeters. In some implementations, the range of the first wireless channel 152 is less than 10 cm, resulting in almost a touch of the mobile controller 120 and the electronic tag 140. In some implementation, the electronic tag 140 and the mobile controller 120 may be configured to require touch. before making a connection. Alternatively, the connection between the mobile controller and the tag may be made by Communication via the User Body (BCC), whereby a BCC can establish a wireless connection between the mobile controller and the tag using the user's body.

Two tags that can be used in systems 100 and 102 for tag 140 are shown in FIG. 3. The tag 140a comprises a public information memory 142, also simply referred to as a memory. The memory 142 may be read by a tag reader, in particular by a tag reader 122 of the mobile controller 120. In FIG. 3 also shows improved tag 140b. In addition to the public information memory 142, the tag 140b also includes a personal information memory 144. The memory 144 of personal information is not readable to unprivileged users; personal memory 144 may be completely unreadable outside the tag. For example, personal memory 144 can only be accessed off-label through an alternative interface, such as the so-called dual interface, and not through NFC. Personal memory 144 may only be writable. Electronic tag 140b also includes a processor 146 that can access personal memory 144. Electronic tag 140b is suitable for more advanced communication options such as request-response protocols. These options are explained in more detail below.

Label 140b is suitable for a dual interface; for example, tag 140b may be configured so that personal memory 144 is accessible only through an alternate, wired interface, while public memory 142 is accessible, at least readable, through a wireless interface.

The tag 140, for example, the tags 140a, and 140b may be a dual-interface tag that is read only through the wireless interface, but is read and write through the wired interface. A wired interface is used to configure a tag, for example, with a configuration server.

Words, public and personal, indicate different access controls. A mobile controller configured to control the managed device 110 is also configured to read public memory. Personal memory should be kept secret from ordinary users, and only accessible to trusted users, if at all.

Typically, tag 140 and memory 142 are configured so that any tag reader can read its contents. However, even then some access control can be used. For example, the contents of memory 142 may be encrypted with a key. Mobile controller 120 receives a key from another source, for example, out-of-band, from an access module, from a Building Management System (BMS), etc.

A memory 142 stores information identifying the managed device 120. This information can be used by the mobile controller 120 to establish a second wireless connection 154 between the mobile controller 120 and the managed device 110. There are various options for the identifying information. For example, the identifying information may contain the identifier of the managed device 110. The managed device 110 also contains the same identifier. In this case, the command can be transmitted by radio to multiple controlled devices. Managed devices are configured to execute the command if they have the same identifier, and to ignore if it is not.

Compared, for example, with a passive tag, tags with a dual interface have 2 interfaces: an RF interface and another interface, for example, Inter-circuit Interface of Integrated Circuits (I2C). The concepts of public / personal memory are different, but relative. Both the RF interface and the dual-interface tag can have public and personal memory, however this is easier to implement on the dual interface. For example, a dual-interface tag may have part of a storage device that is not accessible through the RF interface. The latter is not necessary, the system can use a tag with a dual interface, in which all of its memory is read through the RF interface.

The identifying information may be an electronic address, such as the IP address of a managed device 110, or a unique identifier, for example, a specific number, or a MAC address. The identification information may also contain the network details necessary to establish a connection to the managed device 110, for example, a password, for example, a password to access the wireless network to which the managed device 110 is connected. The identification information may also contain the SSID of the wireless network associated with the managed device 110.

The mobile controller 120 uses information identifying the managed device 110 to send a command in an electronic message to the device 110. The electronic message may contain management information based on the identification information, thereby configuring the message to reach the managed device 110. For example, the device 120 may include identifying information in an electronic message with the team.

For example, the identification information stored in the electronic tag 140 may comprise a resource identifier, such as a managed lamp identifier, also known as a "lamp id".

The electronic tag 140 may be associated with multiple controlled devices. In this case, the electronic tag 140 contains identification information for multiple devices. The description below assumes that only a single managed device is associated with an electronic tag 140, but it can be easily adapted to multiple managed devices: For example, if any information related to a particular managed device is stored on the electronic tag 140, then the electronic tag 140 may also store relevant information for other devices. For example, controller devices can be configured to intercept identifying information from a tag, and all controller devices that have the corresponding identifier will respond. At work, multiple managed devices and one associated tag will usually be located in the same room.

Using a single electronic tag with multiple devices is suitable for rooms with multiple controlled devices, such as multiple lights, or a light and HVAC device, etc. HVAC is a Heating Ventilation and Air Conditioning.

The memory 142 may store information regarding the computer program code required by the mobile controller 120 to remotely control the managed device 110. For example, the memory 142 may store the computer program code directly in itself; for example, as a so-called “software application” suitable for execution on a smartphone 120. The memory 142 may also store information regarding where to obtain the software; for example, memory 142 may store the name of the software application, or the URI or URL for the software. In particular, the mobile controller 120 may be configured to receive computer program code from the electronic tag 140 by implementing an access control module.

The memory 142 may store a condition for disconnecting control from the electronic tag through an electronic tag reader. This means that the access control policy is obtained from tag 140, and not from the central control system. In Figure 1, the mobile controller 120 prescribes the access control policy that it received from the tag.

The electronic tag 140 may be a so-called dual-interface tag. The dual-interface tag is configured with both a wireless and a wired interface. This means that the tag is configured for the first wireless channel 152, but can be independently configured through, for example, a building management system using the third channel. For example, the electronic tag 140 may be configured with a conventional NFC non-contact interface, and with a wired interface such as a PC interface.

The electronic tag 140 may also have only a wireless interface. Electronic tag 140 may be configured through this interface. However, the electronic tag 140 can also be made together with the managed device 110, the tag 140 and the managed device 110, each of which retains the same identifier; The tag 140 and the controlled device 110 together form a kit suitable for joint sale.

Mobile controller 120 includes a tag reader 122, a sender 124, and a user interface controller 128. Optionally, the mobile controller 120 comprises one or both of the clocks and the positioner. The mobile controller 120 shown in FIG. 1 contains both, but only a location identifier 126 is shown.

The tag reader 122 is configured to directly connect to the electronic tag via the first wireless channel and to receive information from the tag identifying the device to be controlled. The tag reader 122 may be an NFC reader device. For example, tag reader 122 may read memory 142 from electronic tag 140. If tag 140b is used, then mobile controller 120 does not have access to personal memory 144.

The sender 124 is configured to wirelessly send a digital command to a managed device via a second wireless channel 154 using information identifying the managed device. Sender 124 may use modulated radio frequencies to send an electronic message. For example, sender 124 may be a Wi-Fi sending device, or a cellular network device such as Zigbee, 802.15.4, 802.15.g. The tag reader 122 may also be configured to access the wireless Internet service, for example through a 3G or 4G service.

The first wireless channel 152 is a direct wireless connection, that is, there is no intermediate device between the mobile controller 120 and the electronic tag 140. However, the second wireless channel 154 may, but should not, be a direct connection. The second wireless channel 154 may be a direct wireless connection to a managed device 110, but may also be wireless, to an intermediate device, for example via a cellular network connected to multiple wireless connections, and wired from an intermediate device to a managed device 110, etc. . The intermediate device may be a module 130 (it is external), and / or BMS.

Mobile controller 120 includes user interface controller 128. The user interface controller 128 provides one or more control options to the managed device 110 for the user on the display of the mobile controller 120 (not shown in FIG. 1). The user interface controller 128 receives an input from a user regarding a control option. For example, a user may express that some aspect of the controlled device 110 may be increased or decreased.

In FIG. 6b shows an example of a mobile controller 120 in the form of a smartphone 400. The display of the mobile controller 400 shows an engine 410. The engine 410 can be used by a user to control an aspect. For example, using the engine 410, the user can inform the user interface controller 128 that he wants to increase or decrease the light intensity, for example, by moving the engine up or down, respectively. The display of the mobile controller 400 is touch.

The user interface controller 128 may be configured to directly generate a digital command that may be executed by the managed device 110; however, this task can also be solved by another unit of the mobile controller 120, for example, access control module 130.

The mobile controller 120 may include a location determiner 126. The positioner 126 is configured to determine the current location of the mobile controller 120, that is, to generate location information indicating the geographical location of the mobile controller 120. The positioner 126 may be configured to determine the current location of the mobile controller 120, using, for example, a device GPS or using a Wi-Fi signal, for example, from a Wi-Fi access point having a known location; either using a Bluetooth signal, for example from Bluetooth beacons, or using a GSM signal; or another internal location system. For example, using a Bluetooth signal, such as from Bluetooth beacons from known locations, works similar to using Wi-Fi signals from known locations.

The location system used does not have to be very accurate. Usually it is enough to determine the location to the level of the room. For some applications, it may even be sufficient to determine whether the mobile controller 120 is in the building or not.

Mobile controller 120 may be configured to receive, through a reader 122 of tags, an electronic tag 140 of computer program code implementing at least an access control module 130. Perhaps the computer program code also contains other parts of the mobile controller 120, such as the user interface controller 128. Mobile controller 120 may also receive a location and / or software identifier, for example, a name. Mobile controller 120 may receive software from either the electronic tag 140 directly or from another server, for example, using a second wireless channel 154 and / or using the Internet. Mobile controller 120 is configured to install and run software on mobile controller 120.

Mobile controller 120 includes an access control module 130. The access control module 130 is configured to selectively enable or disable the mobile controller 120 to control the managed device 110 using digital commands. The access control module 130 is configured to allow the mobile controller 120 to control the managed device 110 within the control period. The control period begins when the tag reader 122 wirelessly connects to the electronic tag 140, and ends when the control shutdown condition is satisfied. The access control module 130 is configured to verify that the period of control of the mobile communication device has begun and has not yet ended before allowing the mobile controller 120 to control the managed device 110.

There are many options for the location of the access control module 130. The authors found that a system for remotely controlling a managed device can be distributed among different devices in different ways. In the embodiment shown in FIG. 1, the access control module 130 is part of the mobile controller 120. However, this is not necessary; access control module 130 may also be part of a managed device 110 or a separate device.

Management of the managed device 110 may be accomplished by controlling the Building Management System (BMS). The BMS system is connected to and may be controlled by the managed device 110. The BMS system receives a command from the mobile controller 120 or the access control module 130 and executes them. For example, the BMS may increase the light intensity of the lamp in response to receiving a command from the mobile controller 120 or access control module 130. Another possibility is that the smartphone requires confirmation from the BMS before the managed device 110 receives its commands. For example, the mobile controller 120 may receive a digital confirmation, for example, an X.509 confirmation from the BMS, and uses this to digitally denote a digital command. Managed device 110 may verify the signature and reject the command if verification of the signature does not confirm.

Also, selective authorization or control blocking can be performed in a variety of ways: blocking the execution of a command in a controlled device 110, refusing to send or send a digital command so that it in no way reaches a controlled device 110, or disabling part of the user interface offered by the user interface controller 128 so that the user cannot formulate a command. If a high level of security is required, some or all of these options can be used together.

Systems in which the access control module 130 is part of the mobile controller 120 are typically somewhat simpler to implement: a building management system is not required in which the access control module 130 could be included. Also, the managed device 110 may be simpler and thus cheaper because it does not have to perform the functions of the access control module 130. However, the presence of the access control module 130 within the mobile controller 120 is also considered less secure.

Security can be provided in various ways. For example, you can add additional access control to the system, for example, requiring the authenticity of a digital command, for example, by the personal key of the mobile controller 120, so that only registered users can send valid commands. Alternatively, lower security requirements can be tolerated and rely on public scrutiny or legislative restraints.

The system requires that the mobile controller 120 be located close to the electronic tag 140, for example, within 50 cm, or even 10 cm, or even touching the electronic tag 140 in order to realize the first wireless channel. At this point, the mobile controller 120 may begin to control the managed device 110. Control will be maintained for a while, but the system has a built-in control shutdown. The condition for turning off the control can be determined depending on various parameters and depending on the intended effect. Two specific parameters turn out to be very effective, that is, the location of the mobile controller 120 and the time that has elapsed since the mobile controller 120 came into contact with the electronic tag 140.

For example, a control deactivation condition may specify a geographical area. The access control module is configured to obtain location information indicating a geographical location of the mobile controller, and to complete a control period if the geographical location of the mobile controller is outside a geographical area. For example, a geographic area can be selected as being close to the mark. For example, the geographic area may be within 100 cm of the electronic tag 140, or within the range of the electronic tag 140. The latter selection avoids the need for a location identifier, such as location identifier 126. Using location simulates the operation of a conventional wall switch. To control, for example, ordinary light, it is necessary to physically switch to the wall switch that controls this light. This control deactivation condition has a similar effect, while the user is physically close to the electronic tag 140, he can control the managed device 110. This control deactivation condition also naturally resolves an access conflict. If two users try to control the light at approximately the same time, they physically do it one after another. This allows them to resolve an access conflict immediately in a social environment, rather than through a technical solution.

The geographical area can also be set larger, for example, by the size of the room. It is well suited for meeting rooms. While the user is in a meeting, he can control the managed device 110. However, as soon as he leaves the meeting room, he also transfers control to the managed device 110.

The geographical area can also be set even larger, for example, by the size of the building. It is well suited for personal use. As long as the user remains in the building, he can control the managed device 110. However, as soon as he leaves the building, he also transfers control to the managed device 110. This eliminates the possibility for the user to control, for example, office light from his home, but excludes the control being turned off each time. when a user leaves his office.

Another possibility is to set a certain period of time for the control to be disabled. The access control unit 130 is configured to end the control period after the control period has continued for at least the said time period. For example, access control module 130 may start a timer configured to provide an interrupt when a certain period of time has elapsed. When an interrupt is received, the access control unit 130 ends the control period. The access control module 130 may start a timer when the mobile controller 120 is in contact with the electronic tag 140 or when the contact is interrupted. The latter option eliminates control deactivation while the user is facing electronic tag 140, which may be unnatural. On the other hand, when the electronic tag 140 is integrated into a work area, such as a desktop, it may be best to start the countdown when the contact is established. Otherwise, the user may place his mobile controller 120 on the electronic tag 140 to suspend control, at least until he resumes the operation of the mobile controller 120.

For example, the time period may be set to approximately 30 seconds, starting when the first wireless channel 152 is interrupted. It also mimics the operation of a conventional wall switch, but achieves the effect in a different way. Although the user has a mobile controller 120 in contact, or close to the electronic tag 140, he can control the device 110 being controlled. When he leaves the electronic tag 140, for example, he leaves, he can continue to control it for a brief period of time. Since the interval is short, it cannot be far removed from the electronic tag 140 without turning off the control.

The time period may be a predetermined period. In this case, the electronic tag 140 only needs to determine that a period of time is being used; access control module 130 is configured with its duration. The time period may be less than a minute, for example, 30 seconds, or more than a minute, for example, 2 hours or 8 hours.

Instead of a period of time, the electronic mark 140 can also set the absolute time. For example, management can be turned off at the end of the day, for example at 19:00. The absolute time to turn off control can be used to start the building management system to begin controlling the managed device 110 and possibly many other managed devices in the building. Absolute time for disabling management can also be used with office space planning software, for example, management can be disabled at the end of a scheduled meeting.

When the control shutdown condition is more flexible, especially when absolute times are used, the system is better suited to use dual-interface tags that can be programmed from a server, such as a building management system, in addition to reading through the first wireless channel 152.

Another possibility is to set the geographic area and time period as a condition for turning control off. These two conditions can be combined in the "and" mode or in the "or" mode. For example, to implement the “and” option, the access control module 130 may be configured to obtain location information indicating the geographical location of the mobile controller, and to complete the control period if the geographical location of the mobile controller is also outside the geographical area and the control period has continued the course of at least said time period. For example, to implement the “or” option, the access control module 130 may be configured to obtain location information indicating the geographical location of the mobile controller, and to complete the control period if either the geographical location of the mobile controller is outside the geographical area or the control period has continued the course of at least the mentioned time period, or both. This is also suitable for situations in which, for some reason, the mobile controller cannot obtain or determine its location, for example, if GPS and / or other location tools are turned off, or if its location is not reliably determined.

For example, time periods may well be combined with the “or” option when the latter corresponds to the building. This may mean that the user turns off the control as soon as his time runs out or he leaves the building. For example, a user may have control over the duration of a meeting (using either a control period or an absolute time to turn off control). Management should be turned off when the meeting ends, or when the user leaves the building. If the user leaves the meeting, for example, for a coffee break, but returns before the meeting has ended, management will not be turned off. Interestingly, the access control module is configured so that, after the end of the control period, not to start a new control period until the tag reader wirelessly connects to the electronic tag again.

The access control module 130 may accept the condition of disconnecting the control from the electronic tag using an electronic tag reader. This means that different control devices can have different conditions for shutting down the control.

The access control policy is set in the NFC tag, and not in the central building management system, for example. A smartphone application provided to the mobile controller 120 may enforce an access control policy. For example, the electronic tag 140 may store an access policy in memory 142 in terms of location and time.

In FIG. 1, the optional configuration server 150 is further shown. The configuration server is configured to store identifying information and / or control disconnection conditions in the electronic tag 140. The configuration of the tag 140 may use different means than the configuration server 150, for example, in manufacturing. The electronic tag 140 and the configuration server 150 are configured to communicate with each other over a third channel. The third channel is a wired channel, that is, at least wired at the boundary with a mark 140. The third channel may be an I2C channel. When using the configuration server, tag 140 contains a wired interface for connecting to the configuration server via a third channel. Configuration server 150 may be combined with a BMS and / or access control module 130.

In an embodiment, a personal light control smartphone application reads policy from an NFC tag. The smartphone application ensures that lighting control commands are only sent to the lamp or to the BMS (building management system) when the user's smartphone is within the framework of the policy (in terms of location and / or time). For example, when the user's smartphone is too far from the lamp, the user loses control over the lighting. In an embodiment, the application is configured to receive a cryptographic key. For example, the application may contain a key, for example, embedded in the application, or the application may receive a key from the BMS. An application can use the key to decrypt and / or verify the authenticity of information received from the tag.

In FIG. 2 shows a system 102 for remotely controlling a managed device 110. In many respects, the system 102 may be the same as the system 100, however, in the system 102, the access control module 130 is external to the mobile controller 120. The sender 124 is configured to wirelessly send digital commands to the access control module 130 via the second wireless channel 154. The access control module 130 is configured to verify that the control period of the mobile communication device has started and not ended, and if this way and that to send digital commands to the controlled device.

In FIG. 2 shows an access control module 130 as a separate device. Access control module 130 may be integrated into the BMS. The access control module 130 can also be integrated into the managed device 110. The last option avoids the BMS, but can increase the cost of the managed device 110.

In an embodiment, an electronic tag 140b is used for the electronic tag 140, and the access control unit 130 is configured to execute a request-response protocol with 10 electronic tags 140 via the tag reader 122. For example, access control module 130 may generate a one-time code (nonce), for example, a serial number or a random number. The access control module 130 may then send a one-time code to the electronic tag as a request, sending a one-time code from the access control module 130 to the mobile controller 120 using the second wireless channel 154, and then to the electronic tag 140 using the first wireless channel 152. The control module 130 access may receive a response from the electronic tag depending on the one-time code. For example, processor 146 may generate a response by accessing personal memory 144 and a one-time code. For example, the processor 146 may sign or encrypt the one-time code using a key stored in the personal memory 144. The access control module 130 may receive the one-time code through the first wireless channel 152, the tag reader 122, the sender 124 and (part) the second wireless channel 154. The module 130 access control is configured to then verify the authenticity of the response regarding a one-time code. The access control module 130 blocks the beginning of the control period if said authentication gives a negative result, or the control period ends if it has already begun.

If the access control module 130 is located in the managed device 110, then the complete second wireless channel 154 is used. If the access control module 130 is located in the mobile controller 120, then the second wireless channel 154 is not necessary for communication between the access control module 130 and the electronic tag 140.

The request-response protocol provides a high level of confidence that the mobile controller 120 is actually close to the electronic tag 140. Although potential “middle-person” attacks are still possible, this is not considered a serious threat, since it still requires physically finding someone close to electronic tag 140.

Typically, in both systems 100 and 102, devices 120 and 110 each contain a microprocessor (not shown) that runs the corresponding software stored in devices 120 and 110. For example, the software could be downloaded and stored in the appropriate memory , for example, in RAM or Flash memory (none are shown). Devices 140 and 130 may also be equipped with microprocessors and memory units (not shown).

In the event that the system 102 uses a location-based control deactivation condition, the location identifier 126 may be used and contained in the mobile controller 120. The mobile controller 120 may be configured to send location information from the mobile controller 120 to the access control module 130. However, the location determiner may also be outside the mobile controller 120. For example, the mobile controller 120 may also be located based on its Wi-Fi signal registered at one or more of the multiple access points. In the latter case, the mobile controller 120 does not have to provide location information. This increases security because the attacker is blocked with illegal changes to the location information that the mobile controller 120 reports.

In FIG. 4 shows a possible implementation of access control module 130. The access control module 130 comprises a memory 132, for example, a storage device, a processor 134, and a sender / receiver (transceiver) 136. The transceiver 136 is configured to communicate via a second channel with the mobile controller 120 and the managed device 110. Between the managed device 110 and the access control module 130 to be BMS. If the access control module 130 is contained in another system, then processor, memory, and communication capabilities with another system can be shared.

During operation, systems 100 and 102 may operate as follows. The mobile controller 120 is placed within the communication range of the electronic tag 140. The mobile controller 120 and the electronic tag 140 establish a first wireless channel 152. The mobile controller 120 receives information from the electronic tag 140 with respect to the managed device 110, for example, the mobile controller 120 reads the memory 142 of the tag 140. Mobile the controller 120 receives at least identifying information for the managed device 110. The mobile controller 120 may also accept a condition for disconnecting the control from the electron second mark 140. Modul130 access control is informed that the mobile controller 120 and the electronic tag 140 established a connection. The access control unit 130 then starts the management period. For example, the access control unit 130 stores, for example, the identifier of the managed device 110, received from the electronic tag 140, a control deactivation condition. The access control module 130 may also store, for example, a time stamp indicating when the connection was established. Mobile controller 120, or access control module 130, may 30 comprise a clock for this purpose. Instead of a timestamp, a timer can also be used.

If the system is configured to start the time period when the connection between the mobile controller 120 and the tag 140 is interrupted, then instead of the latter case, the time stamp can be saved.

Using the user interface controller 128, the user then controls the managed device 110. Based on the user's action, a command is generated and sent to the access control module 130, optionally together with the current location of the mobile controller 120. The access control module 130 then checks whether the managed device 110 can be controlled. For example, depending on the control shutdown condition: the access control module 130 checks that the time that has elapsed since the establishment (or interruption) of the contact between the electronic tag 140 and the mobile controller 120 is within the time period defined in the control shutdown condition. For example, the access control unit 130 verifies that the current location of the mobile controller 120 is within the geographic area specified by the control deactivation condition. If the control shutdown condition is satisfied, then the control period ends. For example, the access control module 130 may remove information received from the electronic tag 140. For example, the access control module 130 may flag the information indicating that the control has been disabled.

If the access control module 130 is an external mobile controller 120, then the required information can be sent from the mobile controller 120 to the access control module 130. The command is sent through the access control module 130, and the access control module 130 may be configured to block the direction of the command to the managed device 110 if the control period is completed. If the access control module 130 is located within the mobile controller 120, then the command may be completely blocked from sending. The access control module 130 may also block the generation of a command, for example, already in the user interface controller 128. If the access control module 130 is located in the managed device 110, then the access control module 130 may block the execution of the command.

If the access control module 130 is external to the mobile controller 120 and the electronic tag 140 has a dual interface, then the access control module 130 may be informed of the installed and / or interrupted first wireless channel 152 through a channel that does not include the mobile controller 120, for example, through a wired connection between the electronic tag 140 and the access control unit 130. This improves safety.

After the management period is completed, the access control module 130 requires that the mobile controller 120 is again connected to the electronic tag 140 before starting a new management period.

In FIG. 5 shows a possible implementation of the memory 142. The tag 140 stores in memory available to the mobile controller 120 the following fields: Authorized program information 312, Identifier 314 of the managed device, and Information 316 to disable the control.

For example, an additional authorized program information field 312 contains the location of the machine code for the access control module 130 and / or user interface controller 128. The identifier 314 of the managed device contains the identifying information of the managed device 110, for example, an identifier, or IP address. The control shutdown information 316 contains information regarding the control shutdown condition. Field 316 is optional because access control module 130 may receive a control disconnect condition from another source. For example, access control module 130 may obtain a control disable condition from a table indexed by the identifier of the managed device 110; or, for example, all conditions can be the same and hardcoded in the access control module 130; or, for example, access control module 130 may receive information from an external source, for example, from a BMS, etc. However, receiving the condition for disconnecting the control from the electronic tag 140 is a preferred embodiment.

The control shutdown condition can be encoded in various ways. For example, a pattern may be defined in which multiple control shutdown conditions can be displayed. The control disconnect condition may then be written at 140 in accordance with the pattern. For example, transceiver 136 may contain four fields: (location, range, duration, and / or). Location and range together define a sphere with location as center and range as radius. A sphere defines a geographical area. The duration may be a period of time expressing how long the switchable control is required. "And / or" indicates whether both conditions must be satisfied before the control is removed, or any condition. The location / range or duration can be set to zero to indicate that the corresponding condition is not used.

In FIG. 6a, building 200 is shown. Building 200 has at least one floor 210. Floor 210 has multiple rooms: three rooms are shown: first room 220, second room 230 and third room 240. Third room 240 does not use the system. Although it may have managed devices, they are managed by another system, such as BMS. The first room 220 has a first lamp 224 and a first mark 222. The second room 230 has a second lamp 234 and a second mark 232. Tags and lights are configured in accordance with a system for remote control, as described here. In the example described here, the first tag 222 and the second tag 232 are configured with location-based controls only, with predetermined areas corresponding to the rooms.

A user may walk with his mobile controller 120, such as a smartphone, into the first room. There, the mobile controller 120 makes a connection to the first tag 222. It then gains control of the first lamp 224. For example, it turns on the light. When he leaves the room, control is turned off. The mobile controller 120 can no longer control the first lamp 224. It may be that a BMS (not shown) now controls the first lamp 224 and, for example, turning on the light. When the user then enters the second room 230, he can establish a connection with the second mark 232. He can then turn on the second lamp 234.

The following describes additional systems, options, and implementations that use lights, smart phones, and NFC tags, as examples of managed devices, mobile controllers, and electronic tags, respectively. Other options are also possible, as noted here.

In some cases, resources or equipment are located in publicly accessible areas where more than one person has access and can issue management commands. The lights in the office building are such an example. Some smartphones have the ability to register location with relatively good accuracy, for example, considering either everything, or one of the following: GPS location coordinates, Wi-Fi access points, Bluetooth beacons, GSM signal, and this will become even better in the near future. Near Field Communication (NFC) is a well-known and accepted (by standards) technology for short range communications. In past years, most smartphones came equipped with an embedded NFC controller (reader / writer). It is undesirable for users who are not in the immediate vicinity of the resource to issue management commands for it. Such an example is a smartphone application for controlling lighting. When a user enters this space, he would like to be able to carry out personal lighting control in this area and apply his personal preferences. The authors realized that, by providing control, it is also necessary to establish a mechanism for disabling control, since otherwise it is possible to control the area periodically or continuously throughout the day, encountering the control actions of those who are physically present in this area. For example, when the user leaves the controlled space (or its immediate proximity), I would like him to remove the lighting control. This is especially appropriate in public spaces (such as office buildings).

When a wall switch is used to control the light, users who control the light are limited by its location; however, if control is transferred to a personal mobile device, the spatial limitation is disabled. Multiple users controlling the light within a certain space at a distance can create quite unexpected / erratic situations.

The existing GPS sensor and mapping software in the user's smartphone can be used to determine its location and its relative distance to the lamp that it controls. The lights in the building have known locations. The user can take over and remove control of the lamp by providing an area or (row) of lamp with an NFC solution that contains information such as:

- identifier of the lamp (s) for control,

- access policy for this fixture, including location and / or duration,

- an application for use in controlling a lamp,

- network props with which the lamp can be controlled,

An option to restrict access to the application is a duration (for example, as soon as the user takes control of a room, he can control the equipment in this room for a limited time), but this approach is limited in some cases, such as office spaces, where users spend considerable time. Another option for limiting the control of luminaires is through a building management system that can monitor who controls what light at any given time and prescribe an access policy at this level. This approach introduces a wait time and can lead to a less smooth change in the light in the case of, for example, controlling the brightness level.

A specific implementation option may include the following elements:

- smartphone with:

- one or more positioning systems, such as GPS, 3G network, Wi-Fi, Bluetooth

- NFC and Wi-Fi connectivity

- user interface

- a lamp or a number of lamps (controlled devices)

- location of the lamp

NFC tag (s), each belonging to a fixture or row of fixtures, containing read-only information, such as:

- application used to control lighting

- resource identifier (id lamp)

- resource access policy (location boundary and / or timer)

Access control policies can be defined in the NFC tag, and not in the central management system. A smartphone application provided to users can then enforce an access control policy. The label may contain an access policy in terms of location and time. A smartphone application for personal lighting control reads the policy from the NFC tag. A smartphone application can ensure that lighting control commands are only sent to the lamp or to the BMS when the user's smartphone is within the limits of policy (in terms of location and time). For example, when the user's smartphone is too far from the lamp, the user may lose control over the lighting. This mechanism ensures that control applications, such as a lighting control application, can only be used in the immediate vicinity of a physically managed resource. Many of the lighting properties of luminaires can be controlled, for example: on / off status, dimming level, light intensity and color, white level, etc.

Each luminaire in a series of luminaires can be identified using an NFC tag. The NFC tag can define a location boundary in the shape of a sphere represented by its center and radius length. The NFC tag can also set the time limit. To ensure that the access policy is not changed by unauthorized people, the NFC tag can only be read, or only recorded by the building management system.

Example NFC Tag information regarding reading - NFC tag only:

Smartphone Authorized Application: Name

Light ID: 3452233

Lamp Location: L (x, y, z)

Location boundary (defined by the sphere): the center of the sphere C_s (x, y, z) and the radius R of the sphere, or some other specified region, such as an ellipsoid (x, y, z, Rl, R2)

Time line: T

Additionally, the NFC tag may include information on how to access a network through which light can be controlled. For example, if the light is controlled via Wi-Fi, the NFC tag should contain a Wi-Fi SSID (and password). The lighting control application can automatically connect to a given network to enable light control.

This invention can be applied to control light in personal office spaces. The NFC tag can be placed near the wall light switch. All occupants of the room gain access to control all the light in this room by touching the mark. Their access ends as soon as the timeout ends (for example, 10 hours). After the specified timeout, they take control off. They can regain control by touching the NFC tag again. A possible extension may include loss of control as soon as the boundary of the location, for example, 100 m, is passed (this ensures, for example, that the user touches the NFC tag just before leaving the room and continues to control the light from the house).

This invention can also be applied to control light in public office spaces. An NFC tag can be placed on each desktop. By touching the NFC tag with his smartphone, the user gets access to the light directly above the desktop. Access control policies can be limited by both time and location. This can ensure that users can only control the light in the immediate vicinity of the desktop (e.g. 10 meters) and for a limited time (e.g. 2 hours). As soon as they remove control, they must again touch the NFC tag to change the light settings.

Another application is for public meeting rooms. An NFC tag can be placed at the entrance to the room. Touching the NFC tag, the user gets access to the whole world in the room. An application can provide a user with a multitude of predefined options (e.g., presentation, meeting, brainstorming, etc.). Access to light control may be limited by the location of the room. As soon as the user leaves the surroundings of the premises, access is lost. Another option for the BMS is to reconfigure the NFC tag each time the meeting begins at the time for which the room was reserved. (For example, if a user has made a reservation for a room for 2 hours starting at 10:00, he takes control of the light in the room by touching the mark, and his access expires at 0:00). This can be combined with confirmation that the user who has access is the user who made the reservation (this can guarantee that only the meeting organizer can control the light).

Most of the office spaces are adjacent, determining the boundary of the location in the form of a sphere, you can come to the intersection of two spheres. In this situation, the user can control the light in two or multiple locations at the same time (provided that he touched the corresponding NFC tags). A smartphone application can be designed in such a way that it provides the user with a choice of which light to control if the user can control more than one set of lights. An alternative to applying lighting control is to control only the last set of lights for which the user has taken control by touching the NFC tag.

A geographic area can also be defined not by a sphere, for example, in the form of polygons, etc. This is suitable for more accurate location determinants.

In FIG. 7a shows a flowchart of a method 700 for remotely controlling a managed device. Method 700 can be used in systems 100 or 102. Method 700 comprises:

Connecting 702 directly to the electronic tag via the first wireless channel, for example, via a mobile controller 120. Receiving 704 information from the tag identifying the managed device, for example, by the mobile controller 120. Sending a digital command 706 wirelessly to the managed device via the second wireless channel using the information identifying a managed device, for example, by a mobile controller 120. Permission 708 to control a managed device within a control period, for example, access control module 130. The control period begins when the tag reader is connected wirelessly with the electronic tag, and ends when the control disconnect condition is satisfied. Receiving 710 a digital command in a managed device, such as a managed device 110. Modification 712 of an aspect of a managed device in response to receiving a digital command, such as a managed device 110.

Charts 720, 740, and 760 provide several options for implementation. These implementations use lighting control, a smartphone, and an NFC tag as examples of a managed device 110, a mobile controller 120, and an electronic tag 140, respectively. Other choices are also possible, as indicated here.

In FIG. 7b is a flowchart illustrating a method based on location only. At step 721, the user touches the NFC tag with his smartphone. At step 722, the smartphone starts and / or downloads an authorized application and reads the tag. At step 723, the user activates the smartphone application. At step 724, the smartphone searches for the coordinates of the smartphone (M (x, y, z)), for example, through the Locator function. At step 726, the smartphone determines whether the coordinate of the smartphone is within a location boundary. Connector 725 indicates the periodic repetition of step 724, for example, every 30 seconds. At step 728, this estimate leads to a conditional transition: is the smartphone within the boundaries, for example, the distance (C_s, M) <= R? Here, C_s displays the center of the sphere, for example, the location of the controlled device 110 or electronic tag 140. The value R represents the radius of the sphere. If the smartphone is still in the sphere, then proceeds to step 732, otherwise, to step 730. At step 732, application controls are allowed. At step 734, the user controls the UI to change the lighting settings. At step 736, the smartphone sends the light settings to the lamp. At block 730, application controls are locked, for example, unavailable.

In FIG. 7c shows an example of a possible flowchart 740 based solely on location and policy prescribing at the very last moment, immediately before sending the control command.

At step 741, the user touches the NFC tags with his smartphone. At step 742, the smartphone starts and / or downloads an authorized application and reads the tag. At step 743, the user activates the smartphone application. At block 744, application control is allowed. At step 746, the user controls the user interface to change lighting settings. At step 748, the smartphone application searches for the coordinates of the smartphone (M (x, y, z)), for example, through the Locator function. At step 750, the smartphone determines whether the coordinates of the smartphone are within a location boundary. At step 752, a conditional transition is performed to: The smartphone is within the boundaries: distance (C_s, M) <= R. If so, the transition goes to step 754, otherwise, to 756. At step 754, the smartphone sends the light settings to the lamp. At step 756, the user interface informs the user that the smartphone is out of range.

In FIG. 7d shows an example of a possible flowchart 760 based only on a time lock. At block 761, the user touches the NFC tag with his smartphone. At block 762, the smartphone starts and / or downloads an authorized application and reads the tag. The smartphone receives time T from the mark. At step 764, the smartphone application starts the access time for the time defined as T. At step 765, the user activates the smartphone application. At block 766, application controls are allowed. At step 768, the user controls the UI to change lighting settings. At step 770, the smartphone sends the light settings to the lamp. At step 772, the smartphone application searches for the time of the smartphone and checks if the time has expired. At step 774, a conditional transition to the elapsed timer time is performed. If so, proceeds to step 776, otherwise, to 778. At step 776, the elapsed time is indicated to the user. At step 778, the smartphone sends the light settings to the lamp.

There are many different ways to implement the methods, as will be obvious to a person skilled in the art. For example, the execution order of the steps may be different, or some steps may be performed in parallel. In addition, other steps of the method may be inserted between steps. The inserted steps may represent improvements to the method as described herein, or may be unrelated to the method.

The method in accordance with the invention may be performed using software that contains instructions to cause the processor system to execute methods, for example, 700, 720, 740, or 760. The software may include only steps performed by a particular subobject of the system. For example, only the steps performed by the mobile controller 120, or the managed device 110, or the access control module 130, etc., can be included in a particular software product. The software may be stored on a suitable storage medium such as a hard disk, diskette, storage device, etc. The software can be sent as a signal over a wire, or wirelessly, or using a data network such as the Internet. The software may be made available for download and / or for remote use on a server.

It should be noted that the invention also extends to computer programs, in particular to computer programs on a medium adapted to practice the invention. The program may be in the form of program code, object code, intermediate code, between program and object codes, such as in a partially compiled form, or in any other form suitable for use in the implementation of the method in accordance with the invention. An implementation option related to a computer program product comprises computer-executable instructions corresponding to each of the processing steps of at least one of the formulated methods. These commands may be subdivided into subroutines and / or may be stored in one or more files, which may be linked statically or dynamically. Another embodiment related to a computer program product comprises computer executable instructions corresponding to each of the means of at least one of the systems and / or formulated products.

It should be noted that the above embodiments illustrate, but not limit, the invention, and that those skilled in the art will be able to design many alternative implementations.

In p.p. formulas, any numerals placed between parentheses should not be construed as limiting the formula. The use of the verb "contains" and its conjugation does not exclude the presence of elements or steps other than those stated in the formula. Indication of an element in the singular does not exclude the presence of a plurality of such elements. The invention may be practiced by means of hardware containing several distinct elements, and by means of a suitably programmed computer. In the formula for a device, several means are listed, and several of these means can be embodied by the same hardware element. The fact that certain provisions are given in mutually different dependent clauses formulas does not mean that a combination of these provisions cannot be used to take advantage.

Claims (38)

1. System (100, 102) for remote control of a managed device (110), and the managed device contains - a receiver (112) configured to receive a digital command, the controlled device being configured to modify an aspect of the controlled device in response to receiving a digital command, the system comprising - a mobile controller (120), and the mobile controller contains a tag reader (122) configured to directly connect to the electronic tag via the first wireless channel (152) and to receive information from the tag identifying the device being controlled (110), and a sender (124) configured to wirelessly send a digital command to a managed device via a second wireless channel (154) using information identifying the managed device, and - an access control module (130) configured to selectively enable or disable control by the mobile controller of the managed device using a digital command, the access control module is configured to allow the mobile controller to control the managed device within the control period, and the control period begins when the reader is connected wirelessly tags with an electronic tag and ends when the control disconnect condition is satisfied. 2. The system of claim 1, wherein - the controllable device is a lamp, and wherein the aspect is a property of the light emitted by the lamp, the property of light being one of: a dimming level, light intensity, color, white level, and on / off state; or - the controlled device is a heating device, and wherein the aspect is one of: intensity of heating and ambient temperature; or - the controlled device is a ventilation device, and wherein the aspect is the intensity of ventilation; or - the controllable device is an air conditioning device, and wherein the aspect is one of: intensity of air conditioning and ambient temperature; or - the controlled device is a remotely controlled blinds, and the aspect is an open / closed state of the blinds. 3. The system of claim 1, wherein - the control disconnection condition defines a geographic area, the access control module being configured to obtain location information indicating a geographic location of the mobile controller, and to complete the control period if the geographic location of the mobile controller is outside the geographic area; and / or - the control shutdown condition defines a period of time, wherein the access control module is configured to end the control period after the control period has continued for at least said time period; and / or - the control disconnection condition sets the geographical area and time period, the access control module being configured to obtain location information indicating the geographical location of the mobile controller, and to end the control period if the geographical location of the mobile controller is outside the geographical area and the control period lasted the course of at least said time period; and / or - the control deactivation condition sets the geographical area and time period, the access control module being configured to receive location information indicating the geographical location of the mobile controller, and to complete the control period if either the geographical location of the mobile controller is outside the geographical area or the control period lasted the course of at least said time period. 4. The system of claim 3, wherein the mobile controller comprises a location determiner configured to generate location information indicating a geographical location of the mobile controller. 5. The system of claim 1, wherein the access control module is configured so that after the control period is completed, a new control period does not begin until the tag reader wirelessly reconnects to the electronic tag. 6. The system of claim 1, wherein the access control module is contained in the mobile controller, the access control module being configured to receive a condition for disconnecting control from the electronic tag using an electronic tag reader. 7. The system of claim 1, wherein the mobile controller is configured to receive computer code from an electronic tag implementing an access control module. 8. The system of claim 1, wherein the range of the first communication channel is less than 50 centimeters. 9. The system of claim 1, wherein the access control module is configured to execute a request-response protocol with an electronic tag through a tag reader, generating a one-time code, sending said one-time code to an electronic tag as a request, and receiving a response from the electronic tag depending on the aforementioned a one-time code, the access control module being configured to verify the authenticity of the response with respect to the one-time code, the access control module blocking the beginning of the control period if The mentioned authentication failed. 10. The system of claim 1, wherein the access control module is external to the mobile communication device, wherein the sender is configured to wirelessly send a digital command to the access control module via a second wireless channel, the access control module being configured to verify that the control period a mobile communication device started and did not end, and if so, then to send a digital command to the managed device. 11. The system of claim. 1, containing a managed device and an electronic tag. 12. A configuration server configured to store identifying information and / or control disconnection conditions in an electronic tag according to claim 1, wherein the electronic tag is configured to communicate with the configuration server via a third channel, the electronic tag comprising a wired interface for connecting to the configuration server via the third channel. 13. A method for remotely controlling a managed device, the method comprising - connection directly to the electronic tag via the first wireless channel, - receiving information from a tag identifying a managed device, - sending a digital command wirelessly to a managed device on a second wireless channel using information identifying the managed device, - permission management of the managed device within the control period, and the control period begins when the wireless connection of the tag reader with an electronic tag and ends when the control shutdown condition is satisfied, - receiving a digital command in a controlled device and - a modification of an aspect of a controllable device in response to receiving a digital command. 14. A computer-readable medium with a computer program implemented thereon for remotely controlling a managed device, the controlled device comprising a receiver configured to receive a digital command, wherein the controllable device is configured to modify an aspect of the controllable device in response to receiving a digital command, the computer program being configured to execute it on a mobile controller, the computer program comprising - a tag-reading code configured to connect the tag reader directly to the electronic tag via the first wireless channel and to receive information from the tag identifying the device to be controlled, - a send code configured to wirelessly send a digital command to a managed device on a second wireless channel using information identifying the managed device, and - an access control code configured to selectively enable or disable control by the mobile controller of the managed device using a digital command, the access control module is configured to allow the mobile controller to control the managed device within the control period, and the control period starts when the tag reader is electronically connected to the electronic label and ends when the control disconnection condition is satisfied.

Images