Identification of backhaul links for termination

A wireless communication network is served by a plurality of network paths between network control nodes and base stations, wherein the network paths each include a plurality of backhaul links. A backhaul link termination system comprises a communication interface and a processing system. The communication interface is configured to receive architecture information that individually associates the backhaul links with the network paths, and to receive communication loading data and cost data for each of the backhaul links. The processing system is configured to process the architecture information, the loading data, and the cost data to identify a set of the backhaul links for termination.

TECHNICAL BACKGROUND

A wireless communication device and its serving base station communicate wirelessly to provide voice, Internet, email, text, video, and other communication services. The serving base station has a backhaul communication link with a communication service provider. When the base station provides a communication service to a wireless communication device, content requested by the device is first sent to the base station over the backhaul link. Once the base station has received the requested data, the base station transmits the data to the wireless communication device.

The communication service provider typically leases the backhaul links from backhaul providers like Local Exchange Carriers (LECs) or coaxial cable companies. Typical backhaul lease terms include a 1, 3, or 5 year pricing plan, monthly recurring costs, and penalties for early termination. As demand for wireless communication service shifts, the communication service provider may desire to remove underutilized backhaul links from the network. However, the service provider must consider the penalties incurred for prematurely terminating a backhaul link lease. In the past, service provider personnel have performed manual calculation steps using complicated tariff documents to determine whether terminating a specific link would result in a lower contractual cost than maintaining it unnecessarily. Unfortunately, these steps are time consuming, requiring manual tracking and tedious decision making points which often result in suboptimal disconnects.

OVERVIEW

A method of operating a backhaul link termination system is described herein, wherein a wireless communication network is served by a plurality of network paths between network control nodes and base stations and wherein the network paths each include a plurality of backhaul links. The method of operating the backhaul link termination system comprises receiving architecture information that individually associates the backhaul links with the network paths, receiving communication loading data and cost data for each of the backhaul links, and processing the architecture information, the loading data, and the cost data to identify a set of the backhaul links for termination.

A wireless communication network is served by a plurality of network paths between network control nodes and base stations, wherein the network paths each include a plurality of backhaul links. A backhaul link termination system comprises a communication interface and a processing system. The communication interface is configured to receive architecture information that individually associates the backhaul links with the network paths, and to receive communication loading data and cost data for each of the backhaul links. The processing system is configured to process the architecture information, the loading data, and the cost data to identify a set of the backhaul links for termination.

A method of operating a backhaul link termination system is described herein, wherein a wireless communication network is served by a plurality of network paths between network control nodes and base stations and wherein the network paths each include a plurality of backhaul links. The method of operating the backhaul link termination system comprises receiving architecture information that individually associates the backhaul links with the network paths, receiving communication loading data and cost data for each of the backhaul links, wherein the loading data comprises an optimal loading level for each of the network paths and an indication of whether each of the backhaul links is overloaded or under loaded based on threshold values, and wherein the cost data comprises a plurality of contract provisions associated with a plurality of contracts for leasing the backhaul links from a plurality of backhaul providers, and processing the architecture information, the loading data, and the cost data to identify a set of the backhaul links for termination by identifying ones of the backhaul links that cost less to terminate than to maintain through a lease time period and by identifying ones of the backhaul links that can be terminated without overloading remaining ones of the backhaul links in the associated network path.

DETAILED DESCRIPTION

The following description and associated drawings teach the best mode of the invention. For the purpose of teaching inventive principles, some conventional aspects of the best mode may be simplified or omitted. The following claims specify the scope of the invention. Some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Thus, those skilled in the art will appreciate variations from the best mode that fall within the scope of the invention. Those skilled in the art will appreciate that the features described below can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific examples described below, but only by the claims and their equivalents.

FIG. 1is a block diagram that illustrates communication environment100. Communication environment100includes wireless communication devices101-104, base stations120and130, network control node140, and communication network150. Communication network150includes backhaul link termination system160. Wireless communication devices101and102communicate with base station120over respective wireless communication links111and112. Likewise, wireless communication devices103and104communicate with base station130over respective wireless communication links113and114. Base station120is in communication with network control node140over network path125. Network path125comprises backhaul links121,122, and123. Likewise, base station130is in communication with network control node140over network path135. Network path135comprises backhaul links131,132, and133. Network control node140communicates with communication network150over communication link141.

