Systems, devices, and methods for controlling network applications

Abstract

This invention relates to a control system, particularly a lighting control system, having a control line for controlling the power modes of network components (such as data forwarding components and end nodes (e.g., application control components)) according to a global application plan. Controlling the power modes may include shutting down data ports in the control network. Data forwarding devices with switchable data ports can be used to efficiently shut down data paths through the control network. Furthermore, a protocol is provided for querying the status of network components and receiving schedules for unattended operation, thereby enabling improved energy use and enhanced safety.

Description

[0001] This application is a divisional application of the invention patent application filed on August 9, 2016, with application number 201680050192.4 and entitled "System, apparatus and method for controlling network applications". Technical Field

[0002] This invention relates to application control networks, such as—but not limited to—lighting control networks. In particular, this invention relates to the efficient use of network components according to application requirements and network topology. Background Technology

[0003] In application control networks (such as—but not limited to—lighting control networks), data forwarding devices are used to forward messages between different application control components, such as sensors and actuators in lighting applications.

[0004] According to Heller et al., in "ElasticTree Reducing Energy in Data Center Networks," data forwarding devices, like data forwarding equipment, are inefficient under low load. Currently, a typical data forwarding device uses only 5% less power when idle (powered but not used for communication) compared to when it is in a state where it is fully loaded with data transmission.

[0005] In wired application control environments, application devices can be powered via Power over Ethernet (PoE). As known from DE10 2008 035544 A1, a PoE terminal device is shut down by turning off its power via a controllable switch integrated into the network card to which it is connected. However, intermediate PoE devices, such as data forwarding devices, are devices that turn all ports on / off, just like ordinary Ethernet data forwarding devices without PoE functionality. Typical PoE data forwarding devices will therefore require a relatively high additional power budget to “keep the line active.” This is standardized in the Ethernet standard “802.3at” (i.e., “Eight-oh-two-dot-three-Alfa-Tango”). The Ethernet standard 802.3at for Power over Ethernet requires a minimum standby power of 250mW per port. In large installations with many nodes, this translates to significant standby power, which comes not only from data communication equipment (such as data forwarding devices, including but not limited to data switches and routers) but also from nodes attached to them, such as electric actuators / loads or sensors. This leads to several problems:

[0006] High standby power generates heat and reduces the lifespan of electronic products (unless the products are designed to exceed safety standards to cope with it), which leads to additional costs.

[0007] • Due to the standby power consumed by data communication networks, application terminal notes with great energy-saving potential (such as LEDs in lighting sectors) may become less substantial.

[0008] In a sustainability context, there is a greater need for more ambitious energy performance calculations for new buildings and / or innovation and reduction in energy use.

[0009] Energy loss itself results in significant costs in medium to large buildings.

[0010] • The energy loss of the equipment usually heats the surrounding air, which requires additional cooling, and the cooling itself consumes additional energy, thus incurring costs.

[0011] PoE devices cannot be forced into a "sleep" state that would mean the device is completely shut down, because PoE devices will have to maintain their network interface to receive wake-up commands, and therefore PoE devices also require power received via Ethernet. However, shutting down components with external power supplies within the network can also negatively impact overall network performance in undesirable ways; for example, data paths may be truncated or inappropriately lengthened. Summary of the Invention

[0012] Therefore, the purpose of this invention is to enhance the efficiency of application control networks, particularly by reducing energy consumption while ensuring the required functionality and quality of service.

[0013] This objective is achieved through the subject matter of the independent claims. Further embodiments are illustrated in the dependent claims.

[0014] The method according to the invention provides a control unit that is enabled to shut down network components or portions thereof according to application plans defined for various application scenarios, thereby saving energy without losing the ability to control the network for applications. A data forwarding device with a switchable data port can be employed to shut down data paths "in efficiency." Furthermore, a protocol is provided for querying the status of network components (such as data forwarding devices or end nodes (such as application control devices)). This protocol further provides a schedule for unattended operation, allocating network components accordingly, thereby enabling improved energy use and enhanced security. Network components receiving the corresponding schedule can operate in the appropriate power mode, for example, turning on or off based on the application scenario.

