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 documents;  provide a reader with convenient reference for technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here, or created internally...

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 Requests. 4) How that Receiver can formulate and transmit a Response. 2 References 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...

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 (successful/unsuccessful) to HTTP response codes. Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (oneM2M TS-0004) for data types. 2 References 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...

1 Scope The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as ‘RESTful CoAP binding’. The scope of this specification is (not limited to as shown below): – Binding oneM2M primitives to CoAP messages – Binding oneM2M Response Status Codes to CoAP Response Codes – Defining behaviour of a CoAP Client and Server depending on oneM2M parameters 2 References 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...

1. Scope The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181i2 Data Model [6] . 2 References 2.1 Normative references The following referenced documents are necessary, partially or totally, for the application of the present document. Their use in the context of this TS is specified by the normative statements that are referring back to this clause. [1] oneM2M TS-0001:“Functional Architecture”. [2 oneM2M TS-0004:“Service Layer Core Protocol Specification”. [3] oneM2M TS-001 1:“Definitions and Acronyms”. [4] BBF:“TR-069 CPE WAN Management Protocol” Issue: 1 Amendment 5, November 2013. [5] BBF:“TR- 106 Data Model Template...

1 Scope The present document contains an informative functional role model and normative technical requirements for oneM2M. 2 References 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 documents are necessary for the application of the present document. [1] 3GPP TS 22.368: “Service requirements for Machine-Type Communications (MTC); Stage 1”. [2] oneM2M TR-0008: “Security Analysis”. 2.2 Informative references References are either specific (identified by...

This Standard addresses the requirements associated with the planning, architecture, design, integration, and operation of sustainable information communications technology (ICT) systems, with a goal to reduce the long term environmental impact associated with ICT deployment. 2 NORMATIVE REFERENCES The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers...

1.1 S COPE This standard establishes telephone audio performance requirements, measurement methods, and test procedures for telephones with high receive gain and control of the receive frequency spectrum. This standard addresses audio performance in narrowband and wideband telephony frequencies using scientific methods and techniques derived or adapted from current telephone measurement standards for handsets and speakerphones.  Narrowband is defined as the frequency range between 300 and 3400 Hz.  Wideband is defined as the frequency range between 100 and 7000 Hz 1.2 C OMPLIANCE TO H EARING L OSS C ATEGORIES This standard provides performance requirements for three levels...

As compared to a HRPD cell, an extended cell is characterized by increased radio path loss between the base station and a user terminal, increased radio path delay between the base station and a user terminal, a larger geographical cell coverage area and highly overlapping coverage with adjacent extended cells. Extended cell HRPD (or xHRPD) is considered as an enhancement to the HRPD standards [2] and [3]. An example of xHRPD application is serving as a component of integrated satellite terrestrial network. The terrestrial network component (e.g., a HRPD cellular network) provides economical and high quality services to areas of...

These technical requirements form a compatibility standard for cdma2000 extended cell high rate packet data systems. These requirements ensure that a compliant access terminal can obtain service through any access network conforming to this standard. These requirements do not address the quality or reliability of that service, nor do they cover equipment performance or measurement procedures. This specification is primarily oriented toward requirements necessary for the design and implementation of access terminals. As a result, detailed procedures are specified for access terminals to ensure a uniform response to all access networks. Access network procedures, however, are specified only to the...