hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.6 Test assertions for Identity child element of RecipientDetails element
|
REMS/BS/EVIDENCE/TA_41 TA Id REMS/BS/EVIDENCE/TA_41 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline h) The SenderDetails/Sender's Identity attributes element shall be set as follows, according to eIDAS TS SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Target Conformance to ERDS Evidence in REM Baseline Predicate The Identity child element of SenderDetails element meets the requirements specified in eIDAS TS SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 104
|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.7 Test assertions for Identity child element of SenderDetails element
|
REMS/BS/EVIDENCE/TA_42 TA Id REMS/BS/EVIDENCE/TA_42 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline i) The RecipientDetails/Recipient's Identity attributes element shall be set as follows, according to IDAS Technical Specifications SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Target Conformance to ERDS Evidence in REM Baseline Predicate The Identity child element of RecipientDetails element meets the requirements specified in eIDAS TS SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence
|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.8 Test assertions for UserContentInfo element
|
REMS/BS/EVIDENCE/TA_43 TA Id REMS/BS/EVIDENCE/TA_43 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline l) The value of the element "AppLayerIdentifier" shall be set to the original message's Message-ID header taking care of the necessary transcoding of the not admitted characters in the values of XML elements (e.g. the '<' and '>' characters, systematically present in Message-ID headers, are translated in '< ' and '>' entities) Target Conformance to ERDS Evidence in REM Baseline Predicate The value of AppLayerIdentifier child element of UserContentInfo element shall be set to the original message's Message-ID header taking care of the necessary transcoding of the not admitted characters in the values of XML elements Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence
|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.9 Test assertions for MessageIdentifier element
|
REMS/BS/EVIDENCE/TA_44 TA Id REMS/BS/EVIDENCE/TA_44 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline k) The MessageIdentifier element shall be a UID generated according to IETF RFC 5322 [4], section 3.6.4 Target Conformance to ERDS Evidence in REM Baseline Predicate The value of MessageIdentifier element is a UID generated according to IETF RFC 5322 [4], section 3.6.4 Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence 12.6.5.10 Test assertions for AssuranceLevelsDetails child element of SenderDetails element REMS/BS/EVIDENCE/TA_45 TA Id REMS/BS/EVIDENCE/TA_45 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline p): • The "AssuranceLevel" element value shall be set to the URI: http://eidas.europa.eu/LoA/substantial • The "PolicyID" element value shall be set to a URI referencing the assurance levels definitions Target Conformance to ERDS Evidence in REM Baseline Predicate The value of AssuranceLevel child element of AssuranceLevelsDetails child element of SenderDetails element is set to "http://eidas.europa.eu/LoA/substantial" Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 105 REMS/BS/EVIDENCE/TA_46 TA Id REMS/BS/EVIDENCE/TA_46 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline p) • The "AssuranceLevel" element value shall be set to the URI: http://eidas.europa.eu/LoA/substantial • The "PolicyID" element value shall be set to a URI referencing the assurance levels definitions Target Conformance to ERDS Evidence in REM Baseline Predicate The value of PolicyID child element of AssuranceLevelsDetails child element of SenderDetails element is set to a URI that references the definitions of the assurance levels Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence
|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.11 Test assertions for ExternalERDSDetails element
|
REMS/BS/EVIDENCE/TA_47 TA Id REMS/BS/EVIDENCE/TA_47 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline q) The ExternalERDSDetails element (..) shall be set as follows, according to eIDAS TS SAML Attribute Profile [17], clauses 2.3.2 and 2.3.4 (…) where The value "LEGAL NAME OF THE SERVICE PROVIDER" shall be set to the same value used in ERDSGoverningBody ERDSMetadata element of the "other party" of the transaction in respect to the issuer Target Conformance to ERDS Evidence in REM Baseline Predicate The content of ExternalERDSDetails element is set according to eIDAS TS SAML Attribute Profile [17], clauses 2.3.2 and 2.3.4 Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence REMS/BS/EVIDENCE/TA_48 TA Id REMS/BS/EVIDENCE/TA_48 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline q) The ExternalERDSDetails element (..)shall be set as follows, according to eIDAS TS SAML Attribute Profile [17], clauses 2.3.2 and 2.3.4 (…) where The value "LEGAL NAME OF THE SERVICE PROVIDER" shall be set to the same value used in ERDSGoverningBody ERDSMetadata element of the "other party" of the transaction in respect to the issuer Target Conformance to ERDS Evidence in REM Baseline Predicate The value of the element saml:AttributeValue, with attribute xsi:type set to "elp:LegalNameType" is set to the same value as the element affected by test assertion REMS/BS/CAPMNG/XSD/TA_25 of the present document Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence
|
4f9d8cab416c99e490f57fde6231c491
|
119 534-1
|
12.6.5.12 Test assertions for ds:Signature element
|
The test assertions defined in ETSI TS 119 134-4 [13] shall apply. In addition, the tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/ERDSEVIDSIG/TA_04 The present document 8.2 Finally, the following test assertion shall also apply. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 106 REMS/BS/EVIDENCE/TA_49 TA Id REMS/BS/EVIDENCE/TA_49 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline m), clause C.4.3, and clause C.4.4 The Signature element shall include digital signature and time-stamp token as defined in clauses C.4.3 and C.4.4 Target Conformance to ERDS Evidence in REM Baseline Predicate The ds:Signature contains a XAdES-B-T signature Prescription level Mandatory Tag Conformance, REM Baseline, REMS, REMSP, ERDS Evidence ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 107 Annex A (informative): Change History Date Version Information about changes April 2023 1.1.2 First incomplete set of test assertions for REM Baselines October 2023 1.1.3 Complete set of test assertions for REM Baseline (clause 12). Changes implemented resulting from comments to version v1.1.2. October 2023 1.1.4 Changes implemented resulting from some comments to version 1.1.2 not implemented in v1.1.3. November 2023 1.1.5 Several editorial changes: suppression of hanging paragraphs, completion of references, fixing one wrong reference from reference to 5.7.1 to a reference to 5.8 ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 108 History Document history V1.1.1 February 2019 Publication V1.2.1 December 2023 Publication
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
1 Scope
|
The present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery Services (ERD services or ERDS hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 522-1 [1] where sender and all the entities at receiving side are subscribed to the same ERDS. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and no intermediate ERDS is required for relaying ERD messages between them. - Environments that correspond to the extended model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and intermediate ERDSs are required for relaying ERD messages between them. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
2 References
| |
8983622e5d417335095cba14cb702b60
|
119 524-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 at https://docbox.etsi.org/Reference/. 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 EN 319 522-1: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 1: Framework and Architecture". [2] ETSI EN 319 522-2: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 2: Semantic contents". [3] ETSI EN 319 522-3: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 3: Formats". [4] ETSI EN 319 522-4-1: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 1: Message delivery bindings". [5] ETSI EN 319 522-4-2: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 2: Evidence and identification bindings". [6] ETSI EN 319 522-4-3: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 3: Capability/requirements bindings". [7] ETSI EN 319 532-3: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 3: Formats". [8] OASIS Standard (January 2013): "AS4 Profile of ebMS 3.0 Version 1.0". ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 7
|
8983622e5d417335095cba14cb702b60
|
119 524-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 are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 119 524-1: "Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Electronic Registered Delivery Services; Part 1: Testing conformance". [i.2] OASIS Standard (October 2007): "ebXML Messaging Services Version 3.0: Part 1, Core Features".
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
3 Definition of terms, symbols and abbreviations
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI EN 319 522-1 [1] apply.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
3.2 Symbols
|
Void.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACC_REJ_EXP ACCeptance REJection EXPiry AS4 Applicability Statement 4 CONS_ACC CONSignment ACCeptance CONS_NOT CONSignment NOTification CONS_NOT_FAIL CONSignment NOTification FAILure CONS_REJ CONSignment REJection CONT_AC_TRACK CONTent ACcess TRACKing CONT_CONS CONTent CONSignment CONT_CONS_FAIL CONTent CONSignment FAILure CONT_HAND CONTent HANDover CONT_HAND_FAIL CONTent HANDover FAILure ebMS ebXML Messaging Services ebXML electronic business using eXtensible Markup Language ERD Electronic Registered Delivery ERDS Electronic Registered Delivery Service EV_SET Evidence - SET IERDS Intermediate Electronic Registered Delivery Service NOT_AC_TRACK NOTification ACcess TRACKing NOT_DEL NOTification DELivered NOT_F_ACC NOTification For ACCceptance NOT_F_ACC_FAIL NOTification For ACCceptance FAIL OASIS Organization for the Advancement of Structured Information Standards REC_F_NERDS RECeived From Non ERDS REL_ACC RELay ACCeptance REL_FAIL RELay FAILure ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 8 REL_REJ RELay REJection REL_T_NERDS RELay To Non ERDS REL_T_NERDS_FAIL RELay To Non ERDS FAILure REM Registered Electronic Mail REMS Registered Electronic Mail Service RERDS Recipient's Electronic Registered Delivery Service SCN_ID Scenario IDentifier SERDS Sender's Electronic Registered Delivery Service SUB_ACC SUBmission ACCeptance SUB_REJ SUBmission REJection URI Universal Resource Identifier XML eXtensible Mark-up Language
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
4 Technical approach
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
4.1 Components of test cases and their identifiers
|
As it has been mentioned before the present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery (ERD hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite. The present document follows a layered approach for building the definition of the test cases in the test suite, which can be summarized as follows: 1) Clause 5 defines a number of parameterized scenarios. A scenario consists of a number of entities, namely: sender, one or more ERDSs, and the entities at receiving side (one or more recipients and/or one or more recipients' delegates), which exchange different ERD messages with time. Each scenario corresponds to one of the three models presented in ETSI EN 319 522-1 [1]. This clause presents a template for defining one scenario, in a way that resembles to some templates used for defining use cases scenarios in software engineering. This template: - Includes the enumeration of the original message and all the ERD messages exchanged by the participating entities. This list of exchanged ERD messages is one of the parameters of the scenario. - Also includes a list of ERDS evidence sets, which, in the scenario, are incorporated in some ERD messages. One scenario may be used for defining several test cases depending on: - The specific components of each exchanged ERD message (suppressing or adding an optional metadata component, or changing the value of a certain metadata component results in a different ERD message and consequently a different test case). - The entities at receiving part (for instance, changing one recipient by one recipient's delegate, or two recipients and one recipient's delegate results in a different the test case). - A named set of additional requirements (for instance details of the original message, like whether it contains or not attachments, is signed, is encrypted, etc.). This means that one test case corresponds to one scenario where all the exchanged ERD messages have been completely defined in terms of their components, all the participating entities have been established, and all the additional requirements have also been defined. Taking the functional notation this can be expressed as follows: TestCase#i = Scenario_id(,<Receiving side identifier>, <ERD message 1 details>, <ERD message 2 details>, …, <ERD message N details>, <additional requirements set identifier) ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 9 Where: - <Receiving side identifier> is the identifier assigned to a certain set of entities at receiving side; - <message identifier I> is the identifier of a specific instantiation of the aforementioned message, defined in clauses 6.3, 6.4, and 6.5 These clauses define specific instantiations of ERD payloads, ERD receipts and ERD dispatches respectively. - <additional requirements set identifier> is the identifier of a named set of additional requirements. Clause 7.2 defines a number of these named sets. 2) Clauses 6.3, 6.4, and 6.5 define specific instantiations of ERD payloads, ERD receipts and ERD dispatches respectively. Each type of ERD message is composed by several components, with their metadata components and payloads as specified in ETSI EN 319 522-4-1 [4] and ETSI EN 319 522-4-2 [5]. The present document defines a number of combinations of metadata components in clauses 6.2.2 and 6.2.3, and assigns to each one a unique identifier. This allows to use again the functional notation, and define one instantiation of a certain type of ERD message as follows: ERD message instance = Sequence(Metadata(<AS4 profiled metadata combination details>, <payload for ERDS relay metadata combination details>) <payload for User Content>* <payload for ERDS Evidence>*) Where '*' stands for 0 or more occurrences of the payload. NOTE: The payloads for user content and for ERDS evidence can be present at certain types of ERD messages but are forbidden in other types. 3) Clauses 6.2.2 and 6.2.3 define named combinations of metadata components defined in OASIS: "AS4 Profile of ebMS 3.0 Version 1.0" [8] and profiled in ETSI EN 319 522-4-1 [4] and ETSI EN 319 522-4-2 [5], and the relay metadata components defined in ETSI EN 319 522-3 [3] respectively. Each clause define different instances of the aforementioned components and assigns them unique identifiers that are used for defining specific instances of the different ERD messages as shown above. Once this level is reached, the specific test case is fully defined as: a scenario where fully defined, ERD messages are exchanged between a specific set participating entities, and where a specific set of additional requirements are imposed.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
4.2 Adding new test cases to the test suite
|
The strategy followed for building the definitions of the test cases makes it easy to expand the test suite by incorporation of new test cases. For defining a new test case the following steps are required: 1) Identify the set of receiving entities. If none of the predefined set of entities at the receiving side is the one required, assign a name to this set (<RECEIVING_ENTITIES >) and incorporate it to the repertoire of named sets as specified in clause 7.3). The sender is always present by default. 2) Define the ERDSs that will participate in the test case. 3) If the set of participating ERDSs is not equal to none of the scenarios already identified in the present document, the new scenario will require to be defined in a new template. 4) Identify the sequence of actions performed by each actor and their order of occurrence and assign a new unique identifier (<SCN_ID >) to the scenario. 5) Identify all the ERD messages generated by the actors as they go through the sequence of actions. For each message: a) Identify its ebMS payloads, e.g. the parts of the user content or XML document with relay meta-data. b) Check if the combinations of metadata components have already been defined in the present document. If not, add the required combination of metadata components to the repertoire of named combinations to the corresponding clause (clause 6.2.2 or 6.2.3). c) List all the ERD messages exchanged as parameters of the scenario. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 10 d) Identify the ERDS evidence format and the set of ERDS evidence for each ERD message including them and add the names of the ERDS evidence sets to the Var section of the template. 6) Identify and define any other additional requirement for completely define the test case. If the set of requirements is different than all the sets already define, assign a name to it (<ADD_REQ_COMB>) and add it to the repertoire of named sets of additional requirements in Table 12 (clause 7.2).
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5 Scenarios
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.1 Introduction
|
The present clause defines a number of selected scenarios that will be used in clause 8. Clause 5.3 defines scenarios where sender and recipient(s) are subscribed to the same ERDS (black-box model described in ETSI EN 319 522-1 [1]). Clause 5.4 defines scenarios where the sender and the recipient(s) are subscribed to different ERDSs and there are not intermediate ERDSs between them (4-corner model described in ETSI EN 319 522-1 [1]). Clause 5.5 defines scenarios where sender is subscribed to a ERDS and the recipient(s) is(are) not subscribed to the same ERDS and there are one or more intermediate ERDSs (extended model described in ETSI EN 319 522-1 [1]). Figure 1 of clause 4 of ETSI EN 319 522-2 [2] shows three structures being exchanged between ERD-UAs and ERDSs, namely: 1) The structure {submission metadata, user content}, which receives the name of original message in Table 1 of clause 4 of ETSI EN 319 522-2 [2]. 2) The structure {ERDS handover metadata, ERDS evidence} for allowing access to ERDS evidences to users. 3) The structure {ERDS handover metadata, user content, ERDS evidence} for allowing the R-ERDS the submission of the user content (and optionally ERDS evidences) to the recipient. Because of that the following decisions have been adopted for building the scenarios: 1) Neither S-ERDS nor R-ERDS will submit {ERDS handover metadata, ERDS evidence} structures to their users, except when the ERDS evidence is an evidence of some kind of relevant rejection by the ERDS (see the first scenario, for instance). Identical scenarios including the submission of such structures can be easily defined and used in interoperability test events. 2) The scenarios will show the R-ERDS submitting {ERDS handover metadata, user content, ERDS evidence} or {ERDS handover metadata, user content} structures to the receiving side. 3) The acronym hndvMet is used for ERDS handover metadata. Table 1 shows the template for defining one scenario. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 11 Table 1: Template for the tabular definition of one scenario Scenario id: <SCN_ID> Purpose Parameter: <ERDS_receipt>_WITH_XML_SUB_REJ <Parameter 1 that helps to fully the scenario. Their number depends on the specific scenario> Var SET_EV#1 = {…, …} Named sets of ERDS evidence used in the definition of the scenario. Parameter: <Parameter 2> Var SET_EV#2 = {… …} Parameter: <Parameter N> Var SET_EV#N = {… …} Sequence of actions <SEQUENCE OF ACTIONS. THERE IS ONE COLUMN PER PARTICIPATING ACTOR> # Sender ERDS Receiving side The sequence is composed of a number of numerated steps, when the actors perform certain actions as shown below. Some frequent actions: send original message, accept submission, reject submission, consign, generate one ERDS evidence, generate one ERD message, etc. 1 Sender sends original message 2 Rejects submission. Generates XML_SUB_REJ ERDS evidence 3 Generates <ERDS_receipt>_WITH_XML_SUB_REJ 4 Sends <ERDS_receipt>_WITH_XML_SUB_REJ 5 Receives <ERDS_receipt>_WITH_XML_SUB_RE J Each scenario is assigned a unique identifier <SCN_ID>. The reasons why the scenario has been defined are shown in column "Purpose". The definition of each scenario requires that parties exchange a number of ERD messages, which appear listed as parameters in the rows immediately below the headers row. Its number depends on the specific scenario. Below the list of parameters, the table shows a sequence of actions performed by different involved entities, which results in that a set of ERD messages is generated and exchanged. The definition of each scenario also can use a number of named ERDS evidence sets, which are listed in cells started with Var. Each ERDS evidence set is given a name EV_SET#<i>, being <i> a non-negative integer number. The involved entities are sender (or sender's delegate, the scenario definition does not make any distinction between them), one or more ERDSs, and the entities at the receiving side (for the same scenario there may be different sets of entities, for instance one recipient, one recipient's delegate, one or more recipients, or one or more recipients and one or more recipients' delegates). Each step is assigned a positive integer number. The actions performed include: submission of messages, generation of ERD messages, generation of ERDS evidence, acceptance of ERD messages, rejection of ERD messages, consignment of ERD messages, retrieval of ERD messages by entities at receiving side, failures, etc.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.2 Abbreviations used in tables defining scenarios
|
This clause shows some abbreviations (which have already been anticipated in clause 3.3) used in the tables that define the scenarios. Table 2 shows the abbreviations used for the different ERDS evidence. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 12 Table 2: ERDS evidence abbreviations ERDS Evidence name ERDS Evidence abbreviation SubmissionAcceptance SUB_ACC SubmissionRejection SUB_REJ RelayAcceptance REL_ACC RelayRejection REL_REJ RelayFailure REL_FAIL NotificationForAcceptance NOT_F_ACC NotificationForAcceptanceFailure NOT_F_ACC_FAIL ConsignmentAcceptance CONS_ACC ConsignmentRejection CONS_REJ AcceptanceRejectionExpiry ACC_REJ_EXP ContentConsignment CONT_CONS ContentConsignmentFailure CONT_CONS_FAIL ConsignmentNotification CONS_NOT ConsignmentNotificationFailure CONS_NOT_FAIL ContentHandover CONT_HAND ContentHandoverFailure CONT_HAND_FAIL RelayToNonERDS REL_T_NERDS RelayToNonERDSFailure REL_T_NERDS_FAIL ReceivedFromNonERDS REC_F_NERDS NotificationDelivered NOT_DEL NotificationAccessTracking NOT_AC_TRACK ContentAccessTracking CONT_AC_TRACK ETSI EN 319 522-1 [1] specify a XML format for ERDS evidence, but also allows that ERDS Evidences are signed PDF documents. The notation defined in the present document makes it clear that all the test cases are defined for XML ERDS Evidence using the XML prefix for the ERDS evidence abbreviations. EXAMPLE: The abbreviation for the XML SubmissionAcceptance ERDS evidence will be XML_SUB_ACC. NOTE: In case some format for PDF ERDS Evidence is defined and ERDS providers need to test interoperability with them, it is always possible to replace the test cases defined in the present document by identical test cases where PDF ERDS Evidences are generated and exchanged instead XML ERDS Evidences. The tables defining the Scenarios use the following abbreviations for the different participating ERDSs: • SERDS stands for the ERDS serving the sender, in the scenarios where it is different than the ERDS serving the entities at receiving side. • RERDS stands for the ERDS serving the entities at receiving side, in the scenarios where it is different than the ERDS serving the sender. • IERDS stands for a ERDS that does not directly serves neither to the sender nor to the recipient(s)/recipient's delegate, but instead is an intermediate ERDS that relies ERD messages from SERDS to RERDS and from RERDS to SERDS.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.3 Black-box model scenarios
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.3.1 Introduction
|
The present clause defines scenarios where the sender and the entities at the receiving side are subscribed to the same ERDS and consequently the user content is not relayed between different ERDSs. Clause 5.3.2 defines scenarios where the ERDS operates in Store and Forward style. Clause 5.3.3 defines scenarios where the ERDS operates in Store and Notify style. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 13
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.3.2 Scenarios without notification for acceptance
|
Table 3 defines a number of scenarios for the case where sender and the entities at the receiving side are subscribed to the same ERDS and the ERDS does not send notification for acceptance to the entities at the receiving side. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 14 Table 3: Scenarios for intra-ERDS without notifications for acceptance (1/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#1 Purpose Parameter: {hndvMet,XML_SUB_REJ} The simplest negative scenario: Where the ERDS rejects the original message submitted by the sender and sends back a structure {ERDS handover metadata, XML_SUB_REJ} containing SubmissionRejection ERDS evidence. Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Rejects submission. Generates XML_SUB_REJ ERDS evidence 3 Sends {hndvMet, XML_SUB_REJ} structure to the sender 4 Receives {hndvMet, XML_SUB_REJ} structure Table 3a: Scenarios for intra-ERDS without notifications for acceptance (2/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#2 Purpose Parameter: {hndvMet, user content} The simplest positive scenario: Where the ERDS accepts the original message, then it generates and consigns the structure {Including handover metadata and user content} to N entities on the receiving side. Lastly, ERDS generates and stores the ContentConsignment ERDS evidence. Parameter: XML_SUB_ACC Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content} structure 5 Consigns {hndvMet, user content} structure to the N entities at the receiving side 6 {hndvMet, user content} structure correctly consigned to the N entities at the receiving side 7 Generates and stores XML_CONT_CONS ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 15 Table 3b: Scenarios for intra-ERDS without notifications for acceptance (3/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#3 Purpose Parameter: {hndvMet, user content} The positive scenario: Where the ERDS accepts the original message, then it generates and consigns the structure {Including handover metadata and user content} to N entities on the receiving side. In the next step, ERDS generates the ContentConsignment ERDS evidence. After the successful retrieval of the ERD payload on the receiving side, ERDS generates and stores ContentHandover ERDS evidence for the N handovers. Parameter: XML_SUB_ACC Parameter: XML_CONT_CONS Parameter: XML_CONT_HAND Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content} structure 5 Consigns {hndvMet, user content} structure to the N entities at the receiving side 6 Generates and stores XML_CONT_CONS ERDS evidence {hndvMet, user content} structure correctly consigned to N entities at receiving side 7 All the entities retrieve the ERD dispatch 8 Generates and stores XML_CONT_HAND ERDS evidence for the N handover and stores N handovers of {hndvMet, user content} structure succeed ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 16 Table 3c: Scenarios for intra-ERDS without notifications for acceptance (4/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#4 Purpose Parameter: {hndvMet, user content} A negative scenario of ERDS_BB_NO_NOT_F_ACC#3 Where one of the entities on the receiving side fails to retrieve the consignment. Now, ERDS generates and stores two evidences; ContentHandover ERDS evidence for the N -1 entities and ContentHandoverFailure ERDS evidence for one entity. Parameter: XML_SUB_ACC Parameter: XML_CONT_HAND Parameter: XML_CONT_HAND_FAIL Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates {hndvMet, user content}structure 4 Consigns {hndvMet, user content} structure to the N entities at the receiving side 5 Generates and stores XML_CONT_CONS ERDS evidence {hndvMet, user content} structure successfully consigned to N entities at the receiving side 6 Entities try to retrieve the ERD dispatch, but one fails 7 Generates one XML_CONT_HAND ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL ERDS evidence for one entity and stores them N-1 handovers of {hndvMet, user content} structure succeed. One fails ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 17 Table 3d: Scenarios for intra-ERDS without notifications for acceptance (5/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#5 Purpose Parameter: {hndvMet, user content, XML_SUB_ACC} A positive scenario of ERDS_BB_NO_NOT_F_ACC#2: Where ERDS generates and consigns the structure {including consignment metadata, user content, and SubmissionAcceptance evidence} to N entities on the receiving side and generates the ContentConsignment ERDS evidence. Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends the original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content, XML_SUB_ACC} structure 5 Consigns {hndvMet, user content, XML_SUB_ACC} structure to the receiving side 6 Generates and stores XML_CONT_CONS ERDS evidence {hndvMet, user content, XML_SUB_ACC} structure successfully consigned to the N entities at the receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 18 Table 3e: Scenarios for intra-ERDS without notifications for acceptance (6/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#6 Purpose Parameter: {hndvMet, user content} A positive scenario of ERDS_BB_NO_NOT_F_ACC#2: Now the ERDS generates and sends a notification of consignment to the receiving side. When the notification of consignment is received by N entities at the receiving side, ERDS generates and stores ConsignmentNotification ERDS evidence. Parameter: XML_SUB_ACC Parameter: {NotificationOfConsignment} Parameter: XML_CONS_NOT Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends the original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates {hndvMet, user content} structure 4 5 Consigns {hndvMet, user content} structure to receiving side 6 {hndvMet, user content} structure successfully consigned to the N entities of the receiving side 7 Generates and stores XML_CONT_CONS ERDS evidence 8 Generates {NotificationOfConsignment} for N entities 9 Sends {NotificationOfConsignment} to receiving side 10 Generates and stores XML_CONS_NOT ERDS evidence {NotificationOfConsignment} received by N entities at the receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 19 Table 3f: Scenarios for intra-ERDS without notifications for acceptance (7/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#7 Purpose Parameter: {hndvMet, user content} A negative scenario of ERDS_BB_NO_NOT_F_ACC#2: When the notification of consignment is not received by one of the entities on the receiving side. Then, ERDS generates and stores two evidences; ConsignmentNotificationFailure ERDS evidence for one entity and ConsignmentNotification ERDS evidence for N-1 entities. Parameter: XML_SUB_ACC Parameter: {NotificationOfConsignment} Parameter: XML_CONS_NOT Parameter: XML_CONS_NOT_FAIL Sequence of actions # Sender ERDS Receiving side 1 Sender sends the original message 2 Accepts submission 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content} structure for N entities at the receiving side 5 Consigns {hndvMet, user content} structure to receiving side 6 N consignments of {hndvMet, user content} structure succeed 7 Generates {NotificationOfConsignment} for N entities in receiving side 8 Consigns {NotificationOfConsignment} for N entities in receiving side but one fails 9 N-1 {NotificationOfConsignment} are successfully received; one is not received 10 Generates and stores one XML_CONS_NOT_FAIL ERDS evidence for one entity and XML_CONS_NOT ERDS evidence for N-1 entities ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 20 Table 3g: Scenarios for intra-ERDS without notifications for acceptance (8/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#8 Purpose Parameter: {hndvMet, user content} A negative scenario of ERDS_BB_NO_NOT_F_ACC#2: Where one of the ERD dispatch consignments fails. Now, ERDS generates and stores two evidences; ContentConsignment ERDS evidence for N-1 entities and ContentConsignmentFailure ERDS evidence for one entity. Parameter: XML_SUB_ACC Parameter: XML_CONT_CONS Parameter: XML_CONS_FAIL Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content} structure 5 Consigns {hndvMet, user content} structure to receiving side 6 N-1 {hndvMet, user content} structures are successfully consigned. One fails 7 Generates XML_CONT_CONS ERDS evidence for N-1 entities and one XML_CONS_FAIL ERDS evidence for one entity and stores them ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 21 Table 3h: Scenarios for intra-ERDS without notifications for acceptance (9/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#9 Purpose Parameter: {hndvMet, user content} The positive scenario: Where the ERDS accepts the original message, then it generates and consigns the structure (including handover metadata and user content) to N entities on the receiving side. In the next step, ERDS generates the ContentConsignment ERDS evidence. After the successful retrieval of the ERD payload on the receiving side, ERDS generates and stores ContentAccessTracking ERDS evidence for the N handovers. Here, the scenario includes ContentAccessTracking event instead of the handover, as both events provide evidence of the successful delivery of the user content. Parameter: XML_SUB_ACC Parameter: XML_CONT_CONS Parameter: XML_CONT_AC_TRACK Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content} structure 5 Consigns {hndvMet, user content} structure to the N entities at the receiving side 6 Generates and stores XML_CONT_CONS ERDS evidence {hndvMet, user content} structure correctly consigned to N entities at receiving side 7 All the entities retrieve the ERD dispatch 8 Generates and stores XML_CONT_AC_TRACK ERDS evidence for the N handovers performed N handovers of {hndvMet, user content} structure succeed ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 22 Table 3i: Scenarios for intra-ERDS without notifications for acceptance (10/10) Scenario id: ERDS_BB_NO_NOT_F_ACC#10 Purpose Parameter: {hndvMet, user content, XML_SUB_ACC} A positive scenario of ERDS_BB_NO_NOT_F_ACC#2: Where ERDS generates and consigns the structure {including handover metadata, user content, and SubmissionAcceptance evidence} to N entities on the receiving side and generates the ContentHandover ERDS evidence. Parameter: XML_CONT_HAND Sequence of actions # Sender ERDS Receiving side 1 Sender sends the original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {hndvMet, user content, XML_SUB_ACC} structure 5 Hands over {hndvMet, user content, XML_SUB_ACC} structure to the receiving side 6 Generates and stores XML_CONT_HAND ERDS evidence {hndvMet, user content, XML_SUB_ACC} structure successfully handed over to the N entities at the receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 23
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.3.3 Scenarios with notification for acceptance
|
Table 4 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same ERDS and the ERDS sends notification for acceptance to the entities at the receiving side. Table 4: Scenarios for intra-ERDS with notifications for acceptance (1/7) Scenario id: ERDS_BB_NOT_F_ACC#1 Purpose Parameter: {hndvMet, user content} The simplest positive scenario: Where the ERDS accepts the original message, then it generates and sends a structure containing NotificationForAcceptance to the receiving side. When the ERDS has succeeded in delivering these NotificationForAcceptance, it generates one NotificationDelivered for each entity in the receiving side. When N entities successfully receive and respond positively to the notification of acceptance at the receiving side, ERDS generates and stores their ConsignmentAcceptance evidence. Afterwards, ERDS generates and consigns the structure {Including handover metadata and user content} to N entities on the receiving side. The cycle of message events is finalized with the generation of the ContentConsignment ERDS evidence for N entities. Parameter: {NotificationForAcceptance} Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_NOT_DEL Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} 5 Generates and stores XML_NOT_F_ACC ERDS evidence 6 Sends {NotificationForAcceptance} 7 All entities in receiving side receive one {NotificationForAcceptance} and answer positively 8 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 9 Receives positive responses from receiving side and Generates and stores XML_CONS_ACC ERDS evidence for the N entities at receiving side 10 Generates {hndvMet, user content} structure 11 Consigns {hndvMet, user content} to N entities in receiving side 12 Generates and stores XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} succeed ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 24 Table 4a: Scenarios for intra-ERDS with notifications for acceptance (2/7) Scenario id: ERDS_BB_NOT_F_ACC#2 Purpose Parameter: {hndvMet, user content} A negative scenario of ERDS_BB_NOT_F_ACC#1: The notification of acceptance is successfully received by N entities on the receiving side, where one entity rejects the consignment. Now ERDS generates and stores two evidences; ConsignmentAcceptance ERDS evidence for N-1 entities and ConsignmentRejection ERDS evidence for 1 entity. Afterwards, ERDS generates and consigns the structure {Including handover metadata and user content} to N-1 entities on the receiving side. The cycle of message events is finalized with the generation of the ContentConsignment ERDS evidence for N-1 entities. Parameter: {NotificationForAcceptance} Parameter: XML_SUB_ACC Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_CONS_REJ Parameter: XML_NOT_DEL Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} for N entities at receiving side 5 Sends {NotificationForAcceptance} to N entities at receiving side 6 Generates and stores XML_NOT_F_ACC ERDS evidence for N entities N entities correctly receive {NotificationForAcceptance}. N-1 accept. One does not accept consignment 7 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 8 Receives N-1 positive answers and one negative answer 9 Generates XML_CONS_ACC ERDS evidence for N-1 entities and one XML_CONS_REJ ERDS evidence for 1 entity 10 Generates {hndvMet, user content} structure for N-1 entities 11 Consigns them to the N-1 entities at receiving side 12 Generates XML_CONT_CONS for N-1 entities N-1 {hndvMet, user content} correctly consigned to N-1 entities at receiving side 13 Generates XML_CONT_CONS ERDS evidence for N-1 entities ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 25 Table 4b: Scenarios for intra-ERDS with notifications for acceptance (3/7) Scenario id: ERDS_BB_NOT_F_ACC#3 Purpose Parameter: {hndvMet, user content} A negative scenario similar to ERDS_BB_NOT_F_ACC#1: Where ERDS does not receive response from one entity after sending the structure of NotificationForAcceptance. Now, ERDS generates and stores two evidences; ConsignmentAcceptance ERDS evidence for N-1 entities and ConsignmentRejection ERDS evidence for 1 entity. Afterwards, ERDS generates and consigns the structure {Including handover metadata and user content} to N-1 entities on the receiving side. The cycle of message events is finalized with the generation of the ContentConsignment ERDS evidence for N-1 entities and AcceptanceRejectionExpiry ERDS evidence for one entity. Parameter: {NotificationForAcceptance} Parameter: XML_SUB_ACC Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_ACC_REJ_EXP Parameter: XML_NOT_DEL Parameter: XML_CONT_CONS Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} for N entities at receiving side 5 Sends {NotificationForAcceptance} to N entities at receiving side 6 Generates and stores XML_NOT_F_ACC ERDS evidence for N entities N entities correctly receive {NotificationForAcceptance}. N-1 accept. One does not answer in time 7 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 8 Receives N-1 positive answers 9 Generates {hndvMet, user content} structure for N-1 entities 10 Consigns {hndvMet, user content} structure to the N-1 entities that have accepted 11 When the expiration time is reached Generates and stores XML_CONS_ACC ERDS evidence for N-1 entities and one XML_ACC_REJ_EXP ERDS evidence for one entity {hndvMet, user content} structure successfully consigned to N-1 entities at receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 26 Table 4c: Scenarios for intra-ERDS with notifications for acceptance (4/7) Scenario id: ERDS_BB_NOT_F_ACC#4 Purpose Parameter: {hndvMet, user content} A positive scenario of ERDS_BB_NOT_F_ACC#3: After the successful handover of the payload at receiving side, the cycle of message events is completed with the generation and storing of ContentHandover ERDS evidence for N entities. Parameter: {NotificationForAcceptance} Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_CONT_CONS Parameter: XML_NOT_DEL Parameter: XML_CONT_HAND Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} 5 Generates and stores XML_NOT_F_ACC ERDS evidence 6 Sends {NotificationForAcceptance} 7 All entities in receiving side receive one {NotificationForAcceptance} and answer positively 8 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 9 Receives positive responses from receiving side and Generates and stores XML_CONS_ACC ERDS evidence for the N entities at receiving side 10 Generates {hndvMet, user content} structure 11 Consigns {hndvMet, user content} to N entities in receiving side 12 Generates and stores XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 13 N handovers of {hndvMet, user content} structure succeed 14 Generates and stores XML_CONT_HAND ERDS evidence for N entities ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 27 Table 4d: Scenarios for intra-ERDS with notifications for acceptance (5/7) Scenario id: ERDS_BB_NOT_F_ACC#5 Purpose Parameter: {hndvMet, user content} A negative scenario of ERDS_BB_NOT_F_ACC#4: After the occurrence of N-1 successful and 1 failed handover of the payload at the receiving side, the cycle of message events is completed with the generation and storing of ContentHandover ERDS evidence for N-1 entities, and ContentHandoverFailure for 1 entity. Parameter: {NotificationForAcceptance} Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_CONT_CONS Parameter: XML_CONT_HAND Parameter: XML_NOT_DEL Parameter: XML_CONT_HAND_FAIL Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} 5 Generates and stores XML_NOT_F_ACC ERDS evidence 6 Sends {NotificationForAcceptance} 7 All entities in receiving side receive one {NotificationForAcceptance} and answer positively 8 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 9 Receives positive responses from receiving side and Generates and stores XML_CONS_ACC ERDS evidence for the N entities at receiving side 10 Generates {hndvMet, user content} structure 11 Consigns {hndvMet, user content} to N entities in receiving side 12 Generates and stores XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 13 N-1 handovers of {hndvMet, user content} structure succeed. One fails 14 Generates and stores XML_CONT_HAND ERDS evidence for N-1 entities, and XML_CONT_HAND_FAIL for 1 entity ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 28 Table 4e: Scenarios for intra-ERDS with notifications for acceptance (6/7) Scenario id: ERDS_BB_NOT_F_ACC#6 Purpose Parameter: {hndvMet, user content} A negative scenario similar to the combination of ERDS_BB_NOT_F_ACC#2 and ERDS_BB_NOT_F_ACC#5: The notification of acceptance is successfully received by N entities on the receiving side, one entity rejects the consignment. Now, ERDS generates and stores two evidences; ConsignmentAcceptance ERDS evidence for N-1 entities and ConsignmentRejection ERDS evidence for 1 entity. Afterwards, ERDS generates and consigns the structure {Including handover metadata and user content} to N-1 entities on the receiving side. Then, ERDS generates ContentConsignment ERDS evidence for N-1 entities and ConsignmentRejection ERDS evidence for one entity. After the N-2 successful and 1 failed handover of the payload at receiving side, the cycle of message events is completed with the generation and storing of ContentHandover ERDS evidence for N-2 entities, and ContentHandoverFailure for 1 entity. Parameter: {NotificationForAcceptance} Parameter: XML_SUB_ACC Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_CONS_REJ Parameter: XML_CONT_CONS Parameter: XML_CONT_HAND Parameter: XML_NOT_DEL Parameter: XML_CONT_HAND_FAIL Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} for N entities at receiving side 5 Sends {NotificationForAcceptance} to N entities at receiving side 6 Generates and stores XML_NOT_F_ACC ERDS evidence for N entities N entities correctly receive {NotificationForAcceptance}. N-1 accept. One does not accept consignment 7 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 8 Receives N-1 positive answers and one negative answer 9 Generates XML_CONS_ACC ERDS evidence for N-1 entities and one XML_CONS_REJ ERDS evidence for 1 entity 10 Generates {hndvMet, user content} structure for N-1 entities 11 Consigns them to the N-1 entities at receiving side 12 Generates XML_CONT_CONS ERDS evidence for N-1 entities N-1 {hndvMet, user content} correctly consigned to N-1 entities at receiving side 13 N-2 handovers of {hndvMet, user content} structure succeed. One fails 14 Generates and stores XML_CONT_HAND ERDS evidence for N-2 entities, and XML_CONT_HAND_FAIL for 1 entity ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 29 Table 4f: Scenarios for intra-ERDS with notifications for acceptance (7/7) Scenario id: ERDS_BB_NOT_F_ACC#7 Purpose Parameter: {hndvMet, user content} A positive scenario of ERDS_BB_NOT_F_ACC#3: After the successful handover of the payload at receiving side, the cycle of message events is completed with the generation and storing of ContentAccessTracking ERDS evidence for N entities. Here, the scenario includes ContentAccessTracking event instead of the handover, as both events provide evidence of the successful delivery of the user content. Parameter: {NotificationForAcceptance} Parameter: XML_NOT_F_ACC Parameter: XML_CONS_ACC Parameter: XML_CONT_CONS Parameter: XML_NOT_DEL Parameter: XML_CONT_AC_TRACK Sequence of actions # Sender ERDS Receiving side 1 Sender sends original message 2 Accepts submission. 3 Generates and stores XML_SUB_ACC ERDS evidence 4 Generates {NotificationForAcceptance} 5 Generates and stores XML_NOT_F_ACC ERDS evidence 6 Sends {NotificationForAcceptance} 7 All entities in receiving side receive one {NotificationForAcceptance} and answer positively 8 Generates and stores XML_NOT_DEL evidence for the N entities at receiving side 9 Receives positive responses from receiving side and Generates and stores XML_CONS_ACC ERDS evidence for the N entities at receiving side 10 Generates {hndvMet, user content} structure 11 Consigns {hndvMet, user content} to N entities in receiving side 12 Generates and stores XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 13 N handovers of {hndvMet, user content} structure succeed 14 Generates and stores XML_CONT_AC_TRACK ERDS evidence for N entities ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 30
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.4 Scenarios for 4-corner model
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.4.1 Introduction
|
The present clause defines test cases for scenarios that take place when the sender and the entities at the receiving side are subscribed to different ERDSs but there are not intermediate ERDSs between the SERDS and the RERDS. Clause 5.4.2 defines test cases when RERDS does not notify for acceptance. Clause 5.4.3 defines test cases when RERDS notifies for acceptance.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.4.2 Scenarios where RERDS does not use notification for acceptance
|
Table 5 defines a number of scenarios for the case where RERDS does not notify for acceptance. The scenarios are based on scenarios at Table 3 adding the relay acceptance and relay rejection events at the some of the RERDSs and their corresponding ERDS evidences. For the sake of simplicity, it will be supposes that all the entities at receiving side are served by the same RERDS. It could be possible to use the templates defined in the present document for defining scenarios where the aforementioned entities are served by different RERDSs. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 31 Table 5: Scenarios for RERDS not using notification for acceptance (1/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC#1 Purpose Parameter: {hndvMet, EV_SET#1} Var EV_SET#1 = {XML_SUB_ACC, XML_REL_REJ} The simplest negative scenario: Where SERDS accepts the submission, then generates and relies ERD dispatch message to RERDS. RERDS rejects the ERD dispatch message submitted by the SERDS and sends back the sender a structure with the set of ERDS evidences generated by SERDS. (Including the XML_REL_REJ). Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch>_WITH_XML_SUB_ ACC 4 Relies the <ERD_dispatch>_WITH_XML_SUB_ ACC to the RERDS 5 Receives ERDS receipt The RERDS Rejects the <ERD_dispatch>_WITH_XML_SU B_ACC 6 Generates and stores XML_REL_REJ ERDS evidence 7 Generates {hndvMet, EV_SET#1} structure 8 Sends {hndvMet, EV_SET#1} back to sender 9 Sender receives {hndvMet, EV_SET#1} ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 32 Table 5a: Scenarios for RERDS not using notification for acceptance (2/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC #2 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC The simplest positive scenario: The SERDS accepts the submission of the original message, then it generates and relies to RERDS a dispatch message. RERDS accepts the relay message and sends back a receipt message containing RelayAcceptance evidence. Afterwards, RERDS generates and consigns a structure containing user content to N recipients on receiving side. If consigned successfully to N entities on the receiving side, RERDS generates and sends back the receipt containing ContentConsignment evidence to SERDS. SERDS generates and sends back the sender ERD receipt message with ContentConsignment ERDS evidence. Clause 4.3.2 of ETSI EN 319 522-1 [1] shows a variation of this scenario where RERDS sends XML_REL_ACC and XML_CONT_CONS in different ERD receipts. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_2>_WITH_XML_CONT_CONS Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SU B_ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SU B_ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_S UB_ACC and generates and stores XML_REL_ACC ERDS evidence 6 Generates <ERDS_receipt_1>_WITH_XML_R EL_ACC 7 Sends <ERDS_receipt_1>_WITH_XML_R EL_ACC to SERDS 8 Receives <ERDS_receipt_1>_WITH_XML_RE L_ACC from RERDS Generates {hndvMet, user content} struct 9 Consigns {hndvMet, user content} to the receiving side 10 Generates XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 11 Generates <ERDS_receipt_2>_WITH_XML_C ONT_CONS 12 Sends <ERDS_receipt_2>_WITH_XML_C ONT_CONS back to the SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 33 13 Receives <ERDS_receipt_2>_WITH_XML_CO NT_CONS and sends it back to the sender 14 Stores the XML_CONT_CONS ERDS evidence for N entities ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 34 Table 5b: Scenarios for RERDS not using notification for acceptance (3/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC#3 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_CONT_CONS} A positive scenario of 4C_RERDS_NO_NOT_F_ACC #2: Where both the RelayAcceptance and ContentConsignment evidences are included in the same ERD receipt and RERDS sends back to SERDS. When the user content is retrieved successfully by entities on the receiving side, the cycle of message events is completed with the generation of a receipt message containing ContentHandover ERDS evidence and sends it back to SERDS. Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_EV_SET#1 Parameter: Generates <ERD_receipt_2>_WITH_CONT_HAND Sequence of actions # Sender ERDS RERDS Receiving side 1 Sender sends original message Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SU B_ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SU B_ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_S UB_ACC and generates and stores XML_REL_ACC ERDS evidence 6 Generates {hndvMet, user content} structure for N recipients 7 Consigns {hndvMet, user content} structure to the receiving side 8 Generates XML_CONT_CONS ERDS evidence for N entities N consignments of {hndvMet, user content} structure succeed 9 Generates <ERDS_receipt>_WITH_XML_EV_ SET#1 10 Send <ERDS_receipt_1>_WITH_XML_E V_SET#1 to SERDS Entities in receiving side retrieve user content 11 Receives <ERDS_receipt_1>_WITH_EV_SET #1 and stores the evidences within the set Generates XML_CONT_HAND ERDS evidence for N entities 12 Generates <ERD_receipt_2>_WITH_CONT_H AND ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 35 Scenario id: 4C_RERDS_NO_NOT_F_ACC#3 Purpose 13 Sends <ERD_receipt_2>_WITH_CONT_H AND to SERDS 14 Receives <ERDS_receipt_2>__WITH_XML_C ONT_HAND and stores the ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 36 Table 5c: Scenarios for RERDS not using notification for acceptance (4/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC #4 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_REL_ACC, XML_CONT_CONS} A negative scenario of 4C_RERDS_NO_NOT_F_ACC# 3: Where one of the handovers fails, the RERDS sends back a receipt message to SERDS containing a set of evidence (including ContentHandover and ContentHandoverFailure evidence). Parameter: {hndvMet, user content} Var EV_SET#2 = {XML_CONT_HAND, XML_CONT_HAND_FAIL} Parameter: <ERDS_receipt_1>_WITH_XML_EV_SET#1 Parameter: ERDS_receipt_2>_WITH_XML_EV_SET#2 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SU B_ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SU B_ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_S UB_ACC and generates and stores XML_REL_ACC ERDS evidence 6 Generates {hndvMet, user content} structure for N recipients 7 Consigns {hndvMet, user content} to the receiving side 8 Generates XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 9 Generates <ERDS_receipt_1>_WITH_EV_SE T#1 10 Sends <ERDS_receipt_1>_WITH_EV_SE T#1 to SERDS N – 1 entities in receiving side successfully retrieve user content. One fails 11 Receives <ERDS_receipt>_WITH_XML_EV_S ET#1 and stores ERDS evidences Generates XML_CONT_HAND ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL ERDS evidence for one entity and stores them 12 Generates <ERD_receipt_2>_WITH_EV_SET #2 13 Sends <ERD_receipt_2>_WITH_EV_SET #2 to SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 37 Scenario id: 4C_RERDS_NO_NOT_F_ACC #4 Purpose 14 Receives <ERD_receipt_2>_WITH_EV_SET#2 and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 38 Table 5d: Scenarios for RERDS not using notification for acceptance (5/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC #5 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_CONT_CONS, CON_CONS_FAIL} A negative scenario 4C_RERDS_NO_NOT_F_ACC #2: Where one of the ERD dispatch consignments fails. The RERDS sends back a set of evidence to SERDS (including N-1 ContentConsignment and 1 ContentConsignmentFailure evidence) in a receipt message. Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC to SERDS Parameter: <ERDS_receipt_2>_WITH_XML_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SU B_ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SU B_ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_S UB_ACC and generates and stores XML_REL_ACC ERDS evidence 6 Generates <ERDS_receipt_1>_WITH_XML_R EL_ACC 7 Sends <ERDS_receipt_1>_WITH_XML_R EL_ACC to SERDS 8 Receives <ERDS_receipt_1>_WITH_XML_RE L_ACC to SERDS Generates {hndvMet, user content} structure for N entities 9 Consigns {hndvMet, user content} structure to receiving side 10 N-1 consignments of {hndvMet, user content} structure succeed. One consignment fails 11 Generates XML_CONT_CONS ERDS evidence related to N-1 entities Generates XML_CONT_CONS_FAIL related to one entity ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 39 Scenario id: 4C_RERDS_NO_NOT_F_ACC #5 Purpose 12 Generates <ERDS_receipt_2>_WITH_XML_E V_SET#1 13 Sends <ERDS_receipt_2>_WITH_XML_E V_SET#1 back to the SERDS 14 Receives <ERDS_receipt_2>_WITH_XML_EV _SET#1 and stores ERDS evidences The set of scenarios shown above could very easily be used for generating other scenarios where ERD payloads replace ERD dispatches. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 40 Below follows the generation of a new scenario resulting from replacing ERD dispatches by ERD payloads in scenario 4C_RERDS_NO_NOT_F_ACC #5. Differences between both scenarios have been highlighted in yellow. Table 5e: Scenarios for RERDS not using notification for acceptance (6/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC #6 Purpose Parameter: <ERD_payload_1> Var EV_SET#1 = {CONT_CONS, CON_CONS_FAIL} A scenario similar to 4C_RERDS_NO_NOT_F_ACC #5: Where SERDS generates and sends payload ERD message to RERDS, and RERDS accepts this relay message. Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC to SERDS Parameter: <ERDS_receipt_2>_WITH_XML_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_payload_1> 4 Relies <ERD_payload_1> to RERDS 5 Accepts <ERD_payload_1> and generates and stores XML_REL_ACC ERDS evidence 6 Generates <ERDS_receipt_1>_WITH_XML_R EL_ACC 7 Sends <ERDS_receipt_1>_WITH_XML_R EL_ACC to SERDS 8 Receives <ERDS_receipt_1>_WITH_XML_RE L_ACC to SERDS Generates {hndvMet, user content} structure for N entities 9 Consigns {hndvMet, user content} structure to receiving side 10 N-1 consignments of {hndvMet, user content} structure succeed. One consignment fails 11 Generates XML_CONT_CONS ERDS evidence related to N-1 entities Generates XML_CONT_CONS_FAIL related to one entity 12 Generates <ERDS_receipt_2>_WITH_XML_E V_SET#1 ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 41 Scenario id: 4C_RERDS_NO_NOT_F_ACC #6 Purpose 13 Sends <ERDS_receipt_2>_WITH_XML_E V_SET#1 back to the SERDS 14 Receives <ERDS_receipt_2>_WITH_XML_EV _SET#1 and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 42 Table 5f: Scenarios for RERDS not using notification for acceptance (7/7) Scenario id: 4C_RERDS_NO_NOT_F_ACC #7 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_REL_ACC, XML_CONT_CONS} A negative scenario of 4C_RERDS_NO_NOT_F_ACC# 3: Where one of the receiving entities fails in retrieving the user content, the RERDS sends back a receipt message to SERDS containing a set of evidence (including ContentAccessTracking and ContentConsignmentFailure evidence). Here, the scenario includes ContentAccessTracking event instead of the handover, as both events provide evidence of the successful delivery of the user content. Parameter: {hndvMet, user content} Var EV_SET#2 = {XML_CONT_AC_TRACK, XML_CONT_HAND_FAIL} Parameter: <ERDS_receipt_1>_WITH_XML_EV_SET#1 Parameter: ERDS_receipt_2>_WITH_XML_EV_SET#2 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SU B_ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SU B_ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_S UB_ACC and generates and stores XML_REL_ACC ERDS evidence 6 Generates {hndvMet, user content} structure for N recipients 7 Consigns {hndvMet, user content} to the receiving side 8 Generates XML_CONT_CONS ERDS evidence N consignments of {hndvMet, user content} structure succeed 9 Generates <ERDS_receipt_1>_WITH_EV_SE T#1 10 Sends <ERDS_receipt_1>_WITH_EV_SE T#1 to SERDS N - 1entities in receiving side successfully retrieve user content. One fails 11 Receives <ERDS_receipt>_WITH_XML_EV_S ET#1 and stores ERDS evidences Generates XML_CONT_AC_TRACK ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL ERDS evidence for one entity and stores them 12 Generates <ERD_receipt_2>_WITH_EV_SET #2 ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 43 Scenario id: 4C_RERDS_NO_NOT_F_ACC #7 Purpose 13 Sends <ERD_receipt_2>_WITH_EV_SET #2 to SERDS 14 Receives <ERD_receipt_2>_WITH_EV_SET#2 and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 44
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.4.3 Scenarios where RERDS uses notification for acceptance
|
Table 6 defines a number of scenarios for the case where RERDS uses notification for acceptance. The scenarios are based on scenarios at Table 4 adding the relay acceptance and relay rejection events at the some of the RERDSs and their corresponding ERDS evidences. For the sake of simplicity, it is supposed that all the entities at receiving side are served by the same RERDS. It could be possible to use the templates defined in the present document for defining scenarios where the aforementioned entities are served by different RERDSs. Again, a similar set of scenarios can be obtained by replacing ERD dispatches with ERD payloads in the scenarios shown below. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 45 Table 6: Scenarios where RERDS uses notification for acceptance (1/6) Scenario id: 4C_REDS_NOT_F_ACC#1 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_NOT_AC_TRACK} The simplest positive scenario: The SERDS accepts the submission of the original message, then it generates and relies RERDS a dispatch message. RERDS accepts the relay message and sends back a receipt message containing RelayAcceptance evidence. RERDS generates and sends the NotificationForAcceptance to N entities at receiving side along with the generation of NotificationForAcceptance evidence. RERDS generates ConsignmentAcceptance evidence, as all the entities on receiving side responded positively. Afterwards, RERDS generates and consigns a structure containing user content to N recipients on receiving side. After the successful consignment to N entities, RERDS generates ContentConsignment evidence. RERDS generates ContentHandover evidence for all receiving entities upon successful retrieval of the user content. RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_NOT_AC_TRACK). Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_XML_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC from RERDS Generates {NotificationForAcceptance} struct 10 Sends {NotificationForAcceptance} struct to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence All entities in receiving side answer positively 12 Generates XML_NOT_DEL ERDS evidence for the N entities at receiving side. Generates and stores XML_NOT_AC_TRACK ERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 46 Scenario id: 4C_REDS_NOT_F_ACC#1 Purpose evidence for the N entities at receiving side 13 Generates XML_CONS_ACC ERDS evidence 14 Generates {hndvMet, user content} struct for N entities 15 Consigns {hndvMet, user content} struct to receiving side 16 N consignments of {hndvMet, user content} struct succeed 17 Generates XML_CONT_CONS ERDS evidence All the entities retrieve user content 18 Generates XML_CONT_HAND ERDS evidence 19 Generates <ERDS_receipt_2>_WITH_EV_SET#1 20 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 21 Receives <ERDS_receipt_2>_WITH_EV_SET#1 and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 47 Table 6a: Scenarios where RERDS uses notification for acceptance (2/6) Scenario id: 4C_RERDS_NOT_F_ACC#2 Purpose Parameter: {hndvMet, user content} Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONS_REJ, XML_CONT_CONS, XML_CONT_HAND} A negative scenario of 4C_REDS_NOT_F_ACC#1: Where one of the entities on the receiving side responds negatively to the NoficationForAcceptance. The RERDS generates and stores both N-1 ConsignmentAcceptance and 1 ConsignmentRejection evidence. RERDS generates and consigns a structure containing user content to N-1 recipients on receiving side. Upon the successful consignment to N -1 entities on the receiving side, RERDS generates ContentConsignment evidence. After the successful retrieval of the user content, RERDS generates ContentHandover evidence for N-1 receiving entities. RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONS_REJ, XML_CONT_CONS, XML_CONT_HAND). Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC and stores ERDS evidence Generates {NotificationforAcceptance} structure 10 Sends {NotificationforAcceptance} structure to receiving side 11 Generates and stores XML_NOT_F_ACC ERDS evidence N-1 entities in receiving side answer positively. One answers negatively 12 Generates and stores XML_NOT_DEL ERDS evidence for the N entities at receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 48 Scenario id: 4C_RERDS_NOT_F_ACC#2 Purpose 13 Generates and stores XML_CONS_ACC ERDS evidence for N-1 entities and one XML_CONS_REJ ERDS evidence for one entity 14 Generates {hndvMet, user content} struct 15 Successfully consigns {hndvMet, user content} structure to N-1 entities at receiving side 16 Generates XML_CONT_CONS ERDS evidence for N-1 entities N-1 entities retrieve user content. One fails 17 Generates XML_CONT_HAND ERDS evidence for N-1 entities 18 Generates <ERDS_receipt_2>_WITH_EV_SET#1 19 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 20 Receives <ERDS_receipt_2>_WITH_EV_SET#1, extracts ERDS evidences and stores them ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 49 Table 6b: Scenarios where RERDS uses notification for acceptance (3/6) Scenario id: 4C_RERDS_NOT_F_ACC#3 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_CONS_ACC, XML_ACC_REJ_EXP, XML_CONT_CONS, XML_CONT_HAND} . A negative scenario of 4C_REDS_NOT_F_ACC#1: Where one of the entities does not respond in time to the NoficationForAcceptance. The RERDS generates and stores both N-1 ConsignmentAcceptance and 1 AcceptanceRejectionExpiry evidence. RERDS generates and consigns a structure containing user content to N-1 recipients on receiving side. Upon successful consignment to N -1 entities on the receiving side, RERDS generates ContentConsignment evidence. After the successful retrieval of the user content, RERDS generates ContentHandover evidence for N-1 receiving entities. RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_ACC_REJ_EXP, XML_CONT_CONS, XML_CONT_HAND). Parameter: {hndvMet, user content} <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_XML_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC Generates {NotificationforAcceptance} structure 10 Sends {NotificationforAcceptance} structure to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence N-1 entities in receiving side answer positively. One does not answer in time 12 Generates XML_NOT_DEL ERDS evidence for the N entities at receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 50 Scenario id: 4C_RERDS_NOT_F_ACC#3 Purpose 13 Generates XML_CONS_ACC ERDS evidence for N-1 entities and one XML_ACC_REJ_EXP ERDS evidence for one entity 14 Generates {hndvMet, user content} structure for N-1 entities 15 Sends {hndvMet, user content} structure to N-1 accepting entities at receiving side 16 {hndvMet, user content} structure consigned to N-1 entities in receiving side 17 Generates XML_CONT_CONS ERDS evidence N-1 entities retrieve user content 18 Generates XML_CONT_HAND ERDS evidence for N-1 entities 19 Generates <ERDS_receipt_2>_WITH_EV_SET#1 20 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 21 Receives <ERDS_receipt_2>_WITH_EV_SET#, extracts ERDS evidences and stores them ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 51 Table 6c: Scenarios where RERDS uses notification for acceptance (4/6) Scenario id: 4C_RERDS_NOT_F_ACC#4 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_CONS_FAIL, XML_CONT_HAND} A negative scenario of 4C_REDS_NOT_F_ACC#1: Where user content is consigned to N-1 entities but failed to one. The RERDS generates and stores both N-1 ContentConsigment and 1 ContentConsignmentFailure evidence. Upon the successful retrieval of the user content, RERDS generates ContentHandover evidence for N-1 receiving entities. The RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_CONS_FAIL, XML_CONT_HAND). Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC Generates {NotificationforAcceptance} structure for N entities 10 Sends {NotificationforAcceptance} structure to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence All the entities in receiving side answer positively 12 Generates and stores XML_NOT_DEL ERDS evidence for the N entities at receiving side 13 Generates XML_CONS_ACC ERDS evidence for all the entities in receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 52 Scenario id: 4C_RERDS_NOT_F_ACC#4 Purpose 14 Generates {hndvMet, user content} structure for N entities 15 Sends {hndvMet, user content} structure to N entities 16 N-1 {hndvMet, user content} structure consignments succeed. One fails 17 Generates XML_CONT_CONS ERDS evidence for N-1 entities and XML_CONS_FAIL for one entity N-1 entities retrieve user content 18 Generates XML_CONT_HAND ERDS evidence 19 Generates <ERDS_receipt_2>_WITH_EV_SET#1 20 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 21 Receives <ERDS_receipt_2>_WITH_EV_SET#1, and stores the ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 53 Table 6d: Scenarios where RERDS uses notification for acceptance (5/6) Scenario id: 4C_RERDS_NOT_F_ACC#5 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONS_FAIL, XML_CONT_HAND XML_CONT_HAND_FAIL} A negative scenario of 4C_REDS_NOT_F_ACC#1: Where RERDS generates N-1 ContentHandover and 1 ContentHandoverFailure evidence for receiving entities when N-1 entities retrieve the user content successfully while 1 fails. RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONS_FAIL, XML_CONT_HAND XML_CONT_HAND_FAIL). Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC Generates {NotificationforAcceptance} structure 10 Sends {NotificationforAcceptance} structure to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence All the entities in receiving side answer positively 12 Generates and stores XML_NOT_DEL ERDS evidence for the N entities at receiving side 13 Generates XML_CONS_ACC ERDS evidence for all the entities in receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 54 Scenario id: 4C_RERDS_NOT_F_ACC#5 Purpose 14 Generates {hndvMet, user content} for N entities 15 Sends {hndvMet, user content} to N-1 accepting entities at receiving side 16 N consignments of {hndvMet, user content} structure succeed 17 Generates XML_CONT_CONS ERDS evidence N-1 entities retrieve user content. One fails 18 Generates XML_CONT_HAND ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL for one entity 19 Generates <ERDS_receipt_2>_WITH_EV_SET#1 20 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 21 Receives <ERDS_receipt_2>_WITH_EV_SET#1 and stores ErDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 55 Table 6e: Scenarios where RERDS uses notification for acceptance (6/6) Scenario id: 4C_RERDS_NOT_F_ACC#6 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_CONS_FAIL, XML_CONT_AC_TRACK} A negative scenario of 4C_REDS_NOT_F_ACC#1: Where user content is consigned to N-1 entities but failed to one. The RERDS generates and stores both N-1 ContentConsigment and 1 ContentConsignmentFailure evidence. Upon the successful retrieval of the user content, RERDS generates ContentAccessTracking evidence for N-1 receiving entities. The RERDS generates and sends back the SERD a receipt message with the set of evidence (including XML_NOT_F_ACC, XML_CONS_ACC, XML_CONT_CONS, XML_CONT_CONS_FAIL, XML_CONT_AC_TRACK). Here, the scenario includes ContentAccessTracking event instead of the handover, as both events provide evidence of the successful delivery of the user content. Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_EV_SET#1 Sequence of actions # Sender SERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_XML_SUB_ ACC 4 Relies <ERD_dispatch_1>_WITH_XML_SUB_ ACC to RERDS 5 Accepts <ERD_dispatch_1>_WITH_XML_SUB _ACC to RERDS 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_XML_REL _ACC 8 Sends <ERD_receipt_1>_WITH_XML_REL_ ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_XML_REL_A CC Generates {NotificationforAcceptance} structure for N entities 10 Sends {NotificationforAcceptance} structure to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence All the entities in receiving side answer positively 12 Generates and stores XML_NOT_DEL ERDS evidence for the N entities at receiving side 13 Generates XML_CONS_ACC ERDS evidence for all the entities in receiving side ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 56 Scenario id: 4C_RERDS_NOT_F_ACC#6 Purpose 14 Generates {hndvMet, user content} structure for N entities 15 Sends {hndvMet, user content} structure to N entities 16 N-1 {hndvMet, user content} structure consignments succeed. One fails 17 Generates XML_CONT_CONS ERDS evidence for N-1 entities and XML_CONS_FAIL for one entity N-1 entities retrieve user content 18 Generates XML_CONT_AC_TRACK ERDS evidence 19 Generates <ERDS_receipt_2>_WITH_EV_SET#1 20 Sends <ERDS_receipt_2>_WITH_EV_SET#1 to SERDS 21 Receives <ERDS_receipt_2>_WITH_EV_SET#1, and stores the ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 57
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.5 Scenarios for extended model
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.5.1 Introduction
|
The present clause defines test cases for scenarios that take place when the sender and the entities at the receiving side are subscribed to different ERDSs and there is one intermediate IERDS between the SERDS and the RERDSs. Clause 5.5.2 defines test cases where the RERDS does not use notification for acceptance. Clause 5.5.3 defines test cases where the RERDS uses notification for acceptance. As with previous scenarios defined in the present document, new sets of scenarios can be obtained by replacing ERD dispatches with ERD payloads in the scenarios shown below.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.5.2 Scenarios where RERDS does not use notification for acceptance
|
Table 7 shows scenarios where RERDS does not use notification for acceptance. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 58 Table 7: Scenarios where SERDS operates Store&Notify and RERDS operate Store&Forward (1/6) Scenario id: EXT_RERDS_NO_NOT_F_ACC#1 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC The simplest positive scenario: The SERDS accepts the submission of the original message, then generates and relies IERDS a dispatch message. IERDS accepts the relay message and sends back to SERDS a receipt message containing RelayAcceptance evidence. Afterwards, IERDS generates a dispatch message along with SubmissionAcceptance evidence to RERDS. RERDS accepts the relay message and sends back to IERDS a receipt message containing RelayAcceptance evidence. Afterwards, RERDS generates and consigns a structure containing user content to N recipients on receiving side. After being consigned successfully to N entities on the receiving side, RERDS generates and sends back the receipt containing ContentConsignment evidence to the previous ERDS. This Previous ERDS performs similar action till this message is sent back to the sender. The cycle of message events in this scenario is completed with the generation of a receipt message containing ContentHandover ERDS evidence. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_3>_WITH_XML_CONT_CONS Parameter: <ERDS_receipt_4>_WITH_XML_CONT_HAND Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC and stores ERDS evidence Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC to RERDS 11 Generates XML_REL_ACC ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 59 Scenario id: EXT_RERDS_NO_NOT_F_ACC#1 Purpose 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC Generates {hndvMet, user content} structure 15 Consigns {hndvMet, user content} structure to receiving side 16 N consignments of {hndvMet, user content} structure succeed 17 Generates XML_CONT_CONS ERDS evidence for N entities 18 Generates <ERDS_receipt_3>_WITH_XM L_CONT_CONS All the entities in receiving side successfully retrieve {hndvMet, user content} structure 19 Sends <ERDS_receipt_3>_WITH_XM L_CONT_CONS back to IERDS 20 Receives <ERDS_receipt_3>_WITH_X ML_CONT_CONS Generates XML_CONT_HAND for N entities 21 Sends <ERDS_receipt_3>_WITH_X ML_CONT_CONS back to SERDS Generates <ERDS_receipt_4>_WITH_XM L_CONT_HAND 22 Receives <ERDS_receipt_3>_WITH_ XML_CONT_CONS and stores ERDS evidences Sends <ERDS_receipt_4>_WITH_XM L_CONT_HAND back to IERDS 23 Sends <ERDS_receipt_3>_WITH_ XML_CONT_CONS back to sender Receives <ERDS_receipt_4>_WITH_X ML_CONT_HAND 24 Receives <ERDS_receipt_3>_W ITH_XML_CONT_CO NS Sends <ERDS_receipt_4>_WITH_X ML_CONT_HAND back to SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 60 Scenario id: EXT_RERDS_NO_NOT_F_ACC#1 Purpose 25 Receives <ERDS_receipt_4>_WITH_ XML_CONT_HAND and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 61 Table 7a: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (2/6) Scenario id: EXT_RERDS_NO_NOT_F_ACC#2 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var SET_EV#1 = {XML_CONT_CONS, XML_CONT_CONS_FAIL} . A negative scenario of EXT_RERDS_NO_NO T_F_ACC#1 : When the user content is consigned successfully to N-1 entities but failed for 1 entity on the receiving side, RERDS generates and sends back to IERD a receipt message with the set of evidence (including XML_CONT_CONS, XML_CONT_CONS_F AIL). After the user content is retrieved successfully by N-1 entities on the receiving side, the cycle of message events in this scenario is completed with the generation of a receipt message containing ContentHandover ERDS evidence. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_3>_WITH_EV_SET#1 Parameter: <ERDS_receipt_4>_WITH_XML_CONT_HAND Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence and stores 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC and stores ERDS evidence Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC 11 Generates and stores XML_REL_ACC ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 62 Scenario id: EXT_RERDS_NO_NOT_F_ACC#2 Purpose 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_AC and stores ERDS evidence Generates {hndvMet, user content} structure for N entities 15 Consigns {hndvMet, user content} to receiving side 16 N-1 {hndvMet, user content} structure consignments succeed. One fails 17 Generates and stores XML_CONT_CONS ERDS evidence for N-1 entities and XML_CONT_CONS_FAIL ERDS evidence for one entity 18 Generates <ERDS_receipt_3>_WITH_EV_ SET#1 N-1 entities in receiving side retrieve {hndvMet, user content} structure 19 Sends <ERDS_receipt_3>_WITH_EV_ SET#1 back to IERDS 20 Receives <ERDS_receipt_3>_WITH_E V_SET#1 Generates and stores XML_CONT_HAND for N-1 entities 21 Sends <ERDS_receipt_3>_WITH_E V_SET#1 back to SERDS Generates <ERDS_receipt_4>_WITH_XM L_CONT_HAND 22 Receives <ERDS_receipt_3>_WITH_ EV_SET#1 and stores ERDS evidences Sends <ERDS_receipt_4>_WITH_XM L_CONT_HAND back to IERDS 23 Receives <ERDS_receipt_4>_WITH_X ML_CONT_HAND 24 Sends <ERDS_receipt_4>_WITH_X ML_CONT_HAND back to SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 63 Scenario id: EXT_RERDS_NO_NOT_F_ACC#2 Purpose 25 Receives <ERDS_receipt_4>_WITH_ XML_CONT_HAND and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 64 Table 7b: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (3/7) Scenario id: EXT_RERDS_NO_NOT_F_ACC #3 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_CONT_HAND, XML_CONT_HAND_FAIL} A negative scenario of EXT_RERDS_NO_NO T_F_ACC#1 : When N-1 entities retrieve the user content while 1 failed to retrieve, the RERDS generates and sends a receipt message back to IERDS containing a set of evidence (including XML_CONT_HAND XML_CONT_HAND_F AIL). Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_3>_WITH_XML_CONT_CONS Parameter: <ERDS_receipt_4>_WITH_EV_SET#1 Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC and stores ERDS evidence Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC to RERDS 11 Generates and stores XML_REL_ACC ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 65 Scenario id: EXT_RERDS_NO_NOT_F_ACC #3 Purpose 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC and stores ERDS evidence Generates {hndvMet, user content} structure 15 Consigns {hndvMet, user content} to receiving side 16 N {hndvMet, user content} structure consignments succeed 17 Generates and stores XML_CONT_CONS ERDS evidence for N entities 18 Generates <ERDS_receipt_3>_WITH_XM L_CONT_CONS N-1 entities in receiving side successfully retrieve {hndvMet, user content} structure. One entity fails 19 Sends <ERDS_receipt_3>_WITH_XM L_CONT_CONS back to IERDS 20 Receives <ERDS_receipt_3>_WITH_X ML_CONT_CONS Generates XML_CONT_HAND ERDS evidence for N-1 entities and XML_CONT_HAND_FAIL for one entity 21 Sends <ERDS_receipt_3>_WITH_X ML_CONT_CONS back to SERDS Generates <ERDS_receipt_4>_WITH_EV_ SET#1 22 Receives <ERDS_receipt_3>_WITH_ XML_CONT_CONS and stores ERDS evidences Sends <ERDS_receipt_4>_WITH_EV_ SET#1 back to IERDS 23 Receives <ERDS_receipt_4>_WITH_E V_SET#1 24 Sends <ERDS_receipt_4>_WITH_E V_SET#1 back to SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 66 Scenario id: EXT_RERDS_NO_NOT_F_ACC #3 Purpose 25 Receives <ERDS_receipt_4>_WITH_ EV_SET#1 and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 67 Table 7c: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (4/7) Scenario id: EXT_RERDS_NO_NOT_F_ACC #4 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC A negative scenario of EXT_RERDS_NO_NOT_F_A CC#1 : When the SERDS accepts the submission, it generates and relies IERDS on an ERD dispatch message. Afterwards, IERDS rejects the ERD dispatch message and sends back the SERDS a receipt message containing RelayRejection evidence. The cycle of message events in this scenario is completed with SERDS generates and sends the structure containing handover metadata along with RelayRejection evidence back to the sender. Parameter: <ERDS_receipt_1>_WITH_XML_REL_REJ Parameter: {hndvMet,XML_REL_REJ} Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Rejects relying 6 Generates and stores XML_REL_REJ ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_REJ 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_REJ back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_REJ and stores ERDS evidence 10 Generates {hndvMet,XML_REL_REJ} structure 11 Sends {hndvMet,XML_REL_REJ} structure back to sender 12 Receives {hndvMet,XML_REL_ REJ} structure ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 68 Table 7d: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (5/7) Scenario id: EXT_RERDS_NO_NOT_F_ACC #5 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC A negative scenario of EXT_RERDS_NO_NOT_F _ACC#1: The SERDS accepts the submission of the original message, It generates and relies IERDS a dispatch message. IERDS accepts the relay message and sends back to SERDS a receipt message containing RelayAcceptance evidence. Afterwards, IERDS generates a dispatch message along with SubmissionAcceptance evidence to RERDS. RERDS rejects the relay message and sends back to IERDS a receipt message containing RelayRejection evidence. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_2>_WITH_XML_REL_REJ Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC but rejects it 11 Generates XML_REL_REJ ERDS evidence 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_REJ 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_REJ back to IERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 69 Scenario id: EXT_RERDS_NO_NOT_F_ACC #5 Purpose 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_REJ 15 Sends <ERDS_receipt_2>_WITH_X ML_REL_REJ back to SERDS 16 Receives <ERDS_receipt_2>_WITH_ XML_REL_REJ 17 Sends <ERDS_receipt_2>_WITH_ XML_REL_REJ back to sender 18 Receives <ERDS_receipt_2>_W ITH_XML_REL_REJ ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 70 Table 7e: Scenarios where SERDS operates Store&Notify and RERDS operate Store&Forward (6/6) Scenario id: EXT_RERDS_NO_NOT_F_ACC#6 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC The simplest positive scenario: The SERDS accepts the submission of the original message, then generates and relies IERDS a dispatch message. IERDS accepts the relay message and sends back to SERDS a receipt message containing RelayAcceptance evidence. Afterwards, IERDS generates a dispatch message along with SubmissionAcceptance evidence to RERDS. RERDS accepts the relay message and sends back to IERDS a receipt message containing RelayAcceptance evidence. Afterwards, RERDS generates and consigns a structure containing user content to N recipients on receiving side. After being consigned successfully to N entities on the receiving side, RERDS generates and sends back the receipt containing ContentConsignment evidence to the previous ERDS. This Previous ERDS performs similar action till this message is sent back to the sender. The cycle of message events in this scenario is completed with Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_3>_WITH_XML_CONT_CONS Parameter: <ERDS_receipt_4>_WITH_XML_CONT_AC_TRACK Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC and stores ERDS evidence Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC to RERDS 11 Generates XML_REL_ACC ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 71 Scenario id: EXT_RERDS_NO_NOT_F_ACC#6 Purpose 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC the generation of a receipt message containing ContentAccessTracking ERDS evidence. 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC Generates {hndvMet, user content} structure 15 Consigns {hndvMet, user content} structure to receiving side 16 N consignments of {hndvMet, user content} structure succeed 17 Generates XML_CONT_CONS ERDS evidence for N entities 18 Generates <ERDS_receipt_3>_WITH_XM L_CONT_AC_TRACK All the entities in receiving side successfully retrieve {hndvMet, user content} structure 19 Sends <ERDS_receipt_3>_WITH_XM L_CONT_CONS back to IERDS 20 Receives <ERDS_receipt_3>_WITH_X ML_CONT_CONS Generates XML_CONT_AC_TRACK for N entities 21 Sends <ERDS_receipt_3>_WITH_X ML_CONT_CONS back to SERDS Generates <ERDS_receipt_4>_WITH_XM L_CONT_AC_TRACK 22 Receives <ERDS_receipt_3>_WITH_ XML_CONT_CONS and stores ERDS evidences Sends <ERDS_receipt_4>_WITH_XM L_CONT_AC_TRACK back to IERDS 23 Sends <ERDS_receipt_3>_WITH_ XML_CONT_CONS back to sender Receives <ERDS_receipt_4>_WITH_X ML_CONT_AC_TRACK 24 Receives <ERDS_receipt_3>_W ITH_XML_CONT_CO NS Sends <ERDS_receipt_4>_WITH_X ML_CONT_AC_TRACK back to SERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 72 Scenario id: EXT_RERDS_NO_NOT_F_ACC#6 Purpose 25 Receives <ERDS_receipt_4>_WITH_ XML_CONT_AC_TRACK and stores ERDS evidences ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 73
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
5.5.3 Scenarios where RERDS uses notification for acceptance
|
Table 8 shows scenarios where RERDS submits notification for acceptance. Table 8: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (1/3) Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#1 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL} The simplest positive scenario: Where the SERDS accepts the submission of the original message, it generates and relies IERDS a dispatch message. IERDS accepts the relay message and sends back to SERDS a receipt message containing RelayAcceptance evidence. Afterwards, IERDS generates a dispatch message along with SubmissionAcceptance evidence to RERDS. RERDS accepts the relay message and sends back RelayAcceptance evidence to IERDS in the receipt message. The RERDS generates and sends the NotificationForAcceptance to N entities at receiving side along with the generation of NotificationForAcceptance evidence. When all the entities on receiving side responded positively, then RERDS generates and sends back to IERDS a ConsignmentAcceptance evidence. The RERDS generates and consigns a structure containing user content to N recipients on receiving side. Upon successful consignment to N entities on the receiving side, RERDS generates and sends back the receipt containing ContentConsignment evidence to the previous ERDS. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_3>_WITH_EV_SET#1 Parameter: <ERDS_receipt_4>_WITH_XML_CONS_ACC Parameter: {hndvMet, user content} Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_SUB_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_SUB_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_SUB_ACC and stores ERDS evidence Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC} to RERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 74 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#1 Purpose 10 Receives <ERD_dispatch_1>_WITH_XM L_SUB_ACC 11 Generates and stores XML_REL_ACC ERDS evidence 12 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 13 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 14 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC Sends {NotificationforAcceptance} 15 Generates and stores XML_NOT_F_ACC ERDS evidence All the entites at receiving side receive {NotificationforAcceptance} 16 Generates and stores XML_NOT_DEL ERDS evidence 17 Generates <ERDS_receipt_3>_WITH_EV_ SET#1 All the entites at receiving side access IERDS and accept consignment 18 Sends <ERDS_receipt_3>_WITH_EV_ SET#1 back to IERDS 19 Receives <ERDS_receipt_3>_WITH_E V_SET#1 Generates {hndvMet, user content} structure 20 Sends <ERDS_receipt_3>_WITH_E V_SET#1 back to SERDS Consigns {hndvMet, user content} structure to N entities at receiving side 21 Receives <ERDS_receipt_3>_WITH_ EV_SET#1 and stores ERDS evidences Generates and stores XML_CONS_ACC N entities N {hndvMet, user content} structure consignments succeed 22 Generates <ERDS_receipt_4>_WITH_XM L_CONS_ACC 23 Sends <ERDS_receipt_4>_WITH_XM L_CONS_ACC back to IERDS 24 Receives <ERDS_receipt_4>_WITH_X ML_CONS_ACC ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 75 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#1 Purpose 25 Sends <ERDS_receipt_4>_WITH_X ML_CONS_ACC back to SERDS 26 Receives <ERDS_receipt_4>_WITH_ XML_CONS_ACC and stores ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 76 Table 8a: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (2/3) Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#2 Purpose # Sender SERDS IERDS RERDS Receiving side Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL} A negative scenario of EXT_RERDS_NOT_F _ACC #1: When one of the entities rejects the NoficationForAcceptan ce, then RERDS generates and sends back to IERDS a receipt message containing a set of evidence (including both N-1 ConsignmentAcceptan ce and 1 ConsignmentRejection evidence). RERDS generates and consigns a structure containing user content to N-1 recipients on receiving side. Upon successful consignment to N -1 entities on the receiving side, RERDS generates and sends back to IERDS a receipt containing ContentConsignment evidence. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Var EV_SET#2 = {XML_CONS_ACC, XML_CONS_REJ} Parameter: {NotificationforAcceptance} Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_3>_WITH_EV_SET#1 Parameter: <ERDS_receipt_4>_WITH_EV_SET#2 Parameter: <ERDS_receipt_5>_WITH_XML_REL_ACC Parameter: {hndvMet, user content} Parameter: <ERDS_receipt_6>_WITH_XML_CONT_CONS Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates and stores XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS _1 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC 6 Generates and stores XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_REL_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_REL_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_REL_ACC and stores ERDS evidence Generates {NotificationforAcceptance} ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 77 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#2 Purpose # Sender SERDS IERDS RERDS Receiving side 10 Relies <ERDS_notification_1>_forAc ceptance to RERDS 11 Receives <ERDS_notification_1>_forAcc eptance 12 Generates XML_REL_ACC ERDS evidence 13 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 14 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 15 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC Sends {NotificationforAcceptance} 16 Generates and stores XML_NOT_F_ACC ERDS evidence All the entities at receiving side receive {NotificationforAcceptance} 17 Generates and stores XML_NOT_DEL ERDS evidence 18 Generates <ERDS_receipt_3>_WITH_EV_ SET#1 . 19 Sends <ERDS_receipt_3>_EV_SET#1 back to IERDS 20 Receives <ERDS_receipt_3>_WITH_E V_SET#1 Generates and stores XML_CONS_ACC ERDS evidence for N-1 entities at receiving side and one XML_CONS_REJ ERDS evidence for one entity at receiving side N-1 entities at receiving side accept consignment. One party rejects it 21 Sends <ERDS_receipt_3>_WITH_E V_SEYT#1 back to SERDS Generates <ERDS_receipt_4>_WITH_EV_ SET#2 22 Receives <ERDS_receipt_3>_WITH_ EV_SET#1 and stores ERDS evidence Sends <ERDS_receipt_4>_WITH_EV_ SET#2 back to IERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 78 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#2 Purpose # Sender SERDS IERDS RERDS Receiving side 23 Receives <ERDS_receipt_4>_WITH_E V_SET#2 Generates hndvMet, user content} structure 24 Sends <ERDS_receipt_4>_WITH_E V_SET#2 back to SERDS Consigns hndvMet, user content} structure to N-1 entities at receiving side 25 Receives <ERDS_receipt_4>_WITH_ EV_SET#2 and stores ERDS evidences Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS to RERDS Generates and stores XML_CONT_CONS ERDS evidence for N-1 entities N-1 {hndvMet, user content} structure consignments succeed 26 Sends <ERDS_receipt_4>_WITH_ EV_SET#2 back to sender Generates <ERDS_receipt_5>_WITH_XM L_CONT_CONS 27 Receives <ERDS_receipt_4>_ WITH_EV_SET#2 Relies <ERDS_receipt_5>_WITH_XM L_CONT_CONS to IERDS 28 Receives <ERDS_receipt_5>_WITH_X ML_CONT_CONS 29 Relies <ERDS_receipt_5>_WITH_X ML_CONT_CONS to SERDS 30 Receives <ERDS_receipt_5>_WITH_ XML_CONT_CONS and stores ERDS evidence ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 79 Table 8b: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (3/3) Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#3 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL} A negative scenario of EXT_RERDS_NOT_F_ACC #1: Where RERDS generates and sends the NotificationForAcceptance to N entities at receiving side. Then it generates and sends a receipt message containing NotificationForAcceptance evidence back to IERDS. When N- 1 the entities on receiving side respond positively while 1 negatively, the IERDS generates and sends back to SERDS a receipt message containing a set of evidence (including N-1 ConsignmentAcceptance and 1 ConsignmentRejection evidence). Afterwards, RERDS generates and consigns a structure containing user content to N-1 recipients on receiving side. Upon successful consignment to N-1 entities on the receiving side, RERDS generates and sends back the receipt containing ContentConsignment evidence to the previous ERDS. The cycle of message events in this scenario is completed with the generation of a receipt message containing a set of evidence (including ContentHandover and ContentHandoverFail evidence) and sends it back to IERDS. Parameter: <ERDS_receipt_1>_WITH_XML_REL_ACC Var EV_SET#2 = {XML_CONS_ACC, XML_CONS_REJ} Parameter: <ERDS_notification_1>_forAcceptance Var EV_SET#3 = {XML_CONT_HAND, XML_CONT_HAND_FAIL } Parameter: <ERDS_receipt_2>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_3>_WITH_EV_SET#1 Parameter: <ERDS_receipt_4>_WITH_EV_SET#2 Parameter: <ERDS_receipt_5>_WITH_XML_REL_ACC Parameter: <ERDS_receipt_6>_WITH_XML_CONT_CONS Parameter: <ERDS_receipt_7>_WITH_EV_SET#3 Sequence of actions # Sender SERDS IERDS RERDS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <ERD_dispatch_1>_WITH_ XML_SUB_ACC 4 Relies <ERD_dispatch_1>_WITH_ XML_SUB_ACC to IERDS 5 Receives <ERD_dispatch_1>_WITH_X ML_SUB_ACC and stores it 6 Generates XML_REL_ACC ERDS evidence 7 Generates <ERDS_receipt_1>_WITH_X ML_SUB_ACC 8 Sends <ERDS_receipt_1>_WITH_X ML_SUB_ACC back to SERDS 9 Receives <ERDS_receipt_1>_WITH_ XML_SUB_ACC Generates <ERDS_notification>_forAcce ptance 10 Relies <ERDS_notification_1>_forAc ceptance to RERDS 11 Receives <ERDS_notification_1>_forAcc eptance ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 80 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#3 Purpose 12 Generates XML_REL_ACC ERDS evidence 13 Generates <ERDS_receipt_2>_WITH_XM L_REL_ACC 14 Sends <ERDS_receipt_2>_WITH_XM L_REL_ACC back to IERDS 15 Receives <ERDS_receipt_2>_WITH_X ML_REL_ACC Sends <ERDS_notification_1>_forAcc eptance 16 Generates XML_NOT_F_ACC ERDS evidence All the entities at receiving side receive <ERDS_notification_1>_for Acceptance 17 Generates XML_NOT_DEL ERDS evidence 18 Generates <ERDS_receipt_3>_WITH_EV_ SET#1 . 19 Sends <ERDS_receipt_3>_WITH_EV_ SET#1 back to IERDS 20 Receives <ERDS_receipt_3>_WITH_E V_SET#1 21 Sends <ERDS_receipt_3>_WITH_E V_SET#1 back to SERDS N-1 entities at receiving side access IERDS and accept consignment. One party rejects it 22 Receives <ERDS_receipt_3>_WITH_ EV_SET#1 Generates XML_CONS_ACC ERDS evidence for N-1 entities at receiving side and one XML_CONS_REJ ERDS evidence for one entity at receiving side 23 Generates <ERDS_receipt_4>_WITH_E V_SET#2 24 Sends <ERDS_receipt_4>_WITH_E V_SET#2 back to SERDS 25 Receives <ERDS_receipt_4>_WITH_ EV_SET#2 Relies <ERD_dispatch_1>_WITH_X ML_SUB_ACC to RERDS to RERDS ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 81 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#3 Purpose 26 Sends <ERDS_receipt_4>_WITH_ EV_SET#2 back to sender Accepts <ERD_dispatch_1>_WITH_XM L_SUB_ACC 27 Receives <ERDS_receipt_4>_W ITH_EV_SET#2 Generates XML_REL_ACC ERDS evidence 28 Generates <ERDS_receipt_5>_WITH_XM L_REL_ACC 29 Sends <ERDS_receipt_5>_WITH_XM L_REL_ACC back to IERDS 30 Generates <ERD_dispatch_2>_WITH_XM L_SUB_ACC 31 Receives <ERDS_receipt_5>_WITH_X ML_REL_ACC Consigns <ERD_dispatch_2>_WITH_XM L_SUB_ACC to N-1 entities at receiving side 32 <ERD_dispatch_2>_WITH_ XML_REL_ACC is consigned to N-1 entities at receiving side 33 Generates XML_CONT_CONS ERDS evidence for N-1 entities 34 Generates <ERDS_receipt_6>_WITH_XM L_CONT_CONS 35 N-2 entities in receiving side retrieve user content, one entity fails 36 Receives <ERDS_receipt_6>_WITH_X ML_CONT_CONS Generates XML_CONT _HAND evidence for N-2 entities and XML_CONT_HAND_FAIL for one entity 37 sends <ERDS_receipt_6>_WITH_X ML_CONT_CONS back to SERDS Generates <ERDS_receipt_7>_WITH_EV_ SET#3 38 Receives <ERDS_receipt_7>_WITH_ XML_CONT_CONS Sends <ERDS_receipt_7>_WITH_EV_ SET#3 back to IERDS 39 Sends <ERDS_receipt_7>_WITH_ XML_CONT_CONS back to sender Receives <ERDS_receipt_7>_WITH_E V_SET#3 ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 82 Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#3 Purpose 40 Receives <ERDS_receipt_7>_W ITH_XML_CONT_CO NS sends <ERDS_receipt_7>_WITH_E V_SET#3 back to SERDS 41 Receives <ERDS_receipt_7>_WITH_ EV_SET#3 42 Sends i<ERDS_receipt_7>_WITH_ EV_SET#2 back to sender 43 Receives <ERDS_receipt_7>__ WITH_EV_SET#2 ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 83
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6 ERD Messages instances
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.1 Introduction and technical approach
|
The present clause defines a number of instances of the different types of ERD Messages, namely: ERDS notification, ERD payload, ERDS receipt, and ERD dispatch, as defined in ETSI EN 319 522-1 [1]. These instances are used in clause 8 for defining different test cases. The set of ERD messages instances is built following the technical approach shown below: • The set includes instances of each type of ERD message. • For each type of ERD message there will be at least one instance including all the optional components of relay metadata components defined in ETSI EN 319 522-3 [3]. • The present document first defines different combinations for the metadata components profiled in ETSI EN 319 522-4-1 [4] and in ETSI EN 319 522-4-2 [5], and for the relay metadata components defined in ETSI EN 319 522-2 [2]. • Each instance of a certain type of ERD message is defined as a composition of different metadata components combinations already mentioned. The rest of the present clause is organized as follows: • Clause 6.2 presents a number of combinations of metadata components for the different headers that can be present in the different ERD message types. These combinations are specified separately as they are used in the definition of instances of different ERD message types. • Clause 6.3 defines instances of ERD payloads. • Clause 6.4 defines instances of ERDS receipts. • Clause 6.5 defines instances of ERD dispatches. As mentioned in clause 4.2 new combinations of metadata components may be defined for each header, and new instances of ERD messages may be added to the current set, for defining new test cases.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.2 Combinations of fields for headers in ERD envelopes
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.2.1 Introduction
|
Clause 6.2.2 defines combinations of values for the metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4]. Clause 6.2.3 defines combinations of values for the relay metadata components defined in ETSI EN 319 522-3 [3]. Clause 6.2.4 defines aggregations of combinations defined in clauses 6.2.2 and 6.2.3.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.2.2 Combinations of AS4 metadata profiled in ETSI EN 319 522-4
|
The present clause defines different combinations of values for the metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4]. These combinations are shown in Table 9. Cells in column "Component name" contain the name of the metadata components. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 84 Cells in column "Value" shows the value to be assigned to the metadata component. These cells may contain the following values: • As specified in ETSI EN 319 522-4-1 [4]. This value is reserved for cases where the ETSI EN 319 522-4-1 [4] specifies a mandatory value for the metadata component. • As recommended in ETSI EN 319 522-4-1 [4]. This value is reserved for cases where the ETSI EN 319 522 4-1 [4] recommends one certain value for the metadata component (usually using the modal verb should). In these cases, the metadata component has this recommended value in the combination. • TEST_DEPENDANT means that the value of the metadata component will be defined in test cases for testing ERD message formats. Cells in "Notes/Additional requirements" contain one or more letters or/and one or more integer numbers. The letters correspond to additional requirements that are given after the table. The numbers correspond to numbers of notes that appear after the aforementioned additional requirements. Table 9: Combinations of metadata values as defined in OASIS specifications Combination identifier Component / Feature name Value Notes/Additional requirements AS4Met#1 PMode.Initiator As specified in ETSI EN 319 522-4-1 [4] PMode.Responder As specified in ETSI EN 319 522-4-1 [4] PMode.Initiator.Role As specified in ETSI EN 319 522-4-1 [4] PMode.Responder.Role As specified in ETSI EN 319 522-4-1 [4] PMode[1].BusinesssInfo.Service As specified in ETSI EN 319 522-4-1 [4] PMode[1].Security.SendReceipt As specified in ETSI EN 319 522-4-1 [4] 1 PMode[1].Security.SendReceipt.NonRepudiation As specified in ETSI EN 319 522-4-1 [4] 1 PMode[1].Security.SendReceipt.ReplyPattern As specified in ETSI EN 319 522-4-1 [4] 2 PMode[1].ErrorHandling.Report.AsResponse As specified in ETSI EN 319 522-4-1 [4] 2 AS4 Reception Awareness Feature As recommended in ETSI EN 319 522-4-1 [4] Duplication elimination function As recommended in ETSI EN 319 522-4-1 [4] NOTE 1: ETSI EN 319 522-4-1 [4] profiles this component for signed receipts. NOTE 2: ETSI EN 319 522-4-1 [4] profiles this component for signed receipts and error signal messages.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.2.3 Combinations of components of relay metadata
|
Table 10 shows combinations of values of the relay metadata defined in ETSI EN 319 522-3 [3]. For the purpose of defining the test cases, the field "ApplicablePolicy" shall always consist in a single URI. New combinations may be added where this field consists in a sequence of URIs. Cells in "Component name" column contain the name of relay metadata component in the ERD message. The names used are the ones defined in ETSI EN 319 522-3 [3]. Cells in "Component value" column contain either: 1) the value of the relay metadata component whose name is the one indicated in the previous column; or 2) AS_PER_TESTCASE, meaning that for this test case the ERDS is free to give to the aforementioned field the value it considers worth. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 85 Cells in "Notes/Additional requirements" contain one or more letters or/and one or more integer numbers. The letters correspond to additional requirements that are given after the table. The numbers correspond to numbers of notes that appear after the aforementioned additional requirements. Cells in "Purpose" contain a description of the purpose of the combination defined in the row. Table 10 defines parameterized combinations for new headers defined in ETSI EN 319 532-3 [7]. The combinations have as parameters the assurance levels and the consignment mode. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 86 Table 10: Parameterized combinations for relay metadata components Combination identifier Header field name Header field value Notes/Additional requirements Purpose RelayMet#1 RelayTime AS_PER_TESTCASE a, Use in tests where: the contents of the components are correct; there is no indication neither of assurance levels nor of mode of consignment. ExpirationTime AS_PER_TESTCASE b ScheduledDeliveryTime AS_PER_TESTCASE c ApplicablePolicy AS_PER_TESTCASE RelayMet#2 RelayTime AS_PER_TESTCASE a Use in tests where: the contents of the components are correct; the assurance levels required is one parameter, and there is no indication of mode of consignment. ExpirationTime AS_PER_TESTCASE b RequiredAssuranceLevel Parameter ScheduledDeliveryTime AS_PER_TESTCASE c ApplicablePolicy AS_PER_TESTCASE RelayMet#3 RelayTime AS_PER_TESTCASE a Use in tests where: the contents of the components are correct; relay metadata include all the optional components present; and the assurance levels and the mode of consignment are parameters. ExpirationTime AS_PER_TESTCASE b RequiredAssuranceLevel Parameter RequestedConsignmentMode Parameter ScheduledDeliveryTime AS_PER_TESTCASE c ApplicablePolicy AS_PER_TESTCASE RelayMet#4 RelayTime AS_PER_TESTCASE a, Use in negative tests where: the scheduled delivery is after the expiration date; assurance levels indication is one parameter, and there is no indication of mode of consignment. ExpirationTime AS_PER_TESTCASE b REM-RecipientAssuranceLeve Parameter ScheduledDeliveryTime AS_PER_TESTCASE d ApplicablePolicy AS_PER_TESTCASE RelayMet#5 RelayTime AS_PER_TESTCASE a Use in negative tests where: the scheduled delivery is after the expiration date; and the assurance levels and the mode of consignment are parameters. ExpirationTime AS_PER_TESTCASE b RequiredAssuranceLevel Parameter RequestedConsignmentMode Parameter ScheduledDeliveryTime AS_PER_TESTCASE d ApplicablePolicy AS_PER_TESTCASE RelayMet#6 RelayTime AS_PER_TESTCASE a As RelayMet#1 but without ScheduledDeliveryTime. ExpirationTime AS_PER_TESTCASE ApplicablePolicy AS_PER_TESTCASE RelayMet#7 RelayTime AS_PER_TESTCASE a As RelayMet#2 but without ScheduledDeliveryTime. ExpirationTime AS_PER_TESTCASE RequiredAssuranceLevel Parameter ApplicablePolicy AS_PER_TESTCASE RelayMet#8 RelayTime AS_PER_TESTCASE a As RelayMet#3 but without ScheduledDeliveryTime. ExpirationTime AS_PER_TESTCASE RequiredAssuranceLevel Parameter RequestedConsignmentMode Parameter ApplicablePolicy AS_PER_TESTCASE ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 87 Additional requirements: a) The date and time indicated in this component shall be earlier than the date and time indicated in "ERD-ExpirationDate" and "ERD-ScheduledDelivery" (if present). b) The date and time indicated in this component shall be later than the date and time indicated in "ERD-RelayDate" and "ERD-ScheduledDelivery" (if present). c) The date and time indicated in this component shall be earlier than the date and time indicated in "ERD-ExpirationDate" and "ERD-ScheduledDelivery" and later than the date and time indicated in "ERD-RelayDate. d) The date and time indicated in this component shall be later than the date and time indicated in "ERD-RelayDate" and later than "ERD-ExpirationDate" (if present). ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 88
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.2.4 Combinations of AS4 metadata profiled and relay metadata
|
The present clause defines aggregations of AS4 metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4], and relay metadata. These combinations are shown in Table 11. Each metadata combination instance is defined as the aggregation of the combination defined in Table 9 and one of the combinations defined in Table 10. Each combination defined in Table 10 has 4 parameters, namely: 1) An integer identifying the AS4 metadata combination in table of clause 6.2.2. 2) An integer identifying the relay metadata combination in table of clause 6.2.3. 3) The value of the required assurance levels (nil if this information is not present in the combination). 4) The value for consignment mode (nil if this information is not present). All the metadata combinations instances can be obtained from the following expression: Metadata(AS4-metadata#I, Relay-Metadata#J,AssuranceLevelComb, ConsignmentMode) where: • I, for the combinations specified in the present document is always 1. • J is one of {1 to 8}. • AssuranceLevelCombs is one of {nil, low/low, subs/subs, high/high}. • ConsignmentMode is one of {nil, basic, consented, consentedSigned}. Table 11 defines a number of possible combinations of these parameters when the required assurance levels are the same for sender and entities at receiving side. It also defines combinations where the consignment mode field is not present. Finally, it also defines two illegal combinations, that can be used in negative test cases. Table 11: ERD messagesmetada combinations For test cases without ShceduledDelivery OutermostHeade(1,6,nil,nil) AS4Met#1 + RelayMet#6 No indications neither of assurance levels nor consignment mode Metadata(1,7,low/low,nil) AS4Met#1 + RelayMet#7(low/low) No consignment mode indicated and assurance level Metadata(1,7,sub/subs,nil) AS4Met#1 + RelayMet#7(substantial/substantial) Metadata(1,7,high/high,nil) AS4Met#1 + RelayMet#7(high/high) Metadata (1,8,low/low,basic) AS4Met#1 + RelayMet#8(low/low, basic) Basic consignment mode and assurance level Metadata(1,8,subs/subs,basic) AS4Met#1 + RelayMet#8(substantial/substantial, basic) Metadata (1,8,high/high,basic) AS4Met#1 + RelayMet#8(high/high, basic) Metadata (1,8,low/low,consented) AS4Met#1 + RelayMet#8(low/low, consented) Consented consignment mode and assurance level Metadata(1,8,subs/subs,consented) AS4Met#1 + RelayMet#8(substantial/substantial, consented) Metadata (1,8,high/high,consented) AS4Met#1 + RelayMet#8(high/high, consented) Metadata (1,8,low/low,consentedSigned) AS4Met#1 + RelayMet#8(low/low, consentedSigned) Consented and signed consignment mode and assurance level Metadata(1,8,subs/subs,consentedSigned) AS4Met#1 + RelayMet#8(substantial/substantial, consentedSigned) Metadata (1,8,high/high,consentedSigned) AS4Met#1 + RelayMet#8(high/high, consentedSigned) For test cases with ShceduledDelivery OutermostHeade(1,1,nil,nil) AS4Met#1 + RelayMet#1 No indications neither of assurance levels nor consignment mode Metadata(1,2,low/low,nil) AS4Met#1 + RelayMet#2(low/low) No consignment mode indicated and assurance level Metadata(1,2,sub/subs,nil) AS4Met#1 + RelayMet#7(substantial/substantial) Metadata(1,2,high/high,nil) AS4Met#1 + RelayMet#2(high/high) Metadata (1,3,low/low,basic) AS4Met#1 + RelayMet#3(low/low, basic) ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 89 For test cases without ShceduledDelivery Metadata(1,3,subs/subs,basic) AS4Met#1 + RelayMet#8(substantial/substantial, basic) Basic consignment mode and assurance level Metadata (1,3,high/high,basic) AS4Met#1 + RelayMet#3(high/high, basic) Metadata (1,3,low/low,consented) AS4Met#1 + RelayMet#3(low/low, consented) Consented consignment mode and assurance level Metadata(1,3,subs/subs,consented) AS4Met#1 + RelayMet#3(substantial/substantial, consented) Metadata (1,3,high/high,consented) AS4Met#1 + RelayMet#3(high/high, consented) Metadata (1,3,low/low,consentedSigned) AS4Met#1 + RelayMet#3(low/low, consentedSigned) Consented and signed consignment mode and assurance level Metadata(1,3,subs/subs,consentedSigned) AS4Met#1 + RelayMet#3(substantial/substantial, consentedSigned) Metadata (1,3,high/high,consentedSigned) AS4Met#1 + RelayMet#3(high/high, consentedSigned) Metadata (1,4,low/low,nil) AS4Met#1 + RelayMet#4(low/low) Combinations for negative test cases (cause of submission rejection for instance) Metadata (1,5,low/low,basic) AS4Met#1 + RelayMet#5(low/low, basic)
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.3 Instances of ERD payload
|
As an ERD payload is the aggregation of metadata and user content, the present document defines as many ERD payload instances as metadata instances have been defined in clause 6.2.4.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.4 Instances of ERDS receipts
|
An ERD receipt is the aggregation of one metadata payload and one or more ERDS evidence payloads. The number and contents of these payloads will depend on the specific test case. The present document uses the following convention for identifying sets of ERDS receipts: ERD_ReceiptInst (Metadata(AS4Met#1,RelayMet#J,nil,nil), userContent,<EVID#M>+) Where: • J is a positive integer between 1 and 9 (inclusive), and the + symbol in <EVID#M> indicates that in each case, the ERDS receipt instance shall contain as many payloads for ERDS evidence as ERDS evidences indicated in the test case where the ERDS receipt is used. This unique content identifies all the possible ERDS receipts that will be needed in the definitions of the test cases.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
6.5 Instances of ERD dispatch
|
The present document uses the following convention for identifying sets of ERD dispatches: ERDS_DispatchInst(Metadata(AS4Met#1,RelayMet#J, AssLevelComb, ConsignmentModeId), <EVID#M>+) Where: • J is a positive integer between 1 and 9 (inclusive), AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, and the + symbol in <EVID#M> indicates that in each case, the ERD dispatch instance shall contain as many payloads for ERDS evidence as ERDS evidences indicated in the test case where the ERDS receipt is used. This unique content identifies all the possible ERD dispatches that will be needed in the definitions of the test cases. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 90
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
7 Other named sets
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
7.1 Named sets of participating ERDSs
|
The present clause defines named sets of participating REMSs that are used for naming test cases in clause 5. The details on the participating ERDSs are given using the following pattern: ERDS(I,J), where: • I stands for the number of Intermediate ERDSs (IERDSs); and • J stands for the number of the Recipient's ERDSs (RERDSs).
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
7.2 Named sets of additional requirements
|
The present clause defines named sets of additional requirements that are used for building different test cases based on the same scenarios of REM messages. Table 12 shows the named sets of additional requirements. Table 12: Named sets of additional requirements Name of the set Additional requirements in the set AdditionalReqs#1 Original message: not signed, no attachment Sender sends original message AdditionalReqs#2 Original message: not signed, no attachment Sender's delegate Sender's delegate sends original message
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
7.3 Named sets of entities in receiving side
|
The present clause defines named sets of entities that are present at receiving side. This allows using one scenario in defining different test cases by changing the entities in the receiving side. EXAMPLE: Scenarios defined for one recipient could be used in test cases where the scenarios involve only one delegate of one recipient. In order to define the names of the sets, the pattern RecSide (I, J, K) is used where: • I stands for the number of recipients. • J stands for the number of recipient's delegates. • K stands for the number of recipients each delegate is delegate of. K shall always be less or equal than I. If I is not 0 then K shall also be different from 0.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8 Test cases definition
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.1 Introduction
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.1.1 General
|
The notations shown in clauses 4.1, 6 and 7, allow building a compact notation for defining tests cases. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 91 The present document defines sets of test cases. Each set of test cases is expressed as a function of a number of parameters (some of them are integers, other are tuples of several values, other -mainly reasons for failures- are enumerated values specified in another ETSI deliverable). Under these conditions one specific test case is obtained when the set is particularized by assigning a single value to each parameter.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.1.2 Notation for black box model scenarios
|
No ERD messages are generated in the scenarios defined for the black box model. Consequently, the only parameters the test cases depend on are the additional requirements specified in clause 7.2 and the entities present at receiving side, identified in clause 7.3. Below follows the notation used for identifying the set of test cases for scenario ERDS_BB_NOT_F_ACC#1: ERDS_BB_NOT_F_ACC#1 ( RecSide(F,G,H), AssLevelComb,ConsignmentModelId, AdditionalReqs#P ) This part shows the components required for defining the test cases for this scenario. For this scenario each test case in the set will require providing details of: • The entities in the receiving side (RecSide). The notation for identifying one of the different alternatives is as specified in clause 7.3. • The additional requirements, whose notation has been specified in clause 7.2. Scenarios where there is some failure also include the FailureReason parameter. Below follows the second part of the definition of the set of test cases: Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases for one recipient, several recipients, and several recipients and one recipient's delegate. • For AdditionalReqs: P is one of {1,2}.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.1.3 Notation for 4 corner and extended models scenarios
|
For helping in understanding the notation, below follows the definition of the set of test cases for the scenario 4C_RERDS_NO_NOT_F_ACC #2. The definition of a set of test cases has two parts. Below follows the first one: 4C_RERDS_NO_NOT_F_ACC #2 ( RecSide(F,G,H), ERD_dispatchInst_WITH_XML_SUB_ACC (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId), UserContent,XML_SUB_ACC), ERDS_receipt_WITH_XML_REL_ACC (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId),XML_REL_ACC), AdditionalReqs#P ) This part shows the components required for defining the test cases for this scenario. For this scenario each test case in the set will require providing details of: • The entities in the receiving side (RecSide). The notation for identifying one of the different alternatives is as specified in clause 7.3. • The ERDS Dispatch instance, which also carries an ERDS Evidence (XML_SUB_ACC). The notation for completely defining one specific instance among all the possibilities offered by the different parameters, is as specified in clause 6.5. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 92 • The ERDS Receipt, carrying a XML_REL_ACC ERDS evidence. The notation for completely defining one specific instance among all the possibilities offered by the different parameters, is as specified in clause 6.4. • The additional requirements, whose notation has been specified in clause 7.2. Scenarios where there is some failure also include the FailureReasonId parameter. Some scenarios include REM payloads instead of REM dispatches. The details of the components of a REM payload are provided as the details of components of a REM dispatch. Below follows the second part of the definition of the set of test cases: Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases for one recipient, several recipients, and several recipients and one recipient's delegate. • For ERDS_dispatchInst_WITH_XML_SUB_ACC and REMS_receipt_WITH_XML_REL_ACC: - I is one of {1..8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, and ConsignmentModeId is one of {nil, basic, consented, consentedSigned. • For AdditionalReqs: P is one of {1,2}. This part shows the different values that the parameters present in the first part, can have. Each legal combination of all the parameters will collapse the set in ONE test case. For instance: RecSide(1,0,0), ERDS_dispatchInst_WITH_XML_SUB_ACC (OuterMostHeader(AS4#1, RelayMet#8, high/high, consentedSigned), UserContent,XML_SUB_ACC)), ERDS_receipt_WITH_XML_REL_ACC (OuterMostHeader(RFCFields#1, NewFields#6, nil, nil), XML_REL_ACC), AdditionalReqs#1 Defines ONE test case in the set, where: • The REM-RelayDate and REM-ScheduledDelivery header fields are absent in the outermost header of the REM Dispatch and the REMS Receipt (NewFields#11 combination of new header fields). • The assurance level combination indication is present and its value is high/high. • The consignment mode indication is present and its value is consentedSigned. • There is only one recipient at receiving side. In addition, the following set of rules govern the selection of coherent triplets (RelayMet#I, AssLevelComb, ConsignmentModeId): 1) Absence of Assurance levels indication is indicated by a nil value. 2) Absence of Consignment mode indication is indicated by a nil value. 3) For I one of {1, 6} both AssLevelComb and ConsignmentModeId are nil. 4) For I one of {2, 4, 7} AssLevelComb is not nil, and ConsignmentModeId is nil. 5) For I one of {3, 5, 8} neither AssLevelComb nor ConsignmentModeId are nil. Any combination (RelayMet#I, AssLevelComb, ConsignmentModeId)in a specific test case has to meet the rules 3 to 5. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 93
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.1.4 Reasons for Failures
|
The present clause shows the different values that may have the reason for failure parameters in those scenarios where failures occur: • For XML_SUB_REJ, the FailureReasonId is one of {RA02, RA03, RA04, RA05, RA06} as specified in clause 8.3.3.1 of ETSI EN 319 522-2 [2]. • For XML_REL_REJ, the FailureReasonId is one of {RB02, RB03, RB04, RB05, RB06, RB07, RB08, RB09, RB010, RB21, RB22} as specified in clause 8.3.3.2 of ETSI EN 319 522-2 [2]. • For XML_CONS_FAIL, and XML_CONS_NOT_FAIL, the FailureReasonId is one of {RD03, RD04, RD05, RD06, RD21, RD32, RD34} as specified in clause 8.3.3.4 of ETSI EN 319 522-2 [2]. • For XML_CONT_HAND_FAIL, the FailureReasonId is one of {RE03, RE04} as specified in clause 8.3.3.5 of ETSI EN 319 522-2 [2]. • For XML_CONS_REJ, the FailureReasonId is RC08 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2]. • For XML_ACC_REJ_EXP, the FailureReasonId is RC09 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2].
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.2 Test cases for black box model
|
For each scenario the present document defines the set of test cases defined by the following expression: SCENARIOID ( RecSide(F,G,H), AssLevelComb,ConsignmentModelId, AdditionalReqs#P, FailureReasonId ) Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases for one recipient, several recipients, and several recipients and one recipient's delegate. • For AdditionalReqs: P is one of {1,2}. • For FailureReasonId: see clause 8.1.4.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3 Test cases for 4-cornel and extended models
| |
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.1 General
|
The present clause, instead of showing one test case set expression for each scenario, which would make the present document very long, defines rules for building these expressions for each scenario in function of: the ERD dispatches, ERDS receipts, ERD payloads present in them, the entities at the receiving side, the failure reasons, and the additional requirements. Some of the rules are defined for parametrizing the different ERD messages appearing in each scenario, other for parametrizing the receiving side, others for parametrizing the failure reasons, and others for parametrizing the additional requirements. The application of all these rules for one scenario results in generating test cases set expressions as the one shown in clause 8.1.3 which define a set of test cases for such an scenario.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.2 Rules for parametrizing ERD dispatches
|
The ERD dispatches for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId), UserContent,<EVID>+) ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 94 Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned},and <EVID>+ stands for the ERDS evidences present in the ERD dispatch as per the scenario.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.3 Rules for parametrizing ERD payloads
|
The ERD payloads for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId), UserContent Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, and ConsignmentModeId is one of {nil, basic, consented, consentedSigned}.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.4 Rules for parametrizing ERDS receipts
|
The ERDS receipts for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, nil), <EVID>+) Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, and <EVID>+ stands for the ERDS evidences present in the ERDS receipt as per the scenario.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.5 Rules for parametrizing entities at receiving side
|
The number and type of entities present at the receiving side will be parametrized as indicated below: RecSide(F,G,H), Where, as specified in clause 7.3: • F stands for the number of recipients. • G stands for the number of recipient's delegates. • H stands for the number of recipients each delegate is delegate of. H shall always be less or equal than F. If F is not 0 then H shall also be different from 0.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.6 Rules for parametrizing failure reasons
|
The FailureReasonId shall follow the requirements specified in clause 8.1.4.
|
8983622e5d417335095cba14cb702b60
|
119 524-2
|
8.3.7 Rules for parametrizing additional requirements
|
The additional requirements will be parametrized as indicated below: AdditionalReqs#P Where P is one of {1,2} with the meaning specified in clause 7.2. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 95 Annex A (informative): Bibliography • ETSI EN 319 532-1: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 1: Framework and Architecture". • ETSI EN 319 532-2: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 2: Semantic Contents". • ETSI EN 319 532-4: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 4: Interoperability profiles". ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 96 Annex B (informative): Change History Date Version Information about changes February 2019 1.1.1 Publication as ETSI TS 119 524-1. April 2023 1.1.2 Early draft - update version 1.1.1 with resolutions to part of the comments received from stakeholders on version 1.1.1 October 2023 1.1.3 Final draft for TS Approval. This version includes the implementation of resolutions to all the comments received to versions v 1.1.1 and v1.1.2. Of important relevance are test cases that include the generation and management of the three new events and their corresponding ERDS evidence added in 319 522-1 clause 6, namely: NotificationDelivered (C.6), NotificationAccessTracking (D.5), and ContentAccessTracking (D.6) October 2023 1.1.4 Final draft for TS Approval. This version includes the right WI; defines the acronym NOT_F_ACC_FAIL; merges empty cells in the last columns of some scenario tables; and makes that each scenario table starts at the beginning of one page. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 97 History Document history V1.1.1 February 2019 Publication V1.2.1 December 2023 Publication
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
1 Scope
|
The present document defines specific supplementary requirements to those defined in ETSI EN 319 403-1 [1] for CABs performing audits based on ETSI EN 319 411-1 [i.9] and those from CA/Browser Forum, [i.7] and [i.8]. In particular, the present document defines the requirements for audit attestations, including their content.
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
2 References
| |
abf56025611bf39064e4e57cf7cf5fae
|
119 403-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 at https://docbox.etsi.org/Reference. 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 EN 319 403-1 (V2.3.1) (06-2020): "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 1: Requirements for conformity assessment bodies assessing Trust Service Providers".
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-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 are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] Regulation (EC) No 765/2008 of the European Parliament and of the Council of 9 July 2008 setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93. [i.3] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.4] ISO/IEC 17021: "Conformity assessment -- Requirements for bodies providing audit and certification of management systems". [i.5] ISO/IEC 27006: "Information technology -- Security techniques -- Requirements for bodies providing audit and certification of information security management systems". [i.6] ISO/IEC 17065: "Conformity assessment -- Requirements for bodies certifying products, processes and services". ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 7 [i.7] CA/Browser Forum (V1.7): "Guidelines for The Issuance and Management of Extended Validation Certificates". [i.8] CA/Browser Forum (V1.7): "Baseline Requirements Certificate Policy for the Issuance and Management of Publicly-Trusted Certificates". [i.9] ETSI EN 319 411-1: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers issuing certificates; Part 1: General requirements". [i.10] ISO 8601-1:2019: "Date and time Part 1: Basic rules".
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
3 Definition of terms, symbols and abbreviations
| |
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: Publicly-Trusted Certificate (PTC): certificate trusted by virtue of the fact that its corresponding Root Certificate is distributed as a trust anchor in widely-available application software NOTE 1: See ETSI EN 319 411-1 [i.9]. NOTE 2: Within the context of the present document, PTC is used synonymously with EVC, DVC, IVC and OVC as per CA/B Forum documents [i.7] and [i.8]. The purpose of PTC is described in BRG [i.8], clause 1.4.1.
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
3.2 Symbols
|
Void.
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] and the following apply: AAL Audit Attestation Letter CA/B Forum Certification Authority and Browser Forum CAB Conformity Assessment Body CCADB Common CA DataBase NOTE: Run by Mozilla® (see https://www.ccadb.org). PTC Publicly-Trusted Certificate 4 Requirements for CABs auditing TSPs that issue PTCs
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
4.1 General
|
PTA-4.1-01: The requirements defined in ETSI EN 319 403-1 [1] shall apply. The following clauses define additional requirements. ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 8
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
4.2 Audit Frequency (see ETSI EN 319 403-1, clause 7.4.5)
|
PTA-4.2-01: A full-surveillance audit shall be conducted no less frequently than annually. PTA-4.2.02: Updated audit information shall be provided no less frequently than annually. PTA-4.2.03: Successive audits shall include an evaluation of evidence produced since the last audit.
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
4.3 Audit Attestation
|
PTA-4.3-01: The Audit Attestation for TSPs issuing publicly-trusted certificates shall provide sufficient details to demonstrate that the audited TSP fulfilled the requirements from ETSI EN 319 411-1 [i.9] and those from CA/Browser Forum, [i.7] and [i.8]. In particular: • PTA-4.3-02: The Audit Attestation shall be written in English. • PTA-4.3-03: The Audit Attestation shall be in a "text searchable" PDF format. • PTA-4.3-04: The Audit Attestation shall be uploaded to their auditor's website and be held available there for retrieval for at least one year. • PTA-4.3-04a: In order to serve CCADB requirements, the Audit Attestation shall be available through a direct link on a website accessible via HTTPS. • PTA-4.3-05: The Audit Attestation shall list the date on which the audit letter was written. • PTA-4.3-05a: The Date Format shall be defined according to the following scheme: YYYY-MM-DD example: 2023-01-03. NOTE 1: This format is conformant with ISO 8601-1 [i.10]. • PTA-4.3-05b: The date of the issuance of the audit attestation shall be not later than 90 days after the end of the audit period. • PTA-4.3-06: The Audit Attestation shall have the CAB's name in the audit letter as well as the CAB's address, the CAB's contact information and information about the CAB's accreditation. • PTA-4.3-07: The Audit Attestation shall be issued annually. • PTA-4.3-08: The Audit Attestation shall include a statement on each sub-clause of the referenced requirements where there is a finding of non-conformity noted during the audit. NOTE 2: With regards to PTA-4.3-08, pending non-conformities are only acceptable in line with clause 7.6 b) of ETSI EN 319 403-1 [1]. • PTA-4.3-09: The Audit Attestation shall include a clear identification of the audited TSP. • PTA-4.3-10: The Audit Attestation shall list the full name, SHA256 thumbprints of the CA certificates of the TSP services that have been audited, and the applied policies of the audited TSP. • PTA-4.3-10a: The Hash values of the SHA 256 thumbprints within the Audit Attestation shall not contain colons, spaces, line feeds, lower case letters or page break code. • PTA-4.3-11: The Audit Attestation for a period of time audit shall state the start and end dates of the period that was audited (see PTA-4.3-05a). • PTA-4.3-11a: The Audit Attestation for a point in time audit shall state the date of the point in time of the audit (see PTA-4.3-05a). • PTA-4.3-12: The Audit Attestation shall list the audit standards that were used during the audit and list the full name and version of the audit standards referenced. ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 9 • PTA-4.3-13: The Audit Attestation shall list the policy and practice statement documents of the TSP that the audit was based on. • PTA-4.3-14: The Audit Attestation shall list the city, state/province (if applicable), and country of all relevant physical locations used in Certification Authority operations. • PTA-4.3-15: The Audit Attestation should cover all Root CAs in scope of the audit in one document. • PTA-4.3-15a: In exceptional cases more than one Audit Attestation may by issued per TSP. NOTE 3: Root programs relying on audits based on ETSI EN 319 403-1 [1] and the present document may place additional mandatory requirements on the audit attestations for TSPs issuing Publicly-Trusted certificates, e. g. the use of one of the Audit Attestation Letter templates provided by the Accredited Conformity Assessment Bodies' Council (ACAB'c, see https://www.acab-c.com/).
|
abf56025611bf39064e4e57cf7cf5fae
|
119 403-2
|
4.4 Audit Scope
|
PTA-4.4-01: The audit attestation shall list all TSP incidents documented in a public repository (e.g. Mozilla® Bugtracker) with an explanation of remediation status. NOTE: If the audit scope includes third party trust service components, such as a Registration Services as defined in ETSI EN 319 411-1 [i.9] the TSP remains responsible for this component and the component is addressed by the TSP's audit as in ETSI EN 319 403-1 [1], clause 7.4.1.0. ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 10 Annex A (informative): Bibliography • ENISA: "Guidelines on supervision of qualified trust services; Technical guidelines on trust services", December 2017. • ENISA: "Towards global acceptance of eIDAS audits", January 2019. • ENISA: "Assessment of ETSI TS 119 403-3 related to eIDAS", November 2019. • ENISA: "Recommendations for QTSP based on Standards", March 2021. ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 11 Annex B (informative): Change History Date Version Information about changes July 2018 1.1.1 First publication of the TS after approval ETSI ESI #62 April 2019 1.2.1 Included Change Requests: CR#1 "report non-conformities": see PTA-4.3-08 agreed at ESI#64 October 2020 1.2.1 Included Change Requests: CR#1 "Add a statement about RA Audits": Change of PTA-4.4.01 and add a note CR#2 "Defining coding rules for the audit dates in AAL": see PTA-4.3-05a CR#3 "Delete statement about findings of critical non-conformities": see PTA-4.3-08 CR#4 "Defining Rules for encoding Hash Values": see PTA-4.3-10a CR#5 "New requirements for a point in time audit": see PTA-4.3-11a CR6# "List all CA incidents documented in a public repository" see PTA-4.4-01 November 2011 1.2.4 Minor editorial changes January 2023 1.2.5 #1 Addition to PTA-4.3-04 "retrieval for at least one year" #2 New PTA-4.3.-04a with "direct link via https" #2 Update to PTA-4.3-05a to change ISO date format to a 'shall' requirement #3 New PTA-4.3-15 "Cover all Root CA AAL of a TSP in one document" #4 Addition to note 3 "Usage of AAL templates provided by ACAB'c" February 2023 1.2.6 Minor editorial changes after discussion at ESI #79 ETSI ETSI TS 119 403-2 V1.3.1 (2023-03) 12 History Document history V1.1.1 July 2018 Publication V1.2.1 April 2019 Publication V1.2.4 November 2020 Publication V1.3.1 March 2023 Publication
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
1 Scope
|
Based on a scoping study and survey with respect to long-term preservation techniques for digital signatures and general data documented in ETSI SR 019 510 [i.13], the present document and its companion document ETSI TS 119 511 [i.14] have been created. ETSI TS 119 511 [i.14] specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. unsigned data or signed data, using digital signature techniques. The present document complements ETSI TS 119 511 [i.14] and specifies protocols for trust service providers providing long-term data preservation services of digital signatures and of general data (i.e. unsigned data or signed data). Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document first addresses general aspects (see clause 4) such as a system architecture for preservation, which contains a preservation interface offered by the preservation service and used by the client (see clause 4.1). The preservation service may aim at different preservation goals (see clause 4.2), may or may not provide storage functionality (see clause 4.3), and provide different profiles of preservation schemes, which may implement different preservation evidence policies (see clause 4.4). In a second step, the present document specifies methods and data objects constituting a protocol between a client and a long-term data preservation service for the issuance and maintenance of evidences (see clause 5). For each call at the preservation interface it first specifies the semantics in a generic fashion and then specifies the concrete syntax of the conveyed data elements based on XML and JSON together with its binding to SOAP [i.25] and REST respectively.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
2 References
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
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 at https://docbox.etsi.org/Reference/. 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 EN 319 162-1: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 1: Building blocks and ASiC Baseline containers". [2] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [3] IETF RFC 4998: "Evidence Record Syntax (ERS)". [4] IETF RFC 6283: "Extensible Markup Language Evidence Record Syntax (XMLERS)". [5] OASIS: "Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0", Committee Specification 02, 11 December 2019. [6] OASIS: "Digital Signature Service Metadata Version 1.0", Committee Specification 02, 11 December 2019. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 12 [7] Recommendation ITU-T X.680 (2021): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
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 are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. OJ L 257, 28.8.2014, p. 73-114. [i.2] BSI TR-03125-F: "Preservation of Evidence of Cryptographically signed Documents, Formats (TR-ESOR-F)". [i.3] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.4] ETSI TS 119 612: "Electronic Signatures and Infrastructures (ESI); Trusted Lists". [i.5] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [i.6] ETSI TS 119 122-3: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 3: Incorporation of Evidence Record Syntax (ERS) mechanisms in CAdES". [i.7] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [i.8] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [i.9] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [i.10] ETSI EN 319 422: "Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles". [i.11] ETSI TS 119 441: "Electronic Signatures and Infrastructures (ESI); Policy requirements for TSP providing signature validation services". [i.12] ETSI TS 119 442: "Electronic Signatures and Infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services". [i.13] ETSI SR 019 510: "Electronic Signatures and Infrastructures (ESI); Scoping study and framework for standardization of long-term data preservation services, including preservation of/with digital signatures". [i.14] ETSI TS 119 511: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers providing long-term preservation of digital signatures or general data using digital signature techniques". [i.15] ISO 13527:2010: "Space data and information transfer systems - XML formatted data unit (XFDU) structure and construction rules". [i.16] ISO 14721:2012: "Space data and information transfer systems - Open archival information system (OAIS) - Reference model". [i.17] ISO/IEC 21320-1:2015: "Information technology - Document Container File - Part 1: Core". ETSI ETSI TS 119 512 V1.2.1 (2023-05) 13 [i.18] IANA: Media Type Registry. [i.19] IETF RFC 3061: "A URN Namespace of Object Identifiers". [i.20] IETF RFC 3161: "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". [i.21] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [i.22] IETF RFC 6960: "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP". [i.23] The National Archives: "PRONOM Unique Identifiers". [i.24] W3C® Recommendation 26 November 2008: "Extensible Markup Language (XML) 1.0 (Fifth Edition)". [i.25] W3C® Recommendation 27 April 2007: "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)". [i.26] W3C® Recommendation 25 January 2005: "SOAP Message Transmission Optimization Mechanism". [i.27] W3C® Recommendation 11 April 2013: "XML Signature Syntax and Processing Version 1.1".
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
3 Definition of terms, symbols and abbreviations
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: certificate status authority: authority providing certificate status information EXAMPLE: The certificate status information can be provided using the Online Certificate Status Protocol (OCSP) [i.22] or in form of Certificate Revocation Lists (CRL) [i.21]. container: data object, which contains a set of data objects and optional additional information, which describes the contained data objects and optionally its content and its interrelationships EXAMPLE: The format of a container can be based on, ZIP as defined in ISO/IEC 21320-1 [i.17] or XML [i.24]. ASiC [1] is an example of a container based on ZIP. NOTE: Additional information may comprise associated digital signatures, time-stamps, evidence records, validation data (CRLs, OCSP responses) and validation reports. data object: actual binary/octet data being operated on (e.g. transformed, digested, or signed) by an application and which may be associated with additional information like an identifier, the encoding, size or type delta preservation object container: special preservation object container describing the difference to an already existing preservation object container EU qualified preservation service: preservation service that meets the requirements for qualified preservation service for qualified electronic signatures and/or for qualified electronic seals as laid down in Regulation (EU) 910/2014 [i.1] evidence record: unit of data, which can be used to prove the existence of an archived data object or an archived data object group at a certain time NOTE: See IETF RFC 4998 [3], IETF RFC 6283 [4] and ETSI TS 119 122-3 [i.6]. expected evidence duration: for a preservation service with temporary storage or without storage, duration during which the preservation service expects that the preservation evidence can be used to achieve the preservation goal ETSI ETSI TS 119 512 V1.2.1 (2023-05) 14 long-term: time period during which technological changes may be a concern EXAMPLE: Possible technological changes are obsolescence of cryptographic technology such as crypto algorithms, key sizes or hash functions, key compromises. NOTE: The transformation of the original data into another data object which equivalent object content and semantic to avoid the risk that the original data object/viewer system is becoming obsolete is not covered. long-term preservation: extension of the validity status of a digital signature over long periods of time and/or of provision of proofs of existence of data over long periods of time, in spite of obsolescence of cryptographic technology such as crypto algorithms, key sizes or hash functions, key compromises or of the loss of the ability to check the validity status of public key certificates metadata: data about other data NOTE: See ISO 14721:2012 [i.16]. notification interface: interface provided by the preservation client supporting the notification protocol NOTE: The notification interface is not addressed by the present document. notification protocol: protocol used by a preservation service to notify the preservation client NOTE: The notification protocol is not addressed by the present document. preservation client: component or a piece of software which interacts with a preservation service via the preservation protocol preservation evidence: evidence produced by the preservation service which can be used to demonstrate that one or more preservation goals are met for a given preservation object preservation evidence policy: set of rules that specify the requirements and the internal process to generate or how to validate a preservation evidence preservation evidence retention period: for a preservation service With Temporary Storage (WTS) the time period during which the evidences that are produced asynchronously can be retrieved from the preservation service preservation goal: one of the following objectives achieved during the preservation time frame: extending over long periods of time the validity status of digital signatures, providing proofs of existence of data over long periods of time, or augmentation of externally provided preservation evidences NOTE: A preservation service can support one or more preservation goals. preservation interface: component implementing the preservation protocol on the side of the preservation service preservation manifest: data object in a preservation object container referring to the preservation data objects or additional information and metadata in the preservation object container EXAMPLE 1: Additional file in an ASiC-container according to ETSI EN 319 162-1 [1], clause A.7. EXAMPLE 2: versionManifest in BSI TR-03125-F [i.2]. EXAMPLE 3: An XML-based manifest data element in an XML-based POC. preservation mechanism: mechanism used to preserve preservation objects and to maintain the validity of preservation evidences NOTE: The present document only addresses preservation mechanisms based on digital signature techniques. preservation object: typed data object, which is submitted to, processed by or retrieved from a preservation service NOTE: This covers submission data objects, preservation object containers and preservation evidences. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 15 preservation object container: container which contains a set of data objects and optionally related metadata providing information about the data objects and optionally preservation manifest(s) specifying its content and relationships EXAMPLE 1: An ASiC-S or ASiC-E container is a Preservation Object Container that supports one or more signature and time assertion files each applicable to its own set of one or more files. EXAMPLE 2: An OAIS Submission Information Packages is a Preservation Object Container. preservation object identifier: unique identifier of a (set of) preservation object(s) submitted to a preservation service preservation planning: monitoring changes and risks e.g. concerning innovations in storage, access and preservation technologies, new design strategies, etc. preservation period: for a preservation service with storage, duration during which the preservation service preserves the submitted preservation objects and the associated evidence NOTE: The submitted preservation objects can be updated during the preservation period. preservation profile: uniquely identified set of implementation details pertinent to a preservation storage model and one or more preservation goals which specifies how preservation evidences are generated and validated NOTE: See clause 5.4.7 of the present document for the specification of the Profile component. preservation protocol: protocol to communicate between the preservation service and a preservation client preservation scheme: generic set of procedures and rules pertinent to a preservation storage model and one or more preservation goals which outlines how preservation evidences are created and validated NOTE 1: Different preservation profiles can implement the same preservation scheme. NOTE 2: A preservation scheme can be considered as a generalization of a set of preservation profiles. preservation service: service capable of extending the validity status of a digital signature over long periods of time and/or of providing proofs of existence of data over long periods of time preservation storage model: one of the following ways of implementing a preservation service: with storage, with temporary storage, without storage preservation submitter: legal or natural person using the preservation client to submit the submission data object preservation subscriber: legal or natural person bound by agreement with a preservation trust service provider to any subscriber obligations proof of existence: evidence that proves that an object existed at a specific date/time proof of integrity: evidence that data has not been altered since it was protected NOTE: A proof of existence requires and implies a proof of integrity. signer: entity being the creator of a digital signature submission data object: original data object provided by the client NOTE: If provided by the client, the Preservation Object Container (POC) is a submission data object. time-stamp: data in electronic form which binds other electronic data to a particular time establishing evidence that these data existed at that time time-stamping authority: trust service provider which issues time-stamps using one or more time-stamping units time-stamping service: trust service for issuing time-stamps time-stamping unit: set of hardware and software which is managed as a unit and has a single time-stamp signing key active at a time ETSI ETSI TS 119 512 V1.2.1 (2023-05) 16 trusted list: list that provides information about the status and the status history of the trust services from trust service providers regarding compliance with the applicable requirements and the relevant provisions of the applicable legislation NOTE: In the context of European Union Member States, as specified in Regulation (EU) No 910/2014 [i.1], it refers to an EU Member State list including information related to the qualified trust service providers for which it is responsible, together with information related to the qualified trust services provided by them. validation data: data that is used to validate a digital signature
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
3.2 Symbols
|
Void.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] and the following apply: API Application Programming Interface ASN.1 Abstract Syntax Notation One AUG Augmentation BSI Bundesamt für Sicherheit in der Informationstechnik CRL Certificate Revocation List CSA Certificate Status Authority EN European Norm ERS Evidence Record Syntax NOTE: See IETF RFC 4998 [3]. IANA Internet Assigned Numbers Authority IETF Internet Engineering Task Force ISO International Organization for Standardization JSON JavaScript Object Notation LXAIP Logical XAIP NOTE: See BSI TR-03125-F [i.2]. OAIS Open Archival Information System NOTE: See ISO 14721:2012 [i.16]. OCSP Online Certificate Status Protocol OID Object Identifier PDS Preservation of Digital Signatures PGD Preservation of General Data PO Preservation Object POC Preservation Object Container PoE Proof of Existence POID unique IDentifier of a submitted PO PUID PRONOM Persistant Unique Identifier REST Representational State Transfer RFC Request For Comments SOAP Simple Object Access Protocol NOTE: See W3C® Recommendation 27 April 2007 [i.25]. SubDO Submission Data Object TSA Time-Stamping Authority URI Unique Resource Identifier URL Unique Resource Locator WOS WithOut Storage WSDL Web Service Description Language ETSI ETSI TS 119 512 V1.2.1 (2023-05) 17 WST With STorage WTS With Temporary Storage XAIP XML-based Archive Information Package NOTE: See BSI TR-03125-F [i.2]. XFDU XML Formatted Data Unit NOTE: See ISO 13527:2010 [i.15]. XML eXtensible Markup Language NOTE: See W3C® Recommendation 26 November 2008 [i.24].
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4 General aspects
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.1 System architecture
|
The overall system architecture with the preservation service specified in the present document is depicted in Figure 1. Figure 1: System architecture with preservation service and related services As depicted in Figure 1, the preservation service defined in the present document provides the preservation interface as specified in clause 5 and may use an external Time-Stamping Authority (TSA), which issues time-stamps (see ETSI EN 319 422 [i.10]), or a signature or seal creation service (SigS), which issues suitable digital signatures. It may optionally use a Validation Service (ValS) (see ETSI TS 119 441 [i.11] and ETSI TS 119 442 [i.12]) to collect certification path information and revocation information or directly collect certification path information and gather certificate status information issued by a Certificate Status Authority (CSA). There are three main variants for a preservation service (see clause 4.3) whether it uses: a) a long-term storage; b) a temporary storage; or c) no storage. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 18 When it uses a storage, the preservation service may use an internal storage or an external storage under its control for preservation. Furthermore, the preservation service may call back the client via the notification interface in order to inform it about relevant events. An important type of event is that a previously applied cryptographic algorithm is expected to become weak and hence the client and/or the preservation service need to perform additional measures. NOTE: The technical details of the notification interface and the notification protocol are not addressed in the present document.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.2 Preservation goals
|
A preservation service can pursue different preservation goals, which has an influence on the supported operational tasks. The present document specifies the following three goals which may be used separately or in combination: • http://uri.etsi.org/19512/goal/pgd The preservation goal "Preservation of General Data" (PGD) provides a proof of existence over long periods of time of the submission data object (SubDO) submitted to the preservation service. NOTE: The PGD goal does not distinguish between signed and unsigned data. • http://uri.etsi.org/19512/goal/pds The preservation goal "Preservation of Digital Signatures" (PDS) extends over long periods of time the ability to validate a digital signature, to maintain its validity status and to get a proof of existence of the associated signed data. • http://uri.etsi.org/19512/goal/aug The preservation goal "Augmentation" (AUG) indicates that the preservation service supports the augmentation of submitted preservation evidences.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.3 Storage models
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.3.1 Preservation with storage
|
In this preservation storage model, the preservation service stores the submission data objects (SubDO) as well as the preservation evidences that are produced for them by the preservation service. In this model, the preservation service supports the export and the import of preservation objects and evidences produced by itself and other preservation services. EXAMPLE 1: The evidences produced in this mode can be evidence records according to IETF RFC 4998 [3] or IETF RFC 6283 [4]. EXAMPLE 2: The preservation evidence produced in this mode can be the information included in an archival format of an AdES signature. This storage model is addressed by the value WithStorage (WST) within the PreservationStorageModelType (see clause 5.4.6).
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.3.2 Preservation with temporary storage
|
In this preservation storage model, the preservation service does not permanently store the SubDO, but it stores them only as long as needed to create the corresponding evidence. The preservation evidences are produced asynchronously and are stored during some time-period to allow the client to retrieve it. EXAMPLE 1: Evidences are produced every 24 hours, but are stored for a longer period of time. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 19 This storage model has two variants: either the client sends the full data object to the preservation service, or the client only sends the corresponding hash values associated with hash function identifiers. These hash values may represent a single Preservation Objects (PO) or a group of several POs contained in a Preservation Object Container (POC) using hash-tree techniques. Sending hash values and hash function identifiers can be useful in cases of very large POs or when confidentiality of the data is important or when privacy is a concern. However, this strategy can impose additional challenges in case the used hash function(s) become weak. EXAMPLE 2: The evidences produced in this mode can be Evidence Records according to IETF RFC 4998 [3] or IETF RFC 6283 [4]. This storage model is addressed by the value WithTemporaryStorage (WTS) within the PreservationStorageModelType (see clause 5.4.6).
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.3.3 Preservation without storage
|
In this preservation storage model, the preservation service does not store the SubDOs and the preservation evidences are produced synchronously. EXAMPLE: This preservation storage model can be implemented doing a continuous augmentation of CAdES signatures with archive-time-stamp-v3 attributes according to ETSI EN 319 122-1 [i.5]. In an alternative approach, similar as in the case of temporary storage specified above, the client only submits hash values associated with hash function identifiers. These hash values may be the representative of a single data object or of several data objects contained in a Preservation Object Container (POC) using hash-tree techniques. This strategy can be useful in cases of very large data objects or when confidentiality of the data is important or when privacy is a concern. This storage model is addressed by the value WithoutStorage (WOS) within the PreservationStorageModelType (see clause 5.4.6).
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
4.4 Preservation schemes, profile and policies
|
A preservation service according to the present document may support different preservation schemes, which define the general approach for preservation. Refer to Annex F for preservation schemes defined in the present document. A preservation scheme supports at least one preservation goal (see clause 4.2) and is operating in exactly one storage model (see clause 4.3). A preservation scheme is a rather abstract description and can be implemented by one or more preservation profiles, which are described by machine-readible Profile elements as outlined in Figure 2 and specified in clause 5.4.7. The Profile element describes the technical aspects of a preservation profile, which enable a client to use the preservation interface to communicate with the preservation service. The set of preservation profiles supported by a preservation service can be retrieved using the RetrieveInfo call (see clause 5.3.2). A preservation profile in particular contains (references to) policy related information, which addresses aspects of evidence creation and validation and signature validation, in case the preservation goal is PDS (see clause 4.2). The general relationship between a preservation scheme, a preservation profile and related policies is outlined in the following UML-based class diagram, which distinguishes between machine-readable components (depicted in blue) and human-readable components (depicted in white). ETSI ETSI TS 119 512 V1.2.1 (2023-05) 20 Figure 2: Relationship between preservation scheme, profile and policy
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5 Technical Specification of Protocol
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.1 Introduction and Overview
|
The present document first specifies the semantics of the different calls of the protocol for the preservation protocol in a generic fashion and then specifies the concrete syntax of the conveyed data elements based on XML and JSON together with its binding to SOAP and REST respectively. This covers the following operations: • RetrieveInfo (see clause 5.3.2) • PreservePO (see clause 5.3.3) • RetrievePO (see clause 5.3.4) • DeletePO (see clause 5.3.5) • UpdatePOC (see clause 5.3.6) • RetrieveTrace (see clause 5.3.7) • ValidateEvidence (see clause 5.3.8) • Search (see clause 5.3.9) The specification of the request and response of these operations uses the basic types in clause 5.3.1 and the structure models defined in clause 5.4. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 21 Clause 5.2 explains how the set of supported preservation profiles can be discovered. Refer to clause 8.1 of ETSI TS 119 511 [i.14] for additional information on the preservation protocol. Furthermore, clause 5.5 contains preservation-specific extensions for ASiC-related components and clause 5.6 specifies extensions for other preservation object formats.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.2 Discovery of supported preservation profiles
|
A preservation service as specified in the present document may be operated in different operation modes (see clauses 4.2 to 4.4), which are expressed by preservation profiles as described by Profile elements as specified in clause 5.4.7. To enable a client to retrieve the set of supported preservation profiles, the preservation service shall support the RetrieveInfo operation according to clause 5.3.2.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3 Operation requests and responses
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1 Basic types for requests and responses
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.1 Component Request
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.1.1 Semantics
|
The Request component is used as basic type within the operation requests defined in clauses 5.3.3 to 5.3.8. Below follows a list of the sub-components that may be present within this component: • The optional OptionalInputs element. If present, it shall contain a sub-component as defined in clause 4.1.8 of OASIS DSS-X Core 2.0 [5]. • The optional RequestID element. If present, it shall contain one instance of a string. The RequestID element is used to correlate requests with responses. When present in a request, the preservation service shall return it in the response.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.1.2 XML Syntax
|
The XML type RequestType shall implement the requirements defined in the Request component. The RequestType XML elements shall be defined as in XML Schema file (Preservation-API.xsd) provided in Annex C, and which is copied below for information. <complexType name="RequestType"> <sequence> <element name="OptionalInputs" type="dsb:OptionalInputsType" minOccurs="0" /> </sequence> <attribute name="RequestID" type="string" use="optional"/> </complexType>
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.1.3 JSON Syntax
|
The component Request is used as a base type only, not as a JSON instance.
|
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.2 Component Response
| |
cdd823ba984b81337eedcd223e1a6810
|
119 512
|
5.3.1.2.1 Semantics
|
The Response component is used as basic type within the operation responses defined in clauses 5.3.3 to 5.3.9. ETSI ETSI TS 119 512 V1.2.1 (2023-05) 22 Below follows a list of the sub-components that may be present within this component: • The optional OptionalOutputs element may be present and shall, if present, contain a sub-component as defined in clause 4.1.9 of OASIS DSS-X Core 2.0 [5]. • The Result element shall be present and contain a sub-component as defined in clause 4.1.7 of OASIS DSS-X Core 2.0 [5]. NOTE: The Result element contains components which allow to convey major and minor status codes and for the different operations. Refer to clause 4.1.7 of OASIS DSS-X Core 2.0 [5] for the specification of the structure of the Result component and to the clauses 5.3.3 to 5.3.9 for the different error code values, which may appear within the different responses. • The optional RequestID component may be present and shall, if present, contain one instance of a string. The RequestID element is used to correlate requests with responses. When present in a request, the preservation service shall return it in the response.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.