Logging of mdt information

Abstract

According to one example of an embodiment of the invention, a method performed by a UE includes receiving (202) a MDT configuration that includes a NPN identity list, and transitioning (204) to idle or inactive state Upon transitioning to idle or inactive state, the UE collects (206) MDT measurements based on the MDT configuration. The UE transitions (208) to an any cell selection state, and upon transitioning to the any cell selection state, determines (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list. If the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, the UE logs (212) first information and measurements associated with the last suitable cell.

Description

LOGGING OF MDT INFORMATIONTECHNICAL FIELD

[0001] The present disclosure relates to wireless communication networks, and, in particular, to the performance of minimization of drive testing (MDT) measurements by a user equipment (UE) in a wireless communication network.BACKGROUND

[0002] MDT was standardized for New Radio (NR) in Rel-16 to reduce the amount of drive tests that need to be performed manually by network operators. MDT is a UE- assisted framework in which network measurements are collected by both IDLE / INACTIVE and Radio Resource Control (RRC) Connected UE(s) in order to aid the network in gathering valuable information. MDT has been specified for both LTE and NE in [1],

[0003] In general, there are two types of MDT measurement logging, namely, Logged MDT and Immediate MDT. For Logged MDT, a UE in RRC IDLE / RRC INACTIVE state is configured to perform periodic and event-triggered MDT logging after receiving an MDT configuration from the network. The UE reports 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 is in RRC CONNECTED state. The DL pilot strength measurement of Logged MDT is collected based on the existing measurements required for cell reselection purpose, without requiring the UE to perform additional measurements. Measurement logging for Logged MDT is shown in Table 1.Table 1 - Measurement Logging for Logged MDT

[0004] For periodic Logged MDT, a UE receives MDT configuration(s) including the parameters logginginterval and loggingduration in an RRC message, i.e., LoggedMeasurementConfiguration, from the network. A timer (T330) is started at the UEupon receiving the configurations. The timer is set to the value of loggingduration (10 min - 120 min). The UE performs periodic MDT logging with the interval set to logginginterval (1.28 s - 61.44 s) when the UE is in RRC IDLE state. An example of MDT logging is shown in Figure 1.

[0005] Non-Public Network

[0006] A Non-Public Network (NPN) is a network deployed for non-public use. An NPN may either be a stand-alone Non-Public Network (SNPN), i.e., a network operated by an NPN operator and not relying on network functions provided by a public land mobile network (PLMN), or a Public Network Integrated NPN (PNI-NPN), i.e. a non-public network deployed with the support of a PLMN. An NPN and a PLMN can share an radio access network (RAN), such as the next generation RAN (NG-RAN).

[0007] PNI-NPN

[0008] PNI-NPNs are NPNs made available via PLMNs. When a PNI-NPN is made available via a PLMN, the UE needs to have a subscription for the PLMN to be able to access the PNI-NPN.

[0009] A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. A CAG is used to prevent UEs that are not allowed to access the NPN via the associated cell(s) from automatically selecting and accessing the associated CAG cell(s).

[0010] A CAG is identified by a CAG Identifier (ID) which is unique within the scope of a PLMN ID. A CAG cell broadcasts one or more CAG Identifiers for each PLMN. A CAG cell may also broadcast a human-readable network name associated with the CAG ID.

[0011] A UE that supports CAG, as indicated as part of the UE 5GMM Core Network Capability, may be pre-configured or (re)configured with the following CAG information, included in the subscription as part of the UE’s mobility restrictions:• an Allowed CAG list, i.e. a list of CAG Identifiers the UE is allowed to access; and• optionally, a CAG-only indication of whether the UE is only allowed to access 5GS via CAG cells.

[0012] In a PLMN, the UE only considers the CAG information provided for the PLMN. When the UE is roaming and the serving PLMN provides CAG information, the UE only updates the CAG information provided for the serving PLMN, while the stored CAGinformation for other PLMNs is not updated. When the UE is not roaming and the home PLMN (HPLMN) of the UE provides CAG information, the UE updates the CAG information stored in the UE with the received CAG information for all the PLMNs.

[0013] The UE stores the latest available CAG information for every PLMN for which it is provided, and keeps it stored when the UE is de-registered or switched off.

[0014] It is assumed for network and cell selection and access control that the CAG cell broadcasts information such that only UEs supporting CAG are accessing the cell, and the Mobility Restrictions are able to restrict the UEs mobility according to the Allowed CAG list (if configured in the subscription) and include an indication as to whether the UE is only allowed to access 5GS via CAG cells (if configured in the subscription).

[0015] Emergency services are supported in CAG cells, for UEs supporting CAG, whether normally registered or emergency registered.

[0016] SNPN

[0017] The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. NIDs are either chosen individually by SNPNs at deployment time (and may therefore not be unique) but use a different numbering space than the coordinated assignment or chosen in a coordinated manner, and are therefore globally unique independent of the PLMN ID used, or are globally unique only in combination with the PLMN ID.

[0018] NG-RAN nodes which provide access to SNPNs broadcast the following information:• one or more PLMN IDs;• a list of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to; and, optionally:• a human-readable network name for each SNPN; and• information to prevent UEs that do not support SNPNs from accessing the cell, e.g. if the cell only provides access to non-public networks.

[0019] An SNPN-enabled UE supports the 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. UEs operating in SNPN access mode only select cells and networks that broadcast both the PLMN ID and NID of the selected SNPN.

[0020] If a UE moves its 3 GPP access between SNPN and PLMN, network selection is performed in which the UE performs initial registration. If the UE moves its3GPP access between SNPNs and network selection is performed, then the UE performs initial or mobility registration.

[0021] Any Cell Selection State

[0022] The "any cell selection" state (also referred to as anyCellSelection state) is applicable for the RRC IDLE and RRC INACTIVE states. In this state, the UE performs a cell selection process to find a suitable cell.

[0023] For a UE that is not in SNPN access mode, if the cell selection process fails to find a suitable cell after a complete scan of all radio access technologies (RATs) and all frequency bands supported by the UE, the UE attempts to find an acceptable cell of any PLMN to camp on, trying all RATs that are supported by the UE and searching first for a high-quality cell.

[0024] For a UE that is in SNPN access mode, if the cell selection process fails to find a suitable cell after a complete scan of all frequency bands supported by the UE, the UE attempts to find an acceptable cell of any SNPN to camp on. A UE that is not camped on any cell will stay in the Any Cell Selection state.

[0025] For a UE that is not operating in SNPN Access Mode, a cell is considered as suitable if the following conditions are fulfilled:• the cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list, and for that PLMN either, the PLMN-ID of that PLMN is broadcast by the cell with no associated CAG-IDs and CAG-only indication in the UE for that PLMN is absent or false, or the allowed CAG list in the UE for that PLMN includes a CAG-ID broadcast by the cell for that PLMN,• the cell selection criteria are fulfilled,• according to the latest information provided by non-access stratum (NAS) signalling, the cell is not barred, and• the cell is part of at least one tracking area (TA) that is not part of the list of "Forbidden Tracking Areas for Roaming", which belongs to a PLMN that fulfils the first requirement above.

[0026] For a UE operating in SNPN Access Mode, a cell is considered as suitable if the following conditions are fulfilled:• the cell is part of either the selected SNPN or the registered SNPN of the UE,• the cell selection criteria are fulfilled,• according to the latest information provided by NAS, the cell is not barred, and• the cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" which belongs to either the selected SNPN or the registered SNPN of the UE.SUMMARY

[0027] Some embodiments described herein enable a UE to log information which may be used to identify possible coverage gaps in a NPN network.

[0028] A method performed by a user equipment, UE, according to some embodiments includes receiving a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list, and transitioning to idle or inactive state. Upon transitioning to idle or inactive state, the UE collects MDT measurements based on the MDT configuration. The UE then transitions to an any cell selection state, and upon transitioning to the any cell selection state, the UE determines whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list. In response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, the UE logs first information and measurements associated with the last suitable cell.

[0029] The NPN identity list may be part of an area scope for the MDT configuration.

[0030] The method may further include storing the NPN identity list in a memory before transitioning to the any cell selection state

[0031] The NPN identity list may include a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

[0032] The NPN identity list may include a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

[0033] The method may further include transitioning to connected state after being in any cell selection state, and in response to transitioning to connected state, transmitting a logged MDT report including the first information and measurements to a network node.

[0034] The first information may include one or more of a serving cell identity of the last suitable cell, a closed access group, CAG, identifier broadcasted by the last suitable cell, a measurement result associated with the last suitable cell, an NPN identity list broadcasted by the last suitable cell, and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

[0035] A UE according to some embodiments includes processing circuitry, a transceiver coupled to the processing circuitry, and a memory coupled to the processing circuitry. The memory includes computer readable program instructions that, when executed by the processing circuitry, cause the UE to perform operations including receiving a MDT configuration that includes a NPN identity list, transitioning to idle or inactive state, upon transitioning to idle or inactive state, collecting MDT measurements based on the MDT configuration, transitioning to an any cell selection state, upon transitioning to the any cell selection state, determining whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging first information and measurements associated with the last suitable cell.

[0036] A UE according to some embodiments is adapted to receive a MDT configuration that includes a NPN identity list and transition to idle or inactive state. Upon transitioning to idle or inactive state, the UE collects MDT measurements based on the MDT configuration. The UE transitions to an any cell selection state and upon transitioning to the any cell selection state, determines whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list. In response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, the UE logs first information and measurements associated with the last suitable cell.

[0037] Some embodiments provide a non-transitory medium including computer readable program instructions that, when executed by processing circuitry of a user equipment, UE, cause the UE to perform operations including receiving a MDT configurationthat includes a NPN identity list, transitioning to idle or inactive state, upon transitioning to idle or inactive state, collecting MDT measurements based on the MDT configuration, transitioning to an any cell selection state, upon transitioning to the any cell selection state, determining whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging first information and measurements associated with the last suitable cell.

[0038] A method performed by a network node according to some embodiments includes transmitting a MDT configuration that includes a NPN identity list to a UE. The network node determines that the UE has transitioned to active state, and receives a logged MDT report from the UE, wherein the logged MDT report includes first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

[0039] The method may further include, after transmitting the MDT configuration to the UE, determining that the UE has transitioned to idle or inactive state.

[0040] The NPN identity list may be part of an area scope for the MDT configuration.

[0041] The NPN identity list may include a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

[0042] The NPN identity list may include a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

[0043] The first information may include one or more of a serving cell identity of the last suitable cell, a closed access group, CAG, identifier broadcasted by the last suitable cell, a measurement result associated with the last suitable cell, an NPN identity list broadcasted by the last suitable cell, and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

[0044] A network node according to some embodiments includes processing circuitry, a transceiver coupled to the processing circuitry, and a memory coupled to the processing circuitry. The memory includes computer readable program instructions that, when executed by the processing circuitry, cause the network node to perform operations including transmitting a MDT configuration that includes a NPN identity list to a UE, determining that the UE has transitioned to active state, and receiving a logged MDT report from the UE, wherein the logged MDT report includes first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

[0045] A network node according to some embodiments is adapted to transmit a MDT configuration that includes a NPN identity list to a UE. The network node determines that the UE has transitioned to active state, and receives a logged MDT report from the UE, wherein the logged MDT report includes first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

[0046] Some embodiments provide a non-transitory medium including computer readable program instructions that, when executed by processing circuitry of a network node, cause the network node to perform operations including transmitting a MDT configuration that includes a NPN identity list to a UE, determining that the UE has transitioned to active state, and receiving a logged MDT report from the UE, wherein the logged MDT report includes first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 illustrates an example of MDT logging.

[0048] Figure 2 illustrates operations by a UE according to some embodiments.

[0049] Figure 3 illustrates operations by a network node according to some embodiments.

[0050] Figure 4 shows an example of a communication system in accordance with some embodiments.

[0051] Figure 5 shows a UE in accordance with some embodiments.

[0052] Figure 6 shows a network node in accordance with some embodiments.

[0053] Figure 7 is a block diagram of a host in accordance with various aspects described herein.

[0054] Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0055] Figure 9 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTION

