id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
119 182-1
|
Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf
|
The present document: 1) Specifies a JSON [1] format for AdES signatures (JAdES signatures hereinafter) built on JSON Web Signatures (JWS hereinafter) as specified in IETF RFC 7515 [2]. For this, the present document: - Extends the JSON Web Signatures specified in IETF RFC 7515 [2] by defining an additional set of JSON header parameters that can be incorporated in the JOSE Header (either in its JWS Protected Header or its JWS Unprotected Header parts). Many of these new header parameters have the same semantics as the attributes/properties defined in CAdES [i.2] and XAdES [4] digital signatures. Other header parameters are defined to meet specific requirements that current JSON Web Signatures cannot meet (e.g. for explicitly referencing detached JWS Payload). These new header parameters and their corresponding types are defined in a JSON schema. - Specifies the mechanisms for incorporating the aforementioned JSON components in JSON Web Signatures [2] to build JAdES signatures, offering the same features as CAdES and XAdES in JSON syntax, and therefore fulfilling the same requirements (such as the long-term validity of digital signatures). 2) Defines four levels of JAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term. Each level requires the presence of certain JAdES header parameters, suitably profiled for reducing the optionality as much as possible. The aforementioned levels provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. EXAMPLE: An example of requirements raised in specific domains is signing HTTP messages exchanged by parties in certain environments, which require signing both the HTTP body and some specific http headers. The format specified in IETF RFC 7515 [2] does not provide any native mechanism for individually identifying a detached JWS Payload. Clause 5.2.8 of the present document defines sigD, a new JSON header parameter that allows to identify one or more detached data objects which, suitably processed and concatenated, form the detached JWS Payload. Procedures for creation, augmentation, and validation of JAdES digital signatures are out of scope. NOTE 1: ETSI EN 319 102-1 [i.3] specifies procedures for creation, augmentation and validation of other types of AdES digital signatures. The present multi-part deliverable aims at supporting electronic signatures independent of any specific regulatory framework. NOTE 2: Specifically, but not exclusively, it is the aim that JAdES digital signatures specified in the present multi-part deliverable can be used to meet the requirements of electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as defined in Regulation (EU) No 910/2014 [i.1].
|
119 172-4
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 4: Signature applicability rules (validation policy) for European qualified electronic signatures/seals using trusted lists
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.01.01_60/ts_11917204v010101p.pdf
|
The present document specifies a set of rules that aims at defining the technical requirements for determining, taking into account the EU Member States trusted lists [i.4], whether a digital signature is fit for meeting the requirements of EU qualified electronic signatures/seals in the sense of the applicable European legislation, i.e. either Directive 1999/93/EC [i.2] or Regulation (EU) No 910/2014 [i.1].
|
119 172-3
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 3: ASN.1 format for signature policies
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917203/01.01.01_60/ts_11917203v010101p.pdf
|
The present document defines an ASN.1 format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define ASN.1 elements for the building blocks specified in ETSI TS 119 172-1 [i.2] defining only applicability rules. For each element of the machine readable signature policy, the present document references to the semantics described in ETSI TS 119 172-2 [3] and defines the corresponding ASN.1 syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate ASN.1 documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An ASN.1 document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE: Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several ASN.1 documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document.
|
119 172-2
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 2: XML format for signature policies
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917202/01.01.01_60/ts_11917202v010101p.pdf
|
The present document defines an XML format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define XML elements for the building blocks specified in ETSI TS 119 172-1 [i.2] that define only applicability rules. For each element of the machine readable signature policy, the present document specifies the semantics and the how to implement it in XML syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate XML documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An XML document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE : Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several XML documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document.
|
119 172-1
|
Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 1: Building blocks and table of contents for human readable signature policy documents
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11917201/01.01.01_60/ts_11917201v010101p.pdf
|
The present document defines the building blocks of signature policy and specifies a table of contents for human readable signature policy documents.
|
119 164-5
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 5: Testing Conformance of additional ASiC containers
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916405/01.01.01_60/ts_11916405v010101p.pdf
|
The present document defines the sets of checks required for testing conformance of ASiC containers against: • ASiC containers conforming to building blocks defined in ETSI EN 319 162-1 [1] and containing extended CAdES [i.5] and extended XAdES [i.6] digital dignatures, expanding the scope of ASiC baseline containers also defined in ETSI EN 319 162-1 [1]; and • additional containers defined in ETSI EN 319 162-2 [2]. The set of checks that are common with ASiC baseline containers, are defined in ETSI TS 119 164-4 [5] and referenced when needed.
|
119 164-4
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 4: Testing Conformance of ASiC baseline containers
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916404/01.01.01_60/ts_11916404v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of ASiC containers against ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The present document does not specify checks leading to conclude whether a container is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in signatures inside the container may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a container that has been successfully tested by any tool conformant to the present document. Checks are exclusively constrained to elements specified by ASiC [1]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by ASiC [1].
|
119 164-3
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 3: Test suites for testing interoperability of ASiC containers other than baseline
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916403/01.01.01_60/ts_11916403v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC building blocks defined in ETSI EN 319 162-1 [1] and additional containers defined in ETSI EN 319 162-2 [2]. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 164-2
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of ASiC baseline containers
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916402/02.01.01_60/ts_11916402v020101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The test suites are defined with four different layers reflecting the four different levels of ASiC baseline containers. • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. • Test suites also cover augmentation of ASiC baseline containers and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 164-2
|
Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) Testing Compliance & Interoperability; Part 2: Test Suite for ASiC interoperability test events
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11916402/01.01.01_60/ts_11916402v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The test suites are defined with four different layers reflecting the four different levels of ASiC baseline containers. • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. • Test suites also cover augmentation of ASiC baseline containers and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 144-5
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of additional PAdES signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914405/01.01.01_60/ts_11914405v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of PAdES signatures against additional PAdES signatures profiles as specified in ETSI EN 319 142-2 [3]. It defines only the checks that are specific to additional PAdES signatures. The set of checks that are common to both additional and baseline PAdES signatures, are defined in ETSI TS 119 144-4 [6]. The complete set of checks to be performed by any tool on additional PAdES signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 142-1 [1] and ETSI EN 319 142-2 [3] defined in ETSI TS 119 144-4 [6], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for additional PAdES signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1].
|
119 144-4
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of PAdES baseline signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914404/01.01.01_60/ts_11914404v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of PAdES signatures against PAdES baseline signatures as specified in ETSI EN 319 142-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for PAdES baseline signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1].
|
119 144-3
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of additional PAdES signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914403/01.01.01_60/ts_11914403v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to additional PAdES signatures profiles [3]. The present document defines test suites for each profile defined in ETSI EN 319 142-2 [3]. Test suites also cover augmentation of additional PAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 144-2
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of PAdES baseline signatures
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914402/02.01.01_60/ts_11914402v020101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to PAdES baseline signatures [2]. The test suites are defined with four different layers reflecting the four different levels of PAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of PAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 144-2
|
Electronic Signatures and Infrastructures (ESI); PDF Advanced Electronic Signature (PAdES) Testing Compliance & Interoperability; Part 2: Test Suite for PAdES interoperability test events
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914402/01.01.01_60/ts_11914402v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to PAdES baseline signatures [2]. The test suites are defined with four different layers reflecting the four different levels of PAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of PAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 142-3
|
Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 3: PAdES Document Time-stamp digital signatures (PAdES-DTS)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11914203/01.01.01_60/ts_11914203v010101p.pdf
|
The present document specifies a type of PDF digital signatures, as specified in ISO 32000-1 [1], based on time-stamps. It specifies a format for PAdES digital signatures using a Document Time-stamp - as defined in ETSI EN 319 142-1 [2] - as a digital signature intended to specifically prove the integrity and existence of a PDF document as defined in ISO 32000-1 [1], rather than proving any form of authentication or proof of origin. NOTE: This format does not meet the requirements of advanced electronic signature and advanced electronic seal as defined in Regulation (EU) No 910/2014 [i.4], as it is not capable of identifying the signer.
|
119 134-5
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended XAdES signatures
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913405/02.01.01_60/ts_11913405v020101p.pdf
|
The present document defines the sets of checks required for testing conformance of XAdES signatures against extended XAdES signatures as specified ETSI EN 319 132-2 [2]. It defines only the checks that are specific to extended XAdES signatures. The set of checks that are common to both extended and baseline XAdES signatures, are defined in ETSI TS 119 134-4 [4]. The complete set of checks to be performed by any tool on XAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2] defined in ETSI TS 119 134-4 [4], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. The only possible inferences are the ones explicitly mentioned in the second paragraph of the present clause. Checks specified by the present document are exclusively constrained to elements specified by ETSI EN 319 132-1 [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:keyInfo). Regarding XAdES properties, the present document does not addresses the structural requirements that are defined by the XAdES XML Schema that are suitably addressed in ETSI TS 119 134-4 [4]. The present document does not address either requirements that are common to both XAdES signatures as specified in ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1].
|
119 134-5
|
Electronic Signatures and Infrastructures (ESI); XML Advanced Electronic Signature (XAdES) Testing Compliance & Interoperability; Part 5: Conformance Testing for XAdES Baseline Profile
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913405/01.01.01_60/ts_11913405v010101p.pdf
|
The present document defines the sets of checks required for testing conformance of XAdES signatures against extended XAdES signatures as specified ETSI EN 319 132-2 [2]. It defines only the checks that are specific to extended XAdES signatures. The set of checks that are common to both extended and baseline XAdES signatures, are defined in ETSI TS 119 134-4 [4]. The complete set of checks to be performed by any tool on XAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2] defined in ETSI TS 119 134-4 [4], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. The only possible inferences are the ones explicitly mentioned in the second paragraph of the present clause. Checks specified by the present document are exclusively constrained to elements specified by ETSI EN 319 132-1 [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:keyInfo). Regarding XAdES properties, the present document does not addresses the structural requirements that are defined by the XAdES XML Schema that are suitably addressed in ETSI TS 119 134-4 [4]. The present document does not address either requirements that are common to both XAdES signatures as specified in ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1].
|
119 134-4
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of XAdES baseline signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913404/01.01.01_60/ts_11913404v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of XAdES signatures against XAdES baseline signatures as specified ETSI EN 319 132-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by XAdES [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:DigestMethod, ds:DigestValue). Regarding XAdES properties, the present document explicitly differentiates between structural requirements that are defined by the XAdES XML Schema, and the rest of the requirements specified by XAdES [1]. Checks corresponding to the first set of requirements are specified in the normative annex A. Checks corresponding to the second set of requirements are specified in the body part of the present document. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1].
|
119 134-3
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of extended XAdES signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913403/01.01.01_60/ts_11913403v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended XAdES signatures as specified in ETSI EN 319 132-2 [2]. The present document defines test suites for each level defined in ETSI EN 319 132-2 [2]. Test suites also cover augmentation of extended XAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 134-2
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of XAdES baseline signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913402/01.01.01_60/ts_11913402v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to XAdES baseline signatures as specified in ETSI EN 319 132-1 [1]. The test suites are defined with four different layers reflecting the four different levels of XAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of XAdES baseline and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 132-3
|
Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 3: Incorporation of Evidence Record Syntax (ERS) mechanisms in XAdES
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11913203/01.01.01_60/ts_11913203v010101p.pdf
|
The present document specifies the semantics and the syntax for a new unsigned XAdES qualifying property able to contain evidence records. The present document specifies the rules that govern the incorporation of evidence records within a XAdES signature or a legacy XAdES signature. NOTE: The present specification allows to incorporate Evidence Records in two different formats, namely: the XML format for ERS specified in IETF RFC 6283 (2011): "Extensible Markup Language Evidence Record Syntax (XMLERS)" [5], and the ASN.1 format for ERS specified in IETF RFC 4998 (2007): "Evidence Record Syntax (ERS)" [8]. The present document also specifies a new level for XAdES signatures, incorporating one or more than one of the aforementioned qualifying properties. The signatures specified in the present document are not baseline XAdES signatures.
|
119 124-5
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended CAdES signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11912405/01.01.01_60/ts_11912405v010101p.pdf
|
The present document defines the checks to be performed for testing conformance of CAdES signatures against extended CAdES signatures as specified in ETSI EN 319 122-2 [2]. It defines only the checks that are specific to extended CAdES signatures. The set of checks that are common to both extended and baseline CAdES signatures, are defined in ETSI TS 119 124-4 [3]. The complete set of checks to be performed by any tool on CAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 122-1 [1] and ETSI EN 319 122-2 [2] defined in ETSI TS 119 124-4 [3], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by CAdES [1]. Regarding CAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for extended CAdES signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by CAdES [1].
|
119 124-4
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of CAdES baseline signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11912404/01.01.01_60/ts_11912404v010101p.pdf
|
The present document defines the set of checks to be performed for testing conformance of CAdES signatures against CAdES baseline signatures as specified in ETSI EN 319 122-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by CAdES [1]. Regarding CAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for CAdES baseline signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by CAdES [1].
|
119 124-3
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of extended CAdES signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11912403/01.01.01_60/ts_11912403v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended CAdES signatures [2]. The present document defines test suites for each level defined in ETSI EN 319 122-2 [2]. Test suites also cover augmentation of extended CAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 124-2
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of CAdES baseline signatures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11912402/01.01.01_60/ts_11912402v010101p.pdf
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to CAdES baseline signatures [1]. The test suites are defined with four different layers reflecting the four different levels of CAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of CAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
119 122-3
|
Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 3: Incorporation of Evidence Record Syntax (ERS) mechanisms in CAdES
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11912203/01.01.01_60/ts_11912203v010101p.pdf
|
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.
|
119 102-2
|
Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 2: Signature Validation Report
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/11910202/01.04.01_60/ts_11910202v010401p.pdf
|
The present document specifies a general structure and an XML format for reporting the validation of AdES digital signatures (specified in ETSI EN 319 122-1 [i.1], ETSI EN 319 132-1 [4], ETSI EN 319 142-1 [i.3] respectively). The present document is aligned with the requirements specified in ETSI EN 319 102-1 [1].
|
119 101
|
Electronic Signatures and Infrastructures (ESI); Policy and security requirements for applications for signature creation and signature validation
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/119100_119199/119101/01.01.01_60/ts_119101v010101p.pdf
|
The present document provides general security and policy requirements for applications for signature creation, validation and augmentation. The present document is primarily relevant to the following actors: • Implementers and providers of applications for signature creation, signature validation and/or signature augmentation, who need to ensure that relevant requirements are covered. • Actors that integrate applications for signature creation, signature validation and/or signature augmentation components with business process software (or use standalone software), who want to ensure proper functioning of the overall signature creation/validation/augmentation process and that the signature creation/validation is done in a sufficiently secure environment. The present document is applicable to these actors, and their evaluators (for a self-evaluation or an evaluation by a third party) to have a list of criteria against which to check the implementation. The requirements cover applications for signature creation, signature validation and/or signature augmentation, i.e. the implementation and provision of the Signature Creation/Validation/Augmentation Application modules (SCA/SVA/SAA), the driving application (DA), the communication between the SCA and the signature creation device (SCDev) and the environment in which the SCA/SVA/SAA is used. It also specifies user interface requirements, while the user interface can be part of the SCA/SVA/SAA or of the DA which calls the SCA/SVA/SAA. Any entity using SCA/SVA/SAA components in its business process acts as driving application. The document covers: • Legal driven policy requirements. • Information security (management system) requirements. • Signature creation, signature validation and signature augmentation processes requirements. • Development and coding policy requirements. • General requirements. Protection Profiles (PP) for signature creation applications and signature validation applications are out of scope and are defined in the CEN standard "Protection Profiles for Signature Creation & Validation Applications" [i.9]. General requirements for trust service providers are provided in ETSI EN 319 401 [i.24]. Requirements for trust service providers providing signature creation or validation services are out of scope. Requirements on trust service providers providing signature creation services are to be defined in ETSI TS 119 431 [i.22], with CEN EN 419 241 [i.21] defining requirements for a remote signature creation device. Requirements on trust service providers providing signature validation services are to be defined in ETSI TS 119 441 [i.23].
|
118 140
|
oneM2M Modbus Interworking (oneM2M TS-0040 version 4.0.0 Release 4)
|
TS
|
4.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118140/04.00.00_60/ts_118140v040000p.pdf
|
The present document specifies the oneM2M and Modbus interworking technologies that enable Modbus devices and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the Modbus IPE is hosted and how the IPE is composed with. Clause 6 defines the architecture aspects that mainly describes Modbus services to oneM2M resource mapping structure and rules. Furthermore, this explains the IPE registration and interworking procedures.
|
118 133
|
Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf
|
The present document defines general guidelines when interworking between external Proximal IoT technologies which are not aware of oneM2M-defined functionality, and the oneM2M system (i.e. the interaction between non-oneM2M- aware devices, gateways or applications (non-oneM2M entities) and oneM2M-defined entities). In the present document guidelines are defined on how to use oneM2M-defined resources to represent the state, events, actions, procedures, services provided by the non-oneM2M entities and how to expose oneM2M functions or services represented by oneM2M-defined resource to non-oneM2M Proximal IoT technologies. Therefore, services provided by non-oneM2M entities can be consumed by oneM2M entities via the oneM2M defined interfaces and vice versa. When following these guidelines, oneM2M-aware entities consuming services provided by non-oneM2M-aware entities via the specified interworking methods do not need to know anything about external Proximal IoT technologies. Also entities in an external Proximal IoT network that are not oneM2M-aware can consume services provided by oneM2M entities when exposed to the external Proximal IoT network according to the specified methods.
|
118 132
|
MAF and MEF Interface Specification (oneM2M TS-0032 version 4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118132/04.00.01_60/ts_118132v040001p.pdf
|
The present document specifies communication between the M2M Authentication Function (MAF) and MAF clients on the reference point Mmaf and between the M2M Enrolment Function (MEF) and MEF clients on the reference point Mmef.
|
118 132
|
MAF and MEF Interface Specification (oneM2M TS-0032 version 2.0.2 Release 2A)
|
TS
|
2.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118132/02.00.02_60/ts_118132v020002p.pdf
|
The present document specifies communication between the M2M Authentication Function (MAF) and MAF clients on the reference point Mmaf and between the M2M Enrolment Function (MEF) and MEF clients on the reference point Mmef.
|
118 130
|
oneM2M; Ontology based Interworking (oneM2M TS-0030 version 4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118130/04.00.01_60/ts_118130v040001p.pdf
|
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 based Interworking had been contained in clauses 8 and 9 of ETSI TS 118 112 [3].
|
118 130
|
oneM2M; Ontology based Interworking (oneM2M TS-0030 version 3.0.2 Release 3)
|
TS
|
3.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118130/03.00.02_60/ts_118130v030002p.pdf
|
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 based Interworking had been contained in clauses 8 and 9 of ETSI TS 118 112 [3].
|
118 125
|
Definition of product profiles (oneM2M TS-0025 version 2.0.0 Release 2A)
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118125/02.00.00_60/ts_118125v020000p.pdf
|
The present document specifies the detailed defined product profiles that can be used by manufactures and service providers where for each dedicated product, one of the defined product profile can be selected. The product profile would provide guidance to what features will be implemented, what features should be implemented and what features may be implemented. The present document also describes the test purposes that need to go through if the product need to be certified.
|
118 124
|
oneM2M; OCF Interworking (oneM2M TS-0024 version 3.2.2 Release 3)
|
TS
|
3.2.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118124/03.02.02_60/ts_118124v030202p.pdf
|
The present document specifies the detailed methods for oneM2M and OCF interworking using the architecture identified in oneM2M TS-0033 [5] and annex F of ETSI TS 118 101 [2] for the following scenario: • Interworking with full mapping of the semantics of the non-oneM2M data model to Mca, see scenario number 1 listed in clause F.2 of ETSI TS 118 101 [2]. This is also in line with the interworking concepts specified in oneM2M TS-0033 [5]. This interworking scenario allows for interworking between OCF devices and oneM2M entities purely based on the common understanding of aligned information models - such as the models defined in ETSI TS 118 123 [6]. There is no limitation regarding the direction of exposure of services: Services provided by OCF devices (OCF servers) can be exposed to oneM2M entities or vice versa. The oneM2M entities do not need to be aware of any details of the OCF protocols or interfaces.
|
118 124
|
oneM2M; OIC Interworking (oneM2M TS-0024 version 2.0.2 Release 2A)
|
TS
|
2.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118124/02.00.02_60/ts_118124v020002p.pdf
|
The present document specifies the detailed methods for oneM2M and OCF interworking using the architecture identified in oneM2M TS-0033 [5] and annex F of ETSI TS 118 101 [2] for the following scenario: • Interworking with full mapping of the semantics of the non-oneM2M data model to Mca, see scenario number 1 listed in clause F.2 of ETSI TS 118 101 [2]. This is also in line with the interworking concepts specified in oneM2M TS-0033 [5]. This interworking scenario allows for interworking between OCF devices and oneM2M entities purely based on the common understanding of aligned information models - such as the models defined in ETSI TS 118 123 [6]. There is no limitation regarding the direction of exposure of services: Services provided by OCF devices (OCF servers) can be exposed to oneM2M entities or vice versa. The oneM2M entities do not need to be aware of any details of the OCF protocols or interfaces.
|
118 123
|
oneM2M; SDT based Information Model and Mapping for Vertical Industries [oneM2M TS-0023 version 4.8.1 Release 4]
|
TS
|
4.8.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf
|
The present document describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model.
|
118 123
|
oneM2M; Home Appliances Information Model and Mapping (oneM2M TS-0023 version 3.7.3 Release 3)
|
TS
|
3.7.3
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118123/03.07.03_60/ts_118123v030703p.pdf
|
The present document describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model.
|
118 114
|
oneM2M; LWM2M Interworking (oneM2M TS-0014 version 2.0.1 Release 2A)
|
TS
|
2.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118114/02.00.01_60/ts_118114v020001p.pdf
|
The present document specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints using the architecture identified in Annex F of ETSI TS 118 101 [2] for the following interworking scenarios: • Interworking for transparent transport of encoded LWM2M Objects and commands in Content Sharing Resources between LWM2M Endpoints and M2M Applications. • Interworking with full mapping of LWM2M Objects in LWM2M Endpoints to semantically enabled Content Sharing Resources that are utilized by M2M Applications. • Interworking with one-to-one mapping of LWM2M Objects with oneM2M <mgmtObj> resources NOTE: The present document limits Content Sharing Resources to <container> and <contentInstance> resources.
|
118 122
|
oneM2M; Field Device Configuration (oneM2M TS-0022 version 4.5.1 Release 4)
|
TS
|
4.5.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118122/04.05.01_60/ts_118122v040501p.pdf
|
The present document specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the device's AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation.
|
118 122
|
oneM2M; Field Device Configuration (oneM2M TS-0022 version 3.0.2 Release 3)
|
TS
|
3.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118122/03.00.02_60/ts_118122v030002p.pdf
|
The present document specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the device's AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation.
|
118 122
|
oneM2M; Field Device Configuration (oneM2M TS-0022 version 2.3.1 Release 2A)
|
TS
|
2.3.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118122/02.03.01_60/ts_118122v020301p.pdf
|
The present document specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the device's AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation.
|
118 121
|
oneM2M; oneM2M and AllJoyn® Interworking (oneM2M TS-0021 version 2.0.1 Release 2A)
|
TS
|
2.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118121/02.00.01_60/ts_118121v020001p.pdf
|
The present document specifies the oneM2M and AllJoyn interworking technologies that enable AllJoyn Applications and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the AllJoyn IPE is hosted and how the IPE is composed with. Clause 6 defines the architecture aspects that mainly describes AllJoyn services to oneM2M resource mapping structure and rules. Furthermore, this explains the IPE registration and AllJoyn service discovery by the IPE. Clause 7 defines the IPE interworking procedures that consists of the initial setup and the service interworking procedures.
|
118 120
|
oneM2M; WebSocket Protocol Binding (oneM2M TS-0020 version 3.0.1 Release 3)
|
TS
|
3.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118120/03.00.01_60/ts_118120v030001p.pdf
|
The present document specifies the binding of Mca and Mcc primitives onto the WebSocket binding. It specifies: • Procedures and message formats for operating and closing of WebSocket connections. • How request and response primitives are mapped into the payload of the WebSocket protocol.
|
118 120
|
oneM2M; WebSocket Protocol Binding (oneM2M TS-0020 version 2.1.2 Release 2A)
|
TS
|
2.1.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118120/02.01.02_60/ts_118120v020102p.pdf
|
The present document specifies the binding of Mca and Mcc primitives onto the WebSocket binding. It specifies: • Procedures and message formats for operating and closing of WebSocket connections. • How request and response primitives are mapped into the payload of the WebSocket protocol.
|
118 119
|
oneM2M Abstract Test Suite and Implementation eXtra Information for Test (oneM2M TS-0019 version 2.3.0 Release 2)
|
TS
|
2.3.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118119/02.03.00_60/ts_118119v020300p.pdf
|
The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in ETSI TS 118 101 [1] and ETSI TS 118 104 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of inter-operability between different manufacturers' equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as ETSI TS 118 115 [i.2] are used as a basis for the test methodology.
|
118 119
|
oneM2M Abstract Test Suite and Implementation eXtra Information for Test (oneM2M TS-0019 version 1.0.0)
|
TS
|
1.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118119/01.00.00_60/ts_118119v010000p.pdf
|
The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in ETSI TS 118 101 [1] and ETSI TS 118 104 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of inter-operability between different manufacturers' equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as ETSI TS 118 115 [i.2] are used as a basis for the test methodology.
|
118 118
|
oneM2M Test Suite Structure and Test Purposes (oneM2M TS-0018 version 2.13.1 Release 2)
|
TS
|
2.13.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118118/02.13.01_60/ts_118118v021301p.pdf
|
The present document specifies oneM2M test suite structure and test purposes that are designed to evaluate the conformity of oneM2M implementations to the oneM2M specifications. It also specifies: • guidelines for description of test behaviours and definition of test purpose structure; • notations to define a test purpose for conformance testing; and • test configurations for conformance testing.
|
118 116
|
oneM2M; Secure Environment Abstraction (oneM2M TS-0016 version 4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118116/04.00.01_60/ts_118116v040001p.pdf
|
The present document specifies mechanisms and interfaces to abstract from different technical implementations of a secure environment as defined in ETSI TS 118 103 [1].
|
118 116
|
oneM2M; Secure Environment Abstraction (oneM2M TS-0016 version 3.0.2 Release 3)
|
TS
|
3.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118116/03.00.02_60/ts_118116v030002p.pdf
|
The present document specifies mechanisms and interfaces to abstract from different technical implementations of a secure environment as defined in ETSI TS 118 103 [1].
|
118 115
|
oneM2M; Testing Framework (oneM2M TS-0015 version 2.0.0 Release 2)
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118115/02.00.00_60/ts_118115v020000p.pdf
|
The present document specifies a testing framework defining a methodology for development of conformance and interoperability test strategies, test systems and the resulting test specifications for oneM2M standards.
|
118 114
|
oneM2M; LWM2M Interworking (oneM2M TS-0014 version 4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118114/04.00.01_60/ts_118114v040001p.pdf
|
The present document specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints using the architecture identified in Annex F of ETSI TS 118 101 [2] for the following interworking scenarios: • Interworking for transparent transport of encoded LWM2M Objects and commands in Content Sharing Resources between LWM2M Endpoints and M2M Applications. • Interworking with full mapping of LWM2M Objects in LWM2M Endpoints to semantically enabled Content Sharing Resources that are utilized by M2M Applications. • Interworking with one-to-one mapping of LWM2M Objects with oneM2M <mgmtObj> resources NOTE: The present document limits Content Sharing Resources to <container> and <contentInstance> resources.
|
118 114
|
oneM2M; LWM2M Interworking (oneM2M TS-0014 version 3.2.0 Release 3)
|
TS
|
3.2.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118114/03.02.00_60/ts_118114v030200p.pdf
|
The present document specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints using the architecture identified in Annex F of ETSI TS 118 101 [2] for the following interworking scenarios: • Interworking for transparent transport of encoded LWM2M Objects and commands in Content Sharing Resources between LWM2M Endpoints and M2M Applications. • Interworking with full mapping of LWM2M Objects in LWM2M Endpoints to semantically enabled Content Sharing Resources that are utilized by M2M Applications. • Interworking with one-to-one mapping of LWM2M Objects with oneM2M <mgmtObj> resources NOTE: The present document limits Content Sharing Resources to <container> and <contentInstance> resources.
|
118 123
|
oneM2M; Home Appliances Information Model and Mapping (oneM2M TS-0023 version 2.0.2 Release 2A)
|
TS
|
2.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118123/02.00.02_60/ts_118123v020002p.pdf
|
The present document describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model.
|
118 113
|
oneM2M; Interoperability Testing (oneM2M TS-0013 version 3.3.1 Release 3)
|
TS
|
3.3.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118113/03.03.01_60/ts_118113v030301p.pdf
|
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].
|
118 113
|
oneM2M; Interoperability Testing (oneM2M TS-0013 version 2.3.2 Release 2A)
|
TS
|
2.3.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118113/02.03.02_60/ts_118113v020302p.pdf
|
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].
|
118 113
|
oneM2M; Interoperability Testing (oneM2M TS-0013 version 1.0.0 Release 1)
|
TS
|
1.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118113/01.00.00_60/ts_118113v010000p.pdf
|
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].
|
118 112
|
oneM2M; Base Ontology (oneM2M TS-0012 version 3.7.3 Release 3)
|
TS
|
3.7.3
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118112/03.07.03_60/ts_118112v030703p.pdf
|
The present document contains the specification of the oneM2M Base Ontology. A formal OWL representation of the Base Ontology can be found at http://www.onem2m.org/ontology/Base_Ontology. The present document also specifies an instantiation of the Base Ontology in oneM2M resources which can be used for semantic annotation and for ontology based interworking [4]. Finally an example is given how external ontologies can be mapped to the Base Ontology. The example uses the Smart Appliances REFerence (SAREF) ontology (http://ontology.tno.nl/saref).
|
118 112
|
oneM2M; Base Ontology (oneM2M TS-0012 version 2.2.2 Release 2A)
|
TS
|
2.2.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118112/02.02.02_60/ts_118112v020202p.pdf
|
The present document contains the specification of the oneM2M Base Ontology. A formal OWL representation of the Base Ontology can be found at http://www.onem2m.org/ontology/Base_Ontology. The present document also specifies an instantiation of the Base Ontology in oneM2M resources which can be used for semantic annotation and for ontology based interworking [4]. Finally an example is given how external ontologies can be mapped to the Base Ontology. The example uses the Smart Appliances REFerence (SAREF) ontology (http://ontology.tno.nl/saref).
|
118 111
|
oneM2M; Common Terminology (oneM2M TS-0011 version 4.1.1 Release 4)
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118111/04.01.01_60/ts_118111v040101p.pdf
|
The present document contains a collection of specialist technical terms, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: • ensure that the terminology is used in a consistent manner across oneM2M documents; • provide a reader with convenient reference for technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here, or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation. In addition in oneM2M Technical Specifications and Technical Reports there are also clauses dedicated for locally unique definitions and abbreviations.
|
118 111
|
oneM2M; Common Terminology (oneM2M TS-0011 version 2.4.1 Release 2)
|
TS
|
2.4.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118111/02.04.01_60/ts_118111v020401p.pdf
|
The present document contains a collection of specialist technical terms, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: • ensure that the terminology is used in a consistent manner across oneM2M documents; • provide a reader with convenient reference for technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here, or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation. In addition in oneM2M Technical Specifications and Technical Reports there are also clauses dedicated for locally unique definitions and abbreviations.
|
118 111
|
oneM2M Common Terminology
|
TS
|
1.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118111/01.00.00_60/ts_118111v010000p.pdf
|
The present document contains a collection of specialist technical terms, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: • ensure that the terminology is used in a consistent manner across oneM2M documents; • provide a reader with convenient reference for technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here, or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation. In addition in oneM2M Technical Specifications and Technical Reports there are also clauses dedicated for locally unique definitions and abbreviations.
|
118 110
|
oneM2M; MQTT Protocol Binding (oneM2M TS-0010 version 4.0.1 Release 4)
|
TS
|
4.0.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118110/04.00.01_60/ts_118110v040001p.pdf
|
The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests. 4) How that Receiver can formulate and transmit a Response.
|
118 110
|
oneM2M; MQTT Protocol Binding (oneM2M TS-0010 version 3.1.0 Release 3)
|
TS
|
3.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118110/03.01.00_60/ts_118110v030100p.pdf
|
The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests. 4) How that Receiver can formulate and transmit a Response.
|
118 110
|
oneM2M; MQTT Protocol Binding (oneM2M TS-0010 version 2.4.1 Release 2)
|
TS
|
2.4.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118110/02.04.01_60/ts_118110v020401p.pdf
|
The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests. 4) How that Receiver can formulate and transmit a Response.
|
118 110
|
oneM2M; MQTT Protocol Binding (oneM2M TS-0010 version 1.5.1 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118110/01.01.00_60/ts_118110v010100p.pdf
|
The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests. 4) How that Receiver can formulate and transmit a Response.
|
118 109
|
oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 4.4.1 Release 4)
|
TS
|
4.4.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118109/04.04.01_60/ts_118109v040401p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types.
|
118 109
|
oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 3.5.0 Release 3)
|
TS
|
3.5.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118109/03.05.00_60/ts_118109v030500p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types.
|
118 109
|
oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 2.13.1 Release 2A)
|
TS
|
2.13.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118109/02.13.01_60/ts_118109v021301p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types.
|
118 109
|
oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 1.5.1 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118109/01.01.00_60/ts_118109v010100p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types.
|
118 108
|
oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 4.4.1 Release 4)
|
TS
|
4.4.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118108/04.04.01_60/ts_118108v040401p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Codes. • Defining behaviour of a CoAP Client and Server depending on oneM2M parameters.
|
118 108
|
oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 3.6.0 Release 3)
|
TS
|
3.6.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118108/03.06.00_60/ts_118108v030600p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Codes. • Defining behaviour of a CoAP Client and Server depending on oneM2M parameters.
|
118 108
|
oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 2.6.1 Release 2A)
|
TS
|
2.6.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118108/02.06.01_60/ts_118108v020601p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Codes. • Defining behaviour of a CoAP Client and Server depending on oneM2M parameters.
|
118 108
|
oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 1.3.2 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118108/01.01.00_60/ts_118108v010100p.pdf
|
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Codes. • Defining behaviour of a CoAP Client and Server depending on oneM2M parameters.
|
118 106
|
oneM2M; Management Enablement (BBF) (oneM2M TS-0006 version 3.6.2 Release 3)
|
TS
|
3.6.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118106/03.06.02_60/ts_118106v030602p.pdf
|
The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181 [6].
|
118 106
|
oneM2M; Management Enablement (BBF) (oneM2M TS-0006 version 2.2.1 Release 2A)
|
TS
|
2.2.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118106/02.02.01_60/ts_118106v020201p.pdf
|
The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181 [6].
|
118 106
|
oneM2M; Management Enablement (BBF) (oneM2M TS-0006 version 1.1.4 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118106/01.01.00_60/ts_118106v010100p.pdf
|
The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181 [6].
|
118 105
|
oneM2M; Management Enablement (OMA) (oneM2M TS-0005 version 3.5.1 Release 3)
|
TS
|
3.5.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118105/03.05.01_60/ts_118105v030501p.pdf
|
The present document specifies the protocol translation and mappings between the oneM2M Service layer and the management technologies specified by OMA such as OMA DM 1.3 [3], OMA DM 2.0 [4] and OMA LightweightM2M. Note that OMA DM 1.3 [3] and OMA DM 2.0 [4] are collectively referenced as OMA DM in the present document.
|
118 105
|
oneM2M; Management Enablement (OMA) (oneM2M TS-0005 version 2.0.2 Release 2A)
|
TS
|
2.0.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118105/02.00.02_60/ts_118105v020002p.pdf
|
The present document specifies the protocol translation and mappings between the oneM2M Service layer and the management technologies specified by OMA such as OMA DM 1.3 [3], OMA DM 2.0 [4] and OMA LightweightM2M. Note that OMA DM 1.3 [3] and OMA DM 2.0 [4] are collectively referenced as OMA DM in the present document.
|
118 105
|
oneM2M; Management Enablement (OMA) (oneM2M TS-0005 version 1.4.1 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118105/01.01.00_60/ts_118105v010100p.pdf
|
The present document specifies the protocol translation and mappings between the oneM2M Service layer and the management technologies specified by OMA such as OMA DM 1.3 [3], OMA DM 2.0 [4] and OMA LightweightM2M. Note that OMA DM 1.3 [3] and OMA DM 2.0 [4] are collectively referenced as OMA DM in the present document.
|
118 104
|
oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004 version 2.7.1 Release 2)
|
TS
|
2.7.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118104/02.07.01_60/ts_118104v020701p.pdf
|
The present document specifies the communication protocol(s) for oneM2M compliant Systems, M2M Applications, and/or other M2M systems. The present document also specifies the common data formats, interfaces and message sequences to support reference points(s) defined by oneM2M.
|
118 104
|
oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004 version 1.6.0 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118104/01.01.00_60/ts_118104v010100p.pdf
|
The present document specifies the communication protocol(s) for oneM2M compliant Systems, M2M Applications, and/or other M2M systems. The present document also specifies the common data formats, interfaces and message sequences to support reference points(s) defined by oneM2M.
|
118 103
|
<empty>
|
TS
|
3.13.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118103/03.13.00_60/ts_118103v031300p.pdf
|
The present document defines security solutions applicable within the M2M system.
|
118 103
|
oneM2M; Security solutions (oneM2M TS-0003 version 2.12.1 Release 2A)
|
TS
|
2.12.1
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118103/02.12.01_60/ts_118103v021201p.pdf
|
The present document defines security solutions applicable within the M2M system.
|
118 103
|
oneM2M; Security solutions (oneM2M TS-0003 version 1.4.2 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118103/01.01.00_60/ts_118103v010100p.pdf
|
The present document defines security solutions applicable within the M2M system.
|
118 102
|
<empty>
|
TS
|
3.1.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118102/03.01.02_60/ts_118102v030102p.pdf
|
The present document contains an informative functional role model and normative technical requirements for oneM2M.
|
118 102
|
oneM2M; Requirements (oneM2M TS-0002 version 2.10.2 Release 2A)
|
TS
|
2.10.2
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118102/02.10.02_60/ts_118102v021002p.pdf
|
The present document contains an informative functional role model and normative technical requirements for oneM2M.
|
118 102
|
oneM2M Requirements
|
TS
|
1.0.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118102/01.00.00_60/ts_118102v010000p.pdf
|
The present document contains an informative functional role model and normative technical requirements for oneM2M.
|
118 101
|
oneM2M; Functional Architecture (oneM2M TS-0001 version 4.15.0 Release 4)
|
TS
|
4.15.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118101/04.15.00_60/ts_118101v041500p.pdf
|
The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services.
|
118 101
|
<empty>
|
TS
|
3.22.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118101/03.22.00_60/ts_118101v032200p.pdf
|
The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services.
|
118 101
|
oneM2M; Functional Architecture (oneM2M TS-0001 version 2.10.0 Release 2)
|
TS
|
2.10.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118101/02.10.00_60/ts_118101v021000p.pdf
|
The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services.
|
118 101
|
oneM2M; Functional Architecture (oneM2M TS-0001 version 1.13.1 Release 1)
|
TS
|
1.1.0
|
http://www.etsi.org/deliver/etsi_ts/118100_118199/118101/01.01.00_60/ts_118101v010100p.pdf
|
The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services.
|
110 174-2-2
|
Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Broadband Deployment and Energy Management; Part 2: Multiservice Networking Infrastructure and Associated Street Furniture; Sub-part 2: The use of lamp-posts for hosting sensing devices and 5G networking
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/110100_110199/1101740202/01.02.01_60/ts_1101740202v010201p.pdf
|
The present document addresses the opportunities and challenges offered by the use of lamp-posts to provide facilities supporting services required by sustainable digital multiservice cities and communities. The replacement of existing luminaires by LED light sources offers an opportunity to increase the functionality provided by the lamp-posts - beginning with improved operational control of the lighting provided. However, additional functionality can be supported by simultaneous installation of an electronics package to enable the lamp-post to host sensing devices. The present document describes the functions to be supported by this package together with consideration of power supply to any hosted sensing devices. A more comprehensive replacement approach includes the incorporation of 5G services by the separate installation of wireless network components acting as a Remote Radio Unit (RRU). The present document describes the technical challenges associated with the physical installation, provision of power, cabling and other infrastructures necessary to meet the required level of availability for these services.
|
110 174-2-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Cities; Broadband Deployment and Energy Management; Part 2: Multiservice Networking Infrastructure and Associated Street Furniture; Sub-part 1: General requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/110100_110199/1101740201/01.01.01_60/ts_1101740201v010101p.pdf
|
The present document details measures which may be taken to ease the deployment of smart new services and their multiservice street furniture of digital multiservice city within the IP network of a single city or an association of cities administratively clustered. Furthermore, the suggested measures will enable to engineer a reliable common networking infrastructure which can improve the Total Cost of Ownership (TCO) for the public administration while improving the energy efficiency of the overall deployment. The present document also lists the requirements which have led to this common architecture. Clause 4 presents a suggestion of an engineered digital multiservice city. Clause 5 introduces the active role categorized urban assets can play in the delivery of digital services across the territory of the city. Clause 6 reviews the spread efforts within the standardization organizations for the digital multiservice city. Clause 7 suggests both the common engineering required to transform an urban asset into an active network nodes of the digital multiservice city while presenting a concrete illustration of network design for one of the categories. This will enable the proper introduction and implementation of a new service, application or content within the city digital portfolio on a unified energy efficient network, though it is not the goal of the present document to provide detailed standardized solutions for network architecture.
|
110 174-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Cities (SDMC); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects of societal and technical pillars for sustainability
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/110100_110199/11017401/01.01.01_60/ts_11017401v010101p.pdf
|
The present document introduces the common and generic aspects of the societal and technical pillars to achieve sustainability objectives behind the deployment of smart new services within the IP network of a single city or an association of cities administratively clustered. Clause 4 identifies and presents a general overview of a city from small entity to significantly large municipality clustering several cities and villages. Clause 5 presents the pursued objectives behind the concept of smart city. Clause 6 describes the general theoretical pillars which bear the engineering requirements to deploy a digital multi service city. Clause 7 identifies the general needs from the cities.
|
105 388
|
Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Asymmetric Digital Subscriber Line (ADSL2plus) - European specific requirements [ITU-T Recommendation G.992.5 modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/105300_105399/105388/01.01.01_60/ts_105388v010101p.pdf
|
The present document specifies European requirements for ADSL2plus. The present document endorses ITU-T Recommendation G.992.5 [1] and amendments 1 [2], 2 [3] and 3 [4], the contents of which apply together with the addition of the modifications being covered herein, to the exclusion of annex C of G.992.5. In particular the aspects covered by the present document are related to: 1) Define INP values as mandatory. 2) Define specific European tests. 3) Define mandatory S&D values. 4) Define mandatory support of extended interleaving memory.
|
105 200-3-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Operational infrastructures; Implementation of Global KPIs; Part 3: ICT Sites; Sub-part 1: DCEM
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/105200_105299/1052000301/01.02.01_60/ts_1052000301v010201p.pdf
|
The reporting of Global KPIs in accordance with ETSI EN 305 200-3-1 [2] requires the collection of data to enable the calculation of the following aspects: • objective KPI relating to the total energy consumption (KPIEC); • objective KPI relating to the use of energy performance (KPIEP) which combines KPIEC with other measurements of energy consumption to provide Objective KPIs related to task efficiency (KPITE), the reuse of energy (KPIREUSE) and the use of renewable energy (KPIREN). The present document supports the requirements of ETSI EN 305 200-3-1 [2] providing a framework for, and detailing, the implementation procedures including any necessary techniques for estimation of energy consumption together with constants to be employed for weighting and banding purposes.
|
105 200-2-3
|
Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Operational infrastructures; Implementation of Global KPIs; Part 2: Specific requirements; Sub-part 3: Mobile broadband access networks
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/105200_105299/1052000203/01.02.01_60/ts_1052000203v010201p.pdf
|
The reporting of Global KPIs in accordance with ETSI EN 305 200-2-3 [2] requires the collection of data to enable the calculation of the following aspects: • Objective KPI relating to task efficiency (KPITE) based on data_volume and total energy consumption (KPIEC). • Objective KPI relating to the use of renewable energy (KPIREN). The present document supports the requirements of ETSI EN 305 200-2-3 [2] providing a framework for, and detailing, the implementation procedures including any necessary techniques for estimation of energy consumption together with clarification and treatment of different types of data volume.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.