hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.7.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/COUNTSIG/2 Normative source: [1]- Clause 5.2.7 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xades:CounterSignature element contains a ds:Reference referencing the ds:SignatureValue of the countersigned signature. Prescript... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.8 Testing xades:AllDataObjectsTimeStamp element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.8.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/ADOTST/1 Normative source: [1] β Clause 5.2.8.1 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: xades:AllDataObjectsTimeStamp does not contain any xades:Include child element. Prescription level: mandatory Tag: XAdES baseline and... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.9 Testing xades:IndividualDataObjectsTimeStamp element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.9.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/IDOTST/1 Normative source: [1] β Clause 5.2.8.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xades:IndividualDataObjectsTimeStamp qualifying property contains one or more xades:Include children element. Prescription level:... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10 Testing xades:SignaturePolicyIdentifier element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/SIGPOLID/1 Normative source: [1] β Clause 5.2.9 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xades:SigPolicyHash element contains the hash value of the object obtained after processing xades:SigPolicyId and ds:Transforms e... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10.2 Testing xades:SPURI signature policy qualifier | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10.2.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/SIGPOLID/SPURI/1 Normative source: [1] β Clause 5.2.9.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The place referenced by its value contains the signature policy document. Prescription level: mandatory Tag: XAdES baseline a... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10.3 Testing xadesv141:SPDocSpecification signature policy qualifier | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.10.3.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/SIGPOLID/SPDOCSPEC/1 Normative source: [1] β Clause 5.2.9.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: The technical specification is identified using an OID. Predicate: The xades:Identifier child contains a URN encoding ... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.11 Testing xadesv141:SignaturePolicyStore | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.11.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/SIGPOLST/1 Normative source: [1]- Clause 6.3, [2] Clauses 4.3, A.1, and A.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: The XAdES signature does not incorporate the xades:SignaturePolicyIdentifier. Predicate: The XAdES sig... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.12 Testing xadesv141:CompleteCertificateRefsV2 element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.12.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/CCERTREFSV2/1 Normative source: [1]- Clause A.1.1 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xadesv141:CompleteCertificateRefsV2 property does not contain a reference of the signing certificate. Prescription level: manda... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.12.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/CCERTREFSV2/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xadesv141:CompleteCertificateRefsV2 property is not present in the signature. Prescription level: preferred Tag: XAdES baseline signatur... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.13 Testing xadesv141:AttributeCertificateRefsV2 element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.13.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/ATTCERTREFSV2/1 Normative source: [1]- Clause A.1.3 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xadesv141:AttributeCertificateRefsV2 property does not contain references present within xadesv141:CompleteCertificateRefsV2 ... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.13.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/ATTCERTREFSV2/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xadesv141:AttributeCertificateRefsV2 property is not present in the signature. Prescription level: preferred Tag: XAdES baseline signa... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.14 Testing xades:CompleteRevocationRefs element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.14.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/CREVREFS/1 Normative source: [1]- Clause A.1.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The xades:CompleteRevocationRefs contains a reference to a revocation value for the signing certificate. Prescription level: mandatory... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.14.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/CREVREFS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:CompleteRevocationRefs property is not present in the signature. Prescription level: preferred Tag: XAdES baseline signatures TA id: ... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.15 Testing xades:AttributeRevocationRefs element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.15.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/ATTREVREFS/1 Normative source: [1]- Clause A.1.4 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: All or some of the references to revocation values for the signing certificate(s) of the attribute certificate(s) and signed asse... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.15.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/ATTREVREFS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:AttributeRevocationRefs property is not present in the signature. Prescription level: preferred Tag: XAdES baseline signatures TA i... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.16 Testing xadesv141:SigAndRefsTimeStampV2 element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.16.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/SIGREFSTSTV2/1 Normative source: [1] β Clause A.1.5.1 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: The xadesv141:SigAndRefsTimeStampV2 element does not contain any xades:Include child element. Predicate: The message imprint... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.16.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/SIGREFSTSTV2/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:SigAndRefsTimeStampV2 property is not present in XAdES-B-B signatures. Prescription level: preferred Tag: XAdES baseline signatur... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.17 Testing xadesv141:RefsOnlyTimeStampV2 element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.17.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/REFSONTSTV2/1 Normative source: [1] β Clause A.1.5.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: The xadesv141:RefsOnlyTimeStampV2 qualifying property does not contain any xades:Include child element. Predicate: The messag... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 5.3.17.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/REFSONTSTV2/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xadesv141:RefsOnlyTimeStampV2 property is not present in XAdES-B-B signatures. Prescription level: preferred Tag: XAdES baseline signatu... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 6.1 General requirements | For testing conformance to B-T level of XAdES baseline signatures, the following test assertions shall apply: 1) The test assertions defined in clause 6; and 2) the test assertions defined in clauses 5.2 and 5.3 unless stated otherwise. According ETSI EN 319 132-1 [1], XAdES-B-T signatures should not incorporate the fo... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 6.2 Testing xades:SignatureTimeStamp element | 6.2.1 Test assertions common to XAdES baseline and extended signatures TA id: XADES_BB/SIGTST/1 Normative source: [1] β Clause 5.3 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: The message imprint computation input of the time-stamp token enca... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 6.2.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/SIGTST/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:SignatureTimeStamp property is present in the signature. Prescription level: mandatory Tag: XAdES baseline signatures TA id: XADES_BS/S... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.1 General requirements | 7.1.1 Core requirements For testing conformance to B-LT level of XAdES baseline signatures, the following test assertions shall apply: 1) the test assertions defined in clause 7; and 2) the test assertions defined in clauses 5.2, 5.3 and 6.2 unless stated otherwise. 7.1.2 Test assertions for testing properties containi... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.1.3 Test assertions for testing properties from upper levels | According ETSI EN 319 132-1 [1], XAdES-B-LT signatures should not incorporate the following qualifying properties: xadesv141:ArchiveTimeStamp, and xadesv141:RenewedDigests. If any of the aforementioned qualifying properties is incorporated into a XAdES-B-LT signature, it shall be tested as indicated in clause 5.1. ETSI... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.2 Testing xades:CertificateValues element | 7.2.1 Test assertions common to XAdES baseline and extended signatures TA id: XAdES_BB/CERTVALS/1 Normative source: [1] β Clause 5.4.1 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Any xades:EncapsulatedX509Certificate child element contains t... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.2.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/CERTVALS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Prerequisite: The rest of elements and properties of the signature miss some of the certificates listed in clause 5.4.1 of ETSI TS 319 132 Part 1[1] that ... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.3 Testing xades:RevocationValues element | 7.3.1 Test assertions common to XAdES baseline and extended signatures TA id: XAdES_BB/REVVALS/1 Normative source: [1] β Clause 5.4.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Each xades:EncapsulatedCRLValue child of xades:CRLValues child ... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.3.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/REVVALS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Prerequisite: The rest of elements and properties of the signature miss some of the revocation values listed in clause 5.4.2 of ETSI TS 319 132 Part 1[1] t... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.4 Testing xades:AttrAuthoritiesCertValues element | 7.4.1 Test assertions common to XAdES baseline and extended signatures TA id: XAdES_BB/ATTCERTVALS/1 Normative source: [1] β Clause 5.4.3 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Any xades:EncapsulatedX509Certificate child element contain... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.4.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/ATTCERTVALS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Prerequisite: The signature incorporates attribute certificate(s) and/or signed assertion(s) AND the rest of elements and properties miss some of the c... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.5 Testing xades:AttributeRevocationValues element | 7.5.1 Test assertions common to XAdES baseline and extended signatures TA id: XAdES_BB/ATTREVVALS/1 Normative source: [1] β Clause 5.4.4 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Each xades:EncapsulatedCRLValue child of CRLValues child con... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.5.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/ATTREVVALS/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Prerequisite: The signature incorporates attribute certificate(s) and/or signed assertion(s) AND the rest of elements and properties miss some of the re... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 7.6 Testing xadesv141:TimeStampValidationData element | 7.6.1 Test assertions common to XAdES baseline and extended signatures TA id: XAdES_BB/TSTVALDAT/1 Normative source: [1] β Clause 5.5.1 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Any xades:EncapsulatedX509Certificate descendant element of x... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.1 General requirements | For testing conformance to B-LTA level of XAdES baseline signatures, the following test assertions shall apply: 1) the test assertions defined in clause 8; and 2) the test assertions defined in clauses 5.2, 5.3, 6.2, 7.1.2, 7.2, 7.3, 7.4, 7.5 and 7.6 unless stated otherwise. ETSI ETSI TS 119 134-4 V1.1.1 (2016-06) 37 |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.2 Testing xadesv141:ArchiveTimeStamp element | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.2.1 Common tests for distributed and not distributed cases | |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.2.1.1 Test assertions common to XAdES baseline and extended signatures | TA id: XADES_BB/ATSTV141/1 Normative source: [1] β Clause 5.5.2.2 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Prerequisite: The xadesv141:ArchiveTimeStamp qualifying property does not have any xades:Include child element. Predicate: The message imprint... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.2.1.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/ATST/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xadesv141:ArchiveTimeStamp property is present in XAdES-B-LTA signatures. Prescription level: mandatory Tag: XAdES baseline signatures TA id: X... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.3 Testing xadesv141:RenewedDigests element | 8.3.1 Test assertions common to XAdES baseline and extended signatures TA id: XADES_BB/RENDIG/1 Normative source: [1] β Clause 5.5.3 Target: XAdES signature generator claiming conformance to XAdES signatures either as specified in [1] or in [2] Predicate: Any xadesv141:RecomputedDigestValue descendant contains the base... |
bd563035a50afe21248e3fe615812d70 | 119 134-4 | 8.3.2 Test assertions specific to XAdES baseline signatures | TA id: XADES_BS/RENDIG/1 Normative source: [1] β Clause 6.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xadesv141:RenewedDigests property is present in the signature. Prescription level: permitted Tag: XAdES baseline signatures ETSI ETSI TS 119 ... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 1 Scope | The present document specifies Generic Interworking of the oneM2M System with external systems (e.g. Area Networks containing non-oneM2M devices) that can be described with ontologies that are compliant with oneM2M's Base Ontology, specified in ETSI TS 118 112 [3]. In oneM2M Release 2 the specification for Ontology bas... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 2 References | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 3 Definitions of terms, symbols and abbreviations | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 112 [3] and the following apply: abstract device: virtual Device (i.e. a set of oneM2M resources together with an IPE) that allows a communicating entity to communicate with an Interworked Device, using an Abstract Information... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 3.2 Symbols | Void. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1], ETSI TS 118 112 [3] and the following apply: IPE Interworking Proxy Application Entity NOTE: See ETSI TS 118 111 [1]. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 8 oneM2M TS-0030 version 4.0.1 Release 4 |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 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]. 5 Introduction to Ontology based Interworking (informative) |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.1 Basic concepts of Ontology based Interworking | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.1.1 Ontology based Interworking vs. Specific interworking | oneM2M supports interworking with several specific non-oneM2M solutions. Examples are: LWM2M Interworking (ETSI TS 118 114 [6]) or OIC Interworking (ETSI TS 118 124 [7]). While these examples refer to specific technologies oneM2M also allows to specify only data models - e.g. in ETSI TS 118 123 [5] - which does not ass... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.2 Using Ontology based Interworking with Device Abstraction | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.2.1 General description | As explained in clause 5.1 it is the task of an IPE to interact via the Area Network with the Interworked Devices and to provide oneM2M resources (Proxied Devices) to the communicating entities for communication with the Interworked Devices. However these Proxied Devices still exhibit the native data model - the Device... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.2.2 An example, involving ZigBee, HAIM and SAREF | Figure 2 illustrates this situation for a light switch. In the example the physical implementation is a ZigBee device implementing a ZigBee Service "On/Off Cluster". An IPE for ZigBee creates the interworking towards the ZigBee network. To enable abstraction, this device is abstracted as oneM2M device according to the ... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.3 Priciples of data flows | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.3.1 Preconditions on the communicating entity | Data flows between a communicating entity and the IPE involve oneM2M resources - specialized <flexContainer>s and possibly <AE>s - that were created by the IPE for the purpose of that communication. NOTE 1: In this clause and in the subsequent clauses it is assumed that the communicating entity and the IPE uses the one... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.1 oneM2M resources for IPE communication | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.1.1 General design principles | For Ontology based Interworking the oneM2M resource types <AE> and specializations of <flexContainer> are intended to hold data that can be used for data exchange with the IPE. For Ontology based Interworking a convention is needed how the IPE uses these resources to communicate with other oneM2M entities. This is desc... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2 Specification of the IPE for Ontology based Interworking | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1 Initialization of the Ontology based Interworking IPE | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1.1 General functionality of a Ontology based Interworking IPE | Ontology based Interworking Interworking supports the interworking variant with full mapping of the semantic of the non-oneM2M data model to Mca as indicated in clause F.2 of ETSI TS 118 101 [2]. The non-oneM2M data model is described in the form of a oneM2M compliant ontology which is derived (as sub-classes and sub-p... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1.2 Initialization sequence of a Ontology based Interworking IPE | After registration of the IPE's <AE> resource the IPE shall do the following: 1) The IPE shall retrieve the formal description of the ontology and parse it. 2) The IPE shall create a child-resource of its <AE> resource of type <container>, subsequently called 'XSD- storage' This <container>is will hold the XSDs that ar... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2 Interworked Device and Service discovery | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.1 General handling of Interworked Device discovery | If supported by the technology of the non-oneM2M solution the IPE shall continue to discover the devices in the non- oneM2M solution. If supported by the technology of the non-oneM2M solution the IPE shall continue to discover services that are provided by the devices in the non-oneM2M solution. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.2 Creation of resources for the Proxied Device | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.2.1 General on the creation of resources for the Proxied Device by the IPE | For each discovered Interworked Device in the non-oneM2M solution the IPE shall: either: - create a <flexContainer>child-resource of the IPE's own <AE> to represent the non-oneM2M Interworked Device in the oneM2M System: ο§ this option should be chosen in most cases, in particular when the individual representations for... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.3 Creation of resources for sub-devices | A Device can consist of (i.e. be composed) of several (sub-) Devices. In the oneM2M Base OntologyBase Ontology the Object Property: consistsOf links a device class to a class of its sub-devices. For each sub-device of a discovered device in the non-oneM2M solution the IPE shall create a specialized <flexContainer> reso... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.4 Creation of resources for Services | For each service, that is supported by a device or sub-device the IPE shall create a specialized <flexContainer> resource, representing the service. The <flexContainer> shall be a child-resource of the Proxied Device representation (<AE> or <flexContainer> resource in case of an interworked Device, specialized <flexCon... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5 Creation of resources for operations of a service of a device | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.1 Introduction | An Operation is the means of a Service to communicate in a procedure-type manner. In general an operation is invoked by the communicating entity and can - but need not - have OperationInput parameters. As a result of the Operation result parameters can - but need not - be returned. An operation can also be invoked by t... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.2 Creation of resources for operation invocation | For each operation, that is supported by a service of a device the IPE shall create a specialized <flexContainer> resource, representing the operation. The <flexContainer> shall be a child-resource of the specialized <flexContainer> of the service. The IPE shall subscribe to all specialized <flexContainer> resources re... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.3 Creation of resources for returning operation results | For each operation, that can produce operation result parameters (i.e. its class:Operation is related via Object Property: hasOutput to some class:OperationOutput) the IPE shall create a specialized <flexContainer> resource, representing the result of the operation for a set of invocation parametes. The <flexContainer>... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.6 Subscription to the created resources | The IPE shall subscribe to all specialized <flexContainer> resources representing services, that it creates. In particular it shall subscribe to the <flexContainer> resources representing Services and <flexContainer> resources for the Operation invocation. The attribute notificationContentType of the <subscription> nee... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.3 Handling of DataPoints by the IPE | β’ When the IPE receives a request by the interworked non-oneM2M device via the non-oneM2M reference point to write an OutputDataPoint belonging to a Service of the device the IPE shall: - de-serialize the received data; and - UPDATE the OutputDataPoint customAttribute of the <flexContainer> resource of the Service with... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.4 Handling of Operations by the IPE | When the IPE receives notification from the CSE about an UPDATE of the <flexContainer> resource of the operation the IPE shall perform the following actions: 1) If the operation has OperationInput data the IPE shall RETRIEVE the OperationInput data of the operation (contained in the customAttributes of the <flexContain... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.5 Removing of resources for Proxied Devices | β’ When a Interworked Device in the non-oneM2M solution becomes unavailable the IPE shall delete the resource for its Proxied Device and all its child-resources. β’ When the IPE detects that an Interworked Device stopped to support a Service (in case such detection is supported by the technology of the non-oneM2M solutio... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7 Rules for creation of XSDs from ontologies | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.1 General information | When the non-oneM2M data model is described in the form of a oneM2M compliant ontology which is derived (as sub- classes and sub-properties) from the oneM2M Base Ontology and is available in a formal description language (e.g. OWL) then the IPE can create XSDs for the resources needed by communicating entities to commu... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2 XSD creation rules | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1 General rules | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.1 General principle for creating XSDs | During initialization (clause 6.2.1) a Ontology based Interworking IPE creates XSD files for device types, service types and operation types, according to the class definitions (sub-classes of class:Device, class:Service, class:Operation) in the ontology. Each XSD file contains the definition of a single specialization... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.2 Parameters for XSD templates | In the subsequent clauses the following conventions for parameters to fill in XSD templates is used. The column "replacement rules" explains how the parameter is derived from the ontology. NOTE: This convention follows roughly conventions of ENTITY declarations for DTD. Each ENTITY that is to be replaced in the XSD sta... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3 Data typing for Variables | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.1 Information on datatypes contained in the ontology | All classes of the Base Ontology that describe data (i.e. InputDataPoint, OutputDataPoint, OperationInput, OperationOutput, ThingProperty are sub-classes of either the class:SimpleTypeVariable or the class StructuredTypeVariable. (This is due to the fact that class:Variable is the disjoint union of classes SimpleTypeVa... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.2 Construction of Simple Data Types | If class:Variable supports: β’ data property: isDataList value FALSE β’ data property: hasDataType value $SIMPLEDATATYPE$ then the XSD for the <flexContainer> that contains a customAttribute of that type (given by &TYPENAME;) needs to contain the typedefinition for that customAttribute. ETSI ETSI TS 118 130 V4.0.1 (2023-... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.3 List Data Types | If class:Variable supports: β’ data property: isDataList value TRUE β’ data property: hasDataType value $SIMPLEDATATYPE$ then the XSD for the <flexContainer> that contains a customAttribute of that type (given by &TYPENAME;) needs to contain the typedefinition for that customAttribute. ETSI ETSI TS 118 130 V4.0.1 (2023-0... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.4 Structured Data Types | If class:Variable supports: β’ data property: isDataList value FALSE; β’ object property: hasSubStructure with range class:&VARIABLENAME_1; β’ object property: hasSubStructure with range class:&VARIABLENAME_2; β’ β¦ β’ object property: hasSubStructure with range class:&VARIABLENAME_n; then the XSD for the <flexContainer> tha... |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.2 XSD template for sub-classes of Base Ontology class: Device | This clause only applies for the case when an Interworked Device is represented as <flexContainer>. In case an Interworked Device is represented as <AE> the resource definition of the <AE> resource in ETSI TS 118 101 [2] applies. Specific XSD definition for class:Device to be substituted at the placeholder in the XSD s... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.