hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.16.2 Class: StructuredTypeVariable | StructuredType Variable Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: StucturedTypeVariable Variable has SubStructure is-a Figure 19: Variable ETSI ETSI TS 118 112 V3.7.3 (2021-01) 43 oneM2M TS-0012 versi... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.17 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.1.18 Class: VariableConversion | Variable Legend: … an OWL class … an Object Property … a Data Property … indicates an inheritance (sub-Class / sub-Property) is-a dataProperty objectProperty Class Class: VariableConversion Variable Conversion hasConversion convertsTo Figure 20: VariableConversion ETSI ETSI TS 118 112 V3.7.3 (2021-01) 44 oneM2M TS-0012... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2 Object Properties | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.1 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.2 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.3 Object Property: consistsOf | Description • A Device can consist of (i.e. be composed) of several (sub-) Devices. Domain Class • Device Range Class • Device |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.4 Object Property: describes | Description • A Variable describes an Aspect (a quality or kind). ETSI ETSI TS 118 112 V3.7.3 (2021-01) 45 oneM2M TS-0012 version 3.7.3 Release 3 Domain Class • Variable Range Class • Aspect |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.5 Object Property: exposesCommand | Description • A -machine interpretable- Operation or an Input/OutputDataPoint of a Service exposes a -human understandable- Command to a network. Domain Class • Operation Range Class • Command |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.6 Object Property: exposesFunction | Description • A Service exposes a Function to the network and makes it discoverable, registerable and remotely controllable in the network. Domain Class • Service Range Class • Function |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.7 Object Property: hasCommand | Description • A Function of a Device can be influenced/observed by a human user through the Commands that this Function has and that are offered to the user. Domain Class • Function Range Class • Command |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.8 Object Property: hasFunction | Description • In order to accomplish its task, a Device performs one or more Functions Domain Class • Device ETSI ETSI TS 118 112 V3.7.3 (2021-01) 46 oneM2M TS-0012 version 3.7.3 Release 3 Range Class • Function |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.9 Object Property: hasInput | Description • An Operation of a Service of the Device or a Command of a Function of the Device can have OperationInput data. Domain Class • Operation • Command Range Class • OperationInput |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.10 Object Property: hasInputDataPoint | Description • A Service of the Device can have InputDataPoints. Communicating entities write data into InputDataPoints and the Device retrieves the data at times according to an internal schedule. Domain Class • Service Range Class • InputDataPoint |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.11 Object Property: hasMetaData | Description • A Variable can have MetaData (like units, precision-ranges, etc.) Domain Class • Variable Range Class • MetaData |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.12 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.13 Object Property: hasOperation | Description • A Service communicates by means of Operations over the network to transmit data to/from other devices. Domain Class • Service ETSI ETSI TS 118 112 V3.7.3 (2021-01) 47 oneM2M TS-0012 version 3.7.3 Release 3 Range Class • Operation |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.14 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.15 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.16 Object Property: hasOutput | Description • An Operation of a Service of the Device or a Command of a Function of the Device can have OperationOutput data. Domain Class • Operation • Command Range Class • OperationOutput |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.17 Object Property: hasOutputDataPoint | Description • A Service of the Device can have OutputDataPoints. The Device writes data into OutputDataPoints at times according to an internal schedule and the communicating entities retrieves the data. Domain Class • Service Range Class • OutputDataPoint |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.18 Object Property: hasService | Description • The Functions of a Device are exposed in the network as Services of the Device. Domain Class • Device Range Class • Service |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.19 Object Property: hasSubStructure | Description • A structured Variable can be composed of (sub-)Variables. ETSI ETSI TS 118 112 V3.7.3 (2021-01) 48 oneM2M TS-0012 version 3.7.3 Release 3 Domain Class • StructuredTypeVariable Range Class • Variable |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.20 Object Property: hasThingProperty | Description • A Thing may have properties that can be described by Values. Domain Class • Thing Range Class • ThingProperty |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.21 Object Property: hasThingRelation | Description • A Thing may have relations to itself or to other Things. Domain Class • Thing Range Class • Thing |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.22 Object Property: hasConversion | Description • A Variable (in the domain of Object Property: hasConversion) can have a conversion rule (the VariableConversion in the range of Object Property: hasConversion) to convert the value range of the Variable into the value range of another Variable. Domain Class • Variable Range Class • VariableConversion |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.23 Object Property: convertsTo | Description • The conversion rule (the VariableConversion in the domain of Object Property: hasConversion) converts the value range of a given Variable (see clause 6.2.22) into the value range of another Variable (the Variable in the range of Object Property: convertsTo). Domain Class • VariableConversion ETSI ETSI TS ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.24 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.25 Object Property: isPartOf | Description • An InterworkedDevice consist a part of an AreaNetwork. Domain Class • InterworkedDevice Range Class • AreaNetwork |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.2.26 Object Property: refersTo | Description • A Function of a Device can refer to a certain Aspect (a quality or kind) that is measured or controlled by that Function. E.g. a temperature sensor would refer to the Aspect "Temperature" that it measures. Domain Class • Function Range Class • Aspect |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3 Data Properties | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.1 Data Property: hasDataType | Note that in the present document the name space identifier for: • W3C Recommendation XML Schema [6] shall be referred to using the prefix: xs Description • This Data Property specifies the data type of the SimpleTypeVariable as URI. Only those simple data types - listed below - that ETSI TS 118 104 [5] incorporated fr... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2 Data Property: hasDataRestriction | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.0 General description | Description • This Data Property specifies the restrictions on the data type of the SimpleTypeVariable. Domain Class • SimpleTypeVariable Range Datatype • rdf:PlainLiteral The Data Property "hasDataRestriction" shall always be sub-classed as one of the following specializations. The range of a sub-classed Data Property... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.1 Data Property: hasDataRestriction_minInclusive | Description • This Data Property specifies the lower bounds for numeric values (the value shall be greater than or equal to this value) allowed for the SimpleTypeVariable. It applies to: • xs:decimal • xs:integer • xs:nonNegativeInteger • xs:positiveInteger • xs:unsignedLong • xs:unsignedInt • xs:unsignedShort • xs:dat... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.2 Data Property: hasDataRestriction_maxInclusive | Description • This Data Property specifies the upper bounds for numeric values (the value shall be less than or equal to this value) allowed for the SimpleTypeVariable. ETSI ETSI TS 118 112 V3.7.3 (2021-01) 52 oneM2M TS-0012 version 3.7.3 Release 3 It applies to: • xs:decimal • xs:integer • xs:nonNegativeInteger • xs:p... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.3 Data Property: hasDataRestriction_minExclusive | Description • This Data Property specifies the lower bounds for numeric values (the value shall be greater than this value) allowed for the SimpleTypeVariable. It applies to: • xs:decimal • xs:integer • xs:nonNegativeInteger • xs:positiveInteger • xs:unsignedLong • xs:unsignedInt • xs:unsignedShort • xs:dateTime • xs:d... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.4 Data Property: hasDataRestriction_maxExclusive | Description • This Data Property specifies the upper bounds for numeric values (the value shall be less than this value) allowed for the SimpleTypeVariable. It applies to: • xs:decimal • xs:integer • xs:nonNegativeInteger • xs:positiveInteger • xs:unsignedLong • xs:unsignedInt • xs:unsignedShort • xs:dateTime • xs:dura... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.5 Data Property: hasDataRestriction_length | Description • This Data Property specifies the exact number of characters or list items allowed of the SimpleTypeVariable. Shall be equal to or greater than zero. It applies to: • xs:anySimpleType • xs:string • xs:normalizedString • xs:token • xs:language • xs:NCName • xs:hexBinary • xs:base64Binary • xs:anyURI Domain ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.6 Data Property: hasDataRestriction_minLength | Description • This Data Property specifies the minimum number of characters or list items allowed of the SimpleTypeVariable. Shall be equal to or greater than zero. It applies to: • xs:anySimpleType • xs:string • xs:normalizedString • xs:token • xs:language • xs:NCName • xs:hexBinary • xs:base64Binary • xs:anyURI Domai... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.7 Data Property: hasDataRestriction_maxLength | Description • This Data Property specifies the maximum number of characters or list items allowed of the SimpleTypeVariable. Shall be equal to or greater than zero. It applies to: • xs:anySimpleType • xs:string • xs:normalizedString • xs:token • xs:language • xs:NCName • xs:hexBinary • xs:base64Binary • xs:anyURI ETSI ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.2.8 Data Property: hasDataRestriction_pattern | Description • This Data Property specifies the restrictions of the SimpleTypeVariable to a subset of strings containing the exact sequence of characters that are acceptable. It applies to: • xs:string • xs:normalizedString • xs:token • xs:language • xs:NCName Domain Class • SimpleTypeVariable Range Datatype • xsd:strin... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.3 Data Property: hasValue | Description • This data property contains the value of the Variable if that value is part of the semantic description and is not contained in a different resource (identified by the oneM2MTargetURI data property). Storing the value of a Variable in a semantic description (i.e. as part of the RDF description in the sema... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.4 Data Property: netTechnologyCommunicationProtocol | Description • Identifies a communication protocol (e.g. ZigBee_1_0) Domain Class • AreaNetwork ETSI ETSI TS 118 112 V3.7.3 (2021-01) 56 oneM2M TS-0012 version 3.7.3 Release 3 Range Datatype • netTechnologyCommunicationProtocol rdf:PlainLiteral |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.5 Data Property: netTechnologyPhysicalStandard | Description • netTechnologyPhysicalStandardIdentification of the physical properties of an Area Network technology (e.g. IEEE_802_15_4_2003_2_4GHz). Domain Class • AreaNetwork Range Datatype • rdf:PlainLiteral |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.6 Data Property: netTechnologyProfile | Description • netTechnologyProfileIdentification of a profile (e.g. ZigBee_HA) of an Area Network technology. Domain Class • AreaNetwork Range Datatype • rdf:PlainLiteral |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.7 Data Property: oneM2MTargetURI | Description • oneM2MTargetURI (range data type: rdfs: Literal) This data property contains the URI of a oneM2M resource (<container> or <flexContainer>) through which the oneM2M instantiation of the value of the Variable can be manipulated by the communicating entity. It can contain an absolute address or an address re... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.8 Data Property: oneM2MAttribute | Description • This Data Property contains the name of the attribute of the oneM2M resource of type <flexContainer> or the child resource of the oneM2M resource of type <container> that is referenced with the oneM2MTargetURI and that stores the value of the SimpleTypeVariable: - if the resource-type of the oneM2M resour... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.9 Data Property: oneM2MMethod | Description • This data property contains a oneM2M CRUD Method through which the oneM2M instantiation of the value of the Variable can be manipulated by the communicating entity: - It contains the string "RETRIEVE" for retrieving the variable when the oneM2M resource is of type <container> or <flexContainer>. This appl... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.10 Data Property: hasThingAnnotation | Description • This data property contains a description of a Thing. NOTE: Data Property: hasThingAnnotation should be used in cases where the annotation data do not change very often and/or where they are usually not the subject of semantic operations (e.g. semantic discovery). Otherwise Object Property: hasThingProper... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.3.11 Data Property: isDataList | Description • This data property indicates if a SimpleTypeVariable contains a list if data or a single datum: - If a sub-class of class: SimpleTypeVariable specifies (i.e. is sub-class of anonymous class of:) "isDataList value TRUE" then the data type is a list (0..n) of values of the base type given by Data Property: ... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.4 Annotation Properties | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 6.4.1 Annotation Property: resourceDescriptorLink | Description • The resourceDescriptorLink annotation property is used to refer to a semanticDescriptor resource that contains more information about its subject. Its subject may be any individual and the range shall be the data literal or URI reference that represents the address of the semanticDescriptor: - For a oneM2... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 7.1 Instantiation rules for the Base Ontology | 7.1.1 Instantiation of classes of the oneM2M Base Ontology and derived external ontologies in the oneM2M System 7.1.1.1 General on instantiating classes of the Base Ontology in the oneM2M System Clause 7.1.1 describes how the Base Ontology shall be instantiated in the oneM2M System. Every class of the Base Ontology (or... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 7.1.1.2 Instantiation of individual classes of the Base Ontology | The <semanticDescriptor> resource is a child-resource of another resource type (e.g. <AE>, <container>, <contentInstance>, <flexContainer>) that may contain data of the entity that is described by the <semanticDescriptor>. As these resources describe application data oneM2M leaves the decision what resource type to use... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 7.1.2 Instantiation of Object Properties | Object properties relate an instance of domain class to an instance of the range class. They shall be instantiated in the data of the descriptor attribute of the <semanticDescriptor> resource that instantiates the domain class of the object property. If the range class of an Object Property is instantiated in a differe... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 7.1.3 Instantiation of Data Properties | Data properties shall be instantiated in the data of the descriptor attribute of the <semanticDescriptor> resource that instantiates the domain class of the data property. |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 7.1.4 Instantiation of Annotation Properties | Annotation properties may be instantiated in the data of the descriptor attribute of any <semanticDescriptor> resource. For a oneM2M instantiation of the Base Ontology the resourceDescriptorLink annotation property is used to annotate the range of object properties with the URI of the <semanticDescriptor> that contains... |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 8 Void | |
aafddb1a92a9da57dd021a69d29dbe98 | 118 112 | 9 Void | ETSI ETSI TS 118 112 V3.7.3 (2021-01) 67 oneM2M TS-0012 version 3.7.3 Release 3 Annex A (normative): OWL representation of Base Ontology The OWL representation of Base Ontology is provided in a separate document. The Base Ontology is available at the oneM2M Gitlab web page for MAS/BaseOntology: • https://git.onem2m.org... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 1 Scope | The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 2 References | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 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... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 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... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 3 Definition of terms, symbols and abbreviations | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 101 [2] and the following apply: originator: actor that initiates a Request NOTE: An Originator can either be an Application or a CSE. receiver: actor that receives the Request NOTE: A Receiver can be a CSE or an Application. resource: uniquely ad... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 3.2 Symbols | Void. |
d0275cfa012b563611bd35833e616d99 | 118 110 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 101 [2] and the following apply: ADN Application Dedicated Node ADN-AE Application Entity which resides in the Application Dedicated Node AE Application Entity ASN Application Service Node CSE Common Service Entity IN Infrastructure Node I... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 4 Conventions | The keywords "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]. |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5 Introduction | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.1 Use of MQTT | This binding makes use of MQTT to provide reliable two-way communications between two parties (AEs and CSEs). It uses the following features of MQTT: • Durable Sessions, providing Store and Forward in cases where network connectivity is not available. • MQTT's "QoS 1" message reliability level. This provides reliabilit... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2 Binding overview | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.1 Introduction | The MQTT protocol binding specifies how the Mca or Mcc request and response messages are transported across the MQTT protocol. Both communicating parties (AEs and CSEs) typically make use of an MQTT client library, and the communications are mediated via the MQTT server. There is no need for the client libraries or the... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.2 Scenarios | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.2.1 MQTT server co-located scenario | Mca ADN AE ADN AE ASN AE CSE AE CSE MN AE CSE MN AE CSE IN AE CSE M QTT Client PS1 Mca PS2 Mcc PS3 PS4 Mcc PS5 Mcc PS6 Mcc PS7 Mca M QTT Client M QTT Client Mcc Mcc’ M QTT Server M QTT Client M QTT Client M QTT Server M QTT Client M QTT Client M QTT Client M QTT Server M QTT Client ASN Figure 5.2.2.1-1: MQTT server co-... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.2.2 MQTT server independently-located scenario | Mca ADN AE ADN AE ASN AE CSE AE CSE MN AE CSE MN AE CSE IN AE CSE M QTT Client PS1 Mca PS2 Mcc PS3 PS4 Mcc PS5 Mcc PS6 Mcc PS7 Mca M QTT Client M QTT Client Mcc Mcc' M QTT Client M QTT Client MQTT Server M QTT Client M QTT Client M QTT Client M QTT Client ASN Mcc or Mca Figure 5.2.2.2-1: MQTT server independently-locat... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3 Configurations | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.1 AE to IN | This configuration, illustrated in figure 5.2.3.1-1, allows an AE to connect to an IN via MQTT. Figure 5.2.3.1-1: Using MQTT between AE and IN-CSE The MQTT server is co-located with the IN-CSE and allows connection of the ADN-AEs (typically devices) and/or IN-AEs. It can store and forward messages if there is a gap in ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.2 AE to MN | This configuration, illustrated in figure 5.2.3.2-1, allows an ADN-AE to connect to an IN via MQTT. Figure 5.2.3.2-1: Using MQTT between AE and MN-CSE This configuration is very similar to the AE-IN configuration shown in clause 5.2.3.1, except that the MQTT server is hosted on the MN rather than the IN. Onwards connec... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.3 MN to IN | This configuration, illustrated in figure 5.2.3.3-1, allows an MN to connect to an IN via MQTT. Figure 5.2.3.3-1: Mcc using MQTT between MN and IN The MQTT server is co-located with the IN-CSE and allows connection of the MNs (typically in-field gateway boxes). It can store and forward messages if there is a gap in the... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.4 AE to MN to IN | This configuration, illustrated in figure 5.2.3.4-1, is a combination of the previous two. Figure 5.2.3.4-1: Mca and Mcc both using MQTT In this configuration the two MQTT servers are independent from each other (that is to say they do not have a shared topic space). Any interactions between the ADN-AE and the IN-CSE a... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.5 AE to IN (Independent scenario) | This configuration, illustrated in figure 5.2.3.5-1, allows an AE to connect to an IN via MQTT. Figure 5.2.3.5-1: Using MQTT between AE and IN-CSE The MQTT server is an independent entity, located outside of the nodes. In order to deliver Mca messages, MQTT clients within ADN-AE/IN-AE and IN-CSE connect to the MQTT ser... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.6 AE to MN (Independent scenario) | This configuration, illustrated in figure 5.2.3.6-1, allows an ADN-AE to connect to an IN via MQTT. Figure 5.2.3.6-1: Using MQTT between AE and MN-CSE In this configuration, the MQTT server is an independent entity, located outside of the nodes. MQTT clients within ADN-AE and MN-CSE are connected to the MQTT server, an... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.7 MN to IN (Independent scenario) | This configuration, illustrated in figure 5.2.3.7-1, allows an MN to connect to an IN via MQTT. ETSI ETSI TS 118 110 V4.0.1 (2023-08) 14 oneM2M TS-0010 version 4.0.1 Release 4 Figure 5.2.3.7-1: Mcc using MQTT between MN and IN In this configuration, the MQTT server is an independent entity, located outside of nodes. Mc... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 5.2.3.8 AE to MN to IN (Independent scenario) | This configuration, illustrated in figure 5.2.3.8-1, is a combination of the previous two. Figure 5.2.3.8-1: Mca and Mcc both using MQTT In this configuration, the MQTT clients of ADN-AE and MN-CSE and IN-CSE connect to the independently located MQTT server. Any interactions such as Mca or Mcc message delivery among th... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6 Protocol Binding | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.1 Introduction | In this clause the use of MQTT is profiled and the key elements of the binding are defined: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests, and how it formulates and... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.2 Use of MQTT | MQTT includes reliability features which allow recovery from loss of network connectivity without requiring explicit involvement of the applications that are using it, however to do this it requires an underlying network protocol that provides ordered, lossless, bi-directional connections. The MQTT standard [1] allows ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.3 Connecting to MQTT | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.3.0 Introduction | In order to communicate, the two client parties (AE and CSE or CSE and CSE) shall connect to a common MQTT server. The MQTT server shall be hosted in one of the two nodes or shall exist as an independent external entity, following one of the two scenarios shown in clause 5.2. Once each party has located the address of ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.3.1 Variable header of MQTT CONNECT Packet | A variable header for the MQTT CONNECT Packet consists of four fields in the following order: Protocol Name, Protocol Level, Connect Flags and Keep Alive as shown in Figure 6.3.1-1. ETSI ETSI TS 118 110 V4.0.1 (2023-08) 16 oneM2M TS-0010 version 4.0.1 Release 4 8 15 0 7 Protocol Name (MQTT) Connect Flags Protocl Level ... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.3.2 Payload of MQTT CONNECT Packet | A payload for the MQTT CONNECT Packet is determined by the Connect Flags in the variable header. These fields may consist of Client Identifier, Will Topic, Will Message, User Name, Password. Mandatory fields to establish an MQTT session for oneM2M are: • Client Identifier Optional fields to establish an MQTT session fo... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.3.3 Application of MQTT CONNECT Packet | The following additional considerations apply: • Client Identifier: The CONNECT Packet contains a Client Identifier as described in clause 6.3.2. The Client Identifiers have to be unique at least among all clients that connect to a given MQTT server instance (this is a requirement imposed by the MQTT protocol). This co... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4 Sending and Receiving Messages | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.1 Request and Response Messages | |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.1.0 Introduction | MQTT does not have a data model to describe or constrain the content of its Application Message payloads (to that extent it is similar to a TCP socket). Mca, Mcc and Mcc' request messages shall be serialized into XML or JSON or CBOR following the serialization process defined in clause 6.5. The packet type field in Fig... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.1.1 Fixed header of MQTT PUBLISH Packet | The fixed header of the MQTT PUBLISH Packet consists of RETAIN, QoS Level, DUP flag, Packet Type, Remaining Length fields as shown in Figure 6.4.1.1-1. The QoS Level represents the QoS level of the MQTT PUBLISH Packet with possible values of 0, 1 or 2. However, since oneM2M messages are idempotent, the QoS Level should... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.1.2 Variable header of MQTT PUBLISH Packet | The variable header for the MQTT PUBLISH Packet consists of two fields in the following order: Topic Name, Packet Identifier. (MQTT) Packet Identifier 8 15 0 7 Topic Name (/oneM2M/req/Originator-ID/Receiver-ID) or (/oneM2M/resp/Originator-ID/Receiver-ID) Figure 6.4.1.2-1: Variable header for PUBLISH Packet The Topic Na... |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.1.3 Payload of MQTT Control PUBLISH Packet | The payload for the MQTT PUBLISH Packet is a oneM2M Request Message or Response Message as specified in clause 6.5. |
d0275cfa012b563611bd35833e616d99 | 118 110 | 6.4.2 Topic Name for Requests | A request is transmitted by sending it as an MQTT PUBLISH Packet to the MQTT Server. The MQTT Publish Packet uses a Topic Name that identifies both the Originator and the Receiver of the request as follows: • /oneM2M/req/<originator>/<receiver>/<type>: - "oneM2M" is a literal string identifying the topic as being used ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.