CN1937567A - Method for determining port role - Google Patents
Method for determining port role Download PDFInfo
- Publication number
- CN1937567A CN1937567A CNA2006101093507A CN200610109350A CN1937567A CN 1937567 A CN1937567 A CN 1937567A CN A2006101093507 A CNA2006101093507 A CN A2006101093507A CN 200610109350 A CN200610109350 A CN 200610109350A CN 1937567 A CN1937567 A CN 1937567A
- Authority
- CN
- China
- Prior art keywords
- port
- root
- role
- message
- hvrp
- 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.)
- Granted
Links
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention discloses a role-of-port determining method, comprising the steps of: determining a port receives a message and determining the role of the port. And it can make HVRP application range not restricted by MSTP application range any more and make HVRP protocol able to apply to any network environment. Because it determines the role of a port by handshake message of HVRP protocol and it only need take the handshake message completely short time to be sent from the root bridge to the farthest- end HVRP bridge, role calculation of each HVRP bridge port can be synchronized basically, better assuring normal operating of HVRP protocol and raising the speed of determining role of port.
Description
Technical field
The present invention relates to virtual local area network technology, refer to a kind of method of definite port role especially.
Background technology
In the typical metropolitan area of prior art networking plan, convergence-level adopts ring topology to carry out the connection of equipment room usually, and the convergence-level equipment that converges on the looped network is visited core net by the convergence-level outlet device, and concrete structure as shown in Figure 1.Ring topology as shown in Figure 1 comprises Broadband Remote Access Server (BRAS), convergence switch 1, convergence switch 2, convergence switch 3, convergence switch 4 and convergence switch 5.Wherein, the convergence-level outlet device is a convergence switch 1, and convergence-level switch 1 connects core net by BRAS, and convergence switch 2, convergence switch 3, convergence switch 4 and convergence switch 5 are by convergence switch 1 visit external core network.
In order to avoid producing broadcast storm on the looped network converging; usually can on convergence-level equipment, enable Spanning-Tree Protocol (STP; Spanning Tree Protocol), RSTP (RSTP; RapidSpanning Tree Protocol) or fast loop protection agreement (RRPP; Rapid Ring ProtectionProtocol) etc. link layer blocks agreement and carries out link obstructions; network topology structure after make blocking is a tree topology, thereby avoids producing broadcast storm on the looped network converging.
Tree structure as shown in Figure 2 is the topological schematic diagram of Fig. 1 ring topology after B point place blocks.Node 1 in convergence switch 1 corresponding diagram 2 among Fig. 1, convergence switch 2 corresponding node 2, convergence switch 3 corresponding node 3, convergence switch 4 corresponding node 4, convergence switch 5 corresponding node 5.When as shown in Figure 1 ring topological structure blocked the tree topology that becomes as shown in Figure 2, convergence switch 1 can be described as the upstream equipment of convergence switch 2 and convergence switch 5; Accordingly, convergence switch 2 and convergence switch 3 can be described as the upstream device of convergence switch 1, other convergence switch by that analogy.
In the prior art, a kind of hierarchical virtual local network log (HVRP) agreement has been proposed, use the HVRP agreement on the looped network converging of link obstructions, can make convergence switch need not learn the forwarding unit of extension under the user port and the MAC Address of adjacent convergence switch, just can realize that user's message is in correct port forwarding.In this article, claim that the convergence switch of operation HVRP agreement is the HVRP bridge.The basic principle of HVRP agreement is:
Media access control protocol (MAC) mode of learning of HVRP bridge at first is set: when the port number of (VLAN) VLAN on the HVRP bridge is less than or equal to two ports, this HVRP bridge is set in current VLAN, do not carry out MAC address learning; When the port number in the VLAN during, be set in current VLAN, carry out MAC address learning more than two ports.Then, the HVRP bridge is set periodically sends logon message, be used for the registration of bridge upstream self to allow the VLAN that passes through.The VLAN that the upstream bridge is indicated in to logon message at the port of receiving logon message registers, and the VLAN that is not registered in the deletion certain hour on port, and promptly VLAN's is aging.After network topology is stable, just can guarantee in the VLAN on a HVRP bridge two ports are only arranged by above-mentioned registration, aging mode.So, when a certain user's message that issues from core net need be transmitted by the HVRP bridge, when being sent to corresponding user port, the HVRP bridge at first can be searched mac address table according to the purpose MAC of user's message, because the HVRP bridge does not carry out the MAC address learning of current VLAN when having only two ports in a VLAN, therefore do not have corresponding MAC Address list item in the mac address table, the HVRP bridge can't find corresponding output port.At this moment, the HVRP bridge then can be broadcasted in the VLAN of user's message correspondence and be transmitted this message, and the port that promptly every this VLAN of permission passes through all can be transmitted this message.Because the HVRP bridge has carried out the aging of port vlan, makes and all have only two ports in each VLAN that promptly outbound port is unique, so user's message must send from unique correct outbound port.Need not study thereby reached, just can realize the correct purpose of transmitting of user's message.
This shows in the HVRP agreement, determine that the HVRP bridge is used to receive the port of upstream bridge timed sending handshake message and the logon message of bridge forwarding upstream, and be used to receive the logon message of downstream bridge transmission and carry out the aging port of VLAN, be the important leverage that realizes the HVRP agreement.Have only the role who has determined each port of convergence switch accurately could guarantee the normal operation of HVRP agreement.
Existing HVRP agreement uses Multiple Spanning Tree Protocol (MSTP, Multiple SpanningTree Protocol) agreement to consult to determine the role of each port of convergence switch usually.But, because MSTP agreement and HVRP agreement have very strong coupling, cause the HVRP agreement to block the agreement mixed networking with other link layers, as RRPP, therefore greatly limited the scope of application of HVRP agreement.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of method of definite port role, uses the constraint that the scope of application that this method can make the HVRP agreement no longer is subjected to the MSTP agreement scope of application, makes the HVRP agreement can be applicable to any network environment.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of method of definite port role, this method may further comprise the steps:
After determining that port is received message, determine port role.
Wherein, described port role comprises: designated port and root port;
Described definite port receives that message is: determine that port receives handshake message;
The role who determines port is: determine to receive that the port of handshake message is a root port, the port of not receiving handshake message is a designated port.
Wherein, described port is: hierarchical virtual local network log-on protocol HVRP port.
In addition, after definite port is received message, determine that before the role of port, this method further comprises:
Judge to receive whether the port of handshake message is root port, when the port of receiving handshake message is not root port, carry out the step of described definite port role.
Wherein, the step of carrying out described definite port role by transmission bridge in the looped network or backup root bridge.
In addition, this method further comprises: the uplink port of root bridge in the configuration looped network, the HVRP port of determining the root bridge is a designated port.
In addition, described port role also comprises: free port;
This method further comprises: the overtime duration of handshake message is set, when root port is not received handshake message in the overtime duration of handshake message, determines that root port place transmission bridge or all HVRP ports of backup root bridge are free port.
Wherein, described port role also comprises: port blocked;
This method further comprises: after determining that port blocked is received logon message, determine to receive that the port blocked of logon message is a designated port.
In addition, this method further comprises: the overtime duration of logon message is set, when designated port is not received logon message in the overtime duration of logon message, determines that described designated port is a port blocked.
In addition, a kind of method of definite port role, port role comprises: root port and designated port; Carry out following steps:
Judge whether port receives the message that the root bridge regularly sends, if receive, then described port is a root port; Otherwise described port is a designated port.
Wherein, the message that described bridge regularly sends is a hello packet, and described port is a hierarchical virtual local network log-on protocol HVRP port.
In addition, after definite port is received message, determine that before the role of port, this method further comprises:
Judge to receive whether the port of hello packet is root port, when the port of receiving hello packet is not root port, carry out the step of described definite port role.
Wherein, the step of carrying out described definite port role by transmission bridge in the looped network or backup root bridge.
In addition, this method further comprises: the uplink port of root bridge in the configuration looped network, the HVRP port of determining the root bridge is a designated port.
In addition, described port role also comprises: free port;
This method further comprises: the overtime duration of hello packet is set, when root port is not received hello packet in the overtime duration of hello packet, determines that root port place transmission bridge or all HVRP ports of backup root bridge are free port.
In addition, described port role also comprises: port blocked;
This method further comprises: after determining that port blocked is received logon message, determine to receive that the port blocked of logon message is a designated port.
In addition, this method further comprises: the overtime duration of logon message is set, when designated port is not received logon message in the overtime duration of logon message, determines that described designated port is a port blocked.
The method of definite port role provided by the present invention, after determining that port is received message, determine port role, promptly transmit bridge and determine that port receives handshake message, and determine to receive that the HVRP port of handshake message is a root port, self other HVRP port is a designated port.Method provided by the present invention is by utilizing the message of HVRP agreement self, determine to receive that the HVRP port of handshake message is a root port, self other HVRP port is a designated port, therefore make the scope of application of HVRP agreement no longer be subjected to the constraint that link layer such as MSTP agreement blocks the agreement scopes of application, make the HVRP agreement can be applicable to any network environment.Simultaneously, determine the role of port owing to utilize the handshake message of HVRP agreement, handshake message only needs through the very short time from the HVRP bridge that the root bridge is issued to distal-most end again, therefore each HVRP bridge port role calculate can basic synchronization, better guarantee the normal operation of HVRP agreement, improved the speed of definite port role.
Description of drawings
Fig. 1 is prior art convergence-level ring topology figure.
Fig. 2 is prior art convergence-level tree topology figure.
Fig. 3 is one embodiment of the invention method flow diagram.
Fig. 4 is another embodiment of the present invention method flow diagram.
Fig. 5 be have a backup root bridge converge the ring network structure schematic diagram.
Fig. 6 is a port role transition process schematic diagram of the present invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.
In order to guarantee the normal operation of HVRP agreement, at first must determine the port role that the HVRP bridge uses.In the present embodiment, be that the hello packet of root bridge timed sending is that example is described with the handshake message.According to the analysis to the HVRP agreement, employed port role must comprise in the HVRP agreement: free port, root port and designated port.The function of these three kinds of port roles is respectively:
Free port, the port that newly enables the HVRP agreement is called free port, and free port does not carry out any HVRP action, as operations such as the VLAN registration of HVRP port, aging, recoveries.
Root port is responsible for receiving the hello packet that the upstream bridge is transmitted in transmitting bridge, and the VLAN logon message of the downstream of bridge forwarding upstream bridge, does not carry out VLAN and wear out on root port.
Designated port is responsible for transmitting the hello packet that the root bridge sends, and is received the VLAN logon message that the downstream bridge is transmitted up, and designated port need dynamically be deleted the unregistered VLAN in downstream.
In addition, in the present invention, the port that claims to enable the HVRP agreement is the HVRP port, and the port that does not enable the HVRP agreement is called and does not activate port.
In topology diagram as shown in Figure 1, weighing-appliance has the convergence switch 1 of convergence-level outlet function to be the root bridge, and convergence switch 2 to 5 is the transmission bridge.Wherein, the port that the root bridge is responsible for communicating with core net is called uplink port, and uplink port disposes generation on the port that does not enable the HVRP agreement.On the root bridge, there is not root port.
Various port role's transition process is: when a certain HVRP port of HVRP bridge is received hello packet, then this port migration of receiving hello packet is root port, the every other HVRP port of traversal on propons is designated port with these HVRP port migrations simultaneously.Simultaneously, for the operate as normal that guarantees that selected root port can be permanently effective, can also work as root port when not receiving hello packet within a certain period of time, the root port migration is free port, the every other HVRP port of traversal on propons is free port with these HVRP port migrations simultaneously.Wherein, converge being defined as of root bridge port in the looped network: when certain converges switching equipment when being set to the root bridge, it is uplink port that configuration one does not activate port, and all that travel through when propons enable the port of HVRP then, and these HVRP ports-settings are the designated port when propons.
The process that the transmission bridge is determined self port role specifically may further comprise the steps as shown in Figure 3:
Step 301: the transmission bridge is received the hello packet that the upstream bridge sends.
Here, according to the residing topology location of transmission bridge, the upstream bridge may be the transmission bridge, also may be the root bridge.
Step 302: the transmission bridge judges whether the port of self receiving hello packet is root port, if then execution in step 304; Otherwise, execution in step 303.
Step 303: the transmission bridge is root port with the HVRP port migration of self receiving hello packet, and self other HVRP ports migration is designated port.
Step 304: then finish current handling process.
Here, receive that hello packet and migration may be free ports, also might be the designated ends mouths for the HVRP port of root port.Because receiving hello packet is the work of root port, therefore after free port and designated port receive Hello, then self being moved is root port, and travels through all the HVRP ports when propons, and all the HVRP ports except that the root port of newly selecting are set to designated port.
Simultaneously, in order to guarantee the selected permanently effective operate as normal of root port that goes out, the overtime duration of hello packet can also be set, after the transmission bridge is root port with a certain HVRP port migration, be provided with and the startup timer at this root port, when timer arrives the overtime duration of hello packet, if this root port is not received hello packet, then this root port migration is free port, traversal all HVRP ports on propons are free port with these HVRP port migrations simultaneously; Before timer arrives the overtime duration of hello packet, just received hello packet at root port, timer resets and restarts timing.Wherein, the overtime duration of hello packet can be set to the hello packet transmission cycle more than or equal to 4 times.
Owing to before converging looped network operation HVRP agreement, converges looped network and moved link layer obstruction agreement, and the topological structure on the ring is a tree structure.Therefore converging on the choke point of looped network, B point for example shown in Figure 1, though transmission bridge 5 can be transmitted the hello packet that self receives to the downstream node transmission bridge 4 of self, but because link layer blocks the support of agreement, as MSTP, the hello packet that forwards from transmission bridge 5 can be dropped in physical layer automatically in the choke point.
And then, in order to improve the forward efficiency of HVRP bridge, can also to increase another port role is set: port blocked.The function of port blocked is, abandons the hello packet that needs self to transmit, and aging all VLAN.Use the user's message that port blocked can abandon automatically in the choke point needs self to transmit, do not abandon hello packet and do not need to utilize link layer to block agreement, processing procedure has been accelerated the speed of HVRP bridge processing message, the system resource of having saved the HVRP bridge like this.
Being defined as of port blocked: when designated port was not received logon message from the downstream bridge in a period of time, then this designated port migration was port blocked; And when port blocked was received logon message from the downstream bridge, the port blocked migration was designated port; When port blocked is received hello packet from the upstream bridge, move and be root port, the every other HVRP port of traversal on propons is designated port with these HVRP ports migrations simultaneously.
The designated port migration for the concrete implementation of port blocked is: the overtime duration of logon message is set, when determining that according to the method for flow chart 3 some HVRP ports are designated port, then be provided with and the startup timer at this designated port, when timer arrives the overtime duration of logon message, if this designated port is not received logon message, then this designated port migration is port blocked; When designated port before timer arrives the overtime duration of logon message, received logon message, then timer resets and picks up counting again.Wherein, the overtime duration of logon message can be set to the logon message transmission cycle more than or equal to 4 times.
Transfer process between above-described designated port and the port blocked is equally applicable to the designated port in the root bridge.
In flow process as shown in Figure 3, description be: when the HVRP of non-root port port is received hello packet, self port role migration is root port.In the present invention, also there is the another one execution mode, promptly as long as the HVRP port is received hello packet, then the port role migration with self is root port, and other HVRP ports on the bridge that will coexist, migration is for designated port, and no matter self current port role is root port or non-root port.If adopt this execution mode, then do not need the overtime duration of hello packet is set, and this port type of port blocked.
Detailed process is as shown in Figure 4:
Step 401: the transmission bridge is received the hello packet that the upstream bridge sends.
Step 402: determine to receive that the HVRP port of hello packet is a root port, self other HVRP port is a designated port.
In addition, as shown in Figure 5, when also having a backup root bridge on converging looped network, definite method of this backup root bridge port role is with definite method basically identical of transmission bridge port role.Just when a backup root bridge upgrades to primary root bridge, can travel through self all HVRP port, these HVRP ports are set to designated port; And when primary root bridge is downgraded to backup root bridge, can at first that self is all HVRP ports move to free port, and determine the role of self each HVRP port then according to the hello packet of receiving, concrete method is the same with method of the present invention.
For the situation that makes each port role state transition clearer, now with uplink port, do not activate port, free port, designated port, root port and port blocked, role's transition process under different situations has carried out a concrete description, specifically as shown in Figure 6.
After utilizing method provided by the present invention, the HVRP agreement then can use the various port role to realize the function of HVRP agreement smoothly.
The present invention determines that the method for port role can also be applied to Ethernet dynamic protocol port role and calculate in the process of determining.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.
Claims (17)
1, a kind of method of definite port role is characterized in that, this method may further comprise the steps:
After determining that port is received message, determine port role.
2, method according to claim 1 is characterized in that, described port role comprises: designated port and root port;
Described definite port receives that message is: determine that port receives handshake message;
The role who determines port is: determine to receive that the port of handshake message is a root port, the port of not receiving handshake message is a designated port.
3, method according to claim 2 is characterized in that, described port is: hierarchical virtual local network log-on protocol HVRP port.
4, method according to claim 3 is characterized in that, after definite port is received message, determines that before the role of port, this method further comprises:
Judge to receive whether the port of handshake message is root port, when the port of receiving handshake message is not root port, carry out the step of described definite port role.
5, method according to claim 3 is characterized in that, the step of carrying out described definite port role by transmission bridge in the looped network or backup root bridge.
6, method according to claim 5 is characterized in that, this method further comprises: the uplink port of root bridge in the configuration looped network, the HVRP port of determining the root bridge is a designated port.
7, method according to claim 3 is characterized in that, described port role also comprises: free port;
This method further comprises: the overtime duration of handshake message is set, when root port is not received handshake message in the overtime duration of handshake message, determines that root port place transmission bridge or all HVRP ports of backup root bridge are free port.
8, according to the described method of arbitrary claim in the claim 2 to 7, it is characterized in that described port role also comprises: port blocked;
This method further comprises: after determining that port blocked is received logon message, determine to receive that the port blocked of logon message is a designated port.
9, method according to claim 8 is characterized in that, this method further comprises: the overtime duration of logon message is set, when designated port is not received logon message in the overtime duration of logon message, determines that described designated port is a port blocked.
10, a kind of method of definite port role is characterized in that, port role comprises: root port and designated port; Carry out following steps:
Judge whether port receives the message that the root bridge regularly sends, if receive, then described port is a root port; Otherwise described port is a designated port.
11, method according to claim 10 is characterized in that, the message that described bridge regularly sends is a hello packet, and described port is a hierarchical virtual local network log-on protocol HVRP port.
12, method according to claim 11 is characterized in that, after definite port is received message, determines that before the role of port, this method further comprises:
Judge to receive whether the port of hello packet is root port, when the port of receiving hello packet is not root port, carry out the step of described definite port role.
13, method according to claim 11 is characterized in that, the step of carrying out described definite port role by transmission bridge in the looped network or backup root bridge.
14, method according to claim 13 is characterized in that, this method further comprises: the uplink port of root bridge in the configuration looped network, the HVRP port of determining the root bridge is a designated port.
15, method according to claim 11 is characterized in that, described port role also comprises: free port;
This method further comprises: the overtime duration of hello packet is set, when root port is not received hello packet in the overtime duration of hello packet, determines that root port place transmission bridge or all HVRP ports of backup root bridge are free port.
16, according to the described method of arbitrary claim in the claim 10 to 15, it is characterized in that described port role also comprises: port blocked;
This method further comprises: after determining that port blocked is received logon message, determine to receive that the port blocked of logon message is a designated port.
17, method according to claim 16 is characterized in that, this method further comprises: the overtime duration of logon message is set, when designated port is not received logon message in the overtime duration of logon message, determines that described designated port is a port blocked.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101093507A CN100459526C (en) | 2006-08-10 | 2006-08-10 | Method for determining port role |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101093507A CN100459526C (en) | 2006-08-10 | 2006-08-10 | Method for determining port role |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1937567A true CN1937567A (en) | 2007-03-28 |
| CN100459526C CN100459526C (en) | 2009-02-04 |
Family
ID=37954843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101093507A Active CN100459526C (en) | 2006-08-10 | 2006-08-10 | Method for determining port role |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100459526C (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483571B (en) * | 2009-02-26 | 2011-06-29 | 杭州华三通信技术有限公司 | RRPP configuring method, system and device |
| CN102932186A (en) * | 2012-11-13 | 2013-02-13 | 杭州迪普科技有限公司 | Trunking system and method of removing loop circuits |
| CN102055656B (en) * | 2009-10-28 | 2013-03-20 | 杭州华三通信技术有限公司 | Processing method for generating link oscillation in tree protocol network and switchboard thereof |
| CN103312429A (en) * | 2013-06-08 | 2013-09-18 | 杭州华三通信技术有限公司 | Time synchronization method and time synchronization device |
| CN105162733A (en) * | 2015-09-25 | 2015-12-16 | 上海斐讯数据通信技术有限公司 | Method and device for determining edge interface |
| CN111585854A (en) * | 2020-05-12 | 2020-08-25 | 中国移动通信集团内蒙古有限公司 | Network system, protection method, device and storage medium for data network load scheduling |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7061875B1 (en) * | 2001-12-07 | 2006-06-13 | Cisco Technology, Inc. | Spanning tree loop guard |
| CN100337428C (en) * | 2003-01-24 | 2007-09-12 | 华为技术有限公司 | Method for managing ring network based on protocol of spanning tree |
| US7916668B2 (en) * | 2004-12-30 | 2011-03-29 | Alcatel Lucent | Spanning tree protocol with burst avoidance |
| CN100499661C (en) * | 2006-01-11 | 2009-06-10 | 杭州华三通信技术有限公司 | Port state shift method |
-
2006
- 2006-08-10 CN CNB2006101093507A patent/CN100459526C/en active Active
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101483571B (en) * | 2009-02-26 | 2011-06-29 | 杭州华三通信技术有限公司 | RRPP configuring method, system and device |
| CN102055656B (en) * | 2009-10-28 | 2013-03-20 | 杭州华三通信技术有限公司 | Processing method for generating link oscillation in tree protocol network and switchboard thereof |
| CN102932186A (en) * | 2012-11-13 | 2013-02-13 | 杭州迪普科技有限公司 | Trunking system and method of removing loop circuits |
| CN102932186B (en) * | 2012-11-13 | 2015-05-06 | 杭州迪普科技有限公司 | Trunking system and method of removing loop circuits |
| CN103312429A (en) * | 2013-06-08 | 2013-09-18 | 杭州华三通信技术有限公司 | Time synchronization method and time synchronization device |
| CN103312429B (en) * | 2013-06-08 | 2015-11-25 | 杭州华三通信技术有限公司 | A kind of method for synchronizing time and device |
| CN105162733A (en) * | 2015-09-25 | 2015-12-16 | 上海斐讯数据通信技术有限公司 | Method and device for determining edge interface |
| CN105162733B (en) * | 2015-09-25 | 2018-04-06 | 上海斐讯数据通信技术有限公司 | A kind of method and apparatus for determining edge interface |
| CN111585854A (en) * | 2020-05-12 | 2020-08-25 | 中国移动通信集团内蒙古有限公司 | Network system, protection method, device and storage medium for data network load scheduling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100459526C (en) | 2009-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6202114B1 (en) | Spanning tree with fast link-failure convergence | |
| CN100459526C (en) | Method for determining port role | |
| US8767587B1 (en) | Exploratory linktrace operations in a computer network | |
| CN103269299B (en) | Message forwarding method in SPBM network and device | |
| CN104378296A (en) | Message forwarding method and device | |
| CN101997735A (en) | Monocylic network topology reconstruction method and system thereof | |
| WO2011110029A1 (en) | Method and system for host route reachability in packet transport network access ring | |
| US20140226525A1 (en) | Safe Multicast Distribution with Predictable Topology Changes | |
| CN101110820B (en) | Method and switchboard for processing spanning tree protocol message | |
| CN106487558A (en) | A kind of method and apparatus realizing the scalable appearance of access device | |
| CN102223312B (en) | Flow control method and equipment based on link status | |
| CN105959216B (en) | A kind of communication means, the apparatus and system of unidirectional serial bus network | |
| CN109428766A (en) | Software defined network system with switch automatically deployed and method thereof | |
| US10348620B2 (en) | Minimum disruption MST reconfiguration (MDMR) | |
| CN104980302A (en) | STP-based method for removing redundancy link under SDN framework | |
| WO2012119372A1 (en) | Message processing method, device and system | |
| CN101902399B (en) | Wireless network communication method, system and device based on spanning tree protocol (STP) | |
| CN103916318A (en) | Single-loop network implementation method | |
| CN108601055B (en) | Method and system for deploying L3 VPN in L TE mobile backhaul network | |
| CN101453412A (en) | Method and apparatus for automatic topology discovery and resource management in PBB network | |
| CN100435528C (en) | Method for reducing learning of media accessing control address in network | |
| WO2014187197A1 (en) | Migrating multicast flow | |
| CN103685029A (en) | Method and equipment for forwarding messages in rapid ring protection protocol networking | |
| Moldovansky | Utilization of modern switching technology in ethernet/IP networks | |
| WO2015058413A1 (en) | Data configuration method and network management server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |