# US 2022/0012101 A1 · Cloud access method for iot devices, and devices performing the same

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0012101 A1
- Document ID: US20220012101A1
- Status: Published application
- Kind: A1
- Application number: 17/368,015
- Filed: 2021-07-06
- Published: 2022-01-13
- Earliest claimed: 2020-07-10
- Assignees: Electronics and Telecommunications Research Institute
- Applicants: Electronics and Telecommunications Research Institute
- Inventors: Joo Chul LEE
- Web page: https://patentgrep.com/patent/US20220012101A1

## CPC

- G06F 9/5072: {Grid computing}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 9/5011: {the resources being hardware resources other than CPUs, Servers and Terminals}
- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- H04L 12/413: with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A cloud access method of an internet of things (IoT) device and devices performing the cloud access method are disclosed. The cloud access method using a cloud proxy function includes receiving a first resource retrieval request of a client device from a cloud, extracting, from the first resource retrieval request, a device identification (ID) of a device including a resource for which a resource retrieval is requested, and transmitting a second resource retrieval request of the client device to the device based on the device ID.

## Claims

### Claim 1

A cloud access method using a cloud proxy function, comprising:
receiving, from a cloud, a first resource retrieval request of a client device;
extracting, from the first resource retrieval request, a device identification (ID) of a device comprising a resource for which a resource retrieval is requested; and
transmitting, to the device, a second resource retrieval request of the client device based on the device ID.

### Claim 2 (depends on 1)

The cloud access method of claim 1, wherein:
the first resource retrieval request comprises a proxy-uniform resource identifier (URI) option header, and
the proxy-URI option header is removed from the second resource retrieval request.

### Claim 3 (depends on 2)

The cloud access method of claim 2, wherein the proxy-URI option header comprises the device ID.

### Claim 4 (depends on 1)

The cloud access method of claim 1, wherein the device is a device that has not a cloud interworking function.

### Claim 5 (depends on 1)

The cloud access method of claim 1, wherein the transmitting comprises:
searching for the device ID and endpoint information of the device from a mapping list that is used for managing device-to-device (D2D) devices that have not a cloud interworking function for access to the cloud.

### Claim 6 (depends on 1)

The cloud access method of claim 1, further comprising:
requesting the cloud for registration of a cloud proxy device that supports the cloud proxy function; and
receiving an access token for the cloud proxy device that is issued by the requesting for the registration.

### Claim 7 (depends on 2)

The cloud access method of claim 2, comprising:
receiving a request for registration of the device from a mediator;
obtaining the resource of the device; and
publishing the resource of the device to the cloud.

### Claim 8 (depends on 7)

The cloud access method of claim 7, comprising:
generating an object entry corresponding to the device based on the resource and the device ID of the device and storing the generated object entry.

### Claim 9 (depends on 1)

The cloud access method of claim 1, wherein the first resource retrieval request is a resource retrieval request forwarded by the cloud after being transmitted from the client device to the cloud.

### Claim 10 (depends on 1)

A computer program embodied on a non-transitory computer readable medium, the computer program being configured to control a processor to perform the cloud access method of claim 1.

### Claim 11

A cloud proxy device supporting a cloud proxy function, comprising:
a memory configured to store therein at least one instruction; and
a processor configured to execute the instruction,
wherein, when the instruction is executed, the processor is configured to:
receive, from a cloud, a first resource retrieval request of a client device;
extract, from the first resource retrieval request, a device identification (ID) of a device-to-device (D2D) device comprising a resource for which a resource retrieval is requested; and
transmit, to the D2D device, a second resource retrieval request of the client device based on the device ID.

### Claim 12 (depends on 11)

The cloud proxy device of claim 11, wherein:
the first resource retrieval request comprises a proxy-uniform resource identifier (URI) option header, and
the proxy-URI option header is removed from the second resource retrieval request.

### Claim 13 (depends on 12)

The cloud proxy device of claim 12, wherein the proxy-URI option header comprises the device ID.

### Claim 14 (depends on 11)

The cloud proxy device of claim 11, wherein the D2D device is a device that has not a cloud interworking function.

### Claim 15 (depends on 11)

The cloud proxy device of claim 11, wherein, for the transmitting, the processor is configured to:
search for the device ID and endpoint information of the D2D device from a mapping list that is used for managing devices that have not a cloud interworking function for access to the cloud.

### Claim 16 (depends on 11)

The cloud proxy device of claim 11, wherein the process is further configured to:
request the cloud for registration of the cloud proxy device; and
receive an access token for the cloud proxy device that is issued by the requesting for the registration.

### Claim 17 (depends on 12)

The cloud proxy device of claim 12, wherein the processor is further configured to:
receive a request for registration of the D2D device from a mediator;
obtain the resource of the D2D device; and
publish the resource of the D2D device to the cloud.

### Claim 18 (depends on 17)

The cloud proxy device of claim 17, wherein the processor is further configured to:
generate an object entry corresponding to the D2D device based on the resource and the device ID of the D2D device and store the generated object entry.

### Claim 19 (depends on 11)

The cloud proxy device of claim 11, wherein the first resource retrieval request is a resource retrieval request that is forwarded by the cloud after being transmitted from the client device to the cloud.

### Claim 20 (depends on 16)

The cloud proxy device of claim 16, wherein the processor is configured to:
request the cloud for the registration of the cloud proxy device in response to cloud setting provisioning of a mediator.