[0056] In the current RRC specification [2], a UE in a public network configured with a logged MDT configuration can be conditionally configured to log additional information if it transitions to “Any Cell Selection state,” as shown in Table 2:Table 2 - Excerpt from TS 38.331 V17.5.0

[0057] However, UEs that conform to 3GPP Release 18 (referred to herein as Rel- 18 UEs) can be configured to monitor performance of a NPN network using a list of CAG identities in the logged measurement configuration. Thus, the UE has a PLMN identity list and / or a CAG ID list configured in the logged measurement configuration. The PLMN identity list and CAG ID list can be configured independently of each other.

[0058] Consider a scenario in which a UE is in camped normally state in Cell-1, and Cell-1 broadcasts PLMN-1 in the supported PLMN ID list of the system information block 1 (SIB1) message, but PLMN-1 is not part of the PLMN ID list configured in thelogged MDT configuration. Cell-1 then broadcasts CAG-1 and CAG-2, both of which are part of the logged MDT configuration in the UE. The UE goes to any cell selection state.

[0059] In this scenario, since the registered PLMN (RPLMN) of the UE at Cell-1 is not part of the PLMN ID list stored in the logged MDT configuration, the UE does not log information of Cell-1. However, the Cell-1 information is important for the network to understand, since Cell-1 was broadcasting CAG-1 and CAG-2 information, and the network would need to identify the coverage of this cell to optimize its performance.

