RU2791121C2 - Devices and methods for detecting collected data and analytical data on a network - Google Patents

Abstract

FIELD: means for discovering collected data and/or analytical data on a network.

SUBSTANCE: information about the collected data is received from at least one first device configured to provide the collected data, and the collected data contain information provided by the first device and recovered by device (100), while the first device is implemented as a network function (NF) and/or application functions (AF). A request for information about the collected data is received from the second device searching for the collected data on the network. The second device, in response to the request, is provided with the information about the collected data.

EFFECT: dynamic and automated detection of analytical data and/or collected data.

26 cl, 10 dwg

Description

The field of technology to which the disclosure relates

The present disclosure relates generally to a new framework for discovering collected data and/or analytics on a network. In particular, the disclosure provides a device for discovering such data on a network. In addition, the disclosure presents a device for discovering such data, that is, the sources of such data, and a device for searching and using such data in a network, respectively.

5G systems defined by 3GPP in TS 23.501 Revision 15 support Network Function (NF) discovery based on the Network Repository Function (NRF). Details of registration and discovery functionality are described in the specification 3GPP TS 23.502 and TS 29.510 In 5G systems, there are two main types of information that can be discovered for NRF: NF instances and their respective services Any subsequent requests/subscriptions to these NF services will need to contain the specific information requested from the NF For example, if the Network Data Analytics Function (NWDAF) needs to be registered in order to collect data from the NF, it must specify when registering the ID of the data that the NWDAF intends to collect. and Management, OAM) need an analytics (analytics) subscription from NW DAF, they need to send a subscription request containing the analytics ID. There are, however, three main problems associated with the current phase of the 3GPP specification.

First, it is reasonable to expect 5G network deployments to work with standardized and non-standardized types of data collection and analytics. Therefore, the discovery of non-standardized types of collected data and analytical data should be considered in the design of 5G systems. In addition, even standardized data must be discovered, because an NF instance cannot offer all data (or analytic data) standardized, and this is the same logic that follows from the definition of NF services (NF Services) in NRF, that is, one an NF instance cannot offer all standardized services for this NF type. Thus, the project, considering that not always all services and data will be available in the NF instance, has the main advantage of offering more flexibility in the deployment of 5G systems, so that it can deal with different deployment scenarios and use cases.

Second, without an automated mechanism to discover the data being collected as well as the analytics to be used, operators must manually modify the NF/AF software/scripts to be able to subscribe to NWDAF analytics and, interchangeably, to NWDAF in order to collect data. .

Third, in the case where the NF, AF, and Analytics Function within 5G systems is not one of the OAMs, the OAM knows the initial configuration of such NFs, but the OAM can learn about changes to the NFs (e.g., new types analytics or collected data) only if the administrator of such NFs personally/manually informs the OAM administrator of such changes.

Some traditional standard implementations are described below.

• NWDAF in TR 23.791 and TS 23.50:

Новая услуга, определенная в TR 23.791, которая должна обеспечиваться NF для сбора данных, но не имеет никакой операции для обнаружения наборов данных, которые могут быть реально собраны из NF.

A new service defined in TR 23.791 that must be provided by the NF for collecting data, but has no operation for discovering the data sets that can actually be collected from the NF.

Новая услуга рекомендации, определенная в TR 23.791, но, опять же, отсутствует операция, разрешающая какое-либо обнаружение.

New recommendation service defined in TR 23.791, but again there is no operation allowing any discovery.

Услуги NWDAF (NWDAF Services), определенные в TS 23.502, также не предлагают никакого варианта для обнаружения, какие категории аналитических данных представляются.

The NWDAF Services defined in TS 23.502 also do not offer any option for discovering which categories of analytic data are being submitted.

• NF profile information (NF Profile) available in NRF (TS23.501, TS23.502, TS29.510):

Профиль NF не позволяет ни обнаружение данных, которые могут быть собраны из NF, ни обнаружение аналитических данных, представляемых посредством NWDAF.

The NF profile does not allow discovery of data that can be collected from NF, nor discovery of analytical data provided by NWDAF.

• Presentation of NF information (NF information Exposure) via NEF (TS23.501, TS23.502, TS29.522):

Описание требования предоставления возможностей NF для аналитики, но отсутствуют конкретные технические требования о возможностях или услугах для аналитики.

Describes the requirement to provide NF analytics capabilities, but there are no specific technical requirements for analytics capabilities or services.

• Data Storage in 3GPP (UDR, UDM, UDSF):

Дают возможность хранения структурированных (то есть, стандартизированных) данных в унифицированной структуре управлении данными (Unified Data Management, UDM) и унифицированном репозитории данных (Unified Data Repository, UDR) и неструктурированных (нестандартизированных) данных в функции хранения неструктурированных данных (Unstructured Data Storage Function, UDSF), но отсутствует определение поддержки хранения собираемых данных или обнаружения аналитики.

Provides the ability to store structured (that is, standardized) data in the Unified Data Management (UDM) structure and the Unified Data Repository (UDR) and unstructured (non-standardized) data in the Unstructured Data Storage Function , UDSF), but there is no definition of support for data collection storage or analytics discovery.

Disclosure of the essence of disclosure

Given the problems and shortcomings listed above, the present disclosure aims to improve traditional implementations with respect to data discovery and collection, and, accordingly, the disclosure and use of analytical data in the network. The challenge, therefore, is to solve the above three problems, namely by defining dynamic and automated discovery of analytical data and/or collected data.

In particular, it should deal with the following tasks

• How standard and non-standard data collected can be identified so that such data can be requested for data collection.

• How can it be known, first of all, which collected data and/or analyzes are available (eg standardized and non-standardized) and presented on the network, and thus how they can be obtained

One or more of these problems are solved using embodiments corresponding to the disclosure, which are presented in the included independent claims of the disclosure. Preferred implementations of the present disclosure are further defined in the dependent claims of the disclosure.

The first embodiment provides a device for discovering data in a network, the device being configured to receive from the first device information about the collected data and/or information about analytical metadata, receive from the second device the request for information about the collected data and/or information about analytical metadata, and provide information about the collected data and/or information about the analytical metadata to the second device in response to its request.

The device corresponding to the first variant can be implemented as NRF. The first device may be a device providing collected data and/or analytics to the network, for example, may be implemented as an AF and/or NF providing collected data, or may be implemented as an NWDAF providing analytics. The second device may be a device that searches the network, that is, the search for collected data and/or analytical data. For example, the second device may be implemented as an OAM searching for analytic data, or may be implemented as an NWDAF searching for collected data. The second device may also be the first device. The collected data information and/or analytic metadata information may be included in the NF Profile (also referred to in this document as "advertisement"), as currently defined in TS 23.502 and TS 29.510. Data information collected and/or analytic metadata information is further defined below.

With the device according to the first embodiment, a Discovery Function can be provided in the network for the collected data and/or analytical data. Through information about the data being collected and/or information about analytical metadata, available categories of such data are provided. Thus, both standard and non-standard collected data and/or analytical data can be identified so that they can be requested for collection or use. In this way, dynamic and automated discovery of analytic data and/or collected data is defined, improving traditional implementations.

In the implementation form of the first variant, the device is additionally configured to provide the second device with notification of a change in state and/or availability of information about the collected data and/or information about analytical metadata.

