Logging of minimization of drive test (MDT) measurements

Abstract

Methods and apparatuses for logging and reporting measurements in a wireless network. An example method, in a wireless device, comprises receiving 210), from a wireless network, a configuration for logging minimization of drive test, MDT, measurements. The method further comprises determining (220) that the received configuration does not identify one or more stand-alone non-public networks, SNPNs, in an area scope for the configuration, and, responsive to said determining, storing (230) a currently SNPN identifier in a variable associated with logged MDT measurements.

Description

[0001] LOGGING OF MINIMIZATION OF DRIVE TEST (MDT) MEASUREMENTS

[0002] TECHNICAL FIELD

[0003] The present disclosure is generally related to wireless networks and is more particularly related to the logging of minimization of drive test (MDT) measurements while operating in such wireless networks.

[0004] BACKGROUND

[0005] NPN

[0006] NPN, which stands for Non-Public Networks, is a feature that allows for a network to be deployed and / or managed by an entity other than a normal operator. A "normal operator" here is assumed to be an operator of one or more PLMNs, i.e., Public Land Mobile Networks. It should be noted that a PLMN also has an identify which is called the PLMN ID, or sometimes just referred to as the "PLMN".

[0007] There are two types of NPN networks, namely SNPNs and PNI-NPNs.

[0008] A first network or network identifier, e.g., a PLMN, can be configured as equivalent to another network or network identifier. For example, the operator of one network may have an agreement with another operator such that the users of these networks can consider the network equivalent - the PLMNs for these networks may be configured to be equivalent to one another in such a case. The current 3rd-Generation Partnership Project (3GPP) specifications do not provide for equivalent SNPN networks, but it would be possible to introduce the concept of equivalent SNPNs in the future. (In the case of PNI-NPNs, the concept of Equivalent PLMN (EPLMN) is implicitly applied.)

[0009] NPN is only specified for NR access.

[0010] SNPN

[0011] SNPN, which stands for Stand-alone NPN, is a type of NPN that does not rely on network functions provided by a PLMN. For example, it may be a private company who deploys a network, but that company does not own a PLMN. It could be, for example, a company who owns factories and deploys networks in and around the factories for the sake of providing service to its employees and machines, etc.

[0012] An SNPN network has an identifier that comprises of a PLMN-identity and a NID (Network Identity). One way for the SNPN network owner to acquire an SNPN identifier is to make an agreement with a PLMN operator so that such SNPNs identity comprises that operator's PLMN ID. Another approach is that a "dummy" (i.e., "special" or "not normally used" or "invalid" or similar) PLMN ID is used as part of the identity of the SNPN.

[0013] Network selection in SNPN access mode

[0014] An SNPN-enabled UE supports an SNPN access mode. When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs, over the Uu interface.

[0015] Emergency services are supported in SNPN access mode.

[0016] If a UE is not set to operate in SNPN access mode, even if it is SNPN-enabled, the UE does not select and register with SNPNs. A UE not set to operate in SNPN access mode performs PLMN selection procedures. For a UE capable of simultaneously connecting to an SNPN and a PLMN, the setting for operation in SNPN access mode is applied only to the Uu interface for connection to the SNPN.

[0017] An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription needs to first enter SNPN access mode to be able to select SNPNs. Once the UE has entered SNPN access mode, SNPN selection is performed. Once an SNPN has been selected the UE attempts registration in the SNPN using the PLMN credentials.

[0018] Note that details of activation and deactivation of SNPN access mode are up to UE implementation.

[0019] When a UE is set to operate in SNPN access mode the UE does not perform normal PLMN selection procedures.

[0020] UEs operating in SNPN access mode read the information from the broadcast system information and takes it into account during network selection.

[0021] Note that if the UE has multiple SNPN subscriptions it is assumed that the subscription to use for automatic selection is determined by implementation-specific means prior to network selection.

[0022] For automatic network selection the UE selects and attempts registration on available and allowable SNPNs in the following order:

[0023] - the SNPN the UE was last registered with (if available);

[0024] - the subscribed SNPN, which is identified by the PLMN ID and NID for which the UE has SUPI and credentials.; - If the UEs supports access to an SNPN using credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order:

[0025] - SNPNs in the user-controlled prioritized list of preferred SNPNs (in priority order);

