Networking

The 3rd Generation Partnership Project (3GPP) is the primary body for developing technology specifications for cellular networks. It self-organises through its Working Groups coordinated by the Chairs of the Technical Specifications Groups (TSGs).

RAN WG6 (GERAN and UTRAN radio and protocol is responsible for the development of specifications dealing with GSM/EDGE Radio Access Network (GERAN) and UMTS Radio Access (UTRA) aspects, and interfaces.

Specifically RAN WG6 is responsible for:

• RF aspects of GERAN.
• GERAN Radio Layer 1 specification.
• GERAN Radio Layer 2 specification.
• GERAN Radio Layer 3 RR specification.
• A interface specification, Gb interface specification.
• Internal GERAN interface specifications such as Abis, and Ater (Channel Codec Unit-Transcoder and Rate Adapter Unit).
• GERAN functionality related to the support of location services.
• Conformance test specifications for testing of all aspects of GERAN base stations.
• Specifications for GERAN radio performance and RF system aspects.
• GERAN specific operation and maintenance specifications for the nodes in the GERAN.

RAN WG6 is also responsible for the specification of the physical layer of the Uu radio Interface for UE, UTRAN, covering both FDD and TDD modes. It carries out work related to handling of the physical layer related UE capabilities and to physical layer related parameters used in UE tests developed in TSG RAN. RAN WG6 is also responsible for UTRA aspects.

The present document provides an evaluation of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. Common Functional Entities and Reference Points are identified, as well as critical differences. New functionality will not be considered as part of this study.

The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications. The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group.

The present document is a study of interworking between oneM2M Architecture and 3GPP Rel-13 architecture for Service Capability Exposure as defined in the release 13 version of ETSI TS 123 682 [i.5]. The key objective and value is analyzed and described. The document also investigates the potential solution in oneM2M by evaluating the existing technical solutions.

The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements.

It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M.

The present document collects the use cases of the industrial domain and the requirements needed to support the use cases collectively. In addition it identifies the necessary technical work needed to be addressed while enhancing future oneM2M specifications.

The present document allows application developers to describe the status of devices as resources on oneM2M-based platform in various ways. Thus different application developers can create different resource trees even when they build the same kinds of applications. Moreover when handling the same kinds of devices from different vendors on M2M platforms, application developers may create disunited resource trees without common information model.

The present document provides technical solutions for oneM2M authorization architecture, authorization procedures and access control policies. The present document also gives evaluations of these proposed technical solutions.

ETSI TS 118 103 [i.2] only defines a high level authorization architecture that describes its major components and general authorization procedure. The objective of the present document is to provide candidate security solutions related to authorization architecture, authorization procedures and access control policies. The present document provides security solutions in the following three aspects:

• Detailed design of authorization architecture: This part investigates the interfaces among authorization components (e.g. procedures and parameters), how these components could be distributed in different oneM2M entities (i.e. different CSEs), and how to implement Role Based Access Control (RBAC) and token based access control.

• Supporting user specified access control policies: This part investigates how the oneM2M authorization system could be an extensible system that can support user-defined access control mechanisms and/or access control policy languages.

• Investigating existing access control policy languages: This part investigates if some standardized access control policy languages could become oneM2M recommended access control policy description languages

The present document provides options and analyses for the security features and mechanisms providing end-to-end security and group authentication for oneM2M.

The scope of this technical report includes use cases, threat analyses, high level architecture, generic requirements, available options, evaluation of options, and detailed procedures for executing end-to-end security and group authentication.

The present document specifies the interworking technologies for oneM2M and OIC interworking using the architecture identified in annex F of ETSI TS 118 101 [2] for the following scenario:

• Interworking using oneM2M Resource Types for transparent transport of encoded OIC Resources and commands in oneM2M Resource Types between OIC Devices and M2M Applications.

The Management Information Base (MIB) module specifications for IEEE Std 802.3, also known as Etherenet, are contained in this standard. It includes the Structure of Management Information Version 2 (SMIv2) MIB module specifications formerly produced and published by the Internet Engineering Task Force (IETF), and the Guidelines for the Definition of Managed Objects (GDMO) MIB modules formerly specified within IEEE Std 802.3, as well as extensions resulting from amendments to IEEE Std 802.3. The SMIv2 MIB modules are intended for use with the Simple Network Management Protocol (SNMP), commonly used to manage Etherenet.

In this amendment to IEEE Std 802.15.4TM-2011, a physical layer for IEEE 802.15.4 in the 2360 MHz to 2400 MHz band which complies with Federal Communications Commission (FCC) MBAN rules is defined. Modifications to the MAC needed to support this new physical layer are also defined in this amendment.

The present document specifies the structure of the Network Service Descriptor (NSD) file archive and the naming conventions for the different files it contains, fulfilling the requirements specified in ETSI GS NFV-IFA 014 [1] for an NSD file structure.