hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.2.1 Freshness | • CoAP server shall use Max-Age CoAP Option to specify the explicit expiration time for the CoAP Response's resource representation. This indicates that the response is not fresh after its age is greater than the specified number of seconds. • Max-Age Option defaults to a value of 60 (seconds). In case, Max-Age Option ... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.2.2 Validity | • A CoAP endpoint with stored responses but not able to satisfy subsequent requests (for example, the response is not fresh), shall use the Etag Option to perform a conditional request to the CoAP server where the resource is hosted. • If the cached response with the CoAP client is still valid, the server shall include... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 5.2.3 Blockwise Transfers | CoAP Block [3] Options may be used when CoAP endpoints need to transfer large payloads e.g. firmware, software updates. Instead of relying on IP fragmentation, CoAP Block Option should be used for transferring multiple blocks of information in multiple request-response pairs. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6 CoAP Message Mapping | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.1 Introduction | When AE or CSE binds oneM2M primitives to CoAP messages, or binds CoAP messages to oneM2M primitives, it is required that: • AE shall host a CoAP client and should host a CoAP server; or • CSE shall host both a CoAP client and a CoAP server. Basically single oneM2M request primitive is mapped to single CoAP request mes... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2 Primitive Mapping to CoAP Message | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.0 Introduction | This clause describes where to map oneM2M parameters in a primitive to header, Option and payload fields in a CoAP message. oneM2M TS-0008 version 4.4.1 Release 4 ETSI ETSI TS 118 108 V4.4.1 (2023-08) 10 |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.1 Header | This clause specifies how to configure CoAP header information: • The Version field shall be configured as 1. • The Type field shall be configured according to clause 6.3. The Reset message is used to indicate an error in response to a malformed message in the CoAP layer. • In case of a request, the Code field indicate... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2 Configuration of Token and Options | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.0 Introduction | This clause describes configuration of Token and Options based on oneM2M parameters. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.1 Token | The CoAP token is used by the CoAP layer to match a response to a request, in a manner that is similar to the oneM2M Request Identifier. Due to size limitations, a Request Identifier cannot be used directly as the CoAP Token. The use of tokens by Originator and Receiver shall comply with requirements of the CoAP specif... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.2 Content Format Negotiation Options | The CoAP Accept Option may be used to indicate which Content-Format is acceptable to an Originator. If a Hosting CSE supports the Content-Format specified in Accept Option of the request, the Hosting CSE shall respond with that Content-Format. If the Hosting CSE does not support the Content-Format specified in Accept O... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.3 URI Options | This clause describes how to configure CoAP Uri-Host, Uri-Port, Uri-Path, and Uri-Query Options. Host and port part of the address specified in pointOfAccess attribute of <remoteCSE> resource shall be mapped to Uri- Host and Uri-Port respectively. If To parameter contains absolute format, then the first URI-Path Option... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4 Definition of New Options | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.0 Introduction | This clause describes new CoAP Options used for binding several oneM2M request/response parameters. Table 6.2.2.4.0-1 contains definitions of the new CoAP Options and sub-clauses specify oneM2M parameter mapping with the newly defined CoAP Options in Table 6.2.2.4.0-1. Table 6.2.2.4.0-1: Definition of New Options No C ... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.1 From | The From parameter shall be mapped to the oneM2M-FR Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.2 Request Identifier | The Request Identifier parameter shall be mapped to the oneM2M-RQI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.3 Void | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.4 Originating Timestamp | The Originating Timestamp parameter shall be mapped to the oneM2M-OT Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.5 Request Expiration Timestamp | The Request Expiration Timestamp parameter shall be mapped to the oneM2M-RQET Option. oneM2M TS-0008 version 4.4.1 Release 4 ETSI ETSI TS 118 108 V4.4.1 (2023-08) 13 |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.6 Result Expiration Timestamp | The Request Expiration Timestamp parameter shall be mapped to the oneM2M-RSET Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.7 Operation Execution Time | The Operation Execution Time parameter shall be mapped to the oneM2M-OET Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.8 notificationURI of Response Type | The notificationURI element of Response Type parameter shall be mapped to the oneM2M-RTURI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.9 Event Category | The Event Category parameter shall be mapped to the oneM2M-EC Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.10 Response Status Code | The Response Status Code parameter shall be mapped to the oneM2M-RSC Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.11 Group Request Identifier | The Group Request Identifier parameter shall be mapped to the oneM2M-GID Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.12 Resource Type | The Resource Type parameter shall be mapped to the oneM2M-TY Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.13 Content Offset | The Content Offset parameter shall be mapped to the oneM2M-CTO Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.14 Content Status | The Content Status parameter shall be mapped to the oneM2M-CTS Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.15 Assigned Token Identifiers | The Assigned Token Identifiers parameter shall be mapped to the oneM2M-ATI Option. The format of the oneM2M- ATI option shall be represented as a sequence of lti-value:tkid-value pairs separated by a colon ':' and multiple pairs separated by a '+' character. EXAMPLE: The option looks as follows: oneM2M-ATI: lti-value1:... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.16 Release Version Indicator | The Release Version Indicator parameter shall be mapped to the oneM2M-RVI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.17 Vendor Information | The Vendor Information parameter shall be mapped to the oneM2M-VSI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.18 Group Request Target Members | The Group Request Target Members parameter shall be mapped to the oneM2M-GTM Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.19 Authorization Signatures | The Authorization Signatures parameter shall be mapped to the oneM2M-AUS Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.20 Authorization Signature Request Information | The Authorization Signature Request Information parameter shall be mapped to the oneM2M-ASRI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.21 Ontology Mapping Resources | The Ontology Mapping Resources parameter shall be mapped to the oneM2M-OMR Option. The format of the oneM2M-OMR option shall be represented as a sequence of oneM2M resource identifiers separated by a '+'. EXAMPLE: The option looks as follows: oneM2M-OMR: /IN-CSE-0001/omr1+/IN-CSE-0001/omr2+… |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.22 Primitive Profile Identifier | The Primitive Profile Identifier parameter shall be mapped to the oneM2M-PRPI Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.2.4.23 M2M Service User | The M2M Service User parameter shall be mapped to the oneM2M-MSU Option. |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.3 Payload | Content parameter shall be mapped to CoAP payload. Blockwise transfers mechanism may be used to deliver large size of Content parameter which is not fit into one CoAP message. Please refer to clause 6.5 for the detail information. If Content parameter contains URI and resource representation in a response to a create r... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.2.4 Response Codes Mapping | Table 6.2.4-1 defines a mapping between oneM2M Response Status Code parameter specified in [2] and CoAP Response Code. In case of where multiple oneM2M Response Status Code parameters are mapped to a single CoAP Response Code, the Response Status Code parameter shall be specified in oneM2M-RSC Option. oneM2M TS-0008 ve... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3 Accessing Resources in CSEs | |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3.0 Introduction | This clause describes the behaviour of the CoAP layer depending on the Response Type parameter. Note that the CoAP messaging model defined in [1] applies to all message exchanges. oneM2M Requests should be sent as CoAP Confirmable (CON) messages, although an Originator can send a request as a Non-confirmable (NON) mess... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3.1 Blocking case | 1) If the Response Type parameter is configured as "blockingRequest" (blocking case), the Originator (CoAP client) shall send the oneM2M request to the Receiver (CoAP server). The oneM2M Operation parameter shall be mapped to a CoAP Method according to Table 6.2.1-1. 2) After processing the oneM2M request, the Receiver... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3.2 Non-Blocking Asynchronous case | 1) If the Response Type parameter is configured as "nonBlockingRequestAsynch" (non-blocking asynchronous case), the Originator (CoAP client) should send the oneM2M request to the Receiver (CoAP server) as a CoAP Confirmable message. This request shall be sent using the CoAP POST method, and shall include the Operation ... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3.3 Non-Blocking Synchronous case | 1) If the Response Type parameter is configured as "nonBlockingRequestSynch" (non-blocking synchronous case), the Originator (CoAP client) should send the oneM2M request to the Receiver (CoAP server) as a CoAP Confirmable message. This request shall be sent using the CoAP POST method, and shall include the Operation pa... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.3.4 Flex Blocking case | 1) If the Response Type parameter is configured as "flex blocking", the Originator (CoAP client) should send the oneM2M request to the Receiver (CoAP server) as a CoAP Confirmable message. This request shall be sent using the CoAP POST method, and shall include the Operation parameter, mapped as described in clause 6.2... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.4 Mapping rules of caching | This clause specifies how to enable or disable CoAP caching mechanism and how to use cached information. If the CoAP end point supports caching mechanism by freshness, the CoAP server shall: • set the Max-Age Option value to "0" (zero) to disable caching, in order to support complete oneM2M mapping; or oneM2M TS-0008 v... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 6.5 Usage of Blockwise Transfers | Using Block Options, large oneM2M resource representations can be fragmented and reassembled by CoAP independently of the lower layers as well as the above application. The CoAP Block1 Option shall be used to define the size of the blocks used for oneM2M request primitives and the CoAP Block2 Option shall be used to de... |
1b8e2d048ecdcc1f1241868583da88b0 | 118 108 | 7 Security Consideration | This clause applies to CoAP unicast communication only. Security for multicast communication is addressed in clause B.1. CoAP itself does not provide protocol primitives for authentication or authorization. Just as HTTP is secured using Transport Layer Security (TLS) over TCP, CoAP can be secured using Datagram TLS (DT... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 1 Scope | The present document contains the specification of the oneM2M Base Ontology. A formal OWL representation of the Base Ontology can be found at http://www.onem2m.org/ontology/Base_Ontology. The present document also specifies an instantiation of the Base Ontology in oneM2M resources which can be used for semantic annotat... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 2 References | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 3 Definition of terms, symbols and abbreviations | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1] and the following apply: annotation property: property that can be used to add information (metadata/data about data) to classes, individuals and Object/Data Properties class: OWL standard ontology language from the World Wide Web Consorti... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 3.2 Symbols | Void. |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1] and the following apply: AE Application Entity OWL Web Ontology Language SAREF Smart Appliances REFerence ontology SPARQL SPARQL Protocol and RDF Query Language |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. 5 General information on the oneM2M Base Ontology (informative) |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1 Motivation and intended use of the ontology | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1 Why using ontologies in oneM2M? | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1.1 Introduction to ontologies | In a nutshell an ontology is a vocabulary with a structure. The vocabulary applies to a certain domain of interest (e.g. metering, appliances, medicine, etc.) and it contains concepts that are used within that domain of interest, similar to the "defined terms" in clause 3.1. An ontology should: • Capture a shared under... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1.2 The purpose of the oneM2M Base Ontology | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1.2.0 Introduction | Ontologies and their OWL representations are used in oneM2M to provide syntactic and semantic interoperability of the oneM2M System with external systems. These external systems are expected to be described by ontologies. The only ontology that is specified by oneM2M is the oneM2M Base Ontology, as described in the pre... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1.2.1 Syntactic interoperability | Syntactic interoperability is mainly used for interworking with non-oneM2M devices in Area Networks. In this case an ontology - represented as an OWL file - that contains the Area Network specific types of communication parameters (names of operations, input/output parameter names, their types and structures, etc.) is ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.1.2.2 Semantic interoperability | Semantic interoperability is mainly used to describe functions provided by oneM2M compliant devices (M2M Devices). EXAMPLE: Different, oneM2M compliant types of washing machines may all perform a Function like "washing-function","drying-function", "select wash temperature", etc., however the oneM2M resources (container... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.2 How are the Base Ontology and external ontologies used? | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.2.1 Overview | This clause describes how an external ontology that is compatible with the Base Ontology can be used in a joint fashion. NOTE: Further use of external ontologies is left to subsequent releases. |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.2.2 Introduction to usage of classes, properties and restrictions | An ontology consists of Properties and Classes. Properties represent relationships, and link individuals from the specified domain (a class) to individuals from the specified range (another class). There are two main types of properties in the Base Ontology, object properties and data properties. An object property des... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.1.2.3 Methods for jointly using the Base Ontology and external ontologies | If the Base Ontology is available and the external ontologies are compatible with the Base Ontology, the Base Ontology and the external ontologies can be jointly used in the following ways. 1) Classes and properties mapping: - The names of the class and properties in different ontologies may be totally different, but t... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.2 Insights into the Base Ontology | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.2.1 General design principles of the Base Ontology | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.2.1.1 General Principle | The Base Ontology has been designed with the intent to provide a minimal number of concepts, relations and restrictions that are necessary for semantic discovery of entities in the oneM2M System. To make such entities discoverable in the oneM2M System they need to be semantically described as classes (concepts) in a - ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.2.1.2 Essential Classes and Properties of the Base Ontology | Device hasService hasFunction Operation Input refersTo Controlling Function consistsOf Operation Output exposes Function Interworked Device Thing hasThingProperty hasThingRelation Thing Property is-a is-a Variable Output DataPoint is-a is-a Function Service Operation hasOperation Command hasCommand is-a Aspect Meta Dat... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 5.2.2 Void | ETSI ETSI TS 118 112 V3.7.3 (2021-01) 18 oneM2M TS-0012 version 3.7.3 Release 3 |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6 Description of Classes and Properties | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1 Classes | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.1 Class: Thing | Thing hasThingProperty Thing Property hasThingRelation Device is-a Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Thing rdfs:Literal hasThing Annotation Figure 2: Thing Description • A Thing in oneM2M (Cla... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.2 Class: ThingProperty | Thing Property hasThingProperty Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: ThingProperty Thing Variable is-a hasMetaData (inherited) MetaData describes (inherited) Aspect Figure 3: ThingProperty Descri... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.3 Class: Aspect | Aspect hasMetaData MetaData Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Aspect Variable describes Function refersTo Figure 4: Aspect Description • An Aspect (Class: Aspect) describes the real-world aspe... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.4 Class: MetaData | MetaData Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: MetaData Variable Aspect hasMetaData hasMetaData Figure 5: MetaData Description • MetaData (Class: MetaData) contain data (like units, precision-rang... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.5 Class: Device | Device hasService Service consistsOf Thing is-a Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Device hasFunction Function Interworked Device is-a hasThingProperty Thing Property Figure 6: Device Descripti... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.6 Class: InterworkedDevice | Interworked Device Area Network Device is-a Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: InterworkedDevice isPartOf Figure 7: InterworkedDevice Description • An InterworkedDevice (Class: InterworkedDevic... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.7 Class: AreaNetwork | Area Network rdf: PlainLiteral Interworked Device Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: AreaNetwork rdf: PlainLiteral rdf: PlainLiteral netTechnology PhysicalStandard netTechnology Communication P... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.8 Class: Service | Service exposes Function Function Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Service Operation hasOperation Device hasService hasSubService Output DataPoint Input DataPoint hasInputDataPoint hasOutputD... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.9 Class: Function | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.9.0 General description | Measuring Function Service exposes Function Function Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Classes: Function, Controlling-, Measuring- Command hasCommand Controlling Function is-a Device hasFunction Aspe... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.9.1 Class: ControllingFunction | Description • A ControllingFunction (Class: ControllingFunction) represents a Function that has impacts on the real world, but does not gather data. In general a ControllingFunction has Commands (and/or Operations of its related Services) that receive input data. • E.g. a thermostat would have "temperature-adjustment" ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.9.2 Class: MeasuringFunction | Description • A MeasuringFunction (Class: MeasuringFunction) represents a Function that has no impacts on the real world, but only gathers data. In general a MeasuringFunction has Commands (and/or Operations of its related Services) that generate output data. • E.g. a temperature sensor would have "temperature-sensing"... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.10 Class: Operation | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.10.0 General description | Operation Command Legend: … an OWL class … an Object PropertyoneM2M … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Operation Operation Output Service hasOperation Operation Input hasOutput hasInput rdfs: Literal oneM2M TargetURI rdf: PlainLiteral on... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.10.1 Class: GET_InputDataPoint | Description • GET_InputDataPoint (Class: GET_InputDataPoint) is an Operation that may be offered by a Device to trigger the device to retrieve the data of an InputDataPoint (e.g. outside of the schedule when the device normally retrieves data from that DataPoint) Object Properties This Class is the domain Class of Obje... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.10.2 Class: SET_OutputDataPoint | Description • SET_OutputDataPoint (Class: SET_OutputDataPoint) is an Operation that may be offered by a Device to trigger the device to update the data of an OutputDataPoint (e.g. outside of the schedule when the device normally updates that DataPoint) Object Properties This Class is the domain Class of Object Property... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.11 Class: Command | Operation Command Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Command Operation Output Functionality hasCommand Operation Input hasOutput hasInput Input DataPoint Output DataPoint exposes Command Figure... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.12 Class: OperationInput | Operation Input Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: OperationInput Operation Command hasInput Variable is-a Figure 13: OperationInput Description • OperationInput (Class: OperationInput) describ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.13 Class: OperationOutput | Operation Output Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: OperationOutput Operation Command hasOutput Variable is-a Figure 14: OperationOutput ETSI ETSI TS 118 112 V3.7.3 (2021-01) 36 oneM2M TS-0012 ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.14 Class: InputDataPoint | Input DataPoint Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: InputDataPoint Service hasInputDataPoint Variable is-a Command exposes Command Figure 15: InputDataPoint Description • InputDataPoint (Class: ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.15 Class: OutputDataPoint | Output DataPoint Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: OutputDataPoint Service hasOutputDataPoint Variable is-a Command exposes Command Figure 16: OutputDataPoint Description • OutputDataPoint (Cl... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.16 Class: Variable | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.16.0 General description | Variable describes rdfs:Literal Aspect Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: Variable Input DataPoint rdf: PlainLiteral oneM2M Method Output DataPoint Thing Property Operation Output Operation Inp... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.16.1 Class: SimpleTypeVariable | SimpleType Variable Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: SimpleTypeVariable rdf: PlainLiteral has DataType Variable is-a isDataList xsd:boolean rdfs: Literal hasData Restriction rdfs: Literal has... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.