ALLOWS THE COLLECTION OF MEASUREMENTS

Abstract

The invention relates to a network node in a communication network configured to determine when to allow the collection of measurements. The network node can receive (810, 910) configuration information including indications of whether a particular type of information is subject to user consent. The network node can receive further (820, 920) requests to measure that particular type of information. The network node further determines (830, 930) whether a particular type of information is subject to user consent based on the configuration information.

Description

ALLOWING COLLECTION OF MEASUREMENTSTECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to allowing collection of measurements.BACKGROUND

[0002] FIG. 1 illustrates an example of current 5thgeneration radio access network (“NG- RAN”) architecture. The NG-RAN architecture can be further described as follows. The NG- RAN includes a set of 5thgeneration (“5G”) base stations (referred to herein as gNBs) connected to the 5thgeneration core network (“5GC”) through the next generation (“NG”) interface. A gNB can support frequency division duplex (“FDD”) mode, time division duplex (“TDD”) mode or dual mode operation. gNBs can be interconnected through the Xn-C interface. A gNB can include a gNB-central unit (“CU”) and gNB-distributed units (“DUs”). A gNB-CU and a gNB- DU are connected via a Fl logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, a gNB-DU may be connected to multiple gNB-CU by appropriate implementation. NG, Xn-C, and Fl are logical interfaces. The NG-RAN is layered into a Radio Network Layer (“RNL”) and a Transport Network Layer (“TNL”). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (e g., NG, Xn-C, and Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.

[0003] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB including a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0004] A gNB may also be connected to a long term evolution (“LTE”) base station (referred to herein as an eNB) via an X2 interface. Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB. The latter is a gNB not connected directly to a core network (“CN”) and connected via X2 to an eNB for the sole purpose of performing dual connectivity.

[0005] The architecture in FIG. 1 can be expanded by splitting the gNB-CU into two entities. One gNB-CU-user plane (“UP”), which serves the user plane and hosts the packet data convergence protocol (“PDCP”) and one gNB-CU-control plane (“CP”), which serves the control plane and hosts the PDCP and radio resource control (“RRC”) protocol. A gNB-DUhosts the radio link control (“RLC”) / media access control (“MAC”) / physical layer (“PHY”) protocols.

[0006] Other standardization groups, such as the open radio access network (“ORAN”), have further extended the architecture above and have for example split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU can include the PHY protocol and the radio frequency (“RF”) parts, the upper node of the split gNB- DU can host the RLC and MAC. In ORAN the upper node is called O-DU, while the lower node is called O-RU.

[0007] An NG-RAN can also include a set of ng-eNBs, an ng-eNB can include an ng-eNB- CU and one or more ng-eNB-DU(s). An ng-eNB-CU and an ng-eNB-DU can be connected via a W1 interface. While this disclosure may refer generally to gNBs, the general principles may apply to other radio access technologies, for example, the principles may apply to a ng-eNB and W1 interface.

[0008] FIG. 2 illustrates an example of an architecture for separation of gNB-CU-CP and gNB-CU-UP. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB- DUs. The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU- UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.

[0009] In dual connectivity a UE capable of multiple transmission / receptions, may be connected to more than one RAN node. The RAN nodes may be of the same RAT (both master node and secondary node in NR or LTE respectively) or different RATs, for example one master LTE node and one secondary NR node.SUMMARY

[0010] According to some embodiments, a method of operating a network node in a communications network is provided. The method includes receiving configuration information including an indication of whether a specific type of information is subject to user consent. The method further includes receiving a request to measure the specific type of information. The method can further include determining whether the specific type of information is subject to user consent based on the configuration information.

[0011] According to additional embodiments, the configuration information comprises an indication of which minimization drive test (“MDT”) measurements are subject to user consent.The specific type of information comprises a specific type of MDT measurement

[0012] According to additional or alternative embodiments, the configuration information comprises an explicit list of MDT measurements that are subject to user consent. Determining whether the specific type of information is subject to user consent comprises determining whether the specific type of MDT measurement is included in the list of MDT measurements that are subject to user consent.

[0013] According to additional or alternative embodiments, the configuration information comprises an explicit list of MDT measurements that are not subject to user consent.Determining whether the specific type of information is subj ect to user consent comprises determining whether the specific type of MDT measurement is included in the list of MDT measurements that are not subject to user consent.

[0014] According to additional or alternative embodiments,, the network node is a core network (“CN”) configured to provide an access and mobility management function (“AMF”).

[0015] According to additional or alternative embodiments, receiving the configuration information comprises at least one of: receiving, by the AMF, the configuration information from operation and maintenance (“0AM”); and receiving, by the AMF, the configuration information from a radio access network (“RAN”) node.

[0016] According to additional or alternative embodiments, the method further includes transmitting, by the AMF, a message to a radio access network (“RAN”) node, the message including an indication of a public land mobile network (“PLMN”) where a minimization drive test (“MDT”) can be collected.

[0017] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is not subject to user consent. The method further includes responsive to determining that the specific type of information is not subject to user consent, transmitting, by the AMF, a request to collect the specific type of information associated with a communication device.

[0018] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent. The method further includes, responsive to determining that the specific type of information is subject to user consent, determining that the user consent has been received. The method further includes, responsive to determining that the user consent has been received, transmitting, by the AMF, a request to collect the specific type of information associated with a communication device.

[0019] According to additional or alternative embodiments, transmitting the request tocollect the specific type of information comprises transmitting a Trace Activation information element, IE, including a minimization drive test (“MDT”) public land mobile network (“PLMN”) list IE.

[0020] According to additional or alternative embodiments, the method further includes determining the MDT PLMN list IE based on parameters retrieved from a unified data management (“UDM”).

[0021] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent. The method further includes, responsive to determining that the specific type of information is subject to user consent, determining that the user consent has not been received. Responsive to determining that the user consent has not been received, avoiding measurement of the specific type of information.

[0022] According to additional or alternative embodiments, the network node is a radio access network (“RAN”) node. Receiving the configuration information comprises receiving, by the RAN node, the configuration information from operation and maintenance (“0 AM”).

