Abstract: System and methods that improve the use of network functions on edge data networks are disclosed. A mechanism that supports edge-assisted UE context and trigger collection is described herein, where a UE can actively send its context information and/or any trigger (e.g. a request for a network function/service to be deployed in edge data networks, etc.) to an edge enabler server, which processes the received context and triggers from its UEs. The edge enabler server may also forward UE context and triggers to 5G core network (5GC) upon receiving a solicitation request from the 5GC, or if the 5GC has already made a subscription for getting notification on UE context and triggers. A network repository function is provided as a new network function collect, store, and manage edge data network information.

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: A distributed ledger interworking architecture is described wherein a distributed ledger proxy interfaces with IoT service layer systems and distributed ledger systems. Service layer nodes may interact with the distributed ledger proxy to leverage functions provided by distributed ledger systems, such as to request that the distributed ledger proxy insert some service layer information into the distributed ledgers. A distributed ledger proxy can support multiple service layer nodes and may interface to multiple different distributed ledger systems.

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

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: 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: 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: Methods, systems, and devices may assist in enhancements to PMF protocol and new ATSSS steering modes to enable support for analytics driven or multi-USIM steering. The following functionalities are disclosed: 1) Enable UEs to use the PMF protocol to provide UE specific data to the NWDAF for analytics purposes; 2) Enable multi-USIM UEs to notify the core network over the user plane of the UE's desire to pause communications with the CN associated with one USIM so the UE can communicate with the CN associated with another USIM; 3) Define new ATSSS steering modes to support data analytics driven steering; and 4) Define new ATSSS steering modes to support Multi-USIM steering, among other things.

Abstract: The provision of fog services may be coordinated by a fog leader adapted to track capabilities and resources available at other fog nodes, and to receive and process requests and policies from entities seeking fog services. For example, the fog leader may divide tasks among several fog nodes according to the capabilities and resources available at various nodes, and do so in a way that is transparent to the requestor and the fog nodes providing the service. The fog leader may request the reservation of capabilities and resources, and confirm and cancel such reservations. Fog services policies may include, for example, periods of time during which capabilities and resources should be reserved.

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 labeled data generation service provides an Internet-of-Things (IoT) system with a capability whereby users may configure how the system gathers, processes, and generates labeled data instances by: collecting and processing the data into a format required by supervised learning algorithms; generating expected outputs from data available in the IoT system; supporting the linking of collected inputs with generated expected outputs; forming labeled data instances; cleaning the labeled data set appropriately; sending the labeled data set to target nodes; and/or communicating with target nodes regarding improving the data processing and labeling processes, as required.

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: 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: Systems and methods are introduced to enable cross-domain discovery. Systems and methods are also introduced to create representations of resources and information discovered from cross-domain discovery.

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: Systems and methods are described to automate managing of relationships between IoT entities (e.g., devices, apps, users) and offloading the burden of managing these relationships from users. A Relationship Management Service (RM Service) is described herein for the autonomous establishment, modification, and tear-down of relationships between IoT entities.

Abstract: Resources on a host may be typically organized in a tree structure. In existing service layer technologies, the originators generating data may typically store their resources in default locations in such a tree, resulting in a relatively flat tree structure. As such, it may be beneficial for the service layer to provide assistance to the originators so that the originators can better structure their resources. Additionally, applications consuming the data may prefer data resources to be structured in a certain way, and may only be interested in a small subset of the hosted resources. Therefore, it may be beneficial for such applications to transmit to the service layer the resources that are of interest, and how to structure such resources. Embodiments described herein provide methods and systems to enable solutions to the problems discussed above, among others. Several aspects are introduced to enable such embodiments.

Abstract: Methods, devices, and systems are disclosed for an M2M Interest Function. An M2M Interest Function may receive requests from users to publish the users' personal interests in particular data identify relationships and patterns in the data. Associated data may then be stored in a single best location for such data based on various criteria rather than on separate M2M Gateways or M2M Servers. This location may be provided to users interested in such data. Relationship and association data may be provided to M2M gateways.

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: A batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.