Efficient resource representation exchange between service layers
Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. It is recognized herein that these requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others, by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.
1. An apparatus comprising at least one processor and memory, the memory storing executable instructions that, when executed by the at least one processor, implement a service layer of a communications network and cause the service layer to perform operations comprising:
storing, in the memory of the apparatus, one or more common attributes of one or more resources, so as to define one or more resource representation common parts (RRCPs), wherein the one or more common attributes comprise one or more static values usable, with portions of resources of the one or more resources, for one or more operations;
receiving, from a device or application on the communications network, a request message comprising information indicating a portion of a resource of the one or more resources and one or more identifiers associated with the one or more RRCPs;
retrieving, from the memory in response to the request message, the one or more RRCPs associated with the one or more identifiers; and
processing the request message based on the portion of the resource and the corresponding one or more RRCPs.
2. The apparatus of claim 1 , wherein the executable instructions further cause the service layer to perform operations comprising:
creating or updating one or more attributes of a target resource in accordance with the one or more common attributes of the one or more RRCPs.
3. The apparatus of claim 2 , wherein the executable instructions further cause the service layer to perform operations comprising:
sending a response to the device or application, the response indicating whether a relationship between the target resource and the one or more RRCPs is persistent or non-persistent.
4. The apparatus of claim 1 , wherein processing the request message comprises forwarding the request message to another service layer of the communications network.
5. The apparatus of claim 1 , wherein the request message further comprises an attribute tag that indicates one or more conditions for retrieving the one or more common attributes of the one or more RRCPs.
6. The apparatus of claim 1 , wherein the executable instructions further cause the service layer to perform operations comprising:
receiving a second request message to create a new RRCP comprising one or more values of one or more attributes;
creating the new RRCP, the new RRCP comprising the one or more values;
generating an identifier associated with the new RRCP;
storing, in the memory, the new RRCP and the identifier associated with the new RRCP; and
sending a response to the second request message to create the new RRCP, the response comprising the identifier associated with the new RRCP.
7. The apparatus of claim 1 , wherein the executable instructions further cause the service layer to perform operations comprising:
determining to create a new RRCP; and
determining one or more attribute values to be included in the new RRCP.
8. The apparatus of claim 7 , wherein the determination to create the new RRCP is based on messages received by the service layer from devices on the communications network.
9. The apparatus of claim 1 , wherein the request message is a resource creation, update, retrieval, or deletion request.
10. A method performed by a service layer of an apparatus connected to a communications network, the method comprising:
storing, in a memory of the apparatus, one or more common attributes of one or more resources, so as to define one or more resource representation common parts (RRCPs), wherein the one or more common attributes comprise one or more static values usable, with portions of resources of the one or more resources, for one or more operations;
receiving, from a device or application on the communications network, a request message comprising information indicating a portion of a resource of the one or more resources and one or more identifiers associated with the one or more RRCPs;
retrieving, from the memory in response to the request message, the one or more RRCPs associated with the one or more identifiers; and
processing the request message based on the portion of the resource and the corresponding one or more RRCPs.
11. The method of claim 10 , the method further comprising:
creating or updating one or more attributes of a target resource in accordance with the one or more common attributes of the one or more RRCPS.
12. The method of claim 11 , the method further comprising:
sending a response to the device or application, the response indicating whether a relationship between the target resource and the one or more RRCPs is persistent or non-persistent.
13. The method of claim 10 , wherein processing the request message comprises forwarding the request message to another service layer of the communications network.
14. The method of claim 10 , wherein the request message further comprises an attribute tag that indicates one or more conditions for retrieving the one or more common attributes of the one or more RRCPs.
15. The method of claim 10 , the method further comprising:
receiving a second request message to create a new RRCP comprising one or more values of one or more attributes;
creating the new RRCP, the new RRCP comprising the one or more values;
generating an identifier associated with the new RRCP;
storing, in the memory, the new RRCP and the identifier associated with the new RRCP; and
sending a response to the second request message to create the new RRCP, the response comprising the identifier associated with the new RRCP.
16. The method of claim 10 , the method further comprising:
determining to create a new RRCP; and
determining one or more attribute values to be included in the new RRCP.
17. The method of claim 16 , wherein the determination to create the new RRCP is based on messages received by the service layer from devices on the communications network.
18. The method of claim 10 , wherein the request message is a resource creation, update, retrieval, or deletion request.