WO2012118531A1 - Discovery of conventional network devices and bridges - Google Patents

Discovery of conventional network devices and bridges Download PDF

Info

Publication number
WO2012118531A1
WO2012118531A1 PCT/US2011/058506 US2011058506W WO2012118531A1 WO 2012118531 A1 WO2012118531 A1 WO 2012118531A1 US 2011058506 W US2011058506 W US 2011058506W WO 2012118531 A1 WO2012118531 A1 WO 2012118531A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
class
devices
network device
hybrid
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.)
Ceased
Application number
PCT/US2011/058506
Other languages
English (en)
French (fr)
Inventor
Sidney B. Schrum, Jr.
Richard E. Newman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Atheros Inc
Original Assignee
Qualcomm Atheros Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Atheros Inc filed Critical Qualcomm Atheros Inc
Priority to CN201180068749.4A priority Critical patent/CN103403697B/zh
Priority to KR20137026010A priority patent/KR101494566B1/ko
Priority to JP2013556607A priority patent/JP5752813B2/ja
Priority to EP11859662.6A priority patent/EP2681663A4/en
Publication of WO2012118531A1 publication Critical patent/WO2012118531A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • H04L12/4625Single bridge functionality, e.g. connection of two networks over a single bridge
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/26Route discovery packet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/24Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246Connectivity information discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/54Store-and-forward switching systems 
    • H04L12/56Packet switching systems
    • H04L12/5601Transfer mode dependent, e.g. ATM
    • H04L2012/5603Access techniques
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/64Hybrid switching systems
    • H04L12/6418Hybrid transport
    • H04L2012/6432Topology

