EP4639861A1 - Wlan-fähiges endgerät, wlan-fähige basisstation und kommunikationssystem umfassend eine wlan-fähige basisstation und mehrere wlan-fähige endgeräte - Google Patents
Wlan-fähiges endgerät, wlan-fähige basisstation und kommunikationssystem umfassend eine wlan-fähige basisstation und mehrere wlan-fähige endgeräteInfo
- Publication number
- EP4639861A1 EP4639861A1 EP23833132.6A EP23833132A EP4639861A1 EP 4639861 A1 EP4639861 A1 EP 4639861A1 EP 23833132 A EP23833132 A EP 23833132A EP 4639861 A1 EP4639861 A1 EP 4639861A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- wlan
- ethernet
- data frame
- vxlan
- enabled
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/4026—Bus for use in automation systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- WLAN-enabled terminal comprising a WLAN-enabled base station and several WLAN-enabled terminals
- the present invention relates to a WLAN-enabled terminal and a WLAN base station, each of which is designed for use in a wireless local area network (WLAN).
- the present invention further relates to a communication system which in particular comprises such a WLAN-enabled base station, several such WLAN-enabled terminals and several Ethernet-enabled terminals.
- a wireless local area network is a local radio network that implements a standard from the IEEE 802.11 family.
- Such a WLAN has several wireless stations and a central base station, which is referred to as an access point according to the IEEE 802.11 standard.
- the 802.11 WLAN architecture is well known to those skilled in the art.
- wired local networks also called wired LAN (Local Area Network) for short, are known according to an Ethernet standard of the IEEE 802.3 family, via which Ethernet-capable end devices, such as PCs, can communicate.
- Ethernet-capable end devices such as PCs
- the present invention is based on the object of providing a WLAN-capable terminal, a WLAN-capable base station and a communication system which enable layer-2 transparent communication between Ethernet-capable terminals which are not connected to a common wired Ethernet-based local network, by integrating a WLAN network.
- a core idea of the invention can be seen in the storage of a software module in each of the network participants of a WLAN, which are preferably several WLAN-capable terminal devices and a WLAN-capable base station, known as an access point for short.
- This software module implements the virtual extensible LAN protocol, also known as Virtual Extensible LAN (VXLAN protocol).
- VXLAN protocol Virtual Extensible LAN
- the software module implements a VXLAN tunnel endpoint, known as VTEP for short.
- VXLAN was defined as a standard by the Internet Engineering Task Force (IETF) in RFC (Request For Comments) 7348.
- the International Assigned Numbers Authority (IANA) has assigned UDP port 4789 to a VTEP.
- each of these WLAN-capable terminal devices has an Ethernet-based interface to which at least one Ethernet-capable terminal device can be connected.
- a further core idea of the invention can be seen in the fact that both the WLAN-enabled base station and each of the WLAN-enabled terminal devices in which a software module is stored that implements the VXLAN protocol each have only a single IP address that is assigned to the WLAN interface of the WLAN-enabled base station and the respective WLAN-enabled terminal device.
- a WLAN-enabled terminal device which can have the following features:
- control device which may be, for example, a microcontroller or microprocessor
- Ethernet-based interface designed for Ethernet-based communication with an Ethernet-capable terminal device, which is assigned a unique MAC address
- Ethernet-based interface and the wireless a unique MAC address can preferably be assigned to each interface, with only one IP address being assigned to the WLAN-enabled terminal, with the control device being designed to cause the WLAN-enabled terminal to execute the stored software, a1) to check whether an Ethernet data frame arriving at the Ethernet-based interface is intended for the WLAN-enabled terminal, a2) if not, to pass the Ethernet data frame to the VXLAN tunnel endpoint, with the VXLAN tunnel endpoint being designed to encapsulate the passed Ethernet data frame in a VXLAN packet, and a3) to pass the VXLAN packet generated by the VXLAN tunnel endpoint to the wireless interface for transmission in a WLAN data frame, and/or bl) to pass a VXLAN packet received via the wireless interface in a WLAN data frame, in which an Ethernet data frame is encapsulated, to the VXLAN tunnel endpoint
- the control device can be designed to first check in step a2) based on the destination MAC address contained in the Ethernet data frame whether the Ethernet data frame is to be sent from the WLAN-enabled terminal via the wireless interface. To do this, the control device can, for example, look in a configuration file stored in the WLAN-enabled terminal, which contains the corresponding information for handling a received Ethernet data frame with a specific destination MAC address.
- the control device can cause the WLAN-enabled terminal to add header information to the VXLAN packet in step a2), which contains source address information that addresses the WLAN-enabled terminal or its VXLAN tunnel endpoint, and destination address information which addresses a predetermined VXLAN tunnel endpoint implemented in another WLAN-enabled terminal or a WLAN-enabled base station as the destination.
- the header information of the VXLAN packet depends, for example, on the header information of the Ethernet data frame, which contains, for example, the MAC address of the WLAN-enabled terminal or the MAC address of an Ethernet-enabled terminal that can be reached via another WLAN-enabled terminal as the destination MAC address.
- steps a1) to a3) it is possible, for example, to send an Ethernet data frame arriving at the Ethernet-based interface, which originates from an Ethernet-capable terminal device that can be connected to the Ethernet-based interface, to another Ethernet-capable terminal device, which is connected to another WLAN-capable terminal device in which a VXLAN tunnel endpoint is implemented, using a WLAN network.
- This enables Ethernet-capable terminal devices that are not connected via a common wired local network to communicate with each other.
- steps bl) and b2) it is possible to transmit an Ethernet data frame intended for a first Ethernet-capable terminal that can be connected to the Ethernet-based interface of the WLAN-capable terminal, involving a WLAN network, to the first Ethernet-capable terminal, even though the first Ethernet-capable terminal contains a different MAC address than the wireless interface of the WLAN-capable terminal.
- Such an Ethernet data frame preferably originates from another Ethernet-capable terminal that is not connected to the first Ethernet-capable terminal via a wired LAN.
- a WLAN data frame is in particular a standardized data frame according to an IEEE 802.11 standard, while an Ethernet data frame is in particular a standardized data frame according to an IEEE 802.3 standard.
- a WLAN data frame according to an IEEE 802.11 standard has three address fields, namely a Field for a source MAC address, a field for a destination MAC address and a field for the MAC address of an intermediate station.
- the control device of the WLAN-enabled terminal can also be designed to
- the control device of the WLAN-enabled terminal can further be designed to cause the WLAN-enabled terminal, when executing the software, to check whether an IP packet or Address Resolution Protocol packet contained in a received Ethernet data frame is intended for the WLAN-enabled terminal and, if so, to cause the WLAN-enabled terminal to process the IP packet or the Address Resolution Protocol packet or, if not, to cause the WLAN-enabled terminal to pass the Ethernet data frame to the Ethernet-based interface or the Ethernet data frame to the VXLAN tunnel endpoint, which encapsulates the Ethernet data frame in a VXLAN packet, and then to pass the VXLAN packet to the wireless interface for transmission in a WLAN data frame.
- a WLAN data frame is a data frame according to an IEEE 802.11 standard and an Ethernet data frame is a data frame according to an IEEE 802.3 standard.
- a WLAN-enabled base station is intended for use in a WLAN network, whereby the WLAN-enabled base station can have the following features in particular:
- a wireless interface designed for wireless communication according to a WLAN standard, wherein the wireless interface is assigned a unique MAC address, wherein the WLAN-enabled base station is assigned only one IP address, and wherein the control device is designed to cause the WLAN-enabled base station, by executing the stored software, to i) check whether a WLAN data frame received via the wireless interface contains a VXLAN packet intended for the base station, wherein the VXLAN packet contains an Ethernet data frame, and ii) if so, to extract the Ethernet data frame from the VXLAN packet.
- the WLAN-enabled base station further comprises an Ethernet-based interface which is designed for Ethernet-based communication with an Ethernet-enabled terminal, wherein the control device is designed to cause the WLAN-enabled base station, by executing the stored software, to further check whether the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface or the wireless interface and, if the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface, to pass the extracted Ethernet data frame to the Ethernet-based interface for forwarding, or, if the extracted Ethernet data frame is to be forwarded via the wireless interface, to convert the extracted Ethernet data frame into a WLAN data frame and pass the WLAN data frame to the wireless interface for transmission.
- the control device is designed to cause the WLAN-enabled base station, by executing the stored software, to further check whether the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface or the wireless interface and, if the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface, to pass the extracted Ethernet data frame to the Ethernet-based interface for forwarding, or,
- control device of the WLAN-enabled base station can be designed to cause the WLAN-enabled base station, by executing the stored software, to convert an Ethernet data frame received via the Ethernet-based interface into a VXLAN packet and send the VXLAN packet in a WLAN data frame over the wireless interface.
- control device of the WLAN-enabled base station can be designed to cause the WLAN-enabled base station, by executing the stored software, to i) first check whether an Ethernet data frame received via the Ethernet-based interface is to be encapsulated in a VXLAN packet, ii) if so, to pass the Ethernet data frame to the VXLAN tunnel endpoint, wherein the VXLAN tunnel endpoint is designed to encapsulate the passed Ethernet data frame in a VXLAN packet, and iii) to pass the VXLAN packet generated by the VXLAN tunnel endpoint to the wireless interface for transmission in a WLAN data frame.
- the software stored in the storage device may, for example, implement a first software bridge and a second software bridge, wherein the first software bridge is configured to pass a VXLAN packet received via the wireless interface and intended for the WLAN-capable base station to the VXLAN tunnel endpoint via at least one virtual Ethernet interface and the second software bridge, and to pass an Ethernet data frame extracted by the VXLAN tunnel endpoint from a VXLAN packet to the Ethernet-based interface or the wireless interface.
- the first software bridge is configured to pass a VXLAN packet received via the wireless interface and intended for the WLAN-capable base station to the VXLAN tunnel endpoint via at least one virtual Ethernet interface and the second software bridge, and to pass an Ethernet data frame extracted by the VXLAN tunnel endpoint from a VXLAN packet to the Ethernet-based interface or the wireless interface.
- a communication system which includes a WLAN network and a wired Ethernet-based system.
- the wired Ethernet-based system has in particular at least a first, second and third Ethernet-capable terminal, each with an Ethernet-based interface, wherein each of the Ethernet-capable terminals is assigned a unique MAC address.
- the WLAN network has at least a first and a second WLAN-enabled device, which is described above, and the WLAN-enabled base station described above. The first Ethernet-enabled device is connected to the first WLAN-enabled device and the second Ethernet-enabled device is connected to the second WLAN-enabled device.
- the communication system can have at least one WLAN-capable terminal in which no VXLAN functionality, i.e. in particular no VXLAN tunnel endpoint, is implemented.
- the communication system is designed to control communication between the first and second Ethernet-capable terminal devices, which are connected to the first and second WLAN-capable terminal devices, respectively.
- the communication system can be designed to control communication between the first, second and third Ethernet-capable terminal devices, which are each connected to the first and second WLAN-capable terminal devices and to the WLAN-capable base station, and the at least one WLAN-capable terminal device without VXLAN functionality.
- the first Ethernet-capable terminal can be designed to generate an Ethernet data frame intended for the second Ethernet-capable terminal and to transmit the Ethernet data frame to the Ethernet-based interface of the first WLAN-capable terminal, wherein the Ethernet data frame contains the MAC address of the second Ethernet-capable terminal as the target MAC address, wherein the control device of the first WLAN-capable terminal can be designed to cause the WLAN-capable terminal to transfer the Ethernet data frame to the VXLAN tunnel endpoint by executing the stored software, wherein the VXLAN tunnel endpoint is designed to encapsulate the transferred Ethernet data frame in a VXLAN packet which contains header information which addresses the VXLAN tunnel endpoint implemented in the second WLAN-enabled terminal, and to transfer the VXLAN packet generated by the VXLAN tunnel endpoint to the wireless interface for transmission in a first WLAN data frame, wherein the first WLAN data frame contains the address of the WLAN-enabled terminal and the address of the WLAN-enabled base station, wherein the control device of the WLAN-enabled base station is designed to
- the first and/or second Ethernet-capable terminal can be designed to generate an Ethernet data frame that is intended for the third Ethernet-capable terminal and to transmit the Ethernet data frame to the corresponding Ethernet-based interface of the first or second WLAN-capable terminal, wherein the Ethernet data frame contains the MAC address of the third Ethernet-capable terminal as the target MAC address, wherein the control device of the first or second WLAN-capable terminal is designed to is designed to cause the first or second WLAN-enabled terminal to transfer the Ethernet data frame to the VXLAN tunnel endpoint when the stored software is executed, the VXLAN tunnel endpoint being designed to encapsulate the transferred Ethernet data frame in a VXLAN packet which contains header information which addresses the VXLAN tunnel endpoint implemented in the WLAN-enabled base station, and to transfer the VXLAN packet generated by the VXLAN tunnel endpoint to the respective wireless interface for transmission in a WLAN data frame, the WLAN data frame containing the address of the WLAN-enabled base station, the control device of the WLAN-enabled base station being designed
- a MAC (Media Access Control) address is a hardware or device address.
- a unique MAC address is stored in the wireless interface of each of the WLAN-enabled terminal devices, in the wireless interface of the WLAN-enabled base station, in the Ethernet-based interface of each of the Ethernet-enabled terminal devices and, if present, in the Ethernet-based interface of the WLAN-enabled base station and at least one of the WLAN-enabled terminal devices.
- Figure 1 is a schematic block diagram of an exemplary WLAN-enabled terminal
- FIG. 2 is a schematic block diagram of an exemplary WLAN-enabled base station
- FIG 3 shows an exemplary communication system with two WLAN-enabled terminals according to Figure 1 and the WLAN-enabled base station shown in Figure 2,
- Figure 4 shows an example format of an Ethernet data frame and Figure 5 shows the format of an example VXLAN packet.
- FIG. 1 shows the schematic block diagram of an exemplary WLAN-enabled terminal 10, which can be a network participant of a WLAN 100 (Wireless Local Area Network).
- the WLAN-enabled terminal 10 has an Ethernet-based interface 11, preferably in accordance with an IEEE 802.3 standard.
- the Ethernet-based interface 11 can be a hardware and/or software component.
- the Ethernet-based interface 11 can be designed as a network adapter that has an Ethernet port to which, for example, a line or a bus can be connected.
- the Ethernet port of the Ethernet-based interface 11 can be an RJ-45 port to which, for example, an 8-wire Ethernet line can be connected.
- the WLAN-enabled terminal 10 can communicate with at least one Ethernet-enabled terminal, for example the Ethernet-enabled terminal 40 shown in Figure 4, via the Ethernet-based interface 11.
- the Ethernet-based interface 11 can be assigned a unique MAC address in a manner known per se, but this is not required.
- the WLAN-enabled terminal 10 has a wireless interface 13, which can preferably be implemented as a WLAN interface according to a standard of the IEEE 802.11 family.
- the WLAN interface 13 can also be designed as a network adapter. It should be noted that the WLAN-enabled terminal 10 has only a single IP address, which is assigned to the WLAN interface 13.
- the WLAN interface 13 is also assigned a unique MAC address.
- the WLAN interface 13 is preferably implemented as a hardware and/or software component. which preferably implements layer 1 and layer 2 of the ISO/OSI reference model. It can be designed as a network adapter in a manner known per se.
- the WLAN-capable terminal device 10 also has a control device 14 and a storage device 15 in which software that can be executed by the control device 14 is stored.
- the software contains, among other things, a software module or a program that implements a VXLAN tunnel endpoint.
- VXLAN stands for Virtual Extensible LAN, which is defined as a standard by the IETF in RFC 7348.
- the control device 14 and the storage device 15 can be components of a microcontroller 12, as shown by way of example in Figures 1 and 3. In this case, the control device 14 can be designed as a microprocessor.
- the control device 14 and the storage device 15 can also be designed as separate, electrically connected components, in which case the control device 14 could also be designed as a microcontroller.
- the storage device 15 can also be arranged separately from the control device 12 and electrically connected to it.
- the software stored in the storage device 15 can contain further software modules and/or programs, such as a software module that implements a first software bridge, a further software module that implements a second software bridge, a software module that implements an IP stack or IP protocols, and a further software module that implements the Address Resolution Protocol (ARP protocol).
- ARP protocol Address Resolution Protocol
- a firmware or an operating system can be stored in the storage device 15, which monitors and controls the WLAN-enabled terminal 10 when executed by the microprocessor 14.
- the Linux operating system can be stored as the operating system, whereby in this example the respective software modules or programs can be Linux-based components of the operating system.
- Communication rules can be stored in the storage device 15 of the WLAN-enabled terminal 10, which, for example, enable data frames received via the Ethernet-based interface 11 or via the WLAN interface 13 to directly reach the IP protocols of the WLAN-enabled terminal 10.
- the Ethernet-based interface 11 is designed to receive Ethernet data frames, in particular according to an 802.3 standard, for example from the Ethernet-capable terminal device 40 and to transfer them to the control device 14 or the microcontroller 12 for further processing or handling, or to receive data from the control device 14 for transmission to the Ethernet-capable terminal device 40.
- the WLAN interface 13 can be designed to receive and transmit WLAN data frames, in particular according to an 802.11 standard. Furthermore, the WLAN interface 13 is designed to supply a received WLAN data frame to the microcontroller 12 for processing and/or handling and to receive data that are to be transmitted via the WLAN interface from the microcontroller 12. It should be noted that the WLAN data frames used here preferably contain a header with three MAC addresses.
- the control device 14 is advantageously designed to cause the WLAN-enabled terminal 10, by executing the software stored in the storage device 15, to a) check whether an Ethernet data frame arriving at the Ethernet-based interface 11, which comes for example from the Ethernet-enabled terminal 40, is intended for the WLAN-enabled terminal 10, a2) if not, to pass the Ethernet data frame to the VXLAN tunnel endpoint 16, wherein the VXLAN tunnel endpoint 16 is designed to encapsulate the passed Ethernet data frame in a VXLAN packet, and a3) to pass the VXLAN packet generated by the VXLAN tunnel endpoint to the wireless interface 13 for transmission in a WLAN data frame, and/or bl) to pass a VXLAN packet received via the wireless interface 13 in a WLAN data frame, in which an Ethernet data frame is encapsulated, to the VXLAN tunnel endpoint 16, wherein the VXLAN tunnel endpoint is designed to extract the Ethernet data frame encapsulated in the received VXLAN packet, and b2) to forward the extracted Ethemet data frame via the Ethemet
- the Ethernet data frame after step a1) contains as header information a destination address, i.e. a destination MAC address for which the Ethernet data frame is intended.
- the destination MAC address can be, for example, a broadcast, a multicast or a unicast address.
- a unicast MAC address can, for example, be assigned to another Ethernet-capable terminal, for example the Ethernet-capable terminal 50 or 70 shown in Figure 3, or to another WLAN-capable terminal, for example the WLAN-capable terminal 10, 30 or 60 shown in Figure 3, or to a WLAN-capable base station, for example the WLAN base station 20 shown in Figure 3.
- control device 14 can be designed to first check in step a2) based on the destination MAC address contained in the Ethernet data frame whether the Ethernet data frame should be sent from the WLAN-capable terminal 10 via the wireless interface 13.
- control device 14 can, for example, look in a configuration file stored in the WLAN-enabled terminal 10, which contains the corresponding information for handling a received Ethernet data frame with a specific destination MAC address.
- the control device 14 can cause the WLAN-enabled terminal 10 to add header information to the VXLAN packet, which contains source address information that addresses the WLAN-enabled terminal 10 or its VXLAN tunnel endpoint, and destination address information that addresses a predetermined VXLAN tunnel endpoint that is implemented in another WLAN-enabled terminal, for example the WLAN-enabled terminal 30 or a WLAN-enabled base station, for example the WLAN-enabled base station 20, as the destination.
- the header information of the VXLAN packet depends, for example, on the header information of the Ethernet data frame, which, for example, as the destination MAC address, can be the MAC address of the WLAN-enabled terminal device 30 or the MAC address of an Ethernet-enabled terminal device, for example the Ethernet-enabled terminal device 50. which can be reached via another WLAN-enabled terminal, for example the WLAN-enabled terminal 30.
- control device 14 can be designed in particular to recognize in step a1) based on the destination MAC address contained in a received Ethernet data frame whether the Ethernet data frame arriving at the Ethernet-based interface 11 is intended for the WLAN-enabled terminal 10 or not.
- the control device 14 is preferably further designed to insert header information into the VXLAN packet in step a2) depending on the destination MAC address contained in a received Ethernet data frame, which header information addresses the VXLAN tunnel endpoint implemented in another WLAN-enabled terminal, for example the WLAN-enabled terminal 30 shown in Figure 3.
- Figure 4 shows a known example format of an Ethernet data frame.
- the Ethernet data frame shown as an example preferably has four fields which, read from left to right, contain a field for a destination MAC address, a field for a source MAC address, a field for data to be transmitted and a field for a check value which is formed from the data to be transmitted.
- the abbreviation CRC stands for Cyclic Redundancy Check.
- the data field can contain an IP packet, for example.
- FIG. 5 A well-known example format of a VXLAN packet is shown in Figure 5.
- the fields read from left to right contain:
- VXLAN header which may contain a VXLAN identification VNI that can be specified during configuration
- This field preferably contains an Ethernet data frame as shown in Figure 4.
- the WLAN-enabled terminal 10 or the WLAN interface 13 is designed to convert a VXLAN packet received from the control device 14 or the microcontroller 12 into a WLAN data frame, which is then sent via the WLAN interface 13.
- a WLAN data frame contains, in addition to the source MAC address of the WLAN-enabled terminal 10, a destination MAC address, which is assigned to a WLAN-enabled base station, for example the one shown in Figure 2.
- the WLAN interface 13 is designed to receive a WLAN data frame received externally and to pass a VXLAN packet contained therein to the microcontroller 12 for further processing.
- a WLAN data frame differs from an Ethernet data frame only in the design of the header.
- a software bridge for example the two software bridges stored in the storage device 15 as software modules, preferably extends a physical interface by a virtual interface and connects these interfaces like a bridge.
- the second software bridge is designed to connect the VXLAN tunnel endpoint 16, which is also a software module, to the WLAN interface 13, wherein the first software bridge is designed to transfer an Ethernet data frame arriving at the Ethernet-based interface 11 to the VXLAN tunnel endpoint 16 and to transfer an Ethernet data frame extracted by the VXLAN tunnel endpoint 16 from a VXLAN packet to the Ethernet-based interface 11.
- the second software bridge is designed to pass a VXLAN packet received via the wireless interface 13 in a WLAN data frame to the VXLAN tunnel endpoint 16 and to pass a VXLAN packet generated by the VXLAN tunnel endpoint 16 to the wireless interface 13 for transmission in a WLAN data frame.
- the order in which the two software bridges and the VXLAN tunnel endpoint are executed by the control device 14 is symbolically represented by their arrangement in the storage device 15 shown in Figure 1.
- the WLAN-capable terminal 10 is preferably designed to exchange WLAN data frames with a WLAN-capable base station, which can also be referred to as an access point, via the WLAN interface 13.
- An example WLAN-capable base station 20 is shown in Figure 2 and is explained in more detail below.
- an Address Resolution Protocol packet for implementing the ARP mechanism or data to be transmitted can be transmitted in an IP packet.
- the control device 14 can be designed to cause the WLAN-enabled terminal 10, by executing the software stored in the storage device 15, to check whether an IP packet or Address Resolution Protocol packet contained in a received Ethernet data frame is intended for the WLAN-enabled terminal 10. If so, the control device 14 causes the WLAN-enabled terminal 10 to process the IP packet or the Address Resolution Protocol packet. If not, the control device 14 causes the WLAN-enabled terminal 10 to pass the Ethernet data frame to the Ethernet-based interface 11 or the Ethernet data frame to the VXL AN tunnel endpoint 16, which encapsulates the Ethernet data frame in a VXLAN packet, and then to pass the VXLAN packet to the wireless interface 13 for transmission in a WLAN data frame.
- FIG 2 shows an exemplary WLAN-capable base station 20, hereinafter referred to as access point.
- the access point 20 like the WLAN-capable terminal device 10 shown in Figure 1, is intended in particular for use in the WLAN network 100.
- the access point 20 has a control device 24 and a memory device 25, which can be components of a microcontroller 22, as shown by way of example in Figures 2 and 3.
- the control device 24 can be designed, for example, as Microprocessor. It is also conceivable that the control device 24 and the memory device 25 are designed as separate, electrically connected components. In this case, the control device 24 can also be designed as a microcontroller.
- Software that can be executed by the control device 24 and contains a software module or a program that implements a VXLAN tunnel endpoint 26 is stored in the memory device 25.
- the abbreviation VXLAN stands for Virtual Extensible LAN, which is defined as a standard by the IETF in RFC 7348.
- the software stored in the memory device 25 can contain a further software module that implements a first software bridge, a software module that implements a second software bridge, a third software module that implements at least one virtual Ethernet interface, a software module that implements the ARP protocol, and a further software module that implements IP protocols, ie an IP stack.
- a firmware or an operating system which is for example the Linux operating system, can be stored in the storage device 25.
- the previously mentioned software modules can be components of the operating system.
- rules are preferably stored in the storage device 25, which are called Ebtables rules when using a Linux operating system. These rules specify, for example, permissible communication paths within the access point 20. These rules are intended in particular to prevent communication loops from occurring in the access point 20.
- the access point 20 has a wireless interface 23, which can preferably be implemented as a WLAN interface according to a standard of the IEEE 802.11 family. It should be noted that the access point 20 has only a single IP address, which is assigned to the WLAN interface 23.
- the WLAN interface 23 is also assigned a unique MAC address.
- the WLAN interface 23 is preferably designed as a hardware and software component, which preferably implements layer 1 and layer 2 of the ISO/OSI reference model. It can be designed as a network adapter in a manner known per se.
- the WLAN-capable base station 20 can optionally have an Ethernet-based interface 21, preferably in accordance with an IEEE 802.3 standard.
- the Ethernet-based interface 21 can be a hardware and/or software component that preferably implements the Ethernet-based layer 1 and layer 2 of the ISO/OSI reference model.
- the Ethernet-based interface 21 can be designed as a network adapter that has an Ethernet port to which a line or a bus can be connected.
- the Ethernet port of the Ethernet-based interface 21 can be an RJ-45 port to which, for example, an 8-wire Ethernet line can be connected.
- the access point 20 can communicate with at least one Ethernet-capable terminal, for example the Ethernet-capable terminal 70 shown in Figure 4, via the Ethernet-based interface 21.
- the Ethernet-based interface 21 can be assigned a unique MAC address in a manner known per se.
- the Ethernet-based interface 21 is designed to receive Ethernet data frames, in particular according to an 802.3 standard, for example from the Ethernet-capable terminal 70 and to pass them on to the microcontroller 22 or the control device 24 for further handling and/or processing, or to receive data from the microcontroller 22 or the control device 24 that are to be transmitted in an Ethernet data frame to the Ethernet-capable terminal 70.
- an Ethernet data frame that is generated by an Ethernet-capable terminal for example the Ethernet-capable terminal 70, for example an Address Resolution Protocol packet for implementing the ARP mechanism or data to be transmitted can be transmitted in an IP packet.
- the WLAN interface 23 can be designed to receive and transmit WLAN data frames, in particular according to an 802.11 standard. It should be noted that the WLAN data frames mentioned here preferably contain a header with three MAC addresses each. Furthermore, the WLAN interface 23 is designed to supply a received WLAN data frame to the microcontroller 22 or the control device 24 for processing and/or handling and to transmit data that is received via the WLAN interface 23, from the microcontroller 22 or from the control device 24.
- the access point 20 is preferably designed to exchange WLAN data frames, each containing a VXLAN packet, with a WLAN-enabled terminal device, for example the WLAN-enabled terminal devices 10, 30 shown in Figure 3, in each of which a VXLAN tunnel endpoint is implemented, via the WLAN interface 23.
- a WLAN-enabled terminal device for example the WLAN-enabled terminal devices 10, 30 shown in Figure 3, in each of which a VXLAN tunnel endpoint is implemented, via the WLAN interface 23.
- the control device 24 of the access point 20 is preferably designed to cause the WLAN-capable base station 20, i.e. the access point, to execute the software stored in the storage device 25, i) check whether a WLAN data frame received via the wireless interface 23 contains a VXLAN packet that is intended for the WLAN-capable base station 20, the VXLAN packet containing an Ethernet data frame, and ii) if so, to extract the Ethernet data frame from the VXLAN packet.
- the check in step i) is advantageously carried out using the header information contained in the WLAN data frame. If the header information contains, for example, the MAC address of the base station 20 as the destination address, the control device 24 recognizes that the base station 20 or the VXLAN tunnel endpoint implemented in the base station is the destination point of the VXLAN packet. However, if the header information contains, for example, the MAC address of the WLAN-capable terminal 10 or 30 as the destination address, the VXLAN packet is not unpacked, but forwarded in a WLAN data frame to the WLAN-capable terminal 10 or 10.
- the VXLAN packet after step i) can contain header information that addresses a predetermined VXLAN tunnel endpoint implemented in a WLAN-enabled terminal, for example in the WLAN-enabled terminal 10 and/or 30, as a destination.
- the header information of the VXLAN packet depends, for example, on the header information of the Ethernet data frame intended for an Ethernet-capable terminal, for example the Ethernet-capable terminal 40 or 50, as the destination terminal.
- the control device 24 can also be designed to cause the WLAN-capable base station 20 to execute the stored software, to further check whether the Ethernet data frame extracted in step ii) is to be forwarded via the Ethernet-based interface 21 or the wireless interface 23, and, if the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface 21, to pass the extracted Ethernet data frame to the Ethernet-based interface 21 for forwarding, or, if the extracted Ethernet data frame is to be forwarded via the wireless interface 23, to convert the extracted Ethernet data frame into a WLAN data frame and to pass the WLAN data frame to the wireless interface 23 for transmission.
- the decision as to whether the extracted Ethernet data frame is to be forwarded via the Ethernet-based interface 21 or the wireless interface 23 is made by the control device 24 depending on the destination MAC address contained in the extracted Ethernet data frame. This means that the extracted Ethernet data frame is forwarded via the Ethernet-based interface 21 if the Ethernet data frame is addressed to the Ethernet-capable terminal 70, or that the extracted Ethernet data frame is converted and forwarded as a WLAN data frame via the WLAN interface 23 if the Ethernet data frame is addressed to the WLAN-capable terminal 60.
- control device 24 can be designed to cause the WLAN-capable base station 20, by executing the stored software, to convert an Ethernet data frame received via the Ethernet-based interface 21 into encapsulate a VXLAN packet and transmit the VXLAN packet in a WLAN data frame over the wireless interface 23.
- control device 24 can, for example, be designed to cause the WLAN-capable base station 20, by executing the stored software, to i) first check whether an Ethernet data frame received via the Ethernet-based interface 21 is to be encapsulated in a VXLAN packet, ii) if so, to transfer the Ethernet data frame to the VXLAN tunnel endpoint, wherein the VXLAN tunnel endpoint is designed to encapsulate the transferred Ethernet data frame in a VXLAN packet, and iii) to transfer the VXLAN packet generated by the VXLAN tunnel endpoint to the wireless interface 23 for transmission in a WLAN data frame.
- control device 24 can be designed to first check in step i) based on the destination MAC address contained in the Ethernet data frame whether the Ethernet data frame is to be encapsulated in a VXLAN packet and transmitted via the wireless interface 23. To do this, the control device 24 can, for example, look in a configuration file or configuration table stored in the base station 20, which contains the corresponding information for handling a received Ethernet data frame with a specific destination MAC address.
- the control device 24 can cause the base station 20 to add header information to the VXLAN packet in step ii), which contains source address information that addresses the base station 20 or its VXLAN tunnel endpoint, and destination address information that addresses a predetermined VXLAN tunnel endpoint that is implemented in another WLAN-enabled terminal, for example the WLAN-enabled terminal 10 or 20, as the destination.
- the header information of the VXLAN packet depends, for example, on the header information of the Ethernet data frame, which can be, for example, the MAC address of the WLAN-enabled device 10 or 30 or the MAC address of the WLAN-enabled device 10 or 30 as the destination MAC address. Address of an Ethernet-capable device that can be reached via the other WLAN-capable device, for example, the WLAN-capable device 10 or 30.
- the first software bridge stored in the storage device 25 is preferably designed to decide whether a VXLAN packet received via the WLAN interface 23 is to be passed to the WLAN interface 23 for forwarding in a WLAN data frame or to the VXLAN tunnel endpoint 26 for decapsulating the VXLAN packet, wherein the Ethernet data frame extracted from the VXLAN packet by the VXLAN tunnel endpoint 26 is then passed via the second software bridge and the at least one virtual Ethernet interface of the Ethernet-based interface 21.
- the second software bridge stored in the storage device 25 is preferably designed to pass a received Ethernet data frame to the VXLAN tunnel endpoint 26, which encapsulates the Ethernet data frame in a VXLAN packet, and passes the VXLAN packet to the WLAN interface 23 for forwarding in a WLAN data frame.
- the order in which the two software bridges, the at least one virtual Ethernet interface and the VXLAN tunnel endpoint are executed by the control device 24 is symbolically represented by their arrangement in the memory device 25 shown in Figure 2.
- FIG 3 shows an exemplary communication system 1, which can be installed, for example, on a factory site comprising several buildings or halls.
- the communication system 1 can be used, for example, in an industrial automation environment.
- the exemplary communication system 1 preferably comprises a wired Ethernet-based system 90 and a wireless WLAN network 100.
- the wired Ethernet-based system 90 can comprise several Ethernet-capable terminal devices 40, 50, 70 that are not connected to one another via a common wired Ethernet-based network. For the sake of clarity, only the three Ethernet-capable terminal devices 40, 50, 70 are shown.
- Each of the Ethernet-capable terminal devices 40, 50 and 70 can be connected together with other Ethernet-capable terminal devices to a separate wired Ethernet-capable network. Network.
- Each of the Ethernet-capable terminal devices 40, 50 and 70 can, for example, have a control device 42, 52 or 72, a storage device 43, 53, 73 and an Ethernet-based interface 41, 51 or 71.
- the Ethernet-capable terminal devices 40, 50 and 70 are each designed to support IP-based communication.
- an IP stack also called an IP stack, for IP communication is preferably stored in each storage device of the Ethernet-capable terminal devices 40, 50 and 70.
- an ARP module is stored in each of the memory devices 43, 53 and 73, which implements an address resolution protocol with which each of the Ethernet-capable terminal devices 40, 50 and 70 can find out the MAC address associated with an IP address of each network participant involved.
- ARP stands for Address Resolution Protocol, which is generally known.
- each of the Ethernet-capable terminal devices 40, 50 and 70 is designed to pack data to be transmitted into an IP packet and to transmit this in an Ethernet-based data frame in a manner known per se via the respective Ethernet-based interface. It should be noted, however, that the Ethernet-capable terminal devices 40, 50 and 70 do not necessarily have to support IP-based communication.
- each of the Ethernet-capable terminal devices 40, 50 and 70 has a unique MAC address and a unique IP address.
- a firmware or an operating system is also expediently stored, which controls and monitors the corresponding Ethernet-capable terminal device.
- the WLAN network 100 is preferably implemented according to a standard of the IEEE 802.11 family.
- the WLAN network 100 includes the WLAN-enabled terminal 10 shown in Figure 1, a further WLAN-enabled terminal 30, which can be constructed essentially identically, or at least similarly, to the WLAN-enabled terminal 10.
- the WLAN-enabled terminal 30 has an Ethernet-based interface 31, a WLAN interface 30, a control device 34 and a Storage device 35, which are, for example, components of a microcontroller 32.
- the WLAN-enabled terminal 30 also has only one IP address, which is uniquely assigned to the WLAN interface 33. In a manner known per se, the WLAN interface 33 and the Ethernet-based interface 31 are each assigned a unique MAC address.
- the WLAN network 100 also includes the WLAN-enabled base station 20 shown in Figure 2 and another WLAN-enabled terminal device 60, which, however, does not have VXLAN functionality, i.e. in which no VXLAN tunnel endpoint is implemented.
- the WLAN-enabled terminal device 60 can, for example, be a conventional smartphone, a PC, a tablet or the like, which are designed for conventional communication according to a WLAN standard, in particular from the 802.11 family.
- the Ethernet-capable terminal 40 can be connected to the Ethernet-based interface 11 of the WLAN-capable terminal 10 via the line 80, while the Ethernet-capable terminal 50 can be connected to the Ethernet-based interface 31 of the WLAN-capable terminal 30 via the line 81.
- the Ethernet-capable terminal 70 can be connected to the Ethernet-based interface 21 of the WLAN-capable base station 20 via the line 82. It should be noted at this point that all WLAN-based communication in the WLAN network 100 can take place in a manner known per se via the access point 20. This is symbolized in Figure 3 by a dashed line that leads from the WL AN interface 13 and the WLAN interface 33 to the WLAN interface 23 of the access point 20.
- the WLAN-enabled terminals 10 and 30 as well as the access point 20 each have a unique MAC address, which is assigned to the WLAN interfaces 13, 33 and 23.
- the WLAN-enabled end devices 10 and 30 as well as the access point 20 are each assigned only a single IP address via which the WLAN-enabled end devices 10 and 30 and also the access point 20 can be reached from both the WLAN network 100 and the Ethernet-based network 90.
- the exemplary communication system 1 and thus the associated WLAN-enabled terminal devices 10 and 30, the access point 20, the WLAN-enabled terminal device 60 and the Ethernet-enabled terminal devices 40, 50 and 70 are each designed to enable communication with one another.
- the WLAN-enabled terminal devices 10 and 30 and the access point 20 ensure layer 2 transparent communication between all network participants of the WLAN network 100 and the Ethernet-enabled terminal devices 40, 50 and 70 of the wired Ethernet-based system 90 thanks to the implemented VXLAN functionality.
- the WLAN network 100 and the wired Ethernet-based system 90 can together form an IP-based subnetwork, which is set up in a configuration phase.
- the first three bytes "172.16.140" of each IP address designate the subnetwork in a manner known per se, with only the last byte being different and thus clearly addressing the WLAN-capable terminal devices and Ethernet-capable terminal devices as well as the WLAN-capable base station 20 in the IP-based subnetwork.
- VXLAN identifier VNI is stored in each of the WLAN-enabled terminal devices 10 and 30 and in the access point 20, which is used by the respective VXLAN tunnel endpoints implemented in the WLAN-enabled terminal devices 10 and 30 and in the access point 20 when generating VXLAN packets.
- the WLAN-enabled base station 20 is preferably designed to 1. to enable data communication, for example, between the WLAN-enabled terminal 60, in which no VXLAN tunnel endpoint is implemented, and the Ethernet-enabled terminal 70 connectable to the Ethernet-based interface 21, bypassing the VXLAN tunnel endpoint 26, by transmitting data untunneled between the WLAN interface 23 and the Ethernet-based interface 21, preferably via the first software bridge, according to the exemplary implementation,
- Ethernet-capable terminal devices 40 and 50 which can each only be reached via the WLAN-capable terminal device 10 having a VXLAN tunnel endpoint or the WLAN-capable terminal device 30 having a VXLAN tunnel endpoint, by only forwarding the received VXL AN packets, in which the data to be transmitted is packed, via the WLAN interface 23, and
- the exemplary communication system 1 can be statically configured before initial commissioning.
- the Ethernet-capable terminal devices 40, 50 and 70, the WLAN-capable terminal devices 10, 30 and 60 and the access point 20 of each participating network participant must receive the IP address and the know the respective MAC address.
- a table or configuration file is stored which in particular contains an assignment of the IP address to the respective MAC address of each network participant.
- the WLAN-capable terminal devices 10 and 30 and the access point 20 contain information about which Ethernet-capable terminal devices can be reached via the Ethernet-based interface 11, 31 or 21 and/or the respective WLAN interface 13, 33, 23. This information can also be contained in the respective configuration file.
- the Ethernet-capable terminals 40, 50 and 70, the WLAN-capable terminals 10, 30 and 60 and possibly also the WLAN-capable base station 20 can execute the known ARP protocol, whereby the communication system 1, i.e. the Ethernet-capable terminals 40, 50 and 70, the WLAN-capable terminals 10, 30 and 60 and the access point 20 learn which IP address and MAC address the respective other network participants have.
- the ARP method is well known to the person skilled in the art.
- Ethernet-capable terminal device 50 which only knows the IP address of the Ethernet-capable terminal device 70 and wants to communicate with the terminal device 70, can obtain the MAC address of the Ethernet-capable terminal device 70 using the ARP protocol.
- the control device 52 of the Ethernet-capable terminal 50 first calls the software module stored in the storage device 53, which implements the ARP protocol. By executing the software module, the control unit 52 causes the Ethernet-capable terminal 50 to generate a so-called ARP request packet, which contains the IP address of the Ethernet-capable terminal 70 and a request to send the associated MAC address back to the Ethernet-capable terminal 50. Since the Ethernet-capable terminal 50 does not know where the Ethernet-capable target terminal 70 is located, a so-called broadcast is started, in which the ARP packet generated by the Ethernet-capable terminal device is sent to all network participants of the communication system 1.
- the control device 52 can be designed to cause the Ethernet-capable terminal 50 to generate an Ethernet data frame according to Figure 4 by executing the stored software, which contains in the header as the destination MAC address a broadcast address, which has been communicated in advance to all network participants of the communication system 1, for example together with unicast and/or multicast addresses, and the source MAC address of the Ethernet-capable terminal 50.
- the ARP packet is inserted in the data field, while the check field contains a corresponding checksum formed over the data, which is not relevant to the invention, however.
- the Ethernet-capable terminal 50 transmits this Ethernet data frame to the Ethernet-based interface 31 of the WLAN-capable terminal 30.
- the Ethernet data frame is transferred from the Ethernet-based interface 31 to the microcontroller 32 or the control device 34, which is preferably designed to check whether the ARP packet contained in the Ethernet data frame is intended for the WLAN-capable terminal 30 or needs to be forwarded.
- the control device 34 recognizes that the ARP packet is to be forwarded.
- the control device 34 is advantageously designed to supply the Ethernet data frame supplied by the Ethernet-based interface 31 via the first software bridge to the VXLAN tunnel endpoint, which encapsulates the Ethernet data frame in a VXLAN packet, by executing the software stored in the memory device 35.
- the VXLAN tunnel endpoint encapsulates the Ethernet data frame in a VXLAN packet.
- the format of the VXLAN packet has the format shown in Figure 5. Accordingly, the control device 34 generates a header which contains the following information, read from right to left:
- the predetermined VXLAN identifier VNI an outer UDP header which contains, for example, the predefined destination port 4789 and the source port 40298, an outer IPv4 header which contains as the destination IP address a multicast address previously defined during the configuration phase and as the source IP address the IP address of the WLAN-enabled terminal device 30, and an outer Ethernet header which contains as the destination MAC address a previously defined multicast address and as the source MAC address the MAC address of the WLAN-enabled terminal device 30.
- the control device 34 then causes the WLAN-enabled terminal 30 to feed the VXLAN packet to the WLAN interface 33, for example via the second software bridge, and to send the VXLAN packet in a WLAN data frame via the WLAN interface 33.
- the WLAN header contains the MAC address of the access point 20 as the destination MAC address and the MAC address of the WLAN-enabled terminal 30 as the source MAC address.
- the WLAN data frame is received by the WLAN-enabled interface 23 of the access point 20 and passed on to the microcontroller 22.
- the control device 24 is preferably designed to read the destination MAC address from the Ethernet data frame contained in the VXLAN packet. Since the destination MAC address is a multicast address, the control device 24, by executing the software stored in the memory device 25, causes the Ethernet frame containing the ARP packet to be decapsulated from the VXLAN packet that was contained in the received WLAN data frame and to be transmitted via the Ethernet-capable interface 21 to the Ethernet-capable terminal device 70.
- the VXLAN packet contained in the received WLAN data frame which contains a multicast IP address as the destination IP address, is forwarded via the WLAN interface 23 to the WLAN terminal devices 10 and 60, among others, in a first WLAN data frame, which now also contains a predetermined multicast address as the destination address.
- the decapsulated ARP packet is also sent via the WLAN interface 23 in a second WLAN data frame, which now also contains a predetermined broadcast address as the destination address.
- the VXLAN packet containing the ARP packet and the non-tunneled ARP packet reach the WLAN-capable end devices 10 and 60 via the WLAN interfaces 13 and 61.
- the control devices 12 and 62 can each be designed to check, by executing the software stored in the storage device 15 or 63, whether the non-tunneled ARP packet received in the second WLAN data frame is intended for the respective WLAN terminal 10 or 60. Since the ARP packet is not intended for the WLAN-capable terminals 10 and 60, the control devices 15 and 63 discard the received ARP packet.
- the control device 12 can also be designed to check the ARP packet received via the WLAN interface 13 in the first WLAN data frame to pass the VXLAN packet received to the VXLAN tunnel endpoint 16, which extracts the Ethemet data frame contained therein and transmits it to the Ethernet-capable terminal 40 via the Ethemet-based interface 11.
- the Ethernet-capable terminal 40 is designed to read the ARP packet contained in the respective Ethemet data frame and to check whether the ARP packet is intended for the Ethernet-capable terminal 40. In the present case, the ARP packet is not intended for the Ethemet-capable terminal 40.
- the control device 72 of the Ethernet-capable terminal 70 is able to read and evaluate the ARP packet contained in the Ethernet data frame received via the Ethernet-based interface 71. The control device 72 now recognizes that the ARP packet contains the IP address of the Ethernet-capable terminal 70 and a request to transmit the associated MAC address to the Ethernet-capable terminal 50.
- the control device 72 therefore causes the Ethernet-capable terminal 70 to generate an ARP response packet which contains both the IP address and MAC address of the Ethernet-capable terminal 70.
- the ARP response packet is then transmitted in an Ethernet data frame via the Ethernet-based interface 71 to the Ethernet-based interface 21 of the access point 20.
- the header of the Ethernet data frame contains the MAC address of the Ethernet-capable terminal 50 as the destination MAC address and the MAC address of the Ethernet-capable terminal 70 as the source MAC address.
- the control device 24 passes the Ethernet data frame to the VXLAN tunnel endpoint, which encapsulates the Ethernet data frame containing the ARP response packet in a VXLAN packet.
- VXLAN packet contains, for example, the following information:
- the predetermined VXL AN identifier an outer UDP (User Datagram Protocol) header with a destination port 4789 and a source port 60108, an outer IPv4 header with the IP address of the access point 20 as the source IP address and the IP Address of the WLAN-capable terminal 30 as the destination IP address and an outer Ethernet header with the MAC address of the WLAN-capable terminal 30 as the destination MAC address and the MAC address of the access point 20 as the source MAC address.
- the WLAN data frame contains a header with the MAC address of the WLAN interface 33 of the WLAN-capable terminal 30 as the destination MAC address and the MAC address of the access point 20 as the source MAC address.
- the WLAN data frame is received by the WLAN interface 33 and passed to the microcontroller 32 or the control device 34.
- the control device 34 is designed to pass the VXLAN packet contained in the WLAN data frame to the VXLAN tunnel endpoint by executing the stored software, which extracts the Ethernet data frame from the VXLAN packet and transmits it to the Ethernet-capable terminal 50 via the Ethernet-based interface 31.
- the control device 52 of the Ethernet-capable terminal 50 is designed to read and evaluate the ARP response packet contained in the Ethernet data frame.
- the control device 52 is preferably designed to cause the Ethernet-capable terminal 50, in response to the data contained in the ARP response packet, to generate an ARP table in a manner known per se, in which the IP address and the MAC address of the Ethernet-capable terminal 70 are stored, for example in the storage device 53.
- each network terminal of the exemplary communication system 1 can create a complete ARP table of all network participants.
- an Ethernet data frame of the Ethernet-capable terminal 70 received via the Ethernet-based interface 21 can be passed to the VXLAN tunnel endpoint via the virtual Ethernet interface and the second software bridge under the control of the control device 24.
- the rules stored in the storage device 25 ensure, for example, that the VXLAN packet generated by the VXLAN tunnel endpoint is not sent again by the first software bridge to the VXLAN tunnel endpoint via the virtual Ethernet interface. Further example communication processes are described in detail below.
- the WLAN-enabled terminals 10, 30 and 60 want to communicate with each other, this can be done according to a known WLAN communication protocol according to a standard of the IEEE 802.11 family. In other words: If the WLAN-enabled terminal 60 wants to transmit data to the WLAN-enabled terminal 30, these are transmitted in a conventional manner in a WLAN data frame to the WLAN interface 23 of the access point 20, which then forwards the received data in a WLAN data frame to the WLAN-enabled terminal 30.
- the control device 62 is designed to cause the WLAN-enabled terminal 60 to insert data to be transmitted into an IP packet which contains the IP address of the WLAN-enabled terminal 60 as the source IP address and the IP address of the Ethernet-enabled terminal 50 as the destination IP address.
- the IP packet is then sent out in a WLAN data frame via the WLAN interface 61.
- the header of the WLAN data frame contains three addresses: the MAC address of the WLAN-enabled terminal 60 as the source MAC address, the MAC address of the WLAN interface 23 of the access point 20 as the destination MAC address and also the MAC address of the Ethernet-enabled terminal 50 as the actual destination.
- the control device 24 of the access point 20 is designed to evaluate the MAC addresses of the received WLAN data frame in order to recognize who the IP packet is intended for. In the present case, the control device 24 recognizes that the IP packet is intended for the Ethernet-capable terminal 50. Due to the system configuration that has been carried out, the control device 24 knows that the Ethernet-capable Terminal 50 can only be reached via the WLAN-capable terminal 30.
- the control device 24 of the access point 20 is designed to supply the IP packet contained in the WLAN data frame via the first software bridge and via the virtual Ethernet interface and the second software bridge to the VXLAN tunnel endpoint, which encapsulates the IP packet in a VXLAN packet, by executing the software stored in the storage device 25.
- the VXLAN packet created in this way contains headers that contain, for example, the following information:
- the control device 24 is further designed to send the VXLAN packet in a WLAN data frame via the WLAN interface 23, which can be received at the WLAN interface 33 of the WLAN-enabled terminal 30.
- the header of the WLAN data frame contains, for example, the MAC address of the access point 20 as the source MAC address and the MAC address of the WLAN interface 33 as the destination MAC address.
- the control device 34 of the WLAN-capable terminal 30 is designed, for example, to pass the VXLAN packet received via the WLAN interface 33 via the software module that implements the second software bridge to the VXLAN tunnel endpoint by executing the software stored in the storage device 35, which decapsulates the Ethernet data frame contained in the VXLAN packet with the IP packet transmitted therein and passes the Ethernet data frame to the software module that implements the first software bridge.
- control device 34 is designed to read and evaluate the target MAC address contained in the Ethernet data frame by executing the software stored in the memory device 35 in order to recognize in the present example that the Ethernet data frame is intended for the Ethernet-capable terminal device 50. Accordingly, the control device 34 causes the WLAN-capable terminal device 30 to transmit the Ethernet data frame via the Ethernet-based interface 31 to the Ethernet-capable terminal 50.
- the Ethernet-capable terminal 50 is designed to receive the Ethernet data frame received via the Ethernet-based interface 51 in a manner known per se, to extract the IP packet and to process the data contained in the IP packet depending on the application program.
- Ethernet-capable terminal 40 acting as the source terminal and the WLAN-capable terminal 60 acting as the destination terminal will now be described.
- the control device 41 of the Ethernet-capable terminal 40 is designed to insert data to be transmitted into an IP packet.
- the IP header of the IP packet contains the IP address of the WLAN-capable terminal 60 as the destination IP address and the IP address of the Ethernet-capable terminal 40 as the source IP address.
- the IP packet is then inserted into an Ethernet data frame, the header of which contains the MAC address of the WLAN-capable terminal 60 as the destination MAC address and the MAC address of the Ethernet-capable terminal 40 as the source MAC address.
- the control device 42 is designed to transmit the Ethernet data frame via the Ethernet-based interface 41 to the Ethernet-based interface 11 of the WLAN-capable terminal 10.
- the Ethernet-based interface 11 transfers the Ethernet data frame to the control device 14, which, by executing the software stored in the storage device 15, first causes the WLAN-enabled terminal 10 to check for whom the received Ethernet data frame or the IP packet contained therein is intended.
- the control device 14 recognizes, in particular based on the destination MAC address contained in the Ethernet data frame, that the Ethernet data frame or the IP packet contained therein is intended for the WLAN-enabled terminal 60.
- the control device 14 executes the stored software module that implements the VXLAN tunnel endpoint.
- the VXLAN tunnel endpoint ensures that the Ethernet data frame is packed into a VXLAN packet, which is then sent out in a WLAN data frame via the WLAN interface 13, so that it can be received by the WL AN interface 23 of the access point 20.
- the header of the WLAN data frame to be transmitted contains the MAC address of the WLAN-enabled terminal device 10 as the source MAC address and the MAC address of the access point 20 as the destination MAC address.
- the WLAN data frame sent via the WLAN interface 13 is received by the WLAN interface 23 and passed on to the control device 24.
- the control device 24 executes the stored software and causes the access point 20 to pass the VXLAN packet contained in the received WLAN data frame to the VXLAN tunnel endpoint and to extract the Ethernet data frame from the VXLAN packet. Based on the destination MAC address contained in the extracted Ethernet data frame, the control device 24 recognizes that the Ethernet data frame is intended for the WLAN-capable terminal device 60. In response to this, the control device 24 causes the access point 20 to convert the extracted Ethernet data frame into a WLAN data frame that contains the MAC address of the WLAN-capable terminal device 60 as the destination MAC address.
- the WLAN data frame is then sent via the WLAN interface 23 and received by the WLAN interface 61 of the WLAN-enabled terminal device 60 and passed on to the control device 62 for further use. Thanks to this measure, the WLAN-enabled terminal device 60, which does not have VXLAN functionality, can communicate with the Ethernet-enabled terminal device 40. Similarly, for example, the Ethernet-capable terminal 40 can communicate with the Ethernet-capable terminal 70. In this case, however, the control device 24 recognizes that the Ethernet data frame extracted from a VXLAN packet contained in a WLAN data frame coming from the WLAN-capable terminal 10 is intended for the Ethernet-capable terminal 70. Accordingly, the control device 24 ensures that the Ethernet data frame extracted from the VXLAN packet is forwarded to the Ethernet-capable terminal 70 via the Ethernet-based interface 21.
- Ethernet-capable terminal 40 As source and the Ethernet-capable terminal 50 as destination will now be described.
- the control device 41 of the Ethernet-capable terminal 40 is designed to insert data to be transmitted into an IP packet.
- the IP header of the IP packet contains the IP address of the Ethernet-capable terminal 50 as the destination IP address and the IP address of the Ethernet-capable terminal 40 as the source IP address.
- the IP packet is then inserted into an Ethernet data frame, the header of which contains the MAC address of the Ethernet-capable terminal 50 as the destination MAC address and the MAC address of the Ethernet-capable terminal 40 as the source MAC address.
- the control device 42 is designed to transmit the Ethernet data frame via the Ethernet-based interface 41 to the Ethernet-based interface 11 of the WLAN-capable terminal 10.
- the Ethernet-based interface 11 transfers the Ethernet data frame to the control device 14, which, by executing the software stored in the storage device 15, first causes the WLAN-capable terminal 10 to check for whom the received Ethernet data frame or the IP packet contained therein is intended.
- the control device 14 recognizes, in particular based on the destination MAC address contained in the Ethernet data frame, that the Ethernet data frame or the IP packet contained therein is intended for the Ethernet-capable terminal 50.
- the control device 14 executes the stored software module which implements the VXLAN tunnel endpoint.
- the VXLAN tunnel endpoint ensures that the Ethemet data frame is packed into a VXLAN packet, which is then sent out in a WLAN data frame via the WLAN interface 13 so that it can be received by the WLAN interface 23 of the access point 20.
- the headers of the VXLAN packet contain, for example, the following information: The known VXLAN identifier VNI contained in the VXLAN header, an outer UDP header with a corresponding destination port 4789 and a corresponding source port, an outer IPv4 header with the IP address of the WLAN-enabled terminal 10 as the source IP address and the IP address of the WLAN-enabled terminal 30 as the destination IP address and an outer Ethernet header with the MAC address of the WLAN-enabled terminal 10 as the source MAC address and the MAC address of the WLAN-enabled terminal 30, via which the Ethernet-enabled terminal can be reached as the actual destination, as the destination MAC address.
- the header of the WLAN data frame to be transmitted contains three MAC addresses: the MAC address of the WLAN-enabled terminal device 10 as the source MAC address, the MAC address of the access point 20 as the destination MAC address and the MAC address of the WLAN-enabled terminal device 30.
- the WLAN data frame sent via the WLAN interface 13 is received by the WLAN interface 23 and passed on to the control device 24.
- the control device 24 is designed to evaluate the information contained in the header of the received WLAN data frame. After evaluating the information, the control device 24 knows that the VXLAN packet contained in the WLAN data frame is to be forwarded to the WLAN-capable terminal 30.
- the control device 24 is designed to forward the received VXLAN packet in the WLAN data frame via the WLAN interface 23 by executing the stored software, so that the WLAN data frame can be received at the WLAN interface 33 of the WLAN-capable terminal 30.
- the WLAN interface 33 of the WLAN-enabled terminal 30 transfers the received WLAN data frame to the control device 34, which is designed to execute the software stored in the storage device, the in particular, the VXLAN tunnel endpoint extracts the Ethernet data frame contained in the received VXLAN packet, which contains the MAC address of the Ethernet-capable terminal 50 as the destination MAC address.
- the control device 34 recognizes from the destination MAC address that the Ethernet data frame is intended for the Ethernet-capable terminal 50, which is connected to the Ethernet-based interface 31. Accordingly, the control device 34 transfers the extracted Ethernet data frame to the Ethernet-based interface 31 for forwarding the Ethernet data frame to the Ethernet-capable terminal 50.
- the Ethernet-capable terminal 50 is designed to receive the Ethernet data frame received via the Ethernet-based interface 51 in a manner known per se, to extract the IP packet and to process the data contained in the IP packet depending on the application program.
- the exemplary communication system 1 shown in Figure 3 it is possible to use VXLAN tunnel technology to enable Ethernet-capable terminal devices, such as terminal devices 40, 50 and 70, to communicate with each other, even though they can only be reached via WLAN-capable terminal devices 10 or 30 and an access point 20, whose MAC addresses do not match the MAC addresses of the respective Ethernet-based terminal devices 40, 50 and 70. Furthermore, the exemplary communication system 1 enables WLAN-capable terminal devices that do not have VXLAN functionality, such as WLAN-capable terminal device 60, and Ethernet-capable terminal devices 40, 50 or 70, to communicate with each other.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| BE20226051A BE1031167B1 (de) | 2022-12-21 | 2022-12-21 | WLAN-fähiges Endgerät, WLAN-fähige Basisstation und Kommunikationssystem umfassend eine WLAN-fähige Basisstation und mehrere WLAN-fähige Endgeräte |
| PCT/EP2023/086729 WO2024133326A1 (de) | 2022-12-21 | 2023-12-19 | Wlan-fähiges endgerät, wlan-fähige basisstation und kommunikationssystem umfassend eine wlan-fähige basisstation und mehrere wlan-fähige endgeräte |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| EP4639861A1 true EP4639861A1 (de) | 2025-10-29 |
Family
ID=85157287
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP23833132.6A Pending EP4639861A1 (de) | 2022-12-21 | 2023-12-19 | Wlan-fähiges endgerät, wlan-fähige basisstation und kommunikationssystem umfassend eine wlan-fähige basisstation und mehrere wlan-fähige endgeräte |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP4639861A1 (de) |
| BE (1) | BE1031167B1 (de) |
| WO (1) | WO2024133326A1 (de) |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11296985B2 (en) * | 2020-07-27 | 2022-04-05 | Cisco Technology, Inc. | Normalized lookup and forwarding for diverse virtual private networks |
-
2022
- 2022-12-21 BE BE20226051A patent/BE1031167B1/de not_active IP Right Cessation
-
2023
- 2023-12-19 WO PCT/EP2023/086729 patent/WO2024133326A1/de not_active Ceased
- 2023-12-19 EP EP23833132.6A patent/EP4639861A1/de active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024133326A1 (de) | 2024-06-27 |
| BE1031167A1 (de) | 2024-07-15 |
| BE1031167B1 (de) | 2024-07-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| DE69729040T2 (de) | Netzwerkübertragung | |
| DE60029430T2 (de) | Mehrfach-sendefähiges adressauflösungsprotokoll | |
| DE60300035T2 (de) | Kommunikationssystem zum Aufbauen einer PPPoE ähnlichen Verbindung zwischen IEEE1394 basierten Peeren und IP basierten Peeren | |
| EP3932020B1 (de) | Verfahren zum routen von telegrammen in einem automatisierungsnetzwerk, datenstruktur, automatisierungsnetzwerk und netzwerkverteiler | |
| DE60133175T2 (de) | Kommunikationsnetz | |
| DE60131765T2 (de) | Verfahren zur verbindung mehrerer kommunikationsbusse mit drahtlosen verbindungen | |
| EP1186200B1 (de) | Verfahren und einrichtung zum übermitteln von daten | |
| DE102018129813A1 (de) | Datenübertragungsverfahren und Automatisierungskommunikationsnetzwerk | |
| EP1081921B1 (de) | Verfahren zur Vergabe von IP-Adressen in Kommunikationsnetzen | |
| BE1031167B1 (de) | WLAN-fähiges Endgerät, WLAN-fähige Basisstation und Kommunikationssystem umfassend eine WLAN-fähige Basisstation und mehrere WLAN-fähige Endgeräte | |
| EP4035315B1 (de) | Automatisierungsnetzwerk und verfahren zur datenübertragung in einem automatisierungsnetzwerk | |
| DE102022134300A1 (de) | WLAN-fähiges Endgerät, WLAN-fähige Basisstation und Kommunikationssystem umfassend eine WLAN-fähige Basisstation und mehrere WLAN-fähige Endgeräte | |
| DE102015209361A1 (de) | Paketbasiertes Kommunikationsnetz mit Autokonfigurierung lokaler Netzwerk-Adressen | |
| WO2001071986A1 (de) | Verfahren und anordnung zum übertragen eines datenpakets von einer ersten vermittlungseinheit an eine zweite vermittlungseinheit in einem datennetz | |
| WO2021004835A1 (de) | Verfahren und datennetzwerk zum kommunizieren von dateninhalten, insbesondere in einer aufzuganlage | |
| DE602005001578T2 (de) | Brücke zur Übersetzung zwsichen lokalen Ethernet- und 1394A-Anschlüssen für Geräte der Unterhaltungselektronik | |
| EP3963839B1 (de) | Netzwerkverteiler, automatisierungsnetzwerk und verfahren zur datenübertragung in einem automatisierungsnetzwerk | |
| EP3142334B1 (de) | Verfahren zum betrieb von kommunikationsgeräten innerhalb eines industriellen automatisierungssystems | |
| EP2605457A1 (de) | Verfahren zum Übertragen von Nutzdaten | |
| DE19927304C2 (de) | Verfahren und Einrichtung zum Übermitteln von Daten | |
| EP2564576A2 (de) | Verfahren zur bereitstellung einer kommunikation für mindestens ein gerät | |
| WO2020038820A1 (de) | Verfahren zum einrichten eines streams, verfahren zur bereitstellung von stream-kennungs-informationen, verwendung eines dns-servers, gerät, computerprogramm und computerlesbares medium | |
| EP4096170B1 (de) | Verfahren zur datenübertragung in einem netzwerksystem sowie netzwerksystem | |
| DE102019000465A1 (de) | Verfahren und Vorrichtung zur unterbrechungsfreien Internet Protocol (IP) Kommunikation in einem Fahrzeug | |
| EP3579498B1 (de) | Verfahren zum konfigurieren eines kommunikationsnetzes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
| 17P | Request for examination filed |
Effective date: 20250710 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| DAV | Request for validation of the european patent (deleted) | ||
| DAX | Request for extension of the european patent (deleted) | ||
| RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: PHOENIX CONTACT GMBH & CO. KG |