[go: up one dir, main page]

WO2025219761A1 - Mdt areas scopes for ntn - Google Patents

Mdt areas scopes for ntn

Info

Publication number
WO2025219761A1
WO2025219761A1 PCT/IB2025/000163 IB2025000163W WO2025219761A1 WO 2025219761 A1 WO2025219761 A1 WO 2025219761A1 IB 2025000163 W IB2025000163 W IB 2025000163W WO 2025219761 A1 WO2025219761 A1 WO 2025219761A1
Authority
WO
WIPO (PCT)
Prior art keywords
mdt
ntn
information
list
area
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IB2025/000163
Other languages
French (fr)
Inventor
Serban Purge
Johan Rune
Angelo Centonza
Luca LUNARDI
Ali PARICHEHREHTEROUJENI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ericsson France SAS
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Ericsson France SAS
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ericsson France SAS, Telefonaktiebolaget LM Ericsson AB filed Critical Ericsson France SAS
Publication of WO2025219761A1 publication Critical patent/WO2025219761A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • MDT AREAS SCOPES FOR NTN TECHNICAL FIELD [0001]
  • the present disclosure relates to Minimization of Drive Testing (MDT) measurements in a wireless communication system including a Non-Terrestrial Network (NTN).
  • NTN Non-Terrestrial Network
  • BACKGROUND MDT Configuration [0002] The following excerpts from 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.413 V18.0.0 are provided where it is shown how a Minimization of Drive Testing (MDT) configuration is formulated and how an MDT area scope is defined.
  • the MDT Area Scope constitutes an area where the User Equipment (UE) is allowed to collect MDT measurements.
  • UE User Equipment
  • NG Initial Context Setup – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 8.3.1 Initial Context Setup 8.3.1.1
  • the purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG- RAN node, when required, including PDU session context, the Security Key, Mobility Restriction List, UE Radio Capability and UE Security Capabilities, etc.
  • the AMF may initiate the Initial Context Setup procedure if a UE- associated logical NG-connection exists for the UE or if the AMF has received the RAN UE NGAP ID IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG- connection by sending an INITIAL UE MESSAGE message via another NG interface instance.
  • the procedure uses UE-associated signalling. For signalling only connections and if the UE Context Request IE is not received in the Initial UE Message, the AMF may be configured to trigger the procedure for all NAS procedures or on a per NAS procedure basis depending on operator’s configuration.
  • Figure 8.3.1.2-1 Initial context setup: successful operation In case of the establishment of a PDU session the 5GC shall be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received by the AMF. If no UE-associated logical NG- connection exists, the UE-associated logical NG-connection shall be established at reception of the INITIAL CONTEXT SETUP REQUEST message.
  • the INITIAL CONTEXT SETUP REQUEST message shall contain the Index to RAT/Frequency Selection Priority IE, if available in the AMF.
  • the NG-RAN node shall pass it transparently towards the UE. If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling.
  • the NG-RAN node Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall - attempt to execute the requested PDU session configuration; - store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]; - store the received Mobility Restriction List in the UE context; - store the received UE Radio Capability in the UE context; - store the received Index to RAT/Frequency Selection Priority in the UE context and use it as defined in TS 23.501 [9]; - store the received UE Security Capabilities in the UE context; - store the received Security Key in the UE context and, if the NG-RAN node is required to activate security for the UE, take this security key into use; - if supported, store the received SRVCC Operation Possible in the UE context and use it as
  • the NG-RAN node For the Initial Context Setup an initial value for the Next Hop Chaining Count is stored in the UE context. If the PDU Session Resource Setup Request List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall behave the same as defined in the PDU Session Resource Setup procedure. The NG-RAN node shall report to the AMF in the INITIAL CONTEXT SETUP RESPONSE message the result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure.
  • the AMF Upon reception of the INITIAL CONTEXT SETUP RESPONSE message the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Setup Response Transfer IE or PDU Session Resource Setup Unsuccessful Transfer IE to the SMF associated with the concerned PDU session. In case the splitting PDU session is not used by the NG-RAN node, the SMF should remove the Additional Transport Layer Information, if any.
  • the NG-RAN node shall use the information in the Mobility Restriction List IE if present in the INITIAL CONTEXT SETUP REQUEST message to - determine a target for subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE; - select a proper SCG during dual connectivity operation; - assign proper RNA(s) for the UE when moving the UE to RRC_INACTIVE state. If the Mobility Restriction List IE is not contained in the INITIAL CONTEXT SETUP REQUEST message, the NG- RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501 [9].
  • the NG-RAN node shall also consider that no roaming and no access restriction apply to the UE when: - one of the QoS flows includes a particular ARP value (TS 23.501 [9]).
  • the NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the Allowed PNI-NPN List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, as described in TS 23.501 [9]. If the Trace Activation IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11].
  • the NG-RAN node shall, if supported: - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [11]; - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", “Logged MDT only”, initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore t he Interfaces To Trace IE and the Trace Depth IE; - if the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, store this information and take it into account in the requested MDT session; - if the Trace Activation IE includes the Signalling Based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration as described
  • the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41].
  • - if the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE take it into account for MDT Configuration as described in TS 37.320 [41].
  • the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present.
  • NG Handover Resource Allocation – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 8.4.2.1
  • the purpose of the Handover Resource Allocation procedure is to reserve resources at the target NG-RAN node for the handover of a UE.
  • the procedure uses UE-associated signalling. 8.4.2.2 Successful Operation [REPROUCED HEREIN AS FIGURE 2] Figure 8.4.2.2-1: Handover resource allocation: successful operation
  • the AMF initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. [part omitted] If the Trace Activation IE is included in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11].
  • the NG-RAN node shall, if supported: - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [11]; - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", “Logged MDT only”, initiate the requested MDT session as described in TS 32.422 [11] and the target NG-RAN node shall i gnore the Interfaces To Trace IE and the Trace Depth IE; - if the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, store this information and take it into account in the requested MDT session; - if the Trace Activation IE includes the Signalling Based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration
  • the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41].
  • - if the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE take it into account for MDT Configuration as described in TS 37.320 [41].
  • the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present. If the Location Reporting Request Type IE is included in the HANDOVER REQUEST message, the target NG-RAN node should perform the requested location reporting functionality for the UE as described in subclause 8.12.
  • Trace Start procedure is to allow the AMF to request the NG-RAN node to initiate a trace session for a UE.
  • the procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established as part of the procedure.
  • FIG. 8.11.1.2-1 Trace start The AMF initiates the procedure by sending a TRACE START message. Upon reception of the TRACE START message, the NG-RAN node shall initiate the requested trace session as described in TS 32.422 [11]. If the Trace Activation IE is included in the TRACE START message which includes the MDT Activation IE set to "Immediate MDT and Trace", the NG-RAN node shall, if supported, initiate the requested trace session and MDT session as described in TS 32.422 [11].
  • the Trace Activation IE is included in the TRACE START message which includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only”, the NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE. If the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, the NG- RAN node shall, if supported, store this information and take it into account in the requested MDT session.
  • the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. If the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41].
  • the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE
  • the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41].
  • the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE
  • the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41].
  • the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration- EUTRA IE shall be present. If the PNI-NPN Area Scope of MDT IE is included in the MDT Configuration-NR IE included in the TRACE START message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas.
  • the NG-RAN node Upon reception of the PNI-NPN Area Scope of MDT IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the PNI-NPN Area Scope of MDT IE. Interactions with other procedures: If the NG-RAN node is not able to initiate the trace session due to ongoing handover of the UE to another NG-RAN node, the NG-RAN node shall initiate a Trace Failure Indication procedure with the appropriate cause value.
  • This IE is composed of the - Trace ID (SIZE(8)) following: Trace Reference defined in TS 32.422 [11] (leftmost 6 octets, with PLMN information encoded as in 9.3.3.5), and Trace Recording Session Reference defined in TS 32.422 [11] (last 2 octets).
  • MDT Configuration IE Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.167 MDT Configuration This IE defines the MDT configuration parameters.
  • MDT PLMN List IE Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.168 MDT PLMN List
  • the purpose of the MDT PLMN List IE is to provide the list of PLMN allowed for MDT.
  • C-ifM1 This IE shall be present if the Measurements to Activate IE has the first bit set to “1”.
  • C -ifM4 This IE shall be present if the Measurements to Activate IE has the third bit set to “1”.
  • C -ifM5 This IE shall be present if the Measurements to Activate IE has the fourth bit set to “1”.
  • C -ifM6 This IE shall be present if the Measurements to Activate IE has the fitth bit set to “1”.
  • C -ifM7 This IE shall be present if the Measurements to Activate IE has the sixth bit set to “1”.
  • the Area Scope determines the area where MDT measurements shall be collected, as specified in TS32.422, as follows: ***** START EXCERPT FROM 3GPP TS 38.413 ***** 5.10.2 Area Scope
  • the Area Scope optional parameter defines the area in terms of Cells or Tracking Area/Routing Area/Location Area where the MDT data collection shall take place.
  • the area scope specified in an MDT session shall support the PLMNs of the MDT PLMN list (defined in clause 5.10.24). If the parameter is not present the MDT data collection shall be done throughout the PLMNs of the MDT PLMN list. For further details see also TS 37.320 [30].
  • the Area Scope parameter in UMTS is either: - list of Cells, identified by CGI.
  • Maximum 32 CGI can be defined. - List of Routing Area, identified by RAI. Maximum of 8 RAIs can be defined. - List of Location Area, identified by LAI. Maximum of 8 LAIs can de defined.
  • the Area Scope parameter in LTE and NR is either: - list of Cells, identified by E-UTRAN-CGI or NG-RAN CGI. Maximum 32 CGI can be defined.
  • Maximum of 8 TAC can be defined.
  • - List of Tracking Area Identity identified by TAC with associated plmn-Identity perTAC-List containing the PLMN identity for each TAC. Maximum of 8 TAI can be defined. For further details see also TS 36.331[32].
  • Non-Terrestrial Network Overview [0012]
  • the NTN component uses a constellation of several satellites (e.g., Low-Earth Orbiting (LEO) satellite(s), Medium-Earth Orbiting (MEO) satellite(s), Geostationary Orbit (GEO) satellite(s), etc.) that can orbit using one or more orbit planes.
  • LEO Low-Earth Orbit
  • MEO Medium-Earth Orbit
  • GEO Geostationary Orbit
  • Each satellite can provide wireless network access to UEs positioned on, or near, the Earth’s surface via the respective service link.
  • the satellite antenna is connected to a Radio Access Network (RAN) node, e.g., a gNodeB (gNB) in the case of 3GPP New Radio (NR).
  • RAN Radio Access Network
  • gNB gNodeB
  • NR 3GPP New Radio
  • each node is expected to provide coverage to a specific territory by dividing the area into coverage sectors.
  • the nodes are using the satellites as mediums to transmit the corresponding radio signals through the beams towards those areas.
  • TR Technical Report
  • NR New Radio
  • TR 38.821 Solutions for NR to support non-terrestrial networks (NTN) (Rel-16).” Please refer to those documents for details.
  • Mapped Cell [0017] The concept of mapped cells is specific to NTN. Below, excerpts from 3GPP TS 38.300 v18.0.0 are provided in which the definition of a “Mapped Cell” is shown. ***** START EXCERPT FROM 3GPP TS 38.300 ***** 3.2 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1], in TS 36.300 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 36.300 [2]. A2X communication: A communication to support A2X services leveraging PC5 reference points.
  • A2X services are realized by various types of A2X applications, i.e. BRID or DAA.
  • Aerial UE communication functionality enabling Aerial UE function, as defined in 16.18.
  • Air to Ground network An NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m.
  • BH RLC channel an RLC channel between two nodes, which is used to transport backhaul packets.
  • Boundary IAB-node as defined in TS 38.401 [4].
  • Broadcast MRB A radio bearer configured for MBS broadcast delivery.
  • CAG Cell a PLMN cell broadcasting at least one Closed Access Group identity.
  • CAG Member Cell for a UE, a CAG cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the Allowed CAG list of the UE for that PLMN.
  • CAG-only cell a CAG cell that is only available for normal service for CAG UEs.
  • Cell-Defining SSB an SSB with an RMSI associated.
  • Child node IAB-DU's and IAB-donor-DU's next hop neighbour node; the child node is also an IAB-node.
  • Conditional Handover (CHO): a handover procedure that is executed only when execution condition(s) are met.
  • CORESET#0 the control resource set for at least SIB1 scheduling, can be configured either via MIB or via dedicated RRC signalling.
  • DAPS Handover a handover procedure that maintains the source gNB connection after reception of RRC message for handover and until releasing the source cell after successful random access to the target gNB.
  • Data Burst A set of multiple PDUs generated and sent by the application in a short period of time, as defined in TS 23.501 [3].
  • Direct Path a type of UE-to-Network transmission path, where data is transmitted between a UE and the network without sidelink relaying.
  • eRedCap UE a UE with enhanced reduced capabilities as specified in clause 4.2.22.1 in TS 38.306 [11].
  • Feeder link wireless link between the NTN Gateway and the NTN payload.
  • Geosynchronous Orbit earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e.
  • Group ID for Network Selection an identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder, as specified in TS 23.501 [3].
  • gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.
  • High Altitude Platform Station airborne vehicle embarking the NTN payload placed at an altitude between 8 and 50 km.
  • IAB-donor gNB that provides network access to UEs via a network of backhaul and access links.
  • IAB-donor-CU as defined in TS 38.401 [4].
  • IAB-donor-DU as defined in TS 38.401 [4].
  • IAB-DU gNB-DU functionality supported by the IAB-node to terminate the NR access interface to UEs and next- hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, as defined in TS 38.401 [4], on the IAB-donor.
  • IAB-MT IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise.
  • IAB-MT function used in 38-series of 3GPP Specifications corresponds to IAB-UE function defined in TS 23.501 [3].
  • IAB-node RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes. The IAB-node does not support backhauling via LTE.
  • IAB topology the unison of all IAB-nodes and IAB-donor-DUs whose F1 and/or RRC connections are terminated at the same IAB-donor-CU.
  • Indirect Path a type of UE-to-Network transmission path, where data is forwarded via a U2N Relay UE between a U2N Remote UE and the network.
  • Inter-donor partial migration migration of an IAB-MT to a parent node underneath a different IAB-donor-CU while the collocated IAB-DU and its descendant IAB-node(s), if any, are terminated at the initial IAB-donor-CU. The procedure renders the said IAB-node as a boundary IAB-node.
  • Intra-system Handover handover that does not involve a CN change (EPC or 5GC).
  • Inter-system Handover handover that involves a CN change (EPC or 5GC).
  • Late Data Forwarding data forwarding that is initiated after the source NG-RAN node knows that the UE has successfully accessed a target NG-RAN node.
  • NTN Non-Terrestrial Network
  • Figure 16.14.1-1 Overall illustration of an NTN N OTE 1: Figure 16.14.1-1 illustrates an NTN; RAN4 aspects are out of scope.
  • the NTN payload transparently forwards the radio protocol received from the UE (via the service link) to the NTN Gateway (via the feeder link) and vice-versa.
  • the following connectivity is supported by the NTN payload: - An NTN gateway may serve multiple NTN payloads; - An NTN payload may be served by multiple NTN gateways.
  • the NTN-payload may change the carrier frequency, before re-transmitting it on the service link, and vice versa (respectively on the feeder link).
  • a Tracking Area corresponds to a fixed geographical area. Any respective mapping is configured in the RAN; - A Mapped Cell ID as specified in clause 16.14.5. ... ***** START NEXT EXCERPT FROM 3GPP TS 38.300 ***** 16.14.5 NG-RAN signalling
  • the Cell Identity as defined in TS 38.413 [26] and TS 38.423 [50], used in following cases corresponds to a Mapped Cell ID, irrespective of the orbit of the NTN payload or the types of service links supported: - The Cell Identity indicated by the gNB to the Core Network as part of the User Location Information; - The Cell Identity used for Paging Optimization in NG interface; - The Cell Identity used for Area of Interest; - The Cell Identity used for PWS.
  • the Cell Identity included within the target identification of the handover messages allows identifying the correct target cell.
  • the cell identity used in the NG and Xn handover messages, Xn Setup and Xn NG-RAN Node Configuration Update procedures is expected to be Uu Cell ID.
  • the Cell Identities used in the RAN Paging Area during Xn RAN paging allow the identification of the correct target cells for RAN paging.
  • N OTE 1 The Cell Identity used for RAN Paging is assumed to typically represent a Uu Cell ID.
  • the mapping between Mapped Cell IDs and geographical areas is configured in the RAN and Core Network.
  • N OTE 2 A specific geographical location may be mapped to multiple Mapped Cell ID(s), and such Mapped Cell IDs may be configured to indicate differerent geographical areas (e.g. overlapping and/or with different dimensions).
  • the gNB is responsible for constructing the Mapped Cell ID based on the UE location information received from the UE, if available. The mapping may be pre-configured (e.g., up to operator's policy) or up to implementation.
  • N OTE 3 As described in TS 23.501 [3], the User Location Information may enable the AMF to determine whether the UE is allowed to operate at its present location.
  • Special Mapped Cell IDs or TACs may be used to indicate areas outside the serving PLMN's country.
  • the gNB reports the broadcasted TAC(s) of the selected PLMN to the AMF as part of ULI. In case the gNB knows the UE's location information, the gNB may determine the TAI the UE is currently located in and provide that TAI to the AMF as part of ULI. * **** END EXCERPTS FROM 3GPP TS 38.300 ***** SUMMARY [0018] Systems and methods related to Minimization of Drive Testing (MDT) area scopes that are particularly well-suited for Non-Terrestrial Networks (NTNs) are disclosed.
  • MDT Minimization of Drive Testing
  • a method performed by a User Equipment comprises receiving, from a first network node, information that configures the UE to perform MDT measurements in one or more coverage areas of an NTN. The method further comprises performing the MDT measurements and reporting the MDT measurements to the first network node or another network node. In this manner, an operator or a network is enabled to focus an MDT measurement collection to specific NTN coverage areas.
  • the information that configures the UE to perform MDT measurements in the one or more coverage areas of the NTN comprises one or more list of identities that identify the one or more coverage areas of the NTN.
  • the information that configures the UE to perform MDT measurements in the one or more coverage areas of the NTN comprises information that indicates one or more geographical areas that correspond to the one or more coverage areas of the NTN.
  • the information that configures the UE to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking areas, a list of registration areas, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state.
  • an area e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area
  • a list of cells e.g.,
  • the information that configures the UE (604) to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state.
  • the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises one or more elements related to the NTN.
  • the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific.
  • the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN.
  • the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN.
  • a method performed by a UE comprises receiving, from a first network node, information that configures the UE to perform MDT measurements in one or more coverage areas for a NTN and a Terrestrial Network (TN), performing the MDT measurements in accordance with the received information, and reporting the MDT measurements to the first network node (700) or another network node together with an indication(s) that indicates whether the MDT measurements are for the NTN or the TN.
  • the indication(s) comprise a separate indication for each MDT measurement.
  • Corresponding embodiments of a UE are also disclosed.
  • Embodiments of a method performed by a first network node are also disclosed.
  • a method performed by a first network node comprises receiving, from a second network node, first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a NTN, and configuring a UE to perform one or more MDT measurements in at least one of the one or more coverage areas of the NTN.
  • the method further comprises receiving second information comprising information about the MDT measurements.
  • the second information comprises an MDT measurements configuration.
  • the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements.
  • the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN.
  • configuring the UE to perform the one or more MDT measurements comprises configuring the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state.
  • an area e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area
  • configuring the UE to perform the one or more MDT measurements comprises configuring the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state.
  • the second information comprises an MDT configuration that comprises one or more elements related to the NTN.
  • the second information comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific.
  • the second information comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN.
  • the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN.
  • the second information is comprised in a UE context modification related message, and the second information relates to a modification to a management based MDT configuration.
  • the management based MDT configuration comprises a list of PLMNs allowed for MDT and an associated indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN.
  • the first information comprises an NTN geographical area list for MDT comprised in an MDT configuration.
  • the first information comprises information that indicates a geographic area for a list of NTN geographical areas for MDT indicated for an area scope of neighbor cells from which the UE is to collect the MDT measurements.
  • a method performed by a first network node comprises receiving, from a second network node, first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a NTN and a TN, and configuring a UE to perform one or more MDT measurements in at least one of the one or more coverage areas of the NTN and TN.
  • the method further comprises receiving second information comprising information about the MDT measurements.
  • the second information comprises an MDT measurements configuration.
  • the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements.
  • the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN and TN.
  • configuring the UE to perform the one or more MDT measurements comprises configuring the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in a connected state.
  • an area e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area
  • a list of cells e.g., a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas
  • configuring the UE to perform the one or more MDT measurements comprises configuring the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state.
  • MDT measurements reported by the UE in response to the configuring comprise or are otherwise associated to an indicator that indicates whether the MDT measurements are for the NTN or the TN.
  • Corresponding embodiments of a first network node are also disclosed.
  • Figure 1 is a reproduction of Figure 8.3.1.2-1 of 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.413 v18.0.0;
  • Figure 2 is a reproduction of Figure 8.4.2.2-1 of 3GPP TS 38.413 v18.0.0;
  • Figure 3 is a reproduction of Figure 8.11.1.2-1 of 3GPP TS 38.413 v18.0.0;
  • Figure 4 illustrates an example of a Non-Terrestrial Network (NTN);
  • Figure 5 is a reproduction of Figure 16.14.1-1 of 3GPP TS 38.300 v18.0.0;
  • Figure 6 illustrates the operation of a first network node, a second network node, and a User Equipment (UE), in accordance
  • UE User Equipment
  • NTN network performance and configuration implies that, in order to monitor the performance of NTNs, the operator has to define a generic Area Scope for MDT and collect MDT measurements there. The result of such measurement collection will have to be post-processed to determine which of the collected measurements are derived from NTNs or from parts of NTNs. This may result in lengthy and resource intensive data post-processing procedures. In some other cases, it would not even be possible to deduce whether existing measurements apply to NTNs because NTN coverage may constitute of parts of a cell or a Tracking Area Identity (TAI).
  • TAI Tracking Area Identity
  • FIG. 6 illustrates the operation of a first network node 600, a second network node 602, and a UE 604, in accordance with some embodiments of the present disclosure. Optional steps are represented by dashed lines/boxes.
  • the first network node 600 is, in some embodiments, a RAN node such as, e.g., a gNB, a gNB-Central Unit (CU), or a gNB-CU-Control Plane (CP).
  • a RAN node such as, e.g., a gNB, a gNB-Central Unit (CU), or a gNB-CU-Control Plane (CP).
  • the first network node 600 may be a TN node (i.e., a network node of a TN) or an NTN node (e.g., a network node of a NTN which may include, e.g., a satellite and gateway).
  • the second network node 602 is, in some embodiments, a core network node (e.g., an Access and Mobility Management Function (AMF)) or an Operations, Administration, and Maintenance (OAM) system.
  • AMF Access and Mobility Management Function
  • OAM Operations, Administration, and Maintenance
  • the first network node 600 receives, from the second network node 602, first information concerning (e.g., about or that indicates) one or more coverage areas of an NTN (step 606).
  • the coverage areas of the NTN are used to derive, or otherwise define, the coverage area(s) where MDT measurements are to be collected.
  • the first information includes, for example, a list of identifiers identifying the one or more coverage areas of the NTN (also referred to herein as the areas of coverage of the NTN), where such NTN coverage area identifiers are used to derive the coverage areas where MDT measurements shall be collected.
  • the first network node 600 may receive from the second network node 602 (or another network node), information concerning MDT measurements that are to be measured by UEs within the coverage areas of the NTN indicated by the first information (step 608).
  • first information of step 606 and the second information of step 608 may be received from the same network node, in which case the first information and the second information may be included in a single message (e.g., RRC message) containing one or more information elements or may be received via separate messages.
  • first information of step 606 and the second information of step 608 may be received from separate network nodes (e.g., the first information may be received from an OAM system and the second information may be received from a core network node (e.g., AMF)).
  • the first network node 600 uses the first information of step 606 and the second information of step 608 to configure the UE 604 to perform MDT measurements in at least one of the indicated coverage areas of the NTN (step 610).
  • the UE 604 performs the configured MDT measurements and reports the MDT measurements, e.g., to the first network node 600 or another network node (step 612). In other words, once the MDT measurements are collected, the UE 604 reports the measurements to a network node (e.g., either the first network node or a different network node).
  • the first network node 600 may use the received first and second information to configure the UE 604 in step 610 for immediate MDT measurements, namely MDT measurements collected by the UE in a connected stated (e.g., Radio Resource Control (RRC) connected stated, i.e., RRC_CONNECTED state).
  • RRC Radio Resource Control
  • RRC_CONNECTED state is used as an example of the connected state.
  • the first network node 600 checks an area where the UE 604 is served while in RRC_CONNECTED, where such area may be constituted by, for example, a cell, a tracking area, a registration area, a Public Land Mobile Network (PLMN), a mapped cell, a geographical area (such as a polygon shaped geographical area, a circle shaped geographical area, etc.), a list of cells, a list of tracking areas, a list of registration areas, a list of PLMNs, a list of mapped cells, or a list of geographical areas.
  • PLMN Public Land Mobile Network
  • the first network node 600 verifies that the area where the UE 604 is served corresponds to at least one of the coverage areas of the NTN indicated by the first information received from the second network node 602 in step 606. Upon verifying that the area where the UE 604 is served while in RRC_CONNECTED corresponds to at least one of the coverage areas of the NTN signaled by the second network node in step 606, the first network node 600 configures the UE 604 with MDT measurements.
  • MDT measurements configuration may include an MDT measurements configuration received from the second network node 608 (e.g., as or as part of the second information of step 608) together with the first information that indicates the one or more coverage areas of the NTN.
  • the first network node 600 uses the first and second information received from the second network node 602 to configure the UE 604, in step 610, with logged MDT measurements, namely measurements logged by the UE 604 while in an idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE) that are to be reported by the UE 604 (e.g., in step 612) to the network once the UE 604 moves back to connected state (e.g., RRC_CONNECTED).
  • an idle state e.g., RRC_IDLE
  • inactive state e.g., RRC_INACTIVE
  • the first network node 600 signals, to the UE 604, (e.g., in step 610) identifiers representing the one or more coverage areas of the NTN where logged MDT measurements should be collected. Additionally, the first network node 600 can signal to the UE 604 (e.g., in step 610) also the MDT measurements configuration that the UE 604 is to use when camping in any areas covered by the one or more coverage areas of the NTN.
  • Figure 7 illustrates the operation of a first network node 700, a second network node 702, and a UE 704, in accordance with some other embodiments of the present disclosure. Optional steps are represented by dashed lines/boxes.
  • the first network node 700 is, in some embodiments, a RAN node such as, e.g., a gNB, a gNB-CU, or a gNB-CU-CP.
  • the first network node 700 may be a TN node (i.e., a network node of a TN) or an NTN node (e.g., a network node of a NTN which may include, e.g., a satellite and gateway).
  • the second network node 702 is, in some embodiments, a core network node (e.g., an AMF) or an OAM system.
  • the first network node 700 receives from the second network node 702, first information that indicates coverages areas of an NTN and an TN (together) (step 706).
  • the first information is information concerning (e.g., including) one or more list of identifiers identifying of the coverage areas of the NTN and TN networks (together), where such TN and NTN area identifiers are used to derive the coverage areas where MDT measurements are to be collected from TN and NTN networks.
  • the first network node 700 may receive second information about MDT measurements to be collected in the indicated coverage areas of the NTN and TN networks (step 708).
  • the second information includes, for example, an MDT measurements configuration(s) including one or more configuration parameters/metrics concerning MDT measurements metrics that are to be collected by the UE within the coverage area(s) indicated by the first information.
  • the first information of step 706 and the second information of step 708 may be received from the same network node, in which case the first information and the second information may be included in a single message (e.g., RRC message) containing one or more information elements or may be received via separate messages.
  • the first information of step 706 and the second information of step 708 may be received from separate network nodes (e.g., the first information may be received from an OAM system and the second information may be received from a core network node (e.g., AMF)).
  • the first network node 700 uses the first information of step 706 and the second information of step 708 to configure the UE 704 to perform MDT measurements in at least one of the indicated coverage areas of the NTN and TN networks (step 710).
  • the UE 604 performs the configured MDT measurements and reports the MDT measurements, e.g., to the first network node 700 or another network node (step 712). In other words, once the configured MDT measurements are collected, the UE 704 reports the measurements to a network node (either first network node or a different network node).
  • the UE 704 upon collecting the MDT measurements when camping in the NTN includes an indication (e.g., a flag) in the MDT measurements indicating whether the measurement is collected in the NTN or in the TN.
  • an indication e.g., a flag
  • Such indication can be used by the network (e.g., OAM) for the post-processing and building a coverage map of the NPN and TN separately.
  • the UE e.g., UE 604 and/or UE 704
  • the UE will collect the configured MDT measurements only when served or camped in the NTN areas that are part of the MDT area scope for NTN signaled to the first network node (e.g., first network node 600 or 700) by the second network node (e.g., second network node 602 or 702).
  • the first network node e.g., first network node 600 or 700
  • the second network node e.g., second network node 602 or 702
  • Embodiments of the present disclosure include a first network node, e.g. a RAN node or function, that receives information comprising one or more identifiers identifying one or more NTN coverage areas.
  • the first network node is able to configure UEs with MDT measurements, which are either collected by the UEs while in a connected state (e.g., RRC_CONNECTED) or logged by the UEs while in an idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE), only if the UE is connected to or camped in an area corresponding to at least one of the one or more NTN coverage areas identified by the information received by the first network node or function and with associated MDT measurements.
  • a connected state e.g., RRC_CONNECTED
  • logged by the UEs while in an idle state
  • RRC_IDLE idle state
  • inactive state e.g., RRC_INACTIVE
  • information concerning the NTN coverage area(s) is also provided from the first network node to the UE.
  • the UE is able, while in idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE), to check if any of the camping cell, areas of a cell, or neighbor cell correspond to any of the NTN coverage areas indicated by the information received from the first network node. If yes, the UE is able to camp on such cell and measure and log the configured MDT measurements.
  • Embodiments of the present disclosure enable a framework where MDT measurements are collected only in specific NTN coverage areas.
  • Embodiments of the present disclosure may enable an operator or a network to focus an MDT measurement collection to specific NTN coverage areas. This provides the advantage of collecting measurements that are pertinent to UEs and services associated with specific NTN coverage areas and that can, for example, be used to monitor whether service level agreements are fulfilled or configurations concerning coverage, network performance, mobility and more are operating as expected. In other words, embodiments of the present disclosure may enable the network/operators to build e.g., a coverage map and/or data determining the performance of an NTN coverage area.
  • the second information received by the first network node includes an MDT Configuration for NR (e.g., a modified MDT Configuration-NR IE).
  • the MDT Configuration for NR e.g., a modified MDT Configuration-NR IE.
  • the MDT Configuration-NR IE is extended with one or more elements related to the NTN deployment.
  • the CHOICE Information Element Area Scope of MDT is extended with one element pertaining to NTN (e.g. an NTN Based MDT IE) and comprising one or more parameters that are NTN specific.
  • the one or more parameters that are NTN specific may include any one or more of the following: information that indicates cells (e.g., cell identities) mapped to NTN, information that defines one or more polygon-shaped geographic areas, one or more satellite IDs, etc.
  • a network operator may have commercial agreements with third parties, or alternatively it can directly operate, a communication network which comprises both a TN and a NTN, wherein the TN corresponds to a first Public Land Mobile Network (PLMN), and the NTN corresponds to a second PLMN.
  • PLMN Public Land Mobile Network
  • the network operator is interested in collecting UE measurements from both the TN and the NTN, the RAN node (e.g., the first network node 600 or 7000) and the UE (e.g., the UE 604 or 704) need to be instructed accordingly.
  • a first PLMN is associated with an NTN and a second PLMN is associated with a TN, wherein the first PLMN is different from the second PLMN.
  • a certain PLMN is associated with both an NTN and a TN.
  • the second information received by the first network node includes a set of MDT configuration parameters (e.g., a modified MDT Configuration NR IE).
  • the set of MDT configuration parameters (e.g., the MDT Configuration NR IE) is extended to indicate whether the MDT configuration is applicable only to NTN, or to both NTN and TN.
  • the MDT Configuration is extended to be able to discriminate whether a certain PLMN allowed for MDT is associated with a NTN, or with a TN. For instance, within the Signaling Based MDT PLMN List, the MDT PLMN List IE is extended with a flag to indicate whether a PLMN allowed for MDT is associated with an NTN or with a TN.
  • the RAN node e.g., the first network node 600 or X700
  • receiving a list of two (or more) PLMNs in the MDT PLMN List e.g., as part of the second information of step 608 or 708, of which at least one is associated with an NTN, and another one not associated with an NTN (i.e., associated with a TN)
  • it can determine to collect the MDT measurements for a UE (e.g., the UE 604 or 704) that is moving across an area that is partly covered by the first PLMN (e.g., across the corresponding NTN) and partly covered by the second PLMN (e.g., across the corresponding TN).
  • the MDT Configuration is constructed to only include one or more PLMN associated with NTN, in which case the RAN node determines that MDT measurements will be collected only for NTN.
  • the extension of the MDT PLMN List IE can be realized as follows: 9.3.1.168 MDT PLMN List
  • the purpose of the MDT PLMN List IE is to provide the list of PLMN allowed for MDT.
  • the Access and Mobility Management Function (e.g., the second network node 602 or 702) provides UE Context information changes to an NG-RAN node (e.g., the first network node 600 or 700), e.g., as part of the second information of step 608 or 708. This can be used to apply modification to the Management Based MDT configuration.
  • the list of PLMN allowed for MDT is modified, and a flag indicates whether the PLMN relates to an NTN.
  • MDT PLMN Modification List IE is extended as follows: 9.3.1.243 MDT PLMN Modification List This IE provides the modified list of PLMN allowed for MDT. IE/Group Name Presence Range IE type and Semantics description reference MDT PLMN Modification 0.. ⁇ maxnoofM An empty list indicates there List DTPLMNs> is no PLMN allowed for MDT. > PLMN Identity M 9.3.3.5 >PLMN Type O ENUMERATE Indicates whether D(‘ntn’,...) the PLMN pertains to an NTN. R ange bound Explanation maxnoofMDTPLMNs Maximum no. of PLMNs in the MDT PLMN list. Value is 16.
  • the UE Context for a UE can be transferred from an old RAN node to a new RAN node, e.g., as in the Retrieve UE Context procedure defined in 3GPP TS 38.423 v18.0.0.
  • the new RAN node obtains the indication of one or more PLMN allowed for MDT, wherein for a certain PLMN allowed for MDT, an attribute (e.g., a flag) is associated, indicating whether the PLMN pertains to (or is associated with) an NTN.
  • an attribute e.g., a flag
  • the first network node e.g.
  • a RAN node receives from a second network node, e.g. a CN function or the OAM system, (e.g., the second network node 602 or 702) information revealing the NTN coverage areas where the UE (e.g., the UE 604 or 704) needs to be connected or camped on in order for MDT measurements to be collected. If the UE is connected or camped on any of such NTN coverage areas, the UE can collect MDT measurements within the area. [0091] The MDT measurements that should be collected by the UE in the NTN coverage areas may also be signaled to the first network node by the second network node.
  • the first network node is a gNB, or a gNB-Central Unit (CU)-Control Plane (CP), and the second network node is the AMF.
  • the first network node receives the information from the second network node via the NG interface.
  • One instance of how such information can be signaled to the first network node is by means of modification of the existing MDT Configuration NR.
  • the information can be included in any other suitable existing IE or in new IEs signaled over the interface connecting the first and second network node directly or indirectly.
  • MDT Activation M ENUMERATED (Immediate MDT only, Logged MDT only, Immediate MDT and Trace, 10) CHOICE Area Scope of MDT M >Cell based > >Cell ID List for MDT 1.. ⁇ maxnoofCe llIDforMDT> > >>NR CGI M 9.3.1.7 >TA based > >TA List for MDT 1.. ⁇ maxnoofTA forMDT> > >>TAC M 9.3.3.10
  • the TAI is derived using the current serving PLMN.
  • the first network node optionally receives from the AMF a list of Mapped Cells and/or a list of Geographic Areas. Similarly, the first network node may receive lists of identifiers defining other coverage areas pertaining to an NTN network such as cell identifiers, tracking area identifiers, PLMN identifiers and more.
  • the first network node may also receive a list of NTN coverage area identifiers that is used to determine the area in which MDT measurements are collected from neighbor cells.
  • such list of NTN coverage area identifiers may be used to determine the Area Scope of Neighbour Cells.
  • the area Scope of neighbor cells identifies details of neighbor cells for which MDT measurements shall be collected.
  • the first network node would be informed about the NTN coverage area identifiers for the neighbor cells from which the UE shall collect MDT measurements.
  • maxnoofNeighPCIforMDT Maximum no. of Neighbour cells subject for MDT scope. Value is 32. maxnoofMappedCellsforMDT *Maximum no.of Mapped Cells for MDT scope. Value is 16. maxnoofGeographicAreaforMDT *Maximum no.of Geographic Areas for MDT scope. Value is 16. [0096] In the example above, it can be seen that the Area Scope of Neighbour Cells has been enhanced with a list of NTN mapped cells and/or a list of NTN geographical areas.
  • the first network node therefore knows that the UE needs to be configured with this information so that the UE would measure MDT measurements from neighbour cells only if the listed NTN coverage area identifiers are signalled by a neighbour cell.
  • the above enhancements to the MDT Area Scope and/or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE performs mobility or tentatively when the UE is expected to move to another network node, for example as part of CHO configuration.
  • the above enhancements to the MDT Area Scope and/or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE is for example in dual-connected mode.
  • the first network node may be required to configure the UE over RRC with the information received in the Area Scope of MDT and in the Area Scope of Neighbour Cells. [0100] Such configuration may occur by enhancing new IEs in the RRC protocol or by introducing new IEs to carry the information.
  • AreaConfiguration-r16 SEQUENCE ⁇ areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R ⁇
  • AreaConfiguration-r1700 SEQUENCE ⁇ areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R ⁇
  • AreaConfiguration-v18xy SEQUENCE ⁇ M appedCell-Area-r18 Define the encoding of mapped cell list OPTIONAL, -- Need R Geographic-Area-r18 Define the encoding of geographic area list OPTIONAL -- Need R ⁇ [0102]
  • N OTE 2 For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. 2 > when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4.
  • the UE may check whether such NTN coverage area identifiers are supported or available in the area where the UE is camped or served. It should be pointed out that the examples above are non-limiting and that the NTN coverage areas could also consist of other coverage area identifiers such ad cell identities, tracking area identities, PLMN identities.
  • Logging indication of NTN network in the MDT measurements when TN and NTN area configuration together is provided to the UE (such as, e.g., in the procedure of Figure 7).
  • the first network node receives from a second node, the first piece of information concerning one or more list of identifiers comprising the areas of coverage of an NTN and TN networks (together), where such TN and NTN area identifiers are used to derive the coverage areas where MDT measurements shall be collected from TN and NTN networks. Additionally, to this information, the first network node may receive one or more configuration parameters/metrics concerning MDT measurements metrics that shall be collected by the UE within the area indicated in the first piece of information. Once collected, the UE reports the measurements to a network node (either first network node or a different network node).
  • a network node either first network node or a different network node.
  • the UE when collecting the MDT measurements (e.g., radio measurements quantities such as RSRP or RSRQ of the serving cell and or neighboring cells in logged MDT measurements) the UE logs an indication based on the type of the network it is camping e.g., when camping in the NTN network includes an indication (e.g., a flag) in the measurements indicating the UE is camped in the NTN networks or when camping in the TN network includes an indication (e.g., a flag) in the measurements indicating the UE is camped in the TN networks.
  • Such indication can be used by the network (e.g., OAM) for the post processing and building the coverage map of the NPN network and TN network separately.
  • LogMeasInfoList-r16 :: SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 anyCellSelectionDetected-r16 ENUMERATED ⁇ true ⁇ OPTIONAL, ..., [[ inDeviceCoexDetected-r17 ENUMERATED ⁇ true ⁇ OPTIONAL ]], [[ campedInNTN-r17 ENUMERATED ⁇ true ⁇ OPTIONAL ]] ⁇ 5.5a.3.2 Initiation While T330 is running and SDT procedure is not ongoing, the UE shall: 1 > if measurement logging is suspended: 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging; > if not suspended, perform the logging in accordance with the following: 2> if the reportType is set to periodical in the VarLogMeasConfig: 3> if the UE is in any cell selection state (a
  • N OTE 2 For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. 2 > when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. [0109] There are various potential reasons for wanting UEs to perform and report the results of MDT measurements. A typical reason is to identify coverage holes in a terrestrial network.
  • an additional reason may be to check the performance of a certain satellite, e.g. if the operator suspects that there may be something wrong with the satellite’s transmission equipment, causing it to not fully cover its intended area.
  • area scope definitions for the use case where the performance of a certain satellite is monitored: -
  • the area scope may be defined in terms of a geometrical area in relation to the satellite and let it move with the satellite. For instance, the parameters used for specification of a satellite’s spotbeam coverage in SIB32 in 3GPP TS 36.331 version 1 8.0.0 may be used for this purpose.
  • the UE uses the ephemeris data of the satellite, which is broadcasted in the system information or provided together with, or as a part of, the area scope definition in the MDT c onfiguration (i.e., in the LoggedMeasurementConfiguration RRC message).
  • the area scope is defined as a satellite ID (or list of satellite IDs), e.g. a satellite ID as defined in 3GPP TS 36.331 version 18.0.0 (i.e. the SatelliteId IE).
  • the OAM provides the area scope (directly to the RAN or via the CN) in terms of a list of geographical areas or mapped cell areas/IDs (which could be seen as “subareas), each with a time schedule, e.g. a validity period, which makes the area scope follow the quasi-Earth- fixed cells served by the same satellite (i.e. as the satellite moves its beam to a new cell area, the area scope’s schedule makes the area scope’s current coverage move along with it). With this concept, only one of the area scope’s “subareas” would be valid at a time. [0111] Various alternatives for area scope definitions for other use cases: - The area scope may be defined as either side of a line, e.g.
  • a chain of interconnected points forming a straight or non-straight line This may be done using a polygon with the chain of points creating a line through the UE’s cell area and then closing the polygon around the cell, with margin outside the cell area.
  • the chain of points (forming a straight or non- straight line) can be continued through multiple cells (e.g. through multiple geographically contiguous cell areas) by using overlapping point(s), i.e. one or more point(s) is/are used in the polygon of adjacent cells.
  • One side of the line (chain of points) is indicated by indicating “inside the polygon) and the other side of the line (chain of points) is indicated by indicating “outside the polygon”.
  • the OAM provides the area scope (directly to the RAN or via the CN) in terms of a mapped cell area or a list of mapped cell areas, i.e. mapped cell ID(s).
  • the RAN translates this into an area scope definition (which is sent to the UE in a LoggedMeasurementConfiguration RRC message) consisting of a geometrical area or a broadcasted CGI or list of broadcasted CGIs.
  • the OAM provides the area scope (directly to the RAN or via the CN) in terms of a geographical area and the RAN translates this into an area scope definition (which is sent to the UE in a LoggedMeasurementConfiguration RRC message) consisting of a broadcasted CGI and/or TAI or TAC, or a list of broadcasted CGI(s) and/or TAI(s) or TAC(s).
  • a list of cells e.g., broadcasted CGI(s)
  • - A list of tracking areas e.g.
  • FIG. 8 shows an example of a communication system 800 in which embodiments of the present disclosure may be implemented.
  • the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a Radio Access Network (RAN), and a core network 806, which includes one or more core network nodes 808.
  • the access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs).
  • 3GPP Third Generation Partnership Project
  • APs non-3GPP Access Points
  • at least one of the network nodes 810 is a NTN network node, which includes, for example, a satellite and a gateway (e.g., as illustrated in the example NTN of Figure 4 or in Figure 5).
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • network nodes include disaggregated implementations or portions thereof.
  • the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN Open-RAN
  • An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and/or core network nodes 808.
  • ORAN specification e.g., a specification published by the O-RAN Alliance, or any similar organization
  • Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
  • the network nodes 810 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.
  • UE User Equipment
  • 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.
  • the communication system 800 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 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 812 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 810 and other communication devices.
  • the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 812 and/or with other network nodes or equipment in the telecommunication network 802 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 802.
  • the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 806 includes one more core network nodes (e.g., core network node 808) that are structured with hardware and software components.
  • 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-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and/or the telecommunication network 802, and may be operated by the service provider or on behalf of the service provider.
  • the host 816 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.
  • the communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 800 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunication network 802 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 Internet of Things (IoT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • IoT massive Internet of Things
  • the UEs 812 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804.
  • a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and/or 812D) and network nodes (e.g., network node 810B).
  • the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 814 may be a broadband router enabling access to the core network 806 for the UEs.
  • the hub 814 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 810, or by executable code, script, process, or other instructions in the hub 814.
  • the hub 814 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.
  • the hub 814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • VR Virtual Reality
  • the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices.
  • the hub 814 may have a constant/persistent or intermittent connection to the network node 810B.
  • the hub 814 may also allow for a different communication scheme and/or schedule between the hub 814 and UEs (e.g., UE 812C and/or 812D), and between the hub 814 and the core network 806.
  • the hub 814 is connected to the core network 806 and/or one or more UEs via a wired connection.
  • the hub 814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 804 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection.
  • the hub 814 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 810B.
  • the hub 814 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 810B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • Figure 9 shows a UE 900 in accordance with some embodiments.
  • 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • NB-IoT Narrowband Internet of Things
  • MTC Machine Type Communication
  • eMTC enhanced MTC
  • 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-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehicle-to-Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • 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).
  • 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).
  • the UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, memory 910, a communication interface 912, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one UE to another UE.
  • the processing circuitry 902 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 910.
  • the processing circuitry 902 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.
  • FPGAs Field Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processor
  • the processing circuitry 902 may include multiple Central Processing Units (CPUs).
  • the input/output interface 906 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 900.
  • 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.
  • the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and/or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.
  • the memory 910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916.
  • the memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.
  • the memory 910 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.
  • the processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912.
  • the communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922.
  • the communication interface 912 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 918 and/or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., the antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • a UE may provide an output of data captured by its sensors, through its communication interface 912, 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.
  • 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.
  • 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.
  • a UE when in the form of an IoT 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 IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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/window sensor, a flood/moisture sensor, an electrical 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 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.
  • UAV Unmanned Ae
  • a UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 900 shown in Figure 9.
  • 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.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • Figure 10 shows a network node 1000 in accordance with some embodiments.
  • 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • O-RAN nodes or components of an O-RAN node e.g., O-RU, O-DU, O-CU.
  • 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, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs).
  • RRUs Remote Radio Units
  • RRHs Remote Radio Heads
  • RRUs Remote Radio Heads
  • Such RRUs 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).
  • DAS Distributed Antenna System
  • 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 BS 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).
  • MSR Transmission Point
  • MSR Multi-Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes
  • the network node 1000 includes processing circuitry 1002, memory 1004, a communication interface 1006, and a power source 1008.
  • the network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 1000 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs).
  • the network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 1000.
  • the processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1000 components, such as the memory 1004, to provide network node 1000 functionality.
  • the processing circuitry 1002 includes a System on a Chip (SOC).
  • the processing circuitry 1002 includes one or more of Radio Frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014.
  • RF Radio Frequency
  • the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
  • the memory 1004 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, RAM, 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 memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1002.
  • volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, 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,
  • the memory 1004 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 1002 and utilized by the network node 1000.
  • the memory 1004 may be used to store any calculations made by the processing circuitry 1002 and/or any data received via the communication interface 1006.
  • the processing circuitry 1002 and the memory 1004 are integrated.
  • the communication interface 1006 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010.
  • the radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022.
  • the radio front-end circuitry 1018 may be connected to the antenna 1010 and the processing circuitry 1002.
  • the radio front-end circuitry 1018 may be configured to condition signals communicated between the antenna 1010 and the processing circuitry 1002.
  • the radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1020 and/or the amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface 1006 may comprise different components and/or different combinations of components. [0148] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018; instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010.
  • the communication interface 1006 includes the one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012 as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
  • the antenna 1010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.
  • the antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 1008 provides power to the various components of the network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein.
  • the network node 1000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008.
  • the power source 1008 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.
  • Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 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.
  • the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
  • Figure 11 is a block diagram of a host 1100, which may be an embodiment of the host 816 of Figure 8, in accordance with various aspects described herein.
  • the host 1100 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 1100 may provide one or more services to one or more UEs.
  • the host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a network interface 1108, a power source 1110, and memory 1112.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of the host 1100.
  • the memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g. data generated by a UE for the host 1100 or data generated by the host 1100 for a UE.
  • Embodiments of the host 1100 may utilize only a subset or all of the components shown.
  • the host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • FLAC Free Lossless Audio Codec
  • AAC Advanced Audio Coding
  • the host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1100 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • DASH or MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs Virtual Machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1204 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1208A and 1208B (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.
  • the VMs 1208 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1206.
  • a virtual appliance 1202 may be implemented on one or more of the VMs 1208, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV).
  • NFV Network Function Virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.
  • a VM 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1208, and that part of the hardware 1204 that executes that VM forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202.
  • the hardware 1204 may be implemented in a standalone network node with generic or specific components.
  • the hardware 1204 may implement some functions via virtualization.
  • the hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of the applications 1202.
  • the hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station.
  • some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
  • a control system 1212 which may alternatively be used for communication between hardware nodes and radio units.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • 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 obtained information 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.
  • processing circuitry may process information by, for example, converting the obtained information 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.
  • 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.
  • 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
  • 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.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • 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 hardwired manner.
  • the processing circuitry can be configured to perform the described functionality.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Systems and methods related to Minimization of Drive Testing (MDT) area scopes that are particularly well-suited for Non-Terrestrial Networks (NTNs) are disclosed. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a first network node, information that configures the UE to perform MDT measurements in one or more coverage areas of an NTN. The method further comprises performing the MDT measurements and reporting the MDT measurements to the first network node or another network node. In this manner, an operator or a network is enabled to focus an MDT measurement collection to specific NTN coverage areas.