Definitions

  • Embodiments of the inventive subject matter generally relate to the field of communication systems and, more particularly, to a mechanism for discovery of conventional devices and bridges in a hybrid communication network.
  • Hybrid communication networks typically comprise multiple networking technologies (e.g., wireless local area network (WLAN) technologies, powerline communication technologies, Ethernet, etc.) that are interconnected using bridging-capable devices that forward packets between devices utilizing the different network technologies and media in order to form a single extended communication network.
  • WLAN wireless local area network
  • bridging-capable devices that forward packets between devices utilizing the different network technologies and media in order to form a single extended communication network.
  • the communication mechanisms, and protocol specifics e.g., device and topology discovery, bridging to other networks, etc.
  • the hybrid communication network can comprise hybrid communication devices and conventional (or legacy) communication devices.
  • a method comprises: detecting, at a first network bridge device of a first class of network devices, that one or more packets originating from a second network device of a second class of network devices that are forwarded by the first network bridge device do not include a predetermined tag; determining, at the first network bridge device, that the second network device of the second class of network devices is communicatively located adjacent to at least one of a plurality of network interfaces of the first network bridge device based, at least in part, on said detecting that the one or more packets originating from the second network device do not include the predetermined tag; and inserting, at the first network bridge device, the predetermined tag in the one or more packets originating from the second network device.
  • the method further comprises transmitting a probe message to the second network device of the second class of network devices; determining whether the probe message was detected by a target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; and determining that a first network segment associated with the first network bridge device is communicatively coupled to a second network segment associated with the target network device via a network bridge device of the second class of network devices in response to determining that the probe message was not detected by the target network device.
  • the method further comprises transmitting a probe message to the second network device of the second class of network devices; determining whether the probe message was detected by a target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; and determining that the second network device and the target network device are associated with a common network segment in response to determining that the probe message was detected by the target network device.
  • said determining that the second network device of the second class of network devices is communicatively located adjacent to at least one of the plurality of network interfaces of the first network bridge device further comprises providing, to one or more other network devices of the first class of network devices, an indication that the first network bridge device of the first class of network devices is communicatively located adjacent to the second network device of the second class of network devices.
  • a method comprises: determining that at least one of a plurality of network interfaces of a first network device of a first class of network devices is communicatively located adjacent to a second network device of a second class of network devices in a communication network based, at least in part, on detecting that one or more packets received at the at least one of the plurality of network interfaces from the second network device do not comprise a predetermined tag; transmitting, via the at least one of the plurality of network interfaces of the first network device, a probe message to the second network device of the second class of network devices; determining whether the probe message was detected by at least one of a plurality of network interfaces of a target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; and determining that a first network segment associated with the at least one of the plurality of network interfaces of the first network device is communicatively coupled to a second network segment associated with the at least one of
  • the first network device and the target network device are network bridge devices of the first class of network devices.
  • the method further comprises determining that the second network device of the second class of network devices and the at least one of the plurality of network interfaces of the target network device are associated with a common network segment, in response to determining that the probe message was detected by the at least one of the plurality of network interfaces of the target network device.
  • said determining that the at least one of the plurality of network interfaces of the first network device of the first class of network devices is communicatively located adjacent to the second network device of the second class of network devices in the communication network comprises receiving, at the at least one of the plurality of network interfaces of the first network device, the one or more packets from the second network device of the second class of network devices; reading the one or more packets to determine whether the one or more packets received from the second network device of the second class of network devices comprises the predetermined tag; and determining that the at least one of the plurality of network interfaces of the first network device of the first class of network devices is communicatively located adjacent to the second network device of the second class of network devices in response to determining that the one or more packets received from the second network device of the second class of network devices do not comprise the predetermined tag.
  • the method in response to determining that the one or more packets received from the second network device of the second class of network devices do not comprise the predetermined tag, the method further comprises determining whether the one or more packets received from the second network device of the second class of network devices are to be forwarded to a destination device of the communication network; and in response to determining that the one or more packets received from the second network device of the second class of network devices are to be forwarded to the destination device of the communication network, inserting the predetermined tag in the one or more packets received from the second network device of the second class of network devices; and forwarding the one or more packets comprises the predetermined tag to the destination device.
  • the method further comprises providing, to at least the target network device of the communication network, an indication that the at least one of the plurality of network interfaces of the first network device of the first class of network devices is communicatively located adjacent to the second network device of the second class of network devices.
  • the method further comprises identifying the at least one of the plurality of network interfaces of the target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices in response to detecting a message from the target network device that indicates that the at least one of the plurality of network interfaces of the target network device is communicatively located adjacent to the second network device of the second class of network devices.
  • said transmitting the probe message to the second network device of the second class of network devices further comprises identifying the at least one of the plurality of network interfaces of the target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; negotiating, with the target network device, a communication schedule in which to probe the second network device of the second class of network devices; and transmitting the probe message to the second network device of the second class of network devices in accordance with the communication schedule.
  • said transmitting the probe message to the network device of the second class of network devices further comprises determining an address of the second network device of the second class of network devices based, at least in part, on a source address associated with the one or more packets received from the second network device of the second class of network devices; and transmitting the probe message from the first network device of the first class of network devices to the source address associated with the second network device of the second class of network devices.
  • the address associated with the second network device comprises a media access control (MAC) address associated with the second network device.
  • MAC media access control
  • a network device comprises: a plurality of network interfaces; and a device detection unit coupled with the one or more network interfaces.
  • the device detection unit is operable to: determine that at least one of the plurality of network interfaces of the network device of a first class of network devices is communicatively located adjacent to a second network device of a second class of network devices in a communication network based, at least in part, on detecting that one or more packets received at the at least one of the plurality of network interfaces from the second network device do not comprise a predetermined tag; transmit, via the at least one of the plurality of network interfaces of the network device, a probe message to the second network device of the second class of network devices; determine whether the probe message was detected by at least one of a plurality of network interfaces of a target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; and determine that a first network segment associated with the at least one of the plurality of
  • the device detection unit is further operable to determine that the second network device of the second class of network devices and the at least one of the plurality of network interfaces of the target network device are associated with a common network segment, in response to the device detection unit determining that the probe message was detected by the at least one of the plurality of network interfaces of the target network device.
  • the device detection unit in response to the device detection unit determining that the one or more packets received from the second network device of the second class of network devices do not comprise the predetermined tag, is further operable to determine whether the one or more packets received from the second network device of the second class of network devices are to be forwarded to a destination device of the communication network; and in response to the device detection unit determining that the one or more packets received from the second network device of the second class of network devices are to be forwarded to the destination device of the communication network, insert the predetermined tag in the one or more packets received from the second network device of the second class of network devices; and forward the one or more packets comprises the predetermined tag to the destination device.
  • the device detection unit operable to transmit the probe message to the second network device of the second class of network devices further comprises the device detection unit operable to identify the at least one of the plurality of network interfaces of the target network device of the first class of network devices that is communicatively located adjacent to the second network device of the second class of network devices; negotiate, with the target network device, a communication schedule in which to probe the second network device of the second class of network devices; and transmit the probe message to the second network device of the second class of network devices in accordance with the communication schedule.
  • the device detection unit operable to transmit the probe message to the network device of the second class of network devices further comprises the device detection unit operable to determine an address of the second network device of the second class of network devices based, at least in part, on a source address associated with the one or more packets received from the second network device of the second class of network devices; and transmit the probe message from the network device of the first class of network devices to the source address associated with the second network device of the second class of network devices.
  • one or more machine-readable storage media having instructions stored therein, which when executed by one or more processors causes the one or more processors to perform operations that comprise: detecting, at a first network device of a first class of network devices, that one or more packets originating from a second network device of a second class of network devices that are forwarded by the first network device do not include a predetermined tag; determining that the second network device of the second class of network devices is communicatively located adjacent to at least one of a plurality of network interfaces of the first network device based, at least in part, on said operation of detecting that the one or more packets originating from the second network device do not include the predetermined tag; inserting the predetermined tag in the one or more packets originating from the second network device; transmitting, via the at least one of the plurality of network interfaces of the first network device, a probe message to the second network device of the second class of network devices; determining whether the probe message was detected by at least one of a plurality
  • the operations further comprise determining that the second network device of the second class of network devices and the at least one of the plurality of network interfaces of the target network device are associated with a common network segment, in response to said operation of determining that the probe message was detected by the at least one of the plurality of network interfaces of the target network device.
  • the operations further comprise providing, to at least the target network device of the communication network, an indication that the at least one of the plurality of network interfaces of the first network device of the first class of network devices is communicatively located adjacent to the second network device of the second class of network devices.
  • said operation of transmitting the probe message to the network device of the second class of network devices further comprises determining an address of the second network device of the second class of network devices based, at least in part, on a source address associated with the one or more packets received from the second network device of the second class of network devices; and transmitting the probe message from the first network device of the first class of network devices to the source address associated with the second network device of the second class of network devices.
  • Figure 1 is an example block diagram illustrating a mechanism for detecting legacy network devices and bridges in a hybrid communication network
  • Figure 2 is a flow diagram illustrating example operations for identifying legacy network devices and bridges in a hybrid communication network
  • Figure 3 is a continuation of Figure 2 and also illustrates example operations for identifying legacy network devices and bridges in a hybrid communication network
  • Figure 4 is an example block diagram of one embodiment of an electronic device including a mechanism for discovery of legacy network devices and bridges in a hybrid communication network.
  • the description that follows includes exemplary systems, methods, techniques, instruction sequences, and computer program products that embody techniques of the present inventive subject matter. However, it is understood that the described embodiments may be practiced without these specific details.
  • the conventional bridge discovery mechanism can be implemented for hybrid communication networks comprising wireless local area network (WLAN) devices (e.g., IEEE 802.11 ⁇ devices), powerline network devices (e.g., HomePlug AV) and Ethernet devices
  • WLAN wireless local area network
  • powerline network devices e.g., HomePlug AV
  • Ethernet devices e.g., Ethernet devices
  • the conventional bridge discovery mechanism can be implemented in hybrid communication networks that may comprise other suitable types of network devices that implement other standards/protocols (e.g., WiMAX, etc.).
  • well-known instruction instances, protocols, structures, and techniques have not been shown in detail in order not to obfuscate the description.
  • a hybrid communication network (e.g., a hybrid home network) is typically formed by interconnecting communication networks (that support different communication protocols) across different network technologies and communication media.
  • the hybrid communication network can comprise multi-interface communication devices ("hybrid devices") that are configured to operate across multiple networking technologies as well as conventional, single- interface communication devices (“legacy devices").
  • the hybrid devices implement topology discovery and other information exchange protocols to advertise their presence to other hybrid devices in the hybrid communication network .
  • the legacy devices including legacy bridges
  • the hybrid devices may attempt to route packets in the hybrid communication network without being aware of the presence or location of legacy devices and legacy bridges in the hybrid communication network.
  • the hybrid devices should be aware of the topology of the hybrid communication network.
  • the hybrid devices may implement protocols to improve network performance by evenly dividing the communication load over multiple routes.
  • the presence of legacy bridges of varying capability and that implement various legacy protocols can influence the route selection decisions made by the hybrid devices.
  • a legacy learning bridge typically "learns" the location of various other communication devices (e.g., legacy devices, hybrid devices, etc.) in the hybrid communication network with respect to various interfaces of the legacy learning bridge.
  • the legacy learning bridge in the hybrid communication network may drop incoming packets if the legacy learning bridge detects the same source address on more than one of its interfaces and/or if the interface at which the incoming packets arrive at the legacy learning bridge is inconsistent with what the legacy learning bridge has previously learned.
  • Existing topology discovery techniques may rely on direct exchange of information between communication devices and on manual configuration of virtual LANs, bridge priorities, or explicit provision of topology information that can be too complicated for users.
  • hybrid devices can implement a mechanism for automatically detecting and locating legacy learning bridges in a hybrid communication network with little or no user configuration, so that route selection decisions can take into consideration the effects of the legacy learning bridges.
  • the hybrid devices can be configured to mark packets received from legacy devices with a special predetermined tag before forwarding the packets (if needed) to indicate that the packets were routed via a hybrid device.
  • the hybrid device can determine whether the packet comprises the special predetermined tag. If the hybrid device determines that the packet was received without the predetermined tag, this can indicate that the legacy device is not coupled to the hybrid device via other intermediate hybrid devices.
  • Such a legacy device is herein referred to as an "adjacent legacy device" with respect to the hybrid device (e.g., with respect to at least one communication interface of the hybrid device) at which the packet was detected.
  • the hybrid device can then transmit a probe message to the adjacent legacy device, determine whether one or more other hybrid devices detected the probe message, and consequently determine whether the hybrid device and the one or more other hybrid devices (which may be located in different network segments) are connected via legacy bridges, as will be further described below with reference to Figures 1-4.
  • Such a topology discovery mechanism for identifying the presence of legacy learning bridges in a hybrid communication network can improve and simplify the route selection process in the hybrid communication network.
  • packet routes can be appropriately selected (or avoided) to try to ensure the legacy learning bridges detect the same source addresses at the appropriate "learned" interfaces. This can minimize the probability of dropped packets and improve performance of the hybrid communication network.
  • FIG. 1 is an example block diagram illustrating a mechanism for detecting legacy devices and bridges in a hybrid communication network 100.
  • the hybrid communication network 100 can comprise communication devices (e.g., hybrid devices, hybrid bridges, legacy devices, legacy bridges, etc.) that implement one or more different communication protocols (e.g., WLAN, HomePlug AV, Ethernet, etc.), based on various networking standards and operating either wirelessly or over various wired media (powerline, coax cable, unshielded twisted pair telephone cable, CAT5 shielded twisted pair cable, etc.).
  • the hybrid devices can be electronic devices that comprise bridging capabilities in addition to communication capabilities.
  • hybrid devices may be referred to as “hybrid bridges.”
  • the hybrid devices can also be electronic devices that comprise communication capabilities but do not comprise bridging capabilities.
  • Such hybrid devices may be referred to as “hybrid communication devices.”
  • the legacy devices can be electronic devices that comprise bridging capabilities in addition to communication capabilities, which can be referred to herein as “legacy bridges.”
  • the legacy devices can also be electronic devices that comprise communication capabilities but do not comprise bridging capabilities.
  • Such legacy devices may be referred to as "legacy communication devices.”
  • the hybrid communication network 100 comprises two network segments 120 and 122.
  • the network segment 120 comprises hybrid devices 102 and 116, and a legacy device 106.
  • the network segment 122 comprises a hybrid device 104 and a legacy device 108.
  • a legacy bridge 1 10 couples the network segment 120 and the network segment 122.
  • the hybrid device 102 comprises a device detection unit 1 12 and a routing unit 1 14.
  • the hybrid devices 104 and 116 can also comprise their respective device detection units and routing units. It is noted that in some implementations, the hybrid devices 102, 104, and 116 can be hybrid bridges. In some embodiments, the hybrid devices 102, 104, and/or 116 can be hybrid bridges or hybrid communication devices. Likewise, the legacy devices 106 and 108 can be legacy bridges or legacy communication devices.
  • the hybrid devices 102, 104, and 116 can comprise multiple communication interfaces, each of which connects the hybrid device to different communication networks.
  • the hybrid device 102 can comprise three communication interfaces (e.g., a powerline interface, an Ethernet interface, and a wireless local area network (WLAN) interface) that enable the hybrid device 102 to connect to a powerline communication network, an Ethernet, and a WLAN, respectively.
  • WLAN wireless local area network
  • the hybrid devices 102, 104 and 1 16 can comprise two or more communication interface that couple the hybrid devices to two or more communication networks.
  • the legacy devices typically comprise only one communication interface for communication via the corresponding communication network.
  • the legacy devices 106 and 108 may comprise an Ethernet interface for communication via Ethernet.
  • each of the hybrid devices 102, 104, and 1 16 can broadcast announcement messages to advertise their presence in the hybrid communication network 100.
  • the hybrid device 102 can broadcast an announcement message (e.g., at predetermined periodic time intervals) comprising an identifier of the hybrid device 102 to announce its presence in the hybrid communication network 100 to the hybrid devices 104 and 1 16.
  • the legacy devices may not be capable of broadcasting announcement messages (or other similar messages). Therefore, the hybrid devices 102, 104, and 116 can execute operations described below in stages A - G (and also Figures 2 - 3) to discover legacy devices and legacy bridges in the hybrid communication network 100 in order to determine the topology of the hybrid communication network 100.
  • the device detection unit 1 12 of the hybrid device 102 detects a packet transmitted by the legacy device 106 that does not comprise a predetermined tag.
  • the legacy device 106 may transmit the packet to another legacy device via the hybrid device 102.
  • the packet transmitted by the legacy device 106 may be intended for the hybrid device 102.
  • the legacy device 106 may broadcast a packet in the hybrid communication network 100 at periodic intervals and the hybrid device 102 can detect the broadcasted packet.
  • the device detection unit 1 12 in response to detecting the packet from the legacy device 106, the device detection unit 1 12 can read a predetermined field in the received packet to determine whether the received packet comprises the predetermined tag.
  • the predetermined tag can be any suitable combination of characters, numbers, and symbols (e.g., any suitable combination of zeros and ones).
  • the predetermined tag can be a virtual local area network (VLAN) tag.
  • the predetermined tag may be a static tag (e.g., hardcoded as part of the hybrid devices during manufacturing), while in other implementations the hybrid devices 102, 104, and 1 16 in the hybrid communication network 100 can negotiate and agree upon the value of the predetermined tag.
  • a user may configure/select the value of the predetermined tag.
  • the device detection unit 1 12 determines that the legacy device 106 is an adjacent legacy device in response to detecting that the packet from legacy device 106 does not comprise the predetermined tag.
  • the hybrid devices 102, 104, and 116 may be configured to append the predetermined tag to any packet received from a legacy device prior to forwarding the received packet to the intended destination device. If the hybrid device 102 receives the packet from the legacy device 106 without the predetermined tag, this can indicate that there are no other hybrid devices along the route between the hybrid device 102 and the legacy device 106 (e.g., along the route between at least one of the interfaces of the hybrid device 102 and the legacy device 106).
  • receiving the packet from the legacy device 106 without the predetermined tag can identify the legacy device 106 as an "adjacent legacy device" with respect to the hybrid device 102 (e.g., with respect to at least one of the interfaces of the hybrid device 102).
  • the device detection unit 1 12 in response to determining that the legacy device 106 is an adjacent legacy device with respect to the hybrid device 102, can broadcast an "adjacent device identification" message to the other hybrid devices 104 and 1 16 in the hybrid communication network 100.
  • the adjacent device identification message can comprise an identifier (e.g., a network address, a device address, etc.) associated with the adjacent device 106 and an identifier associated with the hybrid device 102.
  • the device detection unit 112 can broadcast an indication of the adjacent legacy device 106 in any suitable message (e.g., a beacon message, a periodic synchronization message, etc.).
  • the legacy device 106 does not have to be physically adjacent to the hybrid device 102 (as depicted in Figure 1) in order to be considered an "adjacent legacy device.” Instead, the legacy device 106 may only be "communicatively located adjacent" to at least one interface of the hybrid device 102. In other words, with reference to the example of Figure 1, even though a packet transmitted by the legacy device 108 to the hybrid device 102 may pass through the legacy bridge 110 (another legacy device), it may not pass through another hybrid device. In other words, the packet route between the legacy device 108 and the hybrid device 102 does not comprise any intermediate hybrid devices.
  • the device detection unit 1 12 may receive the packet transmitted by the legacy device 102 without the predetermined tag, and may determine that the legacy device 108 is an adjacent legacy device with respect to the hybrid device 102.
  • the hybrid device 104 determines that the legacy device 106 is an adjacent legacy device in response to detecting that the packet received from legacy device 106 does not comprise the predetermined tag.
  • a device detection unit (not shown) of the hybrid device 104 can detect that the packet transmitted by the legacy device 106 does not comprise the predetermined tag.
  • the hybrid device 104 can determine that there are no other hybrid devices along the packet route between the hybrid device 104 and the legacy device 106.
  • the hybrid device 104 can identify the legacy device 106 as an "adjacent legacy device" with respect to the hybrid device 104 (e.g., with respect to at least one of the interfaces of the hybrid device 104). Furthermore, as described above in stage Bl, the hybrid device 104 may indicate (to the other hybrid devices 102 and 1 16 in the hybrid communication network 100) that the legacy device 106 is an adjacent legacy device with respect to the hybrid device 104 by sending an adjacent device identification message or another suitable message. Likewise, at stage B2, the hybrid device 1 16 can also determine (and announce) that the legacy device 106 is an adjacent legacy device in response to detecting that the packet received from legacy device 106 does not comprise the predetermined tag.
  • the device detection unit 112 appends the predetermined tag to the packet and forwards the packet.
  • the hybrid devices 102, 104, and 116 can be configured to append the predetermined tag (e.g., a VLAN tag) to all packets received at at least one of the interfaces of the hybrid device from an adjacent legacy device. Appending the predetermined tag to packets received from the adjacent legacy device can enable other hybrid devices to identify whether or not the legacy device is an adjacent legacy device. Tagging packets received from the legacy device can enable the other hybrid devices that subsequently detect the packet to determine whether the packet was forwarded by another hybrid device (e.g., a hybrid bridge or a hybrid communication device) or whether the packet was forwarded by a legacy bridge.
  • another hybrid device e.g., a hybrid bridge or a hybrid communication device
  • the device detection unit 1 12 may append the predetermined tag to the packet received from the legacy device 106 and may forward the packet to a destination hybrid device connected on a different network segment.
  • the destination hybrid device can determine that the hybrid device 102 is one of the forwarding devices along the route between the legacy device 106 and the destination hybrid device.
  • the device detection unit 112 identifies one or more target hybrid devices with which the legacy device 106 is an adjacent legacy device.
  • the device detection unit 112 can determine whether the legacy device 106 is an adjacent legacy device with respect to one or more other hybrid devices. In some implementations, the device detection unit 112 can listen for adjacent device identification messages transmitted by other hybrid devices in the hybrid communication network 100. In the example of Figure 1, the device detection unit 112 can detect adjacent device identification messages transmitted by the hybrid devices 104 and 116, and determine that the legacy device 106 is an adjacent legacy device with respect to the hybrid devices 104 and 116.
  • the hybrid devices 104 and 116 that share a common adjacent legacy device (e.g., the legacy device 106) with the hybrid device 102 are referred to herein as "target hybrid devices.”
  • the device detection unit 112 can probe the adjacent legacy device 106 to determine the position of the adjacent legacy device 106 with respect to the hybrid devices 102, 104, and 116, and to determine whether a legacy bridge connects two or more of the hybrid devices 102, 104, and 116.
  • the device detection unit 112 transmits a probe message to the adjacent legacy device 106.
  • the device detection unit 112 can transmit the probe message to the adjacent legacy device 106 via the communication interface (of the hybrid device 102) on which the packet from the legacy device 106 was detected.
  • the probe message can enable the device detection unit 112 to determine the position of the legacy device 106 in the hybrid communication network 100 vis-a-vis the hybrid devices 102, 104, and 116. More specifically, transmitting the probe message to the adjacent legacy device 106 can enable the device detection unit 112 to determine whether the hybrid device 102 and the target hybrid devices 104 and 116 are part of a common network segment, or part of different network segments coupled by a legacy bridge.
  • the device detection unit 112 can transmit the probe message to the adjacent legacy device 106 as soon as the device detection unit 112 identifies the one or more target hybrid devices 104 and 116 that are also adjacent to the legacy device 106.
  • the device detection unit 112 can communicate with the target hybrid devices 104 and 116 and can negotiate a communication schedule in which the probe messages should be transmitted to the adjacent legacy device 106.
  • the device detection unit 1 12 can transmit a probe start message to the target hybrid devices 104 and 116 to indicate that probe messages will be transmitted to the adjacent legacy devices to discover the topology of the communication network 100.
  • the device detection unit 112 can also transmit a probe stop message to indicate (to the target hybrid devices 104 and 1 16) that probe messages have been transmitted to all the adjacent legacy devices.
  • the device detection unit 1 12 may identify multiple adjacent legacy devices and may transmit a unicast probe message to each identified adjacent legacy device.
  • the device detection unit 112 can transmit a multi-cast probe message to two or more identified adjacent legacy devices.
  • the target hybrid device 104 indicates whether the probe message transmitted to the adjacent legacy device 106 was detected at the target hybrid device 104.
  • the device detection unit 1 12 can notify the target hybrid device 104 (e.g., via a notification message) when (e.g., a time instant at which) the probe message is transmitted (or is scheduled to be transmitted) to the adjacent legacy device 106.
  • the device detection 1 12 can also notify the target hybrid device 104 how many probe messages are (or will be) transmitted to the adjacent legacy device 106.
  • the target hybrid device 104 can wait for a predetermined time interval (configured based on the number of probe messages that are transmitted, the length of the probe messages, maximum allowable network delay, etc.) to receive the probe messages.
  • the target hybrid device 104 can transmit an acknowledgment message to the initiating hybrid device 102 to indicate detection of the probe message(s). Alternately, if the target hybrid device 104 does not detect any of the probe messages, the target hybrid device 104 can indicate (e.g., after the predetermined time interval elapses) that none of the probe messages were detected. In another implementation, the hybrid device 102 can transmit one or more probe messages to the adjacent legacy device 106, wait for the predetermined time interval, and then query the target hybrid device 104 to determine whether the one or more probe messages were detected at the target hybrid device 104.
  • the target hybrid device 104 can indicate that the probe message transmitted from the hybrid device 102 to the adjacent legacy device 106 was not detected at the target hybrid device 104 (e.g., since the target hybrid device 104 is located in a different network segment separated by a legacy bridge).
  • the target hybrid device 1 16 can indicate that the probe message transmitted from the hybrid device 102 to the adjacent legacy device 106 was detected at the target hybrid device 116 (e.g., since the hybrid device 1 16 is located in the same network segment as the initiating hybrid device 102).
  • the routing unit 1 14 determines whether the hybrid devices are located in different network segments connected by a legacy bridge based on whether the probe message was detected at the one or more target hybrid devices. In the example of Figure 1, the routing unit 1 14 can determine that the probe message transmitted to the adjacent legacy device 106 was not detected at the target hybrid device 104. This can indicate that the hybrid device 102 and the target hybrid device 104 are located in different network segments 120 and 122 that are connected by the legacy bridge 1 10. In the example of Figure 1, the routing unit 114 can determine that the probe message transmitted to the adjacent legacy device 106 was detected at the target hybrid device 1 16.
  • Determining that the probe message transmitted to the adjacent legacy device 106 was detected at the target hybrid device 1 16 can indicate (e.g., to the routing unit 114) that there are no legacy bridges between the legacy device 106 and the hybrid device 1 16.
  • each of the hybrid devices 102, 104, and 1 16 that identified the legacy device 106 as an adjacent legacy device can transmit a probe message to the legacy device 106, and then determine whether the probe message was detected by one or more of the other hybrid devices. This can enable the hybrid devices 102, 104, and 1 16 to determine, verify, and update the estimation of the topology of the hybrid communication network 100 (e.g., the location of the legacy bridges relative to the hybrid devices). Operations of the routing unit 114 determining the topology of the hybrid communication network 100 will further be described with reference to Figure 3.
  • the routing unit 1 14 can then use the knowledge of the topology of the hybrid communication network 100 for efficient packet routing through bridged network segments.
  • FIG. 2 and Figure 3 depict a flow diagram ("flow") 200 illustrating example operations for identifying legacy network devices in a hybrid communication network.
  • the flow 200 begin at block 202 in Figure 2.
  • a hybrid device detects a packet transmitted by a legacy device in a hybrid communication network.
  • the hybrid device can be a hybrid bridge and the legacy device can be a legacy communication device.
  • the device detection unit 1 12 of the hybrid device 102 can detect a packet transmitted by the legacy device 106.
  • the packet transmitted by the legacy device 102 can be a unicast packet intended for the hybrid device 102, a packet to be forwarded by the hybrid device 102 to another destination device, a multicast packet, a broadcast packet, etc.
  • the legacy device 106 may transmit a test packet (e.g., comprising a NULL payload or a predetermined payload). In other implementations, the legacy device 106 may transmit a control packet or a data packet comprising control information and/or data intended for the destination device. The flow continues at block 204.
  • a test packet e.g., comprising a NULL payload or a predetermined payload.
  • the legacy device 106 may transmit a control packet or a data packet comprising control information and/or data intended for the destination device. The flow continues at block 204.
  • the device detection unit 112 can determine whether the packet (detected at block 202) comprises the predetermined tag.
  • the hybrid devices can be configured to insert the predetermined tag into any packet received directly from an adjacent legacy device (i.e., without being routed by another hybrid device).
  • the presence of the predetermined tag can indicate that there exist one or more other hybrid devices along the route between the legacy device 106 and the hybrid device 102.
  • the absence of the predetermined tag can indicate that the there are no hybrid devices along the route between the legacy device 106 and the hybrid device 102 (i.e., the legacy device 106 is an adjacent legacy device). If it is determined that the packet transmitted by the legacy device comprises the predetermined tag, the flow continues at block 206. Otherwise, the flow continues at block 208.
  • the legacy device and the hybrid device are located on distinct network segments connected by at least one other hybrid device.
  • the flow 200 moves from block 204 to block 206 if the device detection unit 1 12 determines that the packet transmitted by the legacy device 106 comprises the predetermined tag. Because the received packet comprises the predetermined tag, the device detection unit 112 can determine that the packet was routed from the legacy device 106 to the hybrid device 102 via another intermediate hybrid device (e.g., that appended the predetermined tag to the packet). The device detection unit 1 12 can also determine that the hybrid device 102 would have directly received the packet from the legacy device 106 (e.g., without the predetermined tag) if the legacy device 106 and the hybrid device 102 were part of the same network segment.
  • the device detection unit 112 can infer that the legacy device 106 and the hybrid device 102 are located on different network segments connected by one or more hybrid devices.
  • the routing unit 1 14 of the hybrid device 102 can store (e.g., in a routing data structure) routing information associated with the legacy device 106.
  • the routing unit 1 14 can store an identifier associated with the legacy device 106, an identifier associated with the one or more intermediate hybrid devices (if known), an interface (or port) on which the packet from the legacy device 106 was detected, etc.
  • the routing unit 1 14 can use this routing information to route subsequent packets to the legacy device 106. From block 206, the flow ends.
  • the hybrid device determines that the legacy device is adjacent to the hybrid device.
  • the flow 200 moves from block 204 to block 208 if the device detection unit 1 12 determines that the packet transmitted by the legacy device 106 does not comprise the predetermined tag. Because the received packet does not comprise the predetermined tag, the device detection unit 1 12 can infer that the packet was directly transmitted from the legacy device 106 to the hybrid device 102 or that the packet was routed from the legacy device 106 to the hybrid device 102 via one or more legacy bridges. In other words, because the received packet does not comprise the predetermined tag, the device detection unit 1 12 can determine that the route between the hybrid device 102 and the legacy device 106 does not comprise any other hybrid devices.
  • the legacy device 106 can be considered to be an adjacent legacy device with respect to that communication interface of the hybrid device 102.
  • the device detection unit 1 12 can determine whether the legacy device 106 is adjacent to the hybrid device 102 on an interface-by-interface basis.
  • the routing unit 106 may also store an identifier associated with the legacy device 106 and an indication of the interface/port of the hybrid device 102 on which the packet was detected.
  • a notification message is broadcast to other hybrid devices to indicate that the legacy device is adjacent to the hybrid device.
  • the device detection unit 1 12 can broadcast an adjacent device identification message (or another suitable message) to indicate that the legacy device 106 is an adjacent legacy device with respect to the hybrid device 102.
  • the adjacent device identification message can comprise an identifier associated with the adjacent legacy device 106, an identifier associated with the hybrid device 102, an identifier associated with the corresponding interface of the hybrid device 102 on which the packet was detected, etc.
  • the flow continues at block 212.
  • one or more target hybrid devices in the hybrid communication network that are adjacent to the legacy device are identified based on detecting one or more corresponding notification messages. For example, on determining that the legacy device 106 is adjacent to the hybrid device 102, the device detection unit 1 12 can attempt to identify one or more target hybrid devices for which the legacy device 106 is an adjacent legacy device. For example, the device detection unit 1 12 can listen for and can receive one or more adjacent device identification messages from corresponding one or more hybrid devices in the hybrid communication network 100. The device detection unit 1 12 can read the multiple adjacent device identification messages and can identify the one or more target hybrid devices for which the legacy device 106 is an adjacent legacy device.
  • the device detection unit 112 determines that the legacy device 106 is also adjacent to at least one of the interfaces of the target hybrid devices 104 and 116. The flow continues at block 214 in Figure 3, where the device detection unit 112 can probe the adjacent legacy device 106 to determine whether a legacy bridge couples the hybrid device 102 with the hybrid devices 104 and 116.
  • a probe message is transmitted to the adjacent legacy device.
  • the device detection unit 1 12 can transmit the probe message to the adjacent legacy device 106.
  • transmitting the probe message to the adjacent legacy device 106 can enable the device detection unit 112 to determine whether the hybrid device 102 and the one or more target hybrid devices 104 and 116 are part of a common network segment or part of different network segments coupled by a legacy bridge (e.g., based on whether the one or more target hybrid devices 104 and 1 16 detected the probe message).
  • the device detection unit 112 can transmit the probe message to the adjacent legacy device 106 via the communication interface (of the hybrid device 102) on which the packet from the legacy device 106 was detected (at block 202). The flow continues at block 216.
  • a loop is initiated for each of the one or more target hybrid devices in the hybrid communication network.
  • the device detection unit 112 can initiate the loop to determine whether the probe message transmitted to the adjacent legacy device 106 was detected by the one or more target hybrid devices 104 and 1 16, as will be described below. The flow continues at block 218.
  • the device detection unit 1 12 can determine whether the probe message (transmitted to the adjacent legacy device 106 at block 214) was detected at the target hybrid device 104. As described above in Figure 1, in some implementations, the device detection unit 112 can query the target hybrid device 104 to determine whether the probe message transmitted to the legacy device 106 was detected at the target hybrid device 104. The device detection unit 1 12 can receive a response message that indicates whether the probe message was detected at the target hybrid device 104. In another implementation, the target hybrid device 104 may be configured to automatically transmit an indication of whether the probe message was detected at the target hybrid device 104.
  • the target hybrid device 104 may automatically transmit an indication that the probe message was detected at the target hybrid device 104. As another example, if the probe message is not detected within a predetermined time interval, the target hybrid device 104 may indicate that the probe message was not detected at the target hybrid device 104.
  • the communication interfaces of the target hybrid devices 104 and 1 16 may be configured to snoop, receive, and process unicast packets that are intended for the legacy device 106. It is noted that in some implementations, whether the target hybrid devices 104 and 116 detect the probe message transmitted by the hybrid device 102 may depend on the learning capabilities and learning behavior of the legacy bridge 110.
  • the legacy bridge 110 may not forward unicast packets intended for the legacy device 106 from the network segment 120 onto the network segment 122. Consequently, the target hybrid device 104 may not detect the probe messages transmitted from the hybrid device 102 to the legacy device 106. If it is determined that the probe message intended for the adjacent legacy device 106 was detected at the target hybrid device 104, the flow continues at block 222. Otherwise, the flow continues at block 220.
  • the legacy bridge 1 10 connecting the network segments 120 and 122 may receive the probe message.
  • the legacy bridge 1 10 can determine (e.g., based on forwarding tables, based on previously learned topology, etc.) that the legacy device 106 and the hybrid device 102 are connected to the same port (e.g., to the same interface) of the legacy bridge 110.
  • the legacy bridge 110 may receive the probe message on port 1, determine that the legacy device 106 is also connected on port 1, and may therefore not forward the probe message (e.g., to another port associated with the network segment 122).
  • the hybrid device 104 connected to the network segment 122 may therefore not detect the probe message transmitted from the hybrid device 102 to the legacy device 106.
  • the probe message can be transmitted to the legacy device 106 via the same interface of the hybrid device 102 on which the packet was received from the legacy device.
  • the routing unit 114 can infer that the target hybrid device 104 is not connected to that interface of the hybrid device 102.
  • the routing unit 1 14 can infer that the hybrid device 102 and the target hybrid device 104 are located on different network segments connected by at least one legacy bridge (e.g., the legacy bridge 110). The flow continues at block 224.
  • the target hybrid device 1 16 can detect probe messages transmitted from the hybrid device 102 to the legacy device 106. This can indicate that the legacy device 106 and the target hybrid device 1 16 are located on a common network segment 120 and that the target hybrid device 116 and the legacy device 106 are not connected by a legacy bridge.
  • the hybrid device 102 detects probe messages transmitted from the target hybrid device 116 to the legacy device 106, this can indicate that the legacy device 106 and the hybrid device 102 are located on a common network segment 120. In other words, the routing unit 1 14 can determine that the hybrid device 102 and the legacy device 106 are not connected by a legacy bridge. The flow continues at block 224.
  • the flow loops back to block 216, where the device detection unit 112 can identify the next target hybrid device and can determine whether the probe message intended for the adjacent legacy device 106 was detected at the next target hybrid device. Otherwise, the flow continues at block 226. It is noted that although Figure 3 depicts the target hybrid devices being analyzed sequentially (in blocks 218 - 224), in other embodiments, the target hybrid devices can be analyzed simultaneously.
  • the communication network topology is determined and is used to route packets from the hybrid device.
  • the routing unit 1 14 can determine the communication network topology based on whether probe messages transmitted by the hybrid device 102 were detected at each of the target hybrid devices 104 and 1 16 in the hybrid communication network 100.
  • the routing unit 114 can also determine the communication network topology based on detecting packets from the legacy devices, transmitting and detecting probe messages, detecting broadcast announcement messages from other hybrid devices, etc.
  • the hybrid device 102 can store an indication of one or more legacy devices that were deemed to be adjacent to each of the hybrid devices 102, 104, and 116 in the hybrid communication network 100.
  • the initiating hybrid device 102 can also store an indication of whether probe messages transmitted to the one or more adjacent legacy devices were detected by each of the target hybrid devices 104 and 116. Accordingly, the routing unit 114 can infer the topology of the hybrid communication network 100. In some implementations, the hybrid device 102 can also listen for probe messages transmitted by other hybrid devices 104 and 116 to the adjacent legacy device 106. Configuring each of the hybrid devices 102, 104, and 1 16 adjacent to a particular legacy device 106 to transmit probe messages can enable the hybrid devices 102, 104, and 1 16 to verify and to correct (if necessary) their estimation of the topology of the hybrid communication network 100.
  • the routing unit 1 14 can determine the position of legacy bridges in the hybrid communication network 100 with respect to each of the hybrid devices 102, 104, and 1 16. For example, the routing unit 114 can identify network segments to which each of the legacy devices and hybrid devices belong, determine whether the hybrid devices 102, 104, and 116 are located on the same network segment, determine whether the network segments are connected by legacy bridges or hybrid bridges, etc. The routing unit 114 can also identify interfaces of the hybrid devices 102, 104, 106 to which the legacy devices 106 and 108 are connected, interfaces of the hybrid devices 102, 104, 106 to which the other hybrid devices are connected, etc.
  • the routing unit 114 can determine that at least one communication interface of the hybrid devices 102 and 1 16 are connected to the same network segment 120.
  • the routing unit 1 14 can also determine that the communication interfaces of hybrid devices 102 and 104 are connected to different network segments - connected via the legacy bridge 110.
  • the routing unit 114 can also broadcast the estimated topology of the hybrid communication network 100 to the other hybrid devices 104 and 1 16. Based on the estimated communication network topology, the routing unit 114 can select an appropriate packet route for transmitting a packet to a destination device through the hybrid communication network 100. Furthermore, if there are multiple available packet routes to the destination device, the routing unit 1 14 can use the communication network topology information to identify the preferred (or most efficient) packet route for routing the packet to the destination device.
  • the routing unit 1 14 can take various factors into consideration including, whether the source and the destination hybrid devices are located on different network segments, whether any of the packet routes between the source and the destination hybrid devices comprises one or more legacy bridges, whether a packet route that does not comprise any legacy bridges is available, and whether the legacy bridges will receive the packet on a previously determined interface/port. For example, if one of multiple packet routes between a source hybrid device and a destination hybrid device is not in accordance with the communication network topology previously learned by the legacy bridge, the source hybrid device can determine not to select that packet route to minimize/prevent confusion of the legacy bridge. From block 226, the flow ends.
  • Figures 1 - 3 are examples meant to aid in understanding embodiments and should not be used to limit embodiments or limit scope of the claims. Embodiments may perform additional operations, fewer operations, operations in a different order, operations in parallel, and some operations differently. It is noted that in some implementations, to enable the hybrid devices to distinguish between a single network segment with a large propagation delay and two network segments coupled by a legacy bridge, the length of probe message transmitted by the hybrid devices can be the maximum allowable packet size.
  • the target hybrid device 104 can wait to detect the probe message for a predetermined time delay (e.g., a sum of a maximum packet transmission time interval and a maximum propagation delay time interval). After the predetermined time delay elapses, the target hybrid device 104 can indicate whether or not the probe message was detected
  • the hybrid device 102 can transmit multiple probe messages to the same adjacent legacy device 106 and can determine whether some/all or none of the probe messages were detected by the one or more other target hybrid devices 104 and 1 16.
  • the hybrid device 102 and the target hybrid device 104 can be considered part of distinct network segments coupled by the legacy bridge 1 10 if the target hybrid device 104 does not detect any of the probe messages transmitted to the adjacent legacy device 106. Transmitting multiple probe messages can minimize the errors due to network delays, network congestion, etc.
  • the network topology discovery operations described herein may be executed in conjunction with one or more other network topology discovery techniques and/or other route selection techniques.
  • network topology discovery operations described herein may be executed in conjunction with the Bridge Spanning Tree Protocol (STP).
  • STP Bridge Spanning Tree Protocol
  • the network topology discovery operations may be executed in conjunction with load level analysis techniques.
  • a hybrid device 102 can analyze communication load levels at each of the interfaces to which the hybrid device 102 is connected to a network segment. The hybrid device can broadcast the determined communication load levels associated with each of the interfaces to other hybrid devices in the hybrid communication network 100 and can similarly receive communication load level information from the other hybrid devices.
  • the hybrid device 102 can determine whether the communication load level on a particular network segment is approximately equal to the communication load level as seen by all the other hybrid devices connected to that network segment.
  • one of the hybrid devices can artificially increase the communication load level on the network segment (e.g., by transmitting one or more test messages) at predetermined time instants and can determine whether the increase in the communication load level was detected at other hybrid devices.
  • the hybrid devices that detect a corresponding increase in the communication load levels can be considered part of the same network segment.
  • the network topology discovery operations may be executed in conjunction with analysis of dropped packets.
  • the legacy bridges may be configured to drop any VLAN tagged packet with a canonical format indicator (CFI) flag set to "1."
  • CFI canonical format indicator
  • an initiating hybrid device 102 can transmit test messages comprising a VLAN tag and the CFI flag set to "1" to a destination hybrid device 104.
  • the initiating hybrid device 102 can also transmit test messages comprising the VLAN tag and the CFI flag set to "0" to the destination hybrid device 104.
  • the initiating hybrid device 102 determines that the destination hybrid device 104 detected the test messages with the CFI flag set to "0" and did not detect the test messages with the CFI flag set to "1"
  • the initiating hybrid device 102 can infer the presence of a legacy bridge between the initiating hybrid device 102 and the destination hybrid device 104.
  • a hybrid device can be any suitable network device of a "first class of communication devices" that comprises multiple communication interfaces and that is configured to operate across multiple networking technologies.
  • a legacy or conventional device can be any suitable network device of a "second class of communication devices” that comprises a single communication interface and that is configured to operate across a single networking technology.
  • Embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit,” “module” or “system.”
  • embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium.
  • the described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments, whether presently described or not, since every conceivable variation is not enumerated herein.
  • a machine-readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer).
  • a machine-readable medium may be a machine-readable storage medium, or a machine-readable signal medium.
  • a machine-readable storage medium may include, for example, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD- ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of tangible medium suitable for storing electronic instructions.
  • a machine-readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, an electrical, optical, acoustical, or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.). Program code embodied on a machine- readable signal medium may be transmitted using any suitable medium, including, but not limited to, wireline, wireless, optical fiber cable, RF, or other communications medium.
  • Computer program code for carrying out operations of the embodiments may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
  • the program code may execute entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN), a personal area network (PAN), or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider)
  • LAN local area network
  • PAN personal area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • FIG. 4 is a block diagram of one embodiment of an electronic device 400 including a mechanism for discovery of legacy devices and bridges in a hybrid communication network.
  • the electronic device 400 may be one of a laptop computer, a netbook, a mobile phone, a powerline communication device, a personal digital assistant (PDA), or other electronic systems comprising a hybrid communication unit configured to exchange communications across multiple communication networks (which form the hybrid communication network).
  • the electronic device 400 includes a processor unit 402 (possibly including multiple processors, multiple cores, multiple nodes, and/or implementing multithreading, etc.).
  • the electronic device 400 includes a memory unit 406.
  • the memory unit 406 may be system memory (e.g., one or more of cache, SRAM, DRAM, zero capacitor RAM, Twin Transistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS, PRAM, etc.) or any one or more of the above already described possible realizations of machine- readable media.
  • system memory e.g., one or more of cache, SRAM, DRAM, zero capacitor RAM, Twin Transistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS, PRAM, etc.
  • the electronic device 400 also includes a bus 410 (e.g., PCI, ISA, PCI-Express, HyperTransport®, InfiniBand®, NuBus, AHB, AXI, etc.), and network interfaces 404 that include at least one of a wireless network interface (e.g., a WLAN interface, a Bluetooth® interface, a WiMAX interface, a ZigBee® interface, a Wireless USB interface, etc.) and a wired network interface (e.g., an Ethernet interface, a powerline communication interface, etc.).
  • the electronic device 400 may support multiple network interfaces - each of which is configured to couple the electronic device 400 to a different communication network.
  • the electronic device 400 also includes a communication unit 408.
  • the communication unit 408 comprises a device detection unit 412 and a routing unit 414. As described above in Figures 1 - 3, the communication unit 408 implements functionality to determine whether a hybrid communication network that comprises the electronic device 400 also comprises one or more legacy devices (also known as conventional devices). The communication unit 408 can also determine whether the electronic device 400 and one or more other hybrid devices in the hybrid communication network are located on different network segments coupled by a legacy learning bridge (also known as a conventional learning bridge). Any one of these functionalities may be partially (or entirely) implemented in hardware and/or on the processor unit 402.
  • the functionality may be implemented with an application specific integrated circuit, in logic implemented in the processor unit 402, in a coprocessor on a peripheral device or card, etc. Further, realizations may include fewer or additional components not illustrated in Figure 4 (e.g., video cards, audio cards, additional network interfaces, peripheral devices, etc.).
  • the processor unit 402, the memory unit 406, and the network interfaces 406 are coupled to the bus 410. Although illustrated as being coupled to the bus 410, the memory unit 406 may be coupled to the processor unit 402.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)
