Abstract: Mechanisms support machine-to-machine service layer sessions that can span multiple service layer hops where a machine-to-machine service layer hop is a direct machine-to-machine service layer communication session between two machine-to-machine service layer instances or between a machine-to-machine service layer instance and a machine-to-machine application. Mechanisms are also disclosed that illustrate machine-to-machine session establishment procedures for oneM2M Session Management Service supporting multiple resources.

Abstract: A network data analytics function, which may be implemented as a service, is disclosed which provides a new and improved network data analytics capability in 5G core networks.

Abstract: Methods and apparatus are disclosed for integrating NF discovery and application layer service capability discovery in a communications network, such as the 3 GPP NR (e.g., 5G) network.

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

Abstract: Current discovery mechanisms lack capabilities, such as capabilities related to permissions associated with a given registrant for example. In an example embodiment, a registrant of a service layer can communicate with a network node that hosts the service layer. The network node may receive a discovery request for a resource from the registrant. The discovery may request include various context. For example, the context of the discovery request may be indicative of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location in which the registrant intends to access the resource, or a subscription plan that the registrant intends to use if the registrant accesses the resource. Based on the context of the discovery request, the network node may determine whether one or more resources at the service layer satisfy the discovery request.

Abstract: A Service Capability Exposure Function can be added to the UE (U-SCEF). The U-SCEF may be part of the UE's operating system (OS) and expose API's to applications that allow these applications to schedule data plane communications such as periodic sensor measurements or a firmware download. The U-SCEF communicates with an EPC Interworking Service that resides in the mobile network operator's (S)Gi-LAN. The EPC Interworking Service serves as an interface between the U-SCEF and the service capabilities that are exposed by the MNO via the SCEF. The U-SCEF may provide the EPC Interworking Service with information about the UE's anticipated communication schedule and mobility status. The EPC Interworking Service uses the services that are exposed by the SCEF to determine the optimal times for the UE to communicate, an optimal mobility management configuration, etc.

Abstract: Radio networks such as Public Land Mobile Networks (PLMNs), user equipment devices (UEs), servers such as In-temet-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: An IoT/M2M service layer may be provided with the capability to protect user privacy. This functionality may allow the IoT/M2M service layer to anonymize user data, particularly when user data is shared with third party consumers. A privacy policy service may enable the IoT service layer system to generate anonymization (e.g., privacy) policies based on inputs such as legal obligations, subscriber privacy preferences, and an authorization level of the data consumer. Data anonymization policies may be output from the privacy policy service and may be sent to a data anonymization service, where raw data may be anonymized based on the one or more data anonymization policies. The output from the data anonymization service function may be a privatized (e.g., anonymized) version of data that may prevent the data consumer from discovering one or more identifying characteristics of a user.

Abstract: Methods and apparatuses are described herein for sending and receiving messages using a low latency messaging service, referred to herein as a 5GMSG service, which resides in the 5G core network (5GC). In accordance with one embodiment, an apparatus may send, to a second apparatus, a first message comprising a first identifier for a third apparatus to enable the third apparatus to receive the first message. The apparatus may receive, from the second apparatus, a second message comprising a second identifier of the third apparatus. The apparatus may send, to the third apparatus, a third message comprising the second identifier. The first identifier may comprise an external public identifier of the third apparatus. The second identifier may comprise a 5G Globally Unique Temporary Identifier, a 5G Temporary Mobile Subscriber Identity (5G-TMSI), or a hashed version of a 5G-TMSI. The apparatus may receive notifications indicating that the second identifier changed.

Abstract: The present application is directed to one or more aspects with at least one aspect describing a method including a step of receiving device context information including a Power Saving Mode (PSM) Sync Flag from a core network node, where the PSM Sync Flag indicates a monitoring type of a device from among plural devices in the network. The method also includes a step of receiving a tracking area update or an attach request from the device on the network. The method further includes a step of sending a device availability notification request to a core network interworking function.

Abstract: An Application Data Delivery Service (ADDS) facilitates application data transfer between applications that may reside in a device domain (e.g., M2M/MTC devices and gateways) and applications residing in a network domain (e.g., an AS or SCS). The ADDS leverages existing 3GPP transport mechanisms, such as NAS, SMS, USSD, and User Plane, and it is configured to select a transport mechanism for delivering application data based on criteria, such as application data characteristics, application/end node characteristics and availability, subscription information, policies of the network, network conditions (such as congestion, node availability) and the like.

Abstract: A Service Coverage Manager (SCM) may receive or retrieve a report of a service node's coverage and generate a global picture of the service coverage for a service. The SCM may dynamically adjust the service node coverage to accommodate client service requests and provide new service coverage to appropriate clients. The SCM may reduce a service node's service coverage to reduce overlap with another node or reduce wasted resources, or may expand a service node's coverage to cover additional clients.

Abstract: Methods, systems, and apparatuses that enable a Service Layer (SL) to support analysis of internet of things (IoT) data and enable shared access to information generated by the analysis. An analytics management service may allow SL entities to configure analytics functions for many different IoT sources of data and organize the results in a customizable manner. The SL may support coordinating the analysis of IoT data from multiple independent sources and organizing the results of the analysis.

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 standards organization 3GPP is exploring new small data delivery techniques for machine-type communications (MTC). It is recognized herein that existing approaches leave the “small data” decision to the service capability server (SCS) for downlink data and to the user equipment (UE) for uplink data. A user equipment (UE) or the core network can identify the services (or flows) that should be characterized as Small Data, and can make decisions as to when to employ optimized Small Data procedures.

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: Methods are described that can enable resource monitoring over HTTP/2. These methods may rely on using multiple streams over persistent connections and on the HTTP/2 Push mechanism. Furthermore, a mechanism is proposed that can enable resource monitoring over multiple servers.

Abstract: Service Layer adaptation may be realized through one or more adaptation rules that are programmed by server administrators in a structured but flexible manner. As part of integrating the adaptive control into its operations, a Service Layer may be configured to provide the capability to receive requests in which an adaptation rule may be specified, to provide indications through response codes returned to requestors that the Service Layer is not able to process a request due to a reduced functional state, and to send a request for more server resources or move an application, a service, or a service instance to another platform.

Abstract: A 5G Network Architecture uses virtualization and network slicing. The user equipment (UE) interacts with an underlay network that interacts with virtual network slices. The UE interacts with the underlay network (ULN) to establish a connection to a virtual network slice. Procedures are defined to assign a new slice instance to a UE (UE initiated and ULN initiated); to change a UE Profile (UE initiated and ULN Initiated); and to change a UE's assigned slice instance (ULN Initiated).

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.