FIG. 2is a flow diagram that illustrates an operation of communication environment100. The steps of the operation are indicated below parenthetically. The operation ofFIG. 2may be performed in a wireless communication network served by a plurality of network paths125and135between network control node140and base stations120and130, wherein the network paths125and135each include a plurality of respective backhaul links121-123and131-133. InFIG. 2, backhaul link termination system160receives architecture information that individually associates the backhaul links121-123and131-133with the network paths125and135(201). As shown inFIG. 1, the architecture information individually associates backhaul links121-123with network path125and backhaul links131-133with network path135. Backhaul link termination system160may receive the architecture information in a variety of ways, such as by accessing a database, receiving input from a user, or polling elements on or in communication with the network paths125and135, for example.

In addition to the architecture information, backhaul link termination system160receives communication loading data and cost data for each of the backhaul links121-123and131-133(202). The communication loading data comprises information about the bandwidth utilization on backhaul links121-123and131-133. In some examples, the communication loading data could comprise an indication of whether each of the backhaul links is overloaded or under loaded based on threshold values. The communication loading data could also comprise an optimal loading level or threshold for each of the network paths125and135, or a maximum loading level for each of the backhaul links121-123and131-133.

The cost data comprises a plurality of contract provisions associated with a plurality of contracts for leasing the backhaul links121-123and131-133from a plurality of backhaul providers. A backhaul provider could include, for example, a Local Exchange Carrier (LEC), coaxial cable provider, or fiber optic link provider. In some examples, the cost data comprises financial information and lease terms associated with contracts for the lease of the backhaul links121-123and131-133, such as contractual volume commitments. The cost data could comprise a contractual termination liability for each of the backhaul links121-123and131-133, wherein the contractual termination liability comprises a cost of breaching a lease contract at a specified time. The cost data could also comprise a monthly recurring cost for each of the backhaul links121-123and131-133. In some examples, the cost data could be recalculated dynamically based on contractual stipulations and tariffs input by a user of backhaul link termination system160.

Once backhaul link termination system160receives the above information, backhaul link termination system160processes the architecture information, the loading data, and the cost data to identify a set of the backhaul links121-123and131-133for termination (203). The set of backhaul links121-123and131-133for termination could include, for example, links with low utilization and minimal termination liability. In some examples, backhaul link termination system160identifies ones of the backhaul links121-123and131-133that cost less to terminate than to maintain through a lease time period. In other examples, backhaul link termination system160could favor a particular backhaul provider or backhaul link type when identifying the set of the backhaul links121-123and131-133for termination.

Additionally or alternatively, backhaul link termination system160could identify ones of the backhaul links121-123and131-133that can be terminated without overloading remaining ones of the backhaul links in the associated network path125or135. This identification could be achieved by determining whether the overall loading on the network path125or135would exceed a threshold value if a particular backhaul link121-123or131-133were terminated. The threshold value could be based on an optimal loading level for each of the network paths125and135, which typically ranges from fifty to eighty percent, for example.

In some examples, the loading data comprises a growth factor related to an estimated bandwidth requirement at a future time for each of the backhaul links121-123and131-133. Backhaul link termination system160could process the growth factor to estimate future bandwidth requirements when identifying the set of the backhaul links121-123and131-133for termination. In this manner, a backhaul link121-123and131-133that would otherwise be recommended for termination may be preserved if backhaul link termination system160determines that the bandwidth provided by the link will be needed at the future time based on the growth factor.

Advantageously, backhaul link termination system160can automatically identify an optimal set of backhaul links121-123and131-133for termination without requesting any manual calculations or decisions. In addition, backhaul link termination system160may generate a termination report indicating the identified set of the backhaul links for termination. The termination report could indicate, for each of the backhaul links, a recommendation for termination, a recommendation for non-termination, or a recommendation for termination at a future date. The termination report could also rank the backhaul links121-123and131-133in order of termination liability and loading level. By referring to the termination report, an operator of communication network150can quickly identify the optimal links for termination based on underutilization and the lowest early-termination penalties.

