Integrated building automation device with integrated KNX power supply, KNX IP interface and Matter bridge functions.

Abstract

The invention relates to the technical field of building automation and smart home systems, and specifically concerns an integrated building automation device that enables KNX-based automation infrastructures to work together with Matter-based smart home ecosystems.

Description

1 TARIFF INTEGRATED KNX POWER SUPPLY, KNX IP INTERFACE AND MATTER BRIDGE INTEGRATED BUILDING AUTOMATION DEVICE WITH FUNCTIONS Technical Area The invention relates to the technical field of building automation and smart home systems, in particular. KNX-based automation infrastructures together with Matter-based smart home ecosystems. It relates to an integrated building automation device that enables its operation. 10 The invention is particularly useful for KNX-based automation in building automation and smart home systems. enabling their infrastructures to work together with the Matter ecosystem, from network entry KNX processes the energy it receives through appropriate power conversion and regulation circuits. While providing the necessary power supply for the TP line; it also supports KNXnet / IP Tunneling 15. communication, KNX-Matter data mapping operations, and bidirectional communication between the two systems. Integrated KNX power supply that performs protocol bridging functions, KNX IP with integrated building automation device featuring interface and matter bridge functions It is related. The Invention's Infrastructure KNX provides lighting and climate control systems for residential buildings, hotels, offices, commercial buildings, and similar structures. curtain / blind, energy management, security and various building automation functions It is one of the communication infrastructures used in its implementation. KNX TP-based 25 KNX systems include sensors, actuators, thermostats, switches, DALI gateways, and similar devices. The devices communicate via a KNX TP bus. For the KNX TP bus to function, the line must have suitable electrical connections. The supply of nutrients must be ensured. In known applications, this function is usually performed by 30 people. This is performed by an independent KNX power supply. On the other hand, the KNX TP bus is used to connect to Ethernet / IP-based networks. KNX IP interfaces are used. These interfaces include KNXnet / IP Tunneling. 2 KNX communication mechanisms for ETS or other compatible IP clients This enables access to the TP line. With the development of smart home systems, devices from different manufacturers have a common ground. The Matter protocol, which aims for collaboration across the application layer, is also included in section 5. It has begun to be used within the Matter ecosystem of existing KNX systems. Protocol and data model conversion between KNX and Matter for the purpose of connection. Bridge or gateway devices can be used to perform this function. In the known technique, the KNX power supply and KNX / IP or various gateway functions are the same 10 Solutions exist for the device to be located within the building, as well as for different buildings with KNX. gateway that performs bidirectional protocol conversion between automation protocols They also have structures. Similarly, KNX systems are in the Matter ecosystem. KNX-Matter bridge solutions are also available that enable representation. However, in current solutions, the KNX–Matter bridging function is implemented. In these systems, a separate KNX power supply is usually required to power the KNX TP line. This is required. In this case, protocol bridging and IP access are performed on a single device. Even if it can be done internally, the system requires the KNX TP line to be operated. It requires the inclusion of an additional power supply device. 20 The use of separate devices increases the need for DIN rail and panel space, as well as the network and With the proliferation of KNX connections, the increase in the number of terminals and cabling, and This makes the installation more complicated. In addition, the electronic circuit board... Increased variety of housings, terminals and connectors; production, software installation, 25 Function testing, quality control, inventory, supply, packaging, shipping, maintenance and spare parts. This also leads to parts management becoming more complex. Another problem with known solutions is the power level required to supply the KNX TP line. power electronics circuits with sensitive KNX / IP and Matter communication circuits 30 electrical, thermal and electromagnetic risks of operating them together in the same device It requires additional design in terms of compatibility. 3 In the literature, there is a reference to the Chinese patent application numbered CN103763187A regarding this subject. “This invention integrates EnOcean and KNX IP gateway, communication network and protocol conversion. It describes the method. EnOcean and KNX IP gateway, communication network and protocol. The conversion method utilizes embedded internet technology, KNX technology, and EnOcean. By skillfully combining technology, KNX technology uses cable 5 in the installation process. disadvantages include the need for distribution and the limited speed of information transmission. overcomes this by leveraging KNX's easy extensibility and other advantages. by bringing them together, facilitating the implementation of smart building and smart home projects. It provides flexibility and allows the user to use the KNX bus protocol over the internet. You can easily monitor and manage smart building equipment remotely in 10 seconds. This enables it to be implemented. Meanwhile, EnOcean and KNX with the IP gateway communication network and protocol conversion method, remote equipment maintenance and integration It enables equipment management and allows equipment to be actively used over the internet. It enables sending and receiving messages. EnOcean terminal equipment operating power. The fact that it does not require a source, the control system is 15 in the actual construction process. It greatly facilitates their creation and integration and saves energy. It provides..." The aforementioned application refers to EnOcean and KNX's IP gateway and communication network and method. It is explained. 20 In the literature, there is a reference to the Chinese patent application numbered CN105357111A regarding this subject. “This invention describes a gateway that converts ZigBee and KNX protocols.” A ZigBee and KNX protocol conversion gateway, KNX equipment, a ZigBee sensor, and It consists of KNX-ZigBee integrated gateway equipment; here, the KNX equipment is 25 The signal transmitted by ZigBee is routed through KNX-ZigBee integrated gateway equipment. is transmitted to the sensor; and the KNX equipment control signal is transmitted by the ZigBee sensor. or data, via KNX-ZigBee integrated gateway equipment using the protocol. It undergoes conversion and is transmitted to the KNX equipment. ZigBee and KNX protocols Transformation gateway, ensuring a high degree of integration; a single independent 30 Single-chip microcomputer design of integrated gateway equipment instead of a control unit. and implemented through network protocol conversion design; and via the gateway. It has advantages such as combining ZigBee and KNX networks.” is provided. 4 The application in question concerns a gateway for converting ZigBee to KNX protocol, and a radio. The field of communication is explained. Furthermore, in the literature, the subject is discussed in the Chinese utility model application numbered CN207251643U. Regarding this, “This utility model includes the control motherboard, KNX bus gateway, and KNX power supply 5 its power source, including LCD screen and LED indicator light plate, is a smart system. "Residential gateway" provides the host computer. KNX bus gateway, KNX power supply, The LCD screen and LED indicator light plate are respectively connected to the electrical power of the control main board. The KNX power supply is connected to a 220V switching power supply. KNX data The gateway connects to the KNX bus interface card. The KNX power supply connects to the KNX data 10. It is used to provide power to the pathway. The KNX power supply is divided into two parts: one part The KNX bus power supply is one part, and the other part is the KNX bus auxiliary power supply. It is the source. KNX bus gateway, KNX bus device and control motherboard. It is used for data transmission between them. The KNX bus interface card is a three-way KNX data It is a concentrator that includes the bus; two of these tunnels are the KNX bus and bus 15. "One tunnel includes an auxiliary electrical power supply, while the other tunnel only contains the KNX data bus." These statements are included. In the application mentioned, the main unit consists of a control motherboard and a KNX bus network. The Smart Home 20 includes a gateway, a KNX power supply, an LCD screen, and an LED display panel. The gateway server is described. For the reasons mentioned above, a new integrated building automation device is needed. It was needed. Purpose of the Invention Given the current state of the art, the aim of the invention is to overcome the existing disadvantages. The goal is to develop a new integrated building automation device that eliminates this problem. Another purpose of the invention is to enable the operation of a KNX-based building automation system and A single integrated system of functions necessary for integration with the Matter ecosystem. The goal is to create a structure that enables this to be carried out within the device. Another objective of the invention is to provide a separate external KNX power supply for powering the KNX TP bus. The goal is to create a structure that eliminates the need to use the source. Another objective of the invention is to integrate the KNX power supply, KNX IP interface, and Matter bridge unit. Instead of simply being located within the same physical body, they share a common power, data and 5 a structure that enables coordinated operation under a control architecture to place. Another objective of the invention is to convert energy taken from the grid input into power and processed through regulatory structures, both the KNX TP line and the integrated 10 required by the electronic communication and control circuits inside the device The goal is to create a structure that enables the establishment of an electrical power supply. Another objective of the invention is to convert telegrams received over the KNX TP line into the Matter data model. 15 enabling bidirectional data conversion between KNX and Matter systems. The goal is to create a structure that enables the transfer of control. Another purpose of the invention is to connect ETS and compatible IP via KNXnet / IP Tunneling. clients' access to the KNX TP line is simultaneously enabled via KNX-Matter bridging. The goal is to create a structure that performs these functions through the same device. Another objective of the invention is to provide separate power supplies, IP interfaces, and bridging devices. panel space, cabling, terminals, assembly and connection resulting from its use The goal is to create a structure that reduces their requirements. 25 Another aim of the invention is to integrate power electronics with KNX / IP and Matter communication circuits. electrical, thermal and an integrated hardware architecture in which electromagnetic interference can be reduced The goal is to create a structure that provides this. 30 Another aim of the invention is to reduce the number of physical devices and the need for DIN rail space. The goal is to create a structure. 6 Explaining the Figures Figure 1 - General system architecture of the integrated device subject to the invention. Figure 2 - Functional diagram between the KNX power supply, KNX IP interface, and Matter bridge unit. connection diagram 5 Reference Numbers 1. KNX Power Supply 1.1. KNX Line Power Supply Unit 10 1.2. KNX Power Output 1.3. Joint Power Management Unit 2. KNX IP Interface 2.1. KNXnet / IP Tunneling Unit 2.2. Multiple Tunneling Management Unit 15 3. Matter Bridge Unit 3.1. KNX-Matter Mapping Unit 3.2. Matter–KNX Conversion Unit 3.3. Bidirectional Status Synchronization Unit 3.4. KNX Device Representation Unit 20 3.5. Configurable Data Mapping Unit 4. Integrated Device (KMB100) 4.1. KNX TP Common Line Management Unit 4.2. Shared IP Communication Unit 4.3. Electromagnetic Compatibility Installation Unit 25 4.3.1. Power-Communication Separation Zone 4.4. Thermal Management Settlement Unit 4.5. Electrical Insulation Unit 4.6. Simultaneous Communication Management Unit 4.7. Integrated Operational Control Unit 30 4.7.1. Function Coordination Unit Detailed Description of the Invention 7 This detailed explanation aims to provide a better understanding of the innovation in the invention. This is explained with examples that will not create any limiting effect. The invention relates to the technical field of building automation and smart home systems, in particular. KNX-based automation infrastructures together with Matter-based smart home ecosystems 5 It is an integrated building automation device that enables its operation; its feature is that it runs on AC mains power. It receives electrical energy from its input and transmits it through the KNX TP data bus and within the device. KNX converts the DC voltage levels required for the operation of electronic units. Line power supply to the TP bus without the need for an external KNX power unit. The KNX power supply (1) that provides this, the 10 included in the aforementioned KNX power supply (1) The area receives electrical energy from the mains AC input and processes it according to the requirements of the KNX TP bus. KNX line feed unit (1.1) which converts to DC level and transmits it to the KNX TP line, The mentioned KNX power supply (1) contains the AC input from the mains. by processing electrical energy, the KNX TP line and the electronic units within the device creating the different operating voltages required and the relevant 15 of those voltages Common power management unit (1.3) which enables distribution to units, mentioned KNX TP IP-based The KNX IP interface (2), which enables clients to access the KNX TP bus, is mentioned KNX IP interface (2) includes the KNX TP bus and ETS and / or Bidirectional KNXnet / IP tunneling between KNXnet / IP compatible IP clients 20 The KNXnet / IP tunneling unit (2.1) that performs the communication, mentioned KNX TP The Matter communication protocol transmits device, data point, and status information on the data bus. representation in systems using and utilizing the Matter communication protocol By enabling the transfer of control information received from systems to the KNX TP data bus. Matter Bridge 25 performs bidirectional protocol bridging between KNX and Matter. unit (3), KNX TP data located within the aforementioned Matter bridge unit (3). group address, communication object and / or data received from within Telegram The point must have at least one of the KNX data types and value information in the Matter data model. corresponding device, endpoint, cluster and / or attribute Data transformation to the Matter direction by KNX by associating it with the information 30 The KNX–Matter mapping unit (3.1) that performs the aforementioned Matter bridge unit (3) obtained from the system within it that uses the Matter communication protocol. device, endpoint, cluster, attribute and / or command (command) information with the relevant KNX group address, data point and KNX data type. 8 By associating the received control information, it can be transmitted to the KNX TP data bus as a KNX telegram. The Matter–KNX conversion unit (3.2) converts the aforementioned KNX power supply (1), The KNX IP interface (2) and the Matter bridge unit (3) share power within a single device. Integrated device that functionally integrates under data and control architecture (4), 5 by the KNX power supply (1) located within the mentioned integrated device (4). The electrically powered KNX TP bus is also the KNX IP interface (2) and receiving and transmitting KNX telegrams by the Matter bridge unit (3) for the purpose of using it as a common communication infrastructure and thus KNX lines feed, KNX telegram communication, KNXnet / IP access and KNX-Matter data 10 The bridging functions are implemented over the same KNX TP infrastructure. KNX TP common line management unit (4.1), which provides the aforementioned integrated device (4) included in the system, the KNX TP line is powered by the KNX power supply (1). KNXnet / IP tunneling performed via KNX IP interface (2) during bidirectional KNX- communication is carried out via the Matter bridge unit (3). Matter enables the simultaneous and coordinated transfer of data. It is characterized by having an integrated operational control unit (4.7). Figure 1 illustrates the general system architecture of the integrated device that is the subject of the invention. Figure 2 shows the KNX power supply (1), KNX IP interface (2) and Matter bridge unit (3) 20 The functional connection diagram between them is illustrated. The invention utilizes electrical energy received from the AC mains input via a KNX TP data bus and a device. DC voltage levels required for the operation of the electronic components inside converting and enabling 25 KNX TP lines without the need for an external KNX power supply. The KNX power supply (1) that provides the electrical power to the KNX TP bus line power supply required for operation, preferably at approximately 30 V DC. by creating the said feed to the KNX TP line and even to the connected KNX devices. The transferring KNX line supply unit (1.1) preferably supplies 320 mA and / or 640 mA to the KNX TP line. KNX power supply output (1.2) offering supply capacity at mA level, mains 30 By processing the electrical energy received from the input, it can be used as both a KNX TP line and a KNX IP line. interface, Matter bridge unit, control electronics and communication circuits required. the creation and distribution of operating voltages through a common power architecture common power management unit (1.3) providing between KNX TP bus and Ethernet / IP network 9 By establishing bidirectional communication based on KNXnet / IP, it connects to ETS and other compatible IP networks. KNX IP interface (2), which enables clients to access the KNX TP line, KNX TP Telegram messages sent to and from the IP network via KNXnet / IP, and KNX TP messages received from the IP network. KNXnet / IP tunneling unit (2.1) which enables transfer to the line, multiple and preferably the creation of four simultaneous KNXnet / IP tunneling connections, 5 Multi-tunneling management unit (2.2), KNX which enables management and maintenance The device, data point, and status information in the system uses the Matter communication protocol. representation in systems using and control information received by Matter By enabling its transfer to the KNX system, it provides a bidirectional protocol between the two systems. Matter bridge unit (3) performing bridging, telegram 10 received from KNX TP line group address, communication object and / or data point, KNX data type and value within by identifying the information and correspondingly matching that information with the device in the Matter data model. with endpoint, cluster and / or attribute information The associating KNX–Matter mapping unit (3.1), device, end from the Matter ecosystem endpoint, cluster, attribute and / or command 15 Matter associates this information with the relevant KNX group address, data point, and KNX data type. The control information received can be transmitted to the KNX TP line as a KNX telegram. The converting Matter–KNX conversion unit (3.2) converts the KNX TP line. the corresponding device and feature information on the Matter side of the status changes the transfer and control processes carried out by Matter as a result of which KNX 20 by enabling the transmission of current status information from one side back to the Matter side. Bidirectional status ensures that the status information in the two systems is kept consistent. synchronization unit (3.3), relay actuator, dimmer actuator, DALI gateway, HVAC control device, room control unit, thermostat, temperature sensor, motion sensor, Communication objects of KNX devices such as light sensors and / or switches and 25 data points with their corresponding device type and characteristics in the Matter data model. by associating them with the representation of the KNX devices in the Matter system. KNX device representation unit (3.4) which provides hardware in existing KNX devices KNX group address, data point and data type without the need for any changes. 30 pieces of information that can be structured with their counterparts in the Matter data model Configurable data mapping unit (3.5) that enables association, KNX power source (1), KNX IP interface (2) and Matter bridge unit (3) in a single hardware structure functionally integrated within it under a common power, data and control architecture. KNX TP line feed, KNXnet / IP access, and bidirectional KNX–Matter protocol. enabling bridging functions to be performed through the same device The integrated device (4) is electrically supplied by the KNX power supply (1). The TP bus also has a KNX IP interface (2) and a Matter bridge unit (3) joint communication for the purpose of receiving and transmitting KNX telegrams KNX TP common line management unit (4.1), which enables its use as infrastructure, 5 KNXnet / IP communication and Matter communication are both via the same Ethernet / IP connection. Common IP communication unit (4.2) which enables the operation of the power conversion KNX / IP and Matter communication circuits are integrated within the same device. a layout that will reduce electromagnetic interference resulting from its operation electromagnetic compatibility unit (4.3), high current paths 10 and / or switched power conversion zones with KNX / IP and Matter communication By creating a physical separation between sensitive signal regions related to electromagnetics Power-communication separation zone (4.3.1), which reduces interference, KNX power The heat generated as a result of the power conversion processes (1) at the source KNX IP 15 to reduce its impact on the interface (2), Matter bridge unit (3) and control electronics the positioning of power and communication components within the device providing thermal management settlement unit (4.4), grid side, KNX TP side and low by providing the necessary electrical separation between voltage communication electronics, power power supply and communication functions can be safely combined within the same device. The electrical isolation unit (4.5) that enables the operation of multiple KNX devices 20 and / or during the representation of the KNX function as a Matter accessory KNXnet / IP tunneling enables the simultaneous maintenance of connections. real-time communication management unit (4.6), during feeding of the KNX TP line KNXnet / IP tunneling communication enables bidirectional data transfer via KNX–Matter. Integrated work control ensures timely and coordinated execution. 25 unit (4.7), KNX power supply (1), KNX IP interface (2) and Matter bridge KNX TP by managing the working conditions of the unit (3) through a common control architecture line supply, KNXnet / IP access and KNX-Matter protocol bridging functions Function coordination unit (4.7.1) which enables them to work together is one of the main elements. It occurs. 30 The invention enables the use of the Matter communication protocol in KNX-based building automation systems. The electrical interface of the KNX TP bus enables it to work with systems that use it. power supply, IP-based access to the KNX TP bus, and KNX with Matter 11 bidirectional data and control transfer between them within a single device architecture. It is an integrated building automation device for implementation. Invention This includes KNX Power Supply (1), KNX IP Interface (2) and Matter Bridge Unit (3), Functional under common power, data and control architecture within Integrated Device (4) They are assembled together, and thus, in order to operate the KNX TP line, an additional 5 KNX can be controlled from the same device without the need for an external KNX power supply. line supply, KNXnet / IP access, and KNX-Matter protocol bridging operations. is being carried out. The KNX Power Supply (1) included in the invention takes electricity from the AC input of the mains 10 its energy KNX TP bus and the electronics in the Integrated Device (4) converting the DC voltage to the appropriate voltage levels required by the units KNX Power Supply (1) provides only the internal Integrated Device (4) It is not intended for powering electronic circuits, but also for KNX TP data. Line 15 is related to the bus and the operation of KNX devices connected to that bus. It is configured to provide the data feed. Thanks to this structure, KNX TP data an independent system for creating a pathway and even operating connected devices The need for a KNX power supply is eliminated. The KNX Line Supply Unit (1.1), which is part of the KNX Power Supply (1), supplies AC 20V mains power. the electrical energy taken from the input is converted to the DC level required by the KNX TP bus. the function of converting and transferring the said feed to the KNX TP line It performs. In a preferred application, the KNX Line Feeding Unit (1.1), It provides a power supply of approximately 30 V DC for the KNX TP line. (Specified) The voltage value is specific to the preferred application and is subject to the technical specifications of the KNX TP system. Different operating ranges can be applied to meet the requirements. KNX Feed Output (1.2) is generated by the KNX Line Feed Unit (1.1). It enables the transfer of the electrical power supply to the KNX TP bus. Preferred. In applications, the KNX Supply Output (1.2) is at 320 mA and / or 640 mA level KNX 30 It can have line power supply capacity. Thus, sensors, actuators, KNX systems include thermostats, switches, DALI gateways, room control units, and similar devices. The KNX TP line to which the devices are connected is directly through the Integrated Device (4). It can be fed. 12 The Common Power Management Unit (1.3) takes the electrical energy from the grid AC input. voltage levels required by the different functions within the Integrated Device (4) It enables the conversion and distribution of the relevant electronic units. Common Power On the one hand, through the Management Unit (1.3), 5 is required for the operation of the KNX TP data bus. While the necessary line supply is being created, on the other hand, KNX IP Interface (2), Matter Bridge Unit (3) is used for the study required by control electronics and communication circuits. voltages are generated. Thus, the voltage inside the device is supplied via the KNX line power supply. The communication and control electronics are powered within a common power architecture. is being carried out. 10 KNX IP Interface (2), data between KNX TP bus and Ethernet / IP network It enables communication to be carried out via the KNX IP Interface (2). IP-based clients can access the KNX TP bus via the Integrated Device (4). and programming, addressing, and configuring devices in the KNX system, 15 It can be controlled and / or monitored via the KNX TP line. The telegrams received are IP-based communication via the KNX IP Interface (2). KNX communication messages received over the IP network can be transmitted as KNX TP. It can be transmitted to the line. KNXnet / IP Tunneling Unit (2.1), KNX TP bus with ETS, visualization system KNXnet / IP tunneling between and / or other KNXnet / IP compatible IP clients. It carries out communication. KNXnet / IP Tunneling Unit (2.1), KNX TP Telegrams received from the line are transmitted to the IP network in a manner compatible with KNXnet / IP communication. the transmission and reverse of KNXnet / IP Tunneling messages received from the IP network. 25 KNX enables data transmission via the TP bus. Multiple Tunneling Management Unit (2.2), multiple KNXnet / IP Tunneling It ensures the simultaneous creation and maintenance of the connection. In a preferred application, the Multiple Tunneling Management Unit (2.2) consists of four identical 30 It supports real-time KNXnet / IP tunneling connections. Thus, for example, ETS, visualization system and other compatible IP clients within the same time frame Access to the KNX TP line is being made possible. 13 Matter Bridge Unit (3) belongs to the devices and functions within the KNX TP system. the representation of information in systems using the Matter communication protocol and Transferring the control information generated by Matter to the KNX system. Matter Bridge Unit (3) provides different uses on the KNX and Matter sides. by performing bidirectional transformation between data and device representation structures, the existing 5 It enables the KNX infrastructure to work with Matter-compatible systems. The KNX–Matter Mapping Unit (3.1) contains the telegram received from the KNX TP bus. group address, communication object and / or data point, KNX data type and value information. evaluates this information and compares it with its counterparts in the Matter data model. It relates. The aforementioned relation involves the device, endpoint on the Matter side, This is done using cluster and / or attribute information. In this context... On the KNX side, a data point represents a specific physical or logical function. On the Matter side, the device and feature corresponding to that function. They are being matched. 15 For example, the opening and closing information of a relay actuator in a KNX system is Matter. With its corresponding switching feature on the side, the level of a dimmer actuator The information is related to the brightness characteristic on the Matter side, and the measurement value of a temperature sensor. It can be correlated with temperature information on the matter side. Similarly, the movement, 20 Data points for lighting, climate control, and other supported KNX functions. This can be matched with the appropriate counterparts in the Matter data model. Matter–KNX Conversion Unit (3.2), the control information received by Matter is converted to KNX It enables the conversion of telegrams that can be used within the system. Matter 25 Device, endpoint, cluster, attribute and / or command information obtained from the ecosystem. by evaluating the information in question, the corresponding KNX group address, data point, and The KNX data type is determined. Using this information, the Matter command is selected appropriately. It is converted to KNX telegram and that telegram is routed to the KNX TP bus. is transmitted. Thus, a control unit or compatible client on the Matter side 30 It becomes possible to control devices connected to the KNX TP line via this. is being brought. 14 The Bidirectional Status Synchronization Unit (3.3) is the same on both the KNX and Matter sides. keeping status information representing physical or logical function up-to-date It provides this. When a state change occurs on the KNX TP line, the word... The subject of the change is the KNX–Matter Mapping Unit (3.1) in the Matter data model. It is associated with its counterpart and transferred to the Matter side. Similarly, Matter 5 a control operation performed by Matter–KNX Transformation Unit (3.2) After being transferred to the KNX system via this method, the current status information on the KNX side The relevant status information on the Matter side can be updated after reassessment. This provides bidirectional control as well as state consistency between the two systems. is provided. 10 The KNX Device Representation Unit (3.4) represents different types of KNX devices connected to the KNX TP line. Matter data model representation as appropriate devices and features This includes relay actuators, dimmer actuators, DALI gateways, HVAC and air conditioning control devices, room control units, thermostats, temperature 15 various KNX sensors such as motion sensors, light sensors and switches The appropriate device type on the Matter side for communication objects and data points of the devices and can be associated with their features. The types of devices that can be supported are not limited to these. not, but a suitable mapping can be created between the KNX and Matter data models. Different devices and functions can also be represented via the Integrated Device (4). 20 Configurable Data Mapping Unit (3.5) is a hardware component in existing KNX devices. The group address, data point, and on the KNX side are changed without the need for any modifications. associating data type information with its counterparts in the Matter data model It provides. 25 created within the Configurable Data Mapping Unit (3.5). Using mapping information, different KNX installations and different devices can be configured. Data transformation relationships can be defined to suit their configurations. In this way... physical replacement of supported devices in an existing KNX installation monitoring and / or control within the Matter ecosystem without the need for It can be provided. 30 Integrated Device (4), KNX Power Supply (1), KNX IP Interface (2) and Matter Bridge It brings together its unit (3) within a single device architecture. Integrated Device (4) by keeping the said units only in a common enclosure It not only remains but also establishes a shared power, data, and control relationship between the units. Thus, the Integrated Device (4) connects the KNX TP line to its own KNX Power While feeding through source (1), receiving KNX telegrams from the same KNX TP line. and can even send telegrams, access KNXnet / IP via KNX IP Interface (2) providing and KNX–Matter bidirectional data via Matter Bridge Unit (3) 5 It is carrying out its transformation. The KNX TP Common Line Management Unit (4.1) is electrically controlled by the KNX Power Supply (1). The KNX TP bus, which is fed as, is also the KNX IP Interface (2) and Matter It coordinates its use for communication purposes by the Bridge Unit (3). 10 Thanks to this structure, the KNX TP bus, on one side, carries the KNX devices connected to the line. while carrying the necessary electrical power supply for its operation, on the other hand, it also carries the electrical power supply for KNX devices. Telegrams are received by the Integrated Device (4) and telegrams are sent to the KNX TP line. It creates a common infrastructure for sending the line. Thus, the line supply is KNX 15 Telegram communication, KNXnet / IP access, and KNX-Matter data bridging. Their functions are implemented together on the same KNX TP infrastructure. Common IP Communication Unit (4.2) is implemented by KNX IP Interface (2). Matter 20 implemented by Matter Bridge Unit (3) via KNXnet / IP communication communication of the Integrated Device (4) over the common Ethernet / IP connection This ensures that the Integrated Device (4) can be executed over the same IP network. both with ETS and other KNXnet / IP clients, as well as with Matter Controller / Hub and others. Matter can communicate with compatible systems. Electromagnetic Compatibility Installation Unit (4.3), power supply to KNX Power Supply (1) conversion circuits with KNX IP Interface (2), Matter Bridge Unit (3) and other precision communication electronics together in the same Integrated Device (4) to reduce electromagnetic interference that may arise from its operation It refers to the physical location. 30 that may occur during power conversion. the impact of switching effects on KNX, Ethernet / IP and Matter communications power and communication zones are positioned appropriately relative to each other in order to reduce power and communication. It is located. 16 Power-Communication Separation Zone (4.3.1), high current carrying paths and / or Switched power conversion zones and KNX / IP and Matter communication It provides a physical separation between sensitive signal regions. This separation affects power. electromagnetic effects originating from electronics on communication circuits It is designed to reduce transmission. Power-Communication Separation Zone 5 (4.3.1), placement on the circuit board, physical distance, orientation and / or suitability This can be achieved by separating the circuit regions from each other. Thermal Management Installation Unit (4.4), during operation of KNX Power Supply (1) The resulting heat is used by the KNX IP Interface (2), Matter Bridge Unit (3), control electronics and 10 in a way that will reduce the impact of the components on other temperature-sensitive components It ensures the positioning of the Integrated Device (4) inside. Thus, the power thermal load resulting from the transformation of communication and control electronics An integrated device architecture is created by taking working conditions into account together. Electrical Isolation Unit (4.5), Integrated Device (4) on the mains side, KNX 15 The necessary electrical connection between the TP side and the low-voltage communication electronics. It enables the creation of a separation. Through the Electrical Insulation Unit (4.5) Power electronics connected to the AC mains input with KNX TP and IP / Matter communication. circuits that can safely work together within the same device It is supported. Depending on the application, electrical insulation, physical separation, 20 Electronic components that provide adequate clearance and leakage distances and / or isolation. This can be achieved through this means. Simultaneous Communication Management Unit (4.6) for multiple KNX devices and / or KNXnet / IP Tunneling 25 during the representation of the KNX function on the Matter side. It ensures the continuation of the connections. Thus, the Integrated Device (4), KNX– Matter uses KNX to perform data transfer with ETS or other compatible IP clients. It can maintain simultaneous access to the TP line. A preferred option. In practice, the Integrated Device (4) is represented by numerous Matter accessories. Multiple KNXnet / IP tunneling connections can be connected simultaneously within the same time frame (30). It enables management. Integrated Operation Control Unit (4.7), KNX Power Supply (1) of the KNX TP line KNXnet / IP Tunneling communication and KNX- during its power supply. 17 Matter enables the simultaneous and coordinated transfer of bidirectional data. It provides. Integrated Operation Control Unit (4.7), Integrated Device (4) power supply, KNX communication, IP communication and implemented within it protocol bridging functions must be executed in a compatible manner. It coordinates. 5 Function Coordination Unit (4.7.1), KNX Power Supply (1), KNX IP Joint control of the working status of the Interface (2) and the Matter Bridge Unit (3). It manages within its architecture. Function Coordination Unit (4.7.1), KNX TP While the line continues to be electrically powered, data is transmitted over KNXnet / IP 10 coordinating the exchange and execution of KNX-Matter protocol bridging operations by making the said functions work together within the Integrated Device (4) It provides. In the sample working case of the invention, the Integrated Device (4) is connected to the mains AC input, KNX TP 15 It connects to the data bus and the Ethernet / IP network. Power is taken from the mains AC input. electrical energy is transmitted via KNX Power Supply (1) and Common Power Management Unit (1.3) is being processed. KNX line voltage generated by KNX Line Supply Unit (1.1) It is implemented via the KNX Feed Output (1.2) to the KNX TP bus and even The connected KNX devices are powered. At the same time, the 20 within the Integrated Device (4) KNX IP Interface (2), Matter Bridge Unit (3) and the necessary work for control electronics voltages are provided. This applies when a telegram is received from a KNX device on a KNX TP line. Telegram on one side KNX IP Interface (2) and KNXnet / IP Tunneling Unit (2.1) 25 It is possible to transfer it to compatible IP clients via Matter, on the other hand Processing by Bridge Unit (3) to be transferred to the Matter system KNX–Matter Mapping Unit (3.1) is provided within the scope of matter transfer. Telegram specifies the group address, data point, data type, and value information. 30 mapping relationships defined within the Configurable Data Mapping Unit (3.5) According to the corresponding device, endpoint, cluster and / or attribute on the Matter side This information is determined and shared via the Common IP in a manner suitable for Matter communication. It is transmitted to the Matter system via the Communication Unit (4.2). 18 Matter–KNX Conversion when a control command is received from the Matter system in the reverse direction. Unit (3.2) indicates the KNX group address, data point and corresponding to the command in question. It determines the data type and creates the appropriate KNX telegram. Telegram KNX TP Common Line Management Unit (4.1) via KNX TP bus The information is transmitted and the relevant KNX device is checked. After the process, 5 Current status on the KNX side: Bidirectional Status Synchronization Unit (3.3) The relevant device status on the Matter side will be updated after being evaluated by [the relevant authority]. is provided. During this study, the Simultaneous Communication Management Unit (4.6), Matter data 10 Maintaining KNXnet / IP tunneling connections while the transmission is in progress, Integrated Operation Control Unit (4.7) power supply and communication functions Simultaneous execution and Function Coordination Unit (4.7.1) KNX Power The functional relationship between the source (1), KNX IP Interface (2) and Matter Bridge Unit (3). It ensures coordination. 15 As a result, the Integrated Device (4) electrically connects the KNX TP bus. power supply, access to the KNX TP line via KNXnet / IP, and KNX with Matter a shared power to enable bidirectional data, control and status transfer between them, It brings together data and control architecture. Thanks to this integrated structure, 20 a separate KNX power supply, a separate KNX IP interface, and a separate KNX-Matter bridge Number of devices resulting from the use of the device, DIN rail and panel space, Cabling, terminal and connection requirements are reduced; at the same time power power supply, KNX / IP communication, and Matter protocol bridging functions in a single unit. This ensures coordinated execution via the device. 25

