hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.15 Preventing Tampering of Log Data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.15.1 General | The Requirements below are applicable to the vendors of the log management infrastructure. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.15.2 Requirements | REQ-SEC-SLM-TLD-1: The log management infrastructure should support access management for log data. REQ-SEC-SLM-TLD-2: The log management infrastructure should support real time logging (log data streaming). REQ-SEC-SLM-TLD-3: The log management infrastructure should support replication of log data. REQ-SEC-SLM-TLD-4: ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9 Certificate Management Framework | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.1 Requirements | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.1.1 PNFs | REQ-SEC-CMF-PNF-1: An O-RAN PNF requiring a PKI certificate shall support certificate management protocol. REQ-SEC-CMF-PNF-2: In order to facilitate vendor certificate-based initial enrolment of PNFs, vendors shall pre-install vendor-signed certificates in PNFs. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 66 REQ-SEC-CMF-PNF-... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.1.2 VNFs/CNFs | REQ-SEC-CMF-VNF_CNF-1: The O-Cloud shall support a certificate management protocol for use by O-RAN VNFs/CNFs that require a PKI certificate. REQ-SEC-CMF-VNF_CNF-2: An O-RAN VNF/CNF requiring a PKI certificate directly from a CA/RA, without O-Cloud involvement, shall support a certificate management protocol. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.1.3 Any NF (PNF/VNF/CNF) | REQ-SEC-CMF-ANYNF-1: Any offline or out-of-band (automated or manual) PSK/Refnum generation, distribution and provisioning systems shall provide PSK/Refnum values only to an authorized PNF/CNF/VNF. REQ-SEC-CMF-ANYNF-2: NFs shall raise alarms/notifications and/or security events to SMO or certificate management systems ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.2 Security Controls | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.2.1 PNFs | SEC-CTL-CMF-PNF-1: An O-RAN PNF requiring a PKI certificate shall support CMPv2 as specified in O-RAN Security Protocols Specification [3], clause 4.6. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.2.2 VNFs/CNFs | SEC-CTL-CMF-VNF_CNF-1: The O-Cloud shall support CMPv2 as specified in O-RAN Security Protocols Specification [3], clause 4.6. SEC-CTL-CMF-VNF_CNF-2: An O-RAN VNF/CNF requiring a PKI certificate directly from a CA/RA, without O-Cloud involvement, shall support CMPv2 as specified in O-RAN Security Protocols Specificatio... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.9.2.3 Any NF (PNF/VNF/CNF) | SEC-CTL-CMF-ANYNF-1: NFs may establish TLS connection using renewed certificates before terminating existing TLS connections. SEC-CTL-CMF-ANYNF-2: NFs may terminate any established TLS connection after the renewed certificates are validated and re-establish TLS connection with new certificate. SEC-CTL-CMF-ANYNF-3: NFs ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.10 Application Programming Interfaces (APIs) | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.10.1 Introduction | The security requirements in this clause provide protections against the vulnerabilities and security risks identified in the OWASP API Security Project Top 10 2023 vulnerabilities and security risks of Application Programming Interfaces (APIs) [i.9]. APIs as referred to in this clause are transactional APIs based on R... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.10.2 Security Requirements | REQ-SEC-API-1: APIs used in O-RAN to access an internal or external data source should perform object-level authorization checks. REQ-SEC-API-2: O-RAN endpoints using APIs shall support certificate-based authentication. REQ-SEC-API-3: O-RAN endpoints using APIs may support password-based authentication that is a factor... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.10.3 Security Controls | SEC-CTL-API-01: API client and server shall support mTLS 1.2, or higher, as specified in O-RAN Security Protocols Specifications [3], clause 4.2 for mutual authentication. SEC-CTL-API-02: API server shall support OAuth 2.0 resource server functionality, as specified in O-RAN Security Protocols Specifications [3], claus... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.11 Trust Anchor Provisioning | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.11.0 Introduction | Before an O-RAN component can establish a mutual TLS connection with a signalling peer, the O-RAN component needs to be able to trace the peer's certificate path to a valid trust anchor. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.11.1 Requirements | REQ-SEC-TAP-1: An O-RAN PNF using PKIX certificates shall be shipped with one or more pre-provisioned Trust Anchors, which may be a vendor-signed certificate or operator-signed certificate. REQ-SEC-TAP-2: An O-RAN PNF shall support the secure storage of the trust anchors in a secure element or a secure enclave such tha... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.11.2 Security Controls | SEC-CTL-TAP-1: An O-RAN PNF shall support CMPv2, as specified in O-RAN Security Protocols Specification [3], clause 4.6, for trust anchor provisioning. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 69 SEC-CTL-TAP-2: An O-RAN PNF may support voucher-based protocols [69] to enable an O-RAN function to be securely provisioned wit... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6 SBOM Guidelines for O-RAN | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.1 SBOM Overview | This clause provides guidance for generation, delivery, and use of a Software Bill Of Materials (SBOM). SBOM is a fundamental component of a mature Software Development Lifecycle (SDLC) process. SBOM is an industry best practice part of secure software development that enhances the understanding of the upstream softwar... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.2 Void | [Intentionally blank] |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.3 SBOM Requirements for O-RAN | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.3.0 Introduction | The SBOM delivery should be made under contractual agreement with specific terms that include the following requirements and controls. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.3.1 Requirements | REQ-SBOM-001: The O-RAN vendor shall provide the SBOM with every O-RAN software delivery package, including patches. REQ-SBOM-002: The minimum set of data fields shall include Supplier Name, Component Name, Version of the Component, Other Unique Identifiers as available, Dependency Relationship, Author of the SBOM data... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 6.3.2 Security Controls | SEC-CTL-SBOM-001: For integrity, a hash shall be generated for the SBOM, as specified in O-RAN Security Protocols Specification [3], clause 5. SEC-CTL-SBOM-002: For authenticity, a digital signature shall be provided for the SBOM, as specified in O-RAN Security Protocols Specification [3], clause 5. ETSI ETSI TS 104 10... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 1 Scope | The present document specifies a signal-based analysis method and overall measure for linearity of electrical or acoustical recordings that were transmitted via speech communication terminals. The analysis considers the influence of the full transmission paths (talker to POI and POI to listener), including acoustical p... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 2 References | |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 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... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 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... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 3 Definition of terms, symbols and abbreviations | |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 3.1 Terms | For the purposes of the present document, the following terms apply: distortion: undesired modification of a signal's original waveform or the relationship between its frequency components, typically resulting in a degradation of the signal intermodulation distortion: special type of distortion occurring when two or mo... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: C Spectral coherence min threshold to avoid division by zero i segment index of a STFT calculation iA segment index of a STFT calculation considered as active j frequency index frequency at index j of a STFT calculation ′ frequency at in... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: A/D Analogue-to-Digital AEC Acoustic Echo Cancellation AGC Automatic Gain Control AI Artificial Intelligence AMR Adaptive Multi-Rate AMR-WB Adaptive Multi-Rate for Wideband ASL Active Speech Level CPSD Cross-Power Spectral Density D/A Digital-... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 4 Distortions in speech communication terminals | |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 4.1 Overview | Historically, the analysis of distortions in communication terminals focused on the electro-acoustic components, namely the microphone and the loudspeaker. These transducers were the primary sources of non-linearity in otherwise largely analogue and linear systems. The distortions they introduced, such as harmonic and ... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 4.2 Signal Processing | Modern terminals apply various real-time signal processing algorithms to enhance speech intelligibility and suppress unwanted signals. While these techniques serve important functions, they often introduce side effects that may be perceived as distortions: • Automatic Gain Control (AGC): AGC attempts to normalize signa... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 4.3 Codec | The integration of speech and audio codecs is a fundamental part of modern digital communication systems. While codecs are essential for efficient transmission, they inherently introduce quantization noise, bandwidth limitations, and signal reconstruction errors: • Influence of speech codecs: Speech codecs such as AMR ... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5 Non-linearity measure | |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.1 Overview & conventions | In general, the Non-Linearity Measure (NLM) is based on a source signal (), which is fed acoustically or electrically into a terminal, device or system under test. The signal is transmitted through one or multiple linear or non-linear components/paths, which could be either variant or invariant versus time. The signal... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.2 Preparation and preprocessing | The following requirements and recommendations apply for the source signal used for testing: • The signal-to-noise ratio of the source signal shall be equal to or greater than the signal-to-noise ratio of the British English speech sequence specified in clause 7.3 of Recommendation ITU-T P.501 [2]. • The sour... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.3 Activity detection | Since () (and in consequence also ()) could possibly contain longer inactive/silence segments, these need to be excluded for some analyses in the following clauses. This is achieved with classification into active and inactive level-vs-time instances. In a first step, the Short-Time Fourier Transformation (STFT) is c... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.4 Estimate of impulse response | The first step of the analysis is to estimate an impulse response ℎ based on the available signals and . The calculation method is illustrated in Figure 3. Figure 3: Estimation of impulse response In addition to the STFT , as already determined in clause 5.3, , is calculated accordingly fo... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.5 Estimate of linear signal component | The estimate of the linear component lin is calculated according to equation (11) as the convolution of the source signal () with the impulse response estimate ℎ : lin = ℎ ∗ () (11) |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.6 Estimate of spectral noise component | For the measured signal (), the STFT is calculated, leading to (, ). The parameters and window function for this transformation are provided in Table 3. Table 3: STFT parameter for spectral analysis Parameter Value Window function Hann Number of samples per frame 16 384 Overlap 75 % The magnitude of the estimated n... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.7 Spectral analysis | To estimate the average non-linear signal component !nl , first the STFT is calculated for estimate of the linear component lin , leading to lin(, ). Then the average magnitudes of the measured ! and the linear spectrum !lin are calculated according to equations (13) and (14). The parameters and window f... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 5.8 Aggregated non-linearity measure | The non-linearity measure $nl is determined as the ratio of linear and non-linear signal component levels, calculated in the frequency range from min to max according to equations (16) to (18): lin = ∑ !lin( ) max min (16) nl = ∑ !nl max min (17) $nl %dB& = 10 log(lin nl ' ) (18) |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 6 Application of the non-linearity measure | |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 6.1 Overview | Since NLM is agnostic to the actual recording conditions, the following clauses provide additional guidelines for testing speech communication terminals, in particular in the context of test specifications, which typically refer to sending and/or receiving directions. The naming conventions for both directions are illu... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 6.2 Sending direction | The recording procedure for speech communication devices and acoustical insertion in sending direction is illustrated in Figure 5. If not specified otherwise, a HATS equipped with an artificial mouth simulator according to Recommendation ITU-T P.58 [9] shall be used for the playback of the source signal , which cor... |
77e9e90036b7bf84b00eac0a0ea4ec40 | 104 063 | 6.3 Receiving direction | The recording procedure for speech communication devices and electrical insertion in receiving direction is illustrated in Figure 6. If not specified otherwise, a HATS equipped with artificial ears according to Recommendation ITU-T P.58 [9] shall be used to obtain the signal , which is recorded at the DRP and corre... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for Vulnerable Road Users (VRU) Awareness Basic Service as defined in ETSI TS 103 300-3 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.7]. The objective of the present document is to pro... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 2 References | |
a858fc3ebe3acca0443e845025991f62 | 104 018-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... |
a858fc3ebe3acca0443e845025991f62 | 104 018-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... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 3 Definition of terms, symbols and abbreviations | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 300-3 [1], ISO/IEC 9646-1 [i.4] and ISO/IEC 9646-7 [i.7] apply. |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 3.2 Symbols | Void. |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One ATM Abstract Test Method ATS Abstract Test Suite BTP Basic Transport Protocol BV Valid test events for Behaviour tests EG ETSI Guide EN European Norm ES ETSI Standard GeoN GeoNetworking GNSS Global Navigation... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4 Abstract Test Method (ATM) | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.1 Abstract protocol tester | The abstract protocol tester used by this test suite is described in Figure 1. The test system simulates valid and invalid protocol behaviour, and analyses the reaction of the IUT. Figure 1: Abstract protocol tester - VBS |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.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 one ITS station implementing the VBS protocol. Test System SUT ITS-G5/ LTE V2X IUT VAM ITS-G5/ LTE V2X Lower tester PDUs Upper Tester GeoN GeoN BTP BTP ETSI ETSI TS 104 018-3 V2.1... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.3 Test architecture | The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1], clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used in for the VBS ATS. The VBS test component requires using only the Main Test Component (MTC). The MTC communicates with the VBS SUT over the vamPort... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.4.1 Introduction | Two ports are used by the VBS ATS: • The vamPort, of type VamPort. • The utPort of type UpperTesterPort. ITS TTCN-3 test execution ItsMtc (Sync component) ITS lower layers stack Upper tester transport ITS Test Adaptor SUT Adpt_Ctlr control port UTport control port External functions CODECS System adaptor (SA) Platform ... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.4.2 Primitives of the vamPort | Two types of primitives are used in the vamPort: • The VamInd primitive, containing the received messages of type VAM, and a timestamp corresponding to the receipt time. • The VamReq primitive containing the sent messages of type VAM. The VAM type is declared in the VAM.asn ASN.1 module, following the ASN.1 definition ... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.4.3 Primitives of the utPort | This port uses two types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtTrigger primitive used trigger upper layer events in IUT. |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.5 Executing VBS tests in secured mode | All the VBS tests, with the exception of the SSP tests, can be executed with security enabled or with security disabled. The choice of running the VBS tests in secured or non-secured mode has no impact on the result of the VBS tests because the test verdicts assess VBS protocol behaviour only. The SSP tests can only be... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 4.6 ETSI test adapter | All information of the ETSI test adapter is described in ETSI TR 103 099 [i.3]. ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 11 |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 5 Untestable Test Purposes | Table 1 gives a list of TPs, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 1: Untestable TP Test purpose Reason TP/VBS/MSGF/BV-04 It is not possible to automatically test if the VRU reference point is the ground position of the center of the bounding box of the VRU because this... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6 ATS conventions | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.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 testing conventions an... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.2 Testing conventions | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.2.1 Testing states | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.2.1.1 Initial state | 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. |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in ETSI EN 302 637-3 [i.11], the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.2.2 Message types - ASN.1 definitions | ASN.1 definitions from ETSI TS 103 300-3 [1] are directly imported in TTCN-3 using the ASN.1 import method specified in ETSI ES 201 873-7 [i.10]. The following example shows the TTCN-3 import statement used to import ASN.1 definitions in the TTCN-3 modules: import from VAM_PDU_Descriptions language "ASN.1:1997" all; ET... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.3 Naming conventions | |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.3.1 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 2) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.3.2 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, Table 3 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 3: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsVam_ Module containing types ... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.3.3 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** TC_VAM_M... |
a858fc3ebe3acca0443e845025991f62 | 104 018-3 | 6.3.4 Test Case (TC) identifier | Table 4 shows the test case naming convention, which follows the same naming convention as the test purposes. Table 4: TC naming convention TC_<root>_<gr>_<x>_<nn> Sub-Group Category <root> = root VBS <gr> = group MSGF Message format IFGN Interfaces - GeoNetworking INSE Interfaces - security entity CLTR Clustering FRPE... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 1 Scope | The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for Vulnerable Road Users (VRU) Awareness Basic Service as defined in ETSI TS 103 300-3 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.5]. The ISO standard for th... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 2 References | |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 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... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 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... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 3 Definition of terms, symbols and abbreviations | |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 300-3 [1], ISO/IEC 9646-6 [i.4] and ISO/IEC 9646-7 [i.5] apply. |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 3.2 Symbols | Void. |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite BTP Basic Transport Protocol BV valid test events for Behaviour tests CAM Cooperative Awareness Messages CPM Collective Perception Message GN GeoNetworking ISO International Organization for Standardization ITS Intellig... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4 Test Suite Structure (TSS) | |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.1 Structure for VBS tests | Table 1 shows the VBS Test Suite Structure (TSS) including its subgroups defined for conformance testing. Table 1: TSS for VBS Root Group category VAM Message format Valid Interface to the GeoNetworking/BTP stack Valid Interface to the ITS-S security entity Valid Transition triggering between clustering states Valid Fr... |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.2 Test groups | |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.2.1 Introduction | The test suite has a total of three levels. The first level is the root. The second level separates the root into various functional areas. The third level is the standard ISO conformance test categories. |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.2.2 Root | The root identifies the Vulnerable Road Users (VRU) awareness service given in ETSI TS 103 300-3 [1]. |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.2.3 Groups | This level contains height functional areas identified as: • Message format • Interface to the GeoNetworking/BTP stack • Interface to the ITS-S security entity • Transition triggering between clustering states • Frequency/Periodicity range of VAMs • Transmitting VAMs • Triggering conditions • Security constraints |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 4.2.4 Categories | This level contains the standard ISO conformance test categories behaviour: valid events and Timer. ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 8 |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 5 Test Purposes (TP) | |
88e477d9d8b0c55065c738c067ae6be3 | 104 018-2 | 5.1 Introduction |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.