[0026] - SNPNs in the Credentials Holder-controlled prioritized list of preferred SNPNs (in priority order);

[0027] - SNPNs that additionally broadcast a Group ID for Network Selection (GIN) contained in the Credentials Holder-controlled prioritized list of preferred GINs (in priority order) (Note that if multiple SNPNs are available that broadcast the same GIN, the order in which the UE selects and attempts a registration with those SNPNs is implementation-specific);

[0028] - SNPNs that additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e., the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs / GINs in the UE. (Note that if multiple SNPNs are available that broadcast the indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific.)

[0029] When a UE performs Initial Registration to an SNPN, the UE shall indicate the PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID.

[0030] Further details can be found in the 3GPP standards document 3GPP TS 23.501, System architecture for the 5G System (5GS), V18.3.0.

[0031] Minimization of Drive Tests (MDT)

[0032] MDT was standardized for NR in Rel-16 to reduce the amount of drive tests performed manually. It is a UE-assisted framework where network measurements are collected by both Radio Resource Control (RRC) IDLE / INACTIVE and RRC Connected UE(s), to aid the network in gathering valuable information. It has been specified for both LTE and NR in 3GPP TS 37.320, Radio measurement collection for Minimization of Drive Tests (MDT), V17.5.0.

[0033] In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT. Logged MDT

[0034] A UE in RRC_IDLE / RRC_INACTIVE state is configured to perform periodical and event-triggered M DT logging after receiving the MDT configurations from the network. The UE shall report the downlink (DL) pilot strength measurements (RSRP / RSRQ) together with time information, detailed location information if available, and WLAN, Bluetooth to the network via using the UE information framework when it moves to RRC_CONNECTED state. The DL pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purpose, without imposing UE to perform additional measurements.

[0035] Table 1 - Measurement logging for Logged MDT

[0036] For Periodical Logged MDT, the UE receives the MDT configuration, including the information elements (lEs) logginginterval and loggingduration, in an RRC message, i.e., LoggedMeasurementConfiguration, from the network. A timer (T330) is started at the UE upon receiving the configurations and set to loggingduration (10 min - 120 min). The UE shall perform periodical MDT logging with the interval set to logginginterval (1.28 s - 61.44 s) when the UE is in RRCJDLE. An example of the MDT logging is shown Figure 1.

[0037] For event-triggered Logged MDT, the UE receives eventType and logginginterval l Es from the network. The UE logs the measurement reports at every logginginterval if the event configured in eventType is satisfied.

[0038] SUM MARY

[0039] According to the 3GPP standard 3GPPTS 38.331, NR; Radio Resource Control (RRC); Protocol specification, V17.6.0, 3GPP A UE registered in a SNPN can be configured with a LoggedMeasurementConfiguration to perform logged M DT measurement while in RRCJDLE state in the SNPN. The network can configure the UE with snpn-ldentityList to indicate a list of equivalent SNPNs from which the UE can collect measurement reports. However, if the network does not provide the UE with the snpn-ldentityList information element (IE), it remains unclear in which SNPNs UE is allowed to collect logged measurement results. Furthermore, upon returning to RRC_Connected state, if the UE has some logged measurement results, it remains unclear whether the UE should transmit the logged MDT availability indication and, later, the logged MDT report, to the network.

[0040] In short, if the UE is not provided a with a list of SNPNs in the logged measurement configuration, according to current procedures it will not store any SNPN identity (not even the registered SNPN identity). Hence during collection of the logged measurement results, UE will not have the SNPN ID to compare and would not be able to collect measurement results.

[0041] The techniques, apparatuses and systems described herein address these problems. According to at least some of these techniques and apparatuses, a UE registered in a SNPN network stores the current registered SNPN ID if snpn-ldentityList is not configured in a received Logged MDT configuration. The UE, furthermore, uses this stored SNPN ID information to determine whether it is allowed to log the measurements in a cell while being in I dle / lnactive state and also to determine to which cells can the UE report the (availability of) stored measurement.

[0042] Thus, an example method, according to some embodiments, is performed by a wireless device, and is for logging and reporting measurements, and comprises the steps of receiving, from a wireless network, a configuration for logging MDT measurements, and determining that the received configuration does not identify one or more SNPNs in an area scope for the configuration. The method further comprises, responsive to this determining, storing a currently SNPN identifier in a variable associated with logged MDT measurements. The stored SNPN identifier may be subsequently used during idle / inactive mode to determine the logging of MDT measurements, and in connected mode to determine whether to transmit an indication that logged MDT measurements are available.