In this way, up-to-date information regarding the available data is maintained for the second device.

The second embodiment of the disclosure provides a device for providing data to be collected on a network, the device being configured to generate information about the data to be collected related to the data to be collected, and to transmit the information about the data to be collected to a device for discovering data on the network.

The network data discovery device may be a device according to the first embodiment and may also be a first device and/or a second device.

By providing the Discovery Function with information about the collected data, the network can be presented with the available collected data.

In the implementation form of the second option, the device is further configured to receive a request for collected data based on information about the collected data, where the reception is from the second device, and information about the collection point associated with the collected data is provided to the second device in response to its request.

The second device is a device for searching for data, in particular collected data, on the network. For example, it could be NWDAF. The information about the collected data makes it easier for the second device to discover the device corresponding to the second option as the recipient of its request. The collection point information indicates where the second device can receive the collected data from.

In an additional form of implementation of the second option, the device is configured to configure the target device, which should receive data from the device.

The target device can be an External Collection Point (ECP) and/or a relay. The configuration may contain authorization information or information about the interpretation of the receipt. The second device may then communicate with the target device and may request and receive collected data from it.

In a further embodiment of the second embodiment, the device is configured to receive a collection data request based on information about the collection data, where the reception is from the second device, and provide acquisition interpretation information related to the collection data to the second device in response to its request, and /or providing information about the interpretation of the receipt for the configuration of the target device.

The target device may be a collection data providing device when the collection point information indicates an indirect collection point. Information about the interpretation of the acquisition also allows the reading and processing of non-standard collected data.

A third embodiment of the disclosure is a device for providing analytics data to a network, the device being configured to generate analytic metadata information associated with the analytics data and transmit the analytics metadata information to a network data discovery device.

The device according to the third variant for providing analytical data may be NWDAF and may be the device corresponding to the second variant.

By providing information about the analytic metadata to the Discovery Function, the available analytics data can be presented on the network.

The fourth embodiment of the disclosure provides a device for retrieving collected data on a network, in particular, a device corresponding to the third embodiment, wherein said device is configured to obtain, in particular, request and receive information about the collected data from a device for discovering data on a network, obtaining, in particular , by transmitting a request, the data being collected corresponding to the information about the data being collected from the first device, receiving from the first device in response to the request information about the collection point and/or information about the interpretation of the acquisition associated with the data being collected, and receiving the collected data from the collection point, relevant information about the point of collection and/or based on information about the interpretation of the receipt.

The first device may be a device providing the collected data, such as NF and/or AF. The collected data may be obtained from a device providing the collected data and/or from information about the collected data received from the data detection device.

The device according to the fourth option can easily and efficiently receive the collected data even if it is non-standardized.

In the implementation form of the fourth option, the device is further configured to receive collected data from the first device if the collection point corresponding to the information about the collection point is a direct collection point, and/or receive the collected data from another device if the collection point corresponding to the information about the point collection point, is an indirect collection point.

In an additional form of implementation of the fourth option, the device is further configured to receive the collected data from the first device to which the request was sent, if the collection point corresponding to the information about the collection point is a direct collection point, and/or receive the collected data from another device, in particular , sending an additional request to another device to which the request was not sent.

The collected data can in particular be obtained from another device if the collection point corresponding to the collection point information is an indirect collection point. Another device can be an external collection point.

The fifth embodiment of the disclosure provides a device for searching analytical data in a network, in particular, a device corresponding to the second embodiment, wherein said device is configured to receive, in particular, request and receive information about analytical metadata from a data discovery device in a network, receive from the second device, in particular, based on the request and/or subscription, analytics data corresponding to the analytics metadata information.

The device corresponding to the fifth option may be an OAM device. The device according to the fifth embodiment can easily and efficiently obtain analytic data that is available on the network.

The sixth embodiment of the disclosure provides a method for discovering data in a network, said method comprising the steps of: receiving from the first device information about the collected data and/or information about analytical metadata, receiving from the second device a request for information about the collected data and/or information about analytical metadata, and provide the second device, in response to its request, information about the collected data and/or information about analytical metadata received from the first device.

The method according to the sixth variant achieves the same advantages and results as the device according to the first variant, and can be extended with appropriate forms of implementation.

The seventh embodiment of the disclosure provides a method for providing collected data to a network, said method comprising the steps of: generating information about the collected data associated with the collected data, and transmitting the information about the collected data to a data discovery device on the network.

The method according to the seventh variant achieves the same advantages and results as the device according to the second variant, and can be extended with appropriate forms of implementation.

The eighth embodiment of the disclosure provides a method for providing analytic data on a network, said method comprising: generating analytic metadata information associated with the analytic data, and transmitting the analytic metadata information to a device for discovering data on the network.

The method according to the eighth variant achieves the same advantages and results as the device according to the third variant, and can be extended with appropriate forms of implementation.

The ninth embodiment of the disclosure provides a method for searching for collected data in a network, said method comprising the steps of: obtaining, in particular, requesting and receiving, information about the collected data from a data discovery device in a network, obtaining, in particular, by transmission from a first device requesting the data to be collected corresponding to the information about the data to be collected, receiving information about the collection point and/or information about the interpretation of the acquisition associated with the data being collected, where the acquisition is performed from the first device in response to the request, and receiving the data to be collected from the collection point corresponding to the information about point of collection, and/or based on information about the interpretation of the receipt.

The method according to the ninth variant achieves the same advantages and results as the device according to the fourth variant, and can be extended with appropriate forms of implementation.

The tenth embodiment of the disclosure provides a method for searching for analytic data on a network, said method comprising the steps of: obtaining, in particular by requesting and receiving, information about analytic metadata from a device for discovering data on a network, obtaining from a device providing analytic data in network, in particular, through the transmission of the request, analytical data corresponding to the information on analytical metadata.

The method according to the tenth variant achieves the same advantages and results as the device according to the fifth variant, and can be extended with appropriate forms of implementation.

In the implementation form of any of the first to ten options, the information about the collected data indicates the associated data collected and how these associated data collected can be obtained.

In a further implementation form of any one of the first to ten options, the collected data information contains at least one of the following: identification of the associated collected data, type of associated collected data, service of the device providing the associated collected data, in particular, which should be used to obtain the collected data. data, information about the point of collection, information about the interpretation of the receipt.

In a further implementation form of any of the first to tenth options, the analytic metadata information indicates related analytics.

In a further implementation form of any of the first to ten options, the analytics metadata information contains at least one of the following: an identification of the associated analytics, an analytics category and/or an analytics type, a target, for example, for each network section or for each application, target value, such as key performance metrics associated with the identification of associated analytics, target parameter, such as granularity, collection interval, and/or algorithm applied to associated analytics.

In a further implementation of any of the first to tenth options, the collection point information indicates where the associated collection data can be obtained from.

In an additional implementation form of any of the first to tenth options, the information about the collection point contains at least one of the following: the type of the associated collection point, in particular, the type of direct or indirect collection point, identification of the associated collection point.

In a further implementation form of any of the first to ten options, the receive interpretation information indicates how the associated collected data may be read and/or processed.

