# US 2015/0143472 A1 · Method for establishing resource access authorization in m2m communication

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

- Number: US 2015/0143472 A1
- Document ID: US20150143472A1
- Status: Published application
- Kind: A1
- Application number: 14/403,977
- Filed: 2012-11-21
- Published: 2015-05-21
- Earliest claimed: 2012-05-30
- Assignees: Modacom Co., Ltd.
- Applicants: Modacom Co., Ltd.
- Inventors: Kyung-su Kim; Jaeho Lee; Yong-jin Kim
- Web page: https://patentgrep.com/patent/US20150143472A1

## CPC

- H04L 63/10: {for controlling access to devices or network resources}
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 12/069: using certificates or pre-shared keys
- H04W 12/084: using delegated authorisation, e.g. open authorisation [OAuth] protocol
- H04W 48/02: Access restriction performed under specific conditions
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0892: {by using authentication-authorization-accounting [AAA] servers or protocols}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method for establishing a resource access authorization in M2M communication is provided. When an entity including a terminal, a gateway and an end user as client in a first M2M service provider domain attempts to access resource located in terminal or gateway in second M2M service provider domain, the method includes receiving client credential allocated from M2M Authentication Server (MAS1) in first M2M service provider domain by performing client registration to Network Service Capabilities Layer (NSCL1) in first M2M service provider domain by client, requesting an authorization to access resource to resource owner through NSCL (NSCL2) in second M2M service provider domain based on information about Universal Resource Identifier (URI) of resource by client, verifying client through MAS1 by the resource owner, authorizing client to access the resource by the resource owner, and issuing access token to the client by MAS (MAS2) in second M2M service provider domain.

## Claims

### Claim at position 1

1-34. (canceled)

### Claim 35

A method for establishing an authorization to access resource in Machine-to-Machine (M2M) communication, when an entity selected from a terminal, a gateway and an end user as a client in an M2M service provider domain attempts to access resource located in a terminal or a gateway in the same M2M service provider domain, the method comprising:
receiving by the client a client credential allocated from an authentication server for providing an authentication service in the M2M service provider domain by performing a client registration to a service layer of an M2M server for providing an M2M service which is required in the M2M service provider domain;
requesting an authorization to access the resource to a resource owner of the resource through the service layer based on information about a Universal Resource Identifier (URI) of the resource by the client;
verifying by the resource owner the client through the authentication server;
granting the authorization for the client to access the resource by the resource owner; and
issuing an access token to the client by the authentication server in the M2M service provider domain.

### Claim 36 (depends on 35)

The method of claim 35, further comprising acquiring the information about the URI of the resource through one of the service layer and the resource owner by the client.

### Claim 37 (depends on 35)

The method of claim 35, further comprising:
issuing an authorization code to the client by the authentication server; and
requesting an access token to the authentication server using the issued authorization code by the client.

### Claim 38 (depends on 35)

The method of claim 35, wherein the authorization comprises:
requesting generation or update of an access right source associated with the resource to an entity in which the resource is located; and
notifying the authentication server that the client has been authorized.

### Claim 39

(canceled)

### Claim 40 (depends on 35)

The method of claim 35, wherein a lifetime is set for the access token.

### Claim 41

A method for accessing resource located in a terminal or a gateway in a Machine-to-Machine (M2M) service provider domain by an entity selected from a terminal, a gateway and an end user as a client in the same M2M service provider domain, the method comprising:
receiving a client credential allocated from an authentication server for providing an authentication service which is required in the M2M service provider domain by performing a client registration to a service layer of an M2M server for providing an M2M service in the M2M service provider domain;
requesting an authorization to access the resource to a resource owner of the resource based on information about a Universal Resource Identifier (URI) of the resource;
receiving an access token issued from the MAS in the M2M service provider domain; and
accessing the resource based on the issued access token.

### Claim 42 (depends on 40)

The method of claim 40, further comprising acquiring information about the resource through one of the service layer and the resource owner.

### Claim 43 (depends on 41)

The method of claim 41, wherein the client credential includes Client_identifier identifying the client and Client_Secret used as a password corresponding to the Client_identifier.

### Claim 44 (depends on 41)

The method of claim 41, further comprising:
getting an authorization code issued from the authentication server, as an indication indicating that the authorization request has been accepted; and
requesting an access token to the authentication server using the issued authorization code.

### Claim 45

A method for establishing an authorization of a client to access resource located in a terminal or a gateway in a Machine-to-Machine (M2M) service provider domain by a resource owner of the resource, the client being one of a terminal, a gateway, and an end user in the M2M service provider domain, the method comprising:
receiving an authorization request for the client;
verifying the client through an authentication server for providing an authentication service which is required in the M2M service provider domain; and
authorizing the client to an entity in which the resource is located and the authentication server.

### Claim 46 (depends on 45)

The method of claim 45, wherein the reception of an authorization request comprises receiving an authorization request message for the client through a service layer, and
wherein the authorization request message includes information about a client credential of the client and authorization type information.

### Claim 47 (depends on 46)

The method of claim 46, wherein the verification of the client comprises determining whether the client is normally registered to the authentication server based on the information about the client credential of the client.

### Claim 48 (depends on 45)

The method of claim 45, wherein the authorization comprises:
requesting generation or update of an access right resource for the resource to an entity in which the resource is located; and
notifying the authentication server that the client has been authorized.

### Claim 49 (depends on 48)

The method of claim 48, wherein if the resource owner is identical to the entity in which the resource is located, the requesting of generation or update of an access right resource comprises requesting generation or update of the access right resource locally.

### Claim 50

A method for authorizing access of a client to resource by a terminal or gateway having the resource in Machine-to-Machine (M2M) communication, the method comprising:
receiving an authorization request for the client from a resource owner of the resource;
establishing an authorization of the client to access the resource;
receiving an access token issued to the client from an authentication server for providing an authentication service; and
determining whether to authorize the client to access the resource according to whether the access token received from the authentication server is identical to an access token provided by the client.

### Claim 51 (depends on 50)

The method of claim 50, wherein the receiving of the authorization request comprises receiving the authorization request locally, if the terminal or gateway having the resource is identical to the resource owner.

### Claim 52

(canceled)

### Claim 53

(canceled)

### Claim 54 (depends on 50)

The method of claim 50, wherein the receiving of the authorization request comprises receiving an authorization request message including information about at least one of a client credential of the client, an access scope, and a resource location.

### Claim 55 (depends on 54)

The method of claim 54, wherein the establishing the authorization comprises generating or updating an access right resource having information about an authorization to access the resource based on information included in the authorization request message.

### Claim 56 (depends on 55)

The method of claim 55, wherein the receiving of the access token comprises managing the received access token by mapping the access token to the access right resource.

### Claim 57 (depends on 55)

The method of claim 55, wherein the determining of whether to authorize the client to access the resource comprises checking an allowed access scope for the client from the access right resource.
