Enhanced M2M content management based on interest
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.
1. A method for a service layer supporting service capabilities through a set of Application Programming Interfaces (APIs), the service layer being a middleware layer supporting the service capabilities for a plurality of applications on top of underlying network protocols, the method comprising:
receiving, via a network, indications for data which is from more than one applications, wherein the indications for data is associated with filtering criteria for filtering series of data from the more than one applications connected to the service layer and one or more time periods for data, wherein the data is stored in one or more resources of a device associated with resource uniform resource identifiers (URIs) in the service layer, wherein the one or more resources are identified by the resource URIs and the one or more resources are uniquely addressable elements in a Resource Oriented Architecture (ROA);
determining, using the one or more time periods specified in the indications for data, when to filter data from the one or more resources;
filtering data to generate filtered data based on the filtering criteria;
determining, using the indications for data, a second service layer implemented in a second server in the network at which to store the filtered data associated with the one or more resources identified by the resource URIs, wherein the second service layer supports the service capabilities through a set of APIs of the second service layer; and
sending one or more requests to the APIs of the second service layer to store the filtered data.
2. The method of claim 1 , further comprising determining a pattern in customers' content request activity history and automatically generating an indicator.
3. The method of claim 1 , further comprising causing data to be transferred from a second device to a first device.
4. The method of claim 1 , further comprising:
receiving a request from a customer device to indicate where information is stored; and
sending an indication to the customer device of the information is stored.
5. The method of claim 1 , further comprising requesting that a second device transfers the data to a first device.
6. The method of claim 1 , wherein the more than one applications are executed in at least in part in machine-to-machine (M2M) devices.
7. A server comprising one or more processors, one or more memories, and communication circuitry, the server being connected to a communications network via its communication circuitry and implementing a service layer, wherein the service layer supports service capabilities through a set of Application Programming Interfaces (APIs), the service layer being a middleware layer supporting the service capabilities for a plurality of applications on top of underlying network protocols, the server further including computer-executable instructions stored in the one or more memories of the server which, when executed by the one or more processors of the server, cause the server to perform functions for the service layer that comprises:
receive, via a network, indications for data which is from more than one applications, wherein the indications for data is associated with filtering criteria for filtering series of data from the more than one applications connected to the service layer and one or more time periods for data, wherein the data is stored in one or more resources of a device associated with resource uniform resource identifiers (URIs) in the service layer, wherein the one or more resources are identified by the resource URIs and the one or more resources are uniquely addressable elements in a Resource Oriented Architecture (ROA);
determining, using the one or more time periods specified in the indications for data, when to filter data from the one or more resources;
filtering data to generate filtered data based on the filtering criteria;
determine, using the indications for data, a second service layer implemented in a second server in the network at which to store the filtered data associated with the one or more resources identified by the resource URIs, wherein the second service layer supports the service capabilities through a set of APIs of the second service layer; and
sending one or more requests to the APIs of the second service layer to store the filtered data.
8. The server of claim 7 , wherein the computer-executable instructions further cause the server to cause data to be transferred from a second device to a first device.
9. The server of claim 7 , wherein the computer-executable instructions further cause the server to:
receive a request from a customer device to indicate where information is stored; and
send an indication to the customer device of where the information is stored.
10. The server of claim 7 , wherein the more than one applications are executed in at least in part in machine-to-machine (M2M) devices.
11. The server of claim 7 , wherein the computer-executable instructions further cause the server to determine a pattern in content request activity history of customers and automatically generating an indicator.