[0060] Some embodiments provide a method performed by a UE configured with a logged MDT configuration and camping in anyCellSelection state to log a first information if a first condition is satisfied. The UE receives a logged MDT configuration from the network, and transitions to RRC IDLE state or RRC inactive state.

[0061] The UE transitions to anyCellSelection state and determines if a first condition is satisfied, where the first condition is whether one of the CAG IDs broadcasted by the last suitable cell belongs to the NPN-IdentityList configured in the logged MDT configuration.

[0062] In response to determining that the first condition is satisfied, the UE stores a first set of information in a logged MDT report. The first set of information may include one or more of• the serving cell identity of the last suitable cell;• the CAG IDs broadcasted by the last suitable cell;• the measurement results of the last suitable cell;• the NPN-identity list broadcasted by the last suitable cell; or• the NPN-identity list broadcasted by the last suitable cell to which the UE was allowed to connect (e.g., based on the configuration received at the NAS layer).

[0063] The UE transitions to RRC connected state and transmits the logged MDT report to the network upon request.

[0064] Thereby, some embodiments enable a UE to log, in a logged MDT report, when the UE transitions to anyCellSelection state based on broadcasted CAG information by the last suitable cell before entering the anyCellSelection state.

[0065] In particular, some embodiments enable a UE to log information, in a logged MDT report, that allows the network to identify the UE to be in anyCellSelectionstate. The network may thereby be able to identify possible coverage gaps in the NPN network using this information.

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

