US20060215667A1 - Communication nodes and methods using small routers to communicate over a backhaul facility - Google Patents
Communication nodes and methods using small routers to communicate over a backhaul facility Download PDFInfo
- Publication number
- US20060215667A1 US20060215667A1 US11/090,114 US9011405A US2006215667A1 US 20060215667 A1 US20060215667 A1 US 20060215667A1 US 9011405 A US9011405 A US 9011405A US 2006215667 A1 US2006215667 A1 US 2006215667A1
- Authority
- US
- United States
- Prior art keywords
- traffic
- communication node
- routers
- base stations
- small
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
Definitions
- the invention is related to the field of communication networks, and in particular, to communication nodes and methods of a wireless network using a plurality of small routers to communicate over a backhaul facility.
- Wireless networks are comprised of a plurality of base stations, where each base station provides a service area termed a “cell”. Mobile phones in the service area of a base station are able to communicate with the base station to receive the wireless service.
- the base stations transmit voice, data, and signaling traffic from the mobile devices over a backhaul facility to a communication node, such as a Mobile Switching Center (MSC).
- MSC Mobile Switching Center
- the backhaul facility frequently comprises T1 lines from the base stations to the MSC.
- Wireless service providers often lease the T1 lines from telephone companies or cable companies. The cost of leasing the T1 lines constitutes a substantial portion of the operating budget of the service providers. Because of the cost of T1 lines, the backhaul facility is generally not configured redundantly for reliability.
- FIG. 1 illustrates a wireless network 100 using Frame Relay as the transport protocol over the backhaul facility.
- Wireless network 100 includes a plurality of base stations 111 - 113 connected to an MSC 120 over a backhaul facility 130 . Although three base stations 111 - 113 are shown, those skilled in the art understand that MSC 120 can serve many more base stations.
- Backhaul facility 130 comprises a plurality of T1 lines 131 - 133 .
- Wireless network 100 uses Frame Relay (FR) protocol for transporting traffic over the T1 lines 131 - 133 .
- Each base station 111 - 113 includes a transmission interface 115 - 117 for terminating the T1 lines 131 - 133 .
- MSC 120 includes a switch, such as a 5ESS switch, for terminating the T1 lines 131 - 133 .
- switch 122 For each incoming T1 line, switch 122 duplicates the incoming T1 line into redundant lines for backup. One of the redundant lines is in active mode while the other line is in standby mode. The redundant lines in this architecture add reliability to wireless network 100 .
- FIG. 2 illustrates a wireless network 200 using IP as the transport protocol over the backhaul facility.
- Wireless network 200 includes a plurality of base stations 211 - 213 connected to an MSC 220 over a backhaul facility 230 .
- Backhaul facility 230 comprises a plurality of T1 lines 231 - 233 , a Digital Connect (DACS) 234 , and a plurality of DS-3 lines 236 - 237 .
- Each base station 211 - 213 includes a transmission interface 215 - 217 for terminating the T1 lines 231 - 233 .
- MSC 220 includes two large routers 222 - 223 for terminating the DS-3 lines 236 - 237 .
- the T1 lines 231 - 233 connect between DACS 234 and the transmission interfaces 215 - 217 in base stations 211 - 213 .
- the DS-3 lines 236 - 237 connect between DACS 234 and large routers 222 - 223 .
- Wireless network 100 uses IP for transmitting traffic over the T1 lines 131 - 133 and the DS-3 lines 236 - 237 .
- a large router is defined as a router that is to handle more than 10% of the traffic for MSC 220 as configured.
- the percentage of traffic to be handled by a router is based on the configuration of MSC 220 .
- FIG. 2 there are two large routers 222 - 223 , and each large router 222 - 223 is assumed to handle 50% of the traffic for MSC 220 as configured (assuming reasonable load balancing between the large routers 222 - 223 ).
- Actual traffic handled by each of large routers 222 - 223 may be below the 10% level in operation, such as late at night or other low-traffic times.
- the large routers 222 - 223 used in the MSC 220 do not duplicate the incoming DS-3 lines 236 - 237 into redundant lines for backup, as is done in switch 122 in FIG. 1 for Frame Relay. Therefore, if one of the large routers 222 - 223 fails, there may be a 50% traffic loss in MSC 220 .
- a 50% traffic loss unfortunately exceeds the threshold (10%) of outage counting rules set by the TL 9000 and/or the GR 1929. For instance, TL 9000 establishes a common set of quality system requirements for suppliers of telecommunication systems, hardware, software, and services.
- the TL 9000 requirements include a minimum set of performance metrics and indicators to measure progress and evaluate results of quality system implementation.
- the TL 9000 counting rules provide that suppliers of telecommunication systems, hardware, software and services have a traffic loss no greater than 10% traffic loss. Therefore, a 50% traffic loss, as could happen in wireless network 200 , would be counted as an outage.
- the communication node includes at least ten small routers.
- the communication node is implemented or is to be implemented in a wireless network that includes a plurality of base stations and a backhaul facility connecting the base stations to the small routers in the communication node.
- the base stations provide wireless service to mobile devices and transport traffic over the backhaul facility to the communication node.
- the backhaul facility transports the traffic between the base stations and the small routers of the communication node using IP.
- the small routers are configured to receive and handle the traffic.
- a small router in the communication node is defined as a router that is to handle 10% or less of the traffic for the communication node as configured.
- the percentage to be handled by a router is based on the configuration of the communication node. For instance, if there are ten small routers in the communication node, then each of the ten small routers is assumed to handle about 10% of the traffic as configured (assuming reasonable load balancing of the traffic across the ten small routers). If there are twelve small routers in the communication node, then each of the twelve small routers is assumed to handle about 8% of the traffic. Actual traffic in any of the small routers may exceed the 10% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention.
- the use of at least ten small routers in the communication node advantageously mitigates the reliability problems of using large routers in the communication node. If one of the small routers were to fail, then the communication node is assumed to suffer a 10% or less traffic loss as configured. The 10% or less traffic loss satisfies the set of performance metrics provided under the TL 9000 counting rules for suppliers of telecommunication systems, hardware, software, and services, as configured.
- the invention may include other exemplary embodiments described below.
- FIG. 1 illustrates a wireless network using Frame Relay as the transport protocol over a backhaul facility in the prior art.
- FIG. 2 illustrates a wireless network using Internet Protocol (IP) as the transport protocol over a backhaul facility in the prior art.
- IP Internet Protocol
- FIG. 3 illustrates a wireless network using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.
- FIG. 4 illustrates another wireless network using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.
- FIG. 5 illustrates interleaving for a small router in a wireless network in an exemplary embodiment of the invention.
- FIGS. 3-5 and the following description depict specific exemplary embodiments of the invention to teach those skilled in the art how to make and use the best mode of the invention.
- some conventional aspects of the invention have been simplified or omitted.
- Those skilled in the art will appreciate variations from these embodiments 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 embodiments described below, but only by the claims and their equivalents.
- FIG. 3 illustrates a wireless network 300 using Internet Protocol (IP) as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.
- Wireless network 300 includes a plurality of base stations 310 - 319 , a communication node 320 , and a backhaul facility 330 connecting base stations 310 - 319 to communication node 320 .
- Communication node 320 includes at least ten small routers 341 - 350 . Each small router 341 - 350 connects to backhaul facility 330 and is configured to receive traffic from and transmit traffic to backhaul facility 330 .
- Wireless network 300 may include other networks, systems, or devices not shown in FIG. 3 .
- a small router 341 - 350 is defined as a router that is to handle 10% or less of the traffic for communication node 320 as configured.
- To handle traffic means to receive, route, or otherwise process traffic.
- the percentage to be handled by a router is based on the configuration of communication node 320 . For instance, if there are ten small routers in communication node 320 , then each of the ten small routers is assumed to handle about 10% of the traffic as configured (assuming reasonable load balancing of the traffic across the ten small routers). If there are twelve small routers in communication node 320 , then each of the twelve small routers is assumed to handle about 8% of the traffic.
- Actual traffic in any of small routers 341 - 350 may exceed the 10% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention.
- the benchmark is if each small router 341 - 350 is to handle 10% or less of the traffic as configured.
- Base stations 310 - 319 comprise any wireless towers, controllers, and/or transmission interfaces that provide wireless service to mobile devices and transport traffic over a backhaul facility.
- Backhaul facility 330 comprises any media, paths, or facility that transports traffic between base stations 310 - 319 and small routers 341 - 350 .
- Backhaul facility 330 may comprise T1 lines, DS-3 lines, or another other electrical or optical lines.
- Backhaul facility 330 transports traffic using Internet Protocol (IP) in this embodiment, but other similar protocols may be used in other embodiments.
- IP Internet Protocol
- Communication node 320 comprises any network node of a telecommunications system that receives traffic from or transmits traffic to base stations 310 - 319 of wireless network 300 .
- One example of communication node 320 comprises a Mobile Switching Center (MSC).
- MSC Mobile Switching Center
- the use of at least ten small routers 341 - 350 advantageously mitigates the reliability problems of using large routers in the communication node. If one of the small routers 341 - 350 were to fail, then communication node 320 is assumed to suffer a 10% or less traffic loss. The 10% or less traffic loss satisfies the set of performance metrics provided under the TL 9000 counting rules for suppliers of telecommunication systems, hardware, software, and services.
- base stations 310 - 319 When in actual operation, base stations 310 - 319 receive voice or data calls from mobile devices (not shown). Each base station 310 - 319 transmits traffic (comprising voice, data, or signaling) over backhaul facility 330 to communication node 320 . Each small router 341 - 350 handles traffic received from backhaul facility 330 . As previously stated, each small router 341 - 350 is assumed to handle 10% or less of the traffic for communication node 320 (assuming reasonable load balancing of the traffic across small routers 341 - 350 ). If one of the small routers 341 - 350 does fail in actual operation, then communication node 320 will probably suffer a 10% or less traffic loss (assuming reasonable load balancing among the small routers 341 - 350 ). Thus, communication node will probably satisfy the set of performance metrics provided under the TL 9000 counting rules in actual operation.
- a failure of one of the small routers 341 - 350 is assumed to result in a less than 10% traffic loss in communication node 320 as configured.
- a failure of one of the small routers 341 - 350 probably results in a less than 10% traffic loss in communication node 320 in actual operation.
- Suppliers of communication node 320 and other similar telecommunication equipment can then substantially guarantee a maximum traffic outage for communication node 320 to their customers (as configured and in actual operation).
- FIG. 4 illustrates another wireless network 400 using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.
- Wireless network 400 includes geographic regions 402 - 404 of base stations (B.S) 405 - 407 , an MSC 420 , and a backhaul facility 430 connecting the base stations 405 - 407 to MSC 420 .
- MSC 420 includes twelve small edge routers 441 - 452 .
- Backhaul facility 430 includes a plurality of T1 lines 431 , a Digital Connect (DACS) 434 , and a plurality of DS-3 lines 436 .
- the T1 lines 431 connect between DACS 434 and base stations 405 - 407 .
- DACS Digital Connect
- the DS-3 lines 436 connect between DACS 434 and small edge routers 441 - 452 .
- Wireless network 400 uses IP for transmitting traffic over the T1 lines 431 and the DS-3 lines 436 .
- Wireless network 400 may include other networks, systems, or devices not shown in FIG. 4 .
- Geographic region 402 includes a plurality of base stations 405 .
- Geographic region 403 includes a plurality of base stations 406 .
- Geographic region 404 includes a plurality of base stations 407 .
- Each of base stations 405 - 407 backhauls traffic to MSC 420 over backhaul facility 430 .
- small edge routers 441 - 452 are defined as routers that are to handle 10% or less of the traffic for MSC 420 as configured. The percentage to be handled by each small edge router 441 - 452 is based on the configuration of MSC 420 . MSC 420 has twelve small edge routers 441 - 452 , so each of the twelve small routers is assumed to handle about 8% of the traffic for MSC 420 as configured. Actual traffic in any of small edge routers 441 - 452 may exceed the 8% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention.
- base stations 405 - 407 When in operation, base stations 405 - 407 receive voice or data calls from mobile devices (not shown). Each base station 405 - 407 transmits traffic (comprising voice, data, or signaling) over backhaul facility 430 to MSC 420 . Each small edge router 441 - 452 receives traffic from backhaul facility 430 . Each small edge router 441 - 452 will probably handle 8% or less of the traffic for MSC 420 (assuming reasonable load balancing of the traffic across small edge routers 441 - 452 )
- FIG. 5 illustrates interleaving for small edge router 441 in wireless network 400 in an exemplary embodiment of the invention.
- Small edge router 441 is the only router shown just for illustration. Interleaving refers to spreading out the base stations handled by small edge router 441 among multiple geographic regions and not concentrating the base stations in a geographic region.
- geographic region 402 includes base stations (B.S.) 502 - 503
- geographic region 403 includes base stations 504 - 505
- geographic region 404 includes base stations 506 - 507 .
- Wireless network 400 is configured so that small edge router 441 handles traffic from base stations 502 - 507 . Small edge router 441 may handle traffic from other base stations (not shown) in any of geographic regions 402 - 404 , or other geographic regions (not shown).
- wireless network 400 is configured so that the base stations 502 - 507 handled by small edge router 441 are interleaved among the geographic regions 402 - 404 . Interleaving adds reliability to wireless network 400 . If small edge router 441 were to fail, base stations 502 - 503 in geographic region 402 would be affected, base stations 504 - 505 in geographic region 403 would be affected, and base stations 506 - 507 in geographic region 404 would be affected.
- small edge router 441 fails and its corresponding base stations 502 - 507 cannot provide service, neighboring base stations may provide service to some of the mobile devices in the service areas of base stations 502 - 507 .
- the service areas of adjacent base stations commonly overlap.
- a mobile device often communicates with two or more base stations depending in the location of the mobile device. Therefore, if one of the base stations is unable to provide service to the mobile device, the mobile device may still receive service from another adjacent base station.
- Wireless network 400 in FIG. 5 is configured so that base stations 502 - 507 handled by small edge router 441 are not adjacent to one another.
- Adjacent in this embodiment means that the services areas of two base stations are touching, overlapping, or serving the same mobile device.
- base stations 502 and 503 are not adjacent to one another.
- base stations 504 and 505 are not adjacent to one another.
- base stations 506 and 507 are not adjacent to one another. Separating the base stations 502 - 507 handled by small edge router 441 adds another level of reliability.
- any of base stations 502 - 507 can be adjacent to one another, but separating the base stations 502 - 507 adds reliability.
- each small edge router 441 - 452 is shown in FIG. 4 , the number of small edge routers depends on desired implementations. The use of twelve small edge routers assumes that each router will handle about 8% of the traffic as configured. In operation, a small buffer (2%) is also created so that each small edge router stays under the 10% level in actual operation. The use of twenty small edge routers would assume that each router will handle about 5% of the traffic as configured. In operation, a 5% buffer is created so that each small edge router stays under the 10% level in actual operation. Network designers need to balance the desire to create a large enough buffer to stay under the 10% level in actual operation versus the cost of adding more small edge routers.
- the 10% level was also assumed based on the industry standards, such as TL 9000.
- the customers buying the MSCs may also define a traffic loss threshold other than the 10% industry standard.
- the number of small edge routers in the MSC may be less than ten.
- the number of small edge routers depends on the threshold, so that each of the small edge routers is to handle the defined threshold or less of the traffic for the MSC as configured.
- the threshold to be handled by each small edge router is based on the configuration of the MSC. For instance, if the threshold is defined as a 12% or less traffic loss, then the MSC may include eight small edge routers.
Abstract
Description
- 1. Field of the Invention
- The invention is related to the field of communication networks, and in particular, to communication nodes and methods of a wireless network using a plurality of small routers to communicate over a backhaul facility.
- 2. Statement of the Problem
- Wireless networks are comprised of a plurality of base stations, where each base station provides a service area termed a “cell”. Mobile phones in the service area of a base station are able to communicate with the base station to receive the wireless service. The base stations transmit voice, data, and signaling traffic from the mobile devices over a backhaul facility to a communication node, such as a Mobile Switching Center (MSC). The backhaul facility frequently comprises T1 lines from the base stations to the MSC. Wireless service providers often lease the T1 lines from telephone companies or cable companies. The cost of leasing the T1 lines constitutes a substantial portion of the operating budget of the service providers. Because of the cost of T1 lines, the backhaul facility is generally not configured redundantly for reliability.
- Many wireless networks use Frame Relay protocol as the transport protocol over the backhaul facility.
FIG. 1 illustrates awireless network 100 using Frame Relay as the transport protocol over the backhaul facility.Wireless network 100 includes a plurality of base stations 111-113 connected to an MSC 120 over abackhaul facility 130. Although three base stations 111-113 are shown, those skilled in the art understand that MSC 120 can serve many more base stations.Backhaul facility 130 comprises a plurality of T1 lines 131-133.Wireless network 100 uses Frame Relay (FR) protocol for transporting traffic over the T1 lines 131-133. Each base station 111-113 includes a transmission interface 115-117 for terminating the T1 lines 131-133. MSC 120 includes a switch, such as a 5ESS switch, for terminating the T1 lines 131-133. - For each incoming T1 line, switch 122 duplicates the incoming T1 line into redundant lines for backup. One of the redundant lines is in active mode while the other line is in standby mode. The redundant lines in this architecture add reliability to
wireless network 100. - Internet Protocol (IP) has been suggested as a transport protocol over the backhaul facility.
FIG. 2 illustrates awireless network 200 using IP as the transport protocol over the backhaul facility.Wireless network 200 includes a plurality of base stations 211-213 connected to an MSC 220 over abackhaul facility 230.Backhaul facility 230 comprises a plurality of T1 lines 231-233, a Digital Connect (DACS) 234, and a plurality of DS-3 lines 236-237. Each base station 211-213 includes a transmission interface 215-217 for terminating the T1 lines 231-233. MSC 220 includes two large routers 222-223 for terminating the DS-3 lines 236-237. The T1 lines 231-233 connect between DACS 234 and the transmission interfaces 215-217 in base stations 211-213. The DS-3 lines 236-237 connect between DACS 234 and large routers 222-223.Wireless network 100 uses IP for transmitting traffic over the T1 lines 131-133 and the DS-3 lines 236-237. - A large router is defined as a router that is to handle more than 10% of the traffic for MSC 220 as configured. The percentage of traffic to be handled by a router is based on the configuration of MSC 220. In
FIG. 2 , there are two large routers 222-223, and each large router 222-223 is assumed to handle 50% of the traffic for MSC 220 as configured (assuming reasonable load balancing between the large routers 222-223). Actual traffic handled by each of large routers 222-223 may be below the 10% level in operation, such as late at night or other low-traffic times. - One problem with the architecture for using IP over the
backhaul facility 230 shown inFIG. 2 is reliability. The large routers 222-223 used in the MSC 220 do not duplicate the incoming DS-3 lines 236-237 into redundant lines for backup, as is done inswitch 122 inFIG. 1 for Frame Relay. Therefore, if one of the large routers 222-223 fails, there may be a 50% traffic loss in MSC 220. A 50% traffic loss unfortunately exceeds the threshold (10%) of outage counting rules set by the TL 9000 and/or the GR 1929. For instance, TL 9000 establishes a common set of quality system requirements for suppliers of telecommunication systems, hardware, software, and services. The TL 9000 requirements include a minimum set of performance metrics and indicators to measure progress and evaluate results of quality system implementation. The TL 9000 counting rules provide that suppliers of telecommunication systems, hardware, software and services have a traffic loss no greater than 10% traffic loss. Therefore, a 50% traffic loss, as could happen inwireless network 200, would be counted as an outage. - The invention solves the above and other related problems by configuring a communication node, such as an MSC, with a plurality of small routers instead of large routers to handle IP traffic over a backhaul facility. According to the invention, the communication node includes at least ten small routers. The communication node is implemented or is to be implemented in a wireless network that includes a plurality of base stations and a backhaul facility connecting the base stations to the small routers in the communication node. The base stations provide wireless service to mobile devices and transport traffic over the backhaul facility to the communication node. The backhaul facility transports the traffic between the base stations and the small routers of the communication node using IP. The small routers are configured to receive and handle the traffic.
- A small router in the communication node is defined as a router that is to handle 10% or less of the traffic for the communication node as configured. The percentage to be handled by a router is based on the configuration of the communication node. For instance, if there are ten small routers in the communication node, then each of the ten small routers is assumed to handle about 10% of the traffic as configured (assuming reasonable load balancing of the traffic across the ten small routers). If there are twelve small routers in the communication node, then each of the twelve small routers is assumed to handle about 8% of the traffic. Actual traffic in any of the small routers may exceed the 10% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention.
- The use of at least ten small routers in the communication node advantageously mitigates the reliability problems of using large routers in the communication node. If one of the small routers were to fail, then the communication node is assumed to suffer a 10% or less traffic loss as configured. The 10% or less traffic loss satisfies the set of performance metrics provided under the TL 9000 counting rules for suppliers of telecommunication systems, hardware, software, and services, as configured.
- In actual operation, if one of the small routers does fail, then the communication node will probably suffer a 10% or less traffic loss (assuming reasonable load balancing among the small routers). Thus, communication node will probably satisfy the set of performance metrics provided under the TL 9000 requirements in actual operation.
- The invention may include other exemplary embodiments described below.
- The same reference number represents the same element on all drawings.
-
FIG. 1 illustrates a wireless network using Frame Relay as the transport protocol over a backhaul facility in the prior art. -
FIG. 2 illustrates a wireless network using Internet Protocol (IP) as the transport protocol over a backhaul facility in the prior art. -
FIG. 3 illustrates a wireless network using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention. -
FIG. 4 illustrates another wireless network using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention. -
FIG. 5 illustrates interleaving for a small router in a wireless network in an exemplary embodiment of the invention. -
FIGS. 3-5 and the following description depict specific exemplary embodiments of the invention to teach those skilled in the art how to make and use the best mode of the invention. For the purpose of teaching inventive principles, some conventional aspects of the invention have been simplified or omitted. Those skilled in the art will appreciate variations from these embodiments 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 embodiments described below, but only by the claims and their equivalents. -
FIG. 3 illustrates awireless network 300 using Internet Protocol (IP) as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.Wireless network 300 includes a plurality of base stations 310-319, acommunication node 320, and abackhaul facility 330 connecting base stations 310-319 tocommunication node 320.Communication node 320 includes at least ten small routers 341-350. Each small router 341-350 connects tobackhaul facility 330 and is configured to receive traffic from and transmit traffic tobackhaul facility 330.Wireless network 300 may include other networks, systems, or devices not shown inFIG. 3 . - A small router 341-350 is defined as a router that is to handle 10% or less of the traffic for
communication node 320 as configured. To handle traffic means to receive, route, or otherwise process traffic. The percentage to be handled by a router is based on the configuration ofcommunication node 320. For instance, if there are ten small routers incommunication node 320, then each of the ten small routers is assumed to handle about 10% of the traffic as configured (assuming reasonable load balancing of the traffic across the ten small routers). If there are twelve small routers incommunication node 320, then each of the twelve small routers is assumed to handle about 8% of the traffic. Actual traffic in any of small routers 341-350 may exceed the 10% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention. The benchmark is if each small router 341-350 is to handle 10% or less of the traffic as configured. - Base stations 310-319 comprise any wireless towers, controllers, and/or transmission interfaces that provide wireless service to mobile devices and transport traffic over a backhaul facility.
Backhaul facility 330 comprises any media, paths, or facility that transports traffic between base stations 310-319 and small routers 341-350.Backhaul facility 330 may comprise T1 lines, DS-3 lines, or another other electrical or optical lines.Backhaul facility 330 transports traffic using Internet Protocol (IP) in this embodiment, but other similar protocols may be used in other embodiments.Communication node 320 comprises any network node of a telecommunications system that receives traffic from or transmits traffic to base stations 310-319 ofwireless network 300. One example ofcommunication node 320 comprises a Mobile Switching Center (MSC). - With
communication node 320 as configured, the use of at least ten small routers 341-350 advantageously mitigates the reliability problems of using large routers in the communication node. If one of the small routers 341-350 were to fail, thencommunication node 320 is assumed to suffer a 10% or less traffic loss. The 10% or less traffic loss satisfies the set of performance metrics provided under the TL 9000 counting rules for suppliers of telecommunication systems, hardware, software, and services. - When in actual operation, base stations 310-319 receive voice or data calls from mobile devices (not shown). Each base station 310-319 transmits traffic (comprising voice, data, or signaling) over
backhaul facility 330 tocommunication node 320. Each small router 341-350 handles traffic received frombackhaul facility 330. As previously stated, each small router 341-350 is assumed to handle 10% or less of the traffic for communication node 320 (assuming reasonable load balancing of the traffic across small routers 341-350). If one of the small routers 341-350 does fail in actual operation, thencommunication node 320 will probably suffer a 10% or less traffic loss (assuming reasonable load balancing among the small routers 341-350). Thus, communication node will probably satisfy the set of performance metrics provided under the TL 9000 counting rules in actual operation. - Therefore, based on the number of small routers 341-350 in
communication node 320, a failure of one of the small routers 341-350 is assumed to result in a less than 10% traffic loss incommunication node 320 as configured. Similarly, a failure of one of the small routers 341-350 probably results in a less than 10% traffic loss incommunication node 320 in actual operation. Suppliers ofcommunication node 320 and other similar telecommunication equipment can then substantially guarantee a maximum traffic outage forcommunication node 320 to their customers (as configured and in actual operation). -
FIG. 4 illustrates anotherwireless network 400 using IP as the transport protocol over a backhaul facility in an exemplary embodiment of the invention.Wireless network 400 includes geographic regions 402-404 of base stations (B.S) 405-407, anMSC 420, and abackhaul facility 430 connecting the base stations 405-407 toMSC 420.MSC 420 includes twelve small edge routers 441-452.Backhaul facility 430 includes a plurality ofT1 lines 431, a Digital Connect (DACS) 434, and a plurality of DS-3lines 436. The T1 lines 431 connect betweenDACS 434 and base stations 405-407. The DS-3lines 436 connect betweenDACS 434 and small edge routers 441-452.Wireless network 400 uses IP for transmitting traffic over theT1 lines 431 and the DS-3lines 436.Wireless network 400 may include other networks, systems, or devices not shown inFIG. 4 . -
Geographic region 402 includes a plurality ofbase stations 405.Geographic region 403 includes a plurality of base stations 406.Geographic region 404 includes a plurality ofbase stations 407. Each of base stations 405-407 backhauls traffic toMSC 420 overbackhaul facility 430. - Again, small edge routers 441-452 are defined as routers that are to handle 10% or less of the traffic for
MSC 420 as configured. The percentage to be handled by each small edge router 441-452 is based on the configuration ofMSC 420.MSC 420 has twelve small edge routers 441-452, so each of the twelve small routers is assumed to handle about 8% of the traffic forMSC 420 as configured. Actual traffic in any of small edge routers 441-452 may exceed the 8% level in operation, such as with bursts of traffic during high-traffic times, which falls within the scope of the invention. - When in operation, base stations 405-407 receive voice or data calls from mobile devices (not shown). Each base station 405-407 transmits traffic (comprising voice, data, or signaling) over
backhaul facility 430 toMSC 420. Each small edge router 441-452 receives traffic frombackhaul facility 430. Each small edge router 441-452 will probably handle 8% or less of the traffic for MSC 420 (assuming reasonable load balancing of the traffic across small edge routers 441-452) - Further reliability is added in
wireless network 400 by interleaving the base stations handled by each small edge router 441-452 among the geographic regions 402-404 and other geographic regions not shown.FIG. 5 illustrates interleaving forsmall edge router 441 inwireless network 400 in an exemplary embodiment of the invention.Small edge router 441 is the only router shown just for illustration. Interleaving refers to spreading out the base stations handled bysmall edge router 441 among multiple geographic regions and not concentrating the base stations in a geographic region. InFIG. 5 ,geographic region 402 includes base stations (B.S.) 502-503,geographic region 403 includes base stations 504-505, andgeographic region 404 includes base stations 506-507. Different reference numbers are used for base stations 502-507 inFIG. 5 as compared toFIG. 4 to more clearly describe how interleaving works. Although only two base stations 502-503 are shown ingeographic region 402 for example, those skilled in the art understand thatgeographic region 402 includes many other base stations (not shown) to substantially provide wireless service togeographic region 402. Some or all of the other base stations would be handled by the other small edge routers in MSC 420 (seeFIG. 4 ).Wireless network 400 is configured so thatsmall edge router 441 handles traffic from base stations 502-507.Small edge router 441 may handle traffic from other base stations (not shown) in any of geographic regions 402-404, or other geographic regions (not shown). - Instead of configuring
wireless network 400 so thatsmall edge router 441 handles traffic from base stations in a single geographic region, such hasgeographic region 402,wireless network 400 is configured so that the base stations 502-507 handled bysmall edge router 441 are interleaved among the geographic regions 402-404. Interleaving adds reliability towireless network 400. Ifsmall edge router 441 were to fail, base stations 502-503 ingeographic region 402 would be affected, base stations 504-505 ingeographic region 403 would be affected, and base stations 506-507 ingeographic region 404 would be affected. The other base stations in these geographic regions 402-404 would not be affected and would still be able to backhaul traffic toMSC 420 through the other small edge routers (assuming the other small edge routers inMSC 420 are operating). Therefore, an entire geographic region would not be affected much by one of the small routers failing. - If
small edge router 441 fails and its corresponding base stations 502-507 cannot provide service, neighboring base stations may provide service to some of the mobile devices in the service areas of base stations 502-507. When base stations are installed, the service areas of adjacent base stations commonly overlap. A mobile device often communicates with two or more base stations depending in the location of the mobile device. Therefore, if one of the base stations is unable to provide service to the mobile device, the mobile device may still receive service from another adjacent base station. -
Wireless network 400 inFIG. 5 is configured so that base stations 502-507 handled bysmall edge router 441 are not adjacent to one another. Adjacent in this embodiment means that the services areas of two base stations are touching, overlapping, or serving the same mobile device. Ingeographic region 402,base stations 502 and 503 are not adjacent to one another. Ingeographic region 403,base stations 504 and 505 are not adjacent to one another. Ingeographic region 404, base stations 506 and 507 are not adjacent to one another. Separating the base stations 502-507 handled bysmall edge router 441 adds another level of reliability. Ifsmall edge router 441 fails and its base stations 502-507 are not adjacent to one another, the service areas affected will be spread out in the geographic regions 402-404. With the affected service areas spread out and not adjacent to one another, there is an increased chance that a mobile device in the affected service area will receive service from a neighboring base station. In other embodiments, any of base stations 502-507 can be adjacent to one another, but separating the base stations 502-507 adds reliability. - Although twelve small edge routers 441-452 are shown in
FIG. 4 , the number of small edge routers depends on desired implementations. The use of twelve small edge routers assumes that each router will handle about 8% of the traffic as configured. In operation, a small buffer (2%) is also created so that each small edge router stays under the 10% level in actual operation. The use of twenty small edge routers would assume that each router will handle about 5% of the traffic as configured. In operation, a 5% buffer is created so that each small edge router stays under the 10% level in actual operation. Network designers need to balance the desire to create a large enough buffer to stay under the 10% level in actual operation versus the cost of adding more small edge routers. - The 10% level was also assumed based on the industry standards, such as TL 9000. The customers buying the MSCs may also define a traffic loss threshold other than the 10% industry standard. When a customer defines or agrees to a different threshold other than the 10% threshold, the number of small edge routers in the MSC may be less than ten. The number of small edge routers depends on the threshold, so that each of the small edge routers is to handle the defined threshold or less of the traffic for the MSC as configured. The threshold to be handled by each small edge router is based on the configuration of the MSC. For instance, if the threshold is defined as a 12% or less traffic loss, then the MSC may include eight small edge routers.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/090,114 US7929444B2 (en) | 2005-03-25 | 2005-03-25 | Communication nodes and methods using small routers to communicate over a backhaul facility |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/090,114 US7929444B2 (en) | 2005-03-25 | 2005-03-25 | Communication nodes and methods using small routers to communicate over a backhaul facility |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060215667A1 true US20060215667A1 (en) | 2006-09-28 |
US7929444B2 US7929444B2 (en) | 2011-04-19 |
Family
ID=37035087
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/090,114 Expired - Fee Related US7929444B2 (en) | 2005-03-25 | 2005-03-25 | Communication nodes and methods using small routers to communicate over a backhaul facility |
Country Status (1)
Country | Link |
---|---|
US (1) | US7929444B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8902812B1 (en) * | 2006-03-14 | 2014-12-02 | Sprint Spectrum L.P. | System and method for passive optical network backhaul |
US9986458B2 (en) * | 2015-08-27 | 2018-05-29 | Qualcomm Incorporated | Mitigating constrained backhaul availability between a radio access network (RAN) and core network |
US10925099B2 (en) * | 2014-05-13 | 2021-02-16 | Parallel Wireless, Inc. | Multi-egress backhaul |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8965331B2 (en) * | 2012-09-06 | 2015-02-24 | Google Inc. | Traffic management for base stations backhauled over data-capped network connections |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5119366A (en) * | 1990-12-14 | 1992-06-02 | At&T Bell Laboratories | Call processing method for distributed switching |
US6192037B1 (en) * | 1999-05-20 | 2001-02-20 | Motorola, Inc. | Method for changing communication in a communication system, and communication system therefor |
US6347228B1 (en) * | 1998-06-10 | 2002-02-12 | Motorola, Inc. | Location apparatus and method in a mobile telecommunications system |
US6477375B1 (en) * | 1999-04-16 | 2002-11-05 | Nortel Networks Limited | Method and system for reducing call setup processing cost by determining when to forward calls to detached subscribers |
US20030176163A1 (en) * | 2002-03-18 | 2003-09-18 | Samsung Electronics Co., Ltd. | System and method for on-line upgrade of call processing software using load sharing groups |
US6625473B1 (en) * | 1999-07-14 | 2003-09-23 | Samsung Electronics Co. Ltd. | Method of sharing load in mobile switching system |
US6668167B2 (en) * | 2000-01-26 | 2003-12-23 | Mcdowell Mark | Method and apparatus for sharing mobile user event information between wireless networks and fixed IP networks |
US20030237016A1 (en) * | 2000-03-03 | 2003-12-25 | Johnson Scott C. | System and apparatus for accelerating content delivery throughout networks |
US20040071153A1 (en) * | 2002-05-24 | 2004-04-15 | Dan Jasper | Networks and methods integrating digital mobile standards |
US20040114623A1 (en) * | 2002-12-13 | 2004-06-17 | Cisco Technology, Inc. | System and method for communicating traffic between a cell site and a central office in a telecommunications network |
US6782262B1 (en) * | 1998-10-28 | 2004-08-24 | Telefonaktiebolaget Lm Ericsson | Self-tuning sufficient signal strength threshold |
US6854013B2 (en) * | 2001-06-25 | 2005-02-08 | Nortel Networks Limited | Method and apparatus for optimizing network service |
US6950412B2 (en) * | 1999-12-30 | 2005-09-27 | Utstarcom Inc. | Base station controller in IMT-2000 system |
US20060203737A1 (en) * | 2005-03-04 | 2006-09-14 | Sprint Communications Company L.P. | Traffic delay processing |
-
2005
- 2005-03-25 US US11/090,114 patent/US7929444B2/en not_active Expired - Fee Related
Patent Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5119366A (en) * | 1990-12-14 | 1992-06-02 | At&T Bell Laboratories | Call processing method for distributed switching |
US6347228B1 (en) * | 1998-06-10 | 2002-02-12 | Motorola, Inc. | Location apparatus and method in a mobile telecommunications system |
US6782262B1 (en) * | 1998-10-28 | 2004-08-24 | Telefonaktiebolaget Lm Ericsson | Self-tuning sufficient signal strength threshold |
US6477375B1 (en) * | 1999-04-16 | 2002-11-05 | Nortel Networks Limited | Method and system for reducing call setup processing cost by determining when to forward calls to detached subscribers |
US6192037B1 (en) * | 1999-05-20 | 2001-02-20 | Motorola, Inc. | Method for changing communication in a communication system, and communication system therefor |
US6625473B1 (en) * | 1999-07-14 | 2003-09-23 | Samsung Electronics Co. Ltd. | Method of sharing load in mobile switching system |
US6950412B2 (en) * | 1999-12-30 | 2005-09-27 | Utstarcom Inc. | Base station controller in IMT-2000 system |
US6668167B2 (en) * | 2000-01-26 | 2003-12-23 | Mcdowell Mark | Method and apparatus for sharing mobile user event information between wireless networks and fixed IP networks |
US20030237016A1 (en) * | 2000-03-03 | 2003-12-25 | Johnson Scott C. | System and apparatus for accelerating content delivery throughout networks |
US6854013B2 (en) * | 2001-06-25 | 2005-02-08 | Nortel Networks Limited | Method and apparatus for optimizing network service |
US20030176163A1 (en) * | 2002-03-18 | 2003-09-18 | Samsung Electronics Co., Ltd. | System and method for on-line upgrade of call processing software using load sharing groups |
US20040071153A1 (en) * | 2002-05-24 | 2004-04-15 | Dan Jasper | Networks and methods integrating digital mobile standards |
US20040114623A1 (en) * | 2002-12-13 | 2004-06-17 | Cisco Technology, Inc. | System and method for communicating traffic between a cell site and a central office in a telecommunications network |
US20060203737A1 (en) * | 2005-03-04 | 2006-09-14 | Sprint Communications Company L.P. | Traffic delay processing |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8902812B1 (en) * | 2006-03-14 | 2014-12-02 | Sprint Spectrum L.P. | System and method for passive optical network backhaul |
US9843392B1 (en) * | 2006-03-14 | 2017-12-12 | Sprint Spectrum L.P. | System and method for passive optical network backhaul |
US10925099B2 (en) * | 2014-05-13 | 2021-02-16 | Parallel Wireless, Inc. | Multi-egress backhaul |
US9986458B2 (en) * | 2015-08-27 | 2018-05-29 | Qualcomm Incorporated | Mitigating constrained backhaul availability between a radio access network (RAN) and core network |
Also Published As
Publication number | Publication date |
---|---|
US7929444B2 (en) | 2011-04-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7995564B1 (en) | Geographic redundancy for call servers in a cellular system based on a bearer-independent core network | |
US8804486B2 (en) | Base stations routing traffic over a packet backhaul network to multiple routing elements | |
US20060227767A1 (en) | Fault tolerant architecture for wireless base stations using ethernet backhaul | |
CN100574486C (en) | The system of dual-homing networking and method thereof in the communication network | |
JP5784139B2 (en) | Communications system | |
US7929444B2 (en) | Communication nodes and methods using small routers to communicate over a backhaul facility | |
US20120108231A1 (en) | Base station, detection device, communication system and detection method | |
EP1271969A2 (en) | Signaling gateway system and network management method | |
CN101163038B (en) | Ethernet equipment link protecting method | |
US6717939B1 (en) | Virtual transport server in a telecommunication network | |
US6751748B1 (en) | Context redundancy system on a wireless and packet-based telecommunications network interface | |
CN108337162B (en) | System and method for supporting dual-homing protection | |
US7710880B2 (en) | Method and apparatus for security protection of service interruption in switch network | |
US7773555B1 (en) | Extension of an ethernet backhaul system for wireless base stations over a cable television distribution network | |
US9002340B2 (en) | Method and apparatus for backup communication services | |
KR101017502B1 (en) | Duplicate billing system and method in a communication network | |
WO2014125761A1 (en) | Wireless transmission apparatus, communication system, and communication trouble control method | |
US7957270B2 (en) | Resilient packet ring protection over a wavelength division multiplexing network | |
CN100544456C (en) | Call out the method for route in a kind of tandem system and the tandem system | |
US20070093249A1 (en) | SS7 Link failover communications over existing cellular networks | |
JP5144363B2 (en) | Call control device and telephone system | |
JP4354357B2 (en) | Packet processing module | |
Rajalakshmi et al. | A survey on cost effective survivable network design in wireless access network | |
KR100836247B1 (en) | Subscriber DB management system comprising call processing server separated from DB server | |
JP2016052033A (en) | Wireless communication system and control method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LUCENT TECHNOLOGIES, INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LIN, SHENG LING;REEL/FRAME:016429/0546 Effective date: 20050323 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: MERGER;ASSIGNOR:LUCENT TECHNOLOGIES INC.;REEL/FRAME:025774/0384 Effective date: 20081101 |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: MERGER;ASSIGNOR:LUCENT TECHNOLOGIES INC.;REEL/FRAME:025785/0816 Effective date: 20081101 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: ALCATEL-LUCENT USA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033950/0261 Effective date: 20140819 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001 Effective date: 20170912 Owner name: NOKIA USA INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001 Effective date: 20170913 Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001 Effective date: 20170913 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: NOKIA US HOLDINGS INC., NEW JERSEY Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682 Effective date: 20181220 |
|
FEPP | Fee payment procedure |
Free format text: 7.5 YR SURCHARGE - LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1555); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001 Effective date: 20211129 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: BARINGS FINANCE LLC, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:RPX CORPORATION;REEL/FRAME:063429/0001 Effective date: 20220107 |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230419 |