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

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 subscriber issues a message to a resource host to request subscription to multiple resources. This message may indicate identifiers of these resources, event notification criteria for each individual resource and define cross-resource notification criteria such as time window type and time window size. The resource host issues cross-resource notifications to the subscriber or its designated notification targets when expected changes on the target resources occur within a time window.

Abstract: A batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.

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.

Abstract: An Authorization Verification Service (AVS) is disclosed that may be provided by an IoT/M2M service layer to registrants of the service layer for Dynamic Context Aware Authorization. The AVS may allow the IoT/M2M service layer entities to define dynamic limits for authorizing access to services or data. The limits may be set, for example, in terms of the number of allowed accesses. When an IoT/M2M registrant makes a request for data or services for which it has dynamic context aware authorization, the AVS may maintain records of the remaining accesses available.

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: A service layer may be configured to offload requests and responses on behalf of IoT applications in order to reduce congestion and/or overhead on underlying networks, applications and devices. The service layer may be enabled with the capability to script and generate IoT application requests such that the requests can be initiated by the service layer without the IoT application having to re-issue the same request repeatedly (e.g., to periodically retrieve a sensor reading). This scripting may be initiated by request originators. The service layer may support the capability to monitor and detect repetitive request patterns and initiate the scripting itself. This scripting functionality may enable the service layer to perform operations on behalf of IoT applications. As a result, the messaging overhead on IoT applications and devices as well as underlying networks can be minimized.

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

Abstract: A subscriber issues a message to a resource host to request subscription to multiple resources. This message may indicate identifiers of these resources, event notification criteria for each individual resource and define cross-resource notification criteria such as time window type and time window size. The resource host issues cross-resource notifications to the subscriber or its designated notification targets when expected changes on the target resources occur within a time window.

Abstract: A network entity, such as a user equipment (UE), may request that a network provide multicast and broadcast services, e.g., where the request includes entity preferences such as network slice selection information. The network may provide information regarding provision of such services, where the information may include, for example, whether a service will be provided via a user plane or a control plane connection, network slice information, additional connections to be formed, separate encryption for such connections, etc. A Multicast/Broadcast Network Function (MBNF) may be used to establish such connections and manage a broadcast and multicast sessions. The MBNF may, for example, manage groups of entities, check an entity's access privileges for services, communicate with the a Management and Network Orchestration (MANO) system to reserve resources, and send data to entities over a shared control plane connection.

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: 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: A service layer entity may register to another service layer entity and proactively request to gain access to the local services hosted by the registrar entity. A registrar entity may accept a registree entity's registration request but only grant access of its partial services to the registree entity. If a registree entity does not need to proactively request the services within its registration request message, the registrar entity decides what services may be needed by the registree entity and grants access of those services to the registree entity.

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

Abstract: An apparatus can monitor interactions between IoT devices and IoT applications. Based on the monitoring, the apparatus may identify an interaction between a given IoT device and a given IoT application that can be adjusted. In an example, the apparatus may generate a recommendation or instruction in response to identifying the interaction. A first instruction may indicate a change in behavior for one of the IoT device or the IoT application. The apparatus may send the instruction to the one of the IoT device or the IoT application, for example, so as to cause the one of the IoT device or the IoT application to change the respective behavior, thereby adjusting the interaction between the IoT device and the IoT application.

Abstract: Enhancements to the device management functionality within service layer architecture of a Gateway node are described. The SL application registration procedure can be enhanced for devices in support of device management. Functionality can be added to the service layer to initiate automated request notification for DM purposes. Lightweight SL Transport Protocol bindings can support sending multiple DM commands called DM Action Scripts with a specific focus on the Constrained Application Protocol (CoAP) Protocol.

Abstract: Methods, systems, and devices may be used to support freshness-based processing of requests. Freshness-based processing may involve the service layer examining the age of stored content (e.g., resource representation) that it hosts and determining whether it is fresh enough to satisfy a retrieve or discovery request with a specified freshness requirement. If not fresh, the service layer can contact an application to refresh the content. In addition, freshness-based processing can also involve the service layer examining the semantic state of a command oriented update request to determine whether its state is fresh or not with respect to prior commands processed by the service layer. For example, the service layer may compare stored content associated with controlling a particular application (e.g. door is locked) and against the semantic content of an update request (e.g., unlock door) to determine whether it is the same (e.g., stale) or not (e.g., fresh).