[0015] In one aspect of the invention, a control unit is provided for use in an application control network, wherein the application control network includes at least one application device communicatively coupled to the application control network via a data port of a data forwarding device, wherein the control unit is adapted to determine a power schedule for the data port of the data forwarding device according to a predetermined application control scenario, and to provide the power schedule to the data forwarding and / or application device for self-sufficient power management during predetermined time slots determined in the power schedule, wherein during the predetermined time slots determined in the power schedule, the data forwarding and / or application device is adapted to power off its network interface communicatively coupled to the control unit.

[0016] In software-defined application systems, application scenarios can define the interactions of application components within an application control network. For example, in a lighting control network, an exemplary lighting scenario can define which lights should be turned on or off when a specific sensor is triggered. Based on knowledge of which application components are needed in a specific application scenario, the application components can be mapped to the network topology, and the corresponding data paths through the application control network can be determined. The resulting paths are contained within the application control scenario. Depending on the application control scenario, the control unit can set the power mode of all data ports of data forwarding devices along the communication path that are not needed in the corresponding application control scenario to a sleep mode, for example, turning them off. Turning off data ports along the data communication path that are not needed in the application control scenario can result in significant energy savings. For those data ports along the communication path that are needed according to the application control scenario, the power mode can be set to normal operation, for example, turning them on.

[0017] In one embodiment of the invention, the application device is powered via a data port of a data forwarding device. The application device powered via the data port (e.g., via Power over Ethernet) will not receive any power when the data port is off. Therefore, additional energy can be saved. However, to ensure that the application device is not turned off when needed, the data port can only be turned off based on the application control scenario, which provides knowledge of when the application components are needed (e.g., during specific time slots of a day, week, or year). As an example, a typical office building would be least likely to be used at night. Therefore, for lighting scenarios during the midnight to 4 a.m. time slot, only minimal lighting equipment might be required (which could be activated, for example, when a night guard passes by), and multiple detection sensors and light actuators in the building could be turned off.

[0018] In one embodiment of the invention, the control unit is further adapted to determine whether an application device is authorized to couple to a data port of a data forwarding device, and if it is determined that the application device is not authorized, to deactivate the corresponding data port of the data forwarding device. By having a control unit possessing knowledge of the application plan (e.g., a light plan showing lights and sensors installed in each room of a building) and corresponding knowledge of the network architecture, unauthorized access to the network can be prevented by identifying new application components and selectively disabling the data port corresponding to the socket into which the application device is plugged. Therefore, providing a control unit capable of controlling the data forwarding device down to the port level can further help improve network security.

[0019] In another aspect of the invention, a method is provided for controlling application devices and / or data forwarding devices within an application control network, wherein the application devices are connected to the data ports of the data forwarding devices, and the method includes the following steps:

[0020] • Determine whether the application device and / or the data forwarding device coupled to the data port of the data forwarding device are needed within a predetermined time period, and / or

[0021] • Determine whether the application device is authorized to be coupled to the data port of the data forwarding device.

[0022] • Provide a power schedule to application devices and / or data forwarding devices to enable self-sufficient power management during predetermined time slots defined in the power schedule, during which the data forwarding and / or application devices are adapted to power down their communicatively coupled network interfaces provided to the control unit.

[0023] In addition to determining whether a specific data path is needed for an application scenario, it's also possible to determine whether an application control component is authorized, for example, to be coupled to the data path via a data port of a data forwarding device. Based on knowledge about the application control components present in one or more application scenarios, it's possible to determine whether the application control component is authorized. If it's not needed for routing, or if an unauthorized application control component is detected being inserted into a data port, the corresponding data port can be put into hibernation mode, effectively shutting down the corresponding data path.

[0024] In another aspect of the invention, a computer program executable in a processing unit is provided, the computer program including program code components for causing the processing unit to perform methods as defined in the preceding aspects of the invention when the computer program is executed in the processing unit.

[0025] In another aspect of the invention, an apparatus for use in an application control network is provided, wherein the apparatus includes a network interface for receiving or sending control messages to other components within the application control network. The apparatus further includes a storage unit for storing a schedule provided by control messages from a control unit via the network interface, wherein the schedule includes information indicating different operating power modes of the apparatus for specific operating time slots; and a processing unit for processing the schedule to operate the apparatus in different power modes at predetermined times according to the schedule, wherein the apparatus is adapted to power down its communicatively coupled network interface provided to the control unit according to at least one predetermined time slot in the schedule.

