1、 ETSI TS 186 025-1 V2.1.1 (2011-01)Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);IMS/PES Performance Benchmark;Part 1: Core ConceptsETSI ETSI TS 186 025-1 V2.1.1 (2011-01)2Reference DTS/TISPAN-06053-1-NGN-R2 Keywords IMS, pe
2、rformance, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the pre
3、sent document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case
4、 of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and
5、 other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorize
6、d by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the ben
7、efit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks r
8、egistered and owned by the GSM Association. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations
9、. 7g34 Benchmark information model . 7g34.1 Use-case . 9g34.1.1 Call Flow . 9g34.1.2 Load Profile 9g34.1.3 Metrics 9g34.1.4 Use-case outcomes 9g34.1.5 Scenarios and scenario attempts . 9g34.1.6 Design Objective (DO) . 10g34.1.7 Scenario 10g34.2 Benchmark test . 10g34.2.1 Traffic set 10g34.2.2 Backgr
10、ound load . 10g34.2.3 Traffic-time profile . 10g34.2.4 Test parameters . 10g34.3 Benchmark report . 12g35 System Under Test (SUT) 12g35.1 Creation of subscriber data base . 14g36 Test system . 14g37 Benchmark metrics examples . 15g3Annex A (informative): Bibliography . 16g3History 17g3ETSI ETSI TS 1
11、86 025-1 V2.1.1 (2011-01)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 3
12、14: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy,
13、 no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technic
14、al Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 1 of a multi-part deliverable covering the IMS/PES Performance Benchmark, as identified below: Part 1: “
15、Core Concepts“; Part 2: “Subsystem Configurations and Benchmarks“; Part 3: “Traffic Sets and Traffic Profiles“; Part 4: “Reference Load network quality parameters“. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)51 Scope The present document is for an initial release of a PSTN/ISDN Emulation Sub-system (PES
16、) performance benchmark. The same tests can be used also for legacy PSTN/ISDN networks or for inter-working tests between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. The metrics measured and reported are for performance of this subsystem under a communications application load. The prese
17、nt document is the first part of the multi-part deliverable which consists of four parts. The present document contains the overall benchmark descriptions, architectures, processes, and information models that are common to all specific benchmarking scenarios. TS 186 025-2 1 contains the specific be
18、nchmarking use-cases and scenarios, along with scenario specific metrics and design objectives. It also defines the SUT configuration parameters. This part also contains any required extensions to the overall descriptions present in the present document, if necessary for the specific scenario. TS 18
19、6 025-3 i.1 defines an initial benchmark test through the specification of a traffic set, traffic-time profile and benchmark test procedure. TS 186 025-4 i.2 defines Reference Load network quality parameters for the use cases defined in TS 186 025-2 1. 2 References References are either specific (id
20、entified 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
21、 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. 2.1 Normative references The following referenced documents are
22、necessary for the application of the present document. 1 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“. 2 ITU-T Recommendation Q.543: “Digital excha
23、nge performance design objective“. 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 025-3: “Telecommunications and Internet Converged Services
24、 and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 3: Traffic Sets and Traffic Profiles“. i.2 ETSI TS 186 025-4: “Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; Part 4: Reference Load
25、 network quality parameters“. i.3 ITU-T Recommendation 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“. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)6i.4 ITU-T Recommendation P.862.1:
26、“Mapping function for transforming P.862 raw result scores to MOS-LQO“. i.5 ITU-T Recommendation P.56: “Objective measurement of active speech level“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: background load:
27、 workload applied to an SUT during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached benchmark report: document generated at the conclusion of a test procedure containing the metrics mea
28、sured during the execution of the test and/or computed from the data collected in the benchmark log benchmark test: procedure by which a test system interacts with a System Under Test to measure its behaviour and produce a benchmark report configuration: specification of a subset of IMS/PES architec
29、tural elements and metrics for which collection of benchmark tests can be defined design objective: 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 idle load: load that is not de
30、pendent on the traffic or other external activities maximum capacity: maximum processor load that a processor can handle without rejecting new calls metric: performance measurement of SUT reported in a benchmark report parameter: attribute of a SUT, test system, system load, or traffic set whose val
31、ue is set externally and prior to a benchmark test, and whose value affects the behaviour of the benchmark test processor load: part of time the processor executes work, normally expressed in percent NOTE: The processor load consists of Idle load, Traffic load and Usage load. Reference Call (RC): ba
32、sic ISUP to ISUP call connected through two MGW in the same MGC domain test parameters: parameters whose values determine the behaviour of a benchmark test test procedure: specification of the steps to be performed by a benchmark test test scenario: specific path through a use-case, whose implementa
33、tion by a test system creates a system load test system: collection of hardware and software which presents a system load to a system under test and collects data on the system under tests performance, from which metrics can be computed traffic load: load that results from handling traffic events th
34、at are directly related to calls NOTE: This load varies with the traffic intensity. traffic-time profile: evolution of the average scenario over a time interval traffic set: mixture of traffic scenarios usage load: load that is reserved for the administrations operation and maintenance activities du
35、ring busy hour workload: number of reference calls per second (RC/s) NOTE: It is calculated by multiplying calls per second by its corresponding WLF. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)7workload factor (WLF): traffic load for different types of calls in relation to the traffic load of the refere
36、nce call (ISUP call) 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: %IHS Percent Inadequately Handled Scenarios A-BGF Access Border Gateway Function AGCF Access Gateway Control Function APS Attempts per Second BC Bearer CapabilityCLIP Calling Line Iden
37、tification Presentation CW Communication Waiting DO Design Objective IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network ISUP ISDN User Part MCID Malicious Communication IDentification MGW Media Gateway MHT Mean Holding Time NGN Next Generation Networks PIXIT Protocol Implementation
38、eXtra Information for Testing PSTN Public Switched Telecommunications Network RC Reference Call SAPS Session Attempts Per Second SUT System Under Test TA Tones and Announcement TSS Telephony Softswitch Solution UDI Unrestricted Digital Information WLF WorkLoad Factor 4 Benchmark information model In
39、 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. ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)8Figure 1: IMS/PES benchmark information model ETSI ETSI TS 186 025-1 V2.1.1 (2011-01)9The
40、 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 of m
41、easurements during the test; and benchmark test reports, which report metrics interpreted from the benchmark test log files. 4.1 Use-case The top level of the individual behavioural model is the use-case. A use-case describes the goal that a user has in interacting with a system, the various actors
42、(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 of the use-case, the possible outcomes that apply to the use-case, and the metrics to be collected. The goal and actors of a use-case a
43、re documented in narrative text and diagrams; the other elements are complex information elements, which are described in their respective clauses. 4.1.1 Call Flow The calls flows define the characteristic message flows, the tones and announcement for a specific interface. 4.1.2 Load Profile To faci
44、litate the calculation of processing capacity and the appropriate load profile the concept of workload factor has been defined based on the reference call for each combination of traffic case and traffic signalling interface. The reference call (RC) is defined as a basic ISUP to ISUP call connected
45、through two MGW in the same domain. Based on the workload factors for all different types of calls, the call intensities and the services used, one can express the total traffic load in an equivalent number of reference calls per second. The dimensioning of any type of network depends on a number of
46、 different parameters such as utilization per channel, calls per second, mean holding time, type of accesses being involved, and type of services being requested. 4.1.3 Metrics The metrics of a use-case describe the measurements collected from the execution of a scenario attempt. Typical metrics inc
47、lude response times and message rates. If a scenario is selected for execution in a benchmark test, its metrics are collected. See clause 7 for more detail. 4.1.4 Use-case outcomes A use-case outcome is a set of possible outcomes of the scenarios of a use-case. An outcome may be simply “correct“, it
48、 may reflect an error or failure condition; or it may reflect a correct behaviour that took an excessive amount of time to occur. An instance of a scenario that experiences an error, failure, or timeout outcome is referred to as an inadequately handled scenario attempt. 4.1.5 Scenarios and scenario
49、attempts A scenario is a trace of a path through a use-case. It is analogous to “call attempt“, but applies to all interactions within an IMS/PES network, different Bearer, and application interactions. A scenario may succeed, fail, or succeed functionally. The terms “scenario attempt“ and “scenario attempts per second“ are used in this standard in place of “call attempt“ and “call attempts per second“ because IMS/PES is a transaction-oriented system with transactions of a variety of types (e.g. speech calls, 3,1 kHz calls, modem calls, Fax calls, etc.)