In an additional implementation form of any of the first to ten options, the receive interpretation information contains at least one of the following: identification of the interpreter applicable to the associated data being collected, interpreter type, interpreter reference.

It should be noted that all devices, elements, blocks and tools described in this application could be implemented in software or hardware elements or any combination of them. All steps performed by the various entities described herein, as well as the described functionality to be performed by the various entities, are intended to mean that the respective entity is adapted or capable of performing the respective steps and functionality. Even if, in the following description of specific embodiments, a particular functionality or step to be performed by external entities is not reflected in the description of a certain specific element of that object that performs that particular step or functionality, those skilled in the art will appreciate that these methods and functionality may be implemented by appropriate software or hardware elements, or any combination thereof.

Brief description of the drawings

The embodiments and forms of implementation of the present disclosure described above in the following description of specific embodiments will be explained with reference to the attached drawings, in which:

fig. 1 shows devices corresponding to network deployment embodiments;

fig. 2 - stages of discovery in the network of collected data and analytical data;

fig. 3 shows a procedure for registering analytic metadata information by NWDAF and discovering/querying NF/AF/OAM analytic data in NRF;

fig. 4 - NF/AF/OAM subscription procedure to receive notifications of changes in analytic metadata information in NRF;

fig. 5 shows a procedure for registering data collection information by NF/AF for discovering/querying NWDAF information about collection data in NRF and for collecting data by NWDAF;

fig. 6 shows a method for discovering data on a network according to an embodiment of the disclosure;

fig. 7 shows a method for providing collected data to a network according to an embodiment of the disclosure;

fig. 8 is a method for providing analytics data to a network according to an embodiment of the disclosure;

fig. 9 shows a method for searching for collected data on a network according to an embodiment of the disclosure;

fig. 10 illustrates a method for searching for analytics data on a network according to an embodiment of the disclosure.

Implementation of disclosure

In FIG. 1 shows a number of devices 100, 102, 103, 105, 106, and 109 corresponding to embodiments of the network disclosure. In FIG. 1 also shows the specific interactions of these devices 100, 103, 105, 106, and 109, as further detailed below. Note that the interactions shown in FIG. 1 are not the only possible interactions between these devices.

In particular, the device 100 is configured to discover data on the network. The device 102 is configured to provide the collected data to the network. The device 103 is configured to provide analytic data to the network. Device 105 is configured to search for data on the network. The device 106 is configured to search, in particular, the collected data on the network. Device 109 is configured to search, in particular, for information about analytic metadata. Accordingly, devices 106 and 109 may be the same as device 105. Additionally, device 106 and device 103 may be implemented as a single device, as well as device 109 and device 102.

The device 100 is particularly configured to receive from the device 102 and/or 103 data collection information 101a and/or analytic metadata information 101b. Additionally, the device 100 is configured to receive, for example, from the device 105 a request 104 for information about the collected data and/or information about the analytic metadata. It may, however, also receive such a request 104 from the device 102 and/or from the device 103. The device 100 is then configured to provide data collection information 101a and/or analytic metadata information 101b received from the device 102 to the second device 105 ( and/or device 102 and/or device 103) in response to its request 104. Device 100 may be a Discovery Function and/or NRF device. The device may be an OAM device.

Device 100 may further provide device 105 (and/or device 102 and/or device 103) with notification 110 of a change in state and/or availability of collected data information 101a and/or analytic metadata information 101b.

The device 102 is particularly configured to generate collected data information 101a associated with the collected data and transmit the collected data information 101a to the device 100. The device(s) 102 may be an NF 102a and/or an AF 102a and/or a storage data.

The device 102 may further receive a collection data request 107 based on the information about the data being collected, which may be received from the device 106, as shown in FIG. 1 (but may similarly be performed from device 103 and/or from device 105). The device 102 may then provide 118 collection point information 108a associated with the data being collected to the device (and/or device 103 and/or device 105) in response to its request 107 and/or may provide acquisition interpretation information 108b associated with the data being collected. data to device 106 (and/or device 103 and/or device 105) in response to request 107 and/or may provide receive interpretation information 108b to configure target device 200. Additionally, device 102 may also configure 119 target device 200 with which may be, for example, ECP.

The device 103 is configured to generate analytic metadata information 101b associated with the analytics and communicate the analytics metadata information 101b to the device 100. The device 103 may be an Analytics Function and/or NWDAF device.

The device 106 is configured to receive, for example, requesting and receiving information about the collected data 101a from the device 100, and then receiving from the device 102, for example, sending a request for the collected data corresponding to the information about the collected data 101. Additionally, the device 106 is configured to receive the collection point information 108a and/or the acquisition interpretation information 108b associated with the data being collected from the device 102 in response to the request 107, and to receive the collection data from the collection point corresponding to the collection point information 108a , and/or based on the receive interpretation information 108b. Device 106 may be an Analytics Function and/or NWDAF device or other 5G system entity.

The device 109 is configured to receive, for example, by request 123 and receive 124, analytic metadata information 101b from the device 100, and obtain, in particular based on the request 125 and/or subscription, analytic data from the device 103, in accordance with analytic metadata information 101b received from device 100.

With reference to the network and devices 100, 102, 103, 105, 106, 109 shown in FIG. 1, further details and exemplary implementations will now be explained.

Device 100 may be a device with a Discovery Function (e.g., implemented in NRF) of 5G systems that supports discovery of collected data from sources of collected data, such as devices 102 that provide collected data on the network, such as 5G system entities such as as NFS/AF (NF 102a / AF 102b), and supporting the discovery of analytical data from devices with the function of analytics (Analytics Function), for example, from the device 103 providing analytical data.

The network data discovery device 100 may in particular be configured to:

• Receiving and storing information 101a about collected data, received, for example, in an alert, from one or more devices 102 providing collected data (ie, from NF devices 102a and/or AF devices 102b and/or from data storage devices).

• Receiving and storing information 101b about analytic metadata received, for example, in an alert, from device 103 to provide analytic data.

• Receiving an offer/request 104 to retrieve collected data information 101a from one or more devices 102, 103, 105 and/or 106 providing collected data on the network, ie, from one or more sources of collected data.

• Receiving an offer/request from 5G system entities (eg, devices 102) providing data to be collected and/or OAM or other devices searching for analytic data to retrieve analytic metadata information 101b available in 5G systems.

• Receiving subscription requests, eg from OAM, which should notify changes in the state of analytic metadata information 101b (eg, changes in data type, collection point, data granularity, etc.).

The collected data can usually be any information that is provided by its producer and can be obtained by the consumer. Information 101a about the collected data specifically may contain at least one of the following: identification of the data being collected; type of data collected (structured/standardized or unstructured/non-standardized data); a device service 102 providing the collected data to be used by the consumer to request/subscribe to the collected data; collection point information; and/or information about the interpretation of the receipt.

The analytic metadata information 101b may comprise at least one of the following: analytic data ID, analytic data category ID, analytic data type ID; reporting/target (eg, per network section, per application, per TA); target values (for example, all KPIs associated with the analytics ID); target parameters (for example, "granularity in generating analytics data", the interval of data collection for generating analytics, the algorithms used for the analytic ID).

The device 103 providing analytical data (Analytics Function) can be configured to:

• Obtaining information 101b about the collected data from the device 100 data detection.

• Using the received information 101a about the collected data to send a request/subscribe message 107 to the device 102 providing the collected data.

• Receipt from the device 102 of a response confirming or rejecting the request/subscription and, if a response is received, the response must contain information 108a about the collection point, if information 108a about the collection point was not included in the information 101b received from the device 100 about the collected data, and receiving interpretation information 108b if the receiving interpretation information 108b was not included in the collected data information 101b received from the device 100 .

Collection point information 108a contains at least the following fields: collection point type (i.e., direct or indirect), collection point identification (eg, collection point IP address or IF for NF, and/or service to be initiated to receive collected data at that address), that is, from where the collected data should be obtained.

The acquisition interpretation information 108b may be a schema and/or parser and/or script to be used to process (eg, calculate an average from a set of samples) and/or read (eg, using a data structure read scheme) the collected data.

The receiving point is the object that stores the collected data, and it can be a direct receiving point, which means that the device providing the collected data is the same object as the object that stores the collected data. Alternatively, it may be an indirect collection point in which the entity holding the data to be collected, i.e., the External Collection Point (ECP) is not the same entity that generates/produces/provides the data to be collected.

The collection data providing device 102 (source of the collection data) can configure the ECP (also referred to as the "target device" to be configured) with the authorization that entities such as the device 103 can receive the collection data stored in the ECP. The authorization configuration may be the default configuration in the ECP, or may be performed before the collection data source sends a response associated with a request/subscription to the collection data stored in the ECP.

The device 103, after requesting the device 100 and subscribing/requesting the collection of data from the device 102, should have the following information: data collection information 101a, collection point information 108a, and acquisition interpretation information 108b.

In FIG. 2 shows the exemplary steps for discovering data collection information 101a and analytic metadata information 101b on the network as described above. These steps are as follows:

1: These steps describe the process of registering NF/AF devices (here devices 102, that is, 102a/102b).

1a: NF devices 102a and/or AF devices 102b transmit a Discovery Function device registration request (here device 100) containing information 101a about the collected data to be provided (for example, in an alert, i.e., "reported ") by devices such as NF device 102a and/or AF device 102b.

1b: The Analytics Function device (here, the device 103) sends a registration request to the Discovery Function device 100 containing information 101b about the analytical metadata to be reported by the Analytics Function device 103.

2: These steps are associated with information discovery by querying (that is, sending a search request) information stored in the Discovery Function device 100 .

2a, b: The NF device 102a and/or AF 102b and/or the OAM device (here device 105) sends a request to the Discovery Function device 100 searching for information 101b about the analytic metadata associated with the analytic function device 103 ( Analytics Function).

2c: The Analytics Function device 103 sends a request to the Discovery Function device 100 searching for the collected data.

3: NF 102a and/or AF 102b and/or OAM 105 subscribe to receive from device 100 with a Discovery Function status change notifications of collected data information 101a as well as analytic metadata information 101b. Ultimately, changes to either the collected data information 101a or the analytics metadata information 101b are updated by the discovery device 100, and entities that have subscribed to such changes will receive notification messages and can use such notification to regulate their actions.

3a: NF 102a and/or AF 102b and/or OAM 105 subscribe to receive change notifications related to analytic metadata information 101b reported/registered by the Analytics Function device 103 in the Discovery device 100 function).

3b: The Analytics Function device 103 subscribes to receive change notifications related to the data collection information 101a notified/recorded by the NF/AF 102 in the Discovery Function device 100.

3c: If changes to data collection information 101a and/or analytic metadata information 101b occur, they are propagated to device 100 with a Discovery Function that will notify entities that are subscribed to receive change notifications associated with such information, and these objects can adapt their actions accordingly.

4: NF 102a and/or AF 102b and/or OAM 105, based on the detected analytic metadata information 101b, subscribe 103 device with analytic function 103 (Analytics Function) to receive analytic data.

5: These steps describe a process for allowing the Analytics Function device 103 to obtain the collected data associated with the collected data information 101a requested from the Discovery Function device 100 .

5a: Analytics Function devices 103 send a registration request to NF 102a and/or AF 102b to retrieve one or more collected data represented by such NF 102a and/or AF 102b.

5b: NF 102a and/or AF 102b decide whether or not to accept the request from the Analytics Function device 103, if received, NF 102a and/or AF 102b determine the collection point for the requested collection data. If collection point information 108a is contained in collection data information 101a used in registering NF 102a and/or AF 102b, NF and/or AF 102 must be compatible and decide for the same collection point information 108a being advertised.

5c: If the type of collection point for the collected data is indirect, the NF 102a and/or AF 102b send the ECP 200 a configuration to allow the device 103 with the Analytics Function 103 to retrieve data from the ECP 200. This configuration contains authorization and, if necessary, , acquisition interpretation information 108b, such as the schema and/or parser and/or script to be used by the ECP 200 to prepare the data to be collected.

5d: NF 102a and/or AF 102b, in case of receiving a subscription, send a subscription response to the device 103 with an analytical function (Analytics Function), NF 102a and/or AF 102b include information 108a about the collection point and/or information 108b about acquisition interpretations for each requested collection data, if collection point information 108a and/or acquisition interpretation information 108b were not previously determined in step 1.

6: These steps are related to the actual data collection performed by the Analytics Function device 103, the Analytics Function device 103 should have data collection information 101a, collection point information 108a, and acquisition interpretation information 108b, to efficiently collect the collected data.

6a: Using the information 108a about the point of collection, the device 103 with an analytical function (Analytics Function) performs direct data collection in NF 102a and/or AF 102b; and/or

6b: Using the collection point information 108a, the Analytics Function device 103 performs indirect data collection in the ECP 200 (which is an entity other than the same source of data being collected).

6c: The ECP 200 checks whether the consumer, that is, the device 103 with the Analytics Function, is allowed to receive the collected data, and if necessary, the ECP 200 applies the receive interpretation information 108b to process the collected data to be sent. device 103 with an analytical function (Analytics Function). If the request received by the ECP 200 implies multiple occurrences of data collection notifications, the ECP 200 is configured, if possible, to apply for each notification the receive interpretation information 108b before sending the notification.

6d: The device 103 with the Analytics Function 103 receives the collected data from the collection point (NF and/or AF 102) indicated in the collection point information 108a, and uses the acquisition interpretation information 108b to process and/or read the received collected data.

7: The Analytics Function device 103 103 uses the collected data to generate analytical data.

Accordingly, with reference to FIG. 2 offers the following improvements and features:

• Discovery device 100 enhanced with the following features:

Поддержка регистрации, включая доступные данные, которые должны быть собраны (информация 101a о собираемых данных) от NF 102a и/или AF 102b.

Registration support, including available data to be collected (data collected information 101a) from NF 102a and/or AF 102b.

Поддержка регистрациии, включая информацию 101b об аналитических метаданных, от устройства 103 с аналитической функцией (Analytics Function).

Support registration, including information 101b about analytical metadata, from the device 103 with an analytical function (Analytics Function).

Разрешение запроса информации о собираемых данных 101a от NF 102a и/или AF 102b.

Permission to request information about collected data 101a from NF 102a and/or AF 102b.