[0026] For operability, network components (such as end nodes in the form of application control components (such as, for example, but not limited to, sensors and actuators in lighting applications), but also intermediate components (such as, for example, data forwarding devices)) require their network interfaces to be powered in order to respond to incoming control commands. To switch to other power modes, such as sleep mode, for example, shutting down the device, it must be ensured that the device is powered on again when needed. Therefore, the control unit provides the device with an operating schedule that defines the operating modes for specific operating time slots. Thus, the device can enter a low-power mode (e.g., sleep) for a predetermined period (during which no incoming control messages are expected), and switch back to normal operating mode according to the provided schedule when a message might be expected. In this way, the device can be controlled in an energy-efficient manner without sacrificing network performance due to unresponsive components.

[0027] In one embodiment of the invention, the device is powered via a network interface and includes an energy storage unit adapted to store a sufficient amount of energy to power the device after a predetermined time when the device has been scheduled to be in sleep mode, during which time the device cannot receive energy via the network interface. When a node in a network system is powered via a network interface, for example via Power over Ethernet (PoE), powering down its network interface will result in a dead link because it requires an active network interface to receive energy in order to receive commands to power up the network interface. Therefore, the energy storage unit is used to store a sufficient amount of energy to power the device after a predetermined time when the device has been scheduled to be powered down.

[0028] In one embodiment of the invention, the device further includes a monitoring unit for monitoring the state of the energy storage device and initiating recharging if the amount drops below a predetermined value. To ensure sufficient energy to power up the network interface, the monitoring unit can determine energy degradation and initiate recharging by changing the power mode to a state that allows the battery to be recharged, but can still maintain low energy consumption, for example, by keeping it off regarding receiving data messages.

[0029] In one embodiment of the invention, the device is configured to periodically power on after a predetermined time since the device has been set to sleep mode according to the schedule, in order to request an update to the schedule. To avoid any dead links, such as routing paths needed for one application scenario but interrupted or shut down for another outdated application scenario, it is essential to ensure that the device periodically powers on and requests an updated schedule. This routine can be particularly important for long-duration application scenarios to ensure proper data routing across the network. The device can also be configured to keep the network interface operational if no requested schedule update is received. As a precaution, the device may only enter sleep mode when the schedule is up-to-date.

[0030] In one embodiment of the invention, the device is a data forwarding device for transmitting messages within a control network. Much like terminal nodes that are temporarily not needed according to the application scenario, intermediate data forwarding devices can also be configured in a power-saving mode by a network control unit having knowledge of the time slots of the entire data forwarding device that are not needed according to the application control scenario. Therefore, a time-slot schedule can be provided to the data forwarding device, which can switch to a low-power mode or even be set to a hibernation mode.

[0031] In embodiments of the invention, the data forwarding device includes one or more data ports that can be connected to different components within a control network, and defines separate power modes for the respective data ports from a schedule provided by the control unit. In this case, the different power modes also include setting selected data ports of the data forwarding device to sleep, thereby cutting off specific data communication paths through the network, thus providing further granularity to the application control scenario.

[0032] In one embodiment of the invention, the device includes clock circuitry to maintain an updated clock, and a processing unit for processing the schedule operates the device in different power modes only after verifying that the device's internal clock is up-to-date. As a precaution, the device can only switch to another power mode and thus become unreachable from the outside once the internal clock has been verified to be up-to-date. Generally, the clock may experience clock skew or may otherwise be improperly configured. To counter attacks where a hacker would manipulate the clock or when the clock is not yet configured (e.g., during installation), the device will operate in a fail-safe mode, in the "on" state. Secure clock protocols, such as, for example, PTP or NTP, can be used.

[0033] It should be understood that the control unit of claim 1, the method of claim 4, the computer program of claim 5, and the apparatus of claim 6 have preferred embodiments that are similar to and / or equivalent to those defined in the dependent claims.

[0034] It should be understood that the preferred embodiments of the present invention may also be any combination of the dependent claims or the above embodiments and the corresponding independent claims.

[0035] These and other aspects of the invention will be apparent from the embodiments described below, and will be elucidated with reference to the embodiments described below. Attached Figure Description

[0036] Figure 1 An exemplary embodiment of a domain model for energy-saving application control is shown.

[0037] Figure 2 A system diagram of an energy-saving SDA control system is shown.

