Method and device for deleting resource in M2M system
A method for operating a machine-to-machine (M2M) device in an M2M system includes generating a request message including information associated to deletion of a resource, the deletion being performed in response to an operation, and transmitting the request message to a counterpart M2M device. The information includes at least one of information notifying that the resource is deleted in response to the operation, information indicating the resource, information indicating at least one operation that is a condition of the deletion, information indicating content of the condition, or information for identifying an entity that performs an operation causing the deletion.
1 . A method for operating a machine-to-machine (M2M) device in an M2M system, the method comprising:
generating a request message requesting creation of a resource, wherein the resource comprises a <contentInstance> resource with corresponding attributes including data and a counter, wherein the counter has an initial value greater than 0 and is decremented by 1 for each RETRIEVE operation performed to the resource, wherein the RETRIEVE operation comprises another M2M device reading the data of the resource, and wherein the resource, including the data and the counter, should be deleted when the counter becomes 0; and
transmitting, by a transceiver, the request message to a hosting common service entity (CSE) to create the resource, the method further comprising deleting, by the hosting CSE, the resource including the data and the counter, based on the counter becoming 0 without the hosting CSE receiving an explicit deletion request.
2 . The method of claim 1 , wherein the corresponding attributes further include: resourceType, resourceID, resourceName, parentID, creationTime, and lastModifiedTime.
3 . The method of claim 1 , wherein the data comprises one or more of the following: sensor data, security data, health or medical data, biomedical data, or personal data.
4 . The method of claim 1 , wherein the M2M device comprises at least one of a CSE or an application entity AE.
5 . The method of claim 1 , further comprising:
receiving, from the hosting CSE in response to the request message, a response message.
6 . A method for operating a machine-to-machine (M2M) device in an M2M system, the method comprising:
receiving, by a transceiver, a request message requesting creation of a resource, wherein the resource comprises a <contentInstance> resource with corresponding attributes including data and a counter, wherein the counter has an initial value greater than 0 and is decremented by 1 for each RETRIEVE operation performed to the resource, wherein the RETRIEVE operation comprises another M2M device reading the data of the resource, and wherein the resource, including the data and the counter, should be deleted when the counter becomes 0;
creating the resource in response to the request message; and
deleting the resource including the data and the counter based on the counter becoming 0 without the M2M device receiving an explicit deletion request.
7 . The method of claim 6 , wherein the corresponding attributes further include: resourceType, resourceID, resourceName, parentID, creationTime, and lastModifiedTime.
8 . The method of claim 6 , wherein the data comprises one or more of the following: sensor data, security data, health or medical data, biomedical data, or personal data.
9 . The method of claim 6 , wherein the M2M device comprises at least one of a common service entity (CSE) or an application entity (AE).
10 . The method of claim 6 , wherein the request message is received from an application entity (AE), further comprising:
sending, to the AE in response to the request message, a response message.
11 . A machine-to-machine (M2M) device in an M2M system, the M2M device comprising:
a transceiver operatively coupled to a processor, wherein the transceiver and the processor are configured to:
receive a request message requesting creation of a resource, wherein the resource comprises a <contentInstance> resource with corresponding attributes including data and a counter, wherein the counter has an initial value greater than 0 and is decremented by 1 for each RETRIEVE operation performed to the resource, wherein the RETRIEVE operation comprises another M2M device reading the data of the resource, and wherein the resource, including the data and the counter, should be deleted when the counter becomes 0;
create the resource in response to the request message; and
delete the resource including the data and the counter based on the counter becoming 0 without the M2M device receiving an explicit deletion request.
12 . The M2M device of claim 11 , wherein the corresponding attributes further include: resourceType, resourceID, resourceName, parentID, creationTime, and lastModifiedTime.
13 . The M2M device of claim 11 , wherein the data comprises one or more of the following: sensor data, security data, health or medical data, biomedical data, or personal data.
14 . The M2M device of claim 11 , wherein the M2M device comprises at least one of a common service entity (CSE) or an application entity (AE).
15 . The M2M device of claim 11 , wherein the transceiver and the processor are further configured to:
transmit, in response to the request message, a response message.