Referring back toFIG. 1, wireless communication devices101-104each comprise any device having wireless communication connectivity with hardware and circuitry programmed to function as a telecommunications device, including Radio Frequency (RF) communication circuitry and an antenna. The RF communication circuitry typically includes an amplifier, filter, modulator, and signal processing circuitry. Wireless communication devices101-104may also include a user interface, memory device, software, processing circuitry, or some other communication components. For example, wireless communication devices101-104could comprise a telephone, transceiver, mobile phone, cellular phone, smartphone, computer, personal digital assistant (PDA), e-book, game console, mobile Internet device, wireless network interface card, media player, or some other wireless communication apparatus—including combinations thereof. Wireless network protocols that may be utilized by wireless communication devices101-104include Code Division Multiple Access (CDMA) 1xRTT, Global System for Mobile communications (GSM), Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Evolution-Data Optimized (EV-DO), EV-DO rev. A, Third Generation Partnership Project Long Term Evolution (3GPP LTE), Worldwide Interoperability for Microwave Access (WiMAX), IEEE 802.11 protocols (Wi-Fi), Internet, telephony, or any other wireless network protocol that facilitates communication between wireless communication devices101-104and base stations120and130.

Base stations120and130comprise RF communication circuitry and an antenna. The RF communication circuitry typically includes an amplifier, filter, RF modulator, and signal processing circuitry. Base stations120and130may also comprise a router, server, memory device, software, processing circuitry, cabling, power supply, network communication interface, structural support, or some other communication apparatus. Base stations120and130could comprise a wireless access node, Internet access node, telephony service node, wireless data access point, or some other wireless communication system—including combinations thereof. Some examples of base stations120and130include a base transceiver station (BTS), base station controller (BSC), radio base station (RBS), Node B, enhanced Node B (eNode B), and others. Wireless network protocols that may be utilized by base stations120and130include CDMA, GSM, UMTS, HSPA, EV-DO, EV-DO rev. A, 3GPP LTE, WiMAX, Wi-Fi, Internet, telephony, or some other communication format—including combinations thereof.

Network control node140comprises equipment to monitor and control the operations of base stations120and130, including coordinating handoffs of wireless communication devices101-104. Network control node140also includes equipment to route communications between base stations120and130and communication network150. In some examples, network control node140could comprise a radio network controller (RNC), base station controller (BSC), mobile switching center (MSC), media gateway controller (MGC), authentication, authorization and accounting (AAA) server, call processing system, access service network gateway (ASN-GW), application server, router, processing system, or some other equipment—including combinations thereof.

Communication network150comprises the core network of a wireless communication provider, and could include routers, gateways, telecommunication switches, servers, processing systems, or other communication equipment and systems for providing communication and data services. Communication network150could comprise wireless communication nodes, telephony switches, Internet routers, network gateways, computer systems, communication links, or some other type of communication equipment—including combinations thereof. Communication network150may also comprise optical networks, asynchronous transfer mode (ATM) networks, packet networks, metropolitan-area networks (MAN), or other network topologies, equipment, or systems—including combinations thereof. Communication network150may be configured to communicate over metallic, wireless, or optical links. Communication network150may be configured to use time-division multiplexing (TDM), Internet Protocol (IP), Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format—including combinations thereof. In some examples, communication network150includes further access nodes and associated equipment for providing communication services to many wireless communication devices across a large geographic region.

Backhaul link termination system160comprises a computer system and communication interface. Backhaul link termination system160may also include other components such as a router, server, data storage system, and power supply. Backhaul link termination system160may reside in a single device or may be distributed across multiple devices. Backhaul link termination system160may be a discrete system or may be integrated within other systems—including other systems within communication environment100. Backhaul link termination system160could comprise a packet gateway, mobile switching center, network gateway system, Internet access node, application server, service node, firewall, or some other communication system—including combinations thereof.

Wireless communication links111-114use the air or space as the transport medium. Wireless communication links111-114may use various protocols, such as CDMA, GSM, UMTS, HSPA, EV-DO, EV-DO rev. A, 3GPP LTE, WiMAX, Wi-Fi, Internet, telephony, or some other communication format—including combinations thereof. Wireless communication links111-114may transfer many different signals sharing the same link. For example, wireless communication links111-114could include multiple signals operating in a single propagation path comprising multiple communication sessions, frequencies, timeslots, transportation ports, logical transportation links, network sockets, IP sockets, packets, or communication directions—including combinations thereof.

