Convida Wireless, LLC

Interdigital Patent Holdings, Inc.

William Robert Flynn, Iv

Dale N Seed

Catalina Mihaela Mladin

Zhuo Chen

Quang Ly

Hongkun Li

Rocco Di Girolamo

Michael F Starsinic

Lijun Dong

Xu Li

Guang Lu

Chonggang Wang

Shamim Akbar Rahman

Vinod Kumar Choyi

Yogendra C Shah

Phillip Brown

Qing Li

Shoshana Loeb

Jiwan L Ninglekhu

Lu Liu

Paul L Russell, Jr

Gregory S Sternberg

Donald Alfred Fleck

Richard P Gorman

Nicholas J Podias

Mahmoud Watfa

Narayan Parappil Menon

Thomas S Gilley

Philip M Brown

David Goehrig

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.

Mechanisms for an intelligent service layer request abstraction service

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.

Content security at service layer

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. A request may be sent and/or may instruct the one or more service capabilities to perform the change of state of the one or more services identified in the service description.

Service enabler function

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.

Permission based resource and service discovery

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.

Automatic generation of labeled data in IoT systems

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.

Systems and methods for enabling access to third party services via a service layer

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.

Systems and methods for service layer session migration and sharing

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.

Automated relationship management of service layer entities in a communications network

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.

Overlay resource trees in a communication network

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.

Profile based content and services

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.

Enhanced restful operations

Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Internet of things configurable event and action sequencing framework

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.

Service layer resource management for generic interworking and extensibility

An Authorization Verification Service (AVS) is disclosed that may be provided by an IoT/M2M service layer to registrants of the service layer for Dynamic Context Aware Authorization. The AVS may allow the IoT/M2M service layer entities to define dynamic limits for authorizing access to services or data. The limits may be set, for example, in terms of the number of allowed accesses. When an IoT/M2M registrant makes a request for data or services for which it has dynamic context aware authorization, the AVS may maintain records of the remaining accesses available.

Context aware authorization for data and services in the IoT/M2M service layer

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.

Growing community of inventors

Schwenksville, PA, United States of America

William Robert Flynn, Iv