Patent Description:
For example, one parameter in providing good performance and capacity for a given communications protocol in a communications network is data collection and analytics.

In this respect, the network data analytics function (NWDAF) is part of the architecture specified in the third generation partnership project (3GPP) technical specification (TS) <NUM> entitled "System architecture for the <NUM> System (5GS)", version <NUM>. <NUM>, and uses the mechanisms and interfaces specified for the fifth generation core network (5GC) and Operations, Administration and Maintenance (OAM).

The NWDAF interacts with different entities for different purposes, such as data collection based on event subscription, provided by network functions (NF) such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Unified Data Management (UDM) entity, Binding Support Function (BSF), Application Function (AF) (directly or via Network Exposure Function (NEF)), and OAM; retrieval of information from data repositories (e.g. Unified Data Repository (UDR) via UDM for subscriber-related information); retrieval of information about NFs (e.g. Network Repository Function (NRF) for NF-related information, and Network Slice Selection Function (NSSF) for slice-related information); and on demand provision of analytics to consumers.

A single instance or multiple instances of the NWDAF may be deployed in a mobile network, such as in a Public Land Mobile Network (PLMN). In case multiple NWDAF instances are deployed, the architecture supports deploying the NWDAF as a central NF, as a collection of distributed NFs, or as a combination of both. When multiple NWDAFs exist, not all of them need to be able to provide the same type of analytics results, i.e., some of them can be specialized in providing certain types of analytics. An Analytics ID information element is used to identify the type of supported analytics that NWDAF can generate. NWDAF instance(s) can be collocated with a 5GS NF.

To retrieve data related to a specific UE, the NWDAF first needs to determine which NF instances are serving this UE, as stated in table <NUM>. <NUM>-<NUM> of aforementioned document 3GPP TS <NUM> unless the NWDAF has already obtained this information due to recent operations related to this UE. However, how the NWDAF determines which NEF and AF instances are serving a specific UE is still undefined.

<NPL>, and <NPL>, relate to data collection from NFs.

3GPP TS <NUM> V16. <NUM> (<NUM>-<NUM>) relates to procedures for the <NUM> system, stage <NUM> (Release <NUM>).

3GPP TS <NUM> V16. <NUM> (<NUM>-<NUM>) relates to architecture enhancements for <NUM> systems to support network data analytics services (Release <NUM>).

Hence, there is still a need for improved discovery mechanisms in communication networks, and especially, but not exclusively, in the fifth generation core network.

An object of embodiments herein is to provide efficient discovering for the NWDAF to determine which NEF or AF is serving a UE.

According to a first aspect there is presented a method for discovering, for data collection, which NEF or AF is serving a UE, according to claim <NUM>.

According to a second aspect there is presented an NWDAF entity for discovering, for data collection, which NEF or AF is serving a UE, according to claim <NUM>.

According to a third aspect there is presented a computer program for discovering, for data collection, which NEF or AF is serving a UE, according to claim <NUM>.

According to a fourth aspect there is presented a method for enabling discovery, for data collection, which NEF or AF is serving a UE, according to claim <NUM>.

According to a fifth aspect there is presented a 5GC network function entity for enabling discovery, for data collection, which NEF or AF is serving a UE, according to claim <NUM>.

According to a sixth aspect there is presented a computer program for enabling discovery, for data collection, which NEF or AF is serving a UE, according to claim <NUM>. Advantageously these methods, these NWDAF entities, these 5GC network function entities, these computer programs, and this computer program product provide efficient discovering for the NWDAF to determine which NEF or AF is serving the UE.

Advantageously these methods, these computer programs, and this computer program product can be used by any NF (not only the NWDAF entity) to discover and communicate with a NEF or an AF serving a specific UE.

Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, from the attached list of claims as well as from the drawings.

All references to "a/an/the element, apparatus, component, means, module, action, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, action, etc., unless explicitly stated otherwise.