PCT/US2011/058506 2011-03-02 2011-10-31 Discovery of conventional network devices and bridges Ceased WO2012118531A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201180068749.4A CN103403697B (zh) 2011-03-02 2011-10-31 用于混合通信网络中常规网络设备和网桥的发现的方法和系统
KR20137026010A KR101494566B1 (ko) 2011-03-02 2011-10-31 하이브리드 통신 네트워크들에서의 통상의 디바이스들 및 브리지들의 디스커버리
JP2013556607A JP5752813B2 (ja) 2011-03-02 2011-10-31 ハイブリッド通信ネットワーク内での、従来のデバイスおよびブリッジの発見
EP11859662.6A EP2681663A4 (en) 2011-03-02 2011-10-31 DISCOVERING CONVENTIONAL NETWORK DEVICES AND BRIDGES

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201161448511P 2011-03-02 2011-03-02
US61/448,511 2011-03-02
US13/197,275 2011-08-03
US13/197,275 US8897169B2 (en) 2011-03-02 2011-08-03 Discovery of conventional devices and bridges in hybrid communication networks

Publications (1)

Publication Number Publication Date
WO2012118531A1 true WO2012118531A1 (en) 2012-09-07

Family

ID=46753248

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/058506 Ceased WO2012118531A1 (en) 2011-03-02 2011-10-31 Discovery of conventional network devices and bridges

