IP Quality of Service Architecture
Quality of Service Architecture
ASG00xx- Architectural View
Release: Version 0.93
04 October 2005
Page 12 / 120
Natural DemandDelay VariationCapacity Limit
Document No:
ASG00xx
Version Number and Status:
0.94
Final Draft
Publication Date:
3 October 2005
Review Date:
Type:
Standard
Security Classification:
Confidential
IP Quality of Service Architecture
Architectural View
Version 0.94
Customers, Partners and Employees
Network Environment
Integration Services & Profile
Core Business Functions
Service Delivery
Resource and
Technology
Management
CPE
CPN
CPT
CNE
CAM
CAN
AAS
AAN
ACS
NE
NC
EDN
NC
INN
Edge
Mesh
CLNE
Distribution
Aggregation
Customer
Access
Core
Customer
Customers, Partners and Employees
Network Environment
Integration Services & Profile
Core Business Functions
Service Delivery
Resource and
Technology
Management
Customers, Partners and Employees
Network EnvironmentNetwork Environment
Integration Services & Profile
Core Business Functions
Service DeliveryService Delivery
Resource and
Technology
Management
Resource and
Technology
Management
CPE
CPN
CPT
CNE
CAM
CAN
AAS
AAN
ACS
NE
NC
EDN
NC
INN
CPE
CPN
CPT
CNE
CAM
CAN
AAS
AANAAN
ACS
NE
NC
EDNEDN
NC
INNINN
Edge
Mesh
CLNE
Distribution
Aggregation
Customer
Edge
Mesh
CLNE
Distribution
Aggregation
Customer
Access
Core
Customer
AccessAccess
CoreCore
CustomerCustomer
Approver
Name
Signature
Date
Greg Patchell
Supported by
Warren Lemmens
Use of This Document
This document is the copyright of Telecom Corporation of New Zealand Limited ("Telecom") and must not be disclosed or reproduced in whole or part without Telecom's prior written consent. This document is strictly confidential to Telecom, the EDS Telecom Account and the Alcatel Account Team as defined by the relevant contractual relationships and their non-disclosure requirements. Any changes modifications or updates should be requested via the Telecom Technology Strategy & Architecture group.
This document should be printed in colour. It makes extensive use of colour coding.
Revision History
V
Animated Architectures.gif
ersion
Reason
Reviser
Date
0.1
Document Created.
Michael S Cox
01/03/2005
0.7
First draft for internal peer review.
Michael S Cox
27/05/2005
0.8
Second draft for external peer review.
Michael S Cox
10/06/2005
0.9
Third draft incorporating feedback, added detail to availability, added detail to network and resource control and added detail to network dimensioning.
Michael S Cox
Roger Aitkin
Paul Dagger
Evan Stanbury
30/06/2005
0.91
Further feedback incorporated and extensions made to the services section.
Michael S Cox
Roger Aitkin
16/07/2005
0.93
Incomplete or missing sections extended, and/or removed. General document organisation cleanup.
Michael S Cox
Paul Dagger
31/08/2005
0.94
Removal of all remaining comments and interim text. Creation of Glossary.
Michael S Cox
03/10/2005
Summary of Contents
3Summary of Contents
5Summary of Tables
6Summary of Figures
8Glossary
121Document Guide
121.1Document Purpose and scope
131.2Intended Audience
131.3Intended use of this document
141.4Relative Authority of this Document
151.5Note to Reviewers
151.6Note to version 1.0
172Introduction
182.1Background
192.2Input Considerations
192.2.1High Level Requirements
192.2.2Restrictions and Considerations
202.2.3Detailed and Specific Requirements
213Network Intrinsic QoS
213.1Performance Specification Framework
223.1.1The IETF Performance Measurement Framework
243.1.2Common Performance Measurement Terminology
253.1.3Recommended Performance Metrics
323.1.4Recommended Framesizes
333.1.5Statisitical Sampling and Summarisation
353.2Performance Management Framework
363.2.1Traffic Presentation and Conformance
473.2.2Transmission and Distance
483.2.3Network Redundancy, Resiliency and Availability
503.2.4Network Technology and Infrastructure
563.2.5Traffic Aggregation and Dimensioning
703.2.6Services, Classes and Accesses
783.2.7Network Control
903.3Network QoS Reference Architecture
913.3.1TNZ Transport Classes Architecture
953.3.2TCNZ Group Network CoS Standard
983.3.3Monitoring and Managing Transport GoS Targets
1003.4Examples
1003.4.1Designing and Implementing End-to-end Services
1014References
1025Appendices
1025.1Recommended Core, Access and Aggregation Network Availability Standards
1045.1.1Normal Availability Standard by Domain
1055.1.2High Availability Standard by Domain
1065.1.3Bad year probability and asymptotic availability as a Function of Distance
1065.1.4Availability Standard by Network Element
1075.2Recommended TCNZ Network Performance Targets
1085.2.1TNZ Local GoS
1095.2.2TNZ National GoS
1105.2.3TNZ International GoS
113Summary of Requirements
Summary of Tables
95Table 1: TCNZ Transport Class Identification Standard
96Table 2: Recommended Router Configuration for PQ and WRR Queuing
97Table 3: Recommended Router Configuration for PQ Queuing Only
97Table 4: Recommended Router Configuration for WRR Queuing Only
108Table 5: Performance Reporting Standard by Category
108Table 6: Margin-Target Performance Thresholds
109Table 7: TNZ Local Access GoS Targets
110Table 8: TNZ National Core GoS Targets
112Table 9: TNZ International GoS Targets
Summary of Figures
17Figure 1: End-to-end User, Application, Network and Process QoS
18Figure 2: Value-based pricing model
22Figure 3: Intrinsic, assessed and perceived end-to-end QoS
28Figure 4: Definition of Packet Network Connectivity
30Figure 5: Definitions of Degradation and Unavailability
35Figure 6: QoS Cloud Reference Architecture
37Figure 7: RFC2475 Traffic Conditioner Block Diagram
37Figure 8: Stages of Traffic Conditioning within a Congestion Management System
38Figure 9: Traffic Conditioner Classifier Section
40Figure 10: Traffic Conditioner Meter and Marker Sections
41Figure 11: Traffic Conditioner Discard and Queuing Sections
43Figure 12: Queuing System Components
47Figure 13: Effect of Frame size and Bandwidth on Delay
59Figure 14: Hypothetical data providers diurnal cycles (workday, weekly, annual)
67Figure 15: Transition from Unconditioned to Conditioned Traffic Streams
68Figure 16: Example Transport Clouds Architecture
68Figure 17: Service to Transport Class Policy Mapping and eventual Servicing
69Figure 18: Example of a Transport Class Exclusive Conditioner
69Figure 19: Application or Service Gateways within a Transport Cloud
70Figure 20: Application and Service Specific Components
71Figure 21: General customer data service categories
72Figure 22: End-to-end Customer Services and Transport Clouds
72Figure 23: High-level Content Communication Service
73Figure 24: High-level Application Communication Services
73Figure 25: High-level Application Gateway Connection Services
73Figure 26: High-level Network Connection and Distribution Services
74Figure 27: High-level Network Access and Transport Services
75Figure 28: Two-stage Traffic Management Policy
76Figure 29: Example Hierarchical Queuing and Distributed Servicing
77Figure 30: Complex Hierarchical Scheduler with Priority Support
78Figure 31: Successive aggregation of traffic streams towards termination points
79Figure 32: Managing Capacity, Utilisation, Performance and Price
81Figure 33: Reference Network Services
86Figure 34: Reference Resource Management Architecture
90Figure 35: EAF Domains and Network Reference Architecture Alignment
90Figure 36: QoS Cloud Reference Architecture (Customer, Access, National, International )
91Figure 37: QoS Network Reference Architecture (CAI, ANI, ADI and NNI reference points)
100Figure 38: Example of End-to-End Service in an International Context
106Figure 39 Probability of a bad year for access aggregation as a function of distance
106Figure 40 Asymptotic Availability of a bad year for access aggregation as a function of distance
108Figure 41: TNZ Local Access
109Figure 42: TNZ Na
