WO2022033659A1

WO2022033659A1 - Apparatus, methods, and computer programs

Info

Publication number: WO2022033659A1
Application number: PCT/EP2020/072447
Authority: WO
Inventors: Yannick Lair; Anja Jerichow; Saurabh Khare
Original assignee: Nokia Technologies Oy
Priority date: 2020-08-11
Filing date: 2020-08-11
Publication date: 2022-02-17

Abstract

There is provided an apparatus. The apparatus comprises means for selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met. The condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

Description

APPARATUS, METHODS, AND COMPUTER PROGRAMS

Field

The present disclosure relates to apparatus, methods, and computer programs, and in particular but not exclusively to apparatus, methods and computer programs for handling data for analytics.

Background

A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, access nodes and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and/or content data and so on. Content may be multicast or uni-cast to communication devices.

A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user is often referred to as user equipment (UE) or user device. The communication device may access a carrier provided by an access node, and transmit and/or receive communications on the carrier.

The communication system and associated devices typically operate in accordance with a required standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio). Another example of an architecture that is known is the long-term evolution (LTE) or the Universal Mobile Telecommunications System (UMTS) radioaccess technology. Another example communication system is so called 5G radio or new radio (NR) access technology. Within communication systems, data is collected from entities (such as UEs) in order to analyse that data for understanding and improving system performance.

Statement of invention

According to a first aspect there is provided an apparatus comprising means for performing: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to some examples, the threshold quantity comprises a number of user equipment supporting provision of data for analytics.

According to some examples, the threshold quantity comprises a ratio of user equipment supporting provision of data for analytics to a total number of user equipment.

According to some examples, the threshold quantity comprises a ratio of user equipment supporting provision of data for analytics to user equipment not supporting provision of data for analytics .

According to some examples, the ratio is expressed as a percentage.

According to some examples, the selectively performing comprises stopping the collection of user equipment data for analytics or determining not to start the collection of user equipment data for analytics, when it is determined that the condition is not met.

According to some examples, the selectively performing comprises starting collection of user equipment data for analytics or continuing collection of user equipment data for analytics when it is determined that the condition is met.

According to some examples, the means are further configured to subscribe to another apparatus to periodically receive updates of the information of the threshold quantity of user equipment. According to some examples, the means are further configured to perform obtaining information of the threshold quantity of user equipment from the another apparatus.

According to some examples, the means are further configured to receive an update from the another apparatus when the condition is met if the condition was previously not being met, and the means are further configured to receive an update from the another apparatus when the condition is not being met if the condition was previously being met.

According to some examples the means are further configured to notify the another apparatus of the condition.

According to some examples, the means are further configured to perform sending one or more subscription filters to the another apparatus, the one or more subscription filters comprising one or more of: a user equipment vendor specific filter; a roaming specific filter; a geographical area filter; a network slice filter.

According to some examples, the means are further configured to perform sending a request to the user equipment for the data for analytics, the request comprising information of a type of data for analytics to be collected.

According to some examples, the means are further configured to perform sending a request to the user equipment to stop collection of data for analytics, the request comprising information of a type of data for analytics to be stopped to be collected.

According to some examples, the another apparatus comprises any one of: an access and mobility management function; a session management function; a unified data management function; a unified data repository function.

According to some examples, the apparatus comprises a network data analytics function.

According to some examples, the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus. According to a second aspect there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to a third aspect there is provided an apparatus comprising: circuitry for selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to a fourth aspect there is provided a method comprising selectively performing collection of user equipment data for analytics based on a determination by an apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to some examples, the ratio is expressed as a percentage.

According to some examples, the selectively performing comprises stopping the collection of user equipment data for analytics or determining not to start the collection of user equipment data for analytics, when it is determined that the condition is not met. According to some examples, the selectively performing comprises starting collection of user equipment data for analytics or continuing collection of user equipment data for analytics when it is determined that the condition is met.

According to some examples, the method comprises subscribing to another apparatus to periodically receive updates of the information of the threshold quantity of user equipment.

According to some examples, the method comprises obtaining information of the threshold quantity of user equipment from the another apparatus.

According to some examples, the method comprises receiving an update from the another apparatus when the condition is met if the condition was previously not being met, and the method comprises receiving an update from the another apparatus when the condition is not being met if the condition was previously being met.

According to some examples the method comprises notifying the another apparatus of the condition.

According to some examples, the method comprises sending one or more subscription filters to the another apparatus, the one or more subscription filters comprising one or more of: a user equipment vendor specific filter; a roaming specific filter; a geographical area filter; a network slice filter.

According to some examples, the method comprises sending a request to the user equipment for the data for analytics, the request comprising information of a type of data for analytics to be collected.

According to some examples, the method comprises sending a request to the user equipment to stop collection of data for analytics, the request comprising information of a type of data for analytics to be stopped to be collected.

