Method and device for processing a specific request message in wireless communication system

• US 9,867,164 B2
• Filed: 09/11/2014
• Issued: 01/09/2018
• Est. Priority Date: 09/09/2013
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Choi, Heedong, Park, Seungkyu, Kim, Seongyun, Ahn, Hongbeom, Jeong, Seungmyeong
• Primary Examiner(s): Nguyen, Steven H
• Application Number:
  US14/912,837
• Publication Number:
  US 20160212732A1
• Time in Patent Office: 1,216 Days
• Field of Search: None
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 72/04 Wireless resource allocation
• CPC Class Codes: H04W 72/21 in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 92/18 between terminal devices

Abstract

According to one embodiment of the present invention, a method for processing a request message in a wireless communication is disclosed, and the method is performed by a first M2M device and comprises the steps of: receiving a request message related to a specific resource type from a second M2M device; determining whether the specific resource type is supported; searching for another M2M device supporting the specific resource type if the specific resource type is not supported; processing the request message so as to transfer the processed request message to a third M2M device if the third M2M device supporting the specific resource type is discovered according to the searched result, wherein an operation related to the request message is performed by the third M2M device instead of the first M2M device; receiving a response message including the processed result of the request message from the other device; and processing the received response message so as to transfer the processed response message to a transmission device.

Claims

1. A method for processing a request message by a first machine-to-machine (M2M) device in a wireless communication system, comprising:

receiving a request message related to a specific resource type from a second M2M device;

determining whether the specific resource type is supported;

if the specific resource type is not supported, discovering another M2M device supporting the specific resource type;

if a third M2M device supporting the specific resource type is discovered according to the discovery result, processing the request message and transmitting the processed request message to the third M2M device, wherein an operation related to the request message is performed by the third M2M device instead of the first M2M device;

receiving a response message including a result of processing the request message from the another M2M device; and

processing the received response message, and transmitting the processed response message to the second M2M device.

2. The method according to claim 1, wherein the determining whether the specific resource type is supported includes:

determining whether the specific resource type is contained in a value of ‘

supportedResourceType’

attribute contained in a <

CSEBase>

resource.

3. The method according to claim 1, further comprising:

prior to the discovering, determining whether the specific resource type is a resource type allowed to be processed by another device other than a device designated by the second M2M device.

4. The method according to claim 1, wherein the discovering includes:

determining whether the first M2M device has a specific right for the third M2M device; and

if the specific right for the third M2M device is present, determining whether the third M2M device supports the specific resource type.

5. The method according to claim 4, wherein the determining whether the first M2M device has a specific right for the third M2M device includes:

determining the presence or absence of the specific rights based on a first right in which the first M2M device is allowed to read ‘

supportedResourceType’

attribute contained in the resource of the third M2M device or a second right in which the first M2M device is allowed to perform an operation related to the request message to the third M2M device.

6. The method according to claim 1, further comprising:

if the third M2M device supporting the specific resource type is discovered according to the discovery result, including the specific resource type in the ‘

supportedResourceType’

attribute contained in <

CSEBase>

resource.

7. The method according to claim 1, further comprising:

if the third M2M device supporting the specific resource type is discovered according to the discovery result, before transmitting the processed request message to the third M2M device,

generating a resource having a specific resource type (‘

unsupportedResourceType’

).

8. The method according to claim 7, wherein the processed request message, the response message, and the processed response message include information regarding an address of a resource having the specific resource type.

9. A machine-to-machine (M2M) device configured to process a request message in a wireless communication system, comprising:

a radio frequency (RF) unit; and

a processor configured to control the RF unit,

wherein the processor receives a request message related to a specific resource type from a second M2M device, determines whether the specific resource type is supported, if the specific resource type is not supported, discovers another M2M device supporting the specific resource type, if a third M2M device supporting the specific resource type is discovered according to the discovery result, processes the request message and transmits the processed request message to the third M2M device, performs an operation related to the request message by the third M2M device instead of the first M2M device;

receives a response message including a result of processing the request message from the another M2M device; and

processes the received response message, and transmits the processed response message to the second M2M device.

10. The M2M device according to claim 9, wherein the processor determines whether the specific resource type is contained in a value of supportedResourceType attribute contained in a <

CSEBase>

resource so as to determine whether the specific resource type is supported.

11. The M2M device according to claim 9, wherein the processor,

prior to the discovering, determines whether the specific resource type is a resource type allowed to be processed by another device other than a device designated by the second M2M device.

12. The M2M device according to claim 9, wherein the processor determines whether the first M2M device has a specific right for the third M2M device;

and if the specific right for the third M2M device is present, determines whether the third M2M device supports the specific resource type.

13. The M2M device according to claim 12, wherein whether the first M2M device has a specific right for the third M2M device is determined based on a first right in which the first M2M device is allowed to read ‘

supportedResourceType’

attribute contained in the resource of the third M2M device or a second right in which the first M2M device is allowed to perform an operation related to the request message to the third M2M device.

14. The M2M device according to claim 9, wherein:

if the third M2M device supporting the specific resource type is discovered according to the discovery result, the processor includes the specific resource type in the ‘

supportedResourceType’

attribute contained in a <

CSEBase>

resource.

15. The M2M device according to claim 9, wherein:

if the third M2M device supporting the specific resource type is discovered according to the discovery result, before transmitting the processed request message to the third M2M device, the processor generates a resource having a specific resource type (‘

unsupportedResourceType’

).

16. The M2M device according to claim 15, wherein the processed request message, the response message, and the processed response message include information regarding an address of a resource having the specific resource type.