<FIG> is a schematic diagram illustrating a communication network <NUM> where embodiments presented herein can be applied. The communication network <NUM> represents a reference architecture of a fifth generation telecommunication system (5GS) and comprises the following entities: and Authentication Server Function (AUSF), an Access and Mobility Management Function (AMF), a Data Network (DN), e.g. operator services, Internet access or 3rd party services, a Network Exposure Function (NEF), a Network Repository Function (NRF), a Network Slice Selection Function (NSSF), a Policy Control Function (PCF), a Session Management Function (SMF), a Unified Data Management (UDM), a Unified Data Repository (UDR), a User Plane Function (UPF), an Application Function (AF), a User Equipment (UE), a (Radio) Access Network ((R)AN), a Network Data Analytics Function (NWDAF), a Binding Support Function (BSF), and a Charging Function (CHF). Service based interfaces are represented by the format Nxyz (e.g., Nnssf, NNef, etc.) and point to point interfaces are represented by the format Nx (e.g. N1, N2, etc.).

As noted above how the NWDAF determines which NEF and AF instances are serving a UE is still undefined and hence, there is still a need for improved discovery mechanisms in communication networks, and especially, but not exclusively, in the fifth generation core network.

The embodiments disclosed herein therefore relate to mechanisms for discovering, for data collection, which NEF or AF is serving a UE and enabling discovery, for data collection, which NEF or AF is serving a UE. In order to obtain such mechanisms there is provided an NWDAF entity <NUM>, a method performed by the NWDAF entity <NUM>, a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the NWDAF entity <NUM>, causes the NWDAF entity <NUM> to perform the method. In order to obtain such mechanisms there is further provided a 5GC network function entity 300a, 300b, 300c, a method performed by the 5GC network function entity 300a, 300b, 300c, and a computer program product comprising code, for example in the form of a computer program, that when run on processing circuitry of the 5GC network function entity 300a, 300b, 300c, causes the 5GC network function entity 300a, 300b, 300c to perform the method.

Reference is now made to <FIG> illustrating a method for discovering, for data collection, which NEF or AF is serving a UE as performed by the NWDAF entity <NUM> according to an embodiment.

S102: The NWDAF entity <NUM> provides, to a 5GC network function entity 300a, 300b, 300c, a query of which NEF or AF is serving the UE. There might be different examples of network function entities. According to a first example, the 5GC network function entity 300a, 300b, 300c is an NRF 300a. According to a second example, the 5GC network function entity 300a, 300b, 300c is a BSF 300b. According to a third example, the 5GC network function entity 300a, 300b, 300c is a UDM entity 300c.

S104: The NWDAF entity <NUM> receives, from the 5GC network function entity 300a, 300b, 300c, a response comprising an ID of the NEF or the AF when there is a NEF or AF instance stored in the 5GC network function entity 300a, 300b, 300c for the UE.

Embodiments relating to further details of discovering, for data collection, which NEF or AF is serving a UE as performed by the NWDAF entity <NUM> will now be disclosed.

There might be different examples of queries that are provided in action S102. According to some embodiments, the query invokes a discovery service in the 5GC network function entity 300a, 300b, 300c. According to some embodiments, the query comprises an ID of the UE.

As will be further disclosed below with reference to <FIG> the NRF might provide to the NWDAF entity <NUM> an address to the NEF or the AF. Hence, according to an embodiment, the NWDAF entity <NUM> is configured to perform action S106:
S106: The NWDAF entity <NUM> receives, from the NRF, an address to the NEF or the AF.

In some embodiments when the 5GC network function entity 300a, 300b, 300c is the NRF, the address to the NEF or the AF is received in the response from the 5GC network function entity 300a, 300b, 300c (i.e., in the response received by the NWDAF entity <NUM> in action S104). Action S102 might then be equal to action <NUM> in <FIG>.

In some embodiments when the 5GC network function entity 300a, 300b, 300c is not the NRF, the address to the NEF or the AF is received in response to the NWDAF entity <NUM> having provided a query to the NRF for a discovery service. The query in action S102 is then equal to either action <NUM> or action <NUM> in <FIG> and the query provided to the NRF for the discovery service is equal to action <NUM> in <FIG>.

