hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 and values Use upper-case initial letter Its"IUTname"_TypesAndValues ItsVam_TypesAndValues Module containing Templates Use upper-case initial letter Its"IUTname"_Templates ItsVam_Templates Module containing test cases Use upper-case initial letter Its"IUTname"_TestCases ItsVam_TestCases Module containing functions Use upper-case initial letter Its"IUTname"_Functions ItsVam_Functions Module containing external functions Use upper-case initial letter Its"IUTname"_ExternalFunctions ItsVam_ExternalFunctions Module containing components, ports and message definitions Use upper-case initial letter Its"IUTname"_Interface ItsVam_Interface Module containing main component definitions Use upper-case initial letter Its"IUTname"_TestSystem ItsVam_TestSystem Module containing the control part Use upper-case initial letter Its"IUTname"_TestControl ItsVam_TestControl
|
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_MSGF_BV_01: INFO: Initial conditions: First CAM message received ***"); Furthermore, the following rules are applied for the VBS ATS: • Log statements are used in the body of the functions, so that invocations of functions are visible in the test logs: - All TTCN-3 setverdict statements are combined (as defined in ETSI ES 201 873-1 [i.9]) with a log statement following the same above rules (see example 2). EXAMPLE 2: setverdict (pass, "*** f_utInitializeIut: PASS: IUT initialized ***"); ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 14
|
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 Frequency / periodicity range of VAMs TRAN Transmission TRCN Triggering conditions SECC Security constraints <x> = type of testing BV Behaviour: Valid event tests TI Timer tests <nn> = sequential number 01 to 99 EXAMPLE: TP identifier: TP/VAM/MSGF/BV/01 TC identifier: TC_VAM_MSGF_BV_01 ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 15 Annex A (normative): TTCN-3 library modules A.1 TTCN-3 files and other related modules This test suite has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 [i.9]. ETSI TS 103 300-3 [1], ETSI TS 104 018-1 [2] and ETSI TS 104 018-2 [3] have been applied to develop this test suite. This test suite has been compiled error-free using two different commercial TTCN-3 compilers. The TTCN-3 code of the test suite is available as a tagged version "v2.0.5" and released at ETSI forge repository: • https://forge.etsi.org/rep/ITS/ttcn/vru-ts-104-018-3/-/tree/TTF_T036?ref_type=heads ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 16 Annex B (normative): Partial PIXIT pro forma for VBS B.1 The right to copy Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the Partial PIXIT pro forma in this annex so that it can be used for its intended purposes and may further publish the completed Partial PIXIT. B.2 Introduction The PIXIT pro forma is based on ISO/IEC 9646-6. B.3 Identification summary The Identification summary shall be as specified in Table B.1. Table B.1: Identification summary PIXIT Number: Test Laboratory Name: Date of Issue: Issued to: B.4 ATS summary The ATS summary shall be as specified in Table B.2. Table B.2: ATS summary Protocol Specification: ETSI TS 103 300-3 Protocol to be tested: VBS (Vulnerable Road Users (VRU) Basic Service) ATS Specification: ETSI TS 104 018-3 Abstract Test Method: Clause 4 ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 17 B.5 Test laboratory The Test laboratory info shall be specified as in Table B.3. Table B.3: Test laboratory info Test Laboratory Identification: Test Laboratory Manager: Means of Testing: SAP Address: B.6 Client identification The Client identification shall be specified as in Table B.4. Table B.4: Client identification Client Identification: Client Test manager: Test Facilities required: B.7 SUT SUT shall be specified as in Table B.5. Table B.5: SUT Name: Version: SCS Number: Machine configuration: Operating System Identification: IUT Identification: PICS Reference for IUT: Limitations of the SUT: Environmental Conditions: ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 18 B.8 Protocol layer information B.8.1 Protocol identification Protocol identification shall be as specified in Table B.6. Table B.6: Protocol identification Name: ETSI TS 103 300-3 Version: PICS References: ETSI TS 104 018-1 B.8.2 IUT information VBS PIXITs shall be as in Table B.7. Table B.7: VBS PIXITs Identifier Description PX_IUT_STATION_ID Comment Station Id sent by the IUT Type Integer Default value 1 PX_IUT_STATION_TYPE Comment Station Type sent by the IUT Type Integer Default value 1 PX_TESTER_STATION_ID Comment Station Id sent by the tester Type Integer Default value 111 111 PX_TESTER_STATION_TYPE Comment Station Type sent by the tester Type Integer Default value 1 PX_TS_LATITUDE Comment The Latitude of the tester (microdegrees) Type Integer Default value 436 175 790 PX_TS_LONGITUDE Comment The Longitude of the tester (microdegrees) Type Integer Default value 70 546 480 PX_TIME_DELTA Comment Tolerance to be applied when checking timestamps (ms) Type Integer Default value 1 000 PX_GNSS_SCENARIO_SUPPORT Comment Does the IUT support GNSS scenarios? Type Boolean Default value FALSE PX_CERT_FOR_TS Comment The certificate identifier that the tester (TS) shall use in case of secured IUT Type Charstring Default value "CERT_TS_A_AT" PX_IUT_VRU_PROFILE_TYPE Comment To trigger to the IUT which profile to apply Type Integer Default value 2 PX_VRU_CLUSTER_CREATE_PROFILE Comment To trigger to the IUT which cluster profile to apply Type Bitstring Default value '0001'B PX_VRU_REPETITION Comment To indicates how many time a message shall be sent Type Integer Default value 1 ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 19 Identifier Description PX_VRU_CLUSTER_CREATE_CARDINALITY Comment To indicates the cardinality of a cluster initiated by the IUT (≥ 3, 3 + the IUT as leader) Type Integer Default value 4 PX_VRU_CLUSTER_CREATE_ID Comment To indicates the cluster ID when initiated by the TS Type Integer Default value 78 PX_VRU_CLUSTER_CREATE_RADIUS Comment To indicates the size of the clusterBoundingBoxShape Type Integer Default value 30 (3 meters) ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 20 Annex C (normative): PCTR pro forma for VBS C.1 The right to copy Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PCTR pro forma in this annex so that it can be used for its intended purposes and may further publish the completed PCTR. C.2 Introduction The PCTR pro forma is based on ISO/IEC 9646-6. C.3 Identification summary C.3.1 Protocol conformance test report A protocol conformance test report shall be as in Table C.1. Table C.1: Protocol conformance test report PCTR Number: PCTR Date: Corresponding SCTR Number: Corresponding SCTR Date: Test Laboratory Identification: Test Laboratory Manager: Signature: C.3.2 IUT identification An IUT shall be identified as specified in Table C.2. Table C.2: IUT identification Name: Version: Protocol specification: PICS: Previous PCTR if any: ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 21 C.3.3 Testing environment The testing environment shall be as specified in Table C.3. Table C.3: Testing environment PIXIT Number: ATS Specification: Abstract Test Method: Means of Testing identification: Date of testing: Conformance Log reference(s): Retention Date for Log reference(s): C.3.4 Limits and reservation Additional information relevant to the technical contents or further use of the test report, or the rights and obligations of the test laboratory and the client, may be given here. Such information may include restriction on the publication of the present document. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... C.3.5 Comments Additional comments may be given by either the client or the test laboratory on any of the contents of the PCTR, for example, to note disagreement between the two parties. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 22 C.4 IUT Conformance status This IUT has or has not been shown by conformance assessment to be non-conforming to the specified protocol specification. Strike the appropriate words in this sentence. If the PICS for this IUT is consistent with the static conformance requirements (as specified in clause C.5 in the present document) and there are no "FAIL" verdicts to be recorded (in clause C.6 in the present document) strike the words "has or", otherwise strike the words "or has not". C.5 Static conformance summary The PICS for this IUT is or is not consistent with the static conformance requirements in the specified protocol. Strike the appropriate words in this sentence. C.6 Dynamic conformance summary The test campaign did or did not reveal errors in the IUT. Strike the appropriate words in this sentence. If there are no "FAIL" verdicts to be recorded (in clause C.6 of the present document) strike the words "did or" otherwise strike the words "or did not". Summary of the results of groups of test: ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 23 C.7 Static conformance review report If clause C.3 indicates non-conformance, this clause itemizes the mismatches between the PICS and the static conformance requirements of the specified protocol specification. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... C.8 Test campaign report Table C.4: Test cases ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause C.7) TC_VBS_MSGF_BV_01 Yes/No Yes/No TC_VBS_MSGF_BV_02 Yes/No Yes/No TC_VBS_MSGF_BV_03 Yes/No Yes/No TC_VBS_MSGF_BV_04 Yes/No Yes/No Untestable, see clause 5 TC_VBS_MSGF_BV_05 Yes/No Yes/No TC_VBS_MSGF_BV_06 Yes/No Yes/No TC_VBS_MSGF_BV_07 Yes/No Yes/No TC_VBS_MSGF_BV_08 Yes/No Yes/No TC_VBS_MSGF_BV_09 Yes/No Yes/No TC_VBS_MSGF_BV_10 Yes/No Yes/No TC_VBS_MSGF_BV_11 Yes/No Yes/No TC_VBS_MSGF_BV_12 Yes/No Yes/No TC_VBS_MSGF_BV_13 Yes/No Yes/No TC_VBS_MSGF_BV_14 Yes/No Yes/No TC_VBS_MSGF_BV_15 Yes/No Yes/No TC_VBS_MSGF_BV_16 Yes/No Yes/No TC_VBS_MSGF_BV_17 Yes/No Yes/No TC_VBS_MSGF_BV_18 Yes/No Yes/No TC_VBS_MSGF_BV_19 Yes/No Yes/No TC_VBS_MSGF_BV_20 Yes/No Yes/No TC_VBS_MSGF_BV_21 Yes/No Yes/No TC_VBS_MSGF_BV_22 Yes/No Yes/No TC_VBS_MSGF_BV_23 Yes/No Yes/No TC_VBS_MSGF_BV_24 Yes/No Yes/No TC_VBS_MSGF_BV_25 Yes/No Yes/No TC_VBS_MSGF_BV_26 Yes/No Yes/No TC_VBS_MSGF_BV_27 Yes/No Yes/No TC_VBS_MSGF_BV_28 Yes/No Yes/No TC_VBS_IFGN_BV_01 Yes/No Yes/No TC_VBS_IFGN_BV_02 Yes/No Yes/No TC_VBS_IFGN_BV_03 Yes/No Yes/No ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 24 ATS Reference Selected? Run? Verdict Observations (Reference to any observations made in clause C.7) TC_VBS_IFGN_BV_04 Yes/No Yes/No TC_VBS_IFGN_BV_05 Yes/No Yes/No TC_VBS_IFSE_BV_01 Yes/No Yes/No TC_VBS_IFSE_BV_02 Yes/No Yes/No TC_VBS_IFSE_BV_03 Yes/No Yes/No TC_VBS_CLTR_BV_01 Yes/No Yes/No TC_VBS_CLTR_BV_02 Yes/No Yes/No TC_VBS_CLTR_BV_03 Yes/No Yes/No TC_VBS_CLTR_BV_04 Yes/No Yes/No TC_VBS_CLTR_BV_05 Yes/No Yes/No TC_VBS_CLTR_BV_06 Yes/No Yes/No TC_VBS_CLTR_BV_07 Yes/No Yes/No TC_VBS_CLTR_BV_08 Yes/No Yes/No TC_VBS_CLTR_BV_09 Yes/No Yes/No TC_VBS_CLTR_BV_10 Yes/No Yes/No TC_VBS_CLTR_BV_11 Yes/No Yes/No TC_VBS_CLTR_BV_12 Yes/No Yes/No TC_VBS_FRPE_TI_01 Yes/No Yes/No TC_VBS_FRPE_BV_02 Yes/No Yes/No TC_VBS_FRPE_TI_03 Yes/No Yes/No TC_VBS_FRPE_BV_04 Yes/No Yes/No TC_VBS_FRPE_BV_05 Yes/No Yes/No TC_VBS_FRPE_TI_06 Yes/No Yes/No TC_VBS_FRPE_TI_07 Yes/No Yes/No TC_VBS_TRAN_BV_01 Yes/No Yes/No TC_VBS_TRAN_BV_02 Yes/No Yes/No TC_VBS_TRAN_BV_03 Yes/No Yes/No TC_VBS_TRAN_BV_04 Yes/No Yes/No TC_VBS_TRCN_BV_01 Yes/No Yes/No TC_VBS_TRCN_BV_02 Yes/No Yes/No TC_VBS_TRCN_BV_03 Yes/No Yes/No TC_VBS_TRCN_BV_04 Yes/No Yes/No TC_VBS_TRCN_BV_05 Yes/No Yes/No TC_VBS_TRCN_BV_06 Yes/No Yes/No TC_VBS_TRCN_BV_07 Yes/No Yes/No TC_VBS_TRCN_BV_08 Yes/No Yes/No TC_VBS_TRCN_BV_09 Yes/No Yes/No TC_VBS_TRCN_BV_10 Yes/No Yes/No TC_VBS_TRCN_BV_11 Yes/No Yes/No TC_VBS_TRCN_BV_12 Yes/No Yes/No TC_VBS_TRCN_BV_13 Yes/No Yes/No TC_VBS_TRCN_BV_14 Yes/No Yes/No TC_VBS_TRCN_BV_15 Yes/No Yes/No TC_VBS_TRCN_BV_16 Yes/No Yes/No TC_VBS_TRCN_BV_17 Yes/No Yes/No TC_VBS_TRCN_BV_18 Yes/No Yes/No TC_VBS_TRCN_BV_19 Yes/No Yes/No TC_VBS_TRCN_BV_20 Yes/No Yes/No TC_VBS_TRCN_BV_21 Yes/No Yes/No TC_VBS_TRCN_BV_22 Yes/No Yes/No TC_VBS_TRCN_BV_23 Yes/No Yes/No TC_VBS_TRCN_BV_24 Yes/No Yes/No TC_VBS_TRCN_BV_25 Yes/No Yes/No TC_VBS_TRCN_BV_26 Yes/No Yes/No TC_VBS_TRCN_BV_27 Yes/No Yes/No TC_VBS_TRCN_BV_28 Yes/No Yes/No TC_VBS_TRCN_BV_29 Yes/No Yes/No ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 25 C.9 Observations Additional information relevant to the technical content of the PCTR is given here. ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ............................................................................................................................................................................................... ETSI ETSI TS 104 018-3 V2.1.1 (2025-07) 26 History Version Date Status V2.1.1 July 2025 Publication
|
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 the methodology of conformance testing (ISO/IEC 9646-1 [i.2] and ISO/IEC 9646-2 [i.3]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.6]) are used as a basis for the test methodology.
|
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 103 300-3 (V2.2.1): "Intelligent Transport Systems (ITS); Vulnerable Road Users (VRU) awareness; Part 3: Specification of VRU awareness basic service; Release 2 ". [2] ETSI TS 104 018-1 (2.1.1): " Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Vulnerable Road Users (VRU) awareness service; Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS) pro forma; Release 2".
|
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI EG 202 798 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". [i.2] ISO/IEC 9646-1 (1994): "Information technology — Open Systems Interconnection — Conformance testing methodology and framework — Part 1: General concepts". [i.3] ISO/IEC 9646-2 (1994): "Information technology — Open Systems Interconnection — Conformance testing methodology and framework — Part 2: Abstract Test Suite specification". [i.4] ISO/IEC 9646-6 (1994): "Information technology — Open Systems Interconnection — Conformance testing methodology and framework — Part 6: Protocol profile test specification". [i.5] ISO/IEC 9646-7 (1995): "Information technology — Open Systems Interconnection — Conformance testing methodology and framework — Part 7: Implementation Conformance Statements". ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 6 [i.6] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology".
|
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 Intelligent Transportation Systems ITS-AID ITS Application Identifier ITS-S Intelligent Transport System - Station IUT Implementation Under Test LF Low Frequency MSGF Message Format PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement PIXIT Partial Protocol Implementation eXtra Information for Testing SSP Service Specific Permissions TI Timer tests TP Test Purposes TS Test Suite TSS Test Suite Structure VAM VRU Awareness Message VBS VRU Basic Service VRU Vulnerable Road User ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 7
|
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 Frequency/Periodicity range of VAMs Valid and Timer Transmitting VAMs Valid Triggering conditions Valid Security constraints Valid The test suite is structured as a tree with the root defined as DEN. The tree is of rank 2 with the first rank a functional area and the second rank is the standard ISO conformance test categories.
|
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
| |
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.1 TP definition conventions
|
The TP definition is built according to ETSI EG 202 798 [i.1].
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.2 TP Identifier naming conventions
|
The identifier of the TP is built according to Table 2. Table 2: TP naming convention TP/<root>/<gr>/<x>/<nn> or TP/<root>/<gr>/<x>/<nn>-<v> Abbreviation Description <root> = root VBS <gr> = group MSGF Message format IFGN Interfaces - GeoNetworking INSE Interfaces - security entity CLTR Clustering FRPE Frequency / periodicity range of VAMs TRAN Transmission TRCN Triggering conditions SECC Security constraints <x> = type of testing BV Behaviour: Valid event tests TI Timer tests <nn> = sequential number 01 to 99 <v> = variant 01 to 99
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.3 Rules for the behaviour description
|
The description of the TP is built according to ETSI EG 202 798 [i.1]. ETSI TS 103 300-3 [1] does not use the finite state machine concept. As consequence, the test purposes use a generic "Initial State" that corresponds to a state where the IUT is ready for starting the test execution. Furthermore, the IUT shall be left in this "Initial State", when the test is completed. Being in the "Initial State" refers to the starting point of the initial device configuration. There are no pending actions, no instantiated buffers or variables, which could disturb the execution of a test.
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.4 Sources of TP definitions
|
All TPs have been specified according to ETSI TS 103 300-3 [1].
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.5 Mnemonics for PICS reference
|
To avoid an update of all TPs when the PICS document is changed, Table 3 introduces mnemonics name and the correspondence with the real PICS item number. The PICS item column refers to tables and items of ETSI TS 104 018-1 [2]. The 'PICS item' as defined in ETSI TS 104 018-1 [2] shall be used to determine the test applicability. ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 9 Table 3: Mnemonics for PICS reference Mnemonic PICS item PICS_VAM_GENERATION A.1/1 PICS_VAM_TRANSMISSION A.1/2 PICS_PROFILE_PEDESTRIAN A.3/1 PICS_PROFILE_BICYCLIST A.3/2 PICS_PROFILE_MOTORCYCLIST A.3/3 PICS_PROFILE_ANIMAL A.3/4 PICS_CLUSTERING A.4/1 PICS_SECURITY A.5/1 PICS_ELEVATED_HAZARD_SITUATION A.7/1 PICS_ITS_G5 A.2/1
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.1.6 VRU roles and clustering states
|
A VRU can be in two different roles (VRU_ROLE_ON and VRU_ROLE_OFF). They are defined in ETSI TS 103 300-3 [1] in Table 1. The VBS can take on different clustering states (VRU-IDLE, VRU-ACTIVE- STANDALONE, VRU-ACTIVE-CLUSTER-LEADER, VRU-Passive) that are defined in ETSI TS 103 300-3 [1], Table 5.
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2 Test purposes for VBS
| |
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.1 Message format
|
TP Id TP/VBS/MSGF/BV-01 Test objective Check that protocolVersion is set to 3 and messageID is set to 16 Reference ETSI TS 103 300-3 [1], clause 7.2 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing ITS PDU header containing protocolVersion indicating value 3 and containing messageID indicating value 16 } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 10 TP Id TP/VBS/MSGF/BV-02 Test objective Check that the generation time in the VAM is the time of reference position since ITS epoch modulo 216 Reference ETSI TS 103 300-3 [1], clause 7.2 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing generation time indicating reference position time in milliseconds since ITS epoch mod 216 } } NOTE: Current Time - 5 s < Time of Reference Position < Current Time + 5 s TP Id TP/VBS/MSGF/BV-03 Test objective Check that StationType only takes supported values Reference ETSI TS 103 300-3 [1], clause 7.3.1 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing BasicContainer containing StationType indicating pedestrian or indicating cyclist or indicating moped or indicating motorcycle or indicating lightVruVehicle or indicating animal } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 11 TP Id TP/VBS/MSGF/BV-04 Test objective Check that the reference point is the ground position of the center of the front side of the bounding box of the VRU Reference ETSI TS 103 300-3 [1], clause 7.3.1 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM generation requested } then { VAM is sent containing VamAwarness containing BasicContainer containing ReferencePosition containing reference position indicating ground position of the center of the front side of the bounding box } } NOTE: Test case not automatically testable. To be tested manually. TP Id TP/VBS/MSGF/BV-05 Test objective Check that the curvature includes the curvatureValue which is the inverse of the VRU curve radius and the turning direction of the curve Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU is following a curve with radius RADIUS and turning direction DIRECTION } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing VruHighFrequencyContainer containing curvature containing curvatureValue indicating DIRECTION * 1/( RADIUS *10000) } } NOTE: DIRECTION can be 1 (left) or -1 (right) ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 12 TP Id TP/VBS/MSGF/BV-06 Test objective Check that the yawRate includes the yawRateValue Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has a yaw rate of YAW_RATE } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing VruHighFrequencyContainer containing yawRate containing yawRateValue indicating value YAW_RATE } } NOTE: Yaw rate YAW_RATE represents rotation around the z-axis, a negative value indicates clockwise rotation and a positive value counter-clockwise. TP Id TP/VBS/MSGF/BV-07 Test objective Check that the lateralAcceleration indicates the lateral acceleration perpendicular to the heading direction Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has a lateral acceleration of LAT_ACC } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing VruHighFrequencyContainer containing lateralAcceleration indicating value LAT_ACC } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 13 TP Id TP/VBS/MSGF/BV-08 Test objective Check that the vruLanePosition describes a lane on the road, a lane off the road or an island between two lanes Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU in lane LANE } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing VruHighFrequencyContainer containing simpleLanePosition indicating lane LANE } } TP Id TP/VBS/MSGF/BV-09 Test objective Check that the orientation defines the angle between the longitudinal axis and WGS84 north Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION, PICS_PROFILE_BICYCLIST or PICS_PROFILE_MOTORCYCLIST Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has heading HEADING } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing vruHighFrequencyContainer containing orientation containing headingValue indicating value HEADING } } NOTE: Heading h represents angle between longitudinal axis and WGS84 north. ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 14 TP Id TP/VBS/MSGF/BV-10 Test objective Check that the rollAngle includes the angle between the ground plane and the vehicle's y-axis as well as the angle accuracy and that no values between 500 and 3 100 are used Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has roll angle heading of ROLL_ANGLE with heading confidence of CONFIDENCE } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing vruHighFrequencyContainer containing rollAnlge containing headingValue indicating value ROLL_ANGLE and containing headingConfidence indicating value CONFIDENCE < 500 and CONFIDENCE > 3100 } } TP Id TP/VBS/MSGF/BV-11 Test objective Check that the deviceUsage uses values between 0 and 8 Reference ETSI TS 103 300-3 [1], clause 7.3.3 PICS Selection PICS_VAM_GENERATION, PICS_PROFILE_PEDESTRIAN Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU in profile pedestrian (1) and VRU has deviceUsage D } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing vruHighFrequencyContainer containing deviceUsage indicating value D } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 15 TP Id TP/VBS/MSGF/BV-12 Test objective Check that the profileAndSubprofile contains the profile and sub-profile of the VRU if the VRU LF container is present Reference ETSI TS 103 300-3 [1], clause 7.3.4 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has profile PROFILE and sub-profile SUBPROFILE } Expected behaviour ensure that { when { VAM is generated and VRU LF container is present } then { VAM is sent containing VamAwarness containing vruLowFrequencyContainer containing profileAndSubprofile indicating value included in PROFILE containing sub-profile indicating value included in SUBPROFILE } } NOTE: The conditions for including the LF container are tested in TP/VBS/FRPE/BV-03 and TP/VBS/FRPE/BV-04. TP Id TP/VBS/MSGF/BV-13 Test objective Check that the sizeClass contains size information of the VRU Reference ETSI TS 103 300-3 [1], clause 7.3.4 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has sizeClass SC } Expected behaviour ensure that { when { VAM is generated and VRU LF container is present } then { VAM is sent containing VamAwarness containing vruLowFrequencyContainer containing sizeClass indicating value SC } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 16 TP Id TP/VBS/MSGF/BV-14 Test objective Check that exteriorLights is present for VRU profile 2 Reference ETSI TS 103 300-3 [1], clause 7.3.4 PICS Selection PICS_VAM_GENERATION, PICS_PROFILE_BICYCLIST Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU in profile bicyclist (2) } Expected behaviour ensure that { when { VAM is generated and VRU LF container is present } then { VAM is sent containing VamAwarness containing vruLowFrequencyContainer containing exteriorLights } } TP Id TP/VBS/MSGF/BV-15 Test objective Check that clusterProfiles is not set to zeros if VRU has profile 1, 2 or 4 Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING, PICS_PROFILE_PEDESTRIAN or PICS_PROFILE_BICYCLISTor PICS_PROFILE_ANIMAL Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU is part of cluster } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing VamAwarness containing vruClusterInformationContainer containing clusterProfiles not indicating value 0000 } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 17 TP Id TP/VBS/MSGF/BV-16 Test objective Check that clusterLeaveReason indicates clusterLeaderLost when the cluster leader is lost Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE and VRU has last received a cluster VRU from cluster leader at time T1 } Expected behaviour ensure that { when { timeClusterContinuity has passed since T1 } then { VAM is sent containing VamAwarness containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating clusterLeaderLost (1) } } TP Id TP/VBS/MSGF/BV-17 Test objective Check that clusterLeaveReason indicates clusterDisbandedByLeader when the cluster leader breaks up the cluster Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VRU receives VAM containing vruClusterOperationContainer containing clusterBreakupInfo from cluster leader } then { VAM is sent containing VamAwarness containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating clusterDisbandedByLeader (2) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 18 TP Id TP/VBS/MSGF/BV-18 Test objective Check that clusterLeaveReason indicates outOfClusterBoundingBox when the VRU moves out of the cluster bounding box Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE and VRU has received a cluster VAM from cluster leader containing vruClusterInformationContainer containing clusterBoundingBoxShape indicating Shape S } Expected behaviour ensure that { when { the IUT is alerted about new reference position value P and P is not inside S } then { VAM is sent containing VamAwarness containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating outOfClusterBoundingBox (3) } } TP Id TP/VBS/MSGF/BV-19 Test objective Check that clusterLeaveReason indicates outOfClusterSpeedRange when the VRU is out of the cluster speed range Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE and VRU has received a cluster VAM from cluster leader containing vruHighFrequencyContainer containing speed containing speedValue indicating value SPEED_1 } Expected behaviour ensure that { when { the IUT is alerted about new own speed value SPEED_2 and abs(SPEED_2 - SPEED_1) > maxClusterVelocityDifference } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating outOfClusterSpeedRange (4) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 19 TP Id TP/VBS/MSGF/BV-20 Test objective Check that clusterLeaveReason indicates joiningAnotherCluster when the VRU is joining another cluster Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VBS has received a VAM from another cluster leader containing vruClusterInformationContainer containing clusterId indicating CId } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating joiningAnotherCluster (5) and containing clusterJoinInfo containing clusterId indicating CId } } NOTE: The conditions for joining the other cluster are the same as in TP/VBS/CLTR/BV-05. TP Id TP/VBS/MSGF/BV-21 Test objective Check that clusterLeaveReason indicates CancelledJoin when the joining is cancelled Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VBS has started joining the cluster } Expected behaviour ensure that { when { VBS has received a VAM from a cluster leader containing vruClusterInformationContainer containing clusterCardinalitySize indicating value > maxClusterSize } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating CancelledJoin (6) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 20 TP Id TP/VBS/MSGF/BV-22 Test objective Check that clusterLeaveReason indicates FailedJoin when the joining is cancelled Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VBS has started joining the cluster } Expected behaviour ensure that { when { VBS has received a VAM from a cluster leader containing vruClusterInformationContainer containing clusterCardinalitySize indicating value > maxClusterSize } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating FailedJoin (7) } } TP Id TP/VBS/MSGF/BV-23 Test objective Check that clusterLeaveReason indicates SafetyCondition when another cluster VRU comes too close Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { another VRU in the cluster has come closer than MSLaD laterally and another VRU in the cluster has come closer than MSLoD longitudinally and another VRU in the cluster has come closer than MSVD vertically } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterLeaveReason indicating SafetyCondition (8) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 21 TP Id TP/VBS/MSGF/BV-24 Test objective Check that clusterBreakupReason indicates clusteringPurposeCompleted when the clustering purpose is completed Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { the clustering purpose is completed } then { VAM is sent containing vruClusterInformationContainer containing clusterId containing vruClusterOperationContainer containing clusterBreakupInfo indicating value clusteringPurposeCompleted (1) } } TP Id TP/VBS/MSGF/BV-25 Test objective Check that clusterBreakupReason indicates outOfClusterBoundingBox when the cluster leader moves out of the cluster bounding box Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has sent a cluster VAM containing vruClusterInformationContainer containing clusterBoundingBoxShape indicating Shape S } Expected behaviour ensure that { when { the IUT is alerted about new reference position value P and P is not inside S } then { VAM is sent containing vruClusterInformationContainer containing clusterId containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterBreakupReason indicating value leaderMovedOutOfClusterBoundingBox (2) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 22 TP Id TP/VBS/MSGF/BV-26 Test objective Check that clusterBreakupReason indicates joiningAnotherCluster when the cluster leader is joining another cluster Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VBS has received a VAM from another cluster leader containing vruClusterInformationContainer containing clusterId indicating value CId } then { VAM is sent containing vruClusterInformationContainer containing clusterId containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterBreakupReason indicating value joiningAnotherCluster (3) and containing clusterJoinInfo containing clusterId indicating value CId } } NOTE: The conditions for joining the other cluster are the same as in TP/VBS/CLTR/BV-05. TP Id TP/VBS/MSGF/BV-27 Test objective Check that clusterBreakupReason indicates enteringLowriskareaBasedonMAPs when the cluster leader is entering a low-risk area Reference 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { a MAP is received indicating the current position is in a low risk area } then { VAM is sent containing vruClusterInformationContainer containing clusterId containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterBreakupReason indicating value enteringLowriskareaBasedonMAPs (4) } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 23 TP Id TP/VBS/MSGF/BV-28 Test objective Check that clusterBreakupReason indicates receptionOfCPMcontainingCluster when a CPM containing a cluster is received Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { a CPM is received that contains a cluster } then { VAM is sent containing vruClusterInformationContainer containing clusterId containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterBreakupReason indicating value receptionOfCPMcontainingCluster (5) } } TP Id TP/VBS/MSGF/BV-29 Test objective Check that clusterIdChangeTimeInfo indicates the time the cluster leader intents to change the cluster ID Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated and VRU is changing cluster ID } then { VAM is sent containing vruClusterOperationContainer containing clusterIdChangeTimeInfo indicating planned ID change time } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 24 TP Id TP/VBS/MSGF/BV-30 Test objective Check that the ClusterLeaveReason is systematically set to 0 if the reason for breaking up or leaving the cluster cannot be matched with the other reasons (1-8) Reference ETSI TS 103 300-3 [1], clause 7.3.5 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VAM is generated and VRU is leaving the cluster and no other reason applicable to the given 8 } then { VAM is sent containing vruClusterOperationContainer containing clusterLeaveInfo containing clusterId and containing clusterLeaveReason indicating value 0 } } TP Id TP/VBS/MSGF/BV-31 Test objective Check that the VruMotionPredictionContainer includes the pathHistory of type PathHistory consisting of up to 40 past points Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has n PathPoints } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing pathHistory containing n <= 40 PathPoints containing pathPosition } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 25 TP Id TP/VBS/MSGF/BV-32 Test objective Check that the VruMotionPredictionContainer includes the path prediction of type PathPredicted consisting of up to 15 future points, confidence values and time instances Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has n VruPathPoints } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing pathPrediction containing n <= 15 times PathPointPredicted containing horizontalPositionConfidence and containing pathDeltaTime } } TP Id TP/VBS/MSGF/BV-33 Test objective Check that the vruMotionPredictionContainer includes the safe distance indication that includes timeToCollision Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU has detected a possible collision and VRU has timeToCollision of TTC } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing safeDistance containing VruSafeDistanceIndication containing timeToCollision indicating value TTC } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 26 TP Id TP/VBS/MSGF/BV-34 Test objective Check that the vruMotionPredictionContainer includes the accelerationChangeIndication of type AccelerationChangeIndication containing accelOrDecel and actionDeltaTime Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU accelerates or decelerates for time period DELTA_TIME } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing accelerationChangeIndication containing accelOrDecel indicating accelerate / decelerate and containing actionDeltaTime indicating value DELTA_TIME } } TP Id TP/VBS/MSGF/BV-35 Test objective Check that the vruMotionPredictionContainer includes the headingChangeIndication of type HeadingChangeIndication containing the dircetion and actionDeltaTime Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU changes heading to direction d for a time period DELTA_TIME } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing headingChangeIndication containing direction indicating value d and containing actionDeltaTime indicating value DELTA_TIME } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 27 TP Id TP/VBS/MSGF/BV-36 Test objective Check that the vruMotionPredictionContainer includes the stabilityChangeIndication of type StabilityChangeIndication containing the lossProbability and actionDeltaTime Reference ETSI TS 103 300-3 [1], clause 7.3.6 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU changes stability by lossProbability PL for a time period DELTA_TIME } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruMotionPredictionContainer containing stabilityChangeIndication containing lossProbability indicating value PL and containing actionDeltaTime indicating value DELTA_TIME } } TP Id TP/VBS/MSGF/BV-37 Test objective Check that profile 3 VRUs only transmit a VRU special vehicle container in the CAM instead of full VAM Reference 7.4 PICS Selection PICS_VAM_GENERATION, PICS_PROFILE_MOTORCYCLIST Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VRU in profile motorcyclist (3) } Expected behaviour ensure that { when { IUT is triggered to send awareness message } then { CAM is sent containing specialVehicleContainer containing vruSpecialVehicleContainer containing vruSubProfileMotorcyclist and containing sizeClass and no VAM is generated } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 28
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.2 Interface to the GeoNetworking/BTP stack
|
TP Id TP/VBS/IFGN/BV-01 Test objective Check that the BTP header type B and the destination port is passed if the value is not provided by the ITS-S configuration Reference ETSI TS 103 300-3 [1], clause 5.3.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and data being passed from the VBS to GeoNetworking/BTP and BTP type is not provided by the ITS-S configuration } Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing BTP header indicating type B and containing destination port indicating value 2018 } } TP Id TP/VBS/IFGN/BV-02 Test objective Check that the GN packet transport type is GeoNetworking SHB and passed if the value is not provided by the ITS-S configuration Reference ETSI TS 103 300-3 [1], clause 5.3.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and data being passed from the VBS to GeoNetworking/BTP and BTP type is not provided by the ITS-S configuration } Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing GeoNetworking header containing Common Header containing Header Type indicating SHB } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 29 TP Id TP/VBS/IFGN/BV-03 Test objective Check that the GN security profile is passed if the value is not provided by the ITS-S configuration Reference ETSI TS 103 300-3 [1], clause 5.3.3.3 PICS Selection PICS_VAM_GENERATION, PICS_SECURITY Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and GN security profile is activated } Expected behaviour ensure that { when { VAM is generated } then { Message is sent using GN secured packet } } TP Id TP/VBS/IFGN/BV-03 Test objective Check that the GN Traffic class is the same value as for the CAM Reference ETSI TS 103 300-3 [1], clause 5.3.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and data being passed from the VBS to GeoNetworking/BTP Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing GeoNetworking header containing Common Header containing Traffic Class indicating value TC = 2 } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 30 TP Id TP/VBS/IFGN/BV-05 Test objective Check that the GN Maximum packet lifetime does not exceed 1 000 ms Reference ETSI TS 103 300-3 [1], clause 5.3.3.3 PICS Selection PICS_VAM_GENERATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and data being passed from the VBS to GeoNetworking/BTP } Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing GeoNetworking header containing Basic Header containing Lifetime indicating value <= 1000 ms } }
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.3 Interface to the ITS-S security entity (IF.SF)
|
TP Id TP/VBS/IFSE/BV-01 Test objective Check that the VBS temporarily stops generating VAMs when it is notified of a pending identifier change Reference ETSI TS 103 300-3 [1], clause 5.3.5 PICS Selection PICS_VAM_GENERATION, PICS_SECURITY Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { identifier change requested by security entity } then { VBS stops generating VAMs during the change procedure } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 31 TP Id TP/VBS/IFSE/BV-02 Test objective Check that an identifier change is inhibited during an elevated hazard situation Reference ETSI TS 103 300-3 [1], clause 5.3.5 PICS Selection PICS_VAM_GENERATION, PICS_SECURITY, PICS_ELEVATED_HAZARD_SITUATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VBS is in elevated hazard situation } Expected behaviour ensure that { when { identifier change requested by security entity } then { VBS does not change identifier } } TP Id TP/VBS/IFSE/BV-03 Test objective Check that an identifier change is possible after an elevated hazard situation has passed Reference ETSI TS 103 300-3 [1], clause 5.3.5 PICS Selection PICS_VAM_GENERATION, PICS_SECURITY, PICS_ELEVATED_HAZARD_SITUATION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VBS is in elevated hazard situation and identifier change is requested by security entity } Expected behaviour ensure that { when { elevated hazard situation has passed } then { VBS changes identifier } }
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.4 Transmitting VAMs
|
TP Id TP/VBS/TRAN/BV-01 Test objective Check that a VRU in VRU-ACTIVE-STANDALONE sends individual VAMs Reference ETSI TS 103 300-3 [1], clause 6.3 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent not containing vruClusterInformationContainer and not containing vruClusterOperationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 32 TP Id TP/VBS/TRAN/BV-02 Test objective Check that a VRU in VRU-ACTIVE-CLUSTER-LEADER sends cluster VAMs Reference ETSI TS 103 300-3 [1], clause 6.3 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { VAM is sent containing vruClusterInformationContainer } } TP Id TP/VBS/TRAN/BV-03 Test objective Check that a VRU in VRU-PASSIVE sends individual VAMs containing VruClusterOperationContainer when leaving the VRU cluster Reference ETSI TS 103 300-3 [1], clause 6.3 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VRU is triggered to leave cluster } then { VAM is sent containing vruClusterOperationContainer and not containing vruClusterInformationContainer } } TP Id TP/VBS/TRAN/BV-04 Test objective Check that a VRU in VRU-ACTIVE-STANDALONE sends individual VAMs containing VruClusterOperationContainer while joining a VRU cluster Reference ETSI TS 103 300-3 [1], clause 6.3 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE } Expected behaviour ensure that { when { VRU determines to join cluster } then { VAM is sent containing vruClusterOperationContainer and not containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 33
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.5 Transition triggering between clustering states
|
TP Id TP/VBS/CLTR/BV-01 Test objective Check that a VBS starts sending VAMs when the state changes from VRU-IDLE to VRU- ACTIVE-STANDALONE Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-IDLE } Expected behaviour ensure that { when { state changes to VRU-ACTIVE-STANDALONE } then { VBS sends VAMs not containing vruClusterOperationContainer } } TP Id TP/VBS/CLTR/BV-02 Test objective Check that the cluster size is set to minClusterSize and the VRU profile field is set to the VRU profile Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VBS has VRU profile p } Expected behaviour ensure that { when { VBS determining to form a cluster } then { VBS sends VAM containing vruClusterInformationContainer containing clusterProfiles indicating value p and containing clusterCardinalitySize indicating value minClusterSize } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 34 TP Id TP/VBS/CLTR/BV-03 Test objective Check that a VBS in VRU-ACTIVE-STANDALONE stops the transmission of VAMs when changing to VRU-IDLE Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE } Expected behaviour ensure that { when { state changes to VRU-IDLE } then { VBS stops sending VAMs } } TP Id TP/VBS/CLTR/BV-04 Test objective Check that a cluster breaking VRU stops sending cluster VAMs Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and breakup indication has been sent } Expected behaviour ensure that { when { VBS breaking up cluster } then { VBS stops sending cluster VAMs } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 35 TP Id TP/VBS/CLTR/BV-05 Test objective Check that a VRU sends an indication of joining a cluster for timeClusterJoinNotification including the identified cluster and time at which it stops sending individual VAMs Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE } Expected behaviour ensure that { when { VBS has received a VAM from a cluster leader containing basicContainer containing referencePosition indicating Position and distance(Position, EgoPosition) < maxClusterDistance and containing vruHighFreuquencyContainer containing speed containing speedValue indicating value and abs(value – EgoSpeed) < maxClusterVelocityDifference and containing vruClusterInformationContainer containing clusterId indicating Cid and containing clusterCardinalitySize indicating value < maxClusterSize } then { VBS sends VAM for timeClusterJoinNotification not containing vruClusterInformationContainer and containing clusterOperationContainer containing clusterJoinInfo containing clusterId indicating CId and containing joinTime } } TP Id TP/VBS/CLTR/BV-06 Test objective Check that a VBS sends individual VAMs after a cancelled-join odder failed-join including the same station ID as before and the cluster leave notification for timeClusterLeaveNotification Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and cancelled-join has occurred or failed-join has occurred and stationID is value sID } Expected behaviour ensure that { when { VBS generates VAM } then { VBS sends VAM not containing vruClusterInformationContainer and containing ITS PDU header containing stationID indicating sID } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 36 TP Id TP/VBS/CLTR/BV-07 Test objective Check that a VRU leaving a cluster indicates the identified cluster and the reason for timeClusterLeaveNotification Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VRU leaving cluster CL1 } then { VBS sends VAMs for timeClusterLeaveNotification containing vruClusterOperationContainer containing vruClusterInformationContainer containing clusterId indicating CL1 } } TP Id TP/VBS/CLTR/BV-08 Test objective Check that a VRU that left a cluster uses different identifiers from before joining the cluster as long as it has not experienced a cancelled-join or failed-join Reference ETSI TS 103 300-3 [1], clause 5.4.2.2 PICS Selection PICS_CLUSTERING Initial conditions with { VRU has previously sent individual VAMs with stationID sID-1 and VRU has joined a cluster and VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VRU is triggered to leave the cluster } then { VBS sends VAMs not containing vruOperationContainer and containing ITS PDU Header containing stationID indicating value sID != sID-1 and state changes to VRU-ACTIVE-STANDALONE } } NOTE: The conditions for leaving the cluster are tested in TP/VBS/MSGF/BV-24 and TP/VBS/MSGF/BV-28. ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 37 TP Id TP/VBS/CLTR/BV-09 Test objective Check that a cluster leader indicates a cluster ID change for timeClusterIdChangeNotification before the change Reference ETSI TS 103 300-3 [1], clause 5.4.2.3 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and is triggered to change cluster ID and VBS has sent VAM containing vruClusterInformationContainer containing clusterID indicating cID1 and containing vruClusterOperationContainer containing clusterIdChangeTimeInfo indicating value x } Expected behaviour ensure that { when { IUT is sending } then { VBS sends multiple VAMs during timeClusterIdChangeNotification containing vruClusterInformationContainer and containing vruClusterOperationContainer containing clusterIdChangeTimeInfo } } TP Id TP/VBS/CLTR/BV-10 Test objective Check that a cluster leader sends a cluster VAM with the new ID as soon as possible Reference ETSI TS 103 300-3 [1], clause 5.4.2.3 PICS Selection PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and change ID notification has been sent } Expected behaviour ensure that { when { IUT is changing cluster ID } then { VBS sends VAMs containing vruClusterInformationContainer containing clusterId indicating new cluster ID } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 38
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.6 Triggering conditions
|
TP Id TP/VBS/TRCN/BV-01 Test objective Check that the first time individual VAM is generated immediately after VBS activation Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VBS activation has occurred and VBS has sent no VAM yet } Expected behaviour ensure that { when { VAM is generated } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-02 Test objective Check that a VAM is generated immediately if a VRU is in VRU-IDLE and enters VRU-ACTIVE- STANDALONE Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-IDLE } Expected behaviour ensure that { when { state changes to VRU-ACTIVE-STANDALONE } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-03 Test objective Check that a VAM is generated immediately if a VRU is in VRU-PASSIVE, leaves the cluster and enters VRU-ACTIVE-STANDALONE Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { VRU leaves cluster and state changes to VRU-ACTIVE-STANDALONE } then { VBS sends VAM not containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 39 TP Id TP/VBS/TRCN/BV-04 Test objective Check that a VAM is generated immediately if a VRU is in VRU-PASSIVE, determines the cluster leader is lost and enters VRU-ACTIVE-STANDALONE Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-PASSIVE } Expected behaviour ensure that { when { cluster leader is lost and state changes to VRU-ACTIVE-STANDALONE } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-05 Test objective Check that a VAM is generated immediately if a VRU is in VRU-ACTIVE-CLUSTER-LEADER, breaks up the cluster and enters VRU-ACTIVE-STANDALONE Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VRU breaks up cluster and state changes to VRU-ACTIVE-STANDALONE } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-06 Test objective Check that consecutive individual VAM transmissions occur at an interval equal or larger than T_GenVam Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer } Expected behaviour ensure that { when { VAM is transmitted at time t2 not containing vruClusterInformationContainer } then { t2 - t1 >= T_Gen_Vam } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 40 TP Id TP/VBS/TRCN/BV-07 Test objective Check that consecutive VAM transmissions occur when T_GenVamMax is exceeded Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 and no other VAM has been sent since then } Expected behaviour ensure that { when { T_GenVamMax is exceeded } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-08 Test objective Check that consecutive individual VAM transmissions occur when the Euclidian absolute distance between the current estimated VRU reference point position and the last estimated VRU reference point position exceeds minReferencePointPositonChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer and containing basicContainer containing referencePosition P1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new position value P2 and Euclidean distance (P1, P2) > minReferencePointPositonChangeThreshold } then { VBS sends VAM not containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 41 TP Id TP/VBS/TRCN/BV-09 Test objective Check that consecutive individual VAM transmissions occur when the difference between the current estimated VRU reference point ground speed and the last estimated VRU reference point ground speed exceeds minGroundSpeedChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer and containing vruHighFrequencyContainer containing speed containing speedValue indicating v1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new speed value v2 and abs(v2 - v1) > minGroundSpeedChangeThreshold } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-10 Test objective Check that consecutive individual VAM transmissions occur when the difference between the orientation of the vector of the current estimated ground velocity of the reference point of the VRU and the estimated orientation of the vector of the ground velocity of the reference point of the VRU lastly included in an individual VAM exceeds minGroundVelocityOrientationChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer and containing vruHighFrequencyContainer containing heading containing headingValue indicating h1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new heading value h2 and abs(h2 - h1) > minGroundVelocityOrientationChangeThreshold } then { VBS sends VAM not containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 42 TP Id TP/VBS/TRCN/BV-11 Test objective Check that consecutive individual VAM transmissions occur when the difference between the current estimated trajectory interception probability with vehicle(s) or other VRU(s) and the trajectory interception probability with vehicle(s) or other VRU(s) lastly reported in an individual VAM exceeds minTrajectoryInterceptionProbChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer and containing vruMotionPredictionContainer containing trajectoryInterceptionIndication containing trajectoryInterceptionProbability indicating p1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new trajectory interception probability value p2 and abs(p2 - p1) > minTrajectoryInterceptionProbChangeThreshold } then { VBS sends VAM not containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 43 TP Id TP/VBS/TRCN/BV-12 Test objective Check that consecutive individual VAM transmissions occur when one or more other VRUs are simultaneously coming closer than Minimum Safe Lateral Distance (MSLaD) laterally, closer than Minimum Safe Longitudinal Distance (MSLoD) longitudinally and closer than Minimum Safe Vertical Distance (MSVD) vertically Reference ETSI TS 103 300-3 [1], clause 6.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 not containing vruClusterInformationContainer and VAM has been received from other VRU containing basicContainer containing referencePosition P1 containing latitude indicating lat1 and containing longitude indicating lon1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new reference position value P1 containing latitude value lat2 and containing longitude value lon2 and abs(lat2 - lat1) < MSLaD and abs(lon2 - lon1) < MSLoD and Euclidean distance (P1, P2) < MSVD } then { VBS sends VAM not containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-13 Test objective Check that a VRU cluster VAM is generated immediately after a VRU in VRU-ACTIVE- STANDALONE determines to form a VRU cluster Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE } Expected behaviour ensure that { when { VRU forms a cluster } then { VBS sends VAM containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 44 TP Id TP/VBS/TRCN/BV-14 Test objective Check that consecutive cluster VAM transmissions occur when the Euclidean absolute distance between the current estimated VRU reference point position and the last estimated VRU reference point position exceeds minReferencePointPositonChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 containing vruClusterInformationContainer and containing basicContainer containing referencePosition P1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new position value P2 and Euclidean distance (P1, P2) > minReferencePointPositonChangeThreshold } then { VBS sends VAM containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-15 Test objective Check that consecutive cluster VAM transmissions occur when the difference between the current estimated ground speed of the reference point of the VRU cluster and the estimated absolute speed of the reference point lastly included a VRU cluster VAM exceeds minGroundSpeedChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in statestate VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 containing vruClusterInformationContainer and containing vruHighFrequencyContainer containing speed containing speedValue indicating v1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new speed value v2 and abs(v2 - v1) > minGroundSpeedChangeThreshold } then { VBS sends VAM containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 45 TP Id TP/VBS/TRCN/BV-16 Test objective Check that consecutive cluster VAM transmissions occur when the difference between the orientation of the vector of the current estimated ground velocity of the reference point of the VRU cluster and the estimated orientation of the vector of the ground velocity of the reference point lastly included in a VRU cluster VAM exceeds minGroundVelocityOrientationChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 containing vruClusterInformationContainer and containing vruHighFrequencyContainer containing heading containing headingValue indicating h1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new heading value h2 and abs(h2 - h1) > minGroundVelocityOrientationChangeThreshold } then { VBS sends VAM containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-17 Test objective Check that consecutive cluster VAM transmissions occur when difference between the current estimated trajectory interception probability with vehicle(s) or other VRU(s) and the trajectory interception probability with vehicle(s) or other VRU(s) lastly reported in a cluster VAM exceeds minTrajectoryInterceptionProbChangeThreshold Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in statestate VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 containing vruClusterInformationContainer and containing vruMotionPredictionContainer containing trajectoryInterceptionIndication containing trajectoryInterceptionProbability indicating p1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_GenVam is exceeded and the IUT is alerted about new probability value p2 and abs(p2 - p1) > minGroundVelocityOrientationChangeThreshold } then { VBS sends VAM containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 46 TP Id TP/VBS/TRCN/BV-18 Test objective Check that consecutive cluster VAM transmissions occur when the cluster type has been changed after previous VAM generation event Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted containing vruClusterInformationContainer and cluster type has been changed } Expected behaviour ensure that { when { VAM is generated } then { VBS sends VAM containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-19 Test objective Check that consecutive cluster VAM transmissions occur when more than a pre-defined number of new VRUs has joined the VRU cluster after transmission of previous VRU cluster VAM Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted containing vruClusterInformationContainer containing clusterCardinalitySize indicating value S1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_Gen_Vam is exceeded and the IUT alerted of a new cluster size S2 and S2 - S1 > T_ClusterJoinMax } then { VBS sends VAM containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 47 TP Id TP/VBS/TRCN/BV-20 Test objective Check that consecutive cluster VAM transmissions occur when more than a pre-defined number of members has left the VRU cluster after transmission of previous VRU cluster VAM Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted containing vruClusterInformationContainer containing clusterCardinalitySize indicating value S1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_Gen_Vam is exceeded and the IUT alerted of a new cluster size S2 and S1 – S2 > T_ClusterLeaveMax } then { VBS sends VAM containing vruClusterInformationContainer } } TP Id TP/VBS/TRCN/BV-21 Test objective Check that consecutive cluster VAM transmissions occur when one or more non-member VRUs are simultaneously coming closer than Minimum Safe Lateral Distance (MSLaD) laterally, closer than Minimum Safe Longitudinal Distance (MSLoD) longitudinally and closer than Minimum Safe Vertical Distance (MSVD) vertically Reference ETSI TS 103 300-3 [1], clause 6.4.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM has been transmitted at time t1 containing vruClusterInformationContainer and VAM has been received from other VRU containing basicContainer containing referencePosition P1 containing latitude indicating lat1 and containing longitude indicating lon1 and the IUT not having sent any other VAM } Expected behaviour ensure that { when { T_Gen_Vam is exceeded and the IUT is alerted about new reference position value P2 containing latitude value lat2 and containing longitude value lon2 and abs(lat2 - lat1) < MSLaD and abs(lon2 - lon1) < MSLoD and Euclidean distance (P1, P2) < MSVD } then { VBS sends VAM containing vruClusterInformationContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 48 TP Id TP/VBS/TRCN/BV-22 Test objective Check that a consecutive cluster VAM transmission is skipped if the time since the last VAM, the position change, the speed change and the heading change do not exceed the defined thresholds Reference ETSI TS 103 300-3 [1], clause 6.4.3 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 containing vruClusterInformationContainer and VAM has been received from other VRU containing basicContainer containing referencePosition P1 and containing vruHighFrequencyContainer containing speed containing speedValue indicating value v1 and containing heading containing headingValue indicating value h1 and the IUT not having sent any other VAM and [current time] - t1 <= numSkipVamsForRedundancyMitigation * T_GenVamMax } Expected behaviour ensure that { when { T_Gen_Vam is exceeded and the IUT is alerted about new reference position value P2 and Euclidean distance (P1, P2) <= minReferencePointPositionChangeThreshold and the IUT is alerted about a new speed value v2 and abs(v2 - v1) <= minGroundSpeedChangeThreshold and the IUT is alerted about a new heading value h2 and abs(h2 - h1) <= minGroundValocityOrientationChangeThreshold } then { VBS does not send VAM } } TP Id TP/VBS/TRCN/BV-23 Test objective Check that a consecutive cluster VAM transmission is skipped if information about the ego-VRU has been reported by another ITS-S within T_GenVam Reference ETSI TS 103 300-3 [1], clause 6.4.3 PICS Selection PICS_VAM_TRANSMISSION, PICS_CLUSTERING Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE and VAM has been transmitted at time t1 containing vruClusterInformationContainer and information about the ego-VRU has been reported by another ITS-S } Expected behaviour ensure that { when { T_Gen_Vam is exceeded } then { VBS does not send VAM } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 49 TP Id TP/VBS/TRCN/BV-24 Test objective Check that VAM is time-stamped Reference ETSI TS 103 300-3 [1], clause 6.4.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { VBS sends VAM containing generationDeltaTime } } TP Id TP/VBS/TRCN/BV-25 Test objective Check that time required to generate VAM is less than T_AssembleVAM Reference ETSI TS 103 300-3 [1], clause 6.4.4.1 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VAM generation is triggered at time t1 } Expected behaviour ensure that { when { VAM is delivered to the networking & transport layer at time t2 } then { t2 - t1 < T_AssembleVAM } } TP Id TP/VBS/TRCN/BV-26 Test objective Check that the VAM reference timestamp corresponds to the time the reference position provided in the BasicContainer Reference ETSI TS 103 300-3 [1], clause 6.4.4.2 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated containing basicContainer containing referencePosition at time t } then { VAM is sent containing generationDeltaTime indicating value t +- 5 s } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 50 TP Id TP/VBS/TRCN/BV-27 Test objective Check that the difference between VAM generation time and reference timestamp is less than 32 767 ms Reference ETSI TS 103 300-3 [1], clause 6.4.4.2 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing GeoNetworking header containing Secure Header containing signedData containing ToBeSignedData containing HeaderInfo containing GenerationTime64 and containing VAM containing generationDeltaTime indicating value - GenerationTime64 < 32767 ms } }
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.7 Frequency/Periodicity range of VAMs
|
TP Id TP/VBS/FRPE/TI-01 Test objective Check that the minimum time elapsed between the start of consecutive VAM generation events is equal or larger than T_Gen_Vam Reference ETSI TS 103 300-3 [1], clause 6.2 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VBS has started generating a VAM at time t1 } Expected behaviour ensure that { when { VBS starts generating a VAM at time t2 } then { t2 - t1 >= T_Gen_Vam } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 51 TP Id TP/VBS/FRPE/BV-02 Test objective Check that the LF container is included in the first VAM generation Reference ETSI TS 103 300-3 [1], clause 6.2 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VBS activation has occurred and no VAM has been sent yet } Expected behaviour ensure that { when { VAM is generated } then { VBS sends VAM containing vruLowFrequencyContainer } } TP Id TP/VBS/FRPE/BV-03 Test objective Check that the LF container is included periodically after 2000 ms Reference ETSI TS 103 300-3 [1], clause 6.2 PICS Selection PICS_VAM_TRANSMISSION Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and VBS activation has occurred and VBS has sent a VAM containing vruLowFrequencyContainer at time t1 and VBS has not sent VAM containing vruHighFrequencyContainer after t1 } Expected behaviour ensure that { when { VAM is generated at t2 >= (t1 + 2 000 ms) } then { VBS sends VAM containing vruHighFrequencyContainer } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 52 TP Id TP/VBS/FRPE/TI-04 Test objective Check that T_GenVam is set to T_GenVamMax if the value for T_GenVam provided by the VBS management entity is larger than T_GenVamMax in case of ITS-G5 Reference ETSI TS 103 300-3 [1], clause 6.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_ITS_G5 Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and T_GenVam >= T_GenVamMax and VAM has been sent at time t1 } Expected behaviour ensure that { when { next VAM is generated at time t2 } then { t2 - t1 = T_GenVamMax } } TP Id TP/VBS/FRPE/TI-05 Test objective Check that T_GenVam is set to T_GenVamMin if the value for T_GenVam is not provided by the VBS management entity or smaller than T_GenVamMin in case of ITS-G5 Reference ETSI TS 103 300-3 [1], clause 6.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_ITS_G5 Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER and T_GenVam is not provided or T_GenVam <= T_GenVamMin and VAM has been sent at time t1 } Expected behaviour ensure that { when { next VAM is generated at time t2 } then { t2 - t1 = T_GenVamMin } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 53
|
88e477d9d8b0c55065c738c067ae6be3
|
104 018-2
|
5.2.8 Security constraints
|
TP Id TP/VBS/SECC/BV-02 Test objective Check that the ITS-AID indicates the application for which permissions are being granted Reference ETSI TS 103 300-3 [1], clause 6.5.1 PICS Selection PICS_VAM_TRANSMISSION, PICS_SECURITY Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is generated } then { Message is sent containing GeoNetworking header containing Secure Header containing signedData containing certificate containing Certificate containing ToBeSigned containing AppPermissions } } TP Id TP/VBS/SECC/BV-04 Test objective Check that the SSP is a BitmapSsp Reference ETSI TS 103 300-3 [1], clause 6.5.2 PICS Selection PICS_VAM_TRANSMISSION, PICS_SECURITY Initial conditions with { VBS in state VRU-ACTIVE-STANDALONE or VBS in state VRU-ACTIVE-CLUSTER-LEADER } Expected behaviour ensure that { when { VAM is transmitted over BTP with GeoNetworking protocol } then { Message is sent containing GeoNetworking header containing Secure Header containing signedData containing certificate containing Certificate containing ToBeSigned containing AppPermissions containing at least one item containing Bitmap SSP } } ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 54 Annex A (informative): Bibliography • ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary". ETSI ETSI TS 104 018-2 V2.1.1 (2025-07) 55 History Version Date Status V2.1.1 July 2025 Publication
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
1 Scope
|
The present document provides an interface definition for the e-Evidence Regulation (EU) 2023/1543 [i.1], supporting National Authorities and Service Providers in understanding and complying with its requirements. The present document provides an overview of the overall solution, defines the workflow profile for ETSI TS 103 120 [1] that facilitates compliance with Regulation (EU) 2023/1543 [i.1] and provides best practices and technical recommendations. The present document serves as a technical interface definition to foster consistent and effective application across the EU.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
2 References
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 103 120: "Lawful Interception (LI); Interface for warrant information". [2] ETSI TS 103 280: "Lawful Interception (LI); Dictionary for common parameters".
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Regulation (EU) 2023/1543 on European Production Orders and European Preservation Orders for electronic evidence in criminal proceedings and for the execution of custodial sentences following criminal proceedings. [i.2] Directive (EU) 2018/1972 of the European Parliament and of the Council of 11 December 2018 establishing the European Electronic Communications Code. [i.3] Directive (EU) 2015/1535 of the European Parliament and of the Council of 9 September 2015 laying down a procedure for the provision of information in the field of technical regulations and of rules on Information Society services (codification). [i.4] ETSI TS 103 705: "Lawful Interception (LI); Data Structures for Lawful Disclosure". ETSI ETSI TS 104 144 V1.1.1 (2025-06) 8
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
3 Definition of terms, symbols and abbreviations
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
3.1 Terms
|
For the purposes of the present document, the following terms apply: Form 1: European Production Order Certificate (EPOC) for the production of electronic evidence, as given in the Regulation [i.1] Annex I Form 2: European Preservation Order Certificate (EPOC-PR) for the preservation of electronic evidence, as given in the Regulation [i.1] Annex II Form 3: information on the impossibility of executing an EPOC / EPOC-PR, as given in the Regulation [i.1] Annex III Form 5: confirmation of issuance of a request for production following a European Preservation Order, as given in the Regulation [i.1] Annex V Form 6: extension of the preservation of electronic evidence, as given in the Regulation [i.1] Annex VI the Regulation: Regulation (EU) 2023/1543 [i.1]
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
3.2 Symbols
|
Void.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: API Application Programming Interface EPOC European Production Order Certificate EPOC-PR European Preservation Order Certificate GPRS General Packet Radio Service HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol (Secure) ID IDentifier IMEI International Mobile station Equipment Identity IT Information Technology JSON JavaScript Object Notation LDID Lawful Disclosure IDentifier MAC Media Access Control RI-API Reference Implementation Application Programming Interface SP Service Provider URL Uniform Resource Locator UUID Universally Unique IDentifier XML eXtensible Markup Language
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4 Reference Model
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4.1 Wider system of interest
|
The wider system of interest for e-Evidence, as defined by the Regulation [i.1] is given in figure 4.1-1. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 9 Issuing Member State Infrastructure RI Authority / National System Authority e-CODEX European Commission CDB Enforcing Member State Infrastructure Member State Service for Competent Authorities e-CODEX Web-based Interface for SPs (RI-API) Service Provider Infrastructure SP Bespoke IT solution Issuing Authority Enforcing Authority Service Provider ETSI TS 104 144 Figure 4.1-1: Wider system of interest The actors in the wider system of interest are described in table 4.1-1 using the terms from the Regulation [i.1] Article 3. The definitions are provided for reference and illustration only; for authoritative definitions, consult the Regulation [i.1]. The full system of interest also includes additional actors and functions which are not reproduced in figure 4.1-1 in the interests of clarity. For a full set of definitions, see the Regulation [i.1]. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 10 Table 4.1-1: Actors in e-Evidence wider system of interest Actor Description from e-Evidence regulation [i.1] Issuing Authority The competent authority in the Issuing State, which can issue a European Production Order or a European Preservation Order. Issuing Member State The Member State from which the European Production Order or the European Preservation Order is issued. Enforcing Authority The authority in the Enforcing State, which is competent to receive a European Production Order or a European Preservation Order transmitted by the issuing authority for notification or for enforcement. Enforcing Member State The Member State from which the designated establishment is established or the legal representative resides and to which a European Production Order or a European Preservation Order are transmitted by the issuing authority for notification or for enforcement. Service Provider Any natural or legal person that provides one or more of the following categories of services, with the exception of financial services: (a) electronic communications services as defined in Article 2, point (4), of Directive (EU) 2018/1972 [i.2]; (b) internet domain name and IP numbering services, such as IP address assignment, domain name registry, domain name registrar and domain name-related privacy and proxy services; (c) other information society services as referred to in Article 1(1), point (b), of Directive (EU) 2015/1535 [i.3] that: (i) enable their users to communicate with each other; or (ii) make it possible to store or otherwise process data on behalf of the users to whom the service is provided, provided that the storage of data is a defining component of the service provided to the user. RI Authority / National System Authority ("RI-API") Software component meant for use by Issuing Authorities to allow access to the decentralised IT system. Referred to in the present document as the RI-API, but also colloquially referred to as the "pink box" outside of the present document. e-CODEX Underlying message transport system used by the decentralised IT system. Member State Service for Competent Authorities Software component meant for use by Enforcing Authorities to allow access to the decentralised IT system. Web-based Interface for SPs Software component meant for use by Service Providers to allow access to the decentralised IT system. SP Bespoke IT Solution Software component maintained by the Service Providers for the purposes of servicing EPOC and EPOC-PR requests. Colloquially referred to as the "yellow box" outside of the present document. The present document provides a technical means for Service Providers and the Service Provider API of the RI / National IT system (RI-API) to ensure interoperability and compliance with the wider e-Evidence IT systems as defined in the Regulation [i.1]. It achieves this by defining an API for exchange of e-Evidence-related information between the web-based interface for SPs and the SP Bespoke IT Solution. All other aspects of the wider system of interest are out of scope of the present document. Implementers should consult with the providers of the RI-API prior to using the present document. NOTE: The RI-API interface can also be adapted for use between national IT systems of authorities and the RI, but such usage is out of scope of the present document.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4.2 API definition
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4.2.1 Approach
|
The present document defines an API for exchanging e-Evidence-related information between an RI-API and a Service Provider in an Enforcing Member State. This API uses the protocol and framework defined by ETSI TS 103 120 [1], and defines a Workflow Profile (see ETSI TS 103 120 [1] Annex H) that specifies how the messages and fields used in ETSI TS 103 120 [1] are to be used. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 11
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4.2.2 Business Workflows
|
The Regulation [i.1] provides a set of business workflows that specify how and when information is to be transferred between the various e-Evidence actors. An example of one such workflow is given in figure 4.2.2-1. EPOC Form 1 - Traffic Data (except data for the sole purpose of identifying the user) - Content Data Issuing Authority Delegated Establishment or Legal Representative Enforcing Authority Notification and Form 1 Reply - Traffic Data (except data for the sole purpose of identifying the user) - Content Data (10 days) Figure 4.2.2-1: Example business workflow for requesting non-emergency traffic or content data via an EPOC The API defines a set of message exchanges ("Workflow Endpoints") which can be used to realize each of the interactions between the Service Provider and either the Issuing Authority or Enforcing Authority which traverses the RI-API. Other interactions, such as those between Issuing Authority and Enforcing Authority, or interactions which do not traverse the RI-API, are out of scope of the present document. The e-Evidence business workflows can therefore be constructed using one or more of the Workflow Endpoints defined in the present document. As an example, the mapping for the workflow in figure 4.2.2-1 above is given in figure 4.2.2-2 below. /eevidence/delivery (clause 6.3) Out of scope /eevidence/production (clause 5.3) EPOC Form 1 - Traffic Data (except data for the sole purpose of identifying the user) - Content Data Issuing Authority Delegated Establishment or Legal Representative Enforcing Authority Notification and Form 1 Reply - Traffic Data (except data for the sole purpose of identifying the user) - Content Data (10 days) Figure 4.2.2-2: Example business workflow with Workflow Endpoints
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
4.2.3 Protocol definition
|
Each Workflow Endpoint defines a message exchange between the RI-API or Service Provider, as shown in figure 4.2.3-1 below. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 12 HI-1 Request Message (contains HI-1 Objects) RI-API Service Provider HI-1 Response Message (technical acknowledgement) Figure 4.2.3-1: Message exchange example (for an SP Workflow-Endpoint) Each message exchange using the protocol stack defined in ETSI TS 103 120 [1] and is shown in figure 4.2.3-2. This uses HTTPS to transfer XML-encoded messages ("HI-1 Messages") containing specific representations of state ("HI-1 Objects"). HI-1 Objects carry the information required by the e-Evidence processes. HTTPS HI-1 Message HI-1 Objects E-Evidence Info Figure 4.2.3-2: Protocol stack The present document consists of a set of normative rules for what information is required to be present in each HI-1 Message and HI-1 Object in a given message exchange, and where such information is to be mapped from the e-Evidence Forms. This definition of a message exchanges is called a "Workflow Endpoint". The set of Workflow Endpoints defined by the present document are given in clauses 5.1 and 6.1. This Workflow Profile is designed to ensure that e-Evidence material such as EPOC or EPOC-PR requests can, to the extent possible, be handled the same way as any other ETSI TS 103 120 [1] disclosure or preservation request. Details which are common to EPOC/EPOC-PR and other forms of disclosure or preservation are mapped to the appropriate place in existing ETSI TS 103 120 [1] structures, whereas details which are specific only to EPOC/EPOC-PR are contained in an EPOC/EPOC-PR-specific HI-1 object (see clause B.2). This approach is intended to maximize the possibility of re-use between EPOC/EPOC-PR systems and other implementations of ETSI TS 103 120 [1].
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5 SP Workflow Endpoints
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.1 Defined endpoints
|
This Workflow Profile defines the following operations that can be invoked at the SP, each of which is exposed as a Workflow Endpoint (see ETSI TS 103 120 [1], clause H.3.1) with a default relative URL path in table 5.1-1. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 13 Table 5.1-1: SP Workflow Endpoints Relative URL path Description Clause /eevidence/production European Production Order Certificate (EPOC) for the Production of Electronic Evidence (Form 1). 5.3 /eevidence/newdeadline Set a new deadline for an EPOC. 5.4 /eevidence/groundsforrefusal Enables the Enforcing Authority to communicate whether or not it has grounds for refusal after reviewing Form 1 (with Section M completed) or Form 3 from the Service Provider. 5.5 /eevidence/withdraw A decision of the Issuing Authority to withdraw the initial request, thereby terminating the process. 5.6 /eevidence/preservation European Preservation Order Certificate (EPOC-PR) for the Preservation of Electronic Evidence (Form 2). 5.7 /eevidence/subsequentproduction Confirmation of Issuance of a Request for Production Following a European Preservation Order (Form 5). 5.8 /eevidence/preservationextension Extension of the Preservation of Electronic Evidence (Form 6). 5.9 /eevidence/endpreservation Notifies the Service Provider that data preservation is no longer required, ending the preservation obligation. 5.10 /eevidence/deliverystatus Notifies the Service Provider that a message has been successfully delivered to an end recipient, or that delivery has failed. 5.11 /eevidence/correspondence Used by the Issuing Authority or Enforcing Authority to exchange free-text correspondence and associated documentation with the Service Provider, for any of the following purposes: • To notify the Service Provider that Issuing Authority, disagreeing with the reasons given in Form 3, is upholding the EPOC and intends to proceed to court. • To notify the Service Provider that the Issuing Authority wishes to maintain the initial request upon receipt of Form 3, where reasons for non-execution of the request are explained by the Service Provider, or after discussion with the notified Enforcing Authority. • To request additional information from the Service Provider. • To provide additional information to the Service Provider in response to a query. • To communicate a decision of the Enforcing Authority after receiving an objection from the Service Provider. • To notify the Service Provider that the Issuing Authority has initiated enforcement procedures to comply with an EPOC or EPOC-PR. • To communicate a decision of the Enforcing Authority to either uphold or not to recognize an order upon the initiation of enforcement procedures by the Issuing Authority. 5.12 The URL path is specified relative to the API base URL. Usage of the relative URL path is the default for the endpoint but is not required; different URL paths may be provided by mutual agreement during the onboarding process of an SP.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.2 Common procedures and constraints
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.2.1 Message exchange
|
Each invocation of an SP Workflow Endpoint shall consist of one HI-1 message exchange, as shown in figure 5.2.1-1. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 14 HI-1 Request Message (contains HI-1 Objects) RI-API Service Provider HI-1 Response Message (technical acknowledgement) Figure 5.2.1-1: Message exchange for SP Workflow Endpoint
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.2.2 Message contents
|
The Header section of each HI-1 message (see ETSI TS 103 120 [1], clause 6.2) shall be populated as described in table 5.2.2-1 below. Table 5.2.2-1: HI-1 Message Header Field Description M/C/O Reference SenderIdentifier Shall be set to an EndpointID value which identifies the RI-API, which shall be made known to the Service Provider when they are on-boarded to the e-Evidence platform. M ETSI TS 103 120 [1], clause 6.2.4 ReceiverIdentifier Shall be set to an EndpointID value which identifies the SP being addressed (e.g. the "Addressee" in Form 1 Section B) and which shall be agreed when the Service Provider is on-boarded to the E-Evidence platform. This may be distinct from the SP concerned in an EPOC or EPOC-PR (e.g. "Service Provider Concerned" in Form 1 Section B). M ETSI TS 103 120 [1], clause 6.2.4 TransactionIdentifier Shall be set to a unique UUID value for this transaction. M ETSI TS 103 120 [1], table 6.1 Timestamp Shall be set to the time the message was sent by the RI-API. M ETSI TS 103 120 [1], table 6.1 Version Shall be populated with a version of ETSI TS 103 120 [1] no earlier than V1.19.1. The NationalProfileOwner shall be set to "EU" and the NationalProfileVersion shall be set to the version of the present document. M ETSI TS 103 120 [1], clause 6.2.3 The Payload of each message shall be set according to details given in the relevant Workflow Endpoint clause below. Each Workflow Endpoint clause sets out the required set of Objects.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.3 Production Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.3.1 Description
|
This endpoint covers the act of serving a European Production Order ("EPOC") using the form defined in Form 1. It provides the initial set of Authorisation, Document and LDTask objects considered in the object model given in Annex A, which between them contain all the information required by the EPOC.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.3.2 Message contents
|
The contents of the Request shall be as per table 5.3.2-1 below. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 15 Table 5.3.2-1: HI-1 Objects for the Production Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE AuthorisationObject 1 Provides general authorisation information for the EPOC. Clause 5.3.3 CREATE LDTaskObject 1..n Provides technical instructions on what information is required by the EPOC and where to send it. Clause 5.3.4 CREATE DocumentObject 1 Carries the signed PDF representation of the EPOC, encoded as per ETSI TS 103 120 [1]. Annex C CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B CREATE DocumentObject 0..n May be used for any additional attachments that are sent as part of the message. Annex B Unless otherwise specified, each Object other than the AuthorisationObject shall have an association to the AuthorisationObject given in its AssociatedObjects field.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.3.3 AuthorisationObject
|
The fields in table 5.3.3-1 below shall be present in the CREATE Request for the AuthorisationObject. Table 5.3.3-1: Authorisation fields in the Production Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for the state of the Issuing Authority, as given in the "Issuing State" field in Form 1 Section A. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the Issuing Authority given in Form 1 Section A. M ETSI TS 103 120 [1], table 7.1 AssociatedObjects If Form 1 Section D states that the EPOC is related to a previous EPOC or EPOC-PR, and that EPOC or EPOC-PR was received via the RI- API, then the Object Identifier for the relevant AuthorisationObject shall be included. M ETSI TS 103 120 [1], clause 7.1.4 AuthorisationReference May be set to any suitable identifier chosen by the RI-API that identifies communications related to a particular EPOC or EPOC-PR. C ETSI TS 103 120 [1], table 7.1 AuthorisationLegalType Shall be set using the appropriate value from the EPOCLegalType dictionary (see table 5.3.3-2). M Table 5.3.3-2 AuthorisationPriority Shall be set using the appropriate EPOCPriority DictionaryEntry as specified in table 5.3.3-3. M Table 5.3.3-3 AuthorisationDesiredStatus Shall be set to the AuthorisationDesiredStatus DictionaryEntry "SubmittedToCSP". M ETSI TS 103 120 [1], table 7.7 AuthorisationCSPID Shall be set to the relevant technical identifier for the SP concerned (as determined by either the "service provider concerned" or "addressee" fields of Form 1 Section B). C ETSI TS 103 120 [1], table 7.1 AuthorisationApprovalDetails Shall contain at least information regarding the Issuing Authority (see table 5.3.3-5). May also contain details of the Validating Authority (see table 5.3.3-8) if specified. M Table 5.3.3-5 and table 5.3.3-8 AuthorisationFlags If Form 1 Section B specifies that the order is issued in an emergency case, the AuthorisationFlag "IsEmergency" DictionaryEntry shall be included (see ETSI TS 103 120 [1], clause 7.2.12). Other flags shall be included as per table 5.3.3-4. M Table 5.3.3-4 and ETSI TS 103 120 [1], clause 7.2.12 AuthorisationLegalEntity Shall be set to the Service Provider Concerned, if given in Form 1 Section B. Otherwise shall be set to the Addressee given in Form 1 Section B. M ETSI TS 103 120 [1], clause 7.2.15 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 16 Table 5.3.3-2: EPOCLegalType Dictionary Dictionary Owner Dictionary Name ETSI EPOCLegalType Defined DictionaryEntries Value Meaning EPOC The Authorisation is associated with an EPOC. EPOC-PR The Authorisation is associated with an EPOC-PR. Table 5.3.3-3: EPOCPriority Dictionary Dictionary Owner Dictionary Name ETSI EPOCPriority Defined DictionaryEntries Value Meaning TenDaysASAP Indicates that Form 1 Section C specifies that data is required as soon as possible and within ten days (no notification to enforcing authority). TenDaysSubjectToEA Indicates that Form 1 Section C specifies that data is required at the end of ten days if the Enforcing Authority raises no grounds for refusal, or as soon as possible after the Enforcing Authority has confirmed that it will not raise grounds for refusal. EightHours Indicates that Form 1 Section C specifies that data is required as soon as possible and within eight hours due to an emergency case. Table 5.3.3-4: EPOCAuthorisationFlag Dictionary Dictionary Owner Dictionary Name ETSI EPOCAuthorisationFlag Defined DictionaryEntries Value Meaning DelayInformingUser Indicates that Form 1 Section H specifies that the Issuing Authority will delay informing the person whose data are being requested. EnforcingAuthorityNotified Indicates that Form 1 Section K indicates that the Enforcing Authority has been notified of the EPOC. The Authorisation shall contain an Approval populated as per table 5.3.3-5 using the details from Form 1 Section I. Table 5.3.3-5: AuthorisationObject ApprovalDetails for Issuing Authority Field Description M/C/O Reference ApprovalType Shall be set to "IssuingAuthority". M ETSI TS 103 120 [1], table E.1 ApprovalReference Shall be set to the value given as "File number" Form 1 Section I, if available. C ETSI TS 103 120 [1], table E.1. ApproverDetails See table 5.3.3-6. M Table 5.3.3-6 ApprovalTimestamp Shall be set to the date of the signature as given in Form 1 Section I. M ETSI TS 103 120 [1], table E.1 ApprovalIsEmergency Shall be set to "True" if Form 1 Section I specifies that the EPOC was issued in a validly established emergency case without prior validation. Shall be set to "False" otherwise. C ETSI TS 103 120 [1], table E.1 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 17 Table 5.3.3-6: AuthorisationObject ApproverDetails for Issuing Authority Field Description M/C/O Reference ApproverName Shall be set to the value given as "Name of authority" in Form 1 Section I. M ETSI TS 103 120 [1], table E.2 ApprovalRole Shall be set to "JudgeCourtOrInvestigatingJudge" or "PublicProsecutor" or "OtherCompetentAuthority" as given in Form 1 Section I. M ETSI TS 103 120 [1], table E.2 ApproverContactDetails Shall contain at least one instance of ApproverContactDetails populated according to table 5.3.3-7. A second instance shall be included if Form 1 Section I provides alternate point-of-contact details. M Table 5.3.3-7 Table 5.3.3-7: AuthorisationObject ApproverContactDetails for Issuing Authority Field Description M/C/O Reference Name Shall be set to the value given as "Name of its representative" in Form 1 Section I, or "Name of the authority/name" if describing the alternative point of contact. M ETSI TS 103 120 [1], clause 7.1.7 Role Shall be set to the value given as "Post held (title/grade)" in Form 1 Section I, or the literal string "Point of Contact" if describing the alternate point of contact. C ETSI TS 103 120 [1], clause 7.1.7 EmailAddress Shall be set to the value given as the relevant "Email Address" field in Form 1 Section I, if present. C ETSI TS 103 120 [1], clause 7.1.7 PhoneNumber Shall be set to the value given as the relevant "Tel No" field in Form 1 Section I, if present. C ETSI TS 103 120 [1], clause 7.1.7 FaxNumber Shall be set to the value given as the relevant "Fax No" field in Form 1 Section I, if present. C ETSI TS 103 120 [1], clause 7.1.7 Address Shall be set to the value given as the relevant "Address" field in Form 1 Section I, if present. C ETSI TS 103 120 [1], clause 7.1.7 Languages Shall include the language identifiers given in the "Language(s) spoken" field in Form 1 Section I if present or omitted if describing the alternate point of contact. C ETSI TS 103 120 [1], clause 7.1.7 If a Validating Authority is specified in Form 1 Section J, the Authorisation shall contain an ApprovalObject with the fields given in table 5.3.3-8 using details from Form 1 Section J. Table 5.3.3-8: AuthorisationObject ApprovalDetails for Validating Authority Field Description M/C/O Reference ApprovalType Shall be set to "ValidatingAuthority". M ETSI TS 103 120 [1], table E.1 ApprovalReference Shall be set to the value given as "File number" Form 1 Section J, if available. C ETSI TS 103 120 [1], table E.1. ApproverDetails See table 5.3.3-9. M Table 5.3.3-9 ApprovalTimestamp Shall be set to the date of the signature as given in Form 1 Section J. M ETSI TS 103 120 [1], table E.1 Table 5.3.3-9: AuthorisationObject ApproverDetails for Validating Authority Field Description M/C/O Reference ApproverName Shall be set to the value given as "Name of the authority" in Form 1 Section J. M ETSI TS 103 120 [1], table E.2 ApprovalRole Shall be set to "JudgeCourtOrInvestigatingJudge" or "PublicProsecutor" as given in Form 1 Section J. M ETSI TS 103 120 [1], table E.2 ApproverContactDetails Shall contain an instance of ApproverContactDetails populated in the same way as table 5.3.3-7. M Table 5.3.3-7 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 18
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.3.4 LDTask Objects
|
The Production request shall contain one LDTask Object for each independent identifier given in Form 1 Section E, together with the relevant types of data requested in Form 1 Section F. The fields given in table 5.3.4-1 shall be present in each CREATE request for each LDTask Object. Table 5.3.4-1: LDTaskObject fields in the Production Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for the state of the Issuing Authority, as given in the "Issuing State" field in Form 1 Section A. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the Issuing Authority given in Form 1 Section A. M ETSI TS 103 120 [1], table 7.1 AssociatedObjects Shall be set to include the Object ID of the AuthorisationObject (see clause 5.3.3). M ETSI TS 103 120 [1], clause 7.1.4 Reference Shall be set to an LDID chosen by the Issuing Authority or constructed by the RI-API on behalf of the Issuing Authority. M ETSI TS 103 120 [1], clause 8.3.2. DesiredStatus Shall be set to LDTaskDesiredStatus value "AwaitingDisclosure". M ETSI TS 103 120 [1], table 8.17 RequestDetails Identifies the requested data and the evidence to be produced (Form 1 Sections E and F). M Table 5.3.4-2 DeliveryDetails The destination of the transfer of data as specified in (Form 1 Section L). M Table 5.3.4-4 Table 5.3.4-2: LDTaskObject RequestDetails Field Description M/C/O Reference Type Shall be set to the relevant value from the RequestType dictionary in ETSI TS 103 120 [1], clause 8.3.5.2 to match the value given in Form 1 Section E. M ETSI TS 103 120 [1], clause 8.3.5.2. StartTime Shall be set to the value given as the "time range of the data for which production is requested" in Form 1 Section E, if present. C ETSI TS 103 120 [1], clause 8.18 EndTime Shall be set to the value given as the "time range of the data for which production is requested" in Form 1 Section E, if present. C ETSI TS 103 120 [1], clause 8.18 ObservedTimes If "IP address(es) and timestamps" are specified in Form 1 Section E, this field shall be set to the timestamps given. C ETSI TS 103 120 [1], table 8.18 RequestValues Shall be populated with the appropriate values from Form 1 Section E. For standardized identifier types, the mapping shall be performed as per table 5.3.4-6 below. For Service Provider specified identifier types, the relevant Service Provider Format types may be used. M Table 5.3.4-6 SubType Shall be populated with each of the relevant values from table 5.3.4-3 for each option selected in Form 1 Section F. For Service Provider specified request subtypes, the relevant Service Provider RequestSubtypes may be used. M Table 5.3.4-3 TargetIdentifierS ubtype Shall be set to the value(s) given as "Name(s) of the relevant service(s)" from Form 1 Section E, if present, using the relevant SP-provided dictionary of valid TargetIdentifierSubtypes. C ETSI TS 103 120 [1], clause 8.3.5.6 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 19 Table 5.3.4-3: EPOCRequestSubtype Dictionary Dictionary Owner Dictionary Name ETSI EPOCRequestSubtype Defined DictionaryEntries Value Meaning UserInformation Form 1 Section F checkbox labelled "Name, date of birth, postal or geographic address", etc. was checked. RegistrationInformation Form 1 Section F checkbox labelled "Date and time of initial registration" etc. was checked. TypeOfServiceInformation Form 1 Section F checkbox labelled "Type of service and its duration" etc. was checked. ProfileInformation Form 1 Section F checkbox labelled "Profile information" etc. was checked. DataOnValidationOfUse Form 1 Section F checkbox labelled "Data on the validation of the use of service" etc. was checked. DebitOrCreditCardInformation Form 1 Section F checkbox labelled "Debit or credit card information" etc. was checked. SubscriberDataOther Form 1 Section F checkbox labelled "Other" in bullet (a) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. IPConnectionRecords Form 1 Section F checkbox labelled "IP connection records such as IP addresses" etc. was checked. If any details are provided in the associated free- text field, these shall be included in the LDTask ManualInformation field. IdentfyingUserOther Form 1 Section F checkbox labelled "Other" in bullet (b) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. OutgoingAndIncomingTrafficData Form 1 Section F checkbox labelled "Outgoing (A) and incoming (B) identifiers" etc. was checked. TimeAndDurationOfConnections Form 1 Section F checkbox labelled "Time and duration of connection(s)" was checked. CallAttempts Form 1 Section F checkbox labelled "Call Attempt(s)" was checked. MobileBaseStationID Form 1 Section F checkbox labelled "Base station ID, including geographical information" etc. under bullet (c) (i) was checked. BearerUsed Form 1 Section F checkbox labelled "Bearer / teleservice used (e.g. UMTS, GPRS)" was checked. TrafficDataMobileOther Form 1 Section F checkbox labelled "Other" in bullet (c) (i) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. RoutingInformation Form 1 Section F checkbox labelled "Routing information (source IP address" etc. was checked. InternetBaseStationID Form 1 Section F checkbox labelled "Base station ID, including geographical information" etc. under bullet (c) (ii) was checked. VolumeOfData Form 1 Section F checkbox labelled "Volume of data" was checked. DateAndTimeOfConnection Form 1 Section F checkbox labelled "Date and time of connection(s)" was checked. DurationOfConnection Form 1 Section F checkbox labelled "Duration of connection or access session(s)" was checked. TrafficDataMobileOther Form 1 Section F checkbox labelled "Other" in bullet (c) (ii) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. Logfiles Form 1 Section F checkbox labelled "Logfiles" was checked. Tickets Form 1 Section F checkbox labelled "Tickets" was checked. TrafficDataInternetOther Form 1 Section F checkbox labelled "Other" in bullet (c) (iii) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. PurchaseHistory Form 1 Section F checkbox labelled "Purchase History" was checked. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 20 Defined DictionaryEntries Value Meaning PrepaidBalance Form 1 Section F checkbox labelled "Prepaid balance charging history" was checked. TrafficDataOtherOther Form 1 Section F checkbox labelled "Other" in bullet (c) (iv) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. MailboxDump Form 1 Section F checkbox labelled "(web)mailbox dump" was checked. OnlineStorageDump Form 1 Section F checkbox labelled "Online storage dump" etc. was checked. Pagedump Form 1 Section F checkbox labelled "Pagedump" was checked. MessageLog Form 1 Section F checkbox labelled "Message log/backup" was checked. VoicemailDump Form 1 Section F checkbox labelled "Voicemail dump" was checked. ServerContents Form 1 Section F checkbox labelled "Server contents" was checked. DeviceBackup Form 1 Section F checkbox labelled "Device backup" was checked. ContactList Form 1 Section F checkbox labelled "Contact list" was checked. ContentDataOther Form 1 Section F checkbox labelled "Other" in bullet (d) was checked. If the value provided next to the "other" box can be interpreted as a valid Service Provider supplied RequestSubtype DictionaryEntry, then that DictionaryEntry may be used instead, otherwise the relevant details shall also be provided in the LDTask ManualInformation field. AdditionalRequestTypeInfo Form 1 Section F checkbox labelled "Additional information in case necessary to (further) specify or limit the range of the requested data" was checked. Any information present in the associated free text field shall be included in the LDTaskObject ManualInformation field. Table 5.3.4-4: LDTaskObject DeliveryDestination fields Field Description M/C/O Reference DeliveryAddress Shall be given as a DestinationEndpointID containing the name and contact details as given in EPOC Form 1 Section L, if a value is given. C ETSI TS 103 120 [1], clause 8.2.8.3 HandoverFormat Set to the appropriate LDHandoverFormat Dictionary entry (see ETSI TS 103 120 [1], table 8.24) if a supported value is given in EPOC Form 1 Section L. Any other value shall be placed in the LDTask ManualInformation field. C ETSI TS 103 120 [1], clause 8.2.8.4 DeliveryProfile Shall be set with the appropriate EPOCDeliveryProfileDictionary as given in table 5.3.4-5, if a value is given. If more than one destination is specified, a separate LDDeliveryDestination instance shall be given for each destination. M Table 5.3.4-5 Table 5.3.4-5: EPOCDeliveryProfile Dictionary Dictionary Owner Dictionary Name ETSI EPOCDeliveryProfile Defined DictionaryEntries Value Meaning IssuingAuthority The data shall be transferred to the Issuing Authority. ValidatingAuthority The data shall be transferred to the Validating Authority. OtherCompetentAuthority The data shall be transferred to another competent authority. Any details specified in Form 1 Section L shall be placed in the LDTask ManualInformation field. The RequestValues structure shall be populated according to the values given in Form 1 Section E. Table 5.3.4-6 gives the required ETSI TS 103 120 [1], Annex C Format Name to be used in the RequestValues structure for each identifier type in Section E. Each independent identifier shall be provided as a separate LDTask Object, unless otherwise specified in table 5.3.4-6. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 21 Table 5.3.4-6: RequestValue mapping Form 1 Field RequestValue Format Value Notes ETSI TS 103 280 [2] reference IP address(es) and timestamps IPV4Address or IPV6Address, as appropriate If multiple IP addresses that together identify the requested data (i.e. data should only be returned for a subject which matches all supplied IP addresses) then the IP addresses shall be provided as multiple RequestValues in the same LDTask Object. Otherwise, if data should be returned for a subject which matches any of the supplied IP addresses, then the IP addresses shall be supplied individually in separate LDTask Objects. If dates are supplied as part of the IP addresses in Form 1 Section E, these shall be given in the ObservedTimes field (see table 5.3.4-2). Clause 6.11 or 6.13 Tel No InternationalE164 Clause 6.6 Email address(es) EmailAddress or InternationalizedEmailAddress, as appropriate Clause 6.26 or 6.49 IMEI number(s) IMEI or IMEISV as appropriate Clause 6.8 or 6.10 MAC address(es) MACAddress Clause 6.25 The user(s) or other unique identifiers ServiceAccessIdentifier Use of this field is discouraged in favour of using SP-provided definitions (see below) where available. Clause 6.58 Other Other If the identifier type "Other" is chosen and no Service-Provider-specified FormatName can be determined, the RequestValue Format Name "Other" shall be used (with the Format Owner set to "ETSI"). If a Service-Provider- specified FormatName can be determined, that shall be used instead.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.4 New Deadline Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.4.1 Description
|
This endpoint covers the act of setting a new deadline for compliance with an EPOC.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.4.2 Message contents
|
The contents of the Request shall be as per table 5.4.2-1 below. Table 5.4.2-1: HI-1 Objects for the New Deadline Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE LDTaskObject 1..n Resets the deadline for compliance with the original EPOC request for each LDTaskObject for which data is still required. Clause 5.4.3 CREATE EPOCAdditionalInfo 0..n May be used for unmapped information Annex B ETSI ETSI TS 104 144 V1.1.1 (2025-06) 22
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.4.3 LDTaskObject
|
The Request shall contain an UPDATE Request for each LDTaskObject in the original EPOC (see clause 5.3) for which a new deadline is required. The fields in table 5.4.3-1 shall be present in each such UPDATE Request. Table 5.4.3-1: LDTaskObject fields in the New Deadline Workflow Endpoint Field Description M/C/O Reference Deadline Shall contain an LDDeadline entry for all deadlines currently applicable to the LDTaskObject, including the one being updated. M Table 5.4.3-2 Table 5.4.3-2: LDDeadline fields in the New Deadline Workflow Endpoint Field Description M/C/O Reference DateTime Shall be set to a fully qualified date and time of the deadline. M ETSI TS 103 120 [1], clause 8.3 NatureOfDeadline For the new deadline, shall be set to the value "DeadlineForDelivery" from the LDNatureOfDeadline dictionary (see ETSI TS 103 120 [1], table 8.Y) or an appropriate DictionaryEntry value from a Dictionary supplied by the Issuing Authority. For all other deadlines, shall be set to the value originally given (see clause 5.3). M ETSI TS 103 120 [1], clause 8.3 OtherInformation May contain any additional human-readable information related to the deadline. O ETSI TS 103 120 [1], clause 8.3
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.5 Grounds For Refusal Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.5.1 Description
|
This endpoint covers an Enforcing Authority indicating whether it has grounds for refusal or not after reviewing Form 1 (with Section M completed) or Form 3 from the Service Provider.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.5.2 Message contents
|
The contents of the Request shall be as per table 5.5.2-1 below. Table 5.5.2-1: HI-1 Objects for the Grounds For Refusal Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE Document 1..n Indicates that the Enforcing Authority has exercised its grounds for refusal. Clause 5.5.3 CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.5.3 Document Object
|
The Request shall contain at least one CREATE Request for a Document Object that represents the decision of the Enforcing Authority. The fields in table 5.5.3-1 shall be present in each such CREATE Request. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 23 Table 5.5.3-1: DocumentObject fields in the Grounds For Refusal Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for the state of the Enforcing Authority. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the Enforcing Authority given in Form 1 Section A. M ETSI TS 103 120 [1], table 7.1 AssociatedObjects Shall include the Object ID of the original AuthorisationObject created with the Production Workflow Endpoint (see clause 5.3.3). If the Grounds For Refusal is related to a specific identifier, the Object ID of the LDTaskObject related to that identifier (see clause 5.3.4) shall be included. M ETSI TS 103 120 [1], clause 7.1.4 DocumentName Shall be set to "Grounds For Refusal Decision". M ETSI TS 103 120 [1], clause 7.3.3 DocumentType Shall be set to the relevant value from the EPOCDocumentType dictionary. M Table 5.5.3-2 DocumentBody May contain a binary document containing supporting information regarding the Enforcing Authority's decision. O ETSI TS 103 120 [1], clause 7.3.9 Table 5.5.3-2: EPOCDocumentType Dictionary (partial) Dictionary Owner Dictionary Name ETSI EPOCDocumentType Defined DictionaryEntries Value Meaning NoGroundsForRefusal The Enforcing Authority has determined that there are no grounds for refusal. PartialGroundsForRefusal The Enforcing Authority has determined that there are partial grounds for refusal. FullGroundsForRefusal The Enforcing Authority has determined that there are full grounds for refusal.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.6 Withdraw Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.6.1 Description
|
This endpoint covers an Issuing Authority indicating that an EPOC or EPOC-PR has been withdrawn. This is distinct from indicating that an EPOC-PR is no longer required (see clause 5.10).
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.6.2 Message contents
|
The contents of the Request shall be as per table 5.6.2-1 below. Table 5.6.2-1: HI-1 Objects for the Withdraw Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE Authorisation 1 Indicates that the EPOC is no longer required. Clause 5.6.3 CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.6.3 AuthorisationObject
|
The Request shall contain an UPDATE Request for the AuthorisationObject originally supplied in the Production request (see clause 5.3). The fields in table 5.6.3-1 shall be present in each such UPDATE Request. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 24 Table 5.6.3-1: AuthorisationObject fields in the Withdraw Workflow Endpoint Field Description M/C/O Reference DesiredStatus Shall be set to the AuthorisationDesiredStatus DictionaryEntry "Cancelled". M ETSI TS 103 120 [1], table 7.7 If the operation is successful, then the Service Provider shall consider all LDTaskObjects or LPTaskObjects associated with the Authorisation to be cancelled too.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.7 Preservation Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.7.1 Description
|
This endpoint covers the act of serving a European Preservation Order ("EPOC-PR") using the form defined in the Form 2. It provides the initial set of Authorisation, Document and LDTask objects considered in the object model given in Annex A, which between them contain all the information required by the EPOC.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.7.2 Message contents
|
The contents of the Request shall be as per table 5.7.2-1 below. Table 5.7.2-1: HI-1 Objects for the Preservation Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE AuthorisationObject 1 Provides general authorisation information for the EPOC-PR. Clause 5.7.3 CREATE LPTaskObject 1..n Provides technical instructions on what is information is required to be preserved by the EPOC-PR. Clause 5.7.4 CREATE DocumentObject 1 Carries the signed PDF representation of the EPOC- PR. Annex C CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B Unless otherwise specified, each Object other than the AuthorisationObject shall have an association to the AuthorisationObject given in its AssociatedObjects field.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.7.3 AuthorisationObject
|
The fields given in table 5.7.3-1 shall be present in the CREATE Request for the AuthorisationObject. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 25 Table 5.7.3-1: Authorisation fields in the Preservation Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for the state of the Issuing Authority, as given in the "Issuing State" field in Form 2 Section A. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the Issuing Authority given in Form 2 Section A. M ETSI TS 103 120 [1], table 7.1 AuthorisationReference May be set to any suitable identifier chosen by the RI-API that identifies communications related to a particular EPOC or EPOC-PR. C ETSI TS 103 120 [1], table 7.1 AuthorisationLegalType Shall be set using the appropriate value from the EPOCLegalType dictionary (see table 5.3.3-2). M Table 5.3.3-2 AuthorisationDesiredStatus Shall be set to the AuthorisationDesiredStatus DictionaryEntry "SubmittedToCSP". M ETSI TS 103 120 [1], table 7.7 AuthorisationCSPID Shall be set to the relevant technical identifier for the SP concerned (as determined by either the "service provider concerned" or "addressee" fields of Form 1 Section B). C ETSI TS 103 120 [1], table 7.1 AuthorisationApprovalDetails Shall contain information regarding the Issuing Authority (see table 5.7.3-2). May also contain details of the Validating Authority (see table 5.7.3-5) if specified. M Table 5.7.3-2 and table 5.7.3-5 AuthorisationFlags If Form 2 Section B specifies that the order is issued in an emergency case, the AuthorisationFlag "IsEmergency" DictionaryEntry shall be included (see ETSI TS 103 120 [1], clause 7.2.12). M ETSI TS 103 120 [1], clause 7.2.12 AuthorisationLegalEntity Shall be set to the Service Provider Concerned, if given in Form 2 Section B. Otherwise shall be set to the Addressee given in Form 2 Section B. M ETSI TS 103 120 [1], clause 7.2.15 The Authorisation shall contain an Approval with the fields given in table 5.7.3-2 using the details from Form 1 Section F. Table 5.7.3-2: AuthorisationObject ApprovalDetails for Issuing Authority Field Description M/C/O Reference ApprovalType Shall be set to "IssuingAuthority". M ETSI TS 103 120 [1], table E.1 ApprovalReference Shall be set to the value given as "File number" Form 2 Section F if available. M ETSI TS 103 120 [1], table E.1 ApproverDetails See table 5.7.3-3. M Table 5.7.3-3 ApprovalTimestamp Shall be set to the date of the signature as given in Form 2 Section F. M ETSI TS 103 120 [1], table E.1 ApprovalIsEmergency Shall be set to "True" if Form 2 Section F specifies that the EPOC was issued in a validly established emergency case without prior validation. Shall be set to "False" otherwise. C ETSI TS 103 120 [1], table E.1 Table 5.7.3-3: AuthorisationObject ApproverDetails for Issuing Authority Field Description M/C/O Reference ApproverName Shall be set to the value given as "Name of authority" in Form 2 Section F. M ETSI TS 103 120 [1], table E.2 ApprovalRole Shall be set to "JudgeCourtOrInvestigatingJudge" or "PublicProsecutor" or "OtherCompetentAuthority" as given in Form 2 Section F. M ETSI TS 103 120 [1], table E.2 ApproverContactDetails Shall contain at least one instance of ApproverContactDetails populated according to table 5.7.3-4. A second instance shall be included if Form 2 Section F provides alternate point-of- contact details. M Table 5.7.3-4 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 26 Table 5.7.3-4: AuthorisationObject ApproverContactDetails for Issuing Authority Field Description M/C/O Reference Name Shall be set to the value given as "Name of its representative" in Form 2 Section F, or "Name of the authority/name" if describing the alternative point of contact. M ETSI TS 103 120 [1], clause 7.1.7 Role Shall be set to the value given as "Post held (title/grade)" in Form 2 Section F, or the literal string "Point of Contact" if describing the alternate point of contact. C ETSI TS 103 120 [1], clause 7.1.7 EmailAddress Shall be set to the value given as the relevant "Email Address" field in Form 2 Section F, if present. C ETSI TS 103 120 [1], clause 7.1.7 PhoneNumber Shall be set to the value given as the relevant "Tel No" field in Form 2 Section F, if present. C ETSI TS 103 120 [1], clause 7.1.7 FaxNumber Shall be set to the value given as the relevant "Fax No" field in Form 2 Section F, if present. C ETSI TS 103 120 [1], clause 7.1.7 Address Shall be set to the value given as the relevant "Address" field in Form 2 Section F, if present. C ETSI TS 103 120 [1], clause 7.1.7 Languages Shall include the language identifiers given in the "Language(s) spoken" field in Form 2 Section F if present or omitted if describing the alternate point of contact. C ETSI TS 103 120 [1], clause 7.1.7 If a Validating Authority is specified in Form 2 Section G, the Authorisation shall contain an ApprovalObject with the fields in table 5.7.3-5 using the details from Form 2 Section G. Table 5.7.3-5: AuthorisationObject ApprovalDetails for Validating Authority Field Description M/C/O Reference ApprovalType Shall be set to "ValidatingAuthority". M ETSI TS 103 120 [1], table E.1 ApprovalReference Shall be set to the value given as "File number" Form 2 Section G if available. M ETSI TS 103 120 [1], table E.1. ApproverDetails See table 5.7.3-6. M Table 5.7.3-6 ApprovalTimestamp Shall be set to the date of the signature as given in Form 2 Section G. M ETSI TS 103 120 [1], table E.1 Table 5.7.3-6: AuthorisationObject ApproverDetails for Validating Authority Field Description M/C/O Reference ApproverName Shall be set to the value given as "Name of the authority" in Form 2 Section F. M ETSI TS 103 120 [1], table E.2 ApprovalRole Shall be set to "JudgeCourtOrInvestigatingJudge" or "PublicProsecutor" as given in Form 2 Section F. M ETSI TS 103 120 [1], table E.2 ApproverContactDetails Shall contain an instance of ApproverContactDetails populated in the same way as table 5.7.3-4. M Table 5.7.3-4
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.7.4 LPTask Objects
|
The Preservation request shall contain one LPTask Object for each independent identifier or set of identifiers given in Form 1 Section C. The fields given in table 5.7.4-1 shall be present in each CREATE request for each LPTask Object. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 27 Table 5.7.4-1: LPTaskObject fields in the Preservation Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for the state of the Issuing Authority, as given in the "Issuing State" field in Form 2 Section A. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the Issuing Authority given in Form 2 Section A. M ETSI TS 103 120 [1], table 7.1 AssociatedObjects Shall be set to include the Object ID of the AuthorisationObject (see clause 5.7.3). M ETSI TS 103 120 [1], clause 7.1.4 DesiredStatus Shall be set to LPTaskDesiredStatus value "AwaitingPreservation". M ETSI TS 103 120 [1], table 8.17 RequestDetails Identifies the requested data and the evidence to be produced (Form 2 Sections C and D). This shall be populated as per LDTask RequestDetails (see clause 5.3.4) but using the information Form 2 Sections C and D in place of Form 1 Sections E and F as appropriate. M Table 5.3.4-2 DesiredPreservationExpiration Shall be set to the appropriate expiry time for the preservation according to the Regulation [i.1]. M Table 5.3.4-4
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.8 Subsequent Production Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.8.1 Description
|
This endpoint covers the act of serving a confirmation that a request for production has been issued subsequent to an EPOC-PR, using Form 5. It provides the signed PDF version of Form 5 and updates an existing LPTaskObject to reflect the fact that the data should be preserved until the production request has been completed.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.8.2 Message contents
|
The contents of the Request shall be as per table 5.8.2-1 below. Table 5.8.2-1: HI-1 Objects for the Subsequent Production Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE LPTaskObject 1..n Provides technical instructions on what information is required to be preserved by the EPOC-PR. Clause 5.8.3 CREATE DocumentObject 1 Carries the signed PDF representation of Form 5. Annex C CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.8.3 LPTask Object
|
The Request shall contain an UPDATE Request for each LPTaskObject in the original EPOC-PR (see clause 5.3) for which a subsequent production request has been issued under Form 5. The fields given in table 5.8.3-1 shall be present in each such UPDATE Request. Table 5.8.3-1: LPTaskObject fields in the Subsequent Production Workflow Endpoint Field Description M/C/O Reference DesiredStatus Shall be set to the EPOCPRPreservationStatus DictionaryEntry "SubsequentProductionRequested". M Table 5.8.3-2 and ETSI TS 103 120 [1], table 8.27. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 28 Table 5.8.3-2: EPOCPRPreservationStatus Dictionary Dictionary Owner Dictionary Name ETSI EPOCPRPreservationStatus Defined DictionaryEntries Value Meaning SubsequentProductionRequested Indicates that a subsequent production request has been issued against the data covered by the LPTaskObject, and as such the data should not be removed until the production request has been completed, regardless of the value of the PreservationExpiration field.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.9 Preservation Extension Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.9.1 Description
|
This endpoint covers the act of extending the preservation period of an existing EPOC-PR for an additional 30 days, using Form 6. It provides the signed PDF version of Form 6.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.9.2 Message contents
|
The contents of the Request shall be as per table 5.9.2-1 below. Table 5.9.2-1: HI-1 Objects for the Preservation Extension Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE LPTaskObject 1..n Extends the expiry time of each set of data preserved under the original EPOC-PR by 30 days. Clause 5.9.3 CREATE DocumentObject 1 Carries the signed PDF representation of Form 6. Annex C CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.9.3 LPTask Object
|
The Request shall contain an UPDATE Request for each LPTaskObject in the original EPOC-PR (see clause 5.3) for which a subsequent production request has been issued under Form 5. The fields given in table 5.9.3-1 shall be present in each such UPDATE Request. Table 5.9.3-1: LPTaskObject fields in the Preservation Extension Workflow Endpoint Field Description M/C/O Reference DesiredPreservationExpiration Shall be set to the original PreservationExpiry value plus thirty days as per the Regulation [i.1]. M ETSI TS 103 120 [1], table 8.27.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.10 End Preservation Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.10.1 Description
|
This endpoint covers an Issuing Authority indicating that preservation of data under an EPOC-PR is no longer required.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.10.2 Message contents
|
The contents of the Request shall be as per table 5.10.2-1 below. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 29 Table 5.10.2-1: HI-1 Objects for the Preservation Not Needed Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE LPTaskObject 1..n Indicates that the EPOC-PR is no longer required. Clause 5.10.3 CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.10.3 LPTaskObjects
|
The Request shall contain an UPDATE Request for each of the LPTaskObjects originally supplied in the Preservation request (see clause 5.4). The fields given in table 5.10.3-1 shall be present in each such UPDATE Request. Table 5.10.3-1: LPTaskObjects fields in the Preservation Not Needed Workflow Endpoint Field Description M/C/O Reference DesiredStatus Shall be set to the LDTaskDesiredstatus DictionaryEntry "Cancelled". M ETSI TS 103 120 [1], table 7.7
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.11 Delivery Status Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.11.1 Description
|
This endpoint covers indicating to the Service Provider that a previously-sent message has either been successfully delivered to an end recipient, or that such a delivery has failed.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.11.2 Message Contents
|
The contents of the Request shall be as per table 5.11.2-1 below. Table 5.11.2-1: HI-1 Objects for the Delivery Status Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE DeliveryObject 0..n Indicates that a Delivery Object previously issued by the Service Provider containing the outcome of a production order (see clause 6.3) has either been successfully received by the end recipient, or that delivery has failed. Clause 5.11.3
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.11.3 DeliveryObjects
|
The Request shall contain an UPDATE Request for each of the DeliveryObjects issued by the Service Provider (see clause 6.3) for which the RI-API wishes to provide a delivery notification. The fields given in table 5.11.3-1 shall be present in each UPDATE Request. Table 5.11.3-1: DeliveryObject fields in the Delivery Status Workflow Endpoint Field Description M/C/O Reference DesiredDeliveryStatus Shall contain a value from the DeliveryDesiredStatus Dictionary (see ETSI TS 103 120 [1], table 10.9). The value shall be set to "Received" if the data has been confirmed as being received by the end recipient. The value shall be set to "Error" if the RI-API is aware that the delivery has failed and will not complete. M ETSI TS 103 120 [1], clause 10.2.5 ETSI ETSI TS 104 144 V1.1.1 (2025-06) 30
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.12 Correspondence Workflow Endpoint
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.12.1 Description
|
This endpoint is used by the Issuing Authority or Enforcing Authority to exchange free-text correspondence and associated documentation with the Service Provider, for one of the following purposes: • To notify the Service Provider that Issuing Authority, disagreeing with the reasons given in Form 3, is upholding the EPOC and intends to proceed to court. • To notify the Service Provider that the Issuing Authority wishes to maintain the initial request upon receipt of Form 3, where reasons for non-execution of the request are explained by the Service Provider, or after discussion with the notified Enforcing Authority. • To request additional information from the Service Provider. • To provide additional information to the Service Provider in response to a query. • To communicate a decision of the Enforcing Authority after receiving an objection from the Service Provider. • To notify the Service Provider that the Issuing Authority has initiated enforcement procedures to comply with an EPOC or EPOC-PR. • To communicate a decision of the Enforcing Authority to either uphold or not to recognise an order upon the initiation of enforcement procedures by the Issuing Authority.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.12.2 Message contents
|
The contents of the Request shall be as per table 5.12.2-1 below. Table 5.12.2-1: HI-1 Objects for the Correspondence Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE DocumentObject 1 Document containing the correspondence. Clause 5.10.3 CREATE EPOCAdditionalInfo 0..n May be used for unmapped information. Annex B
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
5.12.3 DocumentObject
|
The Request shall contain at least one CREATE Request for a Document Object that represents the correspondence, which shall contain the fields given in table 5.12.3-1. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 31 Table 5.12.3-1: DocumentObject fields in the Correspondence Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriate ISO country code for source of the correspondence. M ETSI TS 103 120 [1], table 7.1 OwnerIdentifier Shall be set to the appropriate technical identifier for the source of the correspondence. M ETSI TS 103 120 [1], table 7.1 AssociatedObjects Shall include the Object ID of the original AuthorisationObject created with either the Production Workflow Endpoint (see clause 5.3) or Preservation Workflow Endpoint (see clause 5.7). M ETSI TS 103 120 [1], clause 7.1.4 DocumentName Shall be set to "Correspondence". M ETSI TS 103 120 [1], clause 7.3.3 DocumentType Shall be set to the relevant value from the EPOCDocumentType dictionary. M Table 5.12.3-2 DocumentProperties If the DocumentType "RequestAdditionalInformation" is chosen, and a response is required by a particular deadline, then this field shall contain a property with a PropertyType of "ResponseRequiredBy" from the "EPOCDocumentPropertyType" dictionary (see table 5.12.3-3), and a date-time given as a string matching the format required by a QualifiedDateTime (see ETSI TS 103 280 [2], clause 6.4). C Table 5.12.3-3 and ETSI TS 103 120 [1], clause 7.3.8 DocumentBody Contains a binary document containing supporting information, along with relevant metadata according to ETSI TS 103 120 [1], clause 7.3.9. Shall be populated if the chosen DocumentType is "RequestAdditionalInformation" or "ProvideAdditionalInformation", and may be provided in all other circumstances. C ETSI TS 103 120 [1], clause 7.3.9 Table 5.12.3-2: EPOCDocumentType Dictionary (partial) Dictionary Owner Dictionary Name ETSI EPOCDocumentType Defined DictionaryEntries Value Meaning ProceedingToCourt The Issuing Authority, disagreeing with the reasons given in Form 3, is upholding the EPOC and intends to proceed to court. Maintain The Issuing Authority wishes to maintain the initial request upon receipt of Form 3, where reasons for non-execution of the request are explained by the Service Provider, or after discussion with the notified Enforcing Authority. RequestAdditionalInformation Additional information is requested from the Service Provider. ProvideAdditionalInformation Additional information is provided to the Service Provider. EnforcingAuthorityAgreesWithObjection A decision of the Enforcing Authority after receiving an objection from the Service Provider. EnforcingAuthorityDisagreesWithObjection A decision of the Enforcing Authority after receiving an objection from the Service Provider. EnforcementProceduresInitiated The Issuing Authority has initiated enforcement procedures to comply with an EPOC or EPOC-PR. EnforcingAuthorityRecognisesOrder Used to indicate that the Enforcing Authority has decided to recognise an order as part of enforcement procedures and requiring the Service Provider to comply. EnforcingAuthorityDoesNotRecogniseOrder A decision of the Enforcing Authority not to recognise the order upon the initiation of enforcement procedures by the Issuing Authority. Table 5.12.3-3: EPOCDocumentProperties Dictionary Dictionary Owner Dictionary Name ETSI EPOCDocumentProperties Defined DictionaryEntries Value Meaning ResponseRequiredBy A response to the correspondence is required by a specific date/time. ETSI ETSI TS 104 144 V1.1.1 (2025-06) 32
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
6 RI-API Workflow Endpoints
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
6.1 Defined endpoints
|
This Workflow Profile defines the following operations at the RI-API, each of which is exposed as a Workflow Endpoint (see ETSI TS 103 120 [1], clause H.3.1) with a default relative URL path in table 6.1-1. Table 6.1-1: RI-API Workflow Profile Endpoints Relative URL path Description Clause /eevidence/outcome Allows the Service Provider to send the requested data to the respective authority in the issuing State. In case of large file sizes, only the manifest is sent, indicating how to download the requested data outside of the decentralised IT system. Clause 6.3 /eevidence/impossibility Information on the Impossibility of Executing an EPOC / EPOC-PR (Form 3). Clause 6.4 /eevidence/datapreserved Confirmation of Issuance of a Request for Production Following a European Preservation Order (Form 5). Clause 6.5 /eevidence/correspondence Used by the Service Provider to exchange free-text correspondence with the Issuing Authority or Enforcing Authority, along with associated documentation, for any of the following purposes: • To request additional information from the relevant Authority. • To provide information to the relevant Authority. Clause 6.6 /eevidence/confirmwithdrawal Confirmation of Withdrawal. Clause 6.7 /eevidence/enforcingauthorityId Allows the Service Provider to retrieve the identifier of the Enforcing Authority it is associated with. Clause 6.8 The URL path is specified relative to the API base URL. Usage of the relative URL path is the default for the endpoint but is not required; different URL paths may be provided by mutual agreement.
|
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
6.2 Common procedures and constraints
| |
fa996e7c0d58726f9bbde1165f5aaff3
|
104 144
|
6.2.1 Message exchange
|
Each invocation of a RI-API Workflow Endpoint shall consist of one HI-1 message exchange as shown in figure 6.2.1-1 below. HI-1 Request Message (contains HI-1 Objects) Service Provider RI-API HI-1 Response Message (technical acknowledgement) Figure 6.2.1-1: Message exchange for RI-API Workflow Endpoint
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.