Claims

19 REQUESTS 1. The invention relates to the technical field of building automation and smart home systems, especially KNX-based automation infrastructures for Matter-based smart homes Integrated building automation 5 that enables it to work together with ecosystems The device's feature is that it converts the electrical energy it receives from the AC mains input into KNX TP data. DC required for the operation of the path and the electronic units inside the device. by converting voltage levels to an external KNX power supply for the KNX TP bus. KNX power supply (1) which provides line supply without the need for a unit. The mentioned KNX power supply (1) includes 10 AC input from the mains. converting the received electrical energy to the DC level required by the KNX TP bus. KNX line feed unit (1.1) which converts and transfers to the KNX TP line, The mentioned KNX power supply (1) includes the AC input from the mains. processing the received electrical energy and transmitting it through the KNX TP line and inside the device. creating the different operating voltages required by electronic units, and 15 joint force management that enables the distribution of these tensions to the relevant units. unit (1.3) transmits data between the mentioned KNX TP bus and the Ethernet / IP network. by enabling communication, IP-based clients can access the KNX TP bus. KNX IP interface (2) which enables access to the aforementioned KNX IP interface (2) IP 20, which is included within the organization and is compatible with ETS and / or KNXnet / IP via the KNX TP data bus. bidirectional KNXnet / IP tunneling communication between clients The KNXnet / IP tunneling unit (2.1) that performs the mentioned KNX TP data Matter communication of device, data point and status information along the path representation in systems using the protocol and Matter communication Control information received from systems using the protocol is KNX TP data 25 By enabling the transfer of data via the KNX-Matter bidirectional protocol, Matter bridge unit (3) performing bridging, the aforementioned Matter bridge Telegram received from the KNX TP bus within unit (3). group address, communication object and / or data point, KNX data type and within it At least one of the value data points corresponds to the device, endpoint 30 in the Matter data model. endpoint, cluster and / or attribute information By associating them, KNX performs data transformation in the Matter direction. The KNX–Matter mapping unit (3.1) is located within the aforementioned Matter bridge unit (3). The device, located in the system using the Matter communication protocol, is an endpoint. endpoint, cluster, attribute and / or command (command) information with the relevant KNX group address, data point and KNX data type. By associating the received control information, it can be transmitted to the KNX TP data bus. The Matter–KNX conversion unit (3.2) which converts to telegram, the aforementioned KNX power supply (1), KNX IP interface (2) and Matter bridge unit (3) in a single 5 The device functions functionally under a common power, data, and control architecture. integrated device (4), within the aforementioned integrated device (4) KNX TP, located and electrically supplied by the KNX power supply (1). the data bus also has a KNX IP interface (2) and a Matter bridge unit (3) For the purpose of receiving and transmitting KNX telegrams, a common 10 to be used as communication infrastructure and thus KNX line feed, KNX telegram communication, KNXnet / IP access, and KNX–Matter data bridging. enabling the functions to be performed over the same KNX TP infrastructure KNX TP common line management unit (4.1), the aforementioned integrated device (4) 15 by the KNX power supply (1) of the KNX TP line included in it. during feeding is performed via KNX IP interface (2) KNXnet / IP tunneling communication via Matter bridge unit (3) Simultaneous and coordinated bidirectional KNX-Matter data transfer is performed. integrated operational control unit (4.7) which enables its operation It is characterized by its inclusion. 20 2. An integrated building automation device that complies with Claim 1, and whose feature is as mentioned above. The electrical supply generated by the KNX line supply unit (1.1) is supplied by KNX By transferring data to the TP bus, the KNX devices connected to that bus KNX 25 that provides power, preferably at 320 mA and / or 640 mA. It includes a KNX feed output (1.2) with line feed capacity.