[0038] Figure 3 The control lines from the SDA system (e.g., the SDL system) to network components, terminal nodes, and data forwarding devices are shown.

[0039] Figure 4 A cascaded network switch is shown.

[0040] Figure 5 A diagram illustrating the different power states of the network interface and the transition mechanisms between these power states is provided.

[0041] Figure 6 A flowchart for reconstructing the time schedule is shown. Detailed Implementation

[0042] Some embodiments are described exemplarily in the context of lighting control applications. However, it should be understood that the embodiments are not limited to lighting control. Those skilled in the art will recognize that these methods and devices can be used in any other control application that requires a similar topology.

[0043] In the following text, Software-Defined Application (SDA) systems provide knowledge about the application-specific needs and instructions specified in the application plan. For example, an example of an SDA system is a Software-Defined Lighting (SDL) system, which defines a lighting plan that includes one or more lighting scenes. The lighting scene can define which lights will be turned on if a specific sensor is triggered.

[0044] Network management systems, such as Software-Defined Networking (SDN) systems, provide knowledge about the individual network components existing in a mesh network and can control the configuration of routing tables, etc. However, the network management system is unaware of the application-specific connections between specific network components.

[0045] Together, SDA and SDN systems constitute a Software-Defined Control (SDC) system, which combines two layers (application and network). The SDC system maps application / lighting components onto the network topology and thus has the knowledge to determine which components or parts of components can be turned off without degrading the (lighting) control network's ability to perform (lighting) applications.

[0046] In some embodiments, a fully automated lighting control system (as described in co-pending application (ID02752)) can be used to save energy by analyzing all data paths that may enable the lighting control scenario and selecting the path that results in the minimum total energy consumption for all components. Usage patterns accumulated from specific lighting control applications are used to select paths based on criteria such as time, frequency, duration, and energy usage. Based on optimization techniques, the system can predict and proactively minimize the energy usage of data paths for all control scenarios. In a communication network shared with other control applications, the control applications can interact with each other to improve decisions regarding maximum total energy savings and avoid self-destruction.

[0047] Figure 1An exemplary application control network 300 is illustrated, comprising a collection of application control components 301, such as sensors for detecting signals and actuators for switching electrical loads. The application control components 301 may be powered by a wired communication link or alternatively by an optional energy source or storage device 330. The application control components 301 may be connected, via wired or wireless means, to a boundary network component 101, which is part of a communication network 100. The boundary network component 101 is connected to a management system 230 via a network path in-between 180. The network path in-between 180 is capable of transmitting and forwarding data according to rules programmed by the network management system 230 (so-called “data path definitions”). The SDA system 203 has knowledge of an application plan 204 that specifies which lighting control components 301 are required to participate in the corresponding application control scenario. Thus, the SDA system 203 can generate information that requires the shutdown of one or more application control components (e.g., any subset of sensors or actuators) in the application control network 300. The SDA system sends power change commands (on / off / idle / other power state levels) to the corresponding application control components. Furthermore, the SDA system 203 controls the network management system 230 to program the correct communication paths (filters with correct durations and addresses), which is necessary to ensure that the application control components can receive the required control messages via the network. By having knowledge of the required application control components for the application and the required communication paths between them, the SDA system can also determine which network components, such as data forwarding components, should be turned on and off based on application requirements. For example, if a communication path is not needed for a certain period, it may be advantageous to turn off the data forwarding device along that communication path in terms of energy savings. Therefore, the SDA system can also send power change commands (on / off / idle / other power state levels) to the corresponding data forwarding components. Typically, a data forwarding component provides several data ports for communication with other corresponding data forwarding components or application control devices, thus providing multiple communication paths. If only one of these communication paths is not needed, the SDA system can provide instructions to turn off only a single communication path by setting the corresponding data port of the data forwarding device to a sleep mode.

