hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.2.1 General description | As explained in clause 5.1 it is the task of an IPE to interact via the Area Network with the Interworked Devices and to provide oneM2M resources (Proxied Devices) to the communicating entities for communication with the Interworked Devices. However these Proxied Devices still exhibit the native data model - the Device Information Model of the external technology of the device - and a communicating entity needs to know that native Device Information Model (e.g. ZigBee, KNX, information model). Device abstraction relieves a communicating entity that wants to communicate with an Interworked Device (e.g. a ZigBee device) from the need to know the native Device Information Model of that Interworked Device. Additionally to providing interworking, the IPE may translate between the - technology specific - native Device Information Model and an Abstract Information Model, that is based on of common functionalities abstracted from a set of Device Information Models. Such Abstract Information Models can be provided by industry associations of a specific industry sector. An example of an Abstract Information Model, which is specified in oneM2M is the Home Appliance Information Model (HAIM), specified in ETSI TS 118 123 [5]. As in the case of a native Device Information Model that is used by the IPE also an Abstract Information Model can be described by an ontology and that ontology needs to be derived from the Base Ontology. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.2.2 An example, involving ZigBee, HAIM and SAREF | Figure 2 illustrates this situation for a light switch. In the example the physical implementation is a ZigBee device implementing a ZigBee Service "On/Off Cluster". An IPE for ZigBee creates the interworking towards the ZigBee network. To enable abstraction, this device is abstracted as oneM2M device according to the Home Appliance Information Model (HAIM). In HAIM the corresponding Service is a "binary Switch". Both types of Services expose a Function "On Off Function" which is e.g. described in the SAREF ontology. To turn the switch on SAREF defines an "On Command". The corresponding Service in HAIM is executed by setting an Input Datapoint called "powerState" to the binary value "TRUE". In Zigbee an operation (ZigBee command) needs to be invoked in the On/Off Cluster with an input parameter (ZigBee Command ID) equal to 0. A VariableConversion can been specified in the ontology of the ZigBee Device Information Model that contains the rules how to convert a value of InputDataPoint "powerState" into a value of OperationInput "ZigBee Command ID". ETSI ETSI TS 118 130 V4.0.1 (2023-06) 11 oneM2M TS-0030 version 4.0.1 Release 4 Device type_DD hasService hasFunction Operation Input “ID = 0” exposes Function Function “On Off Function” Service “On/Off Cluster” Operation “ZigBee Command” hasOperation Command “On Command” hasCommand hasInput exposes Command Device type_DA hasFunction Service “binary Switch” Input DataPoint “powerState = TRUE” hasService exposes Function exposes Command hasInput DataPoint Variable Conversion hasConversion ontology of the Device Information Model (example ZigBee) ontology of the Abstract Information Model (example: HAIM) convertsTo Figure 2: Ontologies relations |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.3 Priciples of data flows | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 5.3.1 Preconditions on the communicating entity | Data flows between a communicating entity and the IPE involve oneM2M resources - specialized <flexContainer>s and possibly <AE>s - that were created by the IPE for the purpose of that communication. NOTE 1: In this clause and in the subsequent clauses it is assumed that the communicating entity and the IPE uses the oneM2M subscribe/notify mechanism to become informed about UPDATEd resources. It remains, however, an implementation option if subscribe/notify is used or other mechanisms (polling or other mechanisms, e.g. in case of IPE collocated/integrated in its hosting CSE) are used. 1) Any communicating entity, that: a) wants to discover interworked non-oneM2M devices of the non-oneM2M system via the IPE needs to be subscribed to the <AE> resource of the IPE to get notified about newly created resources for Proxied Devices. These resources are created by the IPE to represent interworked non-oneM2M devices that were discovered by the IPE: A communicating entity also needs to be subscribed to the <AE> resource of the IPE if it wants to use network services (e.g. broadcast services, registration services, etc.) that are offered by the IPE. NOTE 2: Since the IPE, in addition to being a oneM2M AE, is part of the non-oneM2M system it contains a non- oneM2M device that can offer network services. b) wants to communicate with a specific interworked non-oneM2M device via the IPE needs to be subscribed to the <flexContainer> (or <AE>) resource that had been created by the IPE to represent that interworked non-oneM2M device as Proxied Device. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 12 oneM2M TS-0030 version 4.0.1 Release 4 c) wants to communicate with a sub-device of a Proxied Device, represented by a <flexContainer> that is a child-resource of the Device's <flexContainer> (or <AE>) resource the communicating entity needs also to be subscribed to that <flexContainer> child-resource. 2) The communicating entity needs also be subscribed to: a) The <flexContainer> resources, representing Services, that have been created by the IPE as child resourses of the resource of the Proxied Device. The attribute notificationContentType of the <subscription> needs to be set to "modified-attributes". b) The <flexContainer> resources for the Operation invocation. These resources are child-resources of their respective Service <flexContainer> resources. The eventNotificationCriteria conditions the notificationEventType needs to contain: - (B) Deletion of the subscribed-to resource … to get notified when theoperation becomes unavailable and, if the operation involves an answer (operation results). also - (C) Creation of a direct child of the subscribed-to resource … to get notified about the creation of a <flexContainer> for the Operation result. c) The <flexContainer> for the Operation result. The attribute notificationContentType of the <subscription> needs to be set to "all-attributes". 5.3.2 Data flows for communicating with the IPE using DataPoints of a Service Figure 3 show the data flows for communicating with the IPE using DataPoints of a Service. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 13 oneM2M TS-0030 version 4.0.1 Release 4 UPDATE OutputDataPoint customAttribute of Service <flexContainer> UPDATE InputDataPoint customAttribute of Service <flexContainer> IPE Communicating entity Interworked Device translate input CSE NOTIFY with changed value of InputDataPoint Communication initiated by Communicating entity Communication initiated by Interworked Device translate output Invoke Command Invoke Command NOTIFY with changed value of OutputDataPoint Figure 3: Data flow for an IPE involving dataPoints When a communicating entity wants to invoke a command on the Interworked Device (e.g. an actuation command), using Datapoints of the related Service: • The communicating entity UPDATEs the corresponding <flexContainer> that represents the service with the new value for customAttribute of the InputDatapoint. • The CSE subsequently NOTIFY the IPE about the changed value for customAttribute of the InputDatapoint. • The IPE invokes the command at the Interworked Device that sends the data of the InputDatapoint to the Interworked Device. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 14 oneM2M TS-0030 version 4.0.1 Release 4 When the Interworked Device wants to invoke a command (e.g. a reporting) on the IPE - or a subscribed communicating entity, using Datapoints of the related Service: • The Interworked Device invokes the command at the IPE that sends the data of the OutputDatapoint to the IPE. • The IPE UPDATEs the corresponding <flexContainer> that represents the Service with the new value for customAttribute of that OutputDatapoint. • The CSE subsequently NOTIFY subscribed communicating entities about the changed value for customAttribute of the OutputDatapoint. 5.3.3 Data flows for communicating with the IPE using Operations of a Service Figure 4 show the data flows for communicating with the IPE using an Operation of a Service. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 15 oneM2M TS-0030 version 4.0.1 Release 4 UPDATE Operation result <flexContainer> with original OperationInput and potentially with OperationOutput Command response Invoke Command UPDATE Operation invocation <flexContainer> potentially with OperationInput IPE Communicating entity Interworked Device translate input Waiting for answer for configurable maximum time translate output CSE If operation involves an answer NOTIFY Communication initiated by Communicating entity NOTIFY Figure 4: Data flow for a translating entity involving operations when initiated by a communicating entity In contrast to DataPoints Operations allow grouping of input- and output parameters of a Command into a single transaction between the communicating entity and the target entity. It is permissible that no OperationInput and/or OperationOutput data exist for an Operation: • When the communicating entity invokes an operation in the target entity it UPDATEs the <flexContainer> resource for the Operation invocation, potentially with OperationInput values for the related customAttributes. If the operation involves no OperationInput the UPDATE request contains no customAttributes. • The CSE subsequently NOTIFY the IPE about the updated <flexContainer> resource for the Operation invocation, potetially with OperationInput values for the related customAttributes. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 16 oneM2M TS-0030 version 4.0.1 Release 4 • The IPE invokes the command at the Interworked Device. If the Operation involves an (optional or mandatory) answer from the Interworked Device then: • The Interworked Device returns the answer on the command, containing output data, to the IPE. The IPE needs to wait for that answer for a configurable maximum time that may depend on the technology of the interworked non-oneM2M solution. • The IPE UPDATEs the corresponding <flexContainer> that represents the Operation result with OperationOutput values for the related customAttributes. • The CSE subsequently NOTIFY the communicating entity about the update of the <flexContainer> that represents the Operation result. 6 Functional specification of communication with the Ontology based Interworking IPE |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.1 oneM2M resources for IPE communication | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.1.1 General design principles | For Ontology based Interworking the oneM2M resource types <AE> and specializations of <flexContainer> are intended to hold data that can be used for data exchange with the IPE. For Ontology based Interworking a convention is needed how the IPE uses these resources to communicate with other oneM2M entities. This is described in the subsequent clauses. Resources for RESTful communication style vs. procedure call (RPC) style. A Ontology based Interworking IPE needs to be able to communicate with systems that implement some form of RESTful communication style as well as other systems that communicate in a procedure call (RPC) style. For RESTful systems the use of Input- or OutputDataPoints may be more appropriate. On the other hand procedure calls that involve stateful transactions between the IPE and the Interworked Device can be better modelled using Operations (and their OperationInputs/-Outputs). 6.1.2 Resource structure for modelling devices, sub-devices, services and operations Figure 5 and Figure 6 provide an overview of parent-child resource relationships that are used for communication with Interworked Devices in the context of Ontology based Interworking. It involves the oneM2M resource types: • <AE> - for the Interworking Proxy Entity (IPE). • A <container> child resource of the <AE> of the IPE - for holding XSD files (for the specializations of <flexContainers> used in the interworking. Interworked Devices are represented either by: • <flexContainer> - child- resource of <AE> of IPE; or • <AE> - child resources of the hosting CSE of the IPE. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 17 oneM2M TS-0030 version 4.0.1 Release 4 NOTE: An IPE may, instead of creating <flexContainer>resources for Interworked Devices, also choose to represent them as <AE>s. This option should be chosen if the interworked devices need to be identifiable for the purpose of service subscription, charging, differentiation during access control enforcement, authentication, App-ID registry, etc. • <flexContainer> - for a sub-device (child-resource of the <flexContainer> or <AE> of its parent device). • <node> for the node of a Device or sub-device. • <flexContainer> - for a Service of a Device or sub-device. (child-resource of the <flexContainer> or <AE> of the device that offers the Service). • <flexContainer> for network services (e.g. broadcast services, registration services …) that are offered by the IPE are child-resources of the IPE's <AE>. • <flexContainer> - for an Operation (invocation) of a Service. (child-resource of the <flexContainer> of the Service). • <flexContainer> - for an Operation (result) of a Service. (child-resource of the <flexContainer> of the Operation invocation of the Service). Resources for Generic Interworking (devices represented as <flexContainer>s ) Not shown: <semanticDescriptor>, <subscription> <flexContainer> <flexContainer> OutputDataPoint OperationOutput OperationInput CSEBase OutputDataPoint Service OperationInput Operation (invocation) OperationInput <flexContainer> <AE> IPE <container> <contentInstance> <contentInstance> <contentInstance> nodeLink XSDs of classes XSD storage <flexContainer> Sub-device Operation (result) OperationInput OperationOutput InputDataPoint InputDataPoint <node> node of sub-device nodeLink <flexContainer> <flexContainer> <flexContainer> Device node of device <node> node of IPE <node> nodeLink <flexCont> <flexContainer> <flexContainer> Service (network services) <flexCont> <flexContainer> <flexContainer> <flexCont> <flexContainer> <flexContainer> Figure 5: Resources used in the context of Ontology based Interworking when Interworked Devices are represented as <flexContainer>s ETSI ETSI TS 118 130 V4.0.1 (2023-06) 18 oneM2M TS-0030 version 4.0.1 Release 4 Parent-child relationships when Interworked Devices are represented as <flexContainer>s: • A <container> resource, for holding XSD files, is created as child-resource of the <AE> resource of the IPE. • <flexContainer> resources, for representing (network) Services are created as child-resources of the <AE> of the IPE. • <flexContainer> resources for representing Interworked Devices are created by the Ontology based Interworking IPE as child-resources of the IPE's <AE>. • <flexContainer> resources, for representing sub-devices are created as child-resources of the <flexContainer> resource that represents the device to which the sub-devices belong. • <flexContainer> resources, for representing Services are created as child-resources of the <flexContainer> resource that represents the device or sub-device to which the Service belongs. Input- or OutputDataPoints are modelled as customAttributes. • <flexContainer> resources, for representing Operations invocations are created as child-resources of the <flexContainer> resource that represents the Service to which the Operation belongs. Only OperationInputs are modelled as customAttributes. • <flexContainer> resources, for representing Operations results are created as child-resources of the <flexContainer> resource that represents the Operations invocation to which the Operation result belongs. Both, OperationInputs and -Outputs are modelled as customAttributes. • All of the above can contain a <semanticDescriptor> as child resource and may contain <subscription> resources. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 19 oneM2M TS-0030 version 4.0.1 Release 4 <flexContainer> <flexContainer> <AE> <AE> OutputDataPoint OperationOutput OperationInput CSEBase <AE> OutputDataPoint Service OperationInput Operation (invocation) OperationInput <flexContainer> Device (customAttributes) <AE> IPE <node> <container> <contentInstance> <contentInstance> <contentInstance> nodeLink XSDs of classes XSD storage <flexContainer> Sub-device Operation (result) OperationInput OperationOutput InputDataPoint InputDataPoint node of device Resources for Generic Interworking (devices represented as <AE>s ) Not shown: <semanticDescriptor>, <subscription> <node> node of sub-device nodeLink Service (network services) <flexCont> <flexContainer> <flexContainer> <flexCont> <flexContainer> <flexContainer> <flexCont> <flexContainer> <flexContainer> Figure 6: Resources used in the context of Ontology based Interworking when Interworked Devices are represented as <AE>s Parent-child relationships when Interworked Devices are represented as <AE>s: • A <container> resource, for holding XSD files, is created as child-resource of the <AE> resource of the IPE. • <flexContainer> resources, for representing (network) Services are created as child-resources of the <AE> of the IPE. • An <AE> resource, representing each Interworked Device is created by the IPE as child-resources of the IPE's hosting CSE. • <flexContainer> resources, for representing sub-devices are created as child-resources of the <AE> resource that represents the device to which the sub-devices belong. • <flexContainer> resources, for representing Services are created as child-resources of the <AE> that represents the device (or <flexContainer> that represents the sub-device) to which the Service belongs. Input- or OutputDataPoints are modelled as customAttributes. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 20 oneM2M TS-0030 version 4.0.1 Release 4 • <flexContainer> resources, for representing Operation invocations are created as child-resources of the <flexContainer> resource that represents the Service to which the Operation belongs. Only OperationInputs are modelled as customAttributes. • <flexContainer> resources, for representing Operation results are created as child-resources of the <flexContainer> resource that represents the Operations invocation to which the Operation result belongs. Both, OperationInputs and -Outputs are modelled as customAttributes. • All of the above can contain a <semanticDescriptor> as child resource and may contain <subscription> resources. Link relationships: • The <AE>s and <flexContainer> resources, representing Interworked Devices / fs may have nodeLink attributes to their respective <node> resources. NOTE: If Interworked Devices / sub-devices are resident on the same node their nodeLink attributes reference the same <node> resource. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2 Specification of the IPE for Ontology based Interworking | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1 Initialization of the Ontology based Interworking IPE | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1.1 General functionality of a Ontology based Interworking IPE | Ontology based Interworking Interworking supports the interworking variant with full mapping of the semantic of the non-oneM2M data model to Mca as indicated in clause F.2 of ETSI TS 118 101 [2]. The non-oneM2M data model is described in the form of a oneM2M compliant ontology which is derived (as sub-classes and sub-properties) from the oneM2M Base Ontology and may be available in a formal description language (e.g. OWL). A oneM2M compliant ontology can describe an external technology (e.g. ZigBee) for which a standardized interworking with oneM2M is required or it could describe a model of consensus that is shared by large industry sector (like SAREF, referenced in [i.2]) that facilitates the matching of existing assets (standards/protocols/datamodels, etc.). An IPE that provides Ontology based Interworking with a non-oneM2M system (e.g. an M2M Area Network) shall instantiate the classes, object- and data properties of the ontology describing the non-oneM2M data model of the M2MArea Network as oneM2M resources, according to the instantiation described below. In the following clauses it is assumed that the oneM2M compliant ontology describing the non-oneM2M data model is available as a formal description (e.g. in OWL format). The location (URI) where the formal description of the ontology can be retrieved by the IPE needs to be configured in the IPE - either preconfigured or through administrative means. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.1.2 Initialization sequence of a Ontology based Interworking IPE | After registration of the IPE's <AE> resource the IPE shall do the following: 1) The IPE shall retrieve the formal description of the ontology and parse it. 2) The IPE shall create a child-resource of its <AE> resource of type <container>, subsequently called 'XSD- storage' This <container>is will hold the XSDs that are needed to specialize the <flexContainer>s that are used in the oneM2M resource representation of entities of the non-oneM2M interworked solution: - The resource name of the <container> resource shall be identical to the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - The attribute ontologyRef of that <container>shall contain the reference (URI) to the used ontology. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 21 oneM2M TS-0030 version 4.0.1 Release 4 3) For each class of the ontology the IPE shall create a resource of type <contentInstance> as child resource of this <container>. That <contentInstance> shall hold the XSD for instantiating the class as <flexContainer> specialization in oneM2M. How the IPE create XSDs from an ontology is described in clause 7 of the present document. - The resource name of each <contentInstance> resource shall be identical to the class name of the ontology, followed by ".xsd". - The attribute ontologyRef of that < contentInstance >shall contain the reference (URI) to the class of the ontology. EXAMPLE: For ontology 'http://www.someOrganization.org/someOntology' the IPE would create a <container> resource with resource name "www.someOrganization.org_someOntology". Its ontologyRef would contain the URI: 'http://www.someOrganization.org/someOntology'. If the ontology defines a class 'http://www.someOrganization.org/someOntology#someService' then the IPE needs to create a <contentInstance> as child rsource of that that "www.someOrganization.org_someOntology" <container>. The resource name of that <contentInstance> would be "someService.xsd". Its ontologyRef would contain the URI: 'http://www.someOrganization.org/someOntology#someService'. 4) If supported by the technology of the non-oneM2M solution the IPE shall create <flexContainer>s according to clause 6.2.2.4 for its own (network) services (e.g. broadcast services, etc.) that are provided by the IPE. 5) If supported by the technology of the non-oneM2M solution the IPE shall discover the devices in the non-oneM2M solution, including their supported services. Alternatively, information about the devices in the the non-oneM2M solution may be manually configured in the IPE or obtained by other means. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2 Interworked Device and Service discovery | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.1 General handling of Interworked Device discovery | If supported by the technology of the non-oneM2M solution the IPE shall continue to discover the devices in the non- oneM2M solution. If supported by the technology of the non-oneM2M solution the IPE shall continue to discover services that are provided by the devices in the non-oneM2M solution. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.2 Creation of resources for the Proxied Device | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.2.1 General on the creation of resources for the Proxied Device by the IPE | For each discovered Interworked Device in the non-oneM2M solution the IPE shall: either: - create a <flexContainer>child-resource of the IPE's own <AE> to represent the non-oneM2M Interworked Device in the oneM2M System: this option should be chosen in most cases, in particular when the individual representations for Interworked Devices - the Proxied Devices - do not need to be distinguished with regard to service subscription, charging, etc. as these are derived from the IPE'S <AE>. or - register an <AE> resource with the IPE's hosting CSE. That <AE> resource represents the non-oneM2M Interworked Device in the oneM2M System: this option should be chosen if the interworked devices need to be identifiable for the purpose of service subscription, charging, differentiation during access control enforcement, authentication, App-ID registry, etc. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 22 oneM2M TS-0030 version 4.0.1 Release 4 NOTE: The resource (<flexContainer> or <AE>) that represents the non-oneM2M Interworked Device in the oneM2M System, together with its child resources, and together with the IPE functionality to execute CRUDN operations on these resources is called 'Proxied Device' (see terms in clause 3.1). 6.2.2.2.2 Creation of resources for the Proxied Device when Interworked Devices are represented as <flexContainer>s If the IPE creates <flexContainer>s for Proxied Devices the following rules apply. For each discovered device in the non-oneM2M solution the IPE shall create a specialized <flexContainer> resource as child-resource of the <AE> resource of the IPE: • The specialization type of the <flexContainer> is determined by the XSD file - a <contentInstance>in the XSD-storage - that correlates to the class of the sub-device in the ontology. • It is recommended that the resourceName of an <flexContainer> resource that represents an Interworked Device should be derived and resemble the address (e.g. MAC address) of the Interworked Device in the non- oneM2M solution. As the formats of such addresses are very diverse no general rule for that derivation can be given. • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the Interworked Device. • The labels attribute of the <flexContainer> may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class in the ontology (i.e. a sub-class of class InterworkedDevice of the oneM2M Base OntologyBase Ontology) that specifies the type of the Interworked Device. • The resourceID of a <node> resource that stores the node specific information where this Interworked Device resides may be contained in the nodeLink attribute of the <flexContainer> of the Device. NOTE: Such a <node> resource is required if the device management tasks can be performed via the oneM2M solution. • The IPE may create a <semanticDescriptor> child-resource for the <flexContainer> resource that represents an Interworked Device (see clause 7 in ETSI TS 118 112 [3]). 6.2.2.2.3 Creation of resources for the Proxied Device when Interworked Devices are represented as <AE>s If the IPE registers individual <AE>s for Proxied Devices the following rules apply: • As the IPE registers the <AE> as a proxy for the Interworked Device it should either: - not create a Security Association Establishment procedure; or - create a Security Association Establishment procedure between the Node on which the IPE <AE> is hosted and the Registrar CSE. In this case only the Node from which the registration request is received at the Registrar CSE is authenticated. Thus the IPE, which handles communication for all the Proxied Devices, can communicate over either a single Security Association or over individual Security Associations for each Proxied Device. NOTE 1: The Node authentication as described above (see also ETSI TS 118 101 [2], clause 10.2.2.2) is applicable as the IPE performs AE functionality for all its Proxied Devices, as if their (virtual) individual AEs were resident on the same node as the IPE AE. • The APP-ID of the <AE> shall be the APP-ID of the IPE. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 23 oneM2M TS-0030 version 4.0.1 Release 4 • It is recommended that the AE-ID of an <AE> resource that represents an Interworked Device should be derived and resemble an identifier of the Interworked Device in the non-oneM2M solution. As the formats of such identifiers are very diverse no general rule for that derivation can be given. • It is recommended that the resourceName of an <AE> resource that represents an Interworked Device should be derived and resemble the address of the Interworked Device in the non-oneM2M solution. As the formats of such addresses are very diverse no general rule for that derivation can be given. • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the Interworked Device. • The labels attribute of may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class in the ontology (i.e. a sub-class of class InterworkedDevice of the oneM2M Base OntologyBase Ontology) that specifies the type of the Interworked Device. • The resourceID of a <node> resource that stores the node specific information where this Device resides may be contained in the nodeLink attribute of the <AE> of the Device. NOTE 2: Such a <node> resource is required if the device management tasks can be performed via the oneM2M solution. • The IPE may create a <semanticDescriptor>child-resource for the <AE> (see clause 7 in ETSI TS 118 112 [3]). |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.3 Creation of resources for sub-devices | A Device can consist of (i.e. be composed) of several (sub-) Devices. In the oneM2M Base OntologyBase Ontology the Object Property: consistsOf links a device class to a class of its sub-devices. For each sub-device of a discovered device in the non-oneM2M solution the IPE shall create a specialized <flexContainer> resource as child-resource of the <AE> or <flexContainer> resource of the Proxied Device/: • The specialization type of the <flexContainer> is determined by the XSD file - a <contentInstance>in the XSD-storage - that correlates to the class of the sub-device in the ontology. • The resourceName of the <flexContainer> resource of the sub-device shall be identical to the class name of the (ontology specific sub-class of) class:Device of the sub-device in the ontology. Example: "switchingSubDevice": - If multiple sub-device instances of the same class exist then the resourceName shall be appended by '_' (underline) and followed by a number to distinguish individual <flexContainer> resources for multiple (sub-)devices of the same type. Example: "subDeviceCuff _02" when the device is a blood pressure monitor containing 4 individual cuffs for measuring blood pressure as sub-devices. NOTE: The creation of <flexContainer> resources for sub-devices of a device is basically analogous to the creation of <flexContainer> resources for Services of a device (see next clause). • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the sub-device. • The labels attribute of may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class of the sub-device in the ontology (i.e. a sub- class of class:InterworkedDevice of the oneM2M Base OntologyBase Ontology). • The IPE may create a <semanticDescriptor>child-resource. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 24 oneM2M TS-0030 version 4.0.1 Release 4 |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.4 Creation of resources for Services | For each service, that is supported by a device or sub-device the IPE shall create a specialized <flexContainer> resource, representing the service. The <flexContainer> shall be a child-resource of the Proxied Device representation (<AE> or <flexContainer> resource in case of an interworked Device, specialized <flexContainer> in case of a sub-device): • The services that can be supported by a device or sub-device are specified in the ontology by Object Property: hasService: - If a service is mandatory for a specific device then Object Property:hasService (or a sub-property) of the ontology has a Restriction on cardinality: "exactly 1". In this case the IPE shall create the specialized <flexContainer> for the Service. - If a service is optional for a specific device and can have only one instance on the device then Object Property:hasService (or a sub-property) has a restriction on cardinality: "max 1". In this case the IPE shall create the specialized <flexContainer> for the Service only if the the IPE can determine (using methods of the interworked solution) that the (sub)device actually supports the service. - A service can have multiple instances on a device. In this case Object Property:hasService (or a sub-property) has no restriction on cardinality or a restriction: e.g. "min [x]"with x>1: The ontology may specify that the same service of a device exposes multiple, different Functions (Object Property:exposesFunction). In this case multiple instances of the same service might be distinguishable by the Function they expose. If the ontology does not specify the Function that is exposed by the Service or if multiple Services with the same Function exist in the device then these are semantically indistinguishable Example: a connector strip containing 5 individual switching services. In this case the IPE may create multiple specialized <flexContainer> instances for the Service. • The specialization type of the <flexContainer> is determined by the XSD file - a <contentInstance> in the XSD-storage - that correlates with the class of the service in the ontology. NOTE: The XSD file for the service also includes XSD descriptions for the service's DataPoints - which are represented as customAttributes of the<flexContainer>for the Service. • The resourceName of the <flexContainer> resource of the service shall be identical to the class name of the (ontology specific sub-class of) class:Service in the ontology. Example: "liquidRemaining": - If multiple service instances of the same class:Service exist but expose different Functions (via Object Property:exposesFunction) then the resourceName shall be appended by '_' (underline), followed by the class name of the function in the ontology. Example: "liquidRemaining_ waterStatus", "liquidRemaining_ milkStatus". - If multiple service instances of the same class:Service exist that expose the same function then the resourceName shall be appended by '_' (underline), followed by a number to distinguish individual <flexContainer> resources for multiple services of the same type. Example: "liquidRemaining_ waterStatus_01", "liquidRemaining_ waterStatus_02". • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the service. • The labels attribute of may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class of the service in the ontology (i.e. a sub-class of class:Service of the oneM2M Base Ontology). • The IPE may set access rights for the <flexContainer> resource of the service to restrict/allow AEs to use (UTDATE and / or RETRIEVE and SUBSCRIBE to) the the <flexContainer> that represents the Service. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 25 oneM2M TS-0030 version 4.0.1 Release 4 • The IPE may create a <semanticDescriptor>child-resource of the <flexContainer> resource of the service. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5 Creation of resources for operations of a service of a device | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.1 Introduction | An Operation is the means of a Service to communicate in a procedure-type manner. In general an operation is invoked by the communicating entity and can - but need not - have OperationInput parameters. As a result of the Operation result parameters can - but need not - be returned. An operation can also be invoked by the Interworked Device and can - but need not - have OperationOutput parameters. In this case no operation results are envisaged. NOTE: Analogous to operation invocation by the communicating entity at the Interworked Device also operation invocation by the Interworked Device at another device (oneM2M native or interworked) can happen. This case is not supported in the current release. Operations are represented in the oneM2M systems with one or two types of resources, both of them being specialized <flexContainer> resources: • The first type exists for every operation and is used to invoke the operation: - In the case the operation is invoked by the communicating entity it only contains OperationInput parameters, if they exist for this type of operation. - In the case the operation is invoked by the Interworked Device it only contains OperationOutput parameters, if they exist for this type of operation. • The second type is a child-resource of the first type and only exists if the operation had been invoked by the communicating entity and only for operations that can produce OperationOutput parameters. This type contains both, the OperationInput parameters, if they exist, and the OperationOutput parameters, if they exist. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.2 Creation of resources for operation invocation | For each operation, that is supported by a service of a device the IPE shall create a specialized <flexContainer> resource, representing the operation. The <flexContainer> shall be a child-resource of the specialized <flexContainer> of the service. The IPE shall subscribe to all specialized <flexContainer> resources representing operations, that it creates: • The operations that can be supported by a service are specified in the ontology by Object Property:hasOperation: - An Operation for a specific Service can only have at most a single instance at a time. Unless the operation is optional, i.e. Object Property:hasOperation (or a sub-property) has a restriction on cardinality: "max 1" the IPE shall create the specialized <flexContainer> that represents the Operation. NOTE 1: It is quite well possible, that the Interworked Device supports execution of multiple operation instances of the same operation type at a time. However, mutiple invocations of the same operation type is achieved in oneM2M by consecutively UPDATEing a single specialized <flexContainer> resource that represents the Operation input. Thus a single <flexContainer> resource is sufficient to invoke multiple, concurrent operation instances of that operation in the Interworked Device. Similarly, also returning OperationOutput parameters is done through a single UPDATE operation on the specialized <flexContainer> resource that represents the Operation output. - If an operation is optional for a specific service then Object Property:hasOperation (or a sub-property) has a restriction on cardinality: "max 1". In this case the IPE shall create the specialized <flexContainer> for the Operation only if the the IPE can determine (using methods of the interworked solution) that the Service actually supports the operation. • The specialization type of the <flexContainer> is determined by the XSD file - a <contentInstance> in the XSD-storage - that correlates with the class of the operation in the ontology. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 26 oneM2M TS-0030 version 4.0.1 Release 4 NOTE 2: The XSD file for the operation also includes XSD descriptions for the operation's OperationInput parameters which are represented as customAttributes of the<flexContainer>for the operation. When the IPE creates the <flexContainer> resource it may ignore customAttributes that represent the operation's OperationOutput parameters. • The resourceName of the <flexContainer> resource of the operation shall be identical to the class name of the (ontology specific sub-class of) class:Operation in the ontology. Example: "toggle" as an operation of a service of a light switch, "upVolume" as an operation of a service of a audio device. • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the operation. • The labels attribute of may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class of the operation in the ontology (i.e. a sub-class of class:Operation of the oneM2M Base Ontology). • The IPE may set access rights for the <flexContainer> resource of the service to restrict/allow AEs to use (UTDATE and / or RETRIEVE and SUBSCRIBE to) the the <flexContainer> that represents the Operation. • The IPE may create a <semanticDescriptor>child-resource of the <flexContainer> resource of the Operation. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.5.3 Creation of resources for returning operation results | For each operation, that can produce operation result parameters (i.e. its class:Operation is related via Object Property: hasOutput to some class:OperationOutput) the IPE shall create a specialized <flexContainer> resource, representing the result of the operation for a set of invocation parametes. The <flexContainer> shall be a child-resource of the specialized <flexContainer> resource for operation invocation (described in clause 6.2.2.2.2). The IPE shall subscribe to this specialized <flexContainer> resource: • The specialization type of the <flexContainer> is determined by the XSD file - a <contentInstance> in the XSD-storage - that correlates with the class of the operation in the ontology. NOTE: The XSD file for the operation also includes XSD descriptions for the operation's OperationInput and OperationOutput parameters which are represented as customAttributes of the<flexContainer>. • The resourceName of the <flexContainer> resource of the operation shall be identical to the class name of the (ontology specific sub-class of) class:Operation in the ontology, appended by '_result'. Example: "upVolume_result" as the result of an operation that e.g. returns the current volume level as OperationOutput parameter. • The attribute ontologyRef shall contain the reference (URI) to the class of the ontology that specifies the type of the operation. • The labels attribute of may contain the following key- vale pairs: - Key: "Iwked-Technology" Value: the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). - Key: "Iwked-Entity-Type" Value: Class name of the class of the operation in the ontology (i.e. a sub-class of class:Operation of the oneM2M Base Ontology). • The IPE may set access rights for RETRIEVEing the <flexContainer> resource of the operation. • The IPE may create a <semanticDescriptor>child-resource of the <flexContainer> resource of the operation. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 27 oneM2M TS-0030 version 4.0.1 Release 4 |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.2.6 Subscription to the created resources | The IPE shall subscribe to all specialized <flexContainer> resources representing services, that it creates. In particular it shall subscribe to the <flexContainer> resources representing Services and <flexContainer> resources for the Operation invocation. The attribute notificationContentType of the <subscription> needs to be set to "modified- attributes". |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.3 Handling of DataPoints by the IPE | • When the IPE receives a request by the interworked non-oneM2M device via the non-oneM2M reference point to write an OutputDataPoint belonging to a Service of the device the IPE shall: - de-serialize the received data; and - UPDATE the OutputDataPoint customAttribute of the <flexContainer> resource of the Service with the output data. • When the IPE receives a request by the interworked non-oneM2M device via the non-oneM2M reference point to read an InputDataPoint belonging to a Service of the device the IPE shall: - RETRIEVE data from the InputDataPoint customAttribute of the <flexContainer> resource of the Service; - serialize the data; and - return them to the non-oneM2M device. • When the IPE is notified by the CSE that a customAttribute of the <flexContainer> resource of the Service of the Proxied Device has been changed the IPE shall: - read the data of the changed customAttribute; and - invoke the Service, parameterized with data of the InputDataPoint, via the non-oneM2M reference point in the interworked non-oneM2M device. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.4 Handling of Operations by the IPE | When the IPE receives notification from the CSE about an UPDATE of the <flexContainer> resource of the operation the IPE shall perform the following actions: 1) If the operation has OperationInput data the IPE shall RETRIEVE the OperationInput data of the operation (contained in the customAttributes of the <flexContainer> resource of the operation). 2) The IPE shall serialize OperationInput data and invoke the related operation in the non-oneM2M device via the non-oneM2M reference point. 3) If the operation allows OperationOutput data (i.e. a <flexContainer> resource for returning operation results exists as a child-resource of the operation <flexContainer>) the IPE shall handle the result of the operation, when received from the Interworked Device via the non-oneM2M reference point: - The IPE shall de-serialize OperationOutput data. - The IPE shall UPDATE the <flexContainer> resource for returning operation results. The UPDATE primitive shall contain: the customAttributes with the values for the OperationInput data with which the operation had been invoked; and the customAttributes with the values for the OperationOutput data that had been received as result of the operation. NOTE: The IPE needs to await the operation results by the Interworked Device for an operation transaction only for a configurable timespan that may depend on the technology of the non-oneM2M solution. The duration of that timespan is out of scope of the present document. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 28 oneM2M TS-0030 version 4.0.1 Release 4 When the the non-oneM2M device invokes an operation in the IPE - which may or may not contain OperationInput data - via the non-oneM2M reference point (e.g. when the device reacts on some external event and publishes related output data): 1) The IPE shall de-serialize these data and perform the following actions: - If the operation invocation contained no OperationInput data the IPE shall UPDATE the <flexContainer> resource for the operation with NULL values for all customAttributes. - If the operation invocation contained OperationOutput data then: The IPE shall de-serialize OperationOutput data. The IPE shall UPDATE the OperationOutput customAttributes of the <flexContainer> resource for the operation with the values received. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 6.2.5 Removing of resources for Proxied Devices | • When a Interworked Device in the non-oneM2M solution becomes unavailable the IPE shall delete the resource for its Proxied Device and all its child-resources. • When the IPE detects that an Interworked Device stopped to support a Service (in case such detection is supported by the technology of the non-oneM2M solution) then the IPE shall delete the <flexContainer> resource for the service and all its child-resources. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7 Rules for creation of XSDs from ontologies | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.1 General information | When the non-oneM2M data model is described in the form of a oneM2M compliant ontology which is derived (as sub- classes and sub-properties) from the oneM2M Base Ontology and is available in a formal description language (e.g. OWL) then the IPE can create XSDs for the resources needed by communicating entities to communicate with the IPE. These resources are specializations of <flexContainer>s for Devices, Services and Operations. For these specializations of <flexContainer>s the IPE also needs to create XSD definitionss for customAttributes of the <flexContainer>. NOTE: The alternative of using <AE> resources for Devices is not used for Ontology based Interworking as specified in the present document. <AE> resource types are described in ETSI TS 118 101 [2] and ETSI TS 118 104 [8]. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2 XSD creation rules | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1 General rules | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.1 General principle for creating XSDs | During initialization (clause 6.2.1) a Ontology based Interworking IPE creates XSD files for device types, service types and operation types, according to the class definitions (sub-classes of class:Device, class:Service, class:Operation) in the ontology. Each XSD file contains the definition of a single specialization of a <flexContainer> resource type together with the type definitions that are used for customattributes of that specialization. All of these XSD files are stored as <contentInstance> child- resources of a <container> resource that acts as a XSD-storage and that is a child resource of the IPE's <AE>. The content of these XSD files is entirely based on the information contained in the oneM2M compliant ontology that describes the data model of the interworked technology and which is derived from the oneM2M Base Ontology. A Ontology based Interworking IPE can create these XSD files automatically. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 29 oneM2M TS-0030 version 4.0.1 Release 4 In clauses 7.2.2, 7.2.3 and 7.2.4 templates for specialization of <flexContainer> resources for Device, Service and Operation are given. These templates need to be filled in with parameters. The parameters and how they relate to classes, object properties and data properties of the ontology are given in the next clause 7.2.1.2. The attribute: containerDefinition of these XSDs shall have a value identical to the absolute, hierarchical address of the <contentinstance> containing the <flexContainer> specialization (see table 1 below). EXAMPLE: //m2m.service.com/IN-CSE-0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines /testService.xsd. NOTE: The present specification does not specify short names for primitive parameters, resource attributes, resource types and complex data types members. Such short names can be created on a proprietary basis for individual implementations but for interoperability reasons they are not recommended. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.2 Parameters for XSD templates | In the subsequent clauses the following conventions for parameters to fill in XSD templates is used. The column "replacement rules" explains how the parameter is derived from the ontology. NOTE: This convention follows roughly conventions of ENTITY declarations for DTD. Each ENTITY that is to be replaced in the XSD starts with "&" and ends with";". Table 1: Conventions for creation of XSDs from ontologies Convention Is short for Replacement rule &IPE; resource ID of the <AE> resource of the IPE Out of scope of the present document. &XSDSTORAGE; resource name of the <container> resource of the 'XSD-storage'. also identifies the XML targetnamespace: targetNamespace="&XSDSTORAGE;" Shall be identical to the name of the ontology, omitting "http://" and changing each "/" (slash) into "_" (underscore). Base OntologyThe 'XSD-storage' <container> is a child-resource of the <AE> resource of the IPE and has <contentinstance> child resources that contain XSDs for the individual <flexContainer> specializations. Example for &XSDSTORAGE;: ww.XYZ.com_WashingMachines &XSDFILE; resource name of a <contentInstance> child-resource of the 'XSD-storage'that contains a XSD for a <flexContainer> specialization Shall be the concatenation of • &DEVICE; or 1) &SERVICE; or • &OPERATION; and • ".xsd" EXAMPLE: "testService.xsd". &CONTAINERDEFINITIONVALUE; The value of attribute containerDefinition of the specialization of the <flexContainer> Shall be identical to the absolute, hierarchical address of the <contentinstance> containing the <flexContainer> specialization. It is the concatenation of: [address of the Gen-IWK IPE], "/", &XSDSTORAGE;,"/", &XSDFILE; EXAMPLE: //m2m.service.com/IN- CSE- 0001/bigFatCse/name_of_IPE_AE/ ww.XYZ.com_WashingMachines /testService.xsd &DEVICE; &DEVICE_1; … &DEVICE_n; Name of <flexContainer> specialization type for a device or a sub-device Shall be identical to a class name of a class:Device that is in the range of object property:consistsOf. It identifies a device type. Base Ontology &SERVICE_1; … Name of <flexContainer> specialization type for a Service Shall be identical to the name of a Service class in the ontology. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 30 oneM2M TS-0030 version 4.0.1 Release 4 Convention Is short for Replacement rule &SERVICE_n; The class is in the range of object property:hasService of a Device. (See note 3) &OPERATION_1; … &OPERATION_n; Name of <flexContainer> specialization type for an Operation See Note 1 Shall be identical to the name of an Operation class in the ontology The class is in the range of object property:hasOperation of a Service. &THINGPROPERTY_1; … &THINGPROPERTY_n; Name of a customAttribute of the Device's <flexContainer> describing a ThingpProperty of the device Shall be identical to the name of a ThingProperty class in the ontology The class is in the range of object property: hasThingProperty of a Device. &INPUTDATAPOINT_1; … &INPUTDATAPOINT_n; Name of a customAttribute of the Service's <flexContainer> describing an InputDataPoint Shall be identical to the name of a InputDataPoint class of the service The class is in the range of object property:hasInputDataPoint of a Service. &OUTPUTDATAPOINT_1; … &OUTPUTDATAPOINT_n; Name of a customAttribute of the Service's <flexContainer> describing an OutputDataPoint Shall be identical to the name of a OutputDataPoint class of the service. The class is in the range of object property:hasOutputDataPoint of a Service. &OPERATIONINPUT_1; … &OPERATIONINPUT_n; Name of a customAttribute of the Operation's <flexContainer> describing an OperationInput Shall be identical to the name of a OperationInput class of the Operation. The class is in the range of object property:hasInput of an Operation. &OPERATIONOUTPUT_1; … &OPERATIONOUTPUT_n; Name of a customAttribute of the Operation's <flexContainer> describing an OperationOutput Shall be identical to the name of a OperationOutput class of the Operation. The class is in the range of object property:hasOutput of an Operation. &SIMPLEDATATYPE; One out of: xs:NCName , xs:anySimpleType , xs:anyType , xs:anyURI , xs:base64Binary , xs:boolean , xs:decimal , xs:dateTime, xs:double , xs:duration , xs:float , xs:hexBinary , xs:integer , xs:language , xs:nonNegativeInteger , xs:normalizedString , xs:positiveInteger , xs:string , xs:token , xs:unsignedInt , xs:unsignedLong , xs:unsignedShort Shall be identical to the value of the data property:hasDataType. &RESTRICTIONVALUE; The value of the restriction Is a regular expression in case of restriction type &RESTRICTIONTYPE; = xs:pattern, in all other cases a number. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 31 oneM2M TS-0030 version 4.0.1 Release 4 Convention Is short for Replacement rule &TYPENAME; Name of the type of a variable (Inut/OutputDataPoint, OperationInput/Output,Thingproperty) or name of a sub-structure in a StructuredTypeVariable Shall be identical to the name the class of a Variable or sub-structure (i.e. a Variable that is the range of object property:hasSubStructure), adding "Type" to that name. e.g. if the name of an OutputDataPoint class is &OUTPUTDATAPOINT; = "temperature" then the &TYPENAME; is "temperatureType". If "temperature" is a StructuredTypeVariable, containing substructures with &VARIABLENAME_1; = "fahrenheit" and &VARIABLENAME_2; = "accuracy" then the two &TYPENAME;s would be "fahrenheitType" and "accuracyType". &VARIABLENAME_1; &VARIABLENAME_2; … &VARIABLENAME_n; name of a sub-structure in a StructuredTypeVariable Shall be identical to the class name of a Variable that is the range of object property:hasSubStructure. NOTE 1: In case the operation produces operation output an instance of the <flexContainer> for that operation may have a child-resource of the same <flexContainer> specialization type for that Operation to contain the operation output data. NOTE 2: For the kind of restriction (xs:minInclusive, xs:maxInclusive … ) of simple data types no convention is given in this table. Its entry in the XSD file is given by the line: <kind-of-restriction value="&RESTRICTIONVALUE;"/> where kind-of-restriction is given by the value in the range of a specific sub-property of Data Property: hasDataRestriction of a SimpeTypeVariable. It is possible to specify no restrictions, one restriction or multiple restrictions for a simple data type. NOTE 3: Sub-services (range of object property:hasSubService of a Service) are not considered in this release. |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3 Data typing for Variables | |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.1 Information on datatypes contained in the ontology | All classes of the Base Ontology that describe data (i.e. InputDataPoint, OutputDataPoint, OperationInput, OperationOutput, ThingProperty are sub-classes of either the class:SimpleTypeVariable or the class StructuredTypeVariable. (This is due to the fact that class:Variable is the disjoint union of classes SimpleTypeVariable and StructuredTypeVariable). Class:Variable and its sub-classes Class:SimpleTypeVariable and StructuredTypeVariable support (i.e. are the domain class of) properties that allow to specify the datatype of the variable: • Class:SimpleTypeVariable supports data property:isDataList (range: xsd:Boolean). If a class of the ontology that describes the Interworked Device is a sub-class of class:SimpleTypeVariable and "isDataList value TRUE" is specified then the class describes a list data type. Similarly, if "isDataList value FALSE" is specified or property:isDataList is not specified then the class describes a data type describing a single value. • Class:SimpleTypeVariable supports data property:hasDataType. The range of data property:hasDataType is the set of following strings: {"xs:NCName" , "xs:anySimpleType" , "xs:anyType" , "xs:anyURI" , "xs:base64Binary" , "xs:boolean" , "xs:dateTime" , "xs:decimal" , "xs:double" , "xs:duration" , "xs:float" , "xs:hexBinary" , "xs:integer" , "xs:language" , "xs:nonNegativeInteger" , "xs:normalizedString" , "xs:positiveInteger" , "xs:string" , "xs:token" , "xs:unsignedInt" , "xs:unsignedLong" , "xs:unsignedShort"} This data property indicates that the data type of the Variable is exactly one of these simple XML data types, contained in https://www.w3.org/TR/xmlschema11-2 (see ETSI TS 118 112 [3], clause 6.3.1). ETSI ETSI TS 118 130 V4.0.1 (2023-06) 32 oneM2M TS-0030 version 4.0.1 Release 4 For example if a class of the ontology that describes the Interworked Device is a sub-class of class:SimpleTypeVariable and " hasDataType value "xs:integer"" is specified then the class describes an integer value (or, if additionally "isDataList value TRUE" is specified, then the class describes a list of integer values): • Class:SimpleTypeVariable also supports data property:hasDataRestriction and its sub-properties: - hasDataRestriction_minInclusive; - hasDataRestriction_maxInclusive; - hasDataRestriction_minExclusive; - hasDataRestriction_maxExclusive; - hasDataRestriction_length; - hasDataRestriction_minLength; - hasDataRestriction_maxLength; - hasDataRestriction_pattern; which specify restrictions on the permissible values of the data. • In addition Class: StructuredTypeVariable supports object property:hasSubStructure (range: class:Variable). This object property allows to create complex, structured data types. Each class in the range of object property:hasSubStructure signifies an element of the structure. EXAMPLE: If a class XY of the ontology is a sub-class of class:Variable and supports object property: - hasSubStructure range class:X (class:X being a sub-class of class:Variable); - hasSubStructure range class:Y (class:Y being a sub-class of class:Variable). then class XY is also a sub-class of class: StructuredTypeVariable and describes a structured data type that has data types X and Y as sub structures. NOTE: The data properties:hasDataType, isDataList and the object property:hasSubStructure are mutually exclusive: class:SimpleTypeVariable specifies (is defined as a sub-class of: )"hasSubStructure exactly 0 Variable". A data type cannot at the same time be a simple data type and a structured data type! |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.2 Construction of Simple Data Types | If class:Variable supports: • data property: isDataList value FALSE • data property: hasDataType value $SIMPLEDATATYPE$ then the XSD for the <flexContainer> that contains a customAttribute of that type (given by &TYPENAME;) needs to contain the typedefinition for that customAttribute. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 33 oneM2M TS-0030 version 4.0.1 Release 4 Table 2: Type definition for Simple Types <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="&TYPENAME;"> <xs:restriction base="&SIMPLEDATATYPE;"> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:minInclusive value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxInclusive value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> Example: if the name of an OutputDataPoint class is &OUTPUTDATAPOINT; = "temperature", which contains a temperature value in Celsius, then a type definition could be <xs:simpleType name="temperatureType"> <xs:restriction base="xs:float"> < xs:minInclusive value="−273.15"/> < xs:maxInclusive value="100"/> </xs:restriction> </xs:simpleType> |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.3 List Data Types | If class:Variable supports: • data property: isDataList value TRUE • data property: hasDataType value $SIMPLEDATATYPE$ then the XSD for the <flexContainer> that contains a customAttribute of that type (given by &TYPENAME;) needs to contain the typedefinition for that customAttribute. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 34 oneM2M TS-0030 version 4.0.1 Release 4 Table 3: Type definition for List Data Types <!--********************** --> <!-- Ontology based IWK Simple Types (Lists)--> <!--********************** --> <xs:simpleType name="&TYPENAME;"> <xs:restriction> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="&SIMPLEDATATYPE;"> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs: xs:pattern value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxLength value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> Example: if the name of an OutputDataPoint class is &OUTPUTDATAPOINT; = "temperatureSeries", which contains a list of up to 10 temperature values, then a type definition could be <xs:simpleType name="temperatureSeriesType"> <xs:restriction> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="xs:float"> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> < xs:minInclusive value="−273.15"/> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.1.3.4 Structured Data Types | If class:Variable supports: • data property: isDataList value FALSE; • object property: hasSubStructure with range class:&VARIABLENAME_1; • object property: hasSubStructure with range class:&VARIABLENAME_2; • … • object property: hasSubStructure with range class:&VARIABLENAME_n; then the XSD for the <flexContainer> that contains that customAttribute needs to contain the typedefinition (given by &TYPENAME;) for that customAttribute. Additionally (simple or complex) typedefinitions for the Variables that are in the range of object property: hasSubStructure (given by &TYPENAME_1; … &TYPENAME_n;) need to be contained in the XSD. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 35 oneM2M TS-0030 version 4.0.1 Release 4 Table 4: Type definition for Structured Data Types <!--********************** --> <!-- Ontology based IWK Complex Types --> <!--********************** --> <xs:complexType name="&TYPENAME;"> <xs:sequence> <!-- should include all classes:Variable that are in the range of object property:hasSubStructure --> <xs:element name="&VARIABLENAME_1;" type=" obi:&TYPENAME_1;"/> <!-- ... --> <xs:element name="&VARIABLENAME_n;" type=" obi:&TYPENAME_n;"/> </xs:sequence> </xs:complexType> Example: if the name of a OutputDataPoint class is &OUTPUTDATAPOINT; = "accurateTemperature" and that "accurateTemperature" is a StructuredTypeVariable, containing substructures with &VARIABLENAME_1; = "fahrenheit" and &VARIABLENAME_2; = "accuracy" then then a type definition could be <xs:complexType name="accurateTemperatureType"> <xs:sequence> <!-- should include all classes:Variable that are in the range of object property:hasSubStructure --> <xs:element name="fahrenheit" type="fahrenheitType"/> <!-- ... --> <xs:element name="accuracy" type="accuracyType"/> </xs:sequence> </xs:complexType> |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.2 XSD template for sub-classes of Base Ontology class: Device | This clause only applies for the case when an Interworked Device is represented as <flexContainer>. In case an Interworked Device is represented as <AE> the resource definition of the <AE> resource in ETSI TS 118 101 [2] applies. Specific XSD definition for class:Device to be substituted at the placeholder in the XSD skeleton in clause 7.2.1.2 The value of attribute containerDefinition of the specialization of the <flexContainer> shall be set as specified in table 1. EXAMPLE: <xs:element name="containerDefinition" type="//m2m.service.com/IN-CSE- 0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines /testDevice.xsd" />. Table 5: Template definition of a <flexContainer> for Device <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 36 oneM2M TS-0030 version 4.0.1 Release 4 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <!DOCTYPE placeholders [ <!-- ==== examples; see description in table 1 ==== --> <!ENTITY XSDSTORAGE "ww.XYZ.com_WashingMachines"> <!-- Example targetNamespace value --> <!ENTITY DEVICE "testDevice"> <!-- Example name of the device defined in this file--> <!ENTITY DEVICE_1 "device_1"> <!-- Example name of sub-device --> <!ENTITY DEVICE_n "device_n"> <!-- Example name of sub-device --> <!ENTITY SERVICE_1 "service_1"> <!-- Example name of service of this device --> <!ENTITY SERVICE_n "service_n"> <!-- Example name of service of this device --> <!ENTITY THINGPROPERTY_1 "tp_1"> <!-- Example name of thingProperty of this device --> <!ENTITY THINGPROPERTY_n "tp_n"> <!-- Example name of thingProperty of this device --> <!ENTITY TYPENAME_1 "tp_1Type"> <!-- Example type name (of thingProperty) --> <!ENTITY TYPENAME_2 "variablename_1Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_3 "variablename_3Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_n " tp_nType "> <!-- Example type name (of thingProperty) --> <!ENTITY VARIABLENAME_1 "variablename_1"> <!-- Example variable name (of sub-structure) --> <!ENTITY VARIABLENAME_n "variablename_n"> <!-- Example variable name (of sub-structure) --> <!ENTITY SIMPLEDATATYPE "xs:integer"> <!-- Example simple datatype --> <!ENTITY RESTRICTIONVALUE "100"> <!-- Example value of a type restriction --> ]> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="&XSDSTORAGE;" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="&XSDSTORAGE;" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> <!-- include XSDs of child resources: (sub-)Devices and Services used in this Device --> <xs:include schemaLocation="&DEVICE_1;.xsd" /> <!-- ... --> <xs:include schemaLocation="&DEVICE_n;.xsd" />´ <xs:include schemaLocation="&SERVICE_1;.xsd" /> <!-- ... --> <xs:include schemaLocation="&SERVICE_n;.xsd" /> <xs:element name="&DEVICE;" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes --> <!-- nodeLink as custom attribute --> <xs:element name="nodeLink" type="xs:anyURI" minOccurs="0"/> <!-- all OperationInput- and Outputs are listed here as custom attributes --> <xs:element name="&THINGPROPERTY_1;" type=" obi:&TYPENAME_1;" minOccurs="0"/> <!-- ... --> <xs:element name="&THINGPROPERTY_n;" type=" obi:&TYPENAME_n;" minOccurs="0"/> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 37 oneM2M TS-0030 version 4.0.1 Release 4 <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Device specific Child Resources (sub-Devices of the Device) --> <xs:element ref=" obi:&DEVICE_1;"/> <!-- ... --> <xs:element ref=" obi:&DEVICE_n;"/> <!-- Device specific Child Resources (Services of the Device) --> <xs:element ref=" obi:&SERVICE_1;"/> <!-- ... --> <xs:element ref=" obi:&SERVICE_n;"/> <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for ThingProperties of this Device --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="&TYPENAME_1;"> <xs:restriction base="&SIMPLEDATATYPE;"/> </xs:simpleType> <xs:simpleType name="&TYPENAME_2;"> <xs:restriction base="&SIMPLEDATATYPE;"> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:minInclusive value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxInclusive value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Simple Types (Lists)--> <!--********************** --> <xs:simpleType name="&TYPENAME_3;"> <xs:restriction> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="&SIMPLEDATATYPE;"> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 38 oneM2M TS-0030 version 4.0.1 Release 4 <xs: xs:pattern value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxLength value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Complex Types --> <!--********************** --> <xs:complexType name="&TYPENAME_n;"> <xs:sequence> <!-- should include all classes:Variable that are in the range of object property:hasSubStructure --> <xs:element name="&VARIABLENAME_1;" type=" obi:&TYPENAME_2;"/> <!-- ... --> <xs:element name="&VARIABLENAME_n;" type=" obi:&TYPENAME_3;"/> </xs:sequence> </xs:complexType> </xs:schema> |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.3 XSD template for sub-classes of Base Ontology class: Service | Specific XSD definition for class:Service to be substituted at the placeholder in the XSD skeleton in clause 7.2.1.2. The value of attribute containerDefinition of the specialization of the <flexContainer> shall be set as specified in table 1. EXAMPLE: <xs:element name="containerDefinition" type="//m2m.service.com/IN-CSE- 0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines /testService.xsd" />. Table 6: Template definition of a <flexContainer> for Service <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 39 oneM2M TS-0030 version 4.0.1 Release 4 oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <!DOCTYPE placeholders [ <!-- ==== examples; see description in table 1 ==== --> <!ENTITY XSDSTORAGE "ww.XYZ.com_WashingMachines"> <!-- Example targetNamespace value --> <!ENTITY SERVICE "testService"> <!-- Example name of the service defined in this file--> <!ENTITY OPERATION_1 "operation_1"> <!-- Example name of operation --> <!ENTITY OPERATION_n "operation_n"> <!-- Example name of operation --> <!ENTITY INPUTDATAPOINT_1 "idp_1"> <!-- Example name of inputDataPoint of this service --> <!ENTITY INPUTDATAPOINT_n "idp_n"> <!-- Example name of inputDataPoint of this service --> <!ENTITY OUTPUTDATAPOINT_1 "odp_1"> <!-- Example name of outputDataPoint of this service --> <!ENTITY OUTPUTDATAPOINT_n "odp_n"> <!-- Example name of outputDataPoint of this service --> <!ENTITY TYPENAME_1 "idp_1Type"> <!-- Example type name (of DataPoint) --> <!ENTITY TYPENAME_2 "variablename_1Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_3 "variablename_3Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_n " odp_nType "> <!-- Example type name (of DataPoint) --> <!ENTITY VARIABLENAME_1 "variablename_1"> <!-- Example variable name (of sub-structure) --> <!ENTITY VARIABLENAME_n "variablename_n"> <!-- Example variable name (of sub-structure) --> <!ENTITY SIMPLEDATATYPE "xs:integer"> <!-- Example simple datatype --> <!ENTITY RESTRICTIONVALUE "100"> <!-- Example value of a type restriction --> ]> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="&XSDSTORAGE;" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="&XSDSTORAGE;" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> <!-- include XSDs of child resources: Operations used in this Service --> <xs:include schemaLocation="&OPERATION_1;.xsd" /> <!-- ... --> <xs:include schemaLocation="&OPERATION_n;.xsd" /> <xs:element name="&SERVICE;" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes --> <!-- all Input- and OutputDatapoints are listed here as custom attributes --> <xs:element name="&INPUTDATAPOINT_1;" type=" obi:&TYPENAME_1;" minOccurs="0"/> <xs:element name="&OUTPUTDATAPOINT_1;" type=" obi:&TYPENAME_1;" minOccurs="0"/> <!-- ... --> <xs:element name="&INPUTDATAPOINT_n;" type=" obi:&TYPENAME_n;" minOccurs="0"/> <xs:element name="&OUTPUTDATAPOINT_n;" type=" obi:&TYPENAME_n;" minOccurs="0"/> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Service specific Child Resources (Operations of the Service) --> <xs:element ref=" obi:&OPERATION_1;"/> <!-- ... --> <xs:element ref=" obi:&OPERATION_n;"/> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 40 oneM2M TS-0030 version 4.0.1 Release 4 <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for Datapoints of this Service --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="&TYPENAME_1;"> <xs:restriction base="&SIMPLEDATATYPE;"/> </xs:simpleType> <xs:simpleType name="&TYPENAME_2;"> <xs:restriction base="&SIMPLEDATATYPE;"> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:minInclusive value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxInclusive value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Simple Types (Lists)--> <!--********************** --> <xs:simpleType name="&TYPENAME_3;"> <xs:restriction> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="&SIMPLEDATATYPE;"> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:pattern value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxLength value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Complex Types --> <!--********************** --> <xs:complexType name="&TYPENAME_n;"> <xs:sequence> <!-- should include all classes:Variable that are in the range of object property:hasSubStructure --> <xs:element name="&VARIABLENAME_1;" type=" obi:&TYPENAME_2;"/> <!-- ... --> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 41 oneM2M TS-0030 version 4.0.1 Release 4 <xs:element name="&VARIABLENAME_n;" type=" obi:&TYPENAME_3;"/> </xs:sequence> </xs:complexType> </xs:schema> |
629671bfddb226c7b32c7184db9eee0f | 118 130 | 7.2.4 XSD template for sub-classes of Base Ontology class: Operation | Specific XSD definition for class:Operation to be substituted at the placeholder in the XSD skeleton in clause 7.2.1.2. The value of attribute containerDefinition of the specialization of the <flexContainer> shall be set as specified in table 1. EXAMPLE: <xs:element name="containerDefinition" type="//m2m.service.com/IN-CSE- 0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines /testOperation.xsd" />. Table 7: Template definition of a <flexContainer> for Operation <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <!DOCTYPE placeholders [ <!-- ==== examples; see description in table 1 ==== --> <!ENTITY XSDSTORAGE "ww.XYZ.com_WashingMachines"> <!-- Example targetNamespace value --> <!ENTITY OPERATION "testOperation"> <!-- Example name of operation defined in this file --> <!ENTITY OPERATIONINPUT_1 "oip_1"> <!-- Example name of operationInput of this service --> <!ENTITY OPERATIONINPUT_n "oip_n"> <!-- Example name of operationInput of this service --> <!ENTITY OPERATIONOUTPUT_1 "oop_1"> <!-- Example name of operationOutput of this service --> <!ENTITY OPERATIONOUTPUT_n "oop_n"> <!-- Example name of operationOutput of this service --> <!ENTITY TYPENAME_1 "oip_1Type"> <!-- Example type name (of operationInput) --> <!ENTITY TYPENAME_2 "variablename_1Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_3 "variablename_3Type"> <!-- Example type name (of sub-structure) --> <!ENTITY TYPENAME_n " oop_nType "> <!-- Example type name (of operationOutput) --> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 42 oneM2M TS-0030 version 4.0.1 Release 4 <!ENTITY VARIABLENAME_1 "variablename_1"> <!-- Example variable name (of sub-structure) --> <!ENTITY VARIABLENAME_n "variablename_n"> <!-- Example variable name (of sub-structure) --> <!ENTITY SIMPLEDATATYPE "xs:integer"> <!-- Example simple datatype --> <!ENTITY RESTRICTIONVALUE "100"> <!-- Example value of a type restriction --> ]> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="&XSDSTORAGE;" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="&XSDSTORAGE;" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription- v3_0_0.xsd"/> <!-- for operations no includes needed from obi: namespace --> <xs:element name="&OPERATION;" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes for operations--> <!-- all OperationInput- and Outputs are listed here as custom attributes --> <xs:element name="&OPERATIONINPUT_1;" type=" obi:&TYPENAME_1;" minOccurs="0"/> <xs:element name="&OPERATIONOUTPUT_1;" type=" obi:&TYPENAME_n;" minOccurs="0"/> <!-- ... --> <xs:element name="&OPERATIONINPUT_n;" type=" obi:&TYPENAME_1;" minOccurs="0"/> <xs:element name="&OPERATIONOUTPUT_n;" type=" obi:&TYPENAME_n;" minOccurs="0"/> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Child Resource for Operations that have OperationOutputs is an Operation of the same type --> <xs:element ref="&OPERATION;"/> <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for OperationInputs and -Outputs of this Operation --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="&TYPENAME_1;"> <xs:restriction base="&SIMPLEDATATYPE;"/> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 43 oneM2M TS-0030 version 4.0.1 Release 4 </xs:simpleType> <xs:simpleType name="&TYPENAME_2;"> <xs:restriction base="&SIMPLEDATATYPE;"> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restriction types possible --> <xs:minInclusive value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxInclusive value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Simple Types (Lists)--> <!--********************** --> <xs:simpleType name="&TYPENAME_3;"> <xs:restriction> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="&SIMPLEDATATYPE;"> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:pattern value="&RESTRICTIONVALUE;"/> <!-- ... xs:minInclusive, xs:maxInclusive, xs:minExclusive, xs:maxExclusive, xs:length, xs:minLength, xs:maxLength, xs:pattern --> <xs:maxLength value="&RESTRICTIONVALUE;"/> <!-- end of lines only for restrictions of the values --> </xs:restriction> </xs:simpleType> <!--********************** --> <!-- Ontology based IWK Complex Types --> <!--********************** --> <xs:complexType name="&TYPENAME_n;"> <xs:sequence> <!-- should include all classes:Variable that are in the range of object property:hasSubStructure --> <xs:element name="&VARIABLENAME_1;" type=" obi:&TYPENAME_2;"/> <!-- ... --> <xs:element name="&VARIABLENAME_n;" type=" obi:&TYPENAME_3;"/> </xs:sequence> </xs:complexType> </xs:schema> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 44 oneM2M TS-0030 version 4.0.1 Release 4 Annex A (informative): Example for ontology based interworking A.1 Overview This example extends the example - a (simplified) washing machine - of clause B.1.3.3 of ETSI TS 118 112 [3]. However in contrast to ETSI TS 118 112 [3] in this example it is assumed that the washing machine is not a 'native' oneM2M application but is interworked with the oneM2M System via ontology based interworking. In contrast to ETSI TS 118 112 the semantic description (contained in the descriptor attribute of the <semanticDescriptor> resource) is not of interest but rather the structure of the specialized <flexContainer> resources to which these <semanticDescriptor>s belong. Also Functions and Commands (which are only described in RDF form in the sematic descriptors) are not considered, but only Services, Input- / OutputDatapoints and Operations, which are the resources containing data for communication with the washing machine are handled here. The example given here is a (simplified) washing machine, based on class:WashingMachine, specified in SAREF [i.2]. It is assumed the washing machine has been manufactured by manufacturer XYZ. The ontology that describes XYZ washingmachines is identified by the IRI: http://www.XYZ.com/WashingMachines. It is assumed the XYZ washing machines are compliant with SAREF. Also, as described in clause B.1 of ETSI TS 118 112 [3], SAREF is compliant with the oneM2M base ontology. That implies that every class/property of the XYZ ontology is either a subclass/sub-property of SAREF or - if no suitable class/property exists in SAREF - is a subclass/sub-property of the base ontology. The classes/properties that are taken from SAREF are prefixed with: "saref:" The classes/properties that are taken from XYZ ontology are prefixed with: "XYZ:" The classes/properties that are taken from the base ontology are prefixed with: "BO:" • The model of the type of washing machine is class XYZ:XYZ_Cool: - which is a sub-class of class saref:WashingMachine: which in turn is subclass of BO:InterworkedDevice. • The state of the washing machine is given by XYZ:WashingMachineStatus that can take the values "WASHING" or "STOPPED" or "ERROR": - XYZ:WashingMachineStatus is a sub-class of saref:state: which in turn is subclass of BO:OutputDataPoint. • This WashingMachineStatus is provided as an the OutputDataPoint of a service XYZ:MonitorService which exposes the MonitoringFunction to the network: - Class XYZ:MonitorService is a sub-class of saref:Service: which in turn is subclass of BO:Service. • The related function of the washing machine is described by class XYZ:MonitoringFunction: - Class XYZ:MonitoringFunction is a sub-class of saref: Function: which in turn is subclass of BO:Function. • The function of the washing machine to control the washing machine is in class XYZ:StartStopFunction which has three commands: ON_Command, OFF_Command, Toggle_Command. ETSI ETSI TS 118 130 V4.0.1 (2023-06) 45 oneM2M TS-0030 version 4.0.1 Release 4 NOTE: Since classes for Functions and Commands are not needed for interworking as they only appear in the RDF description in <sematicDescriptor> resources the XYZ:MonitoringFunction and XYZ:StartStopFunction are not further considered here. They are, however, described in the related example of clause B.1.3.3 of ETSI TS 118 112 [3]. • The related service of the washing machine that represents that XYZ:StartStopFunction is class: XYZ:SwitchOnService. It has: - an InputDataPoint: XYZ:BinaryInput (to expose command ON_Command and OFF_Command); and - an Operation: XYZ:ToggleBinary (to expose command Toggle_Command): Class XYZ: SwitchOnService is a sub-class of saref:SwitchOnService: - which in turn is subclass of BO:Service. • InputDataPoint: XYZ:BinaryInput is a sub-class of BO:InputDataPoint. • Operation: XYZ:ToggleBinary is a sub-class of BO:Operation. • XYZ describes this type of washing machine with a XYZ:Description as "Very cool Washing Machine": - XYZ:Description os a sub-class of BO:ThingProperty. Figure A.1 shows the relationship of the ontology that describes model XYZ_cool of XYZ washingmachines with the oneM2M base ontology. Service Operation Output DataPoint Input DataPoint Toggle Binary Binary Input Monitor Service WashingMa chineStatus has Service has Input DataPoint has Output DataPoint has Operation SimpleType Variable Is-a Is-a Is-a Is-a Is-a Is-a <oneM2M:hasDataType>xs:string</oneM2M:hasDataType> <oneM2M:hasDataRestriction_pattern>"WASHING|STOPPED |ERROR" </oneM2M:hasDataRestriction_pattern> offers Is-a has Input Parameter has Output Parameter Is-a Is-a <oneM2M:hasDataType>xs:binary</oneM2M:hasDataType> SwitchOn Service oneM2M base ontology ontology of XYZ washing machines Is-a Thing Property hasThing Property Is-a Description has Description Is-a Is-a Interworked Device XYZ_Cool washing machine <oneM2M:hasDataType>xs:string</oneM2M:hasDataType> Figure A.1: Relationship of the ontology that describes model XYZ_cool of XYZ washingmachines with the oneM2M base ontology ETSI ETSI TS 118 130 V4.0.1 (2023-06) 46 oneM2M TS-0030 version 4.0.1 Release 4 A.2 XSDs created by the IPE A.2.1 XSD storage <container> According to clause 7.2.1.1 the IPE creates a <container> resource that acts as a XSD-storage and that is a child resource of the IPE's <AE>. Derived from the IRI of the ontology: http://www.XYZ.com/WashingMachines, following the rule given in table 1 of clause 7.2.1.2 the resource name for that <container> resource (in the table the placeholder is called &XSDSTORAGE;) will be www.XYZ.com_WashingMachines. The IPE will also create <contentInstance> resources as child-resources of the XSD-storage <container> resource with the following resource names (see &XSDFILE; in table 1 of clause 7.2.1.2): • XYZ_Cool.xsd … contains the XSD for the <flexContainer> resource of the Interworked Device type XYZ_Cool. • SwitchOnService.xsd … contains the XSD for the <flexContainer> resource of the Service type SwitchOnService. • MonitorService.xsd … contains the XSD for the <flexContainer> resource of the Service type MonitorService. • ToggleBinary.xsd … contains the XSD for the <flexContainer> resource of the Operation type ToggleBinary. When the IPE crates a new <flexContainer> specialization of these types then the attribute containerDefinition will contain the absolute, hierarchical address of the <contentinstance> that contains the related XSD. E.g. for the SwitchOnService it could have the value: //m2m.service.com/IN-CSE0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines/SwitchOnService.xsd A.2.2 XSD for the Interworked Device type XYZ_Cool Following the principles of clause 7.2.2 an Interworked Device is represented as <flexContainer>. According to the the convention in table 1 of clause 7.2.1.2 the placeholders and their substitutions that are needed for a <flexContainer>, representing an Interworked Device are: • &XSDSTORAGE; is substituted by www.XYZ.com_WashingMachines • &DEVICE; is substituted by XYZ_Cool • &SERVICE_1; is substituted by SwitchOnService • &SERVICE_2; is substituted by MonitorService • THINGPROPERTY_1; is substituted by Description • &TYPENAME_1; is substituted by DescriptionType • &SIMPLEDATATYPE; is substituted by xs:string The XSD in the <contentInstance> with resource name XYZ_Cool.xsd will contain: Table A.1 <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other ETSI ETSI TS 118 130 V4.0.1 (2023-06) 47 oneM2M TS-0030 version 4.0.1 Release 4 proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="www.XYZ.com_WashingMachines" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="www.XYZ.com_WashingMachines" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> <!-- include XSDs of child resources: (sub-)Devices and Services used in this Device --> <xs:include schemaLocation="SwitchOnService.xsd" /> <xs:include schemaLocation="MonitorService.xsd" /> <xs:element name="XYZ_Cool" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes --> <!-- nodeLink as custom attribute --> <xs:element name="nodeLink" type="xs:anyURI" minOccurs="0"/> <!-- all OperationInput- and Outputs are listed here as custom attributes --> <xs:element name="Description" type=" obi:DescriptionType" minOccurs="0"/> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Device specific Child Resources (sub-Devices of the Device) --> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 48 oneM2M TS-0030 version 4.0.1 Release 4 <!-- Device specific Child Resources (Services of the Device) --> <xs:element ref=" obi:SwitchOnService"/> <xs:element ref=" obi:MonitorService"/> <!-- Common Child Resources --> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for ThingProperties of this Device --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="DescriptionType"> <xs:restriction base="xs:string"/> </xs:simpleType> </xs:schema> A.2.3 XSD for the Service type SwitchOnService Following the principles of clause 7.2.3 a Service is represented as <flexContainer>. According to the the convention in table 1 of clause 7.2.1.2 the placeholders and their substitutions that are needed for a <flexContainer>, representing an Interworked Device are: • &XSDSTORAGE; is substituted by www.XYZ.com_WashingMachines • &SERVICE; is substituted by SwitchOnService • &OPERATION_1; is substituted by ToggleBinary • &INPUTDATAPOINT_1; is substituted by BinaryInput • &TYPENAME_1; is substituted by ToggleBinaryType • &SIMPLEDATATYPE; is substituted by xs:boolean The XSD in the <contentInstance> with resource name SwitchOnService.xsd will contain. Table A.2 <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. Notice of Disclaimer & Limitation of Liability ETSI ETSI TS 118 130 V4.0.1 (2023-06) 49 oneM2M TS-0030 version 4.0.1 Release 4 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="www.XYZ.com_WashingMachines" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="www.XYZ.com_WashingMachines" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> <!-- include XSDs of child resources: Operations used in this Service --> <xs:include schemaLocation="ToggleBinary.xsd" /> <xs:element name="SwitchOnService" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes --> <!-- all Input- and OutputDatapoints are listed here as custom attributes --> <xs:element name="BinaryInput" type=" obi:BinaryInputType" minOccurs="0"/> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Service specific Child Resources (Operations of the Service) --> <xs:element ref=" obi:ToggleBinary"/> <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 50 oneM2M TS-0030 version 4.0.1 Release 4 </xs:element> <!-- types used for Datapoints of this Service --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name=" BinaryInputType "> <xs:restriction base="xs:boolean"/> </xs:simpleType> </xs:schema> A.2.4 XSD for the Service type MonitorService Following the principles of clause 7.2.3 a Service is represented as <flexContainer>. According to the the convention in table 1 of clause 7.2.1.2 the placeholders and their substitutions that are needed for a <flexContainer>, representing an Interworked Device are: • &XSDSTORAGE; is substituted by www.XYZ.com_WashingMachines • &SERVICE; is substituted by MonitorService • &OUTPUTDATAPOINT_1; is substituted by WashingMachineStatus • &TYPENAME_1; is substituted by WashingMachineStatusType • &SIMPLEDATATYPE; is substituted by xs:string • &RESTRICTIONVALUE; is substituted by "WASHING"|"STOPPED"|"ERROR" The XSD in the <contentInstance> with resource name MonitorService.xsd will contain. Table A.3 <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN ETSI ETSI TS 118 130 V4.0.1 (2023-06) 51 oneM2M TS-0030 version 4.0.1 Release 4 PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="www.XYZ.com_WashingMachines" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="www.XYZ.com_WashingMachines" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> <xs:element name="MonitorService" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes --> <!-- all Input- and OutputDatapoints are listed here as custom attributes --> <xs:element name="WashingMachineStatus" type="obi:WashingMachineStatusType" minOccurs="0"/> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Service specific Child Resources (Operations of the Service) --> <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for Datapoints of this Service --> <!-- ********************** --> <!-- Ontology based IWK Simple Types --> <!-- ********************** --> <xs:simpleType name="WashingMachineStatusType"> <xs:restriction base="xs:string"> <!-- next lines for restrictions of the values. Remove not needed ones, Multiple restrictiontypes possible --> <xs:pattern value= "WASHING|STOPPED|ERROR"/> </xs:restriction> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 52 oneM2M TS-0030 version 4.0.1 Release 4 </xs:simpleType> </xs:schema> A.2.5 XSD for the Operation type ToggleBinary Following the principles of clause 7.2.3 a Service is represented as <flexContainer>. According to the the convention in table 1 of clause 7.2.1.2 the placeholders and their substitutions that are needed for a <flexContainer>, representing an Interworked Device are: • &XSDSTORAGE; is substituted by www.XYZ.com_WashingMachines • &OPERATION; is substituted by ToggleBinary The XSD in the <contentInstance> with resource name ToggleBinary.xsd will contain. Table A.4 <?xml version="1.0" encoding="UTF-8"?> <!-- Copyright Notification The oneM2M Partners authorize you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services, nor does it encompass the granting of any patent rights. The oneM2M Partners assume no responsibility for errors or omissions in this document. © 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved. 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. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. --> <xs:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="www.XYZ.com_WashingMachines" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:m2m="http://www.onem2m.org/xml/protocols" xmlns:obi="www.XYZ.com_WashingMachines" elementFormDefault="unqualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-semanticDescriptor- v3_0_0.xsd"/> <xs:import namespace="http://www.onem2m.org/xml/protocols" schemaLocation="CDT-subscription-v3_0_0.xsd"/> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 53 oneM2M TS-0030 version 4.0.1 Release 4 <!-- for operations no includes needed from obi: namespace --> <xs:element name="ToggleBinary" substitutionGroup="m2m:sg_flexContainerResource"> <xs:complexType> <xs:complexContent> <!-- Inherit Common Attributes from data type "flexContainerResource" --> <xs:extension base="m2m:flexContainerResource"> <xs:sequence> <!-- Resource Specific Attributes for operations--> <!-- all OperationInput- and Outputs are listed here as custom attributes --> <!-- Child Resources --> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="childResource" type="m2m:childResourceRef" minOccurs="1" maxOccurs="unbounded"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <!-- Child Resource for Operations that have OperationOutputs is an Operation of the same type - -> <!-- Common Child Resources --> <xs:element ref="m2m:semanticDescriptor"/> <xs:element ref="m2m:subscription"/> </xs:choice> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- types used for OperationInputs and -Outputs of this Operation --> </xs:schema> ETSI ETSI TS 118 130 V4.0.1 (2023-06) 54 oneM2M TS-0030 version 4.0.1 Release 4 History Document history V4.0.1 June 2023 Publication |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 1 Scope | The present document specifies the detailed defined product profiles that can be used by manufactures and service providers where for each dedicated product, one of the defined product profile can be selected. The product profile would provide guidance to what features will be implemented, what features should be implemented and what features may be implemented. The present document also describes the test purposes that need to go through if the product need to be certified. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 2 References | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. Not applicable. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] oneM2M Drafting Rules. NOTE: Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf. [i.2] ETSI TS 118 131: "oneM2M Feature Catalogue (oneM2M TS-0031)". [i.3] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)". |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3 Definition of terms, symbols and abbreviations | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.1 Terms | Void |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.2 Symbols | Void. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 6 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 3.3 Abbreviations | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5 Product service profiles | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.1 Introduction | This clause defines Product Profiles. Product may be Implementations of oneM2M specification. The Implementation is claimed to comply with one or multiple Product Profiles. Each profile is defined with fundamental feature set and extendable feature set. Fundamental feature set includes Features that shall be implemented if the Implementation under test needs to be certified against the profile. Extendable feature set includes features that are recommended to be implemented for optimization purposes. The features in the extendable feature set may be tested based on the requirement. The features in this clause are defined in ETSI TS 118 131 [i.2]. Each profile is also composed of a profile description and a profile example. The profile description is the definition of profile and describes the suitable products that should comply to this profile. The profile example gives some real market product examples as well as the usage and scenarios of the product. Each of the Profile contains the following Features as common Features. Table 5.1-1: Fundamental feature sets for all Profiles Function Feature Set Feature Remark GEN GE/GEN/00001 At least one Support one of the bindings. GE/GEN/00002 At least one Support one of the serializations. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2 Constrained sensor as ADN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.1 Profile description | The profile defines constraint sensor that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint sensor needs to be very limited. A sensor is intended to be reporting sensed data to the CSE periodically or according to some other period. Every time the sensor reports data, it sends one message to the CSE. In order to save battery, the sensor can be sleeping before and after the reporting of sensed data. For the successful report of data, there is needed some context resource architecture like the AE resource, the container resource, etc. The resource architecture can be pre-configured in order to minimize the complexity of the constraint sensor. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.2 Profile usage examples | The profile applies to constraint sensors that report periodically sensed data. Some example of this kind of product include: • Electricity, water, gas meters that report consumed amount of electricity, water or gas to the CSE. The meters are deployed inside houses and are powered by battery. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 7 oneM2M TS-0025 version 2.0.0 Release 2A • Temperature, humidity sensors that are deployed in the open air for environment monitoring. The sensors can be deployed in places that are hardly reachable for people that the sensor's need to be working without human inference for years powered with battery. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.3 Fundamental feature sets | For constrained sensors, the features in the fundamental feature sets assume that the registration relationship between the ADN and the registrar CSE has been pre-configured beforehand. The <container> resource has also been pre-configured and the resource id of the <container> resource was provisioned to the ADN as well. The ADN could utilize the resource id of the <container> resource to create <contentInstance> directly. Table 5.2.3-1: Fundamental feature sets for constrained sensor as ADN Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Support one of the format of resource identification TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/AE/GEN/CRE/002_ABS TP/oneM2M/AE/GEN/UPD/001_CSR TP/oneM2M/AE/GEN/UPD/001_SPR TP/oneM2M/AE/GEN/UPD/001_ABS TP/oneM2M/AE/GEN/UPD/002_CSR TP/oneM2M/AE/GEN/UPD/002_SPR TP/oneM2M/AE/GEN/UPD/002_ABS TP/oneM2M/AE/GEN/RET/001_CSR TP/oneM2M/AE/GEN/RET/001_SPR TP/oneM2M/AE/GEN/RET/001_ABS TP/oneM2M/AE/GEN/RET/002_CSR TP/oneM2M/AE/GEN/RET/002_SPR TP/oneM2M/AE/GEN/RET/002_ABS TP/oneM2M/AE/GEN/DEL/001_CSR TP/oneM2M/AE/GEN/DEL/001_SPR TP/oneM2M/AE/GEN/DEL/001_ABS TP/oneM2M/AE/GEN/DEL/002_CSR TP/oneM2M/AE/GEN/DEL/002_SPR TP/oneM2M/AE/GEN/DEL/002_ABS AE/GEN/00002 AE/GEN/00002/00001 Support create request TP/oneM2M/AE/DMR/CRE/001 DMR AE/DMR/00002 AE/DMR/00002/00001 Support create contentInstance TP/oneM2M/AE/DMR/CRE/002 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 8 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.2.4 Extendable feature sets | Table 5.2.4-1: Extendable feature sets for constrained sensor as ADN Function Feature Set Feature Remark REG AE/REG/00002 AE/REG/00002/00001 Create <AE> TP/oneM2M/AE/REG//CRE/001 TP/oneM2M/AE/REG/CRE/002_RR AE/GEN/00003/00001 Create <AE> with resourceName TP/oneM2M/AE/REG/CRE/002_RN AE/GEN/00003/00002 Create <AE> with expirationTime TP/oneM2M/AE/REG/CRE/002_ET AE/DIS/00001/00017 Create <AE> with labels TP/oneM2M/AE/REG/CRE/002_LBL AE/REG/00002/00002 Create <AE> with applicationName TP/oneM2M/AE/REG/CRE/002_APN DMR AE/DMR/00001 AE/DMR/00001/00001 Create <container> with no attribute set TP/oneM2M/AE/DMR/CRE/001 AE/GEN/00003/00001 Create <container> with resourceName TP/oneM2M/AE/DMR/CRE/004_RN AE/GEN/00003/00002 Create <container> with expirationTime TP/oneM2M/AE/DMR/CRE/004_ET AE/DIS/00001/00017 Create <container> with labels TP/oneM2M/AE/DMR/CRE/004_LBL AE/DMR/00001/00002 Create <container> with maxNrOfInstances TP/oneM2M/AE/DMR/CRE/004_MNI AE/DMR/00001/00003 Create <container> with maxByteSize TP/oneM2M/AE/DMR/CRE/004_MBS AE/DMR/00001/00004 Create <container> with maxInstanceAge TP/oneM2M/AE/DMR/CRE/004_MIA AE/DMR/00002 AE/GEN/00003/00001 Create <contentInstance> with resourceName TP/oneM2M/AE/DMR/CRE/003_RN AE/GEN/00003/00002 Create <contentInstance> with expirationTime TP/oneM2M/AE/DMR/CRE/003_ET AE/DIS/00001/00017 Create <contentInstance> with labels TP/oneM2M/AE/DMR/CRE/003_LBL AE/DMR/00002/00002 Create <contentInstance> with contentInfo TP/oneM2M/AE/DMR/CRE/003_CNF |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3 Constrained actuator as ADN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.1 Profile description | The profile defines constraint actuator that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint actuator needs to be very limited. An actuator is intended to be receiving control command from CSE via notification or other means. The actuator then actuates according to the control command. The actuator needs to receive control command. As a result, the actuator needs to be request reachable to receive notification or be able to start a polling channel. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.2 Profile usage examples | Switches deployed along the street light to switch on or off the street light remotely. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 9 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.3 Fundamental feature sets | Table 5.3.3-1: Fundamental feature sets for constrained sensor as ADN Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Resource identifiers TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/AE/GEN/CRE/002_ABS TP/oneM2M/AE/GEN/UPD/001_CSR TP/oneM2M/AE/GEN/UPD/001_SPR TP/oneM2M/AE/GEN/UPD/001_ABS TP/oneM2M/AE/GEN/UPD/002_CSR TP/oneM2M/AE/GEN/UPD/002_SPR TP/oneM2M/AE/GEN/UPD/002_ABS TP/oneM2M/AE/GEN/RET/001_CSR TP/oneM2M/AE/GEN/RET/001_SPR TP/oneM2M/AE/GEN/RET/001_ABS TP/oneM2M/AE/GEN/RET/002_CSR TP/oneM2M/AE/GEN/RET/002_SPR TP/oneM2M/AE/GEN/RET/002_ABS TP/oneM2M/AE/GEN/DEL/001_CSR TP/oneM2M/AE/GEN/DEL/001_SPR TP/oneM2M/AE/GEN/DEL/001_ABS TP/oneM2M/AE/GEN/DEL/002_CSR TP/oneM2M/AE/GEN/DEL/002_SPR TP/oneM2M/AE/GEN/DEL/002_ABS GEN AE/GEN/00002 AE/GEN/00002/00001 Support Create request targeting one resource TP/oneM2M/AE/DMR/CRE/001 REG AE/REG/00002 AE/REG/00002/00001 Create <AE> with mandatory attributes[2] TP/oneM2M/AE/REG//CRE/001 TP/oneM2M/AE/REG/CRE/002_RR REG AE/REG/00002 AE/REG/00002/00003 Create <AE> with pointOfAccess TP/oneM2M/AE/REG/CRE/002_POA SUB AE/SUB/00001 AE/SUB/00001/00001 Create <subscription> with mandatory attributes[2] TP/oneM2M/AE/SUB/CRE/001 |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.3.4 Extendable feature sets | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4 ADN profile 3 | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.1 Profile description | This profile defines features for normal sensor devices or software components that desire to implement oneM2M sensing services. The sensing services such as monitoring temperature, detecting illumination, collection of location information, etc. are characterized with collecting and uploading measurement data into a destination e.g. a repository. The scope of normal sensor devices cover those that are powered by electricity power or by battery that can be easily changed when the battery is off and have rich resources compared to resource-constraint sensor devices. The sensing service profile defines a set of features required to implement sensing functionalities including creation and update of <container>, creation of <contentInstance>, etc. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 10 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.2 Profile usage examples | This profile applies to normal sensors deployed in non-critical environments have relative rich resources and are powered by electricity power or by battery that can be easily changed. This profile can also apply to software components that implements sensing services. Taking smart socket as an example, when a manufacturer-A decides to design a smart socket with oneM2M sensing service, he can refer to the Sensing Service Profile to check the fundamental features that are required to implement. The fundamental features for Sensing Service Profile are defined in clause 5.4.3. When another manufacturer-B also designs a smart socket complying with the Sensing Service Profile, these two smart sockets produced from two different manufacturers are interoperable potentially to work together to implement complex tasks. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.3 Fundamental feature sets | Container is used for storing the measurements of sensing device and whenever there is data measured from the sensing device, the data will be sent to the CSE for storage by sending a <contentInstance> create request from the originator where the encoded measurement is included within the payload of the <contentInstance> create request. oneM2M sensing service profile consists of minimum features to implement Data Management for Container and ContentInstance functionality shown in table 5.4.3-1. Table 5.4.3-1: Fundamental feature set for ADN profile 3 Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Support one of the format of resource identification TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/AE/GEN/CRE/002_ABS TP/oneM2M/AE/GEN/UPD/001_CSR TP/oneM2M/AE/GEN/UPD/001_SPR TP/oneM2M/AE/GEN/UPD/001_ABS TP/oneM2M/AE/GEN/UPD/002_CSR TP/oneM2M/AE/GEN/UPD/002_SPR TP/oneM2M/AE/GEN/UPD/002_ABS TP/oneM2M/AE/GEN/RET/001_CSR TP/oneM2M/AE/GEN/RET/001_SPR TP/oneM2M/AE/GEN/RET/001_ABS TP/oneM2M/AE/GEN/RET/002_CSR TP/oneM2M/AE/GEN/RET/002_SPR TP/oneM2M/AE/GEN/RET/002_ABS TP/oneM2M/AE/GEN/DEL/001_CSR TP/oneM2M/AE/GEN/DEL/001_SPR TP/oneM2M/AE/GEN/DEL/001_ABS TP/oneM2M/AE/GEN/DEL/002_CSR TP/oneM2M/AE/GEN/DEL/002_SPR TP/oneM2M/AE/GEN/DEL/002_ABS AE/GEN/00002 AE/GEN/00002/00001 Support Create request targeting one resource TP/oneM2M/AE/DMR/CRE/001 REG AE/REG/00002 AE/REG/00002/00001 Create <AE> with mandatory attributes TP/oneM2M/AE/REG//CRE/001 TP/oneM2M/AE/REG/CRE/002_RR DMR AE/DMR/00001 AE/DMR/00001/00001 Create <container> with no attribute set TP/oneM2M/AE/DMR/CRE/001 AE/DMR/00002 AE/DMR/00002/00001 Create <contentInstance> with mandatory attributes TP/oneM2M/AE/DMR/CRE/002 |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.4.4 Extendable feature sets | Void. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 11 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5 ADN Profile 4 | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.1 Profile description | oneM2M provides several logical entity concepts called 'Node' to explain oneM2M Architecture in ETSI TS 118 101 [i.3]. And from the descriptions about the node types, it indicates some examples that particular node could match with physical oneM2M devices (e.g. ADN -> constraintedconstrained oneM2M Device). But for the oneM2M device developers, more detail information may require to design and implement physical devices. This ADN Profile 4 defines set of common features which could be used for small originator device types of oneM2M services. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.2 Profile usage examples | ADN Profile 1 could be the basic profile of oneM2M devices like sensor, actuator, etc. And also this profile could be used independently when developers want to implement oneM2M devices with special functions. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.3 Fundamental feature sets | Table 5.5.3-1: Feature set for ADN Profile 4 Function Feature Set Feature Remark GEN AE/GEN/00001 At least one Support one of the format of resource identification TP/oneM2M/AE/GEN/CRE/001_CSR TP/oneM2M/AE/GEN/CRE/001_SPR TP/oneM2M/AE/GEN/CRE/001_ABS TP/oneM2M/AE/GEN/CRE/002_CSR TP/oneM2M/AE/GEN/CRE/002_SPR TP/oneM2M/AE/GEN/CRE/002_ABS TP/oneM2M/AE/GEN/UPD/001_CSR TP/oneM2M/AE/GEN/UPD/001_SPR TP/oneM2M/AE/GEN/UPD/001_ABS TP/oneM2M/AE/GEN/UPD/002_CSR TP/oneM2M/AE/GEN/UPD/002_SPR TP/oneM2M/AE/GEN/UPD/002_ABS TP/oneM2M/AE/GEN/RET/001_CSR TP/oneM2M/AE/GEN/RET/001_SPR TP/oneM2M/AE/GEN/RET/001_ABS TP/oneM2M/AE/GEN/RET/002_CSR TP/oneM2M/AE/GEN/RET/002_SPR TP/oneM2M/AE/GEN/RET/002_ABS TP/oneM2M/AE/GEN/DEL/001_CSR TP/oneM2M/AE/GEN/DEL/001_SPR TP/oneM2M/AE/GEN/DEL/001_ABS TP/oneM2M/AE/GEN/DEL/002_CSR TP/oneM2M/AE/GEN/DEL/002_SPR TP/oneM2M/AE/GEN/DEL/002_ABS AE/GEN/00002 AE/GEN/00002/00001 Support Create request targeting one resource TP/oneM2M/AE/DMR/CRE/001 AE/GEN/00002/00002 Support Retrieve request targeting one resource TP/oneM2M/AE/DMR/RET/001_CB TP/oneM2M/AE/DMR/RET/001_AE TP/oneM2M/AE/DMR/RET/001_CNT AE/GEN/00002/00003 Support Update request targeting one resource TP/oneM2M/AE/DMR/UPD/002_LBL AE/GEN/00002/00004 Support Delete request targeting one resource TP/oneM2M/AE/DMR/DEL/003 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 12 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark REG AE/REG/00001 AE/REG/00001/00001 The Retrieval of <CSEBase> resource TP/oneM2M/AE/DMR/RET/001_CB AE/REG/00002 AE/REG/00002/00001 Create <AE> with mandatory attributes TP/oneM2M/AE/REG//CRE/001 TP/oneM2M/AE/REG/CRE/002_RR AE/GEN/00003/00001 Create <AE> with resourceName attribute TP/oneM2M/AE/REG/CRE/002_RN AE/GEN/00003/00002 Create <AE> with expirationTime attribute TP/oneM2M/AE/REG/CRE/002_ET AE/DIS/00001/00017 Create <AE> with labels TP/oneM2M/AE/REG/CRE/002_LBL AE/REG/00002/00002 Create <AE> with applicationName TP/oneM2M/AE/REG/CRE/002_APN AE/REG/00002/00003 Create <AE> with pointOfAccess TP/oneM2M/AE/REG/CRE/002_POA AE/REG/00002/00004 Create <AE> with nodeLink TP/oneM2M/AE/REG/CRE/002_NL AE/REG/00002/00005 Create <AE> with contentSerialization TP/oneM2M/AE/REG/CRE/002_CSZ AE/GEN/00003/00002 Update <AE> with expirationTime TP/oneM2M/AE/DMR/UPD/001_ET AE/DIS/00001/00017 Update <AE> with labels TP/oneM2M/AE/DMR/UPD/001_LBL AE/REG/00002/00007 Update <AE> with applicationName TP/oneM2M/AE/DMR/UPD/001_APN AE/REG/00002/00008 Update <AE> with pointOfAccess TP/oneM2M/AE/DMR/UPD/001_PO A AE/REG/00002/00009 Update <AE> with nodeLink TP/oneM2M/AE/DMR/UPD/001_NL AE/GEN/00002/00005 Update <AE> with requestReachability TP/oneM2M/AE/DMR/UPD/001_RR AE/REG/00002/00010 Update <AE> with contentSerialization TP/oneM2M/AE/DMR/UPD/001_CSZ AE/REG/00002/00013 Delete <AE> TP/oneM2M/AE/REG/DEL/001 AE/REG/00002/00012 Retrieve <AE> TP/oneM2M/AE/DMR/RET/001_AE DMR AE/DMR/00001 AE/DMR/00001/00001 Create <container> with no attribute set TP/oneM2M/AE/DMR/CRE/001 AE/GEN/00003/00001 Create <container> with resourceName TP/oneM2M/AE/DMR/CRE/004_RN AE/GEN/00003/00002 Create <container> with expirationTime TP/oneM2M/AE/DMR/CRE/004_ET AE/DIS/00001/00017 Create <container> with labels TP/oneM2M/AE/DMR/CRE/004_LBL AE/DMR/00001/00002 Create <container> with maxNrOfInstances TP/oneM2M/AE/DMR/CRE/004_MNI AE/DMR/00001/00003 Create <container> with maxByteSize TP/oneM2M/AE/DMR/CRE/004_MB S AE/DMR/00001/00004 Create <container> with maxInstanceAge TP/oneM2M/AE/DMR/CRE/004_MIA AE/GEN/00003/00002 Update <container> with expirationTime TP/oneM2M/AE/DMR/UPD/002_ET AE/DIS/00001/00017 Update <container> with labels TP/oneM2M/AE/DMR/UPD/002_LBL AE/DMR/00001/00006 Update <container> with maxNrOfInstances TP/oneM2M/AE/DMR/UPD/002_MNI AE/DMR/00001/00007 Update <container> with maxByteSize TP/oneM2M/AE/DMR/UPD/002_MB S AE/DMR/00001/00008 Update <container> with maxInstanceAge TP/oneM2M/AE/DMR/UPD/002_MIA AE/DMR/00001/00011 Delete <container> TP/oneM2M/AE/DMR/DEL/003 AE/DMR/00001/00012 Retrieve <container> TP/oneM2M/AE/DMR/RET/004 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 13 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark AE/DMR/00002 AE/DMR/00002/00001 Create <contentInstance> with mandatory attributes TP/oneM2M/AE/DMR/CRE/002 AE/GEN/00003/00001 Create <contentInstance> with resourceName TP/oneM2M/AE/DMR/CRE/003_RN AE/GEN/00003/00002 Create <contentInstance> with expirationTime TP/oneM2M/AE/DMR/CRE/003_ET AE/DIS/00001/00017 Create <contentInstance> with labels TP/oneM2M/AE/DMR/CRE/003_LBL AE/DMR/00002/00002 Create <contentInstance> with contentInfo TP/oneM2M/AE/DMR/CRE/003_CNF AE/DMR/00002/00003 Create <contentInstance> with contentRef TP/oneM2M/AE/DMR/CRE/003_CO NR AE/DMR/00002/00004 Retrieve <contentInstance> resource targeting the <contentInstance> resource TP/oneM2M/AE/DMR/RET/005 AE/DMR/00002/00005 Retrieve oldest <contentInstance> resource targeting the <oldest> resource TP/oneM2M/AE/DMR/RET/002 AE/DMR/00002/00006 Retrieve latest <contentInstance> resource targeting the <latest> resource TP/oneM2M/AE/DMR/RET/003 AE/DMR/00002/00007 Delete <contentInstance> TP/oneM2M/AE/DMR/DEL/004 AE/DMR/00002/00008 Delete oldest <contentInstance> resource targeting the <oldest> resource TP/oneM2M/AE/DMR/DEL/001 AE/DMR/00002/00009 Delete latest <contentInstance> resource targeting the <latest> resource TP/oneM2M/AE/DMR/DEL/002 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 14 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.5.4 Extendable feature sets | Table 5.5.4-1 Funct ion Feature Set Feature Remark REG AE/REG/00002 AE/REG/00002/00001 Create <AE> with App-ID attribute TP/oneM2M/AE/REG/CRE/002_API VOID Create <AE> with ontologyRef attribute TP/oneM2M/AE/REG/CRE/002_OR VOID Update <AE> with ontologyRef attribute TP/oneM2M/AE/DMR/UPD/001_OR DMR AE/DMR/00001 AE/SEC/00001/00007 Create <container> with acpi TP/oneM2M/AE/DMR/CRE/004_ACPI VOID Create <container> with ontologyRef TP/oneM2M/AE/DMR/CRE/004_OR VOID Create <container> with locationID TP/oneM2M/AE/DMR/CRE/004_LI SUB AE/SUB/00001 AE/SUB/00001/00002 Create <subscription> with labels TP/oneM2M/AE/SUB/CRE/002_LBL AE/SUB/00001/00005 Create <subscription> with subscriberURI TP/oneM2M/AE/SUB/CRE/002_SU AE/SEC/00001/00007 Create <subscription> with acpi TP/oneM2M/AE/SUB/CRE/002_ACPI AE/SUB/00002/00001 Create <subscription> with eventNotificationCriteria TP/oneM2M/AE/SUB/CRE/002_ENC AE/SUB/00002/00002 Create <subscription> with expirationCounter TP/oneM2M/AE/SUB/CRE/002_EXC AE/SUB/00003/00001 Create <subscription> with notificationForwardingURI TP/oneM2M/AE/SUB/CRE/002_NFU AE/SUB/00002/00009 Create <subscription> with notificationContentType TP/oneM2M/AE/SUB/CRE/002_NCT AE/SUB/00002/00010 Create <subscription> with notificationEventCat TP/oneM2M/AE/SUB/CRE/002_NEC VOID Support NOTIFY Request TP/oneM2M/AE/SUB/NTF/001 TP/oneM2M/AE/SUB/NTF/002 |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6 IN Profile | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.1 Profile description | oneM2M provides several logical entity concepts called 'Node' to explain oneM2M Architecture in ETSI TS 118 101 [i.3] . And from the descriptions about the node types, it indicates some examples that particular node could match with physical oneM2M devices (e.g. ADN -> constraintedconstrained oneM2M Device). But for the oneM2M device developers, more detail information may require to design and implement physical devices. This IN Profile defines set of common features which could be used for server device type of oneM2M services. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.2 Profile usage examples | IN Profile 1 could be the common profile of oneM2M devices like service server, etc. and also this profile could be used independently when developers want to implement oneM2M devices with special functions. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 15 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.3 Fundamental feature sets | Table 5.6.3-1: Fundamental feature set for IN Profile Function Feature Set Feature Remark GEN CE/GEN/00001 CE/GEN/00001/00001 Support Unstructured resource identifier TP/oneM2M/CSE/GEN/CRE/001_CSR TP/oneM2M/CSE/GEN/CRE/001_SPR TP/oneM2M/CSE/GEN/CRE/001_ABS TP/oneM2M/CSE/GEN/UPD/001_CSR TP/oneM2M/CSE/GEN/UPD/001_SPR TP/oneM2M/CSE/GEN/UPD/001_ABS TP/oneM2M/CSE/GEN/RET/001_CSR TP/oneM2M/CSE/GEN/RET/001_SPR TP/oneM2M/CSE/GEN/RET/001_ABS TP/oneM2M/CSE/GEN/DEL/001_CSR TP/oneM2M/CSE/GEN/DEL/001_SPR TP/oneM2M/CSE/GEN/DEL/001_ABS CE/GEN/00001/00002 Support Structured resource identifier TP/oneM2M/CSE/GEN/CRE/002_CSR TP/oneM2M/CSE/GEN/CRE/002_SPR TP/oneM2M/CSE/GEN/CRE/002_ABS TP/oneM2M/CSE/GEN/UPD/002_CSR TP/oneM2M/CSE/GEN/UPD/002_SPR TP/oneM2M/CSE/GEN/UPD/002_ABS TP/oneM2M/CSE/GEN/RET/002_CSR TP/oneM2M/CSE/GEN/RET/002_SPR TP/oneM2M/CSE/GEN/RET/002_ABS TP/oneM2M/CSE/GEN/DEL/002_CSR TP/oneM2M/CSE/GEN/DEL/002_SPR TP/oneM2M/CSE/GEN/DEL/002_ABS GEN CE/GEN/00002 CE/GEN/00002/00001 Support blocking request REG CE/REG/00001 CE/REG/00001/00001 Support <CSEBase> resource. TP/oneM2M/CSE/REG/CRE/021 TP/oneM2M/CSE/REG/RET/001 TP/oneM2M/CSE/REG/RET/008 TP/oneM2M/CSE/REG/UPD/001 TP/oneM2M/CSE/REG/DEL/001 CE/REG/00001/00002 Support the cseType attribute of <CSEBase> TP/oneM2M/CSE/REG/RET/002_CST TP/oneM2M/CSE/REG/RET/005 CE/REG/00001/00003 Support the nodeLink attribute of <CSEBase> TP/oneM2M/CSE/REG/RET/002_NL CE/REG/00002 CE/REG/00002/00001 Support <AE> resource TP/oneM2M/CSE/REG/RET/003 TP/oneM2M/CSE/REG/DEL/003 TP/oneM2M/CSE/DMR/RET/013_AE TP/oneM2M/CSE/DMR/UPD/016_AE/ET TP/oneM2M/CSE/DMR/UPD/016_AE/R R CE/REG/00002/00002 AE registration/de- registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'C'. TP/oneM2M/CSE/REG/CRE/004 TP/oneM2M/CSE/REG/CRE/009 TP/oneM2M/CSE/REG/CRE/011 TP/oneM2M/CSE/REG/CRE/016 TP/oneM2M/CSE/REG/CRE/017_API TP/oneM2M/CSE/REG/CRE/017_RR TP/oneM2M/CSE/REG/CRE/022 TP/oneM2M/CSE/REG/CRE/023 CE/REG/00002/00003 AE registration/de- registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S'. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 16 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/REG/00002/00004 AE registration/de- registration without a pre-assigned AE-ID in the registration request and where no AE-ID Stem is included. CE/REG/00002/00005 AE registration/de- registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S' and where announcement to an IN-CSE is needed to get an AE-ID assigned CE/DIS/00001/00006 Support the labels attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/LB L TP/oneM2M/CSE/REG/RET/004_LBL TP/oneM2M/CSE/DMR/UPD/015_AE/LB L CE/REG/00002/00007 Support the applicationName attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/AP N TP/oneM2M/CSE/REG/RET/004_APN TP/oneM2M/CSE/DMR/UPD/015_AE/A PN CE/REG/00002/00008 Support the pointOfAccess attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/P OA TP/oneM2M/CSE/REG/RET/004_POA TP/oneM2M/CSE/DMR/UPD/015_AE/P OA CE/REG/00002/00009 AE registration with pre-assigned AE-ID TP/oneM2M/CSE/REG/CRE/001 TP/oneM2M/CSE/REG/CRE/002 CE/REG/00004 CE/REG/00004/00001 Support <remoteCSE> resource with attributes multiplicity equals 1 TP/oneM2M/CSE/REG/CRE/018 TP/oneM2M/CSE/REG/CRE/019 TP/oneM2M/CSE/REG/CRE/025 TP/oneM2M/CSE/REG/RET/006 TP/oneM2M/CSE/REG/RET/010 TP/oneM2M/CSE/REG/DEL/002 TP/oneM2M/CSE/DMR/UPD/016_CSR/ ET TP/oneM2M/CSE/DMR/UPD/016_CSR/ RR CE/DIS/00001/00006 Support the labels attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_LBL TP/oneM2M/CSE/REG/CRE/028_LBL TP/oneM2M/CSE/REG/RET/007_LBL TP/oneM2M/CSE/REG/UPD/002_LBL CE/REG/00004/00002 Support the cseType attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_CST TP/oneM2M/CSE/REG/RET/007_CST CE/REG/00004/00003 Support the pointOfAccess attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_POA TP/oneM2M/CSE/REG/CRE/028_POA TP/oneM2M/CSE/REG/RET/007_POA TP/oneM2M/CSE/REG/UPD/002_POA CE/REG/00004/00004 Support the nodeLink attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_NL TP/oneM2M/CSE/REG/CRE/028_NL TP/oneM2M/CSE/REG/RET/007_NL TP/oneM2M/CSE/REG/UPD/002_NL DMR CE/DMR/00001 CE/DMR/00001/00001 Support <container> resource with attributes multiplicity equals 1 TP/oneM2M/CSE/DMR/CRE/001_CNT/ CB TP/oneM2M/CSE/DMR/CRE/001_CNT/ AE ETSI ETSI TS 118 125 V2.0.0 (2020-03) 17 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/DMR/CRE/001_CNT/ CNT TP/oneM2M/CSE/DMR/CRE/002_CNT TP/oneM2M/CSE/DMR/CRE/003_CNT TP/oneM2M/CSE/DMR/CRE/007 TP/oneM2M/CSE/DMR/CRE/008 TP/oneM2M/CSE/DMR/CRE/009 TP/oneM2M/CSE/DMR/CRE/010 TP/oneM2M/CSE/DMR/CRE/011 TP/oneM2M/CSE/DMR/CRE/014_CNT_ CIN TP/oneM2M/CSE/DMR/RET/001_CNT TP/oneM2M/CSE/DMR/RET/013_CNT TP/oneM2M/CSE/DMR/UPD/001_CNT/L BL TP/oneM2M/CSE/DMR/UPD/002_CNT/L BL TP/oneM2M/CSE/DMR/UPD/003_CNT/L BL TP/oneM2M/CSE/DMR/UPD/004_CNT/ ET/MNI/LBL TP/oneM2M/CSE/DMR/UPD/005_CNT/ EXC TP/oneM2M/CSE/DMR/UPD/007_CNT/ CT TP/oneM2M/CSE/DMR/UPD/008_CNT/ ET TP/oneM2M/CSE/DMR/UPD/009_CNT/L BL TP/oneM2M/CSE/DMR/UPD/010 TP/oneM2M/CSE/DMR/UPD/016_CNT/ ET TP/oneM2M/CSE/DMR/DEL/001_CNT TP/oneM2M/CSE/DMR/DEL/005 TP/oneM2M/CSE/DMR/DEL/006 CE/DIS/00001/00006 Support the labels attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/012_CNT/L BL TP/oneM2M/CSE/DMR/UPD/014_CNT/L BL TP/oneM2M/CSE/DMR/UPD/015_CNT/L BL CE/DMR/00002/00001 Support the creator attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/012_CNT/ CR CE/DMR/00001/00002 Support the maxNrOfInstances attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MNI TP/oneM2M/CSE/DMR/CRE/006_MNI TP/oneM2M/CSE/DMR/CRE/012_CNT/ MNI TP/oneM2M/CSE/DMR/UPD/014_CNT/ MNI TP/oneM2M/CSE/DMR/UPD/015_CNT/ MNI CE/DMR/00001/00003 Support the maxByteSize attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MBS TP/oneM2M/CSE/DMR/CRE/006_MBS TP/oneM2M/CSE/DMR/CRE/012_CNT/ MBS TP/oneM2M/CSE/DMR/CRE/013 TP/oneM2M/CSE/DMR/UPD/014_CNT/ MBS TP/oneM2M/CSE/DMR/UPD/015_CNT/ MBS CE/DMR/00001/00004 Support the maxInstanceAge attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MIA TP/oneM2M/CSE/DMR/CRE/006_MIA TP/oneM2M/CSE/DMR/CRE/012_CNT/ MIA TP/oneM2M/CSE/DMR/UPD/014_CNT/ MIA ETSI ETSI TS 118 125 V2.0.0 (2020-03) 18 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/DMR/UPD/015_CNT/ MIA CE/DMR/00002 CE/DMR/00002/00001 Support <contentInstance> resource with attributes multiplicity equals 1 TP/oneM2M/CSE/DMR/CRE/001_CIN/C NT TP/oneM2M/CSE/DMR/RET/001_CIN TP/oneM2M/CSE/DMR/UPD/011 TP/oneM2M/CSE/DMR/DEL/001_CIN CE/DIS/00001/00006 Support the labels attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/012_CIN/L BL CE/DMR/00002/00001 Support the creator attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/012_CIN/C R CE/DMR/00002/00002 Support the contentInfo attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/012_CIN/C NF CE/DMR/00002/00004 Retrieve and Delete of latest <contentInstance> resource by <latest> virtual resource TP/oneM2M/CSE/DMR/RET/012 TP/oneM2M/CSE/DMR/UPD/012 TP/oneM2M/CSE/DMR/DEL/007 CE/DMR/00002/00057 Retrieve and Delete of oldest <contentInstance> resource by <oldest> virtual resource TP/oneM2M/CSE/DMR/RET/010 TP/oneM2M/CSE/DMR/UPD/013 TP/oneM2M/CSE/DMR/DEL/009 SUB CE/SUB/00001 CE/SUB/00001/00001 The Support of <subscription> resource with attributes multiplicity equals 1 TP/oneM2M/CSE/DMR/CRE/001_SUB/ CB TP/oneM2M/CSE/DMR/CRE/001_SUB/ AE TP/oneM2M/CSE/DMR/CRE/001_SUB/ CNT TP/oneM2M/CSE/DMR/CRE/001_SUB/ ACP TP/oneM2M/CSE/DMR/CRE/001_SUB/ CSR TP/oneM2M/CSE/DMR/CRE/001_SUB/ GRP TP/oneM2M/CSE/DMR/CRE/002_SUB TP/oneM2M/CSE/DMR/CRE/003_SUB TP/oneM2M/CSE/DMR/RET/001_SUB TP/oneM2M/CSE/DMR/RET/013_SUB TP/oneM2M/CSE/DMR/UPD/001_SUB/L BL TP/oneM2M/CSE/DMR/UPD/002_SUB/L BL TP/oneM2M/CSE/DMR/UPD/003_SUB/L BL TP/oneM2M/CSE/DMR/UPD/004_SUB/ ET/LBL/EXC TP/oneM2M/CSE/DMR/UPD/005_SUB/ MNI TP/oneM2M/CSE/DMR/UPD/007_SUB/ CT TP/oneM2M/CSE/DMR/UPD/008_SUB/ ET TP/oneM2M/CSE/DMR/UPD/009_SUB/L BL TP/oneM2M/CSE/DMR/UPD/016_SUB/ ET TP/oneM2M/CSE/DMR/UPD/016_SUB/ NU TP/oneM2M/CSE/DMR/UPD/016_SUB/ NCT ETSI ETSI TS 118 125 V2.0.0 (2020-03) 19 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/DMR/DEL/001_SUB CE/DIS/00001/00006 Support the labels attribute of <subscription> resource. TP/oneM2M/CSE/DMR/CRE/012_SUB/L BL TP/oneM2M/CSE/DMR/UPD/014_SUB/L BL TP/oneM2M/CSE/DMR/UPD/015_SUB/L BL CE/SUB/00001/00001 Support the creator attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/012_SUB/ CR CE/SUB/00001/00001 Support the subscriberURI attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/012_SUB/ SU CE/SUB/00004 CE/SUB/00004/00001 Notify the address indicated in notificationURI with notification elements multiplicity equals 1 TP/oneM2M/CSE/SUB/CRE/001_SUB TP/oneM2M/CSE/SUB/CRE/001_CIN TP/oneM2M/CSE/SUB/CRE/003 TP/oneM2M/CSE/SUB/CRE/005 CE/SUB/00004/00002 Notify with notificationEvent/repr esentation set in the notification TP/oneM2M/CSE/SUB/CRE/005 TP/oneM2M/CSE/SUB/UPD/001 TP/oneM2M/CSE/SUB/DEL/001 CE/SUB/00004/00003 Notify with creator set in the notification TP/oneM2M/CSE/SUB/CRE/004 SEC CE/SEC/00001 CE/SEC/00001/00001 Support <accessControlPolic y> resource with attributes multiplicity equals 1 TP/oneM2M/CSE/DMR/CRE/001_ACP/ CB TP/oneM2M/CSE/DMR/CRE/001_ACP/ AE TP/oneM2M/CSE/DMR/CRE/001_ACP/ AEA TP/oneM2M/CSE/DMR/CRE/002_ACP TP/oneM2M/CSE/DMR/CRE/003_ACP TP/oneM2M/CSE/DMR/RET/001_ACP TP/oneM2M/CSE/DMR/RET/013_ACP TP/oneM2M/CSE/DMR/UPD/001_ACP/L BL TP/oneM2M/CSE/DMR/UPD/002_ACP/L BL TP/oneM2M/CSE/DMR/UPD/003_ACP/L BL TP/oneM2M/CSE/DMR/UPD/004_ACP/ PV/AT/LBL TP/oneM2M/CSE/DMR/UPD/005_ACP/ EXC TP/oneM2M/CSE/DMR/UPD/007_ACP/ CT TP/oneM2M/CSE/DMR/UPD/008_ACP/ ET TP/oneM2M/CSE/DMR/UPD/009_ACP/L BL TP/oneM2M/CSE/DMR/UPD/016_ACP/ ET TP/oneM2M/CSE/DMR/UPD/016_ACP/ PV TP/oneM2M/CSE/DMR/UPD/016_ACP/ PVS TP/oneM2M/CSE/DMR/DEL/001_ACP TP/oneM2M/CSE/SEC/ACP/CRE/001 TP/oneM2M/CSE/SEC/ACP/CRE/002 TP/oneM2M/CSE/SEC/ACP/CRE/003 TP/oneM2M/CSE/SEC/ACP/CRE/004 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 20 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/DIS/00001/00006 Support the labels attribute of <accessControlPolic y> resource TP/oneM2M/CSE/DMR/CRE/012_ACP/L BL TP/oneM2M/CSE/DMR/UPD/014_ACP/L BL TP/oneM2M/CSE/DMR/UPD/015_ACP/L BL CE/SEC/00002 CE/SEC/00002/00001 Support accessControlPolicyI Ds attribute for <resource> that the Implementation supports. TP/oneM2M/CSE/DMR/CRE/012_SUB/ ACPI TP/oneM2M/CSE/DMR/CRE/012_CNT/ ACPI TP/oneM2M/CSE/DMR/UPD/014_CNT/ ACPI TP/oneM2M/CSE/DMR/UPD/015_AE/A CPI TP/oneM2M/CSE/DMR/UPD/015_CNT/ ACPI TP/oneM2M/CSE/DMR/UPD/015_SUB/ ACPI TP/oneM2M/CSE/DMR/UPD/015_GRP/ ACPI TP/oneM2M/CSE/SEC/ACP/UPD/001 TP/oneM2M/CSE/SEC/ACP/UPD/002 CE/SEC/00002/00002 Support access control decision and enforcement making on the Hosting CSE TP/oneM2M/CSE/DMR/CRE/004_CNT TP/oneM2M/CSE/DMR/CRE/004_ACP TP/oneM2M/CSE/DMR/CRE/004_SUB TP/oneM2M/CSE/DMR/CRE/004_GRP TP/oneM2M/CSE/DMR/RET/003_ACP TP/oneM2M/CSE/DMR/RET/003_CNT TP/oneM2M/CSE/DMR/RET/003_SUB TP/oneM2M/CSE/DMR/RET/014_ACP TP/oneM2M/CSE/DMR/RET/014_AE TP/oneM2M/CSE/DMR/RET/014_CNT TP/oneM2M/CSE/DMR/RET/014_CSR TP/oneM2M/CSE/DMR/RET/014_SUB TP/oneM2M/CSE/DMR/RET/014_GRP TP/oneM2M/CSE/DMR/UPD/006_CNT/L BL TP/oneM2M/CSE/DMR/UPD/006_ACP/L BL TP/oneM2M/CSE/DMR/UPD/006_SUB/L BL TP/oneM2M/CSE/DMR/DEL/002_CNT TP/oneM2M/CSE/DMR/DEL/002_ACP TP/oneM2M/CSE/DMR/DEL/002_SUB TP/oneM2M/CSE/DMR/DEL/002_GRP TP/oneM2M/CSE/SUB/CRE/002 TP/oneM2M/CSE/SEC/ACP/001_CRE TP/oneM2M/CSE/SEC/ACP/001_UPD TP/oneM2M/CSE/SEC/ACP/001_RET TP/oneM2M/CSE/SEC/ACP/001_DEL TP/oneM2M/CSE/SEC/ACP/002_CRE TP/oneM2M/CSE/SEC/ACP/002_UPD TP/oneM2M/CSE/SEC/ACP/002_RET TP/oneM2M/CSE/SEC/ACP/002_DEL TP/oneM2M/CSE/SEC/ACP/003_CRE TP/oneM2M/CSE/SEC/ACP/003_UPD TP/oneM2M/CSE/SEC/ACP/003_RET TP/oneM2M/CSE/SEC/ACP/003_DEL TP/oneM2M/CSE/SEC/ACP/004_CRE TP/oneM2M/CSE/SEC/ACP/004_UPD TP/oneM2M/CSE/SEC/ACP/004_RET TP/oneM2M/CSE/SEC/ACP/004_DEL TP/oneM2M/CSE/SEC/ACP/005_CRE TP/oneM2M/CSE/SEC/ACP/005_UPD TP/oneM2M/CSE/SEC/ACP/005_RET TP/oneM2M/CSE/SEC/ACP/005_DEL ETSI ETSI TS 118 125 V2.0.0 (2020-03) 21 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/SEC/ACP/006_CRE TP/oneM2M/CSE/SEC/ACP/006_UPD TP/oneM2M/CSE/SEC/ACP/006_RET TP/oneM2M/CSE/SEC/ACP/006_DEL TP/oneM2M/CSE/SEC/ACP/007_CRE TP/oneM2M/CSE/SEC/ACP/007_UPD TP/oneM2M/CSE/SEC/ACP/007_RET TP/oneM2M/CSE/SEC/ACP/007_DEL TP/oneM2M/CSE/SEC/ACP/008_CRE TP/oneM2M/CSE/SEC/ACP/008_UPD TP/oneM2M/CSE/SEC/ACP/008_RET TP/oneM2M/CSE/SEC/ACP/008_DEL TP/oneM2M/CSE/SEC/ACP/009_CRE TP/oneM2M/CSE/SEC/ACP/009_UPD TP/oneM2M/CSE/SEC/ACP/009_RET TP/oneM2M/CSE/SEC/ACP/009_DEL TP/oneM2M/CSE/SEC/ACP/010_CRE TP/oneM2M/CSE/SEC/ACP/010_UPD TP/oneM2M/CSE/SEC/ACP/010_RET TP/oneM2M/CSE/SEC/ACP/010_DEL TP/oneM2M/CSE/SEC/ACP/011_CRE TP/oneM2M/CSE/SEC/ACP/011_UPD TP/oneM2M/CSE/SEC/ACP/011_RET TP/oneM2M/CSE/SEC/ACP/011_DEL TP/oneM2M/CSE/SEC/ACP/012_CRE TP/oneM2M/CSE/SEC/ACP/012_UPD TP/oneM2M/CSE/SEC/ACP/012_RET TP/oneM2M/CSE/SEC/ACP/012_DEL |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.6.4 Extendable feature sets | Table 5.6.4-1: Extendable feature set for IN Profile Function Feature Set Feature Remark DIS CE/DIS/00001 CE/DIS/00001/00001 Support the Discovery request with filterUsage equals to "Discovery" TP/oneM2M/CSE/DIS/001 TP/oneM2M/CSE/DIS/002 TP/oneM2M/CSE/DIS/003 TP/oneM2M/CSE/DIS/004 TP/oneM2M/CSE/DIS/005 TP/oneM2M/CSE/DIS/006 CE/DIS/00001/00002 Support discovery with filterCriteria (createdBefore, createdAfter, modifiedSince, unmodifiedSince, stateTagSmaller, stateTagBigger, expireBefore, expireAfter, labels, resourceType, sizeAbove, sizeBelow, contentType, limit, attribute) TP/oneM2M/CSE/DIS/007 TP/oneM2M/CSE/DIS/008 TP/oneM2M/CSE/DIS/009 CE/DIS/00001/00003 Support discovery with filterCriteria (level, offset) CE/DIS/00001/00004 Support discovery with content filter (contentFilterSyntax, contentFilterQuery of filterCriteria) CE/DIS/00001/00005 Support discovery with filterCriteria (filterOperation) GMG CE/GMG/00001 CE/GMG/00001/00001 Support the <group> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_GRP/CB TP/oneM2M/CSE/DMR/CRE/001_GRP/AE TP/oneM2M/CSE/DMR/CRE/002_GRP TP/oneM2M/CSE/DMR/CRE/003_GRP TP/oneM2M/CSE/DMR/RET/001_GRP TP/oneM2M/CSE/DMR/RET/013_GRP ETSI ETSI TS 118 125 V2.0.0 (2020-03) 22 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/DMR/UPD/001_GRP/LBL TP/oneM2M/CSE/DMR/UPD/002_GRP/LBL TP/oneM2M/CSE/DMR/UPD/003_GRP/LBL TP/oneM2M/CSE/DMR/UPD/004_GRP/ET/G N/LBL TP/oneM2M/CSE/DMR/UPD/005_GRP/EXC TP/oneM2M/CSE/DMR/UPD/006_GRP/LBL TP/oneM2M/CSE/DMR/UPD/007_GRP/CT TP/oneM2M/CSE/DMR/UPD/008_GRP/ET TP/oneM2M/CSE/DMR/UPD/009_GRP/LBL TP/oneM2M/CSE/DMR/UPD/016_GRP/ET TP/oneM2M/CSE/DMR/UPD/016_GRP/MNM TP/oneM2M/CSE/DMR/UPD/016_GRP/MID TP/oneM2M/CSE/DMR/DEL/001_GRP TP/oneM2M/CSE/DMR/DEL/002_GRP TP/oneM2M/CSE/GMG/CRE/001 TP/oneM2M/CSE/GMG/CRE/003 TP/oneM2M/CSE/GMG/UPD/002 TP/oneM2M/CSE/GMG/UPD/007 TP/oneM2M/CSE/GMG/UPD/008 CE/DIS/00001/00006 Support the labels attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/LBL CE/GMG/00001/00001 Support the creator attribute of <group> resource CE/GMG/00001/00001 Support the groupName attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/GN CE/GMG/00002 CE/GMG/00002/00001 Support the memberTypeValidated attribute of <group> resource CE/GMG/00002/00002 Support the validation of member's resource type and set the memberTypeValidated as well as the procedure to update the group according to consistencyStrategy TP/oneM2M/CSE/GMG/CRE/002 TP/oneM2M/CSE/GMG/CRE/004 TP/oneM2M/CSE/GMG/CRE/005 TP/oneM2M/CSE/GMG/CRE/006 TP/oneM2M/CSE/GMG/CRE/007 TP/oneM2M/CSE/GMG/UPD/001 TP/oneM2M/CSE/GMG/UPD/003 TP/oneM2M/CSE/GMG/UPD/004 TP/oneM2M/CSE/GMG/UPD/005 TP/oneM2M/CSE/GMG/UPD/006 TP/oneM2M/CSE/GMG/UPD/009 TP/oneM2M/CSE/GMG/UPD/010 CE/GMG/00002/00003 Support the consistencyStrategy attribute of <group> resource CE/GMG/00003 CE/GMG/00003/00001 Fan out of request to all members and aggregate member responses TP/oneM2M/CSE/GMG/RET/001 TP/oneM2M/CSE/GMG/001_CRE TP/oneM2M/CSE/GMG/001_RET TP/oneM2M/CSE/GMG/001_UPD TP/oneM2M/CSE/GMG/001_DEL TP/oneM2M/CSE/GMG/002_CRE TP/oneM2M/CSE/GMG/002_RET TP/oneM2M/CSE/GMG/002_UPD TP/oneM2M/CSE/GMG/002_DEL TP/oneM2M/CSE/GMG/003_CRE TP/oneM2M/CSE/GMG/003_RET TP/oneM2M/CSE/GMG/003_UPD TP/oneM2M/CSE/GMG/003_DEL TP/oneM2M/CSE/GMG/004_CRE TP/oneM2M/CSE/GMG/004_RET TP/oneM2M/CSE/GMG/004_UPD TP/oneM2M/CSE/GMG/004_DEL TP/oneM2M/CSE/GMG/005_CRE TP/oneM2M/CSE/GMG/005_RET TP/oneM2M/CSE/GMG/005_UPD ETSI ETSI TS 118 125 V2.0.0 (2020-03) 23 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/GMG/005_DEL TP/oneM2M/CSE/GMG/006_CRE TP/oneM2M/CSE/GMG/006_RET TP/oneM2M/CSE/GMG/006_UPD TP/oneM2M/CSE/GMG/006_DEL CE/GMG/00003/00002 Create sub group resource in case multiple members belong to same member CSE CE/GMG/00003/00003 Create <subscription> resource via group without aggregating notifications CE/GMG/00003/00004 Create <subscription> resource via group and aggregate notifications CE/GMG/00003/00005 Support the membersAccessControlPoli cyIDs attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/MAC P DMG CE/DMG/00001 CE/DMG/00001/00001 Support <node> resource with attributes multiplicity equals 1[1] CE/DMG/00001/00002 Support the labels attribute of <node> resource CE/DMG/00001/00003 Support the hostedCSELink attribute of <node> resource CE/DMG/00002 CE/DMG/00002/00001 Support <mgmtObj> resource with attributes multiplicity equals 1[1] CE/DMG/00002/00002 Support the labels attribute of <mgmtObj> resource CE/DMG/00002/00003 Support the description attribute of <mgmtObj> resource CE/DMG/00002/00004 Support the mgmtLink attribute of <mgmtObj> resource CE/DMG/00003 CE/DMG/00003/00001 Support the [software] specialization attributes multiplicity equals 1[1] CE/DMG/00003/00002 Support the activate attribute of [software] resource CE/DMG/00003/00003 Support the deactivate attribute of [software] resource CE/DMG/00003/00004 Support the activeStatus attribute of [software] resource CE/DMG/00004 CE/DMG/00004/00001 Support the [firmware] specialization attributes multiplicity equals 1[1] CE/DMG/00005 CE/DMG/00005/00001 Support the [deviceInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00006 CE/DMG/00006/00001 Support [deviceCapability] specialization attributes multiplicity equals 1[1] CE/DMG/00006/00002 Support the enable attribute of [deviceCapability] resource CE/DMG/00006/00003 Support the disable attribute of [deviceCapability] resource ETSI ETSI TS 118 125 V2.0.0 (2020-03) 24 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/DMG/00007 CE/DMG/00007/00001 Support [reboot] specialization attributes multiplicity equals 1[1] CE/DMG/00008 CE/DMG/00008/00001 Support [memory] specialization attributes multiplicity equals 1[1] CE/DMG/00009 CE/DMG/00009/00001 Support the [battery] specialization attributes multiplicity equals 1[1] CE/DMG/00010 CE/DMG/00010/00001 Support [eventLog] specialization attributes multiplicity equals 1[1] CE/DMG/00011 CE/DMG/00011/00001 Support [areaNwkInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00012 CE/DMG/00012/00001 Support [areaNwkDeviceInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00012/00002 Support the sleepInterval attribute of [areaNwkDeviceInfo] resource CE/DMG/00012/00003 Support the sleepDuration attribute of [areaNwkDeviceInfo] resource CE/DMG/00012/00004 Support the status attribute of [areaNwkDeviceInfo] resource CE/DMG/00013 CE/DMG/00013/00001 Support the objectIDs attribute of <mgmtObj> resource CE/DMG/00013/00002 Support the objectPaths attribute of <mgmtObj> resource CE/DMG/00013/00003 Support the mgmtLink attribute of <mgmtObj> resource |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7 Constrained actuator as ASN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.1 Profile description | The profile defines constraint actuator that is powered by battery and intended to be used for years after deployment without any human interference for maintenance. Therefore, the function of constraint actuator needs to be very limited. An actuator is intended to to receive control command from CSE via notification or other means. The actuator then actuates according to the control command. The actuator needs to receive control command. As a result, the actuator needs to be request reachable to receive notification or be able to start a polling channel. The features described in this profile are features of CSE as the ASN exposes Mcc reference point outside. There are internal AEs of the ASN to synchronize the actual device state with the resource hosted by the ASN-CSE. However, in this profile, the ASN-AE is not sending information to the other CSE's, it's not necessary to include the oneM2M defined AE Features in this profile. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.2 Profile usage examples | Switches deployed along the street light to switch on or off the street light remotely. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 25 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.3 Fundamental feature sets | The fundamental feature set assumes that the resource id of the <container> resource needed for create <contentInstance> is pre-configured at the ASN-CSE and provisioned to the AEs that tends to send requests to the ASN-CSE. Table 5.7.3-1: Fundamental feature sets for constrained sensor as ASN Function Feature Set Feature Remark GEN CE/GEN/00001 CE/GEN/00001/00001 Unstructured resource id CE/GEN/00001/00002 Structured resource id CE/GEN/00002 CE/GEN/00002/00001 Support blocking request REG CE/REG/00005 CE/REG/00005/00001 The Creation with <remoteCSE> resource for CSE registration with mandatory attributes[2] TP/oneM2M/CSE/REG/CRE/024 CE/REG/00005/00006 Create the <remoteCSE> with pointOfAccess TP/oneM2M/CSE/REG/CRE/026_POA DMR CE/DMR/00002 CE/DMR/00002/00001 Support <contentInstance> resource with attributes multiplicity equals 1[1] |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.7.4 Extendable feature sets | Void. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8 Gateway as MN | |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.1 Profile description | The profile defines gateways that may support multiple different area network technologies and connect devices from the corresponding area networks. The devices may be oneM2M defined ADNs, ASNs or NoDNs which are not defined by oneM2M. The gateway hosts resources to enforce common services that devices in the area network may utilize the enable local services without the dependency of the platform and the wide area network. |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.2 Profile usage examples | Home gateways deployed in the home for smart home: • Sensors, actuators and home appliances are connected with the home gateway. Applications can be connected through the platform to access the smart home service as well as applications can be directly connected with the gateway to do the same thing. Head unit in connected vehicles: • Sensors and actuators in the car are connected with the head unit. The sensed data and control command are reported to be delivered through the head unit. Applications may access the head unit and monitor the car state via the platform. Applications may also access the head unit once connected directly with the head unit via area network such as Wifi or Bluetooth. ETSI ETSI TS 118 125 V2.0.0 (2020-03) 26 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.3 Fundamental feature sets | Table 5.8.3-1: Fundamental feature sets for gateway as MN Function Feature Set Feature Remark GEN CE/GEN/00001 CE/GEN/00001/00001 Unstructured resource id TP/oneM2M/CSE/GEN/CRE/001_CSR TP/oneM2M/CSE/GEN/CRE/001_SPR TP/oneM2M/CSE/GEN/CRE/001_ABS TP/oneM2M/CSE/GEN/UPD/001_CSR TP/oneM2M/CSE/GEN/UPD/001_SPR TP/oneM2M/CSE/GEN/UPD/001_ABS TP/oneM2M/CSE/GEN/RET/001_CSR TP/oneM2M/CSE/GEN/RET/001_SPR TP/oneM2M/CSE/GEN/RET/001_ABS TP/oneM2M/CSE/GEN/DEL/001_CSR TP/oneM2M/CSE/GEN/DEL/001_SPR TP/oneM2M/CSE/GEN/DEL/001_ABS CE/GEN/00001/00002 Structured resource id TP/oneM2M/CSE/GEN/CRE/002_CSR TP/oneM2M/CSE/GEN/CRE/002_SPR TP/oneM2M/CSE/GEN/CRE/002_ABS TP/oneM2M/CSE/GEN/UPD/002_CSR TP/oneM2M/CSE/GEN/UPD/002_SPR TP/oneM2M/CSE/GEN/UPD/002_ABS TP/oneM2M/CSE/GEN/RET/002_CSR TP/oneM2M/CSE/GEN/RET/002_SPR TP/oneM2M/CSE/GEN/RET/002_ABS TP/oneM2M/CSE/GEN/DEL/002_CSR TP/oneM2M/CSE/GEN/DEL/002_SPR TP/oneM2M/CSE/GEN/DEL/002_ABS CE/GEN/00002 CE/GEN/00002/00001 Support blocking request REG CE/REG/00001 CE/REG/00001/00001 Support <CSEBase> resource with attributes multiplicity equals 1[1]. TP/oneM2M/CSE/REG/CRE/021 TP/oneM2M/CSE/REG/RET/001 TP/oneM2M/CSE/REG/RET/008 TP/oneM2M/CSE/REG/UPD/001 TP/oneM2M/CSE/REG/DEL/001 CE/REG/00001/00002 Support the cseType attribute of <CSEBase> resource TP/oneM2M/CSE/REG/RET/002_CST TP/oneM2M/CSE/REG/RET/005 CE/REG/00001/00003 Support the nodeLink attribute of <CSEBase> resource. This is dependent on the feature set for <node> resource. TP/oneM2M/CSE/REG/RET/002_NL CE/REG/00002 CE/REG/00002/00001 Support <AE> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/REG/RET/003 TP/oneM2M/CSE/REG/DEL/003 TP/oneM2M/CSE/DMR/RET/013_AE TP/oneM2M/CSE/DMR/UPD/016_AE/ET TP/oneM2M/CSE/DMR/UPD/016_AE/RR CE/REG/00002/00002 AE registration/de- registration without a pre- assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'C'. TP/oneM2M/CSE/REG/CRE/004 TP/oneM2M/CSE/REG/CRE/005 TP/oneM2M/CSE/REG/CRE/006 TP/oneM2M/CSE/REG/CRE/007 TP/oneM2M/CSE/REG/CRE/008 TP/oneM2M/CSE/REG/CRE/010 TP/oneM2M/CSE/REG/CRE/011 TP/oneM2M/CSE/REG/CRE/016 TP/oneM2M/CSE/REG/CRE/017_API TP/oneM2M/CSE/REG/CRE/017_RR TP/oneM2M/CSE/REG/CRE/022 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 27 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/REG/00002/00003 AE registration/de- registration without a pre- assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S'. TP/oneM2M/CSE/REG/CRE/023 CE/REG/00002/00004 AE registration/de- registration without a pre- assigned AE-ID in the registration request and where no AE-ID Stem is included. CE/REG/00002/00005 AE registration/de- registration without a pre- assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S' and where announcement to an IN-CSE is needed to get an AE-ID assigned CE/DIS/00001/00006 Support the labels attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/LBL TP/oneM2M/CSE/REG/RET/004_LBL TP/oneM2M/CSE/DMR/UPD/015_AE/LBL CE/REG/00002/00007 Support the applicationName attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/APN TP/oneM2M/CSE/REG/RET/004_APN TP/oneM2M/CSE/DMR/UPD/015_AE/APN CE/REG/00002/00008 Support the pointOfAccess attribute of <AE> resource TP/oneM2M/CSE/REG/CRE/012_AE/POA TP/oneM2M/CSE/REG/RET/004_POA TP/oneM2M/CSE/DMR/UPD/015_AE/POA CE/REG/00002/00009 AE registration with pre-assigned AE-ID TP/oneM2M/CSE/REG/CRE/002 TP/oneM2M/CSE/REG/CRE/003 TP/oneM2M/CSE/REG/CRE/020 CE/REG/00004 CE/REG/00004/00001 Support <remoteCSE> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/REG/CRE/018 TP/oneM2M/CSE/REG/CRE/019 TP/oneM2M/CSE/REG/CRE/025 TP/oneM2M/CSE/REG/RET/006 TP/oneM2M/CSE/REG/RET/010 TP/oneM2M/CSE/REG/DEL/002 TP/oneM2M/CSE/DMR/UPD/016_CSR/ET TP/oneM2M/CSE/DMR/UPD/016_CSR/RR CE/DIS/00001/00006 Support the labels attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_LBL TP/oneM2M/CSE/REG/CRE/028_LBL TP/oneM2M/CSE/REG/RET/007_LBL TP/oneM2M/CSE/REG/UPD/002_LBL CE/REG/00004/00002 Support the cseType attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_CST TP/oneM2M/CSE/REG/CRE/027 TP/oneM2M/CSE/REG/RET/007_CST ETSI ETSI TS 118 125 V2.0.0 (2020-03) 28 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/REG/00004/00003 Support the pointOfAccess attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_POA TP/oneM2M/CSE/REG/CRE/028_POA TP/oneM2M/CSE/REG/RET/007_POA TP/oneM2M/CSE/REG/UPD/002_POA CE/REG/00004/00004 Support the nodeLink attribute of <remoteCSE> resource TP/oneM2M/CSE/REG/CRE/013_NL TP/oneM2M/CSE/REG/CRE/028_NL TP/oneM2M/CSE/REG/RET/007_NL TP/oneM2M/CSE/REG/UPD/002_NL CE/REG/00005 CE/REG/00005/00001 The Creation with <remoteCSE> resource for CSE registration with mandatory attributes[2] for Create and locally create <remoteCSE> that represents the Registree CSE TP/oneM2M/CSE/REG/CRE/024 TP/oneM2M/CSE/DMR/RET/013_CSR CE/REG/00005/00001 Create the <remoteCSE> with resourceName attribute TP/oneM2M/CSE/REG/CRE/026_RN CE/REG/00005/00001 Create the <remoteCSE> with expirationTime attribute TP/oneM2M/CSE/REG/CRE/026_ET CE/REG/00005/00004 Create the <remoteCSE> with labels attribute TP/oneM2M/CSE/REG/CRE/026_LBL CE/REG/00005/00002 Create the <remoteCSE> with cseType attribute TP/oneM2M/CSE/REG/CRE/026_CST CE/REG/00005/00003 Create the <remoteCSE> with pointOfAccess attribute TP/oneM2M/CSE/REG/CRE/026_POA CE/REG/00005/00005 Create the <remoteCSE> with nodeLink attribute TP/oneM2M/CSE/REG/CRE/026_NL CE/DIS/00001/00006 Update the <remoteCSE> with labels TP/oneM2M/CSE/REG/UPD/003_LBL TP/oneM2M/CSE/DMR/UPD/015_CSR/LBL CE/REG/00005/00001 Update the <remoteCSE> with expirationTime TP/oneM2M/CSE/REG/UPD/003_ET CE/REG/00005/00006 Update the <remoteCSE> with pointOfAccess attribute TP/oneM2M/CSE/REG/UPD/003_POA TP/oneM2M/CSE/DMR/UPD/015_CSR/PO A CE/REG/00005/00007 Update the <remoteCSE> with requestReachabil ity TP/oneM2M/CSE/REG/UPD/003_RR ETSI ETSI TS 118 125 V2.0.0 (2020-03) 29 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/REG/00005/00008 Update the <remoteCSE> with nodeLink attribute TP/oneM2M/CSE/REG/UPD/003_NL TP/oneM2M/CSE/DMR/UPD/015_CSR/NL CE/REG/00005/00001 Delete the <remoteCSE> resource on the Registrar, also delete the <remoteCSE> resource on the Registree TP/oneM2M/CSE/REG/DEL/004 CE/REG/00005/00009 Retrieve the <remoteCSE> resource TP/oneM2M/CSE/REG/RET/009 DMR CE/DMR/00001 CE/DMR/00001/00001 Support <container> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_CNT/CB TP/oneM2M/CSE/DMR/CRE/001_CNT/AE TP/oneM2M/CSE/DMR/CRE/001_CNT/CN T TP/oneM2M/CSE/DMR/CRE/002_CNT TP/oneM2M/CSE/DMR/CRE/003_CNT TP/oneM2M/CSE/DMR/CRE/007 TP/oneM2M/CSE/DMR/CRE/008 TP/oneM2M/CSE/DMR/CRE/009 TP/oneM2M/CSE/DMR/CRE/010 TP/oneM2M/CSE/DMR/CRE/011 TP/oneM2M/CSE/DMR/CRE/014_CNT_CI N TP/oneM2M/CSE/DMR/RET/001_CNT TP/oneM2M/CSE/DMR/RET/013_CNT TP/oneM2M/CSE/DMR/UPD/001_CNT/LBL TP/oneM2M/CSE/DMR/UPD/002_CNT/LBL TP/oneM2M/CSE/DMR/UPD/003_CNT/LBL TP/oneM2M/CSE/DMR/UPD/004_CNT/ET/ MNI/LBL TP/oneM2M/CSE/DMR/UPD/005_CNT/EX C TP/oneM2M/CSE/DMR/UPD/007_CNT/CT TP/oneM2M/CSE/DMR/UPD/008_CNT/ET TP/oneM2M/CSE/DMR/UPD/009_CNT/LBL TP/oneM2M/CSE/DMR/UPD/010 TP/oneM2M/CSE/DMR/UPD/016_CNT/ET TP/oneM2M/CSE/DMR/DEL/001_CNT TP/oneM2M/CSE/DMR/DEL/005 TP/oneM2M/CSE/DMR/DEL/006 CE/DIS/00001/00006 Support the labels attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/012_CNT/LBL TP/oneM2M/CSE/DMR/UPD/014_CNT/LBL TP/oneM2M/CSE/DMR/UPD/015_CNT/LBL CE/DMR/00001/00001 Support the creator attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/012_CNT/CR CE/DMR/00001/00002 Support the maxNrOfInstance s attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MNI TP/oneM2M/CSE/DMR/CRE/006_MNI TP/oneM2M/CSE/DMR/CRE/012_CNT/MNI TP/oneM2M/CSE/DMR/UPD/014_CNT/MNI TP/oneM2M/CSE/DMR/UPD/015_CNT/MNI CE/DMR/00001/00003 Support the maxByteSize attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MBS TP/oneM2M/CSE/DMR/CRE/006_MBS TP/oneM2M/CSE/DMR/CRE/012_CNT/MB S TP/oneM2M/CSE/DMR/CRE/013 TP/oneM2M/CSE/DMR/UPD/014_CNT/MB S TP/oneM2M/CSE/DMR/UPD/015_CNT/MB S ETSI ETSI TS 118 125 V2.0.0 (2020-03) 30 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/DMR/00001/00004 Support the maxInstanceAge attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/005_MIA TP/oneM2M/CSE/DMR/CRE/006_MIA TP/oneM2M/CSE/DMR/CRE/012_CNT/MIA TP/oneM2M/CSE/DMR/UPD/014_CNT/MIA TP/oneM2M/CSE/DMR/UPD/015_CNT/MIA CE/DMR/00002 CE/DMR/00002/00001 Support <contentInstance > resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_CIN/CNT TP/oneM2M/CSE/DMR/RET/001_CIN TP/oneM2M/CSE/DMR/UPD/BV/011 TP/oneM2M/CSE/DMR/DEL/001_CIN CE/DIS/00001/00006 Support the labels attribute of <contentInstance > resource TP/oneM2M/CSE/DMR/CRE/012_CIN/LBL CE/DMR/00002/00001 Support the creator attribute of <contentInstance > resource TP/oneM2M/CSE/DMR/CRE/012_CIN/CR CE/DMR/00002/00002 Support the contentInfo attribute of <contentInstance > resource TP/oneM2M/CSE/DMR/CRE/012_CIN/CNF CE/DMR/00002/00004 Retrieve and Delete of latest <contentInstance > resource by <latest> virtual resource TP/oneM2M/CSE/DMR/RET/012 TP/oneM2M/CSE/DMR/UPD/012 TP/oneM2M/CSE/DMR/DEL/007 CE/DMR/00002/00057 Retrieve and Delete of oldest <contentInstance > resource by <oldest> virtual resource TP/oneM2M/CSE/DMR/RET/010 TP/oneM2M/CSE/DMR/UPD/013 TP/oneM2M/CSE/DMR/DEL/009 SUB CE/SUB/00001 CE/SUB/00001/00001 The Support of <subscription> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_SUB/CB TP/oneM2M/CSE/DMR/CRE/001_SUB/AE TP/oneM2M/CSE/DMR/CRE/001_SUB/CN T TP/oneM2M/CSE/DMR/CRE/001_SUB/AC P TP/oneM2M/CSE/DMR/CRE/001_SUB/CS R TP/oneM2M/CSE/DMR/CRE/001_SUB/AE A TP/oneM2M/CSE/DMR/CRE/002_SUB TP/oneM2M/CSE/DMR/CRE/003_SUB TP/oneM2M/CSE/DMR/RET/001_SUB TP/oneM2M/CSE/DMR/RET/013_SUB TP/oneM2M/CSE/DMR/UPD/001_SUB/LBL TP/oneM2M/CSE/DMR/UPD/002_SUB/LBL TP/oneM2M/CSE/DMR/UPD/003_SUB/LBL TP/oneM2M/CSE/DMR/UPD/004_SUB/ET/ LBL/EXC TP/oneM2M/CSE/DMR/UPD/005_SUB/MNI TP/oneM2M/CSE/DMR/UPD/007_SUB/CT TP/oneM2M/CSE/DMR/UPD/008_SUB/ET TP/oneM2M/CSE/DMR/UPD/009_SUB/LBL TP/oneM2M/CSE/DMR/UPD/016_SUB/ET TP/oneM2M/CSE/DMR/UPD/016_SUB/NU TP/oneM2M/CSE/DMR/UPD/016_SUB/NC T TP/oneM2M/CSE/DMR/DEL/001_SUB ETSI ETSI TS 118 125 V2.0.0 (2020-03) 31 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/DIS/00001/00006 Support the labels attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/012_SUB/LBL TP/oneM2M/CSE/DMR/UPD/014_SUB/LBL TP/oneM2M/CSE/DMR/UPD/015_SUB/LBL CE/SUB/00001/00001 Support the creator attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/012_SUB/CR CE/SUB/00001/00001 Support the subscriberURI attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/012_SUB/SU CE/SUB/00004 CE/SUB/00004/00001 Notify the address indicated in notificationURI with notification elements multiplicity equals 1[2] TP/oneM2M/CSE/SUB/CRE/001_SUB TP/oneM2M/CSE/SUB/CRE/001_CIN TP/oneM2M/CSE/SUB/CRE/003 TP/oneM2M/CSE/SUB/CRE/005 CE/SUB/00004/00002 Notify with notificationEvent/ representation set in the notification TP/oneM2M/CSE/SUB/CRE/005 TP/oneM2M/CSE/SUB/UPD/001 TP/oneM2M/CSE/SUB/DEL/001 CE/SUB/00004/00003 Notify with creator set in the notification TP/oneM2M/CSE/SUB/CRE/004 SEC CE/SEC/00001 CE/SEC/00001/00001 Support <accessControlP olicy> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_ACP/CB TP/oneM2M/CSE/DMR/CRE/001_ACP/AE TP/oneM2M/CSE/DMR/CRE/002_ACP TP/oneM2M/CSE/DMR/CRE/003_ACP TP/oneM2M/CSE/DMR/RET/001_ACP TP/oneM2M/CSE/DMR/RET/013_ACP TP/oneM2M/CSE/DMR/UPD/001_ACP/LBL TP/oneM2M/CSE/DMR/UPD/002_ACP/LBL TP/oneM2M/CSE/DMR/UPD/003_ACP/LBL TP/oneM2M/CSE/DMR/UPD/004_ACP/PV/ AT/LBL TP/oneM2M/CSE/DMR/UPD/005_ACP/EX C TP/oneM2M/CSE/DMR/UPD/007_ACP/CT TP/oneM2M/CSE/DMR/UPD/008_ACP/ET TP/oneM2M/CSE/DMR/UPD/009_ACP/LBL TP/oneM2M/CSE/DMR/UPD/016_ACP/ET TP/oneM2M/CSE/DMR/UPD/016_ACP/PV TP/oneM2M/CSE/DMR/UPD/016_ACP/PV S TP/oneM2M/CSE/DMR/DEL/001_ACP TP/oneM2M/CSE/SEC/ACP/CRE/001 TP/oneM2M/CSE/SEC/ACP/CRE/002 TP/oneM2M/CSE/SEC/ACP/CRE/003 TP/oneM2M/CSE/SEC/ACP/CRE/004 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 32 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark CE/DIS/00001/00006 Support the labels attribute of <accessControlP olicy> resource TP/oneM2M/CSE/DMR/CRE/012_ACP/LBL TP/oneM2M/CSE/DMR/UPD/014_ACP/LBL TP/oneM2M/CSE/DMR/UPD/015_ACP/LBL CE/SEC/00002 CE/SEC/00002/00001 Support accessControlPol icyIDs attribute for <resource> that the Implementation supports. TP/oneM2M/CSE/DMR/CRE/012_SUB/AC PI TP/oneM2M/CSE/DMR/CRE/012_CNT/AC PI TP/oneM2M/CSE/DMR/UPD/014_CNT/AC PI TP/oneM2M/CSE/DMR/UPD/015_AE/ACPI TP/oneM2M/CSE/DMR/UPD/015_CNT/AC PI TP/oneM2M/CSE/DMR/UPD/015_SUB/AC PI TP/oneM2M/CSE/SEC/ACP/UPD/001 TP/oneM2M/CSE/SEC/ACP/UPD/002 CE/SEC/00002/00002 Support access control decision and enforcement making on the Hosting CSE TP/oneM2M/CSE/DMR/CRE/004_CNT TP/oneM2M/CSE/DMR/CRE/004_ACP TP/oneM2M/CSE/DMR/CRE/004_SUB TP/oneM2M/CSE/DMR/RET/003 TP/oneM2M/CSE/DMR/RET/014_ACP TP/oneM2M/CSE/DMR/RET/014_AE TP/oneM2M/CSE/DMR/RET/014_CNT TP/oneM2M/CSE/DMR/RET/014_CSR TP/oneM2M/CSE/DMR/RET/014_SUB TP/oneM2M/CSE/DMR/UPD/006_CNT/LBL TP/oneM2M/CSE/DMR/UPD/006_ACP/LBL TP/oneM2M/CSE/DMR/UPD/006_SUB/LBL TP/oneM2M/CSE/DMR/DEL/002_CNT TP/oneM2M/CSE/DMR/DEL/002_ACP TP/oneM2M/CSE/DMR/DEL/002_SUB TP/oneM2M/CSE/SUB/CRE/002 TP/oneM2M/CSE/SEC/ACP/001_CRE TP/oneM2M/CSE/SEC/ACP/001_UPD TP/oneM2M/CSE/SEC/ACP/001_RET TP/oneM2M/CSE/SEC/ACP/001_DEL TP/oneM2M/CSE/SEC/ACP/002_CRE TP/oneM2M/CSE/SEC/ACP/002_UPD TP/oneM2M/CSE/SEC/ACP/002_RET TP/oneM2M/CSE/SEC/ACP/002_DEL TP/oneM2M/CSE/SEC/ACP/003_CRE TP/oneM2M/CSE/SEC/ACP/003_UPD TP/oneM2M/CSE/SEC/ACP/003_RET TP/oneM2M/CSE/SEC/ACP/003_DEL TP/oneM2M/CSE/SEC/ACP/004_CRE TP/oneM2M/CSE/SEC/ACP/004_UPD TP/oneM2M/CSE/SEC/ACP/004_RET TP/oneM2M/CSE/SEC/ACP/004_DEL TP/oneM2M/CSE/SEC/ACP/005_CRE TP/oneM2M/CSE/SEC/ACP/005_UPD TP/oneM2M/CSE/SEC/ACP/005_RET TP/oneM2M/CSE/SEC/ACP/005_DEL TP/oneM2M/CSE/SEC/ACP/006_CRE TP/oneM2M/CSE/SEC/ACP/006_UPD TP/oneM2M/CSE/SEC/ACP/006_RET TP/oneM2M/CSE/SEC/ACP/006_DEL TP/oneM2M/CSE/SEC/ACP/007_CRE TP/oneM2M/CSE/SEC/ACP/007_UPD TP/oneM2M/CSE/SEC/ACP/007_RET TP/oneM2M/CSE/SEC/ACP/007_DEL TP/oneM2M/CSE/SEC/ACP/008_CRE TP/oneM2M/CSE/SEC/ACP/008_UPD TP/oneM2M/CSE/SEC/ACP/008_RET TP/oneM2M/CSE/SEC/ACP/008_DEL TP/oneM2M/CSE/SEC/ACP/009_CRE TP/oneM2M/CSE/SEC/ACP/009_UPD ETSI ETSI TS 118 125 V2.0.0 (2020-03) 33 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/SEC/ACP/009_RET TP/oneM2M/CSE/SEC/ACP/009_DEL TP/oneM2M/CSE/SEC/ACP/010_CRE TP/oneM2M/CSE/SEC/ACP/010_UPD TP/oneM2M/CSE/SEC/ACP/010_RET TP/oneM2M/CSE/SEC/ACP/010_DEL TP/oneM2M/CSE/SEC/ACP/011_CRE TP/oneM2M/CSE/SEC/ACP/011_UPD TP/oneM2M/CSE/SEC/ACP/011_RET TP/oneM2M/CSE/SEC/ACP/011_DEL TP/oneM2M/CSE/SEC/ACP/012_CRE TP/oneM2M/CSE/SEC/ACP/012_UPD TP/oneM2M/CSE/SEC/ACP/012_RET TP/oneM2M/CSE/SEC/ACP/012_DEL ETSI ETSI TS 118 125 V2.0.0 (2020-03) 34 oneM2M TS-0025 version 2.0.0 Release 2A |
cd027fdc16a1b80df882bb1985c2eecc | 118 125 | 5.8.4 Extendable feature sets | Table 5.8.4-1: Extendable feature set for gateway as MN Function Feature Set Feature Remark DIS CE/DIS/00001 CE/DIS/00001/00001 Support the Discovery request with filterUsage equals to "Discovery" TP/oneM2M/CSE/DIS/001 TP/oneM2M/CSE/DIS/002 TP/oneM2M/CSE/DIS/003 TP/oneM2M/CSE/DIS/004 TP/oneM2M/CSE/DIS/005 TP/oneM2M/CSE/DIS/006 CE/DIS/00001/00002 Support discovery with filterCriteria (createdBefore, createdAfter, modifiedSince, unmodifiedSince, stateTagSmaller, stateTagBigger, expireBefore, expireAfter, labels, resourceType, sizeAbove, sizeBelow, contentType, limit, attribute) TP/oneM2M/CSE/DIS/007 TP/oneM2M/CSE/DIS/008 TP/oneM2M/CSE/DIS/009 CE/DIS/00001/00003 Support discovery with filterCriteria (level, offset) CE/DIS/00001/00004 Support discovery with content filter (contentFilterSyntax, contentFilterQuery of filterCriteria) CE/DIS/00001/00005 Support discovery with filterCriteria (filterOperation) GMG CE/GMG/00001 CE/GMG/00001/00001 Support the <group> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/001_GRP/CB TP/oneM2M/CSE/DMR/CRE/001_GRP/AE TP/oneM2M/CSE/DMR/CRE/002_GRP TP/oneM2M/CSE/DMR/CRE/003_GRP TP/oneM2M/CSE/DMR/RET/001_GRP TP/oneM2M/CSE/DMR/RET/013_GRP TP/oneM2M/CSE/DMR/UPD/001_GRP/LBL TP/oneM2M/CSE/DMR/UPD/002_GRP/LBL TP/oneM2M/CSE/DMR/UPD/003_GRP/LBL TP/oneM2M/CSE/DMR/UPD/004_GRP/ET/GN/LBL TP/oneM2M/CSE/DMR/UPD/005_GRP/EXC TP/oneM2M/CSE/DMR/UPD/006_GRP/LBL TP/oneM2M/CSE/DMR/UPD/007_GRP/CT TP/oneM2M/CSE/DMR/UPD/008_GRP/ET TP/oneM2M/CSE/DMR/UPD/009_GRP/LBL TP/oneM2M/CSE/DMR/UPD/016_GRP/ET TP/oneM2M/CSE/DMR/UPD/016_GRP/MNM TP/oneM2M/CSE/DMR/UPD/016_GRP/MID TP/oneM2M/CSE/DMR/DEL/001_GRP TP/oneM2M/CSE/DMR/DEL/002_GRP TP/oneM2M/CSE/GMG/CRE/001 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 35 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/GMG/CRE/003 TP/oneM2M/CSE/GMG/UPD/002 TP/oneM2M/CSE/GMG/UPD/007 TP/oneM2M/CSE/GMG/UPD/008 CE/DIS/00001/00006 Support the labels attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/LBL CE/GMG/00001/00001 Support the creator attribute of <group> resource CE/GMG/00001/00001 Support the groupName attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/GN CE/GMG/00002 CE/GMG/00002/00001 Support the memberTypeValidated attribute of <group> resource CE/GMG/00002/00002 Support the validation of member's resource type and set the memberTypeValidated as well as the procedure to update the group according to consistencyStrategy TP/oneM2M/CSE/GMG/CRE/002 TP/oneM2M/CSE/GMG/CRE/004 TP/oneM2M/CSE/GMG/CRE/005 TP/oneM2M/CSE/GMG/CRE/006 TP/oneM2M/CSE/GMG/CRE/007 TP/oneM2M/CSE/GMG/UPD/001 TP/oneM2M/CSE/GMG/UPD/003 TP/oneM2M/CSE/GMG/UPD/004 TP/oneM2M/CSE/GMG/UPD/005 TP/oneM2M/CSE/GMG/UPD/006 TP/oneM2M/CSE/GMG/UPD/009 TP/oneM2M/CSE/GMG/UPD/010 CE/GMG/00002/00003 Support the consistencyStrategy attribute of <group> resource CE/GMG/00003 CE/GMG/00003/00001 Fan out of request to all members and aggregate member responses TP/oneM2M/CSE/GMG/RET/001 TP/oneM2M/CSE/GMG/001_CRE TP/oneM2M/CSE/GMG/001_RET TP/oneM2M/CSE/GMG/001_UPD TP/oneM2M/CSE/GMG/001_DEL TP/oneM2M/CSE/GMG/002_CRE TP/oneM2M/CSE/GMG/002_RET TP/oneM2M/CSE/GMG/002_UPD TP/oneM2M/CSE/GMG/002_DEL TP/oneM2M/CSE/GMG/003_CRE TP/oneM2M/CSE/GMG/003_RET TP/oneM2M/CSE/GMG/003_UPD TP/oneM2M/CSE/GMG/003_DEL TP/oneM2M/CSE/GMG/004_CRE TP/oneM2M/CSE/GMG/004_RET TP/oneM2M/CSE/GMG/004_UPD TP/oneM2M/CSE/GMG/004_DEL TP/oneM2M/CSE/GMG/005_CRE TP/oneM2M/CSE/GMG/005_RET TP/oneM2M/CSE/GMG/005_UPD ETSI ETSI TS 118 125 V2.0.0 (2020-03) 36 oneM2M TS-0025 version 2.0.0 Release 2A Function Feature Set Feature Remark TP/oneM2M/CSE/GMG/005_DEL TP/oneM2M/CSE/GMG/006_CRE TP/oneM2M/CSE/GMG/006_RET TP/oneM2M/CSE/GMG/006_UPD TP/oneM2M/CSE/GMG/006_DEL CE/GMG/00003/00002 Create sub group resource in case multiple members belong to same member CSE CE/GMG/00003/00003 Create <subscription> resource via group without aggregating notifications CE/GMG/00003/00004 Create <subscription> resource via group and aggregate notifications CE/GMG/00003/00005 Support the membersAccessControlPolicyIDs attribute of <group> resource TP/oneM2M/CSE/DMR/UPD/015_GRP/MACP ETSI ETSI TS 118 125 V2.0.0 (2020-03) 37 oneM2M TS-0025 version 2.0.0 Release 2A Annex A (normative): Mapping of feature to test purposes Table A-1: Mapping of feature to Test Purposes Feature ID Feature Catalogue Description Mapped Test Purposes CE/GEN/00001/00001 Support Unstructured resource identifier CE/GEN/00001/00002 Support Structured resource identifier CE/GEN/00002/00001 Support blocking request CE/REG/00001/00001 Support <CSEBase> resource. CE/REG/00001/00002 Support the cseType attribute of <CSEBase> CE/REG/00001/00003 Support the nodeLink attribute of <CSEBase> CE/REG/00002/00001 Support <AE> resource CE/REG/00002/00002 AE registration without pre- assigned AE-ID in the registration request. Possible cases are: - The request includes AE-ID Stem as 'C' - The request includes AE-ID Stem as 'S' - The request does not include AE-ID Stem TP/oneM2M/CSE/REG/BV/001 TP/oneM2M/CSE/REG/BV/002 TP/oneM2M/CSE/REG/BV/003 TP/oneM2M/CSE/REG/BV/004 TP/oneM2M/CSE/REG/BV/005 TP/oneM2M/CSE/REG/BV/007 TP/oneM2M/CSE/REG/BV/008 TP/oneM2M/CSE/REG/BV/009 TP/oneM2M/CSE/REG/BV/010 CE/REG/00002/00003 Support the labels attribute of <AE> resource CE/REG/00002/00004 Support the applicationName attribute of <AE> resource CE/REG/00002/00005 Support the pointOfAccess attribute of <AE> resource CE/REG/00002/00006 AE registration with pre-assigned AE-ID CE/REG/00004/00001 Support <remoteCSE> resource with attributes multiplicity equals 1[1] CE/REG/00004/00002 Support the labels attribute of <remoteCSE> resource CE/REG/00004/00003 Support the cseType attribute of <remoteCSE> resource CE/REG/00004/00004 Support the pointOfAccess attribute of <remoteCSE> resource CE/REG/00004/00005 Support the nodeLink attribute of <remoteCSE> resource CE/DMR/00001/00001 Support <container> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/BV/001_01 TP/oneM2M/CSE/DMR/CRE/BV/002_01 TP/oneM2M/CSE/DMR/CRE/BV/003_01 TP/oneM2M/CSE/DMR/CRE/BV/004_01 TP/oneM2M/CSE/DMR/CRE/BV/005_0X TP/oneM2M/CSE/DMR/CRE/BV/006_0X TP/oneM2M/CSE/DMR/CRE/BV/009 TP/oneM2M/CSE/DMR/CRE/BV/012_01 TP/oneM2M/CSE/DMR/CRE/BV/013_01 TP/oneM2M/CSE/DMR/CRE/BV/014_01 TP/oneM2M/CSE/DMR/CRE/BV/015_01-07 TP/oneM2M/CSE/DMR/CRE/BV/016_02 TP/oneM2M/CSE/DMR/CRE/BV/017_02 TP/oneM2M/CSE/DMR/RET/BV/001_01 TP/oneM2M/CSE/DMR/RET/BO/002 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 38 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes TP/oneM2M/CSE/DMR/RET/BO/003_01 TP/oneM2M/CSE/DMR/RET/BV/004_01 TP/oneM2M/CSE/DMR/RET/BV/005_01 TP/oneM2M/CSE/DMR/RET/BV/006_01 TP/oneM2M/CSE/DMR/RET/BO/007_01 TP/oneM2M/CSE/DMR/RET/BO/008_01 TP/oneM2M/CSE/DMR/RET/BV/013_03 TP/oneM2M/CSE/DMR/RET/BO/014_03 TP/oneM2M/CSE/DMR/RET/BV/015_03 TP/oneM2M/CSE/DMR/RET/BV/016_03 TP/oneM2M/CSE/DMR/RET/BV/017_03 TP/oneM2M/CSE/DMR/RET/BV/018_03 TP/oneM2M/CSE/DMR/RET/BO/019_03 TP/oneM2M/CSE/DMR/UPD/BI/005_01 TP/oneM2M/CSE/DMR/UPD/BO/006_01 TP/oneM2M/CSE/DMR/UPD/BO/007_01 TP/oneM2M/CSE/DMR/UPD/BO/008_01 TP/oneM2M/CSE/DMR/UPD/BO/009_01 TP/oneM2M/CSE/DMR/UPD/BV/010 TP/oneM2M/CSE/DMR/UPD/BV/014_01-07 TP/oneM2M/CSE/DMR/UPD/BV/015_02 TP/oneM2M/CSE/DMR/UPD/BV/016_01 TP/oneM2M/CSE/DMR/DEL/BV/001_01 TP/oneM2M/CSE/DMR/DEL/BV/002_01 TP/oneM2M/CSE/DMR/DEL/BV/003 TP/oneM2M/CSE/DMR/DEL/BV/004_01 TP/oneM2M/CSE/DMR/DEL/BV/005 TP/oneM2M/CSE/DMR/DEL/BV/006 TP/oneM2M/CSE/DMR/BV/001_01 TP/oneM2M/CSE/DMR/BV/001_02 TP/oneM2M/CSE/DMR/BV/001_03 TP/oneM2M/CSE/DMR/BV/002_01 TP/oneM2M/CSE/DMR/BV/003_01 TP/oneM2M/CSE/DMR/BV/004_01 TP/oneM2M/CSE/DMR/BV/005_01 CE/DMR/00001/00002 Support the labels attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/BV/015_03 TP/oneM2M/CSE/DMR/UPD/BV/014_03 TP/oneM2M/CSE/DMR/UPD/BV/001_01 TP/oneM2M/CSE/DMR/UPD/BV/002_01 TP/oneM2M/CSE/DMR/UPD/BV/003_01 TP/oneM2M/CSE/DMR/UPD/BV/004_01 TP/oneM2M/CSE/DMR/UPD/BO/009 CE/DMR/00001/00003 Support the creator attribute of <container> resource CE/DMR/00001/00004 Support the maxNrOfInstances attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/BV/015_04 TP/oneM2M/CSE/DMR/CRE/BV/014_04 CE/DMR/00001/00005 Support the maxByteSize attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/BV/015_05 TP/oneM2M/CSE/DMR/CRE/BV/014_05 CE/DMR/00001/00006 Support the maxInstanceAge attribute of <container> resource TP/oneM2M/CSE/DMR/CRE/BV/015_06 TP/oneM2M/CSE/DMR/CRE/BV/014_06 CE/DMR/00002/00001 Support <contentInstance> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/UPD/BV/011 TP/oneM2M/CSE/DMR/CRE/BV/007 TP/oneM2M/CSE/DMR/CRE/BV/008 TP/oneM2M/CSE/DMR/CRE/BI/010 TP/oneM2M/CSE/DMR/CRE/BI/011 TP/oneM2M/CSE/DMR/CRE/BV/015_08-12 TP/oneM2M/CSE/DMR/CRE/BV/016_03 TP/oneM2M/CSE/DMR/CRE/BV/017_03 TP/oneM2M/CSE/DMR/UPD/BV/011 TP/oneM2M/CSE/DMR/UPD/BI/012 TP/oneM2M/CSE/DMR/UPD/BI/013 CE/DMR/00002/00002 Support the labels attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/BV/015_09 CE/DMR/00002/00003 Support the creator attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/BV/015_10 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 39 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes CE/DMR/00002/00004 Support the contentInfo attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/BV/015_11 CE/DMR/00002/00005 Support the contentRef attribute of <contentInstance> resource TP/oneM2M/CSE/DMR/CRE/BV/015_12 CE/DMR/00002/00006 Retrieve and Delete of latest <contentInstance> resource by <latest> virtual resource TP/oneM2M/CSE/DMR/RET/BV/012 TP/oneM2M/CSE/DMR/RET/BO/009 TP/oneM2M/CSE/DMR/UPD/BI/012 TP/oneM2M/CSE/DMR/DEL/BV/007 TP/oneM2M/CSE/DMR/DEL/BO/008 CE/DMR/00002/00007 Retrieve and Delete of oldest <contentInstance> resource by <oldest> virtual resource TP/oneM2M/CSE/DMR/RET/BV/010 TP/oneM2M/CSE/DMR/RET/BO/011 TP/oneM2M/CSE/DMR/UPD/BI/013 TP/oneM2M/CSE/DMR/DEL/BV/009 TP/oneM2M/CSE/DMR/DEL/BO/010 CE/SUB/00001/00001 The Support of <subscription> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/BV/001_06 TP/oneM2M/CSE/DMR/CRE/BV/002_06 TP/oneM2M/CSE/DMR/CRE/BV/003_06 TP/oneM2M/CSE/DMR/CRE/BV/004_06 TP/oneM2M/CSE/DMR/CRE/BV/012_06 TP/oneM2M/CSE/DMR/CRE/BV/013_06 TP/oneM2M/CSE/DMR/CRE/BV/014_06 TP/oneM2M/CSE/DMR/CRE/BV/015_15-31 TP/oneM2M/CSE/DMR/RET/BV/001_06 TP/oneM2M/CSE/DMR/RET/BO/002 TP/oneM2M/CSE/DMR/RET/BO/003_06 TP/oneM2M/CSE/DMR/RET/BV/004_06 TP/oneM2M/CSE/DMR/RET/BV/005_06 TP/oneM2M/CSE/DMR/RET/BV/006_06 TP/oneM2M/CSE/DMR/RET/BO/007_06 TP/oneM2M/CSE/DMR/RET/BO/008_06 TP/oneM2M/CSE/DMR/RET/BV/013_14 TP/oneM2M/CSE/DMR/RET/BO/014_14 TP/oneM2M/CSE/DMR/RET/BV/015_14 TP/oneM2M/CSE/DMR/RET/BV/016_14 TP/oneM2M/CSE/DMR/RET/BV/017_14 TP/oneM2M/CSE/DMR/RET/BV/018_14 TP/oneM2M/CSE/DMR/RET/BO/019_14 TP/oneM2M/CSE/DMR/UPD/BI/005_06 TP/oneM2M/CSE/DMR/UPD/BO/006_06 TP/oneM2M/CSE/DMR/UPD/BO/007_06 TP/oneM2M/CSE/DMR/UPD/BO/008_06 TP/oneM2M/CSE/DMR/UPD/BO/009_06 TP/oneM2M/CSE/DMR/UPD/BV/014_12-25 TP/oneM2M/CSE/DMR/DEL/BV/001_06 TP/oneM2M/CSE/DMR/DEL/BV/002_06 TP/oneM2M/CSE/DMR/DEL/BV/003 TP/oneM2M/CSE/DMR/DEL/BV/004_06 TP/oneM2M/CSE/DMR/DEL/BV/005 TP/oneM2M/CSE/DMR/DEL/BV/006 TP/oneM2M/CSE/DMR/BV/001_01 TP/oneM2M/CSE/DMR/BV/001_02 TP/oneM2M/CSE/DMR/BV/001_03 TP/oneM2M/CSE/DMR/BV/002_06 TP/oneM2M/CSE/DMR/BV/003_06 TP/oneM2M/CSE/DMR/BV/004_06 TP/oneM2M/CSE/DMR/BV/005_06 TP/oneM2M/CSE/SUB/BV/001 TP/oneM2M/CSE/SUB/BV/002 TP/oneM2M/CSE/SUB/BV/003 TP/oneM2M/CSE/SUB/BV/004 TP/oneM2M/CSE/SUB/BV/005 CE/SUB/00001/00002 Support the labels attribute of <subscription> resource. TP/oneM2M/CSE/DMR/CRE/BV/015_17 TP/oneM2M/CSE/DMR/UPD/BV/001_06 TP/oneM2M/CSE/DMR/UPD/BV/002_06 TP/oneM2M/CSE/DMR/UPD/BV/003_06 TP/oneM2M/CSE/DMR/UPD/BV/004_06 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 40 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes TP/oneM2M/CSE/DMR/UPD/BV/014_14 CE/SUB/00001/00003 Support the creator attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/BV/015_30 CE/SUB/00001/00004 Support the subscriberURI attribute of <subscription> resource TP/oneM2M/CSE/DMR/CRE/BV/015_31 CE/SUB/00004/00001 Notify the address indicated in notificationURI with notification elements multiplicity equals 1[2] TP/oneM2M/CSE/SUB/BV/006 TP/oneM2M/CSE/SUB/BV/007 TP/oneM2M/CSE/SUB/BV/008 TP/oneM2M/CSE/SUB/BV/009 TP/oneM2M/CSE/SUB/BV/011 TP/oneM2M/CSE/SUB/BV/012 TP/oneM2M/CSE/SUB/BV/013 TP/oneM2M/CSE/SUB/BV/014 TP/oneM2M/CSE/SUB/BV/015 TP/oneM2M/CSE/SUB/BV/016 TP/oneM2M/CSE/SUB/BV/017 TP/oneM2M/CSE/SUB/BV/018 TP/oneM2M/CSE/SUB/BV/019 TP/oneM2M/CSE/SUB/BV/020 TP/oneM2M/CSE/SUB/BV/021 CE/SUB/00004/00002 Notify with notificationEvent/representation set in the notification CE/SUB/00004/00003 Notify with creator set in the notification TP/oneM2M/CSE/SUB/BV/010 CE/SEC/00001/00001 Support <accessControlPolicy> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/BV/001_03 TP/oneM2M/CSE/DMR/CRE/BV/002_03 TP/oneM2M/CSE/DMR/CRE/BV/003_03 TP/oneM2M/CSE/DMR/CRE/BV/004_03 TP/oneM2M/CSE/DMR/CRE/BV/015_13-14 TP/oneM2M/CSE/DMR/CRE/BV/016_01 TP/oneM2M/CSE/DMR/CRE/BV/017_01 TP/oneM2M/CSE/DMR/RET/BV/001_03 TP/oneM2M/CSE/DMR/RET/BO/002 TP/oneM2M/CSE/DMR/RET/BO/003_03 TP/oneM2M/CSE/DMR/RET/BV/004_03 TP/oneM2M/CSE/DMR/RET/BV/005_03 TP/oneM2M/CSE/DMR/RET/BV/006_03 TP/oneM2M/CSE/DMR/RET/BO/007_03 TP/oneM2M/CSE/DMR/RET/BO/008_03 TP/oneM2M/CSE/DMR/RET/BV/013_01 TP/oneM2M/CSE/DMR/RET/BO/014_01 TP/oneM2M/CSE/DMR/RET/BV/015_01 TP/oneM2M/CSE/DMR/RET/BV/016_01 TP/oneM2M/CSE/DMR/RET/BV/017_01 TP/oneM2M/CSE/DMR/RET/BV/018_01 TP/oneM2M/CSE/DMR/RET/BO/019_01 TP/oneM2M/CSE/DMR/UPD/BI/005_03 TP/oneM2M/CSE/DMR/UPD/BO/006_03 TP/oneM2M/CSE/DMR/UPD/BO/007_03 TP/oneM2M/CSE/DMR/UPD/BO/008_03 TP/oneM2M/CSE/DMR/UPD/BO/009_03 TP/oneM2M/CSE/DMR/UPD/BV/014_08-11 TP/oneM2M/CSE/DMR/UPD/BV/015_01 TP/oneM2M/CSE/DMR/DEL/BV/001_03 TP/oneM2M/CSE/DMR/DEL/BV/002_03 TP/oneM2M/CSE/DMR/DEL/BV/003 TP/oneM2M/CSE/DMR/DEL/BV/004_03 TP/oneM2M/CSE/DMR/DEL/BV/005 TP/oneM2M/CSE/DMR/DEL/BV/006 TP/oneM2M/CSE/DMR/BV/001_01 TP/oneM2M/CSE/DMR/BV/001_02 TP/oneM2M/CSE/DMR/BV/001_03 TP/oneM2M/CSE/DMR/BV/002_03 TP/oneM2M/CSE/DMR/BV/003_03 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 41 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes TP/oneM2M/CSE/DMR/BV/004_03 TP/oneM2M/CSE/DMR/BV/005_03 TP/oneM2M/CSE/SEC/ACP/BV/001 TP/oneM2M/CSE/SEC/ACP/BV/002 TP/oneM2M/CSE/SEC/ACP/BV/003 TP/oneM2M/CSE/SEC/ACP/BV/004 TP/oneM2M/CSE/SEC/ACP/BV/005 TP/oneM2M/CSE/SEC/ACP/BO/006 TP/oneM2M/CSE/SEC/ACP/BV/007 TP/oneM2M/CSE/SEC/ACP/BO/008 TP/oneM2M/CSE/SEC/ACP/BV/009 TP/oneM2M/CSE/SEC/ACP/BO/010 TP/oneM2M/CSE/SEC/ACP/BV/011 TP/oneM2M/CSE/SEC/ACP/BO/012 TP/oneM2M/CSE/SEC/ACP/BO/013 TP/oneM2M/CSE/SEC/ACP/BV/014 TP/oneM2M/CSE/SEC/ACP/BV/015 TP/oneM2M/CSE/SEC/ACP/BV/016 CE/SEC/00001/00002 Support the labels attribute of <accessControlPolicy> resource TP/oneM2M/CSE/DMR/CRE/BV/015_14 TP/oneM2M/CSE/DMR/UPD/BV/014_09 CE/SEC/00002/00001 Support accessControlPolicyIDs attribute for <resource> that the Implementation supports. TP/oneM2M/CSE/DMR/CRE/BV/015_01 TP/oneM2M/CSE/DMR/CRE/BV/014_01 TP/oneM2M/CSE/DMR/CRE/BV/015_15 TP/oneM2M/CSE/DMR/CRE/BV/014_15 CE/SEC/00002/00002 Support access control decision and enforcement making on the Hosting CSE CE/DIS/00001/00001 Support the Discovery request with filterUsage equals to "Discovery" TP/oneM2M/CSE/DIS/BV/001 CE/DIS/00001/00002 Support discovery with filterCriteria (createdBefore, createdAfter, modifiedSince, unmodifiedSince, stateTagSmaller, stateTagBigger, expireBefore, expireAfter, labels, resourceType, sizeAbove, sizeBelow, contentType, limit, attribute) TP/oneM2M/CSE/DIS/BV/002 TP/oneM2M/CSE/DIS/BV/003 TP/oneM2M/CSE/DIS/BV/004 TP/oneM2M/CSE/DIS/BO/005 TP/oneM2M/CSE/DIS/BO/006 TP/oneM2M/CSE/DIS/BI/007 TP/oneM2M/CSE/DIS/BI/008_01-04 CE/DIS/00001/00003 Support discovery with filterCriteria (level, offset) CE/DIS/00001/00004 Support discovery with content filter (contentFilterSyntax, contentFilterQuery of filterCriteria) CE/DIS/00001/00005 Support discovery with filterCriteria (filterOperation) CE/GMG/00001/00001 Support the <group> resource with attributes multiplicity equals 1[1] TP/oneM2M/CSE/DMR/CRE/BV/001_02 TP/oneM2M/CSE/DMR/CRE/BV/002_02 TP/oneM2M/CSE/DMR/CRE/BV/003_02 TP/oneM2M/CSE/DMR/CRE/BV/004_02 TP/oneM2M/CSE/DMR/CRE/BV/012_02 TP/oneM2M/CSE/DMR/CRE/BV/013_02 TP/oneM2M/CSE/DMR/CRE/BV/014_02 TP/oneM2M/CSE/DMR/CRE/BV/016_04 TP/oneM2M/CSE/DMR/CRE/BV/017_04 TP/oneM2M/CSE/DMR/RET/BV/001_02 TP/oneM2M/CSE/DMR/RET/BO/002 TP/oneM2M/CSE/DMR/RET/BO/003_02 TP/oneM2M/CSE/DMR/RET/BV/004_02 TP/oneM2M/CSE/DMR/RET/BV/005_02 TP/oneM2M/CSE/DMR/RET/BV/006_02 TP/oneM2M/CSE/DMR/RET/BO/007_02 TP/oneM2M/CSE/DMR/RET/BO/008_02 TP/oneM2M/CSE/DMR/RET/BV/013_05 TP/oneM2M/CSE/DMR/RET/BO/014_05 ETSI ETSI TS 118 125 V2.0.0 (2020-03) 42 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes TP/oneM2M/CSE/DMR/RET/BV/015_05 TP/oneM2M/CSE/DMR/RET/BV/016_05 TP/oneM2M/CSE/DMR/RET/BV/017_05 TP/oneM2M/CSE/DMR/RET/BV/018_05 TP/oneM2M/CSE/DMR/RET/BO/019_05 TP/oneM2M/CSE/DMR/UPD/BI/005_02 TP/oneM2M/CSE/DMR/UPD/BO/006_02 TP/oneM2M/CSE/DMR/UPD/BO/007_02 TP/oneM2M/CSE/DMR/UPD/BO/008_02 TP/oneM2M/CSE/DMR/UPD/BO/009_02 TP/oneM2M/CSE/DMR/UPD/BV/015_03 TP/oneM2M/CSE/DMR/UPD/BV/016_02 TP/oneM2M/CSE/DMR/DEL/BV/001_02 TP/oneM2M/CSE/DMR/DEL/BV/002_02 TP/oneM2M/CSE/DMR/DEL/BV/003 TP/oneM2M/CSE/DMR/DEL/BV/004_02 TP/oneM2M/CSE/DMR/DEL/BV/005 TP/oneM2M/CSE/DMR/DEL/BV/006 TP/oneM2M/CSE/DMR/BV/001_01 TP/oneM2M/CSE/DMR/BV/001_02 TP/oneM2M/CSE/DMR/BV/001_03 TP/oneM2M/CSE/DMR/BV/002_02 TP/oneM2M/CSE/DMR/BV/003_02 TP/oneM2M/CSE/DMR/BV/004_02 TP/oneM2M/CSE/DMR/BV/005_02 TP/oneM2M/CSE/GMG/BV/001 TP/oneM2M/CSE/GMG/BV/002 TP/oneM2M/CSE/GMG/BV/003 TP/oneM2M/CSE/GMG/BV/004 TP/oneM2M/CSE/GMG/BV/016 TP/oneM2M/CSE/GMG/BV/017 CE/GMG/00001/00002 Support the labels attribute of <group> resource CE/GMG/00001/00003 Support the creator attribute of <group> resource CE/GMG/00001/00004 Support the groupName attribute of <group> resource CE/GMG/00002/00001 Support the memberTypeValidated attribute of <group> resource CE/GMG/00002/00002 Support the validation of member's resource type and set the memberTypeValidated as well as the procedure to update the group according to consistencyStrategy TP/oneM2M/CSE/GMG/BV/005 TP/oneM2M/CSE/GMG/BV/006 TP/oneM2M/CSE/GMG/BV/007 TP/oneM2M/CSE/GMG/BV/013 TP/oneM2M/CSE/GMG/BV/014 TP/oneM2M/CSE/GMG/BV/015 TP/oneM2M/CSE/GMG/BV/018 TP/oneM2M/CSE/GMG/BV/019 CE/GMG/00002/00003 Support the consistencyStrategy attribute of <group> resource CE/GMG/00003/00001 Fan out of request to all members and aggregate member responses TP/oneM2M/CSE/GMG/BV/008 TP/oneM2M/CSE/GMG/BV/009 TP/oneM2M/CSE/GMG/BV/020_01-04 TP/oneM2M/CSE/GMG/BO/021_01-04 TP/oneM2M/CSE/GMG/BV/022_01-04 TP/oneM2M/CSE/GMG/BV/023_01-04 TP/oneM2M/CSE/GMG/BV/024 CE/GMG/00003/00002 Create sub group resource in case multiple members belong to same member CSE CE/GMG/00003/00003 Create <subscription> resource via group without aggregating notifications ETSI ETSI TS 118 125 V2.0.0 (2020-03) 43 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes CE/GMG/00003/00004 Create <subscription> resource via group and aggregate notifications CE/GMG/00003/00005 Support the membersAccessControlPolicyIDs attribute of <group> resource CE/DMG/00001/00001 Support <node> resource with attributes multiplicity equals 1[1] CE/DMG/00001/00002 Support the labels attribute of <node> resource CE/DMG/00001/00003 Support the hostedCSELink attribute of <node> resource CE/DMG/00002/00001 Support <mgmtObj> resource with attributes multiplicity equals 1[1] CE/DMG/00002/00002 Support the labels attribute of <mgmtObj> resource CE/DMG/00002/00003 Support the description attribute of <mgmtObj> resource CE/DMG/00002/00004 Support the mgmtLink attribute of <mgmtObj> resource CE/DMG/00003/00001 Support the [software] specialization attributes multiplicity equals 1[1] CE/DMG/00003/00002 Support the activate attribute of [software] resource CE/DMG/00003/00003 Support the deactivate attribute of [software] resource CE/DMG/00003/00004 Support the activeStatus attribute of [software] resource CE/DMG/00004/00001 Support the [firmware] specialization attributes multiplicity equals 1[1] CE/DMG/00005/00001 Support the [deviceInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00006/00001 Support [deviceCapability] specialization attributes multiplicity equals 1[1] CE/DMG/00006/00002 Support the enable attribute of [deviceCapability] resource CE/DMG/00006/00003 Support the disable attribute of [deviceCapability] resource CE/DMG/00007/00001 Support [reboot] specialization attributes multiplicity equals 1[1] CE/DMG/00008/00001 Support [memory] specialization attributes multiplicity equals 1[1] CE/DMG/00009/00001 Support the [battery] specialization attributes multiplicity equals 1[1] CE/DMG/00010/00001 Support [eventLog] specialization attributes multiplicity equals 1[1] CE/DMG/00011/00001 Support [areaNwkInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00012/00001 Support [areaNwkDeviceInfo] specialization attributes multiplicity equals 1[1] CE/DMG/00012/00002 Support the sleepInterval attribute of [areaNwkDeviceInfo] resource CE/DMG/00012/00003 Support the sleepDuration attribute of [areaNwkDeviceInfo] resource ETSI ETSI TS 118 125 V2.0.0 (2020-03) 44 oneM2M TS-0025 version 2.0.0 Release 2A Feature ID Feature Catalogue Description Mapped Test Purposes CE/DMG/00012/00004 Support the status attribute of [areaNwkDeviceInfo] resource CE/DMG/00013/00001 Support the objectIDs attribute of <mgmtObj> resource CE/DMG/00013/00002 Support the objectPaths attribute of <mgmtObj> resource CE/DMG/00013/00003 Support the mgmtLink attribute of <mgmtObj> resource ETSI ETSI TS 118 125 V2.0.0 (2020-03) 45 oneM2M TS-0025 version 2.0.0 Release 2A History Document history V2.0.0 March 2020 Publication |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 1 Scope | The present document specifies the detailed methods for oneM2M and OCF interworking using the architecture identified in ETSI TS 118 133 [5] and annex F of ETSI TS 118 101 [2] for the following scenario: • Interworking with full mapping of the semantics of the non-oneM2M data model to Mca, see scenario number 1 listed in clause F.2 of ETSI TS 118 101 [2]. This is also in line with the interworking concepts specified in ETSI TS 118 133 [5]. This interworking scenario allows for interworking between OCF devices and oneM2M entities purely based on the common understanding of aligned information models - such as the models defined in ETSI TS 118 123 [6]. There is no limitation regarding the direction of exposure of services: Services provided by OCF devices (OCF servers) can be exposed to oneM2M entities or vice versa. The oneM2M entities do not need to be aware of any details of the OCF protocols or interfaces. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 2 References | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 118 111: "oneM2M; Common Terminology (oneM2M TS-0011)". [2] ETSI TS 118 101: "oneM2M; Functional Architecture (oneM2M TS-0001)". [3] Void. [4] ETSI TS 118 103: "oneM2M; Security Solutions (oneM2M TS-0003)". [5] ETSI TS 118 133: "oneM2M; Interworking Framework (oneM2M TS-0033)". [6] ETSI TS 118 123: "oneM2M; Home Appliances Information Model and Mapping (oneM2M TS-0023)". [7] OCF Core Specification V2.0.0. [8] OCF Device Specification V2.0.0. [9] OCF Security Specification V2.0.0. [10] OCF Bridging Specification V1.3.0. [11] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace". ETSI ETSI TS 118 124 V4.0.1 (2025-10) 7 oneM2M TS-0024 version 4.0.1 Release 4 |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] oneM2M Drafting Rules. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3 Definition of terms, symbols and abbreviations | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and ETSI TS 118 133 [5] and the following apply. NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [1], ETSI TS 118 101 [2] and ETSI TS 118 133 [5]. OCF client: logical entity that accesses a resource on an OCF server OCF device: logical entity that assumes one or more roles (e.g. OCF client, OCF server) OCF framework: set of related functionalities and interactions defined in the OCF Core Specification [7], which enable interoperability across a wide range of networked devices, including the Internet of Things OCF-IPE: IPE providing interworking functions for OCF-oneM2M interworking OCF physical entity: aspect of the physical world that is exposed through an OCF device NOTE: An example of an OCF physical entity is a LED. OCF platform: physical device containing one or more devices OCF resource: represents an OCF entity modelled and exposed by the OCF framework OCF server: OCF device with the role of providing access to OCF resource state information and facilitating remote interaction with those resources OCF function: service or device information provided by one or more OCF servers by exposing access to OCF resources via OCF-specified interfaces |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.2 Symbols | Void. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy AE Application Entity AE-ID Application Entity IDentifier CSE Common Services Entity GUI Graphical User Interface ETSI ETSI TS 118 124 V4.0.1 (2025-10) 8 oneM2M TS-0024 version 4.0.1 Release 4 ID Identification IoT Internet of Things IPE Interworking Proxy Entity M2M Machine-to-Machine OCF OpenConnectivity Foundation OIC Open Interconnect Consortium OS Operating System SP Service Provider URI Uniform Resource Identifier UUID Universally Unique Identifier |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 5 Introduction to OCF interworking | OCF specifies an architecture enabling resource-based interactions among OCF devices, see OCF Core Specification [7]. OCF devices can expose aspects of the physical world like a lightbulb and/or logical entities like an application. The OCF devices in the OCF architecture can provide services - in that case they play the role of an OCF server - and/or consume services - in that case they play the role of an OCF client. The present document specifies details of the interworking with OCF devices on the information model layer, see ETSI TS 118 133 [5], and the implications on how to represent and execute external OCF functions with means of resource instances in the oneM2M system and vice versa. Service provided and/or consumed on either side (OCF versus oneM2M) are represented by resources hosted by service providers (OCF servers or oneM2M CSEs) and accessible to service consumers (OCF clients or oneM2M AEs/CSEs). In order to support seamless interworking across boundaries of OCF and oneM2M deployments, OCF and oneM2M have aligned several information models for such services so that they became technology agnostic. Definitions of such information models are contained in the following specifications: • ETSI TS 118 123 [6]. • OCF Device Specification [8]. In the remainder of the present document it is assumed that mutual exposure of services between oneM2M and OCF deployments is restricted to services represented by resource types defined in these specifications. In line with ETSI TS 118 133 [5], the present document specifies two major directions of mutual OCF/oneM2M interworking: • Expose OCF functions provided by OCF servers to oneM2M entities by using one or more OCF-IPE(s) which are acting as OCF client(s). For this direction - OCF services exposed to oneM2M - the OCF-IPE(s) are creating and managing the oneM2M resources representing exposed services provided by OCF servers and provide the required procedures to allow consumption of OCF services on the oneM2M side. Details on this exposure direction are specified in clause 6.1 of the present document. • Expose services provided by oneM2M entities by using one or more OCF-IPE(s) which are acting as OCF server(s). For this direction - oneM2M services provided to OCF - the OCF-IPE(s) are interacting with already created oneM2M resource representations that are offering the native oneM2M services and provide the required procedures to allow consumption of the oneM2M services on the OCF side. Details on this exposure direction are specified in clause 6.1 of the present document. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 9 oneM2M TS-0024 version 4.0.1 Release 4 While it is possible that a single OCF-IPE can simultaneously support exposure of OCF functions to oneM2M and exposure of oneM2M services to OCF, it is not mandated to implement OCF-IPEs in that way. It is also possible to instantiate separate OCF-IPEs for the different exposure directions. This is an implementation choice. In case that exposure in one direction needs to be correlated with a different Service Subscription Profile than for the other direction, separate OCF-IPEs are required. Details on the representation of OCF functions by oneM2M resources are defined in clause 7 of the present document. |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6 OCF interworking architecture | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6.1 Exposure of OCF functions to the oneM2M system | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 6.1.1 Summary of interworking architecture for exposure of OCF functions | An OCF-IPE exposing OCF functions to the oneM2M system is responsible for the creation of oneM2M resources representing the exposed OCF functions on its own Registrar-CSE. A single OCF-IPE may expose OCF functions provided by one or more OCF servers to the oneM2M system. A high-level summary of the relationship of OCF servers providing OCF functions to be exposed to oneM2M, one or more OCF-IPE(s) and sets of oneM2M resources representing the exposed OCF functions is depicted in figure 6.1.1-1. Figure 6.1.1-1: Summary of interworking architecture for exposure OCF to oneM2M ETSI ETSI TS 118 124 V4.0.1 (2025-10) 10 oneM2M TS-0024 version 4.0.1 Release 4 More than one OCF-IPE may be instantiated for exposure of multiple non-overlapping sets of OCF functions to the oneM2M system. In particular, if OCF functions provided by different sets of OCF servers shall be exposed to the oneM2M system and there is a deployment requirement to differentiate sets of OCF functions provided by different OCF servers - e.g. for the purpose of correlating them with different Service Subscription Profiles - then instantiating more than one OCF-IPE is required. Further details on the implications using more than one OCF-IPE for exposure of OCF functions to the oneM2M system are defined in clause 7.1. A specific instance of an OCF-IPE exposing OCF functions to the oneM2M system shall play the role of a single OCF client on the OCF side. If there is a deployment requirement to differentiate multiple OCF clients who act as interworking proxies for exposing a common set of OCF functions to the oneM2M system - for instance due to the need to assign different access control properties to them on the OCF side - then the OCF-IPE exposing those OCF functions would need to play the role of multiple OCF clients. However, mapping rules between the identifiers of Originators on the oneM2M side who attempt to consume the exposed OCF functions and OCF client identifiers to use for triggering the execution of the exposed OCF functions on the OCF side are not specified in the present document. Therefore, it is assumed that each OCF-IPE is only playing the role of a single OCF client on the OCF side. This restriction implies that all requests originating from oneM2M entities which are successfully modifying the corresponding oneM2M resources and then get translated by a specific OCF-IPE to the corresponding interactions with OCF servers are treated on the OCF side as coming from one single OCF client and, therefore, will be handled by OCF servers with the same access control properties, irrespective of the identifier of the Originator on the oneM2M side. However, by means of setting appropriate access control privileges on the oneM2M side, it is certainly possible to define which entities on the oneM2M side will get which mode of access to the exposed OCF services. Support of multiple OCF clients for a single OCF-IPE is for further study and might be subject of future releases of the present document. After creation of oneM2M resources representing exposed OCF functions by a specific OCF-IPE, this particular OCF-IPE is also responsible for monitoring relevant parts of these created resources in order to detect any operations that need to be translated into an execution of corresponding OCF functions. In case such an operation on the previously created oneM2M resources gets detected, the corresponding function on the OCF side shall be executed by the OCF- IPE. State changes within the OCF functions exposed by a specific OCF-IPE to the oneM2M system that are impacting the state of the corresponding oneM2M resources which were previously created by that specific OCF-IPE need to be monitored on the OCF side and shall be translated by that specific OCF-IPE into corresponding state changes of the associated oneM2M resources. 6.1.2 OCF-IPE responsibilities to support exposure of OCF functions to the oneM2M system When exposing OCF functions to the oneM2M system, an OCF-IPE shall be responsible to support the following procedures: 1) Determination of OCF functions to be exposed to the oneM2M system. The OCF-IPE needs to determine which OCF functions need to be exposed to the oneM2M system. This determination can be done in different ways (e.g. through provisioning, discovery, on-demand signalling, or combinations thereof). Further details of this procedure are defined in clause 8.1.1. 2) Creation/deletion of oneM2M resource representing exposed OCF functions. The OCF-IPE needs to perform creation/deletion of resource instances representing OCF functions according to the - possibly dynamically changing - need to expose them to the oneM2M system using resource types that have been aligned between oneM2M and OCF in order to become technology independent. Further details of this procedure are defined in clause 8.1.2. Resource types that meet the requirement to be technology agnostic between OCF and oneM2M are defined in OCF Device Specification [8] and ETSI TS 118 123 [6]. 3) Mirroring state of exposed OCF functions in oneM2M resources. An OCF-IPE exposing OCF functions provided by OCF servers is responsible to modify the resource instances it has created in order to represent the exposed OCF functions according to any state changes occurring in the corresponding OCF servers. This implies that such an OCF-IPE shall monitor the state of the associated OCF servers and upon detection of OCF server state changes relevant for the exposed OCF functions the OCF-IPE shall modify the previously created oneM2M resources accordingly. Further details of this procedure are defined in clause 8.1.3. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 11 oneM2M TS-0024 version 4.0.1 Release 4 4) Detection of requests to execute OCF functions and invocation thereof. The OCF-IPE is responsible for monitoring relevant changes in the resource instances it has previously created for the purpose of representing the exposed OCF functions. Upon detection of any valid operation meant to trigger the execution of the exposed OCF functions, the OCF-IPE is responsible for the invocation of the corresponding OCF functions via its own OCF client. Further details of this procedure are defined in clause 8.1.4. The set of responsibilities of the OCF-IPE when exposing OCF functions to the oneM2M system is summarized in figure 6.1.2-1. The dashed boxes describe optional/alternative means to determine the set of exposed OCF functions. NOTE: In figure 6.1.2-1 one OCF-IPE is responsible for all interworking procedures to support exposure of OCF functions to oneM2M. More than one OCF-IPE may be used to expose different sets of OCF functions to oneM2M. Details on how to map exposed OCF function into oneM2M resources are defined in clause 7. Figure 6.1.2-1: Exposure of OCF functions to the oneM2M system 6.2 Exposure of native oneM2M services to an OCF Proximal IoT Network 6.2.1 Summary of interworking architecture for exposure of native oneM2M services An OCF-IPE exposing oneM2M services to an OCF Proximal IoT Network is responsible for the creation of OCF server instances in the OCF Proximal IoT Network representing the exposed oneM2M services. A single OCF-IPE may expose one or more oneM2M services to the OCF Proximal IoT Network. A high-level summary of the relationship of oneM2M resources providing the services to be exposed to the OCF Proximal IoT Network, one or more OCF-IPE(s) and sets of OCF servers representing the exposed oneM2M services is depicted in figure 6.2.1-1. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 12 oneM2M TS-0024 version 4.0.1 Release 4 Figure 6.2.1-1: Summary of interworking architecture for exposure oneM2M to OCF More than one OCF-IPE may be instantiated for exposure of multiple non-overlapping sets of oneM2M services to the OCF Proximal IoT Network. In particular, if there is a deployment requirement to differentiate the exposure of different sets of oneM2M services - e.g. for the purpose of correlating them with different Service Subscription Profiles - then instantiating more than one OCF-IPE is required. Further details on the implications using more than one OCF-IPE for exposure of oneM2M services to the OCF Proximal IoT Network are defined in clause 7.1. A specific oneM2M service shall only be exposed to a given OCF Proximal IoT Network by at most one instance of an OCF-IPE connected to that OCF Proximal IoT Network. If there is a deployment requirement to differentiate multiple AE instances who act as interworking proxies on behalf of OCF clients for exposing a common set of oneM2M services to the OCF Proximal IoT Network - for instance due to the need to assign different access control privileges to them on the oneM2M side - then the exposure of that common set of oneM2M services would require multiple instances of OCF-IPEs with a shared set of OCF servers exposing the same set of oneM2M services to a given OCF Proximal IoT Network. However, mapping rules between the identifiers of OCF clients who attempt to consume the exposed oneM2M services and the respective OCF-IPE AE-IDs to use for triggering the execution of the exposed oneM2M services are not specified in the present document. Therefore, it is assumed that each exposed oneM2M service is only interacting with one OCF-IPE for a given OCF Proximal IoT Network. This restriction implies that all requests originating from OCF clients received by any of the OCF servers instantiated by a given OCF-IPE which are meant to be translated by the OCF-IPE to the corresponding operations on oneM2M resources representing the exposed oneM2M services are treated on the oneM2M side as coming from one single oneM2M AE and, therefore, will be handled by oneM2M CSEs with the same access control privileges, irrespective of the identifier of the requesting OCF client. However, by means of setting appropriate access control properties on the OCF side - i.e. access control governing the acceptance or requests at the OCF servers instantiated by the OCF-IPE - it is certainly possible to define which OCF client will get which mode of access to the exposed oneM2M services. Therefore, access control can be imposed on OCF client basis if the appropriate access control properties are provisioned properly into the OCF servers instantiated by the OCF-IPE. Support of multiple OCF-IPEs exposing the same set of oneM2M services is for further study and might be subject of future releases of the present document. After creation of OCF server instances representing the exposed oneM2M services by a specific OCF-IPE, this particular OCF-IPE is also responsible for monitoring incoming OCF client requests reaching these created OCF servers in order to detect any requests that need to be translated into a corresponding operation on oneM2M resources representing the exposed oneM2M services. In case such a request directed to the previously created OCF servers gets detected, the corresponding operation(s) on the oneM2M side shall be executed by the OCF-IPE. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 13 oneM2M TS-0024 version 4.0.1 Release 4 State changes within the oneM2M resources representing the oneM2M services exposed to the OCF Proximal IoT Network by a specific OCF-IPE that are impacting the state of the corresponding resources on any of the OCF servers that were previously created by that specific OCF-IPE need to be detected on the oneM2M side and shall be translated by that specific OCF-IPE into corresponding state changes of the associated resources in the OCF servers. 6.2.2 OCF-IPE responsibilities to support exposure of oneM2M services to an OCF Proximal IoT Network When exposing oneM2M services to an OCF Proximal IoT Network, an OCF-IPE shall be responsible to support the following procedures: 1) Determination of oneM2M services to be exposed to the OCF Proximal IoT Network. The OCF-IPE needs to determine which oneM2M services need to be exposed to the OCF Proximal IoT Network. This determination can be done in different ways (e.g. through provisioning, discovery, on-demand signalling, or combinations thereof). Further details of this procedure are defined in clause 8.2.1. 2) Instantiation/removal of OCF servers representing exposed oneM2M services. The OCF-IPE needs to perform instantiation/removal of OCF server instances representing oneM2M services according to the - possibly dynamically changing - need to expose them to the OCF Proximal IoT Network using OCF servers hosting OCF resource types that have been aligned between oneM2M and OCF in order to become technology independent. Further details of this procedure are defined in clause 8.2.2. OCF resource types and equivalent oneM2M resource types that meet the requirement to be technology agnostic between OCF and oneM2M are defined in ETSI TS 118 123 [6] and OCF Device Specification [8]. 3) Mirroring state of oneM2M resources representing exposed oneM2M services in OCF resources hosted on OCF servers. An OCF-IPE exposing oneM2M services to an OCF Proximal IoT Network is responsible to modify the resource instances in the OCF servers it has instantiated in order to represent the exposed oneM2M services according to any state changes occurring in the corresponding oneM2M resources. This implies that such an OCF-IPE shall monitor the state of the associated oneM2M resources and upon detection of oneM2M resource state changes relevant for the exposed oneM2M services, the OCF-IPE shall modify the corresponding resource state of OCF resources hosted in the previously instantiated OCF servers accordingly. Further details of this procedure are defined in clause 8.2.3. 4) Detection of requests to consume exposed oneM2M services and execution thereof. The OFC-IPE is responsible for monitoring relevant changes in the resources hosted by the OCF servers the OCF-IPE has previously instantiated for the purpose of representing the exposed oneM2M services. Upon detection of any valid operation on the OCF side meant to trigger the consumption of the associated exposed oneM2M services, the OCF-IPE is responsible for the requesting the corresponding oneM2M operation on the oneM2M resources representing the exposed oneM2M service to be consumed. Further details of this procedure are defined in clause 8.2.4. The set of responsibilities of the OCF-IPE when exposing oneM2M services to an OCF Proximal IoT Network is summarized in figure 6.2.2-1. The dashed boxes describe optional/alternative means to determine the set of exposed oneM2M services. NOTE: In figure 6.2.2-1, one OCF-IPE is responsible for all interworking procedures to support exposure of oneM2M services to an OCF Proximal IoT Network. More than one OCF-IPE may be used to expose different sets of oneM2M services to the same OCF Proximal IoT Network. Details on how to map exposed oneM2M services into OCF resources are defined in clause 7. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 14 oneM2M TS-0024 version 4.0.1 Release 4 Figure 6.2.2-1: Exposure of native oneM2M functions to the OCF Proximal IoT Network |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7 Representation of OCF and/or oneM2M functions | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1 Representation of OCF functions by oneM2M resources | |
bf6675e8dc9923ad4b06de459a3f4733 | 118 124 | 7.1.1 Representation of OCF devices by oneM2M <node> resources | An OCF device which provides functions that are exposed to the oneM2M system can be represented by a oneM2M <node> resource that contains device-specific information which can be used e.g. for the purpose of device management. Whether a specific OCF device shall be represented by a oneM2M <node> resource depends on the type of device. OCF devices providing services that are exposed to the oneM2M system using specializations of <flexContainer> resources as defined in ETSI TS 118 123 [6], see also clause 7.1.3, shall be represented by oneM2M <node> resources as well. Each instance of a <flexContainer> resource representing a service provided by a specific OCF device is linked via the nodeLink attribute to a specific <node> resource instance that represents this specific OCF device. For OCF devices that are not matching with any of the listed categories, the present document does not specify any normative procedure to represent such OCF devices as oneM2M <node> resources. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 15 oneM2M TS-0024 version 4.0.1 Release 4 When a <node> resource is used to represent an OCF device, it actually needs to reflect the details of the OCF platform that hosts the OCF device, attributes of the <node> resource listed in table 7.1.1-1 shall have the specified value settings in table 7.1.1-1. All other attributes of the <node> resource shall be used as specified in ETSI TS 118 101 [2]. A <node> resource representing an OCF device shall include exactly one [deviceInfo] child resource instance that represents specifics of the OCF platform hosting the OCF device. All other child resources of the <node> resource shall be used as specified in ETSI TS 118 101 [2]. Attributes of a [deviceInfo] resource listed in table 7.1.1-2 shall have the specified value settings in table 7.1.1-2 for the [deviceInfo] child resource instance representing the OCF platform of the OCF device. All other attributes or child resources of the [deviceInfo] resource shall be used as specified in ETSI TS 118 101 [2]. Table 7.1.1-1: Attribute settings for <node> resources representing an OCF platform Attribute Name Setting resourceName This attribute shall be set to the value of the "pi" property (Platform ID) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7]. labels This attribute shall include a Key:Value pair equal to "Iwked-Technology:OCF". Other Key:Value pairs may also be present. nodeID This attribute shall be set to the value of the "pi" property (Platform ID) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7]. hostedServiceLinks This attribute shall contain a list of resource identifiers of <flexContainer> resources representing OCF services provided by OCF servers which are hosted by the OCF platform that is represented by this <node> resource. Table 7.1.1-2: Attribute settings for a [deviceInfo] child resource of a <node> resource representing an OCF platform Attribute Name Setting labels This attribute shall include a Key:Value pair equal to "Iwked-Technology:OCF". Other Key:Value pairs may also be present. deviceLabel This attribute shall be set to the value of the "pi" property (Platform ID) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7]. manufacturer This attribute shall be set to the value of the "mnmn" property (Manufacturer Name) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. manufacturerDetailsLink This attribute shall be set to the value of the "mnml" property (Manufacturer Details Link) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. manufacturingDate This attribute shall be set to the value of the "mndt" property (Date of Manufacture) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. model This attribute shall be set to the value of the "mnmo" property (Model Number) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. subModel This attribute shall be set to the value of the "mnpv" property (Platform Version) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. deviceType This attribute shall be set to the value "OCF Platform". fwVersion This attribute shall be set to the value of the "mnfv" property (Firmware Version) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. hwVersion This attribute shall be set to the value of the "mnhw" property (Hardware Version) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. osVersion This attribute shall be set to the value of the "mnos" property (OS Version) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. systemTime This attribute shall expose the system time of the device in line with the value of the "st" property (SystemTime) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. supportURL This attribute shall be set to the value of the "mnsl" property (Support link) of the OCF resource with the pre-defined URI "/oic/p" of the respective OCF device as defined in the OCF Core Specification [7], if present. ETSI ETSI TS 118 124 V4.0.1 (2025-10) 16 oneM2M TS-0024 version 4.0.1 Release 4 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.