Разрешение запроса аналитических (мета-) данных от устройства 103 с аналитической функцией (Analytics Function).

Permission to request analytical (meta) data from the device 103 with an analytical function (Analytics Function).

• NF 102a and/or AF 102b enhanced with the following features:

Генерирование информации 101a о собираемых данных и включения ее, например, в оповещение, которое может быть составлено из следующих полей:

Generating information 101a about the collected data and including it, for example, in an alert, which can be composed of the following fields:

- Data type (structured/standardized or unstructured/non-standardized data),

- Data format: from the list of data types (DataTypes) in TS29.571 (if structured) or schemas (Schema) (if unstructured).

Определение информации 108a о точке сбора (то есть, откуда собираемые данные могут быть выбраны/получены), чтобы позволить прямой сбор данных (то есть, от одного и того же объекта, оповещающего о собираемых данных) и/или косвенный сбор данных (то есть, от различных объектов/функций/хранилищ от объекта, оповещающего о собираемых данных).

Defining collection point information 108a (i.e., where the data being collected can be fetched/obtained from) to allow direct data collection (i.e., from the same object reporting the data being collected) and/or indirect data collection (i.e., , from various objects/functions/stores from the object notifying about the collected data).

- While the type of data is produced by a given NF 102 (e.g., session information in SMF) or AF 102 based on operator or third party configuration, respectively, such data may need to be obtained from various locations, e.g. specific repositories

Определение модели сбора данных (подписка, на основе запроса, на основе события, делегирование в случае косвенной точки сбора и т.д.).

Define the data collection model (subscription, request-based, event-based, delegation in case of indirect collection point, etc.).

Услуги по сбору данных, улучшенные с помощью:

Data collection services improved with:

- Definition of information 108b about the interpretation of the receipt, which is used by the consumer of such a service to process and read the collected data. Examples of such receive interpretation information 108b are schema and/or parser and/or script.

- Identification of collection point (eg direct or indirect).

- Data collection authorization.

• Device 103 with Analytics Function 103 enhanced with the following features:

Генерирование информации 101b об аналитических метаданных, связанной с аналитическими данными, которые могут быть сформированы таким устройством с аналитической функцией (Analytics Function) (например, путем улучшения контента ее регистрации в устройстве 100 с функцией обнаружения (Discovery Function)).

Generating analytic metadata information 101b related to analytics that can be generated by such an Analytics Function device (for example, by improving the content of its registration in the Discovery Function device 100).

Запрос устройства 100 с функцией обнаружения (Discovery Function) и/или OAM 105, чтобы идентифицировать возможные стандартные/структурированные и/или нестандартные/ неструктурированные собираемые данные, которые могут поддерживать генерирование аналитических данных.

Query device 100 with Discovery Function and/or OAM 105 to identify possible standard/structured and/or non-standard/unstructured data collections that may support analytic data generation.

Получение (например, посредством запроса или подписки) обнаруженных собираемых данных из указанной информации 108a о точке сбора.

Obtaining (eg, by querying or subscribing) the detected collection data from the specified collection point information 108a.

Получение и считывание собираемых данных от точки сбора, используя информацию 108b об интерпретации получения.

Receiving and reading collected data from the collection point using information 108b about the interpretation of the receipt.

• OAM 105 enhanced with the following features:

Адаптация к запросу устройства 100 с функцией обнаружения (Discovery Function), чтобы получить информацию об аналитических данных и/или подписаться на изменения в метаданных 101b доступных аналитических данных от устройства 103 с аналитической функцией (Analytics Function) в устройстве 100 с функцией обнаружения (Discovery Function).

Adapting to a Discovery Function device 100 request to retrieve analytic data information and/or subscribe to changes in available analytic data metadata 101b from the Analytics Function device 103 in the Discovery Function device 100 ).

Основными преимуществами, к которым ведут вышеупомянутые улучшения и функции, являются:

The main benefits brought about by the aforementioned improvements and features are:

• Reduced need for manual configuration:

Поддержка более быстрого развертывания NFS/AF 102 без необходимости вручную конфигурировать данные, которые могут собираться от различных объектов, и установка конфигурации, для которой доступны аналитические данные.

Support for faster deployment of NFS/AF 102 without the need to manually configure the data that can be collected from various objects, and set the configuration for which analytical data is available.

В случае, когда администратор устройства 103 с аналитической функцией (Analytics Function) внутри систем 5G является не таким же, как OAM 105, OAM 105 знает о начальной конфигурации устройства 103 с аналитической функцией (Analytics Function), но OAM 105 узнает только об изменениях устройства 103 с аналитической функцией (Analytics Function) (например, о новых типах аналитических данных), только когда администратор устройства 103 с аналитической функцией (Analytics Function) лично/вручную информирует администратора OAM о таких изменениях.

In the case where the Analytics Function device manager 103 within 5G systems is not the same as the OAM 105, the OAM 105 knows about the initial configuration of the Analytics Function device 103, but the OAM 105 only knows about device changes 103 with Analytics Function (eg, new types of analytics) only when the administrator of the device 103 with Analytics Function personally/manually informs the OAM administrator of such changes.

• Analytics support using standardized and non-standardized data sources and analytics output.

Структура обнаружения позволяет поставщикам оповещать о нестандартизированной информации для поддержки аналитики.

The discovery framework allows vendors to advertise non-standardized information to support analytics.

• Allows monetization of providing data sources to improve analytics.

Поставщики могут взимать дополнительную плату (например, за информацию оповещения) за разрешение их продуктам предоставлять нестандартизированную информацию, которая улучшает генерирование аналитических данных.

Vendors may charge additional fees (for example, for alert information) to allow their products to provide non-standardized information that improves analytics generation.

• Allows monetization of new analytics

Поставщики могут взимать дополнительную плату (например, за информацию оповещения) за разрешение их продуктам предоставлять нестандартизированную и новую доступную аналитику, которая должна использоваться остальной частью системы.

Vendors may charge additional fees (for example, for alert information) for allowing their products to provide non-standardized and newly available analytics to be used by the rest of the system.

Some general concepts for applying the disclosure embodiment to 3GPP 5G systems are now described below, based on Revision 15 and the definitions in the Study Item section of Revision 16 "Enablers for Network Automation for 5G":

• NWDAF in 3GPP can be enhanced with the capabilities of the Analytics Function device 103 described above.

• There are two possibilities for implementing discovery device 100 as described above, and the preferred implementation (explained further in detail below) uses NRF. Possible implementations are:

Альтернатива, основанная на NRF, где NRF улучшается с помощью возможностей устройства 100 с функцией обнаружения (Discovery Function).

An alternative based on NRF where the NRF is enhanced by the capabilities of the device 100 with a Discovery Function.

Альтернатива, основанная на функции представления сети (Network Exposure Function, NEF), где NEF улучшается с помощью возможностей устройства 100 с функцией обнаружения (Discovery Function).

An alternative based on the Network Exposure Function (NEF), where the NEF is enhanced by the capabilities of the Discovery Function device 100.

Расширяются функциональные возможности функции хранения неструктурированных данных (Unstructured Data Storage Function, UDSF), чтобы поддерживать обнаружение и сбор данных.

The functionality of the Unstructured Data Storage Function (UDSF) is extended to support data discovery and collection.