[0023] According to additional or alternative embodiments, the method further includes receiving, by the RAN node, a message from an access and mobility management (“AMF”) the message including an indication of a public land mobile network (“PLMN”) where a minimization drive test (“MDT”) can be collected.

[0024] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is not subject to user consent. The method further includes, responsive to determining that the specific type of information is not subject to user consent, selecting, by the RAN node, a communication device to measure the specific type of information.

[0025] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent. The method further includes, responsive to determining that the specific type of information is subject to user consent, determining that the user consent has been received for a subscriber associated with a communication device. The method further includes, responsive to determining that the user consent has been received for the subscriber associated with the communication device, selecting, by the RAN node, the communication device to measure the specific type of information.

[0026] According to additional or alternative embodiments, determining that the user consent has been received for the subscriber associated with the communication device comprises determining that the user consent has been received for the subscriber associated withthe communication device based on a minimization dnve test (“MDT”) public land mobile network (“PLMN”) list information element (“IE”) received from the AMF.

[0027] According to additional or alternative embodiments, selecting, by the RAN node, the communication device to measure the specific type of information comprises transmitting a minimization drive test (“MDT”) public land mobile network (“PLMN”) list information element (“IE”) to the communication device.

[0028] According to additional or alternative embodiments, determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent. The method further includes, responsive to determining that the specific type of information is subject to user consent, determining that the user consent has not been received for a subscriber associated with a communication device.The method further includes, responsive to determining that the user consent has not been received for the subscriber associated with the communication device, avoiding measurement of the specific type of information in association with the communication device.

[0029] According to additional or alternative embodiments, determining that the user consent has not been received for the subscriber associated with the communication device comprises determining that the user consent has not been received for the subscriber associated with the communication device based on a minimization drive test (“MDT”) public land mobile network (“PLMN”) list information element (“IE”) received from the AMF.

[0030] According to other embodiments, a communication device, a RAN node, a CN node, an AMF, a computer program, a computer program product, a non-transitory computer readable medium, a host, or a system is provided to perform the above method.

[0031] Certain aspects of the disclosure and their embodiments may provide technical advantages. In some embodiments, signaling and management based MDT enable the collection of MDT measurements not subject to user consent also for UEs whose user did not give consensus to the MDT data collection. This allows operators to collect mass scales of useful measurements, which can be employed for network monitoring and optimization, without incurring in data sample limitations due to a large portion of user not giving user consent. The latter enables to use the MDT feature in a consistent way, where the measurements can achieve statistical validity, hence making MDT an always available tool for monitoring and optimization of network performance.

[0032] Additional or alternative embodiments ensure that the UE behavior is kept unchanged. This has the advantage of making the new MDT user consent solution applicable to all the population of legacy UEs. The latter is an essential aspect of MDT, which is based on mass collection of data to achieve a statistically valid representation of the network,essential to determine root causes of performance and configuration issues across the network deployment.BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0034] FIG. 1 is a schematic diagram illustrating an example of a next generation radio access network (“NG-RAN”) overall architecture;

[0035] FIG. 2 is a schematic diagram illustrating an example of an overall architecture for separation of a gNB-central unit-control plane (“CU-CP”) and gNB-central unit-user plane (“CU-UP”);

[0036] FIG. 3 is a signaling flow diagram illustrating an example of signaling based MDT activation involving El and Fl;

[0037] FIG. 4 is a signaling flow diagram illustrating an example of management based MDT activation in gNB-CU-CP;

[0038] FIG. 5 is a signaling flow diagram illustrating an example of management based MDT activation in gNB-DU;

[0039] FIG. 6 is a signaling flow diagram illustrating an example of management based MDT activation in gNB-CU-UP;

[0040] FIG. 7 is a table illustrating an example of information the CN can retrieve from a subscriber database in accordance with some embodiments;

[0041] FIG. 8 is a flow chart illustrating an example of operations performed by an AMF in accordance with some embodiments;

[0042] FIG. 9 is a flow chart illustrating an example of operations performed by a RAN node in accordance with some embodiments;

[0043] FIG. 10 is a block diagram of a communication system in accordance with some embodiments;

[0044] FIG. 11 is a block diagram of a user equipment in accordance with some embodiments; and

[0045] FIG. 12 is a block diagram of a network node in accordance with some embodiments.DETAILED DESCRIPTION

[0046] Some of the embodiments contemplated herein will now be described more fullywith reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0047] The Third Generation Partnership Project (“3GPP”) is discussing how to improve minimization of drive test (“MDT”) user consent mechanisms to enable collection of MDT measurements for which local laws and regulations do not require the user to provide user consent It has been concluded that the Operation and Maintenance (“0AM”) needs to configure the RAN with information about the MDT measurements that are subject to user consent. Furthermore, it has been concluded that UEs should not be impacted by the MDT user consent enhancements.

[0048] MDT is being standardized for new radio (“NR”) starting in Rel-16 to reduce the amount of drive tests performed manually. It is a user equipment (“UE”) (also referred to herein as communication device) assisted framework where network measurements are collected by UEs in a RRC IDLE state, a RRC INACTIVE state or a RRC CONNECTED state, in order to aid the network in gathering valuable information

[0049] In general, there are two types of MDT measurement logging: Logged MDT for UEs in RRC IDLE / RRC INACTIVE state and Immediate MDT for UEs in RRC CONNECTED state.

[0050] The existing trace / MDT framework enables two methods of activating MDT and collecting data from the UEs: Management based MDT and Signalling based MDT.

[0051] In Management based MDT, the MDT data is collected from UEs in a specified area. The area is defined as a list of cells or as a list of tracking / routing / location areas. The management based MDT is an enhancement of the management based trace functionality. Management based MDT can be either a logged MDT or Immediate MDT.

[0052] In Signalling based MDT, the MDT data is collected from one specific UE. The UE that is participating in the MDT data collection is specified as international mobile equipment identity software version (“IMEI(SV)”) or as international mobile subscriber identity (“IMSI”). The signalling based MDT is an enhancement of the signalling based subscriber and equipment trace. A signalling based MDT can be either a logged MDT or Immediate MDT.

