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: The present application at least describes a computer-implemented method including a step of setting, via a service layer residing on a server outside of an underlying 3GPP network, a trigger in the underlying 3GPP network, where the trigger defines an QoS parameter change in the underlying 3GPP network. The underlying 3GPP network is configured with functionality to send a notification to the service layer upon detecting the QoS parameter change. The computer-implemented method also includes a step of receiving, from the underlying 3GPP network, the notification the detected QoS parameter change has occurred. The computer-implemented method further includes a step of performing, at the service layer residing on the server a service layer operation in response to the received notification.

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, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Abstract: A Delay Indicator parameter is contained in CoAP messages to reflect delay tolerance information. The Delay Indicator is leveraged by CoAP Clients and CoAP Servers to improve their behavior such as entering sleep mode to save energy while not violating delay requirements. A timeout mechanism for CoAP Response is enabled by a RESPONSE_Timer based on the Delay Indicator in CoAP ACK. Cancellation of CoAP Requests is enabled by leveraging the delay tolerance information as indicated by Delay Indicator.

Abstract: A method for communicating a data packet, the method includes receiving a data packet that supports a packet wash operation. The method determines whether the data packet can be forwarded along a network path towards a destination node without any modification. If the data packet cannot be forwarded along the network path towards the destination node without modification, the method determines whether conditions are met for performing the packet wash operation on the data packet. If the conditions are met, the packet wash operation is performed to generate a washed data packet. The packet wash operation generates the washed data packet by modifying a size of a payload of the data packet based on a packet wash specification that associates attributes to a plurality of data payload portions of the payload of the data packet. The washed data packet is forwarded along the network path towards the destination node.

Abstract: An M2M Service Layer is expanded to access the services of third parties and exchange data with these third parties. The M2M Service Layer is then able to act as a proxy between M2M Devices and the third party services. The M2M Service Layer is able to present a single/consistent interface, or API, to the M2M Device and hide the details of the third party service provider from the M2M Device.

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 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: A method implemented by an end user device in a network, comprises transmitting user service expectation data to a network element (NE) in the network, the user service expectation data describing an expected network attribute of a path between the end user device and a destination, receiving path aware network data from the NE in response to transmitting the user service expectation data describing the expected network attribute to the NE, the path aware network data comprising a path index, path quality information, and data plane information, the path index identifying the path, the path quality information describing a network attribute supported by the NE on the path, and the data plane information comprising information associated with a protocol by which to transmit a data packet along the path, and transmitting the data packet along the path based on the data plane information.

Abstract: A method implemented by a network element (NE) in a mobile edge cloud (MEC) network, comprising receiving, by the NE, an offloading request message from a client, the offloading request message comprising task-related data describing a task associated with an application executable at the client, determining, by the NE, whether to offload the task to an edge cloud server of a plurality of edge cloud servers distributed within the MEC network based on the task-related data and server data associated with each of the plurality of edge cloud servers, transmitting, by the NE, a response message to the client based on whether the task is offloaded to the edge cloud server.

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: The present application is directed to a device on a network that is configured to add a service. The device includes a memory that is operably coupled to the processor. The processor is adapted to configure a service enablement policy. The processor is also adapted to receive a request to add the service from a service provider. The processor is adapted to check the service enablement policy for adding the service. The processor is also adapted to collaborate with another device to harmonize the service enablement policy and the host selection criteria. Further, the processor is adapted to send a reply to the service provider. The present application is also directed to a method for adding a service.

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: 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: 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 method is applied to an electronic device, and includes: obtaining content copied by a user on a first page, and determining a category to which the content belongs; obtaining a category of a second page; matching the category of the content against the category of the second page; and if a matching result is not empty, displaying at least one operation option on the second page, where the at least one operation option has a function of performing an operation for the content on the second page, so that the electronic device directly performs the function after the user selects the operation option.

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.

Abstract: An M2M Service Layer is expanded to access the services of third parties and exchange data with these third parties. The M2M Service Layer is then able to act as a proxy between M2M Devices and the third party services. The M2M Service Layer is able to present a single/consistent interface, or API, to the M2M Device and hide the details of the third party service provider from the M2M Device.