hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.5.10 Service history
|
Presence: This field shall be present only when historical information is applicable to the related service. In the case the service has no history prior to the current status (i.e. a first recorded status or history information not retained by the scheme operator) this field shall not be present. Description: It specifies historical information on listed trust services as a sequence of all previous status entries which the scheme has recorded for the given TSP service. Format: A sequence of Service History Instance elements (see clause 5.6). Value: For each change in TSP service approval status which occurred within the historical information period as specified in clause 5.3.12, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective).
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6 Service history instance
| |
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.1 Service type identifier
|
Presence: This field shall be present. Description: It specifies the identifier of the service type, with the Format and Value used in clause 5.5.1.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.2 Service name
|
Presence: This field shall be present. Description: It specifies the name under which the TSP provided the service identified in clause 5.5.1, with the Format and Value used in clause 5.5.2. NOTE: This clause does not require the name to be the same as that specified in clause 5.5.2. A change of name may be one of the circumstances requiring a new status.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.3 Service digital identity
|
Presence: This field shall be present. Description: It specifies at least one representation of a digital identifier of the service used in clause 5.5.1, with the Format and Value used in clause 5.5.3 for any representation, with at least the X509SKI element and to the exception of any certificate.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.4 Service previous status
|
Presence: This field shall be present. Description: It specifies the identifier of the previous status of the service, with the Format and Value used in clause 5.5.4.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.5 Previous status starting date and time
|
Presence: This field shall be present. Description: It specifies the date and time on which the previous status in question became effective, with the Format and Value used in clause 5.5.5. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 51
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.6.6 Service information extensions
|
Presence: This field is optional. Description: It may be used by TLSOs to provide specific service-related information, to be interpreted according to the specific scheme's rules, with the Format and Value used in clause 5.5.9.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.7 Digital signature
| |
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.7.1 Digitally signed Trusted List
|
The trusted list shall be digitally signed by the 'Scheme operator name' (clause 5.3.4) to ensure its authenticity and integrity. The format of the digital signature shall be XAdES-B-B as defined by ETSI EN 319 132-1 [3]. Such digital signature implementation shall meet requirements as stated in annex B. The digital signature algorithm as well as the certified digital signature key shall conform to security requirement for a minimum 3 years usable key as specified in tables 4, 6 and 7 of ETSI TS 119 312 [2]. The TLSO certificate, to be used to validate its digital signature on the TL, shall be protected with the digital signature by incorporating the TLSO certificate within the ds:KeyInfo element that shall not contain any other certificate forming any kind of associated certificate chain. The Scheme Operator's digital signature certificate shall be conformant to the following restrictions: • The Issuer shall be the TLSO itself (i.e. a self-signed certificate) or a TSP trust service listed in the TL or in one of the TL that is part of the same community (see clause 5.3.9). • "Country code" and "Organization" fields in Subject Distinguished Name shall match respectively the "Scheme Territory" and one of the "Scheme operator name" values. For the latter, the value in UK English language (preferred) or local language (transliterated to Latin script), as available, should be used. • KeyUsage extension shall be set to digitalSignature and/or to nonRepudiation (contentCommitment) to the exclusion of any other KeyUsage value. • ExtendedKeyUsage extension should be present containing id-tsl-kp-tslSigning (see below). • The use of the KeyUsage and ExtendedKeyUsage extensions shall be consistent with the purpose of signing trusted lists. • SubjectKeyIdentifier extension shall be present using one of the first 2 methods specified in clause 4.2.1.2 of IETF RFC 5280 [12]. • BasicConstraints extension shall indicate CA=false. In order to indicate that the use of key-pairs is restricted to digitally sign TLs only, an X.509 v3 certificate should include the following key purpose id OID in the extended key usage extension: -- OID for TSL signing KeyPurposeID for ExtKeyUsageSyntax id-tsl OBJECT IDENTIFIER { itu-t(0) identified-organization(4) etsi(0) tsl-specification (2231) } id-tsl-kp OBJECT IDENTIFIER ::= { id-tsl kp(3) } id-tsl-kp-tslSigning OBJECT IDENTIFIER ::= { id-tsl-kp tsl-signing(0) } Additional general requirements regarding this digital signature are stated in the following clauses.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.7.2 Digital signature algorithm identifier
|
Presence: This field shall be present. Description: It specifies the cryptographic algorithm that has been used to create the digital signature. Depending on the algorithm used, this field may require additional parameters. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 52 Format: Character string or Bit string is suggested, depending on the implementation. Value: This field shall be included in the calculation of the digital signature.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
5.7.3 Digital signature value
|
Presence: This field shall be present. Description: It contains the actual value of the digital signature. Value: All fields of the TL except the signature value itself shall be included in the calculation of the digital signature.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6 Operations
| |
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.1 TL publication
|
TL Scheme Operators shall make TLs available through the Hypertext Transfer Protocol (HTTP) defined in IETF RFC 2616 [7]. TLSOs may in addition support publication through LDAP, or FTP. The HTTP URI pointing to the TL shall be without any special character, shall contain a fully qualified domain name in the host section, and an absolute path, without a query section. It shall be an as stable and permanent URI as possible, without implying any redirection, without requiring acceptance of cookies or explicit action for downloading, and it shall lead directly to the .xml/.xtsl file that shall be downloadable by an application. The absolute path shall end with the string ".xml" or ".xtsl". There shall not be any extraneous header or trailer information in the file. When publishing their TLs, TLSOs should make sure that the cache control is set to a reasonable period, i.e. avoiding that an old version of the TL is allowed to linger in network caches long after it was replaced by a new one by the TLSO. The use of this cache-control should be limited to a maximum value not exceeding 4 hours. TLSOs shall publish, at the same locations where they publish their trusted list, a digest that shall be computed as the SHA-256 hash value [10] of the binary representation of the trusted list as it can be retrieved by the server resolving the HTTP URI. The digest shall be published at an HTTP URI derived from the TL URI replacing the ".xml" or ".xtsl" string at the end of the absolute path with ".sha2". This digest may be used to detect if an updated TL was published and shall not be used to authenticate the TL. Applications should regularly check for publication of a new version of a TL and not wait until the time contained in the Next update field (clause 5.3.15) of the previous TL or the previously downloaded TL is elapsed. For example, the TLSOx's TL published at the location http://www.TLSOx.xyz/TrustedList/TL.xml is accompanied by its sha2 digest file i.e. on location http://www.TLSOx.xyz/TrustedList/TL.sha2. Downloaders may adopt the following strategy for downloading file TL.xml: • check whether TL.sha2 is available for download: - if TL.sha2 has been successfully downloaded, verify the digest against the cached TL.xml file. If different, download and process TL.xml; - if TL.sha2 has not been successfully downloaded, download and process TL.xml directly. • TL.xml should be downloaded/processed anyway if the nextUpdate (in the cached file) has been reached.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.2 Transport Protocols
| |
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.2.1 HTTP-Transport
| |
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.2.1.1 HTTP-Media Type
|
This clause specifies a means for transport of TLs via the Internet using HTTP. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 53 TL payloads shall be sent using the following media type: • application/vnd.etsi.tsl+xml The client may, when sending requests, provide an HTTP Accept header field. This header field should indicate an ability to accept "application/vnd.etsi.tsl+xml".
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.2.2 MIME registrations
|
A MIME-Type and a file-extensions support the transfer of TLs: MIME media type name: Application MIME subtype name: vnd.etsi.tsl+xml Required parameters: none encoding considerations: binary File extension: xml or xtsl Security considerations: TLs do not contain any active code or invoke any automated processing by itself. It is expected that clients only parse the TL and that there is no security risk. TLs are signed; no additional integrity protection is required. TLs typically are meant to be public, no confidentiality is required. Published specification: The TL format as defined in the present document.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.3 TL Distribution Points in trust service tokens
|
Trust Service Providers may wish to give information on how to locate a TL of the scheme they operate under. To do so, they may include an appropriate extension in their trust service tokens (e.g. certificates, CRLs, time-stamp tokens, OCSP responses and other). If such extension mechanism allows for the expression of criticality, this extension should not be marked critical. A distribution point should remain accessible until all trust service tokens it is referenced in have expired. The TSP shall guarantee that the distribution point in each trust service token is always resolved to the latest available applicable TL or to a scheme including a pointer to it (e.g. LOTL).
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.4 TL availability
|
TLSOs shall make their TLs available 24 hours a day and 7 days a week, with an availability percentage of minimum 99,9 % over one year.
|
c2bb6e991a732a7c4e762f03ed205a28
|
119 612
|
6.5 TLSO practices
|
The TLSO shall define, maintain and implement appropriate measures, practices and policies, including change management and security procedures, for establishing, publishing and maintaining the trusted list to ensure that the information provided in the trusted list is timely, accurate, complete and authentic. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 54 Annex A (informative): Authenticating and trusting trusted lists A.1 Authenticating and trusting a TL A TL is a digitally signed data. To verify the digital signature, relying parties need to be able to access the applicable public key. Since the scheme issuing the TLs is effectively positioned "above" the TSPs approved by that scheme, the authenticity of the public key cannot be verified solely on the basis of its certification by any TSP inside or outside the scheme. Providing the scheme's public key is therefore a problem very similar to providing the public key of a CA service. In the case where several TLs participate to the same global approval scheme or participate to a common approval scheme or when there is a need to group and facilitate access to such TLs, a compiled list of pointers towards such TLs may be established, published and maintained. This compiled list of pointers can be designed on the model of "EUlistofthelists" type as specified in clause 5.3.3. NOTE 1: To allow access to the trusted lists of all Member States in an easy manner, the European Commission publishes a central list with links to the locations where the trusted lists are published as notified by Member States. This central list, called the List Of Trusted Lists (LOTL), is available in both a human readable format and in a format suitable for automated (machine) processing XML. The "EUlistofthelists" type of such a LOTL is defined in clause D.5. Such a compiled list of pointers towards logically grouped TLs can also play an important role in authenticating and trusting each TL which is pointed to by the compiled list. As a TL is digitally signed by its TLSO, the certificate to be used to verify such a digital signature can be included in the compiled list together with the corresponding pointer to this TL. The compiled list of pointers can be digitally signed and the certificate to be used to verify the digital signature on the compiled list can be published in an official journal or in another trustworthy publication. NOTE 2: The European Commission LOTL plays an important role in authenticating and trusting EU MS trusted lists. Each national trusted list is electronically signed/sealed by its scheme operator and the certificate to be used to verify such an electronic signature/seal is included in the LOTL after notification to the European Commission. The public key certificate(s) corresponding to the private key(s) entitled to be used to electronically sign/seal MS trusted lists and hence to be used by relying parties to validate those TLs signatures/seals are published in the LOTL. The authenticity and integrity of the machine processable version of the LOTL is ensured through a qualified electronic signature or seal supported by a qualified certificate which can be authenticated and directly trusted through one of the digests published in the Official Journal of the European Union (OJEU). See https://eidas.ec.europa.eu/efda/tl-browser/#/screen/home. NOTE 3: Additionally the certificate(s) of the LOTL scheme operator is(are) included in any EU MS trusted list. NOTE 4: In order to authenticate and trust an EU Member State trusted list, relying parties can: 1) download the LOTL from the protected location published in the OJEU, after having authenticated the trusted channel on the basis of the trusted channel certificate whose digest is published in the OJEU; 2) validate the electronic signature/seal on the downloaded LOTL, once having verified that the digest of the LOTL scheme operator public key certificate to be used to validate the signature/seal maps one of the digests of the public key certificate(s) corresponding to the private key(s) entitled to be used to sign/seal the LOTL as published in OJEU; 3) verify, once the LOTL signature/seal being validated, the continued validity of the LOTL, by ensuring that the validity period of the LOTL has not expired; 4) parse the LOTL to retrieve the location and authentication information with regards to the target MS trusted list (one or more public key certificates may be associated to a MS TL as the public key certificate(s) corresponding to the private key(s) entitled to be used to sign the TL); 5) download the target MS TL; ETSI ETSI TS 119 612 V2.4.1 (2025-08) 55 6) validate the signature/seal on the target MS TL, once having verified that the digest of the TL scheme operator public key certificate to be used to validate the signature/seal maps one of the digests of the public key certificate(s) corresponding to the private key(s) entitled to be used to sign/seal the target TL as published in the LOTL. If either of the above checks fails, the TL authentication fails. The procedure described above can be performed by each user, but will in many cases be carried out on the level of an organization according to their own policy. In this case, the software environment of each user's machine would typically be pre-configured and updated by the system administration or by the security officer. In time it is likely and certainly possible that such TLSOs or LOTL scheme operators certificates or public keys could also be pre-installed and updated in browsers, so enabling personal users to gain advantage from this approach. A.2 Ensuring continuity in TL authentication In order to ensure continuity in TL authentication, TL scheme operators need to make sure that at all times two or more scheme operator public key certificates, with shifted validity periods, corresponding to the private keys entitled to be used to digitally sign the TL are available in a trustworthy manner to relying parties (e.g. published in the LOTL in the context of EUMS TLs, or in an Official Journal). Those certificates can be issued so that they: • do not have the same or too close validity start and end dates; • are created on new key pairs as no previously used key pair are to be re-certified; • are allocated to two or more scheme operator trustees in accordance with the scheme operator applicable policy; and • are notified in due time to relying parties (e.g. to the EC for inclusion in the LOTL in the context of EUMS TLs). In the case of compromise or decommissioning of one trusted list digital signature private key, TL scheme operators: • when the current (into force) TL was signed with such a compromised or decommissioned private key, need to re-issue, without any delay, a new trusted list signed with a non-compromised private key entitled to be used to digitally sign the TL and whose corresponding public key certificate was already made available in a trustworthy manner to relying parties (e.g. is published in the LOTL); • need to promptly notify to the relying parties in a trustworthy manner: - of such a key compromise or decommissioning and the associated circumstances or reasons; and - a new list of public key certificate(s) corresponding to the private key(s) entitled to be used to digitally sign the TL. In the case of compromise (or decommissioning) of all the digital signature private keys corresponding to the public key certificates that were entitled to be used to validate one TL and were available to relying parties (e.g. published in the LOTL), scheme operators: • need to generate new key pairs and public key certificates corresponding to the private keys to be entitled to be used to digitally sign the TL; • need to re-issue, without any delay, a new trusted list signed with one of those new private keys entitled to be used to digitally sign the TL and whose corresponding public key certificate is to be made available in a trustworthy manner to relying parties; • need to promptly notify to the relying parties in a trustworthy manner: - of a such a key compromise; and - the new list of public key certificates corresponding to the private keys entitled to be used to digitally sign the TL. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 56 In the case of compromise or decommissioning of one digital signature private key related to a compiled list of pointers to several TLs, the compiled list scheme operator: • when the current (into force) compiled list was digitally signed with such a compromised or decommissioned private key, needs to re-issue, without any delay, a new compiled list digitally signed with a non-compromised private key entitled to be used to digitally sign the compiled list and whose corresponding public key certificate is published e.g. in an official journal; • needs to promptly publish, e.g. in an official journal, a new list of public key certificate(s) corresponding to the private key(s) entitled to be used to digitally sign the compiled list; • needs to inform relying parties and stakeholders of such an official publication update together with the associated circumstances or reasons for such an update. In the case of compromise (or decommissioning) of all compiled list digital signature private keys corresponding to the public key certificates entitled to be used to digitally sign the compiled list and published, e.g. in an official journal, the compiled list scheme operator: • needs to generate new key pairs and public key certificates corresponding to the private keys to be entitled to be used to digitally sign the compiled list; • needs to re-issue, without any delay, a new compiled list digitally signed with one of those new private keys entitled to be used to digitally sign the compiled list and whose corresponding public key certificate is to be published, e.g. in an official journal; • needs to promptly publish, e.g. in an official journal, the new list of public key certificates corresponding to the private keys entitled to be used to digitally sign the compiled list, deprecating compromised or decommissioned certificates; • needs to inform the relying parties and stakeholders of such an official publication update together with the associated circumstances or reasons for such an update. In the context of the direct trust model underlying their trustworthiness recognition, the revocation of TLSO and compiled list scheme operator certificate(s) are de facto implemented by the fact that the issuance of a new update of the related TL or compiled list deprecates the updated one and the deprecation of the compromised or decommissioned certificate(s) respectively in the compiled list and/or in the related official publication. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 57 Annex B (normative): Implementation in XML B.0 General requirements A TL shall comply with the XML schemas attached to the present document as part of a ZIP file identified in annex C, each one defining elements and types in a different namespace, respectively: • http://uri.etsi.org/02231/v2# • http://uri.etsi.org/TrstSvc/SvcInfoExt/eSigDir-1999-93-EC-TrustedList/# • http://uri.etsi.org/02231/v2/additionaltypes# NOTE: "02231" in the name space does not correspond to the ETSI document number of the present document because the name space was initially defined in ETSI TS 102 231 [i.6]. The previously defined name space is kept for compatibility reasons. Applications shall use UTF-8 encoding for XML TLs. With regards to the ElectronicAddressType type, the contents of each URI element shall represent a IETF RFC 5322 [9] e-mail address, expressed by using the "mailto:" URI scheme as defined by IETF RFC 2368 [6], or a web site address. Processing of Critical attribute shall be as the one defined by IETF RFC 5280 [12] for the critical field of extensions of X.509 v3 certificates. Applications shall reject the TL if they encounter a critical extension that they do not recognize. However, they may ignore a non-critical extension that they do not recognize. B.1 The Signature element B.1.0 General Clause 5.7 requires that the TL is digitally signed: this includes use of XAdES [3] signatures. The TL-structure contains a ds:Signature element that represents an enveloped digital signature-type. The present document mandates the following constraints to any XML-Signature [4]-based digital signature applied to a TL: 1) It shall be an enveloped digital signature. 2) Its ds:SignedInfo element shall contain a ds:Reference element with the URI attribute set to a value referencing the TrustServiceStatusList element enveloping the digital signature itself. This ds:Reference element shall satisfy the following requirements: a) It shall contain only one ds:Transforms element. b) This ds:Transforms element shall contain two ds:Transform elements. The first one will be one whose Algorithm attribute indicates the enveloped transformation with the value: "http://www.w3.org/2000/09/xmldsig#enveloped-signature". The second one will be one whose Algorithm attribute instructs to perform the exclusive canonicalization "http://www.w3.org/2001/10/xml- exc-c14n#". 3) ds:CanonicalizationMethod shall be "http://www.w3.org/2001/10/xml-exc-c14n#". 4) It may have other ds:Reference elements. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 58 NOTE 1: Rules 2 and 3 ensure that the enveloping TrustServiceStatusList element is actually digitally signed as mandated by the processing model in clause 4.3.3.3 of XML-Signature [4] (with reference to same-document URI references). They also ensure that if relative referencing mechanisms are used in the ds:Reference element, the TrustServiceStatusList may be safely inserted within other xml documents. NOTE 2: Rule 4 allows, among other things, for inclusion of signed properties in the digital signature, like the ones standardized in XAdES [3]. B.1.1 The scheme operator identifier in XAdES signatures XAdES [3] defines the xades:SigningCertificateV2 as a signed property that contains an identifier of the signer's certificate and its digest. This shall be used as an effective way of securing the scheme operator identifier. Should the child of ds:X509Data element be a ds:X509SKI or an element encapsulating a public key, its contents shall be consistent with the contents of the xades:SigningCertificateV2 signed property, if present. B.1.2 Algorithm and parameters The algorithms, their parameters and formats supported by the present document shall be: • those supported by XML-Signature [4]; or • the Elliptic Curve Digital Signature Algorithm (ECDSA) as defined in [1]; or • the SHA-2 algorithms as defined in [10]. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 59 Annex C (normative): XML schema The present document has an associated electronic ZIP file "ts_119612v020401p0.zip" that contains the XML schemas that are integral parts of the present document and further described below. In the event that any part of the module and/or schemas within this electronic attachment are in conflict with the text of the present document, the present document shall prevail as the authoritative source. The XML Schema files are also available in the following repository: https://forge.etsi.org/rep/esi/x19_612_trusted_lists. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 60 Annex D (normative): Registered Uniform Resource Identifiers D.0 General This annex specifies those Uniform Resource Identifiers (URIs) which have been registered in connection with the present document. Those with the radix (base) "http://uri.etsi.org/19612/……" are registered and declared by their presence in the present document, for specific usage within the present document: those with the radix "http://uri.etsi.org/TrstSvc/……" are registered by ETSI as a Common Domain (see http://portal.etsi.org/pnns/xml.asp#Common_Domain) on behalf of the TC ESI because they have a wider applicability and usage and are defined in the present document. In the following tables the following layout is used for each URI declaration: The URI is given as an unbroken string Related TSL field (if any) The meaning of the URI is given, indented to emphasize its relationship to the preceding URI. Where more than one URI relates to a specific TL field the second column will extend across all URI declarations (row-pairs) which apply. D.1 URIs registered within the present document The following URIs are hereby declared and registered under the present document's assigned radix: http://uri.etsi.org/19612/TSLTag TSL tag A data structure which conforms to the TSL specification published in ETSI TS 119 612 in any of its historical issues or this one. http://uri.etsi.org/02231/v2# N/a The XML namespace identifier relating to the TSL version specified in this issue of ETSI TS 119 612. http://uri.etsi.org/19612/TDPContainer N/a A qualifier for web pages that contain one or more TDPs which can be used as a value of the attribute "profile" for the "head" element of the web page. D.2 ETSI Common Domain URIs Void. D.3 Scheme registered URIs Any organization operating a scheme might choose to create its own URIs for its own specific purposes or request ETSI to assign a registered URI root under the ETSI Identified Organization Domain (see http://portal.etsi.org/pnns/xml.asp), and then define its own URIs under this root. It might be appropriate to register certain of those URIs where they complement URIs required by or which might be used in the context of the publication of a TL. The following examples suggest how additional URIs could be created, including showing a second level of rules, after using the applicable Optional URI as shown above. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 61 Potential URI Related TSL field (if any) Meaning http://uri.etsi.org/"registered_org"/"schemename" Scheme type/community/rules (at the secondary level) This could mean an assessment scheme called "schemename" being operated by "registered_org", where "registered_org" is replaced by the name of the scheme operator and "schemename" is replaced by the actual scheme name. http://"scheme_op_URI_root"/.../schemerules/"schemename" This URI would be registered under a different root, e.g. the scheme operator's, distinguished by "scheme_op_URI_root", or it could be another organization which maintains a registry of URIs. This URI could mean an assessment scheme called "schemename" being operated by "scheme_op" where "scheme_op" is replaced by the name of the scheme operator and "schemename" is replaced by the actual scheme name. D.4 Common trusted lists URIs The following URIs, are registered under the radix "http://uri.etsi.org/TrstSvc/TrustedList/": http://uri.etsi.org/TrstSvc/TrustedList/schemerules/CC where CC is replaced with the code used in the "Scheme territory" field (see clause 5.3.10). Scheme type/community/rules A URI specific to CC's trusted list pointing towards a descriptive text that shall be published by the TLSO and applicable to this CC's trusted list: • Where users can obtain the referenced CC's specific policy/rules against which services included in the list shall be assessed in compliance with the CC's appropriate approval schemes. • Where users can obtain a referenced CC's specific description about how to use and interpret the content of the trusted list (e.g. in the EU with regard to the trust services not related to the issuing of qualified certificates, where this may be used to indicate a potential granularity in the national supervision/accreditation systems related to trust service providers not issuing qualified certificates and how the "Scheme service definition URI" (see clause 5.5.6) and the "Service information extension" field (see clause 5.5.9) are used for this purpose). http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/RootCA-QC Service information extensions/additionalServi ceInformation Extension/ A Root Certification Authority from which a certification path can be established down to a Certification Authority issuing qualified certificates. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC D.5 EU specific trusted lists URIs D.5.1 TSL Type The following URIs, are registered under the radix http://uri.etsi.org/TrstSvc/TrustedList/. http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUgeneric A TL implementation of a supervision/accreditation status list of trust services from trust service providers which are supervised/accredited by the referenced Member State owning the TL implementation for compliance with the relevant provisions laid down in the applicable European legislation, through a process of direct oversight (whether voluntary or regulatory). http://uri.etsi.org/TrstSvc/TrustedList/TSLType/EUlistofthelists A TL implementation of a compiled list of pointers towards Member States supervision/accreditation status lists of trust services from trust service providers which are supervised/accredited by the referenced Member State owning the pointed TL implementation for compliance with the relevant provisions laid down in the applicable European legislation, through a process of direct oversight (whether voluntary or regulatory). ETSI ETSI TS 119 612 V2.4.1 (2025-08) 62 D.5.2 Status determination approach http://uri.etsi.org/TrstSvc/TrustedList/StatusDetn/EUappropriate Services listed have their status determined by or on behalf of the Scheme Operator under an appropriate system as defined by the Member State implementation of the applicable European legislation and further described in the 'Scheme information URI' pointed-to information. D.5.3 Scheme type/community/rules http://uri.etsi.org/TrstSvc/TrustedList/schemerules/EUlistofthelists A URI pointing towards a descriptive text where users can obtain information about the scheme of schemes type (i.e. a compiled list listing pointers to all trusted lists published as part of the scheme of schemes and maintained in the form of a TL) and the relevant driving rules and policy. http://uri.etsi.org/TrstSvc/TrustedList/schemerules/EUcommon A URI pointing towards a descriptive text that applies to all EU Member States' trusted lists: • By which participation of the Member States' trusted lists is denoted in the general scheme of the EU Member States trusted lists. • Where users can obtain policy/rules against which services included in the trusted list are assessed. • Where users can obtain description about how to use and interpret the content of the EU Member States' trusted list. These usage rules are common to all EU Member States' trusted lists whatever the type of listed services. D.5.4 Service information extensions/Qualifications Extension/Qualifiers http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithSSCD QCWithSSCD it is ensured by the trust service provider and controlled (supervision model) or audited (accreditation model) by the referenced Member State (respectively its Supervisory Body or Accreditation Body) that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Secure Signature Creation Device (SSCD) support ARE supported by an SSCD (i.e. that means that the private key associated with the public key in the certificate is stored in a Secure Signature Creation Device conformant with the applicable European legislation). This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoSSCD QCNoSSCD it is ensured by the trust service provider and controlled (supervision model) or audited (accreditation model) by the referenced Member State (respectively its Supervisory Body or Accreditation Body) that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Secure Signature Creation Device (SSCD) support ARE NOT supported by an SSCD (i.e. that means that the private key associated with the public key in the certificate is not stored in a Secure Signature Creation Device conformant with the applicable European legislation). This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCSSCDStatusAsInCert QCSSCDStatusAsInCert it is ensured by the trust service provider and controlled (supervision model) or audited (accreditation model) by the referenced Member State (respectively its Supervisory Body or Accreditation Body) that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Secure Signature Creation Device (SSCD) support DO contain the machine-processable information indicating whether or not the Qualified Certificate is supported by an SSCD. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 63 http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForLegalPerson QCForLegalPerson it is ensured by the trust service provider and controlled (supervision model) or audited (accreditation model) by the referenced Member State (respectively its Supervisory Body or Accreditation Body) that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the issuance to Legal Person ARE issued to Legal Persons. This value shall not be used, if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement QCStatement it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all certificates issued under the service identified in 'Service digital identity' (clause 5.5.3) and further identified by the filters information used to further identify under the 'Sdi' identified trust service that precise set of certificates are issued as qualified certificates. This value shall not be used, if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithQSCD QCWithQSCD it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Qualified Signature or Seal Creation Device (QSCD) support ARE supported by a QSCD (i.e. that means that the private key associated with the public key in the certificate resides in a QSCD conformant with the applicable European legislation); This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoQSCD QCNoQSCD it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Qualified Signature or Seal Creation Device (QSCD) support ARE NOT supported by a QSCD (i.e. that means that the private key associated with the public key in the certificate does not reside in a QSCD conformant with the applicable European legislation). This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDStatusAsInCert QCQSCDStatusAsInCert it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Qualified Signature or Seal Creation Device (QSCD) support DO contain the machine-processable information indicating whether or not the Qualified Certificate is supported by a QSCD. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDManagedOnBehalf QCQSCDManagedOnBehalf it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of Qualified Certificates for which this additional information is required with regards to the presence or absence of Qualified Signature or Seal Creation Device (QSCD) support have their private key residing in a QSCD for which the generation and management of that private key is done by the qualified TSP on behalf of the entity whose identity is certified in the certificate in accordance with the applicable legislation. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 64 http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig QCForESig it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of qualified certificates for which this additional information is required with regards to the nature of the qualified certificate ARE qualified certificates for electronic signatures in accordance with the applicable legislation. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal QCForESeal it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of qualified certificates for which this additional information is required with regards to the nature of the qualified certificate ARE qualified certificates for electronic seals in accordance with the applicable legislation. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA QCForWSA it is ensured by the trust service provider and supervised by the Member State Supervisory Body that all Qualified Certificates issued under the service identified in "Service digital identity" and further identified by the filters information used to further identify under the "Sdi" identified trust service that precise set of qualified certificates for which this additional information is required with regards to the nature of the qualified certificate ARE qualified certificates for web site authentication in accordance with the applicable legislation. This value shall not be used if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified NotQualified it is ensured by the trust service provider, and supervised by the Member State Supervisory Body that all certificates issued under the service identified in 'Service digital identity' (clause 5.5.3) and further identified by the filters information used to further identify under the 'Sdi' identified trust service that precise set of certificates are not to be considered as qualified certificates. This value shall not be used, if the service type is not http://uri.etsi.org/TrstSvc/Svctype/CA/QC D.5.5 Service information extensions/additionalServiceInformation Extension http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures For eSignatures Further specifies the "Service type identifier" identified service as being provided for electronic signatures. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals For eSeals Further specifies the "Service type identifier" identified service as being provided for electronic seals. http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication For Web Site Authentication Further specifies the "Service type identifier" identified service as being provided for web site authentication. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 65 D.5.6 Service current and previous statuses http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision Under Supervision The service identified in "Service digital identity" (see clause 5.5.3) provided by the trust service provider identified in "TSP name" (see clause 5.4.1) is currently under supervision, for compliance with the provisions laid down in the applicable European legislation, by the Member State identified in the "Scheme territory" (see clause 5.3.10) in which the trust service provider is established. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation Supervision of Service in Cessation The service identified in "Service digital identity" (see clause 5.5.3) provided by the trust service provider identified in "TSP name" (see clause 5.4.1) is currently in a cessation phase but still supervised until supervision is ceased or revoked. In the event a different person than the one identified in "TSP name" has taken over the responsibility of ensuring this cessation phase, the identification of this new or fallback person (fallback trust service provider) shall be provided in "Scheme service definition URI" (clause 5.5.6) and in the "TakenOverBy" extension (clause 5.5.9.3) of the service entry. "Supervision of Service in Cessation" status shall be used when a TSP directly ceases its related services under supervision; it shall not be used when supervision has been revoked. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased Supervision Ceased The validity of the supervision assessment has lapsed without the service identified in "Service digital identity" (see clause 5.5.3) being re-assessed. The service is currently not under supervision any more from the date of the current status as the service is understood to have ceased operations. "Supervision Ceased" status shall be used when a TSP directly ceases its related services under supervision; it shall not be used when supervision has been revoked. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked Supervision Revoked Having been previously supervised, the trust service provider's service and potentially the trust service provider itself has failed to continue to comply with the provisions laid down in the applicable European legislation, as determined by the Member State identified in the "Scheme territory" (see clause 5.3.10) in which the trust service provider is established. Accordingly the service has been required to cease its operations and shall be considered by relying parties as ceased for the above reason. The status value "Supervision Revoked" may be a definitive status, even if the trust service provider then completely ceases its activity; it shall not be migrated (without any intermediate status) to either "Supervision of Service in Cessation" or to "Supervision Ceased" status in this case. The only way to change the "Supervision Revoked" status is to recover from non-compliance to compliance with the provisions laid down in the applicable European legislation according to the appropriate supervision system in force in the Member State owing the trusted list, and regaining "Under Supervision" status. "Supervision of Service in Cessation" status, or "Supervision Ceased" status shall be used when a TSP directly ceases its related services under supervision; they shall not be used when supervision has been revoked. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited Accredited An accreditation assessment has been performed by the Accreditation Body on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10) and the service identified in "Service digital identity" (see clause 5.5.3) provided by the trust service provider identified in "TSP name" (see clause 5.4.1) is found to be in compliance with the provisions laid down in the applicable legislation. This accredited trust service provider may be established in another Member State than the one identified in the "Scheme territory" (see clause 5.3.10) of the trusted list or in a non-EU country. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accreditationceased Accreditation Ceased The validity of the accreditation assessment has lapsed without the service identified in "Service digital identity" (see clause 5.5.3) being re-assessed. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accreditationrevoked Accreditation Revoked Having been previously found to be in conformance with the scheme criteria, the service identified in "Service digital identity" (see clause 5.5.3) provided by the trust service provider identified in "TSP name" (see clause 5.4.1) and potentially the trust service provider itself have failed to continue to comply with the provisions laid down in the applicable European legislation. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 66 http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted Granted Following ex ante and active approval activities, in compliance with the provisions laid down in the applicable national legislation and Regulation (EU) No 910/2014 [i.10], it indicates that the Supervisory Body identified in the "Scheme operator name" (see clause 5.3.4) on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10) has granted a qualified status: to the corresponding trust service being of a service type specified in clause 5.5.1.1 and identified in "Service digital identity" (see clause 5.5.3), and to the trust service provider identified in "TSP name" (see clause 5.4.1) for the provision of that service. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn Withdrawn In compliance with the provisions laid down in the applicable national legislation and Regulation (EU) No 910/2014 [i.10], it indicates that the qualified status has not been initially granted or has been withdrawn by the Supervisory Body on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10): from the trust service being of a service type specified in clause 5.5.1.1 and identified in "Service digital identity" (see clause 5.5.3), and from its trust service provider identified in "TSP name" (see clause 5.4.1) for the provision of that service. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/setbynationallaw Set by national law For NationalRootCA-QC type: The service is set by national law in accordance with the applicable European legislation and operated by the responsible national body issuing root-signing or qualified certificates to accredited trust service providers. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/recognisedatnationallevel Recognized at national level For trust services listed under a service type specified in clause 5.5.1.2: In compliance with the provisions laid down in the applicable national legislation, it indicates that the Supervisory Body identified in the "Scheme operator name" (see clause 5.3.4) on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10) has granted an "approved" status, as recognized at national level, to the corresponding trust service identified in "Service digital identity" (see clause 5.5.3) and to the trust service provider identified in "TSP name" (see clause 5.4.1) for the provision of that service, as both the TSP and the trust service it provides meet the provisions laid down in Regulation (EU) No 910/2014 [i.10] and the applicable national legislation. For NationalRootCA-QC type: The service is set by national law in accordance with the applicable European legislation and operated by the responsible national body issuing root-signing or qualified certificates to accredited trust service providers. For other trust services listed under a service type specified in clause 5.5.1.3: In compliance with the provisions laid down in the applicable national legislation, it indicates that the Supervisory Body identified in the "Scheme operator name" (see clause 5.3.4) on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10) has granted an "approved" status, as recognized at national level, to the corresponding trust service identified in "Service digital identity" (see clause 5.5.3) and to the trust service provider identified in "TSP name" (see clause 5.4.1) for the provision of that service, as both the TSP and the trust service it provides meet the provisions laid down in the applicable national legislation. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/deprecatedbynationallaw Deprecated by national law [i.10] For NationalRootCA-QC type: The service is deprecated by national law in accordance with the applicable European legislation and by the responsible national body issuing root-signing or qualified certificates to accredited trust service providers. http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/deprecatedatnationallevel Deprecated at national level For NationalRootCA-QC type: The service is deprecated by national law in accordance with the applicable European legislation and by the responsible national body issuing root-signing or qualified certificates to accredited trust service providers. For other trust services listed under a service type specified in clause 5.5.1.2 or in clause 5.5.1.3: In compliance with the provisions laid down in the applicable EU or national legislation, it indicates that the previously "approved" status has been withdrawn by the Supervisory Body on behalf of the Member State identified in the "Scheme territory" (see clause 5.3.10) from the trust service identified in "Service digital identity" (see clause 5.5.3) and from its trust service provider identified in "TSP name" (see clause 5.4.1) for the provision of that service. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 67 D.6 Non-EU specific trusted lists URIs The following URIs, are registered under the radix "http://uri.etsi.org/TrstSvc/……": http://uri.etsi.org/TrstSvc/TrustedList/TSLType/CClist where "CC" is replaced by a character string identifying the community to which it applies (e.g. "ASEAN", "GCC" or the ISO 3166-1 [15] alpha-2 Country Code used in the 'Scheme territory field' (clause 5.3.10)). TSL type Indicates a trusted list providing assessment scheme based approval status information about trust services from trust service providers which are approved by the competent trusted list scheme operator or by the State or body in charge from which the scheme operator depends or by which it is mandated, for compliance with the relevant provisions of the applicable approval scheme and/or the applicable legislation. http://uri.etsi.org/TrstSvc/TrustedList/TSLType/CClistofthelists where "CC" is replaced by a character string identifying the community to which it applies (e.g. "ASEAN", "GCC" or the ISO 3166-1 [15] alpha-2 Country Code used in the 'Scheme territory field' (clause 5.3.10)). Indicates a compiled list of pointers towards community members' lists of trust services from trust service providers which are approved by the competent trusted list scheme operator or by the State or body in charge from which the scheme operator depends or by which it is mandated, for compliance with the relevant provisions of the applicable approval scheme and/or the applicable legislation. http://uri.etsi.org/TrstSvc/TrustedList/StatusDetn/CCdetermination where "CC" is replaced by a character string identifying the community to which it applies (e.g. "ASEAN", "GCC" or the ISO 3166-1 [15] alpha-2 Country Code used in the 'Scheme territory field' (clause 5.3.10)). Status determination approach Services listed have their status determined after assessment by or on behalf of the scheme operator against the scheme's criteria (active approval/recognition) and as further described in the 'Scheme information URI' pointed-to information. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 68 Annex E (normative): Implementation requirements for multilingual support E.1 General rules When establishing their trusted lists, TLSOs shall use: • Language codes in lower case and country codes in upper case. • Language and country codes according to table E.1 with regards to EU MS. When a Latin script is present (with its proper language code) a transliteration in Latin script with the related language codes specified in table E.1 is added. Table E.1 NOTE: (*) Latin transliteration: България = Bulgaria; Ελλάδα = Elláda; Κύπρος = Kýpros. Short name Short name Notes (source language) (English) Belgique/België Belgium BE fr, de, nl България (*) Bulgaria BG bg bg-Latn Česká republika Czech Republic CZ cs Danmark Denmark DK da Deutschland Germany DE de Eesti Estonia EE et Éire/Ireland Ireland IE ga, en Ελλάδα (*) Greece EL el Country code recommended by EU el-Latn España Spain ES es also Catalan (ca), Basque (eu), Galician (gl) France France FR fr Hrvatska Croatia HR hr Italia Italy IT it Κύπρος/Kıbrıs (*) Cyprus CY el, tr el-Latn Latvija Latvia LV lv Lietuva Lithuania LT lt Luxembourg Luxembourg LU fr, de, lb Magyarország Hungary HU hu Malta Malta MT mt, en Nederland Netherlands NL nl Österreich Austria AT de Polska Poland PL pl Portugal Portugal PT pt România Romania RO ro Slovenija Slovenia SI sl Slovensko Slovakia SK sk Suomi/Finland Finland FI fi, sv Sverige Sweden SE sv United Kingdom United Kingdom UK en Country code recommended by EU Ísland Iceland IS is Liechtenstein Liechtenstein LI de Norge/Noreg Norway NO no, nb, nn Country Code Language Code Transliteration in Latin script ETSI ETSI TS 119 612 V2.4.1 (2025-08) 69 E.2 Multilingual character string The string contained within a multilingual character string shall fulfil the requirements of annex N of ISO/IEC 10646 [5] subject to the following restrictions: 1) the content shall be a string of characters from the Universal Character Set (UCS) as defined by ISO/IEC 10646 [5]; 2) the content shall be UTF-8 encoded; 3) the content shall not include any signature to identify the UCS (see annex H of ISO/IEC 10646 [5]); 4) control functions (ISO/IEC 6429 [13]), escape sequences (ISO/IEC 2022 [14]) and control sequences or strings shall not be used; therefore control characters such as TAB, CR, LF shall not be present; 5) private-use characters (see clause 10 of ISO/IEC 10646 [5]) from the private use zone (code points E000 to F8FF) in the Basic Multilingual Plane (BMP) and from the private-use Planes 0F and 10 in Group 00, shall not be used; 6) Tag Characters (see annex T of ISO/IEC 10646 [5]) shall not to be used: therefore the characters from the TAGS (3001) collection shall not be used (see annex A of ISO/IEC 10646 [5] for the list of defined collections); 7) the content shall be plain text without any mark-up elements or tags from languages as SGML, HTML, XML, XHTML, RTF, TeX and others; 8) the content should follow the semantic rules defined by the Unicode Standard [i.13] (available at http://www.unicode.org/standard/standard.html) for the corresponding characters; 9) combining characters should not be used if the content can be expressed without them; if there is the need to use combining characters but it is possible not to use the ones listed in clause B.1 of ISO/IEC 10646 [5], then that latter set shall not be used. NOTE: This helps to keep as low as possible the required implementation level (as defined by clause 14 of ISO/IEC 10646 [5]) for parsing applications. E.3 Multilingual pointer If the content pointed by the multilingual pointer is plain text, it shall meet the following requirements that express the conformity to annex N of ISO/IEC 10646 [5] and add further restrictions: 1) the pointed content shall be a string of characters from the Universal Character Set (UCS) as defined by ISO/IEC 10646 [5]; 2) the pointed-to content shall be UTF-8 encoded; 3) the pointed-to content may include the signature for UTF-8 (see annex H of ISO/IEC 10646 [5]) to identify the UCS; 4) control functions (ISO/IEC 6429 [13]), escape sequences (ISO/IEC 2022 [14]) and control sequences or strings may be used; 5) private-use characters (see clause 10 of ISO/IEC 10646 [5]) from the private use zone (code points E000 to F8FF) in the Basic Multilingual Plane (BMP) and from the private-use Planes 0F and 10 in Group 00, shall not be used; 6) Tag Characters (see annex T of ISO/IEC 10646 [5]) shall not to be used: therefore the characters from the TAGS (3001) collection shall not be used (see annex A of ISO/IEC 10646 [5] for the list of defined collections); 7) if the pointed-to content is expressed by means of mark-up languages as SGML, HTML, XML, XHTML then: a) the requirements described in W3C Technical Report #20 [i.7] should be met; ETSI ETSI TS 119 612 V2.4.1 (2025-08) 70 b) a language indication may be present according to the mechanisms listed in W3C Technical Report #20 [i.7]. 8) the pointed-to content should follow the semantic rules defined by the Unicode Standard [i.13] (available at http://www.unicode.org/standard/standard.html) for the corresponding characters; 9) combining characters should not be used if the pointed-to content can be expressed without them; if there is the need to use combining characters but it is possible not to use the ones listed in clause B.1 of ISO/IEC 10646 [5], then that latter set shall not be used. NOTE: This helps to keep as low as possible the required implementation level (as defined by clause 14 of ISO/IEC 10646 [5] for parsing applications). E.4 Overall requirements The requirements of W3C Technical Report #20 [i.7] should be met. For interoperability purposes, all applications parsing TLs shall be able to store and manage all characters defined by ISO/IEC 10646 [5]. This way the digital signature applied to the TL can be always verified, whatever UCS characters are used within the TL. However the parsing application may not be able to correctly present all characters. NOTE: Developers of TL parsing applications are advised that if their application does not support some of these characters, the application should give notice to the user about possible incorrect representation of the content of multilingual fields; the precise behaviour of the application while presenting unsupported characters is left to developers [i.7]. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 71 Annex F (informative): TL manual/auto field usage Table F.1 lists all fields defined for the TL and indicates whether the field contents should be made available to users when presenting the TL in a human-readable form (column 2) or whether the field is considered to be essential for effective automatic parsing (column 3), noting that all fields will be accessible through an automated process. Although this annex is informative implementers are strongly recommended to satisfy the guidance which it provides, in order to provide users with information about TLs in a consistent manner. Table F.1 Field name Human-readable? Machine-processable? Identification Tag TSL tag Scheme information TSL version identifier TSL sequence number TSL type Scheme operator name Scheme operator address Scheme name Scheme information URI Status determination approach Scheme type/community/rules Scheme territory TSL policy/legal notice Historical information period Pointers to other TSLs List issue date and time Next update Scheme extensions where recognized and meaningful where recognized TSP information TSP name TSP trade name TSP address TSP information URI TSP information extensions where recognized and meaningful where recognized Service information Service type identifier Service name Service digital identity Service current status Current status starting date and time Scheme service definition URI Service supply points TSP service definition URI Service information extensions where recognized and meaningful where recognized Historical service information Service type identifier Service name Service digital identity Service previous status Previous status starting date and time Service information extensions where recognized and meaningful where recognized TSL signature information Scheme identification Textual certificate details, time and date of signing Cryptographic data ETSI ETSI TS 119 612 V2.4.1 (2025-08) 72 Annex G (normative): Management and policy considerations G.0 General Specific criteria for the provision of revisions to TL information apply. These revisions will fall into the following categories. G.1 Change of scheme administrative information This category includes any changes to information concerning the scheme and which is embedded within the TL. Such changes could include, inter alia, change of scheme addresses, revisions to acceptance criteria, scheme policy. When these changes occur and are material changes to information included in the TL, the TL shall be re-issued. NOTE: If there are material changes to information directly referenced through the TL but the reference itself does not change then there will be no need to amend the TL. If the changes were the result of a change of ownership of the entity operating the scheme then the scheme should continue to operate with changes with regards to information related to the Scheme Operator and the TL being re-issued. G.2 Trust-service identification Whenever a scheme operator adds trust service to a TL, it is important to users of the TL to be able to unambiguously identify that service's status definition. While name and address may be highly relevant and therefore very important, the digital identity-field is the only option that can provide secure identification of the trust service and tokens which it supplies. G.3 Change of trust service status These changes are those directly affecting the inclusion or reported status of any trust service within the TL (and possibly also information concerning their provider) and whether the information is current or historical (e.g. the introduction of a new TSP and service; the revocation of a service). When any such change occurs the TL shall be re-issued with the previous current status becoming the most recent historical status and current status being amended to reflect the situation. The service which is effectively stopping should have its "Service current status" (see clause 5.5.4) revised to meaning "ceased" operations or "withdrawn" status and the previous status information placed into the "History information" (see clause 5.5.10) of the TL. This shall then be retained for the published retention period (since there may be requirements to check on services rendered during its period of activity). No service's "Historical information" shall be discarded. G.4 Change in trust service digital identity Where a service changes its "Service digital identity" (see clause 5.5.3): • In the case of a new public key (e.g. as a result of a re-branding or a renewal of associated digital data for security reasons), the service related to the new digital identity (public key) shall be added in the TL as a new service entry. As new service, the "History information" is absent. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 73 • In the case of a new certificate for the same public key, rules in clause 5.5.3 apply. Providing two or more certificates with the same public key is not regarded as two separate identifiers, but two representations of the same identifier provided they both have identical X.509 Subject Name values. When the new certificate is eligible, it may be added to the existing set of representations for the same public key; no service history instance shall be generated. G.5 Amendment response times Changes to any TL information shall be provided in a timely fashion, not exceeding 24 hours. In particular, once the decision to change the status of a listed certification or trust service is effective, the corresponding change should be implemented and the TL re-issued in less than four working hours. G.6 On-going verification of authenticity The frequency at which information within a TL will change is likely to be low. This could give a determined hacker sufficient time to replicate and replace all instances of a TL, IF they were able to replace all examples of the TL itself and a surrogate PKC for the TL scheme operator. This should be protected against by the scheme operator itself making frequent verification of its own TL and all authorized and recognized replications of it. In addition, the regular re-issuing of the TL, even when there is no change to any statuses within it, will also ensure that, at the least, the signature value changes periodically. G.7 User reference to TL Scheme operators should assist in this by offering additional services to notify when a new TL is issued, or to guarantee frequent re-issue of a TL at a frequency which may mean numerous re-issues without change of any services' status. However, the mechanisms proposed for having multiple copies of TLs existing contemporaneously are designed to cater for the low rate of information change already discussed, and these may not be suitable for frequent TL re-issue. G.8 TL size The present document provides a number of fields in which the scheme operator may choose to provide actual natural language text in preference to a URI or other reference to a source of information. Clearly the inclusion of large quantities of text will have a direct influence on download and parsing times, this especially so if e.g. it relates to the descriptions of services, and the scheme has a large number of trust services listed. Implementers should therefore take advantage of the opportunity to use URIs and limit embedded text as much as is reasonable, accounting for the overall size of the TL and the available bandwidth and storage capacities of the typical user of their TL. Referencing other documents also allows advantage to be taken of more sophisticated presentation options which formats such as PDF and other formats enable. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 74 Annex H (informative): Locating a TL H.1 Introduction This annex provides guidance on how to locate TLs. H.2 Locating a TL In order to allow access to the trusted lists of all Member States in an easy manner, the European Commission publishes a central list with links to the locations where the trusted lists are published as notified by Member States. This central list, called the List Of Trusted Lists (LOTL), is available in both a human readable format and in a format suitable for automated (machine) processing XML. With regards to PKI based services, the country related information of the issuer of a trust service token (e.g. (qualified) certificates, time-stamping tokens, signed OCSP responses, signed CRLs) provides as hint the MS indication where the TL can be retrieved from. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 75 Annex I (informative): Usage of trusted lists I.1 Introduction This annex describes an example of model for the usage of trusted lists. This model is not aimed to restrict how an implementation can be built but identifies the functionality that can be expected from systems applying trusted lists. I.2 Example of model for the usage of trusted lists in the context of signature validation Figure I.1: Example of model for the usage of TL in the context of signature validation Information from trusted lists can be used in the certificate path validation process for an application as follows: • Certificate path validation based upon X.509 (see IETF RFC 5280 [12]) or ETSI TS 102 853 [i.1] on signature verification requires information on CA certificates that can be used as trust anchors for an application requiring a particular trust service. • When "Service digital identifiers" are used as trust anchors in the context of validating electronic signatures for which signer's certificate is to be validated against TL information, only the public key and the associated subject name are needed as trust anchor information. When more than one certificate is representing the public key identifying the service, they are considered as trust anchor certificates conveying identical information with regards to the information strictly required as Trust Anchor information. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 76 This information can be derived from one or more trusted lists as follows: a) The source of the trusted list is validated to ensure that the information comes from a trusted issuer (e.g. using a digital signature validated using a certificate known to come from a recognized authority). b) CA entries are selected from the trusted list based on the rules of the applicable trust policy. c) CA certificates from the selected entries, optionally with associated meta data, are held with the trust anchors. d) The trusted list is checked regularly for changes to the service status of the CAs in the trust anchor store which were previously loaded from the trusted list. The trusted list is also regularly checked for new entries. e) A human user or operator can be asked for confirmation before an entry is added to the trust anchors store. f) CA information from multiple trusted lists can be loaded into the trust anchors store. CA Information from trusted lists can be combined with CA information in the trust anchor store or from any trusted CA certificate store loaded by other means, manually or in an automated way. I.3 Policy elements for trust anchor management Policy elements for trust anchor management can specify the types, status and any other relevant properties of trust services or other trusted entities whose certificates are acceptable as trust anchors. These policy elements can be defined, locally, for a community of users, by the application provider or by the system provider. An example policy rule for an application that requires TSPs supervised or accredited for issuing qualified certificates in line with Directive 1999/93/EC [i.3] for qualified electronic signatures can be: i) ServiceType equals: http://uri.etsi.org/TrstSvc/Svctype/CA/QC; and ii) ServiceStatus is: - Under Supervision (http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision); or - Supervision of Service in Cessation (http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/ supervisionincessation); or - Accredited (http://uri.etsi.org/TrstSvc/Svcstatus/TrustedList/Svcstatus/accredited). ETSI ETSI TS 119 612 V2.4.1 (2025-08) 77 Annex J (normative): Migration of EU MS trusted lists in the context of Regulation (EU) No 910/2014 The migration of the 'Service current status' value of services listed in EU MS trusted list as of the day before the date Regulation (EU) No 910/2014 [i.10] applies (i.e. 30 June 2016) shall be executed on the day the Regulation applies (i.e. 01 July 2016) as follows: a) For each service of type "http://uri.etsi.org/TrstSvc/Svctype/CA/QC": i) A change in the service approval status shall occur as follows and information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6): 1) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted". 2) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked", shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn". ii) When the listed service is further identified by using the "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/RootCA-QC" identifier which is included in the additionalServiceInformation extension (clause 5.5.9.4) within a Service information extension (clause 5.5.9), this information shall be kept in the new 'Service current status' related information. iii) The service type shall be further specified through the use of an additionalServiceInformation extension (clause 5.5.9.4) within a Service information extension (clause 5.5.9) by using the identifier indicating that the service is "for electronic signatures", i.e. that the nature of the qualified certificates for which the qualified status has been granted as being qualified certificates for electronic signatures (as specified in clause 5.5.9.4). iv) When the listed service was making use of a Qualifications extension (clause 5.5.9.2) within a Service information extension (clause 5.5.9), the same used extension shall be kept in the new 'Service current status' related information but the used qualifiers shall be migrated as follows: 1) The "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithSSCD" qualifier shall be migrated to "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithQSCD". 2) The "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoSSCD" qualifier shall be migrated to "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoQSCD". 3) The "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCSSCDStatusAsInCert" qualifier shall be migrated to "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDStatusAsInCert ". 4) The "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement" qualifier shall be kept and complemented with the http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig qualifier. 5) The "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForLegalPerson" qualifier shall be migrated to "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified". v) From the time the above migration has been executed (i.e. no later than 1 July 2016), a change in the service approval status value may occur in accordance with the requirements laid down in the Regulation and the applicable national approval scheme and supervisory activities. In that case, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). ETSI ETSI TS 119 612 V2.4.1 (2025-08) 78 vi) When no conformity assessment report is submitted by the corresponding TSP to the supervisory body by which it is supervised by the one year anniversary day of the Regulation application (i.e. 1 July 2017), a change in the service approval status value shall occur from the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" to http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn" unless the 'Service current status' is already set to this latter value. b) For each service of type "http://uri.etsi.org/TrstSvc/Svctype/CertStatus/OCSP/QC" and of type "http://uri.etsi.org/TrstSvc/Svctype/CertStatus/CRL/QC": i) A change in the service approval status shall occur as follows and information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6): 1) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted". 2) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked", shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn". ii) The service type shall be further specified through the use of an additionalServiceInformation extension (clause 5.5.9.4) within a Service information extension (clause 5.5.9) by using the identifier indicating that the service is "for electronic signatures", i.e. that the nature of the qualified certificates for which the qualified status has been granted as being qualified certificates for electronic signatures (as specified in clause 5.5.9.4). iii) From the time the above migration has been executed (i.e. no later than 1 July 2016), a change in the service approval status value may occur in accordance with the requirements laid down in the Regulation and the applicable national approval scheme and supervisory activities. In that case, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). iv) When no conformity assessment report is submitted by the corresponding TSP to the supervisory body by which it is supervised by the one year anniversary day of the Regulation application (i.e. 1 July 2017), a change in the service approval status value shall occur from the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" to http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn" unless the 'Service current status' is already set to this latter value. c) For each service of type "http://uri.etsi.org/TrstSvc/Svctype/TSA/QTST", of type "http://uri.etsi.org/TrstSvc/Svctype/EDS/Q", of type "http://uri.etsi.org/TrstSvc/Svctype/EDS/REM/Q", of type "http://uri.etsi.org/TrstSvc/Svctype/QESValidation/Q", and of type "http://uri.etsi.org/TrstSvc/Svctype/PSES/Q": i) A change in the service approval status shall occur as follows and information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). 1) The service having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn". ETSI ETSI TS 119 612 V2.4.1 (2025-08) 79 2) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked", shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn". ii) From the time the above migration has been executed (i.e. no later than 1 July 2016), a change in the service approval status value may occur in accordance with the requirements laid down in the Regulation and the applicable national approval scheme and supervisory activities. In that case, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). For services of type "http://uri.etsi.org/TrstSvc/Svctype/QESValidation/Q", and of type "http://uri.etsi.org/TrstSvc/Svctype/PSES/Q", the service type shall be further specified through the use of an additionalServiceInformation extension (clause 5.5.9.4) within a Service information extension (clause 5.5.9) by using the identifier indicating whether it is provided for electronic signatures and/or for electronic seals (as specified in clause 5.5.9.4). d) For each service of a type defined in clause 5.5.1.2: i) A change in the service approval status shall occur as follows and information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6): 1) The service having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/recognisedatnationallevel". 2) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked", shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/deprecatedatnationallevel". ii) From the time the above migration has been executed (i.e. no later than 1 July 2016), a change in the service approval status value may occur in accordance with the requirements laid down in the Regulation and the applicable national approval scheme and supervisory activities. In that case, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). When applicable, the service type shall be further specified through the use of an additionalServiceInformation extension (clause 5.5.9.4) within a Service information extension (clause 5.5.9) by using the identifier indicating whether it is provided for electronic signatures, for electronic seals and/or for web site authentication (as specified in clause 5.5.9.4). e) For each service of a type defined in clause 5.5.1.3: i) A change in the service approval status shall occur as follows and information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6): 1) The service having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/undersupervision", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionincessation", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accredited", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/setbynationallaw" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/recognisedatnationallevel". 2) The services having, as of the day before the date Regulation applies, 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked://uri.etsi.org/TrstSvc/Trusted List/Svcstatus/deprecatedbynationallaw" shall be given the new 'Service current status' value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/deprecatedatnationallevel". ETSI ETSI TS 119 612 V2.4.1 (2025-08) 80 ii) From the time the above migration has been executed (i.e. no later than 1 July 2016), a change in the service approval status value may occur in accordance with the requirements laid down in the Regulation and the applicable national approval scheme and supervisory activities. In that case, information on the previous approval status shall be provided in descending order of status change date and time (i.e. the date and time on which the subsequent approval status became effective) by making use of a service history instance (clause 6). ETSI ETSI TS 119 612 V2.4.1 (2025-08) 81 History Document history V1.1.1 June 2013 Publication V1.2.1 April 2014 Publication V2.1.1 July 2015 Publication V2.2.1 April 2016 Publication V2.3.1 November 2024 Publication V2.4.1 August 2025 Publication
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
1 Scope
|
The present document defines: 1) A test suite for supporting interoperability tests within the field of Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 532-1 [3] where sender and all the entities at receiving side are subscribed to the same REMS. Test cases are defined for REMSs operating Store&Forward and for REMSs operating Store&Notify styles. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and no intermediate REMS is required for relaying REM messages between them. Test cases are defined for covering the three possible different combinations of styles, namely Store&Forward to Store&Forward, Store&Forward to Store&Notify, and Store&Notify to Store&Forward. - Environments that correspond to the extended model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and intermediate REMSs are required for relaying REM messages between them. Test cases are defined for covering two different combinations of styles, namely Store&Forward to Store&Forward to Store&Forward, Store&Forward to Store&Notify to Store&Forward. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
2 References
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 532-1: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 1: Framework and Architecture". [4] ETSI EN 319 532-2: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 2: Semantic Contents". [5] ETSI EN 319 532-3: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 3: Formats". [6] ETSI EN 319 532-4: "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 4: Interoperability profiles". [7] IETF RFC 8118: "The application/pdf Media Type". ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 7 [8] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". [9] IETF RFC 2183: "Communicating Presentation Information in Internet Messages: The Content- Disposition Header Field". [10] IETF RFC 5751: "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification". [11] IETF RFC 5322: "Internet Message Format". [12] IETF RFC 2854: "The 'text/html' Media Type". [13] IETF RFC 7303: "XML Media Types". [14] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 534-1: "Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Registered Electronic Mail Services; Part 1: Testing conformance".
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
3 Definition of terms, symbols and abbreviations
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI EN 319 532-1 [3] apply.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
3.2 Symbols
|
Void.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACC_REJ_EXP ACCeptanceREJectionEXPiry CONS_ACC CONSignmentACCeptance CONS_NOT CONSignmentNOTification CONS_NOT_FAIL CONSignmentNOTificationFAILure CONS_REJ CONSignmentREJection CONT_CONS CONTentCONSignment CONT_CONS_FAIL CONTentCONSignmentFAILure CONT_HAND CONTentHANDover CONT_HAND_FAIL CONTentHANDoverFAILure ERDS Electronic Registered Delivery EV_SET EVidence SET IREMS Intermediate Registered Electronic Mail Service ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 8 NOT_F_ACC NOTificationForACCeptance NOT_F_ACC_FAIL NOTificationForACCeptanceFAILure REC_F_NERDS RECeivedFromNonERDS REL_ACC RELayACCeptance REL_FAIL RELayFAILure REL_REJ RELayREJection REL_T_NERDS RELayToNonERDS REL_T_NERDS_FAIL RELayToNonERDSFAILure REM Registered Electronic Mail REMS Registered Electronic Mail Service RREM Recipient's Registered Electronic Mail RREMS Recipient's Registered Electronic Mail Service S&F Store and Forward S&N Store and Notify S/MIME Secure/Multipurpose Internet Mail Extensions SCN_ID Scenario Identifier SMIME Secure/Multipurpose Internet Mail Extensions SREM Sender's Registered Electronic Mail SREMS Sender's Registered Electronic Mail Service SUB_ACC SUBmissionACCeptance SUB_REJ SUBmissionREJection
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
4 Technical approach
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [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 REMSs, and the entities at receiving side - one or more recipients and/or one or more recipients' delegates -, which exchange different REM messages with time. Each scenario corresponds to one of the three models presented in ETSI EN 319 532-1 [3]. 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 all the REM messages exchanged by the participating entities. This list of exchanged REM 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 REM messages. One scenario may be used for defining several test cases depending on: - The specific components of each exchanged REM message (suppressing or adding an optional header, or changing the value of a certain header field results in a different REM 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). ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 9 - A named set of additional requirements (for instance whether the original message contains or not attachments, is signed, is encrypted, etc.). - In negative test cases, i.e. test cases where the service failed in consigning or handing over the message to one or more recipients, the reason(s) causing that failure. This means that one test case corresponds to one scenario where all the exchanged REM 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>, <REM message identifier 1>, <REM message identifier 2>, …, <REM message identifier N>, <additional requirements set identifier>, <failure reasons>? Where: - <Receiving side identifier> is the identifier assigned to a certain set of entities at receiving side; - <REM message identifier I> is the identifier of a specific instantiation of the aforementioned REM message, namely: REM payload, REM notification, REM Receipt, or REM dispatch, which are defined in clauses 6.3, 6.4, 6.5 and 6.6 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. - <failure reason(s)>? is the reason(s) that caused that the service failed in consigning or handing over the message to the recipient(s). It shall only appear in negative test cases. 2) Clauses 6.3, 6.4, 6.5 and 6.6 define specific instantiations of REM payloads, REM notifications, REM receipts and REM dispatches respectively. Each type of REM message is composed by several MIME sections, with their headers and bodies. One specific instantiation of a certain type of REM message is composed by one specific combination of MIME sections. Each MIME section in turn is formed by one certain combination of headers and has a specific value in its body. The present document defines a number of combinations of MIME sections in clauses 6.2.2, 6.2.3, 6.2.4.3, 6.2.4.4, 6.2.5, 6.2.6, 6.2.7 and 6.2.8, 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 REM message as follows: REM message instance = Sequence(<outer most MIME header identifier>, <signed data MIME header section identifier>, <multipart/alternative free text MIME section identifier>, <multipart/alternative html MIME section>, <original message MIME section identifier>?, <extension MIME section identifier>*, <ERDS evidence MIME section identifier>*,<signature MIME section identifier>) Where ? indicates a cardinality 0 or 1 for the affected MIME section, and * indicates a cardinality of 0 or more for the affected MIME sections. 3) Clauses 6.2.2, 6.2.3, 6.2.4.3, 6.2.4.4, 6.2.5, 6.2.6, 6.2.7 and 6.2.8 define specific instances for the REMS relay metadata MIME Header, the signed data MIME header, the multipart/alternative free text MIME section, the multipart/alternative html MIME section, original message MIME section, the extension MIME section, the ERDS evidence MIME section, and the signature MIME section respectively. Each clause defines different instances of the aforementioned headers and sections and assigns them unique identifiers that are used for defining specific instances of the different REM messages as shown above. Once this level is reached, the specific test case is fully defined as: a scenario where fully defined, REM messages are exchanged between a specific set participating entities, and where a specific set of additional requirements are imposed.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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, define a new set as specified in clause 7.3. The sender is always present by default. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 10 2) Define the REMSs that will participate in the test case. 3) If the set of participating REMSs 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 REM messages generated by the actors as they go through the sequence of actions. For each message: a) Identify its MIME sections. b) For each MIME section identified different than the ERDS MIME sections, check if its header fields combination and the corresponding bodies have already been defined in the present document. If not, add the required combination of header fields and body values to the repertoire of named combinations to the section defining instances of the aforementioned MIME section as in the corresponding clauses (clauses 6.2.2, 6.2.3, 6.2.4.3, 6.2.4.4, 6.2.6 or 6.2.8). c) List all the REM messages exchanged as parameters of the scenario. d) Identify the ERDS evidence format and the set of ERDS evidence for each REM 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 23 (clause 7.2).
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5 Scenarios
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 REMS. Clause 5.4 defines scenarios where the sender and the recipient(s) are subscribed to different REMSs and there are not intermediate REMSs between them. Clause 5.5 defines scenarios where sender is subscribed to a REMS and the recipient(s) is(are) not subscribed to the same REMS and there are one or more intermediate REMSs. Unless anything said against it, all the scenarios assume that there are N entities at the receiving side. Unless anything said against it, all the ERDS evidences that can contain details of different entities at the receiving side shall incorporate the details of the entire set of N entities at the receiving side. Table 1 shows the template for defining one scenario. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 11 Table 1: Template for the tabular definition of one scenario Scenario id: <SCN_ID> Purpose Parameter: <REMS_receipt>_with_XML_SUB_REJ <Parameter 1 that helps to fully specify the scenario. Their number depends on the specific scenario> Var EV_SET#1 = {…, …} Named sets of ERDS evidence used in the definition of the scenario. Parameter: <Parameter 2> Var EV_SET#2 = {… …} Parameter: <Parameter N> Var EV_SET#N = {… …} Sequence of actions <SEQUENCE OF ACTIONS. THERE IS ONE COLUMN PER PARTICIPATING ACTOR> # Sender REMS 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 REM message, etc. 1 Sender sends original message 2 Rejects submission. Generates XML_SUB_REJ ERDS evidence 3 Generates <REMS_receipt>_with_XML_SUB_REJ 4 Sends <REMS_receipt>_with_XML_SUB_REJ 5 Receives <REMS_receipt>_with_XML_SUB_REJ 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 REM 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 REM 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 REMSs, 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 REM messages, generation of ERDS evidence, acceptance of REM messages, rejection of REM messages, consignment of REM messages, retrieval of REM messages by entities at receiving side, failures, etc.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.2 Abbreviations used in tables defining scenarios
|
The present clause shows some abbreviations (which have already been anticipated in clause 3.3 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 534-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 ETSI EN 319 522-1 [1] specify a XML format for ERDS evidence, but also allows that they are PDF documents. The present document differentiates both cases using a prefix for the ERDS evidence abbreviations as follows: • XML_ prefix indicates that the identified object is a XML ERDS evidence. • PDF_ prefix that the identified object is a PDF ERDS evidence. EXAMPLE: The abbreviation for the XML SubmissionAcceptance ERDS evidence will be XML_SUB_ACC. The abbreviation for the PDF SubmissionAcceptance ERDS evidence will be PDF_SUB_ACC. The tables defining the Scenarios use the following abbreviations for the different participating REMSs: • SREMS stands for the REMS serving the sender, in the scenarios where it is different from the REMS serving the entities at receiving side. • RREMS stands for the REMS serving the entities at receiving side, in the scenarios where it is different from the REMS serving the sender. • IREMS stands for a REMS that directly serves neither the sender nor the recipient(s)/recipient's delegate, but instead is an intermediate REMS that relays REM messages from SREMS to RREMS and from RREMS to SREMS.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.3 Black-box model scenarios
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.3.1 Introduction
|
This clause defines scenarios where the sender and the entities at the receiving side are subscribed to the same REMS and consequently REM messages are not relayed between different REMSs. Clause 5.3.2 defines scenarios where the REMS operates in Store and Forward style. Clause 5.3.3 defines scenarios where the REMS operates in Store and Notify style.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.3.2 Scenarios for Store and Forward style
|
Table 3 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same REMS operating in Store and Forward style. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 13 Table 3: Scenarios for intra-REMS operating in Store and Forward style (1/13) Scenario id: REMS_SF#1 Purpose Parameter: <REMS_receipt>_with_XML_SUB_REJ The simplest negative scenario: The sender sends the original message to one entity. The REMS rejects the original message submitted by the sender because of one reason, and sends back a REM receipt with the SubmissionRejection ERDS evidence (<REMS_receipt>_with_XML_S UB_REJ). Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Rejects submission. Generates SUB_REJ ERDS evidence with details of the N recipients 3 Generates <REMS_receipt>_with_XML_SUB_REJ 4 Sends REMS receipt to the sender 5 Receives REMS receipt NOTE 1: As it has been anticipated, negative scenarios like this one do not mention the reason for failure. This is a separated parameter for the test case definition in clause 8. Table 3a: Scenarios for intra-REMS operating in Store and Forward style (2/13) Scenario id: REMS_SF#2 Purpose Parameter: <REMS_receipt>_with_XML_SUB_REJ Var EV_SET#1 = {2 XML_SUB_REJ } Modified scenario REMS_SF#1: The sender sends the original message to N different entities. The REMS rejects the original message submitted by the sender because of one reason for M entities at the receiving side and because of another reason for the other N-M entities. It generates two SubmissionRejection ERDS evidences and sends back a REM receipt with these two SubmissionRejection ERDS evidences (<REMS_receipt>_with_XML_S UB_REJ). Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Rejects submission. Generates 2 XML_SUB_REJ ERDS evidences. One of them with details of M entities; the other with details of N-M entities 3 Generates <REMS_receipt>_with the 2_aforementioned XML_SUB_REJ 4 Sends REMS receipt to the sender 5 Receives REMS receipt ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 14 Table 3b: Scenarios for intra-REMS operating in Store and Forward style (3/13) Scenario id: REMS_SF#3 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC , XML_CONT_CONS} The simplest successful scenario: The sender sends the original message to several entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_S UB_ACC), and consigns them to the receiving entities. After that the REMS generates and sends back to the sender a REM receipt with one SubmissingAcceptance ERDS evidence and one ContentConsignment ERDS evidence (<REMS_receipt>_with_EV_SE T#1) to the sender. Each evidence includes the details of all the (N) entities at receiving side. Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC for the N receiving entities 4 Consigns REM dispatch to receiving side 5 Generates one XML_CONT_CONS ERDS evidence with details of the N recipients <REM_dispatch>_with_XML_SUB_AC C consigned to receiving side 6 Generates <REMS_receipt>_with_EV_SET#1 7 Sends it back to sender 8 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 15 Table 3c: Scenarios for intra-REMS operating in Store and Forward style (4/13) Scenario id: REMS_SF#4 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC , XML_CONT_CONS, XML_CONT_CONS_FAIL} As scenario REMS_SF#3 but now one of the N consignments fails: The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_S UB_ACC), and tries to consign them to the receiving entities, but now one consignment fails, which implies the generation of 1 XML_CONT_CONS_FAIL ERDS evidence. The REMS generates a REMS receipt reporting the acceptance of submission, the successful consignment of N-1 REM dispatches and the failure of 1 REM dispatch (<REMS_receipt>_with_EV_SE T#1). Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC for the N receiving entities 4 Consigns REM dispatch to receiving side 5 Generates one XML_CONT_CONS ERDS evidence with details of the N-1 entities AND one XML_CONT_CONS_FAIL with details of one entity N-1 <REM_dispatch>_with_XML_SUB_AC C consigned to receiving side 1 fails 6 Generates <REMS_receipt>_with_EV_SET#1 7 Sends it back to sender 8 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 16 Table 3d: Scenarios for intra-REMS operating in Store and Forward style (5/13) Scenario id: REMS_SF#5 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC , XML_CONT_CONS, 2 XML_CONT_CONS_FAIL} As scenario REMS_SF#3 but now two consignments fail, and each one for different reason, which implies the generation of two XML_CONT_CONS_FAIL ERDS evidences: The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_S UB_ACC), and tries to consign them to the receiving entities, but now two consignment fail, each one by a different reason. The REMS generates a REMS receipt reporting the acceptance of submission, the successful consignment of N-2 REM dispatches and the failure of 2 REM dispatches, which include 2 ERDS evidence (<REMS_receipt>_with_EV_SE T#1, which include 2 XML_CONT_CONS_FAIL). Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC for the N receiving entities 4 Consigns REM dispatch to receiving side 5 Generates one XML_CONT_CONS ERDS evidence with details of the N-2 entities AND 2 XML_CONT_CONS_FAIL with details of one entity N-2 <REM_dispatch>_with_XML_SUB_AC C consigned to receiving side The other 2 fail, each one for a different reason 6 Generates <REMS_receipt>_with_EV_SET#1 7 Sends it back to sender 8 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 17 Table 3e: Scenarios for intra-REMS operating in Store and Forward style (6/13) Scenario id: REMS_SF#6 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND} Successful scenario: The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_S UB_ACC), and successfully consigns them to the N entities. After the successful consignment, all the entities at the receiving side successfully retrieve the messages. The REMS generates a REMS receipt (<REMS_receipt>_with_EV_SE T#1) with following ERDS evidence: one SubmissiongAcceptance, one ContentConsignment, and one ContentHandover. Each ERDS evidence includes the details of all the (N) entities at the receiving side. Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC 4 Consigns them to the receiving side 5 Generates one XML_CONT_CONS ERDS evidence with details of the N recipients N <REM_dispatch>_with_XML_SUB_AC C consigned to receiving side 6 All the entities retrieve the REM dispatch 7 Generates one XML_CONT_HAND ERDS evidence with details of the N recipients N <REM_dispatch>_with_XML_SUB_AC C handed over to receiving side 8 Generates <REMS_receipt>_with_EV_SET#1 9 Receives <REMS_receipt>_with_EV_SET#1 NOTE 2: The former scenarios explicitly mention in the Sequence of Actions columns that the ERDS evidences include details of the N recipients. As it has been anticipated above, hereinafter the absence of such explicit mention will be interpreted as an explicit mention of this fact. Explicit details will appear wherever this is not true. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 18 Table 3f: Scenarios for intra-REMS operating in Store and Forward style (7/13) Scenario id: REMS_SF#7 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_CONT_HAND_FAIL} As scenario REMS_SF#3 but now the handover of the REM dispatch is performed, and one of the handing over fails: The sender sends the original message to several entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_SUB_ACC), and successfully consigns them to the N receiving entities. N-1 receiving entities successfully hand over the REM dispatch, but 1 entity fails. The REMS generates an ERDS receipt (<REMS_receipt>_with_EV_SET#1) with following ERDS evidence: one SubmissiongAcceptance, one ContentConsignment, one ContentHandover, and one ContentHandoverFailure. Each evidence includes the details of the entire set of recipient entities affected by the event that it reports, namely: • XML_SUB_ACC includes details of the N entities at the receiving side; • XML_CONT_CONS includes details of the N entities at the receiving side; • XML_CONT_HAND includes details of the N-1 entities that the service handed over the message to; • XML_CONT_HAND_FAIL includes the details of the entity that the service could not hand over the message to. Parameter: REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates one XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC 4 Consigns them to the receiving side 5 Generates one XML_CONT_CONS ERDS evidence <REM_dispatch>_with_XML_SUB_ACC consigned to receiving side 6 Entities try to retrieve the REM dispatch, but one fails 7 Generates one XML_CONT_HAND ERDS one evidence for N-1 entities and one XML_CONT_HAND_FAIL ERDS evidence for one entity N-1 <REM_dispatch>_with_XML_SUB_ACC handed over to receiving side. One fails 8 Generates <REMS_receipt>_with_EV_SET#1 9 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 19 Table 3g: Scenarios for intra-REMS operating in Store and Forward style (8/13) Scenario id: REMS_SF#8 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, 2 XML_CONT_HAND_FAIL} As scenario REMS_SF#3 but now the handover of the REM dispatch is performed, and two of the handing overs fail for different reasons. The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_SUB_ACC), and successfully consigns them to the N receiving entities. N-2 receiving entities successfully hand over the REM dispatch, but 2 entities fail. Parameter: REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates one XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC 4 Consigns them to the receiving side 5 Generates one XML_CONT_CONS ERDS evidence <REM_dispatch>_with_XML_SUB_A CC consigned to receiving side 6 Entities try to retrieve the REM dispatch, but one fails 7 Generates one XML_CONT_HAND ERDS one evidence for N-2 entities and 2 XML_CONT_HAND_FAIL ERDS evidences, each one for a different entity N-2 <REM_dispatch>_with_XML_SUB_A CC handed over to receiving side. Two of them fail 8 Generates <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 20 Scenario id: REMS_SF#8 Purpose 9 Receives <REMS_receipt>_with_EV_SET#1 The REMS generates an ERDS receipt (<REMS_receipt>_with_EV_SET#1) with the following ERDS evidence: one SubmissiongAcceptance, one ContentConsignment, one ContentHandover, and two ContentHandoverFailure. Each evidence includes the details of the entire set of recipient entities affected by the event that it reports, namely: • XML_SUB_ACC includes details of the N entities at the receiving side; • XML_CONT_CONS includes details of the N entities at the receiving side; • XML_CONT_HAND includes details of the N-2 entities that the service handed over the message to; • Each one of the two XML_CONT_HAND_FAIL ERDS evidence includes the details of the entity that the service could not hand over the message to with the reasons for not handing over. Hereinafter, the scenarios do not show handing over, but only consignment. However, a set of scenarios including handing over could be easily built based on them. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 21 Table 3h: Scenarios for intra-REMS operating in Store and Forward style (9/13) Scenario id: REMS_SF#9 Purpose Parameter: <REM_dispatch> Var EV_SET#1 = {XML_SUB_ACC,XML_CONS_NOT, XML_CONT_CONS} As scenario REMS_SF#3 but now the REMS sends a REMS notification of consignment to receiving side. The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_SUB_ACC), and successfully consigns them to the N receiving entities. The REMS generates N notifications of consignment (<REMS_notification>_of_Consignment) for the receiving entities and sends them. The REMS generates one REMS receipt (<REMS_receipt>_with_EV_SET#1) with the following ERDS evidence: one SubmissiongAcceptance, one ContentConsignment, and one ContentConsignmentNotification. Each evidence includes the details of the entire set of recipient entities affected by the event that it reports, namely: • XML_SUB_ACC includes details of the N entities at the receiving side; • XML_CONT_CONS_NOT includes details of the N entities at the receiving side; • XML_CONT_CONS includes details of the N entities at the receiving side. Parameter: <REMS_notification>_of_Consignment Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends the original message 2 Accepts submission. Generates one XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_ACC 4 Consigns <REM_dispatch>_with_XML_SUB_ACC to receiving side 5 N <REM_dispatch>_with_XML_SUB_A CC consigned to receiving side 6 Generates one XML_CONT_CONS ERDS evidence 7 Generates <REMS_notification>_of_Consignment for N entities 8 Sends consignment notification to receiving side 9 Generates one XML_CONS_NOT ERDS evidence for N entities <REMS_notification>_of_Consignmen t received by receiving side 10 Generates <REMS_receipt>_with_EV_SET#1 11 Sends it to the sender 12 Receives <REMS_receipt>_with_XML_XML_EV_ SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 22 Table 3i: Scenarios for intra-REMS operating in Store and Forward style (10/13) Scenario id: REMS_SF#10 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, XML_CONS_NOT_FAIL } As scenario REMS_SF#3 but now REMS sends notifications of consignment and one of the REMS consignment notifications fails. The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_SUB_ACC), and successfully consigns them to the N receiving entities. The REMS generates N notifications of consignment (<REMS_notification>_of_Consignment) for the receiving entities and sends them, but one fails. The REMS generates one REMS receipt (<REMS_receipt>_with_EV_SET#1) with the following ERDS evidence: one SubmissiongAcceptance, one Parameter: <REMS_notification>_of_Consignment Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends the original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates N <REM_dispatch>_with_XML_SUB_ACC 4 Consigns REM dispatch to the receiving side N <REM_dispatch>_with_XML_SUB_A CC consigned to receiving side 5 Generates <REMS_notification>_of_Consignment for N entities REM dispatch with the original message AND REMS receipt consigned to recipient 6 Tries to send N <REMS_notification>_of_Consignment but one fails. 7 Generates one XML_CONS_NOT ERDS evidence for N-1 entities (the N-1 whose notifications were sent) and one XML_CONS_NOT_FAIL ERDS evidence corresponding to the notification that failed N-1 <REMS_notification>_of_Consignmen t are received successfully; 1 fails 8 Generates <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 23 Scenario id: REMS_SF#10 Purpose 9 Receives <REMS_receipt>_with_EV_SET#1 ContentConsignment, one ContentConsignmentNotification, and one ContentConsignmentNotificationFailure. Each evidence includes the details of the entire set of recipient entities affected by the event that it reports, namely: • XML_SUB_ACC includes details of the N entities at the receiving side; • XML_CONT_CONS_NOT includes details of the N-1 entities at the receiving side to whom the REMS has sent a consignment notification; • XML_CONT_CONS includes details of the N entities at the receiving side; • XML_CONT_CONS_NOT_FAIL including details of the entity at the receiving side for whom the notification has failed and the reason for failure. Table 3j: Scenarios for intra-REMS operating in Store and Forward style (11/13) Scenario id: REMS_SF#11 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, 2 XML_CONS_NOT_FAIL } As scenario REMS_SF#3 but now REMS sends notifications of consignment and two of the REMS consignment notifications fail due to different reasons. This implies the generation of two XM_CONST_NOT_FAIL ERDS evidences. The sender sends the original message to N entities. The REMS accepts the submission of the original message, generates as many REM dispatches as required by the number of entities in the receiving side, enclosing the original message and the SubmissionAcceptance ERDS evidence (<REM_dispatch>_with_XML_SUB_ACC), and successfully consigns them to the N receiving entities. Parameter: <REMS_notification>_of_Consignment Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends the original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates N <REM_dispatch>_with_XML_SUB_ACC 4 Consigns REM dispatch to the receiving side N <REM_dispatch>_with_XML_SUB_A CC consigned to receiving side 5 Generates <REMS_notification>_of_Consignment for N entities REM dispatch with the original message AND REMS receipt consigned to recipient 6 Sends N <REMS_notification>_of_Consignment but 2 of them fail. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 24 7 Generates 1 XML_CONS_NOT_FAIL ERDS evidence for two entities and one XML_CONS_NOT ERDS evidence for N-2 entities N-2<REMS_notification>_for Consignment are received successfully; 2 <REMS_notification>_for Consignment fail The REMS generates N notifications of consignment (<REMS_notification>_of_Consignment) for the receiving entities and sends them, but two of them fail. The REMS generates one REMS receipt (<REMS_receipt>_with_EV_SET#1) with the following ERDS evidence: one SubmissiongAcceptance, one ContentConsignment, one ContentConsignmentNotification, and one ContentConsignmentNotificationFailure. Each evidence includes the details of the entire set of recipient entities affected by the event that it reports, namely: • XML_SUB_ACC includes details of the N entities at the receiving side; • XML_CONT_CONS_NOT includes details of the N-2 entities at the receiving side; • XML_CONT_CONS includes details of the N entities at the receiving side; • XML_CONT_CONS_NOT_FAIL includes details of 2 the entities at the receiving side that did not receive the consignment notification. 8 Generates <REMS_receipt>_with_EV_SET#1 9 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 25 Table 3k: Scenarios for intra-REMS operating in Store and Forward style (12/13) Scenario id: REMS_SF#12 Purpose Parameter: <REM_payload> Var EV_SET#1 = {XML_SUB_ACC, XML_CONT_CONS} As scenario REMS_SF#3 but now the original message and the ERDS evidence travel in different REM messages to the receiving side. Parameter: <REMS_receipt_1>_with_XML_SUB_ACC Parameter: <REMS_receipt_2>_with_XML_EV_SET#1 Parameter: <REMS_receipt>_with_EV_SET#1 # Sender REMS Receiving side 1 Sender sends the original message 2 Accepts submission. Generates one XML_SUB_ACC ERDS evidence 3 Generates <REM_payload> 4 Generates <REMS_receipt_1>_with_XML_SUB_ACC 5 Consigns <REM_payload> and <REMS_receipt_1>_with_XML_SUB_ACC to the receiving side 6 Generates one XML_CONT_CONS ERDS evidence <REM_payload>AND <REMS_receipt_1>_with_XML_SUB_A CC consigned to receiving side 7 Generates <REMS_receipt_2>_with_EV_SET#1 8 Receives <REMS_receipt_2>_with_EV_SET#1 Sends it to the sender NOTE 3: It is possible to define a set of scenarios covering different types of failures in consignment and/or handover, and/or notifications as for the former test cases where ERDS evidences and original messages travelled together within REM dispatches. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 26 Table 3l: Scenarios for intra-REMS operating in Store and Forward style (13/13) Scenario id: REMS_SF#13 Purpose Parameter: <REM_payload> As scenario REMS_SF#3 but now the REMS generates and sends an REMS receipt as soon as it generates the corresponding ERDS Evidence. Parameter: <REMS_receipt>_with_XML_SUB_ACC Parameter: <REMS_receipt>_with_XML_CONT_CONS Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REMS receipt>_with_XML_SUB_ACC and sends it to both sender and receiving side 4 Sends <REMS receipt>_with_XML_SUB_ACC to both sender and receiving side 5 Sender receives <REMS receipt>_with_XML_SUB_ACC Entities in receiving side receive <REMS receipt>_with_XML_SUB_ACC 6 Generates <REM_payload>_ for the N receiving entities 7 Consigns REM payload to receiving side 8 Generates one XML_CONT_CONS ERDS evidence with details of the N recipients <REM_payload>_ to receiving side 9 Generates <REMS_receipt>_with_XML_CONT_CONS 10 Sends <REMS_receipt>_with_XML_CONT_CONS back to sender 11 Receives <REMS_receipt>_with_XML_CONT_CONS NOTE 4: It is possible to define a set of scenarios where: 1) each time the REMS generates an ERDS evidence, it generates and sends an <ERDS receipt> immediately after; and 2) the original message travels within an <REM payload>. This set would cover different types of failures in consignment and/or handover, and/or notifications as for the former test cases where ERDS evidences and original messages travelled together within REM dispatches. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 27
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.3.3 Scenarios for Store and Notify style
|
Table 4 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same REMS operating in Store and Notify style. Table 4: Scenarios for intra-REMS operating in Store&Notify model of operation (1/4) Scenario id: REMS_SN#1 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = { XML_NOT_F_ACC ERDS, XML_CONS_ACC, XML_CONT_CONS} First scenario for Store&Notify style, where the REMS asks to receiving side for acceptance, and all the entities at receiving side accept. Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REMS_notification>_for_Acceptance 4 Sends <REMS_notification>_for_Acceptance 5 All entities in receiving side receive one <REMS_notification>_for_Acceptance and answer positively 6 Generates XML_NOT_F_ACC ERDS evidence 7 Receives positive responses from receiving side and generates XML_CONS_ACC ERDS evidence for the N entities at receiving side 8 Generates <REM_dispatch>_with_XML_SUB_ACC 9 Consigns N <REM_dispatch>_with_XML_SUB_ACC 10 Generates XML_CONT_CONS ERDS evidence N <REM_dispatch>_with_XML_SUB_ACC consigned to receiving side 11 Generates <REMS_receipt>_with_EV_SET#1 12 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 28 Table 4a: Scenarios for intra-REMS operating in Store&Notify model of operation (2/4) Scenario id: REMS_SN#2 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_NOT_F_ACC, XML_CONS_ACC, XML_CONS_REJ, XML_CONT_CONS} As before but one of the entities at the receiving side does not accept consignment. Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates N <REMS_notification>_for_Acceptance 4 Sends N <REMS_notification>_for_Acceptance 5 Generates one XML_NOT_F_ACC ERDS evidence for N entities Each entity receives one <REMS_notification>_for_Acceptance. N-1 answer positively, one answers negatively 6 Receives N-1 positive answers and one negative answer 7 Generates one XML_CONS_ACC ERDS evidence for N-1 entities and one XML_CONS_REJ ERDS evidence 8 Generates one <REM_dispatch>_with_XML_SUB_ACC 9 Consigns it to the N-1 entities at receiving side 10 Generates XML_CONT_CONS for N-1 entities <REM_dispatch>_with_XML_SUB_ACC consigned to N-1 entities at receiving side 11 Generates <REMS_receipt>_with_EV_SET#1 12 Sends it to sender 13 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 29 Table 4b: Scenarios for intra-REMS operating in Store&Notify model of operation (3/4) Scenario id: REMS_SN#3 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_NOT_F_ACC , XML_ACC_REJ_EXP, XML_CONS_ACC, XML_CONT_CONS } As before but one of the entities at the receiving side does not answer in time. Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates N <REMS_notification>_for_Acceptance 4 Sends <REMS_notification>_for_Acceptance to N entities 5 Generates one XML_NOT_F_ACC ERDS evidence for N entities Each entity receives one <REMS_notification>_for_Acceptance. N-1 answer positively, one does not answer in time 6 Receives N-1 positive answers 7 When the expiration time is reached generates <REM_dispatch>_with_XML_SUB_ACC for N-1 entities Consigns them to the N-1 entities that have accepted Generates one XML_CONS_ACC ERDS evidence for N-1 entities and one XML_ ACC_REJ_EXP ERDS evidence for one entity N-1 entities at receiving side receive the <REM_dispatch>_with_XML_SUB_ACC 8 Generates <REMS_receipt>_with_EV_SET#1 9 Sends it to the sender 10 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 30 Table 4c: Scenarios for intra-REMS operating in Store&Notify model of operation (4/4) Scenario id: REMS_SN#4 Purpose Parameter: <REM_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = { XML_NOT_F_ACC, XML_CONT_HAND } First scenario for Store&Notify style, where the REMS asks to receiving side for acceptance, and all the entities at receiving side accept. Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt>_with_EV_SET#1 Sequence of actions # Sender REMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence Generates <REMS Receipt> with XML_SUB_ACC ERDS Sends back <REMS Receipt> with XML_SUB_ACC ERDS evidence to sender 3 Sender receives <REMS Receipt> with XML_SUB_ACC ERDS evidence Generates N <REMS_notification>_for Acceptance 4 SendsN <REMS_notification>_for Acceptance 5 All entities in receiving side receive one <REMS_notification>_for Acceptance 6 Generates XML_NOT_F_ACC ERDS evidence for N entities All entities in receiving side and answer positively to the N <REMS_notification> 7 Receives positive responses from receiving side All entities in receiving retrieve the REM dispatch 8 Generates one XML_CONT_HAND ERDS evidence with details of the N recipients 9 Generates <REMS_receipt>_with_EV_SET#1 Sends <REMS_receipt>_with_EV_SET#1 back to the sender 10 Receives <REMS_receipt>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 31
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.4 Scenarios for 4-corner model
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 REMSs but there are not intermediate REMSs between the SREMS and the RREMSs. Clause 5.4.2 defines test cases when both REMSs operate in Store and Forward style. Clause 5.4.3 defines test cases when the SREMS operates Store and Forward style and the RREMS operates Store and Notify style. Clause 5.4.4 defines test cases when the SREMS operates Store and Notify style and the RREMS operates Store and Forward style.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.4.2 Scenarios for Store&Forward to Store&Forward
|
Table 5 defines a number of scenarios for the case where SREMS and RREMS operate both Store and Forward style and are NOT the same REMS. The scenarios are based on scenarios in Table 3 adding the relay acceptance and relay rejection events at the some of the RREMSs and their corresponding ERDS evidences. For the sake of simplicity, it will suppose that all the entities at receiving side are served by the same RREMS. It could be possible to use the templates defined in the present document for defining scenarios where the aforementioned entities are served by different RREMSs. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 32 Table 5: Scenarios for SREMS and RREMSs operating Store&Forward (1/7) Table 5a: Scenarios for SREMS and RREMSs operating Store&Forward (2/7) Scenario id: SREMS_SF_RREMS_SF#1 Purpose Parameter: <REMS_receipt_1>_with_XML_SUB_ACC The simplest scenario: the SREMS rejects the original message from the user. Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Rejects submission. Generates XML_SUB_REJ ERDS evidence 3 Generates <REMS_receipt>_with_XML_SUB_R EJ 4 Sends the <REMS_receipt>_with_XML_SUB_R EJ to the sender 5 Sender receives <REMS_receipt>_ XML_SUB_REJ Scenario id: SREMS_SF_RREMS_SF#2 Purpose Parameter: <REMS_dispatch>_with_XML_SUB_ACC Var EV_SET#1 = {XML_SUB_ACC, XML_REL_REJ} Another simple scenario: the RREMS rejects the REM dispatch relayed by the SREMS and sends back a REM receipt with one RelayRejection ERDS evidence. Parameter: <REMS_receipt_1>_with_XML_REL_REJ Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch>_with_XML_SUB_A CC 4 Relays the <REM_dispatch>_with_XML_SUB_A CC to the RREMS 5 The RREMSs Rejects the <REM_dispatch>_with_XML_SUB_ACC 6 Generates XML_REL_REJ ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_REJ ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 33 Table 5b: Scenarios for SREMS and RREMSs operating Store&Forward (3/7) Scenario id: SREMS_SF_RREMS_SF#3 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC The simplest successful scenario: the SREMS accepts the submission of the original message, generates one REM dispatch and relays to RREMS. This accepts relay, builds its own REM dispatch and delivers it to the N recipients in receiving side. SREMS generates and sends back to the sender a REM receipt with one SubmissionAcceptance ERDS evidence, one RelayAcceptance, and one ContentConsignment ERDS evidence. Clause 4.3.2.1 of ETSI EN 319 532-1 [3] shows a variation of this scenario where RREMS sends XML_REL_ACC and XML_CONT_CONS in different REM receipts. Parameter <REMS_receipt_1>_with_XML_SUB_ACC Parameter: <REMS_receipt_2>_with_XML_REL_ACC Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_3>_with_XML_CONT_CONS Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REMS_receipt_1>_with_XML_SUB _ACC and sends it to the sender 4 Receives <REMS_receipt_1>_with_XML _SUB_ACC Generates <REM_dispatch_1>_with_XML_SUB _ACC 5 Relays it to RREMS REM dispatch to recipient 6 Accepts it and generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_2>_with_XML_REL_ACC 8 Sends <REMS_receipt_2>_with_XML_REL_ACC to SREMS 9 Receives <REMS_receipt_2>_with_XML_REL _ACC Generates <REM_dispatch_2>_with_XML_SUB_ACC 10 Consigns it to the receiving side 8 Sends <REMS_receipt_1>_with_XML_REL_REJ to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL _REJ 10 Generates <REMS_receipt_2>_with_EV_SET#1 11 Sends it back to sender 12 Sender receives <REMS_receipt_2>_with_EV_S ET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 34 Scenario id: SREMS_SF_RREMS_SF#3 Purpose 11 Generates XML_CONT_CONS ERDS evidence <REM_dispatch_2>_ with_XML_SUB_AC C consigned to the N entities in receiving side 12 Generates <REMS_receipt_3>_with_XML_ CONT_CONS 13 Sends it back to the SREMS 14 Receives <REMS_receipt_3>_with_XML_CON T_CONS and sends it back to the sender 15 Receives <REMS_receipt_3>_with_XML _CONT_CONS Table 5c: Scenarios for SREMS and RREMSs operating Store&Forward (4/7) Scenario id: SREMS_SF_RREMS_SF#4 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {REL_ACC, CONT_CONS} As scenario SREMS_SF_RREMS_SF#3 but now finalized with hand over and RelayAcceptance and ContentConsignment travel together in the same REM receipt back to SREMS. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_SUB_ACC Parameter: <REMS_receipt_2>_with_EV_SET#1 Parameter: <REMS_receipt_3>_with_XML_CONT_HAND Sequence of actions # Sender REMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REMS_receipt_1>_with_XML_SUB _ACC and sends it to the sender 4 Receives <REMS_receipt_1>_with_XML _SUB_ACC Generates <REM_dispatch_1>_with_XML_SUB _ACC 5 Relays <REM_dispatch_1>_with_XML_SUB _ACC TO RREMS 6 Accepts it and generates XML_REL_ACC ERDS evidence 7 Generates <REM_dispatch_2>_with_XML_SU B_ACC 8 Consigns it to the receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 35 Scenario id: SREMS_SF_RREMS_SF#4 Purpose 9 Generates XML_CONT_CONS ERDS evidence <REM_dispatch_2>_with_X ML_SUB_ACC is consigned to all the entities at receiving side 10 Generates <REMS_receipt_2>_with_EV_SET #1 11 Send <REMS_receipt_2>_with_EV_SET #1 to SREMS Entities in receiving side retrieve user content 12 Receives <REMS_receipt_2>_with_EV_SET#1 and sends it back to the sender Generates XML_CONT_HAND ERDS evidence 13 Receives <REMS_receipt_2>_with_EV_S ET#1 Generates <REMS_receipt_3>_with_XML_CO NT_HAND 14 Sends <REMS_receipt_3>_with_XML_CO NT_HAND to SREMS 15 Receives <REMS_receipt_3>_with_XML_CON T_HAND and sends it back to the sender 16 Receives <REMS_receipt_3>_with_XML _CONT_HAND Table 5d: Scenarios for SREMS and RREMSs operating Store&Forward (5/7) Scenario id: SREMS_SF_RREMS_SF#5 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {XNL_REL_ACC,XML_CON_CONS} As the previous scenario but now one of the handing over fails. Hereinafter, the scenarios do not show handing over, but only consignment. However, a set of scenarios including handing over could be easily built based on them. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Var EV_SET#2 = {XML_CONT_HAND_FAIL} Parameter: <REMS_receipt_1>_with_XML_SUB_ACC Parameter: <REMS_receipt_2>_with_EV_SET#1 Parameter: <REMS_receipt_3>_with_EV_SET#2 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REMS_receipt_1>_with_XML_SUB _ACC and sends it to the sender ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 36 Scenario id: SREMS_SF_RREMS_SF#5 Purpose 4 Receives <REMS_receipt_1>_with_XML _SUB_ACC Generates <REM_dispatch_1>_with_XML_SUB _ACC 5 Relays <REM_dispatch_1>_with_XML_SUB _ACC to RREMS 6 Accepts it and generates XML_REL_ACC ERDS evidence 7 Generates <REM_dispatch_2>_with_XML_SU B_ACC 8 Consigns it to the receiving side 9 Generates XML_CONT_CONS ERDS evidence <REM_dispatch_2>_with_X ML_SUB_ACC is consigned to all the entities at receiving side 10 Generates <REMS_receipt_2>_with_EV_SET #1 11 Send <REMS_receipt_2>_with_EV_SET #1 to SREMS Entities in receiving side retrieve user content. N-1 succeed. One fails. 12 Receives <REMS_receipt_2>_with_EV_SET#1 and sends it back to the sender Generates one XML_CONT_HAND ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL ERDS evidence for one entity 13 Receives <REMS_receipt_2>_with_EV_S ET#1 Generates <REMS_receipt_3>_with_EV_SET #2 14 Sends <REMS_receipt_3>_with_EV_SET #2 to SREMS 15 Receives <REMS_receipt_3>_with_EV_SET#2 and sends it back to the sender 16 Receives <REMS_receipt_3>_with_EV_S ET#2 Table 5e: Scenarios for SREMS and RREMSs operating Store&Forward (6/7) Scenario id: SREMS_SF_RREMS_SF#6 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {CONT_CONS, CON_CONS_FAIL} As scenario SREMS_SF_RREMS_SF#3 but Parameter: <REM_dispatch_2>_with_XML_SUB_ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 37 Scenario id: SREMS_SF_RREMS_SF#6 Purpose Parameter: <REMS_receipt_1>_with_XML_REL_ACC now one of the REM dispatch consignments fails. Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB _ACC 4 Relays it to RREMS 5 Accepts it and generates XML_REL_ACC ERDS evidence 6 Generates <REMS_receipt_1>_with_XML_RE L_ACC 7 Sends <REMS_receipt_1>_with_XML_RE L_ACC to SREMS 8 Receives <REMS_receipt_1>_with_XML_REL _ACC Generates <REM_dispatch_2>_with_XML_SU B_ACC 9 Consigns it to receiving side. One fails. 10 <REM_dispatch_2>_with_X ML_SUB_ACC consigned to N-1 entities in receiving side. The other consignment fails 11 Generates one XML_CONT_CONS ERDS evidence related to N-1 entities Generates one XML_CONT_CONS_FAIL related to one entity 12 Generates <REMS_receipt_2>_with_EV_SET #1 13 Sends it back to the SREMS 14 Receives <REMS_receipt_2>_with_EV_SET#1 and sends it back to the sender 15 Receives <REMS_receipt_2>_with_EV_S ET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 38 Table 5f: Scenarios for SREMS and RREMSs operating Store&Forward (7/7) Scenario id: SREMS_SF_RREMS_SF#7 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC In this scenario the consignment is performed but the SREMS does not receive any information on consignment from RREMS within a predefined period of time. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_receipt_2>_with_XML_CONT_CONS_FAIL Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB _ACC 4 Relays it to RREMS 5 Accepts it and generates XML_REL_ACC ERDS evidence 6 Generates <REMS_receipt_1>_with_XML_RE L_ACC 7 Sends <REMS_receipt_1>_with_XML_RE L_ACC to SREMS 8 Receives <REMS_receipt_1>_with_XML_REL _ACC Generates <REM_dispatch_2>_with_XML_SU B_ACC 9 Consigns it to receiving side 10 <REM_dispatch_2>_with_X ML_SUB_ACC consigned to N entities in receiving side 11 Something goes wrong and RREMS does not generate neither XML_CONT_CONS nor a REMS receipt with this Evidence 12 After waiting the predefined period of time for receiving the REMS receipt from RREMS, generates <REMS_receipt_2>_with_XML_CON T_CONS_FAIL with code RD03 and sends it back to the sender 13 Receives <REMS_receipt_2 with_XML_CONT_CONS_FAIL with code RD03 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 39
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.4.3 Scenarios for Store&Forward to Store&Notify
|
Table 6 defines a number of scenarios for the case where SREMS operates Store and Forward and RREMS operates Store and Notify. The scenarios are based on scenarios in Table 4 adding the relay acceptance and relay rejection events at the some of the RREMSs and their corresponding ERDS evidences. For the sake of simplicity, it will suppose that all the entities at receiving side are served by the same RREMS. It could be possible to use the templates defined in the present document for defining scenarios where the aforementioned entities are served by different RREMSs. Table 6: Scenarios where SREMS operates Store&Forward and RREMSs operate Store&Notify (1/5) Scenario id: SREMS_SF_RREMS_SN#1 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {NOT_F_ACC, CONS_ACC, CONT_CONS, CONT_HAND} First scenario for Store&Notify style, where the REMS asks to all the entities at receiving side for acceptance, and all the entities at receiving side accept. Similar scenarios to the ones present in this table could have been defined where each REMS receipt contains only one ERDS evidence, instead several. Scenario SREMS_SF_IREMS_SF_RREM S_SF#1 in Table 8 of clause 5.5.2 is an example. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_AC C 4 Relays <REM_dispatch_1>_with_XML_SUB_AC C to RREMS 5 Accepts <REM_dispatch_1>_with_XML_SUB_ ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_ ACC 8 Sends <REMS_receipt_1>_with_XML_REL_ ACC back to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL_ACC Generates <REMS_notification>_for_Acceptance ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 40 Scenario id: SREMS_SF_RREMS_SN#1 Purpose 10 Sends <REMS_notification>_for_Acceptance to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence All entities in receiving side answer positively 12 Generates XML_CONS_ACC ERDS evidence 13 Generates <REM_dispatch_2>_with_XML_SUB_ ACC 14 Sends <REM_dispatch_2>_with_XML_SUB_ ACC to receiving side 15 <REM_dispatch_2>_ with_XML_SUB_ACC consigned to all entities in receiving side 16 Generates XML_CONT_CONS ERDS evidence All the entities retrieve user content 17 Generates XML_CONT_HAND ERDS evidence 18 Generates <REMS_receipt_2>_with_EV_SET#1 19 Sends <REMS_receipt_2>_with_EV_SET#1 to SREMS 20 Receives <REMS_receipt_2>_with_EV_SET#1 21 Sends <REMS_receipt_2>_with_XML_XML_EV_ SET#1 back to sender 22 Receives <REMS_receipt_2>_wit h_EV_SET#1 Table 6a: Scenarios where SREMS operates Store&Forward and RREMSs operate Store&Notify (2/5) Scenario id: SREMS_SF_RREMS_SN#2 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = { NOT_F_ACC, CONS_ACC, CONS_REJ, CONT_CONS, CONT_HAND } As scenario SREMS_SF_RREMS_SN#1 but one of the entities at the receiving side does not accept consignment. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt_2>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 41 Scenario id: SREMS_SF_RREMS_SN#2 Purpose Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_AC C 4 Relays <REM_dispatch_1>_with_XML_SUB_AC C to RREMS 5 Accepts <REM_dispatch_1>_with_XML_SUB _ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL _ACC 8 Sends <REMS_receipt_1>_with_XML_REL _ACC back to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL_ACC Generates <REMS_notification>_for_Acceptanc e 10 Sends <REMS_notification>_for_Acceptanc e to receiving side 11 Generates XML_NOT_F_ACC ERDS evidence for all N entities N-1 entities in receiving side answer positively. One answers negatively 12 Generates XML_CONS_ACC ERDS evidence for N-1 entities and one XML_CONS_REJ ERDS evidence for one entity 13 Generates <REM_dispatch_2>_with_XML_SUB _ACC 14 Sends <REM_dispatch_2>_with_XML_SUB _ACC to N-1 accepting entities at receiving side 15 <REM_dispatch_2>_ with_XML_SUB_ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 42 Scenario id: SREMS_SF_RREMS_SN#2 Purpose consigned to N-1 entities in receiving side 16 Generates one XML_CONT_CONS ERDS evidence for N-1 entities N-1 entities retrieve user content 17 Generates one XML_CONT_HAND ERDS evidence for N-1 entities 18 Generates <REMS_receipt_2>_with_EV_SET#1 19 Sends <REMS_receipt_2>_with_EV_SET#1 to SREMS 20 Receives <REMS_receipt_2>_with_EV_SET#1 21 Sends <REMS_receipt_2>_with_XML_XML_EV_ SET#1 back to sender 22 Receives <REMS_receipt_2>_with_ EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 43 Table 6b: Scenarios where SREMS operates Store&Forward and RREMSs operate Store&Notify (3/5) Scenario id: SREMS_SF_RREMS_SN#3 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = { NOT_F_ACC, CONS_ACC, ACC_REJ_EXP, CONT_CONS, CONT_HAND } As scenario SREMS_SF_RREMS_SN#1 but one of the entities at the receiving side does not answer in time. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_AC C 4 Relays <REM_dispatch_1>_with_XML_SUB_AC C to RREMS 5 Accepts <REM_dispatch_1>_with_XML_SUB_ ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_ ACC 8 Sends <REMS_receipt_1>_with_XML_REL_ ACC back to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL_ACC Generates <REMS_notification>_for_Acceptance 10 Sends <REMS_notification>_for_Acceptance to receiving side 11 Generates one XML_NOT_F_ACC ERDS evidence for all N entities N-1 entities in receiving side answer positively. One does not answer in time 12 Generates one XML_CONS_ACC ERDS evidence for N-1 entities and one XML_ACC_REJ_EXP ERDS evidence for one entity ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 44 Scenario id: SREMS_SF_RREMS_SN#3 Purpose 13 Generates <REM_dispatch_2>_with_XML_SUB_ ACC 14 Sends <REM_dispatch_2>_with_XML_SUB_ ACC to N-1 accepting entities at receiving side 23 <REM_dispatch_2>_ with_XML_SUB_ACC consigned to N-1 entities in receiving side 15 Generates one XML_CONT_CONS ERDS evidence for N-1 entities N-1 entities retrieve user content 16 Generates one XML_CONT_HAND ERDS evidence for N-1 entities 17 Generates <REMS_receipt_2>_with_EV_SET#1 18 Sends <REMS_receipt_2>_with_EV_SET#1 to SREMS 19 Receives <REMS_receipt_2>_with_EV_SET#1 20 Sends <REMS_receipt_2>_with_XML_XML_EV_ SET#1 back to sender 21 Receives <REMS_receipt_2>_with_ EV_SET#1 Table 6c: Scenarios where SREMS operates Store&Forward and RREMSs operate Store&Notify (4/5) Scenario id: SREMS_SF_RREMS_SN#4 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = { NOT_F_ACC, CONS_ACC, CONT_CONS, CONT_CONS_FAIL, CONT_HAND } As first scenario in the present table, but one of the consignments fails. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 45 Scenario id: SREMS_SF_RREMS_SN#4 Purpose 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC 4 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS 5 Accepts <REM_dispatch_1>_with_XML_SUB_ ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_ ACC 8 Sends <REMS_receipt_1>_with_XML_REL_ ACC back to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL_AC C Generates <REMS_notification>_for_Acceptance 10 Sends <REMS_notification>_for_Acceptance to receiving side 11 Generates one XML_NOT_F_ACC ERDS evidence for all N entities All the entities in receiving side answer positively 12 Generates one XML_CONS_ACC ERDS evidence for all the N entities in receiving side 13 Generates <REM_dispatch_2>_with_XML_SUB_ ACC 14 Successfully consigns <REM_dispatch_2>_with_XML_SUB_ ACC to N-1 entities at receiving side, one consignment fails 15 <REM_dispatch_2>_ with_XML_SUB_ACC consigned to N-1 entities in receiving side. One consignment fails 16 Generates one XML_CONT_CONS ERDS evidence for N-1 entities and one XML_CONT_CONS_FAIL for one entity N-1 entities retrieve user content 17 Generates one XML_CONT_HAND ERDS evidence for N-1 entities ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 46 Scenario id: SREMS_SF_RREMS_SN#4 Purpose 18 Generates <REMS_receipt_2>_with_EV_SET#1 19 Sends <REMS_receipt_2>_with_EV_SET#1 to SREMS 20 Receives <REMS_receipt_2>_with_EV_SET#1 21 Sends <REMS_receipt_2>_with_XML_XML_E V_SET#1 back to sender 22 Receives <REMS_receipt_2>_with_ EV_SET#1 Table 6d: Scenarios where SREMS operates Store&Forward and RREMSs operate Store&Notify (5/5) Scenario id: SREMS_SF_RREMS_SN#5 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {NOT_F_ACC, CONS_ACC, CONT_CONS, CONT_HAND, CONT_HAND_FAIL} As first scenario in the present table, but one of the handovers fails. Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification>_for_Acceptance Parameter: <REMS_receipt_2>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC 4 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS 5 Accepts <REM_dispatch_1>_with_XML_SUB_ ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_ ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 47 Scenario id: SREMS_SF_RREMS_SN#5 Purpose 8 Sends <REM_receipt_1>_with_XML_XML_R EL_ACC back to SREMS 9 Receives <REMS_receipt_1>_with_XML_REL_AC C Generates <REMS_notification>_for_Acceptance 10 Sends <REMS_notification>_for_Acceptance to receiving side 11 Generates one XML_NOT_F_ACC ERDS evidence for all the N entities All the entities in receiving side answer positively. 12 Generates one XML_CONS_ACC ERDS evidence for all the N entities in receiving side 13 Generates <REM_dispatch_2>_with_XML_SUB_ ACC 14 Sends <REM_dispatch_2>_with_XML_SUB_ ACC to all entities at receiving side 15 <REM_dispatch_2>_ with_XML_SUB_ACC consigned to receiving side 16 Generates one XML_CONT_CONS ERDS evidence for all the N entities N-1 entities retrieve user content. One fails 17 Generates one XML_CONT_HAND ERDS evidence for N-1 entities and one XML_CONT_HAND_FAIL for one entity 18 Generates <REMS_receipt_2>_with_EV_SET#1 19 Sends <REMS_receipt_2>_with_EV_SET#1 to SREMS 20 Receives <REMS_receipt_2>_with_EV_SET#1 21 Sends <REMS_receipt_2>_with_XML_XML_E V_SET#1 back to sender 22 Receives <REMS_receipt_2>_with_ EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 48
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.4.4 Scenarios for Store&Notify to Store&Forward
|
Table 7 defines a number of scenarios for the case where SREMS operates Store and Notify and RREMS operates Store and Forward. For the sake of simplicity, it will suppose that all the entities at receiving side are served by the same RREMS. It could be possible to use the templates defined in the present document for defining scenarios where the aforementioned entities are served by different RREMSs. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 49 Table 7: Scenarios where SREMS operates Store&Notify and RREMSs operate Store&Forward (1/5) Scenario id: SREMS_SN_RREMS_SF#1 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {XML_CONT_CONS, XML_CONT_HAND } Successful scenario where the REM dispatch is successfully consigned to all the entities in receiving side and all the entities successfully retrieve it. This scenario is slightly different than the one shown in clause 4.3.2.3 of ETSI EN 319 532-1 [3] because it groups the two last ERDS evidence generated by RREMS in one unique REMS receipt Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification_2>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_XML_CONS_ACC Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REMS_receipt_5>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC and stores it internally Generates <REMS_notification_1>_for_Acceptance 4 Relays <REMS_notification_1>_for_Acceptance 5 Accepts <REMS_notification_1>_for_Acceptan ce 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XML_REL_ ACC Sends <REMS_receipt_1>_with_XML_ XML_REL_ACC back to SREMS 8 Receives <REMS_receipt_1>_with_XML_REL_AC C Generates <REMS_notification_2>_for_Acceptan ce 9 Sends <REMS_notification_2>_for_Acceptan ce to receiving side 10 Generates XML_NOT_F_ACC ERDS evidence 11 Generates <REMS_receipt_2>_with_XML_NOT_ F_ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 50 Scenario id: SREMS_SN_RREMS_SF#1 Purpose 12 Sends <REMS_receipt_2>_with_XML_NOT_ F_ACC back to SREMS 13 Receives <REMS_receipt_2>_with_XML_NOT_F_ ACC 14 All the entities at receiving side answer positively to SREMS 15 Generates XML_CONS_ACC ERDS evidence for all entities at receiving side 16 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS 17 Generates <REMS_receipt_3>_with_XML_CONS_ ACC Receives <REM_dispatch_1>_with_XML_SUB_ ACC 18 Sends it to sender Generates XML_REL_ACC ERDS evidence 19 Receives <REMS_receipt_3>_with_ XML_CONS_ACC Generates <REMS_receipt_3>_with_XML_REL_ ACC 20 Sends it back to SREMS 21 Receives <REMS_receipt_4>_with_XML_REL_AC C Generates <REM_dispatch_2>_with_XML_SUB_ ACC 22 Consigns it to receiving side 23 Generates XML_CONT_CONS ERDS evidence for all entities at receiving side All the entities at receiving side retrieve the user content 24 Generates XML_CONT_HAND ERDS evidence for all entities at receiving side 25 Generates <REMS_receipt_5>_with_EV_SET#1 26 Sends <REMS_receipt_5>_with_EV_SET#1 to SREMS 27 Receives <REMS_receipt_5>_with_EV_SET#1 28 Sends <REMS_receipt_5>_with_EV_SET#1 back to sender ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 51 Scenario id: SREMS_SN_RREMS_SF#1 Purpose 29 Receives <REMS_receipt_5>_with_ EV_SET#1 Table 7a: Scenarios where SREMS operates Store&Notify and RREMSs operate Store&Forward (2/5) Scenario id: SREMS_SN_RREMS_SF#2 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = { CONS_ACC, CONS_REJ } As scenario SREMS_SN_RREMS_SF#1 but now one of the entities at receiving side rejects the consignment. Parameter: <REMS_notification_1>_for_Acceptance Var EV_SET#2 = {CONT_CONS, CONT_HAND} Parameter: <REMS_notification_2>_for_Acceptance Parameter: <REMS_receipt_1>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_2>_with_XML_EV_SET#1 Parameter: <REMS_receipt_3>_with_XML_XML_REL_ACC Parameter: <REMS_receipt_4>_with_EV_SET#2 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC and stores it internally 4 Relays <REMS_notification_1>_for_Acceptance 5 Receives <REMS_receipt_1>_with_XML_REL_AC C Generates <REMS_notification_2>_for_Acceptan ce 6 Sends <REMS_notification_2>_for_Acceptan ce to receiving side 7 Generates XML_NOT_F_ACC ERDS evidence 8 Generates <REMS_receipt_1>_with_XML_NOT_ F_ACC 9 Sends <REMS_receipt_1>_with_XML_NOT_ F_ACC back to SREMS 10 Receives <REMS_receipt_1>_with_XML_NOT_F_ ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 52 Scenario id: SREMS_SN_RREMS_SF#2 Purpose 11 N-1 entities at receiving side answer positively to SREMS. One answers negatively to SREMS. 12 Generates one XML_CONS_ACC ERDS evidence for N-1 accepting entities, generates one XML_CONS_REJ evidence for the one rejecting entity. 13 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS for N-1 accepting entities 14 Generates <REMS_receipt_2>_with_XML_EV_SET #1 Receives <REM_dispatch_1>_with_XML_SUB_ ACC 15 Sends <REMS_receipt_2>_with_XML_EV_SET #1 back to sender Generates XML_REL_ACC ERDS evidence 16 Receives <REMS_receipt_2>_with_ XML_EV_SET#1 Generates <REMS_receipt_3>_with_XML_REL_ ACC 17 Sends it back to SREMS 18 Receives <REMS_receipt_3>_with_XML_XML_R EL_ACC Generates <REM_dispatch_2>_with_XML_SUB_ ACC 19 Consigns it to receiving side for N-1 accepting entities 20 Generates one XML_CONT_CONS ERDS evidence for N-1 accepting entities N-1 entities at receiving side retrieve the user content 21 Generates one XML_CONT_HAND ERDS evidence for N-1 accepting entities 22 Generates <REMS_receipt_4>_with_EV_SET#2 23 Sends <REMS_receipt_4>_with_EV_SET#2 to SREMS 24 Receives <REMS_receipt_4>_with_EV_SET#2 25 Sends <REMS_receipt_4>_with_EV_SET#2 back to sender 26 Receives <REMS_receipt_4>_with_ EV_SET#2 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 53 Table 7b: Scenarios where SREMS operates Store&Notify and RREMSs operate Store&Forward (3/5) Scenario id: SREMS_SN_RREMS_SF#3 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC EV_SET#1 = {CONT_CONS, CONT_HAND} As the first scenario in the present table but now one of the entities at receiving side does not answer in time to the notification for acceptance of SREMS. Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_notification_2>_for_Acceptance Parameter: <REMS_receipt_1>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_2>_with_XML_CONS_ACC Parameter: <REMS_receipt_3>_with_XML_XML_REL_ACC Parameter: <REMS_receipt_4>_with_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC and stores it internally 4 Relays <REMS_notification_1>_for_Acceptance 5 Accepts <REMS_notification_1>_for_Acceptan ce 6 Receives <REMS_receipt_1>_with_XML_REL_AC C Generates <REMS_notification_2>_for_Acceptan ce 7 Sends <REMS_notification_2>_for_Acceptan ce to receiving side 8 Generates XML_NOT_F_ACC ERDS evidence 9 Generates <REMS_receipt_1>_with_XML_NOT_ F_ACC 10 Sends <REMS_receipt_1>_with_XML_NOT_ F_ACC back to SREMS 11 Receives <REMS_receipt_1>_with_XML_NOT_F_ ACC ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 54 Scenario id: SREMS_SN_RREMS_SF#3 Purpose 12 N-1 entities at receiving side answer positively to SREMS. One does not answer in time to SREMS 13 Generates XML_CONS_ACC ERDS evidence for N-1 accepting entities, generates XML_ACC_REJ_EXP ERDS evidence for the one entity which did not respond in time. 14 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS for N-1 accepting entities 15 Generates <REMS_receipt_2>_with_XML_CONS_ ACC Receives <REM_dispatch_1>_with_XML_SUB_ ACC 16 Sends <REMS_receipt_2>_with_XML_CONS_ ACC back to sender Generates XML_REL_ACC ERDS evidence 17 Receives <REMS_receipt_2>_with_ XML_CONS_ACC Generates <REMS_receipt_3>_with_XML_REL_ ACC 18 Sends it back to SREMS 19 Receives <REMS_receipt_3>_with_XML_XML_R EL_ACC Generates <REM_dispatch_2>_with_XML_SUB_ ACC 20 Consigns it to receiving side for N-1 accepting entities 21 Generates XML_CONT_CONS ERDS evidence for N-1 accepting entities N-1 entities at receiving side retrieve the user content 22 Generates XML_CONT_HAND ERDS evidence for N-1 accepting entities 23 Generates <REMS_receipt_4>_with_EV_SET#1 24 Sends <REMS_receipt_4>_with_EV_SET#1 to SREMS 25 Receives <REMS_receipt_4>_with_EV_SET#1 26 Sends <REMS_receipt_4>_with_EV_SET#1 back to sender 27 Receives <REMS_receipt_>_with_E V_SET#21 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 55 Table 7c: Scenarios where SREMS operates Store&Notify and RREMSs operate Store&Forward (4/5) Scenario id: SREMS_SN_RREMS_SF#4 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {CONT_CONS, CONT_CONS_FAIL } As the first scenario in the present table but now one of the consignments to the receiving side fails. Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification_2>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_XML_CONS_ACC Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REMS_receipt_5>_EV_SET#1 Parameter: <REMS_receipt_6>_XML_CONT_HAND Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC and stores it internally 4 Relays <REMS_notification_1>_for_Acceptance 5 Accepts <REMS_notification_1>_for_Acceptan ce 6 Generates <REMS_notification_2>_for_Acceptan ce 7 Sends <REMS_notification_2>_for_Acceptan ce to receiving side 8 Generates XML_NOT_F_ACC ERDS evidence 9 Generates <REMS_receipt_2>_with_XML_NOT_ F_ACC 10 Sends <REMS_receipt_2>_with_XML_NOT_ F_ACC back to SREMS 11 Receives <REMS_receipt_2>_with_XML_NOT_F_ ACC 12 All the entities at receiving side answer positively to SREMS ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 56 Scenario id: SREMS_SN_RREMS_SF#4 Purpose 13 Generates XML_CONS_ACC ERDS evidence for all entities at receiving side 14 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS 15 Generates <REMS_receipt_3>_with_XML_CONS_ ACC Receives <REM_dispatch_1>_with_XML_SUB_ ACC 16 Sends <REMS_receipt_3>_with_XML_CONS_ ACC back to sender Generates XML_REL_ACC ERDS evidence 17 Receives <REMS_receipt_3>_with_ XML_CONS_ACC Generates <REMS_receipt_4>_with_XML_REL_ ACC ERDS evidence 18 Sends it back to SREMS 19 Receives <REMS_receipt_4>_with_XML_REL_AC C Generates <REM_dispatch_2>_with_XML_SUB_ ACC 20 Consigns it to receiving side 21 N-1 consignments succeed, one fails 22 Generates XML_CONT_CONS for N-1 entities and one XML_CONS_FAIL for one entity 23 Generates <REMS_receipt_5>_with_EV_SET#1 24 Sends <REMS_receipt_5>_with_EV_SET#1 back to SREMS 25 Receives <REMS_receipt_4>_with_EV_SET#1 26 27 N-1 entities at receiving side retrieve the user content 28 Generates XML_CONT_HAND ERDS evidence for N-1 entities 29 Generates <REMS_receipt_5>_with_XML_CONT _HAND 30 Sends <REMS_receipt_5>_with_XML_CONT _HAND to SREMS ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 57 Scenario id: SREMS_SN_RREMS_SF#4 Purpose 31 Receives <REMS_receipt_5>_with_XML_CONT_ HAND 32 Sends <REMS_receipt_5>_with_XML_CONT_ HAND back to sender 33 Receives <REMS_receipt_5>_with_ XML_CONT_HAND Table 7d: Scenarios where SREMS operates Store&Notify and RREMSs operate Store&Forward (5/5) Scenario id: SREMS_SN_RREMS_SF#5 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {CONT_CONS, CONT_HAND, CONT_HAND_FAIL } As the first scenario in the present table but now one of the handovers to the receiving side fails. Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification_2>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_XML_CONS_ACC Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REMS_receipt_5>_EV_SET#1 Sequence of actions # Sender SREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission. Generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_XML_SUB_A CC and stores it internally 4 Relays <REMS_notification_1>_for_Acceptance 5 Accepts <REMS_notification_1>_for_Acceptan ce 6 Generates <REMS_notification_2>_for_Acceptan ce 7 Sends <REMS_notification_2>_for_Acceptan ce to receiving side 8 Generates XML_NOT_F_ACC ERDS evidence ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 58 Scenario id: SREMS_SN_RREMS_SF#5 Purpose 9 Generates <REMS_receipt_2>_with_XML_NOT_ F_ACC 10 Sends <REMS_receipt_2>_with_XML_NOT_ F_ACC back to SREMS 11 Receives <REMS_receipt_2>_with_XML_NOT_F_ ACC 12 All the entities at receiving side answer positively to SREMS. 13 Generates XML_CONS_ACC ERDS evidence for all entities at receiving side 14 Relays <REM_dispatch_1>_with_XML_SUB_A CC to RREMS 15 Generates <REMS_receipt_3>_with_XML_CONS_ ACC ERDS evidence Receives <REM_dispatch_1>_with_XML_SUB_ ACC 16 Sends <REMS_receipt_3>_with_XML_CONS_ ACC to sender Generates XML_REL_ACC ERDS evidence 17 Receives <REMS_receipt_3>_with_ XML_CONS_ACC Generates <REMS_receipt_4>_with_XML_REL_ ACC ERDS evidence 18 Sends it back to SREMS 19 Receives <REMS_receipt_4>_with_XML_REL_AC C Generates <REM_dispatch_2>_with_XML_SUB_ ACC 20 Consigns it to receiving side 21 Generates XML_CONT_CONS ERDS evidence for all entities at receiving side N-1 entities at receiving side retrieve the user content. One entity fails when trying to retrieve. 22 Generates XML_CONT_HAND ERDS evidence for N-1 entities and XML_CONT_HAND_FAIL for one entity 23 Generates <REMS_receipt_5>_with_EV_SET#1 24 Sends <REMS_receipt_5>_with_EV_SET#1 to SREMS 25 Receives <REMS_receipt_5>_with_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 59 Scenario id: SREMS_SN_RREMS_SF#5 Purpose 26 Sends <REMS_receipt_5>_with_EV_SET#1 back to sender 27 Receives <REMS_receipt_5>_with_ EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 60
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.5 Scenarios for extended model
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 REMSs and there is one intermediate IREMS between the SREMS and the RREMSs. Clause 5.5.2 defines test cases when the all the REMSs operate in Store and Forward style. Clause 5.5.3 defines test cases when the SREMS and the RREMS operate in Store and Forward style and the IREMS operates in Store and Notify style.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.5.2 Scenarios for S&F->S&F->S&F
|
Table 8 shows scenarios where SREMS, IREMS and RREMS all operate in Store and Forward style. The sets of scenarios shown in Table 8 extend the set shown in clause 4.4.2.1 of ETSI EN 319 532-1 [3]. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 61 Table 8: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style (1/5) Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#1 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC First scenario where the N entities successfully retrieve the REM dispatch with the user content. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_receipt_2>_with_XML_REL_ACC Parameter: <REMS_receipt_3>_with_XML_CONT_CONS Parameter: <REMS_receipt_4>_with_XML_CONT_HAND Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS 10 Receives <REM_dispatch_1>_with_XML _SUB_ACC 11 Generates XML_REL_ACC ERDS evidence 12 Generates <REMS_receipt_2>_with_XML _REL_ACC 13 Sends it back to IREMS 14 Receives <REMS_receipt_2>_with_XM L_REL_ACC Consigns <REM_dispatch_1>_with_XML _SUB_ACC to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 62 Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#1 Purpose 15 <REM_dispatch_1>_with_X ML_SUB_ACC consigned to all the entities in receiving side 16 Generates XML_CONT_CONS ERDS evidence 17 Generates <REMS_receipt_3>_with_XML _CONT_CONS All the entities in receiving side retrieve <REM_dispatch_1>_with_X ML_SUB_ACC 18 Sends it back to IREMS 19 Receives <REMS_receipt_3>_with_XM L_CONT_CONS Generates XML_CONT_HAND ERDS evidence 20 Sends it back to SREMS Generates <REMS_receipt_4>_with_XML _CONT_HAND 21 Receives <REMS_receipt_3>_with_X ML_CONT_CONS Sends it back to IREMS 22 Sends it back to sender Receives <REMS_receipt_4>_with_XM L_CONT_HAND 23 Receives <REMS_receipt_3>_wi th_XML_CONT_CON S Sends it back to SREMS 24 Receives <REMS_receipt_4>_with_X ML_CONT_HAND 25 Sends it back to sender 26 Receives <REMS_receipt_4>_wi th_XML_CONT_HAND ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 63 Table 8a: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style (2/5) Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#2 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {CONT_CONS, CONT_CONS_FAIL} As the first scenario but now one of the consignments fails. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_receipt_2>_with_XML_REL_ACC Parameter: <REMS_receipt_3>_with_EV_SET#1 Parameter: <REMS_receipt_4>_with_XML_CONT_HAND Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS 10 Receives <REM_dispatch_1>_with_XML _SUB_ACC 11 Generates XML_REL_ACC ERDS evidence 12 Generates <REMS_receipt_2>_with_XML _REL_ACC 13 Sends it back to IREMS 14 Receives <REMS_receipt_2>_with_XM L_REL_ACC Consigns <REM_dispatch_1>_with_XML _SUB_ACC to the receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 64 Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#2 Purpose 15 <REM_dispatch_2>_with_X ML_SUB_ACC is consigned to N-1 entities in receiving side. One of the consignments fails 16 Generates XML_CONT_CONS ERDS evidence for N-1 entities and XML_CONT_CONS_FAIL ERDS evidence for one entity 17 Generates <REMS_receipt_3>_with_EV_S ET#1 N-1 entities in receiving side retrieve <REM_dispatch_2>_with_X ML_SUB_ACC 18 Sends it back to IREMS 19 Receives <REMS_receipt_3>_with_EV _SET#1 Generates XML_CONT_HAND for N-1 entities 20 Sends it back to SREMS Generates <REMS_receipt_4>_with_XML _CONT_HAND 21 Receives <REMS_receipt_3>_with_E V_SET#1 Sends it back to IREMS 22 Sends it back to sender Receives <REMS_receipt_4>_with_XM L_CONT_HAND 23 Receives <REMS_receipt_3>_wi th_EV_SET#1 Sends it back to SREMS 24 Receives <REMS_receipt_4>_with_X ML_CONT_HAND 25 Sends it back to sender 26 Receives <REMS_receipt_4>_wi th_XML_CONT_HAND ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 65 Table 8b: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style (3/5) Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#3 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = { CONT_HAND, CONT_HAND_FAIL } As the first scenario but now one of the entities fails when trying to retrieve the user content. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_receipt_2>_with_XML_REL_ACC Parameter: <REMS_receipt_3>_with_XML_CONT_CONS Parameter: <REMS_receipt_4>_with_EV_SET#1 Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relies it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Relies <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS 10 Receives <REM_dispatch_1>_with_XML _SUB_ACC to RREMS 11 Generates XML_REL_ACC ERDS evidence 12 Generates <REMS_receipt_2>_with_XML _SUB_ACC 13 Sends it back to IREMS 14 Receives <REMS_receipt_2>_with_XM L_SUB_ACC Generates <REM_dispatch_2>_with_XML _SUB_ACC to RREMS 15 Consigns it to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 66 Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#3 Purpose 16 <REM_dispatch_2>_with_X ML_SUB_ACC to RREMS is consigned all the entities 17 Generates XML_CONT_CONS ERDS evidence 18 Generates <REMS_receipt_3>_with_XML _ XML_CONT_CONS N-1 entities in receiving side retrieve <REM_dispatch_2>_with_X ML_SUB_ACC to RREMS. One entity fails when trying to retrieve it 19 Sends it back to IREMS 20 Receives <REMS_receipt_3>_with_XM L_ XML_CONT_CONS Generates XML_CONT_HAND ERDS evidence for N-1 entities and XML_CONT_HAND_FAIL for one entity 21 Sends it back to SREMS Generates <REMS_receipt_4>_with_EV_S ET#1 22 Receives <REMS_receipt_3>_with_X ML_ XML_CONT_CONS Sends it back to IREMS 23 Sends it back to sender Receives <REMS_receipt_4>_with_EV _SET#1 24 Receives <REMS_receipt_3>_wi th_XML_ XML_CONT_CONS Sends it back to SREMS 25 Receives <REMS_receipt_4>_with_E V_SET#1 26 Sends it back to sender 27 Receives <REMS_receipt_4>_wi th_EV_SET#1 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 67 Table 8c: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style (4/5) Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#4 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC As the first scenario but now the IREMS rejects relaying. Parameter: <REMS_receipt_1>_with_XML_REL_REJ Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Rejects relay 6 Generates XML_REL_REJ ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_REJ 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_REJ 10 Sends it back to sender 11 Receives <REMS_receipt_1>_wi th_XML_REL_REJ Table 8d: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style (5/5) Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#5 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC As the first scenario but now the RREMS rejects relaying. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_receipt_2>_with_XML_REL_REJ Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 68 Scenario id: SREMS_SF_IREMS_SF_RREMS_SF#5 Purpose 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS 10 Receives <REM_dispatch_1>_with_XML _SUB_ACC but it rejects it 11 Generates XML_REL_REJ ERDS evidence 12 Generates <REMS_receipt_2>_with_XML _REL_REJ 13 Sends it back to IREMS 14 Receives <REMS_receipt_2>_with_XM L_REL_REJ 15 Sends it back to SREMS 16 Receives <REMS_receipt_2>_with_X ML_REL_REJ 17 Sends it back to sender 18 Receives <REMS_receipt_2>_wi th_XML_REL_REJ ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 69
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
5.5.3 Scenarios for S&F -> S&N -> S&F
|
Table 9 shows scenarios where SREMS, and RREMS operate Store and Forward style and IREMS operates Store and Notify. The sets of scenarios shown in Table 9 extend the set shown in clause 4.4.2.2 of ETSI EN 319 532-1 [3]. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 70 Table 9: Scenarios where SREMS and RREMSs operate Store&Forward style and IREMS operates Store&Notify (1/3) Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#1 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC First scenario where all the entities at receiving side successfully retrieve the user content. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_XML_CONS_ACC Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_5>_with_XML_CONT_CONS Parameter: <REMS_receipt_6>_with_XML_CONT_HAND Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC and stores it 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Generates <REMS_notification_1>_for_ Acceptance 10 Relays <REMS_notification_1>_for_ Acceptance to RREMS 11 Receives <REMS_notification_1>_for_Ac ceptance 12 Sends <REMS_notification_1>_for_Ac ceptance to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 71 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#1 Purpose 13 Generates XML_NOT_F_ACC ERDS evidence All the parties at receiving side receive <REMS_notification_1>_for _Acceptance 14 Generates <REMS_receipt_2>_with_XML _NOT_F_ACC 15 Sends it back to IREMS 16 Receives <REMS_receipt_2>_with_XM L_NOT_F_ACC 17 Sends it back to SREMS 18 Receives <REMS_receipt_2>_with_X ML_NOT_F_ACC 19 All the parties at receiving side access IREMS and accept consignment 20 Generates XML_CONS_ACC for all the N entities at receiving side 21 Generates <REMS_receipt_3>_with_XM L_CONS_ACC 22 Sends it back to SREMS 23 Receives <REMS_receipt_3>_with_X ML_CONS_ACC Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS 24 Accepts <REM_dispatch_1>_with_XML _SUB_ACC 25 Generates XML_REL_ACC ERDS evidence 26 Generates <REMS_receipt_4>_with_XML _REL_ACC 27 Sends it back to IREMS 28 Receives <REMS_receipt_4>_with_XM L_REL_ACC Generates <REM_dispatch_2>_with_XML _SUB_ACC 29 Consigns <REM_dispatch_2>_with_XML _SUB_ACC to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 72 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#1 Purpose 30 <REM_dispatch_2>_with_X ML_REL_ACC is consigned to all entities in receiving side 31 Generates XML_CONT_CONS ERDS evidence 32 Generates <REMS_receipt_5>_with_XML _CONT_CONS 33 Sends it back to IREMS All entities in receiving side retrieve user content 34 Receives <REMS_receipt_5>_with_XM L_CONT_CONS Generates XML_CONT_CONT_HAND evidence 35 sends it back to SREMS Generates <REMS_receipt_6>_with_XML _CONT_HAND 36 Receives <REMS_receipt_5>_with_X ML_CONT_CONS Sends it back to IREMS 37 Sends it back to sender Receives <REMS_receipt_6>_with_XM L_CONT_HAND 38 Receives <REMS_receipt_5>_wi th_XML_CONT_CON S sends it back to SREMS 39 Receives <REMS_receipt_6>_with_X ML_CONT_HAND 40 Sends it back to sender 41 Receives <REMS_receipt_6>_wi th_XML_CONT_HAND ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 73 Table 9a: Scenarios where SREMS and RREMSs operate Store&Forward style and IREMS operates Store&Notify (2/3) Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#2 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {XML_CONS_ACC, XML_CONS_REJ} As first scenario but now one of the entities at receiving side rejects consignment. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_EV_SET#1 Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_5>_with_XML_CONT_CONS Parameter: <REMS_receipt_6>_with_XML_CONT_HAND Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC and stores it 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Generates <REMS_notification_1>_for_ Acceptance 10 Relays <REMS_notification_1>_for_ Acceptance to RREMS 11 Receives <REMS_notification_1>_for_Ac ceptance 12 Sends <REMS_notification_1>_for_Ac ceptance to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 74 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#2 Purpose 13 Generates XML_NOT_F_ACC ERDS evidence All the parties at receiving side receive <REMS_notification_1>_for _Acceptance 14 Generates <REMS_receipt_2>_with_XML _NOT_F_ACC . 15 Sends it back to IREMS 16 Receives <REMS_receipt_2>_with_XM L_NOT_F_ACC 17 Sends it back to SREMS N-1 parties at receiving side access IREMS and accept consignment. One party rejects it 18 Receives <REMS_receipt_2>_with_X ML_NOT_F_ACC 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. 19 Generates <REMS_receipt_3>_with_EV _SET#1 20 Sends it back to SREMS 21 Receives <REMS_receipt_3>_ with_EV_SET#1 Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS for the N-1 accepting entities 22 Sends it back to sender Accepts <REM_dispatch_1>_with_XML _SUB_ACC 23 Receives <REMS_receipt_3>_ with_EV_SET#1 Generates XML_REL_ACC ERDS evidence 24 Generates <REMS_receipt_4>_with_XML _REL_ACC 25 Sends it back to IREMS 26 Receives <REMS_receipt_4>_with_XM L_REL_ACC Generates <REM_dispatch_2>_with_XML _SUB_ACC 27 Consigns <REM_dispatch_2>_with_XML _SUB_ACC to N-1 accepting entities at receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 75 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#2 Purpose 28 <REM_dispatch_2>_with_X ML_SUB_ACC is consigned to N-1 entities at receiving side 29 Generates XML_CONT_CONS ERDS evidence for N-1 entities 30 Generates <REMS_receipt_5>_with_XML _CONT_CONS 31 Sends it back to IREMS N-1 entities in receiving side retrieve user content 32 Receives <REMS_receipt_5>_with_XM L_CONT_CONS Generates XML_CONT_HAND evidence for N-1 entities 33 sends it back to SREMS Generates <REMS_receipt_6>_with_XML _CONT_HAND 34 Receives <REMS_receipt_5>_with_X ML_CONT_CONS Sends it back to IREMS 35 Sends it back to sender Receives <REMS_receipt_6>_with_XM L_CONT_HAND 36 Receives <REMS_receipt_5>_wi th_XML_CONT_CON S sends it back to SREMS 37 Receives <REMS_receipt_6>_with_X ML_CONT_HAND 38 Sends it back to sender 39 Receives <REMS_receipt_6>_wi th_XML_CONT_HAND ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 76 Table 9b: Scenarios where SREMS and RREMSs operate Store&Forward style and IREMS operates Store&Notify (3/3) Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#3 Purpose Parameter: <REM_dispatch_1>_with_XML_SUB_ACC Var EV_SET#1 = {XML_CONS_ACC, XML_CONS_REJ} As first scenario but now one of the entities at receiving side rejects consignment and another entity fails in retrieving the user content. Parameter: <REMS_receipt_1>_with_XML_REL_ACC Var EV_SET#2 = {XML_CONT_HAND, XML_CONT_HAND_FAIL} Parameter: <REMS_notification_1>_for_Acceptance Parameter: <REMS_receipt_2>_with_XML_NOT_F_ACC Parameter: <REMS_receipt_3>_with_EV_SET#1 Parameter: <REMS_receipt_4>_with_XML_REL_ACC Parameter: <REM_dispatch_2>_with_XML_SUB_ACC Parameter: <REMS_receipt_5>_with_XML_CONT_CONS Parameter: <REMS_receipt_6>_with_EV_SET#2 Sequence of actions # Sender SREMS IREMS RREMS Receiving side 1 Sender sends original message 2 Accepts submission and generates XML_SUB_ACC ERDS evidence 3 Generates <REM_dispatch_1>_with_X ML_SUB_ACC 4 Relays it to IREMS 5 Receives <REM_dispatch_1>_with_XM L_SUB_ACC and stores it 6 Generates XML_REL_ACC ERDS evidence 7 Generates <REMS_receipt_1>_with_XM L_REL_ACC 8 Sends it back to SREMS 9 Receives <REMS_receipt_1>_with_X ML_REL_ACC Generates <REMS_notification_1>_for_ Acceptance 10 Relays <REMS_notification_1>_for_ Acceptance to RREMS 11 Receives <REMS_notification_1>_for_Ac ceptance 12 Sends <REMS_notification_1>_for_Ac ceptance to receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 77 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#3 Purpose 13 Generates XML_NOT_F_ACC ERDS evidence All the parties at receiving side receive <REMS_notification_1>_for _Acceptance 14 Generates <REMS_receipt_2>_with_XML _NOT_F_ACC . 15 Sends it back to IREMS 16 Receives <REMS_receipt_2>_with_XM L_NOT_F_ACC 17 Sends it back to SREMS N-1 parties at receiving side access IREMS and accept consignment. One party rejects it 18 Receives <REMS_receipt_2>_with_X ML_NOT_F_ACC 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. 19 Generates <REMS_receipt_3>_with_EV _SET#1 20 Sends it back to SREMS 21 Receives <REMS_receipt_3>_with_E V_SET#1 Relays <REM_dispatch_1>_with_XM L_SUB_ACC to RREMS for the N-1 accepting entities 22 Sends it back to sender Accepts <REM_dispatch_1>_with_XML _SUB_ACC 23 Receives <REMS_receipt_3>_ with_EV_SET#1 Generates XML_REL_ACC ERDS evidence 24 Generates <REMS_receipt_4>_with_XML _REL_ACC 25 Sends it back to IREMS 26 Generates <REM_dispatch_2>_with_XML _SUB_ACC 27 Receives <REMS_receipt_4>_with_XM L_REL_ACC Consigns <REM_dispatch_2>_with_XML _SUB_ACC to N-1 accepting entities at receiving side ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 78 Scenario id: SREMS_SF_IREMS_SN_RREMS_SF#3 Purpose 28 <REM_dispatch_2>_with_X ML_SUB_ACC is consigned to N-1 entities at receiving side 29 Generates XML_CONT_CONS ERDS evidence for N-1 entities 30 Generates <REMS_receipt_5>_with_XML _CONT_CONS 31 Sends it back to IREMS N-2 entities in receiving side retrieve user content, one entity fails 32 Receives <REMS_receipt_5>_with_XM L_CONT_CONS Generates XML_CONT_HAND evidence for N-2 entities and XML_CONT_HAND_FAIL for one entity 33 sends it back to SREMS Generates <REMS_receipt_6>_with_EV_S ET#2 34 Receives <REMS_receipt_5>_with_X ML_CONT_CONS Sends it back to IREMS 35 Sends it back to sender Receives <REMS_receipt_6>_with_EV _SET#2 36 Receives <REMS_receipt_5>_wi th_XML_CONT_CON S sends it back to SREMS 37 Receives <REMS_receipt_6>_with_E V_SET#2 38 Sends it back to sender 39 Receives <REMS_receipt_6>_wi th_EV_SET#2 ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 79
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6 REM Messages instances
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.1 Introduction and technical approach
|
The present clause defines a number of instances of the different types of REM Messages, namely: • REMS notification; • REM payload; • REMS receipt; and • REM dispatch; • as defined in ETSI EN 319 532-1 [3]. These instances are used in clause 8 for defining different test cases. The set of REM message instances is built following the technical approach shown below: • The set includes instances of each type of REM message. • For each type of REM message there is at least one instance where all the optional headers defined in ETSI EN 319 532-3 [5] are present. In the rest of test cases subsets of the aforementioned optional headers are present. • For each type of REM message there will be at least one instance where the REM message includes all the optional MIME parts that it can include (in addition to the mandatory ones). In the rest of instances, subsets of the aforementioned optional MIME parts are present. • The present document first defines different instances for each MIME part that can be present in one of the different types of REM message, namely: REMS relay metadata MIME Header (that includes REMS relay metadata and REMS handover metadata), introduction MIME section, original message MIME section, extensions MIME section, ERDS evidence MIME section, and S/MIME signature MIME section. • Each instance of a certain type of REM message is defined as a composition of different MIME parts specified in the aforementioned MIME parts test cases. The rest of the present clause is organized as follows: Clause 6.2 presents a number of combinations of fields for the different headers that can be present in the different REM message types. These combinations are specified separately as they are used in the definition of instances of different REM message types. Clause 6.3 defines instances of REM payloads. Clause 6.4 defines instances of REMS notifications. Clause 6.5 defines instances of REMS receipts. Clause 6.6 defines instances of REM dispatches. As mentioned in clause 4.2 new combinations of fields may be defined for each header, and new instances of REM messages may be added to the current set, for defining new test cases. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 80
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2 Combinations of fields for headers in REM envelopes
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.1 Introduction
|
The following clauses define combinations of headers fields for all the headers that may be present in REM envelopes, namely: the REMS relay metadata MIME Header, the signed data MIME header, the headers in REMS introduction MIME section, the original message MIME section header, the REMS extensions MIME section header, the ERDS evidence MIME section header, and the REMS signature MIME header.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.2 Combinations of fields for the REMS relay metadata MIME Header
|
The present clause defines different combinations of fields for the REMS relay metadata MIME Header of the REM envelope. The definition of a certain combination is split in two tables, namely Table 10 and Table 11. Table 10 shows combinations of fields that are defined in MIME and SMIME RFCs. Only the fields listed in a certain combination shall be present in that combination. Not listed fields shall be absent. Cells in column "Field name" contain the name of the header fields. Cells in column "Value" shows the value to be assigned to the header field. These cells may contain the following values: • As specified in ETSI EN 319 532-3 [5]. This value is reserved for cases where ETSI EN 319 532-3 [5] specifies a mandatory value for the header field. • As recommended in ETSI EN 319 532-3 [5]. This value is reserved for cases where ETSI EN 319 532-3 [5] recommends one certain value for the header field (usually using the modal verb should). In these cases, the header field has this recommended value in the combination. • AS_PER_TESTCASE means that for this test case the tester is free to give to the aforementioned field the value it considers worth, provided that it fulfils the additional requirements indicated in Table 10. 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 Table 10. The numbers correspond to numbers of notes that appear after the aforementioned additional requirements. Table 10: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value Notes/Additional requirements RFCFields#1 Content-Type As specified in ETSI EN 319 532-3 [5] MIME-Version As specified in ETSI EN 319 532-3 [5] Message-ID As recommended in ETSI EN 319 532-3 [5] Date As specified in ETSI EN 319 532-3 [5] From As recommended in ETSI EN 319 532-3 [5] 1 To As specified in ETSI EN 319 532-3 [5] Subject As recommended in ETSI EN 319 532-3 [5] RFCFields#2 Content-Type As specified in ETSI EN 319 532-3 [5] MIME-Version As specified in ETSI EN 319 532-3 [5] Message-ID As recommended in ETSI EN 319 532-3 [5] Date As specified in ETSI EN 319 532-3 [5] From As recommended in ETSI EN 319 532-3 [5] 1 To As specified in ETSI EN 319 532-3 [5] Cc As recommended in ETSI EN 319 532-3 [5] Subject As recommended in ETSI EN 319 532-3 [5] Reply-To As specified in ETSI EN 319 532-3 [5] Return-Path As specified in ETSI EN 319 532-3 [5] Received As specified in ETSI EN 319 532-3 [5] In-Reply-To As recommended in ETSI EN 319 532-3 [5] ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 81 NOTE 1: "From" header field is mandatory but ETSI EN 319 532-3 [5] recommends two ways of computing its value. The corresponding test cases for REM message formats will be in charge of selecting one of them. As it is expected that each REMS opts for one of the two mechanisms, and selecting one or the other does not introduce any hinder to interoperability, selecting one or the other does not result in a different test case. Table 11 shows the combinations of the new header fields defined in ETSI EN 319 532-3 [5]. For the purpose of defining the test cases, the field "REM-ApplicablePolicy" shall always consist in a single URI and consequently, its formatting does not require creation of one MIME extension section as specified in ETSI EN 319 532-3 [5], clause 6.2.5. New combinations may be added where this field consists in a sequence of URIs and its structured value be placed in the corresponding extension MIME section. Cells in "Header field name" column contain the name of a field in the REMS relay metadata MIME Header. The names used are the ones defined in ETSI EN 319 532-3 [5] and (whenever required) in the different RFCs specifying MIME and S/MIME formats (references [7], [8], [9], [10], [11], [12], [13] and [14]). Cells in "Header field value" column contain either: 1) the value of the header field whose name is the one indicated in the previous column; or 2) AS_PER_TESTCASE, whit the meaning described before. 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. Some rows of the table though only have three columns. This happens when a certain test case is based in a test case already specified and that has only some few differences. Then only the columns "Test case identifier", "Test case based on", and "Purpose" apply for these rows. The "Test case based on" central cell contains all the relevant details for the test case, including the test case on which this one is based and the differences between both of them. The values of these fields shall be the ones specified in the aforementioned references. Table 11 defines parameterized combinations for new headers defined in ETSI EN 319 532-3 [5]. The combinations have as parameters the assurance levels and the consignment mode. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 82 Table 11: First set of parameterized combinations for REMS relay metadata MIME Header Combination identifier Header field name Header field value Notes/Additional requirements Purpose NewFields#1 REM-RelayDate AS_PER_TESTCASE a, 2 Use in tests where: the contents of the fields are correct; there is no indication neither of assurance levels nor of mode of consignment REM-ExpirationDate AS_PER_TESTCASE b REM-ScheduledDelivery AS_PER_TESTCASE c REM-ApplicablePolicy AS_PER_TESTCASE NewFields#2 REM-RelayDate AS_PER_TESTCASE a, 2 Use in tests where: the contents of the fields are correct; the assurance levels required is one parameter, and there is no indication of mode of consignment REM-ExpirationDate AS_PER_TESTCASE b REM-RecipientAssuranceLevel Parameter REM-ScheduledDelivery AS_PER_TESTCASE c REM-ApplicablePolicy AS_PER_TESTCASE NewFields#3 REM-RelayDate AS_PER_TESTCASE a, 2 Use in tests where: the contents of the fields are correct; the REMS relay metadata MIME Header has all the optional fields present; and the assurance levels and the mode of consignment are parameters REM-ExpirationDate AS_PER_TESTCASE b REM-RecipientAssuranceLevel Parameter REM-ModeOfConsignment Parameter REM-ScheduledDelivery AS_PER_TESTCASE c REM-ApplicablePolicy AS_PER_TESTCASE NewFields#4 REM-RelayDate AS_PER_TESTCASE a, 2 Use in negative tests where: the scheduled delivery is after the expiration date; assurance levels is one parameter, and there is no indication of mode of consignment REM-ExpirationDate AS_PER_TESTCASE b REM-RecipientAssuranceLevel Parameter REM-ScheduledDelivery AS_PER_TESTCASE d REM-ApplicablePolicy AS_PER_TESTCASE NewFields#5 REM-RelayDate AS_PER_TESTCASE a, 2 Use in negative tests where: the scheduled delivery is after the expiration date; and the assurance levels and the mode of consignment are parameters REM-ExpirationDate AS_PER_TESTCASE b REM-RecipientAssuranceLevel Parameter REM-ModeOfConsignment Parameter REM-ScheduledDelivery AS_PER_TESTCASE d REM-ApplicablePolicy AS_PER_TESTCASE NewFields#6 REM-RelayDate AS_PER_TESTCASE a, 2 As NewFields#1 but without REM- ScheduledDelivery REM-ExpirationDate AS_PER_TESTCASE REM-ApplicablePolicy AS_PER_TESTCASE NewFields#7 REM-RelayDate AS_PER_TESTCASE a, 2 As NewFields#2 but without REM- ScheduledDelivery REM-ExpirationDate AS_PER_TESTCASE REM-RecipientAssuranceLevel Parameter REM-ApplicablePolicy AS_PER_TESTCASE NewFields#8 REM-RelayDate AS_PER_TESTCASE a, 2 As NewFields#3 but without REM- ScheduledDelivery REM-ExpirationDate AS_PER_TESTCASE REM-RecipientAssuranceLevel Parameter REM-ModeOfConsignment Parameter REM-ApplicablePolicy AS_PER_TESTCASE ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 83 Combination identifier Header field name Header field value Notes/Additional requirements Purpose NewFields#9 REM-ExpirationDate AS_PER_TESTCASE b As NewFields#1 but without REM-RelayDate and without REM- ScheduledDelivery REM-ApplicablePolicy AS_PER_TESTCASE NewFields#10 REM-ExpirationDate AS_PER_TESTCASE As NewFields#2 but without REM-RelayDate and without REM- ScheduledDelivery REM-RecipientAssuranceLevel Parameter REM-ApplicablePolicy AS_PER_TESTCASE NewFields#11 REM-ExpirationDate AS_PER_TESTCASE As NewFields#3 but without REM-RelayDate and without REM- ScheduledDelivery REM-RecipientAssuranceLevel Parameter REM-ModeOfConsignment Parameter REM-ApplicablePolicy AS_PER_TESTCASE Additional requirements: a) The date and time indicated in this field shall be earlier than the date and time indicated in "REM-ExpirationDate" and "REM-ScheduledDelivery" (if present). b) The date and time indicated in this field shall be later than the date and time indicated in "REM-RelayDate" and "REM-ScheduledDelivery" (if present). c) The date and time indicated in this field shall be earlier than the date and time indicated in "REM-ScheduledDelivery" and later than the date and time indicated in "REM-RelayDate" (if present). d) The date and time indicated in this field shall be later than the date and time indicated in "REM-RelayDate" and later than "REM-ExpirationDate" (if present). NOTE 2: This combination can be used only in scenarios of REM messages where a REMS relays the REM message to another REMS, i.e. in situations where sender and receiver are not subscribed to the same REMS. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 84 The present document defines the combinations of fields of the REMS relay metadata MIME Header of the REM envelope that are shown in Table 12. Each instance of the REMS relay metadata MIME Header shown in Table 12 is defined as the aggregation of one of the combinations of RFC header fields defined in Table 10 and one of the combinations of the new header fields defined in Table 11. Each combination defined in Table 12 has four parameters, namely: 1) An integer identifying the RFC headers combination. 2) An integer identifying the new header fields combinations. 3) The value of the required assurance levels (nil if this information is not present in the combination). 4) The consignment mode (nil if this information is not present). The table 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. All the REMS relay metadata MIME Headers instances can be obtained from the following expression: (RFCFields_id, NewFields_id,AssuranceLevelCombs, ConsignmentMode) where: • RFCFields_id goes from 1 to 2. • NewFields_id goes from 1 to 11. • AssuranceLevelCombs is one of {nil, low/low, subs/subs, high/high}. • ConsignmentMode is one of {nil, basic, consented, consentedSigned}. Table 12 defines some combinations and their corresponding purposes. Table 12: REM messages REMS relay metadata MIME Header combinations Combination identifier Combination definition Purpose For test cases without REM-RelayDate and without REM-ScheduledDelivery. Scenarios without message relaying REMSRelayMetadata(1,9,nil,nil) RFCFields#1 + NewFields#9 No indications neither of assurance levels nor consignment mode REMSRelayMetadata(1,10,low/low,nil) RFCFields#1 + NewFields#10(low/low) No consignment mode indicated and assurance level REMSRelayMetadata(1,10,sub/subs,nil) RFCFields#1 + NewFields#10(substantial/substantial) REMSRelayMetadata(1,10,high/high,nil) RFCFields#1 + NewFields#10(high/high) REMSRelayMetadata (1,11,low/low,basic) RFCFields#1 + NewFields#11(low/low, basic) Basic consignment mode and assurance level REMSRelayMetadata(1,11,subs/subs,basic) RFCFields#1 + NewFields#11(substantial/substantial, basic) REMSRelayMetadata (1,11,high/high,basic) RFCFields#1 + NewFields#11(high/high, basic) REMSRelayMetadata (1,11,low/low,consented) RFCFields#1 + NewFields#11(low/low, consented) Consented consignment mode and assurance level REMSRelayMetadata(1,11,subs/subs,consented) RFCFields#1 + NewFields#11(substantial/substantial, consented) REMSRelayMetadata (1,11,high/high,consented) RFCFields#1 + NewFields#11(high/high, consented) REMSRelayMetadata (1,11,low/low,consentedSigned) RFCFields#1 + NewFields#11(low/low, consentedSigned) Consented and signed consignment mode and assurance level REMSRelayMetadata(1,11,subs/subs,consentedSig ned) RFCFields#1 + NewFields#11(substantial/substantial, consentedSigned) ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 85 Combination identifier Combination definition Purpose REMSRelayMetadata (1,11,high/high,consentedSigned) RFCFields#1 + NewFields#11(high/high, consentedSigned) For test cases without REM-ScheduledDelivery. Scenarios with message relaying REMSRelayMetadata(1,6,nil,nil) RFCFields#1 + NewFields#6 No indications neither of assurance levels nor consignment mode REMSRelayMetadata(1,7,low/low,nil) RFCFields#1 + NewFields#7(low/low) No consignment mode indicated and assurance level REMSRelayMetadata(1,7,sub/subs,nil) RFCFields#1 + NewFields#7(substantial/substantial) REMSRelayMetadata(1,7,high/high,nil) RFCFields#1 + NewFields#7(high/high) REMSRelayMetadata (1,8,low/low,basic) RFCFields#1 + NewFields#8(low/low, basic) Basic consignment mode and assurance level REMSRelayMetadata(1,8,subs/subs,basic) RFCFields#1 + NewFields#8(substantial/substantial, basic) REMSRelayMetadata (1,8,high/high,basic) RFCFields#1 + NewFields#8(high/high, basic) REMSRelayMetadata (1,8,low/low,consented) RFCFields#1 + NewFields#8(low/low, consented) Consented consignment mode and assurance level REMSRelayMetadata(1,8,subs/subs,consented) RFCFields#1 + NewFields#8(substantial/substantial, consented) REMSRelayMetadata (1,8,high/high,consented) RFCFields#1 + NewFields#8(high/high, consented) REMSRelayMetadata (1,8,low/low,consentedSigned) RFCFields#1 + NewFields#8(low/low, consentedSigned) Consented and signed consignment mode and assurance level REMSRelayMetadata(1,8,subs/subs,consentedSign ed) RFCFields#1 + NewFields#8(substantial/substantial, consentedSigned) REMSRelayMetadata (1,8,high/high,consentedSigned) RFCFields#1 + NewFields#8(high/high, consentedSigned) For test cases with REM-RelayDate and with REM-ScheduledDelivery. Scenarios with message relaying REMSRelayMetadata(1,1,nil,nil) RFCFields#1 + NewFields#1 No indications neither of assurance levels nor consignment mode REMSRelayMetadata(1,2,low/low,nil) RFCFields#1 + NewFields#2(low/low) No consignment mode indicated and assurance level REMSRelayMetadata(1,2,sub/subs,nil) RFCFields#1 + NewFields#7(substantial/substantial) REMSRelayMetadata(1,2,high/high,nil) RFCFields#1 + NewFields#2(high/high) REMSRelayMetadata (1,3,low/low,basic) RFCFields#1 + NewFields#3(low/low, basic) Basic consignment mode and assurance level REMSRelayMetadata(1,3,subs/subs,basic) RFCFields#1 + NewFields#8(substantial/substantial, basic) REMSRelayMetadata (1,3,high/high,basic) RFCFields#1 + NewFields#3(high/high, basic) REMSRelayMetadata (1,3,low/low,consented) RFCFields#1 + NewFields#3(low/low, consented) Consented consignment mode and assurance level REMSRelayMetadata(1,3,subs/subs,consented) RFCFields#1 + NewFields#3(substantial/substantial, consented) REMSRelayMetadata (1,3,high/high,consented) RFCFields#1 + NewFields#3(high/high, consented) REMSRelayMetadata (1,3,low/low,consentedSigned) RFCFields#1 + NewFields#3(low/low, consentedSigned) Consented and signed consignment mode and assurance level REMSRelayMetadata(1,3,subs/subs,consentedSign ed) RFCFields#1 + NewFields#3(substantial/substantial, consentedSigned) REMSRelayMetadata (1,3,high/high,consentedSigned) RFCFields#1 + NewFields#3(high/high, consentedSigned) REMSRelayMetadata (1,4,low/low,nil) RFCFields#1 + NewFields#4(low/low) ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 86 Combination identifier Combination definition Purpose REMSRelayMetadata (1,5,low/low,basic) RFCFields#1 + NewFields#5(low/low, basic) Combinations for negative test cases (cause of submission rejection for instance) Outer most headers combinations similar to the ones shown in the table but replacing 1 by 2 in the first parameter would result in combinations with RFCFields#2.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.3 Combinations of fields for the signed data MIME header
|
In all the test cases defined in the present document this header shall be as specified in ETSI EN 319 532-3 [5], clause 6.2.2. The resulting combination of header fields will be identified as SIGDATA_COMB.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.4 Combinations of fields for the REMS introduction section
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.4.1 Introduction
|
The present clause defines combinations of fields for three different headers in the REMS introduction section, namely: the REMS introduction MIME header, the multipart/alternative free text subsection header, and the multipart/alternative html subsection header.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.4.2 Combinations of fields for the REMS introduction MIME header
|
All the test cases defined in the present shall include the "REM-Section-Type" field in this header. Its value shall be the recommended value in ETSI EN 319 532-3 [5], namely "rem_message/introduction". This combination is identified as REMS_IntrComb. The mandatory field "REM-Content-Type" shall also be present with its value as specified in ETSI EN 319 532-3 [5]. 6.2.4.3 Combinations of fields for the multipart/alternative free text subsection header Table 13 shows the two possible combinations of fields for the multipart/alternative free text subsection header derived from ETSI EN 319 532-3 [5] specifications, namely one with the "Content-Disposition" field present and one without the "Content-Disposition" field. Columns in Table 13 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10. Table 13: Combinations for the multipart/alternative free text subsection header Combination identifier Header field name Header field value Notes/Additional requirements Purpose FreeText#1 Content-Type as specified in ETSI EN 319 532-3 [5] Combination with Content-Disposition optional field present Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as recommended in ETSI EN 319 532-3 [5] FreeText#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without Content-Disposition optional field Content-Transfer- Encoding as recommended in ETSI EN 319 532-3 [5] ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 87
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.4.4 Combinations of fields for the multipart/alternative html subsection header
|
All the test cases defined in the present document shall include the two mandatory header fields ("Content-Type" and "Content-Transfer-Encoding") in the multipart/alternative html subsection header, with the values specified in ETSI EN 319 532-3 [5]. This combination is identified as HTMLComb. 6.2.5 Combinations of fields for the original message MIME section header Table 14 shows three combinations of fields for the original message section header derived from ETSI EN 319 532-3 [5] specifications. Columns in Table 14 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10 and the values in column "Value" in Table 11. Table 14: Combinations for the original message MIME section header Combination identifier Header field name Header field value Notes/Additiona l requirements Purpose OrMess#1 Content-Type as specified in ETSI EN 319 532-3 [5] Combination with all the optional fields present Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Description AS_PER_TESTCASE REM-Section-Type as recommended in ETSI EN 319 532-3 [5] OrMess#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without Content-Description optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] REM-Section-Type as recommended in ETSI EN 319 532-3 [5] OrMess#3 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without any optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] 6.2.6 Combinations of fields for one REMS extension MIME section header Table 15 shows three combinations of fields for one REMS extension MIME section header derived from ETSI EN 319 532-3 [5] specifications. Columns in Table 15 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10 and the values in column "Value" in Table 11. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 88 Table 15: Combinations for one REMS extension MIME section header Combination identifier Header field name Header field value Notes/Additional requirements Purpose Ext#1 Content-Type as recommended in ETSI EN 319 532-3 [5] Combination with all the optional fields present Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Description AS_PER_TESTCASE REM-Section-Type as recommended in ETSI EN 319 532-3 [5] REM-Extension- Code AS_PER_TESTCASE REM-Extension- Namespace-URI AS_PER_TESTCASE Ext#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without REM-Extension-Code and REM-Extension- Namespace-URI optional fields Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Description AS_PER_TESTCASE REM-Section-Type as recommended in ETSI EN 319 532-3 [5] Ext#3 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without any optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5]
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.7 Combinations of fields for one ERDS evidence MIME section header
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.7.1 Combinations of fields for one XML ERDS evidence MIME section header
|
Table 16 shows three combinations of fields for one ERDS evidence MIME section header derived from ETSI EN 319 532-3 [5] specifications when the ERDS evidence is in XML format. Columns in Table 16 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10 and the values in column "Value" in Table 11. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 89 Table 16: Combinations for one XML ERDS evidence MIME section header Combination identifier Header field name Header field value Notes/Additiona l requirements Purpose EVID#1 Content-Type as recommended in ETSI EN 319 532-3 [5] Combination with all the optional fields present Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Description AS_PER_TESTCASE REM-Section-Type as recommended in ETSI EN 319 532-3 [5] EVID#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without Content-Description optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] REM-Section-Type as recommended in ETSI EN 319 532-3 [5] EVID#3 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without any optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5]
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.7.2 Combinations of fields for one PDF ERDS evidence MIME section header
|
Table 17 shows three combinations of fields for one ERDS evidence MIME section header derived from ETSI EN 319 532-3 [5] specifications when the ERDS evidence is a PDF document. Columns in Table 17 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10 and the values in column "Value" in Table 11. NOTE: The identifiers for these combinations are identical to the identifiers for combinations of fields in headers of ERDS evidence sections containing XML ERDS evidence. This does not introduce any ambiguity in the present document, as the clauses that define test cases assign to each test case a unique identifier that includes a component indicating whether the ERDS evidence present in a certain REMS notification, REMS receipt, or REM dispatch are XML or PDF ERDS evidence. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 90 Table 17: Combinations for one PDF ERDS evidence MIME section header Combination identifier Header field name Header field value Notes/Additional requirements Purpose EVID#1 Content-Type as recommended in ETSI EN 319 532-3 [5] Combination with all the optional fields present Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Description AS_PER_TESTCASE REM-Section-Type as recommended in ETSI EN 319 532-3 [5] EVID#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without Content-Description optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] REM-Section-Type as recommended in ETSI EN 319 532-3 [5] EVID#3 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without any optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5]
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.2.8 Combinations of fields for the REMS signature MIME section header
|
Table 18 shows combinations of fields for the REMS signature section header derived from ETSI EN 319 532-3 [5] specifications, namely one with the "Content-Description" field present and one without the "Content- Description" field. Columns in Table 18 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value" in Table 10. In addition to that, a value enclosed in "" represents a literal value required for the field being dealt with. Table 18: Combinations for the multipart/alternative free text subsection header Combination identifier Header field name Header field value Notes/Additional requirements Purpose Sig#1 Content-Type as specified in ETSI EN 319 532-3 [5] Combination with all the optional fields present Content-Transfer- Encoding as specified in ETSI EN 319 532-3 [5] Content-Disposition as specified in ETSI EN 319 532-3 [5] Content-Description "S/MIME Cryptographic Signature" Sig#2 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without Content-Description optional field Content-Transfer- Encoding as recommended in ETSI EN 319 532-3 [5] Content-Disposition as specified in ETSI EN 319 532-3 [5] Sig#3 Content-Type as specified in ETSI EN 319 532-3 [5] Combination without any optional field Content-Disposition as specified in ETSI EN 319 532-3 [5] ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 91
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.3 Instances of REM payload
|
The present clause defines instances of REM payloads for being used in test cases. Cells in column "Instance" shows the specific instance of REM payload and all its parametrized components. Each instance is the aggregation of one of the instances of the outmost header defined in clause 6.2.2 and a list of MIME sections. Each section is the aggregation of a MIME header and a MIME body. The MIME headers will be instances of the MIME headers as specified in clauses 6.2.3 to 6.2.8. Each REM payload instance is composed by the following components: • the REMS relay metadata MIME Header; • the REM Introduction MIME section; • the Free Text MIME section; • the HTML Text MIME section; • the Original Message MIME section; • the Signature MIME section; and • the optional Extension MIME section. Each cell in column "Instance" identifies several REM payload instances, which have certain aspects in common and some other aspects that are different. This is achieved as indicated below: The content of a cell in column "Instance" has the following pattern: "REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,<AssLevel>,<Consignment>),REMSIntrCom,FreeTe xt#K,HTMLComb,OrMess#L,Sig#M)" Where I, J, K, L, and M are integers. Assigning a value to I one of the existing combinations for RFCFields is selected (for instance RFCFields#1). Assigning a value to J one of the existing combinations for NewFields is selected (for instance NewFields#2). Assigning a value to K one of the existing combinations for FreeText is selected (for instance FreeText#1). Assigning a value to L one of the existing combinations for original message MIME section header is selected (for instance OrMess#1). Finally, assigning value to M one of the existing combinations for Signature MIME section header is selected (for instance OrMess#1). <AssLevel> provides information on the assurance levels combinations, and can take as value either: • nil, indicating that the header fields for indicating assurance levels are absent; OR • "AssLevelComb", indicating that this parameter can take several values, each one corresponding to a combination of assurance levels. <Consignment> provides information on the consignment mode, and can take as value either: • nil, indicating that the header fields for indicating consignment mode is absent; OR • "ConsignmentModeId", indicating that this parameter can take several values, each one corresponding to one specific consignment mode. The aforementioned pattern is followed by text providing information of the values that I, J, K, L, M, "AssLevelComb" (if present), and "ConsignmentModeId" (if present) can take. The aforementioned pattern with this additional piece of information identifies a certain number of REM payloads in one unique cell. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 92 For instance, a cell containing the following text: REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,nil,nil),REMSIntrCom,FreeText#K,OrMess#L,Sig#M) where Where: I is one of {1,2}, J is one of {1, 6,9}, K is one of {1,2}, L is one of {1,2,3} and M is one of {1,2,3} Would identify all those REM payloads built when: • RFCFields#I is one of { RFCFields#1, RFCFields#2}; • NewFields#J is one of {NewFields#1, NewFields#6, NewFields#9}; • FreeText#K is one of {FreeText#1, FreeText#2}; • OrMess#L is one of {OrMess#1, OrMess#2, OrMess#3}; and • Sig#M is one of {Sig#1, Sig#2, Sig#3}. Similarly, a cell containing the following text: REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K, HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {3,8,11}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, L is one of {1,2,3} and M is one of {1,2,3} Would identify all those REM payloads built when: • RFCFields#I is one of { RFCFields#1, RFCFields#2}; • NewFields#J is one of {NewFields#3, NewFields#8, NewFields#11}; • AssLevelComb is one of the following combinations {low/low, substantial/substantial, high/high}; • ConsignmentModeId is one of {basic,consented,consentedSigned}; • FreeText#K is one of {FreeText#1, FreeText#2}; • OrMess#L is one of {OrMess#1, OrMess#2, OrMess#3}; and • Sig#M is one of {Sig#1, Sig#2, Sig#3}. Cells in "Purpose" column contain a description of the purpose of the REM payload instance. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 93 Table 19: Instances of REM payload Instance Purpose REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,nil,nil),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {1,6,9}, K is one of {1,2}, L is one of {1,2,3} and M is one of {1,2,3} No assurance levels indication. No consignment indication. No extension as there are not structured- valued fields in the headers REM payloads where J is 1: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM payloads where J is 6: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM payloads where J is 9: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 94 Instance Purpose REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,nil),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {2,7,10}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, L is one of {1,2,3} and M is one of {1,2,3} Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending of the value of parameter AssLevelComb. No consignment indication. No extensions. REM payloads where J is 2: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM payloads where J is 7: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM payloads where J is 10: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 95 Instance Purpose REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb, OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {3,8,11}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, L is one of {1,2,3} and M is one of {1,2,3} Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending of the value of parameter AssLevelComb. Consignment mode indication (either basic, or consented, or consentedSigned) depending of the value of parameter ConsignmentModeId. No extensions. REM payloads where J is 3: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM payloads where J is 8: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM payloads where J is 11: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 96 Instance Purpose REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#4,AssLevelComb,nil),REMSIntrCom,FreeText#K, HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {4,5}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, L is one of {1,2,3} and M is one of {1,2,3} REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#5,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K, HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {4,5}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, L is one of {1,2,3} and M is one of {1,2,3} Payloads for negative test cases. All of them incorporate REM-RelayDate header field. Negative test cases because scheduled delivery time is after the expiration date. No consignment indication. No extensions. Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. REM payloads where J is 4: No consignment mode indication. REM payloads where J is 5: Consignment mode indication as per value of parameter ConsignmentModeId. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 97
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.4 Instances of REMS notification
|
Table 20 defines instances of REM notifications for being used in test cases. Columns are as in clause 6.3. The notation for the content of cells in column "Instances" is as indicated in clause 6.3, with the addition that the instances of REMS notifications include Extension MIME sections, and the identification of the specific Extension MIME section follows the same principles as other MIME sections. Table 20: Instances of REMS notification Instance Purpose REMS_NotificationInst (REMSRelayMetadata (RFCFields#I,NewFields#J,nil,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M) Where: I is one of {1,2}, J is one of {1,6,9}, K is one of {1,2}, L is one of {1,2,3}, and M is one of {1,2,3} No assurance levels indication. No consignment indication. REMS notifications where J is 1: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REMS notifications where J is 6: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REMS notifications where J is 9: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 98 Instance Purpose REMS_NotificationInst (REMSRelayMetadata (RFCFields#I,NewFields#J,nil,nil),REMSIntrComb,FreeText#K,HTMLComb,Sig#L) Where: I is one of {1,2}, J is one of {1,6,9}, K is one of {1,2}, and L is one of {1,2,3} No assurance levels indication. No consignment indication. No extension as there are not structured- valued fields in the headers REMS notifications where J is 1: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REMS notifications where J is 6: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REMS notifications where J is 9: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 99 Instance Purpose REMS_notificationInst (REMSRelayMetadata (RFCFields#I,NewFields#J,AssLevelComb,nil),REMSIntrCom,FreeText#K,HTMLComb,Ext#L,Sig#M) Where: I is one of {1,2}, J is one of {2,7,10}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, L is one of {1,2,3}, and M is one of {1,2,3} Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending on the value of parameter AssLevelComb. No consignment indication. REMS notifications where J is 2: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REMS notifications where J is 7: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REMS notifications where J is 10: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 100 Instance Purpose REMS_notificationInst (REMSRelayMetadata (RFCFields#I,NewFields#J,AssLevelComb,nil),REMSIntrCom,FreeText#K,HTMLComb, Sig#L) Where: I is one of {1,2}, J is one of {2,7,10}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, and L is one of {1,2,3} Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending on the value of parameter AssLevelComb. No consignment indication. No extensions. REMS notifications where J is 2: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REMS notifications where J is 7: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REMS notifications where J is 10: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 101
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.5 Instances of REMS receipts
|
Table 21 defines instances of REMS receipts for being used in test cases. Columns are as in clause 6.3. A REMS receipt can have more than one ERDS evidence MIME section. The number and contents of these MIME sections will depend on the specific test case. Table 21: Instances of REMS receipt Instance Purpose REMS_ReceiptInst (REMSRelayMetadata (RFCFields#I,NewFields#J,nil,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L, <EVID#M>+,Sig#N) Where: I is one of {1,2}, J is one of {1,6,9}, K is one of {1,2}, L is one of {1,2,3}, M is one of {1,2,3}, and L is one of {1,2,3}. Additionally, the + symbol in <EVID#M> indicates that in each case, the REMS receipt instance shall contain as many Evidence MIME sections as Evidence MIME sections are indicated in the test case where the REMS receipt is used. This unique content identifies all the possible REMS receipts that will be needed in the definitions of the test cases. No assurance levels indication. No consignment indication. REMS receipts where J is 1: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REMS receipts where J is 6: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REMS receipts where J is 9: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 102
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
6.6 Instances of REM dispatch
|
Table 22 defines instances of REM dispatches for being used in test cases. Columns are as in clause 6.3. Details of the ERDS evidence MIME sections are indicated as in clause 6.5. Table 22: Instances of REM dispatch Instance Purpose REM_dispatchInst (REMSRelayMetadata (RFCFields#I,NewFields#J,nil,nil),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>+,Sig#O) Where: I is one of {1,2}, J is one of {1,6,9}, K is one of {1,2}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. As before the symbol + in <EVID#M>+ indicates that there will be as many Evidence MIME sections as the sections indicated in the test case using this REM dispatch. No assurance levels indication. No consignment indication. No extensions REM dispatches where J is 1: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM dispatches where J is 6: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM dispatches where J is 9: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 103 Instance Purpose REM_dispatchInst (REMSRelayMetadata (RFCFields#I,NewFields#J,AssLevelComb,nil),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L,Ext#M,<EVID#N>+,Sig#O) Where: I is one of {1,2}, J is one of {2,7,10}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. As before the symbol + in <EVID#M>+ indicates that there will be as many Evidence MIME sections as the sections indicated in the test case using this REM dispatch. Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending on the value of parameter AssLevelComb. No consignment indication. No extensions. REM dispatches where J is 2: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM dispatches where J is 7: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM dispatches where J is 10: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 104 Instance Purpose REM_dispatchInst REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L,Ext#M,<EVID#N>+,Sig#O) Where: I is one of {1,2}, J is one of {3,8,11}, K is one of {1,2}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. As before the symbol + in <EVID#M>+ indicates that there will be as many Evidence MIME sections as the sections indicated in the test case using this REM dispatch. Assurance levels indications (either low/low, or substantial/substantial, or high/high) depending on the value of parameter AssLevelComb. Consignment mode indication (either basic, or consented, or consentedSigned) depending of the value of parameter ConsignmentModeId. No extensions. REM dispatches where J is 3: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Incorporate REM-RelayDate header field. REM dispatches where J is 8: Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. Do not incorporate REM-RelayDate header field. REM dispatches where J is 11: Cannot be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is absent. Do not incorporate REM-RelayDate header field. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 105 Instance Purpose REM_payloadInst (REMSRelayMetadata (RFCFields#I,NewFields#4,AssLevelComb,nil),REMSIntrCom,FreeText#K, HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {4,5}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, L is one of {1,2,3} and M is one of {1,2,3} REM_payloadInst (REMSRelayMetadata (RFCFields#I,NewFields#5,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K, HTMLComb,OrMess#L,Sig#M) Where: I is one of {1,2}, J is one of {4,5}, AssLevelComb is one of {low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {basic,consented,consentedSigned}, L is one of {1,2,3} and M is one of {1,2,3} Payloads for negative test cases. All of them incorporate REM-RelayDate header field. Negative test cases because scheduled delivery time is after the expiration date. No consignment indication. No extensions. Will be used in scenarios where there is relaying of REM messages, as the REM-RelayDate header field is present. REM payloads where J is 4: No consignment mode indication. REM payloads where J is 5: Consignment mode indication as per value of parameter ConsignmentModeId. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 106
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
7 Other named sets
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
7.1 Named sets of participating REMSs
|
The present clause defines named sets of participating REMSs that are used for naming test cases in clause 5. The details on the participating REMSs are given using the following pattern: REMSs(I,J), where: • I stands for the number of Intermediate REMSs (IREMSs); and • J stands for the number of the Recipient's REMSs (RREMSs).
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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 23 shows the named sets of additional requirements. Table 23: Named sets of additional requirements Name of the set Additional requirements in the set AdditionalReqs#1 Original message: not signed, no attachment Number of recipients: 1 No sender's delegate Sender sends original message AdditionalReqs#2 Original message: not signed, no attachment Number of recipients: 1 Sender's delegate Sender's delegate sends original message
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-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. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 107
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8 Test cases definition
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.1 Introduction
|
The notations shown in clauses 4.1, 6 and 7, allow building a compact notation for defining tests cases. 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. For helping in understanding the notation, below follows the definition of the set of test cases for the scenario REM_SF#3. The definition of a set of test cases has two parts. Below follows the first one: REM_SF#3( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata (RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), 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: 1) The entities in the receiving side (RecSide). The notation for identifying one of the different alternatives is as specified in clause RECEIVING SIDE. 2) The REM 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 REMDISPATCH. 3) The REMS Receipt, carrying a XML_SUB_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 REMSEVIDENCE. 4) The additional requirements, whose notation has been specified in clause ADDITIONALREQS. 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. For AdditionalReqs: P is one of {1,2}. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 108 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), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#1, NewFields#11, high/high, consentedSigned),REMSIntrCom,FreeText#1,HTMLComb,OrMess#1, Ext#1,<EVID#1>,Sig#1), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata(RFCFields#1, NewFields#9 nil, nil),REMSIntrComb,FreeText#1,HTMLComb,Ext#1,<EVID#1>+,Sig#1), AdditionalReqs#P Defines ONE test case in the set, where: • The REM-RelayDate and REM-ScheduledDelivery header fields are absent in the REMS relay metadata MIME 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. • The headers in Free Text, Extension, Evidence, and Signature MIME extensions are as indicated in the corresponding clauses defining combinations of header fields for these MIME sections, when the parameter in all of them is 1.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2 Test cases for black-box model
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1 Test cases for Store&Forward style of operation
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.1 Introduction
|
The present clause defines a set of test cases for each scenario defined in clause XXX (Store&Forward style of operation in the black-box model). Below follow some remarks that apply to all the sets defined in the present clause: • All the scenarios do not deal with relaying of REM messages. REM-RelayDate header field is absent (i.e. the valid combination of NewFields are #9 to #11). • Each set includes test cases for different sets of entities at the receiving side (one or several recipients, and several recipients and one recipients' delegate). • Each set includes test cases for sender and test cases for sender's delegate. Below follow a set of rules that govern the values of NewFields#J, Assurance levels indication, and Consignment mode indication: 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 NewFields#9 neither Assurance levels indication nor Consignment mode indication are present. 4) For NewFields#10 Assurance levels indication is present, and Consignment mode indication is absent. 5) For NewFields#11 both Assurance levels indication, and Consignment mode indication are present. Any combination (NewFields#J, AssLevelComb, ConsignmentModeId) in a specific test case has to meet the rules 3 to 4. This clause defines, for this model and style of operation, one set of test cases with the details shown above. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 109 For other styles and models, the present document will present rules for defining such sets, as defining one set for each scenario would make the present document extremely long, and the specific definition of one set of test cases for one specific scenario will be straightforward applying the aforementioned rules.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.2 Test cases for scenario REM_SF#1
|
REM_SF#1( RecSide(F,G,H), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata(RFCFields#I,NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) 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 REMS_receipt_with_XML_SUB_REJ: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, L is one of {1,2,3}, M is one of {1,2,3}, and N is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RA02,RA03,RD04,RA05 } as defined in clause 8.3.3.1 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.3 Test cases for scenario REM_SF#2
|
REMSF#2( RecSide(F,G,H), REMS_receipt_with_{2 XML_SUB_REJ} (REMSRelayMetadata(RFCFields#I,NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P FailureReason ) 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 REMS_receipt_with_{2 XML_SUB_REJ}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, K is one of {1,2,3}, L is one of {1,2,3}, M is one of {1,2,3}, and N is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RA02,RA03,RD04,RA05 } as defined in clause 8.3.3.1 of ETSI EN 319 522-2 [2]. Failure reasons in REMS receipts will be different. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 110
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.4 Test cases for scenario REM_SF#3
|
REM_SF#3( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P ) 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.5 Test cases for scenario REM_SF#4
|
REM_SF#4( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, XML_CONT_CONS_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, XML_CONT_CONS_FAIL}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RD03,RD04,RD05,RD06} as defined in clause 8.3.3.4 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.6 Test cases for scenario REM_SF#5
|
REM_SF#5( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, 2 XML_CONT_CONS_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 111 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, 2 XML_CONT_CONS_FAIL}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RD03,RD04,RD05,RD06} as defined in clause 8.3.3.4 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.7 Test cases for scenario REM_SF#6
|
REM_SF#6( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P ) 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.8 Test cases for scenario REM_SF#7
|
REM_SF#7( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_CONT_HAND_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) 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. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 112 • For REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_CONT_HAND_FAIL}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RE03,RE04 } as defined in clause 8.3.3.5 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.9 Test cases for scenario REM_SF#8
|
REM_SF#8( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, 2 XML_CONT_HAND_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) 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 REM_dispatchInst_with_XML_SUB_ACC and REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, 2 XML_CONT_HAND_FAIL}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is one of {RE03,RE04 } as defined in clause 8.3.3.5 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.10 Test cases for scenario REM_SF#9
|
REM_SF#9( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC,XML_CONS_NOT, XML_CONT_CONS} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), REMS_notification_of_Consignment (REMSRelayMetadata(RFCFields#I,NewFields#10, AssLevelComb,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M), AdditionalReqs#P ) 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. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 113 • For REM_dispatchInst_with_XML_SUB_ACC, REMS_receipt_with__{XML_SUB_ACC,XML_CONS_NOT, XML_CONT_CONS}, and REMS_notification_of_Consignment: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.11 Test cases for scenario REM_SF#10
|
REM_SF#10( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, XML_CONS_NOT_FAIL } (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), REMS_notification_of_Consignment (REMSRelayMetadata(RFCFields#I, NewFields#10, AssLevelComb,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M), AdditionalReqs#P, ReasonFailure ) 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 REM_dispatchInst_with_XML_SUB_ACC, REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, XML_CONS_NOT_FAIL}, and REMS_notification_of_Consignment: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is identified by one of the codes defined in clause 8.3.3.4 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.12 Test cases for scenario REM_SF#11
|
REM_SF#11( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, 2 XML_CONS_NOT_FAIL } (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), REMS_notification_of_Consignment (REMSRelayMetadata(RFCFields#I, NewFields#10, AssLevelComb,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M), AdditionalReqs#P, ReasonFailure ) 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. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 114 • For REM_dispatchInst_with_XML_SUB_ACC, REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, 2 XML_CONS_NOT_FAIL }, and REMS_notification_of_Consignment: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}. • FailureReason is identified by one of the codes defined in clause 8.3.3.4 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.13 Test cases for scenario REM_SF#12
|
REM_SF#12( RecSide(F,G,H), REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K,HT MLComb,OrMess#L,Sig#M) REMS_receipt_with_XML_SUB_ACC, (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P ) 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 REM_payloadInst, REMS_receipt_with_XML_SUB_ACC,and REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, K is one of {1,2}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. • For AdditionalReqs: P is one of {1,2}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.1.14 Test cases for scenario REM_SF#13
|
REM_SF#13( RecSide(F,G,H), REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K,HT MLComb,OrMess#L,Sig#M) REMS_receipt_with_XML_SUB_ACC, (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), REMS_receipt_with_ XML_CONT_CONS (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P ) 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 REM_payloadInst, REMS_receipt_with_XML_SUB_ACC,and REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS}: - I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned }, K is one of {1,2}, L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 115 • For AdditionalReqs: P is one of {1,2}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.2 Test cases for Store&Notify style of operation
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.2.1 Rules for REM messages
|
The following rules will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios REM_SN#1 to REM_SN#4: REM dispatches with ERDS Evidences will be built on the following components: (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O) Where: • I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. REM receipts with ERDS Evidences or sets of ERDS Evidences will be built on the following components: REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N) Where: • I is one of {1,2}, J is one of {9,10,11}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. REMS_notification_for_Acceptance will be built on the following components: (REMSRelayMetadata(RFCFields#I, NewFields#10, AssLevelComb,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M) Where: • I is one of {1,2}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, L is one of {1,2,3}, and M is one of {1,2,3}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.2.2.2 Rules for failure reasons
|
The following FailureReason codes will be used for the (black-box model/Store&Notify style): 1) In scenario REMS_SN#2, one of the receiving entities rejects consignment. One XML_CONS_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC08 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2]. 2) In scenario REMS_SN#3, one of the receiving entities does not answer in time to the notification for acceptance. One XML_ACC_REJ_EXP ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC09 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3 Test cases for 4-corner model
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.1 Introduction and general rules
|
In this model, SREMS relays REM messages to the RREMS. Below follow a set of rules that govern the values of NewFields#J, Assurance levels indication, and Consignment mode indication: 1) For NewFields#1 and NewFields#4 neither Assurance levels indication nor Consignment mode indication are present. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 116 2) For NewFields#2 and NewFields#5 Assurance levels indication is present, and Consignment mode indication is absent. 3) For NewFields#3 and NewFields#6 both Assurance levels indication, and Consignment mode indication are present. Any combination (NewFields#J, AssLevelComb, ConsignmentModeId) in a specific test case has to meet the rules 3 to 4.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.2 Test cases for Store&Forward to Store&Forward scenarios
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.2.1 Rules for REM messages
|
The following rules will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_RREMS_SF#1 to SREMS_SF_RREMS_SF#5: REM dispatches that are relayed from SREMS to RREMS and REM dispatches that are generated by RREMS from REM dispatches that have been relayed by the SREMS will be built on the following components: (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O) Where: • I is one of {1,2}, J is one of {1,2,3,4,5,6}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. REM receipts with ERDS Evidences or sets of ERDS Evidences will be built on the following components: REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N) Where: • I is one of {1,2}, J is one of {1,2,3,4,5,6}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, ConsignmentModeId is one of {nil, basic, consented, consentedSigned },L is one of {1,2,3}, M is one of {1,2,3}, N is one of {1,2,3}, and O is one of {1,2,3}. REMS_notification_for_XY will be built on the following components: (REMSRelayMetadata(RFCFields#I, NewFields#10, AssLevelComb,nil),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,Sig#M) Where: • I is one of {1,2}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, L is one of {1,2,3}, and M is one of {1,2,3}.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.2.2 Rules for failure reasons
|
The following FailureReason codes will be used for the (4-corner model/Store&Forward to Store&Forward): 1) In scenario SREMS_SF_RREMS_SF#1, RREMS rejects relaying of the REM dispatch generated by SREMS. One XML_REL_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is one of {RB02, RB03, RB04, RB05, RB06, RB02} as specified in clause 8.3.3.2 of ETSI EN 319 522-2 [2]. 2) In scenario SREMS_SF_RREMS_SF#4, one of the handovers by a receiving entity fails. One XML_CONT_HAND_FAIL evidence is generated. For this scenario the reason for failure code is one of {RE03,RE04} as specified in clause 8.3.3.5 of ETSI EN 319 522-2 [2]. 3) In scenario SREMS_SF_RREMS_SF#5, one of the consignments to a receiving entity fails. One XML_CONT_CONS_FAIL evidence is generated. For this scenario the reason for failure code is one of {RD04, RD05, RD06} as specified in clause 8.3.3.4 of ETSI EN 319 522-2 [2]. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 117
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.3 Test cases for Store&Forward to Store&Notify scenarios
| |
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.3.1 Rules for REM messages
|
The rules that will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_RREMS_SN#1 to SREMS_SF_RREMS_SN#5 shall be the same as the rules defined in clause 8.3.2.1 for Store&Forward to Store&Forward scenarios.
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.3.2 Rules for failure reasons
|
The following FailureReason codes will be used for the (4-corner model/Store&Forward to Store&Notify): 1) In scenario SREMS_SF_RREMS_SN#2, one receiving entity rejects consignment. One XML_CONS_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC08 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2]. 2) In scenario SREMS_SF_RREMS_SN#3, one receiving entity does not react in time to the notification for acceptance of consignment. One XML_ACC_REJ_EXP evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC09 as specified in clause 8.3.3.3 of ETSI EN 319 522-2 [2]. 3) In scenario SREMS_SF_RREMS_SN#4, one of the consignments to a receiving entity fails. One XML_CONT_CONS_FAIL evidence is generated. For this scenario the reason for failure code is one of {RD04, RD05, RD06} as specified in clause 8.3.3.4 of ETSI EN 319 522-2 [2]. 4) In scenario SREMS_SF_RREMS_SN#5, one of the handovers by a receiving entity fails. One XML_CONT_HAND_FAIL ERDS Evidence is generated. For this scenario the reason for failure code is one of {RE03,RE04} as specified in clause 8.3.3.5 of ETSI EN 319 522-2 [2].
|
438d2bf0f70eaf9db324bb04b8b1263b
|
119 534-2
|
8.3.4 Test cases for Store&Notify to Store&Forward scenarios
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.