Country Status (6)

Country Link
US (1) US8897169B2 (enExample)
EP (1) EP2681663A4 (enExample)
JP (1) JP5752813B2 (enExample)
KR (1) KR101494566B1 (enExample)
CN (1) CN103403697B (enExample)
WO (1) WO2012118531A1 (enExample)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8897169B2 (en) 2011-03-02 2014-11-25 Qualcomm Incorporated Discovery of conventional devices and bridges in hybrid communication networks
US9025603B2 (en) 2011-03-08 2015-05-05 Qualcomm Incorporated Addressing scheme for hybrid communication networks
US9300491B2 (en) 2011-02-11 2016-03-29 Qualcomm Incorporated Frame delivery path selection in hybrid communication networks
US10645001B2 (en) 2015-10-28 2020-05-05 Xiaomi Inc. Information transmission method and apparatus, device and storage medium

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9461777B2 (en) * 2011-11-21 2016-10-04 Qualcomm Incorporated Hybrid networking system with seamless path switching of streams
CN104365128B (zh) * 2012-04-11 2019-06-04 西门子公司 用于运行技术特定按钮配置会话的方法和设备
US9705747B1 (en) 2012-12-04 2017-07-11 Qualcomm Incorporated Distributed path selection in hybrid networks
US9722943B2 (en) 2012-12-17 2017-08-01 Qualcomm Incorporated Seamless switching for multihop hybrid networks
US9014056B2 (en) * 2012-12-18 2015-04-21 Qualcomm Incorporated Bridging network devices in a hybrid communication network
US9184998B2 (en) 2013-03-14 2015-11-10 Qualcomm Incorporated Distributed path update in hybrid networks
US20140269691A1 (en) * 2013-03-14 2014-09-18 Qualcomm Incorporated Distributed path selection in hybrid networks
US9203717B2 (en) * 2013-12-19 2015-12-01 Google Inc. Detecting network devices
US9386605B2 (en) * 2014-07-11 2016-07-05 Motorola Solutions, Inc. Mobile dynamic mesh cluster bridging method and apparatus at incident scenes
CN111355599B (zh) * 2018-12-20 2023-02-03 北京国基科技股份有限公司 混合网络拓扑发现方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6421751B1 (en) * 1998-11-23 2002-07-16 Advanced Micro Devices, Inc. Detecting a no-tags-free condition in a computer system having multiple outstanding transactions
US20040078460A1 (en) * 2002-10-16 2004-04-22 Microsoft Corporation Network connection setup procedure for traffic admission control and implicit network bandwidth reservation
US20040133704A1 (en) * 2003-01-07 2004-07-08 Openpeak Inc. Legacy device bridge for residential or non-residential networks