• There are the following possible service implementations from NF/AF 102 that allow data collection using the information defined above:

Определение услуги Nxxx_EventExposure в NF и/или AF 102, или, в случае AMF, SMF, UDM и NEF, расширение этой услуги, которая уже была определена в TS 23.502. Расширение связывается с результатом операции подписки, чтобы включать информацию 108a о точке сбора и информацию 108b об интерпретации получения.

The definition of the Nxxx_EventExposure service in NF and/or AF 102, or in the case of AMF, SMF, UDM and NEF, an extension of this service that has already been defined in TS 23.502. The extension is associated with the result of the subscription operation to include collection point information 108a and acquisition interpretation information 108b.

Расширение услуги NF<X>_DataCollection, определенной в TR 23.791, чтобы включать в ответ о подписке информацию 108a о точке сбора и информацию 108b об интерпретации получения.

An extension to the NF<X>_DataCollection service defined in TR 23.791 to include collection point information 108a and receipt interpretation information 108b in the subscription response.

Расширяются операции услуги Nudsf_UnstructuredDataManagement от UDSF, чтобы позволить NF 102, которая создает запись для хранения собираемых данных для указания NF 102, авторизованной для запроса конкретных данных, а также для указания информации об интерпретации получения, которая должна использоваться для информации о собираемых данных, которая должна храниться в UDSF.

The operations of the Nudsf_UnstructuredDataManagement service from the UDSF are extended to allow the NF 102 that creates an entry to store the collected data to indicate the NF 102 authorized to request specific data, as well as to indicate the receive interpretation information to be used for the collected data information to be be stored in UDSF.

The following detailed description of embodiments corresponding to the disclosure is based on the aforementioned preferred implementation of device 100 in NRF, i.e., an alternative based on NRF 100.

Collection point information 108a may be implemented as:

• Collection point type, eg direct, indirect (collectionPointType)

• Collection point identification (collectionPointID); possible implementations are:

ID точки сбора NF/AF/дополнительной внешней (например) + ID услуги (например, URL для инициирования услуги в точке сбора).

NF/AF collection point ID/additional external (for example) + service ID (for example, the URL to initiate the service at the collection point).

ID услуги (например, URL для инициирования услуги в точке сбора).

Service ID (for example, the URL for initiating the service at the collection point).

Опорной точки, протокол, способ и адрес объекта, с которым следует контактировать через опорную точку.

Reference point, protocol, method and address of the object to be contacted through the reference point.

The receiving point information 108b may be implemented as consisting of:

• The Interpreter ID identifies a single interpreter available to apply to the collected data.

• Interpreter Type: defines the type of interpreter and examples of interpreter types are: parsers, schema, script.

• Interpreter Link: The actual document/file/software associated with the interpreter ID.

Collected data information 101a and/or analytic metadata information 101b may be included in the alert and may be implemented as:

• Extensions to the NF Profile (NF Profile) currently defined in TS 23.502 and TS 29.510 to support:

Информации 101a о собираемых данных, состоящей из следующего:

Information 101a about the collected data, consisting of the following:

- Identification of the service that the consumer of the collected data must request/subscribe/register in order to access/authorize the collected data (collectionServiceID).

- Data Identification (cdataID).

- Data Type (Data Type), for example, structured / unstructured (cdataType).

- Collection point (optional).

- Information about the receiving interpreter (optional)

Информация 101b об аналитических метаданных, состоящая из следующего:

Analytic metadata information 101b, consisting of the following:

- An analytic ID, which is a number assigned to identify each analytic that can be generated by NWDAF 103.

- An analytics category ID that is assigned to a possible analytics category where analytics category information was previously defined in PCT/EP2018/071679.

- An analytic type identifier that is associated with the nature of the NWDAF 103 result, which can be either an analytic or a recommendation, as defined in TR 23.791 and further clarified in PCT/EP2018/071679. Reporting/Target, which is a description of the objects to be analyzed by NWDAF 103 to generate analytical data. Target information has been defined in PCT/EP2018/071679 and exemplary embodiments for this information are: "each network hop, each application, each TA".

- Target values that define the information/KPI that NWDAF 103 can generate for the analytic ID, examples of target values are network load, UE experience satisfaction, etc. as defined in PCT/EP2018/071679.

- Target parameters, which define the parameters that can be configured to generate the analytic ID, such as the frequency of analytic generation, the collection interval for generating analytics, the algorithms applicable to the analytic ID, etc.

The request 104 for information about the collected data 101a and/or information 101b about analytical metadata can be implemented as follows:

• The Get operation from the NRF Nnrf_NFDiscovery service is extended to support, respectively, discovery/query of data being collected information 101a as well as analytic metadata information 101b. The list of query parameters defined by table 6.2.3.2.3.1-1 in TS 29.510 can be extended with the following new parameters:

cdataID

cdataID

cdataType

cdataType

collectionPointType

collectionPointType

collectionPointID

collectionPointID

analyticsID

analyticsID

analyticsCategoryID

analyticsCategoryID

analyticsTypeID

analyticsTypeID

analyticsTargetObject

analyticsTargetObject

analyticsTargetYalues

analyticsTargetYalues

analyticsTargetParameters

analyticsTargetParameters

Some common definitions in this context for data collection and analytics discovery considering NRF-based implementations are:

• Data to be collected through NWDAF 103 may include:

CData#l: Расширенной информацией об управлении сеансом, созданной SMF и точкой сбора, является UDSF. Такая информация является неструктурированными/нестандартизированными данными, и такие собираемые данные имеют в качестве сценария информацию 108b об интерпретации получения.

CData#l: Extended session management information generated by SMF and collection point is UDSF. Such information is unstructured/non-standardized data, and such collected data has received interpretation information 108b as a script.

CData#2: Информация о мобильности UE (UE Mobility), напрямую получаемая из AMF.

CData#2: UE mobility information (UE Mobility) directly obtained from the AMF.

CData#3: Опыт услуги, получаемый из AF.

CData#3: Service experience received from AF.

Collection point information, as well as acquisition interpretation information 108b, may be included in the NF Profile registration 101.

In FIG. 3 shows an exemplary procedure for registering analytic metadata information 101b with NWDAF 103 and for NF/AF 102 and OAM 105 discovering/querying analytic metadata information 101b in NRF 100. The procedure includes the following steps:

NWDAF 103 uses the Nnrf_NFManagement_NFRegister service operation from NRF 100 to register with NRF 100. NFProfile information 101 contains information 101b about analytic metadata.

1. NRF 100 stores analytic metadata information 101b received from NWDAF 103 that has been included in NF Profile 101 (NF Profile).

2. NF and/or AF 102 and/or OAM 105 use the Get Nrf_NFDiscovery service operation received from NRF 100 to look up information about the NWDAF NF and its analytic metadata.

3. The NRF 100 sends a response to the request containing the NF Profile (NF Profile) 101 of the NWDAF 103 and its associated analytic metadata information 101b.

4. Using information 101b about analytical metadata from the NF profile (NF Profile) 101 NWDAF received from NRF 100, NF and/or AF 102 and/or OAM 105, use the services offered by NWDAF 103 (Nnwdaf_AnalyticsInfo, or Nnwdaf_EventSubscription, or Nnwdaf_Recommendation) , as defined in 3GPP TR 23.791, to request/subscribe to receive insights or recommendations from NWDAF 103.