[0067] In the following description, the terms “user equipment” (or UE), “wireless access user” and “wireless terminal” are used interchangeably to refer to a generic device or set of devices capable of communicating over a wireless network.

[0068] The network may include any wireless network, such as wireless communication network implementing the Long Term Evolution (LTE) or New Radio (NR) 3 GPP standard.

[0069] The term “network node” refers to a wireless network node.

[0070] The term “NPN” refers to any non-public network, such as, without limitation, an SNPN, PNI-NPN, etc., as described above.

[0071] In the following description, a UE is assumed to be able to connect to a NPN network, and the network has configured the UE with a logged MDT configuration. It is further assumed that the UE is in anyCellSelection state.

[0072] The term “NPN identity” includes both PNI-NPN and SNPN identities broadcasted by the network.

[0073] A method performed by a wireless terminal includes receiving an MDT configuration including an NPN-identity list as a (part of) area scope for MDT measurements. The NPN-identity list can be one or both of the following:• a PNI-NPN identity list (including a list of PLMN and CAG IDs); or• an SNPN identity list (including a list of PLMN and NIDs).

[0074] The method further includes storing the received NPN-identity list in a memory (e.g., loggedMeasurementReporf).

[0075] Upon transitioning to RRC IDLE or Inactive state, the UE starts to collect the MDT measurements based on the provided MDT configuration and the area scope, comprising the NPN-identity list, included in the MDT configuration.

[0076] Upon being unable to find a suitable cell to camp on, the UE performs a transition to “any cell selection” state. The UE determines whether the last suitable cell that the UE camped on (before entering any cell selection state) was broadcasting at least an NPNidentity that is included in the NPN-identity list included as the area scope of the MDT configuration.

