Abstract: A machine-to-machine (M2M) gateway (GW) includes reachability, addressing, and repository (RAR) capability. The GW maintains a local mapping table and local device application repository, performs data aggregation, address/name translation, provides event reporting and establishes GW reachability and wake-up time. The GW supports requests from M2M applications or other capabilities within the GW, and from a network and application (N&A) domain RAR. The GW may include an M2M device and M2M gateway management (MDGM) capability that receives management requests for an M2M device and functions as a network proxy. The MDGM accepts and processes requests from the N&A domain on behalf of the M2M device and performs management functions of the M2M device on behalf of the N&A domain. The MDGM may request the N&A domain for permission to interact with the M2M device, initiate an interaction for device management tasks with the M2M device, and report to the N&A domain.

Abstract: Methods, systems, and apparatus in a service layer environment may create, update, or delete access control policy triples whenever an access control policy (ACP) resource is created, updated, or deleted. In addition, methods address potentially frequent and unnecessary ACP triple management.

Abstract: A new semantic mashup architecture with modular design can comprise separate Semantic Mashup Profiles (SMPs), Virtual Semantic Mashup Resources (VSMRs), and Semantic Mashup Results (SMRSs). This kind of modular design greatly improves the reusability of SMPs, VSMRs, and SMRSs. In addition, this new mashup architecture leverages semantics during each mashup process, which increases the interoperability. Moreover, this new architecture essentially realizes new Semantic Mashup Service (SMS) at the service layer and consequently improves system efficiency.

Abstract: Disclosed herein are a variety of devices, methods, processes, and systems for providing enhanced service discovery. Entities in a network may send requests for service discovery to a resource directory and the resource directory may respond with the requested discovery information. This discovery information may be cached at a network node located on the path between the requesting entity and the resource directory. Upon detecting a similar discovery request, the network node may reply with the cached discovery information, forward the request to another entity based on the cached discovery information, or reply with an address or location of another entity that may have the requested discovery information.

Abstract: Distributed Service Layer Transactions (DSLTs) may be supported by a DSLT service at a service layer of a communications network to offload applications from the burden of managing the processing of DSLTs.

Abstract: Systems, methods and apparatus for managing machine-to-machine (M2M) entities are disclosed. Included herein is a method that may include implementing one or more management layers for managing M2M entities in an M2M environment. The method may also include using a plurality of management layers to manage a M2M area network, wherein the M2M area network may include one or more M2M end devices. The M2M end devices may include, for example, an M2M gateway and/or an M2M device. The management layers may include any of an application management layer, service management layer, network management layer and a device management layer. The management layers may provide any of configuration management, fault management, and performance management of the M2M entities.

Abstract: Disclosed herein are a variety of devices, methods, and systems for load balancing in the internet of things. Devices and other entities can be grouped together in a load balancing group and traffic for such devices balanced according to load balancing criteria. Groups may be discovered, created, manipulated, and deleted by various entities.

Abstract: Methods are proposed to integrate MQTT Server functionality into the oneM2M CSE, as well as to interconnect such CSE-based MQTT Servers into a network organized around a topic structure based on resource address. Methods can dynamically allocate, assign and deliver an identifier that can be used as the AE-ID by the AE, CSE and MQTT Server. The MQTT Server can be internetworked into the M2M Service Layer such that an MQTT Server is available in every Service Layer node that hosts a CSE.

Abstract: The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.

Abstract: Methods, systems, and apparatuses associated with the service layer may provide clustering management capabilities for sensor nodes in M2M/IoT SL platforms, via conventional clustering algorithm reselection and performance optimization, which may be based on service layer analytics. Clustering functionality may be adapted not only within the individual network model and optimization goals employed by each conventional clustering algorithm, but the conventional clustering algorithms themselves may be changed or reconfigured using service layer functionality. These re-configurations may be based on analytics indicating that performance of a sensor node is sub-optimal and may occur within a significantly larger time scale when compared to dynamic routing decisions on a per-message basis.

Abstract: Techniques are disclosed for Machine-to-Machine (M2M) Announce procedures that allow advertisement machine-to-machine service capabilities layer resources and subresources. Resource structures and signal flows of the various disclosed embodiments are defined.

Abstract: Systems, methods, and instrumentalities are disclosed to propagate announcement and de-announcement of a resource across one or more networks. A first entity, which may be a hosting service capability layer (SCL), may receive a request from an issuer to announce a resource. The first entity may create a representation of the resource. The representation may be referred to as an announced resource. The first entity may send an announce resource request to a second entity (e.g., an announced-to SCL), which may be registered with the first entity. The announce resource request may be sent over an mId interface. The first entity may receive a first response from the second entity over the mId interface indicating that the second entity created the announced resource.