[0048] An example control application is a lighting application. According to... Figure 2The lighting control network 300 includes a data switcher with individually switchable data ports. The lighting control network 300 includes various lighting control components, such as, but not limited to, lamps 303, presence detectors 304 with passive infrared (i.e., PIR) sensors, light switcher sensors 305, and, in short, any sensor 306 that can interact with any actuator 302 as required, as specified in the lighting plan 202. Each example of the aforementioned sensors and actuators can be connected to switchable data ports 121 to 125 of the data forwarding component 102. The switchable data ports can switch or change the power state to on / off or a power level in between. When a PoE device is connected to a component, that component also functions as a power component. The switchable data / power ports (121 to 126 in this example) can be controlled by a switcher control module 120. The switcher control module 120 can receive and process messages to switch the data ports to on / off / idle or a power setting in between. Southbound module 110 will run data protocols to interconnect with network management system 231, which can be an SDN system, and / or with SDL system 201. Forwarding module 130 implements rules on how data is forwarded between data ports. Modules 110, 120, and 130 can be implemented as software processes running on microprocessor 140 using memory module 141 for execution and storage module 142 for storing calculated results, time schedules, and firmware. Additionally, lighting control network 300 can deploy wireless sensors 311 and / or wireless actuators 310 connected to communication network 100 via wireless bridges. Traffic between sensors, actuators, and SDL system 201 is transmitted via network path middleware 180 under the control of the SDL system. Network path middleware 180 can be a hybrid of data switches, which may or may not support changes to the power state of the entire data forwarding device and the power state of specific (multiple) corresponding data ports(s). Alternatively, another embodiment could be a router or another data forwarding component working in conjunction with filters for forwarding data.

[0049] like Figure 1 and Figure 2 The SDC system 200 described herein analyzes the “optimal” path based on a control plan that includes knowledge of multiple application control / scenarios (e.g., time, frequency, and duration) and other constraints (e.g., energy, consumption, etc.) and combines all necessary paths for all components, as detailed in co-pending application ID 02752. Communication paths or flow definitions can be provided to network components for programming routing tables, etc.

[0050] To enable / disable or otherwise alter the communication status and / or power level of lighting control components and / or data forwarding devices within the application control network, the SDA system 203 has functional control lines to the relevant network components 101, 180 and exemplary 301 (e.g., any sensor 306 or actuator 302), such as... Figure 3 And as shown in the table below:

[0051]

[0052]

[0053] It should be understood that control lines 290 to 293 can be separate protocols or (whole or in part) bundled within a corresponding network management protocol (such as an SDN protocol). Line 296 represents the interface between the network management system (e.g., an SDN system) and devices 101, 180, and 302 used to forward data via interconnect links between data ports controlled by control lines 291, 292, and 293.

[0054] Data ports on a power-controllable data forwarding device (i.e., a data switcher) can be programmed through various power states. Additionally, it may be beneficial to query the actual power state of the data ports on the data forwarding device. An exemplary embodiment is discussed below. Potential power savings may be the number of data ports on the data switch that do not require power. However, in a typical communication network topology, a data forwarding device can, as... Figure 4 As depicted in the diagram, the data forwarding device 102 at some point between the start A and end B of a data path may need to regulate one input port and one output port to remain energized in order to forward data from A to B. However, even in this case, the SDC system may determine certain time slots in which it is highly likely no data will be delivered through a particular path. In these cases, the SDC system can program the data forwarding device and its data ports to be shut down. Naturally, when a component in the data network is shut down, neither the overall component nor the data ports associated with the communication path can forward data messages. Therefore, if the component along the path cannot be reliably reactivated, there is a risk that the communication path through the mesh network may collapse and remain in an inoperable state. A protocol can be used to ensure that only the permissible power state of the data ports on the data switch is configured. Combined with fallback capability, this protocol will prevent dead communication links. The corresponding flowchart is shown in [the diagram]. Figure 5 As shown in the image.

[0055] In the "On" state (1), the data port of the data switch is powered to communicate with and / or deliver power to devices connected to and communicating with the data port. The data port may provide signals to its surroundings or the SDC system.

[0056] After a certain amount of time t X Afterward, when no communication is received at the data port, the data port can be switched to the "idle" state (2). In this state, although the data port does not receive any communication, it is still powered. However, any incoming data communication triggers the data port to switch back to the on state. Therefore, the power consumption in the idle state is only slightly less than the power consumption in the on state.

[0057] In the "Low Power" (3) state, the data port has a power mode in which it cannot directly respond to data communication but is still listening. Upon receiving a wake-up message, it will switch to the "On" state, ready to process communication. The data port remains in the "Idle" state for a predetermined time t. Y You can then switch to low power.