3. An integrated building automation device that complies with Claim 1 and whose feature is as follows: Multiple KNXnet / IP Tunneling connections via the KNX IP interface (2) 30 that enable the simultaneous creation, management and maintenance preferably supporting four simultaneous KNXnet / IP Tunneling connections It includes a multi-tunneling management unit (2.2). 21 4. An integrated building automation device that complies with Claim 1, and whose feature is as mentioned above. KNX–Matter mapping unit (3.1) and Matter–KNX conversion unit (3.2) In bidirectional data transfer carried out over the KNX TP bus the resulting state changes are represented in the corresponding data in the Matter data model. 5 that transmit device and / or feature information and are performed by Matter Matter provides the updated status information from the KNX side after the verification process. by transferring the status information represented on the KNX and Matter sides to that side Bidirectional status synchronization unit (3.3) which ensures that it is kept in harmony It includes.

5. An integrated building automation device conforming to Claim 1, featuring KNX TP. bus-connected relay actuator, dimmer actuator, DALI gateway, HVAC control device, room control unit, thermostat, temperature sensor, motion sensors, light sensors and / or KNX devices acting as switches communication objects and / or data points in the Matter data model 15 by associating the relevant KNX with the corresponding device type and features. devices represented in systems using the Matter communication protocol It includes the KNX device representation unit (3.4) which enables it to be used.

