A backbone is a part of computer network that interconnects various pieces of network, providing a path for the exchange of information between different LANs or subnetworks. A backbone can tie together diverse networks in the same building, in different buildings in a campus environment, or over wide areas. Normally, the backbone's capacity is greater than the networks connected to it.
A large corporation that has many locations may have a backbone network that ties all of the locations together, for example, if a server cluster needs to be accessed by different departments of a company that are located at different geographical locations. The pieces of the network connections (for example: ethernet, wireless) that bring these departments together is often mentioned as network backbone. Network congestion is often taken into consideration while designing backbones.
The theory, design principles, and first instantiation of the backbone network came from the telephone core network, when traffic was purely voice. The core network was the central part of a telecommunications network that provided various services to customers who were connected by the access network. One of the main functions was to route telephone calls across the PSTN.
Typically the term referred to the high capacity communication facilities that connect primary nodes. A core network provided paths for the exchange of information between different sub-networks.
Core networks usually had a mesh topology that provided any-to-any connections among devices on the network. Many main service providers would have their own core/backbone networks that are interconnected. Some large enterprises have their own core/backbone network, which are typically connected to the public networks.
Core networks typically provided the following functionality:
- Aggregation: The highest level of aggregation in a service provider network. The next level in the hierarchy under the core nodes is the distribution networks and then the edge networks. Customer-premises equipment (CPE) do not normally connect to the core networks of a large service provider.
- Authentication: The function to decide whether the user requesting a service from the telecom network is authorized to do so within this network or not.
- Call Control/Switching: call control or switching functionality decides the future course of call based on the call signalling processing. E.g. switching functionality may decide based on the "called number" that the call be routed towards a subscriber within this operator's network or with number portability more prevalent to another operator's network.
- Charging: This functionality of the collation and processing of charging data generated by various network nodes. Two common types of charging mechanisms found in present-day networks are prepaid charging and postpaid charging. See Automatic Message Accounting
- Service Invocation: Core network performs the task of service invocation for its subscribers. Service invocation may happen based on some explicit action (e.g. call transfer) by user or implicitly (call waiting). It's important to note however that service "execution" may or may not be a core network functionality as third party network/nodes may take part in actual service execution.
- Gateways: Gateways shall be present in the core network to access other networks. Gateway functionality is dependent on the type of network it interfaces with.
Physically, one or more of these logical functionalities may simultaneously exist in a given core network node.
Besides above mentioned functionalities, the following also formed part of a telecommunications core network:
- O&M: Operations & Maintenance centre or Operations Support Systems to configure and provision the core network nodes. Number of subscribers, peak hour call rate, nature of services, geographical preferences are some of the factors which impact the configuration. Network statistics collection (Performance Management), alarm monitoring (Fault Management) and logging of various network nodes actions (Event Management) also happens in the O&M centre. These stats, alarms and traces form important tools for a network operator to monitor the network health and performance and improvise on the same.
- Subscriber Database: Core network also hosts the subscribers database (e.g. HLR in GSM systems). Subscriber database is accessed by core network nodes for functions like authentication, profiling, service invocation etc.
A distributed backbone is a backbone network that consists of a number of connectivity devices connected to a series of central connectivity devices, such as hubs, switches, or routers, in a hierarchy. This kind of topology allows for simple expansion and limited capital outlay for growth, because more layers of devices can be added to existing layers. In a distributed backbone network, all of the devices that access the backbone share the transmission media, as every device connected to this network is sent all transmissions placed on that network.
Distributed backbones, in all practicality, are in use by all large-scale networks. Applications in enterprise-wide scenarios confined to a single building are also practical, as certain connectivity devices can be assigned to certain floors or departments. Each floor or department possesses a LAN and a wiring closet with that workgroup's main hub or router connected to a bus-style network using backbone cabling . Another advantage of using a distributed backbone is the ability for network administrator to segregate workgroups for ease of management.
There is the possibility of single points of failure, referring to connectivity devices high in the series hierarchy. The distributed backbone must be designed to separate network traffic circulating on each individual LAN from the backbone network traffic by using access devices such as routers and bridges.
A collapsed backbone (inverted backbone, backbone-in-a-box) is a type of backbone network architecture. The traditional backbone network goes over the globe to provide interconnectivity to the remote hubs. In most cases, the backbones are the links while the switching or routing functions are done by the equipment at each hub. It is a distributed architecture.
In the case of a collapsed or inverted backbone, each hub provides a link back to a central location to be connected to a backbone-in-a-box. That box can be a switch or a router. The topology and architecture of a collapsed backbone is a star or a rooted tree.
The main advantages of the collapsed backbone approach are
- ease of management since the backbone is in a single location and in a single box, and
- since the backbone is essentially the back plane or internal switching matrix of the box, proprietary, high performance technology can be used.
However, the drawback of the collapsed backbone is that if the box housing the backbone is down or there are reachability problem to the central location, the entire network will crash. These problems can be minimized by having redundant backbone boxes as well as having secondary/backup backbone locations.
There are a few different types of backbones that are used for an enterprise-wide network. When organizations are looking for a very strong and trustworthy backbone they should choose a parallel backbone. This backbone is a variation of a collapsed backbone in that it uses a central node (connection point). Although, with a parallel backbone, it allows for duplicate connections when there is more than one router or switch. Each switch and router are connected by two cables. By having more than one cable connecting each device, it ensures network connectivity to any area of the enterprise-wide network.
Parallel backbones are more expensive than other backbone networks because they require more cabling than the other network topologies. Although this can be a major factor when deciding which enterprise-wide topology to use, the expense of it makes up for the efficiency it creates by adding increased performance and fault tolerance. Most organizations use parallel backbones when there are critical devices on the network. For example, if there is important data, such as payroll, that should be accessed at all times by multiple departments, then your organization should choose to implement a Parallel Backbone to make sure that the connectivity is never lost.
A serial backbone is the simplest kind of backbone network. Serial backbones consist of two or more internet working devices connected to each other by a single cable in a daisy-chain fashion. A daisy chain is a group of connectivity devices linked together in a serial fashion. Hubs are often connected in this way to extend a network. However, hubs are not the only device that can be connected in a serial backbone. Gateways, routers, switches and bridges more commonly form part of the backbone. The serial backbone topology could be used for enterprise-wide networks, though it is rarely implemented for that purpose.
- What is a Backbone?, Whatis.com, Accessed: June 25, 2007
- "Backbone Networks". Chapter 8. Angelfire. Retrieved 2 October 2013.
- Turner, Brough (12 September 2007). "Congestion in the Backbone: Telecom and Internet Solutions". CircleID. Retrieved 2 October 2013.
- Kashyap, Abhishek; Sun, Fangting; Shayman, Mark. "Relay Placement for Minimizing Congestion in Wireless Backbone Networks" (PDF). Department of Electrical and Computer Engineering, University of Maryland. Retrieved 2 October 2013.
- Howdie, Ben (28 January 2013). "The Backbone's connected to the…". KashFlow. Retrieved 2 October 2013.
- Tamara Dean. Network+ Guide to Networks. Course Technology, Cengage Learning, 2010, p. 202.
- BICSI Lan Design Manual - CD-ROM, Issue 1, Distributed backbone network, p.20 , 1996, accessed May 7, 2011.
- Dooley, Kevin. Designing Large-Scale Networks, p.23 , O'Reilly Online Catalog, January, 2002, accessed May 7, 2011.
- Distributed Backbone , accessed May 7, 2011.
- Boon & Kepekci (1996). BICSI Lan Design Manual. Tampa, FL. pp. 20–21.
- Dean, Tamara (2010). Network+ Guide to Networks 5th Edition. Boston, MA: Cengage Course Technology. pp. 203–204. ISBN 1-4239-0245-9.
- CompTIA Network+ In depth, Chapter 5 p. 169
- Dean, T. (2010) Network+ Guide to Networks, Fifth Edition
- , Backbone Networks