hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Reference load A: intended to represent the normal upper mean level of activity which Administrations would wish to provide for on customer lines and inter-exchange activities Reference load B: intended to represent an increased level beyond normal planned activity levels
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: BA ISDN Basic Access BC Bearer Capability BHCA Busy Hour Call Attempts CAPS Call Attempts Per Second Erl Erlang IMS IP Multimedia Subsystem ISDN Integrated Services Digital Network ISUP ISDN User Part MGC Media Gate way Controller MGW Media Gate Way MHT Mean Holding Time MSAN Multi-Service Access Node NGN Next Generation Networks PES PSTN Emulation Solution NOTE: http://www.utstar.com/files/1647.pdf PI Progress Indicator PRA ISDN Primary Access PSTN Public Switched Telecommunications Network s second SIP Session Initiation Protocol SIP-I SIP with encapsulated ISUP SUT System Under Test tm Mean holding time for originating traffic UDI Unrestricted Digital Information VBD Voice Band Data
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4 Initial benchmark traffic set and traffic-time profile
|
This clause defines the load profiles to simulate ISDN - non-ISDN environments. The data used in this traffic -time profile are based on profiles from Austria and Germany. ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 7
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1 Initial benchmark traffic-time profile
|
Following assumptions are valid for the calculations: The required call processing capacity depends on the number of calls offered to the exchange. The basic formula to calculate the required BHCA is: BHCA = A × 3 600 / tm A = traffic for Reference load A [i.4] tm = mean holding time Access Types Traffic per subscriber [Erl] A = number of subscribers × originating traffic per subscriber BHCA (BHCA = A × 3 600 / tm) CAPS (BHCA/3600) mean holding time [s] POTS Summary 0.02 0,72 (1,2 Note) 0,0002 100 ISDN-BA B-Channel 0,050 1,80 (2 Note) 0,0005 100 Summary 0,100 3,60 0,0010 ISDN-PRA B-Channel 0,5 18 0,005 100 Summary 15 540 0,15 ISUP-Trunk Channel utilization 0,800 28,80 0,0080 100 Summary 24,000 864,00 0,2400 NOTE: The values in brackets are values proposed in ITU-T Recommendation Q.543 [i.4]. Traffic distribution of originating traffic: Transit solution 25 % Intra-MGW 50 % Inter-MGW 25 % Inter-domain (SIP-I) Relation between Voice and Data Traffic Types Voice/VBD 90:10 Relation between fax, data and text modem types 90:5:5 Voice/UDI 99:1 Figure 1: Relation between Voice and Voice Band Data (VBD) Traffic Types ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 8 Figure 2: Relation between data modem types
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.1 MSAN 500 PSTN users
|
• Local exchange with 500 analog subscribers • Originating BHCA • A = number of subscribers × originating traffic per subscriber = 500 × 0,02 = 10 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 360 • Load A = 0,1 CAPS Table 1: MGW Traffic Load for 500 POTS subscriber Type of Call Traffic mix Traffic (Erl) cps Intra-MGW 25 % 2,5 0,025 Inter-MGW 50 % 5 0,05 Inter-domain 25 % 2,5 0,025 Total 100 % 10 0,1
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.2 MSAN 500 POTS/ISDN mixed users
|
• 100 % Voice Traffic • 333 POTS Lines • 166 ISDN Lines ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 9 POTS: - Local exchange with 333 analog subscribers - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 333 × 0,02 = 6,66 Erl - tm = mean holding time for originating traffic = 100 s - BHCA = 240 - Load A = 0,067 CAPS Type of Call Traffic mix Traffic (Erl) cps Intra-MGW 25 % 1,66 0,016 Inter-MGW 50 % 3,33 0,033 Inter-domain 25 % 1,66 0,016 Total 100 % 6,67 0,066 ISDN: - MSAN with 166 ISDN subscribers (2 lines per subscriber =332 lines) Originating BHCA - A = number of subscribers × originating traffic per ISDN subscriber (2 lines)= 166 × 0,10 = 16,6 Erl - tm = mean holding time for originating traffic = 100 s - BHCA = 597 - Load A = 0,166 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 4,15 0,042 Inter-MGW 50 % 8,3 0,083 Inter-domain 25 % 4,15 0,042 Total 100% 16,6 0,166
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.3 MSAN 500 POTS/ISDN mixed users with data traffic
|
• 90 % Voice Traffic • 9 % Fax /Modem Traffic • 1 % Data ISDN Traffic • 333 POTS Lines • 166 ISDN Lines POTS: Voice - Local exchange with 300 analog subscribers - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 300 × 0,02 = 6 Erl - tm = mean holding time for originating traffic = 100 s - BHCA = 216 BHCA - Load A = 0,06 CAPS ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 10 Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 1,5 0,083 Inter-MGW 50 % 3 0,166 Inter-domain 25 % 1,5 0,083 Total 100 % 6 0,06 POTS: VBD Data - Local exchange with 33 analog subscribers (10 % of voice traffic) - Originating BHCA - A = number of subscribers × originating traffic per subscriber = 33 × 0,02 = 0,66 Erl - tm = mean holding time for originating traffic = 120 s (2 pages Horizontal: 200 or 204 scan lines per inch; - Vertical: 200 or 196 scan lines per inch ('Fine') (see note in clause 4.1.9) - BHCA = 0,66 × 3 600 / 120 = 19,8 BHCA - Load A = 0,0055 CAPS ISDN: Voice - MSAN with 163 ISDN subscribers (2 lines per subscriber =326 lines) Originating BHCA - A = number of subscribers × originating traffic per ISDN subscriber (2 lines)= 163 × 0,1 = 16,3 Erl - tm = mean holding time for originating traffic = 100 s - BHCA = 586,8 - Load A = 0,163 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 4,075 0,04 Inter-MGW 50 % 8,15 0,0815 Inter-domain 25 % 4,075 0,04 Total 100% 16,3 0,163 ISDN: VBD Data - Local exchange with 2 VBD subscribers (10 % of voice traffic) - Originating BHCA - A = number of subscribers × originating traffic per ISDN subscriber (2 lines) = 2 × 0,1 = 0,2 Erl - tm = mean holding time for originating traffic = 120 s (2 pages Horizontal: 200 or 204 scan lines per inch; Vertical: 200 or 196 scan lines per inch ('Fine') (see note in clause 4.1.9) - BHCA = 0,2 × 3 600 / 120 = 6 BHCA - Load A = 0,0016 CAPS ISDN: Data 64 Kbit/s; MSAN with 2 ISDN subscribers - 2 parallel channels (2xBA) - tm = mean holding time for originating traffic = 500 s - BHCA= 0,27 ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 11 - Load A = 2 CAPS
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.4 MSAN with 500 ISDN subscribers (2 lines)
|
• 100 % Voice Traffic • A = number of subscribers × originating traffic per ISDN subscriber (2 lines)= 500 × 0,1 = 50 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 1 800 BHCA • Load A = 0,5 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 25 0,125 Inter-MGW 50 % 50 0,25 Inter-domain 25 % 25 0,125 Total 100 % 50 0,5
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.5 MSAN with 1 000 analog subscribers
|
• 100 % Voice Traffic • A = number of subscribers × originating traffic per subscriber = 1 000 × 0,02 = 20 Erl • tm = mean holding time for originating traffic = 100 s • BHCA = 20 × 3 600 / 100 = 720 BHCA • Load A = 0,2 CAPS Type of Call Traffic mix Traffic (Erl) Cps Intra-MGW 25 % 5 0,05 Inter-MGW 50 % 10 0,1 Inter-domain 25 % 5 0,05 Total 100 % 20 0,2
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.6 MSAN / TRUNKING MGW with 16 PRA
|
• 100 % Voice Traffic • A = number of subscribers × originating traffic per subscriber = 480 × 0,5 = 240 Erl • BHCA = 480 × 18 = 8 640 • Load A = 480 x 0,005= 2,4 CAPS
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.7 MSAN/TRUNKING MGW with 16 PRA mixed users with data traffic
|
• 90 % Voice Traffic • 10 % Fax /Modem Traffic ISDN PRA: Voice - A = number of channels × originating traffic per ISDN PRA channel = 432 × 0,5 = 216 Erl - BHCA = 432 x 18 = 7 776 ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 12 - Load A = 432 x 0,005= 2,16 CAPS ISDN PRA VBD Data - Local exchange with 48 analog subscribers (10 % of voice traffic) - A = number of channels × originating traffic per ISDN PRA channel = 48 × 0,5 = 24 Erl - tm = mean holding time for originating traffic = 120 s (2 pages Horizontal: 200 or 204 scan lines per inch; - Vertical: 200 or 196 scan lines per inch ('Fine') (see note in clause 4.1.9) - BHCA = 24 × 3 600 / 120 = 720 BHCA
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.8 Load A = 0,2 CAPS 4.1.8 MSAN/TRUNKING MGW with 100 PRA
|
• 100 % Voice Traffic • A = number of channels × originating traffic per ISDN PRA channel = 3 000 × 0,5 = 1 500 Erl • BHCA = 3 000 × 18 = 54 000 • Load A = 3 000 x 0,005= 15 CAPS
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.1.9 MSAN/TRUNKING MGW with 1024 PRA
|
• 100 % Voice Traffic • A = number of channels × originating traffic per ISDN PRA channel = 30 720 × 0,5 = 15 360 Erl • BHCA = 30 720 × 18 = 552 960 • Load A = 30 720 x 0,005= 154 CAPS NOTE: Group 3 faxes conform to the ITU-T Recommendations T.30 [i.1] and T.4 [i.2]. The horizontal and vertical resolutions are allowed by the T.4 [i.2] standard to vary among a set of fixed resolutions: Horizontal: 100 scan lines per inch: - Vertical: 100 scan lines per inch Horizontal: 200 or 204 scan lines per inch: - Vertical: 100 or 98 scan lines per inch ('Standard') - Vertical: 200 or 196 scan lines per inch ('Fine') - Vertical: 400 or 391 (note not 392) scan lines per inch ('Superfine') Horizontal: 300 scan lines per inch: - Vertical: 300 scan lines per inch Horizontal: 400 or 408 scan lines per inch: - Vertical: 400 or 391 scan lines per inch ('Ultrafine') ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 13 Figure 3: Test Pattern Facsimile Test Chart BW01 [i.3] ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 14
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.2 Initial benchmark traffic set
| |
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.2.1 ISDN/PSTN mixed initial benchmark traffic set
|
Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ ISDN-ISDN Use-Case 1 TS 186 025-2 [2], clause 5.1.1.1 ISDN - ISDN Scenario 1.1 Basic call with BC= speech - enblock sending I_ I_S_1.1 10 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.2 ISDN - ISDN Scenario 1.2 Basic call with BC= speech - enblock sending I_ I_S_1.2 10 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.3 ISDN - ISDN Scenario 1.3 Basic call - overlap sending with BC= speech I_ I_S_1.3 9 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.4 ISDN - ISDN Scenario 1.4 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s I_ I_S_1.4 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.5 ISDN - ISDN Scenario 1.5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s I_ I_S_1.5 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.6 ISDN - ISDN Scenario 1.6 Basic call with BC= 3,1 kHz with PI#3 I_ I_S_1.6 30 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.7 ISDN - ISDN Scenario 1.7 Basic call with BC= 3,1 kHz with PI#3 I_ I_S_1.7 30 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.8 ISDN - ISDN Scenario 1.8 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s, 14,4 kbit/s) I_ I_S_1.8 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.9 ISDN - ISDN Scenario 1.9 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) I_ I_S_1.9 2,25 % Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 15 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ ISDN-ISDN Use-Case 1 TS 186 025-2 [2], clause 5.1.1.10 ISDN - ISDN Scenario 1.10 Basic call with BC= UDI - enblock sending I_ I_S_1.10 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.11 ISDN - ISDN Scenario 1.11 Basic call with BC= UDI - enblock sending I_ I_S_1.11 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.12 ISDN - ISDN Scenario 1.12 called user is user determined user busy I_ I_S_1.12 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.1.13 ISDN - ISDN Scenario 1.13 No answer from the called user I_ I_S_1.13 0,5 % Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 16 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ ISDN-PSTN Use-Case 2 (in combination with use case 3) TS 186 025-2 [2], clause 5.1.2.1 ISDN - PSTN Scenario 2.1 Basic call with BC= speech - enblock sending I_ P_S_2.1 15 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.2 ISDN - PSTN Scenario 2.2 Basic call with BC= speech - enblock sending I_ P_S_2.2 15 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.3 ISDN - PSTN Scenario 2.3 Basic call - overlap sending with BC= speech I_ P_S_2.3 14 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.4 ISDN - PSTN Scenario 2.4 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s I_ P_S_2.4 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.5 ISDN - PSTN Scenario 2.5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s I_ P_S_2.5 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.6 ISDN - PSTN Scenario 2.6 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s) I_ P_S_2.6 0,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.7 ISDN - PSTN Scenario 2.7 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) I_ P_S_2.7 0,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.8 ISDN - PSTN Scenario 2.8 called user is user determined user busy I_ P_S_2.8 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.2.9 ISDN - PSTN Scenario 2.9 No answer from the called user I_ P_S_2.9 0,5 % Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 17 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ PSTN- ISDN Use-Case 3 (in combination with use case 2) TS 186 025-2 [2], clause 5.1.3.1 PSTN - ISDN Scenario 3.1 Basic call. The call is released from the calling user P_I_S_3.1 22 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.2 PSTN - ISDN Scenario 3.2 Basic call The call is released from the called user P_I_S_3.2 22 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.3 PSTN - ISDN Scenario 3.3 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s P_I_S_3.3 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.4 PSTN - ISDN Scenario 3.4 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s P_I_S_3.4 2,25 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.5 PSTN - ISDN Scenario 3.5 Basic call with BC= 3,1 KHz audio - Modem V.90 P_I_S_3.5 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.6 PSTN - ISDN Scenario 3.6 called user is user determined user busy P_I_S_3.6 0,5 % Poisson, mean selected by traffic-time profile TS 186 025-2 [2], clause 5.1.3.7 PSTN - ISDN Scenario 3.7 - no answer from the called user P_I_S_3.7 0,5 % Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 18
|
d3966a0ea81147b6e3bc9145cdba95fe
|
186 025-3
|
4.2.2 PSTN initial benchmark traffic set
|
Use Case Section Test Scenario Scenario ID Type Scenario % of System Load Scenario Arrival Distribution TS 186 025-2 [2], clause 5.1: Session Set-Up/ PSTN- PSTN Use-Case 4 TS 186 025-2 [2], clause 5.1.4.1 PSTN - ISDN Scenario 4.1 Basic call. The call is released from the calling user P_P_S_4.1 44,5 % TS 186 025-2 [2], clause 5.1.4.2 PSTN – PSTN Scenario 4.2 Basic call The call is released from the called user P_P_S_4.2 44,5 % TS 186 025-2 [2], clause 5.1.4.3 PSTN - PSTN Scenario 4.3 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s P_P_S_4.3 4,5 % TS 186 025-2 [2], clause 5.1.4.4 PSTN - PSTN Scenario 4.4 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s P_P_S_4.4 4,5 % TS 186 025-2 [2], clause 5.1.4.5 PSTN - PSTN Scenario 4.5 Basic call with BC= 3,1 KHz audio - Modem V.34 (up to 33,6 kbit/s) P_P_S_4.5 0,5 % TS 186 025-2 [2], clause 5.1.4.6 PSTN - PSTN Scenario 4.6 Basic call with BC= 3,1 KHz audio - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s, 14,4 kbit/s) P_P_S_4.6 0,5 % TS 186 025-2 [2], clause 5.1.4.7 PSTN - PSTN Scenario 4.7 Called user is user busy P_P_S_4.7 0,5 % TS 186 025-2 [2], clause 5.1.4.8 PSTN - ISDN Scenario 4.8 no answer from the called user P_P_S_4.8 0,5 % ETSI ETSI TS 186 025-3 V1.1.1 (2012-10) 19 History Document history V1.1.1 October 2012 Publication
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
1 Scope
|
The present document defines initial benchmark tests through definitions of traffics sets and traffic profiles. The benchmark is defined for the IMS network as a whole, as well as for several subsystems of an IMS network. The benchmark is designed so that nodes composing a subsystem can also be benchmarked alone. The initial benchmark test data defined in the present document include: • Traffic set. • Traffic-time profile. • Benchmark test procedure.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
2 References
| |
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 186 008-1: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 1: Core Concepts". [2] ETSI TS 186 008-2: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks". [3] Recommendation ITU-T Q.3930: "Performance testing of distributed systems - Concepts and terminology". [4] ETSI TS 186 025-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks".
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 3261: "SIP: Session Initiation Protocol". [i.2] Recommendation ITU-T V.152: "Procedures for supporting voice-band data over IP networks". [i.3] Recommendation ITU-T T.38: "Procedures for real-time Group 3 facsimile communication over IP networks". ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 6 [i.4] Recommendation ITU-T V.90: "A digital modem and analogue modem pair for use on the Public Switched Telephone Network (PSTN) at data signalling rates of up to 56 000 bit/s downstream and up to 33 600 bit/s upstream". [i.5] Recommendation ITU-T V.34: "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". [i.6] Recommendation ITU-T V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits".
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
3 Definitions and abbreviations
| |
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in Recommendation ITU-T Q.3930 [3] apply.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AKA Authentication and Key Agreement BC Bearer Capability CC Completion of Communications on No Reply CCBS Completion of Calls to Busy Subscriber CCNR Completion of Calls to No Reply CFB Call forwarding busy CFNR Call forwarding not reply CFU Call forwarding unconditional CPU Central processor unit GW Gateway IHS Inadequately Handled Scenarios IMS IP Multimedia Subsystem ISDN Integrated Services Digital Network MEM MEMory usage PI Progress Indicator PSTN Public switched telephone network PX_IHS % Inadequately Handled Scenarios SIP Session Initiation Protocol SIPP SIPP Simple Internet Protocol Plus SUM Subscription Management TLS Transport Layer Security UDI Unrestricted Digital Information UDUB User determined user busy UE User Equipment XML Extensible Markup Language
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4 Benchmark tests
|
ETSI TS 186 008-1 [1] and ETSI TS 186 008-2 [2] have defined the framework for defining and executing an IMS performance benchmark. The present document specifies a benchmark test, which may be implemented and performed as-is, or which may serve as an example for future benchmark tests developed by a service provider or SUT implementor.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.1 Benchmark test goals
|
A benchmark test may be used either for comparison (e.g. comparing the performance of two products), or for prediction (e.g. the configuration specified for a benchmark test is similar enough to a service providers requirements that the result of the test can be used as an estimate of the performance of their deployed system). ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 7
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.2 Initial benchmark traffic set and traffic-time profile
|
As described in details in ETSI TS 186 008-1 [1], a benchmark test measures the behaviour of a SUT for a specified traffic set and traffic-time profile. A traffic set is composed of a mixture of test scenarios, whose relative frequency of occurrence is specified by traffic set parameters; the traffic-time profile is a specification of how the average arrival rate of test scenarios evolves over the execution of the benchmark test. Tables 1 and 2 represent a generic IMS/PES traffic set and profile covering the major use-cases defined in ETSI TS 186 025-2 [4] and ETSI TS 186 008-2 [2]. The percentage of System Load for each scenario has not been defined, because the load depends on the number of selected use cases. ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 8 Table 1: Initial benchmark traffic set Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) [2], clause 6.1: Registration/ De-registration Use-Case Successful initial registration with unprotected REGISTER requests on the SIP default port values as specified in IETF RFC 3261 [i.1] UC1_SC1 Successful initial registration with IMS AKA as a security mechanism UC1_SC2 Successful initial registration with SIP digest without TLS as a security mechanism UC1_SC3 Successful initial registration with SIP digest with TLS as a security mechanism UC1_SC4 Successful initial registration with NASS-IMS bundled authentication as a security mechanism UC1_SC5 Successful initial registration with GPRS-IMS- Bundled authentication as a security mechanism UC1_SC6 Re-registration - user currently registered UC1_SC7 ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 9 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Re-registration - user currently registered UC1_SC8 Re-registration - user roaming UC1_SC9 Initiated de-registration UC1_SC10 [2], clause 7.1: MMTel fixed access to MMTel fixed access Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC2_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the called user. UC2_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state the Fax transfer on the media is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed. UC2_SC3 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 10 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with Fax with 14,4 kBit/s; This scenario represents the case when in the active call state the Fax transfer on the media is performed and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed. UC2_SC4 Poisson, mean selected by traffic-time profile Basic call - Fax with 14,4 kBit/s with V.152 [i.2] This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC2_SC5 Poisson, mean selected by traffic-time profile Basic call - Fax with 14,4 kbit/s with using the T.38 [i.3] in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC2_SC6 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 11 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC2_SC7 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC2_SC8 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC2_SC9 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC2_SC10 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 12 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC2_SC11 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC2_SC12 Poisson, mean selected by traffic-time profile IMS/PES – IMS/PES [2], clause 7.3 ISDN - ISDN Scenario 1.1 Basic call with BC= speech - enblock sending This use case represents the case when the call establishment using enbloc sending is performed. The call is released from the calling user. UC3_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ISDN - ISDN Scenario 1.2 Basic call with BC= speech - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the called user. UC3_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 13 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN - ISDN Scenario 1.3 Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending is performed. The call is released from the calling user. UC3_SC3 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.4 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. UC3_SC4 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. UC3_SC5 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.6 Basic call with BC= 3,1 kHz with PI#3 This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC3_SC6 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 14 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN - ISDN Scenario 1.7 Basic call with BC= 3,1 kHz with PI#3 This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the called user. UC3_SC7 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.8 Basic call with BC= 3,1 kHz - Modem V.32 [i.6] bis (4,8 kBit/s, 9,6 kBit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC3_SC8 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.9 Basic call with BC= 3,1 kHz - Modem V.34 [i.5] (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC3_SC9 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.10 Basic call with BC= UDI - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the calling user. UC3_SC10 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 15 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN - ISDN Scenario 1.11 Basic call with BC= UDI - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the called user. UC3_SC11 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.12 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user with cause value # 17. UC3_SC12 Poisson, mean selected by traffic-time profile ISDN - ISDN Scenario 1.13 No answer from the called user This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user with the cause value # 18. UC3_SC13 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.1 Basic call with BC= speech - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the calling user. UC3_SC14 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 16 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN - PSTN Scenario 2.2 Basic call with BC= speech - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the called user. UC3_SC15 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.3 Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. UC3_SC15 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.4 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels are performed and the echo cancellers in the GW are not activated. The call is released from the called user. UC3_SC16 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. UC3_SC17 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 17 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN - PSTN Scenario 2.6 Basic call with BC= 3,1 kHz - Modem V.32 [I.6] bis (4,8 kBit/s, 9,6 kBit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC3_SC18 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.7 Basic call with BC= 3,1 kHz - Modem V.34 [i.5] (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC3_SC19 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.8 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy. The network initiates call clearing to the calling user with cause value # 17. UC3_SC20 Poisson, mean selected by traffic-time profile ISDN - PSTN Scenario 2.9 No answer from the called user This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiates call clearing to the calling user with the cause value # 18. UC3_SC21 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 18 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) PSTN - ISDN Scenario 3.1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. UC3_SC22 Poisson, mean selected by traffic-time profile PSTN - ISDN Scenario 3.2 Basic call The call is released from the called user This scenario represents the case when the call establishment is performed. The call is released from the called user. UC3_SC23 Poisson, mean selected by traffic-time profile PSTN - ISDN Scenario 3.3 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. UC3_SC24 Poisson, mean selected by traffic-time profile PSTN - ISDN Scenario 3.4 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are deactivated. UC3_SC25 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 19 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) PSTN - ISDN Scenario 3.5 Basic call with BC= 3,1 KHz audio - Modem V.90 [i.4] This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. UC3_SC26 Poisson, mean selected by traffic-time profile PSTN - ISDN Scenario 3.6 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC3_SC27 Poisson, mean selected by traffic-time profile PSTN - ISDN Scenario 3.7 No answer from the called user This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user. UC3_SC28 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.1 Basic call. The call is released from the calling user. This scenario represents the case when the call establishment is performed. The call is released from the calling user. UC3_SC29 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 20 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) PSTN - PSTN Scenario 4.2 Basic call The call is released from the called user. This scenario represents the case when the call establishment is performed. The call is released from the called user. UC3_SC30 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.3 Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are deactivated. UC3_SC31 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.4 Basic call with Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed. The echo cancellers in the GW are activated. UC3_SC32 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.5 Basic call with BC= 3,1 KHz audio - Modem V.34 [I.5] (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are deactivated. UC3_SC33 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 21 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) PSTN - PSTN Scenario 4.6 Basic call with BC= 3,1 KHz audio - Modem V.32 bis (4,8 kBit/s, 9,6 kBit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are activated. UC3_SC34 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.7 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC3_SC35 Poisson, mean selected by traffic-time profile PSTN - PSTN Scenario 4.8 No answer from the called user This scenario represents the case when there is no answer from the called user ("no user responding"), the network initiate call clearing to the calling user. UC3_SC37 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 22 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN to MMTel fixed access [2], clause 7.3.1 Basic call with BC= ITC_value - enblock sending. This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC4_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC4_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC4_SC3 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 23 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 KHz audio - Fax with 33,6 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC4_SC4 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 KHz audio - Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC4_SC5 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with V.152 [i.2] This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC4_SC6 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 24 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with using the T.38 [i.3] in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC4_SC7 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kBit/s, 9,6 kBit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC4_SC8 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC4_SC9 Poisson, mean selected by traffic-time profile Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy. The network initiates call clearing to the calling user. UC4_SC10 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 25 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC4_SC11 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC4_SC12 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC4_SC13 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 26 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user UC4_SC14 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC4_SC15 Poisson, mean selected by traffic-time profile MMTel fix access to ISDN [2], clause 7.3.2 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC5_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 27 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call The call is released from the called user This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC5_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC5_SC3 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user UC5_SC4 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 28 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with V.152 [i.2] This scenario represents the case when in the active call state (N10) the Fax transfer is performed and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC5_SC5 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 KHz audio - Fax with 14,4 kBit/s with using the T.38 [i.3] in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC5_SC6 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kBit/s, 9,6 kBit/s, 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC5_SC7 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 29 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC5_SC8 Poisson, mean selected by traffic-time profile Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC5_SC9 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC5_SC10 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC5_SC11 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 30 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC5_SC12 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC5_SC13 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC5_SC14 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 31 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) MMTel fix Access to PSTN [2], clause 7.3.3 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC6_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC6_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC6_SC3 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 32 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC6_SC4 Poisson, mean selected by traffic-time profile Basic call - Fax with 14,4 kbit/s with V.152 [i.2] This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC6_SC5 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kBit/s, 9,6 kbit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC6_SC6 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 33 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC6_SC7 Poisson, mean selected by traffic-time profile Basic call - Fax with 14,4 kbit/s with using the T.38 [i.3] in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC6_SC8 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC6_SC9 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC6_SC10 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 34 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC6_SC11 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC6_SC12 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC6_SC13 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 35 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC6_SC14 Poisson, mean selected by traffic-time profile PSTN to MMTel fix Access [2], clause 7.3.4 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC7_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call The call is released from the called user. This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC7_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 36 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call - overlap sending This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC7_SC3 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC7_SC4 Poisson, mean selected by traffic-time profile Basic call with Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer is performed. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC7_SC5 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 37 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call - Fax with 14,4 kbit/s with V.152 codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC7_SC6 Poisson, mean selected by traffic-time profile Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer is performed. The call is released from the calling user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC7_SC7 Poisson, mean selected by traffic-time profile Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kBit/s, 9,6 kBit/s 14,4 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC7_SC8 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 38 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kBit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed. The call is released from the calling user. UC7_SC9 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC7_SC10 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC7_SC11 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC7_SC12 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 39 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC7_SC13 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC7_SC14 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC7_SC15 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 40 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) ISDN to VoLTE [2], clause 7.4.1 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC8_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC8_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC8_SC3 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 41 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Called user is user determined user busy. This scenario represents the case, when the called user is user determined user busy. the network initiates call clearing to the calling user. UC8_SC4 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC8_SC5 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC8_SC6 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC8_SC7 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 42 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC8_SC8 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC8_SC9 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 43 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) VoLTE to ISDN [2], clause 7.4.1 VoLTE - PSTN Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC9_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call The call is released from the called user This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC9_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC9_SC3 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC4 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 44 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC5 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC6 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC9_SC7 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 45 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC9_SC8 Poisson, mean selected by traffic-time profile Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC9_SC1 Poisson, mean selected by traffic-time profile Basic call. The call is released from the calling user. This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC9_SC2 Poisson, mean selected by traffic-time profile Called user is user busy. This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC9_SC3 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 46 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC4 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC5 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC9_SC6 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 47 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC9_SC7 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC9_SC8 Poisson, mean selected by traffic-time profile VoLTE to PSTN [2], clause 7.4.3 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed. The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC10_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 48 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC10_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user UC10_SC3 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC10_SC4 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC10_SC5 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 49 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC10_SC6 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user UC10_SC7 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling UC10_SC8 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 50 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) PSTN to VoLTE [2], clause 7.4.4 Basic call. The call is released from the calling user. This scenario represents the case when the call establishment is performed. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC11_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call The call is released from the called user. This scenario represents the case when the call establishment is performed . The call is released from the called user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC11_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call - overlap sending This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). UC11_SC3 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC11_SC4 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 51 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC11_SC5 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC11_SC5 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC11_SC7 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 52 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC11_SC8 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC11_SC9 Poisson, mean selected by traffic-time profile VoLTE to VoLTE [2], clause 7.5 Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC12_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the called user. UC12_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 53 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call - Fax with 14,4 kBit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC12_SC3 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC12_SC4 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC12_SC5 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 54 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC12_SC9 Poisson, mean selected by traffic-time profile VoLTE to MMTel fix access [2], clause 7.6.1 Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC13_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the called user. UC13_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 55 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec. This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC13_SC3 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC13_SC4 Poisson, mean selected by traffic-time profile CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC13_SC5 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 56 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC13_SC6 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC13_SC7 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC13_SC8 Poisson, mean selected by traffic-time profile CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC13_SC9 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 57 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) MMTel fix access to VoLTE [2], clause 7.6.2 Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC14_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Successful call - This scenario represents the case when the call establishment is performed. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the called user. UC14_SC2 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed (e.g. testing QoS parameters). UC14_SC3 Poisson, mean selected by traffic-time profile Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. UC14_SC4 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 58 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC14_SC5 Poisson, mean selected by traffic-time profile CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC14_SC6 Poisson, mean selected by traffic-time profile CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed (e.g. testing QoS parameters). The call is released from the calling user. UC14_SC7 Poisson, mean selected by traffic-time profile CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC14_SC8 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 59 Use Case Section Test Scenario Scenario ID Scenario % of System Load Scenario Arrival Distribution Scenario Duration Distribution (calls), message size (text messaging) CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. UC14_SC9 Poisson, mean selected by traffic-time profile ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 60 Table 2: Initial benchmark traffic-time profile Traffic-time profile Parameter Traffic-time profile Value Notes PX_SimultaneousScenarios (SIMS) 2 Maximum per UE PX_TotalProvisionedSubscribers 100 000 Subs Data in ETSI TS 186 008-2 [2] PX_PercentRegisteredSubscribers 40 % At test start. The percent of registered subscribers will fluctuate during the test PX_PercentRoamingSubscribers None No roaming PX_StepNumber 3 steps DOC underload, DOC, and DOC overload PX_StepTransientTime 120 seconds Maximum PX_StepTime 30 minutes Minimum PX_BackgroundLoad None PX_SApSIncreaseAmount 10 SApS Maximum Report three results, step before, DOC and step after PX_SystemLoad DOC Reported result in Scenario Attempts Per Second PX_IHS % InAdequately Handle Scenario Attempts Maximum (IHS) 0,1 % Average over a test step Figure 1: Example of an IMS benchmark traffic profile
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.3 Initial benchmark test implementation
|
The present document does not dictate the specific implementation of a test scenario. The test scenarios are defined in ETSI TS 186 008-2 [2] as protocol diagrams. These scenarios are implemented either by a commercial test system provider or as part of a benchmark test run. Example implementations include using the ETSI TTCN3 notation, using an XML notation (e.g. based on the open source SIPP), or specifically coding the test in a general programming language. For comparison (and ultimately certification) purposes, a specification of the test system used to implement the traffic-time profile, and documentation of the test scenario implementation in the test system with sufficient detail to be independently replicated, shall be included as part of the report.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.3.1 SUT Configuration
|
The initial benchmark supports a Session Control Subsystem SUT configuration as defined in ETSI TS 186 008-2 [2], clause 4. Release 1 does not specify reliability or availability requirements. The availability architecture and design objective target of the SUT should be described in the test report. 100 105 110 115 120 125 130 135 0 10 20 30 40 50 60 Time (minutes) Scenario Attempts per Second (SApS) 0% 2% 4% 6% 8% 10% 12% 14% System Load Successful Scenario Attempts % Inadequately Handled Scenario Attempts ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 61
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.3.2 Preamble
|
The preamble defines the steps necessary to configure the SUT for a benchmark run. The following steps shall be completed before the initial benchmark test run. 1) The SUT shall be started from a cold boot. 2) "Total Provisioned Subscribers" shall be provisioned in the database. 3) The initial "Percent Registered Subscribers" shall be setup.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.3.3 Test Execution
|
The initial benchmark test shall contain StepNumber stair steps in the profile. The test execution is valid if the profile has steps in the DOC underload range and at least one step in the DOC overload range.
|
852ab15656945a1ce0e6c84a2dcfd35d
|
186 008-3
|
4.3.4 Graphs
|
The following graphs shall be plotted in the benchmark report: • Scenario success rate: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second for the traffic set. - Y-Axis 2: Percentage of Inadequately Handled Scenario Attempts. • Scenario average transaction response time{for each identified scenario in the traffic set}: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second for the individual scenario. - Y-Axis 2: For each TRTdesign objective in the identified scenario, SUM of the TRT for a second divided by the SApS for the second. • Scenario Retransmissions {for each identified scenario in the traffic set that has retransmissions}: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second. - Y-Axis 2: Number of retransmissions in a second for that scenario. • CPU {on each of SUT node}: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second. - Y-Axis 2: CPU. • MEM {on each of SUT node}: - X-Axis: time (s). - Y-Axis 1: Scenario Attempts Per Second. - Y-Axis 2: MEM. ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 62 Annex A (informative): Bibliography ETSI ES 282 007 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". IETF RFC 3310 (September 2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)". IETF RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initialization Protocol (SIP)". ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905 version 7.0.0 Release 7)". ETSI TS 183 041 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3: Protocol specifications [Endorsement of 3GPP TS 24.247 Release 6]". ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 6)". ETSI TS 124 247: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.247)". ETSI ETSI TS 186 008-3 V2.1.1 (2015-06) 63 History Document history V1.1.1 October 2007 Publication V2.1.1 June 2015 Publication
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
1 Scope
|
The present document describes the performance benchmark methology for the IMS based services MMTel, Video Telephony and IMS/ PES. The terminology and concepts are described in TR 101 577 [i.11]. The present document is the second part of the multi-part deliverable which consists of four parts. TS 186 008-1 [i.1] defines the overall benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking scenarios. The present document contains the specific benchmarking use-cases and scenarios, along with scenario specific metrics and design objectives. It also defines the SUT configuration parameters. The present document also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. TS 186 008-3 [i.2] defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. TS 186 008-4 [i.3] defines Reference Load network quality parameters for the use cases defined in TS 186 008-2 [i.1].
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] Void. [2] ETSI TS 123 002 (V11.4.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.4.0 Release 11)".
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 186 008-1: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 1: Core Concepts ". [i.2] ETSI TS 186 008-3: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 3: Traffic Sets and Traffic Profiles". [i.3] ETSI TS 186 008-4: "IMS Network Testing (INT); IMS/NGN Performance Benchmark; Part 4: Reference Load network quality parameters". [i.4] Void. [i.5] Recommendation ITU-T P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO". ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 7 [i.6] Void. [i.7] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Vocabulary for 3GPP Specifications (3GPP TR 21.905)". [i.8] Recommendation ITU-T P.863 (01-2011): "Perceptual objective listening quality assessment". [i.9] Void. [i.10] Void. [i.11] ETSI TR 101 577 (V1.1.1): "Methods for Testing and Specifications (MTS); Performance Testing of Distributed Systems; Concepts and Terminology". [i.12] Void. [i.13] IETF RFC 3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP). [i.14] Recommendation ITU-T Q.543: "Digital exchange performance design objective". [i.15] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification". [i.16] ETSI TS 183 036: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); ISDN/SIP interworking; Protocol specification". [i.17] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)". [i.18] IETF RFC 3261 June 2002: SIP: "Session Initiation Protocol". [i.19] Void. [i.20] 3GPP TS 36.300 E-UTRA and E-UTRAN Overall Description; Stage 2. [i.21] ETSI TS 186 025-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 2: Subsystem Configurations and Benchmarks".
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
3 Definitions and abbreviations
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
3.1 Definitions
|
For the purposes of the present document, the IMS benchmarking terms and definitions given in TR 101 577 [i.11] apply.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 121 905 [i.7] and the following apply: PES IMS- based PSTN/ISDN Emulation Sub-system ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 8
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4 System Under Test (SUT) subsystems
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.1 IMS/MMtel
|
An IMS/NGN benchmark is required to allow not only a complete IMS network but also subsystems of a network corresponding to discrete products that may be available from a supplier. To address this requirement in this multi-part deliverable, a series of subsystems are defined, which will serve as a System Under Test (SUT) for a benchmark test. IMS/NGN elements that do not appear in a subsystem are regarded as part of the test environment, which is present for a subsystem to function, but which is not itself subject to benchmarking. Figure 1 depicts the IMS Reference Architecture. The components of the architecture are the primary building blocks, which are either defined by the IMS standard, or defined by external standards and referenced by IMS. The links between the primary building block represent reference points over which the building blocks communicate with each other. The reference architecture is a logical architecture; no mapping of functional elements to hardware or software component is mandated. E-CSCF P-CSCF S-CSCF MGCF HSS Cx IP Multimedia Networks IMS- MGW CS Network Mn Mb Mg Mm MRFP Mb Mr Mb Legacy mobile signalling Networks I-CSCF Mw Mw Gm BGCF Mj Mi BGCF Mk Mk C, D, Gc, Gr UE Mb Mb Mb MRFC SLF Dx Mp CS CS Rx Mm LRF Ml Le BGCF Mi LCS Client Cx Dx Sh Ut Mw ISC IBCF Mx Mx Mx Ma Dh TrGW Izi Ici, Mm Ix Mg MRB ISC Cr Rc I4 AS EATF Mx Figure 1: Overview of IMS Functional Entities [TS 123 002] For the purposes of benchmarking, however, certain rules concerning subsystem configurations are required. These rules that benchmark measurements taken from equivalent subsystems of different vendors are comparable with one another. The general guidelines for defining an SUT configuration are: • All of the functional elements of the subsystem shall be present in the SUT configuration. • All hardware elements used in the implementation of the SUT configuration shall be completely enumerated. • All the QoS spec measurements defined at the interfaces to the SUT shall be collected as specified in the benchmark test. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 9 • All hardware-specific measurements (e.g. CPU utilization, memory utilization, fabric bandwidth) specified in the benchmark test should be collected for all hardware elements used in the implementation of the SUT configuration. • SUT interface characteristics shall be specified so that they can be emulated by the test system, including: - Security (e.g. IPSec, TLS, DTLS, etc.). - Interface network characteristics (e.g. up and down bandwidth, up and down latency).
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.1.1 Session Control Subsystem (SCS)
|
The Session Control Subsystem (SCS) consists of the P-CSCF, I-CSCF, and S-CSCF, and HSS components, as depicted in figure 2. A valid SCS configuration consists of the set of x-CSCF building blocks, as well as the database functions HSS and SLF that support their functionality. The reference points for the SCS are the Gm reference point between the UE traffic generator and the home and visited P-CSCFs, the Mr reference point between the S-CSCF and the Simulated MRFC, the Mj reference point between the S-CSCF and the Simulated BGCF, and the test system management interface to the HSS and SLF databases. A SUT for this subsystem may consist of either one or two SCS configurations,to allow benchmark tests to use a combination of local and roaming simulated subscribers. Figure 2: SUT topology for SCS
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.1.2 HSS subsystem
|
This subsystem refers to the HSS.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.1.3 P-CSCF subsystem
|
The P-CSCF consists of the P-CSCF component, as depicted in figure 3. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 10 A valid P-CSCF configuration consists of the set of P-CSCF building blocks. The reference points for the subsystem are the Gm reference point between the UE traffic generator and the home and visited P-CSCFs, and the Mw reference points to the other simulated components (which are part of the TS in in this configuration). TS P-CSCF DNS I-CSCF Gm Mw DNS-Q System Under Test Test System Test Environment S-CSCF Figure 3: P-CSCF Subsystem
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.1.4 S/I-CSCF subsystem
|
The S/I-CSCF Subsystem consists of the S-CSCF, I-CSCF, HSS, and SLF components, as depicted in figure 4. A valid S/I-CSCF configuration consists of the set of S-CSCF and I-CSCF building blocks, as well as the database functions HSS and SLF that support their functionality. The reference points for the subsystem are the Mw reference point between the simulated P-CSCF and the S/I-CSCFs. TS I-CSCF DNS P -CSCF Gm DNS- Q System Under Test Test System Test Environment Mi Mr CCF S -CSCF Cx Dx HSS/ UPSF SLF BGCF MRFC Rf SIP AS ISC MGCF Mg ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 11 Figure 4: S/I-CSCF subsystem
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.2 IMS/PES
|
The System Under Test (SUT) subsystems for IMS/PES is described in TS 186 025-2 [i.21].
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.3 IMS to IMS/PES
|
The IMS and IMS/PES configuration are depicted in figure 5. MGC SIP UA MGF MGF UA AGCF RTP FM SIP UA FM MGC S-CSCF S-CSCF AS AS P-CSCF Figure 5: MMtel and IMS/PES configuration
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.4 IMS/LTE Basic Configuration
|
Figure 6: IMS/LTE Basic Configuration ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 12
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
4.5 VoLTE
|
The VoLTE components, are depicted in figure 7. IMS UA MME S-GW HSS P-CSCF IMS-ALG IMS-AGW P-GW V-PCRF UE eNodeB IMS Core LTE-Uu S11 S5 SGi LTE-Uu I/S-CSCF Sh I S C Cx Ut Ut VPLMN HPLMN H-PCRF Mx IMS UA UE Diameter Agent Diameter Agent S6a S9 S9 S6a Diameter App ID = 0 IBCF/TRGW Ici/Izi eNodeB MME S-GW P-GW S5 S6a P-CSCF/ IMS-ALG/ IMS-AGW SGi Rx Mw S1-MME S1-U Sec- GW S11 Gx Gx Rx S1-MME S1-U Sec- GW Rx Rx Gx Gx Cx Sh MMTel / RCS Application Servers IPX IBCF/TrGw Mx Ici/Izi ENUM Server ENUM ENUM MRF Mr’ Mr MRFP Mb Mb ENUM Mb Figure 7: VoLTE Basic Configuration
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5 Use cases
|
The following use cases, and corresponding tests, are currently defined. This clause attempts to define a set of basic use-cases and further ones can be defined similarly. These newly defined use-cases, or modifications to the ones presented here, will have to be described in a similar manner in the test report.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1 IMS
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1 Registration/de-registration use-case 1
|
Registration is the first use-case that is employed when using an IMS network. During this operation the UE announces its contact location to the home domain registrar in order for the home network to route terminating messages towards it. It is performed by an UE when it is turned on. De-registration is the last operation that an UE performs before it is turned off and it is used to invalidate the registered contact information. Because of security concerns, this operation has to be authenticated and the assigned S-CSCF challenges the UE using authentication vectors obtained from the HSS. During the initial registration the P-CSCF also negotiates a set of security associations with the UE. Future registration/deregistration operations performed over these secure channels do not need to further be authenticated as the integrity of the messages is protected. The registration has an attached expiration timer. Depending on the type of the network (fixed or mobile) and the usage patterns, this timer can vary from a few minutes up to one week, and it is negotiated between the UE and the home network. Before this timer expires, or when roaming to a new visited network, the UE has to start re-registration scenarios. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 13 As part of this use-case, after registering, the UE will subscribe to its own registration status at the assigned S-CSCF. This subscription will need to be refreshed periodically, similarly to the registration. Unsubscription is not required, as the S-CSCF will automatically terminate it on de-registration. To avoid congestion, the notification timing is not strictly coupled to events that triggered them, and can have a delay in the order of seconds. The first one is sent shortly after subscription, and as a rule, the UE should be ready to respond to notification at any moment during the subscription period. Update De-registration De-registration Reauth. Figure 8: Registration/de-registration state machine a) Off - In this state the UE does not have any interaction with the environment. b) Discovery - The UE is acquiring an IP address and finds the address of the outbound Proxy-CSCF. c) Unsecured - In this state the UE is completely attached to the IP layer and it can fully act at the signaling level. This state is mainly used to send initial registration intentions. No traffic is to be trusted by the network until the UE is authenticated. The UE should not trust incoming signaling until it will attach to a correctly authenticated network. d) Secured - the UE begun authentication by requesting an authentication challenge. The UE can verify the authenticity of this challenge and it creates a Security Association (SA) with the Proxy-CSCF. e) Secured and Registered - the UE sends the authentication challenge response to the network, indicating the location information that it wishes to save. While in this state, as communication is secured, updates can be performed without re-authentication. f) Secured, Registered and Subscribed - to react to network initiated events regarding the registration status, the UE subscribes to its own registration event package. The UE will then receive notifications on changes and it can act accordingly. For simplification, it is considered that the initial state is unsecured: the UE simulated by the test system already has IP connectivity and the Proxy-CSCF addresses are considered as input configuration for the test system. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 14
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.1 Definition
|
The registration/de-registration is the process by which a UE announces, updates or deletes its location information to the home domain"s registrar. This operation is authenticated and a secure communication channel for subsequent signaling is set-up between the UE and the network.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.2 Scenarios
|
While the scenario describe actions on the part of the UE, the portion of the signaling path between the UE and the complete IMS system outside the System Under Test configuration are simulated by the test environment with test system characteristics fixed with stated values. 5.1.1.2.1 Use Case 1- Scenario 1 - Successful initial registration with unprotected REGISTER requests on the SIP default port values as specified in RFC 326 The P-CSCF shall be prepared to receive the unprotected REGISTER requests on the SIP default port values as specified in RFC 3261 [i.18]. The P-CSCF shall also be prepared to receive the unprotected REGISTER requests on the port advertised to the UE during the P-CSCF discovery procedure. 5.1.1.2.2 Use Case 1- Scenario 2 - Successful initial registration with IMS AKA as a security mechanism The P-CSCF supports the registration with IMS AKA as a security mechanism described in TS 124 229, clause 5.2.2.2 [i.17]. 5.1.1.2.3 Use Case 1- Scenario 3 - Successful initial registration with SIP digest without TLS as a security mechanism The P-CSCF supports the registration with SIP digest without TLS as a security mechanism described in TS 124 229, clause 5.2.2.3 [i.17]. 5.1.1.2.4 Use Case 1- Scenario 4 - Successful initial registration with SIP digest with TLS as a security mechanism The P-CSCF supports the registration with SIP digest with TLS as a security mechanism described in TS 124 229, clause 5.2.2.4 [i.17] 5.1.1.2.5 Use Case 1- Scenario 5 - Successful initial registration with NASS-IMS bundled authentication as a security mechanism The P-CSCF supports the registration with with NASS-IMS bundled authentication as a security mechanism described in TS 124 229, clause 5.2.2.5 [i.17]. 5.1.1.2.6 Use Case 1- Scenario 6 - Successful initial registration with GPRS-IMS-Bundled authentication as a security mechanism The P-CSCF supports the registration with GPRS-IMS-Bundled authentication as a security mechanism described in TS 124 229, clause 5.2.2.6 [i.17].
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.2.7 Use Case 1- Scenario 7 - Re-registration - user currently registered
|
To refresh the registration timer the UE sends a re-registration request before the expiration time expires. This should be sent either 600 seconds before the expiration time if the registration time was greater than 1 200 seconds, or when half the registration time has passed when the registration time was under equal or less than 1 200 seconds. This scenario can also be employed at any time during the registration period when the UE intends to update its capabilities according to RFC 3840 [i.13]. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 15 If a secure channel has been set-up and it is used during this procedure, the S-CSCF does not need to authenticate the user and the signalling is presented in figure 9. If the request is not sent through the secure channel then the signalling flow is similar to that of the Initial Registration Scenario. Figure 9: Re-Registration - user currently registered signalling flow
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.2.8 Use Case 1- Scenario 8 - Re-subscription - user currently registered
|
As the subscription might have a different expiration timer as the registration, re-subscription is not necessarily linked to re-registration. The process is detailed in figure 10. Figure 10: Re-subscription - user currently registered signaling flow
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.2.9 Use Case 1- Scenario 9 - Re-registration - user roaming
|
When the UE is roaming to another visited network, the procedures are similar to those of initial registration. As there are no security association set-up with the new P-CSCF, the initial REGISTER request will be authenticated. The network will internally take care of the old registration, without any UE interaction.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
5.1.1.2.10 Use Case 1- Scenario 10 - UE initiated de-registration
|
When the UE requires terminating immediately the registration it can do so by issueing a REGISTER request with an expiration timer set to "0".
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6 Session set-up/tear-down scenarios
|
This use-case corresponds to a normal 2-party call. The "session set-up" part refers to the establishment of the call and the "session tear-down" to its destroyal. Before this scenario is performed, the respective User Endpoints which belong to the particular SUT domain and involved in the communication have to be successfully registered/re-registered. The registration period should not during execution of this use-case (it is acceptable to do a re-registration refreshment during a call scenario). This version of the document covers several call scenarios that are encountered the most in a real life deployments. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 16 Then several situations for the User Endpoints can been considered, based on the IP-CAN resource reservation status on the two participating sides. For example the originating and/or terminating party might require resource reservation or they could already have the resources preallocated, before the start of the scenario. In case that the Access Network is not part of the SUT, the IP-CAN reservation steps should be simulated by fixed delays in the Test System and the Test Report shall contain this values. In all successful call scenarios defined in the next clauses, the signaling flow of the tear-down part is depicted as initiated on the terminating side of the call. When generating traffic, the Test System should also simulate the symmetric case when the originating user initiates the tear-down and the Test System should maintain a 1:1 ratio between the two cases. During these scenario there are several waiting times during which the Test System should pause, like the ringing time or the call hold time. Distribution of these delays can follow a constant or a Poisson distribution. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 17
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.1 MMTel to MMTel
|
MMTEL to MMTEL Use case 2 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 18 MMTEL to MMTEL Use case 2 Scenario 2 Successful call - This scenario represents the case when the call establishment is performed correctly . Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 19 MMTEL to MMTEL Use case 2 Scenario 3 Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state the Fax transfer on the media is performed correctly and the echo cancellers in the GW are not activated.. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE MMTEL to MMTEL Use case 2 Scenario 4 Basic call with Fax with 14,4 kBit/s; This scenario represents the case when in the active call state the Fax transfer on the media is performed correctly and the echo cancellers in the GW are activated. . The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly. Options a) a resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 20 MMTEL to MMTEL Use case 2 Scenario 5 Basic call - Fax with 14,4 kbit/s with V.152 This scenario represents the case when in the active call state the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8 <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTEL to MMTEL Use case 2 Scenario 6 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTEL to MMTEL Use case 2 Scenario 7 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 21 MMTEL to MMTEL Use case 2 Scenario 8 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTEL to MMTEL Use case 2 Scenario 9 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 22 MMTEL to MMTEL Use case 2 Scenario 10 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTEL to MMTEL Use case 2 Scenario 11 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 23 MMTEL to MMTEL Use case 2 Scenario 12 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.2 IMS/PES to IMS/PES
|
The Use Cases for IMS/PES are described in TS 186 025-2 [i.21]. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 24
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.3 MMTel - IMS/PES
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.3.1 ISDN to MMTel Use case 3
|
ISDN to MMTel Use case 3 Scenario 1 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE SIP Parameter PSTN XML BearerCapability element in the INVITE INVITE: Content-Type: application/vnd.etsi.pstn+xml Content-Disposition: signal;handling=optional <?xml version="1.0" encoding="utf-8"?> PSTN BearerCapability BCoctet3 CodingStandard>00< InformationTransferCabability>ITC_value< < BCoctet4 TransferMode>00< InformationTransferRate>10000< BCoctet5 Layer1Identification>01< UserInfoLayer1Protocol>00011< ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 25 ISDN to MMTel Use case 3 Scenario 2 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE SIP Parameter PSTN XML BearerCapability element in the INVITE INVITE: Content-Type: application/vnd.etsi.pstn+xml Content-Disposition: signal;handling=optional <?xml version="1.0" encoding="utf-8"?> PSTN BearerCapability BCoctet3 CodingStandard>00< InformationTransferCabability>ITC_value< < BCoctet4 TransferMode>00< InformationTransferRate>10000< BCoctet5 Layer1Identification>01< UserInfoLayer1Protocol>00011< Table 1: PSTN XML BearerCapability ITC_value BC Information transfer capability XML InformationTransferCabability ITC_VA_1 Speech '00000' ITC_VA_2 3,1 kHz audio '10000' ITC_VA_3 unrestricted digital information '01000' ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 26 ISDN to MMTel Use case 3 Scenario 3 Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow Multiple INVITE method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) INVITE(CSq 2) 484 Address Incomplete(CSq 1) ACK INVITE(CSq 3) 484 Address Incomplete(CSq 2) ACK ……. INVITE(CSq 4) 484 Address Incomplete(CSq 3) ACK 180 Ringing(CSq 4) Apply post test routine Message flow Overlap sending, the in-Dialogue method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) 1 484 Address Incomplete(CSq 1) ACK INVITE(CSq 2) 2 183 Session Progress(CSq 2) PRACK 200 OK PRACK INFO 200 OK INFO …….. INFO 200 OK INFO 180 Ringing(CSq 2) Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 27 ISDN to MMTel Use case 3 Scenario 4 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ISDN to MMTel Use case 3 Scenario 5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 28 ISDN to MMTel Use case 3 Scenario 6 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with V.152 This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8 <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ISDN to MMTel Use case 3 Scenario 7 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 29 ISDN to MMTel Use case 3 Scenario 8 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ISDN to MMTel Use case 3 Scenario 9 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ISDN to MMTel Use case 3 Scenario 10 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy. the network initiates call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 30 ISDN to MMTel Use case 3 Scenario 11 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ISDN to MMTel Use case 3 Scenario 12 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ISDN to MMTel Use case 3 Scenario 13 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 31 ISDN to MMTel Use case 3 Scenario 14 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ISDN to MMTel Use case 3 Scenario 15 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 32
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.3.2 MMTel to ISDN Use case 4
|
MMTel to ISDN Use case 4 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE MMTel to ISDN Use case 4 Scenario 2 Basic call The call is released from the called user This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE MMTel to ISDN Use case 4 Scenario 3 Basic call with BC= 3,1 KHz audio - Fax with 33,6 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 33 MMTel to ISDN Use case 4 Scenario 4 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to ISDN Use case 4 Scenario 5 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with V.152 This scenario represents the case when in the active call state (N10) the Fax transfer is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8 <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 34 MMTel to ISDN Use case 4 Scenario 6 Basic call with BC= 3,1 KHz audio - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to ISDN Use case 4 Scenario 7 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s, 14,4 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to ISDN Use case 4 Scenario 8 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 35 MMTel to ISDN Use case 4 Scenario 9 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK MMTel to ISDN Use case 4 Scenario 10 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTel to ISDN Use case 4 Scenario 11 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 36 MMTel to ISDN Use case 4 Scenario 12 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTel to ISDN Use case 4 Scenario 13 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS or CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 37 MMTel to ISDN Use case 4 Scenario 14 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS or CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.3.3 MMTel to PSTN Use case 5
|
MMTel to PSTN Use case 5 Scenario 1 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 38 MMTel to PSTN Use case 5 Scenario 2 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE MMTel to PSTN Use case 5 Scenario 3 Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to PSTN Use case 5 Scenario 4 Basic call with Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 39 MMTel to PSTN Use case 5 Scenario 5 Basic call - Fax with 14,4 kbit/s with V.152 This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8 <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to PSTN Use case 5 Scenario 6 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to PSTN Use case 5 Scenario 7 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 40 MMTel to PSTN Use case 5 Scenario 8 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state (N10) the Fax transfer is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine MMTel to PSTN Use case 5 Scenario 9 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK MMTel to PSTN Use case 5 Scenario 10 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 41 MMTel to PSTN Use case 5 Scenario 11 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTel to PSTN Use case 4 Scenario 12 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 42 MMTel to PSTN Use case 4 Scenario 13 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine MMTel to PSTN Use case 4 Scenario 14 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 43
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.3.4 PSTN to MMTEL Use case 6
|
PSTN to MMTel Use case 6 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE PSTN to MMTel - Use case 6 Scenario 2 Basic call The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 44 PSTN to MMTel Use case 6 Scenario 3 Basic call - overlap sending This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow Multiple INVITE method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) INVITE(CSq 2) 484 Address Incomplete(CSq 1) ACK INVITE(CSq 3) 484 Address Incomplete(CSq 2) ACK ……. INVITE(CSq 4) 484 Address Incomplete(CSq 3) ACK 180 Ringing(CSq 4) Apply post test routine Message flow Overlap sending, the in-Dialogue method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) 1 484 Address Incomplete(CSq 1) ACK INVITE(CSq 2) 2 183 Session Progress(CSq 2) PRACK 200 OK PRACK INFO 200 OK INFO …….. INFO 200 OK INFO 180 Ringing(CSq 2) Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 45 PSTN to MMTel Use case 6 Scenario 4 Basic call with Fax with 33,6 kBit/s (Super G3 Fax) This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are deactivated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine PSTN to MMTel Use case 6 Scenario 5 Basic call with Fax with 14,4 kBit/s This scenario represents the case when in the active call state (N10) the Fax transfer is performed correctly. The echo cancellers in the GW are activated. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 46 PSTN to MMTel Use case 6 Scenario 6 Basic call - Fax with 14,4 kbit/s with V.152 codec This scenario represents the case when in the active call state (N10) the Fax transfer on the media and B-channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8 <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP <dynamic-PT> a=rtpmap <dynamic-PT> PCMA/8000 a=gpmd; vbd=yes Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine PSTN to MMTel Use case 6 Scenario 7 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer is performed correctly The call is released from the calling user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 47 PSTN to MMTel Use case 6 Scenario 8 Basic call with BC= 3,1 kHz - Modem V.32 bis (4,8 kbit/s, 9,6 kbit/s 14,4 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine PSTN to MMTel Use case 6 Scenario 9 Basic call with BC= 3,1 kHz - Modem V.34 (up to 33,6 kbit/s) This scenario represents the case when in the active call state (N10) the 3,1 kHz transfer is performed correctly. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=audio <Port> RTP/AVP 8/0 180/200 OK INVITE: SDP m=audio <Port> RTP/AVP 8 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine PSTN to MMTel - Use case 6 Scenario 10 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 48 PSTN to MMTel Use case 6 Scenario 11 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine PSTN to MMTel Use case 6 Scenario 12 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 49 PSTN to MMTel Use case 6 Scenario 13 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine PSTN to MMTel Use case 6 Scenario 14 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 50 PSTN to MMTel Use case 6 Scenario 15 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options resource reservation is on both sides no resource reservation on terminating side no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.4 VoLTE to IMS/PES
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.4.1 ISDN to VoLTE Use case 7
|
ISDN to VoLTE Use Case 7 Scenario 1 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE SIP Parameter PSTN XML BearerCapability element in the INVITE INVITE: Content-Type: application/vnd.etsi.pstn+xml Content-Disposition: signal;handling=optional <?xml version="1.0" encoding="utf-8"?> PSTN BearerCapability BCoctet3 CodingStandard>00< InformationTransferCabability>ITC_value< < BCoctet4 TransferMode>00< InformationTransferRate>10000< BCoctet5 Layer1Identification>01< UserInfoLayer1Protocol>00011< ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 51 ISDN to VoLTE Use Case 7 Scenario 2 Basic call with BC= ITC_value - enblock sending This scenario represents the case when the call establishment using en-bloc sending is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE SIP Parameter PSTN XML BearerCapability element in the INVITE INVITE: Content-Type: application/vnd.etsi.pstn+xml Content-Disposition: signal;handling=optional <?xml version="1.0" encoding="utf-8"?> PSTN BearerCapability BCoctet3 CodingStandard>00< InformationTransferCabability>ITC_value< < BCoctet4 TransferMode>00< InformationTransferRate>10000< BCoctet5 Layer1Identification>01< UserInfoLayer1Protocol>00011< Table 2: PSTN XML BearerCapability ITC_value BC Information transfer capability XML InformationTransferCabability ITC_VA_1 Speech '00000' ITC_VA_2 3,1 kHz audio '10000' ITC_VA_3 unrestricted digital information '01000' ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 52 ISDN to VoLTE Use Case 7 Scenario 3 Basic call - overlap sending with BC= speech This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow Multiple INVITE method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) INVITE(CSq 2) 484 Address Incomplete(CSq 1) ACK INVITE(CSq 3) 484 Address Incomplete(CSq 2) ACK ……. INVITE(CSq 4) 484 Address Incomplete(CSq 3) ACK 180 Ringing(CSq 4) Apply post test routine Message flow Overlap sending, the in-Dialogue method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) 1 484 Address Incomplete(CSq 1) ACK INVITE(CSq 2) 2 183 Session Progress(CSq 2) PRACK 200 OK PRACK INFO 200 OK INFO …….. INFO 200 OK INFO 180 Ringing(CSq 2) Apply post test routine ISDN to VoLTE Use Case 7 Scenario 4 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy. the network initiates call clearing to the calling user . Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 53 ISDN to VoLTE Use case 7 Scenario 11 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ISDN to VoLTE Use Case 7 Scenario 5 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 54 ISDN to VoLTE Use Case 7 Scenario 6 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ISDN to VoLTE Use Case 7 Scenario 7 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 55 ISDN to VoLTE Use case 7 Scenario 8 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.4.2 VoLTE to ISDN Use case 8
|
VoLTE to ISDN Use Case 8 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 56 VoLTE to ISDN Use Case 8 Scenario 2 Basic call The call is released from the called user This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE VoLTE to ISDN Use Case 8 Scenario 3 Called user is user determined user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK VoLTE to ISDN Use Case 8 Scenario 4 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 57 VoLTE to ISDN Use Case 8 Scenario 5 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to ISDN Use Case 8 Scenario 6 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 58 VoLTE to ISDN Use Case 8 Scenario 7 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine VoLTE to ISDN Use case 8 Scenario 8 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 59
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.4.3 VoLTE - PSTN Use case 9
|
VoLTE to PSTN Use Case 9 Scenario 1 Basic call. The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE VoLTE to PSTN Use Case 9 Scenario 2 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE VoLTE to PSTN Use Case 9 Scenario 3 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 60 VoLTE to PSTN Use Case 9 Scenario 4 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to PSTN Use Case 9 Scenario 5 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to PSTN Use Case 9 Scenario 6 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 61 VoLTE to PSTN Use Case 9 Scenario 7 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure when the user B becomes available for CC recall, the CC recall procedure is started. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine VoLTE to PSTN Use Case 9 Scenario 8 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 62
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.4.4 PSTN to VoLTE Use case 10
|
PSTN to VoLTE Use case 10 Scenario 1 Basic call. The call is released from the calling user This scenario represents the case when the call establishment is performed correctly. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE PSTN to VoLTE Use case 10 Scenario 2 Basic call The call is released from the called user. This scenario represents the case when the call establishment is performed correctly. The call is released from the called user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 100 Trying 180 Ringing 200 OK INVITE ACK Communication BYE 200 OK BYE ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 63 PSTN to VoLTE Use case 10 Scenario 3 Basic call - overlap sending This scenario represents the case when the call establishment using overlap sending. The call is released from the calling user. The call is released from the calling user. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow Multiple INVITE method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) INVITE(CSq 2) 484 Address Incomplete(CSq 1) ACK INVITE(CSq 3) 484 Address Incomplete(CSq 2) ACK ……. INVITE(CSq 4) 484 Address Incomplete(CSq 3) ACK 180 Ringing(CSq 4) Apply post test routine Message flow Overlap sending, the in-Dialogue method is used SIP (Test System A) Core Network SIP (Test System B) INVITE(CSq 1) 1 484 Address Incomplete(CSq 1) ACK INVITE(CSq 2) 2 183 Session Progress(CSq 2) PRACK 200 OK PRACK INFO 200 OK INFO …….. INFO 200 OK INFO 180 Ringing(CSq 2) Apply post test routine PSTN to VoLTE Use case 10 Scenario 4 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 64 PSTN to VoLTE Use case 10 Scenario 5 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine PSTN to VoLTE Use case 10 Scenario 6 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 65 PSTN to VoLTE Use case 10 Scenario 7 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine PSTN to MMTel Use case 6 Scenario 8 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 66 PSTN to VoLTE Use case 10 Scenario 9 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request.Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.5 VoLTE to VoLTE Use case 11
|
VoLTE to VoLTE Use case 11 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 67 VoLTE to VoLTE Use case 11 Scenario 2 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine VoLTE to VoLTE Use case 11 Scenario 3 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 68 VoLTE to VoLTE Use case 11 Scenario 4 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK VoLTE to VoLTE Use case 11 Scenario 5 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to VoLTE Use case 11 Scenario 6 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 69 VoLTE to VoLTE Use case 11 Scenario 7 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to VoLTE Use case 11 Scenario 8 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS or CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 70 VoLTE to VoLTE Use case 11 Scenario 9 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS or CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.6 MMTel -VoLTE
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.6.1 VoLTE to MMTel Use case 12
|
VoLTE to MMTel Use case 12 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 71 VoLTE to MMTel Use case 12 Scenario 2 Successful call - This scenario represents the case when the call establishment is performed correctly . Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine VoLTE to MMTel Use case 12 Scenario 3 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 72 VoLTE to MMTel Use case 12 Scenario 4 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK VoLTE to MMTel Use case 12 Scenario 5 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to MMTel Use case 12 Scenario 6 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 73 VoLTE to MMTel Use case 12 Scenario 7 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine VoLTE to MMTel Use case 12 Scenario 8 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 74 VoLTE to MMTel Use case 12 Scenario 9 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
6.6.2 MMTel to VoLTE Use case 13
|
MMTel to VoLTE Use case 13 Scenario 1 Successful call - This scenario represents the case when the call establishment is performed correctly. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 75 MMTel to VoLTE Use case 13 Scenario 2 Successful call - This scenario represents the case when the call establishment is performed correctly . Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the called user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow a) Successful call - resource resevation on both sides SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 183 Session Progress PRACK 200 OK PRACK UPDATE 200 OK UPDATE 180 Ringing 200 OK ACK BYE 200 OK BYE Apply post test routine Message flow: b), c) SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 100 Trying 180 Ringing 200 OK INVITE ACK BYE 200 OK BYE Apply post test routine MMTel to VoLTE Use case 13 Scenario 3 Basic call - Fax with 14,4 kbit/s with using the T.38 in an audio m-line codec This scenario represents the case when in the active call state the Fax transfer on the media and B- channels is performed correctly and the echo cancellers in the GW are not activated. The call is released from the called user. Ensure that in the active call state the data transfer is performed correctly (e.g. testing QoS parameters). Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side SIP Parameter INVITE: SDP m=image <Port> udptl t38 180/200 OK INVITE: SDP m=image <Port> udptl t38 Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE (SDP1) 180 Ringing 200 OK INVITE (SDP2) ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 76 MMTel to VoLTE Use case 13 Scenario 4 Called user is user busy This scenario represents the case, when the called user is user determined user busy the network initiate call clearing to the calling user. Options Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE 486 Busy Here ACK MMTel to VoLTE Use case 13 Scenario 5 CFU Ensure that when user A calls user B, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFU is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTel to VoLTE Use case 13 Scenario 6 CFB Ensure that when user A calls user B which is user determined user busy (UDUB), the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) CFB is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 77 MMTel to VoLTE Use case 13 Scenario 7 CFNR Ensure that when user A calls user B which does not answer, the call is forwarded to user C. Ensure that in the active call state the voice transfer is performed correctly (e.g. testing QoS parameters). The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) INVITE(Call-ID A-B) 180 Ringing(Call-ID B-A) CFNR is performed INVITE(Call-ID B-C) 180 Ringing(Call-ID C-B) 180 Ringing(Call-ID B-A) 200 OK INVITE(Call-ID C-B) ACK(Call-ID B-C) 200 OK INVITE(Call-ID B-A) ACK(Call-ID A-B) Communication Apply post test routine MMTel to VoLTE Use case 13 Scenario 8 CCBS User A is located in network A and user B is located in network B. User A has successfully invoked a CCBS request.Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCBS request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 78 MMTel to VoLTE Use case 13 Scenario 9 CCNR User A is located in network A and user B is located in network B. User A has successfully invoked a CCNR request. Ensure that the recall from user A to user B is successful. The call is released from the calling user. Options a) resource reservation is on both sides b) no resource reservation on terminating side c) no resource reservation on either side Message flow SIP (Test System A) Core Network SIP (Test System B) A CCNR request was already successful NOTIFY 200 OK NOTIFY INVITE 180 Ringing NOTIFY 200 OK NOTIFY 200 OK INVITE ACK Apply post test routine
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7 Metrics and design objectives
| |
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.1 Delay probability
|
This clause defines the delay parameters, the corresponding values are defined in TS 186 008-4 [i.3]. IMS systems shall comply with the requirements given in the following tables. Table 3 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Local exchange call request delay - originating outgoing and internal traffic connections ANALOGUE SUBSCRIBER LINES Local exchange call request delay - originating outgoing and internal traffic connections. clause 2.3.2.1 [i.14] For ANALOGUE SUBSCRIBER LINES, call request delay is defined as the interval from the instant when the off- hook condition is recognizable at the subscriber line interface of the exchange until the exchange begins to apply dial tone to the line. The call request delay interval is assumed to correspond to the period at the beginning of a call attempt during which the exchange is unable to receive any call address information from the subscriber. PES [i.15] For ANALOGUE SUBSCRIBER LINES connected to the AGCF/MSAN . Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the AGCF/MSAN until the AGCF/MSAN begins to apply dial tone to the line. ANALOGUE SUBSCRIBER with IAD (VGW) Local exchange call request delay - originating outgoing and internal traffic connections. PES [i.15] For ANALOGUE SUBSCRIBER LINES connected to the VGW. Call request delay is defined as the interval from the instant when the off-hook condition is recognizable at the subscriber line interface of the VGW until the VGW begins to apply dial tone to the line. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 79 Figure 11: Local exchange analogue subscriber call request delay: overlap sending Table 4 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Local exchange ISDN subscriber call request delay: overlap sending ISDN SUBSCRIBER LINES Local exchange call request delay - Overlap sending. clause 2.3.2.2 [i.14] Local exchange call request delay. Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. ISDN [i.16] Call request delay is defined as the interval from the instant at which the SETUP message has been received from the subscriber signalling system until the SETUP ACKNOWLEDGE message is passed back to the subscriber signalling system. IMS SUBSCRIBER Local exchange call request delay. IMS [i.17] Call request delay is defined as the interval from the instant at which the INVITE message has been received from the SIP subscriber until the 100 Trying from the SBC/P-CSCF is passed back to the subscriber. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 80 OLE AGCF/VGW ISDN line ISDN line SETUP SETUP ACK SETUP SETUP ACK SBC/P-CSCF SIP line INVITE 100 Trying Q.543 IMS Figure 12: Local exchange ISDN subscriber call request delay: overlap sending Table 5 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Local exchange ISDN subscriber call request delay: en Block sending ISDN SUBSCRIBER LINES Local exchange call request delay en - block sending. clause 2.3.2.3 [i.14] For DIGITAL SUBSCRIBER LINES using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the call proceeding message is passed back to the subscriber signalling system. ISDN [i.16] For ISDN using en-bloc sending, call request delay is defined as the interval from the instant at which the SETUP message is received from the subscriber signalling system until the CALL PROCCEDING message is passed back to the subscriber signalling system. Figure 13: Local exchange ISDN subscriber call request delay: en Block sending ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 81 Table 6 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Alerting sending delay for terminating traffic (the users are in different locations, controlled by different S-CSCF/P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for terminating traffic. clause 2.3.6.1.1 [i.14] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the exchange until the ringing tone is sent backwards toward the calling user. PES [i.15] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant when the last digit is available for processing in the AGCF/MSAN until the ringing tone is sent toward the calling user. ISDN SUBSCRIBER LINES Alerting sending Delay for terminating traffic. clause 2.3.6.1.2 [i.14] For calls terminating on DIGITAL SUBSCRIBER LINES, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling system to the instant at which an ADDRESS COMPLETE message is passed to the interexchange signalling system or ringing tone is sent backward toward the calling user. ISDN [i.16] For calls terminating on ISDN, the alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the digital subscriber line signalling to the instant at which an AGCF/MSAN sends the 180 Ringing backward toward the calling user. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 82 Latest address digit Ringing tone DLE Analogue line Q.543 IMS DLE ISDN line ALERTING ACM AGCF/VGW ISDN line ALERTING 180 Ringing Latest address digit AGCF/VGW Analogue line Ringing tone SBC/P-CSCF SIP line 180 Ringing 180 Ringing Figure 14: Local exchange Alerting sending delay for terminating traffic (in different locations) ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 83 Table 7 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) ANALOGUE SUBSCRIBER LINES Alerting sending Delay for internal traffic. clause 2.3.6.2.1 [i.14] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the exchange until ringing tone is applied to an ANALOGUE calling subscriber. PES [i.15] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the AGCF/MSAN until Ringing tone is sent towards the calling subscriber. ANALOGUE SUBSCRIBER LINES VGW Alerting sending Delay for internal traffic. PES [i.15] For calls terminating on ANALOGUE SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that the signalling information is available for processing in the VGW until Ringing tone is sent towards the calling subscriber. ISDN SUBSCRIBER LINES Alerting sending Delay for Internal traffic. clause 2.3.6.2.2 [i.14] For internal calls terminating on DIGITAL SUBSCRIBER LINES originating from DIGITAL SUBSCRIBER LINES, alerting sending delay is defined as the interval from the instant that an ALERTING message is received from the signalling system of the called subscriber's line until the ALERTING message is applied to the calling subscriber line. ISDN [i.16] For calls terminating on ISDN, alerting sending delay is defined as the interval from the instant that an ALERTING message is received and ALERTING is sent towards the calling subscriber. IMS SUBSCRIBER LINES 180 sending Delay for Internal traffic. IMS [i.17] For calls terminating sending delay is defined as the interval from the instant that an 180 message at the Gm interface has received and 180 is sent on the Gm towards the calling subscriber. LTE SUBSCRIBER LINES 180 sending Delay for Internal traffic. LTE For calls terminating sending delay is defined as the interval from the instant that an 180 message at the LTE UE interface has received and 180 is sent on the LTE UE towards the calling subscriber. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 84 Figure 15: Alerting sending delay for internal traffic (the user are in same locations, controlled by same AGCF/VGW or P-CSCF) ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 85 Table 8 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Call set up delay ISDN SUBSCRIBER LINES Call set up delay using overlap signalling. clause 2.4.3.1 [i.14] Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system. Exchange call setup delay for originating outgoing traffic connections, digital subscriber lines. The time interval starts when the INFORMATION message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the corresponding signalling information is passed to the outgoing signalling system. ISDN [i.16] Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on the Ic interface has been sent. ISDN [i.16] Sending, the time interval starts when the INFORMATION message received contains a "sending complete indication" and ends when the INVITE message on terminating Gm interface has been sent. IMS [i.17] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user. IMS [i.17] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user.(without preconditions) ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 86 Figure 16: Call set up delay: Overlap sending is used ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 87 Table 9 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Call set up delay: en Block sending is used ISDN SUBSCRIBER LINES Call set up delay using en-block signalling. clause 2.4.3.1 [i.14] Exchange call setup delay for originating outgoing traffic connections. For call attempts using en-bloc sending Call set-up delay is defined as the interval from the instant when the signalling information required for routing is received from the incoming signalling system until the instant when the corresponding signalling information is passed to the outgoing signalling system. The time interval starts when the SETUP message received contains a "sending complete indication" or when the address information necessary for call set-up is complete and ends when the call setup is sent on the outgoing signalling system. ISDN [i.16] Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the Ic interface. ISDN [i.16] Call set-up delay is defined as the interval from the instant when the signalling information including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding INVITE signalling information is passed to the terminating Gm interface. ISDN [i.16] Call set-up delay for Internal traffic is defined as the interval from the instant when the SETUP including Sending Complete (#) is received from the incoming signalling system until the instant when the corresponding SETUP signalling information is passed to the called line signalling system (see note). IMS SUBSCRIBER Call set up delay using for Internal traffic. IMS [i.17] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Gm interface to the called user. IMS [i.17] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user (without preconditions). IMS [i.17] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating Gm interface until the instant when the corresponding INVITE signalling information is passed on the terminating Ic interface to the called user (with preconditions). ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 88 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description LTE LTE [i.20] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating LTE _UE (ECM Connected ) interface until the instant when the corresponding INVITE signalling information is passed on the terminating LTE _UE (ECM Connected ) interface to the called user with QCI 5 (see note). LTE [i.20] Session initiation delay is defined as the interval from the instant when the INVITE signalling information is received from the calling user on the originating LTE _UE (ECM Connected) interface until the instant when the corresponding INVITE signalling information is passed on the terminating LTE _UE (ECM Connected ) interface to the called user with QCI 1. NOTE: If SC (#) is not included the setup delay may increase up to the digit collection timer (15 s). ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 89 Figure 17: Call set up delay: en Block sending is used ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 90 Table 10 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Through-connection delay ISDN SUBSCRIBER LINES Through-connection delay. clause 2.4.4.2 [i.14] Through-connection delay. The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the ANSWER and CONNECT ACKNOWLEDGEMENT messages have been passed to the appropriate signalling systems. ISDN [i.16] The through connection delay is defined as the interval from the instant that the CONNECT message is received from the called line signalling system until the through connection is established and available for carrying traffic and the CONNECT message has been sent to the calling user signalling system (see note). IMS Through-connection delay Delay for Internal traffic. IMS [i.17] The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating Gm interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating Gm interface. LTE LTE [i.20] The through connection delay is defined as the interval from the instant that the 200 OK message is received from the called user at the terminating LTE _UE interface until the through connection is established and available for carrying traffic and the 200 OK message has been sent to the calling user on the originating LTE _UE interface. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 91 Q.543 IMS DLE ISDN line ANM orig AGCF/VGW ISDN line Connect term AGCF/VGW ISDN line orig Gm interface SIP line 200 OK INVITE term Gm interface SIP line 200 OK INVITE Connect Connect Connect ACK Figure 18: Through-connection delay ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 92 Table 11 Meaning of timers Parameter Q.543 [i.14] IMS/PES equivalent Detailed description Connection release delay ISDN SUBSCRIBER LINES Connection call release delay. clause 2.4.6 [i.14] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when the connection is no longer available for use on the call (and is available for use on another call) and a corresponding RELEASE or DISCONNECT message is passed to the other signalling system involved in the connection. ISDN [i.16] Connection release delay is defined as the interval from the instant when DISCONNECT or RELEASE message is received from a signalling system until the instant when RELEASE COMPLETE is sent and a corresponding RELEASE or DISCONNECT message is sent, or vice versa. IMS SUBSCRIBER Connection call release delay Delay for Internal traffic. IMS [i.17] Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating Gm interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating Gm interface respectively. LTE - IMS SUBSCRIBER Connection call release delay Delay for Internal traffic. LTE [i.20] Connection release delay is defined as the interval from the instant when a BYE message is received at the originating or terminating LTE UE interface until the instant when 200OK is sent and a corresponding BYE message is sent at the terminating or originating LTE UE interface respectively. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 93 Figure 19: Connection call release delay
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.2 Speech quality analysis
|
This clause defines a set of parameters which enables the speech quality analysis of the system under test. They are divided in three parts: speech quality, speech level and PESQ offset. Table12 shows the speech quality parameters based on PESQ/POLQA. Table 13 shows the speech level parameters. Table 14 shows the PESQ/POLQA offset parameters. Table 12: Speech Quality parameters based on PESQ/POLQA Speech Quality Summary P.862.1/P.863 Min Max Mean Std-Dev ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 94 Table 13: Speech level parameters Speech Level Summary (Optional) Active Level Peak Noise Signal to Interval Noise Min Max Mean Std-Dev Table 14: PESQ/POLQA offset parameters Delay Summary - Delay (PESQ/POLQA Time Offset) Min Max Mean Std-Dev Range
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3 Call Profiler Traffic Patterns
|
This clause defines call profiles which are nowadays implemented in benchmark test systems.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.1 Saw Tooth
|
The Saw Tooth ramps up to a peak number of calls and then ramps down from peak. Figure 20: Example of saw tooth call profile ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 95
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.2 Blast
|
Blast - all calls go off-hook simultaneously, are connected for a specified time, and then disconnected. Figure 21: Example of saw tooth call profile
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.3 Rolling Blast
|
Rolling Blast - a defined set of channels go off-hook at once, and the pattern is repeated for all assigned channels.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.4 Ramp
|
Ramp - gradually increases connected calls to a specified number and then maintains those number of calls. Num ber off calls Figure 22
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.5 Steady Call Rate
|
Steady Call Rate - delivers a fixed, regulated call rate into the system under test.
|
268bbc2f61f0ede46bb8b3903229f5bf
|
186 008-2
|
7.3.6 Poisson Distribution
|
Poisson Distribution - defines call arrival rate by a statistical distribution. ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 96 0 50 100 150 200 250 300 350 400 450 1 9 17 25 33 41 49 57 65 73 81 89 97 105 113 121 129 137 145 153 161 169 177 185 193 201 Figure 23 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 97 Annex A (informative): Calls flows This annex defines the calls flows which should be implemented to simulate ISDN - non-ISDN environment. Figure A.1 presents the call flow for the – IMS/PES environment calling side. Figure A.2 presents the call flow for the – IMS/PES environment called side. Figure A.3 presents the call flow for the ISDN environment for voice calls calling side - overlap. Figure A.4 presents the call flow for the ISDN environment for voice calls calling side - enblock. Figure A.5 presents the call flow for the ISDN environment for voice calls called side. Figure A.6 presents the call flow for the ISDN environment for data calls calling side. Figure A.7 presents the call flow for the ISDN environment for data calls called side. Figure A.1 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 98 Timer T5 Connection Holding time Alerting Available On Hook Test Pass Test Fail Called party No No Yes Delay time 1000 ms OFF Hook Send Voice Samples Receive Voice Samples Inband Synch Establi shed No Yes Send inband digits Receive inband digits PESQ > limit Yes No Yes 1 DTMF No 1 2 2 Number of Alerting repetions < limit No Yes T5 time out Stop T5 1 Stop T5 Figure A.2 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 99 Figure A.3 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 100 On Hook Timer T1 Test Fail Timer T4 Waiting for answer T4 time out Timer T5 Connection Holding time Send Voice Samples Receive Voice Samples Inband synch Established No T5 time out No Yes Calling party Send digits Enblock SETUP (sending complete) DTMF Send inband digits Receive inband digits PESQ > limit Yes Receiving ALERTING and ringing tone Yes Timer T3 Waiting for ALERTING STOP Timer T3 Waiting for ALERTING Timer T3 Waiting for ALERTING timeout No Yes Yes No No STOP Timer waiting for CONNECT Yes CONNECT Recived Yes No Yes 1 1 1 2 Test Pas 2 CALL PROCEEDING received? Yes 1 No No 1 1 No Stop T5 Stop T5 STOP Timer T1 Figure A.4 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 101 Figure A.5 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 102 Figure A.6 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 103 Figure A.7 ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 104 Annex B (informative): Load profiles examples This annex defines the load profiles to simulate ISDN - non-ISDN environments. Figure B.1: the load simulates 2,0 CAPS, call duration 100 s, number of simulated users 200. The number of calls increases each 500 ms. After the call duration of 100 s the calls will be released. The call setup phase is marked orange, the call release phase blue. Figure B.2: the load simulates 2,66 CAPS, call duration 15 s, number of simulated users 30. The number of calls increases each 500 ms. After a call duration of 15 s the calls will be released. In the time interval of 5 s are tested simultaneous ISDN call setups using five channels. In order to simulate a load of 2,0 CAPS, the increase of number of calls is changed to 1,5 per second. Figure B.1 2.6666.. CAPS 0 5 10 15 20 25 30 35 40 45 0 5 10 15 20 25 30 Seconds User Figure B.2 2.0 CAPS 0 50 100 150 200 250 0 20 40 60 80 100 120 140 160 180 200 Seconds User ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 105 Annex C (informative): Examples for Test Reports C.1 Example of a Call Detail report CALL DETAIL REPORT Test Name: Basic Call Start Time: Stop Time: Date Time Call ID Server Chan Status Called Number Len Lat ms T1 T2 T3 T4 AVERAGE Date Time Calls Successful Calls Failed: Call Length Latency ms T1 T2 T3 T4 C.2 Example of a call summary report CALL SUMMARY REPORT Test Name: Basic Call Start Time: Stop Time: Server Channel Attempts Successful Failure Call Length (s) Connect Latency (ms) C.3 Example of a voice summary report Test Name: VQ TEST Start Time: Stop Time: SPEECH LATENCY REPORT Server Channel Number of Tests Average Speech Latency ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 106 Total Number of Tests: Total Average Speech Latency: DTMF REPORT Server Channel Number of Failures Total Number of Tests: PESQ/POLQA REPORT Server Channel Number of Tests Average PESQ/POLQA Score Average Offset Total Averages: C.4 Example of a voice quality detail report Test Name: VQ TEST Packetsphere Test: Start Time: Stop Time: SPEECH LATENCY REPORT TimeStamp Call ID Server Channel Speech Lat Number of Speech Latency Tests: Average: (ms) Minimum: (ms) Maximum: (ms) DTMF REPORT TimeStamp Call ID Server Channel Expected Digits Recieved Digits Number of DTMF Test Failures: PESQ REPORT TimeStamp Call ID Server Channel PESQ/POLQA Value Offset time Prompt Name ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 107 Value Offset time Total Average: Minimum Maximum Number of PESQ/POLQA Tests: PESQ/POLQA Score Above Threshold: ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 108 Annex D (informative): Bibliography ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 6)". ETSI TS 124 247: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.247)". ETSI ES 282 002 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES/ISDN Emulation Sub-system (PES); Functional architecture". ETSI TS 101 563 (V1.2.1): "Speech and multimedia Transmission Quality (STQ); IMS/PES exchange performance requirements". Recommendation ITU-T P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs". Recommendation ITU-T P.56: "Objective measurement of active speech level". IEEE 802.16: "A Technical Overview of the WirelessMAN™Air Interface for Broadband Wireless Access". IEEE 802.1, 802.1Q-2011: "IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks". IEEE 802.3: "Ethernet Working Group". ETSI ETSI TS 186 008-2 V2.1.1 (2013-08) 109 History Document history V1.1.1 October 2007 Publication V2.1.1 August 2013 Publication
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
1 Scope
|
The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 014-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specification- and design considerations can be found in the body of the present document: • the overall test suite structure; • the testing architecture; • the test methods and port definitions; • the test configurations; • the design principles, assumptions, and used interfaces to the TTCN3 tester (System Simulator); • TTCN styles and conventions; • the partial PIXIT proforma; • the modules containing the TTCN-3 ATS. Annex A provides the Partial Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex B provides the Testing and Test Control Notation (TTCN-3) part of the ATS.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 604 (V8.7.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.604 version 8.7.0 Release 8)". [2] ETSI TS 186 014-2 (V3.1.1): "Technical Committee for IMS Network Testing (INT); PSTN/ISDN simulation services; Communication Diversion (CDIV); Part 2: Test Suite Structure and Test Purposes (TSS&TP)". [3] ETSI TS 102 790-3: "Technical Committee for IMS Network Testing (INT); Network Integration Testing; IMS specific use of Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Conformance Testing; Part 3: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification". [4] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 6 [5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [6] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [7] ETSI ES 201 873-1 (V4.3.1): "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language". [8] ETSI TS 102 351 (V2.1.1): "Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Testing: Methodology and Framework". [9] ETSI TS 102 587-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to- Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS&TP) specification". [10] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
2.2 Informative references
|
The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
3 Definitions and abbreviations
| |
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 604 [1] apply.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
4 Abstract Test Method (ATM)
|
For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
4.1 Configurations for testing UE
|
The Gm interface is located between SUT (UE) and the IMS. SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 7 The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5 The ATS development process
| |
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 5 of TS 186 014-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 604 [1]. There are no explicit formulations of requirements.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.2 ATS structure
| |
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.2.1 Test case grouping
|
The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 186 014-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 014-2 [2], but use the naming conventions defined for the ATS (see clause 5.2.2). Table 1: CDIV ATS structure Netw ASdivertingUser/DivProcedures CDIV_N01 ASdivertingUser/NotOrigUser CDIV_N02 ASdivertingUser/NotDivUser CDIV_N03 ASdiverted-to CDIV_N04 User OrigUE CDIV_U01 DivertingUE CDIV_U02 Interaction TIP CDIV_N05_xxx TIR CDIV_N06_xxx ACR-CB CDIV_N07_xxx ECT CDIV_N08_xxx
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 8 where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit decimal number, starting in each subgroup path with "001". EXAMPLE: TC_OIP_N01_001: i) the identifier has Group index "CDIV_N01", i.e. it is in the subgroup having complete path: SupplementaryServices_CDIV/Netw/ASdivertingUser/DivProcedures; ii) the identifier is the first test case of this group/subgroup. NOTE: This naming scheme provides a 1-1 correspondence of TP identifiers as defined in TS 186 014-2 [2] and test case names. The TP identifier of TC_CDIV_N01_001 is TP CDIV_N01_001.
|
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.3 ATS specification framework
| |
72d95e4316df0cf9b3c316eb4086b66c
|
186 014-3
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules. 2) LibIms modules. 3) LibSip modules (RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [8]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects there is necessary to create tag version of all library modules. Table 2 shows the organization of the ATS as library of modules. Table 2: Library of modules Module Class Module Id Description CDIV CDIV_TC_Functions CDIV test case functions CDIV_TestCases CDIV test case definitions CDIV_Templates CDIV template definitions AtsCommon SS_Ims_PICS Module Parameter declarations associated with PICS SS_Ims_PIXITS SIP common Module Parameter declarations associated with PIXIT SS_Ims_TestConfiguration Functions which implement the configuration of the SUT adapter and mapping of test components for establishing and tearing down different test configurations SS_Ims_TestSystem TSI components, test system internal ports SS_Ims_TestCases Test case definitions SS_Ims_Functions Test case functions LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT LibIms_Interface IMS component LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note) LibIms_Templates Modified templates with IMS specific header fields LibIms_Steps functions using IMS specific types ETSI ETSI TS 186 014-3 V3.1.1 (2012-01) 9 Module Class Module Id Description LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT LibSip_Interface SIP component LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note) LibSip_SDPTypes SDP types and constants LibSip_Templates Basic and modified templates with SIP specific header fields LibSip_Steps SIP specific behaviour function library LibSip_XMLTypes XML types for SIP tests XSDAUX Basic types used in XML LibCommon LibCommon_AbstractData Generic data types for a stack and its operations LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean) LibCommon_DataStrings Bit and Octet string types LibCommon_Sync Co-ordination/synchronization of test components LibCommon_TextStrings Basic character and string types with fixed length LibCommon_Time Time handling functions and module parameter LibCommon_VerdictControl Basic functions for setting of test component verdicts NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.