Cross network bridging
US-12119958-B2 · Oct 15, 2024 · US
US9385885B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9385885-B2 |
| Application number | US-98678611-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 7, 2011 |
| Priority date | Jan 8, 2010 |
| Publication date | Jul 5, 2016 |
| Grant date | Jul 5, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A network node for a communication network comprising a first subnetwork and a second subnetwork connected to the first subnetwork, wherein the first subnetwork uses a spanning tree protocol and the second subnetwork uses a second protocol differing from the protocol of the first subnetwork, and the network node is configured as an element for the second subnetwork and is configured for communication within the second subnetwork. In addition, the network node configured by a spanning tree functionality as a spanning tree master node for checking and controlling the second subnetwork in such a way that the second subnetwork is handled or is able to be handled by the spanning tree protocol of the first subnetwork as a virtual network node.
Opening claim text (preview).
What is claimed is: 1. A network node for a communication network having a first subnetwork using a spanning tree protocol and a second subnetwork connected to the first subnetwork, the second subnetwork using a second protocol differing from the spanning tree protocol of the first subnetwork: the network node being configured as an element of the second subnetwork and configured for communication within the second subnetwork; and the second subnetwork having at least one external interface; wherein the network node is configured by a spanning tree functionality as a spanning tree master node to check and control the second subnetwork such that the second subnetwork is handled or is able to be handled by the spanning tree protocol of the first subnetwork as a virtual network node such that the second subnetwork is identifiable as a single node by the first subnetwork; wherein the spanning tree functionality of the spanning tree master node comprises: issuing interface identification data comprising Port ID information for external interfaces of the second subnetwork, said external interface comprising interfaces of network nodes which are unconnected between network nodes; and transferring the interface identification data comprising Port ID to other network nodes of the second subnetwork. 2. The network node as claimed in claim 1 , wherein the spanning tree protocol (STP) comprises at least one of a STP protocol, a rapid spanning tree protocol (RSTP) and a multiple spanning tree protocol (MSTP), and the spanning tree functionality comprises at least one of STP functionality, an RSTP functionality and a MSTP functionality. 3. The network node as claimed in claim 1 , wherein the second subnetwork has at least one of a linear structure and ring structure. 4. The network node as claimed in claim 2 , wherein the second subnetwork has at least one of a linear structure and ring structure. 5. The network node as claimed in claim 1 , wherein the second subnetwork uses a realtime-capable protocol, which further uses at least one of a HiPER Ring, hierarchically segmented routing (HSR), Turbo Ring, resilient Ethernet protocol (REP) and multiple registration protocol (MRP). 6. The network node as claimed in claim 1 , wherein the spanning tree functionality of the spanning tree master node further includes at least one of: (i) detecting external interfaces of the second subnetwork, (ii) computing one of interface states and external interfaces of the second subnetwork, (iii) transmitting the interface states to other network nodes of the second subnetwork, (iv) at least one of receiving a protocol data message assigned to the spanning tree protocol from a further network node of the second subnetwork and (v) at least one of (a) determining a reaction to the received protocol data message and (b) transferring a response protocol data message as a reaction to the received protocol data message to the further network node of the second subnetwork; and wherein a functionality of the spanning tree master node as a central node for the first subnetwork is such that the second subnetwork is handled or is able to be handled by the spanning tree functionality of the spanning tree master node by the spanning tree protocol of the first subnetwork as the central node for the first subnetwork. 7. The network node as claimed in claim 1 , wherein the network node as the spanning tree master node is configured to allocate to another network node a functionality of a spanning tree reserve master node. 8. The network node as claimed in claim 7 , wherein the network node as the spanning tree master node one of transfers required information and is configured to transfer the required information to implement a spanning tree functionality of the spanning tree reserve master node. 9. The network node as claimed in claim 8 , wherein the network node as the spanning tree master node at least one of (i) transfers received information in accordance with one of (a) a predetermined rule or (b) a predeterminable rule and (ii) is configured to transfer the received information in accordance with one of (a) the predetermined rule or (b) the predeterminable rule.
Multiprotocol routers · CPC title
Loop networks · CPC title
LAN interconnection over a bridge based backbone · CPC title
Routing tree calculation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.