Convida Wireless, LLC

Interdigital Technology Corporation

Interdigital Patent Holdings, Inc.

Nortel Networks Corporation

Intel Corporation

Sk Telecom Company, Ltd.

Other

Iot Holdings, Inc.

Shamim Akbar Rahman

Quang Ly

Chonggang Wang

Zhuo Chen

Dale N Seed

Xu Li

Lijun Dong

Guang Lu

William Robert Flynn, Iv

Vinod Kumar Choyi

Marian Rudolf

Rocco Di Girolamo

Catalina Mihaela Mladin

Michael F Starsinic

Juan Carlos Zuniga

Yogendra C Shah

Gregory S Sternberg

Teresa Hunkeler

Joseph A Kwak

Catherine M Livet

Ulises Olvera-Hernandez

Kamel M Shaheen

Stephen G Dick

Maged Zaki

Peter Anthony Barany

Michelle Perras

Xavier De Foy

Chandra Sekhar Bontu

Mahmoud Watfa

Hongkun Li

Narayan Parappil Menon

Debashish Purkayastha

Paul Marinier

Christopher R Cave

Qing Li

Prabhakar Chitrapu

Vincent Roy

Hang Liu

Angelo A Cuffaro

Osama Lotfallah

Athmane X Touag

Alan Gerald Carlton

Shavantha Kularatna

Ahmed Ali

Serhad Doken

Khalid Shamsuddin Hossain

Yanyan Han

Fatih M Ozluturk

Peter Shaomin Wang

Jean-Louis Gauvreau

Frank La Sita

Yi-Ju Chao

Hyun Wook Kim

Milan Patel

Yong Sun Cho

Sneha Aman Singh

Jean-Ian Boutin

Suan Eoh

Pascal M Adjakple

Saad Ahmad

James M Miller

Steven Jeffrey Goldberg

Samian Kaur

Paul L Russell, Jr

Rajat Pritam Mukherjee

Kai Liu

John L Tomici

Karl D Mann

Brian Gregory Kiernan

Phillip Brown

Alain Charles Louis Briancon

Frank LaSita

Eric Johnson

Xiang Sun

Yonghai Gu

Mingming Guo

Michel Desgagné

Guy Cote

Teresa Joanne Hunkeler

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

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

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

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

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

Internet of Things (IoT) event objects can be tailored to specific device types and capabilities. An IoT event object can use a flexible definition of an event that can be reconfigured. An IoT event object allows for the ability to set different triggering conditions and priorities. Individual event definitions can be extended to create more complex events. A Notification Handler supports sending a request or command in response to an event that requires action.

Internet of things event management systems and methods

Method, systems, and devices for transparent relocatable application instance deployment are described. A method performed by a Wireless Transmit/Receive Unit may comprise transmitting, to a Multi-access Edge Computing (MEC) system, a first message including a request to deploy the relocatable application instance at a target. The method may comprise receiving a second message including an indication to establish communication with the application instance and a Transparent Instance Relocation Session Identifier (TIRSI) and establishing, based on the second message, communication with the relocatable application instance at the target. The method may comprise transmitting a third message including a request for relocation of the application instance to another target. The method may comprise receiving a fourth message including an indication to establish communication with a relocated application instance at the another target and the TIRSI and establishing, based on the fourth message, communication with the relocated application instance at the another target.

Transparent relocation of MEC application instances between 5G devices and MEC hosts

Methods and apparatuses for enabling multi-host multipath secure transport with Quick User Datagram Protocol (UDP) Connections (QUIC) are described herein. A method performed by a client endpoint may involve sending, to a network node, a request to establish a QUIC connection with a destination endpoint, the request to establish the QUIC connection including a flow identifier (ID). The method may involve receiving, from the network node, a response including an indication that the request to establish the QUIC connection with the destination endpoint is accepted. The method may involve encapsulating inner QUIC packetized data within outer QUIC packetized data, the inner QUIC packetized data including the flow ID. The method may involve sending, to the network node, the outer QUIC packetized data for forwarding toward the destination endpoint based on the flow ID.

Methods and apparatuses for enabling multi-host multipath secure transport with QUIC

Methods, system, and apparatuses may support end-to-end (E2E) quality of service (QoS) through the use of service layer (SL) sessions. For example, an application can communicate with a targeted device based on application specified schedule, latency, jitter, error rate, throughput, level of security, and cost requirements.

Internet of things end-to-end service layer quality of service management

A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

System and methods for service layer cache management

A set of point-of-contact information including a service level identifier, an address, a list of interfaces, and a set of interface selection preferences for each of several entities may be used to facilitate communications among the entities by selecting a preferred interface in accordance with the set. Interface preferences may also be derived from a set of policies. The preferred interface may be resolved in accordance with the preferences of multiple entities. Messages may include an interface type parameter to be used for forwarding of the message, and message forwarding may be resolved in accordance with the parameter and the messages.

Service layer support for multiple interface nodes

Growing community of inventors

Cote St. Luc, Canada

Shamim Akbar Rahman