Description

MDT AREAS SCOPES FOR NTN TECHNICAL FIELD [0001] The present disclosure relates to Minimization of Drive Testing (MDT) measurements in a wireless communication system including a Non-Terrestrial Network (NTN). BACKGROUND MDT Configuration [0002] The following excerpts from 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.413 V18.0.0 are provided where it is shown how a Minimization of Drive Testing (MDT) configuration is formulated and how an MDT area scope is defined. The MDT Area Scope constitutes an area where the User Equipment (UE) is allowed to collect MDT measurements. [0003] NG: Initial Context Setup – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 8.3.1 Initial Context Setup 8.3.1.1 General The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG- RAN node, when required, including PDU session context, the Security Key, Mobility Restriction List, UE Radio Capability and UE Security Capabilities, etc. The AMF may initiate the Initial Context Setup procedure if a UE- associated logical NG-connection exists for the UE or if the AMF has received the RAN UE NGAP ID IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG- connection by sending an INITIAL UE MESSAGE message via another NG interface instance. The procedure uses UE-associated signalling. For signalling only connections and if the UE Context Request IE is not received in the Initial UE Message, the AMF may be configured to trigger the procedure for all NAS procedures or on a per NAS procedure basis depending on operator’s configuration. 8.3.1.2 Successful Operation [REPRODUCED HEREIN AS FIGURE 1] Figure 8.3.1.2-1: Initial context setup: successful operation In case of the establishment of a PDU session the 5GC shall be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received by the AMF. If no UE-associated logical NG- connection exists, the UE-associated logical NG-connection shall be established at reception of the INITIAL CONTEXT SETUP REQUEST message. The INITIAL CONTEXT SETUP REQUEST message shall contain the Index to RAT/Frequency Selection Priority IE, if available in the AMF. If the NAS-PDU IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall pass it transparently towards the UE. If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall - attempt to execute the requested PDU session configuration; - store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for Non-GBR QoS flows for the concerned UE as specified in TS 23.501 [9]; - store the received Mobility Restriction List in the UE context; - store the received UE Radio Capability in the UE context; - store the received Index to RAT/Frequency Selection Priority in the UE context and use it as defined in TS 23.501 [9]; - store the received UE Security Capabilities in the UE context; - store the received Security Key in the UE context and, if the NG-RAN node is required to activate security for the UE, take this security key into use; - if supported, store the received SRVCC Operation Possible in the UE context and use it as defined in TS 23.216 [31]; - store the received NR V2X Services Authorization information, if supported, in the UE context; - store the received LTE V2X Services Authorization information, if supported, in the UE context; - store the received NR A2X Services Authorization information, if supported, in the UE context; - store the received LTE A2X Services Authorization information, if supported, in the UE context; - store the received NR UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE’s sidelink communication in network scheduled mode for NR V2X services; - store the received LTE UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE’s sidelink communication in network scheduled mode for LTE V2X services; - store the received NR A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE’s sidelink communication in network scheduled mode for NR A2X services; - store the received LTE A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE’s sidelink communication in network scheduled mode for LTE A2X services; - store the received PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.287 [33]; - store the A2X PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.256 [54]. - store the received Management Based MDT PLMN List information, if supported, in the UE context; - if supported, store the received IAB Authorization information in the UE context, and use it accordingly for the IAB-MT; - store the received 5G ProSe Authorization information in the UE context, if supported, and use it for the concerned UE’s sidelink communication in network scheduled mode for 5G ProSe services; - store the 5G ProSe UE PC5 Aggregate Maximum Bit Rate in the UE context, if supported, and use it for the concerned UE’s sidelink communication in network scheduled mode for 5G ProSe services; - store the 5G ProSe PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.304 [47]; - store the received Network Controlled Repeater Authorization, if supported, in the UE context; - if supported, store the received Mobile IAB Authorization information in the UE context, and use it accordingly for the mobile IAB-MT; - store the received PDU Set QoS parameters, if supported, in the UE context and use it as specified in TS 23.501 [9]. For the Initial Context Setup an initial value for the Next Hop Chaining Count is stored in the UE context. If the PDU Session Resource Setup Request List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall behave the same as defined in the PDU Session Resource Setup procedure. The NG-RAN node shall report to the AMF in the INITIAL CONTEXT SETUP RESPONSE message the result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure. Upon reception of the INITIAL CONTEXT SETUP RESPONSE message the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Setup Response Transfer IE or PDU Session Resource Setup Unsuccessful Transfer IE to the SMF associated with the concerned PDU session. In case the splitting PDU session is not used by the NG-RAN node, the SMF should remove the Additional Transport Layer Information, if any. The NG-RAN node shall use the information in the Mobility Restriction List IE if present in the INITIAL CONTEXT SETUP REQUEST message to - determine a target for subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE; - select a proper SCG during dual connectivity operation; - assign proper RNA(s) for the UE when moving the UE to RRC_INACTIVE state. If the Mobility Restriction List IE is not contained in the INITIAL CONTEXT SETUP REQUEST message, the NG- RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501 [9]. The NG-RAN node shall also consider that no roaming and no access restriction apply to the UE when: - one of the QoS flows includes a particular ARP value (TS 23.501 [9]). The NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the Allowed PNI-NPN List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, as described in TS 23.501 [9]. If the Trace Activation IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11]. In particular, the NG-RAN node shall, if supported: - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [11]; - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only", initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE; - if the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, store this information and take it into account in the requested MDT session; - if the Trace Activation IE includes the Signalling Based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present. … ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0004] NG: Handover Resource Allocation – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 8.4.2.1 General The purpose of the Handover Resource Allocation procedure is to reserve resources at the target NG-RAN node for the handover of a UE. The procedure uses UE-associated signalling. 8.4.2.2 Successful Operation [REPROUCED HEREIN AS FIGURE 2] Figure 8.4.2.2-1: Handover resource allocation: successful operation The AMF initiates the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. [part omitted] If the Trace Activation IE is included in the HANDOVER REQUEST message the target NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422 [11]. In particular, the NG-RAN node shall, if supported: - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422 [11]; - if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only", initiate the requested MDT session as described in TS 32.422 [11] and the target NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE; - if the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, store this information and take it into account in the requested MDT session; - if the Trace Activation IE includes the Signalling Based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320 [41]. - if the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present. If the Location Reporting Request Type IE is included in the HANDOVER REQUEST message, the target NG-RAN node should perform the requested location reporting functionality for the UE as described in subclause 8.12. … ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0005] Trace Start – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 8.11.1 Trace Start 8.11.1.1 General The purpose of the Trace Start procedure is to allow the AMF to request the NG-RAN node to initiate a trace session for a UE. The procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established as part of the procedure. 8.11.1.2 Successful Operation [REPRODUCED HEREIN AS FIGURE 3] Figure 8.11.1.2-1: Trace start The AMF initiates the procedure by sending a TRACE START message. Upon reception of the TRACE START message, the NG-RAN node shall initiate the requested trace session as described in TS 32.422 [11]. If the Trace Activation IE is included in the TRACE START message which includes the MDT Activation IE set to "Immediate MDT and Trace", the NG-RAN node shall, if supported, initiate the requested trace session and MDT session as described in TS 32.422 [11]. If the Trace Activation IE is included in the TRACE START message which includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only", the NG-RAN node shall, if supported, initiate the requested MDT session as described in TS 32.422 [11] and the NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE. If the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, the NG- RAN node shall, if supported, store this information and take it into account in the requested MDT session. If the Trace Activation IE is included in the TRACE START message which includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only" and if the Signalling Based MDT PLMN List IE is included in the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320 [41]. If the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. If the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. If the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall, if supported, take it into account for MDT Configuration as described in TS 37.320 [41]. If the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration- EUTRA IE shall be present. If the PNI-NPN Area Scope of MDT IE is included in the MDT Configuration-NR IE included in the TRACE START message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas. Upon reception of the PNI-NPN Area Scope of MDT IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the PNI-NPN Area Scope of MDT IE. Interactions with other procedures: If the NG-RAN node is not able to initiate the trace session due to ongoing handover of the UE to another NG-RAN node, the NG-RAN node shall initiate a Trace Failure Indication procedure with the appropriate cause value. ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0006] Trace Activation Information Element (IE) – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.14 Trace Activation This IE defines parameters related to a trace session activation. IE/Group Presence Range IE type and Semantics description Criticality Assig Name reference ned Critica lity NG-RAN M OCTET STRING This IE is composed of the - Trace ID (SIZE(8)) following: Trace Reference defined in TS 32.422 [11] (leftmost 6 octets, with PLMN information encoded as in 9.3.3.5), and Trace Recording Session Reference defined in TS 32.422 [11] (last 2 octets). Interfaces to M BIT STRING Each position in the bitmap - Trace (SIZE(8)) represents an NG-RAN node interface: first bit = NG-C, second bit = Xn-C, third bit = Uu, fourth bit = F1-C, fifth bit = E1: other bits reserved for future use. Value '1' indicates 'should be traced'. Value '0' indicates 'should not be traced'. Trace Depth M ENUMERATED Defined in TS 32.422 [11]. - (minimum, medium, maximum, minimumWithout VendorSpecificE xtension, mediumWithoutV endorSpecificExt ension, maximumWithout VendorSpecificE xtension, …) Trace M Transport Layer For File based Reporting. - Collection Address Defined in TS 32.422 [11]. Entity IP 9.3.2.4 This IE is ignored if the Trace Address Collection Entity URI IE is present. MDT O 9.3.1.167 YES ignore Configuratio n Trace O URI For Streaming based Reporting. YES ignore Collection 9.3.2.14 Defined in TS 32.422 [11]. Entity URI ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0007] MDT Configuration IE – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.167 MDT Configuration This IE defines the MDT configuration parameters. IE/Group Name Presence Range IE type and Semantics description reference MDT Configuration-NR O 9.3.1.169 MDT Configuration-EUTRA O 9.3.1.170 ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0008] MDT PLMN List IE – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.168 MDT PLMN List The purpose of the MDT PLMN List IE is to provide the list of PLMN allowed for MDT. IE/Group Name Presence Range IE type and Semantics description reference MDT PLMN List 1..<maxnoofMDTPLMNs> >PLMN Identity M 9.3.3.5 Range bound Explanation maxnoofMDTPLMNs Maximum no. of PLMNs in the MDT PLMN list. Value is 16. ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0009] MDT Configuration NR IE – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.169 MDT Configuration-NR This IE defines the MDT configuration parameters of NR. IE/Group Name Presenc Range IE type and Semantics Criticalit Assigne e reference description y d Criticalit y MDT Activation M ENUMERAT - ED (Immediate MDT only, Logged MDT only, Immediate MDT and Trace, …) CHOICE Area M - Scope of MDT >Cell based If PNI-NPN Area Scope of MDT IE is present, this IE covers non- CAG cells only, where non-CAG cells refer to cells that only provide public access. >>Cell ID List 1..<maxnoofCellIDforM for MDT DT> >>>NR CGI M 9.3.1.7 - >TA based If PNI-NPN Area Scope of MDT IE is present, this IE covers non- CAG cells only, where non-CAG cells refer to cells that only provide public access. >>TA List for 1..<maxnoofTAforMDT> MDT >>>TAC M 9.3.3.10 The TAI is - derived using the current serving PLMN. >PLMN wide NULL >TAI based If PNI-NPN Area Scope of MDT IE is present, this IE covers non- CAG cells only, where non-CAG cells refer to cells that only provide public access. >>TAI List for 1..<maxnoofTAforMDT> MDT >>>TAI M - >PNI-NPN YES ignore Based MDT >>CAG List 1..<maxnoofCAGforMD - for MDT T> >>>PLMN ID 9.3.3.5 - >>>CAG ID M 9.3.3.43 - >SNPN Cell YES ignore Based MDT >>SNPN Cell 1..<maxnoofCellIDforM - ID List for DT> MDT >>>NR CGI M 9.3.1.7 - - >>>NID M 9.3.3.42 Identifies an - - SNPN together with the PLMN Identity in the NR CGI IE. >SNPN TAI YES ignore Based MDT >>SNPN TAI 1..<maxnoofTAforMDT> - - List >>>TAI M 9.3.3.11 - - >>>NID M 9.3.3.42 Identifies an - - SNPN together with the PLMN Identity in the TAI IE. >SNPN Based YES ignore MDT >>MDT SNPN 1..<maxnoofMDTSNPN - List s> >>>PLMN M 9.3.3.5 - Identity >>>NID M 9.3.3.42 Identifies an - SNPN together with the PLMN Identity IE. CHOICE MDT M - Mode >Immediate MDT
>>Measureme M BITSTRING Each position - nts to Activate (SIZE(8)) in the bitmap indicates a MDT measurement, as defined in TS 37.320 [41]. First Bit = M1, Second Bit= M2, Third Bit = M4, Fourth Bit = M5, Fifth Bit = M6, Sixth Bit = M7, Seventh Bit = logging of M1 from event triggered measurement reports according to existing RRM configuration, other bits reserved for future use. Value “1” indicates “activate” and value “0” indicates “do not activate”. >>M1 C-ifM1 9.3.1.171 - Configuration >>M4 C-ifM4 9.3.1.172 - Configuration >>M5 C-ifM5 9.3.1.173 - Configuration >>M6 C-ifM6 9.3.1.174 - Configuration >>M7 C-ifM7 9.3.1.175 - Configuration >>Bluetooth O 9.3.1.177 - Measurement Configuration >>WLAN O 9.3.1.178 - Measurement Configuration >>MDT O 9.3.1.176 - Location Information >>Sensor O 9.3.1.179 - Measurement Configuration >Logged MDT >>Logging M ENUMERAT Corresponds - Interval ED (320ms, to the 640ms, LoggingInterv 1280ms, al IE as 2560ms, defined in TS 5120ms, 38.331 [18]. 10240ms, 20480ms, 30720ms, 40960ms, 61440ms, infinity, …) >>Logging M ENUMERAT Corresponds - Duration ED (10, 20, to the 40, 60, LoggingDurati 90,120, …) on IE as defined in TS 38.331 [18]. Unit: [minute]. >>CHOICE M - Report Type >>>Periodica NULL l >>>Event Triggered >>>>Event M 9.3.1.180 - Trigger Logged MDT Configuratio n >>Bluetooth O 9.3.1.177 - Measurement Configuration >>WLAN O 9.3.1.178 - Measurement Configuration >>Sensor O 9.3.1.179 - Measurement Configuration >>Area Scope O 9.3.1.182 - of Neighbour Cells >>Early O ENUMERAT This IE YES ignore Measurement ED indicates (true, ...) whether the UE is allowed to log measurement s on early measurement related frequencies in logged MDT as specified in TS 38.331 [18]. Signalling Based O MDT PLMN - MDT PLMN List List 9.3.1.168 PNI-NPN Area O 9.3.3.65 This IE is YES ignore Scope of MDT ignored if the PLMN Wide IE is present Range bound Explanation maxnoofCellIDforMDT Maximum no. of Cell ID subject for MDT scope. Value is 32. maxnoofTAforMDT Maximum no. of TA subject for MDT scope. Value is 8. maxnoofCAGforMDT Maximum no. of CAG IDs for MDT scope. Value is 256. maxnoofMDTSNPNs Maximum no. of SNPNs in the MDT SNPN list. Value is 16. Condition Explanation C-ifM1 This IE shall be present if the Measurements to Activate IE has the first bit set to “1”. C-ifM4 This IE shall be present if the Measurements to Activate IE has the third bit set to “1”. C-ifM5 This IE shall be present if the Measurements to Activate IE has the fourth bit set to “1”. C-ifM6 This IE shall be present if the Measurements to Activate IE has the fitth bit set to “1”. C-ifM7 This IE shall be present if the Measurements to Activate IE has the sixth bit set to “1”. ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0010] Area Scope of Neighbour Cells IE – Excerpt from TS38.413 ***** START EXCERPT FROM 3GPP TS 38.413 ***** 9.3.1.182 Area Scope of Neighbour Cells This IE defines the area scope of neighbour cells for logged MDT. IE/Group Name Presence Range IE type and Semantics description reference Area Scope of M 1..<maxnoofFreqforMDT> Neighbour Cells Item >NR Frequency Info M 9.3.1.181 >PCI List for MDT 0.. <maxnoofNeighPCIforMDT> >>NR PCI M INTEGER NR Physical Cell ID (0..1007, …) Range bound Explanation maxnoofFreqforMDT Maximum no. of Frequency Information subject for MDT scope. Value is 8. maxnoofNeighPCIforMDT Maximum no. of Neighbour cells subject for MDT scope. Value is 32. ***** END EXCERPT FROM 3GPP TS 38.413 ***** [0011] As can be appreciated from the above, the Area Scope constitutes of a list of identifiers identifying an area. The Area Scope determines the area where MDT measurements shall be collected, as specified in TS32.422, as follows: ***** START EXCERPT FROM 3GPP TS 38.413 ***** 5.10.2 Area Scope The Area Scope optional parameter defines the area in terms of Cells or Tracking Area/Routing Area/Location Area where the MDT data collection shall take place. The area scope specified in an MDT session shall support the PLMNs of the MDT PLMN list (defined in clause 5.10.24). If the parameter is not present the MDT data collection shall be done throughout the PLMNs of the MDT PLMN list. For further details see also TS 37.320 [30]. The Area Scope parameter in UMTS is either: - list of Cells, identified by CGI. Maximum 32 CGI can be defined. - List of Routing Area, identified by RAI. Maximum of 8 RAIs can be defined. - List of Location Area, identified by LAI. Maximum of 8 LAIs can de defined. The Area Scope parameter in LTE and NR is either: - list of Cells, identified by E-UTRAN-CGI or NG-RAN CGI. Maximum 32 CGI can be defined. - List of Tracking Area, identified by TAC. Maximum of 8 TAC can be defined. - List of Tracking Area Identity, identified by TAC with associated plmn-Identity perTAC-List containing the PLMN identity for each TAC. Maximum of 8 TAI can be defined. For further details see also TS 36.331[32]. ***** END EXCERPT FROM 3GPP TS 38.413 ***** Non-Terrestrial Network Overview [0012] Consider a wireless network that has a Non-Terrestrial Network (NTN) component. The NTN component uses a constellation of several satellites (e.g., Low-Earth Orbiting (LEO) satellite(s), Medium-Earth Orbiting (MEO) satellite(s), Geostationary Orbit (GEO) satellite(s), etc.) that can orbit using one or more orbit planes. Each satellite can provide wireless network access to UEs positioned on, or near, the Earth’s surface via the respective service link. This is done by satellites having on board antennas that can radiate beams towards (multiple) centers of Earth-Fixed Cells (EFCs). These can be transmitter beams for the downlink (DL), and receiver beams for the uplink (UL). Notice that, in the downlink, the total power of the satellite antenna is shared between simultaneous DL beams, something which is not true for the UL. This setup is depicted in Figure 4. [0013] The satellite antenna is connected to a Radio Access Network (RAN) node, e.g., a gNodeB (gNB) in the case of 3GPP New Radio (NR). Depending on the architecture, components of the nodes can be located either on the ground, or onboard the satellite. The ground components and the onboard components are connected through satellite gateways via the feeder link. [0014] Like the terrestrial network, each node is expected to provide coverage to a specific territory by dividing the area into coverage sectors. In the case of NTN, the nodes are using the satellites as mediums to transmit the corresponding radio signals through the beams towards those areas. [0015] In general, NTN was studied in 3GPP within 3GPP Technical Report (TR) 38.811 “Study on New Radio (NR) to support non-terrestrial networks (Rel-15)” and 3GPP TR 38.821 “Solutions for NR to support non-terrestrial networks (NTN) (Rel-16).” Please refer to those documents for details. [0016] Mapped Cell [0017] The concept of mapped cells is specific to NTN. Below, excerpts from 3GPP TS 38.300 v18.0.0 are provided in which the definition of a “Mapped Cell” is shown. ***** START EXCERPT FROM 3GPP TS 38.300 ***** 3.2 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1], in TS 36.300 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 36.300 [2]. A2X communication: A communication to support A2X services leveraging PC5 reference points. A2X services are realized by various types of A2X applications, i.e. BRID or DAA. Aerial UE communication: functionality enabling Aerial UE function, as defined in 16.18. Air to Ground network: An NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m. BH RLC channel: an RLC channel between two nodes, which is used to transport backhaul packets. Boundary IAB-node: as defined in TS 38.401 [4]. Broadcast MRB: A radio bearer configured for MBS broadcast delivery. CAG Cell: a PLMN cell broadcasting at least one Closed Access Group identity. CAG Member Cell: for a UE, a CAG cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the Allowed CAG list of the UE for that PLMN. CAG-only cell: a CAG cell that is only available for normal service for CAG UEs. Cell-Defining SSB: an SSB with an RMSI associated. Child node: IAB-DU's and IAB-donor-DU's next hop neighbour node; the child node is also an IAB-node. Conditional Handover (CHO): a handover procedure that is executed only when execution condition(s) are met. CORESET#0: the control resource set for at least SIB1 scheduling, can be configured either via MIB or via dedicated RRC signalling. DAPS Handover: a handover procedure that maintains the source gNB connection after reception of RRC message for handover and until releasing the source cell after successful random access to the target gNB. Data Burst: A set of multiple PDUs generated and sent by the application in a short period of time, as defined in TS 23.501 [3]. Direct Path: a type of UE-to-Network transmission path, where data is transmitted between a UE and the network without sidelink relaying. Downstream: direction toward child node or UE in IAB-topology. Early Data Forwarding: data forwarding that is initiated before the UE executes the handover. Earth-centered, earth-fixed: a global geodetic reference system for the Earth intended for practical applications of mapping, charting, geopositioning and navigation, as specified in NIMA TR 8350.2 [51]. eRedCap UE: a UE with enhanced reduced capabilities as specified in clause 4.2.22.1 in TS 38.306 [11]. Feeder link: wireless link between the NTN Gateway and the NTN payload. Geosynchronous Orbit: earth-centered orbit at approximately 35786 kilometres above Earth's surface and synchronised with Earth's rotation. A geostationary orbit is a non-inclined geosynchronous orbit, i.e. in the Earth's equator plane. Group ID for Network Selection: an identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder, as specified in TS 23.501 [3]. gNB: node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. High Altitude Platform Station: airborne vehicle embarking the NTN payload placed at an altitude between 8 and 50 km. IAB-donor: gNB that provides network access to UEs via a network of backhaul and access links. IAB-donor-CU: as defined in TS 38.401 [4]. IAB-donor-DU: as defined in TS 38.401 [4]. IAB-DU: gNB-DU functionality supported by the IAB-node to terminate the NR access interface to UEs and next- hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, as defined in TS 38.401 [4], on the IAB-donor. IAB-MT: IAB-node function that terminates the Uu interface to the parent node using the procedures and behaviours specified for UEs unless stated otherwise. IAB-MT function used in 38-series of 3GPP Specifications corresponds to IAB-UE function defined in TS 23.501 [3]. IAB-node: RAN node that supports NR access links to UEs and NR backhaul links to parent nodes and child nodes. The IAB-node does not support backhauling via LTE. IAB topology: the unison of all IAB-nodes and IAB-donor-DUs whose F1 and/or RRC connections are terminated at the same IAB-donor-CU. Indirect Path: a type of UE-to-Network transmission path, where data is forwarded via a U2N Relay UE between a U2N Remote UE and the network. Inter-donor partial migration: migration of an IAB-MT to a parent node underneath a different IAB-donor-CU while the collocated IAB-DU and its descendant IAB-node(s), if any, are terminated at the initial IAB-donor-CU. The procedure renders the said IAB-node as a boundary IAB-node. Intra-system Handover: handover that does not involve a CN change (EPC or 5GC). Inter-system Handover: handover that involves a CN change (EPC or 5GC). Late Data Forwarding: data forwarding that is initiated after the source NG-RAN node knows that the UE has successfully accessed a target NG-RAN node. L1/L2 Triggered Mobility: a cell switch procedure that the network triggers via MAC CE based on L1 measurements. Mapped Cell ID: in NTN, it corresponds to a fixed geographical area. … ***** START NEXT EXCERPT FROM 3GPP TS 38.300 ***** 16.14 Non-Terrestrial Networks 16.14.1 Overview Figure 16.14.1-1 below illustrates an example of a Non-Terrestrial Network (NTN) providing non-terrestrial NR access to the UE by means of an NTN payload and an NTN Gateway, depicting a service link between the NTN payload and a UE, and a feeder link between the NTN Gateway and the NTN payload. [REPRODUCED HEREIN AS FIGURE 5] Figure 16.14.1-1: Overall illustration of an NTN NOTE 1: Figure 16.14.1-1 illustrates an NTN; RAN4 aspects are out of scope. The NTN payload transparently forwards the radio protocol received from the UE (via the service link) to the NTN Gateway (via the feeder link) and vice-versa. The following connectivity is supported by the NTN payload: - An NTN gateway may serve multiple NTN payloads; - An NTN payload may be served by multiple NTN gateways. NOTE 2: In this release, the NTN-payload may change the carrier frequency, before re-transmitting it on the service link, and vice versa (respectively on the feeder link). For NTN, the following applies in addition to Network Identities as described in clause 8.2: - A Tracking Area corresponds to a fixed geographical area. Any respective mapping is configured in the RAN; - A Mapped Cell ID as specified in clause 16.14.5. … ***** START NEXT EXCERPT FROM 3GPP TS 38.300 ***** 16.14.5 NG-RAN signalling The Cell Identity, as defined in TS 38.413 [26] and TS 38.423 [50], used in following cases corresponds to a Mapped Cell ID, irrespective of the orbit of the NTN payload or the types of service links supported: - The Cell Identity indicated by the gNB to the Core Network as part of the User Location Information; - The Cell Identity used for Paging Optimization in NG interface; - The Cell Identity used for Area of Interest; - The Cell Identity used for PWS. The Cell Identity included within the target identification of the handover messages allows identifying the correct target cell. The cell identity used in the NG and Xn handover messages, Xn Setup and Xn NG-RAN Node Configuration Update procedures is expected to be Uu Cell ID. The Cell Identities used in the RAN Paging Area during Xn RAN paging allow the identification of the correct target cells for RAN paging. NOTE 1: The Cell Identity used for RAN Paging is assumed to typically represent a Uu Cell ID. The mapping between Mapped Cell IDs and geographical areas is configured in the RAN and Core Network. NOTE 2: A specific geographical location may be mapped to multiple Mapped Cell ID(s), and such Mapped Cell IDs may be configured to indicate differerent geographical areas (e.g. overlapping and/or with different dimensions). The gNB is responsible for constructing the Mapped Cell ID based on the UE location information received from the UE, if available. The mapping may be pre-configured (e.g., up to operator's policy) or up to implementation. NOTE 3: As described in TS 23.501 [3], the User Location Information may enable the AMF to determine whether the UE is allowed to operate at its present location. Special Mapped Cell IDs or TACs may be used to indicate areas outside the serving PLMN's country. The gNB reports the broadcasted TAC(s) of the selected PLMN to the AMF as part of ULI. In case the gNB knows the UE's location information, the gNB may determine the TAI the UE is currently located in and provide that TAI to the AMF as part of ULI. ***** END EXCERPTS FROM 3GPP TS 38.300 ***** SUMMARY [0018] Systems and methods related to Minimization of Drive Testing (MDT) area scopes that are particularly well-suited for Non-Terrestrial Networks (NTNs) are disclosed. In one embodiment, a method performed by a User Equipment (UE) comprises receiving, from a first network node, information that configures the UE to perform MDT measurements in one or more coverage areas of an NTN. The method further comprises performing the MDT measurements and reporting the MDT measurements to the first network node or another network node. In this manner, an operator or a network is enabled to focus an MDT measurement collection to specific NTN coverage areas. [0019] In one embodiment, the information that configures the UE to perform MDT measurements in the one or more coverage areas of the NTN comprises one or more list of identities that identify the one or more coverage areas of the NTN. [0020] In one embodiment, the information that configures the UE to perform MDT measurements in the one or more coverage areas of the NTN comprises information that indicates one or more geographical areas that correspond to the one or more coverage areas of the NTN. [0021] In one embodiment, the information that configures the UE to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking areas, a list of registration areas, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state. [0022] In one embodiment, the information that configures the UE (604) to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. [0023] In one embodiment, the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises one or more elements related to the NTN. [0024] In one embodiment, the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific. [0025] In one embodiment, the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN. [0026] In one embodiment, the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. [0027] In another embodiment, a method performed by a UE comprises receiving, from a first network node, information that configures the UE to perform MDT measurements in one or more coverage areas for a NTN and a Terrestrial Network (TN), performing the MDT measurements in accordance with the received information, and reporting the MDT measurements to the first network node (700) or another network node together with an indication(s) that indicates whether the MDT measurements are for the NTN or the TN. [0028] In one embodiment, the indication(s) comprise a separate indication for each MDT measurement. [0029] Corresponding embodiments of a UE are also disclosed. [0030] Embodiments of a method performed by a first network node are also disclosed. In one embodiment, a method performed by a first network node comprises receiving, from a second network node, first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a NTN, and configuring a UE to perform one or more MDT measurements in at least one of the one or more coverage areas of the NTN. [0031] In one embodiment, the method further comprises receiving second information comprising information about the MDT measurements. In one embodiment, the second information comprises an MDT measurements configuration. In one embodiment, the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements. [0032] In one embodiment, the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN. [0033] In one embodiment, configuring the UE to perform the one or more MDT measurements comprises configuring the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state. [0034] In one embodiment, configuring the UE to perform the one or more MDT measurements comprises configuring the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. [0035] In one embodiment, the second information comprises an MDT configuration that comprises one or more elements related to the NTN. [0036] In one embodiment, the second information comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific. [0037] In one embodiment, the second information comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN. In one embodiment, the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. [0038] In one embodiment, the second information is comprised in a UE context modification related message, and the second information relates to a modification to a management based MDT configuration. In one embodiment, the management based MDT configuration comprises a list of PLMNs allowed for MDT and an associated indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. [0039] In one embodiment, the first information comprises an NTN geographical area list for MDT comprised in an MDT configuration. [0040] In one embodiment, the first information comprises information that indicates a geographic area for a list of NTN geographical areas for MDT indicated for an area scope of neighbor cells from which the UE is to collect the MDT measurements. [0041] In another embodiment, a method performed by a first network node comprises receiving, from a second network node, first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a NTN and a TN, and configuring a UE to perform one or more MDT measurements in at least one of the one or more coverage areas of the NTN and TN. [0042] In one embodiment, the method further comprises receiving second information comprising information about the MDT measurements. In one embodiment, the second information comprises an MDT measurements configuration. In one embodiment, the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements. [0043] In one embodiment, the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN and TN. [0044] In one embodiment, configuring the UE to perform the one or more MDT measurements comprises configuring the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in a connected state. [0045] In one embodiment, configuring the UE to perform the one or more MDT measurements comprises configuring the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. [0046] In one embodiment, MDT measurements reported by the UE in response to the configuring comprise or are otherwise associated to an indicator that indicates whether the MDT measurements are for the NTN or the TN. [0047] Corresponding embodiments of a first network node are also disclosed. BRIEF DESCRIPTION OF THE DRAWINGS [0048] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. [0049] Figure 1 is a reproduction of Figure 8.3.1.2-1 of 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.413 v18.0.0; [0050] Figure 2 is a reproduction of Figure 8.4.2.2-1 of 3GPP TS 38.413 v18.0.0; [0051] Figure 3 is a reproduction of Figure 8.11.1.2-1 of 3GPP TS 38.413 v18.0.0; [0052] Figure 4 illustrates an example of a Non-Terrestrial Network (NTN); [0053] Figure 5 is a reproduction of Figure 16.14.1-1 of 3GPP TS 38.300 v18.0.0; [0054] Figure 6 illustrates the operation of a first network node, a second network node, and a User Equipment (UE), in accordance with some embodiments of the present disclosure; [0055] Figure 7 illustrates the operation of a first network node, a second network node, and a UE, in accordance with some other embodiments of the present disclosure; [0056] Figure 8 shows an example of a communication system in accordance with some embodiments of the present disclosure; [0057] Figure 9 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure; [0058] Figure 10 shows a network node in accordance with some embodiments of the present disclosure; [0059] Figure 11 is a block diagram of a host, which may be an embodiment of the host of Figure 8, in accordance with various aspects of the present disclosure described herein; [0060] Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized; and DETAILED DESCRIPTION [0061] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure. [0062] Some of the embodiments contemplated herein will now be described more fully with 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. [0063] There currently exist certain challenge(s). In the current solution for Minimization o Drive Testing (MDT), it is not possible to specify that MDT measurements shall be collected in specific areas covered by Non-Terrestrial Networks (NTNs). With this, it is not possible for an operator to trigger MDT measurements that can monitor the performance of services provided via specific NTNs or NTN coverage areas. [0064] This creates problems in terms of visibility of NTN network performance and configuration. In some cases, the latter implies that, in order to monitor the performance of NTNs, the operator has to define a generic Area Scope for MDT and collect MDT measurements there. The result of such measurement collection will have to be post-processed to determine which of the collected measurements are derived from NTNs or from parts of NTNs. This may result in lengthy and resource intensive data post-processing procedures. In some other cases, it would not even be possible to deduce whether existing measurements apply to NTNs because NTN coverage may constitute of parts of a cell or a Tracking Area Identity (TAI). Therefore, current MDT area scope mechanisms, which can be used to trigger measurement collection at best with a per cell granularity, are not able to identify all possible coverage areas corresponding to an NTN. As a consequence, the problem is that current MDT area scope will trigger collection of measurements coming from areas served by an NTN as well as from areas served by non-NTN networks, e.g., a Terrestrial Network (TN), without making it possible to differentiate which measurement relates to which network. [0065] With lack of observability over the performance of an NTN network, it becomes impossible to deduce whether an issue detected by means of MDT measurements should be attributed to e.g. a misconfiguration in an NTN infrastructure or any other issue in a TN system. This denies the possibility to apply dedicated and effective correction/optimisation measures, hence increasing the costs of network operation and degrading the overall system´s performance. [0066] In addition, considering the current MDT measurements collection framework and in particular based on the current MDT reports, there is no possibility for the network nodes (e.g., operation and management system) to build the coverage map of the NTN based on the collected MDT measurements. [0067] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of the solution(s) described herein apply to Radio Access Networks (RANs) supporting NTN. Without loss of generality, the description provided herein takes a 5th Generation (5G) system into account. However, embodiments of the solution(s) described herein can be applied to any system supporting NTN. [0068] In the remaining parts of the description, the term “network node” is used to specify any of the following entities: a logical node, a function, a system. [0069] Figure 6 illustrates the operation of a first network node 600, a second network node 602, and a UE 604, in accordance with some embodiments of the present disclosure. Optional steps are represented by dashed lines/boxes. The first network node 600 is, in some embodiments, a RAN node such as, e.g., a gNB, a gNB-Central Unit (CU), or a gNB-CU-Control Plane (CP). The first network node 600 may be a TN node (i.e., a network node of a TN) or an NTN node (e.g., a network node of a NTN which may include, e.g., a satellite and gateway). The second network node 602 is, in some embodiments, a core network node (e.g., an Access and Mobility Management Function (AMF)) or an Operations, Administration, and Maintenance (OAM) system. [0070] As illustrated, the first network node 600 receives, from the second network node 602, first information concerning (e.g., about or that indicates) one or more coverage areas of an NTN (step 606). The coverage areas of the NTN are used to derive, or otherwise define, the coverage area(s) where MDT measurements are to be collected. The first information includes, for example, a list of identifiers identifying the one or more coverage areas of the NTN (also referred to herein as the areas of coverage of the NTN), where such NTN coverage area identifiers are used to derive the coverage areas where MDT measurements shall be collected. In addition to the first information, the first network node 600 may receive from the second network node 602 (or another network node), information concerning MDT measurements that are to be measured by UEs within the coverage areas of the NTN indicated by the first information (step 608). Note that the first information of step 606 and the second information of step 608 may be received from the same network node, in which case the first information and the second information may be included in a single message (e.g., RRC message) containing one or more information elements or may be received via separate messages. Alternatively, the first information of step 606 and the second information of step 608 may be received from separate network nodes (e.g., the first information may be received from an OAM system and the second information may be received from a core network node (e.g., AMF)). [0071] The first network node 600 uses the first information of step 606 and the second information of step 608 to configure the UE 604 to perform MDT measurements in at least one of the indicated coverage areas of the NTN (step 610). The UE 604 performs the configured MDT measurements and reports the MDT measurements, e.g., to the first network node 600 or another network node (step 612). In other words, once the MDT measurements are collected, the UE 604 reports the measurements to a network node (e.g., either the first network node or a different network node). Note that while Figure 6 shows only one UE 604, any number of one or more UEs 604 (e.g., multiple or many UEs) may be configured to perform such MDT measurements in the coverage area(s) of the NTN. [0072] In one embodiment, the first network node 600 may use the received first and second information to configure the UE 604 in step 610 for immediate MDT measurements, namely MDT measurements collected by the UE in a connected stated (e.g., Radio Resource Control (RRC) connected stated, i.e., RRC_CONNECTED state). For the following description, the RRC_CONNECTED state is used as an example of the connected state. In this embodiment, the first network node 600 checks an area where the UE 604 is served while in RRC_CONNECTED, where such area may be constituted by, for example, a cell, a tracking area, a registration area, a Public Land Mobile Network (PLMN), a mapped cell, a geographical area (such as a polygon shaped geographical area, a circle shaped geographical area, etc.), a list of cells, a list of tracking areas, a list of registration areas, a list of PLMNs, a list of mapped cells, or a list of geographical areas. The first network node 600 verifies that the area where the UE 604 is served corresponds to at least one of the coverage areas of the NTN indicated by the first information received from the second network node 602 in step 606. Upon verifying that the area where the UE 604 is served while in RRC_CONNECTED corresponds to at least one of the coverage areas of the NTN signaled by the second network node in step 606, the first network node 600 configures the UE 604 with MDT measurements. Such MDT measurements configuration may include an MDT measurements configuration received from the second network node 608 (e.g., as or as part of the second information of step 608) together with the first information that indicates the one or more coverage areas of the NTN. [0073] In another embodiment, the first network node 600 uses the first and second information received from the second network node 602 to configure the UE 604, in step 610, with logged MDT measurements, namely measurements logged by the UE 604 while in an idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE) that are to be reported by the UE 604 (e.g., in step 612) to the network once the UE 604 moves back to connected state (e.g., RRC_CONNECTED). In this embodiment, the first network node 600 signals, to the UE 604, (e.g., in step 610) identifiers representing the one or more coverage areas of the NTN where logged MDT measurements should be collected. Additionally, the first network node 600 can signal to the UE 604 (e.g., in step 610) also the MDT measurements configuration that the UE 604 is to use when camping in any areas covered by the one or more coverage areas of the NTN. [0074] Figure 7 illustrates the operation of a first network node 700, a second network node 702, and a UE 704, in accordance with some other embodiments of the present disclosure. Optional steps are represented by dashed lines/boxes. The first network node 700 is, in some embodiments, a RAN node such as, e.g., a gNB, a gNB-CU, or a gNB-CU-CP. The first network node 700 may be a TN node (i.e., a network node of a TN) or an NTN node (e.g., a network node of a NTN which may include, e.g., a satellite and gateway). The second network node 702 is, in some embodiments, a core network node (e.g., an AMF) or an OAM system. [0075] As illustrated in Figure 7, in some embodiments, the first network node 700, receives from the second network node 702, first information that indicates coverages areas of an NTN and an TN (together) (step 706). In one embodiment, the first information is information concerning (e.g., including) one or more list of identifiers identifying of the coverage areas of the NTN and TN networks (together), where such TN and NTN area identifiers are used to derive the coverage areas where MDT measurements are to be collected from TN and NTN networks. Additionally, to the first information, the first network node 700 may receive second information about MDT measurements to be collected in the indicated coverage areas of the NTN and TN networks (step 708). The second information includes, for example, an MDT measurements configuration(s) including one or more configuration parameters/metrics concerning MDT measurements metrics that are to be collected by the UE within the coverage area(s) indicated by the first information. Note that the first information of step 706 and the second information of step 708 may be received from the same network node, in which case the first information and the second information may be included in a single message (e.g., RRC message) containing one or more information elements or may be received via separate messages. Alternatively, the first information of step 706 and the second information of step 708 may be received from separate network nodes (e.g., the first information may be received from an OAM system and the second information may be received from a core network node (e.g., AMF)). [0076] The first network node 700 uses the first information of step 706 and the second information of step 708 to configure the UE 704 to perform MDT measurements in at least one of the indicated coverage areas of the NTN and TN networks (step 710). The UE 604 performs the configured MDT measurements and reports the MDT measurements, e.g., to the first network node 700 or another network node (step 712). In other words, once the configured MDT measurements are collected, the UE 704 reports the measurements to a network node (either first network node or a different network node). In this embodiment, the UE 704, upon collecting the MDT measurements when camping in the NTN includes an indication (e.g., a flag) in the MDT measurements indicating whether the measurement is collected in the NTN or in the TN. Such indication can be used by the network (e.g., OAM) for the post-processing and building a coverage map of the NPN and TN separately. [0077] According to the above embodiments, the UE (e.g., UE 604 and/or UE 704) will collect the configured MDT measurements only when served or camped in the NTN areas that are part of the MDT area scope for NTN signaled to the first network node (e.g., first network node 600 or 700) by the second network node (e.g., second network node 602 or 702). [0078] Embodiments of the present disclosure include a first network node, e.g. a RAN node or function, that receives information comprising one or more identifiers identifying one or more NTN coverage areas. With this information, the first network node is able to configure UEs with MDT measurements, which are either collected by the UEs while in a connected state (e.g., RRC_CONNECTED) or logged by the UEs while in an idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE), only if the UE is connected to or camped in an area corresponding to at least one of the one or more NTN coverage areas identified by the information received by the first network node or function and with associated MDT measurements. In some embodiments, information concerning the NTN coverage area(s) (e.g., the one or more identifiers that identify the one or more NTN coverage areas) is also provided from the first network node to the UE. With this information the UE is able, while in idle state (e.g., RRC_IDLE) or inactive state (e.g., RRC_INACTIVE), to check if any of the camping cell, areas of a cell, or neighbor cell correspond to any of the NTN coverage areas indicated by the information received from the first network node. If yes, the UE is able to camp on such cell and measure and log the configured MDT measurements. [0079] Embodiments of the present disclosure enable a framework where MDT measurements are collected only in specific NTN coverage areas. The latter enables NTN area specific observability, which can be used to, for example, monitor whether service level agreements within an NTN network are fulfilled. [0080] Certain embodiments may provide one or more of the following technical advantage(s). Embodiments of the present disclosure may enable an operator or a network to focus an MDT measurement collection to specific NTN coverage areas. This provides the advantage of collecting measurements that are pertinent to UEs and services associated with specific NTN coverage areas and that can, for example, be used to monitor whether service level agreements are fulfilled or configurations concerning coverage, network performance, mobility and more are operating as expected. In other words, embodiments of the present disclosure may enable the network/operators to build e.g., a coverage map and/or data determining the performance of an NTN coverage area. [0081] Additionally, embodiments of the present disclosure may enable reduction in the amount of data collected when focusing on NTN network observability. This implies a reduction of overhead in data uploading from the UE to the network, as well as a reduction of data post processing and filtering at the network because the data collected by UEs are triggered only if the UE is within specific NTN coverage areas. [0082] In some embodiments, the second information received by the first network node (e.g., the first network node 600 or 700) includes an MDT Configuration for NR (e.g., a modified MDT Configuration-NR IE). In one embodiment, the MDT Configuration for NR (e.g. the MDT Configuration-NR IE) is extended with one or more elements related to the NTN deployment. For instance, the CHOICE Information Element Area Scope of MDT is extended with one element pertaining to NTN (e.g. an NTN Based MDT IE) and comprising one or more parameters that are NTN specific. For example, the one or more parameters that are NTN specific may include any one or more of the following: information that indicates cells (e.g., cell identities) mapped to NTN, information that defines one or more polygon-shaped geographic areas, one or more satellite IDs, etc. [0083] A network operator may have commercial agreements with third parties, or alternatively it can directly operate, a communication network which comprises both a TN and a NTN, wherein the TN corresponds to a first Public Land Mobile Network (PLMN), and the NTN corresponds to a second PLMN. If the network operator is interested in collecting UE measurements from both the TN and the NTN, the RAN node (e.g., the first network node 600 or 7000) and the UE (e.g., the UE 604 or 704) need to be instructed accordingly. [0084] In one option of the embodiments that follow, a first PLMN is associated with an NTN and a second PLMN is associated with a TN, wherein the first PLMN is different from the second PLMN. In another option, a certain PLMN is associated with both an NTN and a TN. [0085] In some embodiments, the second information received by the first network node (e.g., the first network node 600 or 700) includes a set of MDT configuration parameters (e.g., a modified MDT Configuration NR IE). In one embodiment, the set of MDT configuration parameters (e.g., the MDT Configuration NR IE) is extended to indicate whether the MDT configuration is applicable only to NTN, or to both NTN and TN. [0086] In one embodiment, the MDT Configuration is extended to be able to discriminate whether a certain PLMN allowed for MDT is associated with a NTN, or with a TN. For instance, within the Signaling Based MDT PLMN List, the MDT PLMN List IE is extended with a flag to indicate whether a PLMN allowed for MDT is associated with an NTN or with a TN. With this extension, the RAN node (e.g., the first network node 600 or X700) receiving a list of two (or more) PLMNs in the MDT PLMN List (e.g., as part of the second information of step 608 or 708), of which at least one is associated with an NTN, and another one not associated with an NTN (i.e., associated with a TN), it can determine to collect the MDT measurements for a UE (e.g., the UE 604 or 704) that is moving across an area that is partly covered by the first PLMN (e.g., across the corresponding NTN) and partly covered by the second PLMN (e.g., across the corresponding TN). Another possibility is that the MDT Configuration is constructed to only include one or more PLMN associated with NTN, in which case the RAN node determines that MDT measurements will be collected only for NTN. [0087] In one example of implementation, the extension of the MDT PLMN List IE can be realized as follows: 9.3.1.168 MDT PLMN List The purpose of the MDT PLMN List IE is to provide the list of PLMN allowed for MDT. IE/Group Name Presence Range IE type and Semantics description reference MDT PLMN List 1..<maxnoofM DTPLMNs> >PLMN Identity M 9.3.3.5 >PLMN Type O ENUMERATE Indicates whether D(‘ntn’,…) the PLMN pertains to an NTN. Range bound Explanation maxnoofMDTPLMNs Maximum no. of PLMNs in the MDT PLMN list. Value is 16. [0088] In case of UE Context modification, the Access and Mobility Management Function (AMF) (e.g., the second network node 602 or 702) provides UE Context information changes to an NG-RAN node (e.g., the first network node 600 or 700), e.g., as part of the second information of step 608 or 708. This can be used to apply modification to the Management Based MDT configuration. In one embodiment, the list of PLMN allowed for MDT is modified, and a flag indicates whether the PLMN relates to an NTN. For example, the MDT PLMN Modification List IE is extended as follows: 9.3.1.243 MDT PLMN Modification List This IE provides the modified list of PLMN allowed for MDT. IE/Group Name Presence Range IE type and Semantics description reference MDT PLMN Modification 0..<maxnoofM An empty list indicates there List DTPLMNs> is no PLMN allowed for MDT. >PLMN Identity M 9.3.3.5 >PLMN Type O ENUMERATE Indicates whether D(‘ntn’,…) the PLMN pertains to an NTN. Range bound Explanation maxnoofMDTPLMNs Maximum no. of PLMNs in the MDT PLMN list. Value is 16. [0089] The UE Context for a UE can be transferred from an old RAN node to a new RAN node, e.g., as in the Retrieve UE Context procedure defined in 3GPP TS 38.423 v18.0.0. Following the transfer of the UE Context, in one embodiment, the new RAN node obtains the indication of one or more PLMN allowed for MDT, wherein for a certain PLMN allowed for MDT, an attribute (e.g., a flag) is associated, indicating whether the PLMN pertains to (or is associated with) an NTN. [0090] In one embodiment, the first network node, e.g. a RAN node, (e.g., the first network node 600 or 700) receives from a second network node, e.g. a CN function or the OAM system, (e.g., the second network node 602 or 702) information revealing the NTN coverage areas where the UE (e.g., the UE 604 or 704) needs to be connected or camped on in order for MDT measurements to be collected. If the UE is connected or camped on any of such NTN coverage areas, the UE can collect MDT measurements within the area. [0091] The MDT measurements that should be collected by the UE in the NTN coverage areas may also be signaled to the first network node by the second network node. [0092] In one example of such embodiment, the first network node is a gNB, or a gNB-Central Unit (CU)-Control Plane (CP), and the second network node is the AMF. In this non limiting example, the first network node receives the information from the second network node via the NG interface. One instance of how such information can be signaled to the first network node is by means of modification of the existing MDT Configuration NR. Alternatively, the information can be included in any other suitable existing IE or in new IEs signaled over the interface connecting the first and second network node directly or indirectly. A possible implementation of how the information can be signaled to the first network node is provided below, using the example of enhancement to the MDT Configuration NR IE in 3GPP TS 38.413. 9.3.1.169MDT Configuration-NR This IE defines the MDT configuration parameters of NR. IE/Group Name Presence Range IE type and Semantics reference description MDT Activation M ENUMERATED (Immediate MDT only, Logged MDT only, Immediate MDT and Trace, …) CHOICE Area Scope of MDT M >Cell based >>Cell ID List for MDT 1..<maxnoofCe llIDforMDT> >>>NR CGI M 9.3.1.7 >TA based >>TA List for MDT 1..<maxnoofTA forMDT> >>>TAC M 9.3.3.10 The TAI is derived using the current serving PLMN. >PLMN wide NULL >TAI based >>TAI List for MDT 1..<maxnoofTA forMDT> >>>TAI M >NTN Based >>NTN Mapped Cell List 0..<maxnoofM for MDT appedCellsfor MDT> >>>Mapped Cell M [Here we should ??? provide the mapped cell identifier IE encoding] >>NTN Geographical 0..<maxnoofG Area List for MDT eographicAre aforMDT> >>>Geographic Area M [Here we should ??? provide a description of the Geographic Area identifier] CHOICE MDT Mode M >Immediate MDT >>Measurements to M BITSTRING Each position in Activate (SIZE(8)) the bitmap indicates a MDT measurement, as defined in TS 37.320 [41]. First Bit = M1, Second Bit= M2, Third Bit = M4, Fourth Bit = M5, Fifth Bit = M6, Sixth Bit = M7, Seventh Bit = logging of M1 from event triggered measurement reports according to existing RRM configuration, other bits reserved for future use. Value “1” indicates “activate” and value “0” indicates “do not activate”. >>M1 Configuration C-ifM1 9.3.1.171 >>M4 Configuration C-ifM4 9.3.1.172 >>M5 Configuration C-ifM5 9.3.1.173 >>M6 Configuration C-ifM6 9.3.1.174 >>M7 Configuration C-ifM7 9.3.1.175 >>Bluetooth Measurement O 9.3.1.177 Configuration >>WLAN Measurement O 9.3.1.178 Configuration >>MDT Location O 9.3.1.176 Information >>Sensor Measurement O 9.3.1.179 Configuration >Logged MDT >>Logging interval M ENUMERATED This IE is defined (320ms, 640ms, in TS 38.331 [18]. 1280ms, 2560ms, 5120ms, 10240ms, 20480ms, 30720ms, 40960ms, 61440ms, infinity, …) >>Logging duration M ENUMERATED This IE is defined (10, 20, 40, 60, in TS 38.331 [18]. 90,120, …) Unit: [minute]. >>CHOICE Report Type M >>>Periodical NULL >>>Event Triggered >>>>Event Trigger M 9.3.1.180 Logged MDT Configuration >>Bluetooth Measurement O 9.3.1.177 Configuration >>WLAN Measurement O 9.3.1.178 Configuration >>Sensor Measurement O 9.3.1.179 Configuration >>Area Scope of O 9.3.1.182 Neighbour Cells Signalling Based MDT PLMN O MDT PLMN List List 9.3.1.168 Range bound Explanation maxnoofCellIDforMDT Maximum no. of Cell ID subject for MDT scope. Value is 32. maxnoofTAforMDT Maximum no. of TA subject for MDT scope. Value is 8. maxnoofMappedCellsforMDT *Maximum no.of Mapped Cells for MDT scope. Value is 16. maxnoofGeographicAreaforMDT *Maximum no.of Geographic Areas for MDT scope. Value is 16. [0093] From the above, it can be seen that the first network node optionally receives from the AMF a list of Mapped Cells and/or a list of Geographic Areas. Similarly, the first network node may receive lists of identifiers defining other coverage areas pertaining to an NTN network such as cell identifiers, tracking area identifiers, PLMN identifiers and more. This information enables the first node to determine to which NTN coverage area the UE needs to be connected or camped on when MDT measurements shall be collected by the UE. [0094] In another embodiment, the first network node may also receive a list of NTN coverage area identifiers that is used to determine the area in which MDT measurements are collected from neighbor cells. In one example, such list of NTN coverage area identifiers may be used to determine the Area Scope of Neighbour Cells. The area Scope of neighbor cells identifies details of neighbor cells for which MDT measurements shall be collected. [0095] With the enhancements in this embodiment, the first network node would be informed about the NTN coverage area identifiers for the neighbor cells from which the UE shall collect MDT measurements. An example of how the Area Scope of Neighbour Cell may be enhanced is shown below, taking the IE definition in 3GPP TS 38.413 as a starting point: 9.3.1.182Area Scope of Neighbour Cells This IE defines the area scope of neighbour cells for logged MDT. IE/Group Name Presence Range IE type and Semantics description reference Area Scope of Neighbour M 1..<maxnoofFr Cells Item eqforMDT> >NR Frequency Info M 9.3.1.181 >PCI List for MDT 0.. <maxnoofNeig hPCIforMDT> >>NR PCI M INTEGER (0..1007, NR Physical Cell ID …) >NTN Mapped Cell List for 0..<maxnoofM MDT appedCellsfor MDT> >>Mapped Cell M [Here we should ??? provide the mapped cell identifier IE encoding] >NTN Geographical Area 0..<maxnoofG List for MDT eographicAre aforMDT> >>Geographic Area M [Here we should ??? provide a description of the Geographic Area identifier] Range bound Explanation maxnoofFreqforMDT Maximum no. of Frequency Information subject for MDT scope. Value is 8. maxnoofNeighPCIforMDT Maximum no. of Neighbour cells subject for MDT scope. Value is 32. maxnoofMappedCellsforMDT *Maximum no.of Mapped Cells for MDT scope. Value is 16. maxnoofGeographicAreaforMDT *Maximum no.of Geographic Areas for MDT scope. Value is 16. [0096] In the example above, it can be seen that the Area Scope of Neighbour Cells has been enhanced with a list of NTN mapped cells and/or a list of NTN geographical areas. The first network node therefore knows that the UE needs to be configured with this information so that the UE would measure MDT measurements from neighbour cells only if the listed NTN coverage area identifiers are signalled by a neighbour cell. [0097] In one embodiment, the above enhancements to the MDT Area Scope and/or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE performs mobility or tentatively when the UE is expected to move to another network node, for example as part of CHO configuration. [0098] In one embodiment, the above enhancements to the MDT Area Scope and/or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE is for example in dual-connected mode. [0099] As discussed above, the first network node may be required to configure the UE over RRC with the information received in the Area Scope of MDT and in the Area Scope of Neighbour Cells. [0100] Such configuration may occur by enhancing new IEs in the RRC protocol or by introducing new IEs to carry the information. [0101] An example of how the information may be signalled to the UE is provided below: AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-r1700 ::= SEQUENCE { areaConfig-r17 AreaConfig-r16 OPTIONAL, -- Need R interFreqTargetList-r17 SEQUENCE(SIZE (1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfiguration-v18xy ::= SEQUENCE { MappedCell-Area-r18 Define the encoding of mapped cell list OPTIONAL, -- Need R Geographic-Area-r18 Define the encoding of geographic area list OPTIONAL -- Need R } [0102] Below is a further example of how 3GPP TS 38.331 may be enhanced: 5a Logged Measurements 5.5a.1.3 Reception of the LoggedMeasurementConfiguration by the UE Upon receiving the LoggedMeasurementConfiguration message the UE shall: 1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2; 1> store the received loggingDuration, reportType and areaConfiguration, if included, in VarLogMeasConfig; 1> if the LoggedMeasurementConfiguration message includes plmn-IdentityList: 2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-IdentityList; 1> else: 2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN; 1> store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id in VarLogMeasReport; 1> store the received bt-NameList, if included, in VarLogMeasConfig; 1> store the received wlan-NameList, if included, in VarLogMeasConfig; 1> store the received sensor-NameList, if included, in VarLogMeasConfig; 1> start timer T330 with the timer value set to the loggingDuration; 1> store the received sigLoggedMeasType, if included, in VarLogMeasReport; 1> store the received earlyMeasIndication, if included, in VarLogMeasConfig; 1> store the received Mapped Cell-Area, if included, in VarLogMeasConfig; 1> store the received Geographic-Area, if included, in VarLogMeasConfig; 5.5a.3.2 Initiation While T330 is running and SDT procedure is not ongoing, the UE shall: 1> if measurement logging is suspended: 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging; 1> if not suspended, perform the logging in accordance with the following: 2> if the reportType is set to periodical in the VarLogMeasConfig: 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): 4> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport; 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 2> else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage: 3> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state; 3> upon transition from any cell selection state to camped normally state in NR: 4> if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig: 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging; > else if the reportType is set to eventTriggered and eventType is set to eventL1: 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport: 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met; > when performing the logging: 3> if InterFreqTargetInfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the last logging interval, or 3> if InterFreqTargetInfo is not configured and if the UE detected IDC problems during the last logging interval: 4> if measResultServingCell in the VarLogMeasReport is not empty: 5> include inDeviceCoexDetected; 5> suspend measurement logging from the next logging interval; 4> else: 5> suspend measurement logging; 3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received; 3> if location information became available during the last logging interval, set the content of the locationInfo as in 5.3.3.7: 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): 4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found; 4> if the reportType is set to eventTriggered in the VarLogMeasConfig; and 4> if the RPLMN at the time of entering the any cell selection state is included in plmn-IdentityList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last suitable cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on; 4> else if the reportType is set to periodical in the VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on; 3> else: 4> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on; 4> set the measResultServingCell to include the quantities of the cell the UE is camping on; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re- selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following: 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following: 5> if interFreqTargetInfo is included in VarLogMeasConfig: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and either in measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and SIB4; 5> else: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in SIB4; 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following: 5> if earlyMeasIndication is included in VarLogMeasConfig: 6> include measurement results for inter-RAT neighbouring frequencies that are included in either measIdleCarrierListEUTRA (within the VarMeasIdleConfig) or SIB5; 5> else: 6> include measurement results for inter-RAT frequencies that are included in SIB5; 4> for each neighbour cell included, include the optional fields that are available; NOTE 1: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC_IDLE or RRC_INACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. NOTE 2: For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. 2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. [0103] As explained above, once the UE is configured with the information concerning the NTN coverage area identifiers supported in an area where the UE is camped or served to enable the UE to collect MDT measurements in such area, the UE may check whether such NTN coverage area identifiers are supported or available in the area where the UE is camped or served. It should be pointed out that the examples above are non-limiting and that the NTN coverage areas could also consist of other coverage area identifiers such ad cell identities, tracking area identities, PLMN identities. [0104] Logging indication of NTN network in the MDT measurements when TN and NTN area configuration together is provided to the UE (such as, e.g., in the procedure of Figure 7). [0105] In another embodiment (see, e.g., Figure 7), the first network node, receives from a second node, the first piece of information concerning one or more list of identifiers comprising the areas of coverage of an NTN and TN networks (together), where such TN and NTN area identifiers are used to derive the coverage areas where MDT measurements shall be collected from TN and NTN networks. Additionally, to this information, the first network node may receive one or more configuration parameters/metrics concerning MDT measurements metrics that shall be collected by the UE within the area indicated in the first piece of information. Once collected, the UE reports the measurements to a network node (either first network node or a different network node). [0106] In this embodiment, when collecting the MDT measurements (e.g., radio measurements quantities such as RSRP or RSRQ of the serving cell and or neighboring cells in logged MDT measurements) the UE logs an indication based on the type of the network it is camping e.g., when camping in the NTN network includes an indication (e.g., a flag) in the measurements indicating the UE is camped in the NTN networks or when camping in the TN network includes an indication (e.g., a flag) in the measurements indicating the UE is camped in the TN networks. [0107] Such indication can be used by the network (e.g., OAM) for the post processing and building the coverage map of the NPN network and TN network separately. [0108] A non-limiting example implementation of the above method is highlighted in the following. UEInformationResponse-v1800-IEs ::= SEQUENCE { flightPathInfoReport-r18 FlightPathInfoReport-r18 OPTIONAL, successPSCell-Report-r18 SuccessPSCell-Report-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FlightPathInfoReport-r18 ::= SEQUENCE (SIZE (0..maxWayPoint-r18)) OF WayPoint-r18 WayPoint-r18 ::= SEQUENCE { wayPointLocation-r18 OCTET STRING, timeStamp-r18 AbsoluteTimeInfo-r16 OPTIONAL } LogMeasReport-r16 ::= SEQUENCE { absoluteTimeStamp-r16 AbsoluteTimeInfo-r16, traceReference-r16 TraceReference-r16, traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), tce-Id-r16 OCTET STRING (SIZE (1)), logMeasInfoList-r16 LogMeasInfoList-r16, logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, ... } LogMeasInfoList-r16 ::= SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 anyCellSelectionDetected-r16 ENUMERATED {true} OPTIONAL, ..., [[ inDeviceCoexDetected-r17 ENUMERATED {true} OPTIONAL ]], [[ campedInNTN-r17 ENUMERATED {true} OPTIONAL ]] } 5.5a.3.2 Initiation While T330 is running and SDT procedure is not ongoing, the UE shall: 1> if measurement logging is suspended: 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging; > if not suspended, perform the logging in accordance with the following: 2> if the reportType is set to periodical in the VarLogMeasConfig: 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): 4> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport; 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging at regular time intervals, as defined by the loggingInterval in the VarLogMeasConfig; 2> else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage: 3> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state; 3> upon transition from any cell selection state to camped normally state in NR: 4> if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig: 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging; 2> else if the reportType is set to eventTriggered and eventType is set to eventL1: 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn- IdentityList stored in VarLogMeasReport: 4> if areaConfiguration is not included in VarLogMeasConfig; or 4> if the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig; or 4> if one of the Geographic Area identities is included in Geographic-Area stored in VarLogMeasConfig; or 4> if one of the Mapped Cell identities is included in MappedCell-Area stored in VarLogMeasConfig; 5> perform the logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig only when the conditions indicated by the eventL1 are met; 2> when performing the logging: 3> if InterFreqTargetInfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetInfo or any inter-RAT frequency during the last logging interval, or 3> if InterFreqTargetInfo is not configured and if the UE detected IDC problems during the last logging interval: 4> if measResultServingCell in the VarLogMeasReport is not empty: 5> include inDeviceCoexDetected; 5> suspend measurement logging from the next logging interval; 4> else: 5> suspend measurement logging; 3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received; 3> if location information became available during the last logging interval, set the content of the locationInfo as in 5.3.3.7: 3> if the UE is in any cell selection state (as specified in TS 38.304 [20]): 4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found; 4> if the reportType is set to eventTriggered in the VarLogMeasConfig; and 4> if the RPLMN at the time of entering the any cell selection state is included in plmn-IdentityList stored in VarLogMeasReport; and 4> if areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaConfiguration in VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last suitable cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on; 4> else if the reportType is set to periodical in the VarLogMeasConfig: 5> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was camping on; 5> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on; 3> else: 4> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on; 4> set the campedInNTN to if the UE is camped in the NTN cell; 4> set the measResultServingCell to include the quantities of the cell the UE is camping on; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re- selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following: 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following: 5> if interFreqTargetInfo is included in VarLogMeasConfig: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and either in measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetInfo and SIB4; 5> else: 6> if earlyMeasIndication is included in VarLogMeasConfig; 7> include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4; 6> else: 7> include measurement results for NR neighbouring frequencies that are included in SIB4; 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following: 5> if earlyMeasIndication is included in VarLogMeasConfig: 6> include measurement results for inter-RAT neighbouring frequencies that are included in either measIdleCarrierListEUTRA (within the VarMeasIdleConfig) or SIB5; 5> else: 6> include measurement results for inter-RAT frequencies that are included in SIB5; 4> for each neighbour cell included, include the optional fields that are available; NOTE 1: The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRC_IDLE or RRC_INACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133 [14]. NOTE 2: For logging the measurements on frequencies (indicated in measIdleCarrierListNR/ measIdleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measIdleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation. 2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. [0109] There are various potential reasons for wanting UEs to perform and report the results of MDT measurements. A typical reason is to identify coverage holes in a terrestrial network. In an NTN, an additional reason, or use case, may be to check the performance of a certain satellite, e.g. if the operator suspects that there may be something wrong with the satellite’s transmission equipment, causing it to not fully cover its intended area. [0110] Various alternatives for area scope definitions for the use case where the performance of a certain satellite is monitored: - In a moving cells scenario, the area scope may be defined in terms of a geometrical area in relation to the satellite and let it move with the satellite. For instance, the parameters used for specification of a satellite’s spotbeam coverage in SIB32 in 3GPP TS 36.331 version 18.0.0 may be used for this purpose. To calculate how the area moves with the satellite, the UE uses the ephemeris data of the satellite, which is broadcasted in the system information or provided together with, or as a part of, the area scope definition in the MDT configuration (i.e., in the LoggedMeasurementConfiguration RRC message). - The area scope is defined as a satellite ID (or list of satellite IDs), e.g. a satellite ID as defined in 3GPP TS 36.331 version 18.0.0 (i.e. the SatelliteId IE). - The OAM provides the area scope (directly to the RAN or via the CN) in terms of a list of geographical areas or mapped cell areas/IDs (which could be seen as “subareas), each with a time schedule, e.g. a validity period, which makes the area scope follow the quasi-Earth- fixed cells served by the same satellite (i.e. as the satellite moves its beam to a new cell area, the area scope’s schedule makes the area scope’s current coverage move along with it). With this concept, only one of the area scope’s “subareas” would be valid at a time. [0111] Various alternatives for area scope definitions for other use cases: - The area scope may be defined as either side of a line, e.g. a chain of interconnected points forming a straight or non-straight line. This may be done using a polygon with the chain of points creating a line through the UE’s cell area and then closing the polygon around the cell, with margin outside the cell area. The chain of points (forming a straight or non- straight line) can be continued through multiple cells (e.g. through multiple geographically contiguous cell areas) by using overlapping point(s), i.e. one or more point(s) is/are used in the polygon of adjacent cells. One side of the line (chain of points) is indicated by indicating “inside the polygon) and the other side of the line (chain of points) is indicated by indicating “outside the polygon”. - The OAM provides the area scope (directly to the RAN or via the CN) in terms of a mapped cell area or a list of mapped cell areas, i.e. mapped cell ID(s). The RAN translates this into an area scope definition (which is sent to the UE in a LoggedMeasurementConfiguration RRC message) consisting of a geometrical area or a broadcasted CGI or list of broadcasted CGIs. - The OAM provides the area scope (directly to the RAN or via the CN) in terms of a geographical area and the RAN translates this into an area scope definition (which is sent to the UE in a LoggedMeasurementConfiguration RRC message) consisting of a broadcasted CGI and/or TAI or TAC, or a list of broadcasted CGI(s) and/or TAI(s) or TAC(s). - A list of cells (e.g., broadcasted CGI(s)) with a time schedule for each cell, defining during which time period the cell is part of the area scope to be applied. - A list of tracking areas (e.g. in the form of a list of TAI(s) or a list of TAC(s)) with a time schedule for each tracking area in the list, defining during which time period the tracking area is part of the area scope to be applied. - A set of geographical/geometrical areas, which may be partially overlapping, in which case the union of the areas is what defines the area scope. [0112] For any of the above area scope definition alternatives comprising geometrical shapes/areas or geographical areas, as one option, geographical area definitions specified in 3GPP TS 23.032 version 18.1.0 may be reused. [0113] Figure 8 shows an example of a communication system 800 in which embodiments of the present disclosure may be implemented. In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a Radio Access Network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810A and 810B (one or more of which may be generally referred to as network nodes 810), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Note that, in some embodiments, at least one of the network nodes 810 is a NTN network node, which includes, for example, a satellite and a gateway (e.g., as illustrated in the example NTN of Figure 4 or in Figure 5). [0114] Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and/or core network nodes 808. [0115] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 810 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections. [0116] 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 800 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 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0117] The UEs 812 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 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 812 and/or with other network nodes or equipment in the telecommunication network 802 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 802. [0118] In the depicted example, the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 806 includes one more core network nodes (e.g., core network node 808) 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 808. 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-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). [0119] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and/or the telecommunication network 802, and may be operated by the service provider or on behalf of the service provider. The host 816 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. [0120] As a whole, the communication system 800 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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. [0121] In some examples, the telecommunication network 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunication network 802 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 Internet of Things (IoT) services to yet further UEs. [0122] In some examples, the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC). [0123] In the example, a hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and/or 812D) and network nodes (e.g., network node 810B). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 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 810, or by executable code, script, process, or other instructions in the hub 814. As another example, the hub 814 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 814 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy IoT devices. [0124] The hub 814 may have a constant/persistent or intermittent connection to the network node 810B. The hub 814 may also allow for a different communication scheme and/or schedule between the hub 814 and UEs (e.g., UE 812C and/or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and/or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 804 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 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 810B. In other embodiments, the hub 814 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 810B, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0125] Figure 9 shows a UE 900 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0126] 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-Infrastructure (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). [0127] The UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, memory 910, a communication interface 912, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 9. 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. [0128] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple Central Processing Units (CPUs). [0129] In the example, the input/output interface 906 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 900. 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. [0130] In some embodiments, the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and/or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied. [0131] The memory 910 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems. [0132] The memory 910 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (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 a ‘SIM card.’ The memory 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium. [0133] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 918 and/or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., the antenna 922) and may share circuit components, software, or firmware, or alternatively be implemented separately. [0134] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth. [0135] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, 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). [0136] 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. [0137] A UE, when in the form of an IoT 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 IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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/window sensor, a flood/moisture sensor, an electrical 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 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 900 shown in Figure 9. [0138] As yet another specific example, in an IoT 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 one particular 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, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. [0139] 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. [0140] Figure 10 shows a network node 1000 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). [0141] 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, distributed units (e.g., in an O-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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). [0142] 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 BS 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). [0143] The network node 1000 includes processing circuitry 1002, memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 1000 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 1000 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 1000. [0144] The processing circuitry 1002 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1000 components, such as the memory 1004, to provide network node 1000 functionality. [0145] In some embodiments, the processing circuitry 1002 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of Radio Frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units. [0146] The memory 1004 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, RAM, 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 memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and/or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and the memory 1004 are integrated. [0147] The communication interface 1006 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 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. The radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to the antenna 1010 and the processing circuitry 1002. The radio front-end circuitry 1018 may be configured to condition signals communicated between the antenna 1010 and the processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1020 and/or the amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface 1006 may comprise different components and/or different combinations of components. [0148] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018; instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes the one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012 as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown). [0149] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port. [0150] The antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and/or the processing circuitry 1002 may be configured to perform any transmitting operations described herein as being performed by the network node 1000. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment. [0151] The power source 1008 provides power to the various components of the network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 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. [0152] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000. [0153] Figure 11 is a block diagram of a host 1100, which may be an embodiment of the host 816 of Figure 8, in accordance with various aspects described herein. As used herein, the host 1100 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1100 may provide one or more services to one or more UEs. [0154] The host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a network interface 1108, a power source 1110, and memory 1112. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of the host 1100. [0155] The memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g. data generated by a UE for the host 1100 or data generated by the host 1100 for a UE. Embodiments of the host 1100 may utilize only a subset or all of the components shown. The host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 1114 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1100 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 1114 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc. [0156] Figure 12 is a block diagram illustrating a virtualization environment 1200 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 1200 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1200 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. [0157] Applications 1202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1200 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0158] Hardware 1204 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1206 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1208A and 1208B (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein. The virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208. [0159] The VMs 1208 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1206. Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of the VMs 1208, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment. [0160] In the context of NFV, a VM 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1208, and that part of the hardware 1204 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1208, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1208 on top of the hardware 1204 and corresponds to the application 1202. [0161] The hardware 1204 may be implemented in a standalone network node with generic or specific components. The hardware 1204 may implement some functions via virtualization. Alternatively, the hardware 1204 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1210, which, among others, oversees lifecycle management of the applications 1202. In some embodiments, the hardware 1204 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 1212 which may alternatively be used for communication between hardware nodes and radio units. [0162] 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 obtained information 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. [0163] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired 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. [0164] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. A method performed by a User Equipment, UE, (604), the method comprising: receiving, (610) from a first network node (600), information that configures the UE (604) to perform Minimization of Drive Testing, MDT, measurements in one or more coverage areas of a Non-Terrestrial Network, NTN; performing (612) the MDT measurements; and reporting (612) the MDT measurements to the first network node (600) or another network node. 2. The method of claim 1, wherein the information that configures the UE (604) to perform MDT measurements in the one or more coverage areas of the NTN comprises one or more list of identities that identify the one or more coverage areas of the NTN. 3. The method of claim 1, wherein the information that configures the UE (604) to perform MDT measurements in the one or more coverage areas of the NTN comprises information that indicates one or more geographical areas that correspond to the one or more coverage areas of the NTN. 4. The method of any one of claims 1 to 3, wherein the information that configures the UE (604) to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking areas, a list of registration areas, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state. 5. The method of any one of claims 1 to 3, wherein the information that configures the UE (604) to perform the MDT measurements comprises information that configures the UE to perform the MDT measurements when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. 6. The method of any one of claims 1 to 5, wherein the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises one or more elements related to the NTN. 7. The method of any one of claims 1 to 5, wherein the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific. 8. The method of any one of claims 1 to 5, wherein the information that configures the UE (604) to perform the MDT measurements comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN. 9. The method of claim 8, wherein the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. 10. A method performed by a User Equipment, UE, (704), the method comprising: receiving, (710) from a first network node (700), information that configures the UE (604) to perform Minimization of Drive Testing, MDT, measurements in one or more coverage areas for a Non-Terrestrial Network, NTN, and a Terrestrial Network, TN; performing (712) the MDT measurements in accordance with the received information; and reporting (712) the MDT measurements to the first network node (700) or another network node together with an indication(s) that indicates whether the MDT measurements are for the NTN or the TN. 11. The method of claim 10, wherein the indication(s) comprise a separate indication for each MDT measurement. 12. A method performed by a first network node (600), the method comprising: receiving (606), from a second network node (602), first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a Non-Terrestrial Network, NTN; configuring (610) a User Equipment, UE, (604) to perform one or more Minimization of Drive Testing, MDT, measurements in at least one of the one or more coverage areas of the NTN. 13. The method of claim 12, further comprising receiving (608) second information comprising information about the MDT measurements. 14. The method of claim 13, wherein the second information comprises an MDT measurements configuration. 15. The method of claim 14, wherein the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements. 16. The method of any one of claims 12 to 15, wherein the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN. 17. The method of any one of claims 12 to 16, wherein configuring (610) the UE (604) to perform the one or more MDT measurements comprises configuring (610) the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in a connected state. 18. The method of any one of claims 12 to 16, wherein configuring (610) the UE (604) to perform the one or more MDT measurements comprises configuring (610) the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. 19. The method of any one of claims 12 to 18, wherein the second information comprises an MDT configuration that comprises one or more elements related to the NTN.
20. The method of any one of claims 12 to 18, wherein the second information comprises an MDT configuration that comprises information that indicates an area scope of MDT, where the information that indicates the area scope of MDT comprises one or more parameters that are NTN specific. 21. The method of any one of claims 12 to 18, wherein the second information comprises an MDT configuration that is enabled to discriminate whether a certain PLMN allowed for MDT is associated with an NTN or a TN. 22. The method of claim 21, wherein the MDT configuration comprises an MDT PLMN list information element that comprises an indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. 23. The method of any one of claims 12 to 18, wherein the second information is comprised in a UE context modification related message, and the second information relates to a modification to a management based MDT configuration. 24. The method of claim 23, wherein the management based MDT configuration comprises a list of PLMNs allowed for MDT and an associated indicator that indicates whether a PLMN allowed for MDT is associated with an NTN or a TN. 25. The method of any one of claims 12 to 18, wherein the first information comprises an NTN geographical area list for MDT comprised in an MDT configuration. 26. The method of any one of claims 12 to 18, wherein the first information comprises information that indicates a geographic area for a list of NTN geographical areas for MDT indicated for an area scope of neighbor cells from which the UE is to collect the MDT measurements. 27. A method performed by a first network node (700), the method comprising: receiving (706), from a second network node (702), first information that indicates one or more coverage areas (e.g., one or more cells, one or more tracking areas, one or more registration areas, one or more PLMNs, one or more mapped cells, or one or more geographical areas) of a Non-Terrestrial Network, NTN, and a Terrestrial Network, TN; configuring (710) a User Equipment, UE, (704) to perform one or more Minimization of Drive Testing, MDT, measurements in at least one of the one or more coverage areas of the NTN and TN. 28. The method of claim 27, further comprising receiving (708) second information comprising information about the MDT measurements. 29. The method of claim 28, wherein the second information comprises an MDT measurements configuration. 30. The method of claim 29, wherein the MDT measurements configuration comprises information that indicates one or more parameters and/or metrics related to the MDT measurements. 31. The method of any one of claims 27 to 30, wherein the first information comprises one or more lists of identifiers that identify the one or more coverage areas of the NTN and TN. 32. The method of any one of claims 27 to 31, wherein configuring (710) the UE (704) to perform the one or more MDT measurements comprises configuring (710) the UE to perform at least one MDT measurement when served by an area (e.g., a cell, a tracking area, a registration area, a PLMN, a mapped cell, or a geographical area, a list of cells, a list of tracking area, a list of registration area, a list of PLMNs, a list of mapped cells, or a list of geographical areas) comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in a connected state. 33. The method of any one of claims 27 to 31, wherein configuring (710) the UE (704) to perform the one or more MDT measurements comprises configuring (710) the UE to log at least one MDT measurement when camped in an area comprised in or corresponding to one (e.g., any one) of the one or more coverage areas of the NTN and TN while in an RRC idle or RRC inactive state and to report the logged MDT measurement(s) upon transitioning to a connected state. 34. The method of any one of claims 27 to 33, wherein MDT measurements reported by the UE (704) in response to the configuring (710) comprise or are otherwise associated to an indicator that indicates whether the MDT measurements are for the NTN or the TN. 35. A user equipment comprising: processing circuitry configured to perform any of the steps of any of claims 1 to Erreur ! Source du renvoi introuvable.; and power supply circuitry configured to supply power to the processing circuitry. 36. A network node comprising: processing circuitry configured to perform any of the steps of any of claims 12 to Erreur ! Source du renvoi introuvable.; and power supply circuitry configured to supply power to the processing circuitry.
PCT/IB2025/000163 2024-04-19 2025-04-18 Mdt areas scopes for ntn Pending WO2025219761A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IBPCT/IB2024/000258 2024-04-19
IB2024000258 2024-04-19

