hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.16 O | oneM2M Feature: oneM2M-defined procedure used for the instantiation of a M2M Common Service, which may not be further decomposed/divided, used for the purpose of testing and certification oneM2M Feature Set: collection of oneM2M Features that jointly need to be supported by M2M Common Service, used for the purpose of t... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.17 P | Privacy [i.2]: right of individuals to control or influence what information related to them may be collected and stored and by whom and to whom that information may be disclosed Privilege: qualification given to an entity that allows a specific operation (e.g. Create/Retreive/Update/Delete, etc.) on a specific resourc... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.18 Q | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.19 R | Registrar: legal entities that will directly interface with App Developers seeking App-IDs and can assign unique IDs Remote Security Provisioning: process of providing a credential into a secure environment of a Node deployed in the field Repudiation: denial by an entity of a claimed event or action NOTE: This definiti... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.20 S | Secure [i.12]: not vulnerable to most attacks, are able to tolerate many of the attacks that they are vulnerable to, and that can recover quickly with a minimum of damage from the few attacks that successfully exploit their vulnerabilities Security [i.5]: system condition that results from the establishment and mainten... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.21 T | Time Series Data: sequence of data points which typically consist of successive measurements made over a time interval Thing: element which is individually identifiable in the oneM2M system Trust [i.8]: relationship between two elements, a set of activities and a security policy in which element x trusts element y if a... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.22 U | Underlying Network: functions, networks, busses and other technology assisting in data transportconnectivity services |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.23 V | Verification [i.10]: confirmation, through the provision of objective evidence, that specified requirements have been fulfilled Virtual Device: logical device (implemented as software) that acts similar to physical M2M Device and provides derived data EXAMPLE: Average temperature of a room, number of vehicles that pass... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.24 W | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.25 X | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.26 Y | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.27 Z | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4 Abbreviations | |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.1 0-9 | 3GPP 3rd Generation Partnership Project |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.2 A | ACL Access Control List ADN Application Dedicated Node AE Application Entity API Application Programming Interface AR Application Registrants ARA M2M App-ID Registration Authority ASN Application Service Node |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.3 B | BBF Broadband Forum ETSI ETSI TS 118 111 V4.1.1 (2023-09) 16 oneM2M TS-0011 version 4.1.1 Release 4 |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.4 C | CHA Continua Health Alliance CPU Centralized Processing Unit CSE Common Services Entity CSF Common Services Function |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.5 D | DAS Dynamic Authorization System DM Device Management |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.6 E | E2EKey End-to-End Certificate-based Key Establishment ESData End-to-End Security of Data ESPrim End-to-End Security of Primitives |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.7 F | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.8 G | GBA Generic Bootstrapping Architecture GSM Global System for Mobile communications GSMA GSM Association |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.9 H | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.10 I | IN Infrastructure Node IP Internet Protocol IPE Interworking Proxy application Entity |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.11 J | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.12 K | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.13 L | LWM2M Lightweight M2M. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.14 M | M2M Machine to Machine ETSI ETSI TS 118 111 V4.1.1 (2023-09) 17 oneM2M TS-0011 version 4.1.1 Release 4 MA Management Authority MN Middle Node MSISDN Mobile Subscriber Integrated Services Digital Network-Number MTC Machine Type Communications |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.15 N | NSE Network Service Entity |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.16 O | OMA Open Mobile Alliance |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.17 P | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.18 Q | QoS Quality of Service |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.19 R | RBAC Role-Based Access Control |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.20 S | S&A Sensing and Actuation SDO Standards Developing Organization SMS Short Message Service |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.21 T | TR Technical Report TS Technical Specification |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.22 U | UICC Universal Integrated Circuit Card USIM Universal Subscriber Identity Module USSD Unstructured Supplementary Service Data URI Universal Resource Identifier |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.23 V | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.24 W | WAN Wide Area Network ETSI ETSI TS 118 111 V4.1.1 (2023-09) 18 oneM2M TS-0011 version 4.1.1 Release 4 |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.25 X | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.26 Y | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 4.27 Z | Void. ETSI ETSI TS 118 111 V4.1.1 (2023-09) 19 oneM2M TS-0011 version 4.1.1 Release 4 Annex A (informative): Bibliography • oneM2M TR-0005: "Roles and Focus Areas". ETSI ETSI TS 118 111 V4.1.1 (2023-09) 20 oneM2M TS-0011 version 4.1.1 Release 4 History Document history V4.1.1 September 2023 Publication |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in ETSI TS 118 101 [1] and ETSI TS 118 104 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. The objective of the present document is to provide a basis for conforma... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 2 References | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 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... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 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... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 3 Definition of terms, symbols and abbreviations | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 3.1 Terms | For the purposes of the present document, the terms given in ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [5] and ETSI TS 118 115 [i.2] apply. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 3.2 Symbols | Void. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [i.4] and the following apply: AE Application Entity APT Abstract Protocol Tester ATM Abstract Test Method ATS Abstract Test Suite CoAP Constrained Application Protocol CSE Common Service Entity HTTP HyperText Transfer Protocol IP Inte... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5 Abstract Test Method (ATM) | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 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 oneM2M test suite are described in figure 5.1-1. The test system will simulate valid and invalid protocol behaviour, and... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.2 Test Configuration | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.2.1 AE Test Configuration | Test configurations are defined to test different entities such as CSE and AE, etc. ETSI ETSI TS 118 119 V2.3.0 (2020-11) 9 oneM2M TS-0019 version 2.3.0 Release 2 Figure 5.2.1-1 shows a AE test configuration which is mapped to CF03 in clause 6.3.3.3 in ETSI TS 118 115 [i.2] and aligns with conformance test system archi... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.3 Test architecture | The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework (ETSI TS 118 115 [i.2]) where the TTCN-3 language and its architecture are recommended. Following this recommendation the oneM2M tester architecture comprises a non-platform d... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4 Ports and ASPs (Abstract Services Primitives) | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.0 Introduction | The oneM2M ATS implements the following ports: • The mcaPort and mcaPortIn. • The mccPort and mccPortIn. • The acPort. • The utPort. • The InfoPort. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.1 mcaPort, mcaPortIn, mccPort, mccPortIn | These ports are used to send and receive the following message sets: • Request Primitives messages in accordance with ETSI TS 118 104 [2]. • Response Primitives messages in accordance with ETSI TS 118 104 [2]. Two primitives are currently defined for these ports indicated in table 5.4.1-1: 1) The M2MRequestPrimitive - ... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2 utPort | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.0 Introduction | The utPort is included in the oneM2M ATS in order to be able to stimulate the IUT and receive extra information from IUT upper layers. For instance, the utPort can be applied to automate AE testing shown in clause 5.4.2.1. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.1 Usage for Automated AE Testing | The utPort is in charge of the communication between TTCN-3 Test Component module in Test System and the Upper Tester Application in SUT. Functionalities that TTCN-3 Test Component module and the Upper Tester Application are required to implement are listed as follows: • TTCN-3 Test Component is able to configure the T... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.2 Upper Tester Control Primitives | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.2.1 Introduction | The upper tester triggering message is used to transport control commands between Test System and the Upper Tester Application. The control command will contain essential parameters that are required for certain test case. The upper tester triggering message type maps to particular message formats for exchanging data a... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.2.2 UtTrigger and UtTriggerAck Primitives | The UtTrigger primitive is initialized by the Test System to send triggering message to the target IUT as depicted in figure 5.4.2.2.2-1. The IUT will send acknowledgement message back to the Test System using UtTriggerAck primitive if trigger message is successfully transported to the IUT. Then IUT starts interaction ... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.2.3 Control Communication Protocol | Protocol used for proceeding communications between TS and Upper Tester Application is designated to the Hypertext Transfer Protocol (HTTP) protocol owning it is an application protocol that is widely supported by most all IoT devices and various intrinsic features such as persistent connection, ease of programming, fl... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.2.2.4 Control Message Serialization | Control commands that are wrapped within a request body of HTTP message shall be serialized into JavaScript Object Notation (JSON) because it is very lightweight and easy to parse and generate for machines. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.3 acPort | The acPort is included in the oneM2M ATS in order to be able to control and configure the test adaptor for specific cases. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.4.4 infoPort | The infoPort is included in the oneM2M ATS in order for the TTCN-3 test components to be able to exchange information such as last response primitives or request primitives received by a component, retrieved primitive contents. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.5 Test components | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.5.1 Tester | The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described in table 5.5.1-1. ETSI ETSI TS 118 119 V2.3.0 (2020-11) 17 oneM2M TS-0019 version 2.3.0 Release 2 Table 5.5.1-1: Tester component elements Name Instance type Element type Descripti... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.5.2 AeSimu | The AeSimu test component extends the Tester component by adding elements specific to an AE entity. Table 5.5.2-1 summarizes those elements. Table 5.5.2-1: AeSimu component elements Name Instance type Element type Description mcaPort port oneM2MPort Port that implements the mca interface when test system is the client ... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.5.3 CseSimu | The CseSimu test component extends the Tester component by adding elements specific to an CSE entity. Table 5.5.3-1 summarizes those elements: Table 5.5.3-1 Name Instance type Element type Description mcaPort port OneM2MPort Port that implements the mca interface when test system is the client (sending requests) mcaPor... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 5.6 Test strategy | This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilitates an easy navigation throw the different test steps. The use of the TTCN-3 MTC and PTC(s) is as depicted in figure 5.6-1. Figure 5.6-1 At the start of the test ... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 6 Untestable Test Purposes | Void. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7 ATS Conventions | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.0 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... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.1 Testing conventions | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.1.1 Testing states | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.1.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. |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.1.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. ETSI ETSI TS 118 119 V2.3.0 (2020-11) 20 oneM2M TS-0019 version 2.3.0 Release 2 As neces... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.2 Naming conventions | |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.2.1 General guidelines | This test suite follows the naming convention guidelines provided in ETSI TS 118 115 [i.2]. 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.2.1-1) indicating the type of TTCN-3 element it represen... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.2.2 oneM2M specific TTCN-3 naming conventions | Next to such general naming conventions, table 7.2.2-1 shows specific naming conventions that apply to the oneM2M TTCN-3 ATS. Table 7.2.2-1: oneM2M specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier oneM2M Module Use upper-case initial letter OneM2M_ OneM2M_Testcases_ Module... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.2.3 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... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.2.4 Test Case (TC) identifier | Table 7.2.4-1: TC naming convention Identifier: TC_<root>_<gr>_<sgr>_<nn>_<per> <root> = root ONEM2M oneM2M <gr> = group CSE CSE testing AE AE testing <sgr> = subgroup REG Registration DMR Data Management and Repository SUB Subscription and Notification GMG Group Management DIS Discovery LOC Location DMG Device Managem... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 7.3 IXIT | The following parameters are used by the oneM2M ATS for the correct execution of the test cases. Table 7.3-1: oneM2M ATS IXITs GROUP IXIT NAME DESCRIPTION DEFAULT VALUE IutParameters PX_IN_CSE MN-CSE true PX_MN_CSE IN-CSE false PX_ASN_CSE ASN-CSE false PX_SUT_ADDRESS SUT address "127.0.0.1:8080" PX_UT_IMPLEMENTED Upper... |
f215c66b432ed5d802cfdaafebadf0dc | 118 119 | 8 TTCN-3 Verifications | The principles for Verifying the TTCN-3 test code are given in ETSI TS 118 115 [i.2]. All test cases provided with the present document in annex A which correspond to at least one of the product profiles defined in ETSI TS 118 125 [i.3] have been verified at the time of publication of the present document which corresp... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 1 Scope | The present document specifies oneM2M test suite structure and test purposes that are designed to evaluate the conformity of oneM2M implementations to the oneM2M specifications. It also specifies: • guidelines for description of test behaviours and definition of test purpose structure; • notations to define a test purp... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 2 References | |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 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. The following referenced doc... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 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] oneM2M Drafting Rules. NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 3 Definition of terms, symbols and abbreviations | |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 115 [3] Testing Framework and the following apply: valid <OPERATION> Request: oneM2M Request primitive that only contains all mandatory primitive parameters with correct values which are not required to be explicitly specified in the test purpose ... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 3.2 Symbols | Void. |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 101 [1] and the following apply: ADN Application Dedicated Node ADN-AE AE which resides in the Application Dedicated Node AE Application Entity AE-ID Application Entity-IDentifier APP-ID APPlication IDentifier ASN Application Service Node ... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 5 Prerequisites and Test Configurations | |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 5.1 Test Configurations | Test configurations are defined to test different entities such as CSE and AE etc. Figure 5.1-1 and Figure 5.1-2 show CSE test configurations where CSE as a IUT can be tested against TTCN-3 Test System, which is acting as AE or AE and CSE respectively. Test system may include as well other entities which are necessary ... |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 6 Test Suite Structure (TSS) | |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 6.1 Test groups | |
86bb51039c7d46c1c45390deedd919e6 | 118 118 | 6.1.0 Overview | The test groups are organized in 2 levels. The first level defines the functional entity of oneM2M. The second level defines the common services functions which are represented in oneM2M functional architecture. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.