Family Cites Families (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6130896A (en) 1997-10-20 2000-10-10 Intel Corporation Wireless LAN segments with point coordination
US6272551B1 (en) 1998-04-08 2001-08-07 Intel Corporation Network adapter for transmitting network packets between a host device and a power line network
US6765927B1 (en) 1999-10-20 2004-07-20 Alcatel RSVP proxy service for communication network
EP1170870A4 (en) * 2000-02-15 2006-08-02 Jfe Steel Corp turbo decoder
CA2404984A1 (en) * 2000-04-04 2001-10-11 Comtech Telecommunications Corp. Enhanced turbo product code decoder system
JP3706301B2 (ja) 2000-10-31 2005-10-12 マブチモーター株式会社 小型モータ
US6947736B2 (en) 2001-11-20 2005-09-20 Texas Instruments Incorporated Universal broadband home network for scalable IEEE 802.11 based wireless and wireline networking
US7082134B1 (en) 2002-01-18 2006-07-25 Juniper Networks, Inc. Redirect checking in a network device
US7113763B2 (en) 2002-06-03 2006-09-26 Nokia Corporation Bluetooth access point and remote bluetooth modules for powerline based networking
US20040264503A1 (en) 2003-06-30 2004-12-30 Microsoft Corporation Method and system for providing a virtual protocol interlayer
US7301949B2 (en) 2003-07-15 2007-11-27 Telefonaktiebolaget Lm Ericsson (Publ) Arrangements for connection-oriented transport in a packet switched communications network
EP1678897A2 (en) 2003-09-23 2006-07-12 Arkados, Inc. Integrated universal network adapter
US7002943B2 (en) * 2003-12-08 2006-02-21 Airtight Networks, Inc. Method and system for monitoring a selected region of an airspace associated with local area networks of computing devices
US7463588B1 (en) 2004-02-18 2008-12-09 Woven Systems, Inc. Mechanism for enabling load balancing to be achieved in a loop-free switching path, reverse path learning network
US8130644B2 (en) 2004-02-18 2012-03-06 Fortinet, Inc. Mechanism for enabling load balancing to be achieved in a loop-free switching path, reverse path learning network
US7447153B2 (en) 2004-02-19 2008-11-04 Internap Network Services Corporation System and method for end to end route control
US20050265308A1 (en) 2004-05-07 2005-12-01 Abdulkadev Barbir Selection techniques for logical grouping of VPN tunnels
FR2871013B1 (fr) * 2004-06-01 2007-02-23 Alcatel Sa Routage pour detection de serveurs au sein d'un reseau de communication
US7269403B1 (en) 2004-06-03 2007-09-11 Miao George J Dual-mode wireless and wired power line communications
US7391317B2 (en) 2004-09-08 2008-06-24 Satius, Inc. Apparatus and method for transmitting digital data over various communication media
CN100521684C (zh) * 2004-09-24 2009-07-29 上海贝尔阿尔卡特股份有限公司 自动获取网络中设备的信息和拓扑结构的方法及其装置
US7539202B2 (en) 2004-11-02 2009-05-26 Cisco Technology, Inc. Maintaining secrecy of assigned unique local addresses for IPv6 nodes within a prescribed site during access of a wide area network
US20060251115A1 (en) 2004-12-03 2006-11-09 Haque Samudra E Broadband multi-service, switching, transmission and distribution architecture for low-cost telecommunications networks
US7262695B2 (en) 2004-12-15 2007-08-28 At&T Intellectual Property, Inc. Network interface device
KR101084129B1 (ko) * 2005-03-24 2011-11-17 엘지전자 주식회사 광대역 무선접속 시스템에서의 슬립모드 지원 방법
KR100714690B1 (ko) * 2005-04-07 2007-05-04 삼성전자주식회사 네트워크를 구성하는 노드들과 브리지의 위상을 검출하는방법 및 장치
US8194656B2 (en) * 2005-04-28 2012-06-05 Cisco Technology, Inc. Metro ethernet network with scaled broadcast and service instance domains
US7349325B2 (en) 2005-05-07 2008-03-25 Motorola, Inc. Broadband over low voltage power lines communications system and method
US20060274752A1 (en) 2005-06-06 2006-12-07 Vinit Jain Method and apparatus for managing address resolution protocol data for interfaces connected to different switches
KR100651737B1 (ko) 2005-06-17 2006-12-01 한국전자통신연구원 Plc 망과 무선망을 연동하는 액세스 포인터 및 그 방법
US8406239B2 (en) 2005-10-03 2013-03-26 Broadcom Corporation Multi-wideband communications over multiple mediums
EP1770870B1 (en) 2005-10-03 2019-04-03 Avago Technologies International Sales Pte. Limited Powerline communication device and method
US20070076666A1 (en) 2005-10-03 2007-04-05 Riveiro Juan C Multi-Wideband Communications over Power Lines
US8213895B2 (en) 2005-10-03 2012-07-03 Broadcom Europe Limited Multi-wideband communications over multiple mediums within a network
CN100555949C (zh) * 2006-03-22 2009-10-28 华为技术有限公司 一种对GPON系统配置Native VLAN以及处理以太网报文的方法
KR100823737B1 (ko) 2006-09-29 2008-04-21 한국전자통신연구원 서로 다른 QoS를 제공하는 네트워크들을 위한 브리지장치
KR100809261B1 (ko) 2006-09-29 2008-03-03 한국전자통신연구원 QoS를 지원하는 고속 전력선 네트워크와 이더넷 간의브리지 시스템
US7848337B1 (en) 2006-11-14 2010-12-07 Cisco Technology, Inc. Auto probing endpoints for performance and fault management
EP2092038B1 (en) 2006-12-12 2017-12-20 Solvay USA Inc. Scale squeeze treatment system
US7729278B2 (en) 2007-02-14 2010-06-01 Tropos Networks, Inc. Wireless routing based on data packet classifications
US7792018B2 (en) 2007-05-18 2010-09-07 Nvidia Corporation Intelligent load balancing and failover of network traffic
US20080294967A1 (en) * 2007-05-21 2008-11-27 Martin Tomlinson Incremental Redundancy Coding System
US7852789B2 (en) 2007-06-20 2010-12-14 At&T Intellectual Property Ii, L.P. Methods, systems, and/or devices for providing network access
US8437272B2 (en) 2007-08-16 2013-05-07 Cisco Technology, Inc. Distinguishing between connectivity verification availability and forwarding protocol functionality in a computer network
US8149839B1 (en) 2007-09-26 2012-04-03 Foundry Networks, Llc Selection of trunk ports and paths using rotation
KR20090062664A (ko) 2007-12-13 2009-06-17 한국전자통신연구원 선박 내부 네트워크에서의 통신 시스템 및 방법
US8977737B2 (en) 2007-12-24 2015-03-10 Alcatel Lucent Detecting legacy bridges in an audio video bridging network
US8223649B2 (en) 2008-03-25 2012-07-17 Intel Corporation Method and apparatus for sending a packet from a source node to a destination node in the same broadcast domain
US8856387B2 (en) 2008-04-24 2014-10-07 Qualcomm Incorporated Local IP access scheme
US8619769B2 (en) 2008-06-12 2013-12-31 Mark Henrik Sandstrom Packet-layer transparent packet-switching network
JP2011015095A (ja) 2009-06-30 2011-01-20 Fujitsu Ltd 通信装置、アドレス設定方法およびアドレス設定プログラム
US9832070B2 (en) 2009-11-13 2017-11-28 Comcast Cable Communications, Llc Communication terminal with multiple virtual network interfaces
CN105141516A (zh) 2010-01-08 2015-12-09 日本电气株式会社 通信系统、转发节点、路径管理服务器以及通信方法
US9300491B2 (en) 2011-02-11 2016-03-29 Qualcomm Incorporated Frame delivery path selection in hybrid communication networks
US8897169B2 (en) 2011-03-02 2014-11-25 Qualcomm Incorporated Discovery of conventional devices and bridges in hybrid communication networks
US9025603B2 (en) 2011-03-08 2015-05-05 Qualcomm Incorporated Addressing scheme for hybrid communication networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6421751B1 (en) * 1998-11-23 2002-07-16 Advanced Micro Devices, Inc. Detecting a no-tags-free condition in a computer system having multiple outstanding transactions
US20040078460A1 (en) * 2002-10-16 2004-04-22 Microsoft Corporation Network connection setup procedure for traffic admission control and implicit network bandwidth reservation
US20040133704A1 (en) * 2003-01-07 2004-07-08 Openpeak Inc. Legacy device bridge for residential or non-residential networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2681663A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9300491B2 (en) 2011-02-11 2016-03-29 Qualcomm Incorporated Frame delivery path selection in hybrid communication networks
US8897169B2 (en) 2011-03-02 2014-11-25 Qualcomm Incorporated Discovery of conventional devices and bridges in hybrid communication networks
US9025603B2 (en) 2011-03-08 2015-05-05 Qualcomm Incorporated Addressing scheme for hybrid communication networks
US10645001B2 (en) 2015-10-28 2020-05-05 Xiaomi Inc. Information transmission method and apparatus, device and storage medium

Also Published As

Publication number Publication date
CN103403697B (zh) 2016-11-09
US8897169B2 (en) 2014-11-25
EP2681663A4 (en) 2014-08-20
US20120224503A1 (en) 2012-09-06
EP2681663A1 (en) 2014-01-08
CN103403697A (zh) 2013-11-20
JP2014511633A (ja) 2014-05-15
KR20130132629A (ko) 2013-12-04
JP5752813B2 (ja) 2015-07-22
KR101494566B1 (ko) 2015-02-17

Similar Documents

Publication Publication Date Title
US8897169B2 (en) Discovery of conventional devices and bridges in hybrid communication networks
US9300491B2 (en) Frame delivery path selection in hybrid communication networks
US9059932B2 (en) Packet ordering based on delivery route changes in communication networks
KR101502263B1 (ko) 하이브리드 통신 네트워크들에 대한 어드레싱 방식
US9014056B2 (en) Bridging network devices in a hybrid communication network
WO2016101646A1 (zh) 以太虚拟网络的接入方法及装置
TWI492588B (zh) 用於多跳混合網路的無縫切換
CN107113892A (zh) 一种网关设备自动组网的方法及装置
CN111245700B (zh) 一种环路检测方法及装置
JP7483924B2 (ja) 接続ステータス検出方法、関連デバイス、コンピュータ記憶媒体、およびコンピュータプログラム
CN106900174A (zh) 无线局域网网状网络的数据传输方法、装置及系统
EP3893542A1 (en) Configuration method and controller
CN102833122B (zh) 一种环回检测方法及系统
JP6191703B2 (ja) 通信制御システム、通信制御方法および通信制御プログラム
EP2728815A1 (en) Method and rbridge for avoiding esadi protocol packet storms
JP2005318011A (ja) ネットワーク経路検索装置、その検索方法、検索プログラム及びネットワーク経路検索システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11859662

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2013556607

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20137026010

Country of ref document: KR

Kind code of ref document: A