[0053] There are two cases that RAN should initiate a MDT measurements collection task.One is that the MDT task is initiated without targeting a specific UE by the cell traffic trace (e.g., management based trace function from OAM). The other is that the MDT task is initiated towards a specific UE by the signaling trace activation messages from CN nodes (e.g., the Initial Context Setup message, the Trace Start message or the Handover request message in an evolved universal mobile telecommunications system terrestrial radio access network (“E-UTRAN”), NR, or the core network (“CN”) Invoke Trace message in UTRAN).

[0054] For signaling based MDT, the CN shall not initiate MDT towards a particular user unless it is allowed.

[0055] For management based MDT, the CN indicates to the RAN whether MDT is allowed to be configured by the RAN for this user considering (e.g., user consent and roaming status), by providing management based MDT allowed information. For E-UTRAN / UTRAN, the MDT allowed information includes the Management Based MDT Allowed indication and optionally the Management Based MDT public land mobile network (“PLMN”) List. For NR, the MDT allowed information only includes the Management Based MDT PLMN List. The management based MDT allowed information propagates during inter-PLMN handover or inter-PLMN UE context retrieval if the Management Based MDT PLMN List is available and includes the target PLMN.

[0056] A UE is configured with an MDT PLMN List only if user consent is valid for the registered PLMN (“RPLMN”).

[0057] A MDT PLMN List can be a list of PLMNs where MDT is allowed for a user. It is a subset of the EPLMN list and RPLMN at the time when MDT is initiated. A management based MDT PLMN List can be a MDT PLMN List applicable to management based MDT. A signaling based MDT PLMN List can be a MDT PLMN List applicable to signaling based MDT.

[0058] Signaling based MDT activation is described below and illustrated in FIG. 3, which is a signaling flow for signaling based MDT activation involving El and FL

[0059] At block 310, the AMF starts a trace session and sends a TRACE START message to the gNB. The AMF shall consider the MDT user consent information when activating an MDT trace session for the UE. TRACE START message includes the parameters for configuring MDT measurements.

[0060] At block 320, the gNB-CU-CP decides if the gNB-CU-UP, or the gNB-DU, or both, should be involved in the MDT measurement. If the gNB-CU-UP should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters (block 322). If the gNB-DU should be involved in the MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-DU, includingMDT configuration parameters (block 324).

[0061] Management based MDT activation is described below and illustrated in FIGS. 4-6. Management Based Trace Activation towards a gNB-CU-CP, gNB-CU-UP or a gNB-DU can be fulfilled with the Cell Traffic trace functionality. The following description is valid for both an en-gNB and a gNB.

[0062] If the MDT measurement is initiated by the EM towards the gNB-CU-CP, and if the activation involves measurements collected by multiple nodes under the same gNB-CU-CP control in a split RAN architecture, the EM sends MDT measurement activation to the gNB-CU- CP and the gNB-CU-CP may further decide which gNB-DU(s) or which gNB-CU-UP(s) to perform the MDT measurement.

[0063] When gNB-CU-CP or a gNB-DU receive the Trace Session Activation message from the management system for a given cell or a list of cell(s) under its control, the gNB-CU- CP or gNB-DU shall start a Trace Session for the given cell or list of cell(s). For Management Based MDT sent directly to a gNB-CU-UP, no MDT Area Configuration (apart from PLMN IDs) is to be included in the MDT activation indication.

[0064] The signaling flows for management based MDT activation in gNB-CU-CP, gNB- DU and gNB-CU-UP are shown in FIGS. 4-6 respectively.

[0065] FIG. 4 illustrates an example of a signaling flows for management based MDT activation in gNB-CU-CP.

[0066] At block 410, the EM sends a Trace Session activation request to the gNB-CU-CP. This request includes the parameters for configuring UE measurements.

[0067] At block 420, the gNB-CU-CP shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-CP for MDT data collection.

[0068] For each selected UE, if the gNB-CU-UP should perform MDT measurement, the gNB-CU-CP sends TRACE START message to the gNB-CU-UP, including MDT configuration parameters (block 422).

[0069] For each selected UE, if the gNB-DU should perform MDT measurement, the gNB- CU-CP sends TRACE START message to the gNB-DU, including MDT configuration parameters (block 424).

[0070] The gNB-CU-CP may send CELL TRAFFIC TRACE message to the AMF for the selected UE, including Trace ID for MDT (block 426). The AMF forwards Trace ID and other information to the TCE.

[0071] If the UE reports an indication of measurement pollution, the gNB-CU-CP shall, ifsupported, include such indication as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements.

[0072] FIG. 5 illustrates an example of a signaling flows for management based MDT activation in gNB-DU.

[0073] At block 510, the gNB-CU-CP sends UE CONTEXT SETUP REQUEST message to the gNB-DU, including Management based MDT PLMN List. The message may include the Polluted Measurement Indicator IE. If the gNB-DU has received the Polluted Measurement Indicator IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE, so that the TCE is able to correlate and filter the affected measurements.

[0074] At block 520, the gNB-DU sends UE CONTEXT SETUP RESPONSE message to the gNB-CU-CP

[0075] At block 530, the EM sends a Trace Session activation request to the gNB-DU. This request includes the parameters for configuring UE measurements.

[0076] At block 540, the gNB-DU shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-DU for MDT data collection.

[0077] For each selected UE, the gNB-DU may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the Fl UE associated signalling, including Trace ID for MDT (block 550).

[0078] At block 560, upon reception of a CELL TRAFFIC TRACE message from Fl, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE.

[0079] FIG. 6 illustrates an example of a signaling flows for management based MDT activation in gNB-CU-UP.

[0080] At block 610, the gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP, including Management based MDT PLMN List. The message may include Polluted Measurement Indicator. If the gNB-DU has received the Polluted Measurement Indicator IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements.

[0081] At block 620, the gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP.

[0082] At block 630, the EM sends a Trace Session activation request to the gNB-CU-UP. This request includes the parameters for configuring UE measurements.

[0083] At block 640, the gNB-CU-UP shall select the suitable UEs for MDT datacollection. If the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-UP for MDT data collection.

[0084] For each selected UE, the gNB-CU-UP may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the El UE associated signalling, including Trace ID for MDT (block 650).