According to some examples, the apparatus comprises a network data analytics function. According to a fifth aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to a sixth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: selectively performing collection of user equipment data for analytics based on a determination by an apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to a seventh aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to an eighth aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: selectively performing collection of user equipment data for analytics based on a determination by an apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

According to a ninth aspect there is provided an apparatus comprising means for performing: retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to some examples, the means are further configured to perform collection of data for analytics from one or more of the one or more user equipment based on the retrieved information.

According to some examples, the means are further configured to specify one or more user equipment by providing a subscription permanent identifier or subscription permanent identifier range to the another apparatus. According to some examples, the another apparatus comprises any one of: an access and mobility management function; a session management function; a unified data management function; a unified data repository function.

According to some examples, the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

According to a tenth aspect there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to an eleventh aspect there is provided an apparatus comprising: circuitry for retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to a twelfth aspect there is provided a method comprising: retrieving by an apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to some examples, the method comprises performing collection of data for analytics from one or more of the one or more user equipment based on the retrieved information.

According to some examples, the method comprises specifying one or more user equipment by providing a subscription permanent identifier or subscription permanent identifier range to the another apparatus.

According to some examples, the another apparatus comprises any one of: an access and mobility management function; a session management function; a unified data management function; a unified data repository function. According to some examples, the apparatus comprises a network data analytics function.

According to a thirteenth aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: retrieving by the apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to a fourteenth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: retrieving by an apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to a fifteenth aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: retrieving by the apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to a sixteenth aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: retrieving by an apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

According to a seventeenth aspect there is provided an apparatus comprising means for performing: sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to some examples, the type information comprises environmental information, the environmental information comprising one or more of: location information of the apparatus; mobility information of the apparatus; battery level information of the apparatus.

According to some examples, the means is further configured to perform sending abstraction level information to the another apparatus, wherein the abstraction level information indicates whether the data for analytics that the apparatus makes available is raw data or pre-processed data. According to some examples, the means are further configured to perform updating the another apparatus in response to a change of capability at the apparatus.

According to some examples, the apparatus comprises a user equipment.

According to some examples, the another apparatus comprises one of: an access and mobility management function; a session management function.

According to an eighteenth aspect there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a nineteenth aspect there is provided an apparatus comprising: circuitry for sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and circuitry for sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a twentieth aspect there is provided a method comprising: sending, from an apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to some examples, the type information comprises environmental information, the environmental information comprising one or more of: location information of the apparatus; mobility information of the apparatus; battery level information of the apparatus. According to some examples, the method comprises sending abstraction level information to the another apparatus, wherein the abstraction level information indicates whether the data for analytics that the apparatus makes available is raw data or pre-processed data.

According to some examples, the method comprises updating the another apparatus in response to a change of capability at the apparatus.

According to some examples, the apparatus comprises a user equipment.

According to a twenty first aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: sending, from the apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a twenty second aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: sending, from an apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a twenty third aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: sending, from the apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a twenty fourth aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: sending, from an apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

According to a twenty fifth aspect there is provided an apparatus comprising means for performing: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus.

According to an example, the another apparatus comprises one of: a network data analytics function; a unified data management function; a unified data repository; an unstructured data storage function.

According to an example, the apparatus comprises an access and mobility management function.

According to an example, the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

According to a twenty sixth aspect there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus.

According to a twenty seventh aspect there is provided an apparatus comprising: circuitry for receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; circuitry for storing the information at the apparatus; and circuitry for making the information available to another apparatus.

According to a twenty eighth aspect there is provided a method comprising receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at an apparatus; and making the information available to another apparatus.

According to some examples, the another apparatus comprises one of: a network data analytics function; a unified data management function; a unified data repository; an unstructured data storage function.

According to a twenty ninth aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus.

According to a thirtieth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at an apparatus; and making the information available to another apparatus.

According to a thirty first aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus.

According to a thirty second aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus. In the above, many different aspects have been described. It should be appreciated that further aspects may be provided by the combination of any two or more of the aspects described above.

Various other aspects are also described in the following detailed description and in the attached claims.

Brief

Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

Figure 1 shows a schematic representation of a 5G system;

Figures 2A and 2B schematically show systems comprising a mixture of supporting and non-supporting UEs;

Figure 3 is a signalling diagram according to an example embodiment;

Figure 4 is a signalling diagram according to an example embodiment;

Figure 5 is a signalling diagram according to an example embodiment;

Figure 6 schematically shows a control apparatus according to an example;

Figure 7 schematically shows a user equipment according to an example embodiment;

Figures 8 to 11 are flow charts of methods according to example embodiments;

Figure 12 shows a schematic representation of a non-volatile memory medium storing instructions which when executed by a processor allow a processor to perform one or more of the steps of the methods of some embodiments.

Detailed description

In the following, certain embodiments are explained with reference to mobile communication devices capable of communication via a wireless cellular system and mobile communication systems serving such mobile communication devices. Before explaining the exemplifying embodiments in detail, certain general principles of a 5G wireless communication system are briefly explained with reference to Figure 1.