Abstract: A method and apparatus are described for incorporating an Internet of Things (IoT) service interface protocol layer in at least one node. The format of various IoT messages used to communicate over a service interface are also described. A set of IoT service level operations may be defined in the node. The IoT service level operations may be performed on IoT information elements (IEs). The IoT service level operations may be defined in terms of various actions that are generic and applicable across industry verticals. The operations may leverage each other as sub-operations, (e.g., collaborate, share, synchronize, discover, associate, collect, aggregate, concatenate, share, relocate, invoke, delegate or surrogate). The IoT IEs may include at least one of a content IoT IE, a context IoT IE, a policy IoT IE, a decision IoT IE, an event IoT IE, a discovery IoT IE or a descriptor IoT IE.

Abstract: Methods and procedures allow devices interwork with various types of service layers by updating the device to support the protocol of the M2M/IoT service layer that is being communicated with. Devices can coordinate/initiate download of a service layer API that is compatible with the service layer the device is attempting to use. A service layer can coordinate the autonomous update of a device with the proper service layer API which allows the device to then communicate and use services supported by the service layer component to the device. A service layer can detect a device or application lacking proper service layer functionality and can trigger a management entity to update the device or application with the service layer API required such that the device can then register to the service layer and use its services. A device or application can be customized or optimized to the service layer that it is registered to and using.

Abstract: Interworking LWM2M and OMA DM protocols is disclosed. A new DDF MO enables adding LWM2M object definitions to DM Servers and Gateways. This MO allows a DM Server/Gateway to accept newly defined MOs, such as LWM2M Object definitions. New procedures are defined for registering DDF documents to the newly created DDF MO. A new registration interface is added in the GwMO protocol to allow an LWM2M Server to register end devices to a DM gateway. A protocol translation mechanism bridges the gap between non-RESTful to RESTful protocols, such as OMA DM and/or GwMO to LWM2M.

Abstract: A machine-to-machine (M2M) gateway is configured with a service capability layer (SCL) and includes a storage unit, a network interface and a processor. The storage unit stores rules for allocating resources in a resource tree. The resources include a functions collection resource of function sub-resources, at least one of which represents a function that generates contextual cues from content and a corresponding semantic description. The processor also receives requests to create new function sub-resources in the collection and creates new function sub-resources in the resource tree in response to the requests. The processor receives other requests targeting the new function sub-resources. The processor generates high-level contextual information, using the new function, based on content data and the associated semantic description of the content data received in the other requests, and routes data in the M2M network based on the generated information.

Abstract: Described herein is a Network and Application Management Service (NAMS), which is a new service for the service layer (SL). In accordance with an example embodiment, the NAMS collects, consolidates, and processes information from applications, underlying networks, and other services.

Abstract: A node availability estimation service can be used at a service layer of an M2M/IoT network. Value-added services can leverage this node availability information to improve the operation intelligence, quality of service, communication overhead as well as energy efficiency for M2M/IoT systems. A Real-time Data Collection (DC) component can collect real-time data from input sources at service layer (e.g., other existing CSFs). A Data Processing for Estimating Node Availability component (DP) can execute data processing for estimating node availability based on the data collected by DC. A Node Availability Service Provisioning component (SP) can store the estimated node availability results from DP and expose them to service clients in terms of “node availability estimation services”.

Abstract: Systems, methods and apparatus for managing machine-to-machine (M2M) entities are disclosed. Included herein is a method that may include implementing one or more management layers for managing M2M entities in an M2M environment. The method may also include using a plurality of management layers to manage a M2M area network, wherein the M2M area network may include one or more M2M end devices. The M2M end devices may include, for example, an M2M gateway and/or an M2M device. The management layers may include any of an application management layer, service management layer, network management layer and a device management layer. The management layers may provide any of configuration management, fault management, and performance management of the M2M entities.

Abstract: Service layer multicast communications management may be achieved via indication by entities of multicast capabilities during service layer registration and self-subscription by the entities to the service layer. The service layer, or a managing application in communication with the service layer, may then maintain resources for multicast configurations, dynamically create multicast groups, and notify members via their self-subscription of the entities in the groups. The service layer may then further fan-out multicast messages, thereby allowing the originator of the multicast message to access recipients in multiple underlying networks without the need to configure communications directly. Fan-out may include unicasts to entities lacking multicast capabilities. Self-subscription may also be used, for example, in granting access control to a third party application.