As will be further disclosed below, the AF might be in either trusted mode or untrusted mode. Different actions might be performed depending on whether the AF is in trusted mode or in untrusted mode. According to a first example, the address to the AF is received when the AF is in trusted mode, and the address to the NEF is received when the AF is in untrusted mode. This provides the NWDAF entity <NUM> with an indirect indication as to whether the AF is in trusted mode or in untrusted mode. According to a second example, an explicit indication of whether the AF is in trusted mode or in untrusted mode is by the NWDAF entity <NUM> received from the NRF.

As will be further disclosed below with reference to actions <NUM> and <NUM> of <FIG>, when the AF is in untrusted mode, any request for event subscription for the UE is provided to the NEF. Thus, according to some embodiments, when the AF is in untrusted mode, the NWDAF entity <NUM> is configured to perform (optional) actions S108, S110:.

As will be further disclosed below with reference to actions <NUM> and <NUM> of <FIG>, when the AF is in trusted mode, any request for event subscription for the UE is provided to the AF. Thus, according to some embodiments, when the AF is in trusted mode, the NWDAF entity <NUM> is configured to perform (optional) actions S112, S114:.

As disclosed above, a response is in action S104 received when there is a NEF or AF instance stored in the 5GC network function entity 300a, 300b, 300c for the UE. In some embodiments the response instead comprises an error indication in case there is no NEF or AF instance stored in the 5GC network function entity 300a, 300b, 300c for the UE.

Reference is now made to <FIG> illustrating a method for enabling discovery, for data collection, which NEF or AF is serving a UE as performed by the 5GC network function entity 300a, 300b, 300c according to an embodiment. As above, there might be different examples of network function entities. According to a first example, the 5GC network function entity 300a, 300b, 300c is an NRF 300a. According to a second example, the 5GC network function entity 300a, 300b, 300c is a BSF 300b. According to a third example, the 5GC network function entity 300a, 300b, 300c is a UDM entity 300c.

S218: The 5GC network function entity 300a, 300b, 300c receives, from the NWDAF entity <NUM>, a query of which NEF or AF is serving the UE.

S220: The 5GC network function entity 300a, 300b, 300c provides, to the NWDAF entity <NUM>, a response comprising an ID of the NEF or the AF when there is a NEF or AF instance stored in the 5GC network function entity 300a, 300b, 300c for the UE.

Embodiments relating to further details of enabling discovery, for data collection, which NEF or AF is serving a UE as performed by the 5GC network function entity 300a, 300b, 300c will now be disclosed.

As above, in some embodiments, the query invokes a discovery service in the 5GC network function entity 300a, 300b, 300c. As above, in some embodiments, the query comprises an ID of the UE.

As above, in some embodiments when the 5GC network function entity 300a, 300b, 300c is an NRF, an address to the NEF or the AF is provided in the response. As above, in some embodiments, the address to the AF is provided when the AF is in trusted mode, and wherein the address to the NEF is provided when the AF is in untrusted mode. As above, in some embodiments, an explicit indication of whether the AF is in trusted mode or in untrusted mode is provided to the NWDAF entity <NUM>.

Aspects of possible actions that the 5GC network function entity 300a, 300b, 300c might perform before it receives, from the NWDAF entity <NUM>, the query in action S118 of which NEF or AF is serving the UE will now be disclosed.

As will be further disclosed below with reference to action <NUM> of <FIG>, the NEF might invoke the Nnrf_NFRegister service operation in the NRF, specifying that NFType=NEF, and the UE-ID range (i.e., the range of UE-IDs handled by this NEF instance). Thus, according to some embodiments, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S202:
S202: The 5GC network function entity 300a, 300b, 300c (such as the NRF) receives, from the NEF, an ID of the UE.

As will be further disclosed below with reference to action <NUM> of <FIG>, the NEF might register the AF profile in the NRF, invoking the Nnrf_NFRegister service, and specifying that NFType=AF, the App-ID, and that trust=UNTRUSTED. Thus, according to some embodiments, when the AF is in untrusted mode, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S204:
S204: The 5GC network function entity 300a, 300b, 300c receives, from the NEF when the AF is in untrusted mode, an AF profile for registration of the AF in the network function (such as the NRF). The AF profile comprises an indication that the AF is in untrusted mode.

