METHODS TO ENABLE DATA CONTINUITY SERVICE
A Data Producer may be configured to negotiate and initiate a Data Continuity service with an M2M/IoT system. This service may be for specific data sets or all data sets generated by the Data Producer. The M2M/IoT system may be configured to autonomously decide to start a Data Continuity Service for a data set of a Data Producer. The Data Producer may interact directly with an Aggregator SL to store its aggregated data set, and may also be configured to update and delete entries in this data set and start a data service on this aggregated data set. A Local SL may be configured to manage all interactions with an Aggregator SL, and the Local SL may be configured to retarget requests from the Data Producer to the Aggregator SL, including a request to start a data service on the aggregated data set.
1 . An apparatus comprising a processor and a memory, the memory storing computer-executable instructions which, when executed by the processor, implement a first service layer entity of a communications network and cause the first service layer entity to perform operations comprising:
receiving, from a data producer, a data management request, wherein the data management request comprises information associated with data generated by the data producer;
determining, based on the data management request, that a portion of the data generated by the data producer is at least one of stored or managed by a second service layer entity;
sending, to the second service layer entity, a request associated with the portion of the data, wherein the request to the second service layer entity comprises a request to retrieve the portion of the data from the second service layer entity; and
receiving, from the second service layer entity, a message responsive to the request, wherein the message comprises the portion of the data.
2 . The apparatus of claim 1 , wherein the sending the request to the second service layer entity comprises creating a link to the portion of the data.
3 . The apparatus of claim 1 , wherein the data management request comprises data to be at least one of stored or managed by the first service layer entity.
4 . The apparatus of claim 1 , wherein the data management request comprises an identifier of the second service layer entity.
5 . The apparatus of claim 1 , wherein the instructions, when executed further cause the first service layer entity to perform operations comprising:
sending, to a third service layer entity, a request to retrieve an identifier of the second service layer entity; and
receiving, from the third service layer entity, the identifier of the second service layer entity.
6 . A method performed by a first service layer entity of a communications network, the method comprising:
receiving, from a data producer, a data management request, wherein the data management request comprises information associated with data generated by the data producer;
determining, based on the data management request, that a portion of the data generated by the data producer is at least one of stored or managed by a second service layer entity;
sending, to the second service layer entity, a request associated with the portion of the data, wherein the request to the second service layer entity comprises a request to retrieve the portion of the data from the second service layer entity; and
receiving, from the second service layer entity, a message responsive to the request, wherein the message comprises the portion of the data.
7 . The method of claim 6 , wherein the sending the request to the second service layer entity comprises creating a link to the portion of the data.
8 . The method of claim 6 , wherein the data management request comprises data to be at least one of stored or managed at the first service layer entity.
9 . The method of claim 6 , wherein the data management request comprises an identifier of the second service layer entity.
10 . The method of claim 6 , wherein the method further comprises:
sending, to a third service layer entity, a request to retrieve an identifier of the second service layer entity; and
receiving, from the third service layer entity, the identifier of the second service layer entity.