Enhanced historical data support for network entities
By specifying selection criteria and processing instructions in the data management framework, generating and transmitting only required report data, the problem of delay and bandwidth high in NWDAF when processing historical data is solved, and load optimization and efficiency improvement of data consumers is achieved.
Patent Information
- Application Number
- CN202111173141.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-10-01
- Filing Date
- 2021-10-08
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-10-08
AI Technical Summary
The existing network data analysis function (NWDAF) needs to download and process a large amount of notification data when processing historical data, resulting in high delay and bandwidth consumption, and the inability to effectively reduce the amount of data, affecting the processing load of the data consumer.
By implementing the designation of selection criteria and processing instructions in the data management framework, generating reports or statistics, only sending the required report data to the data consumer, reducing the amount of data transmitted and processing load, and using the data management framework to cut data transmission, Only statistical analysis results are sent.
Optimize the delay of the data consumer, reduce bandwidth consumption, significantly reduce the processing load of the data consumer, and only transmit the necessary reporting data, improving data management efficiency.
Smart Images

Figure CN114374607B_ABST
Abstract
Description
Technical Field
[0001] At least some example embodiments relate to historical data support enhancements for network entities. In particular, at least some example embodiments relate to historical data support enhancements for a network data analysis function (NWDAF) or a data collection coordination function (DCCF), which are examples of such network entities.
[0002] List of abbreviations / initials
[0003] 3GPP Third Generation Partnership Project
[0004] 3CA 3G Consumer Adapter
[0005] 3PA 3G Producer Adapter
[0006] 5GC 5G Core Network
[0007] AF Application Function
[0008] AMF Access and Mobility Management Function
[0009] API Application Programming Interface
[0010] BSF binding support function
[0011] CA Consumer Adapter
[0012] CCA Client Certificate Assertion
[0013] D DCCF Adapter
[0014] DCCF Data Collection Coordination Function
[0015] NEF Network Exposure Function
[0016] NF Network Function
[0017] NFc Network Function Consumer
[0018] NFp Network Function Producer
[0019] NRF Network Repository Functionality
[0020] NWDAF network data analysis function
[0021] OAM Operations, Administration and Maintenance
[0022] PCF Policy Control Function
[0023] SCP Service Communication Proxy
[0024] SMF session management functions
[0025] S-NSSAI Network Slice Selection Auxiliary Information
[0026] TAI Tracking Area Identifier
[0027] UDM Unified Data Management
[0028] UE User Equipment Background Art
[0029] In order to understand the present invention, some knowledge about the principles of historical data collection and / or evaluation at a network entity (such as, for example, NWDAF as defined in 3GPP TS 23.288) is helpful.
[0030] References to NWDAF and the mentioned standards are used as examples only and should not be considered limiting of the present disclosure.Other network entities defined under different existing or to-be-developed standards may similarly benefit from at least the exemplary aspects disclosed below.
[0031] NWDAF was first defined in 3GPP Release 15 and extended in Release 16, and subsequently embodied in 3GPP TR 23.791. NWDAF computes analytics based on data collected from different data sources, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM), Application Function (AF), Operation, Administration and Maintenance (OAM), or any other data source within the communication network. It provides analytics identified by 3GPP-defined analytics identifiers to data consumers (also network entities) using services based on the architecture defined for 5GC.
[0032] For TR 23.700-91, a data management framework has been proposed as a solution to several key issues. Figure 1 An example of such a data management framework is depicted in This solution is documented in TR 23.700-91 as Solution #9.
[0033] Additionally, solution #9 has defined the formatting of notifications, where the DCCF / messaging framework can filter notifications based on given criteria.
[0034] For example, the formatting may be clubbing (or combining) of multiple notifications based on time or events. However, clubbing or other formatting will not reduce the amount of data sent via the notification.
[0035] For example, if the data management framework is used to fetch historical data from a repository with 500.000 applicable notifications and each notification is 1KB in size, 500MB of notification data needs to be delivered from the DCCF / messaging framework to the data consumer. That is, the currently proposed join or any other formatting approach will not reduce the amount of data to be transferred.
[0036] Currently, historical data is often used for statistical purposes, such as e.g.
[0037] How many times the location of the user equipment (UE) in a specific area has been determined within a specific duration,
[0038] Determination of how many calls were made by all UEs registered in a certain area during a certain period of time,
[0039] Determine how many times the AMF was overloaded last year, etc.
[0040] · How many people are calling / using text messages in Times Square, e.g. during New Year's Eve, is determined so that operators can plan network expansion accordingly.
[0041] So far, there is no way to obtain reports containing statistics obtained from historical data from a data management framework or data repository. In existing solutions, data consumers (such as NWDAF) receive all historical data and then calculate statistics or generate reports by themselves.
[0042] For example, if the data repository holds records of terminal devices such as user equipment UE1 and its mobility (Tracking Area Identifier (TAI) change) notification records, in one phase a huge amount of data may be stored, for example 5 million notifications stored for more than 3 years.
[0043] If NWDAF is now interested in knowing the frequency or count of UE1 movements for a specific TAI1 and TAI2 in the past 3 years, NWDAF queries DCCF / data repository. DCCF / data repository then returns 50.000 notifications (AMF notification objects) out of 5 million notifications. These 50.000 notification objects need to be delivered from the data repository / DCCF to the data consumer, such as NWDAF.
[0044] In addition, a notification object received from AMF / SMF usually has many additional attributes related to the event. This will be important if the size of the notification including those additional attributes is evaluated. According to TS 29.518 section 6.2.6.2.5 Type: Amf Event Report (which is a notification object for any type of event), AMF fills in about 25 parameters for different notifications.
[0045] Therefore, the existing data management framework solution with notification formatting will reduce the number of notification messages but not the amount of data. The NWDAF still needs to process all notifications in the message (ie, a large amount of data) to determine the statistics and prepare the required reports.
[0046] Furthermore, historical data is becoming important for NWDAF processing. Historical data can be stored in NWDAF or any network function (NF) that supports a repository. There can be a repository based on DCCF / messaging framework or a local repository attached to NWDAF / NF.
[0047] If there is a local repository attached to NWDAF1 / NF1 where NWDAF1 / NF1 stores notifications, and if another NWDAF2 wants to get data from NWDAF1 / NF1, the same problem will occur because NWDAF2 needs to get all related notifications, which may constitute a huge amount of data. Summary of the invention
[0048] It is an object of at least some example embodiments to improve the prior art.
[0049] This object is achieved by a method, an apparatus and a non-transitory storage medium as specified in the appended claims. More specifically, such improvements are set forth in the respective independent claims 1, 4, 11, 14, 21 and 22.
[0050] Advantageous further developments are set forth in the respective dependent claims.
[0051] Furthermore, a computer program product comprising computer executable code is provided which, when executed by a processor, performs the method according to any aspect of the method.
[0052] That is, while solution #9 in the aforementioned TR23.700-91 essentially describes a data management framework and how data may be formatted, at least some aspects of the present invention improve upon this prior art in that the data management framework is able to generate reports / statistics based on historical raw data (eg, notifications).
[0053] According to at least some example embodiments, at least one of the following advantages is achieved:
[0054] Consumers (such as NWDAF) do not need to download the complete data.
[0055] · Latency is optimized for NWDAF processing.
[0056] The bandwidth required to transmit the original data to the consumer is eliminated,
[0057] The tailoring of data delivered to data consumers as described in this application can be achieved through the data management framework described in solution #9 of TR23.700-91.
[0058] Whereas in pre-existing solutions, a data consumer such as NWDAF was the only entity that could apply statistical analysis, such as counting a certain number of times, e.g., 50,000, that UE1 moved, at least some aspects of the present invention enable a data management framework or data repository to send such statistical analysis / reporting to a data consumer such as NWDAF, stating that the count was a certain number, e.g., 50.000.
[0059] In this way, the data traffic on the internal interface is greatly reduced by the arrangement.
[0060] There is now an option to obtain only report / statistical data, such as counts of NF notifications (e.g. AMF notifications / SMF notifications) for specific events, so that the data sent to the data consuming entity via the interface is greatly reduced and the processing load for the data consumer is significantly removed.
[0061] In the following table, a comparison between the amount of necessary transmitted data in existing solutions and the amount of necessary transmitted data according to at least some example embodiments is shown.
[0062] Here, assume that 1 million notifications are stored in the following manner, for example:
[0063] Notification 1: AMF_EE_notification{UE1, TAI1, time: xyz.., parameter 1.. parameter 10}
[0064] Notification 2: AMF_EE_notification{UE1, TAI1, time: xyz.., parameter 1.. parameter 10}
[0065] Notification 3: AMF_EE_notification{UE1, TAI1, time: xyz.., parameter 1.. parameter 10}
[0066] ·…
[0067] Furthermore, assume that this would require 100MB of data to be transferred over the wire.
[0068]
[0069]
[0070] Further advantages will become apparent from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0071] Additional details, features, objects and advantages will be apparent from the following detailed description of example embodiments of at least some aspects taken in conjunction with the accompanying drawings, in which:
[0072] Figure 1 An example data management framework for 5GC proposed by solution #9 from 3GPP TR 23.700-91 is shown.
[0073] Figure 2 A flow chart illustrating an example method 1 in accordance with at least some embodiments is shown.
[0074] Figure 3 A flow chart illustrating an example method 2 in accordance with at least some embodiments is shown.
[0075] Figure 4 A signaling diagram illustrating an example embodiment of the present application within an example framework is shown.
[0076] Figure 5 A signaling diagram illustrating another example embodiment of the present application is shown.
[0077] Figure 6 Another example data management framework for 5GC is shown.
[0078] Figure 7 An example of data collection and distribution of event notifications according to one specific example embodiment is shown.
[0079] Figure 8 A schematic block diagram illustrating a configuration of a control unit in which at least some example embodiments may be implemented is shown. DETAILED DESCRIPTION
[0080] In the following, certain aspects are exemplified by at least some embodiments described in detail with reference to the accompanying drawings. Unless otherwise stated, the features of the example embodiments may be freely combined with each other. However, it should be clearly understood that the description of certain example embodiments / aspects is given by way of example only and is not intended to be understood as limiting the application to the disclosed details.
[0081] It should be understood that any modifications mentioned may be applied individually or in combination to the response aspects to which they relate, unless they are explicitly stated as excluding alternatives.
[0082] Furthermore, it should be understood that the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or only the method is described.
[0083] According to at least some example embodiments, a possibility is provided within a communication network environment for obtaining historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources (e.g., NWDAF, NF, AF, and NEF) within the communication network environment. In addition, a first device (e.g., a data consumer) specifies selection criteria that are to be applied to the historical data for performing queries on the historical data stored in a historical data repository associated with a second device (e.g., a data management framework, a data consumer, or a data source). In addition, at least one processing instruction (e.g., an output template / report template) is specified at the first device. The at least one processing instruction determines the generation of a report based on the defined query. Subsequently, the selection criteria and the processing instructions are sent to the second device, and the report generated at the second device thereafter is received based on the sent selection criteria and processing instructions.
[0084] exist Figure 2 , method 1 according to at least some example embodiments is illustrated.
[0085] According to the illustrative examples, at least some of the illustrated steps are distributed to be performed by a data consumer.
[0086] Method 1 starts in S200: Then, a possibility is provided within a communication network environment for obtaining historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources within the communication network environment (S20). Then, selection criteria are specified at a first device to be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with a second device (S21). In addition, at least one processing instruction is specified at the first device (S22), wherein the processing instruction determines the generation of a report based on the defined query. Then, the selection criteria and the processing instruction are sent to the second device (S23), and the report generated at the second device is received based on the sent selection criteria and processing instruction (S24). Thereafter, the method ends (S201).
[0087] According to at least some example embodiments, the method further includes discovering the second device by querying a third device (e.g., a network repository function (NRF)), and receiving from the third device an indication of the second device based on capabilities registered by the second device at the third device. In addition, the capabilities indicate a possibility for obtaining historical data indicating events occurring within the communication network environment.
[0088] According to at least some example embodiments, the capabilities of the second device include a duration for which the historical data is stored in an associated historical data repository.
[0089] In addition, Figure 3In FIG. 2 , a method 2 according to at least some example embodiments is illustrated. According to an exemplary example, at least some of the steps illustrated are distributed to be performed by a data management framework DMF and / or a data source and / or another data consumer.
[0090] Method 2 starts in S300. A possibility is provided within a communication network environment for obtaining historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources within the communication network environment (S30). Subsequently, a selection criterion and at least one processing instruction are received from a first device, the selection criterion being applied to the historical data for performing a query on the historical data stored in a historical data repository associated with a second device, and wherein the processing instruction determines the generation of a report based on the defined query (S31). Thereafter, a report is generated based on the received selection criterion and processing instruction (S32). Subsequently, the generated report is sent to the first device or to another device indicated by the first device (S33) and method 2 ends (S301).
[0091] According to at least some example embodiments, generation of a report based on received selection criteria and processing instructions includes: acquiring historical data from a historical data repository associated with a second device based on the selected criteria, providing the received processing instructions to a processor unit of the second device, and processing the acquired historical data by the processor unit based on the received processing instructions to generate a report.
[0092] According to at least some example embodiments, method 2 also includes providing new service capabilities (e.g., an application programming interface (API)) at the second device, and registering the second device with configuration capabilities of the second device at a third device (e.g., an NRF), wherein the capabilities represent a possibility for obtaining historical data indicative of events occurring within the communication network environment.
[0093] According to at least some example embodiments, method 2 further includes collecting historical data from at least one data source, and storing the collected historical data in a historical data repository associated with the second device.
[0094] According to at least another example embodiment, the capabilities of the second device include a duration for which the historical data is stored in an associated historical data repository.
[0095] In at least some example embodiments, the event occurring within the communication network environment is one or more of the presence of a user equipment in a predetermined area for a predetermined duration, the number and / or type of services used, the number of times an access and / or mobility management function (AMF) is overloaded for a predetermined duration, and the one or more data sources are a network function (NF); a network data analysis function (NWDAF); an application function (AF) and a network exposure function (NEF); and one or more of operations, administration and maintenance (OAM).
[0096] According to at least some example embodiments, the selection criteria include at least one event and its associated metadata of a plurality of events and their associated metadata.
[0097] Furthermore, according to at least some example embodiments, the generated report may be a statistical evaluation of one or more of the frequency or count of UE movements, the location distribution, the time that the UE is located in a particular area, and / or any other statistical evaluation.
[0098] In the foregoing, some general aspects of at least some example embodiments are presented. Figure 4 , describes an example framework according to at least some example embodiments.
[0099] exist Figure 4 In FIG. 1 , as an example of a first device, a data consumer is shown on the left. In addition, as an example of a second device, a data management framework is depicted.
[0100] In addition, Figure 4 An exemplary process between devices is shown in FIG. First, in step 1, the data consumer (e.g., NWDAF, NF) initiates (as the role of "first device") a service request to obtain historical data from the data management framework. Therefore, it can use, for example, the following request:
[0101] Ndccf_EventExposure_Subscribe
[0102] ({Nxxx_Service, service parameters}, {UE, data_spec}, format, reportTemplate)
[0103] According to at least one example embodiment / modification, the first device may include information indicating another device to which a report obtained from historical data is to be sent. The report may be sent to the first device or the other device, or optionally to both the first device and the other device. Further, the number of another device is not necessarily limited to one another device, but a plurality of another devices may be indicated, for example, based on a network address identifier assigned to the device.
[0104] Furthermore, one benefit of using a data management framework to obtain historical data is that it offloads the processing of large amounts of notifications from the data consumer to the consumer adapter (3CA), namely because a query to the data repository for data within a specific time period is likely to generate a large amount of notifications to the data consumer, and the data repository as a general purpose storage device is less likely to provide aggregation than the NF, especially if they are not standardized by 3GPP.
[0105] Furthermore, the parameters of the API are the same as those used to obtain data from a network function (eg, AMF or SMF).
[0106] For example, if a data consumer wants to obtain historical data for NF type AMF, UE reachability notification, it can use the following:
[0107] Ndccf_EventExposure_Susbcribe
[0108] ({Namf_EventExposure_Susbcribe, ServiceParameters(UEIdentity=123456789012345, Event=UE Tracking Area Change, TAI=TAI1,TAI2,TAI3..TAI10, TimePeriod: January 2019 to January 2020}
[0109] ReportTemplate:{CountOfNotification}}
[0110] Here, the data consumer hopes to obtain the count of TAI changes of user equipment identifiable by, for example, the device identifier of the user equipment "UE=123456789012345" between January 2019 and January 2020.
[0111] The report template (processing instruction) defines that the data consumer is not interested in the actual data or notifications. However, the data consumer wants the data management framework to process the query and provide only the report defined by the report template.
[0112] In this example embodiment, assume that there are 200.000 notifications stored in the data repository.
[0113] Then, in step 2, the DCCF queries the repository based on the input received from the data consumer. The DCCF also provides the reportTemplate details to the data adapter.
[0114] The data repository provides the data (200.000 notifications in this example) back to the messaging framework in step 3. The messaging framework provides the same to the 3CA.
[0115] 3CA consumes 200.000 notifications and generates reports / statistics according to reportTemplate.
[0116] Afterwards, in step 4, 3CA sends a notification to the data consumer that contains only a report, without the actual notification data, where an example of such a report is shown below:
[0117] N3ca_EventExposure_Notification
[0118] ({UE=123456789012345, CountOfNotification=200000}.
[0119] Figure 5 An example flow diagram depicts an example embodiment of another configuration. According to at least some example embodiments, in this configuration, the first device and the second device are consumer devices.
[0120] That is, if the NWDAFp has a repository, which stores the data (notifications) received from the data source as historical data, another NWDAFc can query the NWDAFp to obtain a report.
[0121] In this case, NWDAFp needs to provide a new API (possibly similar to the one defined for Ndccf) where the query defines the report to be obtained from NWDAFp.
[0122] In step 1, NWDAFp registers with NRF, indicating in its profile that it supports new services or service options for historical data report acquisition. Then, in step 2, NWDAFc discovers NWDAFp that supports historical data report acquisition. In step 3, NWDAFc sends a service request, such as Nnwdaf_EventExposure_Susbcribe request (similar to Figure 4 ), where the request contains reportTemplate (processing instructions). In step 4, NWDAFp performs a query in the repository and prepares a report according to reportTemplate. Finally, in step 5, NWDAFp sends the report back to NWDAFc.
[0123] According to at least some (modified) example embodiments, the first device is a consumer device and the second device is a data source.
[0124] In this case, for example, if the NF supports historical data, the NF registers with the NRF and indicates in its profile a new service or service option that allows historical data and report acquisition, including the duration for storing historical data. The data consumer discovers the NF and the NF profile information, including the duration (e.g., 6 months) and reporting capabilities. If the data consumer wishes, it can obtain data or reports from the NF via the above-described solutions of at least some example embodiments.
[0125] So far, a general exemplary embodiment has been described. However, a detailed description is given below for a case where the second device is a DCCF.
[0126] First, a detailed description of the example DCCF itself is provided. Second, a detailed description of the example messaging framework is provided.
[0127] DCCF is a control plane function that coordinates data collection and triggers data delivery to data consumers. DCCF can support multiple data sources, data consumers, and message frameworks. However, to prevent duplicate data collection, each data source is associated with only one DCCF.
[0128] In addition, DCCF provides the Ndccf_EventExposure service defined by 3GPP to the data consumer (eg, NWDAF), and obtains data using the service of the data source (eg, NF). Figure 6 An example DCCF for 5GC is shown. However, there may be multiple instances of DCCF, for example, for network slices, geographic areas where data sources reside, or for different data source types. The DCCF required by the data consumer can be discovered using NRF as described below.
[0129] It is important to note that the DCCF is aware of the data source it is coordinating. NRF and UDM can provide the DCCF with the identification of the 5GC data source (e.g., the AMF serving the UE). DCCF also hides data source lifecycle events and changes to the entity serving the UE from the data consumer. For example, if the NF data source serving the UE changes due to a lifecycle event, the NRF can notify the DCCF that has previously subscribed to the NRF via an event notification. DCCF can also use UDM to learn new (UE, NF) associations, making changes to the UE serving the NF transparent to the data consumer. The NRF only identifies the 5GC NF source.
[0130] It is also important to note that if there is more than one DCCF, they can coordinate data collection and distribution for orthogonal sets of data sources. In this case, the data consumer discovers the DCCF for the data it needs, and the DCCF and message framework delivers data from the prohibited set of data sources. If the DCCF cannot service a request from a data consumer, it can query the NRF to determine an acceptable DCCF and redirect the query accordingly.
[0131] Additionally, it is important to note that the DCCF is not intended to support aggregation of analytical data across multiple NWDAFs. However, the DCCF tracks consumer requests to NWDAF "data sources" and therefore knows what analysis is being generated by the NWDAF. Therefore, the data management framework can be used by a data consumer (e.g., NWDAF) that consumes analytical data from consumption (e.g., aggregation) of one or more NWDAFs acting as "data sources" or from a data repository. Similar to any other NF, the NWDAF acting as a "data source" uses the services defined in TS 23.288 Section 7 (Subscriptions / Notifications) to provide analytical output as "data". The DCCF tracks consumer requests to NWDAF "data sources" and therefore knows what analysis is being generated by the NWDAF.
[0132] In addition, DCCF receives data requests from data consumers via the Ndccf_EventExposure service. The data consumer can be NWDAF (Rel-17 NWDAF), and the content of the service request is based on Rel-16 services (e.g., AMF or SMF event exposure). The DCCF service can provide additional functionality, such as allowing a request that requires multiple data sources (e.g., AMF and SMF), and allowing notifications to be formatted and processed according to conditions specified by the data consumer, as described in the following table.
[0133] In addition, if the data source is not specified in the data request, the DCCF determines the data source that can provide the data requested by the data consumer (e.g., the events exposed by the data consumer for the NF event request). For example, if the request is for UE-specific data, the DCCF can query the NRF / UDM / BSF to determine which NF instance is serving the UE, as described in TS 23.288 Table 6.2.2.1-2.
[0134] If a data source is specified in the data request, DCCF checks whether the data has been collected from the data source. If not, it requests the data from the specified data source.
[0135] In addition, DCCF uses the procedures specified in TS 23.501 Section 7.1.4 "Network Function Service Authorization" to check whether the data consumer is authorized to access the DCCF service.
[0136] In addition, DCCF determines whether the requested data is currently generated by any data source and sent to the messaging framework. If the requested data is not generated, a new subscription / request is sent to the data source to trigger new data collection, and then DCCF subscribes to the messaging framework for the data consumer to receive future notifications. Similarly, when the latest data consumer of a particular data is no longer interested in the data, DCCF cancels data collection from the data source and the messaging framework. This ensures that the data source generates the same data only once when there are multiple data consumers, and does not generate data that no data consumer needs.
[0137] In addition, the DCCF determines whether the data has been collected by maintaining a record of previous requests it made for the data (e.g., via the Nnf_EventExposure service provided by the data source). If the parameters in the previous request for the data match those required in the subsequent request, the DCCF can determine that the requested data has been collected. The DCCF can then subscribe to the messaging framework for the new data consumer to receive future notifications.
[0138] In addition, the formatting conditions and processing requested by the data consumer via the Ndccf_EventExposure service can be passed to the messaging framework via the Nda_Data_Management service. The 3CA can then send notifications to the data consumer accordingly. Formatting determines when notifications are sent to the consumer, where formatting can include, for example:
[0139] Notification event coalescing (buffering and sending multiple notifications in one message)
[0140] Notification time windows (e.g. notifications are buffered and sent between 2am and 3am) Notifications based on cross-event references (when a subscribing NF is subscribing to multiple events (e.g. event X and event Y), notifications for event X are cached and reported only when event Y occurs)
[0141] Consumer triggers notification
[0142] Accurate notification based on time rather than events (reporting data at the exact time, whether or not an event occurred, e.g. every 30 minutes).
[0143] Notifications based on mathematical calculations (e.g., exponential time windows: first notification sent after 5 minutes, then next notification sent after 10 minutes, and third notification sent after 15 minutes, etc.)
[0144] Additionally, aggregated notifications from the same data source are processed to reduce the amount of data reported from 3CA to data consumers. This is particularly useful when requesting data from a data repository (historical data) that contains a large number of notifications. The type of processing is specified by the consumer and may result in merging information from multiple notifications into a common report.
[0145] When the DCCF receives a request for historical data (eg, a NWDAF requests an analysis previously generated by another NWDAF), the DCCF may trigger the retrieval of the data from the data repository and make it available through the messaging framework.
[0146] In addition, DCCF manages subscription requests and cancellations to the messaging framework on behalf of the data consumer. DCCF can use the local messaging framework protocol or an alternative 3GPP-defined adapter with conversion to the messaging framework protocol (such as Figure 6 shown) protocol.
[0147] If independent 3PA and 3CA are used, the DCCF maintains the (NF, 3PA) and (NF, 3CA) associations.
[0148] For DCCF discovery, the DCCF is registered with the NRF and discovered by a data consumer or a service communication agent (SCP) using the registration and discovery procedures defined in TS 23.502 Section 4.17 for the network function service framework. The DCCF profile in the NRF may specify:
[0149] 1. Slices supported by DCCF (S-NSSAI)
[0150] 2. Source types coordinated by DCCF
[0151] 3. Service area containing DCCF coordinated data sources (e.g., TAI list)
[0152] In addition, the source type can correspond to the NF type (e.g., SMF, AMF, etc.), or different domains (e.g., OAM). Therefore, the consumer or SCP can request or select a DCCF based on the type of information it requests, the network slices it supports, and its service area.
[0153] A detailed description of an example messaging framework is given below.
[0154] The messaging framework contains the messaging infrastructure that propagates event information and data (e.g., streaming and notifications) from data sources to data consumers. The messaging framework can support a publish-subscribe (pub-sub) model, where data is published by a producer adapter (or data source if the data source itself supports a message bus protocol) and can be subscribed to by a consumer adapter (or data consumer if the data consumer itself supports a message bus protocol).
[0155] Furthermore, the messaging framework may support a variety of event delivery mechanisms, such as best effort or guaranteed delivery.For 3GPP purposes, guaranteed event delivery may be utilized.
[0156] The messaging framework may contain one or more adapters that can convert between 3GPP-defined protocols (e.g., Rel-16Nnwdaf_AnalyticsSubscription_Notify) and data forwarding protocols not specified by 3GPP. The messaging framework adapter maintains subscription information, including formatting conditions and processing instructions, which are received by the DCCF adapter (DA).
[0157] Adapters on the producer side (3PA) allow any source data to be distributed via the framework (e.g. from Rel-16 OAM or NF event exposure) without affecting the data source. The DCCF tracks adapter instances. An adapter can be associated with a specific NF type and / or instance, manages one or more data sources, and can be discovered by registering the sources (e.g. NFs) it supports with the DCCF. If the messaging framework directly supports the 3GPP interface, then an adapter may not be needed.
[0158] In the following, reference is made to Figure 7 Another specific example process within the framework is described (not shown as such). That is, a process for data collection and distribution for event notifications (subscription / notification). The process illustrates how the DCCF manages data sources so that data is generated only once, and illustrates how the DCCF interacts with the messaging framework to distribute data to all subscribed data consumers. The process applies to data consumers and producers using 3CA and 3PA, i.e., all steps are within the scope of 3GPP.
[0159] Furthermore, the data processed by the messaging framework is associated with an identifier. This example process assumes that the messaging framework uses a publish / subscribe model based on "topics", and that the topic is therefore the identifier. Thus, the 3PA publishes the "topic", and the 3CA that wishes to receive data subscribes to the "topic". However, other options may also be supported.
[0160] exist Figure 7In step 1 of , data consumer-1 (e.g., NWDAF-1) sends a request for data to the DCCF. The message includes a notification target address. In addition, the message may indicate whether the requested data should be sent to a notification target address set to data consumer-1 and / or other data consumers such as data repositories. The notification association ID of consumer-1 is included in the request message and is used for notifications sent to data consumer-1 (e.g., in step 8).
[0161] In step 2, if the request is for UE data, the DCCF may query the UDM / NRF / BSF to determine the NF serving the UE.
[0162] In step 3, the DCCF determines a data source (eg, AMF-1) that can provide the data and checks whether the requested data has not been collected yet.
[0163] Then, in step 4, the DCCF controls the message bus and adapters so that the notification traverses the messaging framework. The subscription to the DA includes the 3PA's Notification Correlation ID and the Notification Correlation ID for the data consumer-1 as received in step 1. The DA can associate these with the messaging framework "topic". In addition, the 3PA is provided with its Notification Correlation ID and the topic. The 3CA will be provided with the consumer's notification endpoint, the consumer's Notification_Correlation_ID and the topic. The 3CA can then subscribe to the topic in the messaging framework.
[0164] In step 5, the DCCF sends a subscription request to the NF producer acting as the data source. The subscription includes the notification endpoint and the notification correlation ID of the 3PA acting as the receiver for these notifications.
[0165] Then in step 6, the data source acknowledges the request.
[0166] In step 7, after the event of the data source is triggered, a notification containing the notification correlation ID of the 3PA is sent to the 3PA. The 3PA publishes the data in the message framework. In addition, it can use the "topic" associated with the notification correlation ID of the 3PA received in step 4.
[0167] In step 8, when data is published to the "topic", the messaging framework makes it available to all subscribed 3CAs. In this case, the only subscriber is the 3CA of Service Consumer-1. The 3CA maps the topic to the Notification Correlation ID of the Data Consumer received in step 4 (initially provided by Data Consumer-1) and sends a notification to the Notification Endpoint of Data Consumer-1.
[0168] Then, in step 9, data consumer-2 (e.g., NWDAF-2) sends a request for the same data. The message may indicate whether the requested data should be sent to data consumer-2 and / or other consumers such as data repositories. The notification sent to data consumer-2 includes the notification correlation ID of consumer-2.
[0169] In step 10, the DCCF determines that the requested data has been collected from the data source (eg, AMF-1) and obtains the 3PA ID and the Notification Correlation ID of the 3PA.
[0170] Then, in step 11, the DCCF sends a subscription request to the messaging framework, indicating the presence of a new data subscriber. The subscription message to the DA provides the 3PA ID, as well as the currently used 3PA Notification Correlation ID and the Notification Correlation ID for data consumer-2 received in step 9. The DA selects an existing "Topic" corresponding to the 3PA information and sends the 3CA Consumer-2's Notification Endpoint, Consumer-2's Notification_Correlation_ID and the Topic. The 3CA can then subscribe to the topic in the messaging framework. It should be noted that the 3CA of Consumer-2 can be different or the same as the 3CA of Consumer-1.
[0171] In step 12, after an event is triggered in the data source, a notification is sent to the 3PA, and the 3PA publishes data to the corresponding "topic" on the messaging framework.
[0172] In steps 13 and 14, when data is published to the "topic", the messaging framework makes it available to the subscribed 3CAs. In this case, the 3CAs of service consumer-1 and consumer-2 receive the data and apply processing instructions and send notifications to the notification endpoints of data consumer-1 and consumer-2 using their respective notification correlation IDs.
[0173] Having described some example embodiments and some specific examples, the impact on services, entities and interfaces is described below.
[0174] In detail, advantageously, a DCCF within a DMF is suitable as an entity in which at least some exemplary aspects of the present invention may be implemented.
[0175] In this or similar environments, the following new features and / or services according to at least some embodiments appear to be particularly useful:
[0176] -Ndccf_EventExposure Service
[0177] This service enables a data consumer to request data. The baseline for this service is the Rel-16 NF service used to obtain data from the NF. For example, the baseline for a DCCF service used by a data consumer to obtain UE mobility data would be Namf_EventExposure. The response providing data is routed via the messaging framework and 3CA. Ndccf_EventExposure must allow a data consumer to:
[0178] 1. Identifies the data being requested and also identifies the NF instance that can provide the data, the area of interest, or the UE-ID that the DCCF can use to discover the serving NF
[0179] 2. Provide formatting conditions and processing instructions that the DCCF can pass to the 3CA in the Nda_Data_Management request
[0180] Furthermore, the proposed Ndccf_EventExposure service operation is:
[0181] Ndccf_EventExposure_Subscribe(Nxxx_Service, NF-ID, UE-ID, Notification Object Address (+ Notification Correlation ID), Data Notification, Formatting, Processing Instructions, Start_Time, Expiration Time)—It is used by the data consumer to request data.
[0182] The parameters for the Ndccf_EventExposure_Subscribe service operation are:
[0183]
[0184]
[0185] Note that the "Expiration Time" represents the time when the subscription is expected to end and is already an exposed service parameter (see TS 23.501 Section 4.15.1). If part of the interval between Start_Time and Expiration Time is in the past, historical data is requested from the data repository. If part of the interval between Start_Time and Expiration Time is in the future, data is requested from the data source. In both cases, the data can be sent to the data consumer via the messaging framework.
[0186] Ndccf_EventExposure_Unsubscribe(Subscription Association ID)—This is used by the data consumer when the data is no longer wanted.
[0187] The parameters for the Ndccf_EventExposure_Unsubscribe service operation are:
[0188] parameter value Subscription association ID The correlation ID is provided by DCCF when data is requested
[0189] Furthermore, more than one instance of the above parameters may be specified to allow a data consumer to combine multiple data requests in a single message.
[0190] -Nda_Data_Management Service:
[0191] DCCF requires a new service to interact with the messaging framework DCCF adapter. This service enables DCCF to request the messaging framework to provide data to the data consumer. Here, Nda_Data_Management must allow:
[0192] 1.3PA identifies notifications from data sources and delivers them to the messaging framework
[0193] 2.3CA obtains data from the messaging framework and sends notifications to the data consumer. In addition, the proposed Nda_Data_Management service operation is:
[0194] Nda_Data_Management_Subscribe(Nxxx_Service, Nda_Parameters, Format, Processing Instructions)—It is used when data needs to be sent from 3CA to the data consumer.
[0195] The parameters for the Nda_Data_Management_Subscribe service operation are:
[0196]
[0197] Nda_Data_Management_Unsubscribe (Subscription Association ID) - This is used when data is no longer sent from 3CA to the data consumer.
[0198] The parameters for the Nda_Data_Management_Unsubscribe service operation are:
[0199] parameter value Subscription association ID The correlation ID is provided by DCCF when data is requested
[0200] -N3ca_EventExposure Service:
[0201] This service enables 3CA to send data to the data consumer specified by DCCF using the Nda_Data_Management service.
[0202] Here, possible and / or suitable service operations are:
[0203] N3ca / Nda_EventExposure_Notify (Notification Correlation ID, Notification)—Used by 3CA to send data to data consumers.
[0204] The parameters for the N3ca / Nda_EventExposure_Notify service operation are:
[0205]
[0206] -3PA Service
[0207] 3PA is the notification target specified by DCCF when DCCF subscribes to notifications from the data source. 3PA does not provide any services. In addition, according to the instructions received by 3PA from DA, the notifications received from the data source are sent to the messaging framework.
[0208] It is further noted that 3GPP is scheduled to standardize the interfaces between 3PA, DA and 3CA.
[0209] Furthermore, the impact of NRF includes new NFs, new parameters in NF profiles, and new discovered parameters.
[0210] In view of the data repository service, in case of 3GPP defining a data repository, a new service for the data repository of the data consumer is needed. This service can be used via the messaging framework, ie via an adapter.
[0211] Furthermore, data consumers using the data management framework send requests to the DCCF rather than to data producers (as was the case in Release 16).
[0212] In addition, different formatting conditions and processing instructions are requested by the data consumer to the DCCF.
[0213] at last, Figure 8Control units 10, 20 and 30 are depicted, each comprising processing resources (e.g., processing circuitry) 11, 21, 31, memory resources (e.g., memory circuitry) 12, 22, 32 and interfaces (e.g., interface circuitry) 13, 23, 33. In at least one exemplary embodiment, control unit 10 is configured to be implemented in and / or used by a first device, e.g., for a data consumer as described above, control unit 20 is configured to be implemented in and / or used by a second device, e.g., a data management framework, another data consumer or data source as described above, and control unit 30 is configured to be implemented in and / or used by a third device, e.g., a network repository functionality as described above. Furthermore, each control unit has its own bus system 14, 24, 34 connecting the above resources so that data can be exchanged between the three components of the unit. Furthermore, control units 10, 20 and 30 may be connected via links 40, 41 and 42. The control units 10 , 20 and 30 also have additional Xn interfaces 43 , 44 and 45 , which enable a connection between the corresponding unit and its resources.
[0214] The terms "connected," "coupled," or any variations thereof, mean any connection or coupling between two or more elements, whether direct or indirect, and may include the presence of one or more intermediate elements between two elements being "connected" or "coupled" together. The coupling or connection between elements may be physical, logical, or a combination thereof. As non-limiting examples, two elements as used herein may be considered to be "connected" or "coupled" together through the use of one or more wires, cables, and printed electrical connections, and through the use of electromagnetic energy, such as having wavelengths in the radio frequency region, the microwave region, and the optical (visible and invisible) region.
[0215] The definitions indicated in this specification are based on the current 3GPP standards. However, they are not restrictive. Other definitions based on the same or corresponding concepts are also applicable to some example embodiments.
[0216] A piece of information can be sent from one entity to another in one or more messages. Each of these messages can include another (different) piece of information.
[0217] The names of network elements, protocols and methods are based on current standards. In other versions or other technologies, the names of these network elements and / or protocols and / or methods may be different, as long as they provide corresponding functions.
[0218] If not otherwise stated or clear from the context, a different description of two entities means that they perform different functions. This does not necessarily mean that they are based on different hardware. That is, each entity described in this specification can be based on different hardware, or some or all of the entities can be based on the same hardware. This does not necessarily mean that they are based on different software. That is, each entity described in this specification can be based on different software, or some or all of the entities can be based on the same software. Each entity described in this specification can be embodied in the cloud.
[0219] Implementation of any of the above blocks, apparatus, systems, techniques or methods includes, as non-limiting examples, implementation as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.
[0220] Furthermore, as used in this application, the term "circuitry" refers to one or more or all of the following:
[0221] (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry) and
[0222] (b) combined circuitry and software (and / or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s) / software (including digital signal processor(s)), software and memory(s) working together to enable a device (such as a mobile phone or server) to perform various functions) and
[0223] (c) Circuitry (such as microprocessor(s) or portion(s) of microprocessor(s)) that requires software or firmware for operation, even if the software or firmware is not physically present.
[0224] The definition of “circuitry” applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term “circuitry” would also cover an implementation of only a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and / or firmware. The term “circuitry” would also cover, for example and if applicable to a particular claim element, a baseband integrated circuit or an application processor integrated circuit for a mobile phone or a similar integrated circuit in a server, cellular network device, or other network device.
[0225] While the above method refers to first to third apparatuses in terms of definition, the apparatus claims refer to first to third types of devices.
[0226] According to at least some example embodiments, an apparatus is provided within a communication network environment, the apparatus having a possibility for acquiring historical data indicating events occurring within the communication network environment and obtained from one or more data sources within the communication network environment. For example, the apparatus comprises Figure 8 The control unit 10, 20 or 30 shown. According to another example implementation or in addition, the device is configured to perform Figure 2 Method 1 is shown.
[0227] According to one aspect, a device provided within a communication network environment and having the possibility of acquiring historical data indicating events occurring within the communication network environment and obtained from one or more data sources within the communication network environment comprises a component for specifying selection criteria to be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with a second type of device, a component for specifying at least one processing instruction, wherein the processing instruction determines the generation of a report based on the defined query, a component for sending the selection criteria and the processing instruction to the second type of device, and a component for receiving a report generated at the second type of device based on the sent selection criteria and the processing instruction.
[0228] According to an example implementation, the device also includes a component for discovering a second type of device by querying a third type of device, and a component for receiving, from the third type of device, an indication of the second type of device based on a capability of the second type of device registered at the third type of device, wherein the capability indicates a possibility for obtaining historical data indicating events occurring within a communication network environment.
[0229] According to an example implementation, the capabilities of the second type of device include a duration for which the historical data is stored in an associated historical data repository.
[0230] According to at least some other example embodiments, a device (of the second type) is provided within a communication network environment with the possibility to obtain event history data indicating events occurring within the communication network environment and obtained from one or more data sources within the communication network environment. For example, the device (of the second type) comprises Figure 8 According to another exemplary embodiment or in addition, the device (of the second type) is configured to perform the following Figure 3 Method 2 shown.
[0231] According to one aspect, a device provided within a communication network environment and having the possibility of acquiring historical data indicating events occurring within the communication network environment and obtained from one or more data sources within the communication network environment comprises a component for receiving selection criteria and at least one processing instruction from a first type of device, the selection criteria to be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with the device, wherein the processing instruction determines the generation of a report based on the defined query, a component for generating a report based on the received selection criteria and processing instructions, and a component for sending the generated report to the first type of device or other devices indicated by the first type of device.
[0232] Such indication of another device may in embodiments be part of the processing instructions. This provides flexibility for the first device to indicate a recipient different from the first device.
[0233] According to an example implementation, a component for generating a report based on received selection criteria and processing instructions includes a component for acquiring historical data from a historical data repository associated with a device based on the selection criteria, and a component for providing the received processing instructions to a processor unit of the device, wherein the processor unit is configured to process the acquired historical data based on the received processing instructions to generate a report.
[0234] According to an example implementation, the apparatus further comprises means for providing a new service capability at the apparatus and means for registering the apparatus at a third type of apparatus with a configured capability of the apparatus, wherein the capability represents a possibility to obtain historical data indicative of events occurring within a communication network environment.
[0235] In an example implementation, the apparatus further includes means for collecting historical data from at least one data source and means for storing the collected historical data in a historical data repository associated with the apparatus.
[0236] According to an example implementation, the capabilities of the device include a duration for which historical data is stored in an associated historical data repository.
[0237] In an example implementation, the event occurring within the communication network environment is one or more of the presence of a user device in a predetermined area for a predetermined duration, the number and / or type of services used, the number of times an access and mobility management function is overloaded for a predetermined duration, and the one or more data sources are a network function; a network data analysis function; an application function and a network exposure function; and one or more of operations, management, and maintenance.
[0238] According to an example implementation, the selection criteria includes at least one event and its associated metadata of a plurality of events and their associated metadata.
[0239] The following paragraphs describe possible aspects and another example of implementation.
[0240] Example 1. A method comprising: providing the possibility of obtaining historical data within a communication network environment, the historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources within the communication network environment, specifying selection criteria that will be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with a second device, specifying at least one processing instruction at a first device, wherein the processing instruction determines the generation of a report based on the defined query, sending the selection criteria and the processing instruction to the second device, and receiving the report generated at the second device based on the sent selection criteria and processing instruction.
[0241] Example 2. A method according to Example 1, wherein the method further includes discovering the second device by querying a third device, and receiving from the third device an indication of the second device based on capabilities of the second device registered at the third device, wherein the capabilities represent a possibility of obtaining historical data indicating events occurring within a communication network environment.
[0242] Example 3. The method of example 2, wherein the capabilities of the second device include a duration for which the historical data is stored in an associated historical data repository.
[0243] Example 4. A method, comprising providing the possibility of obtaining historical data within a communication network environment, the historical data indicating events occurring within the communication network environment and obtained from one or more data sources within the communication network environment, receiving selection criteria and at least one processing instruction from a first device, the selection criteria to be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with a second device, wherein the processing instruction determines the generation of a report based on the defined query, generates a report based on the received selection criteria and the processing instruction, and sends the generated report to the first device or to another device indicated by the first device.
[0244] Example 5. A method according to Example 4, wherein generation of a report based on the received selection criteria and processing instructions includes: obtaining historical data from a historical data repository associated with a second device based on the selection criteria, providing the received processing instructions to a processor unit of the second device, and processing the obtained historical data by the processor unit based on the received processing instructions to generate a report.
[0245] Example 6. The method according to Example 4 or Example 5 also includes providing new service capabilities at the second device and registering the second device with the configuration capabilities of the second device at the third device, wherein the capabilities represent the possibility of obtaining historical data indicating events occurring within the communication network environment.
[0246] Example 7. The method of Example 6, further comprising collecting historical data from at least one data source, and storing the collected historical data in a historical data repository associated with the second device.
[0247] Example 8. The method of example 6, wherein the capabilities of the second device include a duration for which the historical data is stored in an associated historical data repository.
[0248] Example 9. A method according to any one of the preceding examples, wherein the event occurring within the communication network environment is one or more of: the presence of a user device in a predetermined area for a predetermined duration, the number and / or type of services used, the number of times access and mobility management functions are overloaded for a predetermined duration, and one or more data sources are one or more of the following: network functions; network data analysis functions; application functions and network exposure functions; and operation, management and maintenance.
[0249] Example 10. The method of any of the preceding examples, wherein the selection criteria includes at least one event and its associated metadata of a plurality of events and their associated metadata.
[0250] Example 11. A device provided within a communication network environment having the possibility of acquiring historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources within the communication network environment, the device comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the device to at least perform: specifying selection criteria that will be applied to historical data for performing a query on historical data stored in a historical data repository associated with a second type of device, specifying at least one processing instruction, wherein the processing instruction determines generation of a report based on the defined query, sending the selection criteria and the processing instruction to the second type of device, and receiving a report generated at the second type of device based on the sent selection criteria and processing instruction.
[0251] Example 12. An apparatus according to Example 11, wherein at least one memory and computer program code are configured to, together with at least one processor, cause the apparatus to further perform: discovering a second type of apparatus by querying a third type of apparatus, and receiving from the third type of apparatus an indication of the second type of apparatus based on capabilities of the second type of apparatus registered with the third type of apparatus, wherein the capabilities represent a possibility of obtaining historical data indicating events occurring within a communication network environment.
[0252] Example 13. The device of example 12, wherein the capabilities of the second type of device include a duration for which the historical data is stored in an associated historical data repository.
[0253] Example 14. A device provided within a communication network environment having the possibility of acquiring historical data indicating events that occurred within the communication network environment and were obtained from one or more data sources within the communication network environment, the device comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the device to at least perform: receiving selection criteria and at least one processing instruction from a first type of device, the selection criteria to be applied to historical data for performing a query on historical data stored in a historical data repository associated with the device, wherein the processing instruction determines generation of a report based on the defined query, generates a report based on the received selection criteria and processing instructions, and sends the generated report to the first type of device or to another device indicated by the first type of device.
[0254] Example 15. The apparatus according to Example 14, wherein
[0255] The generation of reports based on the received selection criteria and processing instructions includes:
[0256] Retrieving historical data from a historical data repository associated with the device based on the selection criteria, and
[0257] providing the received processing instructions to a processor unit of the device, wherein
[0258] The processor unit is configured to process the acquired historical data based on the received processing instructions to generate a report.
[0259] Example 16. The apparatus according to example 14 or 15, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to further perform:
[0260] Providing new service capabilities at the device, and
[0261] The device is registered at a device of the third type with configured capabilities of the device, wherein the capabilities represent a possibility for acquisition of historical data indicative of events occurring within the communication network environment.
[0262] Example 17. The apparatus of Example 16, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to further perform:
[0263] Collect historical data from at least one data source, and
[0264] The collected historical data is stored in a historical data repository associated with the device.
[0265] Example 18. The apparatus of example 16, wherein the capabilities of the apparatus include a duration for which historical data is stored in an associated historical data repository.
[0266] Example 19. The device according to any one of Examples 11 to 18, wherein
[0267] The event occurring within the communication network environment is one or more of: the presence of a user equipment in a predetermined area for a predetermined duration, the number and / or type of services used, the number of times an access and mobility management function is overloaded for a predetermined duration, and
[0268] The one or more data sources are one or more of: network functions; network data analysis functions; application functions and network exposure functions; and operations, management, and maintenance.
[0269] Example 20. An apparatus according to any one of Examples 11 to 19, wherein the selection criteria includes at least one event and its associated metadata among a plurality of events and their associated metadata.
[0270] Example 21. A non-transitory computer-readable storage medium storing a program, the program comprising software code portions that, when executed on a processor of an apparatus providing, within a communication network environment, a possibility of acquiring historical data for events indicative of events occurring within the communication network environment and obtained from one or more data sources within the communication network environment, cause the processor to execute:
[0271] specifying selection criteria to be applied to the historical data for performing a query on the historical data stored in a historical data repository associated with the second type of device, specifying at least one processing instruction,
[0272] Where processing instructions determine the generation of reports based on defined queries,
[0273] sending selection criteria and processing instructions to devices of the second type, and
[0274] A report generated at a device of the second type is received based on the sent selection criteria and processing instructions.
[0275] Example 22. A non-transitory computer-readable storage medium storing a program, the program comprising software code portions that, when executed on a processor of an apparatus providing, within a communication network environment, a possibility of acquiring historical data for events indicative of events occurring within the communication network environment and obtained from one or more data sources within the communication network environment, causes the processor to execute:
[0276] receiving, from a device of the first type, selection criteria and at least one processing instruction, the selection criteria to be applied to historical data for performing a query on historical data stored in a historical data repository associated with the device,
[0277] Where processing instructions determine the generation of reports based on defined queries,
[0278] Generates reports based on the received selection criteria and processing instructions,
[0279] The generated report is sent to the device of the first type or to another device indicated by the device of the first type.
[0280] It should be understood that the above content is what is currently considered to be the preferred exemplary embodiment of the present invention. However, it should be noted that the description of the preferred exemplary embodiment is given by way of example only and various modifications can be made without departing from the scope of the present invention defined by the appended claims.
Claims
1. A method for a device of a communication network, the device comprising a historical data storage library, the method comprising: receiving, from a device comprising a data consumer, selection criteria to be applied to historical data, the historical data being stored in the historical data repository and indicating events occurring within the communication network, formatting conditions indicating when reports are to be sent, and processing instructions, wherein the data consumer comprises a network data analysis function NWDAF, obtaining the historical data including a plurality of notifications from the historical data repository based on the selection criteria; generating a report from the historical data based on the formatting conditions and the processing instructions, wherein the report includes a smaller amount of data than the historical data including the plurality of notifications; and The report is sent to the device including the data consumer including the NWDAF or to another device indicated by the device including the data consumer including the NWDAF.
2. The method according to claim 1, wherein: The generating of the report according to the historical data based on the formatting conditions and the processing instructions includes: providing the formatting conditions and the processing instructions to a processor unit of the device, and The acquired history data is processed by the processor unit based on the formatting conditions and the processing instructions to generate the report.
3. The method according to claim 1 or 2, further comprising: providing a configured service capability at a network function for data collection coordination, the apparatus comprising the network function for data collection coordination, and The network function for data collection coordination is registered with configured capabilities of the network function for data collection coordination, wherein the configured service capabilities represent possibilities for acquisition of historical data indicative of events occurring within the communication network.
4. The method according to claim 3, further comprising: collecting the historical data from at least one data source, and The historical data is stored in the historical data storage repository. 5 . The method of claim 3 , wherein the configured service capabilities of the network function for data collection coordination include a duration for which the historical data is stored in an associated historical data repository.
6. The method according to any one of claims 1 to 2, wherein: The event occurring within the communication network comprises one or more of the following: presence of a user equipment in a predetermined area for a predetermined duration, use of a service, overload of access and mobility management functions for a predetermined duration, and The one or more data sources from which the historical data is collected are one or more of the following: Network capabilities; Network data analysis function; Application functions; Network exposed functionality; or Operation, management and maintenance functions.
7. The method according to any one of claims 1 to 2, wherein the selection criteria comprises at least one event and its associated metadata of a plurality of events and their associated metadata.
8. An apparatus for a communication network, the apparatus comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code, when executed by the at least one processor, causing the apparatus to at least perform: receiving, from a device comprising a data consumer, selection criteria to be applied to historical data, the historical data being stored in a historical data repository and indicating events occurring within a communication network, formatting conditions indicating when a report is to be sent, and processing instructions, wherein the data consumer comprises a network data analysis function NWDAF, obtaining the historical data including a plurality of notifications from the historical data repository based on the selection criteria; generating a report from the historical data based on the formatting conditions and the processing instructions, wherein the report includes a smaller amount of data than the historical data including the plurality of notifications; and The report is sent to the device including the data consumer including the NWDAF or to another device indicated by the device including the data consumer including the NWDAF.
9. The device according to claim 8, wherein The generating of the report according to the historical data based on the formatting conditions and the processing instructions includes: providing the formatting conditions and the processing instructions to a processor unit of the device, and The acquired history data is processed by a processor unit based on the formatting conditions and the processing instructions to generate the report.
10. The apparatus according to claim 8 or 9, wherein the computer program code, when executed by the at least one processor, causes the apparatus to further perform: providing configured service capabilities at the device, and The apparatus is registered at a device with configured service capabilities of the apparatus, wherein the configured service capabilities represent a possibility for acquisition of historical data indicative of events occurring within the communication network.
11. The apparatus of claim 10, wherein the computer program code, when executed by the at least one processor, causes the apparatus to further perform: collecting the historical data from at least one data source, and The historical data is stored in the historical data repository associated with the device.
12. The apparatus of claim 10, wherein the configured service capabilities of the apparatus include a duration for which the historical data is stored in an associated historical data repository.
13. The device according to any one of claims 8 to 9, wherein The event occurring within the communication network comprises one or more of the following: presence of a user equipment in a predetermined area for a predetermined duration, use of a service, overload of access and mobility management functions for a predetermined duration, and The one or more data sources from which the historical data is collected are one or more of the following: Network capabilities; Network data analysis function; Application functions; Network exposed functionality; or Operation, management and maintenance functions.
14. The apparatus according to any one of claims 8 to 9, wherein the selection criteria comprises at least one event and its associated metadata of a plurality of events and their associated metadata.
15. A non-transitory computer-readable storage medium storing a program, the program comprising software code portions which, when executed on a processor of a device provided within a communication network, cause the processor to execute: receiving, from a device comprising a data consumer, selection criteria to be applied to historical data, the historical data being stored in a historical data repository associated with the device and indicating events occurring within a communication network, formatting conditions indicating when reports are to be sent, and processing instructions, wherein the data consumer comprises a network data analysis function NWDAF, obtaining the historical data including a plurality of notifications from the historical data repository based on the selection criteria; generating a report from the historical data based on the formatting conditions and the processing instructions, wherein the report includes a smaller amount of data than the historical data including the plurality of notifications; and The report is sent to the device including the data consumer including the NWDAF or to another device indicated by the device including the data consumer including the NWDAF.
