Standard

The IPSO Smart Object Registry registry is intended for developers that are building products based on IPSO Objects, it is not intended to be used at runtime by applications.

IPSO Smart Object Guidelines provide a common design pattern, an object model, that can effectively use the IETF CoAP protocol to provide high level interoperability between Smart Object devices and connected software applications on other devices and services.

This technical specification describes Management Objects and Generic Alerts that are needed to provide the DM Gateway functionality, as defined in [DMDICT].

This document defines an OMA DM management object (data model) to represent ZigBee devices. This ZigBee MO models specific parameters used to represent a specific ZigBee device and should be used together with GwMO TS v1.1 [GwMOTS]. This ZigBee MO is optional for any OMA DM Gateway implementation.

The scope of this document is limited to the Enabler Release Definition of Gateway Management Object (GwMO v1.1) according to OMA Release process and the Enabler Release specification baseline listed in section 5.

The scope of the Gateway Management Object architecture document is to define the architecture for the DM Gateway Management Object v1.1 enabler. This document fulfills the functional capabilities and information flows needed to support this enabler as described in the Gateway Management Object requirements document [GwMO-RD].

The OASIS AMQP TC advances a vendor-neutral and platform-agnostic protocol that offers organizations an easier, more secure approach to passing real-time data streams and business transactions. The goal of AMQP is to ensure information is safely and efficiently transported between applications, among organizations, across distributed cloud computing environments, and within mobile infrastructures. AMQP avoids proprietary technologies, offering the potential to lower the cost of enterprise middleware software integrations through open interoperability. By enabling a commoditized, multi-vendor ecosystem, AMQP seeks to create opportunities for transforming the way business is done in the Cloud and over the Internet.

This document provides a standardized IoT Reference Architecture using a common vocabulary, reusable designs and industry best practices. It uses a top down approach, beginning with collecting the most important characteristics of IoT, abstracting those into a generic IoT Conceptual Model, deriving a high level system based reference with subsequent dissection of that model into five architecture views from different perspectives.

5G EC would play a key role on low latency services and traffic off-load services in 5G era. Several prominent factors would enlarge and complex the security risks to the network layer that supports 5G EC and even bring new security challenges to the network security operation. These factors would be the flexible network architectures of 5G, the variable deployment positions of EC, the various application scenarios, different types of users' private networks and access networks, etc. The boundaries among the telecommunication networks and the private networks would be more ambiguous, and the exposure surface would be expanded. Therefore, the security requirements and measures of the network layer including both of the telecommunication networks and the private networks would be recommended as telecommunication operators enjoying the benefit of EC.

This draft Recommendation analyses the potential deployment scheme and typical application scenarios of edge computing services, specifies the security threats and requirements specific to the edge computing services and thus establishes the security framework for the operator to safeguard its applications.

ISO/PAS 19450:2015 specifies Object-Process Methodology (OPM) with detail sufficient for enabling practitioners to utilise the concepts, semantics, and syntax of Object-Process Methodology as a modelling paradigm and language for producing conceptual models at various extents of detail, and for enabling tool vendors to provide application modelling products to aid those practitioners.

This document specifies functional requirements and architecture about the following items for resource interoperability among heterogeneous IoT platforms (e.g., oneM2M, GS1 Oliot, IBM Watson IoT, OCF IoTivity, and FIWARE, etc.) through the conversion of resource identifiers (IDs) and paths (e.g., uniform resource identifier (URI)): Requirements for interoperability of resource IDs in the heterogeneous IoT platforms; Functional architecture for converting IDs and paths of resources on heterogeneous platforms; and, Functional architecture for mapping and managing resource IDs among heterogeneous platforms.