[0077] Upon determining that the last suitable cell was broadcasting at least an NPN identity that is included in the NPN-identity list included as the area scope of the MDT configuration, the UE logs a first information and measurements of the last suitable cell in the MDT measurements while being in the any cell selection state. The first information and measurements of the last suitable cell may include the following:• the global Cell ID of the last suitable cell;• the measurement results of the last suitable cell, or the last measurement results samples collected in the last suitable cell. The measurement results may include one or more of radio measurements such as RSRP, RSRQ, SINR,RS SI, etc.;• the CAG ID list broadcasted by the last suitable cell;• the NPN-identity list broadcasted by the last suitable cell; and / or• the NPN-identity list broadcasted by the last suitable cell to which the UE was allowed to connect (e.g., based on the configuration received at the NAS layer)

[0078] Referring to Figure 2, a method performed by a UE includes receiving an MDT configuration that includes an NPN identity list (block 202), and thereafter transitioning to idle or inactive state (block 204). Upon transitioning to idle or inactive state, the UE collects MDT measurements based on the MDT configuration (block 206). The UE then transitions to an any cell selection state (block 208). Upon transitioning to the any cell selection state, the UE determines whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list (block 210).

[0079] In response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, the UE logs first information and measurements associated with the last suitable cell (block 212).

[0080] In some embodiments, the NPN identity list is part of an area scope for the MDT configuration.

[0081] The method may further include storing the NPN identity list in a memory before transitioning to the any cell selection state

[0082] In some embodiments, the NPN identity list includes a public network integrated, PNI, NPN identity list that includes a list public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

[0083] In some embodiments, the NPN identity list includes a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

[0084] The method may further include transitioning to connected state after being in any cell selection state, and in response to transitioning to connected state, transmitting a logged MDT report including the first information and measurements to a network node.

[0085] In some embodiments, the first information includes one or more of a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; the NPN-identity list broadcasted by the last suitable cell; or the NPN-identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

[0086] Referring to Figure 3, a method performed by a network node includes transmitting a MDT configuration that includes a NPN identity list to a UE (block 302), determining that the UE has transitioned to idle or inactive state (block 304), determining that the UE has transitioned to active state (block 306), and receiving a logged MDT report from the UE (block 308). The logged MDT report includes first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

[0087] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0088] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3rdGeneration 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, insome embodiments, the telecommunication network 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 402 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 402, including one or more network nodes 410 and / or core network nodes 408.

[0089] 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 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 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 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

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

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

[0092] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408. 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).

[0093] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 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.

[0094] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communicationsystem 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.

[0095] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 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)ZMassive loT services to yet further UEs.

[0096] In some examples, the UEs 412 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 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard 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).

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

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

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

[0100] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0101] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, a memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. 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.

[0102] The processing circuitry 502 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 510. The processing circuitry 502 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 502 may include multiple central processing units (CPUs).

[0103] In the example, the input / output interface 506 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 500. 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.

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

[0105] The memory 510 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 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0106] The memory 510 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium.

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

[0108] In the illustrated embodiment, communication functions of the communication interface 512 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 protocolsand / 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.

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

[0110] 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.[OHl] 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 controlledsurgical 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 500 shown in Figure 5.

[0112] 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-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

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

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

[0115] 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 RadioHeads (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).

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

[0117] The network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. The network node 600 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 600 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 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, 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 600.

[0118] The processing circuitry 602 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 encodedlogic operable to provide, either alone or in conjunction with other network node 600 components, such as the memory 604, to provide network node 600 functionality.

[0119] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 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 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0120] The memory 604 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 602. The memory 604 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 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated.

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

[0122] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

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

[0124] The antenna 610, communication interface 606, and / or the processing circuitry 602 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 610, the communication interface 606, and / or the processing circuitry 602 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.

[0125] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may furthercomprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 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 608. As a further example, the power source 608 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.

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

[0127] Figure 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein. As used herein, the host 700 may be or comprise various combinations 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 700 may provide one or more services to one or more UEs.

[0128] The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a network interface 708, a power source 710, and a memory 712. 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 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host 700.