[0058] In the "Hibernate" (4) state, the data port is not powered for communication and / or power delivery and will not be available for data communication. To reactivate the data port, information must be provided to the data switch, such as the defined time slot in which it should be powered on again.

[0059] If the SDA system is not specifically configured based on a specific application plan, the data port can only use timer t. X and t Y Some default values ​​toggle between state 1 (On), state 2 (Idle), and state 3 (Low Power). However, when the SDA system is configured according to the corresponding control plan, components in the control network can switch to state 3 (Low Power) and state 4 (Sleep) at any appropriate time to save energy consumption.

[0060] As described above, the default fallback mechanism described below ensures that network components, particularly data forwarding devices, periodically transition from a sleep state (4) to an on state (1). It can notify the software-defined control system of its status / presence in order to receive configuration message 10, which may include a schedule defining on and off time slots that can be specified down to individual data ports and individual data streams. Furthermore, configuration message 10 may specify a time interval t. X and t Y and / or t ZIn an exemplary implementation, subsequent reception of this power state configuration message 10 can allow the data port to switch between all states from ON 1, Idle 2, Low Power 3 to Sleep 4. When no power state configuration message 10 is received, the data port may remain in the ON state until it is programmed by the SDA system.

[0061] The data switcher manages which of the multiple possible data paths takes priority and when the power state is eventually changed to a power-saving state to avoid unusable communication links.

[0062] This protocol enables SDL systems to program interval t directly or through SDN systems. X t Y t Z And a time-slotted schedule. The protocol also enables the SDL system to query the current status of data ports and the actual schedule of data forwarding components.

[0063] Figure 6 A flowchart illustrating a method for preventing dead links due to misprogramming is shown. Any device instructed to enter a state of sleep mode, which is enabled to process schedules for unattended operation within the lighting control network, must maintain an updated clock. When no time can be determined (2), the device will only operate in a state of up (3) and attempt to update its clock (4).

[0064] If the clock is feasible (2), the device will listen for appropriate messages (5) with planning information (15) sent by the SDC system via the control network through its control network interface.

[0065] Periodically and / or after receiving a certain amount of data (6) from the SDC system, the device will attempt to reconstruct the time schedule (7) from the data messages it has received. This time schedule can define one or more subsequent time slots.

[0066] If the device has an updated clock corresponding to the system time, the device can process time schedules.

[0067] The time schedule specifies the mode, data routing (i.e., path), start and stop times for network components (especially data forwarding devices). To enhance the flexibility of this ad hoc data protocol and reduce data load, many options can be considered for such a schedule, such as different block granularity, very large and short time window definitions, checksums, and so on.

[0068] The device will check and filter scheduled events (8) according to a certain priority and avoid double definition. During any given time period, the need for a functional data port will always take precedence over the need to switch a data port to sleep or shut down. Therefore, dead links that are unavailable in time are not allowed.

[0069] The following table shows an example of an arbitrary time schedule used for switching data ports (and achieving energy savings "in efficiency"):

[0070]

[0071] If the schedule is valid (8), the device can notify of success and update the schedule in the storage device so that it and the process can be processed by the switcher control module 130.

[0072] • If the schedule is invalid, an error will be notified and the equipment will restart. The equipment may or may not invalidate the current schedule.

[0073] Especially for long-duration data path definitions, using larger granularity in the time schedule can reduce the temporary load of data messages going to the network and provide robustness for network operations should the SDL system become unavailable for any reason. The SDL / SDC system should ensure that the duration of the time schedule is consistent with the definition of the data path.

[0074] It should be understood that the data protocol for implementing this schedule can carry the schedule as a whole, or it can carry only the information from which to build the schedule.

[0075] When the time schedule expires or a time slot in the time schedule expires, the device will fall back to "always on" mode to avoid dead links.