[0043] An example wireless device, or UE, corresponding to the above-summarized method comprises radio circuitry configured to communicate with one or more wireless networks and processing circuitry operatively coupled to the radio circuitry. The processing circuitry is configured to control the wireless device to receive, from a wireless network, a configuration for logging MDT measurements and determine that the received configuration does not identify one or more SNPNs in an area scope for the configuration. The processing circuitry is further configured to control the wireless device to, responsive to this determining, store a currently SNPN identifier in a variable associated with logged MDT measurements. Again, the stored SNPN identifier may be subsequently used during idle / inactive mode to determine the logging of MDT measurements, and in connected mode to determine whether to transmit an indication that logged MDT measurements are available.

[0044] An advantage of the solutions described herein is to enable the UE to collect logged MDT results while registered to a SNPN.

[0045] Variants of these methods and apparatuses are described in detail below.

[0046] BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 illustrates an example of a logged MDT procedure.

[0048] Figure 2 is a process flow diagram illustrating an example method according to some embodiments.

[0049] Figure 3 is a block diagram of an example network, according to some embodiments.

[0050] Figure 4 is a block diagram of an example UE, or wireless device, according to some embodiments.

[0051] Figure 5 is a block diagram of an example network node, according to some embodiments.

[0052] DETAILED DESCRIPTION

[0053] 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.

[0054] This document describes techniques to be performed by a User Equipment (UE) registered in a SNPN and configured with a logged MDT configuration. The disclosed techniques enable a UE, which may be referred to more broadly as a wireless device, to store information about the current registered SNPN to be enabled to collect logged MDT results.

[0055] An example method according to these techniques is performed by a UE registered in a SNPN and comprises the following steps:

[0056] 1) Receiving a logged MDT configuration from the network and determining the absence of a list of non-public network identities in the area scope, such as a. Absence of the list of SNPNs (i.e., snpn-ldentityList) for which it is required to collect

[0057] MDT reports. b. Absence of the list of PLMNs c. Absence of the list of PNI NPN network identities d. Absence of any combination of the above network identities 2) Storing the current registered SNPN ID (e.g., PLMN and the NID as in NPN-identityList) in a variable associated with the logged MDT report (i.e., VarLogMeasReport). a. In a separate embodiment, along with the current registered SNPN ID, the UE also stored the list of equivalent SNPN IDs.

[0058] 3) Changing state to RRC_IDLE and using the stored SNPN ID to determine collection of logged measurement report.

[0059] 4) Returning to RRC_Connected state and using the stored SNPN ID (and if stored, the list of equivalent SNPN IDs) to determine transmission of logged measurement report availability indicator to the network.

[0060] 5) Upon receiving request from the network, using the stored SNPN ID (and if stored, the list of equivalent SNPN IDs) to determine transmission of logged measurement report to the network.

[0061] In the following, the different steps of the method summarized above are described in detail.

[0062] UE receives a LoggedMeasurementConfiguration from the network and determines the absence of NPN network identity e.g., snpn-ldentityList.

[0063] The UE receives a logged MDT configuration and determines there is no list of SNPNs included in the configuration. UE receives the configuration through LoggedMeasurementConfiguration message and determines the presence of snpn-identityList in the configuration.

[0064] UE stores the current registered SNPN ID in variable associated with the logged MDT report.

[0065] If the UE determines the absence of snpn-ldentityList in the received logged MDT configuration, it stores the current registered SNPN information in the snpn-ldentityList in the VarLogMeasReport variable. In another embodiment, the UE may also store in the snpn-ldentityList in the VarLogMeasReport variable the list of equivalent SNPNs (if known by the UE, e.g., via previous NAS signalling configuration)

[0066] UE changes state to RRCJDLE and uses the stored SNPN ID to determine storing of logged measurement report.

[0067] UE moves to RRC IDLE or RRC Inactive state and determines whether it should store logged MDT measurements as configured in the LoggedMeasurementConfiguration based on the registered SNPN ID stored in the MDT report variable. UE returns to RRC_Connected state and uses the stored SNPN ID to determine transmission of logged measurement report availability indicator to the network.

