[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

EP3777327A1 - Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé - Google Patents

Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé

Info

Publication number
EP3777327A1
EP3777327A1 EP19726732.1A EP19726732A EP3777327A1 EP 3777327 A1 EP3777327 A1 EP 3777327A1 EP 19726732 A EP19726732 A EP 19726732A EP 3777327 A1 EP3777327 A1 EP 3777327A1
Authority
EP
European Patent Office
Prior art keywords
mesh network
nodes
application
message
bandwidth
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.)
Withdrawn
Application number
EP19726732.1A
Other languages
German (de)
English (en)
Inventor
Shmuel Silverman
Simon Coombes
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gooee Ltd UK
Original Assignee
Gooee Ltd UK
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US16/264,915 external-priority patent/US10917254B2/en
Application filed by Gooee Ltd UK filed Critical Gooee Ltd UK
Publication of EP3777327A1 publication Critical patent/EP3777327A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/125—Shortest path evaluation based on throughput or bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/28—Connectivity information management, e.g. connectivity discovery or connectivity update for reactive routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • a node may include a redistribution point (e.g. data communication equipment) or a communication endpoint (e.g. data terminal equipment).
  • a mesh network is a local network topology in which infrastructure nodes (i.e. bridges, switches and other infrastructure devices) connect directly, dynamically and non-hierarchically to as many other nodes as possible and cooperate with one another to efficiently route data from/to clients.
  • infrastructure nodes i.e. bridges, switches and other infrastructure devices
  • every node may be interconnected.
  • the simplest fully connected network is a two-node network.
  • a partially connected network such as network 220 illustrated in Fig.
  • certain nodes may be connected to exactly one other node while other nodes are connected to two or more other nodes via a point-to-point link. This may make it possible to make use of some of the redundancy of mesh topology that is physically fully connected, without the expense and complexity required for a connection between every node in the network.
  • Mesh networks are growing in size as industrial, lighting, smart home and other Internet of Things (loT) applications are taking advantage of them with multitudes of sensors and other devices.
  • BLUETOOTH mesh networks are one such network type. These networks make use of messages called heartbeats that are transmitted by nodes periodically.
  • a heartbeat message may indicate to other nodes in the network that the node sending the heartbeat is still active.
  • heartbeat messages may contain data which may allow receiving nodes to determine how far away a sender is in terms of a number of hops required to reach the sender.
  • the use of heartbeat messages may be associated with a time to live (TTL) field within a network packet. TTL may control a maximum number of hops over which a message will be relayed. Setting the TTL may allow nodes to exercise control over relaying and conserve energy, by ensuring messages are not relayed further than is required.
  • each node may implement a cache that contains all recently seen messages and if a message is found to be in the cache this is an indication that the node has seen and processed the message.
  • a mesh network when sending video data, which requires a high frame rate, a mesh network by its very nature may make it difficult to prioritize messages getting through the network due to the competing messages broadcasting through the network. Furthermore, as mesh networks grow in size and are deployed in a relatively close space, there is a substantial increase in a likelihood that interference or collisions will result in message communication failure.
  • a system for managing dynamic tunneling in a mesh network is disclosed.
  • the exemplary system comprises: a first of a plurality of nodes in a mesh network to function as an originator station, where the first of the plurality of nodes is associated with an application that transmits high-density data packets; a second of the plurality of nodes in the mesh network to function as a target station and to receive the high-density data packets from the application; and a third of the plurality of nodes in the mesh network to function as a coordinating node and to generate a message, via a processor, across the plurality of nodes to activate a best path through the mesh network when the application requires more bandwidth.
  • a method for managing dynamic tunneling in a mesh network comprises: associating an application that transmits high density data packets with a first of a plurality of nodes in a mesh network that functions as an originator station for transmitting the high density data packets to a second of the plurality of nodes in the mesh network that functions as a target station; creating an auto-trigger to be initiated by the application in a case that the application requires more bandwidth; and in response to the auto-trigger being activated, generating a message, via a processor, across the plurality of nodes to activate a best path through the mesh network.
  • a non-transitory computer readable medium comprising computer executable steps that, when executed by a processor, perform a method for managing dynamic tunneling in a mesh network.
  • the exemplary method executed by the medium comprises: associating an application that transmits high density data packets with a first of a plurality of nodes in a mesh network that functions as an originator station for transmitting the high density data packets to a second of the plurality of nodes in the mesh network that functions as a target station; creating an auto-trigger to be initiated by the application in a case that the application requires more bandwidth; and in response to the auto-trigger being activated, generating a message, via a processor, across the plurality of nodes to activate a best path through the mesh network, wherein the message indicates a time duration that the application will require more bandwidth.
  • FIG. 1 illustrates a high-level system diagram of a luminaire loT network which may be implemented in any wired or wireless or light communication mesh network system according to some
  • FIG. 2A and FIG. 2B illustrate a logical topology diagram of a fully and partially connected mesh network according to the prior art which may be implemented in any wired or wireless or light communication network system;
  • FIG. 3 illustrates a high-level system diagram of a mesh network, using the interference mitigating protocol according to some embodiments
  • FIG. 4 is a diagram that illustrates an embodiment of a best path determination for transferring data packets between an originator station and a target station in the mesh network;
  • FIG. 5 is a diagram that illustrates an embodiment of an initiated interference mitigating for transferring data packets between an originator station to a target station in a mesh network;
  • FIG. 6 is a diagram showing re-activated nodes after transferring data packets between an originator station to a target station in the mesh network, according to an embodiment.
  • FIG. 7A and FIG. 7B illustrate a method according to some embodiments.
  • Embodiments described herein relate generally to devices, systems, and methods for managing and controlling a dynamic tunneling protocol in a mesh network.
  • the phrases“devices,”“systems,” and“methods” may be used either individually or in any combination referring without limitation to disclosed components, grouping, arrangements, steps, functions, or processes.
  • the exemplary disclosed devices, systems, and methods may provide for an interface to set up identification of an application that may require more bandwidth for high-density data packets.
  • the setup information may store a location of a node associated with the application such as, but not limited to, an originator station.
  • the setup identification may be related to an automatic discovery and/or an auto-trigger setup for the application.
  • controlling the dynamic tunneling protocol may be based on sending a start message to initiate the dynamic tunneling protocol and sending a close message to stop the dynamic tunneling protocol and to restart normal operation of the mesh network.
  • the mesh network described herein may include any type of wired or wireless network or light communication network system. More particularly, the present embodiments relate to a system and method for implementing or initiating an interference mitigating protocol in a mesh network. Exemplary embodiments described herein will be illustrated below in conjunction with a mesh network incorporated in the luminaire loT network system. However, the embodiments of the system and method may be implemented in any type of wired or wireless or light communication, e.g., a Visual Light Communication/Dark Light Communication (VLC/DLC) network system.
  • VLC/DLC Visual Light Communication/Dark Light Communication
  • module may refer to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Also, while the present disclosure may be described in terms of exemplary embodiments, it should be appreciated those individual aspects of the embodiments described herein may be separately claimed.
  • Non-volatile media includes, for example, NVRAM, or magnetic or optical disks.
  • Volatile media includes dynamic memory, such as main memory.
  • Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other non-transitory medium, magneto optical medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, solid state medium like a memory card, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
  • a digital file attachment to email or other self-contained information archive or set of archives may be considered a distribution medium equivalent to a tangible storage medium.
  • the database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Further, while reference is made to various types of databases, it may be understood by one of ordinary skill in the art that all of the database functions may be stored within compartments of a single database, or within individual databases. In any event, the present specification may be considered to include a tangible storage medium or distribution medium and prior art-recognized equivalents and successor media, in which the software implementations of the present disclosure are stored.
  • the system may include at least one of a plurality of luminaires 112 and/or a plurality of LEDs 11 1 configured to communicate with at least one gateway 102, at least one single variable to control the luminaire driver and/or LED driver behavior, at least one sensor subsystem 108 configured to sense a plurality of color channels and monitor at least one change in environment in real time, at least one power meter 1 14 configured to measure power consumption of one or more luminaires 1 12 in real time, at least one dimming control protocol or dimming controller device or driver or interface 1 10 installed in one or more lighting devices (e.g., luminaires 1 12) and for controlling a plurality of dimming levels and/or dimming protocols of the lighting devices, and at least one server 106 (e.g. a cloud based server).
  • a cloud based server e.g. a cloud based server
  • the server 106 is a cloud server 106.
  • one or more servers 106 may be a local server, dedicated server, processor, or other unit consistent with this disclosure.
  • Each of the plurality of luminaires 1 12 and/or LEDs 1 1 1 may include at least one driver and/or LED driver. Further, each of the plurality of luminaires 1 12 and/or LEDs 11 1 may comprise an inbuilt power source where the power source may include at least one of plurality of rechargeable batteries.
  • the at least one sensor subsystem 108 and the at least one power meter 1 14 may be connected with the at least one gateway 102 along with the plurality of luminaires 1 12.
  • the at least one sensor subsystem 108 may include at least two sensors.
  • a first sensor may include an environment sensor dedicated to environment sensing and may be arranged such that it faces away from and/or extends in a downwardly fashion from the luminaire.
  • a second sensor may include a color sensor such as, without limitation, a Red Green Blue (RGB) or Yellow Red Green Blue (YRGB) sensor arranged such that it faces the luminaire directly.
  • the at least one server 106 is configured to calculate and predict depreciation of the dimming levels of the luminaires 1 12 and/or LEDs 1 1 1 .
  • the sensor subsystem 108 may be configured to report and change display status information associated with the luminaires 1 12.
  • the at least one sensor subsystem 108 may also sense and capture environmental data in real time.
  • the at least one server 106 may be connected with the gateway 102 via at least one of a wired connection and a wireless or light communication network connection.
  • the gateway 102 may be capable of discovering a dimming control protocol installed in the luminaire 1 12 and controlling at least one of the dimming levels and dimming control protocol of the luminaire 1 12. Further, the gateway 102 may be capable of controlling power to the luminaire 1 12 and may be capable of dimming the luminaire 1 12 to a minimal level or shutting it off completely. According to some embodiments, the at least one server 106 may be configured to calculate and predict depreciation of the dimming levels of the luminaires 1 12 and/or LEDs 1 1 1 . Each sensor and/or sensor subsystem 108 may be configured to report and change display status information associated with at least one luminaire 1 12.
  • the at least one sensor subsystem 108 and the at least one power meter 1 14 may each be connected with the at least one gateway 102.
  • the at least one of the plurality of luminaires 1 12 and the plurality of LED’s 1 1 1 may be physically connected to the gateway 102 via at least one dimming control interface 1 10.
  • the luminaire 1 12 may comprise a system that includes a single luminaire or multiple luminaires connected with a single common interface to power lines 120, 124.
  • a power meter 1 14 may be connected electrically between the gateway 102 and the luminaire 1 12 and may be connected electrically to the luminaire 1 12 via the power lines 120, 124.
  • the power meter 1 14 may be connected to the gateway 102 via the power meter interface 132.
  • the power meter 1 14 may be connected to an input line of the luminaire 1 12, in such a way that the power meter 1 14 measures electrical power drawn by the luminaire 1 12 at any given moment in real time.
  • the power meter 1 14 may be connected to the gateway 102 to provide real time power measurements correlated 1 -1 to luminaire 1 12 power drawn at any given moment.
  • the interface 132 between the gateway 102 and the power meter 1 14 may be a Universal Asynchronous Receiver/Transmitter (UART) or other communication interface (“power meter interface”).
  • UART Universal Asynchronous Receiver/Transmitter
  • the interface 120, 124 between the power meter device 1 14 and the luminaire 1 12 may depend on the type of power meter 1 14 being used.
  • the power meter 1 14 and power meter interface 132 may be any known power meter 1 14 and power meter interface 132 consistent with this disclosure.
  • the at least one sensor subsystem 108 may detect information related to the system 100 and the luminaires 1 12 by detecting current conditions of at least one of the luminaires 1 12.
  • the current conditions of the luminaires 1 12 may be detected such as, but not limited to, a current color level or color/light intensity, the current temperature or voltage or humidity of the like, the current dimming level, and the like.
  • the current condition information may be relayed to the gateway 102, which relays the information to the server 106 for storage, processing and the like.
  • the sensor subsystem 108 may sense/detect a plurality of color channels and monitor at least one change in environment in real time.
  • the up looking color sensor of the sensor subsystem 108 may identify an increase of fluctuation in the luminaire driver and/or LED driver or flickering. When the luminaire driver and/or LED driver fluctuates, the up looking color sensor may measure a change or disruption associated with the power supply or based on the power source.
  • the information collected by the gateway 102 may include a current power level of the luminaires 1 12 as measured by the power meter 1 14 which may measure a current power level being used by the luminaires 1 12.
  • the gateway 102 may be configured to receive information related to the luminaires 1 12 where the information includes, e.g., the color content, color/light intensity, and at least one environmental condition sensed by the sensor subsystem 108.
  • the sensor subsystem 108 may be arranged such that it connects via connection 130 to the luminaire 112 on one side and to the gateway 102 via a sensor interface 128 on another side.
  • the connection 130 to the luminaire 1 12 may comprise a physical connection and may not be limited to a specific location.
  • the location of the sensor subsystem 108 may be different for various types of sensors that are to be positioned.
  • the gateway 102 may be capable of communicating and handling the plurality of sensors and sensor protocols via its sensor interface 128. Exemplary embodiments in accordance with the present disclosure do not limit the type of hardware/wire/bus interfaces between the gateway 102 and the sensor subsystem 108, e.g., the number of wires, the type of wires or bus connectors. In some embodiments, the connections may be as simple as analog interface connectors and/or
  • the sensor or combination of sensors may measure multiple color channels (“color sensor”) by directly facing the luminaires, and may also include one or more low-resolution imaging / image sensors which may include an array of sensors combined into a low-resolution imaging device, or a single Application-Specific Integrated Circuit (ASIC) that is an imaging sensor (“environment sensor”).
  • ASIC Application-Specific Integrated Circuit
  • a low-resolution image sensor refers to a sensor that typically contains less than approximately 1200 pixels, for example, and without limitation, a 32x32 sensor.
  • the sensor may be capable of detecting and determining how many human individuals or other objects are in an environment in which the sensor is installed and the position and orientation of each individual/object.
  • the color sensor and environment sensor may be separate devices or may be combined as a single ASIC.
  • the color sensor may be used to measure, for example and without limitation, the color content and color/light intensity of a light source.
  • the color sensor can be based on a single color or a plurality of colors.
  • the environment sensor may be used for monitoring the information to be collected about the environment in which the light source is installed.
  • the environment sensor may include three or more different sensors such as a low-resolution image sensor, an ambient light sensor, and a temperature sensor.
  • the environment sensor can use other sensors and more types of sensors to characterize the environment. Without limitation, this disclosure is referring to one or more sensors included in the environment sensor as an“environment sensor”. Further, without limitation, the environment sensor may include less or more sensors than are described herein.
  • the environment sensor provided as a part of the combination of sensors may include sufficient / enough information to measure the environment, as described in this disclosure.
  • the combination of the environment sensor and the color sensor may be set into one of a single ASIC or a set of separate devices, all of which are also connected to the gateway 102.
  • the sensors may be directed as follows: the color sensor is an up looking sensor that faces the luminaire 1 12 directly, and the environment sensor is configured to faces away or in a downward direction from the luminaire in such a way that it monitors the environment. Real time measurements and assessments may be conveyed to the gateway 102 by the sensors that make up the sensor subsystem 108.
  • the environment and color sensors of the sensor subsystem 108 may be placed or connected to a fitting of the luminaire 1 12 and/or LED 1 1 1 .
  • An exact location of the sensors may not be fixed (e.g., two different luminaires by a same manufacturer of the same type of fitting and LED specifications may be assembled such that the sensor location is different relative to the surface and dimensions of the fitting).
  • the location of the color and environment sensors on the fitting may not be limited.
  • the gateway 102 may control the dimming control 1 10 and change at least one of a dimming level, a dimming protocol, and a color temperature of the luminaire 1 12, in luminaire devices that allow for color temperature control.
  • the gateway 102 may receive a set of directives or instructions for dimming setup and sensor measurements to occur at a specific day and time and/or on a specific schedule that repeats itself.
  • the sensors of the sensor subsystem 108 may be programmed via the gateway 102 such that they will provide data only in cases where a parameter such as, e.g., color intensity is outside a predefined range.
  • the gateway 102 may be controlled such that it executes measurements only when environment measurements are in a certain range, as well as when the dimming level is in a certain range.
  • the dimming parameters, the environmental reading parameters, and the sensor parameters and reading setup may all be controlled from outside of the gateway 102 via cloud servers 106 that are in data communication with the gateway 102 via backhaul interface 1 18, described below.
  • the control described with respect to the exemplary embodiments may allow the system to set up a miniature-controlled environment in which, for example and without limitation, at least one of the color content and color/light intensity of the luminaire 1 12 can be measured.
  • the system 100 may continuously receive real-time performance measurements from the sensor devices of the sensor subsystem 108 via the sensor interface 128 and power measurements from the power meter 1 14 via the power meter interface 132.
  • the gateway 102 sends these readings in a compressed format to the cloud servers 106.
  • the gateway 102 is configured to relay the information collected by the system to the at least one server 106 for processing, storage, calculating, compilation, comparing, and the like.
  • the server 106 includes a processor configured to receive and use information from the gateway 102 to calculate and predict a life expectancy of the luminaires 1 12 and/or LEDs 1 1 1 and to generate and relay a life expectancy report to a user.
  • the compressed format may include two types of messages, namely a baseline message set and an updates message set.
  • a message set may comprise any one of the baseline message and/or set of messages and the updates message set.
  • the baseline message set may include the full sensor readings, power level readings and current dimming state.
  • the updates message set may include changes or differentiations from a previous message set.
  • the baseline message set may be sent upon major change, such as a change in the dimming level, while the updates message set may be sent at regular intervals.
  • the updates message set includes readings that are significantly different from a previous set.
  • sensor readings may be averaged over the time interval between two consequent updates message sets.
  • the system 100 may include the backhaul interface 1 18 for connecting the gateway 102 and a network gateway 104.
  • the backhaul interface 1 18 comprises a mesh network.
  • the backhaul interface 1 18 may comprise a wired or wireless Local Area Network (LAN), including one or more of Mesh Bluetooth Low Energy (Mesh BLE), Smart Mesh, Bluetooth Mesh, WLAN, ZigBee, and/or Ethernet LAN.
  • the backhaul interface 1 18 may communicate via a communication protocol such as, but not limited to, a Mesh BLE protocol.
  • the gateway 102 may be connected to the back-end network 104 via LAN, WLAN, WAN, Mesh BLE radio network or other means. This connection may allow another device on the network, local to the gateway or via WAN in the cloud, to handle the lumen prediction process.
  • an entire luminaire half-life prediction process may be distributed between physical machines or on a single machine, local or remote to the gateway 102.
  • Exemplary disclosed embodiments in accordance with the present disclosure provide the system 100 that includes the gateway 102, which can interface with other control systems or devices via wired connections, Ethernet connections, wireless connections or any combination thereof, and can receive control messages that direct the gateway 102 to change at least one of a dimming level and a dimming control protocol via its dimming interface/control/driver 1 10.
  • This interface or plurality of interfaces comprise the backhaul interface 1 18 of the gateway.
  • the backhaul protocol is associated with a mesh network and is capable of delivering dimming directions to the gateway 102 as well as receiving sensor and power level readings via the sensor subsystem 108 and power meter 1 14 from the gateway 102 associated with the luminaires 1 12 managed by the gateway 102.
  • the gateway 102 may be connected to the network gateway 104, which may reside between the local networks and a wide area network (WAN) 1 16.
  • the WAN 1 16 may connect the gateway 102 to cloud servers 106 for operational and management interfaces.
  • the gateway 102 may be configured to control a plurality of dimming levels of the luminaire 1 12 and is capable of communicating sensor readings and the dimming level as well as a power reading of the luminaire 1 12 over the
  • the cloud servers 106 may be continuously receiving performance measurements from one or more gateways 102.
  • the cloud servers 106 provide each gateway 102 with a table of reading directions that include the correct sensor reading thresholds for specific dimming levels associated with the specific luminaire 1 12.
  • the gateway 102 may only need to report changes or deviations from this internal table to the cloud servers 106.
  • the system 100 may further reduce an amount of information that needs to be transmitted over the gateway 102 to backhaul interface 1 18. In this way, the cloud server applications may control the rate of information sent by the gateway 102 and more accurately predict the LED 1 1 1 behavior.
  • the system 100 may send sensor readings and other information over the backhaul interface 1 18 to the cloud server 106 at random times. This may allow for better utilization of the backhaul interface 1 18.
  • messages being sent at random time periods during the day may include a correct time stamp of the measurement or reading and the sensor reading (e.g., dimming level). Because of a delay in transmission, the message receiving time at the cloud server 106 may not correlate with the actual time that the measurement was taken. Thus, in an aspect, the measurement is tagged with a time of measurement.
  • the use of a mesh network as the backhaul interface 1 18 and the likely numerous gateways 102, luminaires 1 12, and sensors per gateway 102 may provide an opportunity to implement an interference mitigating protocol to ensure more timely and successful message and data packet delivery for managing the luminaire loT system.
  • FIG. 3 is a high-level system diagram of a mesh network 300 implemented in any wired or wireless network system, according to certain exemplary disclosed embodiments.
  • the exemplary disclosed embodiments may relate to a system for managing a dynamic tunneling protocol in a mesh network and determining a best path through the mesh network for implementing the dynamic tunneling protocol.
  • the mesh network 300 comprises at least one network server 340 connected with a gateway 350 and at least one tunnelling network routing protocol.
  • the system may be configured to determine a specific or best path to transmit data packets via a tunnelling network protocol from an originator station 310 to a target station 320.
  • the system may be further configured to identify and collect path information from all nodes in a mesh network 300 during normal operation of the mesh network 300.
  • the path information that is collected may include a rate that data packets are received in an ordered sequence based on measuring one or more, or combination of factors such as, time of arrival of the data packets, time of origination of the data packets, and/or a distance of the path from the originator station 310 to the target station 320.
  • the system may be configured to identify one or more high density data packets originated from the originator stations 310.
  • the collection of information such as, a time of arrival while collecting path information for messages from every node during normal operation of the mesh network 300.
  • the collected information may also include a time of origination and may measure a time of arrival and measure the path.
  • the mesh network 300 may be further configured to assign and/or store the specific or best path via one or more nodes for transmission of the one or more high density data packets from the originator station 310 to the target station 320 based on the collected path information.
  • the best path information may be stored at a coordinating node 330 that may not only store information about best paths through the mesh network 300 but may also send a start message to initiate a dynamic tunneling protocol and may send a close message to stop the dynamic tunneling protocol and to restart normal operation of the mesh network 300.
  • a best path may include exiting and reentering the mesh network 300 via the internet.
  • the mesh network 300 may be configured to manage multiple applications and profiles for implementing a dynamic tunneling operation in the mesh network 300.
  • FIG. 4 an exemplary diagram of assigned nodes for transferring data packets between an originator station 410 (e.g., data associated with a high bandwidth application) to a target station 420 in a mesh network 400 is shown.
  • multiple applications may be used to manage dynamic tunneling operations.
  • a management module may provide an interface to set up identification for one or more high bandwidth applications and to associate them with a specific node (e.g., a node location within the mesh network).
  • an automatic discovery mechanism may automatically discover the application and a node that the application is associated with (e.g., where the application is installed or a node that the application communicates through). For example, in a case that a high definition camera is connected to the mesh network, this system may identify this device as being associated with a high bandwidth application that transmits high density packets (e.g., high definition video).
  • the high bandwidth application may utilize a trigger that indicates to the mesh network that the application needs more bandwidth.
  • the trigger may be implemented by transmitting a message that the application needs more bandwidth where the message may further indicate a duration (e.g., how long the application will require more bandwidth).
  • the message may be received at a node (e.g. a coordinating node) and the node may initiate dynamic tunneling operations. For example, the node may send a tunneling start message with a timeout to all of the nodes in the mesh network.
  • the tunneling start message may include a best path for data to be transmitted.
  • the tunneling start message also called a setup message, may be sent from a coordinating node or, in some embodiments, the tunneling start message may be transmitted directly from an originator station or an application residing on one or more nodes that is in need of high bandwidth. In some embodiments, the tunneling start message may be received at the nodes assigned to the best path thereby allowing tunneling to start and for messages to be transmitted along the best path at a higher bandwidth.
  • the system may terminate the dynamic tunneling protocol based on a tunneling close message once the high density data packets have reached their destination (e.g., a target node or gateway).
  • the tunneling start message may be received at nodes that are not associated with the best path and in response to receiving the tunneling start message, the nodes that are not associated with the best path may remain silent and may not transmit or forward messages. Messages received at the nodes that are not associated with the best path may be stored in a cache for later transmission or may simply be dropped.
  • FIG. 5 illustrates an exemplary diagram associated with an initiated dynamic tunneling protocol via a message generated for transferring data packets from an originator station 510 to a target station 520 in the mesh network 500.
  • the generated message may be configured to activate the specific nodes in the best path and to inactivate the nodes other than the specific nodes until the high density data packets have been received by the target station 520.
  • FIG. 6 illustrates an exemplary diagram associated with re-activated nodes after transferring data packets from an originator station 610 to a target station 620 in the mesh network 600.
  • the system may be further configured to re-activate all the nodes in the mesh network 600 once the high density data packets have been received by the target station 620. Further, the system may maintain pre-determined best paths via specific nodes to receive the high density data packets at all times from one or more originator station 610 to one or more target station 620.
  • the exemplary mesh network 600 shown in FIG. 6 may include, but is not limited to, a wired or wireless mesh network, a set of wired switches, a wireless mesh, or any light (e.g., VLC/DLC) communication network.
  • the dynamic tunneling protocol may be initiated after determining the best path through the mesh network 600.
  • the dynamic tunneling protocol may be initiated in conjunction with determining the best path through the mesh network 600 and the best path may be dynamically determined.
  • the system may be configured to identify and collect path information from all nodes during normal operation of the mesh network 600. For example, the system may collect data rates associated with an ordered sequence of data packets that have been received by measuring one or more factors associated with the data packets.
  • the factors may include information such as, but not limited to, times of arrival of the data packets, time of origination of the data packets, and the distance of the path from the originator station to the target station.
  • the system may be configured to assign the best path for transmitting high density bandwidth information based on the collected path information.
  • the system further constantly measures times of arrival associated with data packets during transmission of high density data packets so that the best path may be dynamically changed during transmission of the packets when a slowdown associated with a specific node is determined.
  • the system may generate a second setup message that indicates an alternate path (e.g., an alternate best path)
  • the nodes may include, but are not limited to, any gateway, router, or originator/application that transmits high density memory data packets such as images, video streaming, or HD videos, etc.
  • the system may be configured to generate a setup message across the nodes in the mesh network to enable the best path for transferring high density data packets using a dynamic tunneling protocol.
  • the setup message may include a forwarding identification (ID) of a set of specific nodes using normal protocol interfaces to transfer data packets/high density data packets.
  • the setup message may include a hop by hop ID to transfer the data packets between the specific nodes (e.g. instruction to send the message from node A to node B and then to node C).
  • the system may optionally be configured to transmit a separate control message to pause all activity which is particularly applicable for wireless and/or light-based mesh network systems.
  • the best path of the message may be truncated after every hop in the implemented mesh network. For example, after being sent from node A to node B, the header may be truncated to remove node B prior to the message being sent to node C.
  • the sending of messages is initiated at a high bandwidth where the data packets will be forwarded via the nodes associated with the best path.
  • the system is further configured to re-activate all the nodes in the mesh network after the high density data packets are received by the target station. Further, the system may maintain pre-determined best paths via specific nodes to receive the high density data packets at all times from one or more originator station to one or more target station. In some embodiments, except from the identified nodes associated with the best path, the remaining nodes of the mesh network may stop sending or forwarding messages after an allowed time with some delta constant.
  • FIGS. 7A and 7B show an exemplary method 700 for managing and controlling a dynamic tunneling protocol associated with network hardware devices in a mesh network.
  • the multiple applications and their associated profiles for managing dynamic tunneling operation may be managed in a mesh network.
  • an interface may be provided to identify an application (and a location of the application) in the mesh network.
  • the interface may provide a means for a user to enter in information associated with an application (e.g. a name, an executable file, etc.) and a node (or nodes) associated with the application to register the application with a coordinating node or controller.
  • the system may also allow for automatic discovery of the application based on, for example, an application name, a file type or an identification of a type of device installed at the node (e.g., a high definition camera).
  • the system may then associate the discovered application with a node or nodes (e.g., a node connected to the application).
  • Each application entered (or discovered) may use an auto-trigger that is driven by the application in a case that the application requires more bandwidth at 740.
  • the application at 750, may generate and transmit a message to indicate that the application is in need of higher bandwidth and a time duration for this requirement.
  • This trigger message may initiate a tunneling start message that includes a timeout to the nodes associated with the best path at 760.
  • the trigger message may be transmitted across the mesh network to initiate a dynamic tunneling protocol.
  • the trigger message may be received at a coordinating node and in response to receiving the trigger, the coordinating node may initiate a tunneling start message to enable the dynamic tunneling protocol.
  • the tunneling start message transmitted across the nodes may enable the best path by using a specific set of nodes that may include a forwarding ID (hop by hop route ID) of the specific set of nodes in a header of the tunneling start message.
  • the tunneling start message may be truncated after every hop. For example, the hop by hop route ID is changed to remove each node from the hop to hop route ID after that node received the message.
  • identifying or determining the best path to implement the dynamic tunneling protocol in the mesh network may be based on historic and/or current data associated with actual use of the mesh network or combinations thereof.
  • each path between the originator and the destination may be analyzed using current data (e.g.,.
  • the current and historic data may be collected during normal (e.g., actual) operation of the mesh network and may include, but is not limited to, times of arrival of data packets, times of origination of the data packets, data rates, and distances along one or more paths between an originator station and a target station.
  • the current and historical data may be stored at a coordinating node.
  • the system may automatically indicate specific nodes as being associated with a high bandwidth application.
  • a node that is indicated as comprising a high-resolution camera may automatically be indicated as having a high bandwidth application.
  • the high-density data packets may be received via the specific nodes at 770.
  • the system may send a close message to stop the dynamic tunneling protocol at 780.
  • the nodes of the mesh network may revert to their normal operation.
  • the system and method further comprises a transmission means for changing the transmission of data packets along a different path and/or at a different time based on the current and historical data associated with a current path such that the data packets are received in the ordered sequence at the target station in the mesh network.
  • the system further comprises storage means for storing the current (e.g. real time or near real time) and historical data in a data storage (e.g. a database, a table, etc.).
  • a calculation means e.g. a processor
  • the system further comprises calculation means (e.g. a processor) for determining factors such as, but not limited to, the time of arrival, time of origination of the data packets along a plurality of different paths between the originating station and the target station in the mesh network.
  • the system further comprises calculation means (e.g., the processor) for measuring a time of transmission of data packets along a plurality of different paths in an ordered sequence between the originating station and the target station in the mesh network.
  • the system further comprises selecting means (e.g., the processor) for selecting a best path through the mesh network for transferring one or more high density data packets between the originating station and the target station.
  • the system comprises plurality of nodes wherein at least one of the plurality of nodes comprises a coordinating node that is used to activate specific path/route information to other nodes on request. Further, in some embodiments, the system comprising plurality of nodes may use the coordinating node to deactivate a best path and/or its associated information on request.
  • the system may be configured to reduce a number of hops through the mesh network by initiating the dynamic tunnelling network protocol along the specified best path.
  • the specified best path may be associated with more than one source nodes and/or more than one destination node in the mesh network.
  • the specified best path may be assigned by a coordinating node, one or more targeting stations in the mesh network or by one or more originating stations in the mesh network.
  • the best path may be selected with consideration to the information on the distances between the originating station and the target station in the mesh network.
  • each path through the mesh network may be selected with consideration to the information on the number of nodes between the originating station and the target station in the mesh network.
  • the mesh network comprises a coordinator node, wherein the coordinator node is configured to store the path information on the distances between the originating station and the target station in the mesh network.
  • the coordinator node may be configured to store the route information associated with the number of nodes between the originating station and the target station in the mesh network.
  • the stored path/route information may change in response to messages generated by the coordinator node.
  • the originating station may not be the coordinator node and the originating station may request path information to a target station nodes via one or more coordinator nodes.
  • the coordinator nodes may send path information to the originating station.
  • the coordinator node may send best path information after initiating a dynamic tunnelling protocol to receive high density data and the coordinator node may comprise any one of assigned nodes during deployment of mesh network.
  • the coordinator node may comprise one or more gateways, one or more routers, or any of the network hardware devices.
  • the originating station/source node may not be the coordinator node, the originating station/source nodes may request path/route information from a target station/destination nodes via one or more coordinator nodes. Thereby, the coordinator nodes may send path information to the originating station/source nodes. In some embodiments, the coordinator node may send specific path information via initiating a dynamic interference mitigating protocol to receive high density data packets from applications such as video/image data to the originating station/source nodes. In some embodiments, the coordinator node may comprise any one of assigned nodes during deployment of the mesh network. In some embodiments, the coordinator node may comprise one or more gateways, one or more routers, or any of the network hardware devices.
  • the coordinating node may comprise a processor, such as one or more commercially available Central Processing Units (CPUs) in the form of one-chip microprocessors, coupled to a processor, such as one or more commercially available Central Processing Units (CPUs) in the form of one-chip microprocessors, coupled to a processor, such as one or more commercially available Central Processing Units (CPUs) in the form of one-chip microprocessors, coupled to a processor, such as one or more commercially available Central Processing Units (CPUs) in the form of one-chip microprocessors, coupled to a
  • CPUs Central Processing Units
  • the processor may communicate with a memory/storage device that stores data.
  • the storage device may comprise any appropriate information storage device, including combinations of magnetic storage devices (e.g., a hard disk drive), optical storage devices, and/or semiconductor memory devices.
  • the storage device may store a program and/or processing logic for controlling the processor.
  • the processor performs instructions of the programs and thereby operates in accordance with any of the embodiments described herein.
  • the programs may be stored in a compiled, compressed, uncompiled and/or encrypted format or a combination.
  • the programs may furthermore include other program elements, such as an operating system, a database management system, and/or device drivers used by the processor to interface with peripheral devices.
  • the present disclosure in various embodiments, configurations and aspects, include components, methods, processes, systems and/or apparatus substantially developed as depicted and described herein, including various embodiments, sub-combinations, and subsets thereof. Those of skill in the art will understand how to make and use the present disclosure after understanding the present disclosure.
  • the present disclosure in various embodiments, configurations and aspects, include providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments, configurations, or aspects hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and/or reducing cost of implementation.
  • phrases“at least one”,“one or more”, and“and/or” are open-ended expressions that are both conjunctive and disjunctive in operation.
  • B, and/or C means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
  • a value modified by a term such as “about” is not to be limited to the precise value specified. In some instances, the approximating language may correspond to the precision of an instrument for measuring the value. Terms such as “first,”“second,”“upper,”“lower”, etc. are used to identify one element from another, and unless otherwise specified are not meant to refer to a particular order or number of elements.
  • the word“comprises” and its grammatical variants, such as“including”, and “having” logically also subtend and include phrases of varying and differing extent such as for example, but not limited thereto,“consisting essentially of and“consisting of.” Where necessary, ranges have been supplied, and those ranges are inclusive of all sub-ranges there between. It is to be expected that variations in these ranges will suggest themselves to a practitioner having ordinary skill in the art and, where not already dedicated to the public, the appended claims should cover those variations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Selon certains modes de réalisation, l'invention concerne un système et un procédé de gestion d'une tunnellisation dynamique dans un réseau maillé. Le procédé suppose d'associer une application qui transmet des paquets de données à haute densité à un premier nœud d'une pluralité de nœuds dans un réseau maillé. Le premier nœud de la pluralité de nœuds fait office de station d'origine destinée à transmettre les paquets de données à haute densité à un second nœud de la pluralité de nœuds dans le réseau maillé qui fait office de station cible. Un déclenchement automatique devant être initié par l'application lorsqu'elle nécessite plus de bande passante est créé. En réponse à l'activation du déclenchement automatique, un message est généré parmi la pluralité de nœuds de façon à activer le meilleur trajet à travers le réseau maillé, le message indiquant une durée pendant laquelle l'application nécessitera plus de bande passante.
EP19726732.1A 2018-03-29 2019-03-29 Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé Withdrawn EP3777327A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201862649868P 2018-03-29 2018-03-29
US16/264,915 US10917254B2 (en) 2018-02-07 2019-02-01 System and method of utilizing an interference mitigating protocol in mesh networks
PCT/IB2019/052631 WO2019186506A1 (fr) 2018-03-29 2019-03-29 Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé

Publications (1)

Publication Number Publication Date
EP3777327A1 true EP3777327A1 (fr) 2021-02-17

Family

ID=68060981

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19726732.1A Withdrawn EP3777327A1 (fr) 2018-03-29 2019-03-29 Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé

Country Status (4)

Country Link
EP (1) EP3777327A1 (fr)
CN (1) CN112205033A (fr)
WO (1) WO2019186506A1 (fr)
ZA (1) ZA202006419B (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115568079B (zh) * 2022-11-14 2023-03-07 四川九通智路科技有限公司 基于隧道传感器数据的智慧照明能耗监测方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8958417B2 (en) * 2007-06-26 2015-02-17 Aruba Networks, Inc. Method and system for call admission control in a wireless mesh network
US20130136033A1 (en) * 2011-11-28 2013-05-30 Abhishek Patil One-click connect/disconnect feature for wireless devices forming a mesh network
US10097449B2 (en) * 2015-02-20 2018-10-09 Cisco Technology, Inc. Optimized border gateway protocol best path selection for optimal route reflection
GB201611513D0 (en) * 2016-03-11 2016-08-17 Gooee Ltd Colour based half life prediction system

Also Published As

Publication number Publication date
CN112205033A (zh) 2021-01-08
ZA202006419B (en) 2021-07-28
WO2019186506A1 (fr) 2019-10-03

Similar Documents

Publication Publication Date Title
US11038715B2 (en) System and method for identifying specific/best path in a mesh network
US10917254B2 (en) System and method of utilizing an interference mitigating protocol in mesh networks
US10841201B2 (en) System and method for managing and controlling a dynamic tunneling protocol in a mesh network
CA3018453C (fr) Suivi d'actif employant des balises sans fil actives qui produisent un rapport sur un reseau local de balises connectees
US20160120144A1 (en) Livestock house management system and management method thereof
CA2982946C (fr) Mise a jour hertzienne de maille au moyen du profil du site fonde sur plusieurs images de plateforme
US10205606B2 (en) Mesh over-the-air (OTA) luminaire firmware update
US11997775B2 (en) Communication device
CN104160786A (zh) 照明系统以及提取照明系统状态信息的方法
US9888298B2 (en) System, communications node, and determining method
US20160095182A1 (en) Light control monitoring system
US9654933B2 (en) Systems and methods for synchronizing optical transmitters
WO2019099488A1 (fr) Optimisation heuristique des performances d'un réseau nodal radiofréquence
JP4487211B2 (ja) 接続制御装置及び、ネットワーク接続制御プログラム
CA2970362C (fr) Mise a niveau de progiciel de luminaire maille sans fil
US9629225B2 (en) Apparatus and method for interpreting received control commands
WO2019186506A1 (fr) Système et procédé de gestion et de commande d'un protocole de tunnellisation dynamique dans un réseau maillé
GB2574307A (en) System and method for managing and controlling a dynamic tunneling protocol in a mesh network
WO2019186508A1 (fr) Système et procédé de gestion et de commande d'un protocole de transmission tunnel dynamique dans un réseau maillé
GB2574308A (en) System and method for managing and controlling a dynamic tunneling protocol in a mesh network
GB2572479A (en) System and method of utilizing an interference mitigating protocol in mesh networks
US11297571B2 (en) Controlling end nodes of a low-power wide area network
JP2008294771A (ja) 集中管理システム、論理ネットワーク情報設定方法および集中管理装置
KR20080021278A (ko) 센서 네트워크에서 전원 상태 정보를 이용한 데이터 통신장치 및 그 방법

Legal Events

Date Code Title Description
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: 20201030

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 MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

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: GOOEE LIMITED

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20210615