[0129] The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 may be implemented in a container-based architecture andmay provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., 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, heads-up display systems). The host application programs 714 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 700 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 714 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 (MPEG-DASH), etc.

[0130] Figure 8 is a block diagram illustrating a virtualization environment 800 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 800 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 800 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0131] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0132] Hardware 804 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardwaredevices 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 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

[0133] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, 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.

[0134] In the context of NFV, a VM 808 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 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, 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 808 on top of the hardware 804 and corresponds to the application 802.

[0135] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 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 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 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 radio access node or a base station. In some embodiments, some signaling can be provided with the use ofa control system 812 which may alternatively be used for communication between hardware nodes and radio units.

[0136] Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 412a of Figure 4 and / or UE 500 of Figure 5), network node (such as network node 410a of Figure 4 and / or network node 600 of Figure 6), and host (such as host 416 of Figure 4 and / or host 700 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9.

[0137] Like host 700, embodiments of host 902 include hardware, such as a communication interface, processing circuitry, and memory. The host 902 also includes software, which is stored in or accessible by the host 902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 906 connecting via an over-the-top (OTT) connection 950 extending between the UE 906 and host 902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 950.

[0138] The network node 904 includes hardware enabling it to communicate with the host 902 and UE 906. The connection 960 may be direct or pass through a core network (like core network 406 of Figure 4) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0139] The UE 906 includes hardware and software, which is stored in or accessible by UE 906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 906 with the support of the host 902. In the host 902, an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and host 902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 950.

[0140] The OTT connection 950 may extend via a connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906. The connection 960 and wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0141] As an example of transmitting data via the OTT connection 950, in step 908, the host 902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 906. In other embodiments, the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction. In step 910, the host 902 initiates a transmission carrying the user data towards the UE 906. The host 902 may initiate the transmission responsive to a request transmitted by the UE 906. The request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906. The transmission may pass via the network node 904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 914, the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902.

[0142] In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902. Accordingly, in step 916, the UE 906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904. In step 920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902. In step 922, the host 902 receives the user data carried in the transmission initiated by the UE 906.

[0143] One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments may improve the ability of a UE to collect useful information for a network and thereby provide benefits such as improved network management.

[0144] In an example scenario, factory status information may be collected and analyzed by the host 902. As another example, the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 902 may store surveillance video uploaded by a UE. As another example, the host 902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 902 may be used for energy pricing, remote control of nontime critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0145] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 950 between the host 902 and UE 906, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 902 and / or UE 906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 902. The measurements may be implemented in that software causes messages to be transmitted, inparticular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc.

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