Figure 1 shows a schematic representation of a 5G system (5GS) 100. The 5GS may comprise a user equipment (UE) 102 (which may also be referred to as a communication device or a terminal), a 5G radio access network (5G RAN) 104, a 5G core network (5GC) 106, one or more application functions (AF) 108 and one or more data networks (DN) 110.

The 5G RAN may comprise one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. The 5G RAN may comprise one or more access nodes.

The 5GC 106 may comprise one or more access management functions (AMF) 112, one or more session management functions (SMF) 114, one or more authentication server functions (ALISF) 116, one or more unified data management (UDM) functions 118, one or more user plane functions (UPF) 120, one or more unified data repository (UDR) functions 122 and/or one or more network exposure functions (NEF) 124.

The 5GC 106 also comprises a network data analytics function (NWDAF) 126. The NWDAF is responsible for providing network analytics information upon request from one or more network functions or apparatus within the network. Network functions can also subscribe to the NWDAF 126 to receive information therefrom. Accordingly, the NWDAF 126 is also configured to receive and store network information received from one or more network functions or apparatus within the network.

UE driven analytics (i.e. the collection of data from UEs to obtain information for analytics) has so far focused on which type of data can be provided by the UE, and on procedures to transfer the data from the UE to the network (e.g. via non-access- stratum (NAS); via user plane; at application function (AF) level etc.)). Thus far, attention has not been paid to when such data needs to be collected and under what conditions the data should be collected.

More particularly, the present application has identified that it is unclear whether UE vendors will implement functionality of enabling UEs to provide UE data to the network for data analytics. It may not be possible to force UE vendors to implement such a feature. It is therefore possible that there will be an inconsistent level of functionality between UEs. Moreover, there is a lack of clarity of when data collection from a UE / data provision by a UE will be triggered. There has so far been an assumption that this will be triggered by the UE, possibly based on some configuration, but this is not mandated.

Thus, the present application identifies that there may be difficulties in understanding how many UEs are available for providing information of data for analytics within a group, or within a location area, a network, or a network slice. If an NWDAF would like to build analytics on a population of UEs in e.g. a geographical area (e.g. a list of TAIs, or a list of cells) or in a network slice, it may not be worthwhile triggering data collection if the number of UEs supporting the functionality is too small in that area or slice, as the analytics obtained and/or built by NWDAF may not be representative of the larger group of UEs in that area or slice. See for example Figure 2A which shows by way of example an area, Area 1 , in which only two out of twelve UEs support the provision of data for data analytics. On the other hand, knowledge that there are many UEs to collect data from in an area or a slice would be a good reason for NWDAF or other entity in the network to trigger data collection to build analytics related to that area or slice. See for example Figure 2B which shows by way of example an area, Area 2, in which ten out of seventeen UEs support the provision of data for data analytics.

In view of this, the present application proposes a method (and accompanying apparatus and computer programs) where collection of data for analytics from user equipment is selectively performed, for example by an NWDAF. By “selectively performed” is meant that the collection of data for analytics is performed if a certain condition or criteria is met, and collection of data for analytics is not performed if the certain condition is not met. In example embodiments the certain condition comprises a threshold quantity of user equipment that support the provision of data for analytics. By “support” is meant that the UE makes available at least some information suitable for use in data analytics (e.g. by the NWDAF).

The data for analytics that is provided by a UE may be raw-data or pre- processed data. Where the data for analytics provided by the UE is pre-processed data, the data may be, for example, statistics information or prediction information.

In some examples the data for analytics that is provided by the user equipment comprises any combination of one or more of location information (e.g. TAI, cell) of the user equipment; expected trajectory (i.e. movement) of the user equipment; type of mobility (e.g. pedestrian, slow moving vehicular, fast moving vehicular) of the user equipment; identities of applications running in the user equipment; network slices used by the user equipment.

In some examples the threshold quantity of UEs comprises an absolute number of UEs that support the provision of data for analytics, regardless of a number of UEs that may not support the provision of data for analytics. For example, data collection may be performed if ten or more UEs support collection of data for analytics.

In some examples, the threshold quantity comprises a ratio of user equipment supporting provision of data for analytics to a total number of user equipment.

In some examples the threshold quantity of UEs comprises a ratio of user equipment supporting provision of data for analytics to user equipment not supporting provision of data for analytics.

