Reporting measurement data

Abstract

A user equipment receives, from a network node, a measurement and reporting configuration with a user plane (UP) transmission flag which indicates logged measurements (logged minimisation of drive tes

Description

Field Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR.) access technology, or 5G beyond, or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and / or methods for, or relating to, reporting measurement data. Background Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-A Pro, and / or fifth generation (5G) or New Radio (NR) telecommunications systems, and future generation of telecommunications systems. Fifth generation (5G) telecommunications systems refer to the next generation (NG) of radio access networks and network architectures for core networks. A 5G telecommunication system is mostly based on new radio (NR) radio access technology (5G NR), but a 5G (or NG) network can also build on E-UTRAN. It is estimated that 5G NR will provide bitrates on the order of 10-20 Gbit / s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). 5G NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (loT). It is known to report measurement data, which may relate to a minimization of drive test (MDT) measurement data, to part of a radio network. Summary The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention. According to a first aspect, there is described an apparatus, for example a user device, comprising: means for receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; means for receiving, from the network node, second information comprising at least a trace session activation configuration; and means for, based on receiving the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, reporting of the measurement data such that it is reported directly to a data collection entity which is other than the network node and over the UP. In some embodiments, the reporting of the measurement data directly to the data collection entity is provided in a trace report. In some embodiments, the UP transmission flag comprises an identifier linked to the trace session activation configuration; and the reporting of the measurement data is further based on the identifier being linked to the trace session activation configuration. In some embodiments, the UP transmission flag comprises a first UP transmission flag associated with at least a first measurement and reporting configuration and comprises a first identifier linked to the trace session activation configuration; a second, different transmission flag is associated with at least a second measurement and reporting configuration and comprises a second identifier linked to a different trace session activation configuration, and the reporting of the measurement data comprises reporting of the measurement data associated with the first measurement and reporting configuration and not reporting of measurement data associated with the at least second measurement and reporting configuration. In some embodiments, the second information further comprises at least a network address of the data collection entity for enabling the user device to report the measurement data directly to the data collection entity. In some embodiments, the first information is received at a first time and the second information is received at a second, subsequent, time. In some embodiments, the means for the reporting of the measurement data is configured to report a first set of the measurement data to the network node over a control plane, CP, media access control, MAC, or Physical Layer, PHY, and in response to receiving the second information at the second time, the means for reporting of the measurement data is configured to switch from reporting the measurement data to the network node over the CP or MAC or PHY to reporting at least a second, and subsequent, set of the measurement data directly to the data collection entity. In some embodiments, the first information and the second information are received at substantially the same time. In some embodiments, the second information is received at a first time and the first information is received at a second, subsequent time, in which case the receiving of the second information effectively causes the reporting of the measurement data over the UP. In some embodiments, the measurement data is associated with a first trace reference; and the second information further comprises an indication of at least one of: the first trace reference; a second trace reference derived from the first trace reference; or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some embodiments, the indication is reported with the measurement data directly to the data collection entity. In some embodiments, the apparatus comprises means for detecting at least one terminating event; means for, in response to detecting the at least one terminating event, and based on the measurement and reporting configuration being associated with the UP transmission flag, terminating the reporting of the measurement data directly to the data collection entity and commencing or re-commencing of the reporting of the measurement data to the network node over a CP, MAC or PHY. In some embodiments, the at least one terminating event comprises at least one of: expiry of a time period at the user device; the user device meeting a first threshold number of measurements or measurements reports of the measurement data reported directly to the data collection entity; or the user device receiving of a deactivation message from the, or another, network node. In some embodiments, the at least one terminating event comprises the receiving of the deactivation message from the, or another, network node, and the deactivation message comprises a deactivation configuration for reconfiguring the user device to terminate the reporting of the measurement data directly to the data collection entity and commence or re-commence of the reporting of the measurement data to the network node over the CP, MAC or PHY. In some embodiments, the deactivation message is received by at least one of: a Media Access Control, MAC, message; or a Radio Resource Control, RRC, message. In some embodiments, the apparatus comprises means for transmitting an acknowledgement message to the network node in response to the reconfiguring. In some embodiments, the means for detecting the at least one terminating event is configured, at least in part, based on the second information. In some embodiments, the apparatus further comprises: means for establishing a protocol data unit, PDU, session with a data network associated with the data collection entity; and means for activating a UP connection of the PDU session, wherein the reporting of the measurement data directly to the data collection entity is performed using the UP connection of the PDU session. In some embodiments, the second information is received responsive to the network node detecting at least one trigger condition. According to a second aspect, there is described an apparatus, for example a network node, comprising: means for transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and means for transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. In some embodiments, the first information is transmitted to the user device in response to receiving a trace session activation message, for example from a network management system. In some embodiments, the UP transmission flag comprises an identifier linked to the trace session activation configuration. In some embodiments, the second information further comprises a network address of the data collection entity. In some embodiments, the first information is transmitted at a first time and the second information is transmitted at a second, subsequent, time. In some embodiments, the first information and the second information are transmitted at substantially the same time. In some embodiments, the second information is transmitted at a first time and the first information is transmitted at a second, subsequent time. In some embodiments, the apparatus further comprises: means for receiving, from a network management system, third information comprising at least a trace session switching configuration; and means for determining the second information comprising the at least trace session activation configuration based at least in part on the third information. In some embodiments, the third information is received in response to a request transmitted by the network node to the network management system. In some embodiments, the measurement data is associated with a first trace reference; and the second information further comprises an indication of at least one of: the first trace reference; a second trace reference derived from the first trace reference; or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some embodiments, the apparatus further comprises means for configuring or causing the user device to detect at least one terminating event for causing the user device, upon detecting of the at least one terminating event, to terminate the reporting of the measurement data directly to the data collection entity and commence or recommence the reporting of the measurement data to the network node over a control plane, CP, media access control, MAC, or Physical Layer, PHY. In some embodiments, the at least one terminating event comprises at least one of: expiry of a time period at the user device; the user device meeting a first threshold number of measurements or measurements reports of the logged measurement data reported directly to the data collection entity; or the user device receiving a deactivation message from the network node. In some embodiments, the means for configuring or causing the user device to detect the at least one terminating event network node is configured to transmit the deactivation message to the user device, the deactivation message comprising a deactivation configuration for reconfiguring the user device to terminate the reporting of the measurement data directly to the data collection entity and commence or recommence of the reporting of the measurement data to the network node over the CP, MAC or PHY. In some embodiments, the deactivation message is transmitted by at least one of: a Media Access Control, MAC, message; or a Radio Resource Control, RRC, message. In some embodiments, the apparatus further comprises means for receiving a first acknowledgement message from the user device in response to the reconfiguring by the user device. In some embodiments, the deactivation message is transmitted in response to the receiving of a second, earlier deactivation message from a network management system. In some embodiments, the apparatus further comprises means for transmitting a second acknowledgement message to the network management system in response to receiving the first, earlier acknowledgment message from the user device. In some embodiments, the apparatus further comprises means for detecting at least one trigger condition, wherein the second information is transmitted responsive to the detecting of the at least one trigger condition. In some embodiments, the at least one trigger condition is associated with a performance metric of the network node and / or of a radio access network, RAN, of which the network node forms a part. In some embodiments, the at least one trigger condition is associated with at least one of: an overload condition associated with the network node; a number of measurement reports received by the network node meeting a first threshold; an average delay for receiving measurement reports by the network node meeting a second threshold; an average delay for receiving a critical measurement reports by the network node meeting a third threshold; a throughput required to report measurement reports received by the network node to the, or another, data collection entity meeting a fourth threshold. In some embodiments, the at least one trigger condition is configured by an Operations and Maintenance, OAM, device. According to a third aspect, there is described a method, for example performed at a user device, and comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; and reporting based on receiving the trace session activation configuration, and based on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the measurement data such that it is reported directly to a data collection entity which is other than the network node and over the UP. The third aspect may comprise any feature described in relation to the first aspect. According to a fourth aspect, there is described a method, for example performed at a network node, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. The fourth aspect may comprise any feature described in relation to the second aspect. According to a fifth aspect, there is described a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method, comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; and reporting, based on receiving the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the measurement data such that it is reported directly to a data collection entity which is other than the network node and over the UP. The fifth aspect may comprise any feature described in relation to the first aspect. According to a sixth aspect, there is described a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. The sixth aspect may comprise any feature described in relation to the second aspect. According to a seventh aspect, there is described a non-transitory computer readable medium comprising program instructions stored thereon to cause the apparatus to carry out a method, comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; and reporting based on receiving the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the measurement data such that it is reported directly to a data collection entity which is other than the network node and over the UP. The seventh aspect may comprise any feature described in relation to the first aspect. According to an eighth aspect, there is described a non-transitory computer readable medium comprising program instructions stored thereon to cause the apparatus to carry out a method, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. The eighth aspect may comprise any feature described in relation to the second aspect. According to a ninth aspect, there is described an apparatus, comprising at least one processor; and at least one memory including computer-readable instructions which, when executed by the at least one processor, causes the apparatus to: receive, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receive, from the network node, second information comprising at least a trace session activation configuration; and report, based on receiving the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the measurement data such that it is reported directly to a data collection entity which is other than the network node and over the UP. The ninth aspect may comprise any feature described in relation to the first aspect. According to a tenth aspect, there is described an apparatus, comprising at least one processor; and at least one memory including computer-readable instructions which, when executed by the at least one processor, causes the apparatus to: transmit, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmit, to the user device, second information comprising at least a trace session activation configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. The tenth aspect may comprise any feature described in relation to the second aspect. According to an eleventh aspect, there is described an apparatus, for example a user device, comprising: means for receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; means for receiving, from the network node, second information comprising at least a trace session activation configuration; means for, based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, reporting of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over a UP. In some embodiments, the reporting of the measurement data directly to the data collection entity is provided in a trace report. In some embodiments, the UP transmission flag comprises an identifier linked to the trace session activation configuration; and the reporting of the logged measurement data is further based on the identifier being linked to the trace session activation configuration. Optionally, the UP transmission flag comprises a first UP transmission flag associated with at least a first measurement and reporting configuration and comprises a first identifier linked to the trace session activation configuration, a second, different transmission flag is associated with at least a second measurement and reporting configuration and comprises a second identifier linked to a different trace session activation configuration, and the reporting of the logged measurement data comprises reporting of the logged measurement data associated with the at least first measurement and reporting configuration and not reporting of logged measurement data associated with the at least second measurement and reporting configuration. In some embodiments, the second information further comprises at least a network address of the data collection entity for enabling the user device to report the logged measurement data directly to the data collection entity. In some embodiments, the first information is received at a first time and the second information is received at a second, subsequent, time after the user device transitions from the idle or inactive mode of operation to the connected mode of operation. In some embodiments, the means for the reporting of the logged measurement data is configured, to report a first set of the logged measurement data to the network node over a control plane, CP, media access control, MAC, or Physical Layer, PHY, and in response to receiving the second information at the second time, the means for reporting of the logged measurement data is configured to switch from reporting the logged measurement data to the network node over the CP, MAC or PHY to reporting at least a second, and subsequent, set of the logged measurement data directly to the data collection entity. In some embodiments, the first information and the second information are received at substantially the same time. In some embodiments, the second information is received at a first time and the first information is received at a second, subsequent time, in which case the receiving of the second information effectively causes the reporting of the logged measurement data over the UP. In some embodiments, the logged measurement data is associated with a first trace reference; and the second information further comprises an indication of at least one of: the first trace reference; a second trace reference derived from the first trace reference; or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some embodiments, the indication is reported with the logged measurement data directly to the data collection entity. In some embodiments, the apparatus further comprises means for detecting at least one terminating event; means for, in response to detecting the at least one terminating event, and based on the measurement and reporting configuration being associated with the UP transmission flag, terminating the reporting of the logged measurement data directly to the data collection entity and commencing or re-commencing of the reporting of the logged measurement data to the network node over a CP, MAC or PHY. In some embodiments, the at least one terminating event comprises at least one of: expiry of a time period at the user device; the user device meeting a first threshold number of measurements or measurements reports of the logged measurement data reported directly to the data collection entity; or the user device receiving of a deactivation message from the, or another, network node. In some embodiments, the at least one terminating event comprises the receiving of the deactivation message from the, or another, network node, and the deactivation message comprises a deactivation configuration for reconfiguring the user device to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence of the reporting of the measurement data to the network node over the CP, MAC or PHY. In some embodiments, the deactivation message is received by at least one of a media access control, MAC, message; or a radio resource control, RRC, message. In some embodiments, the apparatus further comprises means for transmitting an acknowledgement message to the network node in response to the reconfiguring. In some embodiments, the means for detecting the at least one terminating event is configured, at least in part, based on the second information. In some embodiments, the apparatus further comprises: means for establishing a protocol data unit, PDU, session with a data network associated with the data collection entity; and means for activating a UP connection of the PDU session, wherein the reporting of the logged measurement data directly to the data collection entity is performed using the UP connection of the PDU session. In some embodiments, the second information is received responsive to the network node detecting at least one trigger condition. According to a twelfth aspect, there is described an apparatus, for example a network node, comprising: means for transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and means for transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP. In some embodiments, the UP transmission flag comprises an identifier linked to the trace session activation configuration. In some embodiments, the second information further comprises a network address of the data collection entity. In some embodiments, the first information is transmitted at a first time and the second information is transmitted at a second, subsequent, time after the first device has transitioned from the idle or inactive mode to the connected mode of operation. In some embodiments, the first information and the second information are transmitted at substantially the same time. In some embodiments, the second information is transmitted at a first time and the first information is transmitted at a second, subsequent time. In some embodiments, the apparatus further comprises means for receiving, from a network management system, third information comprising at least a trace session switching configuration; and means for determining the second information comprising the at least trace session activation configuration based at least in part on the third information, wherein optionally the third information is received in response to a request transmitted by the network node to the network management system. In some embodiments, the logged measurement data is associated with a first trace reference; and the second information further comprises an indication of at least one of: the first trace reference; a second trace reference derived from the first trace reference; or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some embodiments, the apparatus further comprises means for configuring or causing the user device to detect at least one terminating event for causing the user device, upon detecting of the at least one terminating event, to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence the reporting of the logged measurement. In some embodiments, the at least one terminating event comprises at least one of: expiry of a time period at the user device; the user device meeting a first threshold number of measurements or measurements reports of the logged measurement data reported directly to the data collection entity; orthe user device receiving a deactivation message from the network node. In some embodiments, the means for configuring or causing the user device to detect the at least one terminating event network node is configured to transmit the deactivation message to the user device, the deactivation message comprising a deactivation configuration for reconfiguring the user device to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence of the reporting of the logged measurement data to the network node over the CP, MAC or PHY. In some embodiments, the deactivation message is transmitted by at least one of: a media access control, MAC, message or a radio resource control, RRC, message. In some embodiments, the apparatus further comprises means for receiving a first acknowledgement message from the user device in response to the reconfiguring by the user device. In some embodiments, the deactivation message is transmitted in response to the receiving of a second, earlier, deactivation message from a network management system. In some embodiments, the apparatus further comprises means for transmitting a second acknowledgment message to the network management system in response to receiving the first, earlier acknowledgment message from the user device. In some embodiments, the apparatus further comprises means for detecting at least one trigger condition, wherein the second information is transmitted responsive to the detecting of the at least one trigger condition. In some embodiments, the at least one trigger condition is associated with a performance metric of the network node and / or of a radio access network, RAN, of which the network node forms a part. In some embodiments, the at least one trigger condition is associated with at least one of: an overload condition associated with the network node; a number of measurement reports received by the network node meeting a first threshold; an average delay for receiving measurement reports by the network node meeting a second threshold; an average delay for receiving a critical measurement reports by the network node meeting a third threshold; a throughput required to report measurement reports received by the network node to the, or another, data collection entity meeting a fourth threshold. In some embodiments, the at least one trigger condition is configured by an operations and maintenance, OAM device. According to a thirteenth aspect, there is described a method, for example performed at a user device, and comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; reporting, based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over a UP. The thirteenth aspect may comprise any feature described in relation to the eleventh aspect. According to a fourteenth aspect, there is described a method, for example performed at a network node, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP. The fourteenth aspect may comprise any feature described in relation to the twelfth aspect. According to a fifteenth aspect, there is described a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method, comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; reporting, based on the receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over a UP. The fifteenth aspect may comprise any feature described in relation to the eleventh aspect. According to a sixteenth aspect, there is described a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP. The fifteenth aspect may comprise any feature described in relation to the twelfth aspect. According to a seventeenth aspect, there is described a non-transitory computer readable medium comprising program instructions stored thereon to cause the apparatus to carry out a method, comprising: receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receiving, from the network node, second information comprising at least a trace session activation configuration; reporting based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over a UP. The seventeenth aspect may comprise any feature described in relation to the eleventh aspect. According to an eighteenth aspect, there is described a non-transitory computer readable medium comprising program instructions stored thereon to cause the apparatus to carry out a method, comprising: transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP. The eighteenth aspect may comprise any feature described in relation to the eleventh aspect. According to a nineteenth aspect, there is described an apparatus, comprising at least one processor; and at least one memory including computer-readable instructions which, when executed by the at least one processor, causes the apparatus to: receive, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node; receive, from the network node, second information comprising at least a trace session activation configuration; report, based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over a UP. The nineteenth aspect may comprise any feature described in relation to the eleventh aspect. According to a twentieth aspect, there is described an apparatus, comprising at least one processor; and at least one memory including computer-readable instructions which, when executed by the at least one processor, causes the apparatus to: transmit, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; and transmit, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP. The twentieth aspect may comprise any feature described in relation to the eleventh aspect. Drawings Example embodiments will now be described by way of non-limiting example, with reference to the accompanying drawings, in which: FIG. 1 illustrates a radio network; FIG. 2 is a call flow diagram indicative of an example message flow between the components of the FIG. 1 network; FIG. 3 is a flow diagram indicating operations that may be performed according to some example embodiments; FIG. 4 is a further flow diagram indicating operations that may be performed according to some example embodiments; FIG. 5 is a call flow diagram indicative of an example message flow between the components of the FIG. 1 network according to a first embodiment; FIG. 6 is a call flow diagram indicative of an example message flow signaling between the components of the FIG. 1 network according to a second embodiment; FIG. 7 is a call flow diagram indicative of an example message flow signaling between the components of the FIG. 1 network according to a third embodiment; FIG. 8 is a further flow diagram indicating operations that may be performed according to some example embodiments; FIG. 9 is a further flow diagram indicating operations that may be performed according to some example embodiments; FIG. 10 is a call flow diagram indicative of an example message flow between the components of the FIG. 1 network according to a fourth embodiment; FIG. 11 is a call flow diagram indicative of an example message flow signaling between the components of the FIG. 1 network according to a fifth embodiment; FIGs. 12 to 15 are call flow diagrams indicative of an example message flow signaling between the components of the FIG. 1 network and which may be incorporated in some example embodiments; FIG. 16 illustrates a radio network according to some example embodiments; and FIG. 17 illustrates a set of apparatuses according to some example embodiments. Detailed Description Example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR.) access technology, or 5G beyond, or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and / or methods for, and / or related to, transmitting reporting data. A mobile network operator may collect measurement data from one or more devices which form part of, or which connect to, their network. The one or more devices may comprise user devices. A user device may comprise, by way of non-limiting examples, mobile devices such as at least one of a smartphone, tablet computer, wearable computer, laptop computer, digital assistant or internet-of-things (loT) device. The so-called Minimization of Drive Tests (MDT) framework is an example data collection mechanism which is referred to in one or more standardization documents. Example embodiments are however not necessarily limited to MDT standards. MDT may involve configuring devices, for example user devices, to measure measurement data "in the field" and to report the measurement data to the network via one or more network nodes, for example one or more gNBs. The collected measurement data may be used to optimize or at least improve certain functions of the mobile network that may for example relate to capacity and / or performance. In some (non-limiting) examples, the measurement data may be utilized as machine learning (ML) training data for one or more ML models, wherein the one or more ML models may be located at the user device and / or in the network. This means that a high volume of data (measurements and / or data derived from measurements, e.g., calculations) is or are required to be collected at the or each user device. The measurement data may be non -time critical relative to other forms of data which is or are critical to certain network functions. One method of collecting measurement data is for the mobile network to configure a user device to perform certain measurements, which may or may not be in response to a trigger event, and to report said measurements in a measurement report to a network node (e.g., gNB) network via the physical layer (Layer 1, PHY, LI), or media access control (MAC, L2), or via the control plane (CP) (Layer 3, L3) using Radio Resource Control (RRC) or LTE positioning protocol (LPP) signaling. The user device may receive from the network node (or another network node) a measurement and reporting configuration for this purpose. The measurement and reporting configuration configures or causes the user device to perform one or more types of measurement and possibly conditions, or trigger events, for determining when to commence and / or terminate measuring and / or when to report the resulting measurement data in one or more measurement reports. A plurality of measurement and reporting configurations may be provided to the user device, each associated with a different type of measurement, for example. To illustrate further, FIG. 1 illustrates a network 100 which may be useful for understanding example embodiments. The network 100 comprises a user device, hereafter user equipment (UE) 102, a first network node (gNB) 104, a management system (MaS) 106 and a trace collection entity (TCE) 108. The TCE 108 is an example of a data collection entity where measurements are received and stored for subsequent analysis and / or processing, which may or may not involve the use of ML models. The network 100 may optionally comprise an access and management function (AMF) 107a which may communicate with the MaS 106 and the gNB 104. For some forms of MDT, known as management-based MDT, the MaS 106 may communicate directly with the gNB 104. For another form of MDT, known as signaling-based MDT, specific UEs, including the UE 102, may be selected and to realize this the MaS 106 may communicate with the AMF 107a which communicates with the gNB 104. FIG. 2 illustrates a call flow diagram indicative of an example message flow and / or signaling between the above components of the FIG. 1 network 100. FIG. 2 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. The MaS 106 may determine that measurement data should be measured by at least one UE, including the UE 102, which is currently associated with the gNB 104. A consent check (not shown) may optionally be performed to check that particular UEs, including the UE 102, have consented to provide their measurement data (which is determined by customer care process and / or subscription data check), and this may be followed by a UE selection operation 200 at the gNB 104. For example, the MaS 106 may optionally perform the consent check, for example in case of signaling-based MDT, via a Unified Data Management (UDM) system (not shown) to ensure that particular UEs, including the UE 102, have consented to provide their measurement data. The MaS 106 may transmit a trace session activation 201 to the gNB 104. The trace session activation 201 may include a network address, for example an Internet Protocol (IP) address, or uniform resource locator or indicator (URL, URI), or similar, of the TCE 108 and a trace reference for the appropriate trace session. The gNB 104 may responsively transmit to the UE 102 over the control plane (CP, L3) an RRC message, such as an RRC Reconfiguration message 202 including at least one measurement and reporting configuration 202 for configuring the UE 102 to perform one or more measurements and report the measurements in a measurement report. The UE 102, when so configured, may transmit back to the gNB 104 over the control plane (CP, L3) a reply message such as RRC Reconfiguration Complete message 203 that may imply a settlement of a configuration. The UE 102, when so configured, may commence performing measurements in an operation 204, in accordance with the at least one measurement and reporting configuration 202 as now configured. In this respect, and in the context of MDT, it will be understood that there are two modes for MDT measuring, namely immediate MDT and logged MDT modes. In the immediate MDT mode, the UE 102 performs measurements whilst in the RRC connected mode (when the UE is active for transmitting and / or receiving data) and reports them to the gNB in real-time. One or more triggers may be used for initiating the measuring and / or reporting of the measurements to the gNB 104. In the logged MDT mode, the UE 102 performs measurements whilst in the RRC idle or inactive mode, stores (logs) the measurements and reports the measurements (logs) to the gNB 104 after the UE returns to the RRC connected mode. Whichever mode is used, the UE 102 reports the measurements to the gNB 104 in one or more measurement reports 205 over the control plane (CP, L3). For immediate MDT mode, depending on detailed configuration, trigger the UE 102 can report the measurements to the gNB 104 in one or more measurement reports 205 over the physical layer (PHY, LI) or the control plane (CP, L3) or media access control (MAC, L2) . The gNB 104 subsequently transmits a trace record 206 which may include the measurement report 204 (and possibly other measurement reports received from other UEs) in association with the trace reference to the TCE 108 and / or possible other TCEs using the network address provided with the trace session activation configuration 201. Optionally, and not shown, the gNB 104 may initially perform a UE selection process for selecting at least one UE, including the UE 102. The physical layer (PHY, LI) media access control (MAC, L2) and / or control plane (CP, L3) resources and their associated protocols (RRC, LPP) have limitations necessary for relatively low latency transmissions and / or frequent numbers of transmissions in order that the network can react quickly to the content of received measurement reports. An example is where the network might initiate, for the UE 102 for example, a handover procedure from a current cell to a new cell and / or adapts the radio configuration to reduce the number of Multiple-Input Multiple-Output (MIMO) layers on which the UE is receiving downlink data. A potential issue is that some types of measurement data (for example measurement data not associated with a low latency requirement and / or not critical to normal network operation) may adversely affect the transmitting, receiving and / or processing of more critical data (whether in terms of the data being associated with a low latency requirement and / or critical to normal network operation) transmitted using the physical layer (PHY, LI), media access control (MAC, L2) or control plane (CP, L3) or resources. Example embodiments aim to avoid or alleviate potential issues. Example embodiments may involve use of the so-called User Plane (UP) or UP function (UPF) which is a data plane in some communication systems, such as specified in the 5G standard and protocol stack. It will be appreciated that the UP is used for transmitting, primarily, user data. As such, it will also be appreciated that references to transmitting measurement data over the UP may refer to transmitting and / or receiving said measurement data using resources and / or protocols other than are used for the physical layer (PHY, LI) and / or control plane (CP, L3). In this way, it is possible to at least avoid or alleviate issues such as overloading at least part of the network and / or delaying more critical data that is to be transmitted over the physical layer (PHY, LI), media access control (MAC, L2) and / or control plane (CP, L3). FIGs. 3 to 7 are mainly related to immediate MDT mode operations and FIGs. 8 to 11 to logged MDT mode operations, although there are features common to all examples. Immediate MDT Mode FIG. 3 is a flow diagram showing operations 300 that may be performed by one or more example embodiments. The operations 300 may be performed by hardware, software, firmware or a combination thereof. The operations 300 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories. The operations 300 may, for example, be performed by a user device, or UE, which will be assumed hereinafter. The order of operations 300 is not necessarily indicative of their order of processing or performance. The operations 300 may relate to an MDT process, or similar, and particularly to the immediate MDT mode in which measurements are performed when the UE operates in the RRC connected mode of operation. A first operation 302 may comprise receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node. A second operation 304 may comprise receiving, from the network node, second information comprising at least a trace session activation and configuration. The second operation 304 may be performed after, before or at the same time as the first operation 302. A third operation 306 may comprise reporting, based on the receiving of the trace session activation and configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, reporting of the measurement data directly to the data collection entity and over the UP. In some example embodiments, the first information may comprise, or further comprise, at least one measurement and reporting configuration with UP transmission flag. The UP transmission flag may be associated with all or a subset of a plurality of measurement and reporting configurations which may be provided with the first information or which may already be configured at the UE. In some example embodiments, the reporting of the measurement data directly to the data collection entity may be provided in a trace report (which is UE-based trace record or measurement report or logged measurement report). In some example embodiments, the second information may further comprise at least a network address, for example an IP address or a URL or URI, of the data collection entity for enabling the UE to report the measurement data directly to the data collection entity. In some example embodiments, the UP transmission flag may further comprise an identifier linked to the trace session activation and configuration, wherein the reporting of the measurement data is further based on the identifier being linked to the trace session activation and configuration. For example, the UP transmission flag may comprise a first UP transmission flag associated with at least a first measurement and reporting configuration and comprises a first identifier linked to the trace session activation and configuration, and a second, different transmission flag may be associated with at least a second measurement and reporting configuration and comprises a second identifier linked to a different trace session activation and configuration. The reporting of the measurement data may comprise reporting of the measurement data associated with the first measurement and reporting configuration and not reporting of measurement data associated with the at least second measurement and reporting configuration. In some example embodiments, the first information may be received at a first time and the second information may be received at a second, subsequent time. In this case, the reporting of the measurement data may comprise reporting a first set of the measurement data to the network node over a physical layer (PHY, LI), media access control (MAC, L2) and / or control plane (CP, L3) with the network node. Then, in response to receiving the second information at the second time, the UE may switch from reporting the measurement data over the physical layer (PHY, LI), media access control (MAC, L2) and / or control plane (CP, L3) to reporting at least a second, and subsequent set of the measurement data directly to the data collecting entity. In some example embodiments, the first information and the second information may be received at substantially the same time. In some example embodiments, the second information may be received at a first time and the first information may be received at a second, subsequent, time. In this case, the receiving of the first information effectively activates or causes the reporting of measurement data associated with the UP transmission flag because the second information has already been received. Example embodiments, to be described below, outline signaling options for different situations. In some example embodiments, the measurement data may be associated with a first trace reference and the second information may further comprise an indication of at least one of the first trace reference, a second trace reference derived from the first trace reference, or a third trace reference capable of being associated with the first trace reference at the data collection entity. The indication may be reported with the measurement data, i.e., in or with the measurement report, directly to the data collection entity, for example in a trace report (which may be UE-based trace record, or measurement report or logged measurement report). Some example embodiments also comprise operations including detecting at least one terminating event and, in response to detecting the at least one terminating event, and based on the measurement and reporting configuration being associated with the UP transmission flag, terminating the reporting of the measurement data directly to the data collection entity and commencing or re-commencing of the reporting of the measurement data to the network node over the physical layer (PHY, LI), media access control (MAC, L2) and / or control plane (CP, L3). Examples of terminating event(s) will be described later on. In some example embodiments, the second information is received responsive to the network node detecting at least one trigger condition. For example, the at least one trigger condition may be associated with a performance metric of the network node and / or of a RAN of which the network node forms a part. Examples of the at least one trigger condition will be described later on. FIG. 4 is a flow diagram showing operations 400 that may be performed by one or more example embodiments. The operations 400 may be performed by hardware, software, firmware or a combination thereof. The operations 400 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories. The operations 400 may, for example, be performed by a network node, such as a gNB or similar, which will be assumed hereinafter. The order of operations 400 is not necessarily indicative of their order of processing or performance. The operations 400 may relate to an MDT process, or similar, and particularly to the immediate MDT mode. A first operation 402 may comprise transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report, in response to receiving a trace session activation and configuration, measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity. A second operation 404 may comprise transmitting, to the user device, second information comprising at least a trace session activation and configuration for activating the at least one user device to report the measurement data, associated with the at least one measurement and reporting configuration, directly to the data collection entity and over the UP. The second operation 404 may be performed after, before or at the same time as the first operation 402. In some example embodiments, the UP transmission flag may comprise an identifier linked to the trace session activation. In some example embodiments, the second information may further comprise a network address of the data collection entity. In some example embodiments, the first information may be transmitted at a first time and the second information may be transmitted at a second, subsequent, time. In an alternative embodiment, the first information and the second information may be transmitted at substantially the same time. In some example embodiments, the logged measurement data may be associated with a first trace reference and the second information may further comprise an indication of at least one of the first trace reference, a second trace reference derived from the first trace reference, or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some example embodiments, an operation may be provided for configuring or causing the user device to detect at least one terminating event for causing the user device, upon detecting of the at least one terminating event, to terminate the reporting of the measurement data directly to the data collection entity and commence or re-commence the reporting of the measurement data to the network node over the physical layer (PHY, LI), media access control (MAC, L2) and / or control plane (CP, L3). In some example embodiments, an operation may comprise detecting at least one trigger condition, wherein the second information is transmitted responsive to the detecting of the at least one trigger condition. The at least one trigger condition may be associated with a performance metric of the network node and / or of a radio access network, RAN, of which the network node forms a part. Example embodiments will be described in more detail. FIG. 5 illustrates a call flow diagram, in accordance with a first example embodiment, indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100 which in this case also comprises a UDM 110. FIG. 5 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. The MaS 106 may determine that measurement data should be measured by at least one UE, including the UE 102, which is currently associated with the gNB 104. The MaS 106 may transmit a trace session activation 501 to the gNB 104. The trace session activation 501 may include a network address, for example an Internet Protocol (IP) address, URL or URI, or similar, of the TCE 108 and a trace reference associated with a trace session. An optional consent check (not shown) may be performed in the network to ensure that particular UEs, including the UE 102, have consented to provide their measurement data. The gNB 104 may also optionally perform a UE selection 503 for selecting at least one UE, including the UE 102, based on known methods. The gNB 104 may transmit to the UE 102 over the control plane (CP, L3) first information. The first information may at least comprise a UP transmission flag providing an indication for the UE 102 to report measurement data associated with at least one measuring and reporting configuration over the UP when activated to do so. For ease of explanation, these "flagged" at least one measuring and reporting configurations are assumed to relate to non-critical data (although this is not necessarily the case) and hence the term non-critical measurement data may be used to refer to the measurement data resulting therefrom. In this example, the first information is comprised in an RRC Reconfiguration message 504 including the at least one measurement and reporting configuration for configuring the UE 102 to perform one or more measurements and report the measurements in a measurement report. At the UE 102, and based on the RRC Reconfiguration message 504, the at least one measurement and reporting configurations are associated with said UP transmission flag. For example, the UP transmission flag may be associated with one or more measurement and reporting configurations for measuring non-latency sensitive and / or non-critical data types. The UE 102, when so configured, may transmit back to the gNB 104 and over the control plane (CP, L3) an RRC Reconfiguration Complete message 505. The UE 102, when so configured, may commence performing measurements in an operation 506, in accordance with the one or more measurement and reporting configurations for both critical and non-critical data measurements. The UE 102 reports the measurements to the gNB 104 in an RRC measurement report 507 over the control plane (CP, L3). The gNB 104 subsequently transmits a trace record 508 which may include the measurement report 204 (and possibly packaged with other measurement reports received from other UEs) in association with the trace reference to the TCE 108 and using the network address provided with the trace session activation 501. In an operation 509 the gNB 104 may detect at least one triggering condition or event. The at least one triggering condition may be associated with a performance metric of the gNB 104 and / or of the radio access network, RAN, of which the gNB forms a part. For example, data collection of the non-critical data measurements (associated with the UP transmission flag) may be causing undue burden and / or interfering with normal network operation. Therefore, it may be appropriate to switch to transmitting such non-critical data over the UP thereby freeing up existing resources and mitigating such issues. By way of example only, the at least one triggering condition may be associated with_at least one of an overload condition associated with the gNB 104, a number or frequency of measurement reports associated with non-critical data received by the gNB meeting a first threshold, an average delay for receiving measurement reports associated with critical data by the gNB increasing to, or meeting, a second threshold, or a throughput required to report measurement reports received by the gNB to the, or another, TCE 108 meeting a fourth threshold. Said thresholds may be configured by the network. In response to the detection in operation 509, the gNB 104 may transmit a switching request 510 to the MaS 106 for requesting the MaS to switch the current trace transmission entity from being the gNB to being the UE 102 and including the trace reference of the trace session. The MaS 106 may determine that the trace transmission entity can be switched to the UE 102 and may transmit to the gNB 104 a TTE accept message 511, which may include a trace session switching configuration which may itself include at least one of: the same (first) trace reference that was provided in the earlier operation 501, a second trace reference derived from the first trace reference, or a new (third) trace reference associated with UEs switched to being the trace transmission entity. The gNB 104 may responsively transmit second information to the UE 102 which may comprise a trace session activation and configuration 512 for configuring the UE to act as the trace transmission entity for the trace session. The trace session activation and configuration 512 may also comprise at least one of the first trace reference, the second trace reference or the third trace reference referred to above, thereby to allow measurement data received before and after the switching to be matched to the same trace session. The trace session activation and configuration 512 may also comprise the network address of the TCE 108, e.g., the same IP address, URL or URI that was provided to the gNB 104 in the earlier operation 501, a different IP address for the same TCE or even a different IP address for a different TCE. Optionally, the trace session activation and configuration 512 may also comprise indications of one or more terminating events which will be mentioned below. The UE 102, once configured, may transmit a reconfiguration complete or similar acknowledgement message 513 to the gNB 104. The gNB 104 may transmit a trace transmission entity switching request complete acknowledgement message 514 to the MaS 106. The UE 102, once configured, may commence, or carry-on, measuring measurement data according to its one or more measurement and reporting configurations in an operation 515. Non-critical measurement data derived from the measurement and reporting configurations associated with the UP transmission flag, is transmitted in a trace report (which is UE-based trace record, or measurement report or logged measurement report) 516 (which may comprise one or more trace records) and directly to the TCE 108 and over the UP instead of over the physical layer (PHY, LI), media access control (MAC, L2) or the control plane (CP, L3). The trace session may be deactivated responsive to at least one terminating event. Operations 517 and 518 respectively refer to (i) trace session deactivation operations by the gNB and (ii) trace session deactivation by configuration, which two operations may be used alternatively or in combination. Deactivation in this context may effectively undo operations 510 to 513. By way of example, operation 517 may comprise sub-operations comprising the gNB 104 reconfiguring the UE 102 to transmit its measurements derived from said measurement and reporting configurations associated with the UP transmission flag over the the physical layer (PHY, LI), media access control (MAC, L2) or the control plane (CP, L3). The reconfiguration, a form of deactivation message, may be provided in an RRC message and / or via a Medium Access Control (MAC) message, e.g., using a bit corresponding to the UP transmission activation field being set to 1. The UE 102 may responsively transmit a reconfiguration acknowledgement message to the gNB 104, via an RRC message and / or via a MAC message as above. The gNB 104 may responsively transmit a trace session switch cancellation request to the MaS 106. The MaS 106 may responsively transmit an acknowledgement message to the gNB 104 to cancel the trace session switch. These sub-operations may be performed by the gNB 104 immediately following receipt of the reconfiguration acknowledgement message, or after a delay period, in case the gNB needs to reconfigure the UE 102 to transmit measurement reports over the UP again. Operation 518, referring to trace session deactivation by configuration, means that the UE 102 is configured with one or more triggering conditions by the gNB 104, wherein the one or more triggering conditions is or are associated with one or more terminating events. Said triggering condition(s) may be configured by another entity, such as the MaS 106 or an Operations and Maintenance (OAM) centre or similar which informs the gNB 104 of said triggering condition(s) to apply. Said triggering conditions may comprise one or more of expiry of a time period at the UE 102 (time based) or the UE meeting a first threshold number of measurements or measurement reports of the measurement data reported directly to the data collection entity (volume based). The gNB 104 will be able to accept subsequent measurement reports over the the physical layer (PHY, LI), media access control (MAC, L2) or the control plane (CP, L3) because it was the entity that configured the UE 102 with such triggering conditions. The gNB 104 may then optionally perform resetting of the triggering conditions using an RRC or MAC CE message and may, in the manner of the sub-operations of operation 518 described above, undo operations 510 to 513. As a further note, because the mechanism for measuring data is over the UP and therefore does not rely on a control plane context, e.g., an RRC context, it is also possible for the UE 102 to flush an internal measurement buffer at a next opportunity even if the UE is handed over to a new cell before it is able to transmit buffered measurements, if any. FIG. 6 illustrates a call flow diagram, in accordance with a second example embodiment, indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 6 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. In the second example embodiment, and different from the first example embodiment, the MaS 106 may transmit in an initial operation 601 both a trace session activation 501 and a trace session switching configuration to the gNB 104. By providing the trace session switching configuration in advance, there is no need for the gNB 104 to request it from the MaS 106 at a later time. The content of the trace session switching configuration and / or the first information (e.g., measurement and reporting configuration with UP transmission flag) may be the same as the first example embodiment. It will be seen, therefore, that operations 603 to 609, 612 to 613 and 615 to 618 otherwise correspond to operations 503 to 509, 512 to 513 and 515 to 518 respectively. FIG. 7 illustrates a call flow diagram, in accordance with a third example embodiment, indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 7 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. In the third example embodiment, and similar to the second example embodiment, the MaS 106 may transmit in an initial operation 701 both a trace session activation 501 and a trace session switching configuration to the gNB 104. By providing the trace session switching configuration in advance, there is no need for the gNB 104 to request it from the MaS 106 at a later time. Further, the gNB 104 may provide to the UE 102 both the first information (e.g., measurement and reporting configuration with UP transmission flag 704A) and the second information (e.g. trace session activation and configuration 704B) at substantially the same time. This may therefore immediately configure the UE 102 for transmission of measurement reports (which may comprise one or more trace reports) directly to the TOE 108 and over the UP. The content of the trace session switching configuration and / or the measurement and reporting configuration with UP transmission flag may be the same as for the first example embodiment. It will be seen, therefore, that operations 703, 705 to 706 and 717 to 718 otherwise correspond to operations 503, 505 to 506 and 517 to 518 respectively. Other example embodiments will now be described in relation to the logged MDT mode where like terminology may refer to like features and / or operations. Logged MDT Mode FIG. 8 is a flow diagram showing operations 800 that may be performed by one or more other example embodiments. The operations 800 may be performed by hardware, software, firmware or a combination thereof. The operations 800 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories. The operations 800 may, for example, be performed by a user device, or UE, which will be assumed hereinafter. The order of operations 800 is not necessarily indicative of their order of processing or performance. The operations 800 may relate to an MDT process, or similar, and particularly to the logged MDT mode. A first operation 802 may comprise receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data, associated with at least one logged measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node. A second operation 804 may comprise receiving, from the network node, second information comprising at least a trace session activation and configuration. The second operation 804 may be performed after, before or at the same time as the first operation 802. A third operation 806 may comprise based on receiving of the trace session activation and configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, reporting of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, such that the logged measurement data is reported directly to the data collection entity and over the UP. In some example embodiments, the reporting of the logged measurement data directly to the data collection entity is provided in a trace report (which may be a UE-based trace record or logged measurement report). In some example embodiments, the UP transmission flag may comprise an identifier linked to the trace session activation and configuration, wherein the reporting of the logged measurement data is further based on the identifier being linked to the trace session activation and configuration. For example, the UP transmission flag may comprise a first UP transmission flag associated with at least a first measurement and reporting configuration and comprises a first identifier linked to the trace session activation and configuration, and a second, different transmission flag may be associated with at least a second measurement and reporting configuration and comprises a second identifier linked to a different trace session activation and configuration. The reporting of the logged measurement data may comprise reporting of the logged measurement data associated with the at least first measurement and reporting configuration and not reporting of logged measurement data associated with the at least second measurement and reporting configuration. In some example embodiments, the second information may further comprise at least a network address of the data collection entity for enabling the user device to report the logged measurement data directly to the data collection entity. In some example embodiments, the first information may be received at a first time and the second information may be received at a second, subsequent, time after the user device transitions from the idle or inactive mode of operation to the connected mode of operation. For example, reporting of the logged measurement data may comprise, in response to the receiving of the first information at the first time, reporting a first set of the logged measurement data to the network node over a control plane, CP, and in response to receiving the second information at the second time, the reporting of the logged measurement data may comprise switching from reporting the logged measurement data to the network node over the CP reporting at least a second, and subsequent, set of the logged measurement data directly to the data collection entity. In some example embodiments, the first information and the second information are received at substantially the same time. In some example embodiments, the second information is received at a first time and the first information is received at a second, subsequent, time. In some example embodiments, the logged measurement data may be associated with a first trace reference, and the second information may further comprise an indication of at least one of the first trace reference, a second trace reference derived from the first trace reference, or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some example embodiments, the indication may be reported with the logged measurement data directly to the data collection entity. Some example embodiments also comprise operations including detecting at least one terminating event and, in response to detecting the at least one terminating event, and based on the measurement and reporting configuration being associated with the UP transmission flag, terminating the reporting of the logged measurement data directly to the data collection entity and commencing or re-commencing of the reporting of the logged measurement data to the network node over the control plane (CP, L3). Examples of terminating event(s) have been described above. In some example embodiments, the second information is received responsive to the network node detecting at least one trigger condition. For example, the at least one trigger condition may be associated with a performance metric of the network node and / or of a RAN of which the network node forms a part. Examples of the at least one trigger condition have already been described above. FIG. 9 is a flow diagram showing operations 900 that may be performed by one or more example embodiments. The operations 900 may be performed by hardware, software, firmware or a combination thereof. The operations 900 may be performed by one, or respective, means, a means being any suitable means such as one or more processors or controllers in combination with computer-readable instructions provided on one or more memories. The operations 900 may, for example, be performed by a network node, such as a gNB or similar, which will be assumed hereinafter. The order of operations 900 is not necessarily indicative of their order of processing or performance. The operations 900 may relate to an MDT process, or similar, and particularly to the logged MDT mode. A first operation 902 may comprise transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity. A second operation 904 may comprise transmitting, to the user device, second information comprising at least a trace session activation and configuration for activating the at least one user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, and directly to the data collection entity over the UP. The second operation 904 may be performed after, before or at the same time as the first operation 902. In some example embodiments, the UP transmission flag may comprise an identifier linked to the trace session activation. In some example embodiments, the second information may further comprise a network address of the data collection entity. In some example embodiments, the first information may be transmitted at a first time and the second information may be transmitted at a second, subsequent, time after the first device has transitioned from the idle or inactive mode to the connected mode of operation. In an alternative embodiment, the first information and the second information may be transmitted at substantially the same time. In some example embodiments, the logged measurement data may be associated with a first trace reference and the second information may further comprise an indication of at least one of the first trace reference, a second trace reference derived from the first trace reference, or a third trace reference capable of being associated with the first trace reference at the data collection entity. In some example embodiments, an operation may be provided for configuring or causing the user device to detect at least one terminating event for causing the user device, upon detecting of the at least one terminating event, to terminate the reporting of the logged measurement data directly to the data collection entity and commence or recommence the reporting of the logged measurement data to the network node over the control plane (CP, L3). In some example, embodiments an operation may comprise detecting at least one trigger condition, wherein the second information is transmitted responsive to the detecting of the at least one trigger condition. The at least one trigger condition may be associated with a performance metric of the network node and / or of a radio access network, RAN, of which the network node forms a part. Further example embodiments will be described in more detail. FIG. 10 illustrates a call flow diagram, in accordance with a fourth example embodiment, indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 10 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. The MaS 106 may determine that logged measurement data should be measured by at least one UE, including the UE 102, which is currently associated with the gNB 104. Similar to the second and third example embodiments of FIGs. 6 and 7, the MaS 106 may transmit in an initial operation both a trace session activation 1001A and a trace session switching configuration 1001B to the gNB 104 for logged data measurements. This may be based on the UE 102 informing the MaS 1106 or gNB 104 that it supports logged MDT, wherein the UE may be configured to measure logged data measurements based on one or more logged measurement configurations and to report said logged data measurements to the gNB 104. This may be based on provisioned logged data measurement characteristics, e.g., based on duration, buffer size threshold, deployment scenario and / or use case. The trace session activation 1001A may include a network address, for example an Internet Protocol (IP) address, or similar, of the TCE 108 and a trace reference associated with a trace session. The same alternative options for the network address and trace reference described above can be used. An optional consent check (not shown) may be performed in the network.. The gNB 104 may also optionally perform a UE selection 1003 for selecting at least one UE, including the UE 102, based on known methods. By providing the trace session switching configuration 1001B in advance, there is no need for the gNB 104 to request it from the MaS 106 at a later time. Further, and in response, the gNB 104 may provide to the UE 102 in a RRC Reconfiguration message both the first information (e.g., a logged measurement and reporting configuration with UP transmission flag 1004A) and the second information (e.g. trace session activation and configuration 1004B) at substantially the same time. This may therefore immediately configure the UE 102 for transmission of logged measurement reports (which may include one or more trace reports) directly to the TCE 108 and over the UP. The content of the trace session switching configuration and / or the measurement and reporting configuration with UP transmission flag may be the same as for the first to third example embodiments other than it is associated with the reporting of logged data measurements. The above operations are performed when the UE 102 is in the connected mode of operation. In an operation 1005, the UE 102 may transition from the connected mode of operation to the RRC idle or inactive mode of operation. In an operation 1006, the UE 102 may commence measuring and logging measurement data according to its one or more measurement and reporting configurations, including those associated with the UP transmission flag, and packages the resulting measurements or measurement reports into one or more trace records (which can be UE-based trace records)for being reported directly to the TCE 108 and over the UP at a later time when the UE 102 transitions back to the connected mode of operation. The trace session activation and configuration 1004B may determine at least one trigger upon which the conditions for generating logged measurements reports will apply. Examples may comprise at least one of expiry of a time limit (a corresponding timer may be provided for this purpose), a number of data measurement(s), a buffer or memory size reached, or an event, for example a cell reselection event. In operations 1007 and 1008, RRC setup / resume signalling may enable the UE 102 to transition back to the connected mode of operation (RRC connected). In response, a logged measurement report (which can be a UE-based trace record) 1009 comprising the logged data measurements, or measurement reports, associated with the UP transmission flag, may be transmitted by the UE 102 directly to the TCE 108 and over the UP. FIG. 11 illustrates a call flow diagram, in accordance with a fifth example embodiment, indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 11 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. The trace session activation 1001A and trace switching configuration 1001B and the optional data collection consent check and UE selection operation 1103 may be the same as for the FIG. 10 example. However, the subsequent operation may comprise transmitting only the first information comprising a logged measurement and reporting configuration with UP transmission flag 1104. The second information comprising a trace session activation and configuration is not transmitted by the gNB 104 to the UE 102 at this time. The above operations are performed when the UE 102 is in the connected mode of operation. In an operation 1105, the UE 102 may transition from the connected mode of operation to the RRC idle or inactive mode of operation. In an operation 1106, the UE 102 may commence measuring and logging measurement data according to its one or more logged measurement and reporting configurations, including those associated with the UP transmission flag, and packages the resulting measurements into one or more measurement reports. In an operation 1107, a setup or resume message is transmitted by the UE 102 to the gNB 104 indicating that the UE is ready to transition back to the connected mode of operation and may include a logged measurement availability. In an operation 1108, the UE 102 transitions back to the connected mode of operation. In an operation 1109, the gNB 104 may transmit to the UE 102 a logged measurement request. In an operation 1110, the UE 102 may transmit to the gNB 104 a logged measurement report (#1) over the control plane (CP, L3). The logged measurement report (#1) may comprise the network address, for example IP address, URL or URI, of the TCE 108, the trace reference, a trace session recording reference and / or an availability indication for further logged measurement reports. The availability indication may provide the gNB 104 with information which may assist the gNB in determining whether to switch from current control plane (CP, L3) reporting of measurement data to reporting over the UP. For example, a so-called enhanced logged measurement report availability indication may include at least one of: an indication of a threshold number of measurement logs based on a fixed threshold, or a configurable threshold as specified in the logged measurement and reporting configuration, an indication of a number of logs, which could be given as a flexible integer value (e.g., indicating that one to sixteen logs are available) or where the largest value, e.g., sixteen) indicates that more than fifteen logs are available) or an enumerated value or index mapping to a range of available logs, e.g. 0: one log available, 1: between one and three logs are available, 2: between four and fifteen logs are available and 3: sixteen or more logs are available. In an operation 1111, the gNB may transmit to the TCE 108 a trace record which may include the logged measurement report (#1). In an operation 1112, the gNB 104 may detect at least one triggering condition or event which may be the same or similar to that or those described for the previous embodiments, for which refer to operation 609 in the FIG. 6 embodiment. In an operation 1113, the gNB 104 at this time transmits second information comprising a trace session activation and configuration 1113 as described for previous embodiments. In an operation 1114, the UE 102 may transmit an acknowledgment message such as an RRC reconfiguration complete message. In an operation 1115, the UE 102 may report the logged measurements as a logged measurement report (which can be a UE-based trace record or measurement report) directly to the TCE 108 and over the UR Activation, Deactivation and Switching The following describes example RRC and MAC procedures and preferences for activation, deactivation and switching and described in the above. In each example that follows, a MAC control element may be replaced with an RRC message, e.g., an RRC reconfiguration message. FIG. 12 illustrates an example activation process in which the gNB 104 in transmitting the trace session activation and configuration as described above may transmit a UE trace session configuration 1201 followed by a MAC control element 102 for activating UP measurement reporting. FIG. 13 illustrates subsequent optional control flow for a deactivation process in which the MaS 106 may transmit a trace transmission entity switching cancellation message 1203 to the gNB 104. The gNB 104 may then transmit a MAC control element 1204 to the UE 102 and a trace transmission entity switching cancellation acknowledgment message 1205 back to the MaS 106. Switching is implied by the activation and deactivation processes, e.g., switching to the UP is activation of UP transmission or reporting. Trace Reference Provisioning Trace sessions are identified by trace references. In order to allow trace sessions to function, for example as in legacy systems to allow trace sessions to terminate based on known procedures, a new type of trace reference may be applied to example embodiments. The new type of trace reference may be used by UEs, such as UE 102 when acting as trace transmission entities, such that they may generate their own trace record header commands, such as "trace file open", "trace file closed", etc. For example, the MaS 106 may provide to the gNB 104 rules or conditions defining how to provision a new trace reference if the new trace reference is a derived trace reference or a non-derived new trace reference. If a derived trace reference is to be used in the trace session switching configuration for the UE 102 and / or other UEs, one or more rules may be used for the derivation. In one example, the current trace reference may be incremented to provide a derived trace reference for each UE being provisioned until a limit is reached, e.g., from zero to 127 (last eligible UE). In another example, the same derivative trace reference may be used for all UEs being provisioned which will be activated by the same gNB 104, in which case the derived trace reference may be current trace reference when incremented or a fixed derivative trace reference provided by the MaS 106. For example, derived trace references may be valid so long as the current trace reference is valid, for example until the time of trace session deactivation by the MaS 106. If a new (non-derived) trace reference is to be used in the trace session switching configuration for the UE 102 and / or other UEs, this may be based on the cell global identity (CGI) of the gNB 104. The gNB 104 may for example generate new trace reference that may commence with the CGI. For example, each UE may receive a unique trace reference wherein the current trace reference may be incremented to provide the new trace reference for each UE being provisioned until a limit is reached, wherein the base of the new trace reference(s) is the CGI of the gNB 104. In another example, the same new trace reference may be used for all UEs being provisioned which will activated by the same gNB 104, in which case the new trace reference may be current trace reference when incremented or a fixed new trace reference provided by the MaS 106. The gNB 104 may track the new trace reference such that the trace reference of each new trace session configured by the MaS 106 may be associated with the new trace reference, In these cases, because the new trace reference is directly tied to the current (original) trace reference, something about the new trace reference should be unique such that the TOE 108 may associate the current trace reference with the new trace reference used at commencement of the trace session. For example, a fixed timestamp, created at the commencement of the trace session activation may be part of the new trace reference and a new fixed timestamp may be used for each new trace session activation. In all embodiments described herein, file-based or streaming-based trace reporting is assumed. In streaming-based the trace records are reported as soon as they are prepared. In file-based reporting the trace records are buffered and transmitted as a file to the TCE 108. In some embodiments, a flag could indicate to the UE 102 at the time of trace session configuration or trace session activation which mode, streaming or file -based, is to be used. The presence of the flag could, for example, indicate filebased reporting is to be used or alternatively the configuration may directly indicate which to use. In all embodiments described herein, further enhancements may be made to trace records. For example, trace records may use an alternate NF instance ID, an addition of a NF type for the UE 102 and / or an option to transmit a derivative or new trace reference as described above. FIG. 14 illustrates a timing and signaling diagram indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 14 provides a simplified view of how a trace recording session reference may be used and in particular how it may be transmitted in trace records transmitted by the gNB 104 to the TCE 108. FIG. 14 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. An operation 1401 may comprise the MaS 106 transmitting to the gNB 104 a trace session activation and configuration with trace reference. An operation 1402 may comprise the gNB 104 optionally selecting UEs, including the UE 102, after checking user consent for users of said UEs. An operation 1403 may comprise the gNB 102 transmitting first information comprising a measurement reporting configuration with UP transmission flag. An operation 1404 may comprise the gNB 104 generating a trace recording session reference. An operation 1405 may comprise the gNB 104 transmitting to the UE 102 a trace session configuration with the trace reference and a trace recording session reference. An operation 1406 may comprise the UE 102 performing measurements in accordance with the measurement reporting configuration with UP transmission flag. An operation 1407 may comprise the UE 102 reporting to the gNB 104 the measurements in a measurement report. An operation 1408 may comprise the gNB 104 transmitting a trace record with an identity of RAN node, i.e., the gNB, the trace reference, trace recording session reference and the measurements in the received measurement report. An operation 1409 may comprise the gNB 104 transmitting to the UE 102 second information comprising a trace session activation. An operation 1410 may comprise the UE 102 performing measurements in accordance with the measurement reporting configuration with UP transmission flag. An operation 1411 may comprise the UE 102 reporting measurement report (or logged measurement report) directly to the TCE 108 over the UP. The measurement report (or logged measurement report) may comprise a UE-based trace record. The trace record may comprise the identity of the UE 102, the trace reference, the trace recording session reference and the measurements. FIG. 15 illustrates a timing and signaling diagram indicative of an example message flow and / or signaling between, for example, the above components of the FIG. 1 network 100. FIG. 15 provides a simplified view of how the UE 102 may transmit trace records to different TCEs, including the TCE 108. For example, the TCE 108 may be associated with a first network address, a further TCE 120 (UE trace IP) may be on the same server as the TCE 108 and a yet further TCE 122 may be on a different server as the TCE 108 and further TCE 120. FIG. 14 is merely an example and a fewer or larger number of messages and / or signals may be involved in other examples. An operation 1501 may comprise the MaS 106 transmitting to the gNB 104 a trace activation and configuration with trace reference, which may also indicate the network address(es) of one or more of the TCEs 108, 120, 122. An operation 1502 may comprise the gNB 104 optionally selecting UEs, including the UE 102. An operation 1503 may comprise the gNB 102 transmitting to the UE 102 first information comprising a measurement reporting configuration with UP transmission flag and second information comprising a UE trace session configuration and activation which may indicate said network address(es) of one or more of the TCEs 108, 120, 122. An operation 1505 may comprise the UE 102 reporting to the TCE 108 a first trace record comprising measurements, to the further TCE 120 a second trace record comprising measurements and / or to the yet further TCE 122 a third trace record comprising measurements based on the trace session configuration. FIG. 16 illustrates a modified network 100A in accordance with some example embodiments. The network 100A may comprise the same or similar elements of the FIG. 1 network 100 and may also comprise a user plane function (UPF) 107b connected to a data network (DN) 107c which is associated with, for example has access to, the TCE 108 that will be used by the UE 102 as the target for reporting measurement data of any above description. The gNB 104 may have a direct connection to the UPF 107b. A data path that is established between the UE 102 and the DN 107c may be referred to as a protocol data unit (PDU) session. The UE 102 may be configured with an indication of a DN, for example the DN 107c, that has access to the TCE 108. The DN 107c may be referred to as a data collection DN. Hence, in order to report measurement data, the UE 102 may establish a PDU session and activate a UP connection of the PDU session to handle UP transmissions, including user traffic, between the UE 102 and the DN 107c. The UE 102 may for example issue a PDU session establishment request through the AMF 107a (whether directly or via the gNB 104) to a session management function (SMF) 107d which will provide access and also configure, via the AMF 107a, the gNB 104 and UE 102 with parameters of the PDU session. This is such that the UE 102 can send UP data to the gNB 194 which will forward said UP data towards the UPF 107b with access to the DN 107c and the TCE 108. In some examples, the UPF 107b may handle routing of the UP traffic to a local part of the DN 107c. The selection and re-selection of the UPF 170b for PDU session establishment and / or UE traffic offloading may be performed by considering UPF deployment scenarios such as a centrally-located UPF and distributed UPF located close to, or at, the RAN or gNB 104 site. The core network may select a UPF, for example the UPF 107b, which is close to the UE 102. A UP tunnel may therefore be established between the UE 102 and the UPF 107b. For some PDU sessions of the UE 102, a UP tunnel may be established to buffer, forward, transfer and / or route user traffic to the DN 107c. The UPF 107b may forward UP traffic to enable local access to the DN 107c according to provided traffic steering rules to the UPF 107b and a given DN address, for example IP address. Each UPF, including the UPF 107b, will support one interface instance towards the DN 107c. In some examples, there may be provided a network device, for example a network management system (e.g., the MaS 106 or another entity) for providing to a network node (e.g., the gNB 104) the trace session switching configuration. The trace session switching configuration may be provided in response to a switching request, which is received from the network node responsive to detection by the network node of the abovementioned trigger condition. Alternatively, the trace session switching configuration may be provided by the network management system to the network node with the trace session activation which may be prior to detection by the network node of the abovementioned trigger condition and the network node may provide information from the trace session switching configuration in response to the trigger condition. In some examples, therefore, a network node (e.g., the gNB 104) may be provided, the network node being configured to receive a trace session switching configuration from a network management system (e.g., the MaS 106 or another entity) which may be in response to the network node transmitting a switching request to the network management system in response to detecting of the abovementioned trigger condition. Alternatively, the network node may be configured to receive the trace session switching configuration from the network management system with the trace session activation which may be prior to detection by the gNB 104 of the abovementioned trigger condition and the network node may provide information from the trace session switching configuration in response to the trigger condition. Example apparatus FIG. 17 illustrates a set of apparatus 1600 and 1620 according to certain example embodiments. In certain example embodiments, the apparatus 1600 may be a device in a communications network or associated with such a network, such as a UE, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, or other device. It should be noted that one of ordinary skill in the art would understand that apparatus 1600 may include components or features not shown in FIG. 17. In some example embodiments, apparatus 1600 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some example embodiments, apparatus 1600 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatus 1600 may include components or features not shown in FIG. 17. As illustrated in the example of FIG. 17, apparatus 1600 may include or be coupled to a processor 1602 for processing information and executing instructions or operations. Processor 1602 may be any type of general or specific purpose processor. In fact, processor 1602 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 1602 is shown in FIG. 17, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 1600 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 1602 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster). Processor 1602 may perform functions associated with the operation of apparatus 1600 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 1600, including processes illustrated in the flow diagrams. Apparatus 1600 may further include or be coupled to a memory 1604 (internal or external), which may be coupled to processor 1602, for storing information and instructions that may be executed by processor 1602. Memory 1604 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memory 1604 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 1604 may include program instructions or computer program code that, when executed by processor 1602, enable the apparatus 1600 to perform tasks as described herein. In certain example embodiments, apparatus 1600 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 1602 and / or apparatus 1600 to perform any of the methods illustrated in flow diagrams described herein. In some example embodiments, apparatus 1600 may also include or be coupled to one or more antennas 1605 for receiving a downlink signal and for transmitting via an uplink from apparatus 1600. Apparatus 1600 may further include a transceiver 1608 configured to transmit and receive information. The transceiver 1608 may also include a radio interface (e.g., a modem) coupled to the antenna 1605. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink. For instance, transceiver 1608 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 1605 for further processing by other elements of apparatus 1600. In other example embodiments, transceiver 1608 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 1600 may include an input and / or output device (I / O device). In certain example embodiments, apparatus 1600 may further include a user interface, such as a graphical user interface or touchscreen. In certain example embodiments, memory 1604 stores software modules that provide functionality when executed by processor 1602. The modules may include, for example, an operating system that provides operating system functionality for apparatus 1600. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 1600. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatus 1600 may optionally be configured to communicate with apparatus 1620 via a wireless or wired communications link 1670 according to any radio access technology, such as NR. According to certain example embodiments, processor 1622 and memory 1624 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 1628 may be included in or may form a part of transceiving circuitry. For instance, in certain example embodiments, apparatus 1620 may be controlled by memory 1624 and processor 1622 to perform certain operations described above. As illustrated in the example of FIG. 17, apparatus 1620 may be a network, core network element, or element in a communications network or associated with such a network, such as a gNB. It should be noted that one of ordinary skill in the art would understand that apparatus 1620 may include components or features not shown in FIG. 17. As illustrated in the example of FIG. 17, apparatus 1620 may include a processor 1622 for processing information and executing instructions or operations. Processor 1622 may be any type of general or specific purpose processor. For example, processor 1622 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 1622 is shown in FIG. 17, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 1620 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 1622 may represent a multiprocessor) that may support multiprocessing. In certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster). According to certain example embodiments, processor 1622 may perform functions associated with the operation of apparatus 1620, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes illustrated in the above described flow diagrams. Apparatus 1620 may further include or be coupled to a memory 1624 (internal or external), which may be coupled to processor 1622, for storing information and instructions that may be executed by processor 1622. Memory 1624 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memory 1624 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memory 1624 may include program instructions or computer program code that, when executed by processor 1622, enable the apparatus 1620 to perform tasks as described herein. In certain example embodiments, apparatus 1620 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 22 and / or apparatus 20 to perform the methods illustrated in the above-described flow diagrams. In certain example embodiments, apparatus 1620 may also include or be coupled to one or more antennas 1625 for transmitting and receiving signals and / or data to and from apparatus 1620. Apparatus 1620 may further include or be coupled to a transceiver 1628 configured to transmit and receive information. The transceiver 1628 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 1625. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink). As such, transceiver 1628 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 1625 and demodulate information received via the antenna(s) 1625 for further processing by other elements of apparatus 20. In other example embodiments, transceiver 1628 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 1620 may include an input and / or output device (I / O device). In certain example embodiment, memory 1624 may store software modules that provide functionality when executed by processor 1622. The modules may include, for example, an operating system that provides operating system functionality for apparatus 1620. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 1620. The components of apparatus 1620 may be implemented in hardware, or as any suitable combination of hardware and software. According to some example embodiments, processor 1622 and memory 1624 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceiver 1628 may be included in or may form a part of transceiving circuitry. As used herein, the term "circuitry" may refer to hardware-only circuitry implementations (e.g., analog and / or digital circuitry), combinations of hardware circuits and software, combinations of analog and / or digital hardware circuits with software / firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to cause an apparatus (e.g., apparatus 1600 and 1620) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term "circuitry" may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device. A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus. As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium. In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 1600 or apparatus 620), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network. According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation. One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and / or fourth generation (4G) technology.

Claims

1. A user device, comprising:means for receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node;means for receiving, from the network node, second information comprising at least a trace session activation configuration;means for, based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, reporting of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over the UP.

2. The user device of claim 1, whereinthe reporting of the measurement data directly to the data collection entity is provided in a trace report.

3. The user device of claim 1 or claim 2, whereinthe UP transmission flag comprises an identifier linked to the trace session activation configuration; andthe reporting of the logged measurement data is further based on the identifier being linked to the trace session activation configuration,wherein optionallythe UP transmission flag comprises a first UP transmission flag associated with at least a first measurement and reporting configuration and comprises a first identifier linked to the trace session activation configuration;a second, different transmission flag is associated with at least a second measurement and reporting configuration and comprises a second identifier linked to a different trace session activation configuration; andthe reporting of the logged measurement data comprises reporting of the logged measurement data associated with the at least first measurement and reporting configuration and not reporting of logged measurement data associated with the at least second measurement and reporting configuration.

4. The user device of any preceding claim, whereinthe second information further comprises at least a network address of the data collection entity for enabling the user device to report the logged measurement data directly to the data collection entity.

5. The user device of any preceding claim, whereinthe first information is received at a first time and the second information is received at a second, subsequent, time after the user device transitions from the idle or inactive mode of operation to the connected mode of operation.

6. The user device of claim 5, whereinthe means for the reporting of the logged measurement data is configured to report a first set of the logged measurement data to the network node over a control plane, CP, media access control, MAC, or Physical Layer, PHY, andin response to receiving the second information at the second time, the means for reporting of the logged measurement data is configured to switch from reporting the logged measurement data to the network node over the CP, MAC or PHY to reporting at least a second, and subsequent, set of the logged measurement data directly to the data collection entity.

7. The user device of any of claims 1 to 4, whereinthe first information and the second information are received at substantially the same time.

8. The user device of any preceding claim, whereinthe logged measurement data is associated with a first trace reference; andthe second information further comprises an indication of at least one of:the first trace reference;a second trace reference derived from the first trace reference; ora third trace reference capable of being associated with the first trace reference at the data collection entity.

9. The user device of claim 8, whereinthe indication is reported with the logged measurement data directly to the data collection entity.10.The user device of any preceding claim, further comprising:means for detecting at least one terminating event;means for, in response to detecting the at least one terminating event, and based on the measurement and reporting configuration being associated with the UP transmission flag, terminating the reporting of the logged measurement data directly to the data collection entity and commencing or re-commencing of the reporting of the logged measurement data to the network node over a CP, MAC or PHY.11.The user device of claim 10, whereinthe at least one terminating event comprises at least one of:expiry of a time period at the user device;the user device meeting a first threshold number of measurements or measurements reports of the logged measurement data reported directly to the data collection entity; orthe user device receiving of a deactivation message from the, or another, network node.12.The user device of claim 11, whereinthe at least one terminating event comprises the receiving of the deactivation message from the, or another, network node, andthe deactivation message comprises a deactivation configuration for reconfiguring the user device to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence of the reporting of the measurement data to the network node over the CP, MAC or PHY.

13. The user device of claim 11 or claim 12, whereinthe means for detecting the at least one terminating event is configured, at least in part, based on the second information.

14. The user device of any preceding claim, further comprising:means for establishing a protocol data unit, PDU, session with a data network associated with the data collection entity; andmeans for activating a UP connection of the PDU session,wherein the reporting of the logged measurement data directly to the data collection entity is performed using the UP connection of the PDU session.

15. A network node, comprising:means for transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; andmeans for transmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the at least one measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP.

16. The network node of claim 15, further comprising:means for receiving, from a network management system, third information comprising at least a trace session switching configuration; andmeans for determining the second information comprising the at least trace session activation configuration based at least in part on the third information,wherein optionally the third information is received in response to a request transmitted by the network node to the network management system.

17. The network node of claim 15 or claim 16, whereinthe logged measurement data is associated with a first trace reference; andthe second information further comprises an indication of at least one of:the first trace reference;a second trace reference derived from the first trace reference; ora third trace reference capable of being associated with the first trace reference at the data collection entity.

18. The network node of any of claims 15 to 17, further comprising:means for configuring or causing the user device to detect at least one terminating event for causing the user device, upon detecting of the at least one terminating event, to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence the reporting of the logged measurement data to the network node over a control plane, CP, media access control, MAC or Physical Layer, PHY.

19. The network node of claim 18, whereinthe at least one terminating event comprises at least one of:expiry of a time period at the user device;the user device meeting a first threshold number of measurements or measurements reports of the logged measurement data reported directly to the data collection entity; orthe user device receiving a deactivation message from the network node.

20. The network node of claim 19, whereinthe means for configuring or causing the user device to detect the at least one terminating event network node is configured to transmit the deactivation message to the user device, the deactivation message comprising a deactivation configuration for reconfiguring the user device to terminate the reporting of the logged measurement data directly to the data collection entity and commence or re-commence of the reporting of the logged measurement data to the network node over the CP, MAC or PHY.

21. The network node of any of claims 15 to 20, further comprising: means for detecting at least one trigger condition, wherein the second information is transmitted responsive to the detecting of the at least one trigger condition.

22. The network node of claim 21, whereinthe at least one trigger condition is associated with a performance metric of the network node and / or of a radio access network, RAN, of which the network node forms a part.

23. The network node of claim 22, whereinthe at least one trigger condition is associated with at least one of: an overload condition associated with the network node;a number of measurement reports received by the network node meeting a first threshold;an average delay for receiving measurement reports by the network node meeting a second threshold;an average delay for receiving a critical measurement reports by the network node meeting a third threshold;- a throughput required to report measurement reports received by the network node to the, or another, data collection entity meeting a fourth threshold.

24. A method of a user device, comprising:receiving, from a network node, first information comprising a user plane, UP, transmission flag providing an indication to report logged measurement data associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity which is other than the network node;receiving, from the network node, second information comprising at least a trace session activation configuration;reporting, based on receiving of the trace session activation configuration, and on the at least one measurement and reporting configuration being associated with the UP transmission flag, of the logged measurement data, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation such that the logged measurement data is reported directly to a data collection entity which is other than the network node and over the UP.

25. A method of a network node, comprising:transmitting, to a user device, first information comprising a user plane, UP, transmission flag providing an indication for the user device to report logged measurement data, associated with at least one measurement and reporting configuration, over the UP, and directly to a data collection entity; andtransmitting, to the user device, second information comprising at least a trace session activation configuration for activating the user device to report the logged measurement data, associated with the measurement and reporting configuration, after the user device transitions from an idle or inactive mode of operation to a connected mode of operation, directly to the data collection entity and over the UP.57

Images