Abstract: Methods and systems may be used to synchronize time across multiple IoT related entities, such as a network of resource constrained sensor and actuator type devices, IoT gateways, IoT cloud services, or IoT applications.

Abstract: Profile based services and content can assist with the backward and forward compatibility of conventional service layers or the like. Using a profile to manage content and access to services offered may reduce the overhead or processing associated with providing those value added services by service layers. A service layer may be an M2M/IoT Service Layer, and compatibility may refer to compatibility regarding different versions or releases of the oneM2M Service Layer.

Abstract: The present application is directed to a computer-implemented apparatus for negotiating service layer attributes. The apparatus includes a non-transitory memory including instructions stored thereon for a negotiation service layer for negotiating a service attributes. The apparatus also includes a processor, operably coupled to the non-transitory memory. The processor is configured to perform the instruction of reviewing a negotiable service layer attribute received from a negotiatee. The processor is also configured to perform the instruction of sending a negotiation request to the negotiatee based upon the reviewed attribute. The processor is also configured to perform the instruction of receiving an offered suggestion from the negotiatee. Another aspect of the application is directed to a networked system including a computer-implemented negotiatee and a computer-implemented negotiator for negotiating service layer attributes.

Abstract: Mechanisms for discovering ad hoc Service Layer Entities (aSLEs) either deployed in ad hoc or switched from normal operation mode to ad hoc mode can support an IoT service in a distributive self-organized system.

Abstract: Various mechanisms are disclosed for a service domain charging system that can interact with underlying networks. A service domain charging architecture is defined with several logical functions. Service-based charging types may be and applied to existing event, session, online, and offline charging mechanisms. Service domain charging messages may be exchanged over the X, Y, Z reference points. An E reference point may be used for interfacing with a service domain billing system, and a B reference point may be used between a service domain billing system and underlying network's billing system.

Abstract: A system is disclosed for orchestrating services. Service orchestration profiles specify attributes defining desired services. The service orchestration profiles may be distributed amongst nodes and hierarchically related to each other. Service orchestration management functions process the information in the service orchestration profiles in order to determine the desired services and use the information to implement the desired services. The service orchestration management functions may be hierarchically related to each other.

Abstract: Methods, systems, and devices may be used to annotate and store “semantics of normal resources” (hereinafter resource semantics). These methods, systems, and devices may be a part of a functional architecture for semantics support and allow for semantics based query. Also methods, systems, and devices associated with a semantics child resource may be created within a resource in order to represent semantics information.

Abstract: Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Abstract: A system is disclosed for orchestrating services. Service orchestration profiles specify attributes defining desired services. The service orchestration profiles may be distributed amongst nodes and hierarchically related to each other. Service orchestration management functions process the information in the service orchestration profiles in order to determine the desired services and use the information to implement the desired services. The service orchestration management functions may be hierarchically related to each other.

Abstract: Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Abstract: Enhancements to the device management functionality within service layer architecture of a Gateway node are described. The SL application registration procedure can be enhanced for devices in support of device management. Functionality can be added to the service layer to initiate automated request notification for DM purposes. Lightweight SL Transport Protocol bindings can support sending multiple DM commands called DM Action Scripts with a specific focus on the Constrained Application Protocol (CoAP) Protocol.

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: 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: It is recognized herein that current approaches to traffic steering in M2M systems lack capabilities, particularly with respect to traversing value added services in an operator's network. As described herein, nodes or apparatuses at a machine-to-machine (M2M) service layer can leverage value added services that are deployed in an operator's network. The M2M service layer may add metadata to downlink traffic so that the metadata can be used to assist with steering and processing data in the operator's value added services (VASs) network. By of example, the M2M service layer can use a control plane interface to push polices into a network operator's VASs network, and to allow functions in the VASs network to extract information from the M2M service layer.

Abstract: IoT twinning groups can be dynamically created. These twinning groups can be activated based on selected triggers. As part of twinning operation, service delivery can be re-directing away from the primary device to the IoT twinning group. Messages originating from members of the IoT twinning group can be processed and forwarded externally as if they came from the primary device. Further, the twinning service can be de-activated based on selected triggers.

Abstract: A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

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: Methods, systems, and devices may be used to support freshness-based processing of requests. Freshness-based processing may involve the service layer examining the age of stored content (e.g., resource representation) that it hosts and determining whether it is fresh enough to satisfy a retrieve or discovery request with a specified freshness requirement. If not fresh, the service layer can contact an application to refresh the content. In addition, freshness-based processing can also involve the service layer examining the semantic state of a command oriented update request to determine whether its state is fresh or not with respect to prior commands processed by the service layer. For example, the service layer may compare stored content associated with controlling a particular application (e.g. door is locked) and against the semantic content of an update request (e.g., unlock door) to determine whether it is the same (e.g., stale) or not (e.g., fresh).

Abstract: In a machine-to-machine/Internet-of-things environment, end-to-end authentication of devices separated by multiple hops is achieved via direct or delegated/intermediated negotiations using pre-provisioned hop-by-hop credentials, uniquely generated hop-by-hop credentials, and-or public key certificates, whereby remote resources and services may be discovered via single-hop communications, and then secure communications with the remote resources may be established using secure protocols appropriate to the resources and services and capabilities of end devices, and communication thereafter conducted directly without the overhead or risks engendered hop-by-hop translation.

Abstract: An M2M entity may retrieve data such that the representation of the data may consistently be returned in a form that can be dynamically specified in order to reduce complexity and overhead required by a requestor or consumer of the data. The semantic descriptions of the data that exist in the service layer may be used in order to provide desired results to the requestor or consumer of the data.