hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 / peri... |
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 le... |
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 appl... |
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 ... |
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 sta... |
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-... |
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 ... |
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 change... |
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 n... |
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 stat... |
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-CLUSTE... |
2c5adb759be990a10178f42b16bfb2d5 | 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 T... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 2 References | |
2c5adb759be990a10178f42b16bfb2d5 | 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 a... |
2c5adb759be990a10178f42b16bfb2d5 | 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 i... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 3 Definition of terms, symbols and abbreviations. | |
2c5adb759be990a10178f42b16bfb2d5 | 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... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 3.2 Symbols | Void. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CDB Court DataBase DIS Distributed IT System EPOC European Production Order Certificate EPOC-PR European Preservation Order Certificate GPRS General Packet Radio Service HTTP Hypertext Transfer Protocol HT... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 4 Reference Model | |
2c5adb759be990a10178f42b16bfb2d5 | 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. 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 In... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 4.2 API definition | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 4.2.1 Approach | The present document defines an API for exchanging e-Evidence-related information between an WISP 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... |
2c5adb759be990a10178f42b16bfb2d5 | 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. These business workflows are listed in the Forge documentation for the present document in the "/workflows" directory. They provide the detailed message exchanges b... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 4.2.3 Protocol definition | Each Workflow Endpoint defines a message exchange between the WISP or Service Provider, as shown in figure 4.2.3-1. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 12 HI-1 Request Message (contains HI-1 Objects) WISP Service Provider HI-1 Response Message (technical acknowledgement) Figure 4.2.3-1: Message exchange example (for ... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5 SP Workflow Endpoints | |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 13 Table 5.1-1: SP Workflow Endpoints Relative URL path Des... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.2 Common procedures and constraints | |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 14 HI-1 Request Message (contains HI-1 Objects) WISP Service Provider HI-1 Response Message (technical acknowledgement) Figure 5.2.1-1: Message exchange for SP Workflo... |
2c5adb759be990a10178f42b16bfb2d5 | 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 original source of the message (e.g. Issuin... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.3 Production Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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. |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 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... |
2c5adb759be990a10178f42b16bfb2d5 | 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... |
2c5adb759be990a10178f42b16bfb2d5 | 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. ETSI ETSI TS 104 144 V1.3.1 (2026-03... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.3.5 Encryption Objects | The production request may create encryption objects, in order to request encryption of the outcome data. The encryption object is described in ETSI TS 103 120 [1], clause 7.9. The Encryption object shall exclusively use X.509 certificates. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.4 New Deadline Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.4.1 Description | This endpoint covers the act of setting a new deadline for compliance with an EPOC. |
2c5adb759be990a10178f42b16bfb2d5 | 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 ... |
2c5adb759be990a10178f42b16bfb2d5 | 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 Referen... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5 Grounds For Refusal Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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 after the Enforcing Authority having received a Form 3 from the Service Provider. |
2c5adb759be990a10178f42b16bfb2d5 | 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 EPOCNoGroundsFo rRefusal 0..1 Shall be included if the Enforcing Authority has no grounds for refusal. Clause 5.5.4 CREATE ... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5.3 Document Object | The request may contain additional attachments, as per clause B.3. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5.4 EPOCNoGroundsForRefusal Object | If the Enforcing Authority has no grounds for refusal or special conditions have been applied to the Issuing Authority, the Request shall contain a CREATE Request for a EPOCNoGroundsForRefusal object as described in table 5.5.4-1. Table 5.5.4-1: RefusalInformation Field Description M/C/O Reference SpecialConditionsAppl... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5.5 EPOCFullRefusalInformation Object | If the Enforcing Authority has grounds for a full refusal, the Request shall contain a CREATE Request for a EPOCFullRefusal object as described in table 5.5.5-1. Table 5.5.5-1: EPOCFullRefusal Field Description M/C/O Reference FullRefusalInformation Provides information on the grounds for full refusal. M Table 5.5.5-2 ... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5.6 EPOCPartialRefusalInformation Object | If the Enforcing Authority is raising partial grounds for refusal, the Request shall contain a CREATE Request for a EPOCPartialRefusalInformation object as described in table 5.5.6-1 for each identifier against which grounds for refusal are being raised. Each EPOCPartialRefusalInformation object shall contain a referen... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.5.7 LDTask Objects | The Request shall contain an UPDATE for each LDTaskObject for which an EPOCPartialRefusalInformation has been created (see clause 5.5.6). Only the fields given in table 5.5.7-1 shall be present in each UPDATE request for each LDTask Object. Table 5.5.7-1:LDTaskObject fields in the Grounds For Refusal Endpoint Field Des... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.6 Withdraw Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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). |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.6.2 Message contents | The contents of the Request shall be as per table 5.6.2-1 below. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 29 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 EPOCAdditi... |
2c5adb759be990a10178f42b16bfb2d5 | 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. Table 5.6.3-1: AuthorisationObject fields in the Withdraw Workflow Endpoint Field Description M/C/O Reference ... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.7 Preservation Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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. |
2c5adb759be990a10178f42b16bfb2d5 | 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 t... |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 30 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 ... |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 32 Table 5.7.4-1: LPTaskObject fields in the P... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.8 Subsequent Production Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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 compl... |
2c5adb759be990a10178f42b16bfb2d5 | 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 ... |
2c5adb759be990a10178f42b16bfb2d5 | 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 Producti... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.9 Preservation Extension Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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. |
2c5adb759be990a10178f42b16bfb2d5 | 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.... |
2c5adb759be990a10178f42b16bfb2d5 | 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 Extens... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.10 End Preservation Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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. |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 34 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... |
2c5adb759be990a10178f42b16bfb2d5 | 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 Descrip... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.11 Delivery Status Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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. |
2c5adb759be990a10178f42b16bfb2d5 | 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 pr... |
2c5adb759be990a10178f42b16bfb2d5 | 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 WISP 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 Stat... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.12 Correspondence Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 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 EP... |
2c5adb759be990a10178f42b16bfb2d5 | 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... |
2c5adb759be990a10178f42b16bfb2d5 | 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.3.1 (2026-03) 36 Table 5.12.3-1: DocumentObject fields in the Correspondence Workflow Endpoint Field Description M/C/O Reference... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.13 NonExecution Status Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.13.1 Description | This endpoint covers indicating to the Service Provider that a previously-sent NonExecution message has either been successfully transferred to an end recipient, or that such a transmission has failed. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.13.2 Message Contents | The contents of the Request shall be as per table 5.13.2-1 below. Table 5.13.2-1: HI-1 Objects for the NonExecution Status Workflow Endpoint Verb HI-1 Object Cardinality Description Reference UPDATE DocumentObject 1 Indicates that a Document Object previously issued by the Service Provider containing the nonExecution o... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 5.13.3 DocumentObject | The Request shall contain an UPDATE Request for the DocumentObject issued by the Service Provider (see clause 6.4). The fields given in table 5.13.3-1 shall be present in each UPDATE Request. Table 5.13.3-1: DocumentObject fields in the NonExecution Status Workflow Endpoint Field Description M/C/O Reference DesiredDocu... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6 WISP Workflow Endpoints | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.1 Defined endpoints | This Workflow Profile defines the following operations at the WISP, 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. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 38 Table 6.1-1: WISP Workflow Profile Endpoints Relative URL path Description... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.2 Common procedures and constraints | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.2.1 Message exchange | Each invocation of a WISP 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 WISP HI-1 Response Message (technical acknowledgement) Figure 6.2.1-1: Message exchange for WISP Workflow Endpoint |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.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 6.2.2-1 below. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 39 Table 6.2.2-1: HI-1 Message Header Field Description M/C/O Reference SenderIdentifier Shall be set to a value which identifies the Service Provid... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.3 Outcome Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.3.1 Description | This endpoint covers the Service Provider sending the requested data back to the nominated recipient. In case of large file sizes, only a download URL and associated metadata is sent, indicating how to download the requested data outside of the decentralized IT system. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.3.2 Message contents | The contents of the Request shall be as per table 6.3.2-1 below. Table 6.3.2-1: HI-1 Objects for the Outcome Workflow Endpoint Verb HI-1 Object Cardinality Description Reference DELIVER DeliveryObject 1..n Provides the outcome of the request. Clause 6.3.3 CREATE NotificationObject 0..n Shall be present to indicate when... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.3.3 DeliveryObject | The Request shall contain a DELIVER Request for one or more DeliveryObjects containing the outcome of the request. The data may be provided as a single DeliveryObject (i.e. as a single file) or as multiple DeliveryObjects (i.e. as multiple independent files) in each invocation of the endpoint, as determined by the Serv... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.3.4 NotificationObject | The Request shall contain a CREATE Request for a NotificationObject for each LDTask for which all outcome data has been provided by the Service Provider. The fields in table 6.3.4-1 shall be present in the NotificationObject. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 41 Table 6.3.4-1: NotificationObject fields in Outcome W... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.4 Non Execution Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.4.1 Description | This endpoint covers the Service Provider notifying the Issuing Authority information on the impossibility of executing an EPOC or EPOC-PR (Form 3). |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.4.2 Message contents | The contents of the Request shall be as per table 6.4.2-1 below. Table 6.4.2-1: HI-1 Objects for the Non Execution Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE NotificationObject 1..n If the non-execution relates to an entire EPOC or EPOC-PR, a NotificationObject is provided that indicate... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.4.3 NotificationObject | The Request shall contain a CREATE Request for a NotificationObject that indicates that the state of the Authorisation has changed to reflect the de-facto impossibility. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 42 The fields given in table 6.4.3-1 shall be present in the NotificationObject. Table 6.4.3-1: NotificationObje... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.4.4 Form3Information | The Request shall contain a CREATE Request for one or more Form3Information objects as described in table 6.4.2-1. Each Form3Information shall contain a reference to the relevant Authorisation, LDTaskObject or LPTaskObject in the AssociatedObjects field (see ETSI TS 103 120 [1] clause 7.1.4). Table 6.4.4-1: Form3Inform... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.