As will be further disclosed below with reference to action <NUM> of <FIG>, the AF might register itself the AF profile in the NRF, invoking the Nnrf_NFRegister service, and specifying that NFType=AF, the App-ID, and that trust=TRUSTED (i.e., an indication that the AF is in trusted mode. Thus, according to some embodiments, when the AF is in trusted mode, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S208:
S208: The 5GC network function entity 300a, 300b, 300c receives, from the AF when the AF is in trusted mode, an AF profile for registration of the AF in the network function (such as the NRF). The AF profile comprising an indication that the AF is in trusted mode.

As will be further disclosed below with reference to actions <NUM>, <NUM>, <NUM> of <FIG>, the NEF might register the mapping between the UE and the AF when the AF is in untrusted mode. Thus, according to some embodiments, when the AF is in untrusted mode, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S206:
S206: The 5GC network function entity 300a, 300b, 300c (such as NRF, BSF, or UDM) receives, from the NEF when the AF is in untrusted mode, registration of a mapping between the UE and the AF.

As will be further disclosed below with reference to actions <NUM>, <NUM>, <NUM> of <FIG>, the AF might itself register the mapping between the UE and the AF when the AF is in trusted mode. Thus, according to some embodiments, when the AF is in trusted mode, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S210:
S210: The 5GC network function entity 300a, 300b, 300c (such as NRF, BSF, or UDM) receives, from the AF when the AF is in trusted mode, registration of a mapping between the UE and the AF.

As will be further disclosed below with reference to actions <NUM>, <NUM>, <NUM> of <FIG>, the NRF might determine which NEF is serving the UE. Thus, according to some embodiments, when the 5GC network function entity 300a, 300b, 300c is the NRF, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) actions S212, S214:.

Alternatively, the NEF determines the mapping between the UE and the NEF and provides information of the mapping to the network function entity 300a, 300b, 300c (such as NRF, BSF, or UDM). Thus, according to some embodiments, the 5GC network function entity 300a, 300b, 300c is configured to perform (optional) action S216:
S216: The 5GC network function entity 300a, 300b, 300c receives registration of a mapping between the UE and the NEF from the NEF.

Next, three particular embodiments based on at least some of the above disclosed embodiments will be disclosed. In some of these embodiments, different alternatives are covered. In this respect, the notation Option <NUM>, Option <NUM>, and Option <NUM> is used to identify three different alternatives. Thus, when an action pertaining to Option <NUM> is performed, neither any action pertaining to Option <NUM> nor any action pertaining to Option <NUM> is performed, and vice versa. Thus, only the actions of one of Option <NUM>, Option <NUM>, and Option <NUM> are performed per alternative.

One particular embodiment for a registration procedure in the NRF of the NEF and the AF based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>.

According to this embodiment, the above disclosed 5GC network function entity 300a, 300b, 300c is an NRF 300a.

One particular embodiment for when the mapping between UE and AF instance is stored either in the NRF, the BSF or the UDM, for the AF being in untrusted mode and in trusted mode, respectively, based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>.

According to this embodiment, Option <NUM> corresponds to that the above disclosed 5GC network function entity 300a, 300b, 300c is an NRF 300a, Option <NUM>, corresponds to that the 5GC network function entity 300a, 300b, 300c is a BSF 300b, and Option <NUM> corresponds to that the 5GC network function entity 300a, 300b, 300c is a UDM entity 300c.

If the AF is in untrusted mode, actions <NUM> to <NUM> are performed.

One particular embodiment for when the mapping between UE and NEF instance is stored either in the NRF, the BSF or the UDM based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>. This particular embodiment only applies when the AF is in untrusted mode.

According to this embodiment, Option <NUM> corresponds to that the above disclosed 5GC network function entity 300a, 300b, 300c is a BSF 300b, Option <NUM>, corresponds to that the 5GC network function entity 300a, 300b, 300c is a UDM entity 300c, and Option <NUM> corresponds to that the 5GC network function entity 300a, 300b, 300c is an NRF 300a.