Publications (1)

Publication Number Publication Date
WO2025219761A1 true WO2025219761A1 (en) 2025-10-23

Family

ID=95743607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/000163 Pending WO2025219761A1 (en) 2024-04-19 2025-04-18 Mdt areas scopes for ntn

Country Status (1)

Country Link
WO (1) WO2025219761A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020222689A1 (en) * 2019-04-30 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Methods relating to mdt configurations and related devices
WO2023034289A1 (en) * 2021-09-02 2023-03-09 Qualcomm Incorporated Data collection reporting for non-terrestrial network cells
WO2023059260A1 (en) * 2021-10-08 2023-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Minimization of drive testing configuration
WO2023059242A1 (en) * 2021-10-07 2023-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Minimization of drive tests measurement

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020222689A1 (en) * 2019-04-30 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Methods relating to mdt configurations and related devices
WO2023034289A1 (en) * 2021-09-02 2023-03-09 Qualcomm Incorporated Data collection reporting for non-terrestrial network cells
WO2023059242A1 (en) * 2021-10-07 2023-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Minimization of drive tests measurement
WO2023059260A1 (en) * 2021-10-08 2023-04-13 Telefonaktiebolaget Lm Ericsson (Publ) Minimization of drive testing configuration

Similar Documents

Publication Publication Date Title
US20250097811A1 (en) Systems and methods for reducing system information acquisition during cell reselection in a non-terrestrial network
US20250142505A1 (en) Method and Apparatus for SSB Measurement Time Configuration in Communication Network
US20250113277A1 (en) Systems and methods for time-based handover in non-terrestrial networks
US20250184854A1 (en) Systems and methods for time-based triggered handover in non-terrestrial networks
CN118525575A (en) Location information provided
US20250227521A1 (en) Minimization of Drive Testing Configuration
WO2023059259A1 (en) Minimization of drive testing for non-terrestrial networks
WO2023213984A1 (en) Configuration of ue for time-based handover in wireless network such as a non-terrestrial network
US11792693B2 (en) Methods and apparatuses for redirecting users of multimedia priority services
WO2024079717A1 (en) Reporting of qoe reports to the sn
WO2025219761A1 (en) Mdt areas scopes for ntn
WO2025210593A1 (en) Indication of store and forward for ntn
WO2025104275A1 (en) Ssb measurement time configuration for cell switching terminal device provided by a movable base station/relay
WO2025169120A1 (en) Handling of xn connectivity for radio access network nodes with wireless backhaul
WO2025172889A1 (en) Mobility for wireless access and backhaul
WO2025153889A1 (en) Ntn hand-over using beam-hopping patterns
WO2024079721A1 (en) Non-public network (npn) id check to delete the son reports at the user equipment
WO2025202961A1 (en) Time advance configuration in batch for regenerative non-terrestrial network system
EP4635230A1 (en) Systems and methods by a management network node for reducing the likelihood of conflicting use of resources by user equipments
WO2024033272A1 (en) Cag extension for mobile iab-node
WO2025174317A1 (en) User equipment, radio network node, and methods for performing a cell search
WO2025216684A1 (en) Wireless device, first network node, and methods performed thereby for handling a failure
WO2024069494A1 (en) Mobility support for quality of experience reporting
WO2024035311A1 (en) Minimization of drive tests configuration scope for different network types
EP4566354A1 (en) Group signaling for network energy savings

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25725555

Country of ref document: EP

Kind code of ref document: A1