hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
5.7 CAdES-E-A test cases
|
The test cases in this clause have been defined for different combinations of CAdES-E-A signatures attributes. Mandatory attributes for CAdES-E-A described in [2] specification, clauses 6.3 and A.2, shall be present. Table 7 shows which attributes are required to generate test CAdES-E-A signatures for each test case. Table 7: Test cases for CAdES-E-A signatures TC ID Description Pass criteria Signature attributes CAdES/A/1 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- T as specified in CAdES/T/1 test case. Validation data shall be included adding the certificate-values attribute and the revocation-values attribute before applying archive-time-stamp-v3. The revocation data used are CRLs. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, ESSSigningCertificateV2, SigningCertificate (included in SignedData.certificates field), SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/2 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- T as specified in CAdES/T/1 test case. Validation data shall be included adding the certificate-values attribute and the revocation-values attribute before applying archive-time-stamp-v3. The revocation data used are OCSP responses. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, ESSSigningCertificateV2, SigningCertificate (included in SignedData.certificates field), SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o OcspListIDs o CertificateValues o RevocationValues o ocspVals o ArchiveTimeStampV3 o ats-hash-index-v3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 15 TC ID Description Pass criteria Signature attributes CAdES/A/3 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- T as specified in CAdES/T/1 test case. Validation data shall be included adding the certificate-values attribute and the revocation-values attribute before applying archive-time-stamp-v3. The revocation data used are CRLs. A CAdES-C timestamp covering the signature, the signature timestamp, the complete- certificate-references attribute and complete- revocation-references attribute shall be included. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, ESSSigningCertificateV2, SigningCertificate (included in SignedData.certificates field), SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/4 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- T as specified in CAdES/T/1 test case. Validation data shall be included adding the certificate-values attribute and the revocation-values attribute before applying archive-time-stamp-v3. The revocation data used are OCSP responses. A CAdES-C timestamp covering the signature, the signature timestamp, the complete-certificate- references attribute and complete-revocation- references attribute shall be included. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, ESSSigningCertificateV2, SigningCertificate (included in SignedData.certificates field), SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o OcspListIDs o ESCTimeStamp o CertificateValues o RevocationValues o ocspVals o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/5 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- T signature as specified in CAdES/T/1 test case. Validation data shall be included in SignedData before applying archive- time-stamp-v3. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), Crls.crl, ESSSigningCertificateV2, SignatureTimeStamp and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls.crl • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o ArchiveTimeStampV3 o ats-hash-index-v3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 16 TC ID Description Pass criteria Signature attributes CAdES/A/6 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- C signature as specified in CAdES/C/1 test case. Validation data shall be included in SignedData before applying archive- time-stamp-v3. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), Crls.crl, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls.crl • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/7 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- X Type 1 signature as specified in CAdES/X/1 test case. Validation data shall be included in SignedData before applying archive- time-stamp-v3. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), Crls.crl, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls.crl • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/8 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- X Type 2 signature as specified in CAdES/X/2 test case. Validation data shall be included in SignedData before applying archive- time-stamp-v3. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), Crls.crl, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, TimestampedCertsCRLs and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls.crl • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o TimestampedCertsCRLs o ArchiveTimeStampV3 o ats-hash-index-v3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 17 TC ID Description Pass criteria Signature attributes CAdES/A/9 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- XL Type 1 signature as specified in CAdES/XL/1 test case. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/10 This test case tests a CAdES-E-A signature with ATSv3 built on a CAdES-E- XL Type 2 signature as specified in CAdES/XL/2 test case. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, TimestampedCertsCRLs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o TimestampedCertsCRLs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 o ats-hash-index-v3 CAdES/A/11 This test case tests the CAdES-E-A with ATSv3 built on a CAdES-E-A with ATSv2. Validation data related to ATSv2 shall be included in SignedData.Certificates and SignedData.Crls within time- stamp-token. Positive validation. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate (included in SignedData.certificates field), ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues, ArchiveTimeStampV2 and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o TimestampedCertsCRLs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV2 o Certificates o Crls o ArchiveTimeStampV3 o ats-hash-index-v3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 18 6 Testing extended CAdES signatures augmention interoperability
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
6.1 Introduction
|
This clause describes augmentation tests where a signer generates a basic signature and a verifier, after verifying, augments it to a more evolved form. The following clauses contain augmentation test cases grouped by CAdES level.
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
6.2 Augmentation to CAdES-E-C signatures test cases
|
The test cases in this clause deal with the augmentation to CAdES-E-C signatures. Table 8 shows 2 augmentation to CAdES-E-C signatures test cases. Table 8: Test cases for augmentation to CAdES-E-C signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/1 This test case tests the augmentation of a CAdES- E-BES signature as specified in CAdES/BES/2 test case to a CAdES-E-C signature as specified in CAdES/C/1 test case. Positive validation. The signature to be augmented shall be successfully validated before upgrading. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs CAdES/Aug/2 This test case tests the augmentation of a CAdES- E-T signature as specified in CAdES/T/1 test case to a CAdES-C signature as specified in CAdES/C/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 19
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
6.3 Augmentation to CAdES-E-X signatures test cases
|
The test cases in this clause deal with the augmentation to CAdES-E-X signatures. Table 9 shows 3 augmentation to CAdES-E-X signatures test cases. Table 9: Test cases for augmentation to CAdES-E-X signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/3 This test case tests the augmentation of a CAdES- E-BES signature as specified in CAdES/BES/2 test case to a CAdES-E-X signature as specified in CAdES/X/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp CAdES/Aug/4 This test case tests the augmentation of a CAdES- E-T signature as specified in CAdES/T/1 test case to a CAdES-E-X signature as specified in CAdES/X/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp CAdES/Aug/5 This test case tests the augmentation of a CAdES- E-C signature as specified in CAdES/C/1 test case to a CAdES-E-X signature as specified in CAdES/X/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 20
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
6.4 Augmentation to CAdES-E-XL signatures test cases
|
The test cases in this clause deal with the augmentation to CAdES-E-XL signatures. Table 10 shows 3 augmentation to CAdES-E-XL signatures test cases. Table 10: Test cases for augmentation to CAdES-E-XL signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/6 This test case tests the augmentation of a CAdES- E-BES signature as specified in CAdES/BES/2 test case to a CAdES-E-XL signature as specified in CAdES/XL/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals CAdES/Aug/7 This test case tests the augmentation of a CAdES- E-T signature as specified in CAdES/T/1 test case to a CAdES-E-XL signature as specified in CAdES/XL/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals CAdES/Aug/8 This test case tests the augmentation of a CAdES- E-C signature as specified in CAdES/C/1 test case to a CAdES-E-XL signature as specified in CAdES/XL/1 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 21
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
6.5 Augmentation to CAdES-E-A signatures test cases
|
The test cases in this clause deal with the augmentation to CAdES-E-A signatures. Table 11 shows 3 augmentations to CAdES-E-A signatures test cases. Table 11: Test cases for upgrading to CAdES-A forms TC ID Description Pass criteria Signature attributes CAdES/Aug/9 This test case tests the augmentation of a CAdES- E-BES signature as specified in CAdES/BES/2 test case to a CAdES-E-A signature as specified in CAdES/A/5 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, Crls, ESSSigningCertificateV2, SignatureTimeStamp and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o ArchiveTimeStampV3 CAdES/Aug/10 This test case tests the augmentation of a CAdES- E-T signature as specified in CAdES/T/1 test case to a CAdES-E-A signature as specified in CAdES/A/5 test case. Positive validation. The signature to be augmented shall be successfully validated before augmentation. The augmented signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, Crls, ESSSigningCertificateV2, SignatureTimeStamp and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • Crls • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o ArchiveTimeStampV3 CAdES/Aug/11 This test case tests the upgrade of a CAdES-E-C signature as specified in CAdES/C/1 test case to a CAdES-E-A signature as specified in CAdES/A/1 test case. Positive validation. The signature to be updgraded shall be successfully validated before upgrading. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 22
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
7 Testing negative extended CAdES signatures
| |
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
7.1 CAdES-E-BES test cases
|
The test cases in this clause have been defined for CAdES-E-BES signatures. Table 12 shows which attributes are defined in the negative CAdES-E-BES signatures for each test case. Table 12: Negative test cases for CAdES-E-BES signatures TC ID Description Pass criteria Signature attributes CAdES/BESN/1 Verify a signed document having a wrong signature (the hash that was signed is not the hash of the specified MessageDigest element). Negative validation because the hash that was signed is not the hash of the specified MessageDigest attribute. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime CAdES/BESN/2 Verify a document signed with an expired signing certificate. Negative validation because the signing certificate is expired (at the time specified in signingTime attribute). The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime CAdES/BESN/3 Verify a document signed with a revoked/suspended signing certificate. Negative validation because the signing certificate is revoked (at the time specified in signingTime attribute). The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime CAdES/BESN/4 Verify a signed document in which the hash value of the signing certificate is different from the hash value in ESS signing certificate V2 attribute. Negative validation because the certHash value in ESSSigningCertificateV2 attribute does not match to the hash value of signer certificate. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime CAdES/BESN/5 Verify a signed document whose format is not CAdES-E-BES. Negative validation because the signature format is not a CAdES- E-BES form. The signature shall contain ContentType, SigningTime, MessageDigest and SigningCertificate attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ContentType o SigningTime CAdES/BESN/6 Verify a document signed with an untrusted signing certificate. Negative validation because the signing certificate is untrusted. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 23
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
7.2 CAdES-E-EPES test cases
|
The test cases in this clause have been defined for CAdES-E-EPES signatures. Table 13 shows which attributes are defined in the negative CAdES-E-EPES signatures for each test case. Table 13: Negative test cases for CAdES-E-EPES signatures TC ID Description Pass criteria Signature attributes CAdES/EPESN/1 Verify a signed document having the value of SignaturePolicyId.sigPolic yHash field that does *NOT* match to the hash value of signer policy file. Negative validation because the hash value in SignaturePolicyId.sigPolicyHash included in SignaturePolicyIdentifier attribute does not match to the hash value of signer policy file. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, SignaturePolicyIdentifier and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime o SignaturePolicyIdentifier CAdES/EPESN/2 Verify a signed document in which the sigPolicyHash field value of SignaturePolicyIdentifier attribute in the CAdES- EPES signature is identical to signPolicyHash field value of IETF RFC 3125 [i.4] ASN.1 signature policy file. However in the policy file, signPolicyHash is *NOT* identical to the hash value which was calculated by the SignPolicyInfo without ASN.1 tag and length. Negative validation because the sigPolicyHash field value of SignaturePolicyIdentifier attribute in the CAdES-E-EPES signature, while being identical to signPolicyHash field value of ASN.1 signature policy file, is not identical to the hash value which is calculated by the SignPolicyInfo without ASN.1 tag and length. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, SignaturePolicyIdentifier and ESSSigningCertificateV2 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime o SignaturePolicyIdentifier
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
7.3 CAdES-E-T test cases
|
The test cases in this clause have been defined for CAdES-E-T signatures. Table 14 shows which attributes are defined in the negative CAdES-E-T signatures for each test case. Table 14: Negative test cases for CAdES-E-T signatures TC ID Description Pass criteria Signature attributes CAdES/TN/1 Verify a signed document in which the signing certificate, at the time in SignatureTimeStamp, had been already expired. Negative validation because at the time in SignatureTimeStamp, the signing certificate had been already expired. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 24 TC ID Description Pass criteria Signature attributes CAdES/TN/2 Verify a signed document in which the signing certificate, at the time in SignatureTimeStamp, had been already revoked. Negative validation because at the time in SignatureTimeStamp, the signing certificate had been already revoked. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp CAdES/TN/3 Verify a signed document in which the hash value of messageImprint in SignatureTimeStamp does *NOT* match to the hash value of corresponding signature value of signerInfo. Negative validation because the hash value of messageImprint in SignatureTimeStamp does *NOT* match to the hash value of corresponding signature value of signerInfo. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp CAdES/TN/4 Verify a signed document in which the timestamp signing certificate, at the time in SignatureTimeStamp, had been already expired. Negative validation because at the time in SignatureTimeStamp, the timestamp signing certificate had been already expired. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp CAdES/TN/5 Verify a signed document in which the timestamp signing certificate, at the time in SignatureTimeStamp, had been already revoked. Negative validation because at the time in SignatureTimeStamp, the timestamp signing certificate had been already revoked. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp CAdES/TN/6 Verify a signed document in which the timestamp signing certificate is untrusted. Negative validation because the anchor CA of the SignatureTimeStamp signing chain trust is unknown. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate ESSSigningCertificateV2 and SignatureTimeStamp attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 25
|
61cae43c0e2451863c31e9442f9d8612
|
119 124-3
|
7.4 CAdES-E-A test cases
|
The test cases in this clause have been defined for CAdES-E-A signatures. Table 15 shows which attributes are defined in the negative CAdES-E-A signatures for each test case. Table 15: Negative test cases for CAdES-A signatures TC ID Description Pass criteria Signature attributes CAdES/AN/1 Verify a signed document in which the time in the SignatureTimeStamp is ulterior than the time in ATSv3. Negative validation because the time in the SignatureTimeStamp is ulterior than the time in ArchiveTimeStampV3. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, TimestampedCertsCRLs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o TimestampedCertsCRLs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 CAdES/AN/2 Verify a signed document in which the time in the TimestampedCertsCRLs is ulterior than the time in ATSv3. Negative validation because the time in the TimestampedCertsCRLs is ulterior than the time in ArchiveTimeStampV3. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, TimestampedCertsCRLs, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o TimestampedCertsCRLs o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 26 TC ID Description Pass criteria Signature attributes CAdES/AN/3 Verify a signed document in which the time in the ESCTimeStamp is ulterior than the time in ATSv3. Negative validation because the time in the ESCTimeStamp is ulterior than the time in ArchiveTimeStampV3. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 CAdES/AN/4 Verify a signed document in which the content in ats- hash-index element has not the right value related to the CAdES signature to which the ATSv3 has been applied. Negative validation because the content in ats-hash-index element has not the right value related to the CAdES signature to which the ArchiveTimeStampV3 has been applied. The signature shall contain ContentType, SigningTime, MessageDigest, SigningCertificate, ESSSigningCertificateV2, SignatureTimeStamp, CompleteCertificateRefs, CompleteRevocationRefs, ESCTimeStamp, CertificateValues, RevocationValues and ArchiveTimeStampV3 attributes. • Certificates o SigningCertificate • SignedAttributes o MessageDigest o ESSSigningCertificateV2 o ContentType o SigningTime • UnsignedAttributes o SignatureTimeStamp o CompleteCertificateRefs o IssuerSerial o OtherHashAlgAndVal ue o CompleteRevocationRefs o CRLListIDs o ESCTimeStamp o CertificateValues o RevocationValues o crlVals o ArchiveTimeStampV3 ETSI ETSI TS 119 124-3 V1.1.1 (2016-06) 27 History Document history V1.1.1 June 2016 Publication
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
1 Scope
|
The present document provides mechanism to incorporate evidence records in ASN.1 format within a CAdES signature as outlined in ETSI EN 319 122-1 [4], annex B. It specifies the attributes to be used and profiles the ERS standard (IETF RFC 4998 [2]) to provide clear rules how to incorporate ERS within a CAdES signature or a legacy CAdES signature.
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
2 References
| |
06559e33e90280230a357784864e9b49
|
119 122-3
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which 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] IETF RFC 3161 (2001): "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". [2] IETF RFC 4998 (2007): "Evidence Record Syntax (ERS)". [3] IETF RFC 5816 (2010): "ESSCertIDv2 Update for RFC 3161". [4] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures".
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks 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 TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.2] ETSI TS 101 733: "Electronic Signatures and Infrastructures (ESI); CMS Advanced Electronic Signatures (CAdES)". [i.3] ETSI EN 319 122-2: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 2: Extended CAdES signatures". [i.4] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [i.5] ETSI EN 319 162-1: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 1: Building blocks and ASiC baseline containers". [i.6] ETSI EN 319 162-2: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 2: Additional ASiC containers". ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 6 [i.7] ETSI TS 119 172-1: "Electronic Signatures and Infrastructures (ESI); Signature policies; Part 1: Building blocks and table of contents for human readable signature policy documents".
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
3 Definitions and abbreviations
| |
06559e33e90280230a357784864e9b49
|
119 122-3
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.1], ETSI EN 319 122-1 [4] and the following apply: archive-timestamp: timestamp which is used for long-term preservation purposes EXAMPLE: An archive-timestamp can for example be a TimeStampToken according to IETF RFC 3161 [1] and updated by IETF RFC 5816 [3] or an ArchiveTimeStamp according to IETF RFC 4998 [2]. evidence-record: Evidence Record according to IETF RFC 4998 [2]. evidence-records attribute: unsigned attribute which contains one or more evidence-records as defined in the present document evidence record renewal: either time-stamp renewal or hash-tree renewal within an evidence record initial ArchiveTimeStamp: the first ArchiveTimeStamp instance of the first ArchiveTimeStampChain instance within the ArchiveTimeStampSequence instance NOTE: ArchiveTimeStamp, ArchiveTimeStampChain and ArchiveTimeStampSequence are as defined in IETF RFC 4998 [2]. validation data: data that is used to validate a digital signature
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: ER Evidence Record ERS Evidence Record Syntax TSU Time Stamping Unit
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
4 General requirements
| |
06559e33e90280230a357784864e9b49
|
119 122-3
|
4.1 Introduction
|
This clause specifies mechanisms how to include validation data into the signature. 4.2 Inclusion of validation data within a TimeStampToken instance When including validation data within a TimeStampToken instance according to IETF RFC 3161 [1] and updated by IETF RFC 5816 [3] one of the following methods shall be used: 1) adding the information in the SignedData of the timestamp token; or ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 7 2) adding the certificate-values attribute according to ETSI EN 319 122-1 [4], clause A.1.1.2 and the revocation-values attribute according to ETSI EN 319 122-1 [4], clause A.1.2.2 as unsigned attributes within the TimeStampToken instance. Method 1) should be used.
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
4.3 Inclusion of validation data within CAdES signatures
|
The present document specifies two strategies for the inclusion of validation data within a CAdES signature, depending on whether attributes for long term availability, as defined in different versions of ETSI TS 101 733 [i.2], have already been added to the SignedData: • If none of ATSv2 attributes (see clause A.2.4 of ETSI EN 319 122-1 [4]), or an earlier form of archive time-stamp as defined in ETSI TS 101 733 [i.2] or long-term-validation (see clause A.2.5 of ETSI EN 319 122-1 [4]) attributes is already present in any SignerInfo of the root SignedData, then the new validation material shall be included within the root SignedData.certificates, or SignedData.crls as applicable. • If an ATSv2, or other earlier form of archive time-stamp or a long-term-validation attribute, is present in any SignerInfo of the root SignedData then the root SignedData.certificates and SignedData.crls contents shall not be modified. The new validation material shall be provided within the TimeStampToken instance of the latest archive time-stamp (which can be an ATSv2 or an ATSv3 as defined in clause 5.5.3 of ETSI EN 319 122-1 [4]) or within the latest long-term-validation attribute already contained in the SignerInfo as described in ETSI EN 319 122-1 [4], clause A.2.5. OCSP responses shall be included as defined in clause 5.4.2 of ETSI EN 319 122-1 [4]. If the OCSP response is included within SignedData.crls, it shall be included as defined in clause 5.4.2.2 of ETSI EN 319 122-1 [4]. When generating a new attribute to include validation data, either initially when creating the signature or later when augmenting the signature, it shall be encoded in DER (see clause 4.7.1 of ETSI EN 319 122-1 [4]), whilst preserving the encoding of any signed field included in the attribute. The augmentation shall preserve the binary encoding of already present unsigned attributes and any component contributing to the archive time-stamp's message imprint computation input.
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
5 Attribute semantics and syntax
| |
06559e33e90280230a357784864e9b49
|
119 122-3
|
5.1 The evidence-records attributes
|
In the present document two attributes are described that allow to include an evidence record (ER) over the whole SignedData instance: • The internal-evidence-records attribute (clause 5.2) protects the whole SignedData instance and is used in cases of attached signatures. • The external-evidence-records attribute (clause 5.3) also protects the whole SignedData instance not containing an eContent element within encapContentInfo (a detached signature), and the external signed data. The term "evidence-records attribute" is used to denote either one of these attributes. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 8 Semantics The evidence-records attribute shall be an unsigned attribute. At most one of the SignerInfo instances within the SignedData instance shall contain evidence-records attributes. If the SignerInfo instance contains more than one evidence-records attribute, only the ER(s) in the latest added evidence-records attribute shall be updated. NOTE 1: Updating one of the ER in the other evidence-records attributes will invalidate the ER(s) in the later added evidence-records attribute(s). Once an evidence-records attribute is included within a SignedData instance, the only changes that might be applied to the SignedData instance are the renewal of the ER within the evidence-records attribute, the adding of a new ER within a new AttributeValue of the latest evidence record attribute or the adding of another evidence-records attribute. No other changes shall be applied to the SignedData instance. Syntax The ContentInfo instance shall be DER encoded before computing the hash. The evidence-records attribute may contain one or more instances of AttributeValue type. The evidence-records attribute should contain one instance of AttributeValue type. If the evidence-records attribute contains more than one instance of AttributeValue type, the input of the message imprint computation of all initial ArchiveTimeStamp within each of the AttributeValue instances shall include at least exactly the same fields within the signature and the signed document. The parts of the reduced hash-tree not corresponding to the signature or the signed document may be different. NOTE 2: Having more than one instance of AttributeValue type allows to have parallel evidence-records (from different TSAs or with different hash algorithms) protecting the same signature. NOTE 3: This means that if a signature contains already an evidence-records attribute with more than one instance of AttributeValue type, and a new evidence-records attribute is added (with one or more instances of AttributeValue type) this new attribute covers amongst other information the whole previous evidence-records attribute, including all instances of AttributeValue type. The evidence-records attribute value shall be an instance of EvidenceRecord ASN.1 type as defined in IETF RFC 4998 [2]. The timeStamp field of any ArchiveTimeStamp instance within the EvidenceRecord instance shall be of type TimeStampToken as defined in IETF RFC 3161 [1] and updated by IETF RFC 5816 [3]. Before adding a new ArchiveTimeStamp instance to the ER, i.e. during a Timestamp Renewal or a Hash-Tree Renewal, the validation data missing to validate the time-stamp within the latest ArchiveTimeStamp instance shall be included within the TimeStampToken of the latest ArchiveTimeStamp instance as described in clause 4. Before covering a SignedData instance with an ER included in an evidence-records attribute, the SignedData shall be extended to include any validation data, not already present, which is required for validating all the included SignerInfo instances. Validation data may include certificates, CRLs, OCSP responses, as required to validate any signed object within the signature including the existing signature, counter-signatures, time-stamps, OCSP responses, certificates, attribute certificates and signed assertions. In the case that the validation data contains a Delta CRL, then the whole set of CRLs shall be included to provide a complete revocation list. NOTE 4: Validation data already present for example in the time-stamp token need not be included again. Before adding a new evidence-records attribute, all the missing validation data to validate all the evidence-records in the previous evidence-records attributes shall be added within the corresponding timeStamp field instance of the latest ArchiveTimeStamp instance in each evidence-record as described in clause 4. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 9
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
5.2 The internal-evidence-records attribute
|
Semantics The internal-evidence-records attribute incorporates an ER covering the ContentInfo instance of type signed-data, as specified in ETSI EN 319 122-1 [4], containing an eContent element within encapContentInfo. Syntax The internal-evidence-records attribute shall be identified by the id-aa-er-internal OID as defined in ERS (IETF RFC 4998 [2], appendix A). For the initial ArchiveTimeStampSequence, 1) if the initial ArchiveTimeStamp contains the reducedHashtree field, then the first component of the instance of PartialHashtree type shall contain in its object group at least the hash value of the ContentInfo instance of type signed-data; 2) if the initial ArchiveTimeStamp does not contain the reducedHashtree field, then the message imprint of the corresponding TimeStampToken shall be the hash value of the ContentInfo instance of type signed- data. Illustration Figure 1 illustrates the internal-evidence-records attribute. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 10 Figure 1: Illustration of internal-evidence-records attribute ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 11
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
5.3 The external-evidence-records attribute
|
Semantics The external-evidence-records attribute incorporates an ER covering the ContentInfo instance of type signed-data, as specified in ETSI EN 319 122-1 [4], not containing an eContent element within encapContentInfo, i.e. in case of an external signature, and the external signed data. Syntax The external-evidence-records attribute shall be identified by the id-aa-er-external OID as defined in ERS (IETF RFC 4998 [2], appendix A). For the initial ArchiveTimeStampSequence the initial ArchiveTimeStamp shall contain the reducedHashtree field. The first component of the instance of PartialHashtree type shall contain in its object group at least the hash value of the ContentInfo instance of type signed-data and the hash value of the externally signed content. Illustration Figure 2 illustrates the external-evidence-records attribute. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 12 Figure 2: Illustration of external-evidence-records attribute ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 13
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
6 CAdES signature level including ERS
| |
06559e33e90280230a357784864e9b49
|
119 122-3
|
6.1 Overview
|
The present document specifies a new level for CAdES signatures including ERS. Each level is created by a combination of attributes defined in ETSI EN 319 122-1 [4] and the present document.
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
6.2 General requirements
|
The general CMS syntax shall be as specified in ETSI EN 319 122-1 [4], clause 4. The signature shall contain a CMS SignedData, as defined in ETSI EN 319 122-1 [4], clause 4.4 and at least one SignerInfo (ETSI EN 319 122-1 [4], clause 4.6). The algorithms and key lengths used to generate and augment digital signatures should be as specified in ETSI TS 119 312 [i.4]. NOTE: Cryptographic suites recommendations defined in ETSI TS 119 312 [i.4] can be superseded by national recommendations.
|
06559e33e90280230a357784864e9b49
|
119 122-3
|
6.3 CAdES-E-ERS
|
CAdES-E-ERS may be built on all the levels described in ETSI EN 319 122-1 [4] or ETSI EN 319 122-2 [i.3]. Table 1: Requirements for CAdES-E-ERS Signature fields/Attributes/Services Presence in E-ERS level Cardinality References Additional requirements and notes content-type shall be present 1 ETSI EN 319 122-1 [4], clause 5.1.1 message-digest shall be present 1 ETSI EN 319 122-1 [4], clause 5.1.2 Service: protection of signing certificate shall be provided 1 ETSI EN 319 122-1 [4], clause 5.2.2 SPO: ESS signing- certificate conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.2.2 a, e SPO: ESS signing- certificate-v2 conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.2.3 b, e signing-time may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.1 commitment-type-indication may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.3 content-hints may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.4.1 mime-type may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.4.2 signer-location may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.5 signer-attributes-v2 may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.6.1 countersignature may be present ≥ 0 ETSI EN 319 122-1 [4], clause 5.2.7 content-time-stamp may be present ≥ 0 ETSI EN 319 122-1 [4], clause 5.2.8 1 signature-policy-identifier may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.9.1 2, 3 signature-policy-store conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.10 c ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 14 Signature fields/Attributes/Services Presence in E-ERS level Cardinality References Additional requirements and notes content-reference may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.11 content-identifier may be present 0 or 1 ETSI EN 319 122-1 [4], clause 5.2.12 signature-time-stamp shall be present ≥ 1 ETSI EN 319 122-1 [4], clause 5.3 f, 1, 4 complete-certificate- references * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.1.1 e complete-revocation- references * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.2.1 attribute-certificate- references * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.3 d, e attribute-revocation- references * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.4 d CAdES-C-timestamp * ≥ 0 ETSI EN 319 122-1 [4], clause A.1.5.2 1 time-stamped-certs-crls- references * ≥ 0 ETSI EN 319 122-1 [4], clause A.1.5.1 1 Service: certificate values in long- term validation shall be provided ≥ 1 g, h SPO: SignedData.certificates conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 4.4 i SPO: certificate-values * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.1.2 Service: revocation values in long- term validation shall be provided 1 j,k SPO: SignedData.crls.crl conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 4.4 l SPO: SignedData.crls.other conditioned presence 0 or 1 ETSI EN 319 122-1 [4], clause 4.4 m SPO revocation-values * 0 or 1 ETSI EN 319 122-1 [4], clause A.1.2.2 archive-time-stamp-v3 * ≥ 0 ETSI EN 319 122-1 [4], clause 5.5.3 n Service: ERS inclusion shall be provided ≥ 1 Clause 5.1 o, p SPO: internal-evidence- records conditioned presence ≥ 0 Clause 5.2 q SPO external-evidence- records conditioned presence ≥ 0 Clause 5.3 r Additional requirements: a) Requirement for SPO: ESS signing-certificate. The ESS signing-certificate attribute shall be used if the SHA-1 hash algorithm is used. b) Requirement for SPO: ESS signing-certificate-v2. The ESS signing-certificate-v2 attribute shall be used when another hash algorithms than SHA-1 is used. c) Requirement for signature-policy-store. The signature-policy-store attribute may be incorporated in the CAdES signature only if the signature-policy-identifier attribute is also incorporated and it contains in sigPolicyHash the digest value of the signature policy document. Otherwise the signature-policy-store shall not be incorporated in the CAdES signature. d) Requirement for attribute-certificate-references. The attribute-certificate- references and attribute-revocation-references attributes may be used when at least a certified signer attribute (certifiedAttributesV2 as defined in clause 5.2.6.1 of ETSI EN 319 122-1 [4]) or a signed assertion (signedAssertions as defined in clause 5.2.6.1 of ETSI EN 319 122-1 [4]) is present within the signer attributes in the digital signature. Otherwise, attribute- certificate-references and attribute-revocation-references attributes shall not be used. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 15 e) Requirement for SPO: ESS signing-certificate, SPO: ESS signing-certificate-v2, complete-certificate-references, and attribute-certificate-references. The issuerSerial field should not be included in the encoding of the ESSCertID, ESSCertIDv2 or OtherCertID type. f) Requirement for signature-time-stamp. The time-stamp tokens encapsulated within the signature- time-stamp attributes shall be created before the signing certificate has been revoked or has expired. g) Requirement for Service: certificate values in long-term validation. The generator shall include the full set of certificates, including the trust anchors when they are available in the form of certificates that have been used to validate the signature. This set includes certificates required for validating the signing certificate, for validating any attribute certificate present in the signature, for validating revocation information (i.e. OCSP response and CRL) if certificates are not already included, and for validating any time-stamp token's signing certificate (i.e. a TSA certificate) already incorporated to the signature. h) Requirement for Service: certificate values in long-term validation. Duplication of certificate values within the signature should be avoided. i) Requirement for SPO: SignedData.certificates. If the certificate values in the long-term validation are not yet included elsewhere in the signature, they shall be included in SignedData.certificate, following the requirements in clause 5.5.3 of ETSI EN 319 122-1 [4]. j) Requirement for Service: revocation values in long-term validation. The generator shall include the full set of revocation data (CRL or OCSP responses) that have been used in the validation of the signature. This set includes all certificate status information required for validating the signing certificate, for validating any attribute certificate or signed assertion present in the signature, for validating revocation information (i.e. OCSP response and CRL) if they are not already included and for validating any time-stamp token's signing certificate (i.e. a TSA certificate) already incorporated to the signature. k) Requirement for Service: revocation values in long-term validation. Duplication of revocation values within the signature should be avoided. l) Requirement for SPO: SignedData.crls.crl. When the full set of revocation data contains CRLs and this information is not yet included otherwise in the signature, then the CRL values shall be included within SignedData.crls.crl. m) Requirement for SPO: SignedData.crls.other. When the full set of revocation data contains OCSP responses and this information is not yet included otherwise in the signature, then the OCSP response values shall be included within SignedData.crls.other. n) Requirement for archive-time-stamp-v3. Before generating and incorporating an archive-time- stamp-v3 attribute, all the validation material required for verifying the signature, which are not already in the signature, shall be included. This validation material includes validation material used to validate previous archive time stamp. o) Requirement for Service: ERS inclusion. Before generating and incorporating an evidence-records attribute, all the validation material required for verifying the signature, which are not already in the signature, shall be included. This validation material includes validation material used to validate previous archive time stamp. p) Requirement for Service: ERS inclusion. Only one evidence-records attribute should be included. q) Requirement for SPO: internal-evidence-records. In case a signature is attached, the internal- evidence-records attribute shall be used. r) Requirement for SPO: external-evidence-records. In case a signature is detached, the external- evidence-records attribute shall be used. NOTE 1: On content-time-stamp, signature-time-stamp, CAdES-C-timestamp, and time- stamped-certs-crls-references. Several instances of this attribute can occur in the digital signature, from different TSUs. NOTE 2: On signature-policy-identifier. The signature policy can establish specific requirements for other attributes. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 16 NOTE 3: On signature-policy-identifier. Further information on signature policies is provided in ETSI TS 119 172-1 [i.7]. NOTE 4: On signature-time-stamp. Trusted time indications provide the initial steps towards providing long-term validity. ETSI ETSI TS 119 122-3 V1.1.1 (2017-01) 17 History Document history V1.1.1 January 2017 Publication
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
1 Scope
|
The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in ETSI TS 118 101 [1], oneM2M TS-0004 [2], the bindings ETSI TS 118 108 [3], ETSI TS 118 109 [4] and ETSI TS 118 110 [5].
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
2 References
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
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 TS 118 101: "oneM2M; Functional ArchitectureFunctional Architecture (oneM2M TS-0001 Release 3)". [2] oneM2M TS-0004: "Service Layer Core protocol Specification - Release 3". [3] ETSI TS 118 108: "oneM2M; CoAP Protocol Binding (oneM2M TS-0008 Release 3)". [4] ETSI TS 118 109: "oneM2M; HTTP Protocol Binding (oneM2M TS-0009 Release 3)". [5] ETSI TS 118 110: "oneM2M; MQTT Protocol Binding (oneM2M TS-0010 Release 3)". [6] ETSI TS 118 115: "oneM2M; Testing Framework (oneM2M TS-0015)". [7] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)". [8] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [9] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". [10] ETSI TS 118 105: "oneM2M; Management Enablement (OMA) (oneM2M Release 3)". [11] ETSI TS 118 106: "oneM2M; Management Enablement (BBF) (oneM2M TS-0006 Release 3)". [12] ETSI TS 118 103: "oneM2M; Security solutions (oneM2M TS-0003 Release 3)". [13] oneM2M TS-0034: "Semantics Support - Release 3". [14] ETSI TS 118 123: "oneM2M; Home Appliances Information Model and Mapping (oneM2M TS-0023 Release 3)". [15] oneM2M TS-0026: "3GPP interworking - Release 4". [16] oneM2M TS-0040: "Modbus Interworking - Release 4". ETSI ETSI TS 118 113 V3.3.1 (2021-09) 11 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
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] oneM2M Drafting Rules. NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. [i.2] BBF TR-069: "CPE WAN Management Protocol".
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
3 Definitions of terms, symbols and abbreviations
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TS 118 111 [7] and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [7]. hosting CSE: CSE where the addressed resource is hosted M2M service provider domain: part of the M2M System that is associated with a specific M2M Service Provider mc: interface between the management server and the management client NOTE: This interface can be realized by the existing device management technologies such as BBF TR-069 [i.2], OMA DM [10], etc. receiver CSE: any CSE that receives a request registrar CSE: CSE where an Application or another CSE has registered registree: AE or CSE that registers with another CSE resource: uniquely addressable entity in oneM2M architecture transit CSE: any receiver CSE that is not a Hosting CSE
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
3.2 Symbols
|
Void.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy ACP-SD Access Control Policy-Semantic Descriptor ADN-AE AE which resides in the Application Dedicated Node AE Application Entity AE-ID Application Entity Identifier APP-ID Application Identifier BBF BroadBand Forum CFG Configuration CoAP Constrained Application Protocol ETSI ETSI TS 118 113 V3.3.1 (2021-09) 12 oneM2M TS-0013 version 3.3.1 Release 3 CP Communication Patterns CSE Common Services Entity CSE-ID Common Service Entity Identifier DAS Dynamic Authorization System DDN Downlink Data Notification DM Device Management DTLS Datagram Transport Layer Security DUT Device Under Test ECDHE Elliptic-curve Diffie–Hellman FQDN Fully Qualified Domain Name HAIM Home Appliances Information Model HSS Home Subscriber Serve HTTP HyperText Transfer Protocol IN Infrastructure Node IN-AE Application Entity that is registered with the CSE in the Infrastructure Node IN-CSE CSE which resides in the Infrastructure Node IOP Interoperability IP Internet Protocol IPE Interworking Proxy Entity JSON JavaScript Object Notation LWM2M Lightweight M2M M2M Machine to Machine MA Mandatory Announced MBMS Multimedia Broadcast Multicast Service Mca Reference Point for M2M Communication with AE Mcc Reference Point for M2M Communication with CSE MEF M2M Enrolment Function MH Multi Hop MNO Mobile Network Operator MO Management Object MQTT Message Queuing Telemetry Transport MT Mobile Terminated NB Non-Blocking NH No Hop NIDD non-IP Data Delivery NODN Non oneM2M Device Node OMA Open Mobile Alliance PDN Packet Data Network PRO Protocol PSK Pre-Shared Key PSM Power Savings Mode RDS Reliable Data Service RFC Request for Comments RP Reference Point RPC Remote Procedure Calls RQI Request-ID SCEF Service Capability Exposure Function SD Semantic Descriptor SE Security SGS Semantic Graph Store SH Single Hop SP Service Provider SPARQL SPARQL Protocol and RDF Query Language SUID Security Usage Identifier SUT System Under Test TCP Transmission Control Protocol TD Test Description TLS Transport Layer Security TMGI Temporary Mobile Group Identity TP Traffic Pattern UDP User Datagram Protocol URI Uniform Resource Identifier ETSI ETSI TS 118 113 V3.3.1 (2021-09) 13 oneM2M TS-0013 version 3.3.1 Release 3 XML eXtensible Markup Language
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
4 Conventions
|
The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1].
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5 Testing conventions
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.1 The Test Description proforma
|
The testing methodology used in the present document is specified in the ETSI TS 118 115 [6]. A Test Description (TD) is a well detailed description of a process that aims to test one or more functionalities of an implementation. Applying to interoperability testing, these testing objectives address the interoperable functionalities between two or more vendor implementations. In order to ensure the correct execution of an interoperability test, the following information should be provided by the test description: • The proper configuration of the vendor implementations. • The availability of additional equipment (protocol monitors, functional equipment, …) required to achieve the correct behaviour of the vendor implementations. • The correct initial conditions. • The correct sequence of the test events and test results. In order to facilitate the specification of test cases an interoperability test description should include, at a minimum, the following fields as indicated table 5.1-1. Table 5.1-1: Interoperability test description Identifier A unique test description ID. Objective A concise summary of the test which should reflect the purpose of the test and enable readers to easily distinguish this test from any other test in the document. References A list of references to the base specification section(s), use case(s), requirement(s) and Test Purposes which are either used in the test or define the functionality being tested. Applicability A list of features and capabilities which are required to be supported by the SUT in order to execute this test (e.g. if this list contains an optional feature to be supported, then the test is optional). Configuration or Architecture A list of all required equipment for testing and possibly also including a reference to an illustration of a test architecture or test configuration. Pre-Test Conditions A list of test specific pre-conditions that need to be met by the SUT including information about equipment configuration, i.e. precise description of the initial state of the SUT required to start executing the test sequence. Test Sequence An ordered list of equipment operation and observations. The test sequence may also contain the conformance checks as part of the observations. The test descriptions are provided in proforma tables. In order to ensure the correct execution of an interoperability test, the following information is provided in the test description: • The configuration applied for the test. • The need of additional equipment (protocol monitors, functional equipment, etc.) required to achieve the correct behaviour of the implementations. • The initial conditions. • The sequence of the test events and test results. ETSI ETSI TS 118 113 V3.3.1 (2021-09) 14 oneM2M TS-0013 version 3.3.1 Release 3 The following different types of test operator actions are considered during the test execution: • A stimulus corresponds to an event that enforces a DUT to proceed with a specific protocol action, such as sending a message. • A configure corresponds to an action to modify the DUT configuration. • An IOP check consists of observing that one DUT behaves as described in the standard: i.e. resource creation, update, deletion, etc. For each IOP check in the Test Sequence, a result can be recorded. The overall IOP Verdict will be considered OK if all the IOP checks in the sequence are OK. • In the context of Interoperability Testing with Conformance Checks, an additional step type, PRO checks can be used to verify the appropriate sequence and contents of protocol messages, this is helpful for debugging purposes. PRO Verdict will be PASS if all the PRO checks are PASS.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.2 Test Description naming convention
|
TD/<root>/<gr>/<nn> <root> = root M2M oneM2M <gr> = group NH No Hop: Testing on Mca reference point NB Non-Blocking scenario SH Single Hop: management of remote resources on Mca + Mcc MH Multi Hop SE Security <nn> = sequential number 01 to 99
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.3 Test Settings
|
This clause contains some test requirements applied to the testing, some constraints, restrictions for executions or some recommendations. In order to ease test setup and execution, the CSE and AE are requested to support the following settings: • Security shall be disable as it is out of scope of this interoperability testing. • Resource names are pre-provisioned, except for content instance resources that are automatically assigned by the hosting CSE. • After each "Delete" primitive on a resource, the user shall check the resource is effectively deleted. • Unless it is indicated in the test cases prerequisites, by default, all the applications shall have the required access rights to manage resources on the CSE. In order to address the TBDs in the oneM2M CoAP binding specification (ETSI TS 118 108 [3]), basic XML and JSON media-type numbers shall be used in the contentFormat option. In the test descriptions specified below, the following definitions of terms used for short-hand notation apply: Serialized Representation: refers to either an XML or a JSON representation of data in text-string format as defined in clauses 8.3 and 8.4 of oneM2M TS-0004 [2]. Host Address: refers to the authority part of a target URI as defined in IETF RFC 3986 [8] and IETF RFC 7230 [9] which can be represented as an IP literal encapsulated within square brackets, an IPv4 address in dotted decimal form, or a registered name, and optionally extended by a port identifier. ETSI ETSI TS 118 113 V3.3.1 (2021-09) 15 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4 Pre-conditions
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4.1 Registration
|
The AE or CSE that originates the request has been successfully registered to its corresponding CSE. The registration of the AE includes the creation of <AE> resource under the <CSEBase> of its registrar CSE. The registration of the CSE includes the creation of <remoteCSE> resource representing itself under the <CSEBase> of its registrar CSE as well as the creation of <remoteCSE> resource representing the registrar CSE under its own <CSEBase> resource. The creation of <remoteCSE> resource representing the registrar CSE can be achieved by remotely retrieving the <CSEBase> resource of the registrar CSE.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4.2 Security
|
The Originator and the receiver have successfully established security association between each other. This may involve the exchange of key and the establishment of a security connection. The security pre-condition also assumes that the originator has the appropriate access control privilege towards the requested resource.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4.3 Service Subscription
|
Service subscription means that the originator is allowed to be connected with the oneM2M system by contract between the owner of the application and the service provider of the oneM2M system. This may require a corresponding information record in the <m2mServiceSubscriptionProfile> resource.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4.4 ID allocation
|
ID allocation means that the Originator has already acquired usable identity, either from its registrar CSE or the IN-CSE of the oneM2M system. The ID may be CSE relative or SP relative. The ID is then further used as the identity of the Originator to perform access control, charging, etc.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.4.5 Existence of resource
|
Existence of resource means the resource been addressed and has already been created. 5.4.6 Management Session between Management Server and Management Client Before the device management using external technologies is executed, it is required that a management session has already been established between the Management Server and Management Client. If there is no existing management session, the IN-CSE shall request the establishment of a management session between the Management Server and Management Client.
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
5.5 Binding message convention
|
In HTTP/CoAP/MQTT binding messages, the present document defines the convention for <variable>: • <resourceType> represents a resource name (i.e. resourceName attribute) of a resource instance in that resourceType. For example, <CSEBase>/<AE> can represent "CSE1base/AE1" in structured resource ID format. • <parameter> represents a value of a oneM2M request/response parameter. For example, <Request ID> can represent "0001" value of the Request ID parameter. Parameter names are case sensitive and in long names as specified in oneM2M TS-0004 [2]. • <ID> represents an AE-ID or CSE-ID in MQTT Topic names. The value will be given at an interoperability test event. ETSI ETSI TS 118 113 V3.3.1 (2021-09) 16 oneM2M TS-0013 version 3.3.1 Release 3 In ETSI TS 118 110 [5], all oneM2M request/response parameters are carried in the MQTT message payload since it has no message header concept. Therefore, the MQTT message payload needs to be described more than HTTP and CoAP messages to describe those parameters in clause 8. In HTTP and CoAP binding messages, payloads are described as "empty" or "<container> resource to be created" in a very abstract way. Since the representation can be XML or JSON, payload should be abstract to support XML and JSON. The following example is an XML representation and its abstraction for creating a <container> resource. XML payload example for MQTT binding <?xml version="1.0" encoding="UTF-8"?> <m2m:req xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.onem2m.org/xml/protocols CDT-requestPrimitive- v1_0_0.xsd"> <op>1</op> <to>CSE1Base</to> <fr>/CSE1/C_AE1</fr> <rqi>2001</rqi> <ty>3</ty> <nm>cont1</nm> <rti><rt>3</rt></rti> <pc> <cnt> <lbl>SmartMeter</lbl> <et>20141003T112033</et> </cnt> </pc> </m2m:req> Abstracted payload example for MQTT binding op = 1 to = CSE1Base fr = /CSE1/C_AE01 rqi = 3001 ty = 3 name = cont1 rti.rt = 3 pc.cnt.lbl = SmartMeter pc.cnt.et = 20141003T112033 Abstracted payload example for MQTT binding adopting the payload convention op = 1 to = <CSEBase> fr = <From> rqi = <Request ID> ty = 3 name = <Name> rti.rt = 3 pc = <Content>
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
6 Test Description Summary
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
6.1 Tests list
|
Nb Category Procedure/Resource TD ID TD Description 1 Resource management Single Hop CSEBase Management TD_M2M_NH_01 AE retrieves the CSEBase resource 2 RemoteCSE TD_M2M_NH_02 Registree CSE registers to Registrar CSE 3 TD_M2M_NH_03 Registree CSE retrieves RemoteCSE from Registrar CSE 4 TD_M2M_NH_04 Registree CSE updates RemoteCSE from Registrar CSE 5 TD_M2M_NH_05 Registree CSE deletes RemoteCSE from Registrar CSE 6 Application Entity TD_M2M_NH_06 AE registers to its registrar CSE via an AE Create Request 7 TD_M2M_NH_07 AE retrieves <AE> resource via an AE Retrieve Request 8 TD_M2M_NH_08 AE updates attribute in <AE> resource via an AE Update Request 9 TD_M2M_NH_09 AE de-registers by deleting <AE> resource via an AE Delete Request 10 Container TD_M2M_NH_10 AE creates a container resource in registrar CSE via a container Create Request 11 TD_M2M_NH_11 AE retrieves information of a container resource via a container Retrieve Request ETSI ETSI TS 118 113 V3.3.1 (2021-09) 17 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 12 TD_M2M_NH_12 AE updates attribute in application resource via a container Update Request 13 TD_M2M_NH_13 AE deletes a specific container resource via a container Delete Request 14 ContentInstance TD_M2M_NH_14 AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the registrar CSE updates the parent <container> resource with stateTag, and currentNrOfInstances, CurrentByteSize attributes correspondingly 15 TD_M2M_NH_15 AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request 16 TD_M2M_NH_17 AE deletes contentInstance resource via a Delete Request and the registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attribute correspondingly 17 TD_M2M_NH_49 AE deletes a <latest> resource in a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> 18 TD_M2M_NH_50 AE deletes a <oldest> resource in a <container> resource and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> 19 TD_M2M_NH_51 AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource 20 TD_M2M_NH_102 AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' 21 TD_M2M_NH_71 AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> 22 TD_M2M_NH_72 AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> 23 Discovery TD_M2M_NH_18 AE discovers resources residing in Registrar CSE 24 TD_M2M_NH_19 AE discovers accessible resources residing in Registrar CSE using the label filter criteria 25 TD_M2M_NH_20 AE discovers accessible resources residing in Registrar CSE limiting the number of matching resources to the specified value 26 TD_M2M_NH_21 AE discovers accessible resources residing in Registrar CSE using multiple Filter Criteria 27 TD_M2M_NH_58 AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 1 28 TD_M2M_NH_59 AE discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 2 29 TD_M2M_NH_60 AE1 discovers accessible resources residing in Registrar CSE using the level filter criteria value set to 3 30 TD_M2M_NH_61 AE discovers accessible resources residing in Registrar CSE using the offset filter criteria value set to 3 31 TD_M2M_NH_62 AE discovers all the accessible resources residing in Registrar CSE using the offset filter criteria 32 Subscription TD_M2M_NH_22 AE creates a subscription to Application Entity resource via subscription Create Request 33 TD_M2M_NH_23 AE retrieves information about a subscription via subscription Retrieve Request such as expirationTime, labels, etc. 34 TD_M2M_NH_24 AE updates information about a subscription via subscription Retrieve Request 35 TD_M2M_NH_25 AE cancels subscription via an subscription Delete Request 36 AccessControlPolicy TD_M2M_NH_26 AE creates an accessControlPolicy resource 37 TD_M2M_NH_27 AE retrieves accessControlPolicy resource 38 TD_M2M_NH_28 AE updates attribute in accessControlPolicy resource ETSI ETSI TS 118 113 V3.3.1 (2021-09) 18 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 39 TD_M2M_NH_29 AE deletes accessControlPolicy resource 40 TD_M2M_NH_30 AE delete request is rejected due to accessControlPolicy 41 TD_M2M_NH_73 AE delete request is rejected due to accessControlPolicy (accessControlOriginators) 42 TD_M2M_NH_74 AE delete request is allowed due to accessControlPolicy 43 Group TD_M2M_NH_31 AE creates a group resource 44 TD_M2M_NH_32 AE retrieves group resource 45 TD_M2M_NH_33 AE updates attribute in group resource 46 TD_M2M_NH_34 AE deletes group resource 47 Node TD_M2M_NH_35 AE creates a node resource 48 TD_M2M_NH_36 AE retrieves node resource 49 TD_M2M_NH_37 AE updates attribute in node resource 50 TD_M2M_NH_38 AE deletes node resource 51 PollingChannel TD_M2M_NH_39 AE creates a <pollingChannel> resource in registrar CSE via a Create Request 52 TD_M2M_NH_40 AE retrieves information of a pollingChannel resource via a Retrieve Request 53 TD_M2M_NH_41 AE updates attribute in pollingChannel resource via a Update Request 54 TD_M2M_NH_42 AE deletes a pollingChannel resource via a Delete Request 55 TD_M2M_NH_43 AE retrieves information of a pollingChannel resource via a Retrieve Request 56 FanoutPoint TD_M2M_NH_44 AE creates a <contentInstance> resource in each group member 57 TD_M2M_NH_45 AE retrieves the <container> resource from in each group member 58 TD_M2M_NH_46 AE updates an <container> resource of each member resource 59 TD_M2M_NH_47 AE deletes a <container> of each member 60 Notification TD_M2M_NH_48 AE receives a notification request from the HOST CSE 61 TD_M2M_NH_80 AE2 sends maxNrOfInstances UPDATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has specific setting in eventNotificationCriteria, Hosting CSE send notification to AE1 62 TD_M2M_NH_81 AE2 sends DELETE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Resource', Hosting CSE send notification to AE1 63 TD_M2M_NH_82 AE2 sends <contentInstance> CREATE request to <container> which has been set to subscribed-to resource. Since <subscription> resource has notificationEventType with ''Create of Direct Child 'Resource', Hosting CSE send notification to AE1 64 TD_M2M_NH_83 AE2 sends DELETE request to the <contentInstance> which located under the subscribed-to resource. Since <subscription> resource has notificationEventType with 'Delete of Direct Child Resource', Hosting CSE send notification to AE1 65 TD_M2M_NH_89 AE creates <subscription> resources by sending Create Request to the fanOutPoint. Since AE has set notifyAggregation to 2, Hosting CSE aggregate notification and send aggregated notification to AE 66 FlexContainer TD_M2M_NH_52 AE creates a flexcontainer resource in Registrar CSE via a flexcontainer Create Request 67 TD_M2M_NH_53 AE retrieves information of a flexContainer resource via a flexContainer Retrieve Request 68 TD_M2M_NH_54 AE updates attribute in application resource via a flexContainer Update Request 69 TD_M2M_NH_55 AE deletes a specific container resource via a container Delete Request 70 TD_M2M_NH_56 AE receives a notification request on flexContainer update from the HOST CSE 71 TD_M2M_NH_57 AE discovers accessible resources residing in Registrar CSE using attribute filter criteria which has a customAttribute name and value assigned to it ETSI ETSI TS 118 113 V3.3.1 (2021-09) 19 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 72 External Management Operations TD_M2M_NH_63 AE creates a mgmtCmd resource 73 TD_M2M_NH_64 AE retrieves mgmtCmd resource 74 TD_M2M_NH_65 AE updates attribute (not with 'true' in execEnable attribute) in mgmtCmd resource 75 TD_M2M_NH_66 AE updates attribute (with 'true' in execEnable attribute) in mgmtCmd resource 76 TD_M2M_NH_67 AE deletes mgmtCmd resource 77 TD_M2M_NH_68 AE retrieves execInstance resource 78 TD_M2M_NH_69 AE updates attribute 'execDisable' to true in execInstance resource to cancel pending management command 79 TD_M2M_NH_70 AE deletes execInstance resource 80 SemanticDescriptor Management TD_M2M_NH_75 AE creates a SemanticDescriptor resource in Registrar CSE via a SemanticDescriptor Create Request 81 TD_M2M_NH_76 AE retrieves information of a semanticDescriptor resource via a semanticDescriptor Retrieve Request 82 TD_M2M_NH_77 AE updates attribute in <semanticDescriptor> resource via a semanticDescriptor Update Request 83 TD_M2M_NH_78 AE deletes SemanticDescriptor resource via a SemanticDescriptor Delete Request 84 Semantic Resource Discovery TD_M2M_NH_79 AE discovers accessible resources residing in Registrar CSE using the semanticFilter filter criteria 85 ResultContent TD_M2M_NH_84 Check creation of <container> resource with result content set to 0(nothing) 86 TD_M2M_NH_85 Check creation of <container> resource with result content set to 1(attributes) 87 TD_M2M_NH_86 Check creation of <container> resource with result content set to 2(hierarchical address) 88 TD_M2M_NH_87 Check creation of <container> resource with result content set to 3(hierarchical address and attributes) 89 TD_M2M_NH_88 Check retrievability of <container> resource with result content set to 4(attributes and child resources) 90 timeSeries TD_M2M_NH_90 AE creates a <timeSeries> resource in registrar CSE via a Create Request 91 TD_M2M_NH_91 AE retrieves information of a <timeSeries> resource via a Retrieve Request 92 TD_M2M_NH_92 AE updates attribute in <timeSeries> resource via a Update Request 93 TD_M2M_NH_93 AE deletes a <timeSeries> resource via a Delete Request 94 timeSeriesInstance TD_M2M_NH_94 AE sends Create Request of a <timeSeriesInstance> resource to a <timeSeries> resource in Registrar CSE. Registrar CSE creates the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly 95 TD_M2M_NH_95 AE retrieves information of a <timeSeriesInstance> resource via a Retrieve Request 96 TD_M2M_NH_96 AE sends Delete Request of a <timeSeriesInstance> resource in Registrar CSE. Registrar CSE delete the <timeSeriesInstance> resource and updates the parent <timeSeries> resource with currentNrOfInstances and currentByteSize attributes correspondingly 97 TD_M2M_NH_97 AE sends a <timeSeriesInstance> resource Create Request to a <timeSeries> resource which contains currentNrOfInstances value equals to that of maxNrOfInstances and Registrar CSE delets the oldest <timeSeriesInstance> resource from the <timeSeries> resource and then creates the requested <timeSeriesInstance> resource 98 LocationPolicy TD_M2M_NH_98 AE creates a <locationPolicy> resource in registrar CSE via a locationPolicy Create Request 99 TD_M2M_NH_99 AE retrieves information of a <locationPolicy> resource via a locationPolicy Retrieve Request 100 TD_M2M_NH_100 AE updates attribute in <locationPolicy> resource via a locationPolicy Update Request 101 TD_M2M_NH_101 AE deletes a specific <locationPolicy> resource via a locationPolicy Delete Request ETSI ETSI TS 118 113 V3.3.1 (2021-09) 20 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 102 Schedule TD_M2M_NH_155 AE creates a <schedule> resource in Registrar CSE via a Schedule Create Request 103 TD_M2M_NH_156 AE retrieves information of a <schedule> resource via a schedule Retrieve Request 104 TD_M2M_NH_157 AE updates attribute in <schedule> resource via a schedule Update Request 105 TD_M2M_NH_158 AE deletes Schedule resource via a Schedule Delete Request 106 TD_M2M_NH_159 CSE sends a notification request to the AE when Schedule resource is configured 107 Non-Blocking Synchronous request TD_M2M_NB_01 AE creates a container resource using non-blocking synchronous request in registrar CSE 108 TD_M2M_NB_02 AE retrieves a Container resource using non-blocking synchronous request in registrar CSE 109 TD_M2M_NB_03 AE updates a Container resource using non-blocking synchronous request in registrar CSE 110 TD_M2M_NB_04 AE deletes a Container resource using non-blocking synchronous request 111 Asynchronous request TD_M2M_NB_05 AE creates a container resource using non-blocking asynchronous request 112 TD_M2M_NB_06 AE retrieves a Container resource using non-blocking asynchronous request 113 TD_M2M_NB_07 AE updates a Container resource using non-blocking asynchronous request 114 TD_M2M_NB_08 AE deletes a Container resource using non-blocking asynchronous request 115 Single Hop Retargeting TD_M2M_SH_01 AE creates a remote <Resource> resource 116 TD_M2M_SH_02 AE retrieves a remote <Resource> resource 117 TD_M2M_SH_03 AE updates a remote <Resource> resource 118 TD_M2M_SH_04 AE delete a remote <Resource> resource 119 Discovery TD_M2M_SH_09 AE discovers accessible resources residing in the remote Hosting CSE using multiple Filter Criteria 120 Unauthorized operation TD_M2M_SH_10 AE delete request is rejected after access rights verification using retargeting 121 Notification TD_M2M_SH_11 AE receives a notification request from the remote hosting CSE 122 mgmtObj TD_M2M_SH_05 AE creates a <mgmtObj> resource 123 TD_M2M_SH_06 AE updates a <mgmtObj> resource 124 TD_M2M_SH_07 AE retrieves a <mgmtObj> resource 125 TD_M2M_SH_08 AE deletes a <mgmtObj> resource 126 Announcement TD_M2M_SH_12 AE1 announces itself to CSE2 127 TD_M2M_SH_13 AE1 announces a child container to CSE2 128 TD_M2M_SH_14 AE1 announces an Optional Announce attribute to CSE2 129 TD_M2M_SH_15 AE2 retrieves an Announced Resource 130 TD_M2M_SH_16 AE2 retrieves the original resource representation of an announced resource 131 TD_M2M_SH_21 ContainerAnnc Delete by updating announceTo attribute. AE1 deletes its announced child container from CSE2 132 TD_M2M_SH_22 ContainerAnnc Delete by deleting original resource. AE1 deletes its announced child container from CSE2 133 TD_M2M_SH_23 Announced attribute Create by addition to announcedAttribute attribute AE1 announces an announcable attribute of its child container to CSE2 134 TD_M2M_SH_24 Announced attribute Create by creation of a MA attribute at the original resource. AE1 announces an MA attribute of its child container to CSE2 135 TD_M2M_SH_25 Announced attribute Delete by deletion from announcedAttribute attribute. AE1 de-announces an announcable attribute of its child container to CSE2 136 TD_M2M_SH_26 Announced attribute Delete by deletion of a MA attribute at the original resource. AE1 de-announces an MA attribute (conditionally mandatory) of its child container to CSE2 137 fanOut TD_M2M_SH_17 AE creates a <contentInstance> resource in each group member, where some memberIDs are on a remoteCSE ETSI ETSI TS 118 113 V3.3.1 (2021-09) 21 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 138 TD_M2M_SH_18 AE retrieves a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE 139 TD_M2M_SH_19 AE updates a <container> resource in each group member, where some memberIDs are on a remoteCSE 140 TD_M2M_SH_20 AE deletes a <contentInstance> resource from each group member, where some memberIDs are on a remoteCSE 141 Security Secure AE Registration TD_M2M_SE_01 AE uses Provisioned Symmetric Key Security Association Establishment Framework to enable mutual authentication with the Registrar CSE. Registrar CSE performs AE authorization check on incoming AE registration request 142 Authentication TD_M2M_SE_02 AE establishes mutual authentication with the Registrar CSE using Provisioned Symmetric Key Security Association Establishment Framework 143 TD_M2M_SE_03 AE establishes mutual authentication with the Registrar CSE using Certificate-Based Security Association Establishment Framework 144 Authorization TD_M2M_SE_04 AE accesses <accessControlPolicy> resource using its selfPrivileges credentials 145 TD_M2M_SE_05 AE accesses <AE> resource using its accessControlPolicyIDs attribute 146 TD_M2M_SE_06 AE accesses <AE> resource using default access privileges 147 TD_M2M_SE_07 AE accesses <AE> resource using default access privileges 148 TD_M2M_SE_08 AE accesses <AE> resource using Direct Dynamic Authorization 149 TD_M2M_SE_09 AE accesses <AE> resource using Indirect Dynamic Authorization 150 Key provisioning management TD_M2M_SE_10 A MEF Handshake procedure establishes a mutually authenticated TLS session for protecting the communication between an MEF Client and MEF using pre-provisioned certificates 151 TD_M2M_SE_11 A MEF Handshake procedure establishes a mutually authenticated TLS or DTLS session for protecting the communication between an MEF Client and MEF using pre-provisioned Master Credentials 152 TD_M2M_SE_12 The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder 153 TD_M2M_SE_13 The MEF Client retrieves MEF Client Configurations provided by the administrating stakeholder to the MEF 154 TD_M2M_SE_14 MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels 155 TD_M2M_SE_15 The MEF Client registers with the MEF to confirm that it is willing to use the services of the MEF, under the authorization of the administrating stakeholder 156 TD_M2M_SE_16 Source MEF Client establishes a symmetric key with the MEF which can be retrieved for use by one or more Target MEF Clients 157 TD_M2M_SE_17 The Target MEF Client to retrieve the Key Value from a MEF corresponding to a RelativeKeyID received by the Target MEF Client 158 TD_M2M_SE_18 MEF Client updates the MEF Client registration by any combination of extending the expirationTime of the MEF Client Registration record or updating the labels 159 TD_M2M_SE_19 Source MEF Client requests the MEF to stop distributing the registered key 160 End-to-End security management TD_M2M_SE_20 AE sends an arbitrary request primitive inside of ESPrim Object to CSE 161 TD_M2M_SE_21 AE establishes a connection with the Registrar CSE using pairwiseE2EKey 163 HAIM HAIM Device Model TD_M2M_NH_102 AE1 creates a HAIM Light Device Model 164 TD_M2M_NH_103 AE2 reads the status of a HAIM Light Device Model 165 TD_M2M_NH_104 AE2 turns the binarySwitch of a HAIM Light Device Model "ON" or "OFF" 166 TD_M2M_NH_105 AE2 toggles the state of a HAIM Light Device Model 167 TD_M2M_NH_160 AE1 creates a Power Outlet SubDevice Model 168 TD_M2M_NH_161 AE1 creates a Toggle Action Model 169 TD_M2M_NH_162 AE1 creates Device Properties Model ETSI ETSI TS 118 113 V3.3.1 (2021-09) 22 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 170 Semantics Semantic Access Control Policy TD_M2M_NH_106 ACP triples are created when a new <accessControlPolicy> resource is created 171 TD_M2M_NH_107 ACP triples are updated when an existing <accessControlPolicy> resource is updated 172 TD_M2M_NH_108 ACP triples are deleted when an existing <accessControlPolicy> resource is deleted 173 TD_M2M_NH_109 ACP-SD Binding Triples and SD relationship in SGS are created when AE creates a <semanticDescriptor> resource in Registrar CSE 174 TD_M2M_NH_110 ACP-SD Binding Triples are updated when the accessControlPolicyIDs attribute of a <semanticDescriptor> resource is updated 175 TD_M2M_NH_111 SD Relationship Triples are updated when the descriptor attribute of a <semanticDescriptor> resource is changed 176 TD_M2M_NH_112 SD Relationship Triples are deleted when the descriptor attribute of a <semanticDescriptor> resource is deleted 177 Semantic Filtering and discovery TD_M2M_NH_113 AE discovers accessible resources residing in Registrar CSE using the <semanticFanOutPoint> 178 TD_M2M_NH_114 AE discovers accessible resources residing in Registrar CSE using the resource link-based Semantic Discovery 179 TD_M2M_NH_115 AE performs a Semantic Query request in Registrar CSE using the semanticFilter filter criteria 180 Semantic Mashup TD_M2M_NH_116 AE creates a SemanticMashupJobProfile resource in Registrar CSE via a SemanticMashupJobProfile Create Request 181 TD_M2M_NH_117 AE retrieves information of a semanticMashupJobProfile resource via a semanticMashupJobProfile Retrieve Request 182 TD_M2M_NH_118 AE updates attribute in <semanticMashupJobProfile> resource via a semanticMashupJobProfile Update Request 183 TD_M2M_NH_119 AE deletes semanticMashupJobProfile resource via a semanticMashupJobProfile Delete Request 184 TD_M2M_NH_120 AE creates a semanticMashupInstance resource in Registrar CSE via a semanticMashupInstance Create Request 185 TD_M2M_NH_121 AE retrieves information of a semanticMashupInstance resource via a semanticMashupInstance Retrieve Request 186 TD_M2M_NH_122 AE updates attribute in <semanticMashupInstance> resource via a semanticMashupInstance Update Request 187 TD_M2M_NH_123 AE deletes semanticMashupInstance resource via a semanticMashupInstance Delete Request 188 TD_M2M_NH_124 AE retrieves information of a semanticMashupResult resource via a semanticMashupResult Retrieve Request 189 TD_M2M_NH_125 AE deletes semanticMashupResult resource via a semanticMashupResult Delete Request 190 TD_M2M_NH_126 AE triggers a calculation and generation of the mashup result by sending a <semanticMashupInstance>/<mashup> Retrieve Request 191 Ontology Repository TD_M2M_NH_127 AE creates a OntologyRepository resource in Registrar CSE via a OntologyRepository Create Request 192 TD_M2M_NH_128 AE retrieves information of a ontologyRepository resource via a ontologyRepository Retrieve Request 193 TD_M2M_NH_129 AE updates attribute in <ontologyRepository> resource via a ontologyRepository Update Request 194 TD_M2M_NH_130 AE deletes OntologyRepository resource via a OntologyRepository Delete Request 195 Semantic validation TD_M2M_NH_131 AE checks the validity of the <semanticDescriptor> resource via a <semanticValidation> Update Request 196 TD_M2M_NH_132 AE creates a <semanticDescriptor> resource visa SemanticDescriptor Create Request and Registrar CSE checks the validity of the created <semanticDescriptor> resource 197 Ontology Mapping TD_M2M_NH_133 AE creates an OntologyMapping resource in Registrar CSE via an OntologyMapping Create Request 198 TD_M2M_NH_134 AE retrieves information of an ontology mapping result via a ontologyMapping Retrieve Request 199 TD_M2M_NH_135 AE updates attribute in <ontologyMapping> resource via a ontologyMapping Update Request 200 TD_M2M_NH_136 AE deletes OntologyMapping resource via a OntologyMapping Delete Request ETSI ETSI TS 118 113 V3.3.1 (2021-09) 23 oneM2M TS-0013 version 3.3.1 Release 3 Nb Category Procedure/Resource TD ID TD Description 201 3GPP Interworking Cellular IoT non-IP data delivery (NIDD) TD_M2M_SH_27 IN-CSE establishes SCEF Configuration for NIDD 202 TD_M2M_SH_28 IN-AE sends a downlink non-IP data to a UE hosting ADN-AE 203 TD_M2M_SH_29 IN-AE sends a downlink non-IP data to a UE hosting ADN-AE 204 Monitoring events TD_M2M_SH_30 IN-AE monitors UE Reachability status 205 TD_M2M_SH_31 UE Availability after DDN Failure scenario 206 TD_M2M_SH_32 UE Communication Failure scenario 207 TD_M2M_SH_33 Roaming status scenario 208 TD_M2M_SH_34 Location Reporting scenario 209 3GPP Based Device triggering TD_M2M_SH_35 IN-AE triggers ADN-AE hosted on UE 210 TD_M2M_SH_36 IN-AE recalls/replaces a trigger request targeting ADN-AE hosted on UE that has been already created in IN-CSE 211 Configuration of traffic patterns TD_M2M_SH_37 IN-CSE translates the oneM2M Node Traffic Pattern (TP) into a 3GPP Device Communication Pattern 212 Group message delivery using MBMS TD_M2M_SH_38 IN-AE creates a MBMS Group for handling group related requests 213 TD_M2M_SH_39 IN-AE sends a request for accessing member resources to the Group Hosting CSE 214 Advanced Subscriptions & Notifications Notification Target removal TD_M2M_NH_137 AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request 215 NotificationTargetMgm tPolicyRef TD_M2M_NH_138 AE creates a notificationTargetMgmtPolicyRef resource in registrar CSE via a notificationTargetMgmtPolicyRef Create Request 216 TD_M2M_NH_139 AE retrieves notificationTargetMgmtPolicyRef resource from Registrar CSE 217 TD_M2M_NH_140 AE updates information about a notificationTargetMgmtPolicyRef via notificationTargetMgmtPolicyRef>Update Request 218 TD_M2M_NH_141 AE removes notificationTargetMgmtPolicyRef via a notificationTargetMgmtPolicyRef Delete Request 219 NotificationTargetPolic y TD_M2M_NH_142 AE creates a notificationTargetPolicy resource in registrar CSE via a notificationTargetPolicy Create Request 220 TD_M2M_NH_143 AE retrieves notificationTargetPolicy resource from Registrar CSE 221 TD_M2M_NH_144 AE updates information about a notificationTargetPolicy via <notificationTargetPolicy> Update Request 222 TD_M2M_NH_145 AE removes notificationTargetPolicy via a <notificationTargetPolicy> Delete Request 223 PolicyDeletionRules TD_M2M_NH_146 AE creates a policyDeletionRules resource in registrar CSE via a policyDeletionRules Create Request 224 TD_M2M_NH_147 AE retrieves policyDeletionRules resource from Registrar CSE 225 TD_M2M_NH_148 AE updates information about a policyDeletionRules via <policyDeletionRules> Update Request 226 TD_M2M_NH_149 AE removes policyDeletionRules via a <policyDeletionRules> Delete Request 227 CrossResourceSubscr iption TD_M2M_NH_150 AE creates a crossResourceSubscription resource in registrar CSE via a crossResourceSubscription Create Request 228 TD_M2M_NH_151 AE retrieves crossResourceSubscription resource from Registrar CSE 229 TD_M2M_NH_152 AE updates information about a crossResourceSubscription via <crossResourceSubscription> Update Request 230 TD_M2M_NH_153 AE removes crossResourceSubscription via a <crossResourceSubscription> Delete Request 231 TD_M2M_NH_154 AE receives a notification request from the HOST CSE 232 Modbus Interworking Modbus Thermometer device TD_M2M_NH_163 AE1 creates Device Model for Modbus device 233 TD_M2M_NH_164 Modbus IPE reads data from Modbus device and updates Registrar CSE with the read data 234 TD_M2M_NH_165 AE writes data into a Modbus device by updating <flexContainer> resource in Registrar CSE 235 NoDN Interworking Generic IPE TD_M2M_NH_166 NoDN IPE reads data from a NoDN device and updates Registrar CSE with the read data 236 TD_M2M_NH_167 AE writes data into a NoDN device by updating <flexContainer> resource in Registrar CSE ETSI ETSI TS 118 113 V3.3.1 (2021-09) 24 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7 Configuration
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1 Test Configuration
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.1 No hop
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.1.1 M2M_CFG_01
|
The AE manages resources on the registrar CSE (Hosting CSE). oneM2M entities model AE Registrar-CSE Mca Figure 7.1.1.1-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.1.2 M2M_CFG_02
|
oneM2M entities model Registree-CSE Registrar-CSE Mcc Figure 7.1.1.2-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.1.3 M2M_CFG_10
|
oneM2M entities model AE1 Registrar-CSE Mca AE2 Mca Figure 7.1.1.3-1 NOTE: For HAIM Model tests, clause 8.5, AE1 represents a native oneM2M device that implements the HAIM models or a combined IPE(AE) plus a non-oneM2M device node (nodn).
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2 Single hop
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.1 M2M_CFG_03
|
The AE manages resources on the remote CSE. oneM2M entities model AE Registrar-CSE Mca Hosting-CSE Mcc Figure 7.1.2.1-1 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 25 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.2 M2M_CFG_04
|
oneM2M entities model AE1 CSE1 Mca CSE2 Mcc AE2 Mca Figure 7.1.2.2-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.3 M2M_CFG_05
|
oneM2M entities model Registrar-CSE Transit-CSE Mcc Hosting-CSE Mcc Figure 7.1.2.3-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.4 M2M_CFG_08
|
This configuration concerns group management when the AE is using a group to fan out requests to multiple members. The connection between the AE and the Group Hosting CSE, the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. This configuration is mapped to cases including: • AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE. • The Member Hosting CSE sends a notification to the Group Hosting CSE pertaining to the subscription made through the Group Hosting CSE. The Group Hosting CSE then further aggregates the notification and sends it back to the AE. AE Group Hosting CSE Mca Member Hosting CSE Mcc Figure 7.1.2.4-1 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 26 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.5 M2M_CFG_09
|
This configuration concerns device management using external technologies. This configuration is mapped to cases including: • The AE sends a request addressing <mgmtObj> to IN-CSE. IN-CSE then further acts as a Management Server to send management commands to Managed Entity over the mc interface. The management command is defined in OMA DM, BBF TR069 or LWM2M. AE IN-CSE Management Server Mca Managed Entity Management Client mc Figure 7.1.2.5-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.6 M2M_CFG_11
|
This configuration concerns device management using 3GPP network. SCEF IN-CSE Mcn (T8) IN-AE Mca ADN-AE Mca
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.2.7 M2M_CFG_12
|
This configuration concerns group management when the IN-AE is using a group to fan out requests to multiple members in 3GPP interworking scenraios. The connection between the IN-AE and the Group Hosting CSE, the Group Hosting CSE and the Member Hosting CSE may be a multi hop connection following the definition in clause 7.1.3. This configuration is mapped to cases including: • IN-AE sends a request addressing <group>/fanOutPoint in the Group Hosting CSE, the Group Hosting CSE then further fans out the request to each Member Hosting CSE through 3GPP network. ETSI ETSI TS 118 113 V3.3.1 (2021-09) 27 oneM2M TS-0013 version 3.3.1 Release 3 SCEF Group Hosting CSE Mcn (T8) IN-AE Mca Member Hosting CSE Mcc
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.3 Multi hops
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.3.1 M2M_CFG_06
|
oneM2M entities model Registrar-CSE Transit-CSE Mcc Hosting-CSE Mcc AE1 Mca Figure 7.1.3.1-1
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
7.1.3.2 M2M_CFG_07
|
oneM2M entities model Registrar-CSE Transit-CSE Mcc Hosting-CSE Mcc AE1 Mca AE2 Mca Figure 7.1.3.2-1 ETSI ETSI TS 118 113 V3.3.1 (2021-09) 28 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8 Test Descriptions
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1 No Hop configuration testing
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.1 CSEBase Management
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.1.1 CSEBase Retrieve on Mca
|
Interoperability Test Description Identifier: TD_M2M_NH_01 Objective: AE retrieves the CSEBase resource Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.2.11 oneM2M TS-0004 [2], clause 7.3.2 Pre-test conditions: • CSEBase resource has been automatically created in CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a retrieve Request to CSE with name {CSEBaseName} 2 Mca PRO Check Primitive • Operation (op) = 2 (Retrieve) • To (to) = Resource-ID of requested <CSEBase> resource, assumed CSE- relative here • From (from) = AE-ID of request originator • Request Identifier (rqi) = (token-string) 3 Mca PRO Check Primitive • Response Status Code (rsc) = 2000 (OK) • Request Identifier (rqi) = same string as received in request message • Content (pc) = Serialized Representation of <CSEBase> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.2 RemoteCSE Management
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.2.1 RemoteCSE Create
|
Interoperability Test Description Identifier: TD_M2M_NH_02 Objective: Registree CSE registers to Registrar CSE Configuration: M2M_CFG_02 References: ETSI TS 118 101 [1], clause 8.1.2.1 oneM2M TS-0004 [2], clause 7.3.3.2.1 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} Test Sequence Step RP Type Description 1 Stimulus Registree CSE is requested to send a RemoteCSE Create request to Registrar CSE 2 Mcc PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = Registree CSE-ID • rqi = (token-string) • ty = 16 (RemoteCSE) • pc = Serialized representation of <RemoteCSE> resource 3 Mcc PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <RemoteCSE> resource 4 IOP Check Check if possible that the <remoteCSE> resource has been created in registrar CSE 5 IOP Check Check if possible that the corresponding <remoteCSE> resource has been also created in registree CSE ETSI ETSI TS 118 113 V3.3.1 (2021-09) 29 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 6 IOP Check Registree CSE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.2.2 remoteCSE Retrieve
|
Interoperability Test Description Identifier: TD_M2M_NH_03 Objective: Registree CSE retrieves RemoteCSE from Registrar CSE Configuration: M2M_CFG_02 References: ETSI TS 118 101 [1], clause 8.1.2.2 oneM2M TS-0004 [2], clause 7.3.3.2.2 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} Test Sequence Step RP Type Description 1 Stimulus Registree CSE is requested to send a RemoteCSE retrieve request to Registrar CSE 2 Mcc PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/{remoteCSEName} • fr = Registree CSE-ID • rqi = (token-string) • pc = empty 3 Mcc PRO Check Primitive Registrar CSE sends response containing: • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <RemoteCSE> resource 4 IOP Check Registree CSE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.2.3 remoteCSE Update
|
Interoperability Test Description Identifier: TD_M2M_NH_04 Objective: Registree CSE updates RemoteCSE from Registrar CSE Configuration: M2M_CFG_02 References: ETSI TS 118 101 [1], clause 8.1.2.3 oneM2M TS-0004 [2], clause 7.3.3.2.3 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} Test Sequence Step RP Type Description 1 Stimulus Registree CSE is requested to send a RemoteCSE update request to Registrar CSE 2 Mcc PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/{remoteCSEName} • fr = Registree CSE-ID • rqi = (token-string) • pc = Serialized representation of updated <RemoteCSE> resource 3 IOP Check Check if possible that the <remoteCSE> resource has been updated in registrar CSE 4 Mcc PRO Check Primitive Registrar CSE sends response containing: • rsc = 2004 (UPDATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <RemoteCSE> resource 5 IOP Check Registree CSE indicates successful operation ETSI ETSI TS 118 113 V3.3.1 (2021-09) 30 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.2.4 remoteCSE Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_05 Objective: Registree CSE deletes RemoteCSE from Registrar CSE Configuration: M2M_CFG_02 References: ETSI TS 118 101 [1], clause 8.1.2.4 oneM2M TS-0004 [2], clause 7.3.3.2.4 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • Registree CSE has created a remoteCSE resource on registrar CSE with name {RemoteCSEName} Test Sequence Step RP Type Description 1 Stimulus Registree CSE is requested to send a RemoteCSE delete request to Registrar CSE 2 Mcc PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/{remoteCSEName} • fr = Registree CSE-ID • rqi = (token-string) • pc = empty 3 Mcc PRO Check Primitive Registrar CSE sends response containing: • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = empty 4 IOP Check Check if possible that the <remoteCSE> resource has been removed from registrar CSE 5 IOP Check Check if possible that the <remoteCSE> resource is also removed from registree CSE 6 IOP Check Registree CSE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.3 Application Entity Registration
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.3.1 AE Create
|
Interoperability Test Description Identifier: TD_M2M_NH_06 Objective: AE registers to its registrar CSE via an AE Create Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.2.2 oneM2M TS-0004 [2], clause 7.4.5.2.1 Pre-test conditions: • CSEBase resource has been created in CSE with name {CSEBaseName} • AE does not have an AE-ID, i.e. it registers from scratch Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a AE Create request to register to the Registrar CSE 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • ty = 2 (AE) • pc = Serialized representation of <AE> resource 3 IOP Check Check if possible that the <AE> resource is created in registrar CSE 4 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <AE> resource 5 IOP Check AE indicates successful operation ETSI ETSI TS 118 113 V3.3.1 (2021-09) 31 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.3.2 AE Retrieve
|
Interoperability Test Description Identifier: TD_M2M_NH_07 Objective: AE retrieves <AE> resource via an AE Retrieve Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.2.3 oneM2M TS-0004 [2], clause 7.4.5.2.2 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created a <AE> resource on registrar CSE with name {AE}bgf Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a AE retrieve request to Registrar CSE 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/{AE} • fr = AE-ID of request originator • rqi = (token-string) 3 Mca PRO Check Primitive Registrar CSE sends response containing: • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <AE> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.3.3 AE Update
|
Interoperability Test Description Identifier: TD_M2M_NH_08 Objective: AE updates attribute in <AE> resource Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.2.4 oneM2M TS-0004 [2], clause 7.4.5.2.3 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created a <AE> resource on registrar CSE with name {AE} Test Sequence Step RP Type Description 1 Stimulus AE is requested to send an AE Update Request 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/{AE} • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <AE> resource 3 IOP Check Check if possible that the <AE> resource has been updated in registrar CSE 4 Mca PRO Check Primitive Registrar CSE sends response containing: • rsc = 2004 (UPDATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <AE> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 32 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.3.4 AE Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_09 Objective: AE de-registers by deleting <AE> resource via an AE Delete Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.2.5 oneM2M TS-0004 [2], clause 7.4.5.2.4 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • AE has created a <AE> resource on registrar CSE with name {AE} Test Sequence Step RP Type Description 1 Stimulus AE is requested to send an AE Delete Request 2 Mca PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/{AE} • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive Registrar CSE sends response containing: • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = empty 4 IOP Check Check if possible that the <AE> resource has been removed from registrar CSE 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.4 Container Management
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.4.1 Container Create
|
Interoperability Test Description Identifier: TD_M2M_NH_10 Objective: AE creates a container resource in registrar CSE via a container Create Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.3 oneM2M TS-0004 [2], clause 7.4.6.2.1 Pre-test conditions: • AE has created an application resource <AE> on registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a request to create a <container> 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <AE> resource • fr = AE-ID • rqi = (token-string) • ty = 3 (Container) • pc = Serialized representation of <container> resource 3 IOP Check Check if possible that the <container> resource is created in registrar CSE 4 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <container> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 33 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.4.2 Container Retrieve
|
Interoperability Test Description Identifier: TD_M2M_NH_11 Objective: AE retrieves information of a container resource via a container Retrieve Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.4 oneM2M TS-0004 [2], clause 7.4.6.2.2 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <container> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <container> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <container> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.4.3 Container Update
|
Interoperability Test Description Identifier: TD_M2M_NH_12 Objective: AE updates attribute in application resource via a container Update Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.5 oneM2M TS-0004 [2], clause 7.4.6.2.3 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a container Update Request to update the lifetime of the resource 2 Mca PRO Check Primitive • op = 3 (Update) • to = {CSEBaseName}/URI of <container> resource • fr = AE-ID • rqi = (token-string) • pc = Serialized representation of updated <container> resource 3 IOP Check Check if possible that the < container > resource is updated in Registrar CSE 4 Mca PRO Check Primitive • rsc = 2004 (Updated) • rqi = (token-string) same as received in request message • pc = Serialized representation of <container> resource 5 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 34 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.4.4 Container Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_13 Objective: AE deletes a specific container resource via a container Delete Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.6 oneM2M TS-0004 [2], clause 7.4.6.2.4 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a container Delete Request 2 Mca PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/URI of <container> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 IOP Check Check if possible that the <container> resource is deleted in registrar CSE 4 Mca PRO Check Primitive • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = empty 5 IOP Check Check if possible that the <container> resource has been removed in registrar CSE 6 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5 ContentInstance Management
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.1 ContentInstance Create
|
Interoperability Test Description Identifier: TD_M2M_NH_14 Objective: AE adds a contentInstance resource <contentInstance> to a specific container in Registrar CSE via a contentInstance Create Request and the Registrar CSE updates the parent <container> resource with stateTag, currentNrOfInstances, and CurrentByteSize attributes correspondingly Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.7 oneM2M TS-0004 [2], clause 7.4.7.1.1 Pre-test conditions: • AE has created an application resource <AE> on registrar CSE • AE has created a container resource <container> on registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE sends a request to create a < contentInstance > resource 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of < container > resource • fr = AE-ID • rqi = (token-string) • ty = 4 (contentInstance) • pc = Serialized representation of <contentInstance> resource 3 IOP Check Check if possible that the <contentInstance> resource is created in Registrar CSE and AE sends a RETRIEVE request to the <container> resource to check that if the Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful creation of child <contentInstance> resource 4 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <contentInstance> resource ETSI ETSI TS 118 113 V3.3.1 (2021-09) 35 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 5 IOP Check AE indicates successful CREATE operation of <contentInstance> and indicates Registrar CSE has updated stateTag, currentNrOfInstances, and CurrentByteSize attribute correspondingly by checking the response of a <container> request to the <container> resource IOP Verdict Set verdict to pass if IOP check goal is achieved exactly, otherwise verdict fail is set with corresponding error message PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.2 ContentInstance Retrieve
|
Interoperability Test Description Identifier: TD_M2M_NH_15 Objective: AE retrieves information of a contentInstance resource via a contentInstance Retrieve Request Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.8 oneM2M TS-0004 [2], clause 7.4.7.2.2 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created a contentInstance resource <contentInstance> as child resource of <container> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <contentInstance> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <contentInstance> resource • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of <contentInstance> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.3 ContentInstance Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_17 Objective: AE deletes contentInstance resource via a contentInstance Delete Request and the Registrar CSE updates the parent <container> resource with currentNrOfInstances, and CurrentByteSize attributes correspondingly Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.10 oneM2M TS-0004 [2], clause 7.4.7.2.4 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created a contentInstance resource <contentInstance> as child resource of <container> resource Test Sequence Step RP Type Description 1 Stimulus AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <container> resource and AE is requested to send a contentInstance Delete Request 2 Mca PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/URI of <contentInstance> resource • fr = AE-ID • rqi = (token-string) • pc = empty ETSI ETSI TS 118 113 V3.3.1 (2021-09) 36 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 3 IOP Check Check if possible that the <contentInstance> resource is deleted in Registrar CSE and AE sends a RETRIEVE request to the parent <container> resource to check that if the Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly which is resulted from the successful deletion of child <contentInstance> resource 4 Mca PRO Check Primitive • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = empty 5 IOP Check Check if possible that the <contentInstance> resource has been removed in registrar CSE. 6 IOP Check AE indicates successful DELETE operation of <contentInstance> and indicates Registrar CSE has updated currentNrOfInstances, and CurrentByteSize attribute correspondingly IOP Verdict Set the verdict to pass if both the <contentInstance> is deleted and the Registrar CSE updated currentNrOfInstances, and CurrentByteSize attribute. Otherwise, set the verdict to fail with corresponding error message PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.4 <latest> ContentInstance Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_49 Objective: AE deletes a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.12 oneM2M TS-0004 [2], clause 7.4.27.2.4 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE retrieves a <latest> resource in a <container> and then sends a DELETE request to the <latest> resource of the <container> 2 Mca PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/URI of <latest> resource of a <container> • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = representation of deleted <latest> resource of a <container> 4 IOP Check AE indicates successful DELETE operation of a <latest> resource and AE sends a RETRIEVE request to <latest> resource of a <container> to check if the retrieved <latest> resource in the <container> is different with that one that was retrieved before DELETE request of the <latest> resource in terms of resourceID and resourceName attribute value IOP Verdict Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 37 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.5 <oldest> ContentInstance Delete
|
Interoperability Test Description Identifier: TD_M2M_NH_50 Objective: AE deletes a <oldest> resource of a <container> and the Registrar CSE points an oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.14 oneM2M TS-0004 [2], clause 7.4.28.2.4 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created more than one contentInstances <contentInstance> as child of <container> on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE retrieves a <oldest> resource of a <container> and AE sends a DELETE Request to the <oldest> resource of the <container> 2 Mca PRO Check Primitive • op = 4 (Delete) • to = {CSEBaseName}/URI of <oldest> resource of a <container> • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2002 (DELETED) • rqi = (token-string) same as received in request message • pc = representation of deleted <oldest> resource of a <container> 4 IOP Check AE indicates successful DELETE operation of a <oldest> resource and AE sends a RETRIEVE request to <oldest> resource of a <container> to check if the retrieved <oldest> resource in the <container> is different with that one that was retrieved before DELETE request of the <oldest> resource in terms of resourceID and resourceName attribute values IOP Verdict Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message PRO Verdict 8.1.5.6 ContentInstance Create when currentNrOfInstance equals to maxNrOfInstances in parent <container> resource Interoperability Test Description Identifier: TD_M2M_NH_51 Objective: AE sends a <contentInstance> CREATE request to a <container> which contains attribute currentNrOfInstances whose value equals to that of maxNrOfInstances and Registrar CSE deletes the oldest <contentInstance> from the parent <container> and then creates the requested <contentInstance> resource for the originator AE Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.7 oneM2M TS-0004 [2], clause 7.4.6.2.1 Pre-test conditions: • AE has created an application resource <AE> on registrar CSE • AE has created a container resource <container> (where the number of contentInstances equals to the value set in maxNrOfInstance) on registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE sends a RETRIEVE request with resultContent set to 1 (default value) to retrieve the <oldest> contentInstance resource and AE sends a request to create a <contentInstance> resource ETSI ETSI TS 118 113 V3.3.1 (2021-09) 38 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 2 Mca PRO Check Primitive • op = 1 (Create) • to = {CSEBaseName}/URI of <container> resource • fr = AE-ID • rqi = (token-string) • ty = 4 (contentInstance) • pc = Serialized representation of <contentInstance> resource 3 IOP Check Check if possible that the <oldest> resource of a <container> is deleted 4 Mca PRO Check Primitive • rsc = 2001 (CREATED) • rqi = (token-string) same as received in request message • pc = Serialized representation of <contentInstance> resource 5 IOP Check AE indicates successful CREATE operation of <contentInstance> and indicates the representation of the recent <oldest> resource in the <container> is different with that of <oldest> resource retrieved at the beginning of test in terms of resourceID and resourceName attribute value IOP Verdict Set the verdict to pass if IOP check goal is achieved, otherwise set the verdict to fail with corresponding error message PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.7 <latest> ContentInstance Retrieve
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.7.1 Attribute locationID of the <container> resource configured
|
Interoperability Test Description Identifier: TD_M2M_NH_102 Objective: AE retrieves a <latest> resource of a <container> for which attribute locationID is configured, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.11 oneM2M TS-0004 [2], clause 7.4.27.2.2 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created a <locationPolicy> resource on Registrar CSE having its resourceID and locationContainerID attribute set to locationID and resourceID attribute of the <container> resource respectively • In resource <locationPolicy>, value of locationUpdatePeriod is marked '0' or not defined and locationSource attribute is 'Network Based' Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <latest> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <container> resource/la • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of latest <contentInstance> resource, created after acquiring location info from Location Server, in response to Location Request made by the CSE, using the attributes stored in the <locationPolicy> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict ETSI ETSI TS 118 113 V3.3.1 (2021-09) 39 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.7.2 Attribute locationID of the <container> resource not configured
|
Interoperability Test Description Identifier: TD_M2M_NH_71 Objective: AE retrieves a <latest> resource of a <container> and the Registrar CSE points a latest <contentInstance> among the existing contentInstances to the <latest> resource of the <container> Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.11 oneM2M TS-0004 [2], clause 7.4.27.2.2 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <latest> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <container> resource/la • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of latest <contentInstance> resource 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.5.8 <oldest> ContentInstance Retrieve
|
Interoperability Test Description Identifier: TD_M2M_NH_72 Objective: AE retrieves a <oldest> resource of a <container> and the Registrar CSE points a oldest <contentInstance> among the existing contentInstances to the <oldest> resource of the <container> Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.4.13 oneM2M TS-0004 [2], clause 7.4.28.2.2 Pre-test conditions: • AE has created an Application Entity resource <AE> on Registrar CSE • AE has created a container resource <container> on Registrar CSE • AE has created multiple contentInstance resources <contentInstance> as child resource of <container> resource Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Retrieve Request for a <oldest> 2 Mca PRO Check Primitive • op = 2 (Retrieve) • to = {CSEBaseName}/URI of <container> resource/ol • fr = AE-ID • rqi = (token-string) • pc = empty 3 Mca PRO Check Primitive • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of oldest <contentInstance> resource 4 IOP Check AE indicates successful operation ETSI ETSI TS 118 113 V3.3.1 (2021-09) 40 oneM2M TS-0013 version 3.3.1 Release 3
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.6 Discovery
| |
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.6.1 Discovery of all resources
|
Interoperability Test Description Identifier: TD_M2M_NH_18 Objective: AE discovers all accessible resources from registrar CSE Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a discovery request to registrar CSE 2 Mca PRO Check Primitive Sent request contains: • op = 2 (Retrieve) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • fu=1 • pc = empty 3 Mca PRO Check Primitive Registrar CSE sends response containing: • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of data object containing addresses of all discovered resources 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
e80b5da6c14ed17fdbf5d0fb9b8ebe31
|
118 113
|
8.1.6.2 Discovery with label filter criteria
|
Interoperability Test Description Identifier: TD_M2M_NH_19 Objective: AE discovers accessible resources residing in Registrar CSE using the label filter criteria Configuration: M2M_CFG_01 References: ETSI TS 118 101 [1], clause 10.2.6 oneM2M TS-0004 [2], clause 7.3.3.14 Pre-test conditions: • CSEBase resource has been created in registrar CSE with name {CSEBaseName} • A <Container> resource with label "key1" is created on Registrar CSE Test Sequence Step RP Type Description 1 Stimulus AE is requested to send a Discovery request in order to discover the <Container> resource using the label filter criteria 2 Mca PRO Check Primitive Sent request contains: • op = 2 (Retrieve) • to = {CSEBaseName} • fr = AE-ID • rqi = (token-string) • fu=1 • lbl=key1 • pc = empty 3 Mca PRO Check Primitive Registrar CSE sends response containing: • rsc = 2000 (OK) • rqi = (token-string) same as received in request message • pc = Serialized representation of data object containing the address of the <Container> address ETSI ETSI TS 118 113 V3.3.1 (2021-09) 41 oneM2M TS-0013 version 3.3.1 Release 3 Interoperability Test Description 4 IOP Check AE indicates successful operation IOP Verdict PRO Verdict
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.