6. An integrated building automation device conforming to Claim 1, featuring the following characteristics: KNX TP 20 The KNX devices connected to the data bus can be configured without making any hardware changes. Matter data includes group address, data point, and data type information for the devices in question. The device, endpoint, cluster, and attribute in the model. and / or different KNX mapping relationships between command information. 25 that allow identification and modification according to their installations It includes a configurable data mapping unit (3.5).

7. It is an integrated building automation device that complies with Claim 1 and whose feature is as follows: KNXnet / IP communication is performed by the KNX IP interface (2). Matter 30 performed by the aforementioned Matter bridge unit (3). enables communication to be conducted over the same Ethernet / IP connection. It includes a common IP communication unit (4.2). 22 8. An integrated building automation device that complies with Claim 1 and whose feature is as follows: Power conversion circuits of the KNX power supply (1) and the KNX IP interface (2) and The communication circuits of the Matter bridge unit (3) are in the same integrated device (4) resulting from power conversion during their combined operation 5 that will reduce the effect of electromagnetic interference on communication circuits This allows the circuits to be positioned relative to each other. electromagnetic compatibility includes the settlement unit (4.3).

9. An integrated building automation device that complies with claim 8, and its feature is as mentioned above. electromagnetic compatibility settlement unit (4.3) high current 10 transport pathways and / or switched power conversion zones with KNX / IP and Physical separation between sensitive signal regions related to Matter communication. by creating electromagnetic interference originating from power electronics power-communication separation zone that reduces the transmission of power to communication zones (4.3.1) includes. 15 10. An integrated building automation device that complies with Claim 1 and whose feature is; as mentioned above. The heat generated by the KNX power supply (1) during the power conversion process is KNX IP interface (2), Matter bridge unit (3) and integrated device (4) inside power 20 in a way that will reduce its impact on control and communication electronics the relation between conversion components and communication and control components It includes a thermal management settlement unit (4.4) which enables its positioning.

11. An integrated building automation device conforming to Claim 1, characterized by its integrated nature. Power electronics connected to the AC input of the device (4), KNX TP side and 25 by creating an electrical distinction between low-voltage communication electronics the power and communication functions in question are secure within the same device. electrical insulation unit (4.5) which enables them to work together in this way It includes.

12. It is an integrated building automation device that complies with Claim 1 and whose feature is as follows: Multiple KNX devices and / or KNX via the Matter bridge unit (3) KNX IP interface (2) during the representation of the function on the Matter side Simultaneous KNXnet / IP tunneling connections made over 23 and the continuation of the aforementioned communication processes together Simultaneous communication management unit (4.6) that enables its management It includes.

13. An integrated building automation device that complies with Claim 1 and whose feature is; mentioned in 5 KNX power supply (1), KNX IP interface (2) and Matter bridge unit (3) Managing operating conditions through a common control architecture KNX TP line power supply, KNXnet / IP access, and bidirectional KNX–Matter protocol bridging. a function that enables its functions to be performed together and in a coordinated manner It includes a coordination unit (4.7.1). 10

Images