Efficient handling of collected data or analytics data in network data analytics function scenarios
According to one example embodiment, a method may include receiving, by a repository entity, first information on data related to a network entity. The method may further include storing, by the repository entity, second information related to the network entity based on the first information. The second information may include at least one of an identifier of the network entity and an identifier of a data acquiring entity having acquired the data.
1. A user data repository entity of a mobile communication network, comprising:
at least one processor; and
at least one memory including computer program code,
wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the user data repository entity at least to:
receive first information on data related to one or more user equipments;
store, to an entry, second information related to the one or more user equipments based on the first information, wherein the second information comprises at least one of:
an identifier of the one or more user equipments, and
at least one of an identifier of a network analytics function having acquired the data and at least one pointer to a storage location of the data; and
add, responsive to determining that the entry related to the one or more user equipments is already stored, a data set to the entry, wherein the data set is related to another network analytics function that has acquired additional data related to the one or more user equipments.
2. The user data repository entity of claim 1 , wherein the second information further comprises an analytics type of the data.
3. The user data repository entity of claim 1 , wherein an analytics type of the data is one of mobility analytics and communication analytics.
4. The user data repository entity of claim 1 , wherein the data related to the one or more user equipments comprises at least one data type of:
collected historical data related to the one or more user equipments;
determined statistical data related to the one or more user equipments; and
determined prediction data related to the one or more user equipments.
5. The user data repository entity of claim 1 , wherein the second information further comprises indications on availability of at least one data type of the data.
6. The user data repository entity of claim 1 , wherein at least one of:
each indication on availability of at least one data type of the data is provided with a timestamp indicative of a time of acquiring the respective data type of the data; and
each indication on availability of at least one data type of the data is provided with an indication of a period over which the respective data type of the data was acquired.
7. The user data repository entity of claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the user data repository entity at least to:
receive an information retrieval request indicative of the one or more user equipments; and
transmit the second information related to the one or more user equipments.
8. The user data repository entity of claim 1 , wherein each of the at least one pointer comprises the identifier of the network analytics function having acquired the data.
9. The user data repository entity of claim 1 , wherein each of the at least one pointer comprises an analytics type of the data pointed to by the pointer.
10. The user data repository entity of claim 9 , wherein the analytics type of the data is one of mobility analytics and communication analytics.
11. The user data repository entity of claim 1 , wherein each of the at least one pointer comprises a data type of the data pointed to by the pointer.
12. The user data repository entity of claim 11 , wherein the data comprises at least one data type of:
collected historical data related to the one or more user equipments;
determined statistical data related to the one or more user equipments; and
determined prediction data related to the one or more user equipments.
13. The user data repository entity of claim 8 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the user data repository entity at least to:
receive an information retrieval request indicative of the one or more user equipments; and
transmit the second information related to the one or more user equipments.
14. A network data analytics function entity, comprising:
at least one processor; and
at least one memory including computer program code,
wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the network data analytics function entity at least to:
transmit, to a user data repository entity, an information retrieval request indicative of one or more user equipments to be analyzed; and at least one of:
receive, from the user data repository entity, an entry comprising both information acquired by a network analytics function related to the one or more user equipments and information acquired by another network analytics function related to the one or more user equipments; and
receive, from the user data repository entity, an entry comprising a plurality of pointers to a plurality of storage locations of the data related to the one or more user equipments, wherein a respective pointer of the plurality of pointers further comprises an analytics type of the data pointed to by the respective pointer or a data type of the data pointed to by the pointer selected from the group consisting of historical data, statistical data or prediction data.
15. A method, comprising:
receiving, by a user data repository entity in a mobile communication network, first information on data related to one or more user equipments;
storing, by the user data repository entity in the mobile communication network, to an entry, second information related to the one or more user equipments based on the first information, wherein the second information comprises at least one of:
an identifier of the one or more user equipments, and
an identifier of a network analytics function having acquired the data and at least one pointer to a storage location of the data; and
adding, responsive to determining that the entry related to the one or more user equipments is already stored, a data set to the entry, wherein the data set is related to another network analytics function that has acquired additional data related to the one or more user equipments.