By way of example only the threshold ratio may be 1 :2. The threshold ratio may also be expressed as a percentage e.g. 50%. In some examples, the threshold ratio is configurable, for example in the NWDAF. In some examples the threshold ratio may be provided by the NWDAF to the AMF as a parameter. Therefore, in some examples it may be considered that the threshold ratio is configured by the NWDAF. Therefore in some examples there is a threshold configured in the NWDAF to allow configuring of the NWDAF (e.g. via 0AM) so that NWDAF knows from which ratio it can trigger data collection, and there is a threshold provided by NWDAF to AMF defining when NWDAF requests to be notified by AMF about the ratio. A “direction” or “trend” may also be provided (e.g. by the NWDAF to AMF) such as “below”, “above”, or “crossed”, allowing the NWDAF to request to be notified by AMF when the ratio goes below, above or crosses the threshold respectively, and/or simply if the ratio increases or decreases, and possibly by a specific amount. For example, the NWDAF may ask to be notified when the ratio increases by e.g. 10%, not just when the ratio increases by any amount (which could mean the ratio just increases by e.g; 0.1 % and this would not be a good reason to notify NWDAF). In other words, the NWDAF may request to be notified by the AMF when a trend of the ratio of UEs that support provision of data for analytics moves in a certain direction. In some examples, the NWDAF may request to be notified by the AMF when a trend of the ratio of UEs that support provision of data for analytics moves in a certain direction by a specific amount or by more than a specific amount.

In some examples the method is carried out based on a geographical area (e.g. a list of TAIs, or a list of cells) or network slice basis. For example, the NWDAF may consider whether the condition is met on a geographical area (e.g. a list of TAIs, or a list of cells) or network slice basis.

Some example embodiments will now be described with respect to Figures 3 to 5.

Figure 3 shows an example embodiment where UE 302 indicates which type of data it can provide to the network for data analytics. In some examples this is carried out via NAS signalling. This is shown at S1 where UE 302 sends a registration request to AMF 312. The registration request includes UE data for analytics capability information (in other words, whether the UE supports sharing of data for analytics). In examples the capability information comprises information of a type of data. For example, the type of data could be application level data such as application MOS (mean opinion score) and/or application identifiers. The type of data may also comprise environmental data, such as positioning or location of the UE, mobility of the UE etc.

The registration request may also comprise an abstraction level for the data. For example, information of abstraction level may comprise information of whether the data is raw data or pre-processed data. Pre-processed data may comprise, for example, statistics or predictions or analytics. The abstraction level may be provided per type of data.

The information at S1 could be provided, for example, as part of 5GMM Capability in a registration request message. Or the information at S1 could be standalone Analytics Capability information in the registration request message.

The UE data for Analytics Capability is dynamic in some examples. For example, the capability of the UE to provide data for analytics may be dependent upon one or more parameters. For example, a parameter could be battery level, signal quality, location etc. For example if a UE previously indicated its capability to provide data to the network for analytics, and if the battery level of the UE at some point drops too low, the UE could update its registration and inform the AMF 312 that the UE 302 is no longer supporting data collection. That is, it may be considered that the user equipment 302 is configured to update another apparatus (such as AMF 312) in response to a change of capability at the user equipment 302.

At S2 the AMF 312 receives the UE data for Analytics Capability information from the UE 302, and stores the UE data for Analytics Capability information in UE context. By “UE data for Analytics Capability information” is meant information indicating a capability of a UE to provide data for analytics.

At S3, the AMF 312 sends a registration request message to the UDM 318. In some examples, the registration request comprises a Nudm_UECM_Registration Request. In examples, the registration request comprises the UE data for analytics capability information. The registration request at S3 may comprise a fresh registration or a registration update.

At S4, the UE data for analytics capability information is then sent to and stored at the UDR 319.

As shown, a registration response message is then sent from UDM 318 to AMF 312. As shown, a registration accept message is sent from AMF 312 to UE 302.

Therefore it will be understood that the AMF may be configured to receive, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available. The AMF may store this information and make the information available to another apparatus. The another apparatus may be, for example, any one or more of: an NWDAF; a UDM; a UDR; an unstructured data storage function (UDSF). For example, the AMF may store the information in UDSF for use by the AMF or another AMF later on.

Figure 4 is a signalling diagram of an example embodiment, which shows in more detail the processes carried-out by the NWDAF, in this example NWDAF 426.

Figure 4 considers a process in two “areas”, being Area 1 430 and Area 2 432. The areas could be, for example, different geographical areas or different network slices.

As shown in Figure 4, Area 1 430 comprises UEs 402 (“UE-1”) and 403 (“UE- 2”), and AMF 412 (“AMF-A1”). Area 2 432 comprises UEs 401 (“UE-X”) and 405 (“UE- Y”), and AMF 413 (“AMF-A2”). In the example of Figure 4, both Area 1 and Area 2 are served by the same NWDAF 426. In other example embodiments, Areas 1 and 2 may be served by different NWDAFs.

For Area 1 and Area 2, S1 and S2 are analogous to S1 and S2 of Figure 3. That is, the UEs 402 and 403 for Area 1 (UEs 401 and 405 for Area 2) send registration requests to AMF 412 (AMF 413 for Area 2) at S1. The registration requests may comprise UE data for analytics capability information including type of data and an abstraction level for the data. At S2, the AMF 412 (AMF 413 for Area 2) stores UE data for analytics capability information in the UE context. S3 and S4 of Figure 3 are also equally applicable to Figure 4. Therefore S5 to S7 are described in more detail below with respect to Figure 4. Within Figure 4, four main “options” or “behaviours” for S5 to S7 are discussed, which for the purpose of explanation are shown as “Option 1”, “Option 2”, “Option 3” and “Option 4” in Figure 4. These options show different NWDAF behaviours depending on the information received from the AMFs.

