Abstract: The network registrations of Internet-of-Things and like devices may be managed through the exchange of subscriber identity module and public land mobile network information. An exposure function may receive information regarding a device that needs cellular on-boarding, and pass the information to an operator subscription manager, and monitor a registration attempt of the device. The exposure function may process a request to allow transfer of ownership of a device, and such a request may include an expiration time, and an action to be taken upon expiry. The exposure function may also dis-enroll (off-board) devices. A central Equipment Identity Register (EIR) may store information relating to the home networks of devices, along with eSIM operating profiles of the device. An operator subscription manager may retrieve device information from a manufacturer server, create an eSIM operating profile, assign an IMSI, and exchange such information with entities such as user equipment and EIR.

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: 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 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: Existing approaches to security within network, for instance oneM2M networks, are limited. For example, content might only be protected while the content is in transit between entities that trust each other. Here, the integrity and the confidentiality of content in an M2M network are protected. Such content may be “at rest,” such that the content is stored at a hosting node. Only authorized entities may store and retrieve the data that is stored at the hosting node, and the data may be protected from a confidentiality perspective and an integrity perspective.

Abstract: A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Abstract: A machine-to-machine (M2M) gateway (GW) includes reachability, addressing, and repository (RAR) capability. The GW maintains a local mapping table and local device application repository, performs data aggregation, address/name translation, provides event reporting and establishes GW reachability and wake-up time. The GW supports requests from M2M applications or other capabilities within the GW, and from a network and application (N&A) domain RAR. The GW may include an M2M device and M2M gateway management (MDGM) capability that receives management requests for an M2M device and functions as a network proxy. The MDGM accepts and processes requests from the N&A domain on behalf of the M2M device and performs management functions of the M2M device on behalf of the N&A domain. The MDGM may request the N&A domain for permission to interact with the M2M device, initiate an interaction for device management tasks with the M2M device, and report to the N&A domain.

Abstract: A Data Producer may be configured to negotiate and initiate a Data Continuity service with an M2M/IoT system. This service may be for specific data sets or all data sets generated by the Data Producer. The M2M/IoT system may be configured to autonomously decide to start a Data Continuity Service for a data set of a Data Producer. The Data Producer may interact directly with an Aggregator SL to store its aggregated data set, and may also be configured to update and delete entries in this data set and start a data service on this aggregated data set. A Local SL may be configured to manage all interactions with an Aggregator SL, and the Local SL may be configured to retarget requests from the Data Producer to the Aggregator SL, including a request to start a data service on the aggregated data set.

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 machine-to-machine (M2M) node is configured to provide a communication management function to facilitate communication between a first service layer in a first network and a second service layer in a second network. The M2M node is configured to store a plurality of attributes for use by the communication management function and to receive via the first network, a first message from a first application in the first service layer. The M2M node is configured to determine, based on at least a first attribute identifying an expiration time after which the communication management function does not facilitate communication, that the communication management function is available to process the first message. The M2M node is configured to determine, based on at least a second attribute defining an access control list identifying applications in the first service layer, that the communication management function is available to process the first message.

Abstract: Resources on a host may be typically organized in a tree structure. In existing service layer technologies, the originators generating data may typically store their resources in default locations in such a tree, resulting in a relatively flat tree structure. As such, it may be beneficial for the service layer to provide assistance to the originators so that the originators can better structure their resources. Additionally, applications consuming the data may prefer data resources to be structured in a certain way, and may only be interested in a small subset of the hosted resources. Therefore, it may be beneficial for such applications to transmit to the service layer the resources that are of interest, and how to structure such resources. Embodiments described herein provide methods and systems to enable solutions to the problems discussed above, among others. Several aspects are introduced to enable such embodiments.

Abstract: Some services offered by M2M service layers will have contact information that will be used in order to interact with applications. For example, a service layer may need to send notification messages to an application. To do this, the service layer relies on stored contact information to know how to reach the application. If the device hosting the application moves and the application changes its contact information, then the contact information that is in the service layer is stale. As a result, these services will be inefficient, or in some cases, fail altogether. Embodiments described herein provide systems and methods to enable mechanisms to update stale contact information in M2M service layers.

Abstract: A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Abstract: Presented herein is a messaging system architecture that is referred to as an “Open Message Bus” (OMB). The OMB is a messaging system infrastructure that facilitates connectivity and communication between services. The OMB backbone may offer infrastructure services that can be leveraged by all services that connect to the OMB.

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 method and apparatus for distributed services and data in a machine-to-machine (M2M) communication network are disclosed. A network server, an M2M gateway, and M2M devices include an M2M service capability layer for supporting M2M service capabilities, respectively. Reference points may be defined for interactions between network service capability layers, between gateway service capability layers, between a gateway service capability layer and a device service capability layer of an M2M device, between M2M device applications, and/or between a network, gateway, or device service capability layer and an M2M application. The network server may be split into a control server and a data server at a service capability layer to provide service capabilities for control functions and service capabilities for data functions, respectively. The data server may be configured to interact with another data server to push or pull data or resources either directly or indirectly via the control server.

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: A 5G non-IP data delivery (NIDD) architecture is described including different options of data paths for non-IP data delivery through a 5G core network. A registration procedure is provided with new parameters for enabling the NIDD. Also, mechanisms are described for establishing a PDU session between a UE and SCS/AS for non-IP delivery. For example, the PDU session may pass through an AMF, SMF, and User Plane Function (UPF)/NEF. Additionally, methods of Mobile Originated (MO) and Mobile Terminated (MT) non-IP data transfer are described. Data buffering methods are also disclosed.

Abstract: Methods, systems, and apparatuses associated with the service layer may provide clustering management capabilities for sensor nodes in M2M/IoT SL platforms, via conventional clustering algorithm reselection and performance optimization, which may be based on service layer analytics. Clustering functionality may be adapted not only within the individual network model and optimization goals employed by each conventional clustering algorithm, but the conventional clustering algorithms themselves may be changed or reconfigured using service layer functionality. These re-configurations may be based on analytics indicating that performance of a sensor node is sub-optimal and may occur within a significantly larger time scale when compared to dynamic routing decisions on a per-message basis.

Abstract: Methods, devices, and systems may be used for semantics publishing and discovery. In an embodiment, a method for publishing semantics related resource identifiers may include adding a key word to an identifier of a semantics related resource and publishing the identifier to at least one of a sibling node and a child node. In another embodiment, a method may include using a Bloom filter to publish a semantics related resource. In another embodiment, a method may include publishing, by a semantics node, an identifier of a semantics related resource to a sibling node, while publishing a digest of the semantics node to a child node.