In FIG. 4 shows the procedure for subscribing NFS/AF 102 and OAM 105 to receive notifications of changes to analytic metadata information 101b in NRF 100. The procedure contains the following steps:

1. NF and/or AF 102 and/or OAM 105 uses the Nrf_NFManagement NFStatusSubscribe service operation from NRF 100 to subscribe to receive analytic metadata information updates from WDAF NF Profile 101.

2. NRF 100 sends a response to the request containing the identification ID of the subscription.

3. NWDAF 103 analytic metadata information 101b is updated and/or there is an availability in NWDAF 103 that requires NRF 100 to de-register it. NWDAF 103 informs NRF 100 of any changes.

4a. NWDAF 103 uses the Nrf_NFManagement NFUpdate service operation from NRF 100 to update its analytic metadata information 101b.

4b. The NWDAF 103 uses the Nnrf_NFManagement_NFDeregister service operation from the NRF 100 to indicate its unavailability. The NRF 100 uses the Nrf_NFManagement NFStatusNotify service operation to send a change notification of the NWDAF 103 to the NF and/or AF 102 and/or OAM 105 that is subscribed to receive such notifications.

Note that in the case where the operator does not allow direct access to NF 102 for AF 102, communication can be done through NEF 300.

8. NWDAF 103 uses the information from the Nrf_NFManagement NFStatusNotify service operation to update the analytics generation if required.

Note that steps 5-8 can take place at any time when there is a change in the data collection information 101b.

9. This step shows the interactions in the case of the indirect collection point type:

9a. The NWDAF 103 uses the NFsmf_DataCollection Subscribe service operation from the SMF 500 to subscribe to receive the collected data CData#l.

9b. SMF 500 performs authorization and checks what kind of collection point should be used by NWDAF 103 to collect CData#l.

9c. The SMF 500 uses the Nudsf_UnstructuredDataManagement service operations from the UDSF 502 to allow the NWDAF 103 to receive the collected data CData#l from the UDSF 502. In this embodiment, it is not necessary for UDFS 502 to apply any receive interpretation information 108b when NWDAF 103 requests CData#l.

9d. The SMF 500 uses the NFsmf_DataCollection Subscribe service operation to confirm to the NWDAF 103 in such a response that it can collect the requested data, including collection point information 108a and receipt interpretation information 108b.

10. This step shows the interactions between NWDAF 103, AMF 501, AF 102 for direct rally type:

10a. The NWDAF 103 uses the NFamf_DataCollection Subscribe service operation from the AMF 501 to subscribe to receive the collected data CData#2.

10b. The AMF 501 response in such a response confirms to the NWDAF 103 that it can collect the requested data, including collection point information 108a (AMF 501 itself) and receipt interpretation information 108b (none as this is standardized information).

10c. The NWDAF 103 uses the NFamf_DataCollection Subscribe service operation received from the AF 102 to subscribe to receive the collected data CData#3.

10d. The response of AF 102 confirms to NWDAF 103 that it can collect the requested data in such a response, including collection point information 108a (AF 102 itself) and receipt interpretation information 108b (none, since this is standardized information).

11. This step describes the NWDAF 103 interactions to perform indirect collection:

11a. NWDAF 103 uses the Nudsf_UnstructuredDataManagement_Query service operation received from UDSF 502 to query CData#l.

11b. UDSF 502 checks if NWDAF 103 is authorized to collect CData#l

11c. UDSF 502 sends the requested CData#l to NWDAF 103.

12. This step describes the interactions of NWDAF 103 to perform direct collection.

12a. AMF 501 uses the NFamf_DataCollection service operation to send CData#2 to NWDAF 103.

12b. AMF 501 uses the NFaf_DataCollection Notify service to send CData#3 to NWDAF 103.

In FIG. 6 shows a method 600 corresponding to an embodiment of the disclosure, in which method 600 is for discovering data on a network. The method 600 includes: step 601, which receive information 101b about the collected data and/or information 101b about analytical metadata from the first device 102, 103; step 602, receiving a request 104 for data collection information 101a and/or analytic metadata information 101b from the second device 105 (and/or 102, 103 and/or 106); and a step 603 providing data collection information 101a and/or analytic metadata information 101b obtained from the first device 102, 103 to the second device 105 (and/or 102, 103 and/or 106) in response to its request 104 Method 600 may be performed by device 100, such as NRF.

In FIG. 7 shows a method 700 corresponding to an embodiment of the disclosure, in which the method 700 is for providing collected data to a network. Method 700 includes: step 701, which generate information 101a about the collected data associated with the collected data; and step 702, which transmit information 101a about the collected data to the device 100 to discover data on the network. Method 700 may be performed by device 102, such as NF 102a or AF 102b.

In FIG. 8 shows a method 800 according to an embodiment of the disclosure, in which method 800 is for providing analytics data to a network. The method 800 comprises: step 801 generating analytic metadata information 101b associated with the analytic data; and step 802, which transmit information 101b about the analytical metadata to the device 100 to discover data on the network. Method 800 may be performed by device 103, such as NWDAF 103.

In FIG. 9 shows a method 900 corresponding to an embodiment of the disclosure, wherein the method 900 is for searching the collected data on a network. The method 900 includes: step 901, which receive, for example, a request and receive information 101a about the collected data from the device 100 to discover data in the network; step 902, which receive, for example, by transmitting the request 107 of the collected data corresponding to the information 101a about the collected data, from the first device 102, 103; step 903, receiving information 108a about the collection point and/or information 108b about the interpretation of the acquisition associated with the data being collected, where the acquisition is made from the first device 102, 103 in response to the request 107; and step 904, receiving the collected data from the collection point according to the collection point information 108a and/or based on the acquisition interpretation information 108b. Method 900 may be performed by device 106, such as NWDAF.

In FIG. 10 shows a method 1000 according to an embodiment of the disclosure, in which method 1000 is for searching for analytics data on a network. The method 1000 includes: step 1001, which receive, for example, a request and receive information 101b about analytical metadata from the device 100 to discover data in the network; and a step 1002 of obtaining, for example, by sending a request for analytic data corresponding to the analytic metadata information 101b from the device 103 providing the analytic data on the network. Method 1000 may be performed by device 105, such as OAM 105.

This disclosure has been described in conjunction with various exemplary embodiments as well as implementations. However, other variations of the claimed disclosure should be understood and practiced by those skilled in the art based on a study of the drawings, this disclosure, and the independent claims of the disclosure. In the claims of the disclosure, as well as in the description, the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A single element or other block can perform the functions of several objects or elements represented in the disclosure formula. The mere fact that certain measures are repeated in mutually different dependent claims of the disclosure does not indicate that a combination of these measures cannot be used in the preferred implementation.

Claims (89)

