The present document aims to:
• describe the characteristics of the architecture of a Low Throughput Network
• illustrate the applicability of LTN in industrial communication
• highlight the specificity of LTN deployment
The document aims to define the protocols and interfaces of LTN systems. It goes along with the document GS LTN 002 [5] on LTN functional architecture.
The scope of the present document is to specify the minimum set of key scenarios for the Next Generation Protocols (NGP), Industry Specific Group (ISG).
The present document provides an overview of existing identity oriented protocols, mapping systems and proposes next generation mobility with a generic and resilient identity services infrastructure.
The scope of the Standard is to specify the minimum set of key requirements for the Next Generation Protocols (NGP), Industry Specific Group (ISG). The present document addresses requirements in the following areas:
• Business Case and Techno-Economics
• Migration
• General Technical Requirements
• Addressing
• Security
• Mobility
• Multi-Access Support (including FMC)
• Context Awareness
• Performance (including Content Enablement)
• Network Virtualisation
• IoT Support
• Energy Efficiency
• e-Commerce
• MEC
• Mission Critical Services
• Drones and Autonomous Vehicles and Connected Vehicles
• Ultra Reliable Low Latency Communications
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 describes and collects the state-of-art of the existing technologies on management capability, evaluates if the technologies can match the requirements defined in oneM2M, analyzes how the technologies can leverage the design of the architecture of oneM2M.
The OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) Technical Committee works closely with the AMQP TC to advance a wire-level messaging protocol that offers organizations an efficient, reliable approach to passing real-time data and business transactions. AMQP provides a platform-agnostic method for ensuring information is safely transported between applications, among organizations, within mobile infrastructures, and across the Cloud.
The present document specifies the oneM2M and AllJoyn® interworking technologies that enable AllJoyn® Applications and oneM2M entities produce/consume services.
The present document specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the device's AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation.
The present document describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model.
The present document discusses Quality of Service (QoS) aspects of services related to the Internet of Things (IoT) ecosystem from an end-to-end perspective; a strict end-user, service-oriented point of view. Here, end-to-end is understood as "from a service user/terminal/provider to a service user/terminal/provider".
The discussion deals with two questions. The first question is if the existing framework for QoS parameter definitions and methodologies is sufficient to also include the IoT angle of view. The second question is if the existing portfolio of QoS parameters needs extensions or adaptations.
