Convida Wireless, LLC

Interdigital Patent Holdings, Inc.

Ipla Holdings Inc.

Other

Iot Holdings, Inc.

Drnc Holdings, Inc.

Quang Ly

Dale N Seed

Zhuo Chen

Chonggang Wang

Catalina Mihaela Mladin

Shamim Akbar Rahman

William Robert Flynn, Iv

Michael F Starsinic

Xu Li

Rocco Di Girolamo

Hongkun Li

Lijun Dong

Vinod Kumar Choyi

Jiwan L Ninglekhu

Guang Lu

Lu Liu

Yogendra C Shah

Gregory S Sternberg

Shoshana Loeb

Pascal M Adjakple

Mahmoud Watfa

Joseph M Murray

Donald Alfred Fleck

Richard P Gorman

Nicholas J Podias

Qing Li

Suresh Palanisamy

Yanyan Han

Rafael A Cepeda

Nithya Vijay

Darshan Appajigowda

Guodong Zhang

Paul L Russell, Jr

Xiang Sun

Sneha Aman Singh

Jasvir Singh Ramam

Owen Griffin

Lakshmi R Iyer

Narayan Parappil Menon

Thomas S Gilley

Phillip Brown

Owen James Griffin

Catlina Mihaela Mladin

Jasvir Singh Raman

Jinan Ninglekhu

Catalilna Mladin

Li Xu

Shamin Akbar Rahman

David Goehrig

Mingming Guo

Catalina Mihaela Mlandin

Jr Paul L Russell

Michael F Starsnic

Guang X Lu

William Robert Flynn Iv

William Robert Iv Flynn

Rocco Dl Girolamo

William Robert Flynn

Rocco Digirolamo

Jr Paul L Russel

William R Flynn Iv

Rohit Kumar

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

Methods, apparatus, and systems are described for improved edge network access for a UE. According to some aspects, a UE may receive a first Data Network Name (DNN) from an application and determine, based on a Data Network Name (DNN) Replacement Rule, the first DNN is associated with a second Data Network Name (DNN), where the first DNN and the second DNN are different. The UE may determine, based on the DNN Replacement Rule, to associate traffic from the application with a Protocol Data Unit (PDU) Session, where the PDU Session may be used to send data from the application to a network and the PDU Session is associated with the second DNN.

Enhancements for edge network access for a UE

An electronic device including a receiver configured to receive a first Subscriber Identity Module (SIM); a receiver configured to receive a second SIM; and circuitry configured to receive data from the first SIM; and send a request, to a first public land mobile network (PLMN), to register the electronic device to the first PLMN, wherein the request indicates that the electronic device is a multi-SIM device and the request includes multi-SIM assistance information, and wherein the multi-SIM assistance information informs the first PLMN of the electronic device's preference for multi-SIM operations.

Apparatus, system, method, and computer-readable medium for cellular system enhancements for the support of multi-SIM user equipments

Methods, apparatus, and systems are described for improved application interaction for network slicing. A wireless transmit/receive unit may send, to a network node, a registration request including an indication that the WTRU is capable of receiving information associated with a temporal availability of a network slice. The WTRU may receive a registration response including the information associated with the temporal availability of the network slice. The WTRU may determine, based on the temporal availability of the network slice, to stop use of a protocol data unit (PDU) session associated with the network slice.

Application interaction for network slicing

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

A user equipment (UE) operating in an 'Onboarding Mode' may search for a network broadcasting Onboarding Capability Information (OCT), then register using onboarding credentials and receive SNPN credentials from the network. The UE may then exit onboarding mode, enter Manual Network Selection or Automatic Network Selection mode, and connect to the SNPN. A UE may also receive from a network a list of PLMNs and SNPNs that are equivalent then, when registering, indicate to the network that a requested slice is not associated with the IJE's HPLMN, but is associated with an SNPN. The network may indicate to the UE how the slices of the network map to the slices of the SNPN, and may indicate whether a slice that is offered by the network only partially maps to a slice of the SNPN or HPLMN.

SNPN onboarding and obtaining SNPN services from a PLMN

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

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

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

A wireless transmit/receive unit may request, from a core network, authorization for creating one or more personal networks of one or more devices. After being granted authorization, the UE may be enabled to create a personal network and to cause a PDU session for the personal network to be established with the core network. The UE may enable members of the personal network to send data associated with the personal network via the PDU session.

Authorization, creation, and management of personal networks

Network Slice Selection Assistance information (NSSA1) may be signaled between User Equipment (UE) and a network. NSSA1 sent from the network to the UE may include, for example. Operating Frequency Band (OFB) for each Single NSSAI(S-NSSA1) in the NSSAI, as well as a Radio Access Technology (RAT) Frequency Selection Priority (RFSP) index, which the network configures as a part of UE access and mobility; subscription, during a UE registration procedure. RAT restrictions may be enhanced to indicate to the UE that certain slices are not accessible via certain RATs. A UE may be provided by the network with an alternative NSSAI and corresponding OFBs for each S-NSSAI thereby indicating to the UE that these S-NSSAI would have been allowed had they been requested. A UE may be able to choose an alternative Allowed NSSAI and send a registration update request to the network.

Frequency range driven network slicing

Methods, systems, and devices may assist in enhancements to PMF protocol and new ATSSS steering modes to enable support for analytics driven or multi-USIM steering. The following functionalities are disclosed: 1) Enable UEs to use the PMF protocol to provide UE specific data to the NWDAF for analytics purposes; 2) Enable multi-USIM UEs to notify the core network over the user plane of the UE's desire to pause communications with the CN associated with one USIM so the UE can communicate with the CN associated with another USIM; 3) Define new ATSSS steering modes to support data analytics driven steering; and 4) Define new ATSSS steering modes to support Multi-USIM steering, among other things.

Traffic steering enhancements for cellular networks

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

Growing community of inventors

North Wales, PA, United States of America

Quang Ly