1、 ETSI TR 103 482 V1.1.1 (2018-07) Speech and multimedia Transmission Quality (STQ); Framework for multi-service testing TECHNICAL REPORT ETSI ETSI TR 103 482 V1.1.1 (2018-07) 2Reference DTR/STQ-00209m Keywords 3G, data, network, QoS, service, speech ETSI 650 Route des Lucioles F-06921 Sophia Antipol
2、is 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 The present document can be downloaded from: http:/www.etsi.org/standards-search The present docu
3、ment may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/
4、or in print, the only prevailing document is the print of the Portable Document Format (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 st
5、atus of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may
6、 be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing r
7、estriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organization
8、al Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 103 482 V1.1.1 (2018-07) 3Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g3Introduction 4g31 Scope 5g32
9、References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Basic considerations . 6g35 Function and functional limitations of QoS parameters . 7g36 Concept of the multi-service framework 8g37 Taxonomy of
10、multi-service scenarios 8g38 Summary 9g3History 10g3ETSI ETSI TR 103 482 V1.1.1 (2018-07) 4Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is p
11、ublicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “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 E
12、TSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, 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,
13、or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to
14、 use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee
15、Speech and multimedia Transmission Quality (STQ). Standardization offers a large portfolio of QoS and QoE metrics to describe and assess the quality of services available through mobile devices. These standards also provide measurement methodologies to produce these QoS and QoE data. With a few exce
16、ptions (e.g. Multi-RAB), these methodologies use scenarios where a service is used exclusively. This is different from typical user behavior where multiple services are interchanged in the same session, or even run concurrently. The present document addresses this topic by providing a taxonomy and a
17、 descriptive framework which integrates multiple services and the use of multi-service applications with existing QoS and QoE metrics. It thereby integrates existing single-service methodologies effortlessly, such that they become a particular case of parametrization of a multi-service test case. Mo
18、dal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI d
19、eliverables except when used in direct citation. Introduction Mobile communication networks and smartphones are enabling a wide range of user-centric services, from text messaging and telephony to multimedia applications. Usage of such services often takes place in a concurrent way, i.e. several ser
20、vices are used in parallel, or in close succession. While standardized quality metrics exist to describe individual services, aspects of concurrent usage are only addressed in a limited way (see for instance ETSI TS 102 250-2 i.1, clause 6.12 and ETSI TR 103 114 i.2). The purpose of the present docu
21、ment is to provide a comprehensive framework for testing concurrent use of multiple services. This framework is designed to be modular and scalable with respect to seamless expansion to new services. It is not restricted to particular services or multi-service carrier applications, i.e. it covers th
22、e whole range of “over the top“ (OTT) applications and services. ETSI ETSI TR 103 482 V1.1.1 (2018-07) 51 Scope The present document provides a framework for concurrent tests of multiple services, using a top-level approach which is also modular and scalable with respect to new services. Also, the f
23、ramework explicitly integrates measurement methodology, in particular reproducibility aspects. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by date of publication and/or ed
24、ition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of public
25、ation 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 ETSI TS 102 250-2: “Speech and multimedia Transmission Quality (STQ); QoS aspe
26、cts for popular services in mobile networks; Part 2: Definition of Quality of Service parameters and their computation“. i.2 ETSI TR 103 114: “Speech and multimedia Transmission Quality (STQ); QoS Parameters and measurement methodology for Smartphones“. 3 Definitions and abbreviations 3.1 Definition
27、s For the purposes of the present document, the following terms and definitions apply: IP Multimedia Subsystem (IMS): telecommunication system for standardized access to services from different networks NOTE: IMS specifications were created and are maintained by 3GPP. Over The Top (OTT): In the cont
28、ext of services which use standard services of a network but may use also proprietary protocols. NOTE: An example would be WhatsAppTMwhich uses packet data transfer to implement a group of services including but not limited to telephony, text messaging and file transfer. ETSI ETSI TR 103 482 V1.1.1
29、(2018-07) 63.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project IMS IP Multimedia Subsystem IP Internet Protocol MRAB Multi Radio Access Bearer OTT Over The Top QoE Quality of Experience QoS Quality of Service RAB Radi
30、o Access Bearer URL Uniform Resource Locator ViLTE Video over LTE VoIP Voice over IP VoLTE Voice over LTE 4 Basic considerations Concurrent or near-concurrent use of multiple services takes place in many user situations. In most cases, this happens unnoted, such as the download of an app update, e-m
31、ail, or some pre-scheduled music or video download during direct user activities such as telephony or web browsing. In addition, there are applications that directly support usage of multiple services, e.g. sending or receiving images, videos or other units of data during a conversation. Therefore,
32、the performance of a particular service may depend on the activity environment in which it is taking place. Existing network technologies already use resource optimization strategies, which make their behavior content-dependent. This context dependency can be expected to further increase. In upcomin
33、g 5G networks, this behavior is actually part of the design. Therefore, the importance of test strategies and subsequent methods of computation of data that support the concurrent use of multiple services, will increase. Consequently, test and measurement for QoS need to cover such situations, too.
34、The QoS standards literature recognizes a number of services. For each service, a set of QoS parameters is defined. This set is intended to express the quality of the service from a users point of view. Basically, there is a close connection between a service and a use case. In many cases, like tele
35、phony, this is a 1:1 relation - the service is essentially identical with the use case. In other cases, e.g. for Packet Data, a network-provided basic service provides the technical basis for a multitude use cases which belong to different end-user scenarios. Every use case has a number of parameter
36、s which further define how the service is being used. For the purpose of the present document, two types of parameters are distinguished. Please note that the term parameter is used here not only in the sense of a numerical value. For instance, mobile originated and mobile terminated calls are both
37、using the basic service “telephony“. Roles and activities are, in this sense, also parameters. External parameters describe what exactly the use case is supposed to do, such as the called number in telephony, the video URL in video streaming, the target URL in web browsing, or the data volume to be
38、transferred in an upload or download case. Internal parameters describe how it is done. An internal parameter would be the dial-time out or the time-out for a download. The basic requirement of repeatability demands that all these parameters have to be reported. Actually, in order to be able to repe
39、at a test, more information may be, and usually is, required, such as information about the used hardware and software of platforms, and of course the outer conditions of testing, such as the mode (drive/walk/stationary; type of vehicle or transport service). In a multi-service case, this distinctio
40、n is more complex, because the exact composition of a use case does not only include the parameters of each component service, but also the way these service uses are combined. In the simplest case, this is relative timing, e.g. in Multi-RAB the delay between the start of component service A and ser
41、vice B. It will be shown later in the present document, however, that actual relations can become much more complex. ETSI ETSI TR 103 482 V1.1.1 (2018-07) 7For some time, the Multi-RAB (MRAB) use case had rather high relevance and attention in the mobile network community. There is, however, no stan
42、dardized set of QoS parameters for this case. The closest case covered by QoS standardization is IMS Multimedia Telephony (ETSI TS 102 250-2 i.1, clause 6.12) which defines QoS parameters for the sub-services Telephony, Video, Text Messaging and file transfer (called File Sharing) as well as some Qo
43、S parameters for changing media composition. Market solutions for MRAB, which came up during the 3G period of mobile network evolution, were characterized by an explicit diagnostic viewpoint. As resource management relates closely to basic mobile network processes, cross-action could take place. For
44、 instance, setting up packet data transfer could impact existing telephony connections and vice versa. Consequently, the QoS parameters set had explicit members, which expressed this interaction, e.g. the probability that a packet data setup led to a cut-off of the telephony connection. These consid
45、erations lead to a fundamental question regarding a general multi-service framework, namely if this framework should also consider interaction between component services. This issue will be discussed in the next clause along with some basic considerations about the function or role of QoS parameters
46、. 5 Function and functional limitations of QoS parameters The main purpose of QoS parameters, as stated in literature, is to provide information about the quality of a service from a users point of view. Actually, many QoS parameters defined in standardization also have a pronounced “diagnostic“ ang
47、le. Using lower protocol layers as the points of observation (e.g. the IP layer, or Layer 3 messaging events) has assumedly the purpose of abstracting from user interface details. However, these layers typically also offer a high degree of detail or granularity, which is used to define a relatively
48、large number of sub-phases for a transaction, and, consequentially, QoS parameters. Often, these phases are not directly linked to user-observable activities or distinguishable elements of user perception. From a diagnostic point of view, the correlation between events can play an important role. As
49、 the example of MRAB shows, the setup of one service can lead to a disruption or degradation in the performance of another service. Expressing such relations in QoS parameters would be one way of creating diagnostically useful information. The downside, however, is the exponential increase (combinatorial explosion) in QoS parameters when services are combined in a multi-service use case scenario. It also does not make sense to assume a causal relationship between actions in general. For instance, it is reasonable to assume that the probability that an action of one