[0085] At block 660, upon reception of a CELL TRAFFIC TRACE message from El, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE.

[0086] The 3GPP describes the measurements that can be collected via MDT in a “List of Measurements” parameter. This parameter is mandatory if the Job Type is configured for Immediate MDT or combined Immediate MDT and Trace. This parameter defines the measurements that shall be collected. The parameter is a 4 octet long bitmap.

[0087] The parameter can have the following values in UMTS:• Ml : CPICH RSCP and CPICH Ec / No measurement by UE;• M2: For 1.28 Mcps TDD, P-CCPCH RSCP and Timeslot ISCP measurement by UE;• M3: SIR and SIR error (FDD) by NodeB;• M4: UE power headroom (UPH) by the UE, applicable for E-DCH transport channels;• M5: Received total wideband power (RTWP) by Node B;• M6: Data Volume measurement, separately for DL and UL, by RNC;• M7 : Throughput measurement, separately for DL and UL, per RAB and per UE, by RNC; and• Any combination of the above.

[0088] The parameter can have the following values in LTE:• Ml : RSRP, RSRQ and SINR measurement by UE;• M2: Power Headroom (PH) measurement by UE (NOTE: Available from MAC layer);• M3: Received Interference Power measurement by eNB;• M4: Data Volume measurement separately for DL and UL, per QCI per UE, by eNB;• M5: Scheduled IP Throughput measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB;• M6: Packet Delay measurement, separately for DL and UL, per QCI per UE, see UL PDCP Delay, by the UE, and Packet Delay in the DL per QCI, by the eNB;• M7 : Packet Loss rate measurement, separately for DL and UL per QCI per UE, by the eNB• M8: RSSI measurement by UE for WLAN and Bluetooth®-• M9: RTT measurement by UE only for WLAN; and• Any combination of above.

[0089] The parameter can have the following values in NR:• Ml : DL signal quantities measurement results for the serving cell and for intra- frequency / Inter-frequency / inter-RAT neighbour cells, including cell / beam level measurement by UE;• M2: Power headroom (PH) measurement by UE;• M3 is not supported by this release;• M4: PDCP SDU Data volume measurement separately for DL and UL, per DRB per UE by gNB;• M5: Average UE throughput measurement separately for DL and UL, per DRB per UE ;and per UE for the DL, per DRB per UE and per UE for the UL, by gNB;• M6: Packet delay measurement, separately for DL and UL, per DRB per UE by gNB;• M7: Packet loss rate measurement, separately for DL and UL, per DRB per UE by gNB;• M8: RSSI measurement by UE for WLAN and Bluetooth®;• M9: RTT measurement by UE for WLAN; and• any combination of above.

[0090] There currently exist certain challenges. Some procedures are provided to enable the configuration at the RAN of MDT measurements that do not require user consent.However, these procedures are limited because of a number of reasons. In some examples, for signaling based MDT, it is not the RAN but the AMF that performs checks on whether a user has provided or revoked user consent for the collection of MDT measurements subject to user consent. Hence configuring the RAN with the list of measurements that are subject to user consent does not allow the AMF to perform the right checks. In additional or alternative examples, some procedures do not specify how to configure the UE with a plmn-IdentityList at RRC level, where the plmn-IdentityList is used by the UE to determine where to report logged MDT results.

[0091] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Various embodiments herein propose a procedure for signaling based MDT and management based MDT, to allow that user consent only applies to predetermined / (pre)-configured MDT measurements and that enables / disables collection of measurements that are not subject to user consent without any dependency on whether the user gave consent or not.

[0092] In some embodiments, for management based MDT, the RAN is configured by the 0AM with the MDT measurements that are subject to user consent and the RAN checkswhether the Management Based MDT configuration received from the OAM contains any such measurements requiring user consent. In additional or alternative embodiments, where the MDT configuration does not include any measurement subject to user consent, the RAN does not need to select UEs on the basis of whether user consent was given. Instead, any UE can be selected for such MDT configuration, even UEs whose users did not provide user consent. Given that management based MDT user consent is indicated to the RAN in the form of signaling of an Management Based MDT PLMN List IE over the available interfaces, such as over the NG, Xn, Fl, El, it might occur that RAN nodes to not receive the Management Based MDT PLMN List because the user associated to the UE did not give consent. However, such a user can still be selected for Management Based MDT configuration if the MDT configuration does not include any measurement subject to user consent. In this case, and if the MDT configuration includes Logged MDT measurements, the UE is configured by the RAN with a plmn-IdentityList that can be derived in one of the following ways.

[0093] In some examples, the plmn-IdentityList can be derived on the basis of the PLMNs the UE can access. This information is known to the RAN by means of the Mobility Restriction List received from the CN. Hence the plmn-IdentityList can be derived on the basis of the Mobility Restriction List.

[0094] In additional or alternative examples, the plmn ldentityList can be derived on the basis of the PLMN List included in the Management Based MDT configuration received by the RAN node.

[0095] In additional or alternative examples, the plmn IdentityList can be derived by means of operator provided policies which are configured to the RAN and that spell out the list of PLMNs that should be included in the plmn-IdentityList.

[0096] In additional or alternative embodiments, for signaling based MDT, a Core Network (“CN”) node (e.g., configured to provide the AMF) is configured by the OAM with the MDT measurements that are subject to user consent and that the CN checks whether the Signaling Based MDT configuration received from the OAM contains any such measurements requiring user consent. In some examples, where the MDT configuration does not include any measurement subject to user consent, the CN does not need to trigger a Trace Activation for the specific UE on the basis of whether user consent was given. Instead, a Trace Activation can be triggered even if no user consent was given by the user corresponding to the UE.

[0097] In additional or alternative embodiments, given that user consent check for signaling based MDT is performed at the CN, e.g. at the AMF, the methods propose that the Signaling Based MDT PLMN List IE is always signaled to the RAN when a Trace Activation is signaled, so that the RAN has information to configure the plmn-IdentityList at the UE.

