Study Group 13 “Futures Session” Working Party 4

Network Performance and Resource Management

July 25, 2003

Most Active QuestionsQ4/13 -- Broadband and IP related resource management

Q6/13 -- Performance of IP-based networks

Q8/13 -- Transmission error and availability performance

Less Active QuestionsQ7/13 -- B-ISDN/ATM cell transfer/availability performance

Q9/13 -- Call processing performance

Question 4/13 Broadband and IP Related

Resource Management

Accomplishments

• Y.1221 (Traffic and congestion control in IP-based networks )

• I.378 (Traffic and congestion control at the AAL2 )

Goals

• Update I.371 (Traffic and congestion control in B-ISDN) and integrate it with I.371.1 (GFR ATM transfer capability)

•  Add methods and tools for IP TE to Y.1221 (Section 8)

• New Recommendation on traffic/congestion control in MPLS (?)

• New Recommendation on traffic/congestion control in Ethernet (?)

Question 6/13 Performance of IP-Based Networks

Accomplishments  Y.1540 (IP packet transfer/availability parameters)

• Y.1541 (NP/QoS Objectives for IP-Based Services)

Goals• Develop accumulation formulas for all Y.1541 parameters

• Define QoS apportionment procedures for IP-based networks

• Contribute to SG 11 Signaling Rqmts (TRQ.IPQoS.Sig.CS1)

•  Complete Y.MPLSperf (MPLS performance parameters)

•  Complete Y.TCPperf (TCP performance parameters/objectives)

•  Develop Y.ETHperf (Ethernet performance)

Question 8/13 Transmission Error and Availability

Performance

Accomplishments

•  G.821R, G.826R, G.828R, G.829R (PDH error performance)

• G.8201 (OTN error performance)

• G.827R/G.827.1R (CBR path availability)

Goal (?)

• Develop new error performance Rec(s) for services based on 8B10B signals, e.g., Ethernet, fiber channel, ESCON, etc.*

* Coordinate physical (Q8/13) and packet (Q6/13) work

Question 7/13

B-ISDN/ATM Cell Transfer and Availability Performance

Decisions• Expand I.356 to address ATM over ADSL access technology

• Develop I.356 text addressing ATM-IP network interworking

• Replace I.356 “country-based” with “inter-operator” model

Goals (?)•  Implement planned I.356 revisions

•  Develop new Recommendations– I.35AAL2 (Performance of AAL2 switched connections)

– I.35av (B-ISDN/ATM SVC availability)

Question inactive during the current Study Period

Question 9/13 Call Processing Performance

Progress

• I.358R (Call processing performance for B-ISDN SVCs)

• Draft Y.1530 (Call processing performance for voice in hybrid IP networks)

Goals

• Complete Y.1530– Identify call processing protocol(s) for hybrid IP networks

– Specialize existing (generic) parameter definitions

– Specify and allocate performance objectives

• Harmonize Y.1530 with TRQ.IPQoS.Sig.CS1 and E.106/Y.roec

Y.1530 has been hindered by lack of a clear protocol basis

Terminal Terminal

NI to NI QoS (Y.1541) Speed, Accuracy, Dependability Service Availability (Future)

Voice Video Data Call Control

Customer-Perceived QoS Subjective Descriptors Objective Estimators

Voice Video Data Call Control

Network QoSNetwork QoS Network QoS

ControlNetwork

ControlNetwork

BearerNetwork

BearerNetwork

BearerNetwork

ControlNetwork

NINI

(QoS, Flow Signaling)

Issue 1 -- QoS (and Flow) Signaling

Issue 2 -- QoS Measurement in NGNs

NGN Characteristics• Hybrid/Adaptive Infrastructure (ATM, IP, MPLS, Ethernet, …)

• Numerous, Dynamic, and Complex Network Functions – Code, protocol, media, format conversions (some entropy reducing)– Dynamic connectivity and traffic control (mobility, capacity, QoS, ...)– Information collection and distribution (e.g., searching, browsing)

Performance Implications• More Dynamic Performance Boundaries

• More Complex Measurement Issues– ‘Partial Success’ and Non-Discrete Outcomes– Different information at input and output interfaces

Perception-Based, Machine-Based Metrics Needed

TCP(window control)

IP(Diffserve,IP transfer capability)

MPLS

ATM(ATM transfer capability)

SDH(Virtual Container)

Λ(2.4G,10G,40G..)

Fiber(DWDM,CDWM)

Ether(Fast, Giga,)Virtual

Physical

UDP Two VirtualControlsMay notWorkTogether.

API

API will request network to provide a suitable combination of traffic controls.NGN should be adaptive so that it can respond the API’s request.

Issue 3 -- NGN Traffic Management

Summary -- Planning ContextNetwork Performance/Resource Management

Key Technologies and Future Work Areas• IP QoS -- accumulation, apportionment and signalling

• MPLS -- performance, traffic and congestion control

• Ethernet -- parameters, objectives, QoS classes ( SLAs)

• IP/Optical -- network performance, resource management

Major Themes• Network convergence (IP, PSTN, optical, wireless, …)

• QoS and RM interworking among different technologies

• Dynamic QoS control, multi-layer traffic engineering

Cross-cutting, integrative NP/QoS control and resource management standards will be needed