hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 4.2 Coexistence between ETCS and non-ETCS applications | ETCS application can be the only service using GPRS/EGPRS bearer or together with other non-ETCS applications (simultaneous operation of ETCS/non-ETCS applications). Latter scenario requires a strict separation of the different traffic types using different QoS profile parameters as part of the subscription and the pro... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 4.3 Reference 3GPP Release | All GSM GPRS features that are referenced in the present document shall be implemented to fulfil in minimum 3GPP Release 4 GERAN, based on A/Gb mode operation. Specific timer and counter specification of the normative references shall be supported, except the subsequent chapters indicating specific values for the opera... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 4.4 Applicability | The present document shall only apply to Mobile Terminals of an ETCS Data Only Radio. |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5 Bearer services and features for ETCS operation | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1 Basic features | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.0 General | The features that are listed in this clause are considered for ETCS operation. |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.1 Network - Bearer Service capabilities | The GSM-R network shall support all mandatory GPRS bearer services capabilities in the radio access domain (BSS) according to: • ETSI TS 123 002 [1] • ETSI TS 123 060 [2] • ETSI TS 123 107 [3] • ETSI TS 143 064 [10] • ETSI TS 144 018 [11] • ETSI TS 144 060 [12] • ETSI TS 145 001 [16] • ETSI TS 145 002 [17] • ETSI TS 14... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.2 Mobile - Bearer Service capabilities | The Mobile Stations to be used for ETCS operation shall provide GPRS and EGPRS bearer service capabilities which comply to: • ETSI TS 123 002 [1] • ETSI TS 123 060 [2] • ETSI TS 123 107 [3] • ETSI TS 124 008 [5] • ETSI TS 103 368 [6] ETSI ETSI TS 103 328 V1.2.2 (2020-05) 11 • ETSI TS 143 064 [10] • ETSI TS 144 018 [11]... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.3 Quality of Service Management | In order to allow basic QoS management, Mobile Stations and the Network shall support 3GPP QoS concept and architecture according to ETSI TS 123 107 [3]. The relevant network entities and the Mobile Stations shall be able to process non-Guaranteed Bitrate traffic classes, Interactive and Background, between the specifi... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.4 Multislot Operation | GPRS and EGPRS bearer services offers Multislot operation. Possible Multislot configuration/classes shall be implemented according to ETSI TS 145 002 [17]. |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.5 Optimized LLC-PDU delivery | During the lifetime of an ETCS data communication, the ability of cell change processing and the related GPRS Mobility Management is a basic requirement to the Mobile Stations and the network. Due to Mobile Station controlled cell reselection, downlink user data which are not delivered, shall be forwarded to the new se... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.6 Mobility | Mobility Management is one of the key features in GSM. Cell change under GPRS conditions is supported by the cell reselection procedure determined by the Mobile Station. To lower the impact of cell reselection process to the user data packet transfer delay at least Network Assisted Cell Change (NACC) processing accordi... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.7 Gathering radio resources | Regardless of the ETCS user data exchange characteristics, other features are of interest to improve the overall data transfer delay performance. During the phase of gathering Uplink resources, the network assigns the access to the network either in a two phase packet access or in an one phase packet access procedure a... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.8 Radio resource allocation | GPRS Radio Resource (TBF Management) Allocation and release follows the "On demand" principle according to ETSI TS 143 064 [10]. If no further user data are to be exchanged, GPRS radio resources get released after a certain guard time. The inter arrival time of ETCS application messages is rather low and would cause ad... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.9 Automatic GPRS Attach | GPRS Attach procedure according to ETSI TS 124 008 [5] is used to register the Mobile Station towards the applicable Mobility Management node in the network. According to ETSI TS 103 368 [6], the procedure can be ordered manually by using the applicable command or initiated automatically when GPRS is supported in the s... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.1.10 Summary basic features | Table 1 summarizes the basic feature requirements for the operation of ETCS in PS-mode using GPRS/EGPRS bearer services which shall be met by Mobile Stations and network as indicated. Table 1: Basic features Service/Feature Applicable for Network M - Mandatory O - Optional NA - Not Applicable Applicable for Mobile Stat... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.2 Mixed packet data traffic operation | |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.2.0 General | The features that are listed in this clause are considered for simultaneous operation of ETCS and non-ETCS applications. |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.2.1 Quality of Service Management | Simultaneous operation of ETCS and non-ETCS applications may cause unexpected transfer delay to ETCS if the QoS profile parameters are treated always as best effort or best effort with priority. The concept of Packet Flow Context (PFC) according to ETSI TS 123 060 [2] and ETSI TS 148 018 [15] improves the QoS handling ... |
f8b0f307f93593f7c742adb8d1233583 | 103 328 | 5.2.2 Summary mixed packet data traffic operation | Table 2 summarizes the required features for simultaneous operation of ETCS and non-ETCS applications which shall be met by mobile stations and network as indicated. Table 2: Performance enhancing features part 2 Service/Feature Applicable for Network M - Mandatory O - Optional NA - Not Applicable Applicable for Mobile... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for SmartAppliances as defined in ETSI TS 103 264 [1] and ETSI TS 103 267 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [6]. The objective of the present document is to provide a basis for... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 2 References | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 3 Definitions and abbreviations | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 118 115 [5], in ETSI TS 118 112 [4] and in ISO/IEC 9646-7 [6] apply. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 115 [5], ETSI TS 103 264 [1], ETSI TS 118 112 [4] and the following apply: AE Application entity APT Abstract Protocol Tester ATM Abstract Test Method ATS Abstract Test Suite BI Invalid behaviour BV Valid behaviour CoAP Constrained Applica... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 4 Prerequisites and Test Configurations | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 4.1 Test Configurations | Figure 4.1-1: Test configuration 1 (CF01) Figure 4.1-2: Test configuration 2 (CF02) Figure 4.1-3: Test configuration 3 (CF03) IUT TEST SYSTEM AE CSE Mca Mcc IUT TEST SYSTEM AE CSE Mca CSE IUT TEST SYSTEM CSE AE Mca ETSI ETSI TS 103 268-4 V1.1.1 (2017-04) 9 |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5 Abstract Test Method (ATM) | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.1 Abstract protocol tester | An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address a single test objective. APTs used by the SmartAppliances test suite are described in figure 5.1-1. The test system will simulate valid and invalid protocol behav... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.2 Test Configuration | This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates a CSE on Mca interface as defined in Test configuration 3 (CF03) in Figure 4.1-3. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.3 Test architecture | The approach for the implementation of an Abstract Protocol Tester selected in SmartAppliances follows the recommendation of the oneM2M Testing Framework defined in ETSI TS 118 115 [5] where the TTCN-3 language and its architecture are recommended. Following this recommendation the SmartAppliances tester architecture c... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.4 Ports and ASPs (Abstract Services Primitives) | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.4.1 Introduction | The SmartAppliances ATS implements four ports: • The mcaPort • The mccPort • The acPort • The utPort |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.4.2 mcaPort and mccPort | These ports are used to send and receive the following message sets; • Request Primitives messages in accordance with ETSI TS 118 104 [3]. • Response Primitives messages in accordance with ETSI TS 103 267 [2]. Two primitives are currently defined for this port: 1) MsgOut - to send oneM2M messages to the IUT. Depending ... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.4.3 utPort | The utPort has been included in the SmartAppliances ATS in order to be able to stimulate the IUT and receive extra information from IUT upper layers. The utPort is not used in the current implementation and is provided for future extension. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.4.4 acPort | The acPort has been included in the SmartAppliances ATS in order to be able to control and configure the test adapter for specific cases. ETSI ETSI TS 103 268-4 V1.1.1 (2017-04) 13 The acPort is not used in the current implementation and is provided for future extension. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 5.5 External functions | The following external functions are defined: • fx_base64ToBitstring - Description: Converts a base64-encoded blob into bitstring - Parameters: p_base64 - Base64-encoded blob to be converted - Returns: bitstring corresponding to the de-encoded version of the base64 blob |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 6 Untestable Test Purposes | No untestable Test Purpose. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7 ATS Conventions | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the naming conventions and... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.2 Testing conventions | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.2.1 Testing states | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.2.1.1 Initial state | All test cases start with the function f_preamble_XYZ. This function brings the IUT in an "initialized" state by performing some actions such as registration of AE, creation of auxiliary access control policy resource, creation of additional needed resources. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.2.1.2 Final state | All test cases end with the function f_postamble_XYZ. This function brings the IUT back in an "idle" state which means deletion of all created resources being used by the test case so that next test case execution is not disturbed. As necessary, further actions may be included in the f_postamble functions. ETSI ETSI TS... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3 Naming conventions | |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3.1 Introduction | This test suite follows the naming convention guidelines provided in ETSI TS 118 115 [5]. |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 7.3.2-1) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 7.3.2-1... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3.3 SmartAppliances specific TTCN-3 naming conventions | Next to such general naming conventions, table 7.3.3-1 shows specific naming conventions that apply to the SmartAppliances TTCN-3 ATS. Table 7.3.3-1: oneM2M specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier oneM2M Module Use upper-case initial letter SmartAppliances_ SmartA... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, TIMEOUT, NONE. • Free text. EXAMPLE 1: log("f_utInitializeIut: INFO: IUT initialized"); Furthermore, the fol... |
651f5b531a0d5576fab4cb82ffda07f3 | 103 268-4 | 7.3.5 Test Case (TC) identifier | Table 7.3.5-1: TC naming convention Identifier: TC_<root>_<gr>_<sgr>_<x>_<nn> <root> = root SAP SmartAppliances <gr> = group SAREF <sgr> = subgroup <x> = type of testing BV Valid Behaviour tests BI Invalid Behaviour tests <nn> = sequential number 001 to 999 EXAMPLE: TP identifier: TP/SAP/SAREF//BV/001 TC identifier: TC... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for Conformance test specifications for Smart Appliances testing as defined in ETSI TS 103 268-1 [3] and ETSI TS 118 115 [5] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 2 References | |
dbc2d232be9fee185759421134282448 | 103 268-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 referenced document (including any amendments) applies. Referenced documents which a... |
dbc2d232be9fee185759421134282448 | 103 268-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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 3 Definitions and abbreviations | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 103 268-1 [3], in ETSI TS 118 112 [2] and in ISO/IEC 9646-7 [4] apply. ETSI ETSI TS 103 268-3 V1.1.1 (2017-04) 6 |
dbc2d232be9fee185759421134282448 | 103 268-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 268-1 [3], ETSI TS 103 264 [1] and ETSI TS 118 112 [2] and the following apply: API Application Programming Interface EUT Equipment Under Test IFS Interoperable Features Statement IUT Implementation Under Test IWF InterWorking Function PIC... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 4 Prerequisites and Test Configurations | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 4.1 Test Configurations | Figure 4.1-1: Test configuration 1 (CF01) Figure 4.1-2: Test configuration 2 (CF02) IUT TEST SYSTEM AE CSE Mca Mcc IUT TEST SYSTEM AE CSE Mca CSE ETSI ETSI TS 103 268-3 V1.1.1 (2017-04) 7 Figure 4.1-3: Test configuration 3 (CF03) |
dbc2d232be9fee185759421134282448 | 103 268-3 | 5 Test Suite Structure (TSS) | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 5.1 Structure for SAP tests | Table 5.1-1 shows SAP Test Suite Structure (TSS) including its subgroups defined for conformance testing. Table 5.1-1: TSS for oneM2M Root Group Sub-group category SAP SAREF Valid behaviour Valid behaviour Valid behaviour Valid behaviour Valid behaviour Valid behaviour The test suite is structured as a tree with the ro... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6 Test Purposes (TP) | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1 Introduction | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1.1 TP definition conventions | The TPs are defined by the rules shown in table 6.1.1-1. Table 6.1.1-1: TP definition rules TP Header TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming conventions defined in clause 6.1.2. Test objective Short description of test purpose objective according to the requirements fro... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1.2 TP Identifier naming conventions | The identifier of the TP is built according to table 6.1.2-1. Table 6.1.2-1: TP naming convention Identifier: TP/<root>/<gr>/<sgr>/<x>/<nn> <root> = root <gr> = group <sgr> = subgroup <x> = type of testing BV Valid Behaviour tests BI Invalid Syntax or Behaviour Tests BO Inopportune Behaviour <nn> = sequential number 01... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1.3 Rules for the behaviour description | The description of the TP is built according to ETSI TS 103 268-1 [3]. |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1.4 Sources of TP definitions | All TPs are specified according to ETSI TS 103 264 [1] and ETSI TS 118 112 [2]. ETSI ETSI TS 103 268-3 V1.1.1 (2017-04) 9 |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.1.5 Mnemonics for PICS reference | To avoid an update of all TP tables when the PICS document is changed, table 6.1.5-1 introduce mnemonics name and the correspondence with the real PICS item number. Table 6.1.5-1: Mnemonics for PICS reference Mnemonic PICS item PICS_AE A.5.1/1 [1] PICS_CONTAINER A.5.1/1 [1] PICS_FLEXCONTAINER A.5.1/1 [1] PICS_GENERIC_I... |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.2 Test purposes for SAP Testing | |
dbc2d232be9fee185759421134282448 | 103 268-3 | 6.2.1 SAREF | TP Id TP/SAP/SAREF/BV/001 Test objective Check that the IUT creates for an instantiation of a class of the Base Ontology a oneM2M resource of type <semanticDescriptor> containing a descriptor attribute containing the instantiated class in RDF data. Reference ETSI TS 118 112 [2], clause 7.1.1.1 Config Id CF03 PICS Selec... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 1 Scope | The goal of the present document is to provid the following aspects: • A clear and unambiguous terminolo used to address quality of experienc • A theoretical and abstract model for • An operational and generic abstracti • The specification of a software agen F ETSI ETSI TS 103 2 6 de a concept for addressing quality of... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 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 ar... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] 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". [2] Recommendation ITU-... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 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 Workshop on QoS / QoE / User experience focusing on speech / multimedia conference tools, Workshop report, 21-22 September 2010, Sophia-Antipolis... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 3 Definitions and abbreviations | |
586dd07d2b61de0e16afa143b823375a | 103 294 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: actor: abstract entity representing an individual person, a group of persons, an organization or a company NOTE: If needed, an organization can be represented by a group of actors sharing a common interest or purpose. application: set ... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ARCU Application-Resource-Context-User ASN1 Abstract Syntax Notation One HD High Definition HTTP HyperText Transfer Protocol IETF Internet Engineering Task Force IF Influence Factor IP Internet Protocol IP... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 4 Modeling QoE - The ARCU Model | Different types of services, and indeed different individual services can have very variable QoE characteristics, for example with relation to the network performance, or the processing power they have available. Creating proper service taxonomy for QoE taking all these possible dependencies into account is extremely h... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 6.1 Stand-alone and distributed QoE-Agents | Figure 8 presents an adequate description for embedding a QoE-Agent in a single device/monitoring equipment (ME). Data and metric values can however be collected on remote devices/equipments (RE) and provided to the QoE-Agent using its communication API (i.e. the API of the Communication object) using SNMP. When requir... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 6.3 Communication Aspects | Communications related to QoE-Agents are of two types: 1) Internal communications: these are the communications between master QoE-Agents and slaves QoE-Agents. 2) External Communications: these are the communications between a QoE-Agent and other entities like probes, QoE-aware applications or other QoE-Agents. |
586dd07d2b61de0e16afa143b823375a | 103 294 | 6.3.1 Internal Communications | Internal communications take place between a master QoE-agent and its associated slaves QoE-Agents. All internal communications have to be done using SNMP. |
586dd07d2b61de0e16afa143b823375a | 103 294 | 6.3.2 External Communications | The default external communications shall be done using either SNMP (see J. Case et al. [i.21]) or HTTP (see R. Fielding et al. [i.22]). As a consequence, implementations of QoE-Agents shall include at least these two protocols. Users should however have the possibility to include their own code in the QoE-Agent to bro... |
586dd07d2b61de0e16afa143b823375a | 103 294 | 6.4 The QoE-Agent Implementation | A complete specification of a QoE-Agent fulfilling the constraints described in the previous clauses is provided in T. Mäki [i.23]. A UML description of the Java implementation is given in Figure 14. This implementation includes the SNMP interface for internal communications as well as the default (SNMP-based and HTTP-... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 1 Scope | The scope of the present document is to support Smart Appliance common ontology and communication framework testing needs. It specifies a global methodology for testing for Smart Appliances, based oneM2M specifications. It analyses the overall testing needs and identifies and defines the additional documentation requir... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 2 References | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 3 Definitions and abbreviations | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 10746 [i.8], ETSI TS 103 264 [1], ETSI TS 103 267 [2], ETSI TS 118 101 [3], ETSI TS 118 104 [4] and the following apply: conformance testing: process for testing that an implementation is compliant with a protocol standard, which is realiz... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 10746 [i.8], ETSI TS 103 268-2 [i.9], ETSI TS 118 101 [3], ETSI TS 118 104 [4] and the following apply: API Application Programming Interface ATS Abstract Test Suite DUT Device Under Test EUT Equipment Under Test IFS Interoperable Features Stateme... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 4 Introduction to the SAP testing methodology | The present document provides: • Identification of the implementations under test (IUT) for conformance testing and the device under test (DUTs) for interoperability, i.e. answering the question "what is to be tested". • Definition of the applicable test procedures, i.e. answering the question "how is to be tested". • ... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5 Conformance testing | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.1 Introduction | The following clauses show how to apply the ETSI conformance testing methodology to SAP M2M in order to properly produce SAP M2M conformance test specifications. The Conformance testing can show that a product correctly implements a particular standardized protocol, that is, it establishes whether or not the implementa... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.2 Implementation Under Test | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.2.1 Introduction | The "Implementation Under Test" (IUT) is a protocol implementation considered as an object for testing. This means that the test process will focus on verifying the compliance of this protocol implementation (IUT) with requirements set up in the related base standard. An IUT normally is implemented in a "System Under T... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.2.2 Service Layer Communication | |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.2.2.1 oneM2M implementation | Table 5.2.2.1-1 shows the IUTs for oneM2M reference architecture as defined in ETSI TS 118 101 [3]. Table 5.2.2.1-1: IUTs for oneM2M IUT (node) Entities Interfaces Notes ASN Application Entity (AE) Mca Common Services Entity (CSE) Mca, Mcc, Mcn ADN Application Entity (AE) Mca MN Application Entity (AE) Mca Common Servi... |
ad6d8a84f35fc219abcc0f2eea83ed6c | 103 268-1 | 5.2.2.2 SAP implementation | In Smart Appliance Testing, only the AE is tested. Table 5.2.2.2-1: IUTs for Smart Appliance IUT (node) Entities Interfaces Notes ASN Application Entity (AE) Mca ADN Application Entity (AE) Mca MN Application Entity (AE) Mca IN Application Entity (AE) Mca |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.