[0068] Upon returning to RRC_Connected state, UE uses the snpn-ldentityList stored in the VarLogMeasReport to determine whether it should indicate the logged MDT report availability to the network. For example, if the UE is connected to the same SNPN to which it was registered when it received the logged MDT configuration or to an equivalent SNPN, the UE informs this to the network using logMeasAvailable IE.

[0069] UE receives request from the network and uses the stored SNPN ID to determine transmission of logged measurement report to the network.

[0070] An example implementation of the invention for TS 38.331 is provided below where the UE is registered in a SNPN and stores registered SNPN ID in the snpn-ldentityList in the VarLogMeasResults.

[0071] - begin proposed specification excerpt -

[0072] 5.5a.1.3 Reception of the LoggedMeasurementConfiguration by the UE

[0073] Upon receiving the LoggedMeasurementConfiguration message the UE shall:

[0074] 1> discard the logged measurement configuration as well as the logged measurement information as specified in 5.5a.2;

[0075] 1> store the received loggingDuration, reportType and areaconfiguration, if included, in VarLogMeasConfig;

[0076] 1> if the LoggedMeasurementConfiguration message includes plmn-ldentityList or cagConfigList

[0077] 2> set plmn-ldentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-ldentityList and PLMNs included in cagConfigList;

[0078] 1> else if the UE is registered in a PLMN:

[0079] 2> set plmn-ldentityList in VarLogMeasReport to include the RPLMN;

[0080] 1> if the LoggedMeasurementConfiguration message includes snpnCon fig List:

[0081] 2> set the snpn-ldentityList in VarLogMeasReport to include the current registered SNPN ID as well as SNPN IDs in snpnConfigList;

[0082] 1> else if the UE is registered in an SNPN:

[0083] 2> set the snpn-ldentityList in VarLogMeasReport to include the current registered SNPN;

[0084] - end proposed specification excerpt - In view of the detailed examples and variants described above, it will be appreciated that Figure 2 is a process flow illustrating an example method, in a wireless device, for logging and reporting measurements. It should be understood that this method is intended to be a generalization of many, if not all, of the techniques described above, and thus where there are minor differences between the terminology used below and that used above, the terms used below should be understood as at least encompassing the similar or clearly related terms used above, unless the context clearly indicates otherwise. Note also that the term "wireless device," as used herein, is a generalization of the 3GPP term of art, "UE," and refers to an access terminal or end user device configured to operate in a wireless network, such as the wireless networks standardized by 3GPP.

[0085] As shown at block 210, the example method illustrated in Figure 2 includes the step of receiving, from a wireless network, a configuration for logging MDT measurements. This configuration may include, for example, the contents of the LoggedMeasurementConfiguration RRC message as specified, with appropriate modifications as needed accommodate the techniques described herein, by 3GPP.

[0086] The method shown in Figure 2 further includes the step of determining that the received configuration does not identify one or more SNPNs in an area scope for the configuration. This is shown at block 220. As discussed above, this may comprise determining that the received configuration does not include any one or of the following: a list of SNPNs; a list of PLMNs; and a list of PNI NPN identities.

[0087] As shown at block 230, the method further comprises storing an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements, responsive to the determining. Thus, a wireless device registered with an SNPN that receives an MDT measurement configuration that omits any SNPN identifier in its area scope stores the identifier for the currently registered SNPN. As seen below, that allows this SNPN identifier to be associated with subsequent MDT measurements / reports. In some embodiments, the wireless device may also, responsive to the determining shown at block 220, store one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

[0088] As shown at block 240, the method may further comprise, subsequently to the storing shown at bock 230, using the stored SNPN identifier and the configuration for determining collection of logged measurements, while in an RRC idle state or RRC inactive state. In some embodiments, this may comprise using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, for determining collection of logged measurements. As shown at block 250, the method may still further comprise, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, entering an RRC connected state and using the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements. Again, this may comprise using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

[0089] Thus, in some instances, the method may comprise determining, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmitting the indication of available logged MDT measurements. In such instances, the method may further comprise receiving, from the wireless network, a request for logged MDT measurements, and transmitting, to the wireless network, logged measurements associated with the stored SNPN identifier. These steps are shown at blocks 260 and 270. Note that the "SNPN corresponding to the stored SNPN" may be an equivalent SNPN to the SNPN having the stored SNPN identifier, in some instances and / or embodiments.