Communication links121-123,131-133, and141use metal, air, space, optical fiber such as glass or plastic, or some other material as the transport media—including combinations thereof. Communication links121-123,131-133, and141could use various communication protocols, such as TDM, IP, Ethernet, telephony, optical networking, hybrid fiber coax (HFC), communication signaling, wireless protocols, or some other communication format—including combinations thereof. Communication links121-123,131-133, and141could be direct links or may include intermediate networks, systems, or devices.

Network paths125and135each include a plurality of respective backhaul links121-123and131-133. Each backhaul link121-123on network path125provides a communication link between base station120and network control node140. Likewise, backhaul links131-133on network path135provide separate communication links between base station130and network control node140. In some examples, the total communication loading on network path125or135comprises the sum of the loading on the individual links121-123or131-133for each respective path125or135.

FIG. 3is a block diagram that illustrates communication environment300in an exemplary embodiment. Communication environment300utilizes Universal Mobile Telecommunications System (UMTS) third generation (3G) wireless communication technology. Communication environment300includes wireless communication devices301-304, Node B base stations320and330, Radio Network Controllers (RNCs)340and345, communication network350, and backhaul link termination system360. Wireless communication devices301and302communicate with Node B320over respective wireless communication links311and312. Likewise, wireless communication devices303and304communicate with Node B330over respective wireless communication links313and314. Node B320is in communication with RNC340over communication path325. Communication path325comprises backhaul links321,322, and323. Likewise, Node B330is in communication with RNC345over communication path335. Communication path335comprises backhaul links331,332, and333. RNCs340and345communicate with communication network350over respective communication links341and342. Communication network350includes network database355. Network database355is in communication with backhaul link termination system360over communication link351. Backhaul link termination system360communicates with communication network350over communication link352. While backhaul link termination system360is shown external to communication network350, system360could be included within communication network350or other elements shown in communication environment300. Note that while the exemplary embodiment ofFIG. 3describes a wireless communication environment, the principles discussed herein could equally apply to wired networks.

FIG. 4is a block diagram that illustrates network path325between Node B320and RNC340. The utilization of each of the backhaul links321-323that together form network path325is shown inFIG. 4, along with the total communication loading on network path325. InFIG. 4, the utilization of each of the backhaul links321-323represents the amount of bandwidth being consumed by voice or data transmissions over the links at the present time. Thus, backhaul link321is operating at 25% utilization, backhaul link322has 55% utilization, and backhaul link323has 35% utilization. Assuming each backhaul link321-323provides the same amount of bandwidth, the total loading on network path325is 38% communication loading, as shown inFIG. 4. Since optimal loading levels typically range from 50-80%, network path325is relatively underutilized at 38% loading. It should be noted that although this example assumes each backhaul link321-323has the same capacity, any combination of backhaul links could be included in a network path, regardless of the bandwidth, service provider, or other attributes of the links.

FIG. 5is a block diagram that illustrates network path335between Node B330and RNC345. The utilization of each of the backhaul links331-333that together form network path335is shown inFIG. 5, along with the total communication loading on network path335. As shown, backhaul link331is operating at 85% utilization, backhaul link332has 50% utilization, and backhaul link333has 80% utilization. Assuming each backhaul link331-333provides the same amount of bandwidth, network path335is operating at 72% communication loading, as shown inFIG. 5. Since optimal loading levels typically range from 50-80%, network path335is optimally loaded and may soon approach over-utilization if it experiences further growth in the future.

FIG. 6illustrates termination report601in an exemplary embodiment. Termination report601is generated by backhaul link termination system360and provides a recommendation for each of the backhaul links321-323and331-333of communication environment300. Termination report601is presented in tabular form with each column showing a different metric related to the backhaul links321-323and331-333. Note that termination report601is provided as an illustrative example and thus other termination reports could include greater or fewer columns of related information or be presented in an entirely different format.

