hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.1 Introduction | The present clause specifies how to name the files which define data types in XSD for Device and SubDevice models, ModuleClasses, Actions and enumerated types. Seven SDT domains correspond to different vertical, economic domains (Agriculture, Smart City, Health, Home, Industry, Railway, Vehicular), they contain devices... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.2 XSD definitions for Device models | The XSD definitions for Device models are specified upon the following rule: • Rule: [Domain Prefix]-[device name]-v<TS-version>.xsd where the string '<TS-version>' shall be interpreted as the version of the present document. For example, the XSD definition for deviceAirConditioner specified in TS-0023 v4.3.0 shall be ... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.3 XSD definitions for ModuleClass | The XSD definitions for ModuleClass are specified upon the following rule: • Rule: [Domain Prefix]-mod-[ModuleClass name]-v<TS-version>.xsd where the string '<TS-version>' shall be interpreted as the version of the present document. ETSI ETSI TS 118 123 V4.8.1 (2024-02) 119 oneM2M TS-0023 version 4.8.1 Release 4 For ex... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.4 XSD definitions for Action | The XSD definitions for Actions are specified upon the following rule: • Rule: [Domain Prefix]-act-[action name]-v<TS-version>.xsd where the string '<TS-version>' shall be interpreted as the version of the present document. For example, the XSD definition for activateClockTimer specified in TS-0023 v4.3.0 shall be "HOD... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.5 XSD definitions for SubDevices | The XSD definitions for SubDevices are specified upon the following rule: • Rule: [Domain Prefix]-[SubDevice name]-v<TS-version>.xsd where the string '<TS-version>' shall be interpreted as the version of the present document. For example, the XSD definition for subDeviceCuff specified in TS-0023 v4.3.0 shall be "COD-su... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 6.5.6 XSD definitions for Enumerated Types | The XSD definitions for enumerated types are specified upon the following rule: • Rule: HD-enumerationTypes-v<TS-version>.xsd where the string '<TS-version>' shall be interpreted as the version of the present document. This file contains the definitions of all enumerated types, and nothing else. 7 Mapping with Other In... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.0 Introduction | This clause specifies how the Home Appliance Information Model (HAIM) defined in clause 5 of the present document can be mapped with existing external models from , OCF, ECHONET, OMA GotAPI etc. and introduction of these models is written in annex B. The mapping shall be to enable the interworking between the oneM2M sy... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1 OMA GotAPI (DWAPI) | |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.1 Introduction | The following clauses are intended to specify the mapping relationship between HAIM and OMA DWAPI with tables. OMA Device Web Application Programming Interface (DWAPI) [7] is based on OMA Generic Open Terminal Application Programming Interface (GotAPI) [19] and supports Personal Healthcare Devices (DWAPI-PCH) and 3D pr... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2 Device Models | |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.1 device3Dprinter | The device3Dprinter of HAIM shall be mapped to 3D printer of OMA DWAPI-3DP on the basis of Table 7.1.2-1. Table 7.1.2.1-1: Map of device3Dprinter of oneM2M HAIM to OMA DWAPI-3DP ModuleClass Data Points of oneM2M HAIM Data objects of OMA DWAPI-3DP Description binarySwitch powerState - See clause 5.3.1.12. The powerState... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.2 deviceBloodPressureMonitor | DeviceBloodPressureMonitor of HAIM shall be mapped to Blood Pressure Monitor of OMA DWAPI-PCH on the basis of Table 7.1.2.2-1. Table 7.1.2.2-1: Map of deviceBloodPressureMonitor of oneM2M HAIM to OMA DWAPI-PCH ModuleClass DataPoints of oneM2M HAIM Data objects of OMA DWAPI-PCH Description sphygmomanometer diastolicPres... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.3 deviceGlucosemeter | DeviceGlucometer of HAIM shall be mapped to Glucometer of OMA DWAPI-PCH on the basis of Table 7.1.2.3-1. Table 7.1.2.3-1: Map of deviceGlucometer of oneM2M HAIM to OMA DWAPI-PCH ModuleClass DataPoints of oneM2M HAIM Data objects of OMA DWAPI-PCH Description glucometer concentration concentration See clause 5.3.1.42. hb... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.4 devicePulseOximeter | DevicePulseOximeter of HAIM shall be mapped to Pulse Oximeter of OMA DWAPI-PCH on the basis of Table 7.1.2.4-1. Table 7.1.2.4-1: Map of devicePulseOximeter of oneM2M HAIM to OMA DWAPI-PCH ModuleClass DataPoints of oneM2M HAIM Data objects of OMA DWAPI-PCH Description pulsemeter modality spo2, pulse See clause 5.3.1.68.... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.5 deviceThermometer | DeviceTermometer of HAIM shall be mapped to Thermometer of OMA DWAPI-PCH on the basis of Table 7.1.2.5-1. ETSI ETSI TS 118 123 V4.8.1 (2024-02) 123 oneM2M TS-0023 version 4.8.1 Release 4 Table 7.1.2.5-1: Map of deviceThermometer of oneM2M HAIM to OMA DWAPI-PCH ModuleClass Data Points of oneM2M HAIM Data objects of OMA ... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.6 deviceWeightScaleAndBodyCompositionAnalyser | DeviceWeightScaleAdBodyCompositionAnalyser of HAIM shall be mapped to Weight Scale Body Composition Analyser of OMA DWAPI-PCH on the basis of Table 7.1.2.6-1. Table 7.1.2.6-1: Map of deviceWeightScaleAdBodyCompositionAnalyser of oneM2M HAIM to OMA DWAPI-PCH ModuleClass DataPoints of oneM2M HAIM Data objects of OMA DWAP... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.2.7 deviceHeartRateMonitor | DeviceHeartRateMonitor of HAIM shall be mapped to Heart Rate Monitor of OMA DWAPI-PCH on the basis of Table 7.1.2.7-1. ETSI ETSI TS 118 123 V4.8.1 (2024-02) 124 oneM2M TS-0023 version 4.8.1 Release 4 Table 7.1.2.7-1: Map of deviceHeartRateMonitor of oneM2M HAIM to OMA DWAPI-PCH ModuleClass DataPoints of oneM2M HAIM Dat... |
e6ebfc519c3e089619ef5d1ffe3caa64 | 118 123 | 7.1.3 Data Types | Data types of oneM2M HAIM and OMA DWAPI-PCH shall be mapped each other on the basis of Table 7.1.3-1. Table 7.1.3-1: Map of data types between oneM2M and OMA DWAPI-PCH oneM2M data type Mapping to data type in OMA DWAPI Description xs:integer int, number, string Data type for 32-bit signed integer. For indicating 3D pri... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 1 Scope | 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 interopera... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 2 References | |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 3 Definitions and abbreviations | |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.2] and the following apply: negative test case: test case for a signature whose validation according to ETSI EN 319 102-1 [i.3] would not result in TOTAL-PASSED |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] apply. |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 4 Overview | This clause describes the overall approach used throughout the present document to specify test suites for CAdES baseline signatures interoperability testing. ETSI EN 319 122-1 [1] defines four different levels of CAdES baseline signatures. The test suites are defined with different layers reflecting the levels of CAdE... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 5 Testing interoperability of CAdES-B-B signatures | The test cases in this clause have been defined for different combinations of CAdES-B-B signatures attributes. Mandatory attributes for CAdES-B-B signatures described in [1], clause 6.3, shall be present. Table 1 shows which attributes are required to generate CAdES-B-B signatures for each test case. ETSI ETSI TS 119 1... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 6 Testing interoperability of CAdES-B-T signatures | The test cases in this clause have been defined for different combinations of CAdES-B-T signatures attributes. CAdES baseline signatures claiming conformance to B-T level of document [1] shall be built on baseline signatures conformant to B-B level. A CAdES baseline signature conformant to B-T level shall be a baseline... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 7 Testing interoperability of CAdES-B-LT signatures | The test cases in this clause have been defined for different combinations of CAdES-B-LT signatures attributes. CAdES baseline signatures claiming conformance to B-LT level of document [1] shall be built on baseline signatures conformant to B-T level. A CAdES baseline signature conformant to B-LT level shall be a basel... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 8 Testing interoperability of CAdES-B-LTA signatures | The test cases in this clause have been defined for different combinations of CAdES-B-LTA signatures attributes. CAdES baseline signatures claiming conformance to B-LTA level of document [1] shall be built on baseline signatures conformant to B-LT level. A CAdES baseline signature conformant to B-LTA level shall be a b... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 10 Negative test cases for CAdES baseline signatures | |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 10.1 CAdES-B-B signatures test cases | The test cases in this clause have been defined for CAdES-B-B signatures. Table 6 summarizes negative test cases for CAdES-B-B signatures. Table 6: Negative test cases for CAdES-B-B signatures TC ID Description Pass criteria Signature attributes CAdES/BBN/1 Verify a CAdES-B-B signature that DOES NOT CONTAIN the mandato... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 10.2 CAdES-B-T signatures test cases | The test cases in this clause have been defined for CAdES-B-T signatures. Table 7 summarizes negative test cases for CAdES-B-T signatures. Table 7: Negative test cases for CAdES-B-T signatures TC ID Description Pass criteria Signature attributes CAdES/BTN/1 Verify a CAdES-B-T signature in which, at the time in Signatur... |
8c6aa05a3ff29e7e35f3f09979852c3d | 119 124-2 | 10.3 CAdES-B-LTA signatures test cases | The test cases in this clause have been defined for CAdES-B-LTA signatures. Table 8 summarizes negative test cases for CAdES-B-LTA signatures. Table 8: Negative test cases for CAdES-B-LTA signatures TC ID Description Pass criteria Signature attributes CAdES/BLTAN/1 Verify a CAdES-B-LTA signature in which the time in th... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 1 Scope | 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 includ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 2 References | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 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... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 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... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 3 Definition of terms, symbols and abbreviations | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and the following apply: application configuration: procedure that configures an AE on an M2M Node in the Field Domain for M2M Service Layer operation authentication profile: security information needed to establish mu... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 3.2 Symbols | Void. |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and the following apply: NP Not Present XML eXtensible Markup Language XSD XML Schema Definition |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 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]. ETSI ETSI TS 118 122 V4.5.1 (2023-07) 8 oneM2M TS-0022 version 4.5.1 Release 4 |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 5 Introduction | Devices in the Field Domain that host oneM2M AEs and CSEs require configuration that permits the AE or CSE to successfully operate in the M2M Service Layer. ETSI TS 118 101 [2] and ETSI TS 118 103 [3] specifies much of what is needed to configure these devices in the Field Domain (i.e. ADN, ASN/MN). Specifically, ETSI ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6 Architectural Aspects | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.1 Introduction | The information needed by the remote AE or CSE in the field domain to establish M2M Service Layer operation uses the architectural aspects of ETSI TS 118 101 [2] in order to convey the information elements to the ASN/MN or ADN nodes that host the AE or CSE prior to or during M2M Service Layer operation and to the AE or... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2 Information needed for M2M Service Layer operation | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.1 Introduction | The Configuration AE provisions the <mgmtObj> resource types in the IN-CSE and the IN-CSE then interacts with the DM Server, ADN or ASN/MN node or Configuration IPE in order to configure the AE or CSE on the nodes. |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2 Information elements required for M2M Service Layer operation | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.1 Introduction | The ASN/MN and ADN in the Field Domain should support the capability to be configured with the <mgmtObj> resource types defined in the present document prior to initial registration with a registrar CSE (enrolment phase). When the AE or CSE has established M2M Service Layer operation with a Registrar CSE (operational p... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.2 M2M Service Layer registration information elements | The information elements used for CSE or AEs to register with a Registrar CSE shall include the following information which depends on the M2M Service Provider: • PoA information of Registrar CSE. • Protocol binding to be used between AE or CSE and the Registrar CSE. • CSE-ID of the CSE hosted on the ASN/MN. • AE-ID of... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.3 Application configuration information elements | In order for an AE to operate, the AE may need to know the resource location within the Hosting CSE to maintain its resource structure. In addition, for resources that are frequently provided by the AE to the Hosting CSE, the AE may be configured with information that defines how frequently the AE collects or measures ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.4 Authentication profile information elements | Authentication profile information elements may be required to establish mutually-authenticated secure communications. The applicable security framework is identified via a Security Usage Identifier (SUID). Where the security framework uses TLS or DTLS, a set of permitted TLS cipher suites may be provided. Then the app... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.5 My certificate file credential information elements | A security framework can use a certificate to authenticate the intended security principal in the Managed Entity to other security principals, as part of establishing mutually-authenticated secure communications. The certificate can be pre-provisioned or remotely provisioned, as discussed in ETSI TS 118 103 [3]. If a c... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.6 Trust anchor credential information elements | A security framework can use one or more trust anchor certificates (also known as "root Certificate Authority certificates" or" root of trust certificates"). These trust anchor certificates are used by a security principal on the Managed Entity for validating certificates of other security principals as part of establi... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.7 MAF Client registration configuration information elements | A security framework can use a MAF to establish symmetric key in a security principal in the Managed Entity and one or more other security principals, with the symmetric key used for establishing mutually-authenticated secure communications between the security principals. In this case, the security principals are MAF ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 6.2.2.8 MEF Client registration configuration information elements | A security framework can use a MEF to provision credentials to a security principal (an MEF Client) in the Managed Entity for establishing mutually-authenticated secure communications between the security principal and another entity such as a security principal or MAF or MEF or device management server. The security p... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7 Resource type and data format definitions | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1 <mgmtObj> Resource type specializations | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.1 Introduction | The present clause specifies <mgmtObj> resource specializations used to configure AEs or CSEs on ADN or ASN/MN nodes in the Field Domain in order to establish M2M Service Layer operation. Table 7.1.1-1 shows a summary of <mgmtObj> resource specializations defined in the present document. Table 7.1.1-1: Summary of defin... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.2 Resource [registration] | This specialization of <mgmtObj> is used to convey the service layer configuration information needed to register an AE or CSE with a Registrar CSE. The [registration] resource shall contain the child resource specified in table 7.1.2-1. ETSI ETSI TS 118 122 V4.5.1 (2023-07) 13 oneM2M TS-0022 version 4.5.1 Release 4 Ta... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.3 Resource [dataCollection] | This specialization of <mgmtObj> is used to convey the application configuration information needed by an AE to collect data and then transmit the data to a Hosting CSE. The [dataCollection] resource shall contain the child resource specified in table 7.1.3-1. Table 7.1.3-1: Child resources of [dataCollection] resource... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.4 Resource [authenticationProfile] | The [authenticationProfile] specialization of the <mgmtObj> is used to convey the configuration information regarding establishing mutually-authenticated secure communications. The security principal using this configuration information can be a CSE or AE or the Managed ADN/ASN/MN acting as security principal on behalf... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.5 Resource [myCertFileCred] | This <mgmtObj> specialization is used to configure a certificate or certificate chain which the Managed Entity knows the private key. The [myCertFileCred] resource shall contain the child resource specified in table 7.1.5-1. Table 7.1.5-1: Child resources of [myCertFileCred] resource Child Resources of [myCertFileCred]... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.6 Resource [trustAnchorCred] | The [trustAnchorCred] <mgmtObj> specialization is read by AEs or CSEs on ADN or ASN/MN nodes in the Field Domain. A [trustAnchorCred] is configured as a child or children of [authenticationProfile] resources by means of a mgmtLink. A security principal acting on a [authenticationProfile] uses the information in the ass... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.7 Resource [MAFClientRegCfg] | This <mgmtObj> specialization is used to convey instructions regarding the MAF Client Registration procedure (clause 8.8.2.3 of ETSI TS 118 103 [3]). The [MAFClientRegCfg] resource shall contain the child resource specified in table 7.1.7-1. Table 7.1.7-1: Child resources of [MAFClientRegCfg] resource Child Resources o... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.8 Resource [MEFClientRegCfg] | This <mgmtObj> specialization is used to convey instructions regarding the MEF Client Registration procedure (clause 8.3.5.2.3 of ETSI TS 118 103 [3]). The [MEFClientRegCfg] resource shall contain the child resource specified in table 7.1.8-1. Table 7.1.8-1: Child resources of [MEFClientRegCfg] resource Child Resources... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.9 Resource [OAuth2Authentication] | This specialization of <mgmtObj> is used to store access token and refresh token used in OAuth2 security protocol The [OAuth2Authentication] resource shall contain the child resources specified in table 7.1.9-1. Table 7.1.9-1: Child resources of [OAuth2Authentication] resource Child Resources of [OAuth2Authentication] ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.1.10 Resource [wifiClient] | This specialization of <mgmtObj> is used to store configuration of Wi-Fi® connection on the client device. The [wifiClient] resource shall contain the child resources specified in table 7.1.10-1. Table 7.1.10-1: Child resources of [wifiClient] resource Child Resources of [wifiClient] Child Resource Type Multiplicity De... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2 Resource-Type specific procedures and definitions | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.1 Introduction | The present clause defines the resource-type specific details of the resource representations and protocol procedures for each <mgmtObj> specialization defined in clause 7.1. ETSI ETSI TS 118 122 V4.5.1 (2023-07) 24 oneM2M TS-0022 version 4.5.1 Release 4 |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.2 Resource [registration] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.2.1 Introduction | This specialization of <mgmtObj> is used to convey the service layer configuration information needed to register an AE or CSE with a Registrar CSE. Table 7.2.2.1-1: Data Type Definition of [registration] Data Type ID File Name Note registration DCFG-registration.xsd Table 7.2.2.1-2: Resource specific attributes of [re... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.2.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. In addition to the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource following check shall be done in... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.3 Resource [dataCollection] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.3.1 Introduction | Table 7.2.3.1-1: Data Type Definition of [dataCollection] Data Type ID File Name Note dataCollection DCFG-dataCollection.xsd Table 7.2.3.1-2: Resource specific attributes of [dataCollection] Attribute Name Request Optionality Data Type Default Value and Constraints Create Update mgmtDefinition M NP See clause 7.4.15 of... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.3.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.4 Resource [authenticationProfile] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.4.1 Introduction | Table 7.2.4.1-1: Data Type Definition of [authenticationProfile] Data Type ID File Name Note authenticationProfile DCFG-authenticationProfile.xsd Table 7.2.4.1-2: Resource specific attributes of [authenticationProfile] Attribute Name Request Optionality Data Type Default Value and Constraints Create Update mgmtDefiniti... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.4.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.5 Resource [myCertFileCred] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.5.1 Introduction | Table 7.2.5.1-1: Data Type Definition of [myCertFileCred] Data Type ID File Name Note myCertFileCred DCFG-myCertFileCred.xsd Table 7.2.5.1-2: Resource specific attributes of [myCertFileCred] Attribute Name Request Optionality Data Type Default Value and Constraints Create Update mgmtDefinition M NP See clause 7.4.15 of... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.5.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.6 Resource [trustAnchorCred] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.6.1 Introduction | Table 7.2.6.1-1: Data Type Definition of [trustAnchorCred] Data Type ID File Name Note trustAnchorCred DCFG-trustAnchorCred.xsd ETSI ETSI TS 118 122 V4.5.1 (2023-07) 28 oneM2M TS-0022 version 4.5.1 Release 4 Table 7.2.6.1-2: Resource specific attributes of [trustAnchorCred] Attribute Name Request Optionality Data Type ... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.6.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.7 Resource [MAFClientRegCfg] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.7.1 Introduction | Table 7.2.7.1-1: Data Type Definition of [MAFClientRegCfg] Data Type ID File Name Note MAFClientRegCfg DCFG-MAFClientRegCfg.xsd Table 7.2.7.1-2: Resource specific attributes of [MAFClientRegCfg] Attribute Name Request Optionality Data Type Default Value and Constraints Create Update mgmtDefinition M NP See clause 7.4.1... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.7.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.8 Resource [MEFClientRegCfg] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.8.1 Introduction | Table 7.2.8.1-1: Data Type Definition of [MEFClientRegCfg] Data Type ID File Name Note MEFClientRegCfg DCFG-MEFClientRegCfg.xsd Table 7.2.8.1-2: Resource specific attributes of [MEFClientRegCfg] Attribute Name Request Optionality Data Type Default Value and Constraints Create Update mgmtDefinition M NP See clause 7.4.1... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.8.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4], '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. ETSI TS 118 105 [5] an... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.9 Resource [OAuth2Authentication] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.9.1 Introduction | 7.2. |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 9.1 Introduction | This specialization of <mgmtObj> is used to store access token and refresh token used in OAuth2 security protocol Table 7.2.9.1-1: Data Type Definition of [OAuth2Authentication] Data Type ID File Name Note OAuth2Authentication DCFG-OAuth2.xsd Table 7.2.9.1-2: Resource specific attributes of [OAuth2Authentication] Attri... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.9.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 in ETSI TS 118 104 [4],'<mgmtObj> specific procedures' shall be used. There are no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource. |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.10 Resource [wifiClient] | |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.10.1 Introduction | This specialization of <mgmtObj> is used to store configuration of Wi-Fi® connection on the client device. Table 7.2.10.1-1: Data Type Definition of [wifiClient] Data Type ID File Name Note wifiClient DCFG-wifiClient.xsd ETSI ETSI TS 118 122 V4.5.1 (2023-07) 31 oneM2M TS-0022 version 4.5.1 Release 4 Table 7.2.10.1-2: R... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.2.10.2 Resource specific procedure on CRUD operations | When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of ETSI TS 118 104 [4],'<mgmtObj> specific procedures' shall be used. There are no change from the generic procedures in clause 7.2.2 of ETSI TS 118 104 [4] for operations on this resource except retrieve operati... |
ebce105b6d97ede43cea618c70172b77 | 118 122 | 7.3 Data formats for device configuration |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.