With respect to the example embodiment of Figure 4, the AMF(s) provide a service that can indicate a number or quantity of UEs supporting data for analytics. This service may be considered an exposure service. In some examples, an event ID for the AMF exposure service may be “number of UEs supporting data for analytics” or similar.

In some examples, the AMF(s) comprise filter functionality. That is, the AMF(s) may in some examples be configured to make a filtered set of information available, for example based on subscription filters defined by another apparatus such as NWDAF. In some examples, the filters comprise one or more of: an area of interest (e.g. list of tracking area identities (TAIs)); a network slice; a type of data (e.g. environmental data); a group of users. Alternatively, a new service different from AMF exposure service could be defined specifically for retrieving information on UE capabilities regarding analytics.

“Option 1”

As shown at S5, the NWDAF 426 sends a message to the AMF 412 regarding UE data for analytics that the NWDAF 426 would like to obtain. In the example of Figure 4 the message at S5 comprises an Namf_EventExposure_Subscribe Request message. Therefore, in some examples, the message at S5 may be considered a subscription request message. In other words it may be considered that the NWDAF 426 subscribes to information from the AMF 412. More specifically, it may be considered that the NWDAF 426 subscribes to the event ID “number of UEs supporting data for analytics”. In the example of S5 in Figure 4, the information that the NWDAF 426 subscribes to comprises: number of UEs supporting data for analytics; data type; level of abstraction; ratio with total number of UEs; threshold. Therefore, in this example, the AMF is asked to count the number of UEs supporting the functionality compared to the total number of UEs, and then the threshold informs the AMF when to notify the NWDAF, (e.g. only when the ratio reaches the threshold will the AMF notify the NWDAF at S6, or when the ratio crosses the threshold will the AMF notify the NWDAF at S6). Therefore, in some examples, S6 occurs when a trend of the ratio of UEs that support provision of data for analytics moves in a certain direction, as previously described.

In some examples the NWDAF 426 subscribes to the above event from AMF 412, along with an existing event of “number of UEs located in an area”. Therefore, in some examples it is considered that the NWDAF 426 subscribes to the AMF 412 for information of: number of UEs located in an area; and number of UEs in that area that support provision of UE data for analytics. This allows NWDAF 426 to compute a ratio between UEs supporting the feature and total UEs in the area.

In some examples, thresholds can be provided or stipulated by the NWDAF 426 so that AMF 412 notifies when certain criteria or conditions are met. For example, a condition could be e.g. more than 50% of the UEs can provide analytics; and/or more than 40% of the UEs can provide predictions on their environmental status.

In some examples, the NWDAF 426 can subscribe to the event with a filter indication for TAC (Type Allocation Code). This allows the NWDAF 426 to discriminate between different device manufacturers. This functionality could be used, for example, if a UE vendor would like to collect data from its own devices and conduct analysis via NWDAF. In some examples, a service operator could sell device specific information to the device manufacturer(s).

Similarly, in some examples the NWDAF 426 could subscribe to specific roaming devices. For example, the NWDAF 426 could subscribe to all UEs with a subscription for a specific public land mobile network (PLMN). This enables the NWDAF 426 to retrieve information from roaming devices of a specific operator. This information could then be reported to the roaming partner or used to improve the roaming service.

Therefore, at S6 a notification is sent from AMF 412 to NWDAF 426. Using notifications from the AMF 412, the NWDAF 426 can determine how many UEs in e.g. an area or a slice can provide data for analytics. For example, the number of UEs determined may comprise a ratio compared to a total number of UEs in the area or in the slice. The NWDAF 426 can then determine whether it is worth triggering data collection from the UEs that support data collection. In some examples the determination carried out by the NWDAF 426 of whether it is worth performing data collection not only considers the number of UEs that support data collection but also the type(s) of information that those UEs make available for data analytics. Then the NWDAF 426 can determine whether it is worth performing data collection for the type of data analytics the NWDAF wants to build. In some examples the AMF 412 may also provide UE identities to NWDAF 426. Then the NWDAF 426 knows which UEs to contact, should the NWDAF 426 need to trigger data collection from these UEs. In the example of Figure 4, the notification at S6 comprises the following information: number of UEs supporting data for analytics; list of UEs = UE-1 (i.e. UE 401 ), UE-2 (i.e. UE 405); ratio = 50%.