The first row of termination report601indicates each of the backhaul links in the ‘LINK’ column, followed by the ‘PATH’, ‘BS’, ‘VENDOR’, ‘REGION’, ‘MARKET’, ‘LINK UTILIZATION’, ‘CONTRACT START DATE’, ‘PRICING PLAN’, and ‘DISCONNECT APPROVAL STATUS’. The ‘PATH’ and ‘BS’ columns indicate the network path325or335and the Node B base station320or330associated with each of the respective backhaul links321-323and331-333. The ‘VENDOR’ column lists the various backhaul providers for each of the backhaul links321-323and331-333, while the ‘REGION’ and ‘MARKET’ columns indicate the general and specific geographical areas where the backhaul links321-323and331-333are in service. The ‘LINK UTILIZATION’ column designates the loading level on each of the backhaul links321-323and331-333expressed as a percentage of the total available bandwidth on each of the links. The ‘CONTRACT START DATE’ and “PRICING PLAN’ columns relate to the lease terms associated with each of the backhaul links321-323and331-333, where the ‘PRICING PLAN’ indicates the duration of the lease contract. Finally, ‘DISCONNECT RECOMMENDATION’ identifies whether disconnection of a particular backhaul link321-323and331-333is approved, denied, or approved at a future date. In some examples, the approval, denial, and future approval indications are colored coded green, red, and yellow for easier identification, and may be sorted by recommendation type.

As shown in termination report601, backhaul link termination system360recommends backhaul link321for immediate termination, as indicated by the ‘DISCONNECT APPROVED’ status for link321, and recommends backhaul link323for termination on Dec. 8, 2009. Backhaul link termination system360could arrive at this recommendation by processing the architecture information, loading data, and cost data received from network database355, which could be entered into database355by communication service provider personnel as new backhaul links are installed or leased. In some examples, the communication service provider personnel can review the architecture information, loading data, and cost data. Upon review of the data, the personnel are presented with an option to approve, reject, or mark the data for further analysis or data collection, and may provide a reason code to explain their selection. Rejected backhaul links or network paths are triaged based on the reason code provided, while accepted network paths are processed by backhaul link termination system360to determine a recommended action.

To determine the recommended action, backhaul link termination system360first determines which network paths325and335are operating below the optimal loading level according to threshold values. In one example, the optimal loading level threshold for each network path325and335is provided in the loading data, and backhaul link termination system360calculates the total loading on each network path325and335from the architecture information and the loading data. To perform this calculation, backhaul link termination system360first determines from the architecture information the specific backhaul links321-323and331-333comprising the network paths325and335, respectively. Once the backhaul links321-323and331-333are associated with their respective network paths325and335, backhaul link termination system360calculates the loading on the entire network path325and335based on the link utilization of each of the links321-323and331-333on each path325and335as provided in the loading data. Alternatively, the total loading level on each network path325and335may be predetermined and provided in the loading data along with the optimal loading level for each network path325and335.

When the optimal loading level and the total loading for each network path325and335are known, backhaul link termination system360determines the network paths325and335operating below the optimal loading level by comparing the optimal loading level to the total loading on each network path325and335. For the purpose of clarity, the optimal loading level for each network path325and335in this example is 80%, although the optimal levels for each path could be different values or ranges. As shown inFIGS. 4 and 5, network path325is operating at a suboptimal 38% loading, while the 72% loading on network path335is nearing the optimal loading level of 80%. Thus, links321-323of network path325are identified as appropriate for a disconnect approval recommendation based on underutilization, provided that the contractual volume commitment of at least one of the backhaul links321-323allows for a financially viable early termination.

The contractual volume commitment for each link321-323and331-333in network paths325and335is based on monthly recurring cost and termination liability, where the termination liability is defined as the cost to immediately terminate a backhaul link. Backhaul link termination system360determines the contractual volume commitment for each backhaul link321-323and331-333by combining the monthly recurring cost and the termination liability for all links in each network path325and335and comparing the two-year recurring cost to the one-time disconnect cost. The backhaul links321-323and331-333with the lowest financial impact are identified for termination. If all financial impacts are the same, then the most recently installed link is identified for termination to avoid additional labor costs in rearranging the entire network path. Backhaul link termination system360then generates termination report601and indicates which of the backhaul links321-323and331-333are recommended for termination.

As shown in termination report601, backhaul links321and323are recommended for termination, as indicated by ‘DISCONNECT APPROVED’ disconnect recommendation. In particular, backhaul link321is recommended for immediate termination, likely because link321has the lowest utilization at 25% and the contractual volume commitment of link321results in the lowest financial impact for immediate termination. In addition, shifting the 25% utilization of link321onto the remaining links322and323results in 58% loading on network path325, lower than the 80% optimal level while still allowing room for future growth.

