IST - 6th FP
Contract N 507295
Andreas Foglar
Infineon Technologies, Balanstrasse 73, 81541 Munich, Germany
Andreas.foglar@infineon.com
Identifier:
Deliverable D TF3.1
Class:
Report
Version:
09
Version Date:
20/01/2005
Distribution:
Consortium Confidential
Responsible Partner:
IFX
Filename:
TF3-0001-V09.doc
1/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
DOCUMENT INFORMATION
Project ref. No.
IST-6thFP-507295
Project acronym
MUSE
Consortium Confidential
31.12.2004
20.01.2005
Deliverable number
TF3.1
Deliverable name
Type
Report
09
Number of pages
70
WP / TF contributing
TF3
WP / TF responsible
IFX
Main contributors
EAB, PT, LU, FT, DT, ALC, STM, THO, TID, INR, NTU, UC3
Editor(s)
EU Project Officer
Pertti Jauhiainen
Keywords
2/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
DOCUMENT HISTORY
Version
Date
Author
Partner
01
25.03.04
Foglar
IFX
First draft
01_TS
25.10.04
Sundberg
TS
02
30.10.04
Foglar
IFX
03
04.11.04
De Smedt
THOB
05.11.04
UC3M
LU
09.11.04
Foglar
IFX
04
17.11.04
Foglar
IFX
05
18.11.04
Foglar
de Smedt
Balemans
IFX
THOB
LU
06
10.12.04
Foglar
Balemans
IFX
LU
07
09.01.05
Foglar
IFX
08
11.01.05
Haag
DT
09
20.01.05
Foglar
IFX
3/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
TABLE OF CONTENTS
DOCUMENT INFORMATION ..................................................................................................................2
DOCUMENT HISTORY............................................................................................................................3
TABLE OF CONTENTS...........................................................................................................................4
LIST OF FIGURES AND TABLES ..........................................................................................................6
ABBREVIATIONS....................................................................................................................................8
REFERENCES .......................................................................................................................................14
EXECUTIVE SUMMARY........................................................................................................................15
CONCLUSIONS AND NEXT STEPS.....................................................................................................16
1
INTRODUCTION ............................................................................................................................17
1.1
Strategy ..................................................................................................................18
1.2
MUSE specific functions (from SPA, Access Architectures)................................18
1.2.1
Multiple Connections ..............................................................................................19
1.2.2
Quality of Service QoS ...........................................................................................19
1.2.3
New Business Roles...............................................................................................20
CONTROL PLANE.........................................................................................................................41
APPENDIX......................................................................................................................................42
6.1
Home network technologies: USB..........................................................................42
6.1.1
Overview.................................................................................................................42
6.1.2
Bandwidth ...............................................................................................................43
6.1.3
Distance information (meters) ................................................................................43
4/70
Consortium Confidential
Project Deliverable
6.1.4
6.1.5
6.1.6
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
6.4.8
6.4.9
6.5
6.5.1
6.5.2
6.5.3
6.5.4
6.6
6.6.1
6.6.2
6.6.3
6.6.4
6.6.5
IST - 6th FP
Contract N 507295
Latency ...................................................................................................................43
Layer 2 QoS............................................................................................................43
Limitations...............................................................................................................43
Home network technologies: Bluetooth ..................................................................44
Core architecture overview.....................................................................................44
Modulation and Bandwidth .....................................................................................46
Distance information ...............................................................................................46
Latency and QoS ....................................................................................................46
Bluetooth profiles ....................................................................................................47
Limitations...............................................................................................................47
Home network technologies: WLAN.......................................................................48
Overview.................................................................................................................48
Protocol suite ..........................................................................................................49
Available Bandwidth ...............................................................................................49
Latency ...................................................................................................................51
Layer 2 QoS mechanism ........................................................................................51
GSB Traffic Classes over slow Access Lines.........................................................54
Packet multiplexing.................................................................................................55
QoS class support ..................................................................................................55
Jitter calculation for highest priority queue .............................................................57
Jitter calculation for lower priority queues ..............................................................60
ATM or PTM-TC? ...................................................................................................60
Pros and cons of multiple ADSL paths ...................................................................61
Fulfilling GSB traffic classes ...................................................................................62
Correlating low jitter flows.......................................................................................65
Conclusion ..............................................................................................................67
Layer 1 Example: PON...........................................................................................67
Interface for Point to Point Ethernet over SM fibre.................................................67
Optical characteristics of the U interface................................................................67
Performance requirements .....................................................................................68
Mechanical properties of U interface ......................................................................68
Layer 1 Example: SHDSL.......................................................................................68
General Definitions .................................................................................................68
Electrical characteristics of the SHDSL U interface ...............................................69
Performance requirements .....................................................................................69
Mechanical properties of SHDSL U interface.........................................................69
Management of the SHDSL physical layer.............................................................70
5/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
6/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
7/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
ABBREVIATIONS
AAA
AAL
ACS
Auto-Configuration Server
ADSL
AF
Assured Forwarding
ALG
AM
Access Multiplexer
APON
ARP
ASP
ATM
ATA
BAS
BER
B-NT
BRAS
CAC
CATV
Cable TV
CHAP
CoS
Class of Service
CPE
CPN
CRC
C-VLAN
CWDM
DF
Default Forwarding
DiffServ
Differentiated Services
DHCP
DNS
DP
Distribution Point
DSCP
DSL
DSM
EAP
8/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
EF
Expedited Forwarding
EFM
ELMI
EOC
EPON
ETH
Ethernet
EUT
End-User Terminal
EVC
FEC
FOO
FPD
FQDN
FTTB
FTTCab
FTTEx
FTTH
FTTO
FWA
GARP
GbE
Gigabit Ethernet
GFR
GMRP
GPON
GSB
HSI
IAD
IANA
IEEE
IFG
interframe Gap
IGMP
ILEC
ILMI
IMS
IP Multimedia Subsystem
IntServ
Integrated Services
IP
Internet Protocol
9/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
IPCP
IP Control Protocol
IPDV
IPER
IPG
Interpacket Gap
IPLR
IPTD
IPv4
IPv6
ISDL
ISP
ITU-T
LAC
LACP
LCP
LER
LEx
Local eXchange
LMI
LNS
LSP
LSR
MAC
MAC DA
MAC SA
MAC FF
MBGP
MDF
MEF
MIDCOM
MIDdlebox COMmunications
MITM
Man-in-the-Middle
MPEG
MPLS
NAP
NAPT
NAT
NGN
10/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
NSP
NT
Network Termination
OSGi
OAM
OLT
ONT
ONU
PAP
PBX
PDU
PDV
PHY
Physical Layer
PLOAM
PON
PoP
Points of Presence
PPP
Point-to-Point Protocol
PPPoA
PPPoE
PPV
PSTN
PTM
P-t-MP
P-t-P
Point to Point
PVC
QoS
Quality of Service
RADIUS
RADSL
RE-ADSL
RDI
RFC
RG
RGW
Residential Gateway
RNP
SAR
SDH
11/70
Consortium Confidential
Project Deliverable
SDSL
SG
Service Gateway
SHDSL
SIP
SLA
SLS
SNMP
SP
ST
Service Termination
STB
STP
S-VLAN
T-CONT
Traffic Container
TC
TCP
TDM
TDMA
ToIP
Telephony over IP
ToS
Type of Service
TVoIP
TV over IP
UDP
UNI
URL
VC
Virtual Channel
VCC
VCI
VDSL
VLAN
VoD
Video on Demand
VoDSL
VoIP
Voice over IP
VP
Virtual Path
VPI
WAN
WP
12/70
IST - 6th FP
Contract N 507295
Consortium Confidential
Project Deliverable
xDSL
IST - 6th FP
Contract N 507295
xDSL refers to different variations of DSL, such as ADSL, HDSL, and RADSL
13/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
REFERENCES
[1]
Technical Report DSL Forum TR-058 Multi-Service Architecture & Framework Requirements, September 2003
[2]
[3]
MUSE deliverable D TF1.2 Node requirements for applying QoS and GoS, December 2004
[4]
Draft Standard P802.1p/D8 IEEE Standards for Local and Metropolitan Area Networks Supplement to Media Access Control (MAC) Bridges: Traffic Class Expediting
and Dynamic Multicast Filtering, October 21, 1997
[5]
ITU-T STUDY GROUP 15 Temporary Document SI-022, ADSL: Draft new G.992.3
Annex K.4 (64/65 based PTM-TC), Stresa, Italy, 18-22 October, 2004
[6]
Draft Standard IEEE P802.1ad/D2.0 Virtual Bridged Local Area Networks Amendment 4: Provider Bridges, December 15, 2003
[7]
QoS as service enabler for BB Access, Presentation by Romain Vinel, France Telecom; Broadband Europe, Bruges - December 8-10, 2004; link:
http://www.ist-muse.org/Documents/BBEurope/BBEurope_RomainVinel.pdf
14/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
EXECUTIVE SUMMARY
This document reflects one year work on the functional details of the MUSE residential gateway. Starting with DSL Forum reference architecture (TR-58) the functionality of the Routing
Gateway was broken down into small functional blocks. In parallel the enhanced functionality
of MUSE networks was introduced, in particular
Also the new service provider roles defined in WPA1 had to be considered. They lead to
functional entities which can be assigned individually to service providers.
TF3 goal is to assure that a GSB compliant residential gateway shall work in every GSB network. GSB, the Global System for Broadband communication is defined by MUSE for broadband access networks. Within the GSB framework this document specifies an universal residential gateway architecture. Well defined interfaces shall assure easy adaptation to various
first mile technologies and also to the large variety of home network scenarios.
The common residential gateway architecture must support different access technologies
ranging from a few hundred kb/s up to 100Mb/s. Another challenge is the variety of residential network configurations ranging from a simple analogue phone up to mid-size networks
with several terminals and triple play services. Solutions must be scalable and still be cost
effective in all application scenarios.
An answer to this challenge apart from a perfect architecture is the definition of explicit
values for parameters. Explicit values can be hard-coded and must not be configured. This
makes a solution easy to use and less complex. In this document a first attempt is made to
agree on explicit values. Throughout the document explicit values are proposed with the term
default value. In case there is no objection within the run-time of MUSE, these default values could become (industry) standard values.
The main part of this document is the Layer 2 and 3 functional description of the residential
gateway. The physical layer of the 1st mile is not a central part of the specification, but the
Transmission Convergence (TC) sub-layer is considered. For reference two examples for
physical layer interfaces are given, one electrical (SHDSL) and one optical. Another appendix studies thoroughly how to fulfil the high-end QoS of MUSE over slow access lines. Also
some background information about home network technologies is given.
Management protocols such as ELMI, OSGI, SNMP are not covered, but configuration parameters are listed. This simplifies further work on residential gateway management. The
goal of a common set of physical layer parameters could not be achieved for this deliverable.
It will be tackled in future documents.
Control plane functions such as signalling protocols are not yet finalised in SPA. Therefore
no final solution can be given in this document. Control messages use data path connections and no special signalling connection. A control flow may share a connection with another control flow or with a data flow. It could also use a dedicated connection. The QoS of
the control flow must be selected accordingly.
15/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Residential
ATA
L3+ Service
Gateway
POTS
Gateway
ETH
Access
1st Mile
ETH
Gateway
Home
L2 Service
Router
Gateway
Bluetooth
ETH
ETH
STB
L2+ Service
Gateway
SCART
Residential Network
Terminals
16/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
1 INTRODUCTION
With increasing functionality of the network also the complexity of the network termination NT
increases. In analogue telephony the NT is just a plug. The wire loop is closed in the terminal
(phone). With ISDN an active NT box is installed, which does signal conversion and also includes loop test functions. With ADSL a passive splitter is needed and the signal conversion
and loop test functions move into the modem. The modem could be built into a PC, but in
most cases it is a separate box with more or less additional functionality such as routing,
firewall and protocol conversion. With the additional functionality of the MUSE GSB solution
the complexity of the NT increases. The NT becomes an Access Gateway which includes
many other functions. Optionally in some cases the NT might be realised in a separate box.
In these cases it should contain most MUSE/GSB specific functions.
The GSB (Gobal System for Broadband communication) system defined by MUSE introduces among others two, new, technical features:
1. Multiple connections: while an ADSL modem uses a single connection to an Internet Service Provider ISP the MUSE access network offers several connections to different service providers. These connections can be permanent as with ADSL or dynamically set up on demand.
2. Quality of Service QoS: while ADSL based services today offer best-effort traffic
only, GSB networks will offer several QoS classes with selectable parameters such
as throughput, jitter etc.
Another aspect of MUSE GSB solution is standardisation. Todays ADSL solutions are not
fully compatible, but operator specific. It is not possible to re-use a modem from one operator
in the network of another operator, even within the same country. Also the manufacturer of a
modem must homologise it separately for each operator in each country. This leads to additional costs and is a big barrier for small manufacturers. To improve this situation MUSE
drives for standardisation.
3. MUSE aims at a European or even global standard (GSB) for home gateways. A
GSB compliant home gateway will work with all GSB networks. It is the aim of TF3
and also of this document to consolidate inputs from all subprojects.
Finally MUSE provides solutions for unbundling. Network access and transport are separated
from network and application services.
4. MUSE has defined new service roles such as packager, network access provider,
network service provider, application service provider. The residential gateway must
reflect the different service roles.
All the issues 1-4 listed above lead to enhanced functionality and hence enhanced complexity in the home gateway. On the other hand the home gateway should be as simple as
possible to keep cost low and to simplify operation. One big step to solve this conflict is the
QoS solution described in D TF1.2. It allows to configure automatically the schedulers in the
NT depending on the transmission rate. Another solution to solve this conflict is the agreement on explicit values.
17/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
If for example explicit values are assigned to the four ATM VCs in the case of ATM segmentation there is no need to configure these values. GSB home gateways will automatically
support four traffic classes without configuration. One of the reasons for the success of
Ethernet and of the Internet is based on the assignment of fixed values. It is made visible in
RFC1340 and RFC3232, Assigned Numbers. On the other hand at the beginning one might
not overlook possible inconsistencies when choosing explicit values. Therefore throughout
this document proposed explicit values are denominated as default values (see Table 1
and Table 3). If within the runtime of MUSE no contradiction is detected these values will be
frozen.
The main part of this document is the Layer 2 and 3 functional description of the home gateway. The physical layer of the 1st mile is not a central part of the specification, but the
Transmission Convergence (TC) sub-layer is considered. For reference two examples for
physical layer interfaces are given, one electrical (SHDSL) and one optical.
Management protocols such as ELMI, OSGI, SNMP are not covered, but configuration parameters are listed. This simplifies further work on home gateway management.
Control plane functions such as signalling protocols are expected to be done in the terminal
and are not described in this document. Control messages use data path connections and no
special signalling connection. A control flow may share a connection with another control flow
or with a data flow. It could also use a dedicated connection. The QoS of the control flow
must be selected accordingly.
1.1 Strategy
MUSE has the goal to establish GSB, an (industry) standard solution for broadband access
networks. It will have added value services to be competitive against other solutions. Therefore MUSE will provide solutions for multi-service, QoS, security and other innovative features. These features must be offered at low cost, which means that maximum synergy must
be exploited from existing systems. For example use of Ethernet brings the economy of scale
from the LAN market into the access network.
Enhanced functionality means also additional complexity. Strategy is to concentrate the additional functions in a few points of the system. For example in the Access Network additional
functions will be located at the border, so that core components are not affected. In the CPE
the strategy is to implement all MUSE specific functions in the Home Gateway. Terminals
connected to the Home Gateway should not be adapted. Standard terminals like (IP) phone
and PC shall be connected to the Home Gateway and benefit from MUSE features.
18/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
19/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
The QoS solution exploits the capabilities of Ethernet equipment, in particular the strict priority scheduling defined in 802.1p. Four of the eight priorities are used for the QoS solution. At
the network border per-connection policing must be implemented, a feature which is not supported by standard Ethernet equipment, but can be added easily at this point. At the network
border the rates tend to be low as well as the number of connections.
Implementation of the high-end QoS solution over slow access lines needs special measures
to be taken. These are segmentation in the TC layer (ATM or PTM with pre-emption) and restrictions on the number of independent flows. A detailed elaboration is given in Appendix 6.4.
The Access Network Provider NAP is responsible of the last mile. Loop tests are initiated by the NAP.
The Packager provides a complete (triple play) service bundle to the customer. The
Packager has mainly an accounting role; the customer gets one single bill for all services from the Packager which is based on billing data collected by the CP. It has
no technical knowledge of the network.
Each of the providers needs a counterpart in the CPE. NAP, CP and Packager exist only
once, but many ASP and NSP may be connected.
20/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Network
Service
Provider
Application
Service
Provider
Customer
Application
Service
Provider
Content
Provider
Packager
consumer
Connectivity
Provider
Application Service /
Content Provider
Customer
Access
Network
Provider
Regional
Network
Provider
Packager
Network Provider
Figure 2: The business role model that was introduced in DA1.1 [2]
The differentiated provider roles influence the structure of the home gateway. For comparison with ISDN the network termination was separated logically in NT1 and NT2, which are
controlled by network operator and customer, respectively. In MUSE this model must be expanded. There will be a termination for the NAP and one for the CP and one termination per
ASP/NSP. These terminations can be somewhat associated to OSI layers, for example the
NAP termination is Layer 1, CP termination Layer 2 and ASP/NSP terminations Layer 3. In
this document the network terminations for NAP and CP, NT1 and NT2 respectively, are primarily considered.
21/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
MAC@ known
in Access
Network
NT2 (RGW)
ST3
CPN
optional
L3 Termination
(e.g. NAT)
n 1
n 1
optional
optional
Ethernet
Ethernet
L3 routing
Forwarding &
Scheduling
n 1 Switching 1 1
Filtering
Filtering
QoS Scheduling
MAC termination
QoS Tagging
VLAN ID known
in Access
Network
Access Gateway AGW
NT1 (B-NT)
1 1
Rate
Adaptation
TC Layer
Filtering
Phy
Termination
ST2
Tcn
T1
RG
Data relay
L3
IP
IP relay
ETH
PHY
PHY
PHY
PHY
Ethernet over
Access Network
specific technology
Ethernet
+ VLAN
Ethernet
MAC relay
802.1P/Q
ETH
ETH
PHY
PHY
ETH relay
PHY
TC
PHY
Service Data
ETH
PHY
All the functional groupings are situated in equipment located at the customer premises.
So the conglomerate of all this equipment is called Customer Premises Equipment (CPE)
and it is interfacing to the first Access Node in the access network.
The grouping of sub-blocks into blocks is introduced for compatibility with DSL Forum
nomenclature (B-NT and RG). It does no preclude any implementation.
22/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
The protocol stacks at the bottom of Figure 3 describe the data path. The default protocol stack is IP over Ethernet. One exception is Service Data over Ethernet for the application MPEG over Ethernet. This option avoids Layer 3 processing of high speed video
data.
Not all functional blocks need to be present, nor do functions need to be implemented in
separate devices. When several functions are integrated in a single physical device, related protocol stacks may be collapsed. These stacks are coloured light grey in the diagram.
ST2 is a termination for L2 service (e.g. MPEG over Ethernet) and performs service related network independent functions.
ST3 is a termination for L3 service. All transport framing is removed and service related
data is available for processing. ST3 may include coding and decoding, signaling, etc.
Both ST2 and ST3 can be located in the terminal (as in the case of a PC) or in a Service
Gateway (as in the case of an ATA).
The numbers between the functional blocks indicate the cardinality of the functions, e.g.
there is always exactly one NT1 per access line, but there can be multiple (n) ST2.
Media indicated by Y and Z in the protocol stacks are not necessarily Ethernet. Y may be
any IEEE standard transport technology with compatible MAC addresses. Z can be any
transport technology.
23/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
Re-assembly
& Packet
Scheduling
Filtering
TC Rx
TC-
PHY - Rx
Home
Network
Access
Network
Filtering
RG
TC - Tx
Segmentation
& Segment
Scheduling
PHY - Tx
24/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
The 802.1P VLAN frame is needed by the NT1 as traffic class identifier. The P-bits in the
VLAN are used for this purpose. The VLAN ID is transparent for the NT1. In upstream direction the (optional) Segmentation & Segment Scheduling unit interprets the P-bits to assign
incoming packets to queues. In addition to the four traffic class queues a dummy queue is
provided to discard packets of certain P-bit combinations. For example 111 is used for control traffic which should not leave the home LAN. Mapping of P-bits to queues is programmable, but default values are given (see Table 1).
Note that packet format is always identical in upstream and downstream direction.
Rate adaptation is needed in the NT1. For example in case of ADSL packets in upstream
direction enter the NT1 with 10 or 100Mb/s, but leave the NT1 at the WAN side with about
1Mb/s. This discrepancy may lead to packet loss, but with the MUSE QoS concept only
packets of Best Effort type are lost. As long as the line rate does not fall below a minimum
value packets of higher traffic classes are not dropped. The minimum line rate is configured
by the NAP. It is assumed that the NAP will analyse an access line and introduce some
safety margin before deciding on the minimum rate.
In case the line rate falls below the minimum rate an error message must be issued to the
NAP and also to the customer network. An intelligent Residential Gateway could intercept
the error message to find out which application will be affected. Individual error messages
could then be forwarded to selected terminals.
Another error message must be issued in case upstream data transmission is not possible at
all. The physical Layer has two possibilities to detect this error. Either the link is not synchronised or in training mode or the far end indicates a reception error (for example Remote Defect Indication RDI).
TC Sub-layer: provides framing required on the physical access link. There are two options,
ATM and PTM mode.
In case of ATM four VCs are used which are terminated on both sides of the access line.
Only over the access line Ethernet packets are encapsulated in ATM as shown in Figure 5.
Ethernet Layer 2 is not terminated at NT1 side nor at the access node side.
25/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Ethernet
Access Line
NT1
Access Node
QoS mapping
QoS mapping
Ethernet MAC
Ethernet MAC
RFC2684
RFC2684
AAL5 SAR
AAL5 SAR
ATM
PHY
Ethernet
ATM
ADSL
PHY
Access
NT1
Access Node
Ethernet
Ethernet
QoS mapping
QoS mapping
Ethernet MAC
Ethernet MAC
PTM-TC
PHY
PTM-TC
ADS
PHY
26/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Ethernet
Access Line
NT1
Access Node
IPv6
Ethernet
IPv6
QoS mapping
AAL5 SAR
Ethernet MAC
ATM
ADSL
PHY
AAL5 SAR
QoS mapping
ATM
Ethernet MAC
PHY
Mandatory/ Optional
Comment
M
M
O
O
O
Configured by NAP
Preconfigured in NT1; default:
ATM-TC
Auto-configured from table
Auto-configured from table
Auto-configured from table
O
O
O
O
O
O
O
O
O
27/70
IST - 6th FP
Contract N 507295
Project Deliverable
Parameter
Mandatory/ Optional
Comment
O
O
O
Discard packet
Select queue=1 (Best Effort)
Select queue=1 (Best Effort)
Up-/ Downstream
Up / Dn
Dn
Comment
VLAN tagged Ethernet frames are not commonly used in home networks
B)
C)
The NT2 shapes the packet stream in upstream direction. In case the access line
rate is (slightly) lower than the shaping rate a backpressure signal is needed.
Over an external Ethernet interface the only means to backpressure are pause
frames. However, this mechanism needs a significant amount of buffer in the
NT1.
28/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
The Ethernet Switching block of the NT2 has multiple ports towards the home network and
one port towards the NT1. Ethernet frames can be switched among residential network ports.
Hence the NT2 can be considered as an Ethernet switch with a special NT1 port. This port
does accurate filtering and shaping to the uplink rate of the access line. The NT1 port also
does VLAN tagging.
For optimised shaping the rate of the NT1 port must exactly match the upstream access line
rate. Within a box or component this is easy to realise. With an external interface between
NT1 and NT2 the Ethernet pause frame mechanism could be used (see also issue C" in
Section 2.2). Another option is to set the shaper rate slightly lower than the upstream access
line rate. A message protocol is needed to notify the NT2 about rate changes of the access
line (retraining). At residential ports Ethernet packets without VLAN are assumed.
At the NT1 port the Ethernet frames in both directions are VLAN tagged. According to IEEE
802.1ad [6] a VLAN tag is inserted between Source-MAC and EtherType field. It has 32 bit
with the following structure:
TPID
P-bits
16 bit
3 bit
VID
12 bit
With:
TPID: identifier for VLAN tagged frame. For customer (C-)VLAN its value is fixed to 0x8100.
For service (S-)VLAN the value is to be defined.
P-bits: Priority bits. Indicate the User_priority of a packet.
According to [4] the traffic types in IEEE LANs is defined as follows:
User_priority
Acronym
Traffic Type
BK
Background
Spare
0 (Default)
BE
Best Effort
EE
Excellent Effort
CL
Controlled Load
VI
VO
NC
Network Control
29/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
The VLAN tag contains two independent fields with different meanings. The VID indicates the
service, which is related to the destination of a packet. The P-bits indicate the QoS of a
packet. It is assumed that MUSE access network architecture will keep these fields orthogonal. For example two packet streams with the same VID, but different P-bits will both reach
the same destination, but with different QoS. (In the MAC tables of the Ethernet switches in
access and aggregation network only one entry will be needed for both flows. The switch
ports will treat the flows with different priorities.) Therefore the NT2 should generate both
fields independently.
In some access network scenarios the VID is not used, but only the (destination) MAC address (McCircuit). In these cases the NT2 sets the VID to zero. Only the P-bits must be generated.
To obtain the VLAN ID two possible methods are presented here.
If services are statically configured the list will be permanent. Changes only occur
when the customer subscribes a new service or un-subscribes a service. For each
service connection there will be one entry in the list. In this case entries could be updated via management protocols (e.g. ELMI).
In case service connections are established dynamically on demand the list will be
updated by some signalling protocol (e.g. XML). See Figure 12.
In an Ethernet based (Layer 2) access network the NT2 will learn one MAC address
per edge node.
In case of an IP based (Layer 3) access network the NT2 will learn only the MAC address of the access node.
30/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
This mode works in case of priority tagged VLAN. It does not need any configuration or signalling, but has the disadvantage that packet streams could occupy the (scarce) upstream
bandwidth which are discarded later at the access node. This is due to the fact that the access node filters packets at IP Layer.
For example a terminal could issue two packet flows to the same edge node, one with Best
Effort and one with Real Time traffic class. Both have the same destination MAC address (of
the edge node) and both are accepted by the NT2. But the access node could discard the
Real Time flow if it is not enabled. Hence this flow produces unwanted load on the uplink. It
is in the responsibility of the customer to avoid such a situation.
P-bits: the P-bits can be generated independently from the VID in case of IP. Both IPv4 and
IPv6 headers have a ToS byte which contains the 6-bit DiffServ code point field. Three selected DSCP values are associated to GSB traffic classes. The values are preconfigured as
shown in Table 3. All other DSCP combinations are associated to the Best Effort class. Each
of the four traffic classes has a fixed pattern of the P-bits associated (see Table 3). For Best
Effort traffic the value is 000.
In case the payload of the Ethernet packet is not IPv4 or IPv6 the P-bits could be obtained
from a MAC table.
TPID: the NT2 uses a pre-configured value to generate the TPID.
CFI:
This bit is always set to 0 when the NT2 generates the VLAN tag.
In downstream direction the VLAN tag is removed at the NT1 port without further action.
Some obvious filtering can be done, for example packets with non-IP payload would be discarded.
L3 Routing block:
This functional block is responsible for Layer 2 termination and Layer 3 routing. In case a
home router is used it is represented by this block. In bridging mode this block does not exist.
Optionally this block may change to another Layer 2 technology, for example from Ethernet
to Bluetooth.
The Routing block does not have any MUSE specific function. An off-the-shelf commercial
home router can be used in case it is implemented as separate physical entity. If it is contained in the residential gateway standard routing functionality according to RFC791 (IP) and
RFC1812 (Router Requirements) is implemented.
L3 Termination block:
IP termination: the L3 address may be changed here and the frames may be routed further
into the home network, or delivered directly to the CPN/ST3.
In case of a home router with NAPT this block contains the NAPT function. In case of a
bridged gateway the L3 termination moves into the terminal.
31/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Parameter
Default value
Comment
0x8100 (C-VLAN)
16-bit field
101010
101110 (EF)
100010 (AF)
Up-/ Downstream
Comment
32/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
3 IMPLEMENTATION OPTIONS
In this chapter the CPE Functional Block model (Figure 3) is checked for consistency by applying it to some special configurations.
Especially important are configurations which consist of different boxes. Unlike a complete
residential gateway in one box such configurations need interfaces which are fully interoperable.
Typically some network operators might install NT-boxes in households which are preconfigured for GSB.
The simplest configuration with a NT box is that only one device is connected to it, an IP
phone. The next obvious configuration is an IP phone and a PC. Usually the PC is connected
via the IP phone (Figure 9). Finally a standard home router may be connected to the NT box.
In the following the CPE functional blocks of Figure 3 are mapped to these applications. It
will turn out that the NT box ideally should contain NT1 and part of NT2.
The NT Box is controlled by the network access provider NAP and may even be owned
by the NAP. For example the NAP will perform loop tests.
For fibre based first mile technologies the physical connection is difficult to establish. A
permanent connection is needed.
Many terminals such as telephone and PC are either already existing and/ or their functionality can not be influenced by MUSE. It is difficult to add MUSE specific features to
these terminals. This argument is investigated in the following for some important terminals.
Cost saving: todays high integration allows to implement all functions in a few components.
Business case: the routing gateway is considered as a consumer product with short life
cycles
33/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
3.1.1 PC
The PC is driven by Intel and Microsoft. The interfaces are given, mainly 10/100baseT, USB
and WLAN. The operating system is Windows. It includes TCP/IP and higher protocol stacks.
Modifications at this level are difficult as they are possible via registry only, which can only be
done by experts. At intermediate level for example browser plugins could be distributed for
free for consumers enabling them access to MUSE services. Finally at the application level
new programs can be written or existing programs adapted. However, this can only be expected later, once GSB has had some market success.
One major challenge will be the mediation between the two different worlds. The PC operating system assumes a connectionless world where all servers are permanently accessible.
Conversely the MUSE access network is connection based. One or more connections must
be configured to the respective service providers.
If the user tries to access the Internet when no connection is setup the NT Box could return
an error message such as the DSCP message destination unreachable. Otherwise the PC
would have to wait for a timeout.
As an alternative solution a permanent best effort connection to the Internet could be configured (always-on feature).
Analogue
Phone
Line
3.1.3 IP Phone
The IP phone is certainly not widely deployed, but it is considered as the phone of the future.
Falling prices on the one hand and added value functions on the other hand will proliferate
the IP phone especially for technically aware subscribers.
A basic scenario will have to be considered where an IP phone and a PC are connected to a
NT box. IP phones usually have two Ethernet RJ-45 pugs, so that this configuration does not
need any extra hub or switch.
34/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
10/100
PC
baseT
10/100
IP
Phone
baseT
Access
NT Box
Line
RJ11 plug
S
L
I
C
ST3
Conversion
Codec
pack/depack
L3
Term. 1 1
L3 routing
Scheduling
2 1
Filtering
MAC termination
3-port
Ethernet 1 1
Switch
Ethernet
Forwarding & 1 1
Filtering
QoS Scheduling
QoS Tagging
Rate
Adaptation
TC Layer
Phy
Termination
U
10/100
base-T
MAC &
PHY
RJ45 plug
NT-Box
35/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
4 MANAGEMENT PLANE
4.1 Management Responsibilities
The introduction of several business roles (see Figure 2) brings additional complexity to the
management of the various functional blocks. One example scenario is shown in Figure 11.
Control over the functional blocks is authorised to the respective service providers. The NT1
is controlled by the NAP, for example in case of ADSL via the EOC. The Connectivity Provider CP controls the NT2 via ELMI. It provides the IP address either by itself or from the
Packager. In both cases duplicate IP addresses are avoided. This would be the case if the
ASPs would provide IP addresses independently. The Service Terminations STa...c are controlled by the respective ASP or NSP. As there is transparent IP connectivity some control
protocol over IP will be selected or defined.
Functional blocks normally are not allowed to read out relevant data from other blocks. However, some exceptions could be defined. For example the NT2 could be allowed to access
part of the management data base of NT1. In order to adjust the upstream schedulers the
NT2 must be allowed to access the upstream rate of NT1. Other possible parameters such
as bit error rate etc. will be decided on a case by case basis. These Layer 1 management
parameters will be defined in a data format which is independent on the type of first mile
technology.
The whole management issue needs to be worked out further.
STa
L3+ protocol
ASP/NSPa
STb
L3+ protocol
ASP/NSPb
STc
L3+ protocol
ASP/NSPc
NT2
ELMI
CP
EOC
NAP
IP adr.
Packager
Read only
NT1
36/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
37/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
1.
End to end visibility on L2 between BRAS and CPE (with or without a PPP or DHCP
session being established)
2.
Unique point to point connection between CPE and BRAS within layer 2 for addressing
customer connection(s)
3.
Use of a default Loop Back ID when addressing the connection endpoint at the CPE,
combined with connection ID which assigns the virtual connection between CPE and
BRAS. This provides a unique addressing scheme for DSL connections between CPE
and BRAS
(Administering the CPEs MAC addresses is to complex for operation in a mass market
environment due to the fact that various CPEs could be connected to the open Uinterface)
DSL lines are identified in an ATM based network by a one to one mapping between DSL
line and ATM VPI/VCI between BRAS and DSLAM (single VCC model).
Basically in the static ATM approach each customer connection is described similar to a
leased line scenario with four parameters, BRAS ID, physical port ID, ATM VP and VC. The
virtual path identifier consists of 8 to 12 bits and addresses a virtual path which contains several virtual circuits which identify specific customer connection. The VC addresses must not
be unique at all (only per VP) because they are relevant for the point to point connection
only.
2.3.2
38/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
IEEE specifies an OAM sub layer as an option. This addressing scheme requires also a
unique loop back address per loop back end point.
Conclusion
Identifying DSL lines by ATM provides full control by the operator, whereas using CPE MAC
addresses to do so (in order to trigger an OAM request like a Loop Back test) is expected to
be much more complicated.
Layer1 and Layer2 managed by network operator Network Termination (NT) approach
If an operator needs to identify the CPE by a unique address he needs to get the information
about the CPE.
ATM and Ethernet use different forwarding paradigms. ATM uses a label swapping connection oriented forwarding mechanism. ATM loopback assumes a connection and the integrity
of the connection is verified by a successful loopback of the OAM cell inserted into a particular VCC or VPC.
Ethernet uses a destination based forwarding paradigm whereby the destination MAC address needs to be known to verify Ethernet layer connectivity. An Ethernet loopback would
verify integrity via successfully getting a response from a message directed towards a specific MAC address. The provider does not administer customer MAC addresses, therefore
mechanisms would be required to learn or discover this information (and track corresponding changes).
ATM default Loop Back ID provides the ability to check DSL access end-to-end via layer 2
between BRAS and CPE based on a virtual connection scheme (VPI/VCI value). This can be
performed without requiring a specific CPE addressing scheme, which greatly simplifies operation for the network operator.
39/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
Layer 3 parameters
o
o
o
Functions located in the Router Gateway block can use user accessible parameters to control the functionality of the NT1.
40/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
5 CONTROL PLANE
For the control plane 4 service models are proposed in WPA2 (see TF1 document [3] or the
public overview presentation [7]). All of them follow the generic approach outlined in Figure
12. The terminal originates a request for a QoS flow via application layer signalling (e.g. SIP,
H.323). A mediator translates it into network layer signalling which is network technology dependent. At the end of the setup process the terminal is informed via application layer signalling. It is assumed that the home gateway is also informed about the successful connection
setup process. For this last step there are two options:
A) The home gateway intercepts the application layer signalling acknowledge message
B) The home gateway receives a separate network layer signalling acknowledge message (e.g. XML).
Application layer signalling
Mediator
Network
Control
Home Gateway
Terminal
Option B
Option A
Figure 12: Service Connection set-up Signalling
Further work on control plane issues for home gateway is depending on the selected service
model.
41/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
6 APPENDIX
6.1 Home network technologies: USB
6.1.1 Overview
The Universal Serial Bus (USB) is an interface standard for interconnecting peripheral devices to a computer. Up to 127 devices can be connected to a single USB bus. USB allows
hot plug/unplug of devices.
2 versions of USB standard are available:
USB 1.1
USB 2.0 (Hi-Speed USB)
USB 2.0 is fully compatible with USB 1.1 and uses the same cables and connectors.
USB supports 4 modes of operation for transferring data:
Control transfers are typically used for command and status operations. They are essential
to set up a USB device with all enumeration functions being performed using control
transfers. They are typically bursty, random packets, which are initiated by the host and
use best effort delivery. The packet length of control transfers in low speed devices must
be 8 bytes, high speed devices allow a packet size of 8, 16, 32 or 64 bytes and full speed
devices must have a packet size of 64 bytes
Interrupt transfers are typically non-periodic, small device "initiated" communication requiring bounded latency. An Interrupt request is queued by the device until the host polls the
USB device asking for data.
The maximum size of data payload size is 8 bytes for low-speed devices, 64 bytes for
full-speed devices and 1024 bytes for high-speed devices
Isochronous transfers occur continuously and periodically. They typically contain time sensitive information, such as an audio or video stream. If there were a delay or retry of data
in an audio stream, then you would expect some erratic audio containing glitches. The
beat may no longer be in sync. However if a packet or frame was dropped every now and
again, it is less likely to be noticed by the listener.
The maximum size of data payload can be up to 1024 bytes for USB 2.0 (1023 for USB
1.1)
Bulk transfers can be used for large bursty data. Such examples could include a print-job
sent to a printer or an image generated from a scanner. Bulk transfers provide error correction in the form of a CRC16 field on the data payload and error detection/retransmission mechanisms ensuring data is transmitted and received without error.
42/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
Bulk transfers will use spare un-allocated bandwidth on the bus after all other transactions have been allocated. If the bus is busy with isochronous and/or interrupt then bulk
data may slowly trickle over the bus. As a result Bulk transfers should only be used for
time insensitive communication as there is no guarantee of latency.
Bulk transfers are only supported by full-speed and high-speed devices. For full speed
endpoints, the maximum bulk packet size is either 8, 16, 32 or 64 bytes long. For highspeed endpoints, the maximum packet size can be up to 512 bytes long. If the data payload falls short of the maximum packet size, it doesn't need to be padded with zeros. A
bulk transfer is considered complete when it has transferred the exact amount of data requested, transferred a packet less than the maximum endpoint size of transferred a zerolength packet.
6.1.2 Bandwidth
USB bandwidth is 12Mbits/s in its 1.1 version and reaches up to 480Mbits/s with version 2.0.
Note the USB 1.1 also supports a low speed mode of 1.5Mbits/s
USB 2.0 extends significantly speed of connections over USB 1.1 capabilities. It is more
adapted to new applications such as digital imaging and allows connection of higher speed
devices.
6.1.4 Latency
Latency can be guaranteed using isochronous transfers only. There is no way to have guaranteed latency when using Bulk transfers.
Isochronous transfers enable pre-negotiated delivery latency.
6.1.6 Limitations
As already exposed above, USB is limited by the reduced distance between devices (30m).
The latency, even in isochronous mode, might affect traffic for time sensitive applications
such as audio or video.
43/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Asynchronous and
isosynchronuous framed
data control
data
control
control
data
L2CAP
Resource
Manager
L2CAP
layer
Channel
Manager
L2CAP
Device
control
services
HCI
Bluetooth controller
Link Manager
layer
Device
Manager
Baseband
layer
Link
Manager
LMP
LC
Link Controller
Radio
layer
RF
Radio
44/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
L2CAP
Channel
Unicast
Logical
Links
Control
(LMP)
Logical
Transport
ACL
User
(L2CAP)
SCO
Physical
Links
Active
Physical link
Physical
Channel
Inquiry scan
channel
Page scan
channel
Broadcast
Basic
piconet
ESCO
Stream
ASB
PSB
Parked
Physical link
Adapted
piconet channel
45/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
The logical link control and adaptation protocol (L2CAP) supports higher-level protocol multiplexing, packet segmentation and reassembly, flow control, error control and the conveying
of quality of service information. This protocol is not used for unframed streaming data such
as voice.
Traffic symmetry
asymmetric
ACL
symmetric
SCO
duplex voice
Transmit
Receive
732.2 Kb/s
57.6 Kb/s
57.6 Kb/s
732.2 Kb/s
433.9 Kb/s
433.9 Kb/s
46/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
An ACL link uses a retransmission scheme based on a CRC check to send data. An acknowledgement bit is provided in each packet header. Since 1 time slot is 625 s, and a
slave is allowed to transmit in the time slot after it has received a packet, the delay before
receiving an acknowledgement may be small. But as the quality of the link goes down, this
delay will increase and may become too large due to the high number of retransmissions. In
order to support isochronous data on a link with variable delay, the old undelivered data can
be flushed and the link controller is forced to take the next data instead.
A poll interval, that is defined as the maximum time between transmissions from the master
to a particular slave on the ACL logical transport, is used to support bandwidth allocation and
latency control.
These parameters managed at the LM-level are reflected in some of the QoS parameters
available at the L2CAP level. The QoS parameters available at the L2CAP level are:
Token Rate
Peak bandwidth
Delay Variation
In addition, Bluetooth provides a 64Kb/s synchronous SCO link that is used to carry audio
data. An SCO link reserves time slots in the hopping pattern so that the bandwidth is guaranteed.
6.2.6 Limitations
Interference. Interference of other devices in the ISM band can strongly reduce the
link quality. A problem case is for example a gateway that needs support an SCO
channel over Bluetooth and also acts as an 802.11b/g access point. Collaboration
mechanisms are absolutely necessary, but do not guarantee a transparent coexistence of both technologies. This topic is further described in more detail in the
DB3.1 Part II: Access Gateway document.
47/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Bandwidth. The current maximal speed of 723 Kb/s is low in comparison to for example the 802.11g standard. Within a piconet, the master is the bottleneck for all traffic.
User interaction. To connect to a device, a user has typically to go through the following steps: discovery of devices, select device to connect to, select service to connect to, enter PIN code and get authorized. Effort is needed to make this whole process user-friendly and to avoid that the user needs too much knowledge of the inner
workings of the Bluetooth technology.
File
Transfer
Serial
Port
Dial-up
FAX
Cordless
Telephony
Intercom
Object
Push
Synchroniza
tion
Generic Object
Exchange Profile
IP Network
access
Profiles
Protocols
RFCOMM
(Serial)
Telephony Control
(TCS.BIN)
Object
Exchange Protocol
BNEP
L2CAP
Figure 15: Relation between upper stack protocols and most common profiles
802.11b
802.11g
802.11a
Max. Speed
11 Mbps
54 Mbps
54 Mbps
Modulation
CCK
OFDM
Frequencies
48/70
5 Ghz band
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
802.11
The original 802.11 standard specified three different physical layer solutions; a Direct Sequence Spread Spectrum scheme and a Frequency Hopping Spread Spectrum scheme
both providing 1 or 2 Mbps throughput in the 2.4 GHz ISM band - and a third scheme for Infrared based systems. Of these the DSSS scheme has had the most commercial success.
6.3.2.2
802.11b
The 11b annex to the base standard was published in 1999 providing 5.5 and 11 Mbps data
rates using a spread spectrum technique called Complementary Code Keying. The attainment of >10Mbps transmission rates was the trigger which ignited adoption of the technology.
6.3.2.3
802.11a
The 11a annex to the base standard was also published in 1999 but has taken rather longer
to translate to significant adoption in the marketplace. This annex provides a physical layer
solution based on OFDM modulation for the U-NII bands between 5.15 and 5.825 GHz. The
available data rates are 6, 9, 12, 18, 24, 36, 48, and 54 Mbps.
6.3.2.4
802.11g
The 802.11g annex is expected to be officially ratified during 2004. Products based on the
final drafts are however already available. 802.11g provides a higher rate extension of the
existing 11b rates in the 2.4GHz band. Typical implementations make use of the OFDM
modulation applied in the 11a standard to provide rates of 6, 9, 12, 18, 24, 36, 48, and 54
Mbps in addition to the 11b rates. The standard provides for an alternative solution based on
PBCC modulation.
49/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Throughput [Mbit/s]
6 Mbit/sec
9 Mbit/sec
12 Mbit/sec
18 Mbit/sec
24 Mbit/sec
36 Mbit/sec
48 Mbit/sec
54 Mbit/sec
0
1000
2000
3000
4000
50/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
10
10
Lower
Modulation
Rate
Shorter
Packets
10
-1
10
-1
PER
PER
10
-2
10
mode3
-2
mode4
mode6
mode7
mode8
-3
10
15
Eb/No
20
25
10
-3
10
12
14
16
18
20
22
24
26
28
30
Eb/No
6.3.4 Latency
As the discussion of the 802.11 MAC access mechanism should make clear, predicting latency in an 802.11 system is not possible, since it is entirely dependent on randomised contention with an unknown and uncontrolled set of terminals. The original standard made provision for a Point Coordination Function which could provide for guaranteed access to the medium under AP control. This functionality is not required for WiFi certification and has rarely
been implemented. The 802.11e standard, which is work in progress, specifies two basic approaches to achieving QoS in an 802.11 network. The first, Enhanced Distributed Contention
Function (EDCF), enhances the basic 802.11 distributed access mechanism to provide statistically prioritised access to certain traffic classes. The prioritised technique is labelled WME
(Wireless Multimedia Extensions) by the Wifi Alliance. Whilst providing useful discrimination
for delay-sensitive traffic, it is not capable of providing bandwidth or latency guarantees. The
second, Hybrid Coordination Function (HCF), is an enhancement of the Point Coordination
Function (PCF) which is intended to provide a capability to reserve bandwidth for delay sensitive flows. Medium Access based on the HCF is planned to be adopted by the WiFi Alliance
under the title WSM (wireless scheduled multimedia).
51/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
AIFSN
Cw min
Cw max
(def = 31)
(def = 1023)
TXOP Limit
(802.11b)
TXOP Limit
(802.11a/g)
AC_BK
31
1023
AC_BE
31
1023
Legacy
31
1023
AC_VI
15
31
6.016ms
3.008ms
AC_VO
15
3.264ms
1.504ms
23)
52/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
These parameters may be flexibly controlled by the access point, which regularly broadcasts
the current parameter set in broadcast beacons. The intent is that a QoS enabled AP can
use these mechanisms in an adaptive way to maintain QoS guarantees as the network load
changes, but of course the definition of an algorithm to satisfactorily achieve this is not a trivial proposition.
Mapping to
Access Category
(AC)
Transmit Queues
Per queue
channel access
functions with
internal collision
resolution
The HCCA frame sequences can occur within the Contention Free Period or the Contention Period (this means that an AP which does not use PCF procedures can flexibly switch between EDCA and HCCA exchanges)
Within a granted TXOP the terminal may transmit multiple frames provided the overall
TXOP is not exceeded
53/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
New frame exchange sequences allow for more efficient frame acknowledgement
strategies
Like the legacy PCF, the HCF has privileged access to the medium because it is permitted to
transmit after a shorter IFS than any (E)DCF terminal. Under control of the HCF (a Controlled
Access Phase CAP), a sequence of frame exchanges can be maintained, with SIFS delays
between frames. HCCA supports parameterized QoS, where specific QoS flows from applications can request scheduled TXOPS and tighter control of latency and scheduling.
54/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Terminal 1
Terminal 2
FE
FE
FE
First
HGW
Terminal N
Mile
CO
FE
N independent Sources
Home network
FE = Fast Ethernet (100Mb/s)
Figure 21: Upstream traffic model
The output port must have some buffering, as packets from different, independent sources
can arrive simultaneously, even if the sum of average rates of each source fits into the upstream bandwidth of the access line. Packet bursts must be stored temporarily in an output
port specific buffer.
55/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
the transmission delay over the transmission links (including eventual interleave delays over xDSL; it is also referenced as propagation delay with 5s/km),
the de-jitter buffer in the terminal. It is set to the maximum value of the jitter.
As transmission delay and node processing delay are fixed the only means to reduce the
end-to-end delay is to minimise the jitter.
The usual method for QoS support is to separate packet flows according to their QoS class
and store them in different queues as shown in Figure 22. These queues are served by a
multiplexer that prioritises queues with low jitter packet streams.
Current target of MUSE is to align with 3GPP and ITU-T QoS classes. Both have 4 delay priorities. Hence 4 queues are implemented in the downstream port Buffer (Figure 22). The two
loss priorities in both standards translate into queue dimensioning. MUSE strategy is to offer
only low packet loss service, even for loss tolerant applications.
Buffer
1
First
High
Mile
Prio
FE
Serving
3
Prio
Low
4
Prio
Flow
Packet
Detection
Queues 1..4
Priority
Multiplexer
56/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
The last mechanism is particularly problematic for low rate transmission lines. Assume for
example that the transmission of a maximum size packet of 1500 bytes has just started when
a high priority packet enters an empty queue. In case of a 1Mb/s ADSL upstream link the
long packet needs 12 ms for transmission. To reduce this time there are pre-emption
mechanisms such as:
Use of different ATM VCs: the waiting time reduces to the transmission time for the
first cell (53byt segment), which is 0.42ms for 1Mb/s.
Use of PTM-TC with pre-emption option according to G.992.3 Annex K.4: waiting time
reduces to one 65byte segment which is 0.52ms.
Abort of the long frame and immediate insertion of the high priority packet: this
method leads to frequent packet losses of the low priority flow. It is not considered
further.
Fragmentation at Layer 3. This method leads to inefficient packet size for bulky data
transmission. It is not considered further.
VoIP
Packets
200byte
Serving
Pre-emption segment
Prio
53/65byte
Max. size Ethernet packet
Priority
1500byte
Multiplexer
57/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
With Figure 23 calculation methods to obtain the maximum number of flows N and the
queue length are derived. For this purpose the following variables are introduced:
LinkRate .............. link rate in b/s
N .......................... number of independent flows
QueueSize........... queue length of high priority queue
SegmentSize ....... given by segmenting mechanism; 53byte for ATM, 65byte for PTM
TC, 1500byte for Ethernet
PacketSize........... maximum packet size
MaxDelay............. maximum delay a packet experiences in the output port
MinDelay.............. minimum delay a packet experiences in the output port
MaxJitter .............. maximum jitter.
The jitter is defined as the difference between maximum and minimum forwarding delay.
From Figure 8.3 the maximum delay is experienced by the last arriving (blue) packet. It has
to wait for a segment from the low priority queue and three packets to be transmitted, including itself:
MaxDelay = (SegmentSize + N x PacketSize) / LinkRate
If on the other hand all queues were empty the minimum delay is experienced by the packet,
the time to be transmitted itself:
MinDelay = (1 x PacketSize) / LinkRate
The difference between both is the jitter:
MaxJitter = (SegmentSize + (N-1) x PacketSize) / LinkRate.
{1}
From {1} one can see that there is a lower bound for MaxJitter for N=1:
MaxJitter SegmentSize / LinkRate,
which can be resolved for LinkRate:
LinkRate SegmentSize / MaxJitter.
{4}
Equation {4} shows that there is a minimum LinkRate for a certain jitter limit. The lowest jitter
can be achieved with 53-byte ATM cells.
Equation {1} is resolved for N to obtain the maximum number of flows possible for a given
link rate:
N = Integer[ (MaxJitter x LinkRate SegmentSize) / PacketSize + 1]
{1a}
Once N is known the required queue size for the high priority queue according to Figure 8.3
obviously is:
QueueSize = N x PacketSize
{2}
With equations {1a} and {2} the queue length and the maximum number of allowed flows can
be calculated. However, for large values of N this deterministic view can be completed by a
statistical one.
58/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
For values of N beyond 10 it is more and more unlikely that a large number of independent
sources send packets simultaneously. For a given loss probability the maximum allowed load
of an infinite number of flows (N -> ) can be calculated using the M/D/1 model. Results for
packet loss probability 10-11 and 10-7 are shown in Figure 24 and Figure 25, respectively.
With N -> equation {2} can not be used any more for queue size calculation. Replacing N
by {1a} and neglecting SegmentSize and the +1 term leads to
QueueSize = MaxJitter x LinkRate
{3}
Assume for example N=20 is the result of {1a} with a given set of parameters. The deterministic view says that 20 independent flows can share the queue with zero loss probability,
provided that their load sum is <100%. The statistical view according to Figure 24 says that
an infinite number of flows can share the queue with up to ca. 52% load sum for a loss probability of 10-11. The statistical view is usable for links with high rate, used for node interconnection. The number of flows allowed on these links must not be controlled by admission,
just the total rate.
1
0,9
0,8
0,7
0,6
0,5
0,4
0,3
0,2
0,1
0
1
10
100
1000
Figure 24: Maximum load per QueueSize given in multiples of PacketSize for packet loss
probability 10-11
59/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
1
0,9
0,8
0,7
0,6
0,5
0,4
0,3
0,2
0,1
0
1
10
100
1000
Figure 25: Maximum load per QueueSize given in multiples of PacketSize for packet loss
probability 10-7
60/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
1Mb/s
Case A
ADSL path 1
ADSL path 2
Case B
0.9Mb/s
ADSL path 1
0.1Mb/s
61/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Typically the bandwidth reserved for the low jitter path will be low. Hence in this example a
1Mb/s ADSL link is split into one 0.1Mb/s path for one low jitter connection and a second
path with 0.9Mb/s for all the other connections. This solution is compared to one single
1Mb/s path. In both cases the end-to-end transfer time (including de-jitter buffer) of a 200byte
voice packet is considered. In both cases the interleave delay is 8ms. This value is reasonable in case of omnipresent 100Hz noise. With no interleaving at all (fast path) sporadic bit
errors can not be avoided. Hence 8ms seems to be a practical value.
A) Two path solution
In this case the packet has no waiting time for downstream transmission. The transmission of the 200byte over the 0.1Mb/s link, however, lasts 16ms. The jitter from access
and core network is expected to be below 1ms. The de-jitter buffer compensates this jitter
with a 1ms delay.
Resulting end-to-end delay for the high priority path: 16ms+8ms+1ms=25ms.
B) Single path solution
In this case the packet in worst case has to wait for a 53byte ATM cell from a lower priority queue to be transmitted. At 1Mb/s this lasts 0.42ms. Then the voice packet is transmitted over the access line which lasts 1.6ms. The accumulated jitter from access and core
network is less than 1ms.
Resulting end-to-end delay: 0.42ms+1.6ms+8ms+1ms=11ms.
The single path solution B has much lower end-to-end delay. Even if fast mode is used instead of interleave mode the two path solution would be slower (17ms).
Even if the two path solution has two equal paths of 0.5Mb/s the resulting end-to-end delay is
longer than in the single path solution (12.2ms).
Other disadvantages of the two path solution are the performance degradation for all flows
using ADSL path 1, the lower overall link usage and the missing flexibility.
Conclusion: the single path ADSL mode is preferred versus two path mode.
Max. Packet
loss rate per
node
Low Latency
200 byte
1 ms
10-10
10%
Real Time
1500 byte
30 ms
10-10
60%
Guaranteed
Rate
9000 byte
900 ms
62/70
10
-10
<100%
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Traffic class
Max. Packet
loss rate per
node
Best Effort
LinkRate [Mb/s]
QueueSize [byte]
200
400
600
1 000
10
2 000
50
10 000
Unlimited
12 500
10-11
63/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
The LinkRate values in Table 2 are rounded to 100kb/s, the proposed rate granularity.
For the 100Mb/s value both the deterministic view with up to 50 flows and the statistic approach according to Figure 24 are listed. For QueueSize calculation in unlimited case formula {3} has been used. With QueueSize expressed in multiples of PacketSize the allowed
load for an unlimited number of flows is looked up in Figure 24.
At implementation it is recommended to limit the queue size to the calculated value and discard whole packets in case of overflow (partial packet discard PPD). This takes into account
that for inelastic QoS classes timing behaviour is more important than data integrity.
{1a}
{1b}
Using these equations and {2} some values have been calculated in Table 10:
No of flows N
LinkRate [Mb/s]
QueueSize [byte]
1 500
3 000
4 500
6 000
7 500
21
31 500
226
100 (load<100%)
339 000
Unlimited
337 500
10-11
64/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
{1a}
{1b}
Using these equations and {2} some values have been calculated in Table 11:
No of flows N
LinkRate [Mb/s]
QueueSize [byte]
9 000
18 000
27 000
36 000
45 000
54 000
10
90 000
51
10 (load<100%)
459 000
Unlimited
10 (load<77%)
450 000
10-11
Unlimited
4 500 000
10-11
Table 11: Some key values for a 900ms Guaranteed Rate class
For the 10Mb/s link both deterministic and statistical view are given. In statistic view the
maximum aggregate load is 77% of the 4Mb/s, hence ~3Mb/s. The remaining ~1Mb/s are
available for best effort traffic.
Queue size calculation for the statistic view is analogous to {3}:
QueueSize = 900ms x LinkRate x 0.4
{3}
With QueueSize expressed in multiples of PacketSize the allowed load for an unlimited number of flows is looked up in Figure 24.
Note that the calculated buffer sizes for the Guaranteed Rate class are minimum values and
can be implemented larger with in the aim of data integrity. For example the calculated
queue size could be used as threshold. When the queue fill exceeds this threshold new arriving packets are discarded, but partially received packets are still accepted (early packet discard EPD).
65/70
Consortium Confidential
Project Deliverable
IST - 6th FP
Contract N 507295
Up to now independent terminals in the Home Network have been assumed. Flows arriving
at the Home Gateway are uncorrelated.
However, terminals in a household or SOHO usually are located within short distances.
Their packet flows could be synchronised. For example by collecting packets from three IP
phones in a circular manner, for example 1/2/3, 1/2/3, 1/2/3, etc. as shown in Figure 28. The
uncorrelated flow is shown for reference in Figure 27. However, the procedure could lead to
additional delays within the NT2.
Phone 1
Large jitter
ADSL upstream
NT1
N
T
2
Phone 2
Phone 3
Phone 1
Zero jitter
NT1
ADSL upstream
N
T
2
Phone 2
Phone 3
66/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
As another example if three analogue phones are connected to a Home Gateway correlated
upstream packet streams could be achieved by synchronising the packetisation circuits
within the Home Gateway.
The issue of correlating upstream flows should be further explored.
6.4.9 Conclusion
In this section the realisation of the QoS classes of MUSE for access line rates up to 10Mb/s
is studied. An important result is that an appropriate segmentation mechanism is absolutely
necessary to support the desired low jitter values. ATM turns out to be a valuable solution.
PTM TC mode with pre-emption for the highest priority class could be an alternative which
remains to be investigated.
KM
fibres
100BASE-LX10
ONU/OLT
100
10
dual
100BASE-BX10-D
OLT
100
10
single
100BASE-BX10-U
ONU
100
10
single
1000BASE-LX10
ONU/OLT
1000
10
dual
1000BASE-BX10-D
OLT
1000
10
single
1000BASE-BX10-U
ONU
1000
10
single
Received
Wavelength
67/70
Pout
min
Sensitivity
max
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Wavelength
[nm]
100BASE-LX10
100BASE-BX10-U
1260-1360
1260-1360
1000BASE-LX10
1000BASE-BX10-U
Wavelength
[nm]
1480-1580
1260-1360
1260-1360
1480-1500
min
[dBm]
max
[dBm]
-15
-25
-14
-28,2
-9
-19,5
-9
-19,5
Return loss
Tbd.
Operation of regenerators between the SDSL modem and the DSLAM is optional.
Support of all data rates with the corresponding granularity according to the used
application specific Transmission Protocol Specific Transmission Convergence (TPSTC) layer is required.
68/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Support for a rate adaptive mode using the Power Measurement Modulation
Session PMMS (Line Probe) is required. The support of the current condition target
margin is mandatory, the support of the worst case condition target margin is optional.
The value for the target noise margin (min. required noise margin) has to be
configurable according to ETSI TS 101 524. For the configuration the DSLAM is
the master.
The support of the optional reduced power mode, the deactivation and the
warm-start is reserved for future use.
The Minimum longitudinal conversion loss and the maximum longitudinal component of the
output signal for a SDSL modem shall be according ETSI TS 101 524, chapter 11.3.
Return loss
The minimum return loss of a SDSL modem shall be according to ETSI TS 101 524, chapter
11.2.
69/70
Consortium Confidential
IST - 6th FP
Contract N 507295
Project Deliverable
Pin
1
2
3
4
5
6
7
8
Allocation
not allocated, reserved for future use: U-RS2 a
not allocated, reserved for future use: U-RS2 b
not allocated
U-RS a
U-RS b
not allocated
not allocated
not allocated
70/70
Consortium Confidential