Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

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: A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Abstract: An apparatus can monitor interactions between IoT devices and IoT applications. Based on the monitoring, the apparatus may identify an interaction between a given IoT device and a given IoT application that can be adjusted. In an example, the apparatus may generate a recommendation or instruction in response to identifying the interaction. A first instruction may indicate a change in behavior for one of the IoT device or the IoT application. The apparatus may send the instruction to the one of the IoT device or the IoT application, for example, so as to cause the one of the IoT device or the IoT application to change the respective behavior, thereby adjusting the interaction between the IoT device and the IoT application.

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: The concept of a service layer message template is introduced, which may be a request template or a response template. Message templates may be created and stored at the service layer. Each message template may contain a set of request or response parameters and their values. Once in place, an application can send a request to the service layer that does not include the request parameters contained in the message template (i.e. request template); instead, a message template identifier may be sent. Since request parameters are included in the message template and stored at the service layer, communication overhead between the service layer and the application (or another service layer) may be reduced.

Abstract: Methods, system, and apparatuses may support end-to-end (E2E) quality of service (QoS) through the use of service layer (SL) sessions. For example, an application can communicate with a targeted device based on application specified schedule, latency, jitter, error rate, throughput, level of security, and cost requirements.

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: 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.

Abstract: Systems and methods are described herein to automate managing of service layer operations comprised of multiple elementary operations and offloading the burden of performing such multi-step operations from a requesting entity to the service layer. A Request Abstraction Service (RAS) is described herein for the autonomous execution of such multi-step operations. Methods and apparatuses are also described herein for a service layer framework for integrating generic and functional user interfaces as services managed by the SL on behalf of requesting entities.

Abstract: The present application describes a method and apparatus for managing a service in a service layer. In particular, a method describes a computer readable storage medium including instructions for managing a service in a service layer where the instructions are executed by a processor. The executed instructions cause the processor to receive a request to manage, via a service enabler function of the service layer, a change of state of the service including adding, removing, activating, or deactivating the service. The request may include a service description. The executed instructions also cause the processor to evaluate, via the service enabler function, the service description comprising identifiers of one or more services to manage. The executed instructions further cause the processor to identify one or more service capabilities in the service layer to assist in managing the one or more services identified in the service description.

Abstract: An M2M Service Layer is expanded to access the services of third parties and exchange data with these third parties. The M2M Service Layer is then able to act as a proxy between M2M Devices and the third party services. The M2M Service Layer is able to present a single/consistent interface, or API, to the M2M Device and hide the details of the third party service provider from the M2M Device.

Abstract: When mobile terminated devices sleep, the devices might not be reachable when needed, for instance when the device is a recipient of data from a third party server. As described herein, a third party application server may inform the network that it has data to send to a particular UE or group of UEs. In an example, the mobile core network (MCN) may use information from the third party server to ensure that the UE is awake when it needs to be. For example, a given UE or group of UEs can be prevented from entering a sleep state before a data transfer is completed.

Abstract: The present application at least describes a computer-implemented method including a step of setting, via a service layer residing on a server outside of an underlying 3GPP network, a trigger in the underlying 3GPP network, where the trigger defines an QoS parameter change in the underlying 3GPP network. The underlying 3GPP network is configured with functionality to send a notification to the service layer upon detecting the QoS parameter change. The computer-implemented method also includes a step of receiving, from the underlying 3GPP network, the notification the detected QoS parameter change has occurred. The computer-implemented method further includes a step of performing, at the service layer residing on the server a service layer operation in response to the received notification.

Abstract: It is recognized herein that capabilities are lacking related to how different users can be authenticated on top of an existing subscription authentication. In some examples, a user¬ centric authentication layer may be supported on top of an existing subscription authentication, such that different users may use the same user equipment (UE) with customized services, and different users of devices can be identified behind a gateway with a 3GPP subscription (without the devices having a dedicated 3GPP subscription). Further, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.

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.

Abstract: The present application describes a method and apparatus for updating a service in a service layer function of a network. In particular, a method for adding a service is disclosed. Initially, a request is received at a service enabler function located in the service layer function to add the service. A service description of the requested service is reviewed to understand its capabilities. A verification request is sent to a service capability located in the service layer function. Further, another service layer function or application is notified that the requested service is enabled.

Abstract: An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.

Abstract: A service layer (SL) function may be used for managing a user profile that is associated with a SL user and using this profile to automatically configure different types of devices connected to an IoT service provider's platform. A SL function may be used to support user data privacy and security when data is imported and exported between gateways or servers temporarily.

Abstract: Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.