However, backhaul link323is not approved for immediate termination, but is instead recommended for termination at a future date of Dec. 8, 2009. Backhaul link termination system360provides a recommended termination date at a future time when immediate termination would result in a high financial impact or excessive communication loading shifted to remaining backhaul links in a network path. For example, in termination report601, link323is not recommended for immediate termination along with link321because network path325would then solely comprise backhaul link322and be overloaded at 115% utilization. However, backhaul link termination system360recommends disconnection of link323on Dec. 8, 2009, one year and eight months after the contract start date of Apr. 8, 2008. This may be due to certain contract provisions that reduce the financial impact of termination on that date, or may be due to other considerations, such as a growth factor.

The growth factor could comprise a projected reduction in communication loading on link323or the associated network path325, or a projected increase in the bandwidth available on network path325. For example, backhaul link termination system360may detect a trend of declining link utilization for link323or across the total loading of network path325. In another example, backhaul link termination system360may process the architecture information to determine that new or planned backhaul link installations in the proximity of backhaul link323are projected to shift a large amount of the communication loading away from link323and path325. In another example, new or planned installations of backhaul links on network path325will increase the available bandwidth on the path, allowing for earlier termination of older links321-323if their lease terms permit such action with low financial impact.

Regarding network path335, all backhaul links331-333on path335are not recommended for termination at the present time or in the future, as indicated by the ‘DISCONNECT DENIED’ disconnect recommendation. Based on an 80% optimal loading level, backhaul link331is overloaded at 85%, backhaul link332is 50% loaded, and backhaul link333is optimally loaded at 80%. However, disconnecting any of these links331-333would result in overloading the entire network path335. In addition, the contractual volume commitment for each of the backhaul links331-333in path335likely has a large financial impact for early termination due to the contract start dates and pricing plan. The contract start date for each of the links331-333of network path335indicates that the leases were recently executed, resulting in a large remainder of the contract term requiring payment through the lease time period under the 5 year pricing plan. Thus, due to the high communication loading on links331-333and the costly financial impact for early termination of leases with substantial remaining time under the pricing plan, backhaul link termination system360has denied termination of links331-333in the ‘DISCONNECT RECOMMENDATION’ column of termination report601.

In some examples, backhaul link disconnect recommendations are reviewed based on an automated list of approval and denial templates for a vendor, region, or market. The automated list of approval and denial templates is input and maintained by communication service provider personnel. However, the automation is based on prior approval or denial in cases where no contractual volume commitment exists or the loading level for a particular LEC or network path is already optimal or not in question. Backhaul links or network paths with no prior approval or denial history or that are marked for manual review are presented to service provider personnel for manual approval/denial from a contractual standpoint. In some examples, an automated approval/denial recommendation is marked for manual review after a threshold period of time has elapsed.

FIG. 7is a block diagram that illustrates backhaul link termination system700. Backhaul link termination system700provides an example of backhaul link termination system160, although system160may use alternative configurations. Backhaul link termination system700comprises communication interface701and processing system703. Processing system703is linked to communication interface701. Processing system703includes processing circuitry705and memory device706that stores operating software707.

Communication interface701comprises components that communicate over communication links, such as network cards, ports, RF transceivers, processing circuitry and software, or some other communication components. Communication interface701may be configured to communicate over metallic, wireless, or optical links. Communication interface701may be configured to use TDM, IP, Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format—including combinations thereof. Communication interface701is capable of receiving architecture information that individually associates a plurality of backhaul links with a plurality of network paths, and capable of receiving communication loading data and cost data for each of the backhaul links.

Processing circuitry705comprises microprocessor and other circuitry that retrieves and executes operating software707from memory device706. Memory device706comprises a disk drive, flash drive, data storage circuitry, or some other memory apparatus. Operating software707comprises computer programs, firmware, or some other form of machine-readable processing instructions. Operating software707may include an operating system, utilities, drivers, network interfaces, applications, or some other type of software. When executed by circuitry705, operating software707directs processing system703to operate backhaul link termination system700as described herein. In particular, operating software707directs processing system703to process architecture information, loading data, and cost data to identify a set of backhaul links for termination.