1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Q.3932.3 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2015) SERIES Q: SWITCHING AND SIGNALLING Testing specifications Testing specifications for next generation networks IMS/NGN performance benchmark Part 3: Traffic
2、sets and traffic profiles Recommendation ITU-T Q.3932.3 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES A
3、PPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING
4、SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.19
5、00Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3899 TESTING SPECIFICATIONS Q.3900Q.4099 Testing specifications for next generation networks Q.3900Q.3999 Testing specifications for SIP-IMS Q.4000Q.4039 Testing specifications for Cloud computing Q.4040Q.
6、4059 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3932.3 (06/2015) i Recommendation ITU-T Q.3932.3 IMS/NGN performance benchmark Part 3: Traffic sets and traffic profiles Summary Recommendation ITU-T Q.3932.3 provides the third part of a multi-part deliverable
7、 covering the IMS/NGN performance benchmark, as identified below: Part 1: Core concepts; Part 2: Subsystem configurations and benchmarks; Part 3: Traffic sets and traffic profiles; Part 4: Reference load network quality parameters. The metrics measured and reported are for the performance of this su
8、bsystem under a communications application load. 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 p
9、resent document include: traffic set; traffic-time profile; benchmark test procedure. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Q.3932.3 2015-06-13 11 11.1002/1000/12496 _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your w
10、eb browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Q.3932.3 (06/2015) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and commu
11、nication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. Th
12、e World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution
13、1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a
14、recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met.
15、The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibilit
16、y that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recomm
17、endation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information
18、and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.3932.3 (06/2015) iii Table of Contents
19、Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Benchmark tests 3 6.1 Benchmark test goals 3 6.2 Initial benchmark traffic set and traffic-time profile 3 7 Initial benchmark
20、test implementation . 54 7.1 SUT configuration 54 7.2 Preamble . 54 7.3 Test Execution 54 7.4 Graphs . 54 Bibliography. 56 Rec. ITU-T Q.3932.3 (06/2015) 1 Recommendation ITU-T Q.3932.3 IMS/NGN performance benchmark Part 3: Traffic sets and traffic profiles 1 Scope This Recommendation provides the th
21、ird part of a multi-part deliverable covering the IMS/NGN Performance Benchmark, as identified below: Part 1: Core concepts; Part 2: Subsystem configurations and benchmarks; Part 3: Traffic sets and traffic profiles; Part 4: Reference load network quality parameters. The metrics measured and reporte
22、d are for the performance of this subsystem under a communications application load. 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
23、benchmark test data defined in this Recommendation include: traffic set; traffic-time profile; benchmark test procedure. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At th
24、e time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed belo
25、w. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Q.3930 Recommendation ITU-T Q.3930 (2012), Performance testing of distributed syste
26、ms Concepts and terminology. ITU-T Q.3931.2 Recommendation ITU-T Q.3931.2 (2011), Performance benchmark for the PSTN/ISDN emulation subsystem of an IP multimedia system Part 2: Subsystem configurations and benchmarks. ITU-T Q.3932.1 Recommendation ITU-T Q.3932.1 (2015), IMS/NGN performance benchmark
27、 Part 1: Core concept. ITU-T Q.3932.2 Recommendation ITU-T Q.3932.2 (2015), IMS/NGN performance benchmark Part 2: Subsystem configurations and benchmarks. ITU-T T.38 Recommendation ITU-T T.38 (2010), Procedures for real-time Group 3 facsimile communication over IP networks. ITU-T V.152 Recommendatio
28、n ITU-T V.152 (2010), Procedures for supporting voice-band data over networks. 2 Rec. ITU-T Q.3932.3 (06/2015) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the IMS benchmarking definitions as described in ITU-T Q.3930. 3.2 Terms defined in this Recommendation None. 4 Abbreviati
29、ons and acronyms This Recommendation uses the following abbreviations and acronyms: AKA Authentication and Key Agreement BC Bearer Capability CC Completion of Communications CCBS Completion of Calls to Busy Subscriber CCNR Completion of Calls to No Reply CFB Call forwarding busy CFNR Call Forwarding
30、 Not Reply CFU Call Forwarding Unconditional CPU Central Processor Unit DO Design Objective DOC Design Objective Capacity GW Gateway IHS Inadequately Handled Scenarios IMS IP Multimedia Subsystem ISDN Integrated Services Digital Network MEM Memory usage PI Progress Indicator PSTN Public Switched Tel
31、ephone Network SApS Scenario Attempts per Second SIMS Simultaneous Scenarios SIP Session Initiation Protocol SIPP Simple Internet Protocol Plus SUM Subscription Management SUT System Under Test TLS Transport Layer Security TRT Total Round-trip Time UDI Unrestricted Digital Information UDUB User Dete
32、rmined User Busy Rec. ITU-T Q.3932.3 (06/2015) 3 UE User Equipment XML extensible Markup Language 5 Conventions None. 6 Benchmark tests ITU-T Q.3932.1 and ITU-T Q.3932.2 have defined the framework for defining and executing an IMS/NGN performance benchmark. This Recommendation specifies a benchmark
33、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 system under test (SUT) implementer. 6.1 Benchmark test goals A benchmark test may be used either for comparison (e.g., comparing the performance of two
34、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). In order to accomplish these goals, a suite of benchmark tes
35、ts must cover a range of scenarios that are representative of the real world. Given the early nature of the IMS/NGN deployments, the data required to construct these scenarios is still in the process of being collected. For that reason, the benchmark test described here is more useful for prediction
36、 than for comparison. It is expected that the benchmark test specified in this part of the standard will have to be supplemented by additional benchmark tests that follow the framework of the standard, but which are parameterized differently. Additionally, while the primary metric collected by this
37、benchmark test is the design objective capacity (DOC) of the SUT, as experience is gained both with IMS/NGN deployments and with this benchmark, additional metrics will be defined. 6.2 Initial benchmark traffic set and traffic-time profile As described in detail in ITU-T Q.3932.1, a benchmark test m
38、easures 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
39、 test scenarios evolves over the execution of the benchmark test. Tables 1 and 2 represent a generic IMS/NGN traffic set and profile covering the fourteen major use-cases defined in ITU-T Q.3931.2 and ITU-T Q.3932.2. See also Figure 1, which shows an IMS benchmark traffic profile example. The percen
40、tage of system load for each scenario has not been defined, because the load depends on the number of selected use cases. 4 Rec. ITU-T Q.3932.3 (06/2015) Table 1 Initial benchmark traffic set Use case section Test scenario Scenario ID Scenario % of system load Scenario arrival distribution Scenario
41、duration distribution (calls), message size (text messaging) Registration/ De-registration ITU-T Q.3932.2, clause 7.1: Use case 1 scenario 1 Successful initial registration with unprotected REGISTER requests on the session initiation protocol (SIP) default port values as specified in b-IETF RFC 3261
42、 UC1_SC1 Use case 1 scenario 2 Successful initial registration with IMS AKA as a security mechanism UC1_SC2 Use case 1 scenario 3 Successful initial registration with SIP digest without TLS as a security mechanism UC1_SC3 Use case 1 scenario 4 Successful initial registration with SIP digest with TLS
43、 as a security mechanism UC1_SC4 Use case 1 scenario 5 Successful initial registration with NASS-IMS bundled authentication as a security mechanism UC1_SC5 Use case 1 scenario 6 Successful initial registration with GPRS-IMS bundled authentication as a security mechanism UC1_SC6 Use case 1 scenario 7
44、 Re-registration user currently registered UC1_SC7 5 Rec. ITU-T Q.3932.3 (06/2015) 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) Use case 1
45、 scenario 8 re-registration user currently registered UC1_SC8 Use case 1 scenario 9 re-registration user roaming UC1_SC9 Use case 1 scenario 10 UE initiated de-registration UC1_SC10 MMTel fixed access to MMTel fixed access ITU-T Q.3932.2, clause 8.1: Successful call this scenario represents the case
46、 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 UC2_SC1 Poisson, mean selected by traffic-time profile Exponential, mean 120 s Successful cal
47、l 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 UC2_SC2 Poisson, mean selected by traffic-time profile Expo
48、nential, 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 correctly and the echo cancellers in the gateway (GW) are not activated. The call is released from the calling user. Ensu
49、re that in the active call state the data transfer is performed correctly UC2_SC3 Poisson, mean selected by traffic-time profile 6 Rec. ITU-T Q.3932.3 (06/2015) 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) Basic call with fax with 14.4 kbit/s This scenario represents the cas
