Telefonaktiebolaget Lm Ericsson (publ)

Sylvain Monette

Martin Julien

Benoit Tremblay

Mathieu Giguere

Joacim Halén

Panagiotis Saltsidis

Attila Takács

Balázs Peter Gerö

Joacim Halen

Benoit C Tremblay

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.

Adaptive router architecture using logical internal addressing

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.

GMPLS based OAM provisioning

A method of providing protection switching on a backbone network includes configuring a service instance table for a first port of a first bridge. The service instance table includes a Virtual Local Access Network (VLAN) identifier entry for one or more service instances. The method also includes mapping data traffic received at the first bridge onto a first trunk by setting a VLAN identifier entry for a first service instance and transmitting data traffic to a second bridge on the first trunk in accordance with the mapping and monitoring the first trunk for faults by exchanging continuity check messages with the second bridge over the first trunk. The method additionally includes, upon detecting a fault, remapping data traffic for the first service instance by changing the VLAN identifier entry for the first service instance and transmitting data traffic to the second bridge in accordance with the remapping.

System and method for ethernet protection switching in a provider backbone bridging traffic engineering domain

A system and method of providing Ethernet protection switching in a PBB-TE Domain. Two PBB-TE trunks are established between a first B-component and a second B-component. Each trunk includes two unidirectional Ethernet Switching Paths (ESPs), each associated with a possibly different VLAN identifier. Data traffic is mapped onto the first PBB-TE trunk, where the first PBB-TE trunk corresponds to a working entity and the second PBB-TE trunk corresponds to a backup protection entity. Data traffic is sent via a first ESP of the first trunk associated with a first VID and a second ESP of the first trunk associated with a second VID. The two PBB-TE trunks are monitored for faults. Upon detecting a fault on one of the PBB-TE trunks, data traffic is remapped onto the other PBB-TE trunk via a third ESP associated with a third VID and a fourth ESP associated with a fourth VID.

System and method for Ethernet protection switching in a provider backbone bridging traffic engineering domain

Systems and methods according to these exemplary embodiments provide for methods and systems for negotiating resources in a communication system. One exemplary method includes transmitting, by a service manager, a request for a service, wherein the service request either explicitly provides, or implicitly refers to, a list of a plurality of service options for providing the service. Additionally, a resource manage can receive the transmission request from a service manager and process the request based upon either the explicitly transmitted list of service options or the reference to a list of service options.

Network resource negotiation between a service provider network and an access network

A method and nodes for aggregating data traffic over an access domain between service providers and user domains. An access edge node is introduced in the access domain between service providers and user domains. The access edge node hosts service agents, each service agent controlling a Virtual Local Area Network (VLAN) over the access domain for one of the service providers. The access edge node verifies whether a service agent, corresponding to the service provider identified in a received service request, exists. If so, the user domain is added to the VLAN corresponding to the requested service provider by creating a service binding at the access edge node. An access node providing access to the access domain to the user domain is informed of the service binding. Data traffic between the user domain and the identified service provider is aggregated over the access domain according to the created service binding.

Method for aggregating data traffic over an access domain and nodes therefor

The present invention relates to a method and nodes for managing service bindings over an access domain. For doing so, an access edge node is introduced in the access domain between a plurality of service providers and user domains, and an access node is introduced between the user domains and the access domain. The access edge node creates, modifies and removes service bindings and informs the access node of those creations, modifications and removals. Each service binding binds one of the user domain, the access node and the access edge node on data traffic handling over the access domain between the user domain and the service provider domain. More particularly, the service binding associates the user domain to a Virtual Local Area Network (VLAN) for the service provider domain on the access domain, controlled by the access edge node.

Method for managing service bindings over an access domain and nodes therefor

The present invention relates to a method and nodes for performing bridging of data traffic over an access domain. For doing so, for data traffic received at an access node from a first user domain and destined to a second user domain, the access node identifies a service binding corresponding to the received data. Then, the access node tunnels the data traffic in a Unicast message addressed to an access edge node in accordance with the identified service binding. The tunnelled data traffic is then forwarded to the access edge node. The access edge node receives the tunnelled data traffic, and identifies the service binding corresponding to the received tunnelled data traffic. The access edge node then proceeds with redirecting the tunnelled data traffic to a second access node in accordance with the identified service binding therein. The redirected tunnelled data traffic is received at a second access node, where it is detunnelled and forwarded to the second user domain. The method also provides an access node and an access edge node for performing the invention.

Method and nodes for performing bridging of data traffic over an access domain

The present invention relates to a method and nodes for handling multicast messages over an access domain. The method starts with the receipt of a multicast message from a service provider domain. The method pursues with the identification of a service agent corresponding to the service provider domain from which the multicast message is received. Then, the content of a Virtual Local Area Network (VLAN) Tag field of the multicast message is modified so as to correspond to the identified service agent. The modified multicast message is forwarded on the access domain. Upon receipt of the modified multicast message at an access node, the access node identifies at least one service binding related to the service agent identified in the VLAN Tag field of the received multicast message. For each related service binding, the access node adapts the VLAN Tag field of the multicast message so as to correspond to a local VLAN information, and forwards the adapted multicast message on a user port corresponding to the service binding. The invention also includes an access edge node and an access node adapted to perform the method of the present invention.

Method and nodes for handling multicast messages

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.

Applying policies for managing a service flow

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.

Decentralized node, access edge node, and access node for aggregating data traffic over an access domain, and method thereof

A router architecture with one or more network interfaces, processing, switching and forwarding elements, each which has one or more processing units 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 to the processing elements while each of the forwarding elements are capable of receiving network traffic on the network interface and are capable to delegate processing of network traffic toward processing elements through at least one switching element.

Adaptive router architecture

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.

Method and nodes for aggregating data traffic through unicast messages over an access domain using service bindings

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.

Growing community of inventors

Blainville, Canada

Sylvain Monette