Convida Wireless, LLC

Interdigital Patent Holdings, Inc.

Iot Holdings, Inc.

Ipla Holdings Inc.

Drnc Holdings, Inc.

Dale N Seed

Michael F Starsinic

Catalina Mihaela Mladin

William Robert Flynn, Iv

Chonggang Wang

Quang Ly

Guang Lu

Zhuo Chen

Lijun Dong

Rocco Di Girolamo

Hongkun Li

Shamim Akbar Rahman

Xu Li

Paul L Russell, Jr

Vinod Kumar Choyi

Qing Li

Yogendra C Shah

Phillip Brown

Lu Liu

Shoshana Loeb

Jiwan L Ninglekhu

Suresh Palanisamy

Mahmoud Watfa

Jean-Louis Gauvreau

Gregory S Sternberg

Ana Lucia Pinheiro

Zongrui Ding

Kamel M Shaheen

Behrouz Aghili

Rocco DiGirolamo

Chunxuan Ye

Lei Wang

Marian Rudolf

Eldad M Zeira

Prabhakar Chitrapu

Inhyok Cha

John L Tomici

Ronald Murias

Ulises Olvera-Hernandez

Alexander Reznik

Peter Shaomin Wang

Sudheer A Grandhi

Nicholas J Podias

Donald Alfred Fleck

Richard P Gorman

Dorothy Gellert

John Cartmell

Kushanava Laha

Debjani Majumder

Rafael A Cepeda

Joseph M Murray

Martino M Freda

Arty Chandra

Alpaslan Demir

Ana Lucia A Pinheiro

Athmane X Touag

Scott C Hergenhan

Kenneth F Lynch

Prashanth Murthy

Reeteshkumar Varshney

Onkarnath Upadhyay

Owen Griffin

Mohsen Akbari

Aravind Kamarajugadda

Samian Kaur

Michelle Perras

Narayan Parappil Menon

Thomas S Gilley

Dolores F Howry

Philip M Brown

Xiang Sun

Paul Russell

Owen James Griffin

Oscar Lopez-Torres

Shamin Akbar Rahman

David Goehrig

Rohit Kumar

Ronald G Murias

Rocco Digirolamo

William Robert Iv Flynn

William R Flynn Iv

Jr Paul L Russel

Samian J Kaur

William Robert Flynn

William Robert Flynn Iv

Catalina Mihaela Mlandin

Michael F Starsnic

Guang X Lu

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.

Service layer message templates in a communications network

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.

Automated service enrollment in a machine-to-machine communications network

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

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.

Interworking service for the restful internet of things

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

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.

Dynamic fog service deployment and management

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 and apparatuses are described herein for configuration of background data transfers (BDTs) between local area data networks (LADNs). An apparatus may receive a message indicating a request from a user equipment (UE) for a data transfer of data originating from the UE. The apparatus may send, to a database, a request for subscription information associated with the UE and a policy profile associated with the UE to determine whether there is an existing BDT policy. The apparatus may receive, from the database, a response indicating whether there is an existing BDT policy that can be re-used. The apparatus may determine, based on the received response, a BDT policy for the data transfer and a LADN to service the data transfer. The apparatus may send, to the LADN via a radio access network (RAN) node, a notification message of an arrival time and data rate for the data transfer.

Methods of managing connections to a local area data network (LADN) in a 5G network

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

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.

Lightweight IoT information model

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

Growing community of inventors

Allentown, PA, United States of America

Dale N Seed