Abstract: Methods and apparatuses are described herein for an automated product management (APM) service. An apparatus may receive from a second apparatus, at least one first request to enroll a third apparatus with a service layer associated with the second apparatus. The apparatus may send a second request to verify authenticity of the third apparatus and to generate a customized firmware or software for the third apparatus. The apparatus may send a third request to configure the third apparatus based on consent of a user of the third apparatus. The apparatus may send a response indicating whether the third apparatus has been enrolled with the service layer. The apparatus may receive a fourth request to diagnose or troubleshoot the third apparatus and a fifth request comprising information and the consent and requesting the fourth apparatus to perform at least one operation on the third apparatus.

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: 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: Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Abstract: Existing approaches to security within network, for instance oneM2M networks, are limited. For example, content might only be protected while the content is in transit between entities that trust each other. Here, the integrity and the confidentiality of content in an M2M network are protected. Such content may be “at rest,” such that the content is stored at a hosting node. Only authorized entities may store and retrieve the data that is stored at the hosting node, and the data may be protected from a confidentiality perspective and an integrity perspective.

Abstract: Lightweight, dynamic mechanisms are provided to support service layer interworking and resource extensibility. For example, one mechanism disclosed herein comprises defining a new service layer (SL) resource definition registration procedure that allows for specifying custom attributes of service layer resources to represent third party technology resources. A second mechanism disclosed herein comprises defining a new SL data model mapping registration procedure to map service layer resources to third party data models and to provide a new interworked retargeting indicator to the service layer. Further, a third mechanism disclosed herein comprises defining a SL generic interworking procedure to intelligently retarget requests toward interworked resources based on the interworked retargeting indicator provided by the data model mapping.

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: Described herein are complete lifecycle management processes for IoT/M2M devices, which are commissioned and de-commissioned in a given system without requiring a user/human administrator. A delegated life-cycle management process is described, wherein devices rely upon a delegatee, which may have more computing and battery resources than the devices. Further, a Trust Enabling Infrastructure (TEI) is described herein, which may belong to a different trusted domain than the given device and its delegatee. A device in response to powering on for the first time, registers with a trust enabling infrastructure (TEI) and generates one or more credentials based on the registration with the TEI so as to define a trust relationship with the TEL After the registration, the device receives one or more security components and policies from the TEI and installs the one or more security components so as to define a secure environment.

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: Cellular devices are becoming more and more powerful, and may host a number of different non-cellular capabilities, such as cameras, accelerometers, and sensors. Today, these capabilities are used mainly to provide some service to the device or the device owner. Disclosed herein are methods and systems for enabling devices to register their device capabilities with a cellular network, providing a mechanism for Application Servers to discover non-cellular capabilities of the devices, providing a mechanism to have the Application Servers configure these non-cellular capabilities of the devices, and preparing the device and the network for cellular traffic generated as a result of the Application Server using these non-cellular capabilities.

Abstract: Methods and apparatuses are described herein for a framework for data brokerage services in a service layer. A first apparatus may receive, from a second apparatus, a first signal comprising first information indicating a publishing intent associated with atopic indicator. The first apparatus may receive, from a third apparatus, a second signal comprising second information indicating a subscription intent associated with the topic indicator. The first apparatus may generate, based on the publishing intent and the subscription request, a topic instance. The first apparatus may send a third signal comprising an announcement message indicating the generated topic instance. The first apparatus may receive, from the third apparatus, a fourth signal comprising a subscription request for the generated topic instance. The first apparatus may send, to the third apparatus, at least one fifth signal comprising notifications and publish instances associated with the generated topic instance.

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: User equipment may be provisioned with information used to determine whether to send data via a user plane or a control plane. The information may be a management object comprising rules or polices, or uplink rate control information, for example. The user equipment may then respond to conditions autonomously, e.g., in response to congestion. An application or a service layer on user equipment may receive control plane/user plane (CPUP) selection policies. The application or service layer may then apply the CPUP selection policies to uplink traffic in determining whether uplink traffic should be sent over the user plane or control plane.

Abstract: Mechanisms support machine-to-machine service layer sessions that can span multiple service layer hops where a machine-to-machine service layer hop is a direct machine-to-machine service layer communication session between two machine-to-machine service layer instances or between a machine-to-machine service layer instance and a machine-to-machine application. Mechanisms are also disclosed that illustrate machine-to-machine session establishment procedures for oneM2M Session Management Service supporting multiple resources.

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: 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: 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: 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: Current discovery mechanisms lack capabilities, such as capabilities related to permissions associated with a given registrant for example. In an example embodiment, a registrant of a service layer can communicate with a network node that hosts the service layer. The network node may receive a discovery request for a resource from the registrant. The discovery may request include various context. For example, the context of the discovery request may be indicative of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location in which the registrant intends to access the resource, or a subscription plan that the registrant intends to use if the registrant accesses the resource. Based on the context of the discovery request, the network node may determine whether one or more resources at the service layer satisfy the discovery request.

Abstract: A registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.