hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.2.1.2 oneM2M Service Layer Communication | Table 6.2.1.2-1 shows the IUTs for oneM2M reference architecture as defined in ETSI TS 118 001 [1]. Table 6.2.1.2-1: IUTs for oneM2M IUT (node) Entities Interfaces Notes ASN Application Entity (AE) Mca Common Services Entity (CSE) Mca, Mcc, Mcn ADN Application Entity (AE) Mca MN Application Entity (AE) Mca Common Servi... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.2.2 Identification of the Reference Points | This clause illustrates candidate reference points (RPs) where test systems can be connected in order to test conformance of oneM2M protocols (IUTs) with oneM2M base standards. Table 6.2.2-1: RPs for oneM2M RP Identifier RP Type oneM2M node- entity oneM2M node- entity Network RP-oneM2M-1 Mca ASN-AE ASN-CSE RP-oneM2M-2 ... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3 Development of Conformance Test Specifications | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.1 Implementation Conformance Statement (ICS) | The purpose of an ICS is to identify those standardized functions which an IUT shall support, those which are optional and those which are conditional on the presence of other functions. It helps to provide a means for selection of the suite of tests which will subsequently be developed. In addition, the ICS can be use... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2 Test Suite Structure & Test Purposes (TSS&TP) | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.1 Introduction | A test purpose is a prose description of a well-defined objective of testing. Applying to conformance testing, it focuses on a single conformance requirement or a set of related conformance requirements from the base standards. Several types of presentation of the test purposes exist. These presentations are combining ... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.2 Test Suite Structure | Defining the test suite structure consists of grouping the test purposes according to different criteria like for instance: • The functional groups and sub-groups of procedures in the base standard, from which the requirement of the test purpose is derived. • The category of test applying to the test purposes, for inst... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3 Test Purpose | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.1 Introduction | A test purpose is an informal description of the expected test behaviour. As such it is written in prose. When needed to clarify the TP, it is helpful to add some graphical presentations, mainly tables, and include message sequence charts. In order to increase the readability of the TP, the following two recommendation... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.2 TP identifier | The TP identifier identifies uniquely the test purposes. In order to ensure the uniqueness of the TP identifier, it follows a naming convention. The more useful and straightforward naming convention consists of using the test suite structure, to form the first part of the TP identifier. Then the final part consists of ... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.3 Test objective | The test objective clearly indicates which requirement is intended to be tested in the test purpose. This part eases the understanding of the TP behaviour. This also eases the identification of the requirements, which were used as a basis for the test purpose. It is recommended to limit the length of the test objective... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.4 Reference | In the reference row, the TP writer indicates, in which clauses of the protocol standards, the requirement are expressed. This information is critical, because it justifies the existence and the behaviour of the TP. The reference row may refer to several clauses. When the clause containing the requirement is big (for i... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.5 ICS selection | The ICS selection row contains a Boolean expression, made of ICS parameters. It is recommended to use ICS acronym, which clearly identify the role of the ICS. A mapping table is included in the TP document to link the ICS acronym with its corresponding reference in the ICS document. Table 6.3.2.3.5-1: Example of pre-de... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.2.3.6 TP behaviour | First of all, the following global rules apply, when writing the behaviour description: • The behaviour description is written in an explicit, exhaustive and unambiguous manner. • The behaviour description only refers to externally observable test events (send/receive PDUs, timer, counters, etc.) or to events or states... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3 Abstract Test Suite (ATS) | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.1 Abstract protocol tester | An abstract protocol tester presented in figure 6.3.3.1-1 is a process providing the test behaviour for testing an IUT. Thus it will emulate a peer IUT of the same layer/the same entity. This type of test architecture provides a situation of communication which is equivalent to real operation between real oneM2M system... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.2 TTCN-3 test architecture | This clause illustrates how to implement the abstract test architecture presented in clause 6.3.3.1 in a functional test environment. There are many possibilities to implement this abstract test architecture using different types of programming languages and test devices. This oneM2M testing framework uses TTCN-3 being... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.3 Test configurations | The test suite uses test configurations in order to cover the different test scenarios. In following 2 examples, the IUT is tested by the test system simulating an AE in CF01 (no hop configuration) or an AE and a CSE in a CF02 (single hop configuration). EXAMPLE 1: Test configuration 1 (CF01): EXAMPLE 2: Test configura... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.4 ATS conventions | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.4.1 Importing XSD definition | The oneM2M set of standards uses XSD for the definition of the message types. The process for using XSD data types and values in TTCN-3 modules consists of importing the existing XSD productions. For this purpose, the TTCN-3 "import from" statement should be used, in association with the "language" statement. |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.4.2 The TTCN-3 naming conventions | TTCN-3 core language contains several types of elements with different rules of usage. Applying naming conventions aims to enable the identification of the type when using specific identifiers according to the type of element. For instance, a variable declared in a component has different scoping rules than a local var... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.3.5 Verification of TTCN-3 | Before release for use by industry and external organisations (for example Certification Bodies) the TTCN-3 should be Verified for correct operation against a number of IUTs. A list of all TTCN-3 test cases and their Verification status is maintained in the associated ATS. An example table to be used to record this sta... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 6.3.4 Implementation eXtra Information for Testing (IXIT) | The ICS contains base specification dependent information. To derive executable tests this is insufficient; also information about the IUT and its environment shall be supplied. Such information is called Implementation eXtra Information for Testing (IXIT). An IXIT proforma identifies which ICS items are to be tested a... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7 Interoperability testing | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.1 Introduction | Interoperability testing can demonstrate that a product will work with other like products: it proves that end-to-end functionality between (at least) two devices is as required by the standard(s) on which those devices are based. In that context, the system under test is made of the combination of different devices un... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2 Basic Concepts | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.1 Overview | Interoperability testing consists simply in inter-operating different vendor implementations, which are supposed to be inter-operable according to the expected conformance with the base standards. Even if this process looks easy, it requires specifying a complete environment enabling to operate vendors implementation a... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.2 System Under Test (SUT) | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.2.0 Introduction | In the context of interoperability testing, the System Under Test (SUT) is made of a number of Devices Under Test (DUTs) coming from different suppliers. Depending on the complexity of the end-to-end system, the overall amount of DUTs under study, and the interactions among them, it might be advisable to define differe... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.2.1 Devices Under Test (DUT) | In the context of oneM2M, a Device Under Test is a combination of software and/or hardware items which implement the functionality of oneM2M and interact with other DUTs via one or more reference points. NOTE: When using Interoperability Test Specifications in a certification scheme, the notion of Qualified Equipment (... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.2.2 Test interfaces | The interfaces that are made available by the SUT to enable the testing are usually known as the test interfaces. These interfaces are accessed by the test drivers to trigger and verify the test behaviour, Other interfaces offered by the SUT can be used for monitoring, log analysis, etc. In the simplest case, the test ... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.3 Test Environment | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.3.0 Introduction | Interoperability testing involves control and observation at the functional (rather than protocol) level. The Test Environment is the combination of equipment and procedures enabling testing the interoperability of the DUTs. Entities in the test environment access the different Devices Under Test via the Test Interface... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.3.1 Test Descriptions | A test description provides the detailed set of instructions (or steps) that need to be followed in order to perform a test. Most often, interoperability tests are described in terms of actions that can be performed by the user(s) of the endpoint device(s). In the case where the test is executed by a human operator, te... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.2.3.2 Test drivers | The test driver realizes the steps specified in a test description at one specific test interface. Testing efficiency and consistency can be improved by implementing the role of the test driver via an automatic device programmed to carry out the specified test steps. This approach may require standardized test interfac... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3 Development of Interoperability Test Specifications | |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.1 Overview | The main steps involved in the process of developing an interoperability test specification are as follows: • describing a generic architecture for the System Under Test; • defining test scenarios; • identifying the test bed architecture; • collecting requirements in the Interoperable Features Statement (IFS); • defini... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.2 Generic SUT Architecture | A generic SUT architecture provides an abstract framework within which any specific SUT configuration should fit in. The starting point for defining a generic SUT architecture is most often the functional architecture described in the base standards, in combination with pragmatic input on how the industry and open sour... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.3 Test scenarios | In oneM2M, a large number of use cases is identified. In order to perform interoperability tests, EUTs supporting the same use cases are required. This classification of interoperability tests is given by test scenarios. A test scenario thus selects a set of use cases and is restricted to a sub-set of the full function... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.4 Test bed architecture and Interfaces | A test bed architecture is an abstract description of logical entities as well as their interfaces and communication links involved in a test. It describes all implementation (DUTs) involved in the interoperability tests, together with the set of equipment and procedures required to enable implementations to execute th... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.5 Interoperable Functions Statement (IFS) | An "Interoperable Functions Statement" (IFS) identifies standardized functions that an DUT shall support. These functions are either mandatory, optional or conditional (depending on other functions). In addition, the IFS can be used as a proforma by a manufacturer to identify the functions an DUT will support when inte... |
9f25db803a4d03590d7c1361d4bb9675 | 118 115 | 7.3.6 Test Descriptions (TD) | A "Test Description" (TD) is a well detailed description of a process that pretends to test one or more functionalities of an implementation. Applying to interoperability testing, these testing objectives address the interoperable functionalities between two or more vendor implementations. In order to ensure the correc... |
5884f20096a929755c7228996f24adba | 118 109 | 1 Scope | The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successfu... |
5884f20096a929755c7228996f24adba | 118 109 | 2 References | |
5884f20096a929755c7228996f24adba | 118 109 | 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 reference document (including any amendments) applies. The following referenced docu... |
5884f20096a929755c7228996f24adba | 118 109 | 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 reference document (including any amendments) applies. The following referenced docu... |
5884f20096a929755c7228996f24adba | 118 109 | 3 Definition of terms, symbols and abbreviations | |
5884f20096a929755c7228996f24adba | 118 109 | 3.1 Terms | Void. |
5884f20096a929755c7228996f24adba | 118 109 | 3.2 Symbols | Void. |
5884f20096a929755c7228996f24adba | 118 109 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [Error! Reference source not found.] apply and the following apply: HTTP Hyper Text Transfer Protocol TLS Transport Layer Security URI Uniform Resource Identifier |
5884f20096a929755c7228996f24adba | 118 109 | 4 Conventions | The keywords "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. |
5884f20096a929755c7228996f24adba | 118 109 | 5 Overview on HTTP Binding | |
5884f20096a929755c7228996f24adba | 118 109 | 5.0 Overview | HTTP binding specifies the equivalence between oneM2M request and response primitives and HTTP request and response messages, respectively. This clause provides a brief overview on the mapping relationship between oneM2M and HTTP message parameters. This clause describes how oneM2M request/response primitives can be ma... |
5884f20096a929755c7228996f24adba | 118 109 | 5.1 Introduction | Figure 5.1-1 illustrates an example oneM2M system configuration and its correspondence to an HTTP-based information system if HTTP binding as defined in this specification is applied. The upper diagram in figure 5.1-1 shows with solid line arrows the flow of a request primitive originating from an AE which is registere... |
5884f20096a929755c7228996f24adba | 118 109 | 5.2 Request-Line | The HTTP method of a request message is mapped to the Operation parameter, and vice-versa. At the message originator side the HTTP Request-Target is derived from the To parameter of the request primitive, including a query string which carries other specific primitive parameters. HTTP-Version is specified in clause 6. |
5884f20096a929755c7228996f24adba | 118 109 | 5.3 Status-Line | HTTP Version is specified in clause 6. The Status-Code of HTTP response messages is derived from the Response Status Code parameter of the response primitive. The Reason-Phrase is not applicable to oneM2M systems and is omitted. ETSI ETSI TS 118 109 V4.4.1 (2023-12) 9 oneM2M TS-0009 version 4.4.1 Release 4 |
5884f20096a929755c7228996f24adba | 118 109 | 6 HTTP Message Mapping | |
5884f20096a929755c7228996f24adba | 118 109 | 6.1 Introduction | Mapping between oneM2M primitives and HTTP messages shall be applied in the following four use cases: 1) Mapping of request primitive to HTTP request message at the request originator (HTTP client). 2) Mapping of HTTP request message to request primitive at the request receiver (HTTP server). 3) Mapping of response pri... |
5884f20096a929755c7228996f24adba | 118 109 | 6.2 Parameter Mappings on Request-Line | |
5884f20096a929755c7228996f24adba | 118 109 | 6.2.1 Method | The HTTP 'Method' shall be derived from the Operation request primitive parameter of the request primitive. Table 6.2.1-1: HTTP Method Mapping oneM2M Operation HTTP Method Create POST Retrieve GET Update PUT Delete DELETE Notify POST At the Receiver, an HTTP request message with POST method shall be mapped either to a ... |
5884f20096a929755c7228996f24adba | 118 109 | 6.2.2 Request-Target | |
5884f20096a929755c7228996f24adba | 118 109 | 6.2.2.1 Path component | The path component of the origin-form HTTP Request-Target shall be interpreted as the mapping of the resource identifier part of the To request primitive parameter. If the HTTP message is sent directly to the next hop CSE, the origin-form of Request-Target shall be employed (see clause 5.3.1 of IETF RFC 7230 [1]). The ... |
5884f20096a929755c7228996f24adba | 118 109 | 6.2.2.2 Query component | The query component (e.g. query-string) may include the optional primitive parameters listed in table 6.2.2.2-1 compliant with IETF RFC 7230 [1]. Each applicable request primitive parameters and elements of Filter Criteria parameter shown in table 6.2.2.2-1 shall be represented as pair of field-name and value in query-... |
5884f20096a929755c7228996f24adba | 118 109 | 6.2.3 HTTP-Version | This specification defines binding compliant with HTTP 1.1 [1]. The HTTP version field in HTTP request messages shall be set to "HTTP/1.1". |
5884f20096a929755c7228996f24adba | 118 109 | 6.3 Status-Line | |
5884f20096a929755c7228996f24adba | 118 109 | 6.3.1 HTTP-Version | The HTTP version field in HTTP response messages shall be set to "HTTP/1.1". |
5884f20096a929755c7228996f24adba | 118 109 | 6.3.2 Status-Code | The Response Status Code parameter of response primitives shall be mapped to the HTTP Status-Code. Since the Response Status Code parameter values have been defined with more detailed information than HTTP status codes, one or more Response Status Code value may be mapped to the same HTTP Status-Code. The original Resp... |
5884f20096a929755c7228996f24adba | 118 109 | 6.3.3 Reason-Phrase | The Reason-Phrase shall be omitted in HTTP response messages. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4 Header Fields | |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.0 Introduction | The header fields listed in this clause shall be supported by all entities of the oneM2M system when using HTTP binding. Any other unrecognized HTTP headers shall be ignored by the HTTP client and server. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.1 Host | The Host header shall be present in each HTTP request message. ETSI ETSI TS 118 109 V4.4.1 (2023-12) 17 oneM2M TS-0009 version 4.4.1 Release 4 While the Request-Target indicates a target resource on the Hosting CSE, the Host header indicates the FQDN or IP address of the Receiver CSE of the next hop in multi-hop commun... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.2 Accept | The Originator may use the Accept header to indicate which media types are acceptable for the response. The Accept header shall be mapped to a set of media types among "application/xml", "application/json", "application/cbor" or the oneM2M defined media types defined in clause 6.7 of ETSI TS 118 104 [3]. Note that some... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.3 Content-Type | Any HTTP request or response containing message-body shall include the Content-type header set to one of "application/xml", "application/json", or the oneM2M defined media types defined in clause 6.7 of ETSI TS 118 104 [3]. Content-Type of the HTTP response should be chosen by the Hosting CSE considering the Accept hea... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.4 Content-Location | The Content-Location header of the HTTP response to a Create request shall be set to the URI of the created resource, if this URI is present in the Content parameter of the Create response primitive. See clause 7.3.3.12 "Create a success response" in ETSI TS 118 104 [3]. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.5 Content-Length | If message-body is included into HTTP request or response messages, the Content-Length header shall be included indicating the length of the message-body in octets (8-bit bytes). |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.6 Etag | A response primitive sent in reply to a resource retrieval request primitive should include an Etag header [Error! Reference source not found.] in combination with the resource representation in the HTTP message body. Etag facilitates the use of conditional requests (i.e. using the if-match and if-none-match HTTP heade... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.7 X-M2M-Origin | The X-M2M-Origin header shall be mapped to the From parameter of request and response primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.8 X-M2M-RI | The X-M2M-RI header shall be mapped to the Request Identifier parameter of request and response primitives and vice versa. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.9 Void | |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.10 X-M2M-GID | The X-M2M-GID header shall be mapped to the Group Request Identifier parameter of request primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.11 X-M2M-RTU | The X-M2M-RTU header shall be mapped to the notificationURI element of the Response Type parameter of request primitives and vice versa, if applicable. If there are more than one value in the element, then the values shall be combined with "&" character. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.12 X-M2M-OT | The X-M2M-OT header shall be mapped to the Originating Timestamp parameter of request and response primitives, and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.13 X-M2M-RST | The X-M2M-RST header shall be mapped to the Result Expiration Timestamp parameter of request and response primitives, and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.14 X-M2M-RET | The X-M2M-RET header shall be mapped to the Request Expiration Timestamp parameter of request primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.15 X-M2M-OET | The X-M2M-OET header shall be mapped to the Operation Execution Time parameter of request primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.16 X-M2M-EC | The X-M2M-EC header shall be mapped to the Event Category parameter of request and response primitives, and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.17 X-M2M-RSC | The X-M2M-RSC header in a HTTP response message shall be mapped to the Response Status Code parameter of response primitives and vice versa (e.g. Response Status Code 4000 and 4102 are mapped to HTTP Status Code 400 in table 6.3.2-1). ETSI ETSI TS 118 109 V4.4.1 (2023-12) 19 oneM2M TS-0009 version 4.4.1 Release 4 |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.18 X-M2M-ATI | The X-M2M-ATI header in a HTTP response message shall be mapped to the Assigned Token Identifiers parameter of response primitives and vice versa. The format of the X-M2M-ATI header shall be represented as a sequence of lti-value:tkid-value pairs separated by a colon ":' and multiple pairs separated by '+' character. E... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.19 Authorization | If a request primitive includes a Tokens parameter it shall be mapped to the Authorization header. The Tokens primitive parameter is represented as a space separated list of JSON Web Signature (JWS) and JSON Web Encryption (JWE) strings in Compact Serialization format of datatype m2m:dynAuthJWT as defined in clause 6.3... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.20 X-M2M-CTS | The X-M2M-CTS header shall be mapped to the Content Status parameter of response primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.21 X-M2M-CTO | The X-M2M-CTO header shall be mapped to the Content Offset parameter of response primitives, and vice versa, if applicable. ETSI ETSI TS 118 109 V4.4.1 (2023-12) 20 oneM2M TS-0009 version 4.4.1 Release 4 |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.22 X-M2M-RVI | The X-M2M-RVI header shall be mapped to the Release Version Indicator parameter of request and response primitives and vice versa. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.23 X-M2M-VSI | The X-M2M-VSI header shall be mapped to the Vendor Information parameter of request and response primitives and vice versa. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.24 X-M2M-AS | If a request primitive includes an Authorization Signature parameter, it shall be mapped to the X-M2M-AS header. The Authorization Signature primitive parameter is represented as a space separated list of URL-safe base64 encoded (base64url)) strings of datatype m2m:signatureList as defined in clause 6.3.3 of ETSI TS 11... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.25 X-M2M-ASRI | The X-M2M-ASRI header in a HTTP response message shall be mapped to the Authorization Signature Request Information parameter of response primitives and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.26 X-M2M-OMR | The X-M2M-OMR header shall be mapped to the Ontology Mapping Resources parameter of request primitives and vice versa, if applicable. The format of the oneM2M-OMR header shall be represented as a sequence of oneM2M resource identifiers separated by a '+'. EXAMPLE: The header looks as follows: oneM2M-OMR: /IN-CSE-0001/o... |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.27 X-M2M-MSU | The X-M2M-MSU header shall be mapped to the M2M Service User parameter of request and response primitives, and vice versa, if applicable. |
5884f20096a929755c7228996f24adba | 118 109 | 6.4.28 X-M2M-PRPI | The X-M2M-PRPI header shall be mapped to the Primitive Profile Identifier parameter of request primitives and vice versa. ETSI ETSI TS 118 109 V4.4.1 (2023-12) 21 oneM2M TS-0009 version 4.4.1 Release 4 |
5884f20096a929755c7228996f24adba | 118 109 | 6.5 Message-body | Message-body shall be mapped to the Content parameter of request and response primitives, and vice versa, if applicable. This applies to the Content parameter of all primitives with the following exceptions: 1) For partial Retrieve request primitives. Attributes contained in the Content parameter of Retrieve request pr... |
5884f20096a929755c7228996f24adba | 118 109 | 6.6 Message Routing | HTTP request and response message routing shall be performed as described in HTTP/1.1 [1]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.