Seminar on ITU-T hot topics for Seminar on ITU-T hot topics for Standardization Standardization

(Mar del Plata, Argentina, 2 (Mar del Plata, Argentina, 2 September 2009)September 2009)

Interoperability technical means, Interoperability technical means, services, classes and parameters services, classes and parameters

of QoSof QoS

A. Koucheryavy, ZNIISA. Koucheryavy, ZNIIS

General Director Advisor,General Director Advisor,

ITU-T SG11 Vice ChairmanITU-T SG11 Vice Chairman

2

ContentContent

1.1. ITU-T activitiesITU-T activities2.2. Testing methodology historyTesting methodology history3.3. Technical means interoperability Technical means interoperability 4.4. Model NetworksModel Networks5.5. The services interoperabilityThe services interoperability6.6. The QoS interoperabilityThe QoS interoperability7.7. DiffServDiffServ8.8. IPTV trafficIPTV traffic9.9. BenchmarkingBenchmarking10.10. QoS classesQoS classes11.11. ConclusionsConclusions

3

ITU-T activitiesITU-T activities

Resolution 76 “Studies related to Resolution 76 “Studies related to conformance and interoperability testing, conformance and interoperability testing, assistance to developing countries, and a assistance to developing countries, and a possible future ITU mark program” was possible future ITU mark program” was approved at the World approved at the World Telecommunication Standard Assembly Telecommunication Standard Assembly (Johannesburg, 2008). (Johannesburg, 2008).

4

““The interoperability of international The interoperability of international telecommunication networks was the telecommunication networks was the main reason to create ITU in the year main reason to create ITU in the year 1865 (International Telegraph Union), 1865 (International Telegraph Union), and that this remains one of the main and that this remains one of the main goals in the ITU strategic plan”.goals in the ITU strategic plan”.

5

What is the What is the

interoperability today?interoperability today?

6

Recommendation Y.101 “Global Recommendation Y.101 “Global Information Infrastructure terminology: Information Infrastructure terminology: Terms and definitions” Interoperability is Terms and definitions” Interoperability is the ability of two or more systems or the ability of two or more systems or applications to exchange information and applications to exchange information and to mutually use the information that has to mutually use the information that has been exchanged”. This Recommendation been exchanged”. This Recommendation was approved at March 2000. It’s so long was approved at March 2000. It’s so long ago from today point of view.ago from today point of view.

7

We will consider further interoperability We will consider further interoperability issues for the technical means, services issues for the technical means, services and QoS context on the base of the last and QoS context on the base of the last searching and developing progress and searching and developing progress and Study Group 11 ITU-T activities. The main Study Group 11 ITU-T activities. The main focus for interoperability issues will be focus for interoperability issues will be interoperability supporting by testing interoperability supporting by testing procedures.procedures.

8

The NGN concept is the real The NGN concept is the real implementation plan for network implementation plan for network modernization today. The full NGN modernization today. The full NGN definition could be found in the definition could be found in the Recommendation Y.2001. The NGN Recommendation Y.2001. The NGN concept includes the some QoS guarantees concept includes the some QoS guarantees levels in according with Y.1540 and Y.1541 levels in according with Y.1540 and Y.1541 and very widely services set, in principle and very widely services set, in principle unlimited. Both of them points request to unlimited. Both of them points request to consider interoperability as a complex consider interoperability as a complex definition, including technical means, definition, including technical means, services and QoS interoperability, not only services and QoS interoperability, not only systems or applications.systems or applications.

9

The testing methodology history.The testing methodology history.

1.1. 1995, ITU-T (X.290), ETSI (ETS 300406) – 1995, ITU-T (X.290), ETSI (ETS 300406) – conformance testing based on the conformance testing based on the ISO/IEC 9646 and specific ISO/IEC 9646 and specific telecommunication criteria and features.telecommunication criteria and features.

2.2. 1999, ETSI (TR 101667) – Network 1999, ETSI (TR 101667) – Network Integral (Interconnection) testing (end-to-Integral (Interconnection) testing (end-to-end, node-to-node).end, node-to-node).

10

The conformance testing goal is the The conformance testing goal is the specification profiles verification. The specification profiles verification. The network testing goal is the correct, network testing goal is the correct, integrity and reliability services for users.integrity and reliability services for users. The table 1 ETR 101 667 defines the users The table 1 ETR 101 667 defines the users of both methodologies. The conformance of both methodologies. The conformance testing methodology users are the vendors testing methodology users are the vendors at first place and Administrations and at first place and Administrations and operators optionally, the network testing operators optionally, the network testing methodology users are the methodology users are the Administrations and operators only.Administrations and operators only.

