Abstract: Internet of Things (IoT) event objects can be tailored to specific device types and capabilities. An IoT event object can use a flexible definition of an event that can be reconfigured. An IoT event object allows for the ability to set different triggering conditions and priorities. Individual event definitions can be extended to create more complex events. A Notification Handler supports sending a request or command in response to an event that requires action.

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: Method and apparatus are described for delivering triggers and small data. In an embodiment, a receiver may be configured to receive a trigger or small data packet, and a transmitter may be configured to transmit a subscriber information request to see whether a subscriber is present. The receiver may be further configured to receive an identity of a second node on a condition that the subscriber is present. The transmitter may be further configured to transmit the trigger or small data packet to the second node over an interface, the second node configured to create an Internet Protocol (IP) packet with an IP address containing the trigger or small data packet and deliver the IP packet to a wireless transmit/receive unit (WTRU) using the IP address and a default or dedicated bearer of the WTRU.

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: 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: Methods and apparatuses are described herein for configuration of background data transfers (BDTs) between local area data networks (LADNs). An apparatus may receive a message indicating a request from a user equipment (UE) for a data transfer of data originating from the UE. The apparatus may send, to a database, a request for subscription information associated with the UE and a policy profile associated with the UE to determine whether there is an existing BDT policy. The apparatus may receive, from the database, a response indicating whether there is an existing BDT policy that can be re-used. The apparatus may determine, based on the received response, a BDT policy for the data transfer and a LADN to service the data transfer. The apparatus may send, to the LADN via a radio access network (RAN) node, a notification message of an arrival time and data rate for the data transfer.

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: Methods, systems, and apparatus in a service layer environment may create, update, or delete access control policy triples whenever an access control policy (ACP) resource is created, updated, or deleted. In addition, methods address potentially frequent and unnecessary ACP triple management.

Abstract: An IoT E2E Service Layer Security Management system supports methods and procedures to allow an application to establish, use, and teardown an IoT SL communication session that has application specified E2E security preferences and that targets one or more SL addressable targets (e.g., an IoT application, device, or gateway SL addressable resource). E2E SL Session based methods and procedures described herein achieve a required overall E2E security level, by allowing IoT SL instances to influence and coordinate hop security for a multi-hop communication path spanning across multiple intermediary nodes. The methods and procedures described herein reduce overhead, simplify and obviate the need for E2E service level nodes (initiation and termination nodes) from having to perform security service negotiation, in order to establish secure hop-by-hop security associations aligned with an E2E security requirement.

Abstract: Methods and procedures allow devices interwork with various types of service layers by updating the device to support the protocol of the M2M/IoT service layer that is being communicated with. Devices can coordinate/initiate download of a service layer API that is compatible with the service layer the device is attempting to use. A service layer can coordinate the autonomous update of a device with the proper service layer API which allows the device to then communicate and use services supported by the service layer component to the device. A service layer can detect a device or application lacking proper service layer functionality and can trigger a management entity to update the device or application with the service layer API required such that the device can then register to the service layer and use its services. A device or application can be customized or optimized to the service layer that it is registered to and using.

Abstract: Mechanisms for service layer charging correlation are disclosed. Embodiments can include a Service Domain Charging Correlation Function (SD-CCF), which is responsible for interacting with underlying network and correlating charging information at service layer. Charging correlation information can be used to enable and facilitate the service layer charging correlation.

Abstract: Two methods are described to enable the communication between two service layer entities that do not have registration relations. In the first method, service layer entities employ a retargeting table that stores the service layer entity to retarget the message in order to deliver the message to the destination. In a second method, an infrastructure node in a service provider employs a retargeting chain table that stores a chain of entities that can retarget the message to the destination.

Abstract: The present application is at least directed to an apparatus on a network. The apparatus includes a non-transitory memory having instructions stored thereon for online charging of an event. The apparatus also includes a processor that is operably coupled to the non-transitory memory. The processor is configured to execute the instructions of receiving, from an M2M gateway, a rating request message for service layer online charging. The processor is also configured to execute the instructions of determining a rating scheme to charge for the event. The processor is further configured to execute the instructions of calculating an amount of service units based on the rating request message and determined rating scheme. The processor is even further configured to execute the instructions of sending, to the M2M gateway, a rating response based upon the calculated amount of service units.

Abstract: Methods, systems, and devices may be used for assigning names and bootstrapping of security credentials for Smart Objects inside a Digital Home environment. Methods, systems, and devices for identification and security bootstrapping of a smart object within a digital home environment may include automated assignment of a device level ID and security credential for each smart object in the home using a resource directory.

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: Internet of Things (IoT) event objects can be tailored to specific device types and capabilities. An IoT event object can use a flexible definition of an event that can be reconfigured. An IoT event object allows for the ability to set different triggering conditions and priorities. Individual event definitions can be extended to create more complex events. A Notification Handler supports sending a request or command in response to an event that requires action.

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: 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: 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: Methods, devices, and systems are disclosed for an M2M Interest Function. An M2M Interest Function may receive requests from users to publish the users' personal interests in particular data identify relationships and patterns in the data. Associated data may then be stored in a single best location for such data based on various criteria rather than on separate M2M Gateways or M2M Servers. This location may be provided to users interested in such data. Relationship and association data may be provided to M2M gateways.