SUPPORT OF TRIPLE PLAY SERVICES IN USER DEVICES

• US 20090097492A1
• Filed: 10/12/2007
• Published: 04/16/2009
• Est. Priority Date: 10/12/2007
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Giguere, Mathieu, Tremblay, Benoit, Julien, Martin, Monette, Sylvain
• Application Number:
  US11/871,284
• Publication Number:
  US 20090097492A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 12/4658 wherein a VLAN tag represents a service provider backbone VLAN, e.g. B-Tag, S-Tag
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming

Abstract

Several services offered by distinct service providers can be accessed from a single user device, through one or more gateways. To ensure quality of service control, each service provider allocates a distinct address to the user device. Distinct forwarding information bases and service mappings are defined at the user device, comprising one such forwarding information base for each service provider and one service mapping for each service type offered by a given service provider. The separate addresses allocated to the user device are related to the separate service mappings. Distinct virtual local area networks (VLANs) are defined, each containing one of the forwarding information base and one of the service mappings. Tags added to packets by the gateways and arriving at the user device are used to link the packets to the proper service provider and to the proper service type.

Claims

1. A method of exchanging data packets between a user device and a plurality of service providers, the method comprising the steps of:

defining in the user device at least two forwarding information bases (FIB), each FIB comprising an identity and an internet protocol (IP) address of a corresponding service provider, each FIB being associated with at least one service type, with a corresponding IP address allocated to the user device by the corresponding service provider, and with a corresponding tag;

inserting a given tag in a data packet; and

using the given tag to identify a given service provider and a given service type corresponding to the data packet.

2. The method of claim 1, wherein:

a first one of the at least two FIBs is associated with a first IP address allocated to the user device by a first service provider;

a second one of the at least two FIBs is associated with a second IP address allocated to the user device by a second service provider; and

the first and the second IP addresses allocated to the user device are equal.

3. The method of claim 1, wherein:

one of the at least two FIBs corresponds to the given service provider;

the one of the at least two FIBs comprises a first virtual local area network (VLAN); and

the first VLAN comprises the user device, the given service type and the given service provider.

4. The method of claim 3, wherein:

the one of the at least two FIBs further comprises a second VLAN; and

the second VLAN comprises another service type.

5. The method of claim 1, wherein:

an IP address of the given service provider and an IP address allocated to the user device by the given service provider are used as a source address and as a destination address in data packets exchanged between the user device and the given service provider.

6. The method of claim 1, further comprising:

receiving a downstream data packet at the user device;

extracting a received tag from the downstream data packet;

using the received tag to identify a service provider having produced the downstream data packet and to identify a corresponding service type; and

processing the data packet according to the service provider having produced the downstream data packet and according to the corresponding service type.

7. A user device for exchanging data packets with a plurality of service providers, comprising:

an input/output (I/O) port adapted to receive data packets from the service providers;

two or more service units adapted to process the data packets, wherein each service unit supports at least one service type;

a memory adapted to store at least two forwarding information bases (FIB), each FIB comprising an identity and an internet protocol (IP) address of a corresponding service provider, each FIB being associated with at least one service type, with a corresponding IP address allocated to the user device by the corresponding service provider, and with a corresponding tag; and

a service selector adapted to retrieve a given tag from a received data packet, to read from the memory a given service type and an identity of a given service provider by use of the given tag, and to forward the received data packet towards one of the two or more service units based on the given service type and on the identity of the given service provider.

8. The user device of claim 7, wherein:

the I/O port is further adapted to send data packets towards the given service provider.

9. The user device of claim 8, wherein:

the two or more service units are each further adapted to produce an upstream data packet and to provide an indication of the given service type and of the identity of the given service provider; and

the service selector is further adapted to read from the memory the given tag by use of the indication of the given service type and of the identity of the given service provider, to insert the given tag in the upstream data packet, and to request the I/O port to send the upstream data packet towards the given service provider.

10. The user device of claim 7, wherein:

the I/O port is further adapted to receive from the given service provider a service response comprising an IP address allocated to the user device and an IP address of the given service provider; and

the memory is further adapted to store, in relation with the given tag, the IP addresses received in the service response.