[0098] In additional or alternative embodiments, for management based MDT and / or for signaling based MDT, the RAN (or one of a gNB-CU-CP, a gNB-DU, a gNB-CU-UP) is configured by the 0AM with MDT measurements not subject to user consent and that the RAN, (or one of a gNB-CU-CP, a gNB-DU, a gNB-CU-UP) can initiate or terminated MDT measurements not subject to user consent.

[0099] Some embodiments herein refer to a 5G system where the RAN is composed of nodes such as gNBs and where the CN is composed of nodes such as the AMF. These examples are non limiting and the embodiments in this invention can be applied to any network where Minimization of Drive Test (MDT) is supported, such as a 4G network, a 3G network or a 2G network. To map the embodiments described herein to technologies different form 5G, the names of CN and RAN nodes would need to be substituted with the appropriate names of equivalent nodes in the network technology of reference.

[0100] Requirements needed to enhance MDT user consent include that “user consent is given to the operator so that the 3GPP system can be provisioned / configured based on the operator-subscriber agreed permissions stored in UDM to make it feasible for the 3GPP system to comply with local laws and regulations.”

[0101] Operators operate in different jurisdictions, where each jurisdiction may prescribe different rules for the application of consent, for example the information or uses of information that should be governed by user consent. User consent procedures can enable the operators to configure their networks with appropriate checks to allow / disallow the processing (and dissemination) of specific information governed by consent, as determined by local regulation or by the choice of the operator.

[0102] With this respect, current MDT user consent procedures for MDT either allow in full or disallow in full the collection and distribution of ALL MDT measurements defined in 3GPP.

[0103] In many jurisdictions, most MDT measurements defined in 3GPP are not considered sensitive. Measurements like M6: Packet delay measurement; or M7: Packet loss rate measurement; are not considered sensitive in any jurisdiction so far. Therefore, the current MDT procedure should be amended and corrected.

[0104] The RAN checks user consent only for cases of management based MDT. For example, the gNB-CU-CP shall select the suitable UEs for MDT data collection. If the UE is not in the specified area or if the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-CP for MDT data collection. Therefore, it is valuable to clarify that some descriptions are only valid for the case of management based MDT.

[0105] In some embodiments, the 0AM configures the RAN with rules that instruct the RAN on whether user consent needs to be checked for collection and reporting of a specific typeof information / data of a subscriber for a particular purpose. In other words, the OAM tells the RAN which MDT measurements are governed by user consent and for such measurements the RAN needs to check if the user did or did not provide user consent.

[0106] For those measurements that are not configured by the OAM as subject to user consent, such measurement can be collected by the RAN and distributed to the TCE without any user consent check.

[0107] In additional or alternative embodiments, the OAM configures the RAN (or functions within the RAN) with a list of MDT measurements for which the RAN is not requested to check the user consent provided by the users. Hence, the RAN can check the Management Based MDT configuration against these measurements and if the MDT measurements in the management based configuration appear in the list configured by the OAM, the RAN deduces that the measurements can be collected without the presence of user consent.

[0108] In some examples, the OAM chooses not to configure the RAN for user consent check for M6: Packet delay measurement; or M7: Packet loss rate measurement, the reason being that local laws and regulations do not consider such measurements to be sensitive. In this case, the RAN would not need to check if user consent was given when collecting M6 and M7 measurements and when distributing such measurements to the TCE.

[0109] In additional or alternative examples,, the OAM configures the RAN to not perform user consent check for one (or more) MDT measurements.

[0110] For signaling based MDT, it is the AMF that checks whether user consent is in place. For example, the AMF starts a trace session and sends a TRACE START message to the gNB. The AMF shall consider the MDT user consent information when activating an MDT trace session for the UE.

[0111] In some embodiments, for the case of signaling based MDT, the OAM configures the AMF with information indicating whether user consent is required for a specific type of MDT measurement, so to enable the AMF to check whether, upon receiving a Signaling Based MDT configuration for a given UE from the OAM, any of the measurements included in the MDT configuration are subject to user consent and therefore whether triggering a Trace Activation towards the RAN, to activate the Signaling Based MDT configuration towards the UE, is subject to presence of user consent from the user associated to the UE or not.

[0112] In additional or alternative embodiments, the AMF receives information about the MDT measurements subject to user consent via signaling from the RAN. Namely, once the RAN is configured by the OAM about the MDT measurements that are subject to user consent, or equivalently of the MDT measurements that ae not subject to user consent, the RAN can signal such list of measurements to the AMF for example over the NG interface.

[0113] In additional or alternative embodiments, for the case of signaling based MDT, the 0AM configures the AMF in relation to the MDT measurements for which check on user consent is not needed at the AMF. Upon receiving a signaling based MDT configuration, the AMF skips the user consent check for the MDT measurements, if the list of Signaling Based MDT measurements is not subject to user consent, as per configuration received by 0AM.

[0114] In additional or alternative embodiments, the 0AM updates its configuration as the RAN and at the AMF, for measurements that are subject to user consent, or equivalently that are not subject to user consent, in case such list of measurements changes in time.

[0115] In additional or alternative embodiments, if the 0 AM does not configure any measurement that is subject or not subject to user consent at the RAN or AMF, the RAN and AMF shall deduce that all measurements are subject to user consent.

[0116] In some embodiments, for Management Based MDT, the 0AM configures the RAN with rules concerning the MDT measurements that can be collected and distributed to the TCE. Taking the example of configuration of measurements that are subject to user consent, MDT measurements not listed in such 0AM configuration can be collected by the RAN and reported to the TCE without consent from the user. In additional or alternative embodiments, the 0AM configures the RAN with MDT measurements which can be configured without user consent check at the RAN.

[0117] In additional or alternative embodiments, for Signalling Based MDT, the 0AM configures the AMF with rules concerning the MDT measurements that can be collected by the RAN and distributed to the TCE. For MDT configurations containing measurements not listed in such 0AM configuration, the AMF can trigger a Trace Activation towards the RAN and the RAN can collect the MDT measurements and report them to the TCE without consent from the user. In additional or alternative embodiments, the 0AM configures the AMF with MDT measurements which can be configured without user consent check at AMF.

