Metropolitan area network

A metropolitan area network (MAN) is a computer network that interconnects users with computer resources in a geographic region of the size of a metropolitan area. The term MAN is applied to the interconnection of local area networks (LANs) in a city into a single larger network which may then also offer efficient connection to a wide area network. The term is also used to describe the interconnection of several local area networks in a metropolitan area through the use of point-to-point connections between them . By 1994, local area networks (LANs) were well established to provide data communication in buildings and offices. For the interconnection of LANs within a city, businesses relied primarily on the public switched telephone network. But while the telephone network was able to support the packet-based exchange of data that the various LAN protocols implemented, the bandwidth of the telephone network was already under heavy demand from circuit-switched voice, and the telephone exchanges were ill-designed to cope with the traffic spikes that LANs tended to produce. To interconnect local area networks more effectively, it was suggested that office buildings are connected using the single-mode optical fiber lines, which were by that time widely used in long-haul telephone trunks. Such dark fibre links were in some cases already installed on customer premises and telephone companies started to offer their dark fibre within their subscriber packages. Fibre optic metropolitan area networks were operated by telephone companies as private networks for their customers, and did not necessarily have full integation with the public wide area network (WAN) through gateways. Besides the larger companies that connected their offices across an metropolitan area, universities and research institutions also adopted dark fibre as their metropolitan area network backbone. In West Berlin the BERCOM project built up a multifunctional broadband communications system to connect the mainframe computers that publicly funded universities and research institutions in the city housed. The BERCOM MAN project could progress at speed because the Deutsche Bundespost had already installed hundreds of miles of fibre optic cable in West Berlin. Like other metropolitan dark fibre networks at the time, the dark fibre network in West Berlin had a star topology with a hub somewhere in the city centre. The backbone of the dedicated BERCOM MAN for universities and research institutions was a optical fibre double ring that used a high speed slotted ring protocol developed by the GMD Research Centre for Innovative Computer Systems and Telephony. The BERCOM MAN backbone could thus support two times 280 Mbit/s data transfer. The productive use of dense wavelength division multiplexing (DWDM) provided another impetus for the development of metropolitan area networks in the 2000s. Long haul DWDM, with ranges from 0 to 3000+ km, had been developed so that companies that stored large amount of data on different sites, could exchange data or establish mirrors of their file server. With the use of DWDM on the existing fibre optic MANs of carriers, companies no longer needed to connect their LANs with a dedicated fibre optic link. With DWDM companies could build dedicated MANs using the existing dark fibre network of a provider in a city. MANs thus became cheaper to build and maintain. The DWDM platforms provided by dark fibre providers in cities could allow for a single fibre pair to be divided into 32 wavelengths. One multiplexed wavelength could support between 10 Mbit/s and 10 Gbit/s. Thus companies that paid for a MAN to connect different office sites within a city could increase the bandwidths of their MAN backbone as part of their subscription. DWDM platforms also alleviated the need for protocol conversion to connect LANs in a city, because any protocol and any traffic type could be transmitted using DWDM. Effectively it gave companies wishing to establish a MAN choice of protocol. Metro Ethernet, where a fibre optic ring within a larger city was built as MAN backbone carrying Gigabit Ethernet, became common. The ring topology was implemented using the Internet protocol (IP), so that data could be rerouted if a link was congested or one of the links that was part of the ring failed. In the USA the Sprint Corporation was at the forefront of building fibre optic rings that routed IP Packets on the MAN backbone. Between 2002 and 2003 Sprint build three MAN rings to cover San Francisco, Oakland and San Jose, and in turn connected these three metro rings with a further two rings. The Sprint metro rings routed voice and data, were connected to several local telecom exchange points, and totalled 189 miles of fibre optic cable. The metro rings also connected many cities to the Internet that went on to become part of the Silicon Valley tech-hub, such as Fremont, Milpitas, Mountain View, Palo Alto, Redwood City, San Bruno, San Carlos, Santa Clara and Sunnyvale. By adopting IP routing for its metro Ethernet rings, Sprint could re-route traffic in its MANs within milliseconds in the event of fibre cuts or local power outages. The metro Ethernet rings that did not route IP traffic, instead used one of the various proprietary spanning tree protocol implementations, so that each MAN ring had a root bridge. Because layer 2 switching can not operate if there is a loop in the network, the protocols to support L2 MAN rings all need to block redundant links and thus block part of the ring. Capsuling protocols, such as Multiprotocol Label Switching (MPLS), were also deployed to address the drawbacks of operating L2 metro Ethernet rings. Metro Ethernet was effectively the extension of Ethernet protocols beyond the local area network (LAN) and the ensuing investment in Ethernet led to the deployment of carrier Ethernet, where Ethernet protocols are used in wide area networks (WAN). The efforts of the Metro Ethernet Forum (MEF) in defining best practice and standards for metropolitan area networks thus also defined carrier Ethernet. While the IEEE tried to standardise the emerging Ethernet based proprietary protocols, industry forums such as the MEF filled the gap and in January 2013 launched a certification for network equipment that can be configured to meet Carrier Ethernet 2.0 specifications.