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 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 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.
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.
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 identifies the requirements that should characterise an ontology for the semantic conceptualisation of information related to IP traffic measurements. The requirements are obtained through the analysis of use cases spanning across a variety of related application categories and domains of interest, as well as the consideration of additional qualitative needs, such as the protection of personal data. Additional inputs arise from user experience, as well as the 'GS/MOI-010' Work Item study, entitled "Report on information models for IP traffic measurement" . The general difficulty of setting limits to an ontology, taking concepts from outside is also dealt within the present document that states MOI focus on IP traffic measurement concepts and let's side ontologies dealing with other subjects, an easy way to link. Thus a rather practical approach to define MOI ontology will be laid so that further QoS, traffic monitoring and Internet governance issues can be built on top of it by means of semantic tools.