[0118] Operations for Management Based MDT in accordance with some embodiments are described below. In a first operation, the 0AM has configured the RAN with a list of MDT measurements that require user consent. In a second operation, if user consent is available for a UE, the RAN receives from the AMF the Management Based MDT PLMN List IE, which indicates that the UE gave consent for the measurements subject to user consent. In a third operation, the 0AM signals to the NG-RAN a Management Based MDT configuration. In some examples, if the configured MDT data are subject to user consent, the RAN shall select UEs on the basis of the received user consent information represented by the Management Based MDT PLMN List IE. In additional or alternative examples, if the configured MDT data are not subject to user consent, the RAN does not need to consider user consent when selecting UEs. Namely,the RAN can select also UEs for which the Management Based MDT PLMN Lis was not received.

[0119] Operations for Signaling Based MDT in accordance with some embodiments are described below. In a first operation, the 0AM has configured the AMF with a list of MDT measurements that require user consent. In a second operation, the AMF signals to the NG- RAN, on a per UE basis, and separately from the Trace Activation procedure, the Signaling Based MDT PLMN List IE, which specifies the PLMNs where MDT can be collected. In a third operation, the 0AM signals to the AMF a Signaling Based MDT configuration. In some examples, if the configured MDT data are subject to user consent, and if the AMF determines (from data acquired from the UDM) that user consent is available for the UE, the AMF shall trigger a Trace Activation for the UE. In additional or alternative examples, if the configured MDT data are not subject to user consent, the AMF shall trigger a Trace Activation even if user consent is not available for the UE. The trace Activation IE shall include the Signaling Based MDT PLMN List IE in order to enable the RAN to configure the UE with a list of PLMNs, needed to cany out logged MDT measurements, as described below.

[0120] It should be noted that the Signaling Based MDT PLMN List IE is optionally included in the Trace Activation IE, and therefore it cannot currently be assumed that the CN will always signal it to the RAN. Indeed, as per current specifications, the CN determines that there is no user consent for the user associated to the UE involved in the Signalling Based MDT process, the CN currently does not signal the Signalling Based MDT PLMN List IE.

[0121] With respect to the above, it should be noted that the AMF can always retrieve a PLMN List to signal to the RAN as Signaling Based MDT PLMN List. This is possible because the CN can retrieve from the subscriber database the information in FIG. 7.

[0122] The UDM (subscriber's database in 5G) includes two separate IES, one for MDT user consent and another for the MDT Allowed PLMN List. Therefore, if the AMF (CN) retrieves these parameters from the UDM, the AMF can use them to construct and to signal the Signaling Based MDT PLMN List IE to the RAN. Such Signaling Based MDT PLMN List IE can be derived from the mdtAllowedPlmnldList retrieved from the UDM.

[0123] A reason why the Signaling Based MDT PLMN List IE needs to always be included by the AMF towards the RAN is to make Signaling Based MDT work for collection of MDT measurements that do not require user consent in logged MDT. Indeed, this list is needed at the RAN to configure the UE with a plmn-IdentityList over RRC and therefore ensure that the legacy UE behavior is respected and that the solution can be used also by legacy UEs.

[0124] UE Behavior in case of Logged MDT is described below.

[0125] To keep the UE behavior unchanged, an MDT PLMN List (namely the plmn- IdentityList over RRC), which describes where the UE can collect and report logged MDT measurements, can be signaled to the UE for the following two reasons. First, in cases where the configured MDT measurements require user consent, the MDT PLMN List indicates to the UE the list of PLMNs where measurements can be collected and reported to the TCE because the user gave consensus. Second, in cases where the configured MDT measurements do not require user consent, the MDT PLMN List shall still be signalled to the UE, but in this case this list only indicates to the UE the PLMNs where these MDT measurements should be collected and reported, independently of user consent.

[0126] The above currently contradicts with specifications in TS 37.320, which states: “A UE is configured with an MDT PLMN List only if user consent is valid for the RPLMN”.

[0127] One way to overcome this problem is to modify TS 37 320 to state: “A UE is configured with an MDT PLMN List if user consent is valid for the RPLMN, or if the data types of the configured MDT measurements are not subject to user consent.”

[0128] The above change implies that if a MDT configuration includes measurements that are subject to user consent and if the user has not given user consent, the UE will not be configured with an MDT PLMN List.

[0129] However, if an MDT configuration includes measurements that are not subject to user consent, the UE can still be configured with an MDT PLMN List. The UE in this case will report logged MDT measurements accordingly to the configured PLMN List.

[0130] The above ensures that measurements not subject to user consent can still be collected from UEs even if the user did not give consent. At the same time it ensures that no changes to the UE behavior are applied.

[0131] The above UE behavior cannot currently be achieved because the Management / Signaling Based MDT PLMN List may not be signaled to the RAN by the CN. Namely, in today's solution, if a user did not give consensus for MDT measurement collection, the Management / Signaling Based MDT PLMN List may not be signaled from to the RAN.

[0132] To overcome this problem, the some embodiments proposes that, if the RAN receives a Management Based MDT configuration including measurements that are not subject to user consent, and if the RAN has not received from the CN the Management Based MDT PLMN List, the NG-RAN can configure the UE with a MDT PLMN List, namely with the plmn-IdentityList over RRC, which is derived at the RAN.

[0133] In some examples, the NG-RAN derives the MDT PLMN List based on the PLMNs the UE can access. This information is known to the RAN by means of the Mobility Restriction List received from the CN. Hence the plmn-IdentityList can be derived on the basisof the Mobility Restriction List.

[0134] In additional or alternative examples, the NG-RAN derives the MDT PLMN List based onf the PLMN List included in the Management Based MDT configuration received by the RAN node.

[0135] In additional or alternative examples, the NG-RAN derives the MDT PLMN List by means of operator provided policies which are configured to the RAN and that spell out the list of PLMNs that should be included in the plmn-IdentityList.

[0136] In additional or alternative embodiments, for signaling based MDT, the CN always signals the Signaling Based MDT PLMN List to the RAN, either as an independent IE (e.g., as part of UE context setup / update procedures) or included in the Trace Activation IE.

[0137] Operations of the network node 1200 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow charts of FIGS 8-9 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1204 of FIG. 12, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1202, network node 1200 performs respective operations of the flow charts.

[0138] FIG. 8 illustrates an example of operations performed by a CN node configured to provide an AMF.

[0139] At block 810, processing circuitry 1202 receives, via communication interface 1206, configuration information including an indication of whether a specific type of information is subject to user consent.

[0140] At block 820, processing circuitry 1202 receives, via communication interface 1206, a request to measure the specific type of information.

[0141] At block 830, processing circuitry 1202 determines whether the specific type of information is subject to user consent based on the configuration information.

[0142] At block 840, processing circuitry 1202 determines whether the user consent has been received.

[0143] At block 850, processing circuitry 1202 determines the MDT PLMN List IE.

[0144] At block 860, processing circuitry 1202, performs an action associated with the specific type of information.

[0145] FIG. 9 illustrates an example of operations performed by a RAN node.

[0146] At block 810, processing circuitry 1202 receives, via communication interface 1206, configuration information including an indication of whether a specific type of information is subject to user consent.

[0147] At block 820, processing circuitry 1202 receives, via communication interface 1206,a request to measure the specific type of information.

[0148] At block 830, processing circuitry 1202 determines whether the specific type of information is subject to user consent based on the configuration information.

[0149] At block 940, processing circuitry 1202 receives, via communication interface 1206, a MDT PLMN List IE.

[0150] At block 950, processing circuitry 1202 determines whether the user consent has been received.

[0151] At block 960, processing circuitry 1202, performs an action associated with the specific type of information.

[0152] Various operations from the flow charts of FIGS. 8-9 may be optional with respect to some embodiments of RAN nodes, CN node, and related methods.

[0153] Example Embodiments are described below.

[0154] Embodiment 1. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to transmit the user data from the host to the UE: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

[0155] Embodiment 2. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0156] Embodiment 3. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs the following operations to transmit theuser data from the host to the UE: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