At S7, if or when it is determined by the NWDAF 426 that the condition has been met (e.g. the number of UEs supporting provision of data for analytics meets a required threshold), then the NWDAF 426 may decide to trigger data collection from the UEs in Area 1 430. For example, the NWDAF 426 may send a request to the UEs for data collection. The request sent to the UEs may specify the type of data to be collected. This could be done at NAS level for example, but could also be done on the user plane. The NWDAF 426 could also decide to stop data collection for one or more UEs at any point. For example, the NWDAF 426 could decide to stop collecting data from the UEs if, for example, the number of UEs which can provide data in an area is no longer significant enough. Therefore, in some examples it may be considered that the NWDAF 426 is configured to dynamically monitor whether to continue data monitoring. In some examples the NWDAF 426 may decide whether to continue data collection based on configuration (e.g. operator configuration) and/or operator policies.

“Option 2”

In Option 2, at S5 the NWDAF 426 sends a subscription message to AMF 413 in Area 2. The subscription message in this example is of the form Namf_EventExposure_Subscribe Request (number of UEs supporting data for analytics, data type, level of abstraction, ratio with total number of UEs). In this example the AMF asks to be notified periodically about the ratio.

At S6, the AMF 413 sends a notification message to NWDAF 426 in response. In this example, the notification at S6 informs the NWDAF 426 that 15% of UEs in Area 2 432 support provision of data for analytics.

At S7, based on the notification from AMF 413, the NWDAF 426 decides whether to start collection of data for analytics with the UEs in Area 2 432. In the example of Option 2, at S7 the NWDAF 426 decides not to start collection of data for analytics with the UEs in Area 2 432. “Option 3”

S6 and S7 of Option 3 are alternatives of S6 and S7 of option 1 .

In Option 3, at S6 the notification from AMF 412 to NWDAF 426 informs the NWDAF 426 that 20% of UEs in Area 1 430 support provision of information for data analytics.

In response to receiving this information, at S7 the NWDAF 426 determines not to perform data collection with UEs in Area 1 430, or to stop performing data collection with UEs in Area 1 if data collection was ongoing.

“Option 4”

S6 and S7 of option 4 are alternatives of S6 and S7 of option 2.

In option 4, at S6 the notification from AMF-2 413 to NWDAF 426 informs the NWDAF 426 that 65% of UEs in Area 2 support data collection.

In response, at S7, NWDAF 426 determines to start data collection with UEs in Area 2.

It will be understood that “Option 1”, “Option 2”, “Option 3” and “Option 4” are explained separately for ease of understanding and conciseness. However, it will be understood that they are not strict alternatives except where clearly stated. For example, aspects explained in detail with respect to Option 1 (e.g. how the NWDAF subscribes to the AMF) are equally applicable to Options 2 to 4, but are not repeated for conciseness. It will also be understood that, for example, each area (e.g. Area 1 and Area 2) may of course comprise more than two UEs in practice. It will also be understood that there could be more than two areas.

Some further functionality of the NWDAF is now explained with respect to Figure 5, which builds on Figures 3 and 4.

Figure 5 shows a UE 502, AMF 512, UDM 518, UDR 519, and NWDAF 526.

S1 to S4 are analogous to S1 to S4 in Figure 3. Albeit not shown in Figure 5 for conciseness, S6 and S7 (and the various options thereof) of Figure 4 may precede S8 which is shown in Figure 5.

In some example embodiments, the NWDAF 526 (or other application function (AF) or network function (NF)) identifies whether a UE supports analytics capability or not. In the example of Figure 5, the NWDAF 526 is required to collect data from one or more UEs. The one or more UEs to collect data from may be identified by a Subscription Permanent Identifier (SUPI) or SUPI range. However, the NWDAF 526 is not aware of UE(s) capability to provide data for analytics. In other words, when NWDAF 526 wants to collect data, the information of UE(s) capability to provide data for analytics may not be known to NWDAF 526, in which case the NWDAF can retrieve the information of UE(s) capability to provide data for analytics from UDM 518. Based on the information retrieved from the UDM 518, the NWDAF 526 can determine whether requested SUPI or SUPI range support provision of data for analytics or not.

This is shown at S8 of Figure 5 - “NWDAF is required to collect data from the UE, but capability [of the UE] is unknown”. As shown, this is resolved by the NWDAF 526 sending a request to the UDM 518. In the example of Figure 5 the request comprises an Nudm_UECM_Get Request (AMF Registration data). The UDM 518 responds with the UE data for analytics capability information. In the example, the response comprises Nudm_UECM_Get Response [UE data for analytics capability information], UE data for analytics capability information may also be part of AMF Registration data in Nudm_UECM_Get Response.

Considering that a UE (e.g. UE 502) can change its capability over time, the NWDAF 526 can subscribe to UDM 518 to get a notification when UE 502 performs any of: starts supporting data reporting; stops supporting data reporting. This helps NWDAF/NF/AF to schedule a data collection from UE.

As shown at S9, NWDAF 526 can collect data from the UE if the UE supports the capability.

In some examples, for slice specific UE information, NWDAF could send a similar subscription to an SMF event exposure service instead of AMF event exposure service.

For AMF_EventExposure or SMF_EventExposure, there is the possibility that the NWDAF is notified on a periodic basis of the number of UEs that support provision of data for analytics or the ratio of UEs that support provision of data for analytics, with or without a threshold provided by the NWDAF.

