Abstract:
The present invention relates to a method, an access node, an access edge node and a decentralized node for aggregating data traffic over an access domain. The decentralized node corresponds to one of the service providers, and is located in closer proximity with user domains to be serviced. The decentralized node maintains over the access domain one or several Virtual Local Area Networks, for aggregating thereon data traffic to be exchanged with the user domains, on behalf of the service provider domain. To allow proper aggregation of the data traffic, service bindings are created and stored at the access edge node, and further stored at the decentralized node and at the access node. Therefore, aggregation of the data traffic between the decentralized node and the user domains over the access domain is performed in accordance with the created service bindings.
Abstract:
A method and a related router comprising a network interface, a logical addressing module and a forwarding element card. The logical addressing module is capable of maintaining at least one local table associating at least one card of the router with at least a portion of at least one service provided by the router. The forwarding element card is capable of receiving a packet stream on the network interface, detecting that the packet stream requires further treatment from a further card of the router and, upon detection, consulting the local table to find an identifier, to which the further card is linked, based on information found in the packet stream before forwarding the packet stream toward the further card.
Abstract:
A router comprising a plurality of elements, each having an element identifier, subdivided into a plurality of groups of at least one element. Each group has a common identifier and each member within each group shares redundant capabilities. Each element is capable of communicating with another element by addressing information to the common identifier instead of the element identifier. Optionally, one element can be a member of more than one group. Another option suggests that all elements within a group share essential information associated with a service provided by the group. Another option is implemented through one element of the router identifying a primary element for a group, wherein the primary element serves requests addressed the corresponding common identifier. Yet another option suggests that one element is identified through configuration of the router as a primary element in its group to serve requests addressed to the common identifier.
Abstract:
A router and a router architecture comprising at least one network interface, a plurality of processing elements, at least one switching element and a plurality of forwarding elements. Each of the plurality of processing elements comprises at least one processing unit, wherein each processing unit is capable of processing network traffic to provide at least a portion of a network service. The switching element is capable of acting as a proxy of the plurality of processing elements while each of the plurality of forwarding elements is capable of receiving network traffic on the at least one network interface of the router and delegating processing of network traffic toward at least one of the plurality of processing elements through the at least one switching element.
Abstract:
The present invention relates to an ingress node (102, 700) and methods therein for Operation Administration arid Maintenance, OAM related to Resource Reservation Protocol-Traffic Engineering, RSVP-TE5 for obtaining attributes for timer values being assigned to a connection from the ingress node (102) via intermediate nodes (104, 106, 108, 110) to an egress node (112), during configuration of die connection. An interval of suitable tinier values for the intermediate nodes is specified. Configuration attributes are obtained for a timer value within an interval that is acceptable by the intermediate nodes and the egress node, based on the specified interval of suitable timer values. The obtained configuration attributes are applied during configuration of the connection from the ingress node via the intermediate nodes to the egress node, if the obtained configuration attributes are appropriate to the ingress node. Fine-tuning of connection related timers can therefore be achieved, decreasing the overall recovery time and the overall overhead.
Abstract:
A packet node and corresponding methods are provided for providing services to packets received at the packet node. At an ingress card, a packet is classified and a virtual media access control (VMAC) address is attached to the packet. The VMAC address identifies a service component for providing a service to the packet. Layer two switching of the packet is made within the packet node, based on the VMAC address. After processing of the packet by the service component, a new VMAC address is attached to the packet. Further layer two switching of the packet, based on the new VMAC address, may lead to further processing by another service component or to forwarding of the packet beyond the packet node.
Abstract:
A method and network are described herein for provisioning Operations, Administration, and Maintenance (OAM) entities for a connection when setting-up the connection between an ingress edge node and an egress edge node.
Abstract:
A method and an access domain node identify and manage a type of service offered by a service provider to user domains. A service template is prepared by the service provider, comprising an address of a server and a protocol identifier, as well as policies for controlling traffic for the service. Upon set up of a connection between a user domain and the service provider, an address of the user domain is added to the service template to produce a service flow management set. Every data packet exchanged between the user domain and the server, in either direction, is related to a service data flow for a given service type by checking for a match between a source address, a destination address, and a protocol type contained therein, with an appropriate service type. Policies from the service flow management set are used to manage the flow of data packets.
Abstract:
The present invention relates to a method and nodes for performing data traffic aggregation over an access domain using service bindings. Upon receipt of a service request related message at an access edge node for a first device of a user domain, the service request related message identifying the first device of the user domain and one of the service provider domains, a service binding is created at the access edge node. The service binding rules data traffic between the first device of the user domain and the service provider domain by committing an access node serving the user domain and the access edge node in a manner of managing data traffic therebetween over the access domain. An access node serving the user domain for which the service request related message is received is informed of the created service binding. The created service binding is enforced at the access node and the access edge node for data traffic over the access domain between the first device of the user domain and the service provider domain by removing a user device MAC address from Unicast messages exchanged therebetween over the access domain and replacing with a virtual MAC address recognized by the access node and the access edge node.
Abstract:
A finite state machine and a router adapted thereto for providing a service. The finite state machine is executed on a first and a second distinct hardware modules. The first module has access to a first memory and the second module has access to a second memory. The first and second memory are different and not shared therebetween. At least one transition between a first state and a second state of the finite state machine from the first module to the second module is performed by sending local information of the first module toward the second module. The local information at least indicates the second state of the finite state machine. Local information can be inserted by the router, for example, in a meta-data header.