[0157] Embodiment 4. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0158] Embodiment 5. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0159] Embodiment 6. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to transmit the user data from the host to the UE: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

[0160] Embodiment 7. The communication system of the previous embodiment, further comprising: the network node; and / or the user equipment.

[0161] Embodiment 8. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE,the client application being associated with the host application.

[0162] Embodiment 9. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to receive the user data from the UE for the host: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

[0163] Embodiment 10. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0164] Embodiment 11. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0165] Embodiment 12. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs the following operations to receive the user data from the UE for the host: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

[0166] Embodiment 13. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0167] FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.

[0168] In the example, the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1010 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.

[0169] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1000 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0170] The UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1010 and other communication devices. Similarly, the network nodes 1010 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1012 and / or with other network nodes or equipment in the telecommunication network 1002 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1002.

[0171] In the depicted example, the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. These connections may be direct or indirect via one or more intermediaiy networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1006 includes one more core network nodes (e.g., core network node 1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF),Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealmg function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0172] The host 1016 may be under the ownership or control of a service provider other than an operator or provider of the access network 1004 and / or the telecommunication network 1002, and may be operated by the service provider or on behalf of the service provider. The host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0173] As a whole, the communication system 1000 of FIG. 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0174] In some examples, the telecommunication network 1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0175] In some examples, the UEs 1012 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004. Additionally,a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0176] In the example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and / or 1012d) and network nodes (e g., network node 1010b). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1010, or by executable code, script, process, or other instructions in the hub 1014. As another example, the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1014 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0177] The hub 1014 may have a constant / persistent or intermittent connection to the network node 1010b. The hub 1014 may also allow for a different communication scheme and / or schedule between the hub 1014 and UEs (e.g., UE 1012c and / or 1012d), and between the hub 1014 and the core network 1006. In other examples, the hub 1014 is connected to the core network 1006 and / or one or more UEs via a wired connection. Moreover, the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection. In some embodiments, the hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1010b. In other embodiments, the hub 1014 may be anon-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0178] FIG. 11 shows a UE 1100 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0179] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infirastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0180] The UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input / output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0181] The processing circuitry 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1110. The processing circuitry 1102 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor(DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1102 may include multiple central processing units (CPUs).

[0182] In the example, the input / output interface 1106 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1100. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0183] In some embodiments, the power source 1108 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1108 may further include power circuitry for delivering power from the power source 1108 itself, and / or an external power source, to the various parts of the UE 1100 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1108. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1108 to make the power suitable for the respective components of the UE 1100 to which power is supplied.

[0184] The memory 1110 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memoiy (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth In one example, the memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. The memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems.

[0185] The memory 1110 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, externalhard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1110 may allow the UE 1100 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1110, which may be or comprise a device-readable storage medium.

[0186] The processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112. The communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1118 and / or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0187] In the illustrated embodiment, communication functions of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communicab on function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0188] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0189] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0190] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / wmdow sensor, a flood / moisture sensor, an electncal door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1100 shown in FIG. 11.

[0191] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As oneparticular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0192] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0193] FIG. 12 shows a network node 1200 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0194] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0195] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0196] The network node 1200 includes a processing circuitry 1202, a memory 1204, acommunication interface 1206, and a power source 1208. The network node 1200 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1200 comprises multiple separate components (e g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1200 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1200.

[0197] The processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1200 components, such as the memory 1204, to provide network node 1200 functionality.

[0198] In some embodiments, the processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuity 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.

[0199] The memory 1204 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memorydevices that store information, data, and / or instructions that may be used by the processing circuitry 1202. The memory 1204 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1202 and utilized by the network node 1200. The memory 1204 may be used to store any calculations made by the processing circuitry 1202 and / or any data received via the communication interface 1206. In some embodiments, the processing circuitry 1202 and memory 1204 is integrated.

[0200] The communication interface 1206 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1206 comprises port(s) / terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection. The communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222. The radio front-end circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202. The radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202. The radio front-end circuitry 1218 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and / or amplifiers 1222. The radio signal may then be transmitted via the antenna 1210. Similarly, when receiving data, the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218. The digital data may be passed to the processing circuitry 1202. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0201] In certain alternative embodiments, the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

[0202] The antenna 1210 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1210 may be coupled to the radio front-end circuitry 1218 and may be any type of antenna capable of transmitting and receiving data and / orsignals wirelessly. In certain embodiments, the antenna 1210 is separate from the network node 1200 and connectable to the network node 1200 through an interface or port.