[0076] A management system with control lines, such as an SDC system (which extends to all basic data ports along the data paths between the corresponding sensor(s) and actuator(s) interacting in a lighting control scenario), allows for the significant ability to minimize energy consumption. Lighting control networks based on data forwarding devices have relatively high idle energy usage, and lighting control messages on the control network do not consume much bandwidth. The SDC system can monitor lighting control commands and extract patterns, such as when there are many commands and when there are few or no commands at all during a time window of the day. These patterns are highly application-dependent, such as the actual location of the sensors and / or actuators (buildings, rooms) where they are installed. If it is determined that certain lighting control devices are not needed during a specific time slot, these devices, along with the data ports of the corresponding data forwarding devices serving those lighting control devices, can be turned off. Accordingly, certain data communication paths through the communication network are closed. However, based on the extracted patterns, the SDC system knows when each communication path needs to be re-enabled. Therefore, the SDC system can provide the data forwarding devices with a time schedule for on / off states. The data forwarding device needs to process this information and reliably shut down and reconnect itself when and where necessary. Because once a data port is closed, communication, including providing further control messages, is no longer possible, the data forwarding device includes a fallback method to avoid dead devices once it is programmed to shut down. This process can be fully automated before or during the use of the system without any manual configuration. The system will manage itself according to the actual use of the control network.

[0077] Application management systems with control lines, such as the SDC system (which reach all basic data ports along the data communication path between the corresponding (multiple) sensors and (multiple) actuators interacting in the lighting control scenario), allow for a significant ability to enhance security.

[0078] The SDC system enhances security by automatically "patching" data ports. Under normal circumstances, unused and unnecessary data ports are shut down. An attacker can still physically connect cables to the lighting control network to attempt to connect manipulators, sensors, or actuators. However, when the corresponding data port of the data forwarding device is not powered, it offers no possibility of communication. Therefore, it is impossible for an attacker to gain access to an operational communication link in the control network.

[0079] Whenever a new component is added to the lighting control network, the SDC system, which maintains the global lighting control plan, can compare the new state with the previous state and check whether the new component is legitimate or authorized. In other words, the SDC system knows:

[0080] Which sensors and actuators are registered / exist in the lighting control network;

[0081] Which sensors and actuators interact in which lighting control scenarios?

[0082] o Possible data communication paths between these corresponding components.

[0083] If the SDC system is not in a mode where it accepts new components into the lighting control network, it will compare the new component with the previous one. If it determines that the new component is ineffective, it effectively shuts down the communication path by setting the corresponding data port to a sleep state.

[0084] In hibernation mode 4, such as Figure 5 As described, new equipment can connect its cable receptacle to the data port of the data forwarding equipment, but the data port will not detect the new equipment because the corresponding port or service link is not active. It could be a long time before the schedule allows the data port to be switched back on. To facilitate the registration of new equipment, the power cycle will be reset. Figure 5 The flowchart in the diagram is a state machine, and the state machine will start the data port according to the default state "on".

[0085] To allow the installation of new components, a special mode can be set up in which new devices can be registered in the system.

[0086] However, when the SDC system is not in a special mode where it is allowed to register new devices, the SDC system compares the new device with a snapshot of previously known devices and determines whether it can enter the control system or whether this is not allowed. If not allowed, the SDC system can keep the corresponding data port in a dormant state.

[0087] The SDC system can trigger an alarm if an attacker attempts to connect a cable outlet to another data port outlet on the same data switcher or another data forwarding device. By combining the network topology with the lighting control plan, preferably as a visual map with physical components, the SDC system can indicate the approximate physical location (room / lobby section) of the attack. This alarm can be presented to the user using a building map, relative coordinates, GIS of room facility management codes, or otherwise entirely. The SDC system accumulates knowledge about lighting scenarios where certain sensors and actuators (e.g., lights and switchers) interact with each other in certain spaces (e.g., rooms). The SDC system can combine this information with a representation of the communication network as a visual map to pinpoint the data switcher or data port from which the attack originated.

Claims

1. An apparatus (100) for use in an application control network (300), wherein the apparatus includes a network interface for receiving control messages from or sending messages to other components within the application control network, wherein the apparatus further includes: Storage unit (142) for storing a schedule provided by control messages from the control unit via the network interface, wherein the schedule includes information indicating different operating power modes of the device for a specific operating time slot; as well as Processing unit (140) is used to process the schedule to operate the device in different power modes within a predetermined time according to the schedule; The device is adapted to power off its network interface, which is communicatively coupled to the control unit, according to at least one predetermined time slot in the schedule, such that communication with the application control network and the provision of further control messages are not possible during the at least one predetermined time slot, and the device is adapted to restore power to the network interface during a later predetermined time slot, thereby ensuring that the device can receive the required control messages through the application control network. The device enters a low-power mode for a predetermined period of time, during which no incoming control messages are expected, and switches back to normal operating mode according to a provided schedule when a message is expected.

