Abstract: A fog service layer architecture is disclosed using hierarchical fog node deployment including the co-existence and interactions of the fog node with a cloud node. The architecture also includes a list of functions, capabilities or services that are hosted in each fog node. One or more fog management procedures may be run between fog nodes (or between fogs and the cloud) and may comprise a fog capability discovery procedure, a fog connection verification procedure, and a fog capability status report procedure. In addition, fog nodes may be configured to interact with each other to get particular services using one or more fog service procedures described herein.

Abstract: 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.

Abstract: Network Slice Selection Assistance information (NSSA1) may be signaled between U ser 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.

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

Abstract: Methods devised for enabling external AF/AS to provide information to SGC regarding Edge Data Network Configurations. Further, methods for UE provisioning for Edge service enablement are provided. Mechanisms are disclosed for: enabling UEs, not hosting an EEC, to request EDN information provisioning in order to enable Application Clients, which are not Edge-aware, to utilize Edge services; enabling an EEC, hosted by a UE, to obtain Edge Configuration information by using URSP rules for establishing IP connectivity with a Configuration Server; and enabling an EEC, hosted by a UE, to obtain Edge Data Network configuration information during registration.

Abstract: 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.

Abstract: 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.

Abstract: A radio apparatus communicating with a first and a second network, and having a first connection to the first network, may receive a page from the second network and determine to form a second connection with the second network, and notify the first network of the selection. The first network may then notify the apparatus to release or suspend the first connection. The apparatus may send release and/or suspension preferences to the first network, such as a preference to be treated in an idle or inactive mode, paging preferences, and a preferred identifier of the apparatus. The apparatus may then form the second connection, and monitor for paging from the first network, e.g., during a given paging occasion and paging frame.

Abstract: Methods and apparatuses are described herein for multi-subscriber identification module (SIM) connected mode operation. In one embodiment, a wireless communications device may receive, from an access stratum interface, a request access to the receiver chain during a receiving opportunity. The wireless communications device may determine that the receiver chain is available during the receiving opportunity. The wireless communications device may send a response indicating access is granted to cause the access stratum interface to receive a downlink transmission during the receiving opportunity. The wireless communications device may receive, from the access stratum interface, a second request for a transmitter chain during a transmitting opportunity. The wireless communications device may determine that the transmitter chain is available during the transmitting opportunity.

Abstract: A service layer (SL) function may be used for managing a user profile that is associated with a SL user and using this profile to automatically configure different types of devices connected to an IoT service provider's platform. A SL function may be used to support user data privacy and security when data is imported and exported between gateways or servers temporarily.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.

Abstract: 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.

Abstract: Methods and systems may be used to synchronize time across multiple IoT related entities, such as a network of resource constrained sensor and actuator type devices, IoT gateways, IoT cloud services, or IoT applications.

Abstract: 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 as supported service, supported interface type, or a supported device type.

Abstract: 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.

Abstract: A 5G network may support path switch mechanisms from a direct path to an indirect path to the network, and vice versa. Methods and systems are disclosed for performing the path switching process.

Abstract: Embodiments concern a dynamic authorization framework. Security Classification Process (SCP) is the process of classifying raw data, information extracted from raw data, content or code from security-value perspective. Security Achievability Determination Process (SADP) is a process based on a SV/SC that has been assigned, the RHE may determine the Security Requirements and how the security requirements may be achieved. During the Security Achievability Listing Process (SALP), the RHE uploads onto the Resource Listing Entity (RLE) the URI of the resource, the SAM associated with the resource and optionally a digital certificate associated with the resource. During the SAM Assessment Process (SAMAP) process, a Client evaluates the security mechanisms that must be carried out in order to meet the SAM that was provided as part of the Discovery Process (DP). Based on the SAM obtained from the RLE, the Client may initiate a Security Achievability Enabling Process (SAEP).

Abstract: 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.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.