Service layer methods for offloading IoT application message generation and response handling
A service layer may be configured to offload requests and responses on behalf of IoT applications in order to reduce congestion and/or overhead on underlying networks, applications and devices. The service layer may be enabled with the capability to script and generate IoT application requests such that the requests can be initiated by the service layer without the IoT application having to re-issue the same request repeatedly (e.g., to periodically retrieve a sensor reading). This scripting may be initiated by request originators. The service layer may support the capability to monitor and detect repetitive request patterns and initiate the scripting itself. This scripting functionality may enable the service layer to perform operations on behalf of IoT applications. As a result, the messaging overhead on IoT applications and devices as well as underlying networks can be minimized.
1 . A method implemented by a service supporting capabilities through a set of Application Programming Interfaces (APIs), the method comprising:
receiving, from a first entity, a plurality of requests to communicate with a second entity;
determining that two or more of the plurality of requests to communicate with the second entity form a pattern of repetitive requests;
based on determining that two or more of the plurality of requests to communicate with the second entity form the pattern of repetitive requests, creating and storing a scripted request resource, wherein the scripted request resource enables the service to create and send scripted requests to the second entity on behalf of the first entity, wherein the scripted request resource comprises one or more conditions for triggering the creation of one or more scripted requests, and wherein the scripted request resource further comprises an identifier of a schema comprising information defining at least the ordering of elements and data type definitions of values of the elements of a valid scripted request;
creating and sending, to the second entity, based on determining that one or more of the conditions for triggering the generation of the one or more scripted requests has been satisfied and based on the identified schema, a plurality of scripted requests;
sending, to the first entity, an indication that the scripted request resource has been created and an identifier associated with the scripted request resource;
receiving, from the second entity, a plurality of responses to the plurality of scripted requests;
processing, at the service and based on one or more response parameters identified in the scripted request resource, the plurality of responses, wherein the processing comprises at least aggregating the plurality of responses; and
sending, to the first entity, the processed responses.
2 . The method of claim 1 , wherein the plurality of scripted requests are used by the service to communicate information to the second entity automatically on behalf of the first entity.
3 . The method of claim 1 , wherein the service is configured with one or more policies that enable the service to determine whether the plurality of requests to communicate with the second entity form the pattern of repetitive requests.
4 . The method of claim 1 , further comprising receiving, from the first entity, an instruction to automatically create the scripted request resource based on determining at the service that two or more of the requests to communicate with the second entity form the pattern of repetitive requests.
5 . The method of claim 1 , further comprising:
receiving, from the first entity, a request to update a condition of the scripted request resource; and
updating, based on the request to update the condition of the scripted request resource, the condition of the scripted request resource.
6 . The method of claim 1 , wherein the information, of the identified schema, further comprises one or more of:
information indicative of which of the one or more elements of the valid scripted request are mandatory; or
information indicative of which of the one or more elements of the valid scripted request are optional.
7 . An apparatus comprising:
one or more processors; and
memory storing computer-executable instructions which, when executed by the one or more processors, implement a service supporting capabilities of a communications network through a set of Application Programming Interfaces (APIs) and cause the service to perform operations comprising:
receiving, from a first entity, a plurality of requests to communicate with a second entity;
determining that two or more of the plurality of requests to communicate with the second entity form a pattern of repetitive requests;
based on determining that two or more of the plurality of requests to communicate with the second entity form the pattern of repetitive requests, creating and storing a scripted request resource, wherein the scripted request resource enables the service to create and send scripted requests to the second entity on behalf of the first entity, wherein the scripted request resource comprises one or more conditions for triggering the creation of one or more scripted requests, and wherein the scripted request resource further comprises an identifier of a schema comprising information defining at least the ordering of elements and data type definitions of values of the elements of a valid scripted request;
creating and sending, to the second entity, based on determining that one or more of the conditions for triggering the generation of the one or more scripted requests has been satisfied and based on the identified schema, a plurality of scripted requests;
sending, to the first entity, an indication that the scripted request resource has been created and an identifier associated with the scripted request resource;
receiving, from the second entity, a plurality of responses to the plurality of scripted requests;
processing, at the service and based on one or more response parameters identified in the scripted request resource, the plurality of responses, wherein the processing comprises at least aggregating the plurality of responses; and
sending, to the first entity, the processed responses.
8 . The apparatus of claim 7 , wherein the plurality of scripted requests are used by the service to communicate information to the second entity automatically on behalf of the first entity.
9 . The apparatus of claim 7 , wherein the service is configured with one or more policies that enable the service to determine whether the plurality of requests to communicate with the second entity form the pattern of repetitive requests.
10 . The apparatus of claim 7 , wherein the instructions, when executed, further cause the service to perform operations comprising receiving, from the first entity, an instruction to automatically create the scripted request resource based on determining at the service that two or more of the requests to communicate with the second entity form the pattern of repetitive requests.
11 . The apparatus of claim 7 , wherein the instructions, when executed, further cause the service to perform operations comprising:
receiving, from the first entity, a request to update a condition of the scripted request resource; and
updating, based on the request to update the condition of the scripted request resource, the condition of the scripted request resource.
12 . The apparatus of claim 7 , wherein the information, of the identified schema, further comprises one or more of:
information indicative of which of the one or more elements of the valid scripted request are mandatory; or
information indicative of which of the one or more elements of the valid scripted request are optional.
13 . A computer-readable storage medium storing computer-executable instructions which, when executed by a processor of a service supporting capabilities through a set of Application Programming Interfaces (APIs), cause the service to perform operations comprising:
receiving, from a first entity, a plurality of requests to communicate with a second entity;
determining that two or more of the plurality of requests to communicate with the second entity form a pattern of repetitive requests;
based on determining that two or more of the plurality of requests to communicate with the second entity form the pattern of repetitive requests, creating and storing a scripted request resource, wherein the scripted request resource enables the service to create and send scripted requests to the second entity on behalf of the first entity, wherein the scripted request resource comprises one or more conditions for triggering the creation of one or more scripted requests, and wherein the scripted request resource further comprises an identifier of a schema comprising information defining at least the ordering of elements and data type definitions of values of the elements of a valid scripted request; and
creating and sending, to the second entity, based on determining that one or more of the conditions for triggering the generation of the one or more scripted requests has been satisfied and based on the identified schema, a plurality of scripted requests;
sending, to the first entity, an indication that the scripted request resource has been created and an identifier associated with the scripted request resource;
receiving, from the second entity, a plurality of responses to the plurality of scripted requests;
processing, at the service and based on one or more response parameters identified in the scripted request resource, the plurality of responses, wherein the processing comprises at least aggregating the plurality of responses; and
sending, to the first entity, the processed responses.
14 . The computer-readable storage medium of claim 13 , wherein the plurality of scripted requests are used by the service to communicate information to the second entity automatically on behalf of the first entity.
15 . The computer-readable storage medium of claim 13 , wherein the service is configured with one or more policies that enable the service to determine whether the plurality of requests to communicate with the second entity form the pattern of repetitive requests.
16 . The computer-readable storage medium of claim 13 , wherein the instructions, when executed, further cause the service to perform operations comprising receiving, from the first entity, an instruction to automatically create the scripted request resource based on determining at the service that two or more of the requests to communicate with the second entity form the pattern of repetitive requests.
17 . The computer-readable storage medium of claim 13 , wherein the instructions, when executed, further cause the service to perform operations comprising:
receiving, from the first entity, a request to update a condition of the scripted request resource; and
updating, based on the request to update the condition of the scripted request resource, the condition of the scripted request resource.
18 . The computer-readable storage medium of claim 13 , wherein the information, of the identified schema, further comprises one or more of:
information indicative of which of the one or more elements of the valid scripted request are mandatory; or
information indicative of which of the one or more elements of the valid scripted request are optional.