[0147] 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 thecomputing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0148] Embodiments of the techniques, apparatuses, and systems described herein include, but are not limited to, the following enumerated examples:Group A EmbodimentsAl. A method performed by a user equipment, UE, comprising: receiving (202) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list; transitioning (204) to idle or inactive state; upon transitioning to idle or inactive state, collecting (206) MDT measurements based on the MDT configuration; transitioning (208) to an any cell selection state; upon transitioning to the any cell selection state, determining (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list; in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging (212) first information and measurements associated with the last suitable cell.A2. The method of Embodiment Al, wherein the NPN identity list is as part of an area scope for the MDT configuration.A3. The method of Embodiment Al or A2, further comprising: storing the NPN identity list in a memory before transitioning to the any cell selection stateA4. The method of any previous Embodiment, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.A5. The method of any of Embodiments Al to A3, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobilenetworks, PLMNs, and associated network identifiers.A6. The method of any previous Embodiment, further comprising: transitioning to connected state after being in any cell selection state; and in response to transitioning to connected state, transmitting a logged MDT report including the first information and measurements to a network node.A7. The method of any previous Embodiment wherein the first information comprises one or more of a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; the NPN-identity list broadcasted by the last suitable cell; or the NPN-identity list broadcasted by the last suitable cell to which the UE is allowed to connect.A8. The method of any of the previous Embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B EmbodimentsBl. A method performed by a network node, comprising: transmitting (302) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list to a user equipment, UE; determining (306) that the UE has transitioned to active state; and receiving (308) a logged MDT report from the UE, wherein the logged MDT report comprises first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.B2. The method of Embodiment Bl, wherein the NPN identity list is as part of an area scope for the MDT configuration.B3. The method of any previous Embodiment, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.B4. The method of Embodiment Bl or B2, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.B5. The method of any previous Embodiment wherein the first information comprises one or more of: a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; the NPN-identity list broadcasted by the last suitable cell; or the NPN-identity list broadcasted by the last suitable cell to which the UE is allowed to connect.B6. The method of any previous Embodiment, further comprising: after transmitting the MDT configuration to the UE, determining (304) that the UE has transitioned to idle or inactive state.B7. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C EmbodimentsCl. A user equipment, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.C2. A network node, comprising: processing circuitry configured to perform any of the steps of any of the Group Bembodiments; power supply circuitry configured to supply power to the processing circuitry.C3. A user equipment (UE), comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.C4. A host configured to operate in a communication system to provide an over-the- top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.C5. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.C6. A method implemented in a host configured to operate in a communication systemthat further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.C7. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.C8. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.C9. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.CIO. The communication system of the previous embodiment, further comprising: the network node; and / or the UE.Cl 1. A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, theprocessing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.C12. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.C13. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.C14. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.Cl 5. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.Cl 6. A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.Cl 7. The host of the previous embodiment, wherein the cellular network furtherincludes a network node configured to communicate with the UE to transmit the user data to the UE from the host.C18. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.Cl 9. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.C20. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.C21. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.C22. A host configured to operate in a communication system to provide an over- the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group Aembodiments to transmit the user data to the host.C23. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.C24. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.C25. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.C26. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.C27. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.Some references:[1] 3GPP TS37.320V17.4.0 Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2, 3 GPP[2] 3GPP TS 38.331V17.5.0 NR; Radio Resource Control (RRC); Protocol specification, 3 GPP[3] 3GPP TS 38.304 V17.5.0 NR; User Equipment (UE) procedures in idle mode and in RRC Inactive state, 3 GPP

Claims

CLAIMS1. A method performed by a user equipment, UE, comprising: receiving (202) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list; transitioning (204) to idle or inactive state; upon transitioning to idle or inactive state, collecting (206) MDT measurements based on the MDT configuration; transitioning (208) to an any cell selection state; upon transitioning to the any cell selection state, determining (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list; and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging (212) first information and measurements associated with the last suitable cell.

2. The method of Claim 1, wherein the NPN identity list is part of an area scope for the MDT configuration.

3. The method of Claim 1 or 2, further comprising: storing the NPN identity list in a memory before transitioning to the any cell selection state4. The method of any of Claims 1 to 3, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

5. The method of any of Claims 1 to 3, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

6. The method of any of Claims 1 to 5, further comprising: transitioning to connected state after being in any cell selection state; andin response to transitioning to connected state, transmitting a logged MDT report including the first information and measurements to a network node.

7. The method of any of Claims 1 to 6, wherein the first information comprises one or more of a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; an NPN identity list broadcasted by the last suitable cell; and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

8. A user equipment, UE, comprising: processing circuitry; a transceiver coupled to the processing circuitry; and a memory coupled to the processing circuitry, wherein the memory comprises computer readable program instructions that, when executed by the processing circuitry, cause the UE to perform operations comprising: receiving (202) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list; transitioning (204) to idle or inactive state; upon transitioning to idle or inactive state, collecting (206) MDT measurements based on the MDT configuration; transitioning (208) to an any cell selection state; upon transitioning to the any cell selection state, determining (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list; and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging (212) first information and measurements associated with the last suitable cell.

9. The UE of Claim 8, wherein the NPN identity list is part of an area scope for theMDT configuration.

10. The UE of Claim 8 or 9, wherein the operations further comprise: storing the NPN identity list in a memory before transitioning to the any cell selection state11. The UE of any of Claims 8 to 10, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

12. The UE of any of Claims 8 to 10, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

13. The UE of any of Claims 8 to 12, wherein the operations further comprise: transitioning to connected state after being in any cell selection state; and in response to transitioning to connected state, transmitting a logged MDT report including the first information and measurements to a network node.

14. The UE of any of Claims 8 to 13, wherein the first information comprises one or more of: a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; an NPN identity list broadcasted by the last suitable cell; and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

15. A user equipment, UE, adapted to: receive (202) a minimization of drive testing, MDT, configuration that includes a nonpublic network, NPN, identity list; transition (204) to idle or inactive state; upon transitioning to idle or inactive state, collect (206) MDT measurements based onthe MDT configuration; transition (208) to an any cell selection state; upon transitioning to the any cell selection state, determine (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list; and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, log (212) first information and measurements associated with the last suitable cell.

16. The UE of Claim 15, wherein the UE is further adapted to perform the operations according to any of Claims 2 to 7.

17. A non-transitory medium comprising computer readable program instructions that, when executed by processing circuitry of a user equipment, UE, cause the UE to perform operations comprising: receiving (202) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list; transitioning (204) to idle or inactive state; upon transitioning to idle or inactive state, collecting (206) MDT measurements based on the MDT configuration; transitioning (208) to an any cell selection state; upon transitioning to the any cell selection state, determining (210) whether a last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list; and in response to determining that the last suitable cell the UE camped on prior to entering the any cell selection state was broadcasting an NPN identity that is included in the NPN identity list, logging (212) first information and measurements associated with the last suitable cell.

18. A method performed by a network node, comprising: transmitting (302) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list to a user equipment, UE;determining (306) that the UE has transitioned to active state; and receiving (308) a logged MDT report from the UE, wherein the logged MDT report comprises first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

19. The method of Claim 18, wherein the NPN identity list is part of an area scope for the MDT configuration.

20. The method of Claim 18 or 19, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

21. The method of Claim 18 or 19, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

22. The method of any of Claims 18 to 21, wherein the first information comprises one or more of: a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; an NPN identity list broadcasted by the last suitable cell; and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

23. The method of any of Claims 18 to 22, further comprising: after transmitting the MDT configuration to the UE, determining (304) that the UE has transitioned to idle or inactive state.

24. A network node, comprising: processing circuitry; a transceiver coupled to the processing circuitry; anda memory coupled to the processing circuitry, wherein the memory comprises computer readable program instructions that, when executed by the processing circuitry, cause the network node to perform operations comprising: transmitting (302) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list to a user equipment, UE; determining (306) that the UE has transitioned to active state; and receiving (308) a logged MDT report from the UE, wherein the logged MDT report comprises first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

25. The network node of Claim 24, wherein the NPN identity list is part of an area scope for the MDT configuration.

26. The network node of Claim 24 or 25, wherein the NPN identity list comprises a public network integrated, PNI, NPN identity list that includes a list of public land mobile networks, PLMNs, and associated closed access group, CAG, identifiers.

27. The network node of Claim 24 or 25, wherein the NPN identity list comprises a standalone NPN, SNPN, identity list that includes a list of public land mobile networks, PLMNs, and associated network identifiers.

28. The network node of any of Claims 24 to 27, wherein the first information comprises one or more of a serving cell identity of the last suitable cell; a closed access group, CAG, identifier broadcasted by the last suitable cell; a measurement result associated with the last suitable cell; an NPN identity list broadcasted by the last suitable cell; and an NPN identity list broadcasted by the last suitable cell to which the UE is allowed to connect.

29. The network node of any of Claims 24 to 28, wherein the operations further comprise:after transmitting the MDT configuration to the UE, determining (304) that the UE has transitioned to idle or inactive state.

30. A network node, adapted to: transmit (302) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list to a user equipment, UE; determine (306) that the UE has transitioned to active state; and receive (308) a logged MDT report from the UE, wherein the logged MDT report comprises first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

31. The network node of Claim 30, wherein the network node is further adapted to perform the operations according to any of Claims 19 to 23.

32. A non-transitory medium comprising computer readable program instructions that, when executed by processing circuitry of a network node, cause the network node to perform operations comprising: transmitting (302) a minimization of drive testing, MDT, configuration that includes a non-public network, NPN, identity list to a user equipment, UE; determining (306) that the UE has transitioned to active state; and receiving (308) a logged MDT report from the UE, wherein the logged MDT report comprises first information and measurements associated with a last suitable cell the UE camped on prior to entering an any cell selection state that was broadcasting an NPN identity that is included in the NPN identity list.

Images