Convida Wireless, LLC

Interdigital Patent Holdings, Inc.

Iot Holdings, Inc.

Nec Laboratories America, Inc.

At&t Intellectual Property I, L.p.

Ipla Holdings Inc.

Other

Nec Corporation

Chonggang Wang

Dale N Seed

Quang Ly

Xu Li

Lijun Dong

Hongkun Li

Catalina Mihaela Mladin

Guang Lu

Michael F Starsinic

Qing Li

Zhuo Chen

Shamim Akbar Rahman

Rocco Di Girolamo

Paul L Russell, Jr

William Robert Flynn, Iv

Vinod Kumar Choyi

Zongrui Ding

Lu Liu

Ting Wang

Mahmoud Watfa

Gregory S Sternberg

Ana Lucia Pinheiro

Jiwan L Ninglekhu

Nicholas J Podias

Phillip Brown

Lusheng Ji

Rocco DiGirolamo

Jean-Louis Gauvreau

Inhyok Cha

Ahmed Mohamed

Tao Han

Mahmoud Daneshmand

Sneha Aman Singh

Yanyan Han

Rafael A Cepeda

Kamel M Shaheen

Yogendra C Shah

Behrouz Aghili

Suresh Palanisamy

Xavier De Foy

Prashanth Murthy

Dorothy Gellert

Wei Wei

Xiang Sun

Paul Russell

Michael J Starsinic

Mohsen Akbari

Owen Griffin

Alexander Reznik

Samian Kaur

Ana Lucia A Pinheiro

John L Tomici

Shoshana Loeb

Catherine M Livet

Robert G Gazda

Kenneth F Lynch

Dolores F Howry

Rahim Tafazolli

Michel Roy

Debjani Majumder

Reeteshkumar Varshney

Kevin Di Lallo

Martin Jolicoeur

Owen James Griffin

Seyed Amir Hoseinitabatabaei

Payam Barnaghi

Ning Wang

George Kamel

Jeremy Pallats

Mingming Guo

Li Xu

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

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 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

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products that may be implemented in wireless communications. In one representative method, the WTRU may send one or more age of information (AoI) preferences for a traffic flow to a network entity, and the WTRU may receive one or more AoI rules for the traffic flow from the network entity. The WTRU may receive a packet associated with the traffic flow, and the received packet may include an indication of AoI of the packet. The WTRU may send one or more additional AoI preferences to the network entity, such as upon determining that any of the AoI preferences and/or AoI rules are not satisfied based on the indication of AoI. The indication of AoI may correspond to a processing state of the packet along a path in a network and/or to a time since the packet was created.

Methods, architectures, apparatuses and systems for age aware services

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

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

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

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.

Enhanced M2M content management based on interest

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

Growing community of inventors

Princeton, NJ, United States of America

Chonggang Wang