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: 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: Radio networks such as Public Land Mobile Networks (PLMNs), user equipment devices (UEs), servers such as Internet-of-Things servers, and core network entities may be adapted to facilitate transfers of connections of wireless devices. For example, a first PLMN may provide restricted access to a UE to assist the UE in finding a second PLMN for a full connection. Entities may be adapted to support for non-coverage related PLMN transfers, such as transfers initiated by UEs, PLMNs, servers, and core network entities, e.g., in response to changing usage, congestion, etc.

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: 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: When mobile terminated devices sleep, the devices might not be reachable when needed, for instance when the device is a recipient of data from a third party server. As described herein, a third party application server may inform the network that it has data to send to a particular UE or group of UEs. In an example, the mobile core network (MCN) may use information from the third party server to ensure that the UE is awake when it needs to be. For example, a given UE or group of UEs can be prevented from entering a sleep state before a data transfer is completed.

Abstract: The present application is at least directed to an apparatus. The apparatus includes a non-transitory memory including instructions stored thereon for configuring a service. The apparatus also includes a processor operably coupled to the non-transitory memory may be configured to execute the instructions of (i) receiving first information for accessing an exposure function; (ii) receiving a request for the service via an application; (iii) creating a request for the service based on the first information; (iv) sending the created request to the exposure function; and (v) receiving a response from the exposure function. The service may include any one or more of buffering, a background data transfer, a communication pattern configuration, sponsored services, reachability, a mobile originating/paging-off mode or value added services. Moreover, the received request includes parameters to configure the service.

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: It is recognized herein that capabilities are lacking related to how different users can be authenticated on top of an existing subscription authentication. In some examples, a user¬ centric authentication layer may be supported on top of an existing subscription authentication, such that different users may use the same user equipment (UE) with customized services, and different users of devices can be identified behind a gateway with a 3GPP subscription (without the devices having a dedicated 3GPP subscription). Further, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.

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: A network entity may determine whether a network context of a device is stored in the device or in the network based, at least in part, on a preference or capability of the device, as reported by the device during attachment to the network entity. The context may be stored in, and retrieved from, a dedicated context storage function that is independent of the network entity. A context storage function may be partitioned, or separate storage functions used, to automatically group and track access network contexts, core network contexts, or network slice contexts. The context storage function may provide to the device an index, such as a link or other identifier to be used in retrieving the stored context information. The context storage function may further provide a token to secure re-attachment communications among the device, the network entity, and the context storage function.

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: The present application is directed to an apparatus communicating with a mobile core network. The apparatus includes a non-transitory memory including instructions stored thereon for configuring a service. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute the instructions of: (i) receiving, from a core network node, first information for accessing a Network Exposure Function (NEF); (ii) receiving a request for the service from an application on user equipment (UE); (iii) creating a request for the service; (iv) using the first information to send the created request to the NEF; (v) receiving a response from the NEF, the response includes a second information; and (vi) sending the second information to the application. The service includes one or more of buffering, background data transfer, communication pattern configuration, sponsored services, reachability, mobile originating/paging-off mode, and value added services.

Abstract: The present application is at least directed to an M2M gateway apparatus. The apparatus includes a non-transitory memory having instructions stored thereon for service layer online charging of a service layer event. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute a set of instructions. One of the instructions includes sending, to a service layer charging function of an M2M server, a service layer rating request message for the service layer online charging of the service layer event detected by the M2M gateway. The service layer event is triggered by an application registered to the M2M gateway and that performs a read or write operation on a resource of the M2M gateway. Another one of the instructions includes receiving, from the service layer charging function of the M2M server, a rating response including the calculated amount of service units required for the M2M gateway to process the service layer event.

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: 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: 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: The present application is at least directed an apparatus including a non-transitory memory and a processor that is operably coupled to the non-transitory memory for managing a server transition with a service for user equipment (UE). The processor is configured to perform the instructions of receiving, at a core network, a first request from a first server to switch responsibility of the service to a second server to communicate with the UE. The processor is also configured to perform the instructions of determining a first core network terminating point needs updating to a second core network terminating point. The processor is further configured to perform the instructions of selecting the second core network terminating point sends a result of the determination to the user equipment. The processor is still further configured to perform the instructions of sending, to the service, a notification the user equipment is associated with the second core network terminating point.