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.1 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 1: Core con
2、cept Recommendation ITU-T Q.3932.1 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 APPLICABLE TO ITU-T ST
3、ANDARD 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 SYSTEM No. 1 Q.850Q.9
4、99 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.1900Q.1999 BROADBAND IS
5、DN 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.4059 For further deta
6、ils, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3932.1 (06/2015) i Recommendation ITU-T Q.3932.1 IMS/NGN performance benchmark Part 1: Core concept Summary Recommendation ITU-T Q.3932.1 provides the first part of a multi-part deliverable covering the IP multimedia subsystem (IMS
7、)/next generation networks (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. This Recommendation describes the performance benchmark m
8、ethodology for the IMS based services multimedia telephony (MMTel), video telephony and IMS/PES. The terminology and concepts are described in Recommendation ITU-T Q.3930. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Q.3932.1 2015-06-13 11 11.1002/1000/12495 _ * To access
9、 the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Q.3932.1 (06/2015) FOREWORD The International Telecommunication Union (ITU) is the Unite
10、d Nations specialized agency in the field of telecommunications, information and communication 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 Recommenda
11、tions on them with a view to standardizing telecommunications on a worldwide basis. The 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 appro
12、val of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 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 “Administrati
13、on“ is used for conciseness to indicate both a telecommunication administration and a 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 complianc
14、e with the Recommendation is achieved when all of these mandatory provisions are met. 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 re
15、quired of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility 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 Intelle
16、ctual Property Rights, whether asserted by ITU members or others outside of the Recommendation 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. H
17、owever, implementers are cautioned that this may not represent the latest information 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
18、 prior written permission of ITU. Rec. ITU-T Q.3932.1 (06/2015) iii Table of Contents 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 3 5 Conventions 4 6 Benchmark information model . 4 6.1 Use
19、case 5 6.2 Benchmark test . 7 6.3 Benchmark report . 9 7 System under test (SUT) . 9 8 Test system . 13 9 Benchmark metrics examples . 13 Rec. ITU-T Q.3932.1 (06/2015) 1 Recommendation ITU-T Q.3932.1 IMS/NGN Performance benchmark Part 1: Core concept 1 Scope Recommendation ITU-T Q.3932.1 provides th
20、e first 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 present Recommendation d
21、escribes the performance benchmark methodology for the IMS based services MMTel, video telephony and IMS/PSTN emulation solution (PES). The terminology and concepts are described in ITU-T Q.3930. 2 References The following ITU-T Recommendations and other references contain provisions which, through
22、reference in this text, constitute provisions of this Recommendation. At the 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
23、most recent edition of the Recommendations and other references listed below. 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 P.56 Rec
24、ommendation ITU-T P.56 (2011), Objective measurement of active speech level. ITU-T P.862 Recommendation ITU-T P.862 (2001), Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs. ITU-T P.862.1
25、Recommendation ITU-T P.862.1 (2003), Mapping function for transforming P.862 raw result scores to MOS-LQO. ITU-T P.863 Recommendation ITU-T P.863 (2014), Perceptual objective listening quality assessment. ITU-T Q.3930 Recommendation ITU-T Q.3930 (2012), Performance testing of distributed systems Con
26、cepts and terminology. ITU-T Q.3932.2 Recommendation ITU-T Q.3932.2 (2015), IMS/NGN performance benchmark Part 2: Subsystem configurations and benchmarks. TS 101 563 ETSI TS 101 563 V.1.3.1 (2014), Speech and multimedia Transmission Quality (STQ); IMS/PES/VoLTE exchange performance requirements. TS
27、123 002 ETSI TS 123 002 (V11.6.0) (2013), Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 version 11.6.0 Release 11). 2 Rec. ITU-T Q.3932.1 (06/2015) 3 Definitions 3.1 Terms defined elsewhere The IMS
28、benchmarking definitions are described in ITU-T Q.3930. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 background load: Workload applied to a system under test (SUT) during a benchmark test, for the purpose of consuming SUT resources during a benchmar
29、k test and changing the traffic intensity at which the capacity of the SUT is reached. 3.2.2 benchmark report: Document generated at the conclusion of a test procedure containing the metrics measured during the execution of the test and/or computed from the data collected in the benchmark log. 3.2.3
30、 benchmark test: Procedure by which a test system interacts with a system under test (SUT) to measure its behaviour and produce a benchmark report. 3.2.4 configuration: Specification of a subset of IMS/PES architectural elements and metrics for which collection of benchmark tests can be defined. 3.2
31、.5 design objective (DO): Probabilistic model of delay and failure requirements for SUT, associated with a use case, specified by threshold values and probabilities for delay and scenario failure. 3.2.6 design objective capacity (DOC): Largest load a SUT can sustain while not exceeding design object
32、ives (DOs) defined for a use case. 3.2.7 idle load: Load that is not dependent on the traffic or other external activities. 3.2.8 maximum capacity: maximum processor load that a processor can handle without rejecting new calls. 3.2.9 metric: Performance measurement of a system under test (SUT) repor
33、ted in a benchmark report. 3.2.10 parameter: Attribute of a SUT, test system, system load, or traffic set whose value is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test. 3.2.11 processor load: Amount of time the processor executes work. It is
34、 normally expressed in percent. NOTE The processor load consists of idle load, traffic load and usage load. 3.2.12 reference call (RC): Basic ISDN user part (ISUP) to ISUP call connected through two media gateways (MGWs) in the same media gateway controller (MGC) domain. 3.2.13 session attempts per
35、second (SAPS) increase amount: Increment by which the average SAPS changes between steps of a profile. 3.2.14 test parameters: Parameters whose values determine the behaviour of a benchmark test. 3.2.15 test procedure: Specification of the steps to be performed by a benchmark test. 3.2.16 test scena
36、rio: Specific path through a use case, whose implementation by a test system creates a system load. 3217 test system: Collection of hardware and software which presents a system load to a system under test (SUT) and collects data on the SUTs performance, from which metrics can be computed. 3.2.18 tr
37、affic load: Load that results from handling traffic events that are directly related to calls. Rec. ITU-T Q.3932.1 (06/2015) 3 NOTE This load varies with the traffic intensity. 3.2.19 traffic-time profile: Evolution of the average scenario over a time interval. 3.2.20 traffic set: Mixture of traffic
38、 scenarios. 3.2.21 usage load: Load that is reserved for the administrations operation and maintenance activities during busy hour. 3.2.22 workload: Number of reference calls per second (RC/s). NOTE It is calculated by multiplying calls per second by its corresponding workload factor (WLF). 3.2.23 w
39、orkload factor (WLF): Traffic load for different types of calls in relation to the traffic load of the reference call (ISUP call). 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AGCF Access Gateway Control Function BGCF Breakout Gateway Control Functi
40、on BYE BYE message CN Core Network CPU Central Processor Unit CS Circuit Switched CSCF Call Server Control Function DO Design Objective DOC Design Objective Capacity ETH Ethernet HSS Home Subscriber Server FM Fault Management IBCF Interconnection Border Control Function II-NNI Inter-IMS Network to N
41、etwork Interface IM IP Multimedia IMS IP Multimedia Subsystem IP Internet Protocol ISC IP multimedia Service Control ISDN Integrated Service Digital Network ISUP ISDN User Part LCS Location Services LRF Location Retrieval Function MCS Modulation and Coding Scheme MGC Media Gateway Controller MGW Med
42、ia Gateway MHT Mean Holding Time 4 Rec. ITU-T Q.3932.1 (06/2015) MME Mobile Management Entity MMTel Multimedia Telephony MRB Media Resource Broker MRF Media Resource Function MRFP Media Resource Function Processor NGN Next Generation Networks NNI Network-to-Network Interface PES PSTN Emulation Solut
43、ion PESQ Perceptual Evaluation of Speech Quality POLQA Perceptual Objective Listening Quality Assessment POTS Plain old telephone service RC Reference Call RTP Real-Time Protocol SAPS Session Attempts Per Second S-CSCF Serving CSCF SIGTRAN Steam Control Transmission Protocol SIP Session Initiation P
44、rotocol SIP-I a mapping from SIP to ISUP SLF Subscription Locator Function SUA SCCP-User Adaptation Layer SUT System Under Test TA Tones and Announcement TDM Time-division multiplexing UDI Unrestricted Digital Information UDI/TA Unrestricted Digital Information with tones and announcements UE User E
45、quipment VGW Voice Gateway WLF Workload factor 5 Conventions None. 6 Benchmark information model In this clause, “benchmark information model“ refers to the structure of the information elements that define the benchmark. This information model is depicted in Figure 1. Rec. ITU-T Q.3932.1 (06/2015)
46、5 The information model consists of three primary elements: use cases, which describe the behaviour of an individual user, and which in turn define scenarios; benchmark tests, which generate a workload by aggregating the behaviour of individual scenarios in a controlled manner, and collect log files
47、 of measurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files. Figure 1 IP multimedia subsystem (IMS) benchmark information model 6.1 Use case The top level of the individual behavioural model is the use case. A use case describes: T
48、he goal that a user has in interacting with a system, the various actors (e.g., other users, network elements) that participate in the use case, the basic course of events that are carried out by the user and the SUT, the design objective (DO) of the use case, the possible outcomes that apply to the
49、 use case, and the metrics to be collected. The goal and actors of a use case are documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses. 6 Rec. ITU-T Q.3932.1 (06/2015) 6.1.1 Call flow The calls flows define the characteristic message flows, the tones and announcements (TAs) for a specific interface. 6.1.2 Load profile To facilitate the calculation of processing capacity and the appropriate load profile, th