For AMF_EventExposure or SMF_EventExposure, in some examples the NWDAF is notified when the number of UEs that support provision of data for analytics or the ratio of UEs that support provision of data for analytics increases or decreases by a specific amount. According to some examples, counting of UEs that support provision of data for analytics can be useful for NWDAF to decide to stop collecting data from the UEs.

According to some examples, any NF (in addition to NWDAF) can utilize the above-described methods to optimize data collection from UE.

It will be appreciated that example embodiments may help avoid blind and costly collection of data from UEs, which may eventually be of no use for NWDAF and the network if the number of UEs to collect data from is not sufficiently significant and not representative of the total number of UEs.

Moreover, instead of relying on UEs to autonomously send data to the network, the network controls, e.g. on an area basis or on a slice basis, whether to trigger data collection from the UEs, when the NWDAF considers that there are enough UEs in the area or the slice to collect data from and build relevant analytics from. The NWDAF can also control when to stop such data collection from UEs if/when the number of UEs becomes too small or too insignificant.

Figure 6 shows an example of a control apparatus for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, gNB, a central unit of a cloud architecture or a node of a core network such as an MME or S-GW, a scheduling entity such as a spectrum management entity, or a server or host, for example an apparatus hosting an NWDAF, AMF, SMF, UDM, UDR etc. The control apparatus may be integrated with or external to a node or module of a core network or RAN. In some embodiments, base stations comprise a separate control apparatus unit or module. In other embodiments, the control apparatus can be another network element such as a radio network controller or a spectrum controller. The control apparatus 600 can be arranged to provide control on communications in the service area of the system. The apparatus 600 comprises at least one memory 601 , at least one data processing unit 602, 603 and an input/output interface 604. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the apparatus. The receiver and/or the transmitter may be implemented as a radio front end or a remote radio head. For example the control apparatus 600 or processor 601 can be configured to execute an appropriate software code to provide the control functions. A possible wireless communication device will now be described in more detail with reference to Figure 7 showing a schematic, partially sectioned view of a communication device 700. Such a communication device is often referred to as user equipment (UE) or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or a tablet provided with wireless communication capabilities, or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email), text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.

A wireless communication device may be for example a mobile device, that is, a device not fixed to a particular location, or it may be a stationary device. The wireless device may need human interaction for communication, or may not need human interaction for communication. In the present teachings the terms UE or “user” are used to refer to any type of wireless communication device.

The wireless device 700 may receive signals over an air or radio interface 707 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 7 transceiver apparatus is designated schematically by block 706. The transceiver apparatus 706 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device.

A wireless device is typically provided with at least one data processing entity 701 , at least one memory 702 and other possible components 703 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 704. The user may control the operation of the wireless device by means of a suitable user interface such as key pad 705, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 708, a speaker and a microphone can be also provided. Furthermore, a wireless communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.

Figures 8 to 10 are flow charts showing methods according to some example embodiments.

Figure 8 is a flow chart of a method according to an example. The flow chart of Figure 8 is viewed from the perspective of an apparatus. For example, the apparatus may be an NWDAF.

As shown at S1 , the method comprises selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met. According to examples, the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

Figure 9 is a flow chart of a method according to an example. The flow chart of Figure 9 is viewed from the perspective of an apparatus. For example, the apparatus may be an NWDAF.

As shown at S1 , the method comprises retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

Figure 10 is a flow chart of a method according to an example. The flow chart of Figure 10 is viewed from the perspective of an apparatus. For example, the apparatus may be a UE.

As shown at S1 , the method comprises sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus.

At S2, the method comprises sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

Figure 11 is a flow chart of a method according to an example. The flow chart of Figure 11 is viewed from the perspective of an apparatus. For example, the apparatus may be an AMF. As shown at S1 , the method comprises

Figure 12 shows shows a schematic representation of non-volatile memory media 1200a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 1200b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 1202 which when executed by a processor allow the processor to perform one or more of the steps of the methods of Figures 8 to 11 .

The embodiments may thus vary within the scope of the attached claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures, e.g., as in Figures 6 and 7, may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, 1 microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi-core processor architecture, as non-limiting examples.

Alternatively or additionally some embodiments may be implemented using circuitry. The circuitry may be configured to perform one or more of the functions and/or method steps previously described. That circuitry may be provided in the base station and/or in the communications device.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analogue and/or digital circuitry);

(b) combinations of hardware circuits and software, such as:

(i) a combination of analogue and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and

