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) 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 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:
A method to provide authentication services to third party vendors by a service provider hosting an authentication, authorization and accounting (AAA) server or a similar device that can authenticate users for some other service. This method enables easy and substantially error-free end-user authentication, which forms the basis for enabling electronic transactions (e.g., web-based) that are less vulnerable to fraud.
Abstract:
In one embodiment, a method for estimating the cardinality of one or more tags in a system that has the one or more tags and one or more readers. The reader issues a command requesting that the tags identify themselves. The command includes timing information defining a total number of timeslots. In response to the command, each of the one or more tags (i) selects a timeslot in which to reply to the command and (ii) issues a reply in the selected timeslot. The method includes: (a) issuing the command; (b) receiving, in one or more timeslots, replies from the one or more tags; and (c) deriving an estimate of the cardinality of the one or more tags in the system based on at least one of: (i) the number of zero slots, wherein a zero slot is a timeslot that has no tags transmitting therein, (ii) the number of singleton slots, wherein a singleton slot is a timeslot that has only one tag transmitting therein, and (iii) the number of collision slots, wherein a collision slot is a timeslot that has more than one tag transmitting therein.