City domain ethernet network bridge, system and method for providing service

Abstract

The disclosed Ethernet edge bridge comprises a bridging member including a US port, a NS port and a transmission entity. It also discloses a MAN system including a user bridge network and a provider backbone network. Wherein, the user bridge network connects with the backbone network, and the latter connects with each other through the bridge network. This invention also discloses the method for providing service on edge of the MAN, which comprises: the user bridge network accesses with the US port of MAC-in-MAC edge bridge; the US port builds mapping table between the virtual user ID and provider business, and the MAC-in-MAC edge bridge completes the business mapping or port mapping according to data message and mapping relation.

Description

technical field [0001] The invention relates to the technical field of metropolitan Ethernet, in particular to a metropolitan Ethernet bridge, system and method. Background technique [0002] DA SA TAG (including VID) load verify [0003] In recent years, the development of Ethernet technology has begun to move from local area network to metropolitan area network, but the metropolitan area Ethernet required by operators requires a larger scale and more water domains (4K is far from enough), and requires and user network Isolation (VLANs of the two cannot be mixed together). In order to realize the scalability of Ethernet, support large-capacity Ethernet bearer networks, and isolate user networks and carrier bearer networks, the IEEE standard organization proposed Q-in-Q schemes and MAC-in-MAC schemes. FIG. 1 is a schematic diagram of a Q-in-Q networking solution in the prior art; FIG. 2 is a schematic diagram of a MAC-in-MAC networking solut...

AI Technical Summary

Problems solved by technology

[0028] The advantage of the MAC-in-MAC scheme is that for the backbone bridge network, since the transmission and forwarding in the network core only use the MAC address of the backbone edge MAC access point as the forwarding basis, and the number of edge nodes is not many, the backbone Ethernet core The FDB will not be very large, but the solution is basically positioned at the edge of the backbone bridge network, mainly facing the carrier bridge network. Although a transparent service interface is also defined, it can directly face the user bridge network to a certain extent, but However, it does not define the C-Tagged interface like the carrier bridge, and cannot provide finer-grained services

Images