(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example integrated device.

The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of some embodiments. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined in the appended claims.

Claims

1 . An apparatus comprising means for performing: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

2. An apparatus according to claim 1 , wherein the threshold quantity comprises a number of user equipment supporting provision of data for analytics.

3. An apparatus according to claim 1 , wherein the threshold quantity comprises a ratio of user equipment supporting provision of data for analytics to a total number of user equipment.

4. An apparatus according to claim 1 , wherein the threshold quantity comprises a ratio of user equipment supporting provision of data for analytics to user equipment not supporting provision of data for analytics .

5. An apparatus according to claim 3 or claim 4, wherein the ratio is expressed as a percentage.

6. An apparatus according to any of claims 1 to 5, wherein the selectively performing comprises stopping the collection of user equipment data for analytics or determining not to start the collection of user equipment data for analytics, when it is determined that the condition is not met.

7. An apparatus according to any of claims 1 to 5, wherein the selectively performing comprises starting collection of user equipment data for analytics or continuing collection of user equipment data for analytics when it is determined that the condition is met.

8. An apparatus according to any of claims 1 to 7, wherein the means are further configured to subscribe to another apparatus to periodically receive updates of the information of the threshold quantity of user equipment.

9. An apparatus according to claim 8, wherein the means are further configured to perform obtaining information of the threshold quantity of user equipment from the another apparatus.

10. An apparatus according to claim 8 or claim 9, wherein the means are further configured to receive an update from the another apparatus when the condition is met if the condition was previously not being met, and the means are further configured to receive an update from the another apparatus when the condition is not being met if the condition was previously being met.

11. An apparatus according to any of claims 8 to10, wherein the means are further configured to perform sending one or more subscription filters to the another apparatus, the one or more subscription filters comprising one or more of: a user equipment vendor specific filter; a roaming specific filter; a geographical area filter; a network slice filter.

12. An apparatus according to any of claims 1 to 11 , wherein the means are further configured to perform sending a request to the user equipment for the data for analytics, the request comprising information of a type of data for analytics to be collected.

13. An apparatus according to any of claims 1 to 12, wherein the means are further configured to perform sending a request to the user equipment to stop collection of data for analytics, the request comprising information of a type of data for analytics to be stopped to be collected.

14. An apparatus comprising means for performing: retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

15. An apparatus according to claim 14, wherein the means are further configured to perform collection of data for analytics from one or more of the one or more user equipment based on the retrieved information.

16. An apparatus according to claim 14 or claim 15, wherein the means are further configured to specify one or more user equipment by providing a subscription permanent identifier or subscription permanent identifier range to the another apparatus.

17. An apparatus according to any of claims 1 to 16, wherein the another apparatus comprises any one of: an access and mobility management function; a session management function; a unified data management function; a unified data repository function.

18. An apparatus according to any of claims 1 to 17, wherein the apparatus comprises a network data analytics function.

19. An apparatus according to any of claims 1 to 18, wherein the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

20. An apparatus comprising means for performing: sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

21. An apparatus according to claim 20, wherein the type information comprises environmental information, the environmental information comprising one or more of: location information of the apparatus; mobility information of the apparatus; battery level information of the apparatus.

22. An apparatus according to claim 20 or claim 21 , wherein means is further configured to perform sending abstraction level information to the another apparatus, wherein the abstraction level information indicates whether the data for analytics that the apparatus makes available is raw data or pre-processed data.

23. An apparatus according to any of claims 20 to 22, wherein the means are further configured to perform updating the another apparatus in response to a change of capability at the apparatus.

24. An apparatus according to any of claims 20 to 23, wherein the apparatus comprises a user equipment.

25. An apparatus according to any of claims 20 to 24, wherein the another apparatus comprises one of: an access and mobility management function; a session management function.

26. An apparatus according to any of claims 20 to 25, wherein the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

27. An apparatus comprising means for performing: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at the apparatus; and making the information available to another apparatus.

28. An apparatus according to claim 27, wherein the another apparatus comprises one of: a network data analytics function; a unified data management function; a unified data repository; an unstructured data storage function.

29. An apparatus according to any of claims 27 to 28, wherein the apparatus comprises an access and mobility management function.

30. An apparatus according to any of claims 27 to 29, wherein the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

31 . A method comprising: selectively performing collection of user equipment data for analytics based on a determination by an apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

32. A method comprising: retrieving by an apparatus, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

33. A method comprising: sending, from an apparatus to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

34. A method comprising: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at an apparatus; and making the information available to another apparatus.

35. A computer program comprising instructions for causing an apparatus to perform at least the following: selectively performing collection of user equipment data for analytics based on a determination by the apparatus of whether a condition is met; wherein the condition comprises a threshold quantity of user equipment supporting provision of data for analytics.

36. A computer program comprising instructions for causing an apparatus to perform at least the following: retrieving, from another apparatus, information of whether one or more user equipment support the provision of data for analytics.

37. A computer program comprising instructions for causing an apparatus to perform at least the following: sending, to another apparatus, information of whether the apparatus makes data for analytics available to the another apparatus; and sending, to the another apparatus, type information of the data for analytics that the apparatus makes available.

38. A computer program comprising instructions for causing an apparatus to perform at least the following: receiving, from each of a plurality of user equipment, information of whether each of the user equipment makes data for analytics available; storing the information at an apparatus; and making the information available to another apparatus.