11

Technical means interoperabilityTechnical means interoperability

The methodology of the model network The methodology of the model network using for network testing was proposed using for network testing was proposed at ITU-T in 2004 (Q.39xx series).at ITU-T in 2004 (Q.39xx series).The model network is the network, which The model network is the network, which simulates the capabilities similar to those simulates the capabilities similar to those available in present telecommunication available in present telecommunication networks, has a similar architecture and networks, has a similar architecture and functionality and users, the same functionality and users, the same telecommunication technical means.telecommunication technical means.

12

The NGN testing experience.The NGN testing experience.

ZNIIS Model Network (2004, Softswitch) ZNIIS Model Network (2004, Softswitch) 1016 tests – 8.1% unsuccessful tests 1016 tests – 8.1% unsuccessful tests

Plug Test ETSI (Slovenia, 2008, IMS)Plug Test ETSI (Slovenia, 2008, IMS)

410 tests – 18% unsuccessful tests.410 tests – 18% unsuccessful tests.

(Joint ITU-T/ETSI meeting, Moscow, ZNIIS, (Joint ITU-T/ETSI meeting, Moscow, ZNIIS, 10 April, 2009).10 April, 2009).

13

The Q.39xx Recommendation list.The Q.39xx Recommendation list.

Q.3900Q.3900 – Model Network Architecture – Model Network ArchitectureQ.3901Q.3901 – NGN (Softswitches) – NGN (Softswitches)Q.3903Q.3903 – Data base – Data baseQ.3904Q.3904 – NGN (IMS) (draft) – NGN (IMS) (draft)Q.3905Q.3905 – IPTV – IPTVQ.3906.1Q.3906.1 – Broadband access (wired) – Broadband access (wired)

(draft)(draft)Q.3906.2Q.3906.2 - Broadband access (WiFi) (draft) - Broadband access (WiFi) (draft)Q.3906.3Q.3906.3 - Broadband access (WiMax) - Broadband access (WiMax)

(draft)(draft)

14

The services interoperability The services interoperability testingtesting

The ITU –T recommendations on the The ITU –T recommendations on the services interoperability testing are services interoperability testing are absent today. Furthermore, the service absent today. Furthermore, the service scenarios for important NGN services are scenarios for important NGN services are absent too. It’s very complicated problem absent too. It’s very complicated problem today, but during ITU-T study period today, but during ITU-T study period 2009-2012 the key recommendations set 2009-2012 the key recommendations set for service interoperability testing should for service interoperability testing should be developed.be developed.

15

The detailed requirements for the services The detailed requirements for the services implementation should be developed. It could be implementation should be developed. It could be include:include:

service definition and features;service definition and features; network capabilities;network capabilities; network architecture and function elements;network architecture and function elements; access network types and user equipments;access network types and user equipments; service delivery scenarios;service delivery scenarios; call flows;call flows; reference points and protocols;reference points and protocols; service implementation on the non-IMS network;service implementation on the non-IMS network; interworking with otherinterworking with otherss services services..

16

The testing scenarios, list and types of The testing scenarios, list and types of tests for NGN TS1 basic call and tests for NGN TS1 basic call and supplementary services, NGN TS1 supplementary services, NGN TS1 streaming services and NGN TS1 streaming services and NGN TS1 multimedia services should be developed multimedia services should be developed as separately ITU-T Recommendations.as separately ITU-T Recommendations.

17

The Q.39xx recommendation list The Q.39xx recommendation list (services testing)(services testing)

Q.3915 Q.3915 – TS1 (draft)– TS1 (draft)

Q.3916Q.3916 – Testing scenarios, list and types of – Testing scenarios, list and types of tests for NGN (TS1) basic call and tests for NGN (TS1) basic call and supplementary services,supplementary services,

Q.3917Q.3917 - Testing scenarios, list and types of - Testing scenarios, list and types of tests for streaming services (TS1),tests for streaming services (TS1),

Q.3918Q.3918 - Testing scenarios, list and types of - Testing scenarios, list and types of tests for multimedia services (TS1).tests for multimedia services (TS1).

18

The QoS interoperabilityThe QoS interoperability

The many networks are realized NGN The many networks are realized NGN concept. At first, of course, it’s the basic IP concept. At first, of course, it’s the basic IP network. Furthermore, it could be WiFi network. Furthermore, it could be WiFi (based on Ethernet technology), IPTV and (based on Ethernet technology), IPTV and so on.so on.

19

