Abstract:
The SoftRouter architecture separates the implementation of control plane functions from packet forwarding functions. In this architecture, all control plane functions are implemented on general purpose servers called the control elements (CEs) 200, 204 that may be multiple hops away from the forwarding elements (FEs) 202, 206. A network element (NE) or a router is formed using dynamic binding between the CEs and the FEs. The flexibility of the SoftRouter architecture over conventional routers with collocated and tightly integrated control and forwarding functions results in increased reliability, increased scalability, increased security, ease of adding new functionality, and decreased cost.
Abstract:
A SoftRouter architecture deconstructs routers by separating the control entities of a router from its forwarding components, enabling dynamic binding between them. In the SoftRouter architecture, control plane functions are aggregated and implemented on a few smart servers which control forwarding elements that are multiple network hops away. A dynamic binding protocol performs network-wide control plane failovers. Network stability is improved by aggregating and remotely hosting routing protocols, such as OSPF and BGP. This results in faster convergence, lower protocol messages processed, and fewer route changes following a failure. The SoftRouter architecture includes a few smart control entities 402, 404 that manage a large number of forwarding elements 406 to provide greater support for network-wide control. In the SoftRouter architecture, routing protocols operate remotely at a control element and control one or more forwarding elements by downloading the forwarding tables, etc. into the forwarding elements. Intra-domain routing and inter-domain routing are also included.
Abstract:
The SoftRouter architecture separates the implementation of control plane functions from packet forwarding functions. In this architecture, all control plane functions are implemented on general purpose servers called the control elements (CEs) 502 that may be multiple hops away from the forwarding elements (FEs) 506. A network element (NE) or a router is formed using dynamic binding between the CEs 502 and the FEs 506. There is a protocol failover mechanism for handling failovers initiated by FEs 506 to transfer control from one CE 502 to another CE 502.
Abstract:
An embodiment of the exemplary SoftRouter architecture includes two physically separate networks, a control plane network and a data plane network. The data plane network is one physical network for the data traffic, while the control plane network is another physical network for the control traffic. The topology of the data plane network is made up of interconnected forwarding elements (FEs) 506. The topology of the control plane network is made up interconnected control elements (CEs) 502. This physical independence of the control plane network from the data plane network provides for a secure mechanism to communicate among the CEs 502 in the control plane network. In addition, this physical independence provides improved reliability and improved scalability, when compared to the traditional router architecture, where control plane message are in-band with the data plane.
Abstract:
The SoftRouter architecture separates the implementation of control plane functions from packet forwarding functions. In this architecture, all control plane functions are implemented on general purpose servers called the control elements (CEs) 200, 204 that may be multiple hops away from the forwarding elements (FEs) 202, 206. A network element (NE) or a router is formed using dynamic binding between the CEs and the FEs. The flexibility of the SoftRouter architecture over conventional routers with collocated and tightly integrated control and forwarding functions results in increased reliability, increased scalability, increased security, ease of adding new functionality, and decreased cost.
Abstract:
The SoftRouter architecture separates the implementation of control plane functions from packet forwarding functions. In this architecture, all control plane functions are implemented on general purpose servers called the control elements (CEs) 502 that may be multiple hops away from the forwarding elements (FEs) 506. A network element (NE) or a router is formed using dynamic binding between the CEs 502 and the FEs 506. There is a protocol failover mechanism for handling failovers initiated by FEs 506 to transfer control from one CE 502 to another CE 502.
Abstract:
A base station controller (BSC) of a radio or wireless telecommunications network base station includes a director. A BSC includes multiple central processing units (CPUs), with each CPU running a call-processing application for one or more connections. The director is a logical entity that intercepts wireless call-setup signaling and assigns each corresponding connection to a CPU according to a centralized load-balancing algorithm. The centralized load-balancing algorithm distributes connections to less loaded CPUs to i) prevent individual CPUs from overloading, ii) utilize otherwise unused system resources, and iii) increase overall system performance. The director hosts cell components that manage code division multiple access (CDMA) downlink spreading codes for a base station, providing centralized allocation of spreading codes by the base station.
Abstract:
In a wireless network, an architecture for wireless attack resistance (AWARE) detects power-drain denial-of-service (DoS) attacks by generating statistical measures relating the power consumption by a mobile unit and data transmitted to and from the mobile unit during normal operations of the wireless network. The AWARE architecture compares those statistical measures to current measures to detect a DoS attack if the current measure differs from the statistical measure by more than a specified threshold. If a DoS attack is detected, then the AWARE architecture can inhibit communications with the mobile unit to prevent the mobile from consuming too much power. The statistical measure may be an energy efficiency ratio relating the number of bits of data transmitted to or from the mobile unit over a specified time interval to the amount of power consumed by the mobile unit during that time interval.
Abstract:
In a wireless network, an architecture for wireless attack resistance (AWARE) detects power-drain denial-of-service (DoS) attacks by generating statistical measures relating the power consumption by a mobile unit and data transmitted to and from the mobile unit during normal operations of the wireless network. The AWARE architecture compares those statistical measures to current measures to detect a DoS attack if the current measure differs from the statistical measure by more than a specified threshold. If a DoS attack is detected, then the AWARE architecture can inhibit communications with the mobile unit to prevent the mobile from consuming too much power. The statistical measure may be an energy efficiency ratio relating the number of bits of data transmitted to or from the mobile unit over a specified time interval to the amount of power consumed by the mobile unit during that time interval.
Abstract:
Wireless state information collected or inferred from a 3G wireless network is used to detect and prevent malicious attacks against the network.