Systems and methods for enabling access to third party services via a service layer

US12301681B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12301681-B2
Application numberUS-202318530713-A
CountryUS
Kind codeB2
Filing dateDec 6, 2023
Priority dateSep 17, 2014
Publication dateMay 13, 2025
Grant dateMay 13, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

The invention claimed is: 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.

Assignees

Inventors

Classifications

  • involving control of end-device applications over a network · CPC title

  • H04L67/53Primary

    using third party service providers · CPC title

  • H04W4/70Primary

    Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

  • Integrating service provisioning from a plurality of service providers · CPC title

  • H04L67/51Primary

    Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12301681B2 cover?
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.
Who is the assignee on this patent?
Convida Wireless LLC
What technology area does this patent fall under?
Primary CPC classification H04L67/53. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 13 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).