[0090] Figure 3 shows an example of a communication system 300, in accordance with some embodiments, in which the techniques described above may be implemented.

[0091] In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. 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 302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 302 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 302, including one or more network nodes 310 and / or core network nodes 308.

[0092] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (0- 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 Al, Fl, Wl, El, 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 0- 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 310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

[0093] 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 300 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 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0094] The UEs 312 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 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 312 and / or with other network nodes or equipment in the telecommunication network 302 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 302.

[0095] In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. 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 306 includes one more core network nodes (e.g., core network node 308) 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 308. 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).

[0096] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunication network 302, and may be operated by the service provider or on behalf of the service provider. The host 316 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded 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.

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

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

[0099] In some examples, the UEs 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0100] In the example, the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and / or 312d) and network nodes (e.g., network node 310b). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 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 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 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 314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0101] The hub 314 may have a constant / persistent or intermittent connection to the network node 310b. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312c and / or 312d), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to an M2M service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310b. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

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

[0103] 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).

[0104] The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 4. 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.

[0105] The processing circuitry 402 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 410. The processing circuitry 402 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 402 may include multiple central processing units (CPUs).

[0106] In the example, the input / output interface 406 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 400. 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.

[0107] In some embodiments, the power source 408 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 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

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

[0109] The memory 410 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 random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as 'SIM card.' The memory 410 may allow the UE 400 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 410, which may be or comprise a device-readable storage medium.

[0110] The processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 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 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

[0112] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 412, 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).

[0113] 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.

[0114] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / 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 Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 400 shown in Figure 4.

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

[0116] 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.

[0117] A UE like the UE 400 shown in Figure 4 may be configured, e.g., with appropriate program code stored in program memory for execution by one or more processors in the UE, to carry out a method like those described above, e.g., as illustrated in Figure 2. More generally, a wireless device, which term encompasses the industry term "UE," may be configured to carry out such a method. Thus, an example wireless device according to various embodiments described herein may comprise radio circuitry configured to communicate with one or more wireless networks and processing circuitry operatively coupled to the radio circuitry, where the processing circuitry (e.g., one or more processors executing stored program instructions) is configured to receive, from a wireless network, a configuration for logging MDT measurements, determine that the received configuration does not identify one or more SNPNs in an area scope for the configuration, and, responsive to said determining, store an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements. In some embodiments or instances, the processing circuitry may be configured to determine that the received configuration does not identify one or more SNPNs in the area scope for the configuration by determining an absence, in the configuration, of any one or more of: a list of SNPNs; a list of PLMNs; and a list of PNI NPN identities.

[0118] In some embodiments or instances, the processing circuitry is further configured to, responsive to said determining, store one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

[0119] In some embodiments or instances, the processing circuitry is further configured to use the stored SNPN identifier and the configuration for determining collection of logged measurements, subsequently to said storing, while in an RRC idle state or RRC inactive state. The processing circuitry may be further configured to use an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, while the wireless device is in said RRC idle state or RRC inactive state, for determining collection of logged measurements.

[0120] In some embodiments or instances, the processing circuitry may be further configured to, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, enter an RRC connected state and use the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements. In some embodiments or instances, the processing circuitry may be further configured to, while the wireless device is in said RRC connected state, using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements. In some embodiments or instances, the processing circuitry may be further configured to control the wireless device such that when the wireless determine determines, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmits the indication of available logged MDT measurements, the processing circuity further controls the wireless device to receive, from the wireless network, a request for logged MDT measurements, and transmit, to the wireless network, logged measurements associated with the stored SNPN identifier. The SNPN corresponding to the stored SNPN identifier may be, in some embodiments or instances, an equivalent SNPN to the SNPN having the SNPN identifier.

[0121] Figure 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gN Bs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0122] 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 remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0124] The network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 500 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 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 500.

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

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

[0127] The memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non- transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 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 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0128] The communication interface 506 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 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 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 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0129] In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

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

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

[0132] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 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.

[0133] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0134] 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.

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

[0136] Embodiments of the techniques, apparatuses, and systems described in detail above include, but are not limited to, the following enumerated examples:

[0137] 1. A method, in a wireless device, for logging and reporting measurements, the method comprising: receiving, from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determining that said configuration does not identify one or more stand-alone non-public networks, SNPNs, in an area scope for the configuration; and responsive to said determining, storing an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

[0138] 2. The method of example embodiment 1, further comprising, responsive to said determining, storing one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

[0139] 3. The method of example embodiment 1 or 2, further comprising, subsequently to said storing, using the stored SNPN identifier and the configuration for determining collection of logged measurements, while in an Radio Resource Control, RRC, idle state or RRC inactive state.

[0140] 4. The method of example embodiment 3, further comprising, while in said RRC idle state or RRC inactive state, using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, for determining collection of logged measurements.

[0141] 5. The method of example embodiment 3 or 4, further comprising, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, entering an RRC connected state and using the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

[0142] 6. The method of example embodiment 5, further comprising, while in said RRC connected state, using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

[0143] 7. The method of example embodiment 5 or 6, wherein the method comprises determining, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmitting the indication of available logged MDT measurements, the method further comprising: receiving, from the wireless network, a request for logged MDT measurements; and transmitting, to the wireless network, logged measurements associated with the stored SNPN identifier. 8. The method of example embodiment 7 wherein the SNPN corresponding to the stored SNPN identifier is an equivalent SNPN to the SNPN having the SNPN identifier.

[0144] 9. The method of any of example embodiments 1-8, wherein determining that said configuration does not identify one or more stand-alone SNPNs in the area scope for the configuration comprises determining an absence, in the configuration, of any one or more of: a list of SNPNs; a list of PLMNs; and a list of PNI NPN identities.

[0145] 10. A wireless device adapted to carry out a method according to any one of example embodiments 1-9.

[0146] 11. A wireless device comprising radio circuitry configured to communicate with one or more wireless networks and processing circuitry operatively coupled to the radio circuitry and configured to control the wireless device to: receive, from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determine that said configuration does not identify one or more stand-alone non-public networks, SNPNs, in an area scope for the configuration; and responsive to said determining, store an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

[0147] 12. The wireless device of example embodiment 12, wherein the processing circuitry is further configured to, responsive to said determining, store one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

[0148] 13. The wireless device of example embodiment 11 or 12, wherein the processing circuitry is further configured to use the stored SNPN identifier and the configuration for determining collection of logged measurements, subsequently to said storing, while in an Radio Resource Control, RRC, idle state or RRC inactive state. 14. The wireless device of example embodiment 13, wherein the processing circuitry is further configured to use an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, while the wireless device is in said RRC idle state or RRC inactive state, for determining collection of logged measurements.

[0149] 15. The wireless device of example embodiment 13 or 14, wherein the processing circuitry is further configured to, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, enter an RRC connected state and use the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

[0150] 16. The wireless device of example embodiment 15, wherein the processing circuitry is further configured to, while the wireless device is in said RRC connected state, using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

[0151] 17. The wireless device of example embodiment 15 or 16, wherein the processing circuitry is further configured to control the wireless device such that when the wireless determine determines, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmits the indication of available logged MDT measurements, the processing circuity further controls the wireless device to: receive, from the wireless network, a request for logged MDT measurements; and transmit, to the wireless network, logged measurements associated with the stored SNPN identifier.

[0152] 18. The wireless device of example embodiment 17 wherein the SNPN corresponding to the stored SNPN identifier is an equivalent SNPN to the SNPN having the SNPN identifier.

[0153] 19. The wireless device of any of example embodiments 11-18, wherein the processing circuitry determines that said configuration does not identify one or more stand-alone SNPNs in the area scope for the configuration by determining an absence, in the configuration, of any one or more of: a list of SNPNs; a list of PLMNs; and a list of PNI NPN identities.

[0154] Some abbreviations:

[0155] AMF Access and Mobility Management Function

[0156] DL Downlink

[0157] EPLMN Equivalent Public Land Mobile Network

[0158] GIN Group ID for Network Selection

[0159] IE Information Element

[0160] LTE Long Term Evolution

[0161] MDT Minimization of Drive Test

[0162] NG-RAN Next Generation Radio Access Network

[0163] NID Network Identifier

[0164] NPN Non Public Network

[0165] NR New Radio

[0166] PLMN Public Land Mobile Network