2. The apparatus (100) of claim 1, wherein the apparatus is powered via the network interface and includes an energy storage unit adapted to store an amount of energy sufficient to power on the apparatus after a predetermined time when the apparatus has been set to a sleep mode according to a schedule, wherein the apparatus cannot receive energy via the network interface during the sleep mode.

3. The apparatus (100) according to claim 2 further includes a monitoring unit for monitoring the state of the energy storage unit and initiating recharging if the amount of energy drops below a predetermined value.

4. The apparatus (100) according to claim 1, wherein, The device is configured to periodically power on after a predetermined time, after which the device has been set to sleep mode according to the schedule, in order to request an update to the schedule.

5. The apparatus (100) of claim 4, wherein the apparatus is configured to keep the network interface operational if no requested update is received.

6. The apparatus (100) according to claim 1, wherein the apparatus is a data forwarding device for transmitting messages within the application control network.

7. The apparatus (100) of claim 6, wherein the data forwarding device includes one or more data ports (121, 122, 123, 124, 125) connectable to different components within the control network (300), and the schedule provided by control messages from the control unit defines separate power modes for the respective data ports.

8. The apparatus (100) of claim 1, wherein the apparatus includes a clock circuit to maintain an updated clock, and wherein the processing unit for processing the schedule operates the apparatus in different power modes only after verifying that the internal clock of the apparatus is up-to-date.

9. The apparatus (100) according to claim 1, wherein the apparatus is an application control component.

10. The apparatus (100) of claim 1, wherein the application control network (300) is a lighting control network, and the apparatus is a lighting control component.

11. The device (100) according to claim 1, wherein the application control network (300) is a lighting control network, and the device is an actuator or a sensor.

12. An apparatus for use in an application control network (300), wherein the application control network includes at least one application device (303) communicatively coupled to the application control network via a data port (121) of a data forwarding device, the apparatus further including a storage unit and a control unit, wherein the control unit is adapted to determine a power schedule for the data port (121) of the data forwarding device according to a predetermined application scenario, and to provide the power schedule to the data forwarding and / or application device (303) for self-contained power management during predetermined time slots determined in the power schedule, during which the data forwarding and / or application... The device is adapted to power down its communicatively coupled network interface to the control unit such that communication with the application control network and the provision of further control messages are impossible during the predetermined time slot, and the data forwarding and / or application device is adapted to restore power to the network interface during a subsequent predetermined time slot, ensuring that the application device can receive the required control messages through the application control network, wherein the data forwarding and / or application device enters a low-power mode for a predetermined time during which no incoming control messages are expected, and switches back to normal operating mode according to a provided schedule when a message is expected.

13. The apparatus of claim 12, wherein the application device (303) is powered through the data port (121) of the data forwarding device.

14. The apparatus of claim 12 is further adapted to determine whether the application device (303) is authorized to couple to the data port (121) of the data forwarding device, and if it is determined that the application device (303) is not authorized, to set the corresponding data port (121) of the data forwarding device to a sleep mode.

15. A method for controlling an application device (303) and / or a data forwarding device within an application control network (300), wherein the application device (303) is connected to a data port (121) of the data forwarding device, and the method comprises: Determine whether the application device (303) coupled to the data port (121) of the data forwarding device and / or the data forwarding device are needed for a predetermined time period, and / or Determine whether the application device (303) is authorized to be coupled to the data port (121) of the data forwarding device. A power schedule is provided to the application device (303) and / or the data forwarding device to enable self-sufficient power management during predetermined time slots defined in the power schedule. During these predetermined time slots, the application device and / or the data forwarding device are adapted to power down their communicatively coupled network interface to the control unit, making communication with the application control network and the provision of further control messages impossible during the predetermined time slots. Furthermore, the application device and / or the data forwarding device are adapted to restore power to the network interface during subsequent predetermined time slots, ensuring that the application device can receive the required control messages through the application control network. The application device and / or data forwarding device enters a low-power mode for a predetermined period of time, during which no incoming control messages are expected, and switches back to normal operating mode according to a provided schedule when a message is expected.

16. A computer-readable medium, characterized in that... It includes computer program code components for causing the processing unit to perform the method as defined in claim 15 when the computer program code components are executed in the processing unit.

Images