One particular embodiment for when the NWDAF entity discovers, for data collection, the NEF or AF serving the UE based on at least some of the above disclosed embodiments will now be disclosed in detail with reference to the signalling diagram of <FIG>.

In summary according to at least some of the herein disclosed embodiments, there has been presented mechanisms allowing the NWDAF to determine which NEF and AF instances are serving a specific UE for data collection purposes. The following alternatives have been disclosed: the UE-ID is registered in the NF profile of the NEF and AF in the NRF (i.e., the above disclosed 5GC network function entity 300a, 300b, 300c is an NRF 300a), or the mapping between UE and NEF or AF instance is registered in the BSF (i.e., the above disclosed 5GC network function entity 300a, 300b, 300c is a BSF 300b), or the mapping between UE and NEF or AF instance is registered in the UDM (i.e., the above disclosed 5GC network function entity 300a, 300b, 300c is a BSF 300c).

According to at least some of the herein disclosed embodiments, there has also been presented mechanisms for assigning a NEF instance to a UE. According to a first alternative, the NEF registers in NRF the UE-ID range that it handles. Then the NEF assigned to a certain UE-ID is selected based on this range by the NRF. According to a second alternative, the mapping between UE and NEF is stored in the network function entity 300a, 300b, 300b, such as either the NRF, the BSF, or the UDM. The NEF receives the first request related to a UE-ID from the AF and tries to retrieve from NRF, BSF or UDM the NEF instance that serves the UE. If there is no NEF assigned to the UE, the NRF might decides which NEF to assign the UE based on, for example, the NEF UE-ID range, App-IDs, NEF APIs the AF is interested to, and metrics that the AF indicates that it can provide for NWDAF data collection or NEF parameter provisioning procedures.

According to at least some of the herein disclosed embodiments, there has also been presented mechanisms for AF and NEF profile registration in the NRF. The NEF might register the UE-ID range that it will serve. If the AF is trusted the AF might registers its AF profile directly in the NRF. If the AF is untrusted the AF on-boards to the NEF and the NEF registers the AF profile in the NRF.

According to at least some of the herein disclosed embodiments, there has also been presented mechanisms for determining whether the AF is trusted (whereby NFs can communicate directly with the AF) or untrusted (whereby NFs communicate with the AF via the NEF). The NEF might determine whether the AF is trusted or untrusted. Information of whether the AF is trusted or untrusted is included in the AF profile in the NRF. If the AF is untrusted, the NRF responds with the corresponding NEF instance address in the AF discovery request.

