>> Study Group 13 : Next Generation Networks
Question 4/13 - Requirements and framework for QoS for NGN
(Continuation of Question16/13)
- Motivation
Specialized application-specific networks increasingly converge to general
packet networks supporting voice, data and multimedia applications. Certain
packet networking technologies (e.g., IP), however, avoid, by design, any in-built
mechanism for creation and maintenance of circuits that guarantee application or
network performance. As such, support of quality of service in a general-purpose
packet network or the NGN is a complex matter, compounded by several additional factors:
- Requirement for maximal resource utilization
- Highly-distributed intelligence and applications end to end
- Co-existence of multiple networking technologies and QoS mechanisms end to end
- Involvement of multiple administrative domains end to end
The complexity of the issue necessitates a systematic study of QoS enablers and QoS
architectures that integrate QoS enablers to deliver application or network performance
as needed in various environments, such as access networks or end to end. The draft
Recommendation Y.1291 has defined an initial architectural framework for QoS support in
packet networks and served as the basis for developing New Recommendations (e.g., Y.123.qos
and Y.e2eqos) on environment-specific QoS architectures.
- Question
Study items to be considered include, but are not limited to:
- What new Recommendations or enhancements to existing Recommendations are needed to provide for additional QoS enablers (such as centralized admission control and resource management, and adaptive QoS mechanisms based on measurements) in packet networks and the NGN?
- What new Recommendations or enhancements to existing Recommendations are needed to allow for various QoS enablers to interact with each other as needed?
- What new Recommendations or enhancements to existing Recommendations are needed to provide safeguards to QoS support?
- What new Recommendations are needed to support QoS in packet access networks?
- What new Recommendations are needed to enable the comprehensive, end-to-end support of QoS in packet networks and the NGN employing different QoS mechanisms across multiple administrative domains?
- What additional protocol requirements (including further extensions to the Session Initiation Protocol (SIP)) are needed in order for the delivery of assured QoS content to be possible in NGNs?
- What additional protocol requirements are necessary for content hosts or application service providers (ASPs) to initiate the provision of assured QoS on a per session basis? Note in order to be scalable any signalling system or protocol identified should take into account of the following consideration:
- The protocol should be “lightweight” and little or no session or state information should need to be maintained by the ASP.
- Only limited state information should need to be maintained by the network.
- Bandwidth reservations should automatically time out if packet flows are not maintained.
- The protocol should only need to be implemented at the network edges (typically in the BRAS and content host servers) and should rely on established QoS assurance mechanisms (such as MPLS) in the core network.
- Tasks
Tasks include but are not limited to:
- New Recommendation (Y.123.qos) on a QoS architecture for Ethernet-based IP access networks
- New Recommendation (Y.e2eqos) on an end-to-end QoS architecture
- New Recommendations on other environment-specific QoS architectures as necessary
- Maintenance and enhancement of Y.1291
- Relationships
Recommendations: Y-series
Questions: Relevant Questions on NGN networking, architecture and performance
Study Groups: ITU-T Study Groups 2, 9, 11, 12, 15, 16, 19
Standardisation bodies fora and consortia:
ITU-R
IETF Internet, Routing, and Transport Areas
3GPP and 3GPP2 as appropriate
DSL Forum
IEEE 802 LAN/MAN Standards Committee
» List of Questions «
|
|
