The purpose of oBIX (open Building Information Exchange) is to enable the mechanical and electrical control systems in buildings to communicate with enterprise applications, and to provide a platform for developing new classes of applications that integrate control systems with other enterprise functions. Enterprise functions include processes such as Human Resources, Finance, Customer Relationship Management (CRM), and Manufacturing.
This revision specifies technical corrections and clarifications to IEEE Std 802.11 for wireless local area networks (WLANS) as well as enhancements to the existing medium access control (MAC) and physical layer (PHY) functions. It also incorporates Amendments 1 to 10 published in 2008 to 2011.
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 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.
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 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 present document specifies communication between the M2M Authentication Function (MAF) and MAF clients on the reference point Mmaf and between the M2M Enrolment Function (MEF) and MEF clients on the reference point Mmef.
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 present document is to specify the minimum set of key scenarios for the Next Generation Protocols (NGP), Industry Specific Group (ISG).
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 present document outlines the motivation for the deployment of IPv6 in enterprises, the objectives, the benefits, the risks, the challenges, the technology guidelines, the different choices that arise when designing IPv6-only or dual-stack enterprise network, step-by-step process, the addressing plan, and the milestones.