1. A device (100) for discovering data in a network, characterized in that it is implemented as a network repository function (NRF) and is configured to: receiving, from at least one first device (102) configured to provide collected data, information (101a) about the collected data, and the collected data contains information provided by the first device (102) and recovered by the device (100), while the first device implemented as a network function (NF) and/or application function (AF); receiving, from the second device (102, 103, 106, 105) searching for collected data in the network, requesting (104) information about the collected data, and providing the second device (105, 102, 103, 106), in response to the request (104), with information (101a) about the collected data. 2. Device (100) according to claim 1, characterized in that it is additionally configured to: providing, to the second device (102, 103, 105), a notification (110) of a change in state and/or the availability of information (101a) about the collected data. 3. Device (100) according to claim 1 or 2, wherein the collected data information (101a) indicates the associated collected data and/or how said associated collected data can be obtained. 4. The device (100) according to any one of paragraphs. 1-3, in which information (101a) about the collected data contains at least one of: - identification of associated collected data, - the type of associated data collected, - the services of the device providing the associated collected data, in particular to be used to obtain the collected data, - information (108a) about the collection point, and - information (108b) about the interpretation of the receipt. 5. Device (102) for providing collected data on the network, characterized in that it is implemented as a network repository function (NRF) or application function (AF) and is configured to: generating information (101a) about the collected data related to the collected data, and the collected data contains information provided by the first device (102) and recovered by the network data discovery device (100), and transmitting information (101a) about the collected data to the network data discovery device (100) so that information (101a) about the collected data is provided from the device (100) to the second device in response to a request (104) for information about the collected data received from the second device , wherein the device (100) is implemented as a network repository function (NRF). 6. Device (102) according to claim 5, characterized in that it is additionally configured to: receiving a request (107) for data to be collected based on information about the data to be collected from a second device (106, 103, 105) searching for the data to be collected on the network, and providing (118) to the second device (106, 103, 105), in response to the request (107), information (108a) about the collection point related to the collected data. 7. Device (102) according to claim 6, characterized in that it is additionally configured to configuring (119) the target device (200) to receive data from the device (102). 8. The device (102) according to any one of paragraphs. 5-7, characterized in that it is additionally configured to: receiving a request (107) for collected data based on the information (101a) about the collected data from the second device (105, 106, 103), and providing the second device (105, 106, 103), in response to the request (107), with information (108b) about the interpretation of the receipt, related to the collected data, and/or providing information (108b) about the interpretation of the receipt for the configuration of the target device (200). 9. The device (102) according to any one of paragraphs. 5-8, in which the collected data information (101a) indicates the associated collected data and/or how said associated collected data can be obtained. 10. The device (102) according to any one of paragraphs. 5-9, in which information (101a) about the collected data contains at least one of: - identification of associated collected data, - the type of associated data collected, - the services of the device providing the associated collected data, in particular to be used to obtain the collected data, - information (108a) about the collection point, and - information (108b) about the interpretation of the receipt. 11. The device (102) according to claim 6 or 10, in which the collection point information (108a) indicates where the associated collection data can be obtained from. 12. The device (102) according to any one of paragraphs. 6, 10 and 11, in which collection point information (108a) contains at least one of: - the type of associated collection point, in particular the type of direct or indirect collection point, and - identification of the associated collection point. 13. Device (102) according to claims 8 and 10, in which the receive interpretation information (108b) indicates how the associated collected data can be read and/or processed. 14. The device (102) according to any one of paragraphs. 8, 10 and 13, in which receive interpretation information (108b) contains at least one of: - identification of the interpreter applied to the associated collected data, - the type of interpreter, and - interpreter links. 15. The system for providing data on the network, containing the device (102) for providing the collected data on the network according to any one of paragraphs. 1-4 and a device (103) providing analytical data in the network, and the device (103) providing analytical data in the network is configured to: generating information (101b) about analytic metadata related to the analytics, and transmitting information (101b) about the analytical metadata to the device (100) data discovery in the network. 16. The system of claim 15, wherein the analytic metadata information (101b) indicates associated analytics data. 17. The system of claim 15 or 16, wherein the analytic metadata information (101b) comprises at least one of: - identification of associated analytical data, - categories of analytical data, and/or - type of analytical data, - the target object, in particular for each network section or for each application, - the target value, in particular, indicators of key indicators related to the identification of associated analytical data, and - target parameter, in particular, the granularity of the associated analytic data, the collection interval of the associated analytic data and/or the algorithm used for the associated analytic data. 18. The system for providing data on the network, containing the device (100) data discovery on the network according to any one of paragraphs. 1-4 and a device (106) for searching the collected data in the network, and the device (106) for searching the collected data in the network is configured to: receiving, in particular, by request (120) and receiving (121), information (101a) about the collected data from the data discovery device (100) in the network, receiving from the first device (102), in particular by requesting (107), the collected data in accordance with the information about the collected data (101a), receiving (118), from the first device (102), in response to a request (107), collection point information (108a) and/or acquisition interpretation information (108b) associated with the data being collected, and receiving collected data from the collection point in accordance with the information (108a) about the collection point and/or based on the information (108b) about the interpretation of the receipt. 19. The system according to claim 18, additionally configured to: receiving collected data from the first device (102) if the collection point corresponding to the information (108a) about the collection point is a direct collection point, and/or receiving collected data from another device (200) if the collection point corresponding to the collection point information (108a) is an indirect collection point. 20. The system according to claim 18, additionally configured to: receiving collected data from the first device (102) to which the request (107) is transmitted, if the collection point corresponding to the collection point information (108a) is a direct collection point, and/or receiving (122) collected data from another device (200), in particular by sending an additional request for collected data to another device (200) to which the request (107) was not transmitted. 21. The system according to any one of paragraphs. 18-20, in which the collection point information (108a) indicates where the associated collection data can be obtained from. 22. The system according to any one of paragraphs. 18-21, in which collection point information (108a) contains at least one of: - the type of associated collection point, in particular the type of direct or indirect collection point, and - identification of the associated collection point. 23. The system according to claim 18, in which the receive interpretation information (108b) indicates how the associated collected data can be read and/or processed. 24. The system according to any one of paragraphs. 18-23, in which receive interpretation information (108b) contains at least one of: - identification of the interpreter applied to the associated collected data, - the type of interpreter, and - interpreter links. 25. A method (600) for discovering data on a network, comprising the steps of: receive (601), using the device (100) data discovery in the network, from at least one first device (102), configured to provide the collected data, information (101a) about the collected data, and the device (100) is implemented as a network repository function (NRF), the collected data contains information provided by the first device (102) and retrieved by the device (100), and the first device is implemented as a network function (NF) and/or an application function (AF); receive (602), using the device (100) data discovery in the network, from the second device (102, 103, 105, 106, 107), which searches for the collected data in the network, request (104) information (101a) about the collected data, And provide (603), by means of the network data discovery device (100), to the second device (105), in response to the request (104), information (101a) about the collected data. 26. A method (700) for providing collected data to a network, comprising the steps of: generating (701), by means of a network function (NF) or an application function (AF), information (101a) about the collected data related to the collected data, and the collected data contains information provided by the network function (NF) or the application function (AF) and recovered by the device (100) to discover data on the network, and transmit (702), respectively, using the network function (NF) or the application function (AF), information (101a) about the collected data to the device (100) data discovery in the network so that information (101a) about the collected data is provided from the device ( 100) to the second device in response to a collection data request (104) received from the second device, the device (100) being implemented as a network repository function (NRF).

Images