Convida Wireless, LLC

Interdigital Patent Holdings, Inc.

Other

Nec Laboratories America, Inc.

Xu Li

Chonggang Wang

Quang Ly

Catalina Mihaela Mladin

Lijun Dong

Dale N Seed

Hongkun Li

Guang Lu

Shamim Akbar Rahman

William Robert Flynn, Iv

Zhuo Chen

Qing Li

Rocco Di Girolamo

Phillip Brown

Vinod Kumar Choyi

Michael F Starsinic

Gregory S Sternberg

Lu Liu

Mahmoud Watfa

Rafael A Cepeda

Sneha Aman Singh

Yanyan Han

Yogendra C Shah

Paul L Russell, Jr

Xiang Sun

Paul Russell

Owen Griffin

Neda Cvijetic

Konstantinos Kanonakis

Philip M Brown

Owen James Griffin

Mingming Guo

Akihoro Tanaka

William Robert Iv Flynn

Shamin Akbar Rahman

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.

Interworking between IoT service layer systems and distributed ledger systems

Procedures, methods, architectures, apparatuses, systems, devices, etc. directed to enablers for blockchain-enabled wireless systems are provided. Among the apparatuses, is an first apparatus that may be configured to receive, from a network application, a registration request including information indicating a plurality of application-level requirements for a distributed ledger service, including one or more performance requirements, and one or more actions; determine a node of a distributed ledger system to associate to the network application based at least in part on the performance requirement; provide, to each of a one or more computing resources, executable code for conducting one or more of the one or more actions; and send a confirmation of registration to the network application.

Methods, architectures, apparatuses and systems directed to enablers for blockchain-enabled wireless systems

A subscriber issues a message to a resource host to request subscription to multiple resources. This message may indicate identifiers of these resources, event notification criteria for each individual resource and define cross-resource notification criteria such as time window type and time window size. The resource host issues cross-resource notifications to the subscriber or its designated notification targets when expected changes on the target resources occur within a time window.

Cross-resource subscription for M2M 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

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

Subscription and notification service

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

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

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.

Cross-domain discovery between service layer systems and web of things systems

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

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

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products directed to messaging through blockchain networks are provided. Among such methods is a method that may be implemented in a device comprising circuitry, including a transmitter, a receiver and a processor, and may include any of receiving a request to send a message including a message and information indicating a source of the message, a destination of the message and a distributed ledger system; determining a first node associated with a distributed ledger system based, at least in part, the information indicating the distributed ledger system and the information indicating the destination; generating a transaction for the message; and sending the transaction to a second node of the distributed ledger system.

Methods, architectures, apparatuses and systems directed to messaging through blockchain networks

A Data Sample Collection Service (DSCS) may be configured to receive various data sample collection requests from users and to process the one or more requests on behalf of the users. In order to properly describe what kind of Ready-to-Use Data Samples (RDS) a user needs, the DSCS may adopt a Data Sample Template (DST). By using the DST, the user can clearly depict what their desired data samples look like, along with various quality requirements regarding the data samples. The DSCS can further provide a DST Management function to users. In general, DST management involves the processes of DST creation, DST update, DST deletion and DST activation/de-activation. For example, a user may create a DST based on its data sample collection needs. Later, the created DST can also be updated and/or deleted based on dynamic changes to the needs of the user.

Data sample template (DST) management for enabling fog-based data processing

Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. These requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.

Efficient resource representation exchange between service layers

Mechanisms for multidimensional data modeling and operations and related procedures are described. Resource structures for multidimensional data can be used. This can allow lumped operations such as RESTful operations and procedures on the multidimensional data. A new attribute 'SamplingPeriodCovered' can be used to indicate the time interval when the related time series data (or any multi-dimension data streams) are stored. This can reduce the total size of the data stored.

Growing community of inventors

Plainsboro, NJ, United States of America

Xu Li