hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.9.3 Write data to a Modbus Thermometer device | Interoperability Test Description Identifier: TD_M2M_NH_165 Objective: AE writes data into a Modbus device by updating <flexContainer> resource in Registrar CSE Configuration: M2M_CFG_10 References: oneM2M TS-0040 [16], clause 6.5.2 Pre-test conditions: • AE1 is running in Modbus IPE • AE1 has created an application re... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.10 NoDN Interworking | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.10.1 Retrieve data from a NoDN device | Interoperability Test Description Identifier: TD_M2M_NH_166 Objective: NoDN IPE reads data from a NoDN device and updates Registrar CSE with the read data Configuration: M2M_CFG_10 References: Pre-test conditions: • AE1 is running in NoDN IPE • AE1 has created an application resource <AE> on registrar CSE • AE1 has cre... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 8.10.2 Write data to a NoDN device | Interoperability Test Description Identifier: TD_M2M_NH_167 Objective: AE writes data into a NoDN device by updating <flexContainer> resource in Registrar CSE Configuration: M2M_CFG_10 References: Pre-test conditions: • AE1 is running in NoDN IPE • AE1 has created an application resource <AE> on registrar CSE • AE1 has... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 1 Scope | The present document specifies the oneM2M and AllJoyn interworking technologies that enable AllJoyn Applications and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the AllJoyn IPE is hosted and how the IPE is composed with. Clause 6 defines the archit... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 2 References | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 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... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 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... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 3 Definition of terms, symbols and abbreviations | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 3.1 Terms | For the purposes of the present document, the following terms apply: AllJoyn application: application that either produces an AllJoyn service or consumes an AllJoyn service AllJoyn consumer application: role of an AllJoyn application that consumes AllJoyn services provided by other AllJoyn applications AllJoyn producer... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 3.2 Symbols | Void. |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 3.3 Abbreviations | Void. |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 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]. |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 5 Architecture Model | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 5.1 Reference model | The architecture model followed in the present document is based on the architecture model in annex F of ETSI TS 118 101 [1] that describes how interworking between oneM2M CSEs and non-oneM2M systems using specialized Interworking Proxy application Entities (IPE). The present document describes the AllJoyn IPE that sup... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 5.2 Composition of the IPE | The AllJoyn IPE consists of AE and AllJoyn application. To provide the interworking functions to other oneM2M entities, the IPE registers to a CSE and communicate with other AllJoyn applications using AllJoyn protocols. The IPE registration is mandatory in oneM2M systems which is not defined in AllJoyn system. AllJoyn ... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6 Architecture Aspect | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.1 Introduction | oneM2M and AllJoyn have different architecture aspects (annex A oneM2M and AllJoyn technical comparison). The present document specifies the interworking functions for those differences in the following aspects: • oneM2M resource mapping structure; • AllJoyn IPE registration; • AllJoyn service discovery; • AllJoyn serv... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.2 oneM2M resource mapping structure | In this clause, the overall resource mapping structure for exposing service between AllJoyn Applications(either Producer or Consumer) and oneM2M entities is introduced. Since it is difficult to put the resource tree into a single figure that remains well-readable, the description is split up in multiple figures, In thi... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.3 AllJoyn IPE registration | To start oneM2M-AllJoyn interworking, the IPE shall perform AE registration procedure to the a CSE specified in ETSI TS 118 101 [1]. To stop using the interworking function, IPE shall perform AE de-registration procedure. The IPE shall be represented as the <AE> resource as follows. Table 6.3-1: Attribute values of IPE... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.4 AllJoyn service discovery | After the IPE registration, the IPE performs AllJoyn service discovery. The IPE may provide the following AllJoyn service discovery modes: • Advertisement-based discovery mode: This modes utilizes AllJoyn multicast service advertisement. When the IPE gets service advertisements from AllJoyn service provider application... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.5 AllJoyn service mapping | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.5.1 AllJoyn service categorization | AllJoyn services can be categorized into: • AllJoyn framework services (pre-defined by AllJoyn service framework). • App-specific services (implemented using application developer defined AllJoyn interfaces). AllJoyn framework services are pre-defined and can be sub-categorized into two: base services (e.g. Notificatio... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.5.2 AllJoyn base service mapping | The list of AllJoyn base services [i.2]: • OnBoarding. • Configuration. • Notification. • ControlPanel. • Audio Streaming. The present document specifies base services mapping for Configuration, Notification, ControlPanel. See annex C for the AllJoyn base services mapping. For Configuration, Notification or ControlPane... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.5.3 Other framework service mapping | For example, AllJoyn Lighting Services Framework mapping can be specified as described in the figure 6.2-4. However, this is not specified in the present document. |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.5.4 AllJoyn app-specific service mapping | App-specific services implement AllJoyn interface(s) defined by 3rd party developers. In the AllJoyn system, the introspection feature can be used to deliver interface information of an AllJoyn Producer Application to AllJoyn Consumer Applications. Mapping for AllJoyn app-specific services shall follow the resource map... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 6.6 AllJoyn access control mapping | AllJoyn security 1.0 feature supports authentication and encryption, but not authorization. AllJoyn security 2.0 feature supports permission management (authorization), which is similar to oneM2M access control mechanism, as well as authentication and encryption. NOTE: The present document does not specify AllJoyn secu... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7 Interworking Procedures | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.1 Introduction | The interworking procedures describe the following: • how does the IPE initially creates necessary resources for oneM2M-AllJoyn interworking (clause 7.2); • how does the IPE performs interworking between the oneM2M system and AllJoyn networks depending on the service exposure direction (clause 7.3). |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2 IPE initial configuration | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.1 Introduction | The initial configuration of the IPE consists of registration with its Registrar CSE and resource creation procedures. As part of registration, an <AE> resource is created to represent the AE part of the IPE. After that, AllJoyn-specific resources to support interaction between oneM2M AE/CSE(s) and AllJoyn Consumer and... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.2 IPE registration and AllJoyn service discovery | For the interworking, firstly the IPE shall perform IPE registration (see clause 6.3). The 'labels' attribute shall include the string "AllJoyn-IPE". ETSI ETSI TS 118 121 V2.0.1 (2020-03) 16 oneM2M TS-0021 version 2.0.1 Release 2A If the IPE is set to advertisement-based or pre-configured discovery mode (see clause 6.4... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.3 AllJoyn Service Resource creation | The AllJoyn Service Resources listed in table 7.2.3-1 shall only be created by the AllJoyn IPE. The listed resources are created as children of the <AE> resource instance representing the AllJoyn IPE according to the tree structure and resource attribute values defined in clause 6.2. Table 7.2.3-1: Resources created by... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.4 Subscription creation | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.4.1 Subscription creation by AE/CSE(s) acting as service producers | In the context of AllJoyn interworking, the AllJoyn IPE and other AE/CSE(s) providing services to AllJoyn Consumer Applications are acting as producers of services to other entities: • The AllJoyn IPE acts as a service producer towards other oneM2M AE/CSE(s) consuming the service. At the same time, the AllJoyn IPE acts... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.2.4.2 Subscription creation by entities acting as service consumers | In the context of AllJoyn interworking, the AllJoyn IPE and other oneM2M AE/CSE(s) can act as consumers of services to other entities: • In general, oneM2M AE/CSE(s) can act as service consumers towards the AllJoyn IPE which is producing services on the oneM2M side for services exposed from AllJoyn to oneM2M. At the sa... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.3 IPE interworking | |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.3.1 Introduction | When the AllJoyn Service Resources are created by the IPE or an AE/CSE exposing services to the AllJoyn side, oneM2M AE/CSE(s) trying to consume those exposed services can manipulate certain parts of those AllJoyn Service Resources in order to initiate and process the service consumption. Since an AllJoyn service is pr... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.3.2 AllJoyn services consumed by AE/CSE(s) | For an AllJoyn service that is consumed by AE/CSE(s) (i.e. direction attribute of the respective [allJoynApp] resource is indicating "allJoynToOneM2m"), the IPE performs the following: • When a new instance of an [allJoynMethodCall] resource is created, the IPE shall parse the input attribute of the [allJoynMethodCall]... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.3.3 AllJoyn services produced by oneM2M AE/CSE(s) via the IPE | For an AllJoyn service that is produced by AE/CSE(s) and consumed by AllJoyn Consumer Applications on AllJoyn devices (i.e. direction attribute of [allJoynApp] resource is "oneM2MToAllJoyn"), the IPE shall perform the following: • When the AllJoyn Producer Application on the IPE receives AllJoyn method call message, it... |
b91843ad94c9e1da80e5c8a88af6952a | 118 121 | 7.3.4 AllJoyn services addition and deletion | After the initial configuration of the IPE, new AllJoyn services can be exposed to oneM2M and existing AllJoyn services interworking can be stopped. Also services produced by oneM2M AE/CSE(s) and exposed to AllJoyn via the AllJoyn IPE can be added and removed. When a new AllJoyn service that is supposed to be exposed t... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 1 Scope | The present document specifies the binding of Mca and Mcc primitives onto the WebSocket binding. It specifies: • Procedures and message formats for operating and closing of WebSocket connections. • How request and response primitives are mapped into the payload of the WebSocket protocol. |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 2 References | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 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... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 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... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 3 Definition of terms, symbols and abbreviations | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 3.1 Terms | For the purposes of the present document, the following terms apply: oneM2M WebSocket Client (WS Client): WebSocket Client associated with an AE or a CSE capable of establishing the WebSocket connections oneM2M WebSocket Server (WS Server): WebSocket Server associated with a CSE which accepts requests to establish WebS... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 3.2 Symbols | Void. |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADN Application Dedicated Node AE Application Entity ASN Application Service Node CBOR Concise Binary Object Representation CMDH Communication Management and Delivery Handling CRUDN Create Retrieve Update Delete Notify CSE Common Services Enti... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. ETSI ETSI TS 118 120 V3.0.1 (2021-01) 7 oneM2M TS-0020 version 3.0.1 Release 3 |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 5 Overview on WebSocket Binding | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 5.1 Use of WebSocket | This binding makes use of the WebSocket protocol IETF RFC 6455 [1] to transport serialized representations of oneM2M request and response primitives over the Mca or Mcc reference points. Establishment of a WebSocket connection shall be initiated by a WebSocket client by sending a handshake to a WebSocket server as spec... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 5.2 Binding Overview | WebSocket binding may be employed for communication between any two endpoints which can be connected over the Mca, Mcc or Mcc' interface reference points supported by the oneM2M Architecture as shown in figure 6.1-1 of ETSI TS 118 101 [2]. When using the WebSocket protocol, one communication endpoint shall act as the W... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6 Protocol Binding | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.1 Introduction | The WebSocket protocol enables two-way communication between client and server even when a firewall and/or NAT are present between them. This means, once a WebSocket connection is established, request (and response) primitives can be exchanged in both directions, from the client to the server and vice versa. However, A... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2 WebSocket connection establishment | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.1 General | A WebSocket connection is opened by the client side as specified in section 4 of IETF RFC 6455 [1] with sending of a client handshake. The server responds with a server handshake. The client handshake consists of an HTTP upgrade request, along with a list of required and optional header fields. ETSI ETSI TS 118 120 V3.... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2 Client handshake | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.1 Format of request-line | The request-line of a client handshake shall begin with the method token "GET", followed by the request target "/" and the HTTP version set to "HTTP/1.1" as follows: GET / HTTP/1.1 If the client is configured to use a proxy when using the WebSocket Protocol, a connection to the proxy server shall be established prior t... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.2 Host header | The Host header shall be present in each client handshake. The Host header indicates the FQDN or IP address of the Receiver CSE of the next hop. If the originator of the client handshake is an oneM2M field entity, the host header represents the registrar CSE of the originator. When no proxy is used, the Host header sha... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.3 Upgrade header | The Upgrade header shall be present in each client handshake message with value WebSocket as follows: Upgrade: WebSocket |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.4 Connection header | The Connection header shall be present in each client handshake message with value Upgrade as follows: Connection: Upgrade ETSI ETSI TS 118 120 V3.0.1 (2021-01) 12 oneM2M TS-0020 version 3.0.1 Release 3 |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.5 Sec-WebSocket-Key header | The Sec-WebSocket-Key header shall be present in each client handshake message. The header field includes a base64- encoded representation of a random 16 bytes pattern, for example: Sec-WebSocket-Key: ud63env87LQLd4uIV20/oQ== |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.6 Sec-WebSocket-Version header | The Sec-WebSocket-Version header shall be present in each client handshake message with value 13 as follows: Sec-WebSocket-Version: 13 |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.7 Sec-WebSocket-Protocol header | The Sec-WebSocket-Protocol header shall be present in a client handshake message. It enables the client to indicate its supported application subprotocols on the server and be sure that the server agreed to support that subprotocol. It is used by the client to indicate the oneM2M Service Layer Protocol version and supp... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.8 Sec-WebSocket-Extensions header | The Sec-WebSocket-Extensions header may be used to negotiate the use of per-message compression as specified in IETF RFC 7692 [6]. If the client handshake includes the header, e.g.: Sec-WebSocket-Extensions: permessage-deflate it indicates to the server the client’s preference to apply the compression mechanism defined... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.2.9 Subprotocol names and serialization formats | The Sec-WebSocket-Protocol header in the opening handshake is used to negotiate the application protocol layered on top of WebSocket. The application protocol addressed in the present document is the Release-2 version of the oneM2M Service Layer. The oneM2M Service Layer Protocol consists of the exchange of serialized ... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3 Server handshake format | |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.1 Format of status-line | The status-line of a server handshake shall begin with the HTTP version set to "HTTP/1.1", followed by the status code and reason phrase as defined in IETF RFC 6455 [1]. When the WebSocket connection is established successfully, the status-line may look as follows: HTTP/1.1 101 Switching Protocols For the unsuccessful ... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.2 Upgrade header | The Upgrade header shall be present in each server handshake message with value WebSocket as follows: Upgrade: WebSocket |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.3 Connection header | The Connection header shall be present in each server handshake message with value Upgrade as follows: Connection: Upgrade |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.4 Sec-WebSocket-Accept header | The Sec-WebSocket-Accept header shall be present in each server handshake message. The header field shall be constructed from the Sec-WebSocket-Key value and the GUID as specified in section 4.2.2 of IETF RFC 6455 [1]. It may look e.g. as follows: Sec-WebSocket-Accept: FuSSKANnI7C/6/FrPMt70mfBY8E= |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.5 Sec-WebSocket-Protocol header | The Sec-WebSocket-Protocol header shall be present in a server handshake message. It indicates to the client that the server accepts (one of) the subprotocol(s) indicated by the client. The server compliant with this specification shall select one of the subprotocol names indicated in the Sec-WebSocket- Protocol header... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.2.3.6 Sec-WebSocket-Extensions header | If the optional Sec-WebSocket-Extensions header with value "permessage-deflate" was included in the client handshake message, the Sec-WebSocket-Extensions header with same value shall also be included into the server handshake message, if the server accepts usage of message compression, and apply message compression in... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.3 Closing WebSocket connection | Compliant with section 7 of IETF RFC 6455 [1] a WebSocket connection shall be closed by sending a Connection Close Frame (opcode x8). Both, client and server may initiate a closing handshake of an existing WebSocket connection at any time. WebSocket connections should be kept open for as long as possible considering an... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.4 Registration procedure | A oneM2M entity (AE or CSE) not yet registered to its registrar CSE needs to be preconfigured with various parameters as specified in ETSI TS 118 101 [2] and ETSI TS 118 103 [4] in order to be able to send the registration request primitive (i.e. create <AE> or create <remoteCSE> request primitive). To establish a WebS... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.5 Handling of Non-Registration Request | Registered entities (AE and CSE) are allowed to send and receive non-registration request primitives. A WebSocket connection should support any of the transfer modes defined in clause 8.2 of ETSI TS 118 101 [2], i.e. blocking requests, and non-blocking requests for both synchronous and asynchronous cases. When sending ... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 6.6 Use of proxy servers | The connection to a proxy shall be requested by sending a request-line with the method token "CONNECT", followed by the request target host and port of the WebSocket server and the HTTP version set to "HTTP/1.1" for example as follows: CONNECT WSserver.example.com:80 HTTP/1.1 ETSI ETSI TS 118 120 V3.0.1 (2021-01) 15 on... |
50cbd74f4282e252a1273b38f41e86c5 | 118 120 | 7 Security Aspects | Authentication and Transport Layer Security can be established when the oneM2M entity which hosts the WebSocket Server can be addressed with the wss URI scheme. When using the wss URI scheme, one of the Security Association Establishment Frameworks (SAEF) as defined in ETSI TS 118 103 [4] shall be applied to provide mu... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 1 Scope | The present document contains a collection of specialist technical terms, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: • ensure that the terminology is used in a consistent manner across oneM2M do... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 2 References | |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 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... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 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... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3 Definitions | |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.0 General Information | NOTE 1: Whenever in the present document a term "M2M Xyz" (e.g. M2M Application, M2M Solution, etc.) is used, then the prefix "M2M" should indicate that - unless otherwise indicated - the term identifies an entity Xyz that complies with oneM2M specifications. NOTE 2: For better readability of the present document the p... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.1 0-9 | Void. |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.2 A | Abstract Information Model: Information Model of common functionalities abstracted from a set of Device Information Models Abstraction: process of mapping between a set of Device Information Models and an Abstract Information Model according to a specified set of rules Access Control Attributes: set of parameters of th... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.3 B | Void. ETSI ETSI TS 118 111 V4.1.1 (2023-09) 9 oneM2M TS-0011 version 4.1.1 Release 4 |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.4 C | M2M Common Services: set of oneM2M specified functionalities that are widely applicable to different application domains made available through the set of oneM2M specified interfaces Common Services Entity (CSE): represents an instantiation of a set of Common Service Functions of the M2M environments. Such service func... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.5 D | Data: in the context of oneM2M the term "Data" signifies digital representations of anything NOTE: Data can or cannot be interpreted by the oneM2M System and/or by M2M Applications. See also Information. M2M Device: physical equipment with communication capabilities, providing computing and/or sensing and/or actuation ... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.6 E | Edge/Fog Deployment: oneM2M System that can be deployed as a hierarchical collection of oneM2M nodes capable of supporting the following types of functionality: • Dynamic instantiation/installation (i.e. orchestration) of oneM2M Services (i.e. CSEs, CSFs, CSs and AEs) onto the nodes in the oneM2M System in an automated... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.7 F | Field Domain: consists of M2M Devices, M2M Gateways, Sensing and Actuation (S&A) Equipment and M2M Area Networks ETSI ETSI TS 118 111 V4.1.1 (2023-09) 11 oneM2M TS-0011 version 4.1.1 Release 4 |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.8 G | M2M Gateway: physical equipment that includes, at minimum, the entities and APIs of a Middle Node Geo-fence: virtual perimeter for real-time geographical area to detect whether an object is entering into or leaving from |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.9 H | Heterogeneous Identification Service: service that supports various identification systems, and allows the mapping between identifiers, and the retrieval of the identification schema information |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.10 I | Identification [i.9]: process of recognizing an entity in a particular domain as distinct from other entities NOTE 1: The process of identification applies verification to claimed or observed attributes. NOTE 2: Identification typically is part of the interactions between an entity and the services in a domain and to a... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.11 J | Void. ETSI ETSI TS 118 111 V4.1.1 (2023-09) 12 oneM2M TS-0011 version 4.1.1 Release 4 |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.12 K | Key [i.6]: parameter used in conjunction with a cryptographic algorithm that determines its operation in such a way that an entity with knowledge of the Key can reproduce or reverse the operation, while an entity without knowledge of the Key cannot |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.13 L | LWM2M Client [i.14]: application that manages and controls things that are represented as LWM2M objects LWM2M Client Endpoint Name [i.14]: identifier for a LWM2M Client LWM2M Object [i.14]: LWM2M representation of a thing. LWM2M Objects are identified through a URI LWM2M Server [i.14]: application that manages and cont... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.14 M | Management Authority (MA): legal entity that will supervise the issuance of unique global App-IDs under given Authority IDs, and potentially contract with an organization that will issue such unique global identifiers Middle Node (MN): contains one Common Services Entity and contains zero or more Application Entities N... |
691ca80596d2f7c0e7065a3edf625456 | 118 111 | 3.15 N | Network Operator: entity (e.g. a company) that operates an Underlying Network Node: logical entity that is identifiable in the oneM2M System |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.