[0203] The antenna 1210, communication interface 1206, and / or the processing circuitry 1202 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1210, the communication interface 1206, and / or the processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0204] The power source 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e g., at a voltage and current level needed for each respective component). The power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein. For example, the network node 1200 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1208. As a further example, the power source 1208 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0205] Embodiments of the network node 1200 may include additional components beyond those shown in FIG. 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.

[0206] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtainedinformation into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0207] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

CLAIMSWhat is claimed is:

1. A method of operating a network node in a communications network, the method comprising: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

2. The method of Claims 1, wherein the configuration information comprises an indication of which minimization drive test, MDT, measurements are subject to user consent, and wherein the specific type of information comprises a specific type of MDT measurement.

3. The method of Claim 2, wherein the configuration information comprises an explicit list of MDT measurements that are subject to user consent, and wherein determining whether the specific type of information is subject to user consent comprises determining whether the specific type of MDT measurement is included in the list of MDT measurements that are subject to user consent.

4. The method of Claim 2, wherein the configuration information comprises an explicit list of MDT measurements that are not subject to user consent, and wherein determining whether the specific type of information is subject to user consent comprises determining whether the specific type of MDT measurement is included in the list of MDT measurements that are not subject to user consent.

5. The method of any of Claims 1-4, wherein the network node is a core network, CN, configured to provide an access and mobility management function, AMF.

6. The method of Claim 5, wherein receiving the configuration information comprises at least one of: receiving, by the AMF, the configuration information from operation and maintenance, 0AM; andreceiving, by the AMF, the configuration information from a radio access network, RAN, node.

7. The method of any of Claims 5-6, further comprising: transmitting, by the AMF, a message to a radio access network, RAN, node, the message including an indication of a public land mobile network, PLMN, where a minimization drive test, MDT, can be collected.

8. The method of any of Claims 5-7, wherein determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is not subject to user consent, the method further comprising: responsive to determining that the specific type of information is not subject to user consent, transmitting (860), by the AMF, a request to collect the specific type of information associated with a communication device.

9. The method of any of Claims 5-7, wherein determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent, the method further comprising: responsive to determining that the specific type of information is subject to user consent, determining (840) that the user consent has been received; and responsive to determining that the user consent has been received, transmitting (860), by the AMF, a request to collect the specific type of information associated with a communication device.

10. The method of any of Claims 8-9, wherein transmitting the request to collect the specific type of information comprises transmitting a Trace Activation information element, IE, including a minimization drive test, MDT, public land mobile network, PLMN, list IE.

11. The method of any of Claims 7-10, further comprising: determining (850) the MDT PLMN list IE based on parameters retrieved from a unified data management, UDM.

12. The method of any of Claims 5-7, wherein determining whether the specific type ofinformation is subject to user consent comprises determining that the specific type of information is subject to user consent, the method further comprising: responsive to determining that the specific type of information is subject to user consent, determining (840) that the user consent has not been received; and responsive to determining that the user consent has not been received, avoiding (860) measurement of the specific type of information.

13. The method of Claims 1-4, wherein the network node is a radio access network, RAN, node, and wherein receiving the configuration information comprises receiving, by the RAN node, the configuration information from operation and maintenance, 0AM.

14. The method of Claims 13, further comprising: receiving (940), by the RAN node, a message from an access and mobility management, AMF, the message including an indication of a public land mobile network, PLMN, where a minimization drive test, MDT, can be collected.

15. The method of any of Claims 13-14, wherein determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is not subject to user consent, the method further comprising: responsive to determining that the specific type of information is not subject to user consent, selecting (960), by the RAN node, a communication device to measure the specific type of information.

16. The method of any of Claims 13-15, wherein determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent, the method further comprising: responsive to determining that the specific type of information is subject to user consent, determining (950) that the user consent has been received for a subscriber associated with a communication device; and responsive to determining that the user consent has been received for the subscriber associated with the communication device, selecting (960), by the RAN node, thecommunication device to measure the specific type of information.

17. The method of Claim 16, wherein determining that the user consent has been received for the subscriber associated with the communication device comprises determining that the user consent has been received for the subscriber associated with the communication device based on a minimization drive test, MDT, public land mobile network, PLMN, list information element, IE, received from the AMF.

18. The method of any of Claims 15-17, wherein selecting, by the RAN node, the communication device to measure the specific type of information comprises transmitting a minimization drive test, MDT, public land mobile network, PLMN, list information element, IE, to the communication device.

19. The method of any of Claims 13-15, wherein determining whether the specific type of information is subject to user consent comprises determining that the specific type of information is subject to user consent, the method further comprising: responsive to determining that the specific type of information is subject to user consent, determining (950) that the user consent has not been received for a subscriber associated with a communication device; and responsive to determining that the user consent has not been received for the subscriber associated with the communication device, avoiding (960) measurement of the specific type of information in association with the communication device.

20. The method of Claim 19, wherein determining that the user consent has not been received for the subscriber associated with the communication device comprises determining that the user consent has not been received for the subscriber associated with the communication device based on a minimization drive test, MDT, public land mobile network, PLMN, list information element, IE, received from the AMF.

21. A network node (1200) configured to perform operations comprising: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consentbased on the configuration information.

22. The network node of Claim 21, the operations further comprising any of the operations of Claims 2-20.

23. A computer program comprising program code to be executed by processing circuitry (1202) of a network node (1200), whereby execution of the program code causes the network node to perform operations comprising: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

24. The computer program of Claim 23, the operations further comprising any of the operations of Claims 2-20.

25. A computer program product comprising a non-transitory storage medium (1204) including program code to be executed by processing circuitry (1202) of a network node (1200), whereby execution of the program code causes the network node to perform operations comprising: receiving (810, 910) configuration information including an indication of whether a specific type of information is subject to user consent; receiving (820, 920) a request to measure the specific type of information; and determining (830, 930) whether the specific type of information is subject to user consent based on the configuration information.

26. The computer program product of Claim 25, the operations further comprising any of the operations of Claims 2-20.

Images