The some QoS mechanisms were The some QoS mechanisms were developed for QoS supporting at IP-based developed for QoS supporting at IP-based networks. The recommendation Y.1291 networks. The recommendation Y.1291 which was approved in 2004 determine which was approved in 2004 determine four standardized approaches for QoS four standardized approaches for QoS supporting: Integrated services (IntServ), supporting: Integrated services (IntServ), Differentiated services (DiffServ), Differentiated services (DiffServ), MultiProtocol Label Switching (MPLS), MultiProtocol Label Switching (MPLS), IPCablecom Dynamic QoS.IPCablecom Dynamic QoS.

20

DiffServDiffServ

The service level agreement (SLA) concept The service level agreement (SLA) concept and the wireless broadband access and the wireless broadband access technologies development (WiFi and technologies development (WiFi and WiMax) are shown, that DiffServ WiMax) are shown, that DiffServ mechanism could be using for QoS mechanism could be using for QoS supporting in the heterogeneous NGN supporting in the heterogeneous NGN networks. If we can see the IEEE 802.11e networks. If we can see the IEEE 802.11e or QoS requests at the pooling-based or QoS requests at the pooling-based services for WiMax, we will found that the services for WiMax, we will found that the QoS classes based on DiffServ concept.QoS classes based on DiffServ concept.

21

There are three PHB classes:There are three PHB classes: Assured Forwarding (AF PHB);Assured Forwarding (AF PHB); Expedited Forwarding (EF PHB);Expedited Forwarding (EF PHB); Best Effort or Default PHB.Best Effort or Default PHB.

22

EF PHB is targeted to applications which EF PHB is targeted to applications which require strict guarantees of end-to-end require strict guarantees of end-to-end delay. The EF PHB applications request the delay. The EF PHB applications request the QoS level, which compare with the QoS QoS level, which compare with the QoS level for unloaded network.level for unloaded network.

23

AF PHB has been designed for a range AF PHB has been designed for a range applications which require different QoS applications which require different QoS guarantees. There are four classes of PHB guarantees. There are four classes of PHB identification codes within the AF PHB identification codes within the AF PHB group. Within each class there are three group. Within each class there are three distinct DiffServ Code Points (DSCP) with distinct DiffServ Code Points (DSCP) with different packet drop precedence.different packet drop precedence.

24

The mapping between Y.1541 QoS classes The mapping between Y.1541 QoS classes and DiffServ mechanism are determined in and DiffServ mechanism are determined in the recommendation Y.1291. The EF are the recommendation Y.1291. The EF are corresponding with Y.1541 classes 0 and corresponding with Y.1541 classes 0 and 1,1, AF – classes 2, 3 and 4 respectively, AF – classes 2, 3 and 4 respectively, and Best Effort – class 5.and Best Effort – class 5.

The mapping between VLAN (Virtual LAN The mapping between VLAN (Virtual LAN in accordance with IEEE 802.1) and in accordance with IEEE 802.1) and DiffServ DSCP are recommended in the DiffServ DSCP are recommended in the Y.2112.Y.2112.

25

IPTV trafficIPTV traffic

The traffic flows types are really The traffic flows types are really complicated for NGN. They are complicated for NGN. They are

self-similar as usually. The self-self-similar as usually. The self-similar traffic generation at the similar traffic generation at the model network is a real problem model network is a real problem today. We will consider IPTV traffic today. We will consider IPTV traffic further.further.

26

The IPTV traffic measurements was made The IPTV traffic measurements was made at ZNIIS model network. The actual traffic at ZNIIS model network. The actual traffic of movies named Ohotnik, likely thriller of movies named Ohotnik, likely thriller performed on DVD was analyzed for performed on DVD was analyzed for differences times fragments and for differences times fragments and for differences aggregation period in differences aggregation period in processing of measuring data.processing of measuring data.The minimum observation movies The minimum observation movies fragment is the 60s. The fragment fragment is the 60s. The fragment includes 6863 frames, each of frame has includes 6863 frames, each of frame has the length 1356 bytesthe length 1356 bytes

0 10 20 30 40 50

0

0.2

0 .4

0 .6

0 .8

k

r

Autocorrelation function

H=0.48

28

Wavelet transform for Poisson traffic

29

min max

Wavelet transform for measured traffic (fragment 60s)

30

The Q.39xx recommendations listThe Q.39xx recommendations list (for QoS testing)(for QoS testing)

Q.3919Q.3919 – The types of traffic flows which should be – The types of traffic flows which should be generated for voice, data and video on the Model generated for voice, data and video on the Model Network for testing QoS parameters.Network for testing QoS parameters.

Q.3920Q.3920 – The types and list of tests for QoS testing – The types and list of tests for QoS testing on Model networks for traffic-unloaded conditions.on Model networks for traffic-unloaded conditions.