[0167] PNI-NPN Public network integrated - Non Public Network

[0168] RRC Radio Resource Control

[0169] RSRP Reference Signal Received Power

[0170] RSRQ Reference Signal Received Quality

[0171] SNPN Stand Alone Non Public Network

[0172] SUPI Subscription Permanent Identifier

[0173] UE User Equipment

[0174] Uu Radio interface between UE and network

Claims

CLAIMS1. A method, in a wireless device (400), for logging and reporting measurements, the method comprising:Receiving (210), from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determining (220) that said configuration does not identify one or more stand-alone nonpublic networks, SNPNs, in an area scope for the configuration; and responsive to said determining, storing (230) an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

2. The method of claim 1, further comprising, responsive to said determining, storing one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

3. The method of claim 1 or 2, further comprising, subsequently to said storing, using the stored SNPN identifier and the configuration for determining collection of logged measurements, while in a Radio Resource Control, RRC, idle state or RRC inactive state.

4. The method of claim 3, further comprising, while in said RRC idle state or RRC inactive state, using an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, for determining collection of logged measurements.

5. The method of claim 3 or 4, further comprising, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, entering an RRC connected state and using the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

6. The method of claim 5, wherein the method comprises determining, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmitting the indication of available logged MDT measurements, the method further comprising:Receiving (260), from the wireless network, a request for logged MDT measurements; and Transmitting (270), to the wireless network, logged measurements associated with the stored SNPN identifier.

7. A wireless device (400) for logging and reporting measurements, the wireless device being adapted to: receive (210), from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determine (220) that said configuration does not identify one or more stand-alone nonpublic networks, SNPNs, in an area scope for the configuration; and responsive to said determining, store (230) an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

8. The wireless device of claim 7, being further adapted to carry out the method of any one of claims 2-6.

9. A wireless device (400) comprising radio circuitry (412) configured to communicate with one or more wireless networks and processing circuitry (402) operatively coupled to the radio circuitry and configured to control the wireless device to: receive, from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determine that said configuration does not identify one or more stand-alone non-public networks, SNPNs, in an area scope for the configuration; and responsive to said determining, store an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

10. The wireless device of claim 9, wherein the processing circuitry is further configured to, responsive to said determining, store one or more identifiers for equivalent SNPNs to the SNPN with which the wireless device is currently registered.

11. The wireless device of claim 9 or 10, wherein the processing circuitry is further configured to use the stored SNPN identifier and the configuration for determining collection of logged measurements, subsequently to said storing, while in an Radio Resource Control, RRC, idle state or RRC inactive state.

12. The wireless device of claim 11, wherein the processing circuitry is further configured to use an identifier for each of one or more equivalent SNPNs to the SNPN identifier, and the configuration, while the wireless device is in said RRC idle state or RRC inactive state, for determining collection of logged measurements.

13. The wireless device of claim 11 or 12, wherein the processing circuitry is further configured to, subsequently to said determining collection of logged measurements while in the RRC idle state or inactive, enter an RRC connected state and use the stored SNPN identifier to determine whether to transmit, to the wireless network to which the wireless device is connected, an indication of available logged MDT measurements.

14. The wireless device of claim 13, wherein the processing circuitry is further configured to control the wireless device such that when the wireless determine determines, upon entering the RRC connected state, that the wireless device is connected to an SNPN corresponding to the stored SNPN identifier and transmits the indication of available logged MDT measurements, the processing circuity further controls the wireless device to: receive, from the wireless network, a request for logged MDT measurements; and transmit, to the wireless network, logged measurements associated with the stored SNPN identifier.

15. The wireless device of any of claims 9-14, wherein the processing circuitry comprises one or more processors and memory comprising computer program code for execution by the one or more processors, whereby the processing circuitry is configured to control the wireless device according to the respective one of claims 9-14.

16. A computer-readable medium comprising program code for execution by processing circuitry of a wireless device, the program code comprising instructions configured to cause the wireless device to: receive, from a wireless network, a configuration for logging minimization of drive test, MDT, measurements; determine that said configuration does not identify one or more stand-alone non-public networks, SNPNs, in an area scope for the configuration; and responsive to said determining, store an SNPN identifier for an SNPN with which the wireless device is currently registered, in a variable associated with logged MDT measurements.

Images