Systems and methods for enabling access to third party services via a service layer
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.
1. A node comprising circuitry configured to:
create a resource within a service of the node, wherein the resource is a uniquely addressable element in a Resource Oriented Architecture (ROA) having a representation that can be manipulated via RESTful methods, wherein the service supports service capabilities through a set of Application Programming Interfaces (APIs) and wherein the resource represents an external service outside of the service and determines a mapping of one or more parameters of the resource to an Application Programming Interface (API) associated with the external service, wherein the resource is accessible by one or more applications via one or more protocols of the service;
receive, from an application based on a protocol associated with the service, a discovery request;
send, to the application based on the protocol associated with the service, a discovery result comprising one or more URIs of one or more resources representing the external service based on one or more features indicated by the discovery request;
receive, from the application and based on the protocol associated with the service, a first request associated with the resource;
send, to the external service via the API of the external service, one or more second requests, the one or more second requests being generated from the first request based on the mapping,
wherein the external service is provided to the application via the resource so that requests associated with the application can be communicated via the service;
receive, from the external service via the API of the external service, one or more first responses to the one or more second requests; and
send, to the application, a second response to the first request, wherein the second response is based on the protocol associated with the service and comprises information from the one or more first responses received to the one or more second requests.
2. The node of claim 1 , wherein the service is provided as a middleware service in a service layer located on top of network protocol stacks for IoT services.
3. The node of claim 2 , wherein the service layer is defined according to ETSI/oneM2M standards.
4. The node of claim 1 , wherein the node proxies data to the external service from the service for the application.
5. The node of claim 1 , wherein the API comprises input parameters and output parameters.
6. The node of claim 5 , wherein the API further comprises access credentials.
7. The node of claim 1 , wherein the discovery result identifies one or more topics that match the one or more features indicated by the discovery request.
8. A method comprising:
creating a resource within a service of a node, wherein the resource is a uniquely addressable element in a Resource Oriented Architecture (ROA) having a representation that can be manipulated via RESTful methods, wherein the service supports service capabilities through a set of Application Programming Interfaces (APIs) and wherein the resource represents an external service outside of the service and determines a mapping of one or more parameters of the resource to an Application Programming Interface (API) associated with the external service, the API comprises input parameters, output parameters and access credentials, wherein the resource is accessible by one or more applications via one or more protocols of the service;
receive, from an application based on a protocol associated with the service, a discovery request;
send, to the application based on the protocol associated with the service, a discovery result identifying one or more resources representing the external service based on one or more features indicated by the discovery request;
receiving, from the application and based on the protocol associated with the service, a first request associated with the resource;
sending, to the external service via the API of the external service, one or more second requests, the one or more second requests being generated from the first request based on the mapping,
wherein the external service is provided to the application via the resource so that requests associated with the application can be communicated via the service;
receiving, from the external service via the API of the external service, one or more first responses to the one or more second requests; and
sending, to the application, a second response to the first request, wherein the second response is based on the protocol associated with the service and comprises information from the one or more first responses received to the one or more second requests.
9. The method of claim 8 , wherein the service is provided as a middleware service in a service layer located on top of network protocol stacks for IoT services.
10. The method of claim 9 , wherein the service layer is defined according to ETSI/oneM2M standards.
11. The method of claim 8 , further comprising:
proxying data to the external service from the service for the application.
12. The method of claim 8 , wherein the discovery result identifies one or more topics that match the one or more features indicated by the discovery request.