<FIG> schematically illustrates, in terms of a number of functional units, the components of an NWDAF entity <NUM> according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1210a (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the NWDAF entity <NUM> to perform a set of operations, or actions, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the NWDAF entity <NUM> to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The NWDAF entity <NUM> may further comprise a communications interface <NUM> for communications with other entities, functions, nodes and devices of the communication network <NUM>. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the NWDAF entity <NUM> e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the NWDAF entity <NUM> are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of an NWDAF entity <NUM> according to an embodiment. The NWDAF entity <NUM> of <FIG> comprises a number of functional modules; a provide module 210a configured to perform action S102, and a receive module 210b configured to perform action S104. The NWDAF entity <NUM> of <FIG> may further comprise a number of optional functional modules, such as any of a receive module 210c configured to perform action S106, a provide module 210d configured to perform action S108, a receive module 210e configured to perform action S110, a provide module 210f configured to perform action S112, and a receive module 210fg configured to perform action S114.

In general terms, each functional module 210a-<NUM> may be implemented in hardware or in software. Preferably, one or more or all functional modules 210a-<NUM> may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and/or the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 210a-<NUM> and to execute these instructions, thereby performing any actions of the NWDAF entity <NUM> as disclosed herein.

<FIG> schematically illustrates, in terms of a number of functional units, the components of a 5GC network function entity 300a, 300b, 300c according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 1210b (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the 5GC network function entity 300a, 300b, 300c to perform a set of operations, or actions, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the 5GC network function entity 300a, 300b, 300c to perform the set of operations. Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed.

The 5GC network function entity 300a, 300b, 300c may further comprise a communications interface <NUM> for communications with other entities, functions, nodes and devices of the communication network <NUM>. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components.

The processing circuitry <NUM> controls the general operation of the 5GC network function entity 300a, 300b, 300c e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the 5GC network function entity 300a, 300b, 300c are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a 5GC network function entity 300a, 300b, 300c according to an embodiment. The 5GC network function entity 300a, 300b, 300c of <FIG> comprises a number of functional modules; a receive module 310i configured to perform action S218, and a provide module 310j configured to perform action S220. The 5GC network function entity 300a, 300b, 300c of <FIG> may further comprise a number of optional functional modules, such as any of a receive module 310a configured to perform action S202, a receive module 310b configured to perform action S204, a receive module 310c configured to perform action S206, a receive module 310d configured to perform action S208, a receive module 310e configured to perform action S210, a determine module 310f configured to perform action S212, a provide module <NUM> configured to perform action S214, and a receive module <NUM> configured to perform action S216.

In general terms, each functional module 310a-310j may be implemented in hardware or in software. Preferably, one or more or all functional modules 310a-310j may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and/or the storage medium <NUM>. The processing circuitry <NUM> may thus be arranged to from the storage medium <NUM> fetch instructions as provided by a functional module 310a-310j and to execute these instructions, thereby performing any actions of the 5GC network function entity 300a, 300b, 300c as disclosed herein.

The NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c may be provided as a standalone device or as a part of at least one further device. Alternatively, functionality of the NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c may be distributed between at least two devices, or nodes. In general terms, instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the cell than instructions that are not required to be performed in real time. Thus, a first portion of the instructions performed by the NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c may be executed in a first device, and a second portion of the instructions performed by the NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c may be executed. Hence, the methods according to the herein disclosed embodiments are suitable to be performed by an NWDAF entity <NUM> and/or the 5GC network function entity 300a, 300b, 300c residing in a cloud computational environment. Therefore, although a single processing circuitry <NUM>, <NUM> is illustrated in <FIG> the processing circuitry <NUM>, <NUM> may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 210a-<NUM>, 310a-310j of <FIG> and the computer programs 1220a, 1220b of <FIG>.

<FIG> shows one example of a computer program product 1210a, 1210b comprising computer readable means <NUM>. On this computer readable means <NUM>, a computer program 1220a can be stored, which computer program 1220a can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1220a and/or computer program product 1210a may thus provide means for performing any actions of the NWDAF entity <NUM> as herein disclosed. On this computer readable means <NUM>, a computer program 1220b can be stored, which computer program 1220b can cause the processing circuitry <NUM> and thereto operatively coupled entities and devices, such as the communications interface <NUM> and the storage medium <NUM>, to execute methods according to embodiments described herein. The computer program 1220b and/or computer program product 1210b may thus provide means for performing any actions of the 5GC network function entity 300a, 300b, 300c as herein disclosed.

In the example of <FIG>, the computer program product 1210a, 1210b is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 1210a, 1210b could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 1220a, 1220b is here schematically shown as a track on the depicted optical disk, the computer program 1220a, 1220b can be stored in any way which is suitable for the computer program product 1210a, 1210b.

Claim 1:
A method for discovering, for data collection, which network exposure function, NEF, or application function, AF, is serving a user equipment, UE, the method being performed by a network data analytics function, NWDAF, entity (<NUM>), the method comprising:
providing (S102), to a 5GC network function entity (300a, 300b, 300c), a query of which NEF or AF is serving the UE, wherein the query comprises an ID of the UE; characterized by
receiving (S104), from the 5GC network function entity (300a, 300b, 300c), a response comprising an ID of the NEF or the AF when there is a NEF or AF instance stored in the 5GC network function entity (300a, 300b, 300c) for the UE; and
receiving (S106), from a network repository function, NRF (300a), an address to the NEF or the AF, wherein the address to the AF is received when the AF is in trusted mode, and wherein the address to the NEF is received when the AF is in untrusted mode.