diff --git a/TS-0022-Field_Device_Configuration.md b/TS-0022-Field_Device_Configuration.md index 9b69c0b89615e8651dbf262bff271ede0fc49752..478f5f1150b327388467b802c06c52ad3259a3d6 100644 --- a/TS-0022-Field_Device_Configuration.md +++ b/TS-0022-Field_Device_Configuration.md @@ -1,21 +1,12 @@ - - - - - - - - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> + +---------------------------------------------------+------------------------------------+ -| **oneM2M**\ | -| **Technical** **Specification** | +| oneM2M\ | +| Technical Specification | +:==================================================+:===================================+ | Document Number | TS-0022-V5\_1\_0 | +---------------------------------------------------+------------------------------------+ -| Document Name: | Field Device Configuration\ | -| | | +| Document Name: | Field Device Configuration | +---------------------------------------------------+------------------------------------+ | Date: | 2024-12-24 | +---------------------------------------------------+------------------------------------+ @@ -25,25 +16,12 @@ +---------------------------------------------------+------------------------------------+ - - - - - - - - - - The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this specification. The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices. - - - -<br />About oneM2M +About oneM2M The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. @@ -57,8 +35,6 @@ All rights reserved. The copyright extends to reproduction in all media. - - Notice of Disclaimer & Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. @@ -69,8 +45,8 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA # Contents - # 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 includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation. @@ -90,27 +66,27 @@ The following referenced documents are necessary for the application of the pres - <a name="_ref_6">[6]</a> oneM2M TS-0006: "Management Enablement (BBF)". - <a name="_ref_7">[7]</a> IETF RFC 6920: "Naming Things with Hashes". - <a name="_ref_8">[8]</a> IANA Transport Layer Security (TLS) Parameters. -> NOTE: Available at [http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml](http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml). +> NOTE: Available at [http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml](http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml). - <a name="_ref_9">[9]</a> oneM2M TS-0032: "MAF and MEF Interface Specification". - <a name="_ref_10">[10]</a> FIPS PUB 180-4: "Secure Hash Standard (SHS)". > NOTE: Available at [http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf](http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf). - <a name="_ref_11">[11]</a> OMA LightweightM2M (LwM2M) Object and Resource Registry - Connection Monitoring -`NOTE: Available at https://technical.openmobilealliance.org/OMNA/LwM2M/LwM2MRegistry.html <a href="#_ref_12">[12]</a> 3GPP Specification #: 44.018 - Mobile radio interface layer 3 specification; GSM/EDGE Radio Resource Control (RRC) protocol` -`NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2686 <a href="#_ref_13">[13]</a> 3GPP Specification #: 36.214 - Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements` -`NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2428` +>NOTE: Available at https://technical.openmobilealliance.org/OMNA/LwM2M/LwM2MRegistry.html <a href="#_ref_12">[12]</a> 3GPP Specification #: 44.018 - Mobile radio interface layer 3 specification; GSM/EDGE Radio Resource Control (RRC) protocol +>NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2686 <a href="#_ref_13">[13]</a> 3GPP Specification #: 36.214 - Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements +>NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2428 - <a name="_ref_14">[14]</a> 3GPP Specification #: 23.003 - Numbering, addressing and identification -`NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729` +NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=729 - <a name="_ref_15">[15]</a> 3GPP Specification #: 24.008 - Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 -`NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1015` +>NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1015 - <a name="_ref_16">[16]</a> 3GPP Specification #: 36.331 - Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification -`NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2440` +>NOTE: Available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2440 - <a name="_ref_17">[17]</a> 3GPP Specification #: 36.213 - Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures -`NOTE: Available at [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2427](https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2427)` +>NOTE: Available at [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2427](https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2427) - <a name="_ref_18">[18]</a> ETSI TS 102 221: "Smart Cards; UICC-Terminal interface; Physical and logical characteristics" -`NOTE: Available at https://www.etsi.org/deliver/etsi\_ts/102200\_102299/102221/15.00.00\_60/ts\_102221v150000p.pdf` -> +>NOTE: Available at https://www.etsi.org/deliver/etsi_ts/102200_102299/102221/15.00.00_60/ts_102221v150000p.pdf + ## 2.2 Informative references @@ -118,10 +94,8 @@ References are either specific (identified by date of publication and/or edition The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. - - <a name="_ref_i.1">[i.1]</a> oneM2M Drafting Rules. -> NOTE: Available at [http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf](http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf). - + > NOTE: Available at [http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf](http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf). - <a name="_ref_i.2">[i.2]</a> Broadband Forum TR-069: "CPE WAN Management Protocol Issue": 1 Amendment 5, November 2013. - <a name="_ref_i.3">[i.3]</a> OMA-DM: "OMA Device Management Protocol", Version 1.3, Open Mobile Alliance. - <a name="_ref_i.4">[i.4]</a> LWM2M: "OMA LightweightM2M", Version 1.0, Open Mobile Alliance. @@ -132,21 +106,16 @@ The following referenced documents are not necessary for the application of the For the purposes of the present document, the terms given in oneM2M TS-0011 <a href="#_ref_1">[1]</a> and oneM2M TS0001 <a href="#_ref_2">[2]</a> and the following apply: -**a** **pplication** **c** **onfiguration** **:** procedure that configures an AE on an M2M Node in the Field Domain for M2M Service Layer operation - -**a** **uthentication** **p** **rofile** **:** security information needed to establish mutually-authenticated secure communications - -**c** **onfigur** **ation** **AE** **:** AE whose role is to configure the M2M System, including the M2M Node in the Field Domain +**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 mutually-authenticated secure communications +**configuration AE** : AE whose role is to configure the M2M System, including the M2M Node in the Field Domain +**configuration IPE** : IPE that provides the capability to configure the M2M Node in the Field Domain by interworking the exchange of information between the M2M Node and the M2M System +**credential object** : end-point of a security protocol +**(oneM2M) security principal** : CSE or AE or Node or M2M Device which can be authenticated -**c** **onfiguration** **IPE** **:** IPE that provides the capability to configure the M2M Node in the Field Domain by interworking the exchange of information between the M2M Node and the M2M System +> NOTE: When the Security Principal is a Node or M2M Device, then Node or M2M Device is acting on behalf of the CSE and/or AE executing on the Node or M2M Device. -**c** **redential** **object:** end-point of a security protocol - -**(oneM2M) security principal** **:** CSE or AE or Node or M2M Device which can be authenticated - -> NOTE: When the Security Principal is a Node or M2M Device, then Node or M2M Device is acting on behalf of the CSE and/or AE executing on the Node or M2M Device. - -**s** **ervice** **l** **ayer** **c** **onfiguration** **:** procedure that configures a CSE on an M2M Node in the Field Domain for M2M Service Layer operation +**service layer configuration** : procedure that configures a CSE on an M2M Node in the Field Domain for M2M Service Layer operation ## 3.2 Symbols @@ -156,7 +125,6 @@ Void. ## 3.3 Abbreviations For the purposes of the present document, the abbreviations given in oneM2M TS-0011 <a href="#_ref_1">[1]</a>, oneM2M TS-0001 <a href="#_ref_2">[2]</a> and the following apply: - `NP Not Present` `XML eXtensible Markup Language` `XSD XML Schema Definition` @@ -167,8 +135,8 @@ The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in # 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. oneM2M TS-0001 <a href="#_ref_2">[2]</a> and oneM2M TS-0003 <a href="#_ref_3">[3]</a> specifies much of what is needed to configure these devices in the Field Domain (i.e. ADN, ASN/MN). Specifically, oneM2M TS0001 <a href="#_ref_2">[2]</a> provides: +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. oneM2M TS-0001 <a href="#_ref_2">[2]</a> and oneM2M TS-0003 <a href="#_ref_3">[3]</a> specifies much of what is needed to configure these devices in the Field Domain (i.e. ADN, ASN/MN). Specifically, oneM2M TS0001 <a href="#_ref_2">[2]</a> provides: - Guidance on how a CSE is minimally provisioned in Annex E of the specification including how a user AE is established within a Hosting CSE. - Specification of the general communication flows across the Mca and Mcc reference points in clause 8. @@ -186,30 +154,28 @@ The present document specifies the additional architectural elements, resources ## 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 oneM2M TS-0001 <a href="#_ref_2">[2]</a> 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 CSE during M2M Service Layer operation. - - + **Figure 6.1-1: Architectural Aspects for Configuration of ASN/MN and ADN Nodes** Figure 6.1-1 depicts three (3) methods, in which ADN or ASN/MN nodes are configured using the following: - -1. Device Management technologies using the mc reference point defined in clause 6 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. Using this method, the information that is used to configure the ASN/MN or ADN is described as <_mgmtObj_ > resource types that are hosted in the IN-CSE. +1. Device Management technologies using the mc reference point defined in clause 6 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. Using this method, the information that is used to configure the ASN/MN or ADN is described as _<mgmtObj>_ resource types that are hosted in the IN-CSE. 1. oneM2M Mcc and Mca reference point when M2M Service Layer operation has been established to the AE or CSE. Establishment of the M2M Service Layer operation includes actions such as setting up security associations and registration of the M2M entities as per oneM2M TS-0003 <a href="#_ref_3">[3]</a> and oneM2M TS-0001 <a href="#_ref_2">[2]</a>. -1. To convey the information elements to the ASN/MN nodes that have established M2M Service Layer operation via Mcc reference points, resource announcement mechanism may be used. In this case, the CSE in the ASN/MN node stores the copy of the <mgmtObj> resource as a <mgmtObj_Annc_ > resource as shown in the figure 6.1-1. +1. To convey the information elements to the ASN/MN nodes that have established M2M Service Layer operation via Mcc reference points, resource announcement mechanism may be used. In this case, the CSE in the ASN/MN node stores the copy of the <mgmtObj> resource as a _<mgmtObj_Annc>_ resource as shown in the figure 6.1-1. 1. oneM2M IPE technology where the IPE interworks the information exchange between the ADN and ASN/MN and the IN-CSE. This type of IPE is called a Configuration IPE in order to depict the role and capabilities of the IPE related to the present document. -> NOTE: The reference point between the Configuration IPE and the ADN and ASN/MN is unspecified in the present document. + > NOTE: The reference point between the Configuration IPE and the ADN and ASN/MN is unspecified in the present document. In addition, figure 6.1-1 introduces an AE whose role is to configure the IN-CSE and nodes in the Field Domain with the information needed to establish M2M Service Layer operation. This type of AE is called a Configuration AE in order to depict the role and capabilities of the AE related to the present document. -The information that is used to configure the ASN/MN or ADN is described as <_mgmtObj_ > resource types that are hosted in the IN-CSE. +The information that is used to configure the ASN/MN or ADN is described as _<mgmtObj>_ resource types that are hosted in the IN-CSE. ## 6.2 Information needed for M2M Service Layer operation ### 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. +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. ### 6.2.2 Information elements required for M2M Service Layer operation @@ -221,7 +187,6 @@ The ASN/MN and ADN in the Field Domain should support the capability to be confi #### 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. @@ -277,12 +242,12 @@ The MEF Client registration configuration information elements configure the sec ## 7.1 <mgmtObj> Resource type specializations ### 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. +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 shows a summary of _<mgmtObj>_ resource specializations defined in the present document. -**Table 7.1.1-1: Summary of defined <_mgmtObj_ > resources**<a name="table_7.1.1-1"></a> +**Table 7.1.1-1: Summary of defined _<mgmtObj>_ resources**<a name="table_7.1.1-1"></a> |mgmtObj |mgmtDefinition |Intended use |Note | |-|-|-|-| @@ -300,183 +265,173 @@ Table 7.1.1-1 shows a summary of <_mgmtObj_ > resource specializations define |mobileNetwork |1031 |To store information about the currently connected mobile network. | | - - ### 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. +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. +The _[registration]_ resource shall contain the child resource specified in table 7.1.2-1. **Table 7.1.2-1: Child resources of _[registration]_ resource**<a name="table_7.1.2-1"></a> -|**Child Resources of** **_[registration]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[registration]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | - -The [_registration_ ] resource shall contain the attributes specified in table 7.1.2-2. - - -**Table 7.1.2-2: Attributes of _[registration_ _]_ resource**<a name="table_7.1.2-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| **Attributes of** \ | **Multiplicity** | **RW/**\ | **Description** | -| **_[_** **_registration_** **_]_** | | **RO/**\ | | -| | | **WO** | | -+:================================================================================+:===================+:===================================+:==========================================================================================================================================================================================================================================================================================+ -| _resourceType_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _resourceID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _resourceName_ | 1 | WO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _parentID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _expirationTime_ | 1 | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _accessControlPolicyIDs_ | 0..1 (L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _creationTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _lastModifiedTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _labels_ | 0..1(L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _mgmtDefinition_ | 1 | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. This attribute shall have the fixed value 1020 ("registration"). | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _object_ _IDs_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _objectPaths_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _description_ | 0..1 | RW | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _originatorID_ | 0..1 | RW | CSE-ID of the CSE hosted on the ASN/MN or the AE-ID of an AE hosted on an ASN/MN or ADN node.\ | -| | | | If the setting is for a CSE, then this attribute shall be present. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _pointOfAccess_ | 0..1(L) | RW | The point of access URI of the Registrar CSE. It represents the list of physical address used by AE/CSEs to connect to registrar CSE.\ | -| | | | EXAMPLE:\ | -| | | | http://172.25.0.10:8080/xyz\ | -| | | | coap://m2m.sp.com:5683\ | -| | | | mqtt://172.25.0.10:1883\ | -| | | | ws://10.222.254.26:80\ | -| | | | See note. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _CSEBase_ | 0..1 | RW | The resource identifier of the <_CSEBase_ _>_ resource representing Registrar CSE. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _CSE_ _-_ _ID_ | 0..1 | RW | The CSE identifier of Registrar CSEin SP-relative CSE-ID format. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _appID_ | 0..1 | RW | The App-ID of an AE. This attribute shall only be present when this resource is used for the registration of an AE. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _externalID_ | 0..1 | RW | The M2M-Ext-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _T_ _rigger_ _-_ _Recipient_ _-_ _ID_ | 0..1 | RW | The Trigger-Recipient-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _mgmtLink_ | 0..1 | RW | A link to a <_mgmtObj_ > resource instance containing the information for establishing a security association with the Registrar CSE. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| M2M-Sub-ID | 0..1 | WO | The identifier assigned by the M2M Service Provider for the M2M Service Subscription of the registree. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: Protocol binding is determined from the protocol schema in this URI. | -+---------------------------------------------------------------------------------+--------------------+------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - +The _[registration]_ resource shall contain the attributes specified in table 7.1.2-2. + + +**Table 7.1.2-2: Attributes of _[registration]_ resource**<a name="table_7.1.2-2"></a> + + ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Attributes of \ | Multiplicity | RW/\ | Description | +| _[registration]_ | | RO/\ | | +| | | WO | | ++:==========================+:=============+:=======+:================================================================================================================================================================================================================================================+ +| _resourceType_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _resourceID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _resourceName_ | 1 | WO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _parentID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _expirationTime_ | 1 | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _accessControlPolicyIDs_ | 0..1 (L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _creationTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _lastModifiedTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _labels_ | 0..1(L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _mgmtDefinition_ | 1 | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). This attribute shall have the fixed value 1020 ("registration"). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _objectIDs_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _objectPaths_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _description_ | 0..1 | RW | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _originatorID_ | 0..1 | RW | CSE-ID of the CSE hosted on the ASN/MN or the AE-ID of an AE hosted on an ASN/MN or ADN node.\ | +| | | | If the setting is for a CSE, then this attribute shall be present. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _pointOfAccess_ | 0..1(L) | RW | The point of access URI of the Registrar CSE. It represents the list of physical address used by AE/CSEs to connect to registrar CSE.\ | +| | | | EXAMPLE:\ | +| | | | http://172.25.0.10:8080/xyz\ | +| | | | coap://m2m.sp.com:5683\ | +| | | | mqtt://172.25.0.10:1883\ | +| | | | ws://10.222.254.26:80\ | +| | | | See note. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _CSEBase_ | 0..1 | RW | The resource identifier of the _<CSEBase>_ resource representing Registrar CSE. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _CSE-ID_ | 0..1 | RW | The CSE identifier of Registrar CSEin SP-relative CSE-ID format. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _appID_ | 0..1 | RW | The App-ID of an AE. This attribute shall only be present when this resource is used for the registration of an AE. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _externalID_ | 0..1 | RW | The M2M-Ext-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _Trigger-Recipient-ID_ | 0..1 | RW | The Trigger-Recipient-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _mgmtLink_ | 0..1 | RW | A link to a _<mgmtObj>_ resource instance containing the information for establishing a security association with the Registrar CSE. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| M2M-Sub-ID | 0..1 | WO | The identifier assigned by the M2M Service Provider for the M2M Service Subscription of the registree. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: Protocol binding is determined from the protocol schema in this URI. | ++---------------------------+--------------+--------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ### 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. +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. +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**<a name="table_7.1.3-1"></a> +**Table 7.1.3-1: Child resources of _[dataCollection]_ resource**<a name="table_7.1.3-1"></a> -|**Child Resources of** **_[_** **_dataCollection_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[dataCollection]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | - -The [_dataCollection_ ] resource shall contain the attributes specified in table 7.1.3-2. - - -**Table 7.1.3-2: Attributes of _[_ _dataCollection_ _]_ resource**<a name="table_7.1.3-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| **Attributes of** \ | **Multiplicity** | **RW/**\ | **Description** | -| **_[_** **_dataCollection_** **_]_** | | **RO/**\ | | -| | | **WO** | | -+:==================================================================================================================================================================+:===================+:===================================+:==================================================================================================================================================================================================================================+ -| _resourceType_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _resourceID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _resourceName_ | 1 | WO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _parentID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _expirationTime_ | 1 | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _accessControlPolicyIDs_ | 0..1 (L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _creationTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _lastModifiedTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _labels_ | 0..1(L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _mgmtDefinition_ | 1 | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. This attribute shall have the fixed value 1021 ("dataCollection"). | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _objectIDs_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _objectPaths_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _description_ | 0..1 | RW | See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _containerPath_ | 1 | RW | The URI of the <container> resource in the hosting CSE that stores the data transmitted by the device. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _reportingSchedule_ | 0..1 | RW | The frequency interval, in seconds, used to transmit the data to the Hosting CSE. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _measurement_ _Schedule_ | 0..1 | RW | The frequency interval, in seconds, that the device will use to collect or measure the data. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _mgmtLink_ | 0..1 | RW | A link to a <_mgmtObj_ > resource instance containing the information for establishing End-to-End Security of Primitives (ESPrim) between AE and hosting CSE. ESPrim is specified in oneM2M TS-0003 <a href="#_ref_3">[3]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: The present specification does not support configuration for End-to-End Security of Data (ESData) specified in oneM2M TS-0003 <a href="#_ref_3">[3]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - +The _[dataCollection]_ resource shall contain the attributes specified in table 7.1.3-2. + +**Table 7.1.3-2: Attributes of _[dataCollection]_ resource**<a name="table_7.1.3-2"></a> + ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Attributes of \ | Multiplicity | RW/\ | Description | +| _[dataCollection]_ | | RO/\ | | +| | | WO | | ++:==========================+:=============+:=====+:==================================================================================================================================================================================================================================+ +| _resourceType_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _resourceID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _resourceName_ | 1 | WO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _parentID_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _expirationTime_ | 1 | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _accessControlPolicyIDs_ | 0..1 (L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _creationTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _lastModifiedTime_ | 1 | RO | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _labels_ | 0..1(L) | RW | See clause 9.6.1.3 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _mgmtDefinition_ | 1 | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). This attribute shall have the fixed value 1021 ("dataCollection"). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _objectIDs_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _objectPaths_ | 0..1 (L) | WO | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _description_ | 0..1 | RW | See clause 9.6.15 of oneM2M TS-0001 [\[2\]](#_ref_2). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _containerPath_ | 1 | RW | The URI of the <container> resource in the hosting CSE that stores the data transmitted by the device. | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _reportingSchedule_ | 0..1 | RW | The frequency interval, in seconds, used to transmit the data to the Hosting CSE. | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _measurementSchedule_ | 0..1 | RW | The frequency interval, in seconds, that the device will use to collect or measure the data. | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _mgmtLink_ | 0..1 | RW | A link to a _<mgmtObj>_ resource instance containing the information for establishing End-to-End Security of Primitives (ESPrim) between AE and hosting CSE. ESPrim is specified in oneM2M TS-0003 [\[3\]](#_ref_3). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: The present specification does not support configuration for End-to-End Security of Data (ESData) specified in oneM2M TS-0003 [\[3\]](#_ref_3). | ++---------------------------+--------------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ### 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 of AEs on the Node. -An [_authenticationProfile_ ] instance identifies a security framework, TLS cipher suites, and credentials to be used. The applicable security framework is identified by the SUID attribute. The interpretation of SUID is specified in table 7.1.43. +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 of AEs on the Node. -> NOTE 1: The present document does not support using [authenticationProfile] for identifying ESData credentials. +An _[authenticationProfile]_ instance identifies a security framework, TLS cipher suites, and credentials to be used. The applicable security framework is identified by the SUID attribute. The interpretation of SUID is specified in table 7.1.43. -The [_authenticationProfile_ ] resource does not include any credentials, but either identifies credentials which are stored locally on the Managed Entity or identifies an M2M Authentication Function (MAF) which is to be used to facilitate establishing symmetric keys. The intended security principal on the Managed Entity is the security principal which can use either all the credentials identified by the [_authenticationProfile_ ] resource, or (in the case that a MAF is identified) all of the credentials required for mutual authentication with the MAF. +> NOTE 1: The present document does not support using [authenticationProfile] for identifying ESData credentials. -> NOTE 2: The other security principal can be any of the following: CSE; AE; a Node terminating the security protocol on behalf of AE on Node; and an M2M Authentication Function (MAF). +The _[authenticationProfile]_ resource does not include any credentials, but either identifies credentials which are stored locally on the Managed Entity or identifies an M2M Authentication Function (MAF) which is to be used to facilitate establishing symmetric keys. The intended security principal on the Managed Entity is the security principal which can use either all the credentials identified by the _[authenticationProfile]_ resource, or (in the case that a MAF is identified) all of the credentials required for mutual authentication with the MAF. -The [_authenticationProfile_ ] resource shall contain the child resource specified in table 7.1.4-1. +> NOTE 2: The other security principal can be any of the following: CSE; AE; a Node terminating the security protocol on behalf of AE on Node; and an M2M Authentication Function (MAF). +The _[authenticationProfile]_ resource shall contain the child resource specified in table 7.1.4-1. -**Table 7.1.4-1: Child resources of _[_ _authenticationProfile_ _]_ resource**<a name="table_7.1.4-1"></a> -|**Child Resources of** **_[_** **_authenticationProfile_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +**Table 7.1.4-1: Child resources of _[authenticationProfile]_ resource**<a name="table_7.1.4-1"></a> + +|Child Resources of _[authenticationProfile]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | - -The [_authenticationProfile_ ] resource shall contain the attributes specified in table 7.1.4-2. +The _[authenticationProfile]_ resource shall contain the attributes specified in table 7.1.4-2. -**Table 7.1.4-2: Attributes of _[_ _authenticationProfile_ _]_ resource**<a name="table_7.1.4-2"></a> +**Table 7.1.4-2: Attributes of _[authenticationProfile]_ resource**<a name="table_7.1.4-2"></a> -|**Attributes of** <br />**_[_** **_authenticationProfile_** **_]_** |**Multiplicity** |**RW/**<br />**RO/**<br />**WO** |**Description** | +|Attributes of<br />_[authenticationProfile]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -500,100 +455,93 @@ The [_authenticationProfile_ ] resource shall contain the attributes specified i |_mycertFingerprint_ |0..1 |WO |Present when certificate-based authentication is to be used. Provides a hash value for identifying the certificate to be used by the intended security principal on the Managed Entity to authenticate itself to other security principals. | |_rawPubKeyID_ |0..1 |WO |Present when certificate-based authentication is to be used and the other security principal will authenticate itself with a Raw Public Key Certificate. | |M2M-Sub-ID |0..1 |WO |The identifier assigned by the M2M Service Provider for the M2M Service Subscription of the registree. | -|_mgmtLink_ |0..1(L) |RW |Present when MAF is to be used to facilitate establishing one or more symmetric keys for mutual authentication or certificate-based authentication is to be used. In the former case, the list contains one reference to a [_MAFClientRegCfg_ ] resource. In the latter case, the list contains one or more references pointing to _[_ _trustAnchorCred_ _]_ resources. | - - - - -**Table 7.1.4-3: SUID which are currently supported in the [_authenticationProfile_ ] resource, along with reference to the authentication procedure in oneM2M TS-0003 <a href="#_ref_3">[3]</a> and mapping to symmetric key**<a name="table_7.1.4-3"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| **Value** | **Interpretation** \ | Authentication Procedure in oneM2M TS-0003 <a href="#_ref_3">[3]</a> | **Derived Symmetric Key** | **DTLS/TLS Notes** | -| | **(see n** **ote)** | | | | -+:==========================================================================================================================================================================================+:=======================================================================================================================================================================================+:=====================================================================+:============================+:==============================================================================================================================================+ -| 10 | A pre-provisioned symmetric key intended to be shared with a MEF | 8.3.2.1 | Kpm | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 11 | A pre-provisioned symmetric key intended to be shared with a MAF | 8.8.2.2 | Km | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 12 | A pre-provisioned symmetric key intended for use in a Security Associated Establishment Framework (SAEF) | 8.2.2.1 | Kpsa | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 13 | A pre-provisioned symmetric key intended for use in End-to-End Security of Primitives (ESPrim) | 8.4.2 | pairwiseESPrimKey | DTLS/TLS is not used | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 21 | A symmetric key, provisioned via a Remote Security Provisioning Framework (RSPF), and intended to be shared with a MAF | RSPF: 8.3.1.2\ | Km | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | -| | | MAF: 8.8.2.2, 8.8.3.1 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 22 | A symmetric key, provisioned via a RSPF, and intended for use in a SAEF | RSPF: 8.3.1.2\ | Kpsa | | -| | | SAEF: 8.2.2.1, 9.1.1.1 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 23 | A symmetric key, provisioned via a RSPF, and intended for use in ESPrim | RSPF: 8.3.1.2\ | pairwiseESPrimKey | DTLS/TLS is not used | -| | | ESPrim: 8.4.2 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 32 | A MAF-distributed symmetric key intended for use in a SAEF | MAF: 8.8.2.7, 8.8.3.3\ | Kpsa | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | -| | | SAEF: 8.2.2.3, 9.1.1.1 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 33 | A MAF-distributed symmetric key intended for use in ESPrim | MAF: 8.8.2.7, 8.8.3.3\ | pairwiseESPrimKey | | -| | | ESPrim: 8.4.2 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 40 | A certificate intended to be shared with a MEF | 8.3.2.2 | NP | See certificate-based TLS profile in clause 10.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a> | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 41 | A certificate intended to be shared with a MAF | 8.8.2.2 | NP | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 42 | A certificate intended for use in a Security Associated Establishment Framework (SAEF) | 8.2.2.2 | NP | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| 43 | A certificate intended for use in End-to-End Security Certificate-based Key Establishment (ESCertKE) to establish a pairwiseESPrimKey for End-to-End Security of Primitives (ESPrim) | ESCertKE: 8.7\ | NP | For ESCertKE, see certificate-based TLS profile in clause 10.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a>. For ESPrim, DTLS/TLS is not used | -| | | ESPrim: 8.4.2 | | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: The interpretation is copied from definition of m2m:suid in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. The oneM2M TS-0004 <a href="#_ref_4">[4]</a> description takes precedence. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+ - - -The Managed Entity shall allow only TLS cipher suites identified in _TLSCiphersuites_ in the TLS Handshakes for a [_authenticationProfile_ ] instance. The final column of table 7.1.4-3 provides references to clauses in oneM2M TS0003 <a href="#_ref_3">[3]</a> specifying the TLS Profiles to be used with the SUID values. The _TLSCiphersuite_ attribute shall be present only when the value of _SUID_ identifies a security framework that uses TLS or DTLS. - -If the value of _SUID_ is 10, 11, 12, 21, 22 or 23, then the _symmKeyID_ attribute shall be present. The _symmKeyID_ provides the symmetric key identifier for a symmetric key which shall be retrieved from local storage on the Managed Entity for use in the TLS Handshake. The symmetric key value may be configured in the _symmKeyValue_ . Otherwise, the symmetric key, and associated symmetric key identifier, may be provisioned to the Managed Entity before or after the [_authenticationProfile_ ] is configured. Pre-provisioning or Remote Security Provisioning Frameworks (RSPFs), specified in oneM2M TS-0003 <a href="#_ref_3">[3]</a>, should be used whenever possible to establish symmetric keys. Special care is recommended to ensure the confidentiality and integrity of the credentials when using the _symmKeyValue_ to configure symmetric keys. - -If the value of _SUID_ is 32 or 33, then the _MAFKeyRegDuration_ attribute shall be present, the _MAFKeyRegLabels_ attribute may be present, and a [_MAFClientRegCfg_ ] specialization shall be configured as a child of the [_authenticationProfile_ ] resource. These attributes provide the configuration controlling how the Managed Entity shall interact with a MAF to establish the symmetric key subsequently used for mutual authentication. The fqdn attribute of the [_MAFClientRegCfg_ ] specialization identifies the MAF. - - -- If the Managed Entity has not already performed MAF Client Registration procedure with the identified MAF, then the MAF shall perform MAF Client Registration procedure in clause 8.8.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a> using the information in the [_MAFClientRegCfg_ ] specialization of the <_mgmtObj_ > specified in clause 7.1.7 of the present document. +|_mgmtLink_ |0..1(L) |RW |Present when MAF is to be used to facilitate establishing one or more symmetric keys for mutual authentication or certificate-based authentication is to be used. In the former case, the list contains one reference to a _[MAFClientRegCfg]_ resource. In the latter case, the list contains one or more references pointing to _[trustAnchorCred]_ resources. | + + +**Table 7.1.4-3: SUID which are currently supported in the _[authenticationProfile]_ resource, along with reference to the authentication procedure in oneM2M TS-0003 <a href="#_ref_3">[3]</a> and mapping to symmetric key**<a name="table_7.1.4-3"></a> + ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| Value | Interpretation \ | Authentication Procedure in oneM2M TS-0003 [\[3\]](#_ref_3) | Derived Symmetric Key | DTLS/TLS Notes | +| | (see note) | | | | ++:========+:=======================================================================================================================================================================================+:============================================================+:======================+:=====================================================================================================================================+ +| 10 | A pre-provisioned symmetric key intended to be shared with a MEF | 8.3.2.1 | Kpm | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 [\[3\]](#_ref_3) | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 11 | A pre-provisioned symmetric key intended to be shared with a MAF | 8.8.2.2 | Km | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 12 | A pre-provisioned symmetric key intended for use in a Security Associated Establishment Framework (SAEF) | 8.2.2.1 | Kpsa | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 13 | A pre-provisioned symmetric key intended for use in End-to-End Security of Primitives (ESPrim) | 8.4.2 | pairwiseESPrimKey | DTLS/TLS is not used | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 21 | A symmetric key, provisioned via a Remote Security Provisioning Framework (RSPF), and intended to be shared with a MAF | RSPF: 8.3.1.2\ | Km | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 [\[3\]](#_ref_3) | +| | | MAF: 8.8.2.2, 8.8.3.1 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 22 | A symmetric key, provisioned via a RSPF, and intended for use in a SAEF | RSPF: 8.3.1.2\ | Kpsa | | +| | | SAEF: 8.2.2.1, 9.1.1.1 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 23 | A symmetric key, provisioned via a RSPF, and intended for use in ESPrim | RSPF: 8.3.1.2\ | pairwiseESPrimKey | DTLS/TLS is not used | +| | | ESPrim: 8.4.2 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 32 | A MAF-distributed symmetric key intended for use in a SAEF | MAF: 8.8.2.7, 8.8.3.3\ | Kpsa | See TLS-PSK Profile in clause 10.2.2 of oneM2M TS-0003 [\[3\]](#_ref_3) | +| | | SAEF: 8.2.2.3, 9.1.1.1 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 33 | A MAF-distributed symmetric key intended for use in ESPrim | MAF: 8.8.2.7, 8.8.3.3\ | pairwiseESPrimKey | | +| | | ESPrim: 8.4.2 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 40 | A certificate intended to be shared with a MEF | 8.3.2.2 | NP | See certificate-based TLS profile in clause 10.2.3 of oneM2M TS0003 [\[3\]](#_ref_3) | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 41 | A certificate intended to be shared with a MAF | 8.8.2.2 | NP | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 42 | A certificate intended for use in a Security Associated Establishment Framework (SAEF) | 8.2.2.2 | NP | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| 43 | A certificate intended for use in End-to-End Security Certificate-based Key Establishment (ESCertKE) to establish a pairwiseESPrimKey for End-to-End Security of Primitives (ESPrim) | ESCertKE: 8.7\ | NP | For ESCertKE, see certificate-based TLS profile in clause 10.2.3 of oneM2M TS0003 [\[3\]](#_ref_3). For ESPrim, DTLS/TLS is not used | +| | | ESPrim: 8.4.2 | | | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: The interpretation is copied from definition of m2m:suid in oneM2M TS-0004 [\[4\]](#_ref_4). The oneM2M TS-0004 [\[4\]](#_ref_4) description takes precedence. | ++---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + + +The Managed Entity shall allow only TLS cipher suites identified in _TLSCiphersuites_ in the TLS Handshakes for a _[authenticationProfile]_ instance. The final column of table 7.1.4-3 provides references to clauses in oneM2M TS0003 <a href="#_ref_3">[3]</a> specifying the TLS Profiles to be used with the SUID values. The _TLSCiphersuite_ attribute shall be present only when the value of _SUID_ identifies a security framework that uses TLS or DTLS. + +If the value of _SUID_ is 10, 11, 12, 21, 22 or 23, then the _symmKeyID_ attribute shall be present. The _symmKeyID_ provides the symmetric key identifier for a symmetric key which shall be retrieved from local storage on the Managed Entity for use in the TLS Handshake. The symmetric key value may be configured in the _symmKeyValue_ . Otherwise, the symmetric key, and associated symmetric key identifier, may be provisioned to the Managed Entity before or after the _[authenticationProfile]_ is configured. Pre-provisioning or Remote Security Provisioning Frameworks (RSPFs), specified in oneM2M TS-0003 <a href="#_ref_3">[3]</a>, should be used whenever possible to establish symmetric keys. Special care is recommended to ensure the confidentiality and integrity of the credentials when using the _symmKeyValue_ to configure symmetric keys. + +If the value of _SUID_ is 32 or 33, then the _MAFKeyRegDuration_ attribute shall be present, the _MAFKeyRegLabels_ attribute may be present, and a _[MAFClientRegCfg]_ specialization shall be configured as a child of the _[authenticationProfile]_ resource. These attributes provide the configuration controlling how the Managed Entity shall interact with a MAF to establish the symmetric key subsequently used for mutual authentication. The fqdn attribute of the _[MAFClientRegCfg]_ specialization identifies the MAF. + + +- If the Managed Entity has not already performed MAF Client Registration procedure with the identified MAF, then the MAF shall perform MAF Client Registration procedure in clause 8.8.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a> using the information in the _[MAFClientRegCfg]_ specialization of the _<mgmtObj>_ specified in clause 7.1.7 of the present document. - The Managed Entity shall perform the MAF Key Registration Procedure in clause 8.8.2.7 of oneM2M TS0003 <a href="#_ref_3">[3]</a> with the identified MAF, with the parameters of table 8.8.2.7-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> set as follows: + - The _MAF-FQDN_ parameter shall be set to the value of the _fqdn_ attribute in the _[MAFClientRegCfg]_ specialization which is the child of the _[authenticationProfile]_ resource. + - The _expirationTime_ Parameter shall be set to the time obtained by adding the _MAFKeyRegDuration_ attribute to the present time. + - If _MAFKeyRegLabels_ attribute is present in the _[authenticationProfile]_ resource, then the _labels_ parameter shall be set to the value of the _MAFKeyRegLabels_ attribute. Otherwise, the _labels_ parameter shall not be present. + - The _SUID_ parameter shall be set to the _SUID_ attribute. + - The _targetIDs_ parameter shall be set to the CSE-ID in the _[registration]_ or _[dataCollection]_ resource. - - The _MAF-FQDN_ parameter shall be set to the value of the _fqdn_ attribute in the [_MAFClientRegCfg_ ] specialization which is the child of the [_authenticationProfile_ ] resource. - - The _expirationTime_ Parameter shall be set to the time obtained by adding the _MAFKeyRegDuration_ attribute to the present time. - - If _MAFKeyRegLabels_ attribute is present in the [_authenticationProfile_ ] resource, then the _labels_ parameter shall be set to the value of the _MAFKeyRegLabels_ attribute. Otherwise, the _labels_ parameter shall not be present. - - The _SUID_ parameter shall be set to the _SUID_ attribute. - - The _targetIDs_ parameter shall be set to the CSE-ID in the [_registration_ ] or [_dataCollection_ ] resource. +If the value of SUID is 40, 41, 42, or 43, then the _mycertFingerprint_ attribute shall be present, and either the _rawPubKeyID_ attribute shall be present or one or more _[trustAnchorCred]_ specializations shall be configured as children of the _[authenticationProfile]_ resource. The Managed Entity shall use the certificate matching _mycertFingerprint_ to authenticate itself. The hash value portion of _mycertFingerprint_ shall be computed over the X.509 ASN.1 DER encoded certificate: -If the value of SUID is 40, 41, 42, or 43, then the _my_ _c_ _ertFingerprint_ attribute shall be present, and either the _rawPubKeyID_ attribute shall be present or one or more [_trustAnchorCred_ ] specializations shall be configured as children of the [_authenticationProfile_ ] resource. The Managed Entity shall use the certificate matching _my_ _c_ _ertFingerprint_ to authenticate itself. The hash value portion of _my_ _c_ _ertFingerprint_ shall be computed over the X.509 ASN.1 DER encoded certificate: +- If the _rawPubKeyID_ attribute is present, then the Managed Entity shall compare this value against the public key identifier (similar to a certificate fingerprint) generated from the raw public key certificate presented by the other entity, as specified in clause 10.1.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>. If the _rawPubKeyID_ attribute is present, the Managed Entity shall ignore _[trustAnchorCred]_ resource(s) configured as children of the _[authenticationProfile]_ . +- If the _rawPubKeyID_ attribute is not present, then the Managed Entity shall use the one or more _[trustAnchorCred]_ resource instance(s) configured as children of the _[authenticationProfile]_ resource instance to retrieve Certificate Authority certificates to be used by the Managed Entity as a trust anchor certificate (also known as a "root CA certificate" or "trust root certificate") when validating the certificate chains provided by other entities. The Managed Entity shall allow the TLS handshake only if the other entity provides a certificate chaining to one of these trust anchors, using the process specified in clause 8.1.2.2 in oneM2M TS-0003 <a href="#_ref_3">[3]</a>. - -- If the _rawPubKeyID_ attribute is present, then the Managed Entity shall compare this value against the public key identifier (similar to a certificate fingerprint) generated from the raw public key certificate presented by the other entity, as specified in clause 10.1.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>. If the _rawPubKeyID_ attribute is present, the Managed Entity shall ignore [_trustAnchorCred_ ] resource(s) configured as children of the [_authenticationProfile_ ]. -- If the _rawPubKeyID_ attribute is not present, then the Managed Entity shall use the one or more [_trustAnchorCred_ ] resource instance(s) configured as children of the [_authenticationProfile_ ] resource instance to retrieve Certificate Authority certificates to be used by the Managed Entity as a trust anchor certificate (also known as a "root CA certificate" or "trust root certificate") when validating the certificate chains provided by other entities. The Managed Entity shall allow the TLS handshake only if the other entity provides a certificate chaining to one of these trust anchors, using the process specified in clause 8.1.2.2 in oneM2M TS-0003 <a href="#_ref_3">[3]</a>. - -[_authenticationProfile_ ] resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. +_[authenticationProfile]_ resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. ### 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. +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. +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**<a name="table_7.1.5-1"></a> +**Table 7.1.5-1: Child resources of _[myCertFileCred]_ resource**<a name="table_7.1.5-1"></a> -|**Child Resources of** **_[_** **_myCertFileCred_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[myCertFileCred]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[myCertFileCred]_ resource shall contain the attributes specified in table 7.1.5-2. -The [_myCertFileCred_ ] resource shall contain the attributes specified in table 7.1.5-2. +**Table 7.1.5-2: Attributes of _[myCertFileCred]_ resource**<a name="table_7.1.5-2"></a> -**Table 7.1.5-2: Attributes of _[_ _myCertFileCred_ _]_ resource**<a name="table_7.1.5-2"></a> - -|**Attributes of** <br />**_[_** **_myCertFileCred_** **_]_** |**Multiplicity** |**RW/**<br />**RO/**<br />**WO** |**Description** | +|Attributes of<br />_[myCertFileCred]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -613,60 +561,55 @@ The [_myCertFileCred_ ] resource shall contain the attributes specified in table |_myCertFileContent_ |1 |WO |Certificate or certificate chain. Default media-type is "application/pkcs7-mime". | - -The _SUIDs_ attribute lists the Security Usage Identifiers (SUIDs) of the security frameworks which shall be allowed using this credential for establishing mutually-authenticated secure communication. Any SUID which is not in this list shall be prevented from using this credential for establishing mutually-authenticated secure communication. The SUID values allowed in this attribute are listed in table 7.1.5-3. See table 7.1.4-3 for references to the corresponding authentication procedure in oneM2M TS-0003 <a href="#_ref_3">[3]</a> and DTLS/TLS notes. +The _SUIDs_ attribute lists the Security Usage Identifiers (SUIDs) of the security frameworks which shall be allowed using this credential for establishing mutually-authenticated secure communication. Any SUID which is not in this list shall be prevented from using this credential for establishing mutually-authenticated secure communication. The SUID values allowed in this attribute are listed in table 7.1.5-3. See table 7.1.4-3 for references to the corresponding authentication procedure in oneM2M TS-0003 <a href="#_ref_3">[3]</a> and DTLS/TLS notes. -**Table 7.1.5-3: SUID which are currently supported in the [_myCertFileCred_ ] resource**<a name="table_7.1.5-3"></a> +**Table 7.1.5-3: SUID which are currently supported in the _[myCertFileCred]_ resource**<a name="table_7.1.5-3"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| **Value** | **Interpretation (see n** **ote)** | -+:==============================================================================================================================================================================================+:=======================================================================================================================================================================================+ -| 40 | A certificate intended to be shared with a MEF | -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 41 | A certificate intended to be shared with a MAF | -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 42 | A certificate intended for use in a Security Associated Establishment Framework (SAEF) | -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 43 | A certificate intended for use in End-to-End Security Certificate-based Key Establishment (ESCertKE) to establish a pairwiseESPrimKey for End-to-End Security of Primitives (ESPrim) | -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: The interpretation is copied from the definition of m2m:suid in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. The oneM2M TS-0004 <a href="#_ref_4">[4]</a> description takes precedence. | -+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ++----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Value | Interpretation (see note) | ++:===============+:=======================================================================================================================================================================================+ +| 40 | A certificate intended to be shared with a MEF | ++----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 41 | A certificate intended to be shared with a MAF | ++----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 42 | A certificate intended for use in a Security Associated Establishment Framework (SAEF) | ++----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 43 | A certificate intended for use in End-to-End Security Certificate-based Key Establishment (ESCertKE) to establish a pairwiseESPrimKey for End-to-End Security of Primitives (ESPrim) | ++----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: The interpretation is copied from the definition of m2m:suid in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. The oneM2M TS-0004 <a href="#_ref_4">[4]</a> description takes precedence. | ++---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ The Certificate issuer should verify that the corresponding private key is known to the Managed Entity. The present specification does not provide a mechanism for such verification. -> NOTE: In many scenarios, if the device management session takes place over a TLS connection in which the Managed Entity is authenticated using an existing certificate (e.g. a manufacturer certificate), then it would be acceptable to issue a certificate with SubjectPublicKeyInfo copied from the existing certificate. +> NOTE: In many scenarios, if the device management session takes place over a TLS connection in which the Managed Entity is authenticated using an existing certificate (e.g. a manufacturer certificate), then it would be acceptable to issue a certificate with SubjectPublicKeyInfo copied from the existing certificate. Managed Entities shall support the default certificate-related media type. -If the _my_ _c_ _ertFingerprint_ attribute in an [_authenticationProfile_ ] resource matches the certificate in a [_myCertFileCred_ ] resource, then the authentication protocol based on that [_authenticationProfile_ ] shall provide the certificate or certificate chain in the _myCertFileContent_ , and shall use the corresponding private key to authenticate the Managed Entity. +If the _mycertFingerprint_ attribute in an _[authenticationProfile]_ resource matches the certificate in a _[myCertFileCred]_ resource, then the authentication protocol based on that _[authenticationProfile]_ shall provide the certificate or certificate chain in the _myCertFileContent_ , and shall use the corresponding private key to authenticate the Managed Entity. -[_myCertFileCred_ ] instances are expected to be protected by a secure environment on the Managed Entity, in order to preserve confidentiality and integrity of the attributes. Optimal protection is provided when the decryption and integrity verification of the management protocol message occurs in the secure environment. +_[myCertFileCred]_ instances are expected to be protected by a secure environment on the Managed Entity, in order to preserve confidentiality and integrity of the attributes. Optimal protection is provided when the decryption and integrity verification of the management protocol message occurs in the secure environment. ### 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 associated [_trustAnchorCred_ ] resources to identify a trust anchor certificate for validation of certificates. +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 associated _[trustAnchorCred]_ resources to identify a trust anchor certificate for validation of certificates. -The [_trustAnchorCred_ ] resource shall contain the child resource specified in table 7.1.6-1. +The _[trustAnchorCred]_ resource shall contain the child resource specified in table 7.1.6-1. -**Table 7.1.6-1: Child resources of _[_ _trustAnchorCred_ _]_ resource**<a name="table_7.1.6-1"></a> +**Table 7.1.6-1: Child resources of _[trustAnchorCred]_ resource**<a name="table_7.1.6-1"></a> -|**Child Resources of** **_[_** **_trustAnchorCred_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[trustAnchorCred]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[trustAnchorCred]_ resource shall contain the attributes specified in table 7.1.6-2. -The [_trustAnchorCred_ ] resource shall contain the attributes specified in table 7.1.6-2. - +**Table 7.1.6-2: Attributes of _[trustAnchorCred]_ resource**<a name="table_7.1.6-2"></a> -**Table 7.1.6-2: Attributes of _[_ _trustAnchorCred_ _]_ resource**<a name="table_7.1.6-2"></a> - -|**Attributes of** <br />**_[_** **_trustAnchorCred_** **_]_** |**Multiplicity** |**RW/**<br />**RO/**<br />**WO** |**Description** | +|Attributes of <br />_[trustAnchorCred]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -676,41 +619,39 @@ The [_trustAnchorCred_ ] resource shall contain the attributes specified in tabl |_accessControlPolicyIDs_ |0..1 (L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_creationTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_lastModifiedTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -|_L_ _abels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_Labels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_mgmtDefinition_ |1 |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. This attribute shall have the fixed value 1024 ("trustAnchorCred"). | |_objectIDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_objectPaths_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -|_D_ _escription_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_Description_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_certFingerprint_ |1 |WO |Provides a hash value for identifying a certificate authority certificate to be used for validating certificates presented by other entities. | |_URI_ |1 |RW |A URI from which the trust anchor certificate may be retrieved. | +The _certFingerprint_ attribute of the _[trustAnchorCred]_ resource identifies a Certificate Authority certificate to be used by the Managed Entity as a trust anchor when validating the certificate chains provided by other entities. The hash value portion of the _certFingerprint_ attribute shall be computed over the X.509 ASN.1 DER encoded certificate using the SHA-256 hash algorithm defined in FIPS PUB 180-4 <a href="#_ref_10">[10]</a>. The certFingerprint attribute shall be represented in the named information (ni) URI format defined in IETF RFC 6920 <a href="#_ref_7">[7]</a>, see tables 7.2.6.1-2 and 7.3.2-1. Where the CA Certificate identified in a _[trustAnchorCred]_ resource is not already in local storage, then the Managed Entity shall retrieve the certificate using the _URI_ attribute in the _[trustAnchorCred]_ resources. -The _certFingerprint_ attribute of the [_trustAnchorCred_ ] resource identifies a Certificate Authority certificate to be used by the Managed Entity as a trust anchor when validating the certificate chains provided by other entities. The hash value portion of the _certFingerprint_ attribute shall be computed over the X.509 ASN.1 DER encoded certificate using the SHA-256 hash algorithm defined in FIPS PUB 180-4 <a href="#_ref_10">[10]</a>. The certFingerprint attribute shall be represented in the named information (ni) URI format defined in IETF RFC 6920 <a href="#_ref_7">[7]</a>, see tables 7.2.6.1-2 and 7.3.2-1. Where the CA Certificate identified in a [_trustAnchorCred_ ] resource is not already in local storage, then the Managed Entity shall retrieve the certificate using the _URI_ attribute in the [_trustAnchorCred_ ] resources. - -[_trustAnchorCred_ ] resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. +_[trustAnchorCred]_ resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. ### 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 oneM2M TS-0003 <a href="#_ref_3">[3]</a>). +This _<mgmtObj>_ specialization is used to convey instructions regarding the MAF Client Registration procedure (clause 8.8.2.3 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>). -The [_MAFClientRegCfg_ ] resource shall contain the child resource specified in table 7.1.7-1. +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**<a name="table_7.1.7-1"></a> +**Table 7.1.7-1: Child resources of _[MAFClientRegCfg]_ resource**<a name="table_7.1.7-1"></a> -|**Child Resources of** **_[_** **_MAFClientRegCfg_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[MAFClientRegCfg]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[MAFClientRegCfg]_ resource shall contain the attributes specified in table 7.1.7-2. -The [_MAFClientRegCfg_ ] resource shall contain the attributes specified in table 7.1.7-2. +**Table 7.1.7-2: Attributes of _[MAFClientRegCfg]_ resource**<a name="table_7.1.7-2"></a> -**Table 7.1.7-2: Attributes of _[_ _MAFClientRegCfg_ _]_ resource**<a name="table_7.1.7-2"></a> - -|**Attributes of** <br />**_[_** **_MAFClientRegCfg_** **_]_** |**Multiplicity** |**RW/**<br />**RO/**<br />**WO** |**Description** | +|Attributes of<br />_[MAFClientRegCfg]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -733,32 +674,30 @@ The [_MAFClientRegCfg_ ] resource shall contain the attributes specified in tabl |_mgmtLink_ |1 |RW |A link to a [authenticationProfile] resource containing the parameters for the MAF Client to establish mutuallyauthenticated secure communications with the MAF. | - The MAF Client shall perform the MAF Client Registration Procedure specified in clause 8.8.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a>, using the linked authentication profile for mutual authentication of the MAF Client and MAF. -The MOs configured to the Managed Entity via [_MAFClientRegCfg_ ] resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. +The MOs configured to the Managed Entity via _[MAFClientRegCfg]_ resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. ### 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 oneM2M TS-0003 <a href="#_ref_3">[3]</a>). +This _<mgmtObj>_ specialization is used to convey instructions regarding the MEF Client Registration procedure (clause 8.3.5.2.3 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>). -The [_MEFClientRegCfg_ ] resource shall contain the child resource specified in table 7.1.8-1. +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**<a name="table_7.1.8-1"></a> +**Table 7.1.8-1: Child resources of _[MEFClientRegCfg]_ resource**<a name="table_7.1.8-1"></a> -|**Child Resources of** **_[_** **_MEFClientRegCfg_** **_]_** |**Child Resource Type** |**Multiplicity** |**Description** | +|Child Resources of _[MEFClientRegCfg]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[MEFClientRegCfg]_ resource shall contain the attributes specified in table 7.1.8-2. -The [_MEFClientRegCfg_ ] resource shall contain the attributes specified in table 7.1.8-2. +**Table 7.1.8-2: Attributes of _[MEFClientRegCfg]_ resource**<a name="table_7.1.8-2"></a> -**Table 7.1.8-2: Attributes of _[_ _MEFClientRegCfg_ _]_ resource**<a name="table_7.1.8-2"></a> - -|**Attributes of** <br />**_[_** **_MEFClientRegCfg_** **_]_** |**Multiplicity** |**RW/**<br />**RO/**<br />**WO** |**Description** | +|Attributes of <br />_[MEFClientRegCfg]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -778,35 +717,31 @@ The [_MEFClientRegCfg_ ] resource shall contain the attributes specified in tabl |_httpPort_ |0..1 |WO |See clause 8.3.7 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | |_coapPort_ |0..1 |WO |See clause 8.3.7 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | |_websocketPort_ |0..1 |WO |See clause 8.3.7 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | -|_mgmtLink_ |1 |RW |A link to a [_authenticationProfile_ ] resource containing the parameters for the MEF Client to establish mutually-authenticated secure communications with the MEF. | - +|_mgmtLink_ |1 |RW |A link to a _[authenticationProfile]_ resource containing the parameters for the MEF Client to establish mutually-authenticated secure communications with the MEF. | The MEF Client shall perform the MEF Client Registration Procedure specified in clause 8.8.2.3 of oneM2M TS0003 <a href="#_ref_3">[3]</a>, using the linked authentication profile for mutual authentication of the MEF Client and MEF. -The MOs configured to the Managed Entity via [_MEFClientRegCfg_ ] resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. +The MOs configured to the Managed Entity via _[MEFClientRegCfg]_ resources are expected to be protected by a secure environment on the Managed Entity, in order to preserve integrity of the attributes. Optimal protection is provided when the integrity protection of the management protocol message is verified in the secure environment. ### 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. +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**<a name="table_7.1.9-1"></a> +**Table 7.1.9-1: Child resources of _[OAuth2Authentication]_ resource**<a name="table_7.1.9-1"></a> -|Child Resources of _[_ _OAuth2Authentication_ _]_ |Child Resource Type |Multiplicity |Description | +|Child Resources of _[OAuth2Authentication]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[OAuth2Authentication]_ resource shall contain the attributes specified in table 7.1.9-2. +**Table 7.1.9-2: Attributes of _[OAuth2Authentication]_ resource**<a name="table_7.1.9-2"></a> -The _[_ _OAuth2Authentication_ _]_ resource shall contain the attributes specified in table 7.1.9-2. - - -**Table 7.1.9-2: Attributes of _[_ _OAuth2Authentication_ _]_ resource**<a name="table_7.1.9-2"></a> - -|**Attributes of** <br />**[** **_OAuth2Authentication_** **]** |**Multiplicity** |**RW/** <br />**RO/** <br />**WO** |**Description** | +|Attributes of<br />_[OAuth2Authentication]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |resourceType |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |resourceID |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -825,32 +760,26 @@ The _[_ _OAuth2Authentication_ _]_ resource shall contain the attributes specif |refreshToken |1 |RW |Indicates OAuth2 refresh token. | - - -### 7.1.10 Resource [_wifiClient_ _]_ +### 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. - +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**<a name="table_7.1.10-1"></a> +**Table 7.1.10-1: Child resources of _[wifiClient]_ resource**<a name="table_7.1.10-1"></a> -|Child Resources of _[_ _wifiClient_ _]_ |Child Resource Type |Multiplicity |Description | +|Child Resources of _[wifiClient]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[wifiClient]_ resource shall contain the attributes specified in table 7.1.10-2. +**Table 7.1.10-2: Attributes of _[wifiClient]_ resource**<a name="table_7.1.10-2"></a> -The _[_ _wifiClient_ _]_ resource shall contain the attributes specified in table 7.1.10-2. - - -**Table 7.1.10-2: Attributes of _[_ _wifiClient_ _]_ resource**<a name="table_7.1.10-2"></a> - -|**Attributes of** <br />**_[_** **_wifiClient_** **_]_** |**Multiplicity** |**RW/** <br />**RO/** <br />**WO** |**Description** | +|Attributes of <br />_[wifiClient]_ |Multiplicity** |RW/ <br />RO/ <br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -|_resource_ _Name_ |1 |WO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_resourceName_ |1 |WO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_parentID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_expirationTime_ |1 |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_accessControlPolicyIDs_ |0..1 (L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -858,44 +787,39 @@ The _[_ _wifiClient_ _]_ resource shall contain the attributes specified in tab |_lastModifiedTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_labels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_mgmtDefinition_ |1 |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. This attribute shall have the fixed value 1027(wifiClient). | -|_object_ _ID_ _s_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_objectIDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_objectPaths_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_description_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -|_ssid_ |1 |RW |Indicates ssid of Wi-Fi® network. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. | +|_ssid_ |1 |RW |Indicates ssid of Wi-Fi® network. This attribute is a specialization of _[objectAttribute]_ attribute. | |_credentials_ |0..1 |RW |Indicates encryption type and credentials used to authenticate connection. This attribute is a specialization of [objectAttribute] attribute. | |_macAddress_ |0..1 |RW |Indicates MAC address of network's access point. This attribute is a specialization of [objectAttribute] attribute. | |_channel_ |0..1 |RO |Indicates Wi-Fi® channel. This attribute is a specialization of [objectAttribute] attribute. | -|_connectionStatus_ |0..1 |RW |Indicates current status of the connection. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. | -|_scan_ |1 |RW |The action that allows to scan the environment to find available Wi-Fi® networks. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. This action will provide all the available ssids in _scanResult_ . | -|_scanResult_ |1 |RW |Indicates list of networks detected by the device. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. | +|_connectionStatus_ |0..1 |RW |Indicates current status of the connection. This attribute is a specialization of _[objectAttribute]_ attribute. | +|_scan_ |1 |RW |The action that allows to scan the environment to find available Wi-Fi® networks. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of _[objectAttribute]_ attribute. This action will provide all the available ssids in _scanResult_ . | +|_scanResult_ |1 |RW |Indicates list of networks detected by the device. This attribute is a specialization of _[objectAttribute]_ attribute. | |_update_ |1 |RW |The action is to trigger the device to update its Wi-Fi® configuration based on the provided values (e.g. ssid, credentials, etc.).The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of [objectAttribute] attribute. | -|_updateStatus_ |1 |RW |Indicates status of update operation. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. | -|_toggleRadioStatus_ |0..1 |RW |The action that allows to turn on and turn off the Wi-Fi® subsystem on Wi-Fi® client device according to present radioStatus attribute value. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. This action will switch _radioStatus_ . | -|_radioStatus_ |0..1 |RW |Indicates whether the Wi-Fi® sub-system on Wi-Fi® client device is turned on or turned off. This attribute is a specialization of _[_ _objectAttribute_ _]_ attribute. | +|_updateStatus_ |1 |RW |Indicates status of update operation. This attribute is a specialization of _[objectAttribute]_ attribute. | +|_toggleRadioStatus_ |0..1 |RW |The action that allows to turn on and turn off the Wi-Fi® subsystem on Wi-Fi® client device according to present radioStatus attribute value. The action is triggered by assigning value "TRUE" to this attribute. This attribute is a specialization of _[objectAttribute]_ attribute. This action will switch _radioStatus_ . | +|_radioStatus_ |0..1 |RW |Indicates whether the Wi-Fi® sub-system on Wi-Fi® client device is turned on or turned off. This attribute is a specialization of _[objectAttribute]_ attribute. | - - -### 7.1.11 Resource [_credentials_ _]_ +### 7.1.11 Resource [credentials] This specialization of <mgmtObj> is used to store credentials on the client device. -The _[credentials]_ resource shall contain the child resources specified in table 7.1.11-1. +The _[credentials]_ resource shall contain the child resources specified in table 7.1.11-1. +**Table 7.1.11-1: Child resources of _[credentials]_ resource**<a name="table_7.1.11-1"></a> -**Table 7.1.11-1: Child resources of _[credentials]_ resource**<a name="table_7.1.11-1"></a> - -|Child Resources of _[_ _credentials_ _]_ |Child Resource Type |Multiplicity |Description | +|Child Resources of _[credentials]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[credentials]_ resource shall contain the attributes specified in table 7.1.11.-2 -The _[credentials]_ resource shall contain the attributes specified in table 7.1.11.-2 - +**Table 7.1.11-2: Attributes of _[credentials]_ resource**<a name="table_7.1.11-2"></a> -**Table 7.1.11-2: Attributes of _[credentials]_ resource**<a name="table_7.1.11-2"></a> - -|Attributes of <br />_[_ _wifiClient_ _]_ |Multiplicity |RW/<br />RO/<br />WO |Description | +|Attributes of <br />_[wifiClient]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -907,7 +831,7 @@ The _[credentials]_ resource shall contain the attributes specified in table 7. |_lastModifiedTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_labels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_mgmtDefinition_ |1 |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>.. This attribute shall have the fixed value 1029(credentials). | -|_object_ _IDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_objectIDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_objectPaths_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_description_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_purpose_ |0..1 |RW |Indicates the intended use of this credentials set. | @@ -916,28 +840,25 @@ The _[credentials]_ resource shall contain the attributes specified in table 7. |_credentialToken_ |0..1 |RW |Indicates a token for authentication. | - - -### 7.1.12 Resource [_SIM_ _]_ +### 7.1.12 Resource [SIM] This specialization of <mgmtObj> is used to store configuration of Subscriber Identification Module (SIM) and status information. This information is meant to configure devices, e.g. to activate or deactivate SIM on a device, as well as provide information about used and deployed SIM identify to other entities. The terms "SIM" and "Subscriber Identity Module" are used in this resource to refer to the physical/logical platform hosting the application handling authentication of the related subscriber onto a 3GPP network. -The _[SIM]_ resource shall contain the child resources specified in table 7.1.12-1. +The _[SIM]_ resource shall contain the child resources specified in table 7.1.12-1. -**Table 7.1.12-1: Child resources of _[SIM]_ resource**<a name="table_7.1.12-1"></a> +**Table 7.1.12-1: Child resources of _[SIM]_ resource**<a name="table_7.1.12-1"></a> |Child Resources of _[SIM]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | +The _[SIM]_ resource shall contain the attributes specified in table 7.1.12-2. -The _[SIM]_ resource shall contain the attributes specified in table 7.1.12-2. - -**Table 7.1.12-2: Attributes of _[SIM]_ resource**<a name="table_7.1.12-2"></a> +**Table 7.1.12-2: Attributes of _[SIM]_ resource**<a name="table_7.1.12-2"></a> |Attributes of <br />_[SIM]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| @@ -951,7 +872,7 @@ The _[SIM]_ resource shall contain the attributes specified in table 7.1.12-2. |_lastModifiedTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_labels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_mgmtDefinition_ |1 |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>.. This attribute shall have the fixed value 1030 (SIM). | -|_object_ _IDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_objectIDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_objectPaths_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_description_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_imsi_ |0..1 |RW |The _international mobile subscriber identity_ (IMSI) that is associated with the SIM. | @@ -961,28 +882,24 @@ The _[SIM]_ resource shall contain the attributes specified in table 7.1.12-2. |_serviceProviderName_ |0..1 |RW |The Service Provider Name (SPN) of a SIM. | - - -### 7.1.13 Resource [_mobileNetwork_ _]_ +### 7.1.13 Resource [mobileNetwork] This specialization of <mgmtObj> is used to store information about the currently connected mobile network. This information can be derived from the network, but also be provided by an OSS (Operation Support System), or be provided by a device. -The _[_ _mobileNetwork_ _]_ resource shall contain the child resources specified in table 7.1.13-1. +The _[mobileNetwork]_ resource shall contain the child resources specified in table 7.1.13-1. +**Table 7.1.13-1: Child resources of _[mobileNetwork]_ resource**<a name="table_7.1.13-1"></a> -**Table 7.1.13-1: Child resources of _[_ _mobileNetwork_ _]_ resource**<a name="table_7.1.13-1"></a> - -|Child Resources of _[_ _mobileNetwork_ _]_ |Child Resource Type |Multiplicity |Description | +|Child Resources of _[mobileNetwork]_ |Child Resource Type |Multiplicity |Description | |-|-|-|-| |_[variable]_ |_<subscription>_ |0..n |See clause 9.6.8 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> | - -The _[_ _mobileNetwork_ _]_ resource shall contain the attributes specified in table 7.1.13-2. The specialisation attributes are derived from and map to the LwM2M Object #4 "Connectivity Monitoring" definition <a href="#_ref_11">[11]</a>. +The _[mobileNetwork]_ resource shall contain the attributes specified in table 7.1.13-2. The specialisation attributes are derived from and map to the LwM2M Object #4 "Connectivity Monitoring" definition <a href="#_ref_11">[11]</a>. -**Table 7.1.13-2: Attributes of _[_ _mobileNetwork_ _]_ resource**<a name="table_7.1.13-2"></a> +**Table 7.1.13-2: Attributes of _[mobileNetwork]_ resource**<a name="table_7.1.13-2"></a> -|Attributes of <br />_[_ _mobileNetwork_ _]_ |Multiplicity |RW/<br />RO/<br />WO |Description | +|Attributes of <br />_[mobileNetwork]_ |Multiplicity |RW/<br />RO/<br />WO |Description | |-|-|-|-| |_resourceType_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_resourceID_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | @@ -994,7 +911,7 @@ The _[_ _mobileNetwork_ _]_ resource shall contain the attributes specified in |_lastModifiedTime_ |1 |RO |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_labels_ |0..1(L) |RW |See clause 9.6.1.3 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_mgmtDefinition_ |1 |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>.. This attribute shall have the fixed value 1031 (mobileNetwork).<br /> | -|_object_ _IDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | +|_objectIDs_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_objectPaths_ |0..1 (L) |WO |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_description_ |0..1 |RW |See clause 9.6.15 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | |_cellularNetworkBearer_ |0..1 |RW |Indicates the cellular network bearer used for the current cellular communication session. | @@ -1010,414 +927,364 @@ The _[_ _mobileNetwork_ _]_ resource shall contain the attributes specified in |_coverageEnhancementLevel_ |0..1 |RW |Indicates the Coverage Enhancement Level of the UE in the serving cell. The Coverage Enhancement levels are defined and specified in 3GPP 36.331 <a href="#_ref_16">[16]</a> and 36.213 <a href="#_ref_17">[17]</a>. | - - ## 7.2 Resource-Type specific procedures and definitions ### 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. +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. ### 7.2.2 Resource [registration] #### 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. +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_ ]**<a name="table_7.2.2.1-1"></a> +**Table 7.2.2.1-1: Data Type Definition of _[registration]_**<a name="table_7.2.2.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |registration |DCFG-registration.xsd | | - - -**Table 7.2.2.1-2: Resource specific attributes of [_registration_ ]**<a name="table_7.2.2.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | -+:===========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+:======================+:==============+:==============================================================+:=========================================================================================================================================================================================================================================================+ -| | Create | Update | | | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1020 (registration). | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| originatorID | O | O | m2m:ID | CSE-ID of the CSE hosted on the ASN/MN or the AE-ID of an AE hosted on an ASN/MN or ADN node.\ | -| | | | | If the setting is for a CSE, then this attribute shall be present. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| pointOfAccess | O | O | m2m:poaList | The point of access URI of the Registrar CSE.\ | -| | | | | Note; protocol binding is determined from the protocol schema in this URI. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _CSEBase_ | O | O | xs:anyURI | No Defaults. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| _CSE-ID_ | O | O | m2m:ID | No Defaults. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| appID | O | O | m2m:ID | The APP\_ID of an AE. This attribute shall only be present when this resource is used for the registration of an AE. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| externalID | O | O | m2m:externalID | The M2M-Ext-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS0001 <a href="#_ref_2">[2]</a>. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Trigger-Recipient-ID | O | O | m2m:triggerRecipientID | The Trigger-Recipient-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| mgmtLink | O | O | m2m:mgmtLinkRef | 1 link to a [_authenticationProfile_ ] resource instance. See note. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| M2M-Sub-ID | O | NP | m2m:ID | | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: The SUID in the linked [_authenticationProfile_ ] instance constrains the security framework to be used with the Authentication Profile. The security frameworks used with the [registration] resource are Security Association Establishment Frameworks (SAEF). The entity composing a [_registration_ ] instance is expected to confirm that the linked Authentication Profile contains a SUID corresponding to an SAEF. The SAEF SUIDs are the values 12, 22, 32 or 42 as defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | -+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+---------------+---------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - +**Table 7.2.2.1-2: Resource specific attributes of _[registration]_**<a name="table_7.2.2.1-2"></a> + + ++------+-----+-----+-----+-----+ +| H1 | H2 | H3 | +| +-----+-----+ | +| | H4 | H5 | | ++:=====+:====+:====+:====+:====+ +| D1 | D2 | D3 | D4 | D5 | ++------+-----+-----+-----+-----+ + + ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | +| +-----------+-----------+ | +| | Create | Update | | ++:=======================+:==========+:==========+:=====================================================+:=====================================================================================================================================================================================================================================================================================================================================================================================================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1020 (registration). | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| originatorID | O | O | m2m:ID | CSE-ID of the CSE hosted on the ASN/MN or the AE-ID of an AE hosted on an ASN/MN or ADN node.\ | +| | | | | If the setting is for a CSE, then this attribute shall be present. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| pointOfAccess | O | O | m2m:poaList | The point of access URI of the Registrar CSE.\ | +| | | | | Note; protocol binding is determined from the protocol schema in this URI. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _CSEBase_ | O | O | xs:anyURI | No Defaults. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| _CSE-ID_ | O | O | m2m:ID | No Defaults. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| appID | O | O | m2m:ID | The APP\_ID of an AE. This attribute shall only be present when this resource is used for the registration of an AE. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| externalID | O | O | m2m:externalID | The M2M-Ext-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS0001 [\[2\]](#_ref_2). | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Trigger-Recipient-ID | O | O | m2m:triggerRecipientID | The Trigger-Recipient-ID of the ASN/MN CSE. This attribute can be present when the originatorID is a CSE-ID and the CSE uses the dynamic registration defined in clause 7.1.10 Trigger Recipient Identifier of oneM2M TS-0001 [\[2\]](#_ref_2). | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| mgmtLink | O | O | m2m:mgmtLinkRef | 1 link to a _[authenticationProfile]_ resource instance. See note. | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| M2M-Sub-ID | O | NP | m2m:ID | | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: The SUID in the linked _[authenticationProfile]_ instance constrains the security framework to be used with the Authentication Profile. The security frameworks used with the [registration] resource are Security Association Establishment Frameworks (SAEF). The entity composing a _[registration]_ instance is expected to confirm that the linked Authentication Profile contains a SUID corresponding to an SAEF. The SAEF SUIDs are the values 12, 22, 32 or 42 as defined in oneM2M TS-0004 [\[4\]](#_ref_4). | ++------------------------+-----------+-----------+------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. In addition to the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource following check shall be done in CREATE and UPDATE operation: +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. In addition to the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource following check shall be done in CREATE and UPDATE operation: -If _appID_ attribute is set to a value starting with other than 'r', 'R' or 'N' then the Hosting CSE shall reject the request with "BAD\_REQUEST" **_Response Status Code_** . +If _appID_ attribute is set to a value starting with other than 'r', 'R' or 'N' then the Hosting CSE shall reject the request with "BAD\_REQUEST" **_Response Status Code_** . -> NOTE: Use of 'r' will be forbidden when subsequently registering an AE that supports release 4 or above. +> NOTE: Use of 'r' will be forbidden when subsequently registering an AE that supports release 4 or above. ### 7.2.3 Resource [dataCollection] #### 7.2.3.1 Introduction -**Table 7.2.3.1-1: Data Type Definition of [_dataCollection_ ]**<a name="table_7.2.3.1-1"></a> +**Table 7.2.3.1-1: Data Type Definition of _[dataCollection]**<a name="table_7.2.3.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |dataCollection |DCFG-dataCollection.xsd | | - - - -**Table 7.2.3.1-2: Resource specific attributes of [_dataCollection_ ]**<a name="table_7.2.3.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | **Default Value and Constraints** | -+:==============================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+:==========================+:==================+:==============================================================+:============================================================================================================================================================================================================================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | **Default Value and Constraints** | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1021 (dataCollection). | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| containerPath | M | O | m2m:ID | The URI of the <container> resource in the hosting CSE that stores the data transmitted by the device. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| reportingSchedule | O | O | m2m:scheduleEntries | The schedule, used to transmit the measured or collected data to the Hosting CSE. \ | -| | | | | If the entity that reports the data misses a reporting interval, the entity shall wait until the next interval to report the data. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| measurementSchedule | O | O | m2m:scheduleEntries | The schedule, that the device will use to collect or measure the data.\ | -| | | | | If the entity that measures or collects the data misses a measurement interval, the entity shall wait until the next interval to collect or measure the data. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| mgmtLink | O | O | m2m:mgmtLinkRef | 1 link to a [authenticationProfile]. See note. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| NOTE: The SUID in the linked [_authenticationProfile_ ] instance constrains the security framework to be used with the Authentication Profile. The security frameworks used with the [_dataCollection_ ] resource are End-to-End Security of Primitives (ESPrim). The entity composing a [_dataCollection_ ] instance is expected to confirm that the linked Authentication Profile contains a SUID corresponding to ESPrim. The SUIDs corresponding to ESPrim security frameworks are the values 13, 23, 33 or 43 as defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - +**Table 7.2.3.1-2: Resource specific attributes of _[dataCollection]_**<a name="table_7.2.3.1-2"></a> + ++---------------------------+-----------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | +| +---------------------------+-------------------+ | +| | Create | Update | | ++:==========================+:==========================+:==================+:==============================================================+:===================================================================================================================================================================================================================================================================================================================================================================================================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1021 (dataCollection). | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| containerPath | M | O | m2m:ID | The URI of the <container> resource in the hosting CSE that stores the data transmitted by the device. | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| reportingSchedule | O | O | m2m:scheduleEntries | The schedule, used to transmit the measured or collected data to the Hosting CSE. \ | +| | | | | If the entity that reports the data misses a reporting interval, the entity shall wait until the next interval to report the data. | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| measurementSchedule | O | O | m2m:scheduleEntries | The schedule, that the device will use to collect or measure the data.\ | +| | | | | If the entity that measures or collects the data misses a measurement interval, the entity shall wait until the next interval to collect or measure the data. | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| mgmtLink | O | O | m2m:mgmtLinkRef | 1 link to a [authenticationProfile]. See note. | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| NOTE: The SUID in the linked _[authenticationProfile]_ instance constrains the security framework to be used with the Authentication Profile. The security frameworks used with the _[dataCollection]_ resource are End-to-End Security of Primitives (ESPrim). The entity composing a _[dataCollection]_ instance is expected to confirm that the linked Authentication Profile contains a SUID corresponding to ESPrim. The SUIDs corresponding to ESPrim security frameworks are the values 13, 23, 33 or 43 as defined in oneM2M TS-0004 [\[4\]](#_ref_4). | ++---------------------------+---------------------------+-------------------+---------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.4 Resource [authenticationProfile] #### 7.2.4.1 Introduction -**Table 7.2.4.1-1: Data Type Definition of [_authenticationProfile_ ]**<a name="table_7.2.4.1-1"></a> +**Table 7.2.4.1-1: Data Type Definition of _[authenticationProfile]_**<a name="table_7.2.4.1-1"></a> -|**Data Type** **ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |authenticationProfile |DCFG-authenticationProfile.xsd | | - - -**Table 7.2.4.1-2: Resource specific attributes of [_authenticationProfile_ ]**<a name="table_7.2.4.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | **Default Value and Constraints** | -+:=====================+:==========================+:==============+:==============================================================+:=============================================+ -| **Attribute Name** | **Create** | **Update** | **Data Type** | **Default Value and Constraints** | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1022 (authenticationProfile). | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| SUID | M | NP | m2m:suid | Allowed values are listed in table 7.1.43. | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| TLSCiphersuites | O | O | dcfg:listOfTLSCiphersuite | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| symmKeyID | O | NP | sec:credentialID | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| symmKeyValue | O | NP | xs:hexBinary | The minimum key length is 256 bits. | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| MAFKeyRegLabels | O | NP | m2m:labels | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| MAFKeyRegDuration | O | NP | xs:duration | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| mycertFingerprint | O | NP | dcfg:niURI or dcfg:nihURI | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| rawPubKeyID | O | NP | dcfg:niURI or dcfg:nihURI | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| M2M-Sub-ID | O | NP | m2m:ID | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ -| mgmtLink | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+---------------+---------------------------------------------------------------+----------------------------------------------+ - - - -**Table 7.2.4.13: Child resources of [_authenticationProfile_ ] resource**<a name="table_7.2.4.13"></a> - -|**Child Resource Type** |**Child Resource Name** |**Multiplicity** |**Ref. to in Resource Type Definition** | +**Table 7.2.4.1-2: Resource specific attributes of _[authenticationProfile]_**<a name="table_7.2.4.1-2"></a> + ++----------------------+---------------------+------------------------------------------------------+----------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:=====================================================+:=============================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1022 (authenticationProfile). | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| SUID | M | NP | m2m:suid | Allowed values are listed in table 7.1.43. | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| TLSCiphersuites | O | O | dcfg:listOfTLSCiphersuite | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| symmKeyID | O | NP | sec:credentialID | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| symmKeyValue | O | NP | xs:hexBinary | The minimum key length is 256 bits. | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| MAFKeyRegLabels | O | NP | m2m:labels | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| MAFKeyRegDuration | O | NP | xs:duration | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| mycertFingerprint | O | NP | dcfg:niURI or dcfg:nihURI | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| rawPubKeyID | O | NP | dcfg:niURI or dcfg:nihURI | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| M2M-Sub-ID | O | NP | m2m:ID | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ +| mgmtLink | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+----------------------------------------------+ + + +**Table 7.2.4.13: Child resources of _[authenticationProfile]_ resource**<a name="table_7.2.4.13"></a> + +|Child Resource Type |Child Resource Name |Multiplicity |Ref. to in Resource Type Definition | |-|-|-|-| |<subscription> |[variable] |0..n |Clause 7.4.8 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | - - #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.5 Resource [myCertFileCred] #### 7.2.5.1 Introduction -**Table 7.2.5.1-1: Data Type Definition of [_myCertFileCred_ ]**<a name="table_7.2.5.1-1"></a> +**Table 7.2.5.1-1: Data Type Definition of _[myCertFileCred]_**<a name="table_7.2.5.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |myCertFileCred |DCFG-myCertFileCred.xsd | | - - - - - - - - - - - - - -**Table 7.2.5.1-2: Resource specific attributes of [_myCertFileCred_ ]**<a name="table_7.2.5.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | **Default Value and Constraints** | -+:=====================+:==========================+:==================+:==============================================================+:====================================================================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | **Default Value and Constraints** | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1023 (myCertFileCred) | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| SUIDs | M | O | xs:list of m2m:suid | Allowed values are listed in table 7.1.5-3. | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| myCertFileFormat | M | NP | xs:anyURI | Media Type of myCertFileContent attribute. Default is "application/pkcs7-mime". | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ -| myCertFileContent | M | NP | xs:string | Certificate or certificate chain. Default media-type is "application/pkcs7-mime". | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------------------------------------------------------+ - - - - - -**Table 7.2.5.13: Child resources of [_myCertFileCred_ ] resource**<a name="table_7.2.5.13"></a> - -|**Child Resource Type** |**Child Resource Name** |**Multiplicity** |**Ref. to in Resource Type Definition** | +**Table 7.2.5.1-2: Resource specific attributes of _[myCertFileCred]_**<a name="table_7.2.5.1-2"></a> + ++----------------------+---------------------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:=====================================================+:====================================================================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1023 (myCertFileCred) | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| SUIDs | M | O | xs:list of m2m:suid | Allowed values are listed in table 7.1.5-3. | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| myCertFileFormat | M | NP | xs:anyURI | Media Type of myCertFileContent attribute. Default is "application/pkcs7-mime". | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ +| myCertFileContent | M | NP | xs:string | Certificate or certificate chain. Default media-type is "application/pkcs7-mime". | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------------------------------------------------------------+ + + +**Table 7.2.5.13: Child resources of _[myCertFileCred]_ resource**<a name="table_7.2.5.13"></a> + +|Child Resource Type |Child Resource Name |Multiplicity |Ref. to in Resource Type Definition | |-|-|-|-| |<subscription> |[variable] |0..n |Clause 7.4.8 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | - - #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.6 Resource [trustAnchorCred] #### 7.2.6.1 Introduction -**Table 7.2.6.1-1: Data Type Definition of [_trustAnchorCred_ ]**<a name="table_7.2.6.1-1"></a> +**Table 7.2.6.1-1: Data Type Definition of _[trustAnchorCred]_**<a name="table_7.2.6.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |trustAnchorCred |DCFG-trustAnchorCred.xsd | | +**Table 7.2.6.1-2: Resource specific attributes of _[trustAnchorCred]_**<a name="table_7.2.6.1-2"></a> ++----------------------+---------------------+------------------------------------------------------+-------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:=====================================================+:==============================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1024 (trustAnchorCred) | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ +| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ +| certFingerprint | M | NP | dcfg:niURI | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ +| URI | M | O | xs:anyURI | | ++----------------------+---------+-----------+------------------------------------------------------+-------------------------------+ -**Table 7.2.6.1-2: Resource specific attributes of [_trustAnchorCred_ ]**<a name="table_7.2.6.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | **Default Value and Constraints** | -+:=====================+:==========================+:==================+:==============================================================+:====================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | **Default Value and Constraints** | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1024 (trustAnchorCred) | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| objectID | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| certFingerprint | M | NP | dcfg:niURI | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ -| URI | M | O | xs:anyURI | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+-------------------------------------+ +**Table 7.2.6.13: Child resources of _[trustAnchorCred]_ resource**<a name="table_7.2.6.13"></a> - -**Table 7.2.6.13: Child resources of [_trustAnchorCred_ ] resource**<a name="table_7.2.6.13"></a> - -|**Child Resource Type** |**Child Resource Name** |**Multiplicity** |**Ref. to in Resource Type Definition** | +|Child Resource Type |Child Resource Name |Multiplicity |Ref. to in Resource Type Definition | |-|-|-|-| |<subscription> |[variable] |0..n |Clause 7.4.8 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | - #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. + +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.7 Resource [MAFClientRegCfg] #### 7.2.7.1 Introduction -**Table 7.2.7.1-1: Data Type Definition of [_MAFClientRegCfg_ ]**<a name="table_7.2.7.1-1"></a> +**Table 7.2.7.1-1: Data Type Definition of _[MAFClientRegCfg]_**<a name="table_7.2.7.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |MAFClientRegCfg |DCFG-MAFClientRegCfg.xsd | | - - -**Table 7.2.7.1-2: Resource specific attributes of [_MAFClientRegCfg_ ]**<a name="table_7.2.7.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | **Default Value and Constraints** | -+:==============================================================================================================================+:==========================+:==============+:===============================================================+:============================================================+ -| **Attribute Name** | **Create** | **Update** | **Data Type** | **Default Value and Constraints** | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1025 (MAFClientRegCfg) | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| fqdn | M | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| adminFQDN | M | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| httpPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| coapPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| websocketPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| mgmtLink | M | O | m2m:mgmtLinkRef | 1 link to a [_authenticationProfile_ ] resources instance | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ -| NOTE: For further details of these attributes, see clauses 8.8.3.2 and 12.4.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+---------------+----------------------------------------------------------------+-------------------------------------------------------------+ - - - -**Table 7.2.7.13: Child resources of [_MAFClientRegCfg_ ] resource**<a name="table_7.2.7.13"></a> - -|**Child Resource Type** |**Child Resource Name** |**Multiplicity** |**Ref. to in Resource Type Definition** | +**Table 7.2.7.1-2: Resource specific attributes of _[MAFClientRegCfg]_**<a name="table_7.2.7.1-2"></a> + ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:======================================================+:============================================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1025 (MAFClientRegCfg) | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| fqdn | M | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| adminFQDN | M | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| httpPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| coapPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| websocketPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| mgmtLink | M | O | m2m:mgmtLinkRef | 1 link to a _[authenticationProfile]_ resources instance | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ +| NOTE: For further details of these attributes, see clauses 8.8.3.2 and 12.4.2 of oneM2M TS-0003 [\[3\]](#_ref_3). | ++----------------------+---------+-----------+-------------------------------------------------------+-------------------------------------------------------------+ + +**Table 7.2.7.13: Child resources of __MAFClientRegCfg]_ resource**<a name="table_7.2.7.13"></a> + +|Child Resource Type |Child Resource Name |Multiplicity |Ref. to in Resource Type Definition | |-|-|-|-| |<subscription> |[variable] |0..n |Clause 7.4.8 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | - - #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.8 Resource [MEFClientRegCfg] #### 7.2.8.1 Introduction -**Table 7.2.8.1-1: Data Type Definition of [_MEFClientRegCfg_ ]**<a name="table_7.2.8.1-1"></a> +**Table 7.2.8.1-1: Data Type Definition of _[MEFClientRegCfg]_**<a name="table_7.2.8.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |MEFClientRegCfg |DCFG-MEFClientRegCfg.xsd | | - - -**Table 7.2.8.1-2: Resource specific attributes of [_MEFClientRegCfg_ ]**<a name="table_7.2.8.1-2"></a> - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | Default Value and Constraints | -+:==============================================================================================================================+:==========================+:==================+:===============================================================+:====================================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | Default Value and Constraints | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1026 (MEFClientRegCfg) | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| fqdn | M | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| adminFQDN | M | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| httpPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| coapPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| websocketPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 <a href="#_ref_3">[3]</a> | At least one of these attributes shall be present | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| mgmtLink | M | O | m2m:mgmtLinkRef | | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ -| NOTE: For further details of these attributes, see clauses 8.3.7.2 and 12.4.2 of oneM2M TS-0003 <a href="#_ref_3">[3]</a>. | -+-------------------------------------------------------------------------------------------------------------------------------+---------------------------+-------------------+----------------------------------------------------------------+-----------------------------------------------------+ - - - -**Table 7.2.8.13: Child resources of [_MEFClientRegCfg_ ] resource**<a name="table_7.2.8.13"></a> - -|**Child Resource Type** |**Child Resource Name** |**Multiplicity** |**Ref. to in Resource Type Definition** | +**Table 7.2.8.1-2: Resource specific attributes of _[MEFClientRegCfg]_**<a name="table_7.2.8.1-2"></a> + + ++----------------------+---------------------+-------------------------------------------------------+-----------------------------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:======================================================+:====================================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1026 (MEFClientRegCfg) | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| fqdn | M | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| adminFQDN | M | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| httpPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| coapPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| websocketPort | O | NP | See table 12.4.2-1 of oneM2M TS-0003 [\[3\]](#_ref_3) | At least one of these attributes shall be present | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| mgmtLink | M | O | m2m:mgmtLinkRef | | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ +| NOTE: For further details of these attributes, see clauses 8.3.7.2 and 12.4.2 of oneM2M TS-0003 [\[3\]](#_ref_3). | ++----------------------+---------+-----------+-------------------------------------------------------+-----------------------------------------------------+ + +**Table 7.2.8.13: Child resources of _[MEFClientRegCfg]_ resource**<a name="table_7.2.8.13"></a> + +|hild Resource Type |Child Resource Name |Multiplicity |Ref. to in Resource Type Definition | |-|-|-|-| |<subscription> |[variable] |0..n |Clause 7.4.8 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | - - #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<_mgmtObj_ > specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '_<mgmtObj>_ specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.9 Resource [OAuth2Authentication] @@ -1425,46 +1292,36 @@ When management is performed using technology specific protocols, the procedures #### 7.2.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]**<a name="table_7.2.9.1-1"></a> -|**Data Type ID** |**File Name** |**Note** | +|Data Type ID |File Name |Note | |-|-|-| |OAuth2Authentication |DCFG-OAuth2.xsd | | - - - - - - **Table 7.2.9.1-2: Resource specific attributes of [OAuth2Authentication]**<a name="table_7.2.9.1-2"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | Default Value and Constraints | -+:=====================+:==========================+:==================+:==============================================================+:================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | Default Value and Constraints | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1027 (OAuth2Authentication) | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| accessToken | M | O | xs:string | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| refreshToken | M | O | xs:string | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ - ++----------------------+---------------------+------------------------------------------------------+---------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:=====================================================+:================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1027 (OAuth2Authentication) | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ +| accessToken | M | O | xs:string | | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ +| refreshToken | M | O | xs:string | | ++----------------------+---------+-----------+------------------------------------------------------+---------------------------------+ #### 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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>,'<_mgmtObj_ > specific procedures' shall be used. There are no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 in oneM2M TS-0004 <a href="#_ref_4">[4]</a>,'_<mgmtObj> specific procedures' shall be used. There are no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. ### 7.2.10 Resource [wifiClient] @@ -1472,7 +1329,6 @@ When management is performed using technology specific protocols, the procedures #### 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.11: Data Type Definition of [wifiClient]**<a name="table_7.2.10.11"></a> |Data Type ID |File Name |Note | @@ -1480,48 +1336,43 @@ This specialization of <mgmtObj> is used to store configuration of Wi-Fi® |wifiClient |DCFG-wifiClient.xsd | | - - **Table 7.2.10.12: Resource specific attributes of [wifiClient]**<a name="table_7.2.10.12"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| **Attribute Name** | **Request Optionality** | **Data Type** | Default Value and Constraints | -+:=====================+:==========================+:==================+:==============================================================+:================================+ -| **Attribute Name** | **C** **reate** | **U** **pdate** | **Data Type** | Default Value and Constraints | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | 1028 (wifiClient) | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| ssid | M | O | dcfg:ssid | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| credentials | O | O | dcfg:wifiCredentials | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| macAddress | O | O | xs:string | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| channel | O | O | xs:integer | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| update | O | O | xs:boolean | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| scan | M | O | xs:boolean | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| toggleRadioStatus | O | O | xs:boolean | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| scanResult | O | O | dcfg:listOfSsids | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| updateStatus | O | O | m2m:actionStatus | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| connectionStatus | O | O | dcfg:wifiConnectionStatus | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ -| radioStatus | O | O | xs:boolean | | -+----------------------+---------------------------+-------------------+---------------------------------------------------------------+---------------------------------+ - ++----------------------+---------------------+-------------------------------------------------------+---------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=====================+:========+:==========+:======================================================+:================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | 1028 (wifiClient) | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4) | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| ssid | M | O | dcfg:ssid | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| credentials | O | O | dcfg:wifiCredentials | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| macAddress | O | O | xs:string | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| channel | O | O | xs:integer | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| update | O | O | xs:boolean | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| scan | M | O | xs:boolean | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| toggleRadioStatus | O | O | xs:boolean | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| scanResult | O | O | dcfg:listOfSsids | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| updateStatus | O | O | m2m:actionStatus | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| connectionStatus | O | O | dcfg:wifiConnectionStatus | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| radioStatus | O | O | xs:boolean | | ++----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ #### 7.2.10.2 Resource specific procedure on CRUD operations @@ -1531,8 +1382,8 @@ When management is performed using technology specific protocols, the procedures ### 7.2.11 Resource [credentials] #### 7.2.11.1 Introduction -This specialization of <mgmtObj> is used to store credentials on the client device for authentications. +This specialization of <mgmtObj> is used to store credentials on the client device for authentications. **Table 7.2.11.11: Data Type Definition of [credentials]**<a name="table_7.2.11.11"></a> @@ -1541,45 +1392,40 @@ This specialization of <mgmtObj> is used to store credentials on the client d |credentials |DCFG-credentials-v4\_0\_0.xsd | | - - **Table 7.2.11.12: Resource specific attributes of [credentials]**<a name="table_7.2.11.12"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | -+:===================+:======================+:==============+:===============================================================+:================================+ -| Attribute Name | Create | Update | Data Type | Default Value and Constraints | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | 1029 (credentials) | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| purpose | O | O | xs:string | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| credentialID | O | O | xs:string | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| credentialSecret | O | O | xs:string | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| credentialToken | O | O | Xs:string | | -+--------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ ++--------------------+---------------------+-------------------------------------------------------+---------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:===================+:========+:==========+:======================================================+:================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | 1029 (credentials) | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| purpose | O | O | xs:string | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| credentialID | O | O | xs:string | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| credentialSecret | O | O | xs:string | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| credentialToken | O | O | Xs:string | | ++--------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ #### 7.2.11.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 oneM2M TS-0004 <a href="#_ref_4">[4]</a> shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. - +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. ### 7.2.12 Resource [SIM] #### 7.2.12.1 Introduction -This specialization of <mgmtObj> is used to store configuration of Subscriber Identification Module (SIM) and status information. +This specialization of <mgmtObj> is used to store configuration of Subscriber Identification Module (SIM) and status information. **Table 7.2.12.11: Data Type Definition of [SIM]**<a name="table_7.2.12.11"></a> @@ -1587,44 +1433,41 @@ This specialization of <mgmtObj> is used to store configuration of Subscriber |-|-|-| |SIM |DCFG-SIM.xsd | | - - - **Table 7.2.12.12: Resource specific attributes of [SIM]**<a name="table_7.2.12.12"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | -+:======================+:======================+:==============+:===============================================================+:================================+ -| Attribute Name | Create | Update | Data Type | Default Value and Constraints | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | 1030 (SIM) | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| imsi | O | O | dcfg:imsi | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| iccid | M | NP | dcfg:iccid | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| simStatus | O | O | dcfg:simStatus | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| simType | O | O | dcfg:simType | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| serviceProviderName | O | O | xs:string | | -+-----------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ ++-----------------------+---------------------+-------------------------------------------------------+---------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:======================+:========+:==========+:======================================================+:================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | 1030 (SIM) | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| imsi | O | O | dcfg:imsi | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| iccid | M | NP | dcfg:iccid | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| simStatus | O | O | dcfg:simStatus | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| simType | O | O | dcfg:simType | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| serviceProviderName | O | O | xs:string | | ++-----------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ #### 7.2.12.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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS 0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ### 7.2.13 Resource [mobileNetwork] #### 7.2.13.1 Introduction + This specialization of <mgmtObj> is used to store configuration of the currently connected mobile network. @@ -1634,88 +1477,76 @@ This specialization of <mgmtObj> is used to store configuration of the curren |-|-|-| |mobileNetwork |DCFG-mobileNetwork.xsd | | - - - **Table 7.2.12.12: Resource specific attributes of [mobileNetwork]**<a name="table_7.2.12.12"></a> -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | -+:=============================+:======================+:==============+:===============================================================+:================================+ -| Attribute Name | Create | Update | Data Type | Default Value and Constraints | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | 1031 (mobileNetwork) | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| description | O | O | See clause 7.4.15 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| cellularNetworkBearer | O | O | dcfg:cellularNetworkBearerType | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _radioSignalStrength_ | O | O | xs:integer | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _linkQuality_ | O | O | xs:integer | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _ipAddresses_ | O | O | list of m2m:ipAddress | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _routerIPAddresses_ | O | O | list of m2m:ipAddress | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _apn_ | O | O | dcfg:apn | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _cellID_ | O | O | xs:integer | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _smnc_ | O | O | xs:integer | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _smcc_ | O | O | xs:integer | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _lac_ | O | O | dcfg:lac | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ -| _coverageEnhancementLevel_ | O | O | dcfg:coverageEnhancementLevel | | -+------------------------------+-----------------------+---------------+----------------------------------------------------------------+---------------------------------+ - ++------------------------------+---------------------+-------------------------------------------------------+---------------------------------+ +| Attribute Name | Request Optionality | Data Type | Default Value and Constraints | +| +---------+-----------+ | | +| | Create | Update | | | ++:=============================+:========+:==========+:======================================================+:================================+ +| mgmtDefinition | M | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | 1031 (mobileNetwork) | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectIDs | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| objectPaths | O | NP | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| description | O | O | See clause 7.4.15 of oneM2M TS-0004 [\[4\]](#_ref_4). | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| cellularNetworkBearer | O | O | dcfg:cellularNetworkBearerType | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _radioSignalStrength_ | O | O | xs:integer | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _linkQuality_ | O | O | xs:integer | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _ipAddresses_ | O | O | list of m2m:ipAddress | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _routerIPAddresses_ | O | O | list of m2m:ipAddress | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _apn_ | O | O | dcfg:apn | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _cellID_ | O | O | xs:integer | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _smnc_ | O | O | xs:integer | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _smcc_ | O | O | xs:integer | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _lac_ | O | O | dcfg:lac | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ +| _coverageEnhancementLevel_ | O | O | dcfg:coverageEnhancementLevel | | ++------------------------------+---------+-----------+-------------------------------------------------------+---------------------------------+ #### 7.2.13.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 oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS 0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. - - - - +When management is performed using technology specific protocols, the procedures defined in clause 7.4.15.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>, '<mgmtObj> specific procedures' shall be used. There is no change from the generic procedures in clause 7.2.2 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> for operations on this resource. oneM2M TS-0005 <a href="#_ref_5">[5]</a> and oneM2M TS 0006 <a href="#_ref_6">[6]</a> provide the mapping of these resources into the technology specific protocol data model. ## 7.3 Data formats for device configuration ### 7.3.1 Introduction + Clause 7.3 defines data formats of resource attributes and parameters used in present document. Any data types of XML elements defined for use in present document shall be one of name spaces in table 7.3.1-1. - **Table 7.3.1-1: Namespaces used in present document**<a name="table_7.3.1-1"></a> -|**Name space** |**prefix** |**N** **ame** **space definition** | +|Name space |prefix |Namespace definition | |-|-|-| |oneM2M protocol CDT |m2m: |http://www.onem2m.org/xml/protocol | |Device Configuration |dcfg: |http://www.onem2m.org/xml/deviceConfig | |oneM2M Security |sec: |http://www.onem2m.org/xml/securityProtocols | - - ### 7.3.2 Simple oneM2M data types for device configuration -Table 7.3.2-1 describes simple data type definitions specific to security. The types in table 7.3.2-1 are either: +Table 7.3.2-1 describes simple data type definitions specific to security. The types in table 7.3.2-1 are either: - Atomic data types derived from XML Schema data types by restrictions other than enumeration. - List data types constructed from other XML Schema or oneM2M-defined atomic data types. **Table 7.3.2-1: oneM2M simple data types for device configuration**<a name="table_7.3.2-1"></a> -|**XSD type name** |**Used for** |**Examples** |**Description** | +|XSD type name |Used for |Examples |Description | |-|-|-|-| |dcfg:TLSCiphersuite |A TLS Ciphersuite identifier |C0A5 |Four hexadecimal characters representing a TLS Cipher suite identifier. The list of TLS cipher suites identifiers can be found at the IANA TLS Cipher Suite Registry <a href="#_ref_8">[8]</a>. | |dcfg:ListOfTLSCiphersuite |A list of TLS Ciphersuite identifiers | |xs:list of elements of data type dcfg:TLSCiphersuite. | @@ -1729,14 +1560,11 @@ Table 7.3.2-1 describes simple data type definitions specific to security. The t |dcfg:lac |Location Area Code for a cellular network |0x0523 |A Location Area Code is a fixed length code of 2 octets identifying a location area. The data type is xs:integer. | - - - ### 7.3.3 Enumerated oneM2M data types for device configuration #### 7.3.3.1 dcfg:wifiConnectionStatus -Used to indicate Wi-Fi® connection status. +Used to indicate Wi-Fi® connection status. **Table 7.3.3.11: Interpretation of dcfg:wifiConnectionStatus**<a name="table_7.3.3.11"></a> @@ -1751,12 +1579,9 @@ Used to indicate Wi-Fi® connection status. |6 |Lost | | - - #### 7.3.3.2 dcfg:wifiEncryptionType Used for indicating which Wi-Fi® encryption protocol is used to provide security in wireless network. - **Table 7.3.3.2-1: Interpretation of dcfg:wifiEncyrptionType**<a name="table_7.3.3.2-1"></a> |Value |Interpretation |Note | @@ -1771,13 +1596,9 @@ Used for indicating which Wi-Fi® encryption protocol is used to provide secu |8 |WPA3 Enterprise | | - - #### 7.3.3.3 dcfg:simStatus -Used for indicating a SIM status. - - +Used for indicating a SIM status. **Table 7.3.3.3-1: Interpretation of dcfg:simStatus**<a name="table_7.3.3.3-1"></a> @@ -1787,13 +1608,9 @@ Used for indicating a SIM status. |1 |active | | - - #### 7.3.3.4 dcfg:simType -Used for indicating a SIM type. - - +Used for indicating a SIM type. **Table 7.3.3.4-1: Interpretation of dcfg:simType**<a name="table_7.3.3.4-1"></a> @@ -1806,9 +1623,8 @@ Used for indicating a SIM type. #### 7.3.3.5 dcfg:cellularNetworkBearerType -Used for indicating a Cellular Network Bearer type. - +Used for indicating a Cellular Network Bearer type. **Table 7.3.3.5-1: Interpretation of dcfg:cellularNetworkBearerType**<a name="table_7.3.3.5-1"></a> @@ -1825,13 +1641,9 @@ Used for indicating a Cellular Network Bearer type. |7 |NB-IoT | | - - #### 7.3.3.6 dcfg:coverageEnhancementLevel -Used for indicating a Coverage Enhancement Level. - - +Used for indicating a Coverage Enhancement Level. **Table 7.3.3.6-1: Interpretation of dcfg:coverageEnhancementLevel**<a name="table_7.3.3.6-1"></a> @@ -1844,17 +1656,15 @@ Used for indicating a Coverage Enhancement Level. |4 |Coverage Enhancement level 3 | | - - ### 7.3.4 Complex type definitions #### 7.3.4.1 dcfg:wifiCredentials -Used for credentials in [wifiClient] Management Object resource. Values contained in username, password, wep.key and wpa.psk attributes shall not be readable. Each Retrieve request shall be forwarded to device and from there the data shall be retrieved. +Used for credentials in [wifiClient] Management Object resource. Values contained in username, password, wep.key and wpa.psk attributes shall not be readable. Each Retrieve request shall be forwarded to device and from there the data shall be retrieved. **Table 7.3.4.1-1: Type Definition of dcfg:wifiCredentials**<a name="table_7.3.4.1-1"></a> -|**Element Path** |**Element Data Type** |**Multiplicity** |**Note** | +|Element Path |Element Data Type |Multiplicity |Note | |-|-|-|-| |encryptionType |dcfg:wifiEncryptionType |1 |Indicates type of encryption used to provide network security | |username |xs:string |0..1 |Indicates username used to authenticate user in WPA-Enterprise, WPA2-Enterprise or WPA3-Enterprise protocols<br />Only valid if encryptionType=6,7 or 8 | @@ -1863,135 +1673,133 @@ Used for credentials in [wifiClient] Management Object resource. Values containe |wpaPsk |xs:string |0..1 |Indicates WPA Pre Shared Key<br />Only valid if field encryptionType = 3,4 or 5 | - - # 8 Procedures ## 8.1 <mgmtObj> life cycle procedures ### 8.1.1 Introduction -The life cycle of the <_mgmtObj_ > resource in the Hosting CSE(IN-CSE) is established either through the: +The life cycle of the _<mgmtObj>_ resource in the Hosting CSE(IN-CSE) is established either through the: -- Provisioning of the <_mgmtObj_ > resource by the Configuration AE. -- Discovery of the <_mgmtObj_ > resource by the Hosting CSE using the methods described in clause 6.1. +- Provisioning of the _<mgmtObj>_ resource by the Configuration AE. +- Discovery of the _<mgmtObj>_ resource by the Hosting CSE using the methods described in clause 6.1. ### 8.1.2 Setting configuration information on <mgmtObj> resource -The Configuration AE is able to configure the <_mgmtObj_ > resources used for device configuration by either creating the <_mgmtObj_ > resource or updating existing <_mgmtObj_ > resources for the targeted AE or CSE. Likewise, the Configuration AE can delete the <_mgmtObj_ > resource as part of a decommissioning process. +The Configuration AE is able to configure the _<mgmtObj>_ resources used for device configuration by either creating the _<mgmtObj>_ resource or updating existing _<mgmtObj>_ resources for the targeted AE or CSE. Likewise, the Configuration AE can delete the _<mgmtObj>_ resource as part of a decommissioning process. -In some scenarios the <_mgmtObj_ > resource may already exist due to pre-provisioning or a previous discovery action by the IN-CSE's interaction with the Configuration IPE, DM Server or ASN/MN or ADN node. As such the Configuration AE needs to first discover if the <_mgmtObj_ > resource exists in the Hosting CSE. As <_mgmtObj_ > resources are represented under the <node> resource of the ASN/MN or ADN node, the discovery operation's scope can use the <node> resource within the discovery criteria. Based on the results of the discovery the Configuration AE will either create or update the <_mgmtObj_ > resource. Figure 8.1.2-1 depicts this flow. +In some scenarios the _<mgmtObj>_ resource may already exist due to pre-provisioning or a previous discovery action by the IN-CSE's interaction with the Configuration IPE, DM Server or ASN/MN or ADN node. As such the Configuration AE needs to first discover if the _<mgmtObj>_ resource exists in the Hosting CSE. As _<mgmtObj>_ resources are represented under the <node> resource of the ASN/MN or ADN node, the discovery operation's scope can use the <node> resource within the discovery criteria. Based on the results of the discovery the Configuration AE will either create or update the _<mgmtObj>_ resource. Figure 8.1.2-1 depicts this flow. - + -**Figure 8.1.2-1: Configuring attributes of a <_mgmtObj_ > resource** +**Figure 8.1.2-1: Configuring attributes of a _<mgmtObj>_ resource** -Likewise, the Configuration AE may use the same approach to discover when deleting the <_mgmtObj_ > resource as part of a decommissioning process or retrieval of the <_mgmtObj_ > resource. +Likewise, the Configuration AE may use the same approach to discover when deleting the _<mgmtObj>_ resource as part of a decommissioning process or retrieval of the _<mgmtObj>_ resource. -> NOTE: In order for the IN-CSE to forward the request onto the DM Server, the <_mgmtObj_ > resource is required to be configured with the path to the resource in the context of the technology specific protocol (e.g. LWM2M URI <a href="#_ref_i.4">[i.4]</a>, OMA-DM path <a href="#_ref_i.3">[i.3]</a>, BBF TR-069 path <a href="#_ref_i.2">[i.2]</a>). The fully qualified domain name can also be used if the IN-CSE does not know the address of the DM Server. +> NOTE: In order for the IN-CSE to forward the request onto the DM Server, the _<mgmtObj>_ resource is required to be configured with the path to the resource in the context of the technology specific protocol (e.g. LWM2M URI <a href="#_ref_i.4">[i.4]</a>, OMA-DM path <a href="#_ref_i.3">[i.3]</a>, BBF TR-069 path <a href="#_ref_i.2">[i.2]</a>). The fully qualified domain name can also be used if the IN-CSE does not know the address of the DM Server. ### 8.1.3 Management of <mgmtObj> resource on ASN/MN/ADN nodes #### 8.1.3.1 Introduction -Management of the <_mgmtObj_ > object resources on ASN/MN or ADN nodes may be managed using one of the architectural methods described in clause 6.1. +Management of the _<mgmtObj>_ object resources on ASN/MN or ADN nodes may be managed using one of the architectural methods described in clause 6.1. #### 8.1.3.2 Management using device management technologies -Clause 10.2.8 '<_mgmtObj_ > Resource Procedures' of oneM2M TS-0001 <a href="#_ref_2">[2]</a> describes the procedures for M2M Nodes to represent their technology specific data as oneM2M resources within the IN-CSE. +Clause 10.2.8 '_<mgmtObj>_ Resource Procedures' of oneM2M TS-0001 <a href="#_ref_2">[2]</a> describes the procedures for M2M Nodes to represent their technology specific data as oneM2M resources within the IN-CSE. - + + **Figure 8.1.3.2-1: Management using Device Management technologies** -1. The Configuration AE issues a request for <_mgmtObj_ > resource for an ASN/MN/ADN node that is managed using Device Management technologies. -1. The IN- CSE processes the request issued by Configuration AE. -1. The IN-CSE executes the Device Management command which is mapped from operation on <_mgmtObj_ > resource to external management technologies. +1. The Configuration AE issues a request for _<mgmtObj>_ resource for an ASN/MN/ADN node that is managed using Device Management technologies. +1. The IN-CSE processes the request issued by Configuration AE. +1. The IN-CSE executes the Device Management command which is mapped from operation on _<mgmtObj>_ resource to external management technologies. 1. The ASN/MN/ADN then creates, updates, deletes or retrieve the configuration parameters on the node, and returns the result of Device Management command. #### 8.1.3.3 Management using the Mca or Mcc reference point -Once M2M Service Layer operation is established between the AE or CSE and the Registrar/Hosting CSE, <_mgmtObj_ > resources may be managed using the Mca or Mcc reference point by the AE or CSE respectively subscribing to receive changes to the <_mgmtObj_ > resource using the subscription procedures defined in clause 10.2.11 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. Establishment of the M2M Service Layer operations includes actions such as establishing the appropriate security associations and registration of the CSEs and AEs. +Once M2M Service Layer operation is established between the AE or CSE and the Registrar/Hosting CSE, _<mgmtObj>_ resources may be managed using the Mca or Mcc reference point by the AE or CSE respectively subscribing to receive changes to the _<mgmtObj>_ resource using the subscription procedures defined in clause 10.2.11 of oneM2M TS-0001 <a href="#_ref_2">[2]</a>. Establishment of the M2M Service Layer operations includes actions such as establishing the appropriate security associations and registration of the CSEs and AEs. - + **Figure 8.1.3.3-1: Management using the Mca or Mcc reference point** -1. Once M2M Service Layer operation is established, the AE or CSE on the ASN/MN/ADN node subscribes to the <_mgmtObj_ > resource which is associated with the specific M2M Application functionality creating <subscription> resource. -1. When the Configurator AE creates, updates or delete the <_mgmtObj_ > resource, the Configuration AE issues a request on the <_mgmtObj_ > resource. -1. The Hosting CSE for the <_mgmtObj_ > resource performs the operation on the resource as Receiver. +1. Once M2M Service Layer operation is established, the AE or CSE on the ASN/MN/ADN node subscribes to the _<mgmtObj>_ resource which is associated with the specific M2M Application functionality creating <subscription> resource. +1. When the Configurator AE creates, updates or delete the _<mgmtObj>_ resource, the Configuration AE issues a request on the _<mgmtObj>_ resource. +1. The Hosting CSE for the _<mgmtObj>_ resource performs the operation on the resource as Receiver. 1. The Hosting CSE notifies the subscribed AE or CSE as the subscribed event message. 1. The AE or CSE configures the M2M Application on the ASN/MN or ADN node. -Alternatively, <_mgmtObj_ > specializations hosted by the IN-CSE may be announced to a CSE on a MN or ASN node depending on whether the <_mgmtObj_ > specialization type is announceable. If a <_mgmtObj_ > specialization type is not announceable, the MN or ASN nodes shall be managed using the subscription mechanism as shown in the Figure 8.1.3.3-1. - -The following <_mgmtObj_ > specializations specified in the present document are announceable (i.e. announceable variants of this resource type are defined in the XSD of the respective <_mgmtObj_ > specialization): +Alternatively, _<mgmtObj>_ specializations hosted by the IN-CSE may be announced to a CSE on a MN or ASN node depending on whether the _<mgmtObj>_ specialization type is announceable. If a _<mgmtObj>_ specialization type is not announceable, the MN or ASN nodes shall be managed using the subscription mechanism as shown in the Figure 8.1.3.3-1. +The following _<mgmtObj>_ specializations specified in the present document are announceable (i.e. announceable variants of this resource type are defined in the XSD of the respective _<mgmtObj>_ specialization): -- _[registration], [_ _dataCollection_ _]_ +- _[registration]_, _[dataCollection]_ -The following <_mgmtObj_ > specializations specified in the present document are not announceable (i.e. announceable variants of this resource type are not defined in the XSD of the respective <_mgmtObj_ > specialization): +The following _<mgmtObj>_ specializations specified in the present document are not announceable (i.e. announceable variants of this resource type are not defined in the XSD of the respective _<mgmtObj> specialization): - _[_ _authenticationProfile_ _], [_ _myCertFileCred_ _], [_ _trustAnchorCred_ _], [_ _MAFClientRegCfg_ _], [_ _MEFClientRegCfg_ _]_ _,_ _[OAuth2Authentication], [_ _wificlient_ _], [credentials]_ +- _[authenticationProfile]_, _[myCertFileCred]_, _[trustAnchorCred]_, _[MAFClientRegCfg]_, _[MEFClientRegCfg]_, _[OAuth2Authentication]_, _[wificlient]_, _[credentials]_ - -When a <_mgmtObj_ > specialization is announced to a CSE on a MN or ASN node, a <_mgmtObjAnnc_ > resource specialization is created in this CSE. The AE residing on the same node as the CSE may subscribe to the <_mgmtObjAnnc_ > specialization for receiving notifications when the original <_mgmtObj_ > is updated by the Configuration AE. +When a _<mgmtObj>_ specialization is announced to a CSE on a MN or ASN node, a _<mgmtObjAnnc>_ resource specialization is created in this CSE. The AE residing on the same node as the CSE may subscribe to the _<mgmtObjAnnc>_ specialization for receiving notifications when the original _<mgmtObj>_ is updated by the Configuration AE. #### 8.1.3.4 Management using the oneM2M IPE technology -When ASN/MN or ADN nodes are configured using a Configuration IPE, the ASN/MN/ADN may periodically request the Configuration IPE to configure the ASN/MN/ADN node. The method that the ASN/MN/ADN uses to periodically request to be configured is unspecified in the present document. Once the Configuration IPE receives the request from the ASN/MN/ADN node, the Configuration IPE shall send a retrieve request to the Hosting CSE to obtain the applicable specialization of <_mgmtObj_ > resources for the ASN/MN/ADN node. How the Configuration IPE maintains the mapping between the ASN/MN/ADN and the associated <_node_ > and <_mgmtObj_ > resources is unspecified in the present document. + +When ASN/MN or ADN nodes are configured using a Configuration IPE, the ASN/MN/ADN may periodically request the Configuration IPE to configure the ASN/MN/ADN node. The method that the ASN/MN/ADN uses to periodically request to be configured is unspecified in the present document. Once the Configuration IPE receives the request from the ASN/MN/ADN node, the Configuration IPE shall send a retrieve request to the Hosting CSE to obtain the applicable specialization of _<mgmtObj>_ resources for the ASN/MN/ADN node. How the Configuration IPE maintains the mapping between the ASN/MN/ADN and the associated _<node>_ and _<mgmtObj>_ resources is unspecified in the present document. - + **Figure 8.1.3.4-1: Management using oneM2M IPE technology** -1. The Configuration AE issues a CRUD request to <_mgmtObj_ > resource which is associated with the functionality of targeted field device. +1. The Configuration AE issues a CRUD request to _<mgmtObj>_ resource which is associated with the functionality of targeted field device. 1. The Hosting CSE processes the CRUD request. 1. When the ASN/MN/ADN determines it needs to be configured, the ASN/MN/ADN issues a request to the Configuration IPE. -1. The Configuration IPE determines <_mgmtObj_ > resource to refer as the source of configuration parameter for the targeted field device, and issues an operation on the <_mgmtObj_ > or <_node_ > resource. -1. When the RETRIEVE request is successfully performed, the Configuration IPE transforms the <_mgmtObj_ > resource into a form understandable by ASN/MN/ADN node. +1. The Configuration IPE determines _<mgmtObj>_ resource to refer as the source of configuration parameter for the targeted field device, and issues an operation on the _<mgmtObj>_ or _<node>_ resource. +1. When the RETRIEVE request is successfully performed, the Configuration IPE transforms the _<mgmtObj>_ resource into a form understandable by ASN/MN/ADN node. 1. The ASN/MN/ADN configures setting parameters for the M2M Application. -> NOTE: One possible method of exchanging information between the Configuration IPE and the ASN/MN/ADN is to simply serialize the <_mgmtObj_ > resource using the MIME content types defined in clause 6.7 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> 'oneM2M specific MIME media types'. + +> NOTE: One possible method of exchanging information between the Configuration IPE and the ASN/MN/ADN is to simply serialize the _<mgmtObj>_ resource using the MIME content types defined in clause 6.7 of oneM2M TS-0004 <a href="#_ref_4">[4]</a> 'oneM2M specific MIME media types'. ## 8.2 Obtaining authentication credential procedure -When an ASN/MN or ADN node is required to be authenticated, a mgmtLink 'authProfile' referring to the <_mgmtObj_ > resource specialization for maintaining the Authentication Profiles shall be provided. +When an ASN/MN or ADN node is required to be authenticated, a mgmtLink 'authProfile' referring to the _<mgmtObj>_ resource specialization for maintaining the Authentication Profiles shall be provided. The Authentication Profile contains following information: - - Choice of TLS options. -- mgmtLinkRef(s) to the <_mgmtObj_ > which provides information required to obtain the credential(s). +- mgmtLinkRef(s) to the _<mgmtObj>_ which provides information required to obtain the credential(s). -When an ASN/MN or ADN node is establishing the appropriate security associations, the <_mgmtObj_ > specialization for Authentication Profile shall be used to identify the security related settings. +When an ASN/MN or ADN node is establishing the appropriate security associations, the _<mgmtObj>_ specialization for Authentication Profile shall be used to identify the security related settings. -Actual credential shall be obtained using the information on the <_mgmtObj_ > specializations (Authentication Credential Configuration) which is referred by mgmtLinkRef(s) from Authentication Profile. +Actual credential shall be obtained using the information on the _<mgmtObj>_ specializations (Authentication Credential Configuration) which is referred by mgmtLinkRef(s) from Authentication Profile. - + **Figure 8.2-1: Relationship between 'Authentication Profile' and 'Authentication Credential Configuration(s)'** ## 8.3 AE and CSE registration procedure -When an ASN/MN or ADN node receives the information in the [_registration_ ] resource, the AE or CSE performs the registration procedure for that type of resource. If the resource is for CSE, then the CSE registration procedure which is defined in clause 10.1.1.2.1 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> is used. If the resource is for AE, the Application Entity Registration procedure defined in clause 10.1.1.2.2 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> is used. +When an ASN/MN or ADN node receives the information in the _[registration]_ resource, the AE or CSE performs the registration procedure for that type of resource. If the resource is for CSE, then the CSE registration procedure which is defined in clause 10.1.1.2.1 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> is used. If the resource is for AE, the Application Entity Registration procedure defined in clause 10.1.1.2.2 of oneM2M TS-0001 <a href="#_ref_2">[2]</a> is used. Required parameter for registration procedures is retrieved as attribute value of [registration] resource. **Table 8.3-1: Required [registration] resource parameters for registration**<a name="table_8.3-1"></a> -|**attribute of** **[** **_registration_** **]** |**parameter** **in** **oneM2M** **TS-0001 [** 2**]/TS** **0004 [** 4**]** | +|attribute of _[registration]_ |parameter in oneM2M TS-0001 <a href="#_ref_2">[2]</a>/TS0004 <a href="#_ref_4">[4]</a> | |-|-| |originatorID |From primitive parameter | |PoA |CSE-PoA (Point of Access) | @@ -1999,16 +1807,17 @@ Required parameter for registration procedures is retrieved as attribute value o - ## 8.4 Enabling data collection by [dataCollection] resource + When an AE needs to measure or collect data to be later reported to a Hosting CSE , report measured data to a CSE, the ASN/MN/ADN may be instructed when to measure/collect the data and then when to report the measured/collected data along with where to place the data within the Hosting CSE. -Once AE is configured with the [_dataCollection_ ] resource AE performs CREATE operation for new <_contentInstance_ > resource as the child resource of <container> resource which is specified as 'containerPath' attribute of [_dataCollection_ ] resource to report the measured/collected data. The frequency of collection/measurement and reporting are accordingly specified as 'reportingSchedule' and 'measurementSchedule' attributes of the [_dataCollection_ ] resource. +Once AE is configured with the _[dataCollection]_ resource AE performs CREATE operation for new _<contentInstance>_ resource as the child resource of <container> resource which is specified as 'containerPath' attribute of _[dataCollection]_ resource to report the measured/collected data. The frequency of collection/measurement and reporting are accordingly specified as 'reportingSchedule' and 'measurementSchedule' attributes of the _[dataCollection]_ resource. # 9 Short Names ## 9.1 Introduction + Short names are introduced in clause 8.2.1 of oneM2M TS-0004 <a href="#_ref_4">[4]</a>. The short names in oneM2M TS-0004 shall apply in addition to the short names defined in the present document. @@ -2018,11 +1827,13 @@ In protocol bindings, resource attribute names shall be translated into short na **Table 9.2-1: Common and Field Device Configuration specific oneM2M Attribute Short Names**<a name="table_9.2-1"></a> -|**Attribute Name** |**Occurs in** |**Short Name** |**Notes** | +<mark>Editors note: some shortname are italcs, some are not</mark> + +|Attribute Name |Occurs in |Short Name |Notes | |-|-|-|-| |_resourceType_ |All |**_ty_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_resourceID_ |All |**_ri_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | -|_resource_ _Name_ |All |**_rn_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | +|_resourceName_ |All |**_rn_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_parentID_ |All |**_pi_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_expirationTime_ |All |**_et_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_creationTime_ |All |**_ct_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | @@ -2039,7 +1850,7 @@ In protocol bindings, resource attribute names shall be translated into short na |_pointOfAccess_ |registration |**_poa_** | | |_appID_ |registration |**_apid_** | | |_externalID_ |registration |**_eid_** | | -|_T_ _rigger_ _-_ _Recipient_ _-_ _ID_ |registration |**_tri_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | +|_Trigger-Recipient-ID_ |registration |**_tri_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_containerPath_ |dataCollection |**_cntp_** | | |_reportingSchedule_ |dataCollection |**_rpsc_** | | |_measurementSchedule_ |dataCollection |**_mesc_** | | @@ -2096,15 +1907,13 @@ In protocol bindings, resource attribute names shall be translated into short na |_coverageEnhancementLevel_ |mobileNetwork |**_coel_** | | - - ## 9.3 Field Device Configuration specific oneM2M Resource types -In protocol bindings, resource type names of the <mgmtObj> specializations shall be translated into the short names of table 9.3-1. +In protocol bindings, resource type names of the <mgmtObj> specializations shall be translated into the short names of table 9.3-1. **Table 9.3-1: Field Device Configuration specific Resource Type Short Names**<a name="table_9.3-1"></a> -|**ResourceType** **Name** |**Short Name** | +|ResourceType Name |Short Name | |-|-| |_registration_ |**_reg_** | |_registrationAnnc_ |**_regA_** | @@ -2116,53 +1925,44 @@ In protocol bindings, resource type names of the <mgmtObj> specializations sh |_myCertFileCred_ |**_nycfc_** | |_trustAnchorCred_ |**_tac_** | |_wifiClient_ |**_wfct_** | -|_OAuth2Authentication_ |**_o_** **_aan_** | +|_OAuth2Authentication_ |**_oaan_** | |_credentials_ |**_crds_** | |_SIM_ |**_sim_** | |_mobileNetwork_ |**_mnwk_** | - - ## 9.4 oneM2M Complex data type members + In protocol bindings, complex data types member names shall be translated into the short names of table 9.4-1. **Table 9.4-1: oneM2M Complex data type member short names**<a name="table_9.4-1"></a> -|**Member Name** |**Occurs in** |**Short Name** |**Notes** | +|Member Name |Occurs in |Short Name |Notes | |-|-|-|-| |_encryptionType_ |dcfg:wifiCredentials |**_enct_** | | -|_u_ _sername_ |dcfg:wifiCredentials |**_unm_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | +|_username_ |dcfg:wifiCredentials |**_unm_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_password_ |dcfg:wifiCredentials |**_pwd_** |Defined in oneM2M TS-0004 <a href="#_ref_4">[4]</a>. | |_wepKey_ |dcfg:wifiCredentials |**_wepk_** | | |_wpaPsk_ |dcfg:wifiCredentials |**_wpap_** | | - - # History -This clause shall be the last one in the document and list the main phases (all additional information will be removed at the publication stage). - - +This clause shall be the last one in the document and list the main phases (all additional information will be removed at the publication stage). - - -<mark>Table with colspans converted to grid table. Please check and adjust manually if necessary.</mark> - -+-------------------------------+---------------+---------------------------------------------------------------------------------+ -| **Publication** **history** | -+:==============================+:==============+:================================================================================+ -| V2.3.1 | 2018-Mar-12 | Release 2A - Publication | -+-------------------------------+---------------+---------------------------------------------------------------------------------+ -| V5.0.0 | 2024-Mar-19 | Following R5 CRs are incorporated from CR pack agreed in TP 64:\ | -| | | SDS-2021-0185R02-Adding\_[credentials]\_specialization\_to\_TS-0022\ | -| | | SDS-2023-0216R04-TS-0022\_-\_Adding\_SIM\_and\_mobileNetwork\_MgmtObjs\ | -| | | Note: this baseline is created from V 4.6.0 | -+-------------------------------+---------------+---------------------------------------------------------------------------------+ -| V5.1.0 | 2024-Dec-24 | ETSI editHelp V4.5.1 merged as per open action A-SDS-64-01.\ | -| | | Following CRs from SDS #66 are incorporated:\ | -| | | SDS-2024-0104-AuthenticationProfile\_M2MSubID\_dataTypeCorrection\_mirrorCR\_R5 | -+-------------------------------+---------------+---------------------------------------------------------------------------------+ ++-------------------------------+---------------+-------------------------------------------------------------------------------------------------------------+ +| Publication history | ++:==============================+:==============+:============================================================================================================+ +| V2.3.1 | 2018-Mar-12 | Release 2A - Publication | ++-------------------------------+---------------+-------------------------------------------------------------------------------------------------------------+ +| V5.0.0 | 2024-Mar-19 | Following R5 CRs are incorporated from CR pack agreed in TP 64:\ | +| | | SDS-2021-0185R02-Adding\_[credentials]\_specialization\_to\_TS-0022\ | +| | | SDS-2023-0216R04-TS-0022\_-\_Adding\_SIM\_and\_mobileNetwork\_MgmtObjs\ | +| | | Note: this baseline is created from V 4.6.0 | ++-------------------------------+---------------+-------------------------------------------------------------------------------------------------------------+ +| V5.1.0 | 2024-Dec-24 | ETSI editHelp V4.5.1 merged as per open action A-SDS-64-01.\ | +| | | Following CRs from SDS #66 are incorporated:\ | +| | | SDS-2024-0104-AuthenticationProfile\_M2MSubID\_dataTypeCorrection\_mirrorCR\_R5 | ++-------------------------------+---------------+-------------------------------------------------------------------------------------------------------------+ diff --git a/media/image2.png b/media/6_1_1.png similarity index 100% rename from media/image2.png rename to media/6_1_1.png diff --git a/media/image3.png b/media/8_1_2_1.png similarity index 100% rename from media/image3.png rename to media/8_1_2_1.png diff --git a/media/image3.svg b/media/8_1_2_1.svg similarity index 100% rename from media/image3.svg rename to media/8_1_2_1.svg diff --git a/media/image4.png b/media/8_1_3_2_1.png similarity index 100% rename from media/image4.png rename to media/8_1_3_2_1.png diff --git a/media/image4.svg b/media/8_1_3_2_1.svg similarity index 100% rename from media/image4.svg rename to media/8_1_3_2_1.svg diff --git a/media/image5.png b/media/8_1_3_3_1.png similarity index 100% rename from media/image5.png rename to media/8_1_3_3_1.png diff --git a/media/image5.svg b/media/8_1_3_3_1.svg similarity index 100% rename from media/image5.svg rename to media/8_1_3_3_1.svg diff --git a/media/image6.png b/media/8_1_3_4_1.png similarity index 100% rename from media/image6.png rename to media/8_1_3_4_1.png diff --git a/media/image6.svg b/media/8_1_3_4_1.svg similarity index 100% rename from media/image6.svg rename to media/8_1_3_4_1.svg diff --git a/media/image7.png b/media/8_2_1.png similarity index 100% rename from media/image7.png rename to media/8_2_1.png diff --git a/media/image7.svg b/media/8_2_1.svg similarity index 100% rename from media/image7.svg rename to media/8_2_1.svg diff --git a/media/image1.png b/media/image1.png deleted file mode 100644 index 97c1800c30f775e41f7ceeccb99e5678e51651cd..0000000000000000000000000000000000000000 Binary files a/media/image1.png and /dev/null differ diff --git a/media/image3.emf b/media/image3.emf deleted file mode 100644 index eff059ab25d657a9956ae9b5eb8058b7ecd48c8d..0000000000000000000000000000000000000000 Binary files a/media/image3.emf and /dev/null differ diff --git a/media/image4.emf b/media/image4.emf deleted file mode 100644 index 5e9aaf5d7ab6a1318ea3581c1bddc650398490fd..0000000000000000000000000000000000000000 Binary files a/media/image4.emf and /dev/null differ diff --git a/media/image5.emf b/media/image5.emf deleted file mode 100644 index e4e6eb2c5f69038d9713a22873dc5ad63a7a210b..0000000000000000000000000000000000000000 Binary files a/media/image5.emf and /dev/null differ diff --git a/media/image6.emf b/media/image6.emf deleted file mode 100644 index 86f04da6cd195fe6fa3beb6950ca46a0a070f17e..0000000000000000000000000000000000000000 Binary files a/media/image6.emf and /dev/null differ diff --git a/media/image7.emf b/media/image7.emf deleted file mode 100644 index 119286c432fffdd81cf124c2005b85cd0b58fc2b..0000000000000000000000000000000000000000 Binary files a/media/image7.emf and /dev/null differ