US20150245369A1 - Communicating data over a mesh network - Google Patents
Communicating data over a mesh network Download PDFInfo
- Publication number
- US20150245369A1 US20150245369A1 US14/505,437 US201414505437A US2015245369A1 US 20150245369 A1 US20150245369 A1 US 20150245369A1 US 201414505437 A US201414505437 A US 201414505437A US 2015245369 A1 US2015245369 A1 US 2015245369A1
- Authority
- US
- United States
- Prior art keywords
- communication device
- schedule
- broadcast
- transmit
- mesh network
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/73—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information by creating or determining hardware identification, e.g. serial numbers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/76—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in application-specific integrated circuits [ASIC] or field-programmable devices, e.g. field-programmable gate arrays [FPGA] or programmable logic devices [PLD]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
- G06Q10/0833—Tracking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04H—BROADCAST COMMUNICATION
- H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
- H04H20/65—Arrangements characterised by transmission systems for broadcast
- H04H20/71—Wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/06—Generation of reports
- H04L43/065—Generation of reports related to network devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0882—Utilisation of link capacity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- 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/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/11—Identifying congestion
- H04L47/115—Identifying congestion using a dedicated packet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/16—Flow control; Congestion control in connection oriented networks, e.g. frame relay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/15—Interconnection of switching modules
- H04L49/1553—Interconnection of ATM switching modules, e.g. ATM switching fabrics
- H04L49/1584—Full Mesh, e.g. knockout
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1475—Passive attacks, e.g. eavesdropping or listening without modification of the traffic monitored
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1491—Countermeasures against malicious traffic using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0877—Generation of secret information including derivation or calculation of cryptographic keys or passwords using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/18—Network planning tools
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/06—Testing, supervising or monitoring using simulated traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
- H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/38—TPC being performed in particular situations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
- H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/02—Inter-networking arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/77—Graphical identity
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- This invention relates to an apparatus and method for communicating data over a mesh network.
- FIG. 1 shows a distributed network.
- the network comprises a number of communication devices 101 , 103 , 105 and 107 .
- Each device can communicate wirelessly with the other devices that are in effective range of it.
- the network is a mesh network and each device relays data for the network.
- the devices can communicate to propagate data between them. For example, if device 101 transmits a signal, that signal can be received by devices 103 and 107 which are within range of device 101 .
- Device 103 can then relay the signal received from device 101 so that it can be received by device 105 , which is out of range of device 101 .
- the coverage area of device 101 is illustrated at 108 and the coverage area of device 105 is illustrated at 109 .
- This method of communication allows devices to communicate even though they are out of direct range or not synchronised with each other.
- Each device may also be connected to, or integrated within, an associated consumer device. So device 101 is connected to a sensor that detects whether window 102 is open or closed, and devices 103 and 105 are connected to light fittings 104 and 106 respectively.
- the routing tables store routes from one network device to another so that messages can be propagated from source to destination via a series of hops.
- the topology of the network has to be known in order that routes between the various devices can be determined and stored.
- An alternative is flood routing. In this method messages do not travel from one device to another via a predefined route. Instead messages are broadcast and any device in range that receives a message retransmits it. A message thus propagates its way through the network, potentially reaching its destination via a number of different routes.
- Flood routing is very simple to implement and although it may appear inefficient has a number of advantages, particularly for ad hoc networks that may change their topology on a random basis.
- a communication device capable of operating in a mesh network and configured to transmit data to a destination device by encapsulating that data in a broadcast packet and transmitting it over the mesh network in order that another communication device, on receiving the broadcast packet, may forward it towards the destination device, the communication device being further configured to: establish a schedule for transmitting data encapsulated in broadcast packets; transmit information defining that schedule over the mesh network; and subsequently transmit the broadcast packets in accordance with that schedule.
- the communication device may be configured to encapsulate non-audio data in the broadcast packets.
- the communication device may be configured to encapsulate control data in the broadcast packets.
- the communication device may be configured to transmit the broadcast packets over a channel that implements frequency hopping.
- the communication device may be configured to transmit the broadcast packets by transmitting each broadcast packet on a different frequency from the preceding broadcast packet.
- the communication device may be configured to transmit the information defining the schedule over a different channel from the broadcast packets.
- the communication device may be configured to transmit information that defines the timing and frequency of the schedule.
- the communication device may be configured to broadcast the information defining the schedule over the mesh network.
- the communication device may be configured to transmit the information defining the schedule over a connection with another communication device.
- the communication device may be configured to terminate the connection with the other communication device once it has transmitted the information defining the schedule.
- the communication device may be configured to establish a schedule under which the communication device transmits broadcast packets that encapsulate the same data for the same destination device at different time instants.
- the communication device may be configured to transmit the broadcast packets over a Bluetooth Low Energy isochronous channel.
- the communication device may be configured to encapsulate data for transmission over the mesh network in a Bluetooth Low Energy advertising packet.
- a communication device capable of operating in a mesh network and having a scan mode in which it listens for broadcast packets on the mesh network, said broadcast packets encapsulating data that is intended for a destination device, and forwards any such broadcast packet towards the respective destination device, the communication device being configured to: obtain information that defines a schedule according to which another communication device may transmit broadcast packets over the mesh network; and enter scan mode and listen for broadcast packets at times defined by the schedule.
- the communication device may be configured to not enter scan mode at times that are not defined by the schedule.
- the communication device may be configured to obtain information defining the schedule by listening for a broadcast packet that defines that schedule.
- the communication device may be configured to obtain information defining the schedule by connecting with the other communication device.
- the communication device may be configured to disconnect from the other communication device once the information defining the schedule has been received.
- the communication device may be configured to enter scan mode and listen for broadcast packets when it is not connected to the other communication device.
- FIG. 1 shows an example of a distributed network
- FIGS. 2 a to 2 c show examples of communication devices and a method of operating the same
- FIGS. 3 a and 3 b show an example of a mesh network
- FIG. 4 shows an example of a communication channel
- FIG. 5 shows an example of a communication device.
- FIG. 2 a shows an example of a communication device.
- the communication device is generally configured for transmitting data over a mesh network.
- the communication device may be configured for wireless communication, although wired configurations are also possible. This is represented generally by output 201 .
- output 201 In a wireless network data is transmitted via radio signals.
- data In a wired implementation, data may be transmitted via electrical signals. Most commonly data may be arranged in “packets” incorporating payload data and some indication of the source device and the destination devices.
- the communication device may be configured to operate in accordance with a communication protocol that governs communications across the mesh network.
- a communication protocol that governs communications across the mesh network.
- the communication protocol defines a broadcast packet type.
- a broadcast packet is one that is not addressed to any one particular device, and thus can be received by any device in the network that is within range.
- the communication device comprises a transmit unit 202 , which is configured to transmit data over the mesh network in accordance with the protocol.
- the transmit unit comprises a broadcast unit 203 , which is configured to encapsulate data in broadcast packets. Suitably that data is control data.
- the data is usually intended for a particular subset of one or more devices in the mesh network.
- the broadcast unit identifies these destination devices in the broadcast packet, it may not establish a connection with those devices. Indeed, in many instances the communication device will be out of range of one or more of the destination devices. Instead, the transmission unit broadcasts the packet in the hope that another device in the mesh network, acting as a relay, will receive the packet and forward it on to its destination.
- the communication device is thus configured to operate in a mesh network that utilises flood routing to transport data between source and destination devices.
- Flood routing implies that all devices should listen continuously for signals from other devices in the network, otherwise there is a risk that data might not reach its destination. There are three main reasons why it may be impractical for a mesh communication device to spend significant amount of time listening for packets. The first is the cost in power. The second is the physical impossibility for many devices of receiving at the same time as transmitting. The third is the need to perform other functions outside of the network, which may not be possible while listening for packets. Time that a communication device saves by not listening for packets may be spent performing other functions or in a low power mode to conserve battery life.
- relay devices decide unilaterally when to listen for packets, there is a risk that none of them will be listening when a particular packet is broadcast, and the packet may be dropped. Having some form of direct coordination between neighbouring relay devices might help to avoid listening gaps but could add undesirable complexity, particularly in an ad hoc mesh in which a relay device's neighbours may change with time. An indirect form of coordination may therefore be beneficial.
- the communication device that is transmitting the broadcast packets may establish a transmission schedule.
- the relay devices may choose to listen to those packets or not (retaining their unilateral behavior), but having a mesh device transmit its broadcast messages at set times enables a relay device to tailor its listening windows to those times when there might actually be a broadcast packet for it to relay.
- relays may reduce their power consumption without missing packets.
- the relays might reduce their power consumption still further by listening to only a subset of the transmission slots. This introduces a risk that a packet might be dropped.
- multiple relays, independently selecting which slots to listen to might, as a group, end up listening to all slots.
- the likelihood that all slots will be listened to can be improved still further by the transmitting device communicating information about different subsets of its transmission slots to different relay devices. This is described in more detail below.
- the communication device comprises a scheduler 204 for establishing a schedule for the transmission unit to transmit data encapsulated in broadcast packets over the mesh network.
- Transmit unit 202 may be configured to transmit information defining the schedule over the mesh network. Subsequently the transmit unit may establish a channel that embodies the schedule and transmit the broadcast packets over that channel.
- FIG. 2 b shows another example of a communication device.
- the communication device is generally configured for receiving data over the mesh network.
- the communication device may be configured to act as a relay.
- the communication devices represented by FIGS. 2 a and 2 b may be implemented together as part of one device that is capable of transmitting and receiving data over the mesh network.
- the communication device shown in FIG. 2 b will usually be configured for wireless communication, although wired configurations are also possible.
- This is represented generally by output 205 .
- the communication device may be configured to operate in a number of different modes, including a scan mode.
- the communication device comprises a mode controller 206 for controlling operation of a transceiver 207 in dependence on the current mode of operation. In scan mode, the mode controller 206 may control the transceiver 207 to listen for broadcast packets on the mesh network. These broadcast packets may encapsulate data that is intended for a destination device, which often may not be the communication device itself.
- the communication device may be configured to act as a relay in the mesh network by forwarding any broadcast packets intended for a different device towards their destination.
- the communication device may comprise a relay unit 208 for controlling the transceiver to retransmit any such packets.
- the mode controller may also comprise a timing unit 209 for determining when the communication device should change from one operating mode to another, e.g. for determining when the communication device should wake from a sleep mode and enter the scanning mode.
- the timing unit 209 may be configured to obtain information that defines a schedule according to which another communication device may transmit broadcast packets over the mesh network.
- the mode controller 206 may be configured to control the transceiver to enter scan mode and listen for broadcast packets during the time slots defined by that schedule.
- FIGS. 2 a and 2 b are intended to correspond to a number of functional blocks in an apparatus. This is for illustrative purposes only. FIGS. 2 a and 2 b are not intended to define a strict division between different parts of hardware on a chip or between different programs, procedures or functions in software. In some embodiments, some or all of the algorithms described herein may be performed wholly or partly in hardware. In many implementations, at least part of transmit unit 202 , broadcast unit 203 , scheduler 204 , mode controller 206 , transceiver 207 , relay unit 208 or timing unit 209 may be implemented by a processor acting under software control (e.g. the CPU of a communication device). Any such software may be stored on a non-transient computer readable medium, such as a memory (RAM, cache, hard disk, etc.) or other storage means (USB stick, CD, disk, etc.).
- a non-transient computer readable medium such as a memory (RAM, cache, hard disk, etc.) or other storage
- relay is not intended to be limiting to devices that are specifically operating as a relay, however, as a device that is the destination for a particular broadcast packet may still operate in the same way with respect to listening for that packet as a device that relays the packet. Thus actions described as being performed by a “relay” might equally be performed by a generic “receiving device”.
- the transmitting device establishes a schedule for transmitting its broadcast packets (step S 201 ).
- the transmitting device then communicates this schedule over the mesh network (step S 202 ).
- this schedule may be communicated.
- the schedule may be communicated directly to a particular mesh device.
- the schedule may simply be broadcast so that it can be intercepted by one or more mesh devices. (This is described in more detail below.)
- the transmitting device may communicate the entirety of its schedule or only selective parts of it. For example, the transmitting device may communicate different parts of its schedule to different mesh devices to increase the likelihood that all of its transmission schedule will be listened to.
- step S 203 the schedule is received by the relay device.
- the relay device may then align its listening windows to the transmit schedule (step S 204 ). In most implementations it may be up to the relay device to decide how many of the transmission slots it wants to listen to. Thus while the transmitting device is able to improve the chances of its broadcast packets being relayed by communicating its schedule, in some implementations the relays may still unilaterally decide when it wants to listen. In some implementations, however, the relay device may be mandated to listen to specified transmission slots.
- step S 205 the transmitting device transmits its broadcast packets over a communication channel that embodies its transmit schedule. The relay device listens according to its own listening schedule (step S 206 ), and if it receives a broadcast packet intended for another device, rebroadcasts it (step S 207 ).
- FIG. 3 represents a house having a distributed lighting system.
- the system comprises a light switch unit 301 and light fittings 302 , 303 , 304 , 305 .
- Light switch unit 301 is integrated with a wireless communication device 312 .
- Light fittings 302 to 305 are integrated with respective wireless communication devices 306 , 307 , 308 , and 309 .
- the house has a mains electrical supply which powers the light fittings and their respective wireless communication devices 306 to 309 .
- Light switch unit 301 and its wireless communication device 312 are powered by a local battery 311 .
- the house contains other items of equipment that contain other wireless communication devices.
- a tablet computer 310 which contains a wireless communication device 313
- a mobile phone 315 which contains a wireless communication device 316 .
- a sensor 320 for detecting the open/closed state of window 318 , which contains communication device 319 .
- Computer 310 , phone 315 and sensor 320 are powered by batteries 314 , 317 and 321 respectively.
- Wireless communication devices 306 to 309 , 310 , 315 and 319 operate according to the same wireless communication protocol. That could be a relatively short-range protocol. For example the effective range of each device could be less than 35 m. That characteristic can permit the devices to use less power for transmitting and/or receiving than would be expected in a longer range protocol.
- the protocol could be one that imposes no common time-base at or below the transport level, or below the application or presentation levels. In other words, the devices in the network operate asynchronously of each other. That characteristic can reduce the devices' power consumption by reducing their for need accurate clocks running continuously.
- the devices could operate according to the Bluetooth protocol, specifically the Bluetooth Low Energy protocol (BLE).
- BLE Bluetooth Low Energy protocol
- Devices 306 to 309 are configured cooperatively in order that the light fittings 302 to 305 know to respond to signals from the light switch 301 . This may be done by the devices 306 to 309 storing a common identification code in their respective non-volatile memories.
- the identification code may be stored in the light switch when it is manufactured, and stored in the light fittings at the time they are installed in the house. They may be stored in the light fittings by means of another device such as mobile phone 315 communicating with the wireless device of the light switch to read its identification code, and then communicating with the wireless devices of the light fittings to cause them to store that same identification code.
- This code may be a network key, and it may be used to sign all packets sent over the network.
- the network may also be configured to implement flood routing, which is well suited to ad hoc networks.
- the phone 315 and the tablet computer 310 are both portable devices that change location within the network as a user picks them up and moves them. They may also occasionally leave the network and then reappear some time later. For example, when a user takes them out of range of the network by taking them out of the house and later returns them to the house.
- the network's topology is thus subject to random alteration.
- Some of the communication devices may act as master devices, while others of the communication devices may act as slave devices. Some devices may always have the same role; communication device 319 of sensor 320 attached to window 318 might always act as a slave, for example. Other devices such as communication device 316 in mobile phone 315 may be capable of swapping between master and slave roles or of acting as a master and a slave at the same time. Master devices, for example, might act as slaves to other master devices. Master/slave arrangements can result in a full mesh node having significantly lower power consumption requirements than other mesh designs.
- Each communication device may be capable of acting as a relay in the network.
- An example of this is shown in FIG. 3 b , which shows the same distributed lighting system as FIG. 3 a .
- the network is configured as a mesh network so, at least in theory, all devices that are part of the network have a responsibility to act as relays.
- a relay device suitably retransmits any packet that it recognises as having originated from the network (e.g. because it has been signed using a network key).
- the relay device might also take steps to prevent old packets from being continuously bounced around the network, e.g. by only forwarding the packet if it is new and/or by decrementing a “time-to-live” value in the packet before forwarding it on.
- Light switch 301 transmits a packet addressed to all of devices 306 to 309 instructing light fittings 302 to 305 to switch on. This packet is propagated by all devices that receive it, eventually reaching light fitting 305 , which is out of range of light switch 301 , the source of the packet.
- both device 316 and device 319 are capable as acting as relays, they are both battery powered and would prefer to reduce power consumption where possible. Therefore, one or both of those devices may deliberately reduce their receive power. For example, if device 316 communicates its transmit schedule to device 319 , then device 319 can reduce its listening time by only entering scan mode during device 316 's scheduled transmission slots. Thus it will still receive packets broadcast by device 316 but is able to save power by significantly reducing its receive windows.
- a transmitting device's scheduled transmission slots can be considered to embody a “communication channel”. This channel may be termed an “isochronous channel” because it schedules communications to occur at set times. Isochronous channels allow for time predictable transmission and reception slots. A particular sequence of time slots might represent a particular physical channel.
- An isochronous channel might be used as a uni-directional broadcast channel.
- Device A might transmit data in broadcast packets at set times on an isochronous channel.
- Device B might listen to the isochronous channel at the set times to receive Device A's broadcast packets.
- Device A and Device B do not need to be connected with each other to do this. All that is required is for one device to know when it should listen for broadcasts from the other.
- Another option is for Devices A and B to use the set times on the isochronous channel as a bi-directional broadcast channel, which they both transmit and receive on (e.g. by each device having the right to transmit on alternate slots).
- a transmitting device may be configured to use just one isochronous channel or multiple isochronous channels.
- a transmitting device that is acting as a “master” or “central” device may use multiple isochronous channels to communicate with its slaves. Each channel may be designated for broadcasting to a particular slave.
- a master device is normally limited in the number of connections it can support simultaneously with its slave devices.
- An advantage of broadcasting data over isochronous channels is that it allows many slaves to be synchronised with the same master without all having to be connected to the master. This is because all the slave devices need to be able to synchronise with the isochronous channel is the timing of the transmission slots and the frequency of the channel. It does not need to be connected to the master to listen to isochronous broadcasts once it has the relevant timing and frequency information. Once a slave device is on the channel, it can stay synchronised.
- a transmitting device can communicate its schedule simply by broadcasting it over the network.
- An alternative is for a relay device to connect to the transmitting device (or vice versa) and ask for the isochronous channel information. In some embodiments this request might be accompanied by a request to be able to send data back.
- the transmitting device may then allocate the relay a particular time slot (which may, for example, be defined relative to an isochronous event anchor point).
- the relay device then disconnects, allowing other devices to connect and request their own time slots.
- the schedule may be communicated over a different channel from the isochronous channel that the transmitting device uses to broadcast mesh data. This enables the transmitting device to send data at low power to many relay devices, and allow those devices to send data back to it.
- the transmitting device it also enables the transmitting device to send data to device it is not connected to; it simply broadcasts data in the appropriate time slot and any relay device that has been assigned that slot, or has unilaterally decided to listen to that slot, should receive it.
- Using isochronous channels may therefore improve mesh throughput.
- time slots may hop between different frequencies to provide increased robustness.
- One option for transmitting mesh packets would be to use BLE advertising channels. There are three such channels, each on a different frequency. These channels offer frequency diversity but no frequency hopping, and thus no resilience to other networks that might be transmitting in the same frequency band. Therefore, use of isochronous channels that hop between different frequencies may be beneficial. Adaptive frequency hopping can actually be achieved with just two different frequencies. An isochronous channel might advantageously hop from one time slot to the next.
- BLE defines an isochronous channel that is designed for the transmission of audio traffic.
- the BLE isochronous channel defines regular time slots and a frequency hopping sequence that a master device will use to transmit some data to one or more listening slave devices.
- An example of such a channel is shown in FIG. 4 .
- the channel is defined by specific times, known as “anchor points”, which set the start of each transmission.
- Each transmission may be known as an “event”, and may be followed by up to three re-transmissions known as “sub-events”.
- the sub-event anchor points are referenced to the event anchor points.
- Each transmission may be followed by an acknowledgement.
- Each “sub-event” may occur on a different frequency to increase robustness.
- the “sub-events” may also be an opportunity for the slave device to transmit data.
- data may be time bound, meaning that specific data (e.g. a specific packet) can only be sent for a limited period of time after which the data is automatically flushed and new data can be sent.
- the isochronous channel is therefore different from a normal data channel on which data is retransmitted until acknowledged.
- the isochronous channel is typically used for broadcasting audio to multiple devices.
- BLE isochronous channels are designed for audio data. They are not designed for command and control applications. When abstracted from an audio context, however, they have two qualities that particularly suit them to mesh networks: (i) transmissions occur according to a predefined schedule; and (ii) transmissions hop across different frequencies. BLE isochronous channels may therefore be advantageously adapted for transporting control-related data across a mesh network.
- Each of the BLE sub-events might be treated as a different isochronous channel.
- a different packet might be broadcast on each time slot.
- packets may be repeated across successive sub-events, although this might be at the expense of latency, as mentioned above.
- BLE isochronous channels allow for acknowledgements to be sent. These may be optionally adopted as part of a mesh control channel.
- Mesh control messages may be either unreliable or reliably delivered. An unreliable message would typically not have a transaction identifier and would not be retransmitted. Typically these unreliable messages are used for status messages or for user-initiated actions that may be repeated again quickly, for example when rotating a dimmer control for a light. No acknowledgements may be sent for messages of this type. Reliable messages would typically contain a transaction identifier, and devices that respond to these would copy the transaction identifier from the message into the response to provide an acknowledgement for the transaction.
- BLE isochronous channels are just an example of a channel that might be employed to broadcast control data over a mesh network. Channels according to other protocols might equally be used. For example, other protocols that might be employed in a mesh network include UDP, IPv4, IPv6 and TCP.
- FIG. 5 Another example of a mesh communication device is shown in FIG. 5 .
- the communication device is configured for wireless communication.
- the device of FIG. 5 comprises an antenna 501 , a radio frequency front end 502 and a baseband processor 503 .
- the baseband processor comprises a microprocessor 504 and a non-volatile memory 509 .
- the non-volatile memory 509 stores in non-transitory form program code that is executable by the microprocessor to cause the baseband processor to implement the communication protocol of the network.
- non-volatile memory 509 stores in non-transitory form program code that is executable by the microprocessor to implement the transmit unit 505 , broadcast unit 506 , scheduler 507 , mode controller 508 , relay unit 513 , timing unit 514 and receive unit 515 .
- the device also comprises a clock 510 , which can be turned on or off by the microprocessor 504 in order to save power, and an external wired connection 512 for exchanging information with the device's associated consumer. This information may include the sensing external events (e.g. the operation of an associated user interface device such as a switch) or issuing control signals to associated appliances (e.g. light fittings).
- the device also comprises a power source 511 , which may be a battery. The device may also be mains-powered.
- the RF front end 502 and the baseband processor could be implemented on one or more integrated circuits.
Abstract
A communication device capable of operating in a mesh network and configured to transmit data to a destination device by encapsulating that data in a broadcast packet and transmitting it over the mesh network in order that another communication device, on receiving the broadcast packet, may forward it towards the destination device, the communication device being further configured to: establish a schedule for transmitting data encapsulated in broadcast packets; transmit information defining that schedule over the mesh network; and subsequently transmit the broadcast packets in accordance with that schedule.
Description
- This non-provisional patent application claims priority to Great Britain applications: GB 1412716.1, filed Jul. 17, 2014; GB 1405790.5, filed Mar. 31, 2014; GB 1403314.6, filed Feb. 25, 2014; GB 1405785.5, filed Mar. 31, 2014; GB 1405786.3, filed Mar. 31, 2014; GB 1405789.7, filed Mar. 31, 2014; GB 1403312.0, filed Feb. 25, 2014; GB 1405791.3, filed Mar. 31, 2014; GB 1405797.0, filed Mar. 31, 2014.
- This invention relates to an apparatus and method for communicating data over a mesh network.
-
FIG. 1 shows a distributed network. The network comprises a number ofcommunication devices device 101 transmits a signal, that signal can be received bydevices device 101.Device 103 can then relay the signal received fromdevice 101 so that it can be received bydevice 105, which is out of range ofdevice 101. The coverage area ofdevice 101 is illustrated at 108 and the coverage area ofdevice 105 is illustrated at 109. This method of communication allows devices to communicate even though they are out of direct range or not synchronised with each other. Each device may also be connected to, or integrated within, an associated consumer device. Sodevice 101 is connected to a sensor that detects whetherwindow 102 is open or closed, anddevices light fittings - Many mesh networks send data using complex routing tables. The routing tables store routes from one network device to another so that messages can be propagated from source to destination via a series of hops. The topology of the network has to be known in order that routes between the various devices can be determined and stored. An alternative is flood routing. In this method messages do not travel from one device to another via a predefined route. Instead messages are broadcast and any device in range that receives a message retransmits it. A message thus propagates its way through the network, potentially reaching its destination via a number of different routes. Flood routing is very simple to implement and although it may appear inefficient has a number of advantages, particularly for ad hoc networks that may change their topology on a random basis.
- Flood routing implies that all devices should listen continuously for signals from other devices in the network, otherwise there is a risk that data might not reach its destination. Continuous listening increases power consumption. In current mesh networks this is often unimportant because most mesh devices have access to a mains power source, which eliminates the requirement for power saving. It does, however, limit the range of devices that can form part of the network. There is a need to open up mesh networks to a wider range of devices, including those with severe power restrictions.
- According to a first embodiment, there is provided a communication device capable of operating in a mesh network and configured to transmit data to a destination device by encapsulating that data in a broadcast packet and transmitting it over the mesh network in order that another communication device, on receiving the broadcast packet, may forward it towards the destination device, the communication device being further configured to: establish a schedule for transmitting data encapsulated in broadcast packets; transmit information defining that schedule over the mesh network; and subsequently transmit the broadcast packets in accordance with that schedule.
- The communication device may be configured to encapsulate non-audio data in the broadcast packets.
- The communication device may be configured to encapsulate control data in the broadcast packets.
- The communication device may be configured to transmit the broadcast packets over a channel that implements frequency hopping.
- The communication device may be configured to transmit the broadcast packets by transmitting each broadcast packet on a different frequency from the preceding broadcast packet.
- The communication device may be configured to transmit the information defining the schedule over a different channel from the broadcast packets.
- The communication device may be configured to transmit information that defines the timing and frequency of the schedule.
- The communication device may be configured to broadcast the information defining the schedule over the mesh network.
- The communication device may be configured to transmit the information defining the schedule over a connection with another communication device.
- The communication device may be configured to terminate the connection with the other communication device once it has transmitted the information defining the schedule.
- The communication device may be configured to establish a schedule under which the communication device transmits broadcast packets that encapsulate the same data for the same destination device at different time instants.
- The communication device may be configured to transmit the broadcast packets over a Bluetooth Low Energy isochronous channel.
- The communication device may be configured to encapsulate data for transmission over the mesh network in a Bluetooth Low Energy advertising packet.
- According to a second embodiment, there is provided a communication device capable of operating in a mesh network and having a scan mode in which it listens for broadcast packets on the mesh network, said broadcast packets encapsulating data that is intended for a destination device, and forwards any such broadcast packet towards the respective destination device, the communication device being configured to: obtain information that defines a schedule according to which another communication device may transmit broadcast packets over the mesh network; and enter scan mode and listen for broadcast packets at times defined by the schedule.
- The communication device may be configured to not enter scan mode at times that are not defined by the schedule.
- The communication device may be configured to obtain information defining the schedule by listening for a broadcast packet that defines that schedule.
- The communication device may be configured to obtain information defining the schedule by connecting with the other communication device.
- The communication device may be configured to disconnect from the other communication device once the information defining the schedule has been received.
- The communication device may be configured to enter scan mode and listen for broadcast packets when it is not connected to the other communication device.
- The present invention will now be described by way of example with reference to the accompanying drawings. In the drawings:
-
FIG. 1 shows an example of a distributed network; -
FIGS. 2 a to 2 c show examples of communication devices and a method of operating the same; -
FIGS. 3 a and 3 b show an example of a mesh network; -
FIG. 4 shows an example of a communication channel; and -
FIG. 5 shows an example of a communication device. - The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art.
- The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
-
FIG. 2 a shows an example of a communication device. The communication device is generally configured for transmitting data over a mesh network. In most examples the communication device may be configured for wireless communication, although wired configurations are also possible. This is represented generally byoutput 201. In a wireless network data is transmitted via radio signals. In a wired implementation, data may be transmitted via electrical signals. Most commonly data may be arranged in “packets” incorporating payload data and some indication of the source device and the destination devices. - The communication device may be configured to operate in accordance with a communication protocol that governs communications across the mesh network. Suitably the communication protocol defines a broadcast packet type. A broadcast packet is one that is not addressed to any one particular device, and thus can be received by any device in the network that is within range.
- The communication device comprises a transmit
unit 202, which is configured to transmit data over the mesh network in accordance with the protocol. The transmit unit comprises abroadcast unit 203, which is configured to encapsulate data in broadcast packets. Suitably that data is control data. The data is usually intended for a particular subset of one or more devices in the mesh network. Although the broadcast unit identifies these destination devices in the broadcast packet, it may not establish a connection with those devices. Indeed, in many instances the communication device will be out of range of one or more of the destination devices. Instead, the transmission unit broadcasts the packet in the hope that another device in the mesh network, acting as a relay, will receive the packet and forward it on to its destination. The communication device is thus configured to operate in a mesh network that utilises flood routing to transport data between source and destination devices. - Flood routing implies that all devices should listen continuously for signals from other devices in the network, otherwise there is a risk that data might not reach its destination. There are three main reasons why it may be impractical for a mesh communication device to spend significant amount of time listening for packets. The first is the cost in power. The second is the physical impossibility for many devices of receiving at the same time as transmitting. The third is the need to perform other functions outside of the network, which may not be possible while listening for packets. Time that a communication device saves by not listening for packets may be spent performing other functions or in a low power mode to conserve battery life.
- This leads to two further insights. First, it is often the case that a device acting as a relay in a mesh network does not actually need to receive all packets because its role is only to relay those packets, not to alter its behaviour in dependence on the data that those packets contain. Consequently, not only is it often technically impossible for a single device to listen continuously, it is also (at least from the perspective of that particular device) often unnecessary. Second, from the perspective of the network it generally does not matter which particular device relays each packet; it only matters that the packet is relayed. Thus it may be possible to have one relay device deliberately not listen for packets at all, on the basis that any gaps in its listening will be covered by other devices in the vicinity.
- If the relay devices decide unilaterally when to listen for packets, there is a risk that none of them will be listening when a particular packet is broadcast, and the packet may be dropped. Having some form of direct coordination between neighbouring relay devices might help to avoid listening gaps but could add undesirable complexity, particularly in an ad hoc mesh in which a relay device's neighbours may change with time. An indirect form of coordination may therefore be beneficial.
- The communication device that is transmitting the broadcast packets may establish a transmission schedule. The relay devices may choose to listen to those packets or not (retaining their unilateral behavior), but having a mesh device transmit its broadcast messages at set times enables a relay device to tailor its listening windows to those times when there might actually be a broadcast packet for it to relay. Thus relays may reduce their power consumption without missing packets. The relays might reduce their power consumption still further by listening to only a subset of the transmission slots. This introduces a risk that a packet might be dropped. But by limiting the potential transmit time down to a number of discrete time slots it also becomes feasible that multiple relays, independently selecting which slots to listen to, might, as a group, end up listening to all slots. The likelihood that all slots will be listened to can be improved still further by the transmitting device communicating information about different subsets of its transmission slots to different relay devices. This is described in more detail below.
- The communication device comprises a
scheduler 204 for establishing a schedule for the transmission unit to transmit data encapsulated in broadcast packets over the mesh network. Transmitunit 202 may be configured to transmit information defining the schedule over the mesh network. Subsequently the transmit unit may establish a channel that embodies the schedule and transmit the broadcast packets over that channel. -
FIG. 2 b shows another example of a communication device. In this example the communication device is generally configured for receiving data over the mesh network. The communication device may be configured to act as a relay. In many implementations the communication devices represented byFIGS. 2 a and 2 b may be implemented together as part of one device that is capable of transmitting and receiving data over the mesh network. - As before, the communication device shown in
FIG. 2 b will usually be configured for wireless communication, although wired configurations are also possible. This is represented generally byoutput 205. The communication device may be configured to operate in a number of different modes, including a scan mode. The communication device comprises amode controller 206 for controlling operation of atransceiver 207 in dependence on the current mode of operation. In scan mode, themode controller 206 may control thetransceiver 207 to listen for broadcast packets on the mesh network. These broadcast packets may encapsulate data that is intended for a destination device, which often may not be the communication device itself. The communication device may be configured to act as a relay in the mesh network by forwarding any broadcast packets intended for a different device towards their destination. The communication device may comprise arelay unit 208 for controlling the transceiver to retransmit any such packets. - The mode controller may also comprise a
timing unit 209 for determining when the communication device should change from one operating mode to another, e.g. for determining when the communication device should wake from a sleep mode and enter the scanning mode. Thetiming unit 209 may be configured to obtain information that defines a schedule according to which another communication device may transmit broadcast packets over the mesh network. Themode controller 206 may be configured to control the transceiver to enter scan mode and listen for broadcast packets during the time slots defined by that schedule. - The structures shown in
FIGS. 2 a and 2 b (and indeed all block apparatus diagrams included herein) are intended to correspond to a number of functional blocks in an apparatus. This is for illustrative purposes only.FIGS. 2 a and 2 b are not intended to define a strict division between different parts of hardware on a chip or between different programs, procedures or functions in software. In some embodiments, some or all of the algorithms described herein may be performed wholly or partly in hardware. In many implementations, at least part of transmitunit 202,broadcast unit 203,scheduler 204,mode controller 206,transceiver 207,relay unit 208 ortiming unit 209 may be implemented by a processor acting under software control (e.g. the CPU of a communication device). Any such software may be stored on a non-transient computer readable medium, such as a memory (RAM, cache, hard disk, etc.) or other storage means (USB stick, CD, disk, etc.). - Various example scenarios are described below in which on device acts the part of a “transmitting device” and another device acts the part of a “receiving device”. This nomenclature just refers to the specific role that each device is playing in that particular scenario, and it should be understood that in most embodiments a “transmitting device” may be equally capable of “receiving” and vice versa. A “receiving device” is often also referred to as a “relay”. This is for reasons of convenience, since a receiving device may be acting as a relay when it listens for packets over the mesh network. The term “relay” is not intended to be limiting to devices that are specifically operating as a relay, however, as a device that is the destination for a particular broadcast packet may still operate in the same way with respect to listening for that packet as a device that relays the packet. Thus actions described as being performed by a “relay” might equally be performed by a generic “receiving device”.
- An example of a method for setting transmission times in an ad hoc mesh network is shown in
FIG. 2 c. The transmitting device establishes a schedule for transmitting its broadcast packets (step S201). The transmitting device then communicates this schedule over the mesh network (step S202). There are different ways in which this schedule may be communicated. In some implementations the schedule may be communicated directly to a particular mesh device. In other implementations the schedule may simply be broadcast so that it can be intercepted by one or more mesh devices. (This is described in more detail below.) The transmitting device may communicate the entirety of its schedule or only selective parts of it. For example, the transmitting device may communicate different parts of its schedule to different mesh devices to increase the likelihood that all of its transmission schedule will be listened to. - In step S203 the schedule is received by the relay device. The relay device may then align its listening windows to the transmit schedule (step S204). In most implementations it may be up to the relay device to decide how many of the transmission slots it wants to listen to. Thus while the transmitting device is able to improve the chances of its broadcast packets being relayed by communicating its schedule, in some implementations the relays may still unilaterally decide when it wants to listen. In some implementations, however, the relay device may be mandated to listen to specified transmission slots. In step S205, the transmitting device transmits its broadcast packets over a communication channel that embodies its transmit schedule. The relay device listens according to its own listening schedule (step S206), and if it receives a broadcast packet intended for another device, rebroadcasts it (step S207).
- One advantage of the techniques described above is it removes the need for continuous listening. This enables battery-powered relay devices become possible, whereas previously mains-powered relay devices could realistically be considered. This is a step in permitting flexible mesh deployment and ad-hoc arrangements. It also enables any device configured to operate in accordance with the mesh protocol to form part of the mesh whilst still allowing other “primary” (i.e. non-mesh) functions to be performed.
- The transport of messages throughout a mesh network will now be described in more detail with reference to a specific example of a mesh network.
- Within buildings, the propagation of radio frequency energy can be severely constrained by the construction of walls and other obstacles. This has led the development of a mesh network that relays messages via multiple devices (otherwise known as a mesh topology) to provide whole building coverage. An example of such a network is shown in
FIG. 3 , which represents a house having a distributed lighting system. - The system comprises a
light switch unit 301 andlight fittings Light switch unit 301 is integrated with awireless communication device 312.Light fittings 302 to 305 are integrated with respectivewireless communication devices wireless communication devices 306 to 309.Light switch unit 301 and itswireless communication device 312 are powered by alocal battery 311. - The house contains other items of equipment that contain other wireless communication devices. For example, there is a
tablet computer 310 which contains awireless communication device 313, and amobile phone 315 which contains awireless communication device 316. There is also asensor 320 for detecting the open/closed state ofwindow 318, which containscommunication device 319.Computer 310,phone 315 andsensor 320 are powered bybatteries -
Wireless communication devices 306 to 309, 310, 315 and 319 operate according to the same wireless communication protocol. That could be a relatively short-range protocol. For example the effective range of each device could be less than 35 m. That characteristic can permit the devices to use less power for transmitting and/or receiving than would be expected in a longer range protocol. The protocol could be one that imposes no common time-base at or below the transport level, or below the application or presentation levels. In other words, the devices in the network operate asynchronously of each other. That characteristic can reduce the devices' power consumption by reducing their for need accurate clocks running continuously. In one example, the devices could operate according to the Bluetooth protocol, specifically the Bluetooth Low Energy protocol (BLE). -
Devices 306 to 309 are configured cooperatively in order that thelight fittings 302 to 305 know to respond to signals from thelight switch 301. This may be done by thedevices 306 to 309 storing a common identification code in their respective non-volatile memories. The identification code may be stored in the light switch when it is manufactured, and stored in the light fittings at the time they are installed in the house. They may be stored in the light fittings by means of another device such asmobile phone 315 communicating with the wireless device of the light switch to read its identification code, and then communicating with the wireless devices of the light fittings to cause them to store that same identification code. This code may be a network key, and it may be used to sign all packets sent over the network. - The network may also be configured to implement flood routing, which is well suited to ad hoc networks. The
phone 315 and thetablet computer 310 are both portable devices that change location within the network as a user picks them up and moves them. They may also occasionally leave the network and then reappear some time later. For example, when a user takes them out of range of the network by taking them out of the house and later returns them to the house. The network's topology is thus subject to random alteration. - Some of the communication devices may act as master devices, while others of the communication devices may act as slave devices. Some devices may always have the same role;
communication device 319 ofsensor 320 attached towindow 318 might always act as a slave, for example. Other devices such ascommunication device 316 inmobile phone 315 may be capable of swapping between master and slave roles or of acting as a master and a slave at the same time. Master devices, for example, might act as slaves to other master devices. Master/slave arrangements can result in a full mesh node having significantly lower power consumption requirements than other mesh designs. - Each communication device may be capable of acting as a relay in the network. An example of this is shown in
FIG. 3 b, which shows the same distributed lighting system asFIG. 3 a. The network is configured as a mesh network so, at least in theory, all devices that are part of the network have a responsibility to act as relays. A relay device suitably retransmits any packet that it recognises as having originated from the network (e.g. because it has been signed using a network key). The relay device might also take steps to prevent old packets from being continuously bounced around the network, e.g. by only forwarding the packet if it is new and/or by decrementing a “time-to-live” value in the packet before forwarding it on.FIG. 3 a shows an example of the network operating according to traditional mesh principles.Light switch 301 transmits a packet addressed to all ofdevices 306 to 309 instructinglight fittings 302 to 305 to switch on. This packet is propagated by all devices that receive it, eventually reachinglight fitting 305, which is out of range oflight switch 301, the source of the packet. - Although the arrangement shown in
FIG. 3 b is effective at propagating packets to all devices in the network, constant listening is an expensive operation and should be avoided in contexts where power availability is an issue. Although bothdevice 316 anddevice 319 are capable as acting as relays, they are both battery powered and would prefer to reduce power consumption where possible. Therefore, one or both of those devices may deliberately reduce their receive power. For example, ifdevice 316 communicates its transmit schedule todevice 319, thendevice 319 can reduce its listening time by only entering scan mode duringdevice 316's scheduled transmission slots. Thus it will still receive packets broadcast bydevice 316 but is able to save power by significantly reducing its receive windows. - A transmitting device's scheduled transmission slots can be considered to embody a “communication channel”. This channel may be termed an “isochronous channel” because it schedules communications to occur at set times. Isochronous channels allow for time predictable transmission and reception slots. A particular sequence of time slots might represent a particular physical channel.
- An isochronous channel might be used as a uni-directional broadcast channel. For example, Device A might transmit data in broadcast packets at set times on an isochronous channel. Device B might listen to the isochronous channel at the set times to receive Device A's broadcast packets. Device A and Device B do not need to be connected with each other to do this. All that is required is for one device to know when it should listen for broadcasts from the other. Another option is for Devices A and B to use the set times on the isochronous channel as a bi-directional broadcast channel, which they both transmit and receive on (e.g. by each device having the right to transmit on alternate slots).
- A transmitting device may be configured to use just one isochronous channel or multiple isochronous channels. For example, a transmitting device that is acting as a “master” or “central” device may use multiple isochronous channels to communicate with its slaves. Each channel may be designated for broadcasting to a particular slave. A master device is normally limited in the number of connections it can support simultaneously with its slave devices. An advantage of broadcasting data over isochronous channels is that it allows many slaves to be synchronised with the same master without all having to be connected to the master. This is because all the slave devices need to be able to synchronise with the isochronous channel is the timing of the transmission slots and the frequency of the channel. It does not need to be connected to the master to listen to isochronous broadcasts once it has the relevant timing and frequency information. Once a slave device is on the channel, it can stay synchronised.
- A transmitting device can communicate its schedule simply by broadcasting it over the network. An alternative is for a relay device to connect to the transmitting device (or vice versa) and ask for the isochronous channel information. In some embodiments this request might be accompanied by a request to be able to send data back. The transmitting device may then allocate the relay a particular time slot (which may, for example, be defined relative to an isochronous event anchor point). The relay device then disconnects, allowing other devices to connect and request their own time slots. Thus the schedule may be communicated over a different channel from the isochronous channel that the transmitting device uses to broadcast mesh data. This enables the transmitting device to send data at low power to many relay devices, and allow those devices to send data back to it. It also enables the transmitting device to send data to device it is not connected to; it simply broadcasts data in the appropriate time slot and any relay device that has been assigned that slot, or has unilaterally decided to listen to that slot, should receive it. Using isochronous channels may therefore improve mesh throughput.
- In a further example, time slots may hop between different frequencies to provide increased robustness. One option for transmitting mesh packets would be to use BLE advertising channels. There are three such channels, each on a different frequency. These channels offer frequency diversity but no frequency hopping, and thus no resilience to other networks that might be transmitting in the same frequency band. Therefore, use of isochronous channels that hop between different frequencies may be beneficial. Adaptive frequency hopping can actually be achieved with just two different frequencies. An isochronous channel might advantageously hop from one time slot to the next.
- An example of a frequency hopping, isochronous channel can be found in the BLE protocol. BLE defines an isochronous channel that is designed for the transmission of audio traffic. The BLE isochronous channel defines regular time slots and a frequency hopping sequence that a master device will use to transmit some data to one or more listening slave devices. An example of such a channel is shown in
FIG. 4 . The channel is defined by specific times, known as “anchor points”, which set the start of each transmission. Each transmission may be known as an “event”, and may be followed by up to three re-transmissions known as “sub-events”. The sub-event anchor points are referenced to the event anchor points. Each transmission may be followed by an acknowledgement. Each “sub-event” may occur on a different frequency to increase robustness. The “sub-events” may also be an opportunity for the slave device to transmit data. - For a BLE isochronous channel, data may be time bound, meaning that specific data (e.g. a specific packet) can only be sent for a limited period of time after which the data is automatically flushed and new data can be sent. The isochronous channel is therefore different from a normal data channel on which data is retransmitted until acknowledged. The isochronous channel is typically used for broadcasting audio to multiple devices.
- BLE isochronous channels are designed for audio data. They are not designed for command and control applications. When abstracted from an audio context, however, they have two qualities that particularly suit them to mesh networks: (i) transmissions occur according to a predefined schedule; and (ii) transmissions hop across different frequencies. BLE isochronous channels may therefore be advantageously adapted for transporting control-related data across a mesh network.
- Assuming a BLE channel with a 120 ms interval, 0.35 ms long packets, spaced 0.15 ms apart, and three transmission opportunities every 50 ms, it is possible to have almost 40 devices synchronised with the broadcasts of a single mesh node. This is significantly higher than the number of simultaneous connections that could be supported by a single mesh node. Furthermore a slave would only need to listen for 0.35 ms every 120 ms, which is a very low duty cycle. It might be possible to reduce this duty cycle further without increasing the packet drop rate if data was retransmitted on two (or more) anchor points in a row. This would, however, be at the expense of latency.
- Each of the BLE sub-events might be treated as a different isochronous channel. A different packet might be broadcast on each time slot. Alternatively packets may be repeated across successive sub-events, although this might be at the expense of latency, as mentioned above.
- As can be seen from
FIG. 4 , BLE isochronous channels allow for acknowledgements to be sent. These may be optionally adopted as part of a mesh control channel. Mesh control messages may be either unreliable or reliably delivered. An unreliable message would typically not have a transaction identifier and would not be retransmitted. Typically these unreliable messages are used for status messages or for user-initiated actions that may be repeated again quickly, for example when rotating a dimmer control for a light. No acknowledgements may be sent for messages of this type. Reliable messages would typically contain a transaction identifier, and devices that respond to these would copy the transaction identifier from the message into the response to provide an acknowledgement for the transaction. - BLE isochronous channels are just an example of a channel that might be employed to broadcast control data over a mesh network. Channels according to other protocols might equally be used. For example, other protocols that might be employed in a mesh network include UDP, IPv4, IPv6 and TCP.
- Another example of a mesh communication device is shown in
FIG. 5 . In this example the communication device is configured for wireless communication. The device ofFIG. 5 comprises anantenna 501, a radio frequencyfront end 502 and abaseband processor 503. The baseband processor comprises amicroprocessor 504 and anon-volatile memory 509. Thenon-volatile memory 509 stores in non-transitory form program code that is executable by the microprocessor to cause the baseband processor to implement the communication protocol of the network. In this example thenon-volatile memory 509 stores in non-transitory form program code that is executable by the microprocessor to implement the transmitunit 505,broadcast unit 506,scheduler 507,mode controller 508,relay unit 513,timing unit 514 and receiveunit 515. - The device also comprises a
clock 510, which can be turned on or off by themicroprocessor 504 in order to save power, and an externalwired connection 512 for exchanging information with the device's associated consumer. This information may include the sensing external events (e.g. the operation of an associated user interface device such as a switch) or issuing control signals to associated appliances (e.g. light fittings). The device also comprises apower source 511, which may be a battery. The device may also be mains-powered. - The RF
front end 502 and the baseband processor could be implemented on one or more integrated circuits. - The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that aspects of the present invention may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.
Claims (19)
1. A communication device capable of operating in a mesh network and configured to transmit data to a destination device by encapsulating that data in a broadcast packet and transmitting it over the mesh network in order that another communication device, on receiving the broadcast packet, forwards it towards the destination device, the communication device being further configured to:
establish a schedule for transmitting data encapsulated in broadcast packets;
transmit information defining the schedule over the mesh network; and
subsequently transmit the broadcast packets in accordance with the schedule.
2. The communication device as claimed in claim 1 , configured to encapsulate non-audio data in the broadcast packets.
3. The communication device as claimed in claim 1 , configured to encapsulate control data in the broadcast packets.
4. The communication device as claimed in claim 1 , configured to transmit the broadcast packets over a channel that implements frequency hopping.
5. The communication device as claimed in claim 1 , configured to transmit the broadcast packets by transmitting each broadcast packet on a different frequency from the preceding broadcast packet.
6. The communication device as claimed in claim 1 , configured to transmit the information defining the schedule over a different channel from the broadcast packets.
7. The communication device as claimed in claim 1 , configured to transmit information that defines the timing and frequency of the schedule.
8. The communication device as claimed in claim 1 , configured to broadcast the information defining the schedule over the mesh network.
9. The communication device as claimed in claim 1 , configured to transmit the information defining the schedule over a connection with another communication device.
10. The communication device as claimed in claim 9 , configured to terminate the connection with the other communication device once it has transmitted the information defining the schedule.
11. The communication device as claimed in claim 1 , configured to establish a schedule under which the communication device transmits broadcast packets that encapsulate the same data for the same destination device at different time instants.
12. The communication device as claimed in claim 1 , configured to transmit the broadcast packets over a Bluetooth Low Energy isochronous channel.
13. The communication device as claimed in claim 1 , configured to encapsulate data for transmission over the mesh network in a Bluetooth Low Energy advertising packet.
14. A communication device capable of operating in a mesh network and having a scan mode in which it listens for broadcast packets on the mesh network, said broadcast packets encapsulating data that is intended for a destination device, and forwards any such broadcast packet towards the respective destination device, the communication device being configured to:
obtain information that defines a schedule according to which another communication device will transmit broadcast packets over the mesh network; and
enter scan mode and listen for broadcast packets at times defined by the schedule.
15. The communication device as claimed in claim 14 , configured to not enter scan mode at times that are not defined by the schedule.
16. The communication device as claimed in claim 14 , configured to obtain information defining the schedule by listening for a broadcast packet that defines the schedule.
17. The communication device as claimed in claim 14 , configured to obtain information defining the schedule by connecting with the other communication device.
18. The communication device as claimed in claim 17 , configured to disconnect from the other communication device once the information defining the schedule has been received.
19. The communication device as claimed in claim 14 , configured to enter scan mode and listen for broadcast packets when it is not connected to the other communication device.
Applications Claiming Priority (18)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1403314.6A GB2512733B (en) | 2014-02-25 | 2014-02-25 | Broadcast retransmission |
GB1403312.0 | 2014-02-25 | ||
GB1403312.0A GB2515853B (en) | 2014-02-25 | 2014-02-25 | Latency mitigation |
GB1403314.6 | 2014-02-25 | ||
GB1405791.3A GB2512748B (en) | 2014-02-25 | 2014-03-31 | Auto-configuration of a mesh relay's TX/RX schedule |
GB1405789.7 | 2014-03-31 | ||
GB1405791.3 | 2014-03-31 | ||
GB1405786.3 | 2014-03-31 | ||
GB1405785.5A GB2512501A (en) | 2014-02-25 | 2014-03-31 | Packet identification |
GB1405789.7A GB2512502B (en) | 2014-02-25 | 2014-03-31 | Device authentication |
GB1405797.0A GB2512749B (en) | 2014-02-25 | 2014-03-31 | Linking ad hoc networks |
GB1405797.0 | 2014-03-31 | ||
GB1405790.5 | 2014-03-31 | ||
GB1405785.5 | 2014-03-31 | ||
GB1405786.3A GB2512746B (en) | 2014-02-25 | 2014-03-31 | Thwarting traffic analysis |
GB1405790.5A GB2512747B (en) | 2014-02-25 | 2014-03-31 | Mesh relay |
GB1412716.1 | 2014-07-17 | ||
GB1412716.1A GB2512542B (en) | 2014-02-25 | 2014-07-17 | Communicating data over a mesh network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150245369A1 true US20150245369A1 (en) | 2015-08-27 |
Family
ID=50737759
Family Applications (14)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/270,884 Abandoned US20150244648A1 (en) | 2014-02-25 | 2014-05-06 | Auto-configuration of a mesh relay's tx/rx schedule |
US14/270,961 Active 2035-05-12 US10055570B2 (en) | 2014-02-25 | 2014-05-06 | Mesh relay |
US14/297,324 Active 2034-12-08 US9489506B2 (en) | 2014-02-25 | 2014-06-05 | Linking ad hoc networks |
US14/298,177 Abandoned US20150245203A1 (en) | 2014-02-25 | 2014-06-06 | Packet identification |
US14/316,529 Abandoned US20150244828A1 (en) | 2014-02-25 | 2014-06-26 | Thwarting traffic analysis |
US14/316,404 Abandoned US20150245204A1 (en) | 2014-02-25 | 2014-06-26 | Device authentication |
US14/505,454 Expired - Fee Related US9842202B2 (en) | 2014-02-25 | 2014-10-02 | Device proximity |
US14/505,465 Abandoned US20150244565A1 (en) | 2014-02-25 | 2014-10-02 | Network configuration |
US14/505,458 Active US9672346B2 (en) | 2014-02-25 | 2014-10-02 | Object tracking by establishing a mesh network and transmitting packets |
US14/505,466 Abandoned US20150244623A1 (en) | 2014-02-25 | 2014-10-02 | Mesh profiling |
US14/505,399 Active 2035-04-03 US9910976B2 (en) | 2014-02-25 | 2014-10-02 | Processing mesh communications |
US14/505,437 Abandoned US20150245369A1 (en) | 2014-02-25 | 2014-10-02 | Communicating data over a mesh network |
US14/505,443 Active 2035-06-01 US9754096B2 (en) | 2014-02-25 | 2014-10-02 | Update management |
US14/505,418 Abandoned US20150242614A1 (en) | 2014-02-25 | 2014-10-02 | Provisioning of security credentials |
Family Applications Before (11)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/270,884 Abandoned US20150244648A1 (en) | 2014-02-25 | 2014-05-06 | Auto-configuration of a mesh relay's tx/rx schedule |
US14/270,961 Active 2035-05-12 US10055570B2 (en) | 2014-02-25 | 2014-05-06 | Mesh relay |
US14/297,324 Active 2034-12-08 US9489506B2 (en) | 2014-02-25 | 2014-06-05 | Linking ad hoc networks |
US14/298,177 Abandoned US20150245203A1 (en) | 2014-02-25 | 2014-06-06 | Packet identification |
US14/316,529 Abandoned US20150244828A1 (en) | 2014-02-25 | 2014-06-26 | Thwarting traffic analysis |
US14/316,404 Abandoned US20150245204A1 (en) | 2014-02-25 | 2014-06-26 | Device authentication |
US14/505,454 Expired - Fee Related US9842202B2 (en) | 2014-02-25 | 2014-10-02 | Device proximity |
US14/505,465 Abandoned US20150244565A1 (en) | 2014-02-25 | 2014-10-02 | Network configuration |
US14/505,458 Active US9672346B2 (en) | 2014-02-25 | 2014-10-02 | Object tracking by establishing a mesh network and transmitting packets |
US14/505,466 Abandoned US20150244623A1 (en) | 2014-02-25 | 2014-10-02 | Mesh profiling |
US14/505,399 Active 2035-04-03 US9910976B2 (en) | 2014-02-25 | 2014-10-02 | Processing mesh communications |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/505,443 Active 2035-06-01 US9754096B2 (en) | 2014-02-25 | 2014-10-02 | Update management |
US14/505,418 Abandoned US20150242614A1 (en) | 2014-02-25 | 2014-10-02 | Provisioning of security credentials |
Country Status (3)
Country | Link |
---|---|
US (14) | US20150244648A1 (en) |
DE (13) | DE102014012257B4 (en) |
GB (18) | GB2517844B (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9489506B2 (en) | 2014-02-25 | 2016-11-08 | Qualcomm Technologies International, Ltd. | Linking ad hoc networks |
WO2017059206A1 (en) * | 2015-09-30 | 2017-04-06 | Fossil Group, Inc. | Systems, devices, and methods for simulataneously exchanging messages between a low-energy radio device and multiple communication devices |
US9692538B2 (en) | 2014-02-25 | 2017-06-27 | Qualcomm Technologies International, Ltd. | Latency mitigation |
WO2017146829A1 (en) * | 2016-02-24 | 2017-08-31 | Qualcomm Incorporated | A source device broadcasts synchronization information associated with a bluetooth isochronous channel |
US20180172664A1 (en) * | 2016-12-20 | 2018-06-21 | Abbott Diabetes Care Inc. | Systems, devices, and methods for wireless communications in analyte monitoring systems |
US10313540B2 (en) * | 2015-03-12 | 2019-06-04 | Canon Kabushiki Kaisha | Information processing apparatus, control method thereof, and storage medium |
WO2019117763A1 (en) * | 2017-12-11 | 2019-06-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Channel scanning in a mesh network |
US20190215673A1 (en) * | 2016-08-22 | 2019-07-11 | Lg Electronics Inc. | Method for controlling device by using bluetooth technology, and apparatus |
US20200059827A1 (en) * | 2018-03-23 | 2020-02-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Message Cache Management in a Mesh Network |
US10624028B2 (en) | 2015-02-26 | 2020-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Energy efficient BLE mesh initialisation and operation |
US10644746B2 (en) | 2016-04-29 | 2020-05-05 | Texas Instruments Incorporated | Pseudo channel hopping using scan dwell times in mesh networks without time synchronization |
CN111886843A (en) * | 2018-06-13 | 2020-11-03 | 卧安科技(深圳)有限公司 | Low power consumption Bluetooth network maintenance method, electronic device, Bluetooth network and medium |
US11246132B2 (en) * | 2017-11-28 | 2022-02-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Message transmission with reduced interference |
US11490400B2 (en) * | 2017-11-15 | 2022-11-01 | Telefonaktiebolaget Lm Ericsson (Publ) | End node, relay node, and methods performed therein for handling transmission of information |
Families Citing this family (115)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103974225B (en) * | 2013-02-01 | 2018-03-13 | 财团法人工业技术研究院 | Communication device, device-to-device communication system and wireless communication method thereof |
US9234757B2 (en) | 2013-11-29 | 2016-01-12 | Fedex Corporate Services, Inc. | Determining node location using a variable power characteristic of a node in a wireless node network |
US9451462B2 (en) * | 2014-08-10 | 2016-09-20 | Belkin International Inc. | Setup of multiple IoT network devices |
US9918351B2 (en) | 2014-04-01 | 2018-03-13 | Belkin International Inc. | Setup of multiple IOT networks devices |
US10453023B2 (en) | 2014-05-28 | 2019-10-22 | Fedex Corporate Services, Inc. | Methods and node apparatus for adaptive node communication within a wireless node network |
US9386605B2 (en) * | 2014-07-11 | 2016-07-05 | Motorola Solutions, Inc. | Mobile dynamic mesh cluster bridging method and apparatus at incident scenes |
US9872240B2 (en) | 2014-08-19 | 2018-01-16 | Belkin International Inc. | Network device source entity triggered device configuration setup |
FR3026587A1 (en) * | 2014-09-30 | 2016-04-01 | Orange | METHOD OF ACCESS BY A MASTER DEVICE TO A VALUE TAKEN BY A CHARACTERISTIC MANAGED BY A PERIPHERAL DEVICE |
FR3031822B1 (en) * | 2015-01-16 | 2018-04-13 | Airbus Operations | DOWNLOADING DATA ON REMOTE EQUIPMENT |
US10681479B2 (en) | 2015-01-30 | 2020-06-09 | Cassia Networks Inc. | Methods, devices and systems for bluetooth audio transmission |
US9769594B2 (en) | 2015-01-30 | 2017-09-19 | Cassia Networks Inc. | Methods, devices and systems for increasing wireless communication range |
US11238397B2 (en) | 2015-02-09 | 2022-02-01 | Fedex Corporate Services, Inc. | Methods, apparatus, and systems for generating a corrective pickup notification for a shipped item using a mobile master node |
US9426616B1 (en) | 2015-02-10 | 2016-08-23 | Tyco Fire & Security Gmbh | Wireless sensor network controlled low energy link |
FR3033118B1 (en) * | 2015-02-19 | 2017-02-17 | Sigfox | METHOD AND SYSTEM FOR WIRELESS COMMUNICATION BETWEEN TERMINALS AND SEMI-DUPLEX BASE STATIONS |
US10848485B2 (en) | 2015-02-24 | 2020-11-24 | Nelson Cicchitto | Method and apparatus for a social network score system communicably connected to an ID-less and password-less authentication system |
US11171941B2 (en) * | 2015-02-24 | 2021-11-09 | Nelson A. Cicchitto | Mobile device enabled desktop tethered and tetherless authentication |
US11122034B2 (en) | 2015-02-24 | 2021-09-14 | Nelson A. Cicchitto | Method and apparatus for an identity assurance score with ties to an ID-less and password-less authentication system |
TWI552001B (en) * | 2015-04-13 | 2016-10-01 | 聚眾聯合科技股份有限公司 | Connection information sharing system, computer program, and connection information sharing method thereof |
CN106304303B (en) * | 2015-06-09 | 2019-11-12 | 沈阳中科奥维科技股份有限公司 | A kind of power regulating method suitable for WIA-PA wireless network |
US10375492B2 (en) | 2015-06-30 | 2019-08-06 | Sonova, AG | Method of fitting a hearing assistance device |
EP3320721A4 (en) * | 2015-07-06 | 2018-08-01 | Telefonaktiebolaget LM Ericsson (publ) | Apparatus and method for forwarding messages |
US10305744B2 (en) | 2015-07-08 | 2019-05-28 | Fedex Corporate Services, Inc. | System, apparatus, and methods of event monitoring for an event candidate related to an ID node within a wireless node network |
US9843929B2 (en) | 2015-08-21 | 2017-12-12 | Afero, Inc. | Apparatus and method for sharing WiFi security data in an internet of things (IoT) system |
US9503969B1 (en) | 2015-08-25 | 2016-11-22 | Afero, Inc. | Apparatus and method for a dynamic scan interval for a wireless device |
US10990616B2 (en) * | 2015-11-17 | 2021-04-27 | Nec Corporation | Fast pattern discovery for log analytics |
US10673646B1 (en) * | 2018-12-09 | 2020-06-02 | Olibra Llc | System, device, and method of multi-path wireless communication |
US10432461B2 (en) * | 2015-12-04 | 2019-10-01 | T-Mobile Usa, Inc. | Peer-to-peer distribution of radio protocol data for software defined radio (SDR) updates |
KR102381371B1 (en) * | 2015-12-10 | 2022-03-31 | 삼성전자주식회사 | System and method for providing information by using near field communication |
US10805344B2 (en) * | 2015-12-14 | 2020-10-13 | Afero, Inc. | Apparatus and method for obscuring wireless communication patterns |
US10447784B2 (en) | 2015-12-14 | 2019-10-15 | Afero, Inc. | Apparatus and method for modifying packet interval timing to identify a data transfer condition |
US10091242B2 (en) | 2015-12-14 | 2018-10-02 | Afero, Inc. | System and method for establishing a secondary communication channel to control an internet of things (IOT) device |
US9992065B2 (en) * | 2015-12-15 | 2018-06-05 | T-Mobile Usa, Inc. | Selective wi-fi calling router updates |
US10659442B1 (en) * | 2015-12-21 | 2020-05-19 | Marvell International Ltd. | Security in smart configuration for WLAN based IOT device |
US20170187602A1 (en) * | 2015-12-29 | 2017-06-29 | Vivek Pathela | System and method of troubleshooting network source inefficiency |
WO2017124012A1 (en) * | 2016-01-13 | 2017-07-20 | Locus-Control Llc | Low power communications system |
CN108780538A (en) | 2016-03-23 | 2018-11-09 | 联邦快递服务公司 | The system, apparatus and method of broadcast setting for the node in self-adjusting wireless node network |
GB2549735B (en) * | 2016-04-26 | 2020-07-29 | Checkit Ltd | Network access control |
US10205606B2 (en) | 2016-06-15 | 2019-02-12 | Abl Ip Holding Llc | Mesh over-the-air (OTA) luminaire firmware update |
US10873854B2 (en) * | 2016-07-28 | 2020-12-22 | Lg Electronics Inc. | Method and apparatus for establishing connection of devices |
EP3312762B1 (en) * | 2016-10-18 | 2023-03-01 | Axis AB | Method and system for tracking an object in a defined area |
US9781603B1 (en) | 2016-10-20 | 2017-10-03 | Fortress Cyber Security, LLC | Combined network and physical security appliance |
US10348514B2 (en) * | 2016-10-26 | 2019-07-09 | Abl Ip Holding Llc | Mesh over-the-air (OTA) driver update using site profile based multiple platform image |
US11210678B2 (en) | 2016-11-18 | 2021-12-28 | Samsung Electronics Co., Ltd. | Component for provisioning security data and product including the same |
US10728026B2 (en) * | 2016-11-24 | 2020-07-28 | Samsung Electronics Co., Ltd. | Data management method |
DE102016124168A1 (en) * | 2016-12-13 | 2018-06-14 | Endress+Hauser Conducta Gmbh+Co. Kg | Method for operating a specific field device via a mobile operating device |
CN106792853B (en) * | 2016-12-22 | 2020-05-12 | 青岛亿联客信息技术有限公司 | New equipment adding method for Bluetooth mesh network |
CN106713047A (en) * | 2017-01-12 | 2017-05-24 | 泰凌微电子(上海)有限公司 | Node upgrading method and system in mesh network |
US10433134B2 (en) | 2017-01-24 | 2019-10-01 | Arris Enterprises Llc | Video gateway as an internet of things mesh enhancer apparatus and method |
WO2018154891A1 (en) * | 2017-02-21 | 2018-08-30 | Omron Corporation | Method and control device for controlling a field device |
US10362612B2 (en) * | 2017-03-06 | 2019-07-23 | Citrix Systems, Inc. | Virtual private networking based on peer-to-peer communication |
WO2018162565A1 (en) * | 2017-03-08 | 2018-09-13 | Abb Schweiz Ag | Methods and devices for providing cyber security for time aware end-to-end packet flow networks |
DE102017106381A1 (en) | 2017-03-24 | 2018-09-27 | Newtec Gmbh | Method and apparatus for wirelessly transmitting a data signal |
WO2018191198A1 (en) * | 2017-04-10 | 2018-10-18 | Itron Networked Solutions, Inc. | Efficient internet-of-things device configuration via quick response codes |
US10116523B1 (en) * | 2017-04-12 | 2018-10-30 | Fisher-Rosemount Systems, Inc. | Predictive connectivity diagnostics for a wireless mesh network in a process control system |
US11229023B2 (en) | 2017-04-21 | 2022-01-18 | Netgear, Inc. | Secure communication in network access points |
US10605609B2 (en) | 2017-05-03 | 2020-03-31 | Microsoft Technology Licensing, Llc | Coupled interactive devices |
DE102017207871A1 (en) * | 2017-05-10 | 2018-11-15 | Tridonic Gmbh & Co Kg | Firmware Update-Over-The Air (FOTA) in building technology |
CN116629743A (en) | 2017-05-23 | 2023-08-22 | 沃尔玛阿波罗有限责任公司 | Automated inspection system |
US10389854B2 (en) * | 2017-06-15 | 2019-08-20 | Infinet, LLC | Method and system for forming an ad-hoc network over heterogeneous protocols |
US9955307B1 (en) * | 2017-08-03 | 2018-04-24 | Here Global B.V. | Distributed relative positioning |
US20210132932A1 (en) * | 2017-08-15 | 2021-05-06 | General Electric Company | Smart equipment, method used by smart equipment, and smart lamp |
US10666624B2 (en) * | 2017-08-23 | 2020-05-26 | Qualcomm Incorporated | Systems and methods for optimized network layer message processing |
CN107635215A (en) * | 2017-08-25 | 2018-01-26 | 西安电子科技大学 | Mesh network-building methods based on low-power consumption bluetooth |
US10951653B2 (en) | 2017-09-22 | 2021-03-16 | Samsung Electronics Co., Ltd. | Apparatus including secure component and method of provisioning security information into the apparatus |
CN107508714B (en) * | 2017-09-26 | 2020-09-15 | 深圳市微智电子有限公司 | Method and device for carrying out network configuration on Bluetooth equipment based on Bluetooth mesh |
US11057204B2 (en) * | 2017-10-04 | 2021-07-06 | Amir Keyvan Khandani | Methods for encrypted data communications |
CN109756324A (en) * | 2017-11-02 | 2019-05-14 | 大唐移动通信设备有限公司 | Cryptographic key negotiation method, terminal and gateway in a kind of Mesh network |
CN108064034A (en) * | 2017-11-17 | 2018-05-22 | 芯海科技(深圳)股份有限公司 | A kind of data collection network method of mesh networkings |
EP3489922B1 (en) | 2017-11-24 | 2022-01-05 | Andreas Stihl AG & Co. KG | Method of operating a wireless transmitter and a wireless receiver and system |
US10554562B2 (en) * | 2017-12-22 | 2020-02-04 | International Business Machines Corporation | Streaming network |
RU2666306C1 (en) * | 2017-12-27 | 2018-09-06 | федеральное государственное автономное образовательное учреждение высшего образования "Санкт-Петербургский политехнический университет Петра Великого" (ФГАОУ ВО "СПбПУ") | Method of controlling communication of single-range intercomputer data network |
US10607012B2 (en) | 2017-12-29 | 2020-03-31 | Delphian Systems, LLC | Bridge computing device control in local networks of interconnected devices |
US10706179B2 (en) * | 2018-01-10 | 2020-07-07 | General Electric Company | Secure provisioning of secrets into MPSoC devices using untrusted third-party systems |
KR102530441B1 (en) | 2018-01-29 | 2023-05-09 | 삼성전자주식회사 | Electronic device, external electronic device, system comprising the same and control method thereof |
US10944669B1 (en) | 2018-02-09 | 2021-03-09 | GoTenna, Inc. | System and method for efficient network-wide broadcast in a multi-hop wireless network using packet echos |
WO2019177505A1 (en) | 2018-03-16 | 2019-09-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and nodes for obtaining information regarding a bluetooth mesh network |
US11448632B2 (en) | 2018-03-19 | 2022-09-20 | Walmart Apollo, Llc | System and method for the determination of produce shelf life |
US11658865B2 (en) * | 2018-03-20 | 2023-05-23 | Delphian Systems, LLC | Updating devices in a local network of interconnected devices |
US10613505B2 (en) | 2018-03-29 | 2020-04-07 | Saudi Arabian Oil Company | Intelligent distributed industrial facility safety system |
US10311705B1 (en) * | 2018-03-29 | 2019-06-04 | Saudi Arabian Oil Company | Distributed industrial facility safety system |
US10303147B1 (en) | 2018-03-29 | 2019-05-28 | Saudi Arabian Oil Company | Distributed industrial facility safety system modular remote sensing devices |
US11018871B2 (en) * | 2018-03-30 | 2021-05-25 | Intel Corporation | Key protection for computing platform |
KR102114992B1 (en) * | 2018-04-25 | 2020-05-25 | (주)휴맥스 | Wireless communication equipment and method for configuring mesh network thereof |
US11308950B2 (en) | 2018-05-09 | 2022-04-19 | 4PLAN Corporation | Personal location system for virtual assistant |
US11146540B2 (en) * | 2018-05-09 | 2021-10-12 | Datalogic Ip Tech S.R.L. | Systems and methods for public key exchange employing a peer-to-peer protocol |
CN110493758B (en) | 2018-05-14 | 2023-01-13 | 阿里巴巴集团控股有限公司 | Bluetooth Mesh network and network distribution method, equipment and storage medium thereof |
CN110505606B (en) * | 2018-05-18 | 2022-12-02 | 阿里巴巴集团控股有限公司 | Bluetooth Mesh network and distribution network authentication method, equipment and storage medium thereof |
US10574475B2 (en) * | 2018-05-24 | 2020-02-25 | Haier Us Appliance Solutions, Inc. | Household appliance with bluetooth connection and authentication |
CN110636478B (en) | 2018-06-22 | 2023-04-14 | 阿里巴巴集团控股有限公司 | Bluetooth Mesh network system, communication method, device and storage medium thereof |
US10650023B2 (en) * | 2018-07-24 | 2020-05-12 | Booz Allen Hamilton, Inc. | Process for establishing trust between multiple autonomous systems for the purposes of command and control |
WO2020023762A1 (en) | 2018-07-26 | 2020-01-30 | Walmart Apollo, Llc | System and method for produce detection and classification |
EP3831021A1 (en) | 2018-07-27 | 2021-06-09 | Gotenna Inc. | VINEtm ZERO-CONTROL ROUTING USING DATA PACKET INSPECTION FOR WIRELESS MESH NETWORKS |
US11140659B2 (en) * | 2018-08-21 | 2021-10-05 | Signify Holding B.V. | Wireless organization of electrical devices by sensor manipulation |
US11368436B2 (en) * | 2018-08-28 | 2022-06-21 | Bae Systems Information And Electronic Systems Integration Inc. | Communication protocol |
US11715059B2 (en) * | 2018-10-12 | 2023-08-01 | Walmart Apollo, Llc | Systems and methods for condition compliance |
FI128520B (en) | 2018-11-14 | 2020-07-15 | Xiphera Oy | Method for providing a secret unique key for a volatile FPGA |
WO2020106332A1 (en) | 2018-11-20 | 2020-05-28 | Walmart Apollo, Llc | Systems and methods for assessing products |
WO2020123958A1 (en) * | 2018-12-14 | 2020-06-18 | Denso International America, Inc. | System and method of determining real-time location |
CN109673014B (en) * | 2019-01-25 | 2022-07-15 | 欧普照明股份有限公司 | Network combination method |
CN109862548B (en) * | 2019-03-06 | 2021-01-26 | 乐鑫信息科技(上海)股份有限公司 | Method for processing data packets at a node in a bluetooth Mesh network |
CN111669732B (en) * | 2019-03-06 | 2021-09-07 | 乐鑫信息科技(上海)股份有限公司 | Method for filtering redundant data packets at nodes in bluetooth Mesh network |
US11777715B2 (en) | 2019-05-15 | 2023-10-03 | Amir Keyvan Khandani | Method and apparatus for generating shared secrets |
CN111988268A (en) * | 2019-05-24 | 2020-11-24 | 魏文科 | Method for establishing and verifying input value by using asymmetric encryption algorithm and application thereof |
US11265410B2 (en) * | 2020-01-06 | 2022-03-01 | Vorbeck Materials Corp. | Self-organizing communications network nodes and systems |
EP3844935B1 (en) * | 2019-07-05 | 2023-02-22 | Samsung Electronics Co., Ltd. | System and method for dynamic group data protection |
CN110779500B (en) * | 2019-11-14 | 2021-11-30 | 中国人民解放军国防科技大学 | Mesoscale vortex detection method for incremental deployment sensor |
KR102324374B1 (en) | 2019-11-18 | 2021-11-11 | 한국전자통신연구원 | Method and apparatus for configuring cluster in wireless communication system |
US11432167B2 (en) | 2020-01-22 | 2022-08-30 | Abl Ip Holding Llc | Selective updating of nodes of a nodal wireless network |
US20210273920A1 (en) * | 2020-02-28 | 2021-09-02 | Vmware, Inc. | Secure certificate or key distribution for synchronous mobile device management (mdm) clients |
US11166253B2 (en) * | 2020-03-27 | 2021-11-02 | Dell Products L.P. | Data center automatic inventory and location data population and recovery using mesh network |
EP3968600A1 (en) * | 2020-09-11 | 2022-03-16 | Volkswagen Ag | Controlling a communication between a vehicle and a backend device |
WO2022148695A1 (en) * | 2021-01-06 | 2022-07-14 | Signify Holding B.V. | A method of, a node device and a system for relaying a message in a network comprising at least two mesh networks |
US20230266960A1 (en) * | 2022-02-24 | 2023-08-24 | Whirlpool Corporation | Systems and methods of offline over the air (ota) programming of appliances |
CN115051921B (en) * | 2022-05-27 | 2023-11-07 | 北京交通大学 | Self-adaptive heterogeneous network attribute information collection method |
US11870879B1 (en) * | 2023-01-04 | 2024-01-09 | Getac Technology Corporation | Device communication during emergent conditions |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060025180A1 (en) * | 2004-07-30 | 2006-02-02 | Qualcomm Incorporated | Method for waking a wireless device |
US20080279155A1 (en) * | 2007-04-13 | 2008-11-13 | Hart Communication Foundation | Adaptive Scheduling in a Wireless Network |
US20110128884A1 (en) * | 2008-07-29 | 2011-06-02 | France Telecom | Routing adaptable to electromagnetic conditions in a multihop network |
US20120087292A1 (en) * | 2010-10-07 | 2012-04-12 | Gm Global Technology Operations, Inc. | Adaptive Multi-Channel Access for Vehicular Networks |
Family Cites Families (184)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6079034A (en) * | 1997-12-05 | 2000-06-20 | Hewlett-Packard Company | Hub-embedded system for automated network fault detection and isolation |
EP1125419B1 (en) * | 1998-10-30 | 2009-08-26 | VirnetX Inc. | An agile network protocol for secure communications with assured system availability |
US6986046B1 (en) | 2000-05-12 | 2006-01-10 | Groove Networks, Incorporated | Method and apparatus for managing secure collaborative transactions |
US6836466B1 (en) * | 2000-05-26 | 2004-12-28 | Telcordia Technologies, Inc. | Method and system for measuring IP performance metrics |
US6745027B2 (en) | 2000-12-22 | 2004-06-01 | Seekernet Incorporated | Class switched networks for tracking articles |
US20030014507A1 (en) | 2001-03-13 | 2003-01-16 | International Business Machines Corporation | Method and system for providing performance analysis for clusters |
WO2002078272A1 (en) * | 2001-03-23 | 2002-10-03 | Kent Ridge Digital Labs | A method and system for providing bridged mobile ad-hoc networks |
US20030037237A1 (en) | 2001-04-09 | 2003-02-20 | Jean-Paul Abgrall | Systems and methods for computer device authentication |
DE10145596A1 (en) * | 2001-09-15 | 2003-04-03 | Philips Corp Intellectual Pty | Network with several sub-networks |
CA2460768A1 (en) | 2001-10-17 | 2003-04-24 | British Telecommunications Public Limited Company | Network location management system |
KR100408525B1 (en) * | 2001-10-31 | 2003-12-06 | 삼성전자주식회사 | System and method of network adaptive real- time multimedia streaming |
US7391731B1 (en) | 2002-03-07 | 2008-06-24 | Ibasis, Inc. | Method for determining best path |
US6917974B1 (en) * | 2002-01-03 | 2005-07-12 | The United States Of America As Represented By The Secretary Of The Air Force | Method and apparatus for preventing network traffic analysis |
CA2419767C (en) | 2002-02-25 | 2011-01-04 | Olsonet Communications Corporation | Method for routing ad-hoc signals |
US7532862B2 (en) | 2002-03-19 | 2009-05-12 | Apple Inc. | Method and apparatus for configuring a wireless device through reverse advertising |
US20030212821A1 (en) | 2002-05-13 | 2003-11-13 | Kiyon, Inc. | System and method for routing packets in a wired or wireless network |
US7251235B2 (en) | 2002-06-12 | 2007-07-31 | Conexant, Inc. | Event-based multichannel direct link |
US20040001483A1 (en) | 2002-06-27 | 2004-01-01 | Schmidt Kurt E. | Distribution and reconstruction of AD-HOC timing signals |
US7474874B2 (en) | 2002-06-28 | 2009-01-06 | Nokia Corporation | Local browsing |
US6898751B2 (en) * | 2002-07-31 | 2005-05-24 | Transdimension, Inc. | Method and system for optimizing polling in systems using negative acknowledgement protocols |
EP1540875A4 (en) | 2002-08-28 | 2011-01-26 | Ntt Docomo Inc | Certificate-based encryption and public key infrastructure |
GB0313473D0 (en) | 2003-06-11 | 2003-07-16 | Koninkl Philips Electronics Nv | Configuring a radio network for selective broadcast |
KR100547133B1 (en) | 2003-07-11 | 2006-01-26 | 삼성전자주식회사 | Apparatus and method for constructing ad-hoc network of heterogeneous terminals |
KR100640327B1 (en) * | 2003-11-24 | 2006-10-30 | 삼성전자주식회사 | The Frame Structure and Data Transmission Method for Bridge Operation of WPAN |
US20050175184A1 (en) * | 2004-02-11 | 2005-08-11 | Phonex Broadband Corporation | Method and apparatus for a per-packet encryption system |
US7436790B2 (en) | 2004-03-25 | 2008-10-14 | Research In Motion Limited | Wireless access point methods and apparatus for reduced power consumption and cost |
BRPI0511708A (en) | 2004-05-31 | 2008-01-08 | Matsushita Electric Ind Co Ltd | mobile terminal management device, mobile terminal, and communication system |
US7656901B2 (en) | 2004-08-10 | 2010-02-02 | Meshnetworks, Inc. | Software architecture and hardware abstraction layer for multi-radio routing and method for providing the same |
DE102004040069B3 (en) | 2004-08-18 | 2006-03-23 | Siemens Ag | Establishment of a wireless communication network with determination of local topology information from the identifiers of the communication devices |
US7747774B2 (en) * | 2004-08-23 | 2010-06-29 | At&T Intellectual Property I, L.P. | Methods, systems and computer program products for obscuring traffic in a distributed system |
WO2006053304A2 (en) | 2004-11-12 | 2006-05-18 | Pufco, Inc. | Volatile device keys and applications thereof |
KR100594127B1 (en) * | 2004-11-16 | 2006-06-28 | 삼성전자주식회사 | Bonding process method and device in a Bluetooth device |
US7496059B2 (en) * | 2004-12-09 | 2009-02-24 | Itt Manufacturing Enterprises, Inc. | Energy-efficient medium access control protocol and system for sensor networks |
US7533258B2 (en) | 2005-01-07 | 2009-05-12 | Cisco Technology, Inc. | Using a network-service credential for access control |
JP4550636B2 (en) * | 2005-03-18 | 2010-09-22 | 富士通株式会社 | Electronic device, its registration method and registration program |
US7522540B1 (en) | 2005-04-15 | 2009-04-21 | Nvidia Corporation | Extended service set mesh topology discovery |
US8027289B2 (en) * | 2005-04-27 | 2011-09-27 | Raytheon Bbn Technologies Corp. | Ultra-low latency packet transport in ad hoc networks |
US7653011B2 (en) | 2005-05-31 | 2010-01-26 | Cisco Technology, Inc. | Spanning tree protocol for wireless networks |
US7606178B2 (en) | 2005-05-31 | 2009-10-20 | Cisco Technology, Inc. | Multiple wireless spanning tree protocol for use in a wireless mesh network |
US7894372B2 (en) | 2005-05-31 | 2011-02-22 | Iac Search & Media, Inc. | Topology-centric resource management for large scale service clusters |
KR20080025095A (en) | 2005-06-01 | 2008-03-19 | 밀레니얼 넷, 인크. | Communicating over a wireless network |
US9654200B2 (en) | 2005-07-18 | 2017-05-16 | Mutualink, Inc. | System and method for dynamic wireless aerial mesh network |
GB2467657B (en) * | 2005-07-21 | 2010-09-15 | Firetide Inc | Method for enabling the efficient operation of arbitrarily interconnected mesh networks |
US7787361B2 (en) | 2005-07-29 | 2010-08-31 | Cisco Technology, Inc. | Hybrid distance vector protocol for wireless mesh networks |
US8948805B2 (en) * | 2005-08-26 | 2015-02-03 | Qualcomm Incorporated | Method and apparatus for reliable transmit power and timing control in wireless communication |
US7778270B1 (en) | 2005-08-31 | 2010-08-17 | Hrl Laboratories, Llc | Code-switching in wireless multi-hop networks |
US7546139B2 (en) | 2005-12-27 | 2009-06-09 | F4W, Inc. | System and method for establishing and maintaining communications across disparate networks |
US20100005294A1 (en) * | 2005-10-18 | 2010-01-07 | Kari Kostiainen | Security in Wireless Environments Using Out-Of-Band Channel Communication |
JP4641245B2 (en) | 2005-10-26 | 2011-03-02 | 三菱電機株式会社 | Ad hoc network system, wireless ad hoc terminal and failure detection method thereof |
US7978666B2 (en) * | 2005-10-31 | 2011-07-12 | Robert Bosch Gmbh | Node control in wireless sensor networks |
US7539488B2 (en) | 2005-11-09 | 2009-05-26 | Texas Instruments Norway As | Over-the-air download (OAD) methods and apparatus for use in facilitating application programming in wireless network devices of ad hoc wireless communication networks |
US20070110024A1 (en) | 2005-11-14 | 2007-05-17 | Cisco Technology, Inc. | System and method for spanning tree cross routes |
US7593376B2 (en) | 2005-12-07 | 2009-09-22 | Motorola, Inc. | Method and apparatus for broadcast in an ad hoc network using elected broadcast relay nodes |
US20130219482A1 (en) | 2006-01-31 | 2013-08-22 | Sigma Designs, Inc. | Method for uniquely addressing a group of network units in a sub-network |
US7848261B2 (en) * | 2006-02-17 | 2010-12-07 | Isilon Systems, Inc. | Systems and methods for providing a quiescing protocol |
US8023478B2 (en) | 2006-03-06 | 2011-09-20 | Cisco Technology, Inc. | System and method for securing mesh access points in a wireless mesh network, including rapid roaming |
US7647078B2 (en) * | 2006-03-07 | 2010-01-12 | Samsung Electronics Co., Ltd. | Power-saving method for wireless sensor network |
US8340106B2 (en) * | 2006-03-13 | 2012-12-25 | Microsoft Corporation | Connecting multi-hop mesh networks using MAC bridge |
US8519566B2 (en) | 2006-03-28 | 2013-08-27 | Wireless Environment, Llc | Remote switch sensing in lighting devices |
US8681671B1 (en) * | 2006-04-25 | 2014-03-25 | Cisco Technology, Inc. | System and method for reducing power used for radio transmission and reception |
US7786885B2 (en) | 2006-04-25 | 2010-08-31 | Hrl Laboratories, Llc | Event localization within a distributed sensor array |
US8406794B2 (en) | 2006-04-26 | 2013-03-26 | Qualcomm Incorporated | Methods and apparatuses of initiating communication in wireless networks |
CN101083597A (en) | 2006-05-31 | 2007-12-05 | 朗迅科技公司 | SIP based instant message of mobile self-organizing network |
DE102006036109B4 (en) | 2006-06-01 | 2008-06-19 | Nokia Siemens Networks Gmbh & Co.Kg | Method and system for providing a mesh key |
EP2041910A4 (en) * | 2006-07-06 | 2013-05-22 | Apple Inc | Wireless access point security for multi-hop networks |
FR2903830B1 (en) | 2006-07-11 | 2008-08-22 | Alcatel Sa | METHOD AND DEVICE FOR MONITORING OPTICAL CONNECTION PATHS FOR A TRANSPARENT OPTICAL NETWORK |
US8411651B2 (en) | 2006-07-27 | 2013-04-02 | Interdigital Technology Corporation | Media independent multi-rat function in a converged device |
EP1892913A1 (en) | 2006-08-24 | 2008-02-27 | Siemens Aktiengesellschaft | Method and arrangement for providing a wireless mesh network |
US8634342B2 (en) | 2006-10-05 | 2014-01-21 | Cisco Technology, Inc. | Upgrading mesh access points in a wireless mesh network |
US8270302B2 (en) | 2006-10-20 | 2012-09-18 | Stmicroelectronics, Inc. | System and method for providing an adaptive value of TTL (time to live) for broadcast/multicast messages in a mesh network using a hybrid wireless mesh protocol |
US8149748B2 (en) | 2006-11-14 | 2012-04-03 | Raytheon Company | Wireless data networking |
KR100879026B1 (en) | 2006-12-05 | 2009-01-15 | 한국전자통신연구원 | Method for grouping among sensor nodes in heterogeneous wireless sensor networks |
US8838481B2 (en) * | 2011-07-26 | 2014-09-16 | Golba Llc | Method and system for location based hands-free payment |
US8270340B2 (en) | 2006-12-19 | 2012-09-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of idle gap commands in a telecommunication system |
US9760146B2 (en) | 2007-01-08 | 2017-09-12 | Imagination Technologies Limited | Conditional activation and deactivation of a microprocessor |
US7787427B1 (en) | 2007-01-09 | 2010-08-31 | Dust Networks, Inc. | Providing low average latency communication in wireless mesh networks |
US20080205385A1 (en) | 2007-02-26 | 2008-08-28 | Motorola, Inc. | Data frame formats to improve groupcast efficiency in multi-hop wireless networks |
US8676219B2 (en) | 2007-04-13 | 2014-03-18 | Hart Communication Foundation | Combined wired and wireless communications with field devices in a process control environment |
US8451752B2 (en) | 2007-05-21 | 2013-05-28 | Arrowspan, Inc. | Seamless handoff scheme for multi-radio wireless mesh network |
US20080292105A1 (en) | 2007-05-22 | 2008-11-27 | Chieh-Yih Wan | Lightweight key distribution and management method for sensor networks |
MX2010001248A (en) * | 2007-08-01 | 2010-03-01 | Philip Morris Prod | Degradable cigarette filters. |
US8189506B2 (en) * | 2007-09-12 | 2012-05-29 | Nokia Corporation | Deep sleep mode for mesh points |
KR101405688B1 (en) | 2007-09-14 | 2014-06-12 | 엘지이노텍 주식회사 | Zigbee system |
US20090089408A1 (en) | 2007-09-28 | 2009-04-02 | Alcatel Lucent | XML Router and method of XML Router Network Overlay Topology Creation |
US7941663B2 (en) | 2007-10-23 | 2011-05-10 | Futurewei Technologies, Inc. | Authentication of 6LoWPAN nodes using EAP-GPSK |
CN101855861A (en) | 2007-11-16 | 2010-10-06 | 富士通天株式会社 | Authentication method, authentication system, on-vehicle device, and authentication device |
US9166934B2 (en) | 2007-11-25 | 2015-10-20 | Trilliant Networks, Inc. | System and method for operating mesh devices in multi-tree overlapping mesh networks |
US8289883B2 (en) | 2007-12-21 | 2012-10-16 | Samsung Electronics Co., Ltd. | Hybrid multicast routing protocol for wireless mesh networks |
US7929446B2 (en) | 2008-01-04 | 2011-04-19 | Radiient Technologies, Inc. | Mesh networking for wireless communications |
KR20090090461A (en) * | 2008-02-21 | 2009-08-26 | 삼성전자주식회사 | Method for prolonging lifetime of sensor nodes in a wireless sensor network and system therefor |
JP4613969B2 (en) | 2008-03-03 | 2011-01-19 | ソニー株式会社 | Communication apparatus and communication method |
US8116247B2 (en) * | 2008-03-11 | 2012-02-14 | Nokia Siemens Networks Oy | Adaptive mechanism for dynamic reconfiguration of mesh networks |
US8923285B2 (en) | 2008-04-30 | 2014-12-30 | Qualcomm Incorporated | Apparatus and methods for transmitting data over a wireless mesh network |
US8179845B2 (en) | 2008-08-21 | 2012-05-15 | Motorola Solutions, Inc. | Antenna-aware method for transmitting packets in a wireless communication network |
US8699377B2 (en) | 2008-09-04 | 2014-04-15 | Trilliant Networks, Inc. | System and method for implementing mesh network communications using a mesh network protocol |
US9485649B2 (en) | 2008-09-25 | 2016-11-01 | Fisher-Rosemount Systems, Inc. | Wireless mesh network with pinch point and low battery alerts |
GB2464125A (en) | 2008-10-04 | 2010-04-07 | Ibm | Topology discovery comprising partitioning network nodes into groups and using multiple discovery agents operating concurrently in each group. |
US8782746B2 (en) | 2008-10-17 | 2014-07-15 | Comcast Cable Communications, Llc | System and method for supporting multiple identities for a secure identity device |
EP2350910B1 (en) * | 2008-11-24 | 2018-07-25 | Certicom Corp. | System and method for hardware based security |
US8294573B2 (en) | 2008-12-11 | 2012-10-23 | International Business Machines Corporation | System and method for optimizing power consumption of container tracking devices through mesh networks |
US8498229B2 (en) | 2008-12-30 | 2013-07-30 | Intel Corporation | Reduced power state network processing |
US8904177B2 (en) * | 2009-01-27 | 2014-12-02 | Sony Corporation | Authentication for a multi-tier wireless home mesh network |
US8254251B2 (en) | 2009-02-03 | 2012-08-28 | Mobix Wireless Solutions Ltd. | Mesh hybrid communication network |
US8964634B2 (en) | 2009-02-06 | 2015-02-24 | Sony Corporation | Wireless home mesh network bridging adaptor |
US9172612B2 (en) | 2009-02-12 | 2015-10-27 | Hewlett-Packard Development Company, L.P. | Network device configuration management by physical location |
EP2528279A3 (en) | 2009-02-13 | 2013-03-27 | Nokia Siemens Networks Oy | Method, system and nodes for network topology detection in communication networks |
US8194576B2 (en) | 2009-03-27 | 2012-06-05 | Research In Motion Limited | Wireless access point methods and apparatus using dynamically-activated service intervals |
US8171292B2 (en) | 2009-04-08 | 2012-05-01 | Research In Motion Limited | Systems, devices, and methods for securely transmitting a security parameter to a computing device |
US9069727B2 (en) * | 2011-08-12 | 2015-06-30 | Talari Networks Incorporated | Adaptive private network with geographically redundant network control nodes |
CN102474279B (en) * | 2009-07-23 | 2015-03-25 | 诺基亚公司 | Method and apparatus for reduced power consumption when operating as a bluetooth low energy device |
KR20110020005A (en) * | 2009-08-21 | 2011-03-02 | 주식회사 팬택 | Method for tranmitting and receiving data in wireless communication system |
JP5338567B2 (en) * | 2009-08-25 | 2013-11-13 | 沖電気工業株式会社 | Wireless terminal and wireless system |
US8879994B2 (en) | 2009-10-02 | 2014-11-04 | Blackberry Limited | Methods and devices for facilitating Bluetooth pairing using a camera as a barcode scanner |
EP2306692B1 (en) * | 2009-10-02 | 2014-05-21 | BlackBerry Limited | Methods and devices for facilitating bluetooth pairing using a camera as a barcode scanner |
US20150058409A1 (en) | 2013-03-22 | 2015-02-26 | Frank C. Wang | Enhanced content delivery system and method spanning multiple data processing systems |
EP2486697B1 (en) | 2009-10-06 | 2013-12-11 | Thomson Licensing | A method and apparatus for hop-by hop reliable multicast in wireless networks |
CN102045280B (en) | 2009-10-26 | 2013-08-07 | 国基电子(上海)有限公司 | Cable modem (CM) and certificate test method thereof |
JP5544863B2 (en) | 2009-12-17 | 2014-07-09 | 富士通株式会社 | Reception device, reception method, and reception program |
CN101729296B (en) | 2009-12-29 | 2012-12-19 | 中兴通讯股份有限公司 | Method and system for statistical analysis of ethernet traffic |
KR101727130B1 (en) | 2010-01-20 | 2017-04-14 | 인트린직 아이디 비브이 | Device and method for obtaining a cryptographic key |
US10645628B2 (en) | 2010-03-04 | 2020-05-05 | Rosemount Inc. | Apparatus for interconnecting wireless networks separated by a barrier |
US8495618B1 (en) | 2010-03-31 | 2013-07-23 | American Megatrends, Inc. | Updating firmware in a high availability enabled computer system |
US8516269B1 (en) | 2010-07-28 | 2013-08-20 | Sandia Corporation | Hardware device to physical structure binding and authentication |
WO2012064178A1 (en) * | 2010-11-11 | 2012-05-18 | Mimos Berhad | Method for use in providing an adaptable sensor nodes schedule in a wireless sensor network |
CN103222241B (en) | 2010-11-25 | 2017-10-03 | 飞利浦灯具控股公司 | System and method for the data transfer of the node that is optimized to wireless mesh network |
US8873526B2 (en) | 2010-12-17 | 2014-10-28 | Cisco Technology, Inc. | Collision avoidance for wireless networks |
US20120163292A1 (en) | 2010-12-23 | 2012-06-28 | Nokia Corporation | Frame Header in Wireless Communication System |
US9094316B2 (en) | 2011-01-28 | 2015-07-28 | Hewlett-Packard Development Company, L.P. | Dynamic name generation |
US20120198434A1 (en) | 2011-01-31 | 2012-08-02 | Digi International Inc. | Virtual bundling of remote device firmware upgrade |
US8769525B2 (en) | 2011-01-31 | 2014-07-01 | Digi International Inc. | Remote firmware upgrade device mapping |
US20120196534A1 (en) | 2011-02-01 | 2012-08-02 | Nokia Corporation | Method, apparatus, and computer program product for broadcasting in short-range communication |
WO2012122994A1 (en) | 2011-03-11 | 2012-09-20 | Kreft Heinz | Off-line transfer of electronic tokens between peer-devices |
US9716659B2 (en) * | 2011-03-23 | 2017-07-25 | Hughes Network Systems, Llc | System and method for providing improved quality of service over broadband networks |
US9268545B2 (en) * | 2011-03-31 | 2016-02-23 | Intel Corporation | Connecting mobile devices, internet-connected hosts, and cloud services |
CN102761941B (en) | 2011-04-28 | 2016-08-03 | 北京云天创科技有限公司 | A kind of method utilizing ultra-low power consumption wireless smart sensor's network protocol transmission |
US20130128809A1 (en) | 2011-05-19 | 2013-05-23 | Qualcomm Incorporated | Apparatus and methods for media access control header compression |
US8553536B2 (en) | 2011-07-12 | 2013-10-08 | General Electric Company | Mesh network management system |
CN102355351B (en) | 2011-07-21 | 2014-11-05 | 华为技术有限公司 | Key generation, backup and migration method and system based on trusted computing |
US8849202B2 (en) | 2011-08-19 | 2014-09-30 | Apple Inc. | Audio transfer using the Bluetooth Low Energy standard |
US8982785B2 (en) | 2011-09-08 | 2015-03-17 | Cisco Technology, Inc. | Access point assisted direct client discovery |
US9445305B2 (en) | 2011-09-12 | 2016-09-13 | Microsoft Corporation | Low energy beacon encoding |
GB2510721B (en) | 2011-09-15 | 2020-02-26 | Fisher Rosemount Systems Inc | Communicating data frames across communication networks that use incompatible network routing protocols |
US8892866B2 (en) | 2011-09-26 | 2014-11-18 | Tor Anumana, Inc. | Secure cloud storage and synchronization systems and methods |
US8649883B2 (en) | 2011-10-04 | 2014-02-11 | Advanergy, Inc. | Power distribution system and method |
WO2013057666A1 (en) | 2011-10-17 | 2013-04-25 | Koninklijke Philips Electronics N.V. | Automatic recommissioning of electronic devices in a networked system |
US8654869B2 (en) | 2011-10-27 | 2014-02-18 | Cooper Technologies Company | Multi-path radio transmission input/output devices, network, systems and methods with link suitability determination |
US9936382B2 (en) * | 2011-11-21 | 2018-04-03 | Vital Connect, Inc. | Method and system for pairing a sensor device to a user |
US8953790B2 (en) | 2011-11-21 | 2015-02-10 | Broadcom Corporation | Secure generation of a device root key in the field |
US9191461B2 (en) | 2012-02-21 | 2015-11-17 | Entropic Communications, Inc. | Software upgrade using layer-2 management entity messaging |
US9270584B2 (en) * | 2012-02-28 | 2016-02-23 | Cisco Technology, Inc. | Diverse paths using a single source route in computer networks |
US9172636B2 (en) | 2012-02-28 | 2015-10-27 | Cisco Technology, Inc. | Efficient link repair mechanism triggered by data traffic |
US20130279410A1 (en) | 2012-04-18 | 2013-10-24 | Draker, Inc. | Communicating Data in a Mesh Network |
US9629063B2 (en) | 2012-05-09 | 2017-04-18 | Trellisware Technologies, Inc. | Method and system for global topology discovery in multi-hop ad hoc networks |
US8844026B2 (en) | 2012-06-01 | 2014-09-23 | Blackberry Limited | System and method for controlling access to secure resources |
US20150195692A1 (en) | 2012-06-26 | 2015-07-09 | Nokia Corporation | Method and apparatus for providing device ringtone coordination |
US8751615B2 (en) | 2012-07-18 | 2014-06-10 | Accedian Networks Inc. | Systems and methods of discovering and controlling devices without explicit addressing |
JP5881047B2 (en) | 2012-08-08 | 2016-03-09 | 株式会社日立製作所 | Network management system, network management computer, and network management method |
WO2014039540A1 (en) | 2012-09-05 | 2014-03-13 | Interdigital Patent Holdings, Inc. | Methods for mac frame extensibility and frame specific mac header design for wlan systems |
US9081643B2 (en) | 2012-09-21 | 2015-07-14 | Silver Sring Networks, Inc. | System and method for efficiently updating firmware for nodes in a mesh network |
US9208676B2 (en) | 2013-03-14 | 2015-12-08 | Google Inc. | Devices, methods, and associated information processing for security in a smart-sensored home |
US9279856B2 (en) | 2012-10-22 | 2016-03-08 | Infineon Technologies Ag | Die, chip, method for driving a die or a chip and method for manufacturing a die or a chip |
US9306660B2 (en) * | 2012-10-22 | 2016-04-05 | Qualcomm Technologies International, Ltd. | Dynamic interactive zone driven proximity awareness system |
CN102984798B (en) | 2012-11-21 | 2016-02-03 | 越亮传奇科技股份有限公司 | Position-based accurate positioning method |
US20140167912A1 (en) | 2012-12-17 | 2014-06-19 | David M. Snyder | System, method and apparatus for providing security systems integrated with solid state lighting systems |
US20140171062A1 (en) | 2012-12-19 | 2014-06-19 | Telefonaktiebolaget L M Ericsson (Publ) | Wireless Devices, Network Node and Methods for Handling Relay Assistance in a Wireless Communications Network |
US9628373B2 (en) | 2012-12-19 | 2017-04-18 | Comcast Cable Communications, Llc | Multipath communication in a network |
WO2014098504A1 (en) | 2012-12-19 | 2014-06-26 | 엘지전자 주식회사 | Method for communicating in wireless communication system supporting multiple access network and apparatus supporting same |
US20140181172A1 (en) | 2012-12-20 | 2014-06-26 | Brent J. Elliott | Offloading tethering-related communication processing |
US9699768B2 (en) | 2012-12-26 | 2017-07-04 | Ict Research Llc | Mobility extensions to industrial-strength wireless sensor networks |
US9032480B2 (en) | 2012-12-28 | 2015-05-12 | Cellco Partnership | Providing multiple APN connections support in a browser |
US8938792B2 (en) | 2012-12-28 | 2015-01-20 | Intel Corporation | Device authentication using a physically unclonable functions based key generation system |
US9239723B2 (en) | 2013-05-13 | 2016-01-19 | Lenovo (Singapore) Pte. Ltd. | Configuring a device based on proximity to other devices |
US9264892B2 (en) | 2013-07-03 | 2016-02-16 | Verizon Patent And Licensing Inc. | Method and apparatus for attack resistant mesh networks |
US9983651B2 (en) | 2013-07-15 | 2018-05-29 | Google Technology Holdings LLC | Low-power near-field communication authentication |
US9386008B2 (en) | 2013-08-19 | 2016-07-05 | Smartguard, Llc | Secure installation of encryption enabling software onto electronic devices |
US20150071216A1 (en) | 2013-09-09 | 2015-03-12 | Qualcomm Connected Experiences, Inc. | Allowing mass re-onboarding of headless devices |
US9565576B2 (en) | 2013-10-09 | 2017-02-07 | At&T Intellectual Property I, L.P. | Network operating system client architecture for mobile user equipment |
US10591969B2 (en) | 2013-10-25 | 2020-03-17 | Google Technology Holdings LLC | Sensor-based near-field communication authentication |
US20150143130A1 (en) | 2013-11-18 | 2015-05-21 | Vixs Systems Inc. | Integrated circuit provisioning using physical unclonable function |
GB2512733B (en) | 2014-02-25 | 2018-09-05 | Qualcomm Technologies Int Ltd | Broadcast retransmission |
GB2517844B (en) | 2014-02-25 | 2015-09-09 | Cambridge Silicon Radio Ltd | Thwarting traffic analysis |
GB2515853B (en) | 2014-02-25 | 2015-08-19 | Cambridge Silicon Radio Ltd | Latency mitigation |
US9660836B2 (en) | 2014-05-06 | 2017-05-23 | Lattice Semiconductor Corporation | Network topology discovery |
US10142799B2 (en) * | 2014-08-19 | 2018-11-27 | Qualcomm Incorporated | Multicasting traffic using multi-connectivity |
-
2014
- 2014-03-31 GB GB1415178.1A patent/GB2517844B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1405786.3A patent/GB2512746B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1405797.0A patent/GB2512749B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1405785.5A patent/GB2512501A/en not_active Withdrawn
- 2014-03-31 GB GB1405789.7A patent/GB2512502B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1405791.3A patent/GB2512748B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1415177.3A patent/GB2515923B8/en not_active Expired - Fee Related
- 2014-03-31 GB GB1421698.0A patent/GB2523444B/en not_active Expired - Fee Related
- 2014-03-31 GB GB1405790.5A patent/GB2512747B/en not_active Expired - Fee Related
- 2014-05-06 US US14/270,884 patent/US20150244648A1/en not_active Abandoned
- 2014-05-06 US US14/270,961 patent/US10055570B2/en active Active
- 2014-06-05 US US14/297,324 patent/US9489506B2/en active Active
- 2014-06-06 US US14/298,177 patent/US20150245203A1/en not_active Abandoned
- 2014-06-26 US US14/316,529 patent/US20150244828A1/en not_active Abandoned
- 2014-06-26 US US14/316,404 patent/US20150245204A1/en not_active Abandoned
- 2014-07-17 GB GB1501075.4A patent/GB2518120B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412719.5A patent/GB2512545B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412720.3A patent/GB2513048B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412716.1A patent/GB2512542B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412714.6A patent/GB2512256B8/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412715.3A patent/GB2513265B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412722.9A patent/GB2512781B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412718.7A patent/GB2512544B/en not_active Expired - Fee Related
- 2014-07-17 GB GB1412717.9A patent/GB2512543B/en not_active Expired - Fee Related
- 2014-08-19 DE DE102014012257.3A patent/DE102014012257B4/en not_active Expired - Fee Related
- 2014-08-19 DE DE102014012258.1A patent/DE102014012258A1/en not_active Withdrawn
- 2014-08-19 DE DE102014019749.2A patent/DE102014019749B3/en not_active Expired - Fee Related
- 2014-08-19 DE DE102014012252.2A patent/DE102014012252A1/en not_active Ceased
- 2014-08-20 DE DE102014012379.0A patent/DE102014012379B4/en not_active Expired - Fee Related
- 2014-08-25 DE DE102014012517.3A patent/DE102014012517B4/en not_active Expired - Fee Related
- 2014-08-25 DE DE102014012518.1A patent/DE102014012518A1/en not_active Withdrawn
- 2014-09-11 DE DE102014013471.7A patent/DE102014013471A1/en not_active Withdrawn
- 2014-10-02 US US14/505,454 patent/US9842202B2/en not_active Expired - Fee Related
- 2014-10-02 US US14/505,465 patent/US20150244565A1/en not_active Abandoned
- 2014-10-02 US US14/505,458 patent/US9672346B2/en active Active
- 2014-10-02 US US14/505,466 patent/US20150244623A1/en not_active Abandoned
- 2014-10-02 US US14/505,399 patent/US9910976B2/en active Active
- 2014-10-02 US US14/505,437 patent/US20150245369A1/en not_active Abandoned
- 2014-10-02 US US14/505,443 patent/US9754096B2/en active Active
- 2014-10-02 US US14/505,418 patent/US20150242614A1/en not_active Abandoned
-
2015
- 2015-02-04 DE DE102015101620.6A patent/DE102015101620A1/en not_active Withdrawn
- 2015-02-04 DE DE102015101604.4A patent/DE102015101604A1/en not_active Withdrawn
- 2015-02-05 DE DE102015101698.2A patent/DE102015101698A1/en not_active Withdrawn
- 2015-02-05 DE DE102015101697.4A patent/DE102015101697A1/en not_active Withdrawn
- 2015-02-05 DE DE102015101699.0A patent/DE102015101699B4/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060025180A1 (en) * | 2004-07-30 | 2006-02-02 | Qualcomm Incorporated | Method for waking a wireless device |
US20080279155A1 (en) * | 2007-04-13 | 2008-11-13 | Hart Communication Foundation | Adaptive Scheduling in a Wireless Network |
US20110128884A1 (en) * | 2008-07-29 | 2011-06-02 | France Telecom | Routing adaptable to electromagnetic conditions in a multihop network |
US20120087292A1 (en) * | 2010-10-07 | 2012-04-12 | Gm Global Technology Operations, Inc. | Adaptive Multi-Channel Access for Vehicular Networks |
Cited By (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10055570B2 (en) | 2014-02-25 | 2018-08-21 | QUALCOMM Technologies International, Ltd | Mesh relay |
US9672346B2 (en) | 2014-02-25 | 2017-06-06 | Qualcomm Technologies International, Ltd. | Object tracking by establishing a mesh network and transmitting packets |
US9692538B2 (en) | 2014-02-25 | 2017-06-27 | Qualcomm Technologies International, Ltd. | Latency mitigation |
US9489506B2 (en) | 2014-02-25 | 2016-11-08 | Qualcomm Technologies International, Ltd. | Linking ad hoc networks |
US9754096B2 (en) | 2014-02-25 | 2017-09-05 | Qualcomm Technologies International, Ltd. | Update management |
US9842202B2 (en) | 2014-02-25 | 2017-12-12 | Qualcomm Technologies International, Ltd. | Device proximity |
US9910976B2 (en) | 2014-02-25 | 2018-03-06 | Qualcomm Technologies International, Ltd. | Processing mesh communications |
US10624028B2 (en) | 2015-02-26 | 2020-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Energy efficient BLE mesh initialisation and operation |
US10313540B2 (en) * | 2015-03-12 | 2019-06-04 | Canon Kabushiki Kaisha | Information processing apparatus, control method thereof, and storage medium |
WO2017059206A1 (en) * | 2015-09-30 | 2017-04-06 | Fossil Group, Inc. | Systems, devices, and methods for simulataneously exchanging messages between a low-energy radio device and multiple communication devices |
CN108702720A (en) * | 2016-02-24 | 2018-10-23 | 高通股份有限公司 | Source device broadcasts synchronizing information associated with bluetooth equal ratio channel |
KR20180117618A (en) * | 2016-02-24 | 2018-10-29 | 퀄컴 인코포레이티드 | A source device that broadcasts synchronization information associated with a Bluetooth isochronous channel |
US10148453B2 (en) | 2016-02-24 | 2018-12-04 | Qualcomm Incorporated | Using update slot to synchronize to Bluetooth LE isochronous channel and communicate state changes |
KR101971183B1 (en) | 2016-02-24 | 2019-04-22 | 퀄컴 인코포레이티드 | A source device that broadcasts synchronization information associated with a Bluetooth isochronous channel |
WO2017146829A1 (en) * | 2016-02-24 | 2017-08-31 | Qualcomm Incorporated | A source device broadcasts synchronization information associated with a bluetooth isochronous channel |
US10644746B2 (en) | 2016-04-29 | 2020-05-05 | Texas Instruments Incorporated | Pseudo channel hopping using scan dwell times in mesh networks without time synchronization |
US11705937B2 (en) | 2016-04-29 | 2023-07-18 | Texas Instruments Incorporated | Pseudo channel hopping in mesh networks without time synchronization |
US11394423B2 (en) | 2016-04-29 | 2022-07-19 | Texas Instruments Incorporated | Pseudo channel hopping using scan dwell times in mesh networks without time synchronization |
US10951261B2 (en) | 2016-04-29 | 2021-03-16 | Texas Instruments Incorporated | Pseudo channel hopping in mesh networks without time synchronization |
US20190215673A1 (en) * | 2016-08-22 | 2019-07-11 | Lg Electronics Inc. | Method for controlling device by using bluetooth technology, and apparatus |
US10798548B2 (en) * | 2016-08-22 | 2020-10-06 | Lg Electronics Inc. | Method for controlling device by using Bluetooth technology, and apparatus |
US11789008B2 (en) * | 2016-12-20 | 2023-10-17 | Abbott Diabetes Care Inc. | Systems, devices, and methods for wireless communications in analyte monitoring systems |
US20180172664A1 (en) * | 2016-12-20 | 2018-06-21 | Abbott Diabetes Care Inc. | Systems, devices, and methods for wireless communications in analyte monitoring systems |
US20230145119A1 (en) * | 2016-12-20 | 2023-05-11 | Abbott Diabetes Care Inc. | Systems, devices, and methods for wireless communications in analyte monitoring systems |
US11490400B2 (en) * | 2017-11-15 | 2022-11-01 | Telefonaktiebolaget Lm Ericsson (Publ) | End node, relay node, and methods performed therein for handling transmission of information |
US11246132B2 (en) * | 2017-11-28 | 2022-02-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Message transmission with reduced interference |
WO2019117763A1 (en) * | 2017-12-11 | 2019-06-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Channel scanning in a mesh network |
US10880778B2 (en) | 2018-03-23 | 2020-12-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Message cache management in a mesh network |
US10869227B2 (en) * | 2018-03-23 | 2020-12-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Message cache management in a mesh network |
US20200059827A1 (en) * | 2018-03-23 | 2020-02-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Message Cache Management in a Mesh Network |
CN111886843A (en) * | 2018-06-13 | 2020-11-03 | 卧安科技(深圳)有限公司 | Low power consumption Bluetooth network maintenance method, electronic device, Bluetooth network and medium |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150245369A1 (en) | Communicating data over a mesh network | |
US11570790B2 (en) | Coexistence of wireless sensor networks with other wireless networks | |
Rowe et al. | RT-Link: A time-synchronized link protocol for energy-constrained multi-hop wireless networks | |
US8514758B2 (en) | Low-power wireless multi-hop networks | |
WO2018028416A1 (en) | Electronic device and method used for network control terminal and network node | |
Hsu et al. | Joint design of asynchronous sleep-wake scheduling and opportunistic routing in wireless sensor networks | |
US9226253B2 (en) | Passive synchronization in wireless networks | |
US20100290379A1 (en) | Method for wireless multi-hop network | |
US9826493B2 (en) | Synchronized multi-sink routing for wireless networks | |
JP2015505206A (en) | Wireless sensor network, method and computer program for routing at least one data packet within a wireless sensor network | |
US10070388B2 (en) | Coordinated duty cycle assignment in mesh networks | |
Rowe et al. | RT-Link: A global time-synchronized link protocol for sensor networks | |
US10397872B2 (en) | Systems and methods for providing communications with an improved network frame structure architecture within wireless sensor networks | |
JP6871318B2 (en) | Wireless mesh network and data transmission method | |
US8300756B2 (en) | Intermittent operative communication apparatus adaptively controlling the timing of waiting data reception and a method therefor | |
Guerroumi et al. | On the medium access control protocols suitable for wireless sensor networks-a survey | |
JP5617929B2 (en) | Wireless station, communication system, and communication method | |
JP4975427B2 (en) | Wireless communication apparatus and wireless communication method | |
JP6583497B1 (en) | Wireless communication apparatus, wireless communication program, and wireless communication system | |
Cho et al. | Density‐adaptive network reprogramming protocol for wireless sensor networks | |
JP6382046B2 (en) | Broadcast communication system, broadcast communication method, and intermittent operation wireless terminal for wireless communication network | |
KR20170052508A (en) | loT BROADCASTING NETWORK FOR LOW POWER WIRELESS SENSOR NETWORK | |
Minh et al. | Reducing idle listening time in pipeline-forwarding MAC protocols of wireless sensor networks | |
Parsch et al. | A reliable MAC for delay-bounded and energy-efficient WSNs | |
Kweon et al. | A retransmission-enhanced duty-cycle MAC protocol based on the channel quality for wireless sensor networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CAMBRIDGE SILICON RADIO LIMITED, UNITED KINGDOM Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEYDON, ROBIN;REEL/FRAME:033892/0904 Effective date: 20140909 |
|
AS | Assignment |
Owner name: QUALCOMM TECHNOLOGIES INTERNATIONAL, LTD., UNITED Free format text: CHANGE OF NAME;ASSIGNOR:CAMBRIDGE SILICON RADIO LIMITED;REEL/FRAME:036663/0211 Effective date: 20150813 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |