hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.7.1 Message overview | RTC_ICE_CANDIDATE messages are sent from the participants to the Audio_Video signalling room after having sent an RTC_SESSION_DESCRIPTION "offer" message, and are sent from the Audio_Video signalling room after having answered with an RTC_SESSION_DESCRIPTION "answer" message. They are used to exchange the ICE candidate... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.7.2 Examples | Message sent from a participant to the Audio_Video signalling room: { "type":"RTC_ICE_CANDIDATE", "user":{ "name":"PSAP 1", "role":"PSAP", "uniqueId":"ljfvgtsy26540" }, "candidate":{ "candidate":"candidate:943110355 1 udp 41885695 36.181.54.52 51484 typ relay raddr 0.0.0.0 rport 0 generation 0 ufrag Ylsq network-id 1 n... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.8 USER_MEDIA message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.8.1 Message overview | The USER_MEDIA message is sent from the participants to the Audio_Video signalling room, and when the Audio_Video signalling room receives a MEDIA_CONTROL message it broadcasts it to all the participants of the room. It is used to inform other participant about what a participant is doing with the streams of the Audio_... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.8.2 Examples | Message sent from a participant to the Audio_Video signalling room: { "type":"USER_MEDIA", "audio":true, "video":false, "receiveAudio":true, "receiveVideo":true, "timestamp":1683893671026 } Message sent from the Audio_Video signalling room to a participant: { "type":"USER_MEDIA", "user":{ "name":"PSAP 1", "role":"PSAP"... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.9 MEDIA_CONTROL message | |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.9.1 Message overview | The MEDIA_CONTROL message is sent from the participants to the Audio_Video signalling room, and when the Audio_Video signalling room receives a MEDIA_CONTROL message it broadcasts it to all the participants of the room. It is used to request the Audio_Video signalling room to control the streams of users interacting wi... |
fc2c3fd5c4ea38b243e66c2ca9707c19 | 103 945 | 21.9.2 Examples | Message sent from a participant to the Audio_Video signalling room: { "type":"MEDIA_CONTROL", "media":"ALL", "action":"MUTE", "target":{ "name":"+34611223344", "role":"CALLER", "uniqueId":"jgh204nq9md" }, "timestamp":1683893671026 } Message sent from the Audio_Video signalling room to a participant: { "type":"MEDIA_CON... |
619730927abf52d80150d045872478dc | 103 942 | 1 Scope | The scope of the present document is designed to guide users and developers involved in the security testing of IoT systems. While the testing approach described is primarily tailored to the IoTAC System Architecture, it can be adaptable to various IoT domains. The present document covers essential aspects of testing, ... |
619730927abf52d80150d045872478dc | 103 942 | 2 References | |
619730927abf52d80150d045872478dc | 103 942 | 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 ... |
619730927abf52d80150d045872478dc | 103 942 | 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... |
619730927abf52d80150d045872478dc | 103 942 | 3 Definition of terms, symbols and abbreviations | |
619730927abf52d80150d045872478dc | 103 942 | 3.1 Terms | For the purposes of the present document, the following terms apply: black-box testing: testing without an understanding of the system's internal structure Dynamic Application Testing (DAST): testing methodology that analyses a running application for potential security vulnerabilities during execution functional secur... |
619730927abf52d80150d045872478dc | 103 942 | 3.2 Symbols | Void. |
619730927abf52d80150d045872478dc | 103 942 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AADRNN Auto-Associative DRNN AD Attack Detection ADT Attack Detection Training AI Artificial Intelligence ETSI ETSI TS 103 942 V1.1.1 (2023-11) 10 AID Application ID APDU Application Protocol Data Unit API Application Programming Interface AR ... |
619730927abf52d80150d045872478dc | 103 942 | 4 Specification of the IoT Modules | |
619730927abf52d80150d045872478dc | 103 942 | 4.1 IoTAC Secure Reference Architecture | ISO/IEC 30141 [1] provides a comprehensive and flexible framework that organizations can use to design and implement secure IoT systems in various domains. Its international recognition and emphasis on risk management make it a reliable choice for organizations looking to deploy secure IoT solutions. Despite this, ISO/... |
619730927abf52d80150d045872478dc | 103 942 | 4.2 IoTAC Modules | |
619730927abf52d80150d045872478dc | 103 942 | 4.2.1 Front End Access Management | The Front-end Access Management Module is a novel capability-based access control system. In this system, the responsibility of authorizing transactions and authenticating users is delegated to the front end, which refers to the secure element of the user. Upon registration with the access management system, users are ... |
619730927abf52d80150d045872478dc | 103 942 | 4.2.2 Run-time monitoring system | Runtime Monitoring System (RMS) is a comprehensive framework for data collection that offers the specifications and necessary implementation to enable real-time data collection, transformation, filtering, and management service. Its purpose is to support data consumers, including analytics algorithms responsible for de... |
619730927abf52d80150d045872478dc | 103 942 | 4.2.3 Attack Detection | The Attack Detection (AD) module uses a Machine Learning (ML) model called Dense Random Neural Network (DRNN), with novel network metrics provided from online traffic measurements. These measurement-based metrics are used as input data for learning by the AD module and for decision-making during normal operation. Thus,... |
619730927abf52d80150d045872478dc | 103 942 | 4.2.4 Honeypots | The honeypots are passive network participants that record and analyse network traffic to detect threats and attacks against network devices. As part of efforts to secure the IoT application network, a honeypot solution was implemented utilizing both classical and advanced detection techniques. The classical detection ... |
619730927abf52d80150d045872478dc | 103 942 | 4.2.5 AI-based Network Wide Attack Assessment | Network Wide Attack Assessment (NWAA) component detects the infected IoT devices by assessing the attack decisions made for individual devices via the Attack Detection component. NWAA module consists of two components which are ARNN Infected Device Detection (IDD) and ARNN Training (see Figure 7). IDD component, at eac... |
619730927abf52d80150d045872478dc | 103 942 | 5 Relevant Security Test Methods | |
619730927abf52d80150d045872478dc | 103 942 | 5.1 Functional and Security Testing | The approach for testing and evaluation of IoTAC run-time components is focused on the detection of functional errors and security vulnerabilities. The following three phases are defined: • Functional (Security) Testing - to verify the functionality of a component according to the functional requirements. The present d... |
619730927abf52d80150d045872478dc | 103 942 | 5.2 Static Application Security Testing (SAST) | Static Application Security Testing (SAST) is a testing methodology that analyses source code in an automated fashion to find security vulnerabilities that can make software applications in their runtime susceptible to cyber-attacks. SAST is realized with the usage of specialized tools, following formalized procedures ... |
619730927abf52d80150d045872478dc | 103 942 | 5.3 Dynamic Application Security Testing (DAST) | Non-functional security testing aims at identifying vulnerabilities through negative testing. The most prevalent technique is fuzz testing, a highly automated approach that generates randomly invalid and unexpected input data. More advanced approaches exploit information about the interface to generate semi-valid input... |
619730927abf52d80150d045872478dc | 103 942 | 5.4 TDL-TO as a specification technique | The Structured Text Objective (TDL-TO) as outlined in ETSI ES 203 119-4 [2], is an extension of the Test Description Language (TDL) meta-model created with the goal to enable more formal specification of structured test purposes and test objectives. The specification of TDL has matured into a standard comprised of mult... |
619730927abf52d80150d045872478dc | 103 942 | 5.5 A methodology for defining TDL-TO Test Purposes | Taking into account the IoTAC testing approach, the process of defining TDL-TO test purposes involves careful strategizing and the integration of both functional security tests and SAST cases into the process. DAST is an important part of the software development process to ensure the security of web applications. Howe... |
619730927abf52d80150d045872478dc | 103 942 | 6 Detailed List of Test Purposes | |
619730927abf52d80150d045872478dc | 103 942 | 6.1 Intra-component Test Purposes | |
619730927abf52d80150d045872478dc | 103 942 | 6.1.1 Front-End Access Management | TP Id TC_FEAM_02_01 Test Objective Ensure that a keypair is stored in keystore. Reference AFR02 Initial Conditions with { the IUT_FEAM has an empty keystore and the IUT_FEAM generates a new_TLS_keypair } Expected Behaviour ensure that { when { the IUT_FEAM stores the new_TLS_keypair containing new_TLS_keypair correspon... |
619730927abf52d80150d045872478dc | 103 942 | 6.1.2 Run-time Monitoring System | TP Id TC_RMS_01 Test Objective Ensure that a new Processor Definition is registered. Reference RTM_FR_6 Initial Conditions with { the IUT_RMS_ProcessingEngine being_in the deployed_state and the IUT_RMS_ProcessingEngine_Interface being_in the reachable_state } Expected Behaviour ensure that { when { the IUT_RMS_Process... |
619730927abf52d80150d045872478dc | 103 942 | 6.1.3 Attack Detection | TP Id TC_AD_01 Test Objective Ensure that the AD component detects Botnet attack packets with high accuracy. Reference AD_FR3, AD_NFR3 Initial Conditions with { the IUT_AD being_in the deployed_state and the IUT_AD being_in the trained_state and the IUT_AD being_in the default_state } Expected Behaviour ensure that { w... |
619730927abf52d80150d045872478dc | 103 942 | 6.1.4 Honeypots | TP Id TC_HP_01 Test Objective Ensure that the Honeypot can detect a common portscan attack. Reference HP_FR2 Initial Conditions with { the IUT_HP being_in the started_state and the IUT_HP being_in the default_state } Expected Behaviour ensure that { when { the IUT_HP receives a portscan containing more than 25 packets_... |
619730927abf52d80150d045872478dc | 103 942 | 6.1.5 AI-based Network Wide Attack Detection | TP Id TC_NWAA_01 Test Objective Ensure that the NWAA component successfully distinguishes compromised and normal devices in the considered IoT network. Reference NWAD_FR_1, NWAD_NFR_1 Initial Conditions with { the IUT_NWAA_IDD being_in the deployed_state and the IUT_NWAA_IDD being_in the trained_state } Expected Behavi... |
619730927abf52d80150d045872478dc | 103 942 | 6.2 Inter-component Test Purposes | TP Id TC_RMS_AD_001 Test Objective Ensure that the runtime monitoring system captures identified attacks by the attack detection module. Reference RTM_FR_4, RTM_FR_5, RTM_FR_6, AD_FR_1, AD_FR_2, AD_FR_3 Initial Conditions with { the IUT_RMS_ProcessingEngine being_in the deployed_state and // TODO: is that the correct I... |
619730927abf52d80150d045872478dc | 103 942 | 6.3 SAST Test Purposes | 6.3.1 Example SAST Test Cases and their TDL-TO Description for Critical/Blocker Vulnerabilities Below, a set of illustrative examples is provided for mapping commonly used SAST test cases, which encompass vulnerability assessments, code quality evaluations, and identification of security vulnerabilities, into TDL-TO fo... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 1 Scope | The present document specifies the Basic Transport Protocol (BTP) for the transport of packets among ITS stations. It resides on top of the GeoNetworking protocol specified in ETSI TS 103 836-4-1 [4] with its media-dependent extensions and below the ITS-S facilities layer. It provides an end-to-end, connection-less and... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 2 References | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-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... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-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... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 3 Definition of terms, symbols and abbreviations | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-3 [3] and the following apply: BTP-PDU: protocol Protocol Data Unit exchanged between BTP peer entities destination: receiving BTP entity in the ITS station destination port: port at which the destination is expected to listen for a BTP packet... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 3.2 Symbols | Void. |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 836-3 [3] and the following apply: BTP Basic Transport Protocol BTP-PDU Basic Transport Protocol Protocol Data Unit BTP-SAP Basic Transport Protocol Service Access Point GN-PDU GeoNetworking protocol PDU exchanged between peer entities of ... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 4 Services provided by the Basic Transport Protocol | The Basic Transport Protocol (BTP) provides an end-to-end, connection-less transport service in the ITS ad hoc network (ETSI TS 103 836-3 [3]). Similar to UDP (IETF RFC 768 [i.1]), it offers a minimal transport service, i.e. the non-guaranteed delivery of BTP-PDUs among BTP entities. It also allows protocol entities at... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 5 Format convention | The basic convention for the specification of packet formats is illustrated in figure 2. The bits are grouped into octets. The bits of an octet are always shown horizontally and are numbered from 0 to 7. Up to 4 octets are shown horizontally; multiple sets of 4 octets are grouped vertically. Octets are numbered from 0 ... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 6 BTP packet structure | As specified in ETSI TS 103 836-3 [3], the BTP is used in the GeoNetwork protocol stack. A BTP packet shall be comprised of the protocol headers and the payload as depicted in figure 3: • The access layer header is the header of the underlying ITS access technology. • The GeoNetworking header is the header of the GeoNe... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7 BTP header | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.1 Overview | BTP defines two protocol headers: • BTP-A for interactive packet transport; and • BTP-B for non-interactive packet transport. The headers are distinguished by the Next Header field in the GeoNetworking header (ETSI TS 103 836-4-1 [4]) as illustrated in table 1. Table 1: Encoding of BTP header types in the Next Header (... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.2 BTP-A header | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.2.1 Structure of the BTP-A header | The BTP-A header carries the source and the destination port (figure 4). The destination port identifies the protocol entity at the ITS facilities layer in the destination of a BTP-PDU. The source port indicates the port that the ITS facilities layer protocol entity in the source has used to send the ITS-FSDU. The sour... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.2.2 Fields of the BTP-A header | The BTP header shall carry the fields as specified in table 2. Table 2: Fields of BTP-A header Field # Field name Octet position Type Unit Description First Last 1 Destination port 0 1 16 bit integer Identifies the protocol entity at the destination's ITS facilities layer. 2 Source port 2 3 16 bit integer Identifies th... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.3 BTP-B header | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.3.1 Structure of the BTP-B header | The BTP-B header carries the destination port, but no source port (figure 5). The destination port identifies the protocol entity at the ITS facilities layer in the destination of a BTP-PDU and shall be set to the values in ETSI TS 103 248 [5]. The destination protocol provides additional info if Destination port is a ... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 7.3.2 Fields of the BTP-B header | The BTP-B header shall carry the fields as specified in table 3. Table 3: Fields of BTP-B header Field # Field name Octet position Type Unit Description First Last 1 Destination port 0 1 16 bit integer Identifies the protocol entity at the ITS facilities layer in the destination and shall be set to the values in ETSI T... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 8 Protocol operations | |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 8.1 General | This clause specifies the operations of a BTP entity for sending and receiving a BTP-PDU. |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 8.2 Source operations | On reception of a BTP-Data.request primitive, the source shall execute the following operations: 1) create a BTP-PDU with the ITS-FSDU as payload and a BTP packet header (clause 7): a) if the BTP type parameter in the BTP-Data.request primitive is BTP-A, set the BTP header fields as specified in table 4; Table 4: Field... |
e78622dc400ebfc07da3d34285c92ba5 | 103 836-5-1 | 8.3 Destination operations | On reception of a BTP-PDU via the GN-Data.indication primitive, the destination shall pass the payload of the BTP- PDU via the BTP-SAP by means of a BTP-Data.indication with the parameter settings in table 7. Table 7: Parameter settings in the GN-Data.indication primitive to indicate the reception of a BTP PDU Paramete... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) for ITS MRS service as defined in ETSI TS 103 759 [2] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to provide a basis for conformance tests for ITS Misbehaviour Reporting service in order to ... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 2 References | |
47021d2e806d414510fb595a318c7753 | 103 868-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... |
47021d2e806d414510fb595a318c7753 | 103 868-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... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 3 Definition of terms, symbols and abbreviations | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 097 [3], ETSI TS 103 868-1 [4], ETSI TS 103 868-2 [5], ETSI TS 102 871-3 [7], ISO/IEC 9646-6 [i.5] and ISO/IEC 9646-7 [i.6] apply. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 3.2 Symbols | Void. ETSI ETSI TS 103 868-3 V2.1.1 (2024-05) 8 |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 759 [2], ETSI TS 103 097 [3], ETSI TS 103 861-1 [4] and the following apply: ASP Abstract Service Primitive ATM Abstract Test Method ATS Abstract Test Suite BV Valid Behaviour tests ES ETSI Standard GN GeoNetworking HTML HyperText Markup L... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 4 Contents of the ITS MRS Test Suite | The ITS MRS test suite contains: • test implemented in TTCN-3 code; • certificate profiles and certificate generation tool. To execute the ITS MRS Test Suite a Test Adapter implementation and a TTCN-3 compiler are required. The reference Test Adapter implementation can be found at https://forge.etsi.org/rep/ITS/TS.ITS.... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5 Abstract Test Method | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.1 Introduction | This clause describes the ATM used to test the ITS MRS framework. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.2 Abstract protocol tester | The abstract protocol tester used by the ITS-Mrs test suite is described in Figure 1. The Test System simulates valid and invalid protocol behaviour and analyses the reaction of the IUT. ETSI ETSI TS 103 868-3 V2.1.1 (2024-05) 9 Figure 1: Abstract protocol tester - MRS |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3 Test Configuration | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.1 Introduction | This test suite shall use test configurations as defined in ETSI TS 103 868-2 [5], i.e. the tester simulates the MA implementing the ITS Mrs framework over HTTP protocol. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2 MRS infrastructure | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.1 Overview | Before executing tests: • security certificates need to be generated, see clause 5.3.2.5; • security certificates need to be installed onto the IUT, see clause 5.3.2.6; and • some Test System settings need to be configured, see clause 5.3.2.3. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.2 MRS certificate hierarchy | The required MRS certificate hierarchy of the test infrastructure shall be as specified in ETSI TS 102 940 [1] and ETSI TS 103 759 [2]. The following certificates are required for the test execution: 1) The custom user-generated root certificate, referred as CERT_IUT_A_RCA, is used to sign all CA certificates used by t... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.3 Test system settings | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.3.1 Test adapter settings | A reference test adapter has been developed and validated on the TTCN-3 runtime environments as listed in Table 2 and can be downloaded at https://forge.etsi.org/rep/ITS/ttcn/mbr_ts_103759.git. Table 2: TTCN-3 Tool Test Adapter Location TTCN-3 Tool Location TITAN AtsMBR.cfg The relevant test adapter parameters for the ... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.3.2 Test Suite Parameters | The MRS test suite parameters defined in ETSI TS 103 868-2 [5] shall be applied. In addition the parameters defined in ETSI TS 102 871-3 [7] and in ETSI TS 103 096-2 [8] shall be applied as listed in Tables 4 and 5. Table 4: PICS Parameters Parameter Reference Role Default value PICS_GN_SECURITY ETSI TS 102 871-2 [6], ... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.4 Certificate profiles | The ITS MRS Test Suite contains certificate profiles describing content of certificates to be used by both TS and IUT. Then certificate profiles are used by the Certificate Generation Tool to generate all necessary certificates, see clause 5.3.2.5. EXAMPLE: <certificate name="CERT_IUT_A_RCA" keep-existing="yes"> <versi... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.5 Certificate generation | Certificates can be generated based on certificate profiles using the certificate generation tool, provided as a part of the test suite. Certificate generation tool does not make any validation of the input profile, it just transforms the XML profile to the XER representation of the certificate, encode it to OER repres... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.3.2.6 Certificate installation | The ATS requires installing some certificates onto the IUT. The installation procedure is manual, customer dependent and out of scope of the present document. The list of certificates to be installed on the IUT is given in the certificate content definition, defined in ETSI TS 103 096-2 [8], clause 6.1.1 and ETSI TS 10... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.4 Test architecture | The ITS Mrs Test Suite is based on the test architecture described in ETSI TS 102 871-3 [7]. The test system communicates with the MRS SUT over the mbrPort and over the utPorts as described in clause 5.5. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.5 Ports and ASPs | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.5.1 Introduction | Five ports are used by the ITS-Mrs ATS: • The MRS Port, of type HTTP. • The geoNetworking Port, of type geoNetworkingPort. • The utMbrPort of type LibItsMbr_TestSystem.UpperTesterPort. • The denmUtPort of type LibItsDenm_TestSystem.UpperTesterPort. • The camUtPort of type LibItsCam_TestSystem.UpperTesterPort. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.5.2 Primitives of the geoNetworkingPort | Two types of primitives are used in the securityPort: • The geoNetworkingInd primitive used to receive messages of type GeoNetworkingPacket. • The geoNetworkingReq primitive used to send messages of type GeoNetworkingPacket. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 5.5.3 Primitives of the utPort | The Upper Tester port uses these types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtCamTrigger primitive with the changeSpeed parameter is used to configure IUT to send CAM messages with high rate (greater than 1 Hz). • The UtDenmTrigger primitive used trigger the event in the IUT to send... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 6 External functions | The external functions, described in ETSI TS 103 096-3 [9] shall be applied. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7 ATS conventions | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 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 the testing conventions, described in c... |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.2 Testing conventions | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.2.1 Testing states | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.2.1.1 Initial states | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back to operational state. As no specific actions are required for the idle state in the ETSI TS 103 759 [2], the function f_poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.3 Naming conventions | |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 7.3.1 Introduction | This test suite follows the naming convention guidelines provided in ETSI EG 202 798 [i.1]. |
47021d2e806d414510fb595a318c7753 | 103 868-3 | 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 6) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in Table 8; • prefixes... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.