Q.3921Q.3921 - The types and list of tests for QoS testing - The types and list of tests for QoS testing on Model networks for traffic-loaded conditions.on Model networks for traffic-loaded conditions.

Q.3922Q.3922 - The types and list of tests for QoS testing - The types and list of tests for QoS testing for intra-domain connectivity.for intra-domain connectivity.

Q.3923Q.3923 - The types and list of tests for QoS testing - The types and list of tests for QoS testing for inter-domain connectivity.for inter-domain connectivity.

31

BenchmarkingBenchmarking

100

105

110

115

120

125

130

135

0 10 20 30 40 50 60Time (minutes)

Sc

en

ario

Att

em

pts

pe

r S

eco

nd

(S

Ap

S)

0%

2%

4%

6%

8%

10%

12%

14%

System Load Successful Scenario Attempts % Inadequately Handled Scenario Attempts

COM 11-C33-E, SG11 meeting, 19-23 January, 2009, Geneva.ETSI TS 186 008-1, October, 2007

32

Benchmarking Recommendations Benchmarking Recommendations listlist

Q. Bench–IMS–NGN-A Q. Bench–IMS–NGN-A

Q. Bench–IMS–NGN-BQ. Bench–IMS–NGN-B

Q. Bench–IMS–NGN-CQ. Bench–IMS–NGN-C

Q. Perf-Bench-IMSQ. Perf-Bench-IMS

IMS/NGN Performance IMS/NGN Performance Benchmark Part 1:Benchmark Part 1:Core ConceptsCore Concepts

IMS/NGN Performance IMS/NGN Performance Benchmark Part 2:Benchmark Part 2:Subsystem Configurations and Subsystem Configurations and Benchmarks Benchmarks

IMS/NGN Performance IMS/NGN Performance Benchmark Part 3:Benchmark Part 3:Traffic Sets and Traffic ProfilesTraffic Sets and Traffic Profiles

IMS/NGN PerformanceIMS/NGN Performance Benchmark Part 4:Benchmark Part 4:Delay objectives for various Delay objectives for various IMS transactionsIMS transactions

33

Q. Bench-PES NGN AQ. Bench-PES NGN A

Q. Bench-PES NGN BQ. Bench-PES NGN B

Q. Bench-PES NGN CQ. Bench-PES NGN C

PES PerformancePES PerformanceBenchmark Part 1:Benchmark Part 1:Core ConceptsCore Concepts

PES PerformancePES PerformanceBenchmark Part 2:Benchmark Part 2:Subsystem Configurations Subsystem Configurations and Benchmarks and Benchmarks

PES PerformancePES PerformanceBenchmark Part 3:Benchmark Part 3:Traffic Sets and Traffic Traffic Sets and Traffic ProfilesProfiles

34

QoS classesQoS classes

The six QoS classes from 0 to 5 are The six QoS classes from 0 to 5 are defined at the table 2/Y.1541 “Guidance defined at the table 2/Y.1541 “Guidance for IP QoS classes” Recommendation for IP QoS classes” Recommendation Y.1541.Y.1541.

35

The “0” QoS class contents real-time, jitter The “0” QoS class contents real-time, jitter sensitive, high interaction applications. It sensitive, high interaction applications. It could be VoIP and VTC (Video could be VoIP and VTC (Video Teleconference). The same applications Teleconference). The same applications (VoIP, VTC) is the base for ”1” QoS class, (VoIP, VTC) is the base for ”1” QoS class, named “Real-time, jitter sensitive, named “Real-time, jitter sensitive, interactive” as we see, the difference is interactive” as we see, the difference is only between “high interactive” and only between “high interactive” and “interactive”.“interactive”.

36

The Q.39xx recommendation list The Q.39xx recommendation list (for VoIP testing)(for VoIP testing)

Q. Perf-obj test VS IPQ. Perf-obj test VS IP Network PerformanceNetwork Performance

objectives Tests for IP-objectives Tests for IP-based Voice servicesbased Voice services

37

Conclusions.Conclusions.

1.1. The main goal of testing today should be The main goal of testing today should be network testing (interoperability) for network testing (interoperability) for supporting the correct, integrity and supporting the correct, integrity and reliability services for users.reliability services for users.

2.2. This goal could be supported by Model This goal could be supported by Model network methodology.network methodology.

3.3. The interoperability issues include the The interoperability issues include the technical means, services, QoS classes technical means, services, QoS classes and parameters. All of this features and parameters. All of this features create the Global Interoperability, which create the Global Interoperability, which could be tested on the Model network in could be tested on the Model network in complex.complex.