Abstract: A Message Flow Management (MFM) service of a service layer (SL) of a communications network enables dynamic control of the rate of particular SL messages that are destined to a target entity, such as an IoT device or application, based on its SL status or other context information.

Abstract: The application is at least directed to a core network including a non-transitory memory including instructions stored thereon for transferring infrequent small data to a service capability or application server on a 5G network. The core network also includes a processor operably coupled to the non-transitory memory. The processor is configured to execute the instructions of detecting a relay user equipment (UE) sending a data transfer request message to the core network based on uplink traffic generated at a remote UE and control information of the remote UE. The processor is also configured to execute the instructions of querying a database in the core network for subscription information of the remote UE based on the control information. The processor is also configured to execute the instructions of receiving the subscription information from the database. The processor is further configured to execute the instructions of processing the received subscription information.

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

Abstract: Methods and apparatuses are described herein for an automated product management (APM) service. An apparatus may receive from a second apparatus, at least one first request to enroll a third apparatus with a service layer associated with the second apparatus. The apparatus may send a second request to verify authenticity of the third apparatus and to generate a customized firmware or software for the third apparatus. The apparatus may send a third request to configure the third apparatus based on consent of a user of the third apparatus. The apparatus may send a response indicating whether the third apparatus has been enrolled with the service layer. The apparatus may receive a fourth request to diagnose or troubleshoot the third apparatus and a fifth request comprising information and the consent and requesting the fourth apparatus to perform at least one operation on the third apparatus.

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: The application is at least directed to a core network including a non-transitory memory having instructions stored thereon for registering a network function or network function template in the core network. The network includes a processor, operably coupled to the non-transitory memory. The processor is configured to perform the instruction of determining that registration of the network function or network function template is acceptable. The processor is also configured to perform the instruction of transmitting a message including the network function or network function template to a repository in the core network. The processor is also configured to perform the instruction of verifying the network function or network function template against existing policies in the core network. The processor is also configured to perform the instruction of registering the network function or network function template in the repository after verification.

Abstract: A Service Continuity Network Function (SCNF) may be used to provide service continuity support in IoT networks such as 3 GPP and oneM2M, whereby higher layer session and service information is associated with transport layer session information. By means of the SCNF, a higher layer service may be resumed when a new session or connection is created, without support for transport layer session continuity. The service continuity capabilities of the SCNF may be exposed to the service layer of the network by way of a resource data structure.

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: Methods and apparatuses are described herein for a framework for data brokerage services in a service layer. A first apparatus may receive, from a second apparatus, a first signal comprising first information indicating a publishing intent associated with atopic indicator. The first apparatus may receive, from a third apparatus, a second signal comprising second information indicating a subscription intent associated with the topic indicator. The first apparatus may generate, based on the publishing intent and the subscription request, a topic instance. The first apparatus may send a third signal comprising an announcement message indicating the generated topic instance. The first apparatus may receive, from the third apparatus, a fourth signal comprising a subscription request for the generated topic instance. The first apparatus may send, to the third apparatus, at least one fifth signal comprising notifications and publish instances associated with the generated topic instance.

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 and apparatuses are described herein for securely connecting to a private local area network (LAN). In accordance with one embodiment, an apparatus may receive, from a private LAN that has been provisioned with first identifying information associated with the apparatus, a first broadcast message comprising an invitation to connect to the private LAN and the first identifying information. The apparatus may send, based on the first broadcast message comprising the first identifying information, a request for system information and second identifying information associated with the apparatus. The apparatus may receive, from the private LAN, the requested system information. The apparatus may send, based on the requested system information, a registration request and third identifying information associated with the apparatus. The apparatus may receive, from the private LAN, acceptance of the registration request.

Abstract: Methods and apparatus are disclosed for facilitating social discovery and social communication among M2M/IoT devices, connected via cellular networks, such as 3 GPP NR networks, and, optionally, supported by M2M/IoT servers.

Abstract: Distributed Service Layer Transactions (DSLTs) may be supported by a DSLT service at a service layer of a communications network to offload applications from the burden of managing the processing of DSLTs.

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 registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.

Abstract: Systems and methods are described to automate managing of relationships between IoT entities (e.g., devices, apps, users) and offloading the burden of managing these relationships from users. A Relationship Management Service (RM Service) is described herein for the autonomous establishment, modification, and tear-down of relationships between IoT entities.

Abstract: It is recognized herein that current cellular radio access technologies lack capabilities for both long range and low power usage devices. Public LPWAN networks are described herein that may use multiple network servers. Further, the network may distribute IoT devices (e.g., LoRa end nodes) across network servers. This may allow the public IoT networks to balance loads across network servers, to allow for redundancy of network servers, to provide differentiated services across network servers, and to permit roaming of end nodes across different public IoT networks, among other things.

Abstract: A set of point-of-contact information including a service level identifier, an address, a list of interfaces, and a set of interface selection preferences for each of several entities may be used to facilitate communications among the entities by selecting a preferred interface in accordance with the set. Interface preferences may also be derived from a set of policies. The preferred interface may be resolved in accordance with the preferences of multiple entities. Messages may include an interface type parameter to be used for forwarding of the message, and message forwarding may be resolved in accordance with the parameter and the messages.

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.