Minimized configuration range of operational tests for different network types

Abstract

A Radio Access Network ("RAN") node may determine 2310 a Minimization of Driving Test ("MDT") configuration that includes area coverage associated with cells identified by at least one of a Public Network Integrated Non-Public Network ("PNI-NPN"), a Standalone Non-Public Network ("SNPN"), and a Public Regional Mobile Network ("PLMN"). The RAN node may configure 2320 a communication device served by a first cell in a first communication network with the MDT configuration to instruct the communication device to collect MDT measurements from a second cell in the second communication network.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to minimizing set ranges of driving tests for different network types. [Background technology]

[0002] FIG. 1 illustrates an example of a New Radio ("NR") network (e.g., a 5G network) that includes a fifth-generation ("5G") core ("5GC") network 130, network nodes 120a-120b (e.g., 5G base stations ("gNBs")), and multiple communication devices 110 (also referred to as user equipment ("UE")).

[0003] A Non-Public Network ("NPN") is a mechanism that allows a network to be deployed and / or managed by an entity other than the authorized operator. In this specification, an "authorized operator" is assumed to be the operator of one or more Public Local Mobile Networks ("PLMNs"). Note that a PLMN also has an identifier, which may be called a PLMN Identifier ("ID") or simply a "PLMN." Summary of the Invention

[0004] According to some embodiments, a method of operating a Radio Access Network ("RAN") node is provided. The method includes determining a Minimization of Driving Test ("MDT") configuration that includes an area range that identifies at least one of a Public Network Integrated Non-Public Network ("PNI-NPN") identity, a Standalone Non-Public Network ("SNPN") identity, and a Public Local Mobile Network ("PLMN") identity. The method may further include configuring a communication device served by a first cell in a first communication network with the MDT configuration to instruct the communication device to collect MDT measurements from a second cell in the second communication network.

[0005] According to another embodiment, a method of operating a core network ("CN") node is provided. The method includes transmitting a Minimization of Driving Test ("MDT") configuration to a radio access network ("RAN") node. The MDT configuration includes a region range that identifies at least one of a public network integrated non-public network ("PNI-NPN") identity, a standalone non-public network ("SNPN") identity, and a public regional mobile network ("PLMN") identity.

[0006] According to other embodiments, there is provided a RAN node, a CN node, a communications device, a computer program, a computer program product, a non-transitory computer-readable medium, a system, or a host for performing one of the above methods.

[0007] Particular embodiments may provide one or more of the following technical advantages: In some embodiments, MDT measurement related information may be reported between SNPNs, PNI-NPNs, and PLMNs, which allows networks to optimize inter-network and intra-network coverage issues.

[0008] The addition of an NPN identifier to the list of networks for which the MDT configuration is valid is not clear. The reason for this is that private networks are separate networks from PLMNs. For example, SNPNs are not intended to be connected to PLMNs or PNI-NPNs. Furthermore, UEs under current specifications are not permitted to roam between SNPNs and other networks. Currently, MDT configurations are equivalent to each other and can only be applied to a UE within the set of PLMNs that includes the UE's registered PLMN. Therefore, extending the area scope of MDT configuration to NPNs is not clear, as it would require coordination and agreement between the NPN operator and the PLMN operator. However, the advantage of this configuration is that for UEs that can roam between NPNs and PLMNs, the operator (PLMN operator or NPN operator) can configure MDT measurements in the UE and, by receiving such measurements, have uniform monitoring of some aspects related to the PLMN and NPN. In some examples, the operator can monitor coverage in the NPN and PLMN, as well as at the coverage boundary between the PLMN and NPN. This ensures that coverage between different networks is uniform and that movements between different networks do not suffer from failures due to insufficient coverage. In an additional or alternative example, an operator can monitor performance at the radio and service levels for UEs moving between PLMNs and NPNs. This allows the operator to optimize steering of UEs toward coverage locations where particular services are best served, as well as optimize service coverage where performance is poor.

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

[0010] [Figure 1]FIG. 1 is a schematic diagram illustrating an example of a fifth generation ("5G") network. [Figure 2] FIG. 10 is a signal flow diagram illustrating an example of successful operation of initial context setup. [Figure 3] FIG. 10 is a signal flow diagram illustrating an example of successful operation of handover resource allocation. [Figure 4] FIG. 10 is a signal flow diagram illustrating an example of a successful operation of start trace. [Figure 5] 10 is a table illustrating an example of a trace activation IE. [Figure 6] 10 is a table showing an example of an MDT setting IE. [Figure 7] 10 is a table illustrating an example of an MDT PLMN list IE. [Figure 8] 1 is a table illustrating an example of range boundaries for an MDT PLMN list. [Figure 9] 10 is a table showing an example of an MDT configuration-NR IE. [Figure 10] 10 is a table showing an example of range boundaries for MDT configuration-NR. [Figure 11] 10 is a table showing an example of area ranges of neighboring cell IEs. [Figure 12] 10 is a table illustrating an example of range boundaries for area ranges of neighboring cells. [Figure 13] FIG. 1 is a schematic diagram illustrating an example of communication devices entering and leaving a PN / NPN, according to some embodiments. [Figure 14] 1 is a schematic diagram illustrating an example of a communication device moving within a PN / NPN, according to some embodiments. [Figure 15] 1 is a table illustrating an example of an MDT configuration-NR IE, according to some embodiments. [Figure 16] 1 is a table illustrating an example of range boundaries for MDT configuration-NR, according to some embodiments. [Figure 17] 1 is a table illustrating an example of an MDT PLMN List IE, according to some embodiments. [Figure 18]18 is a table illustrating an example of range boundaries for the MDT PLMN list of FIG. 17, according to some embodiments. [Figure 19] 1 is a table illustrating an example of a Cell NID Information IE, according to some embodiments. [Figure 20] 1 is a table illustrating an example of an MDT NPN List IE, according to some embodiments. [Figure 21] 10 is a table illustrating an example of area coverage of neighboring cells IEs, according to some embodiments. [Figure 22] 10 is a table illustrating another example of an MDT configuration-NR IE according to some embodiments. [Figure 23] 1 is a flowchart illustrating an example of an operation performed by a network node, according to some embodiments. [Figure 24] 1 is a block diagram of a communication system according to some embodiments. [Figure 25] FIG. 2 is a block diagram of a user equipment according to some embodiments. [Figure 26] FIG. 2 is a block diagram of a network node according to some embodiments. [Figure 27] FIG. 2 is a block diagram of a host computer in communication with user equipment, according to some embodiments. [Figure 28] FIG. 1 is a block diagram of a virtualized environment, according to some embodiments. [Figure 29] FIG. 1 is a block diagram of a host computer that communicates with user equipment via a base station, in part, over a wireless connection, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0011] Some of the embodiments discussed herein will now be more fully described with reference to the accompanying drawings. The embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, and in which example embodiments of the inventive concepts are set forth. However, the inventive concepts may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It may be implicitly assumed that an element from one embodiment is present / used in another embodiment.

[0012] There are two types of NPN networks, described below: Standalone NPN ("SNPN") and Public Network Integrated-NPN ("PNI-NPN").

[0013] A first network or network identifier (e.g., a PLMN) can be configured to be equivalent to another network or network identifier. For example, an operator of one network may have an agreement with another operator that allows users of these networks to consider the networks equivalent. In current Third Generation Partnership Project ("3GPP") specifications, there are no equivalent NPN networks, but it should be possible to introduce the concept of an equivalent NPN in the future. In the case of a PNI-NPN, the concept of an equivalent PLMN ("EPLMN") is implicitly applied.

[0014] An SNPN is a type of NPN that consists of non-PLMN entities. For example, it may be a private company that deploys a network, but that company is not a PLMN / does not own a PLMN. It may be, for example, a company that owns a factory and deploys a network in and around the factory to serve its employees, machines, etc.

[0015] The entity that owns the SNPN does not necessarily own its own PLMN. An SNPN network has an identifier that includes a PLMN identity and a network identity ("NID"). As mentioned above, the entity that owns / manages the SNPN does not have to have its own PLMN identity. However, because the SNPN includes a PLMN, one way for the owner of the SNPN network to obtain an SNPN identifier is to enter into an agreement with the PLMN operator to be able to use that operator's PLMN. Another approach is for a "dummy" (e.g., "special," "not normally used," "invalid," or similar) PLMN to be used as part of the SNPN's identity.

[0016] A PNI-NPN mechanism is another type of NPN. Like an SNPN, a PNI-NPN may be deployed to serve a specific set of users, for example, the employees and machines of an enterprise. The main difference between an SNPN and a PNI-NPN is that the PNI-NPN is integrated into a PLMN. Thus, the PNI-NPN may be managed by the operator of the PLMN in which the PNI-NPN is integrated.

[0017] Instead of the NID identifier used by the SNPN, the PNI-NPN has an identifier called a Closed Access Group ("CAG"). A CAG is associated with each cell that forms the PNI-NPN. UEs such as company employees, machines, etc. that should be given access to the PNI-NPN are configured with the associated CAG. Other UEs do not have access to the PNI-NPN and are not configured to use the CAG. In the general case, both the UE and the network perform a check to determine whether the UE can connect to the PNI-NPN by examining whether the UE is configured with a CAG, and only if so, is the UE given access to the PNI-NPN.

[0018] The purpose of the initial context setup procedure is to establish the entire required initial UE context in the NG-RAN node, including protocol data unit ("PDU") session context, security keys, mobility restriction lists, UE radio capabilities, and UE security capabilities, as needed. The Access and Mobility Management Function ("AMF") can initiate the initial context setup procedure if a UE-associated logical NG connection exists for the UE, or if the AMF receives a RAN UE NGAP ID IE in the INITIAL UE MESSAGE, or if the NG-RAN node has already initiated a UE-associated logical NG connection by sending an INITIAL UE MESSAGE over another NG interface instance. The procedure can use UE-associated signaling as shown in Figure 2.

[0019] In the case of a signaling-only connection and if no UE Context Request IE is received in the initial UE message, the AMF may be configured to trigger the procedure for all NAS procedures or for each NAS procedure, depending on the operator's configuration.

[0020] For PDU session establishment, the 5GC must be ready to receive user data before the INITIAL CONTEXT SETUP RESPONSE message is received by the AMF. If a UE-associated logical NG connection does not exist, the UE-associated logical NG connection must be established upon reception of the INITIAL CONTEXT SETUP REQUEST message.

[0021] The INITIAL CONTEXT SETUP REQUEST message must include the Index to RAT / Frequency Selection Priority IE if available in the AMF.

[0022] If the NAS-PDU IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall pass it transparently towards the UE.

[0023] If the Masked IMEISV IE is included in the INITIAL CONTEXT SETUP REQUEST message, the target NG-RAN node shall use it, if supported, to determine the UE characteristics for further handling.

[0024] Upon receiving the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node attempts to perform the requested PDU session setup, stores the received UE aggregated maximum bit rate in the UE context, uses the received UE aggregated maximum bit rate for non-GBR QoS flows for the UE as specified in TS 23.501, stores the received mobility restriction list in the UE context, stores the received UE radio capabilities in the UE context, stores the received index to RAT / frequency selection priority in the UE context and uses it as specified in TS 23.501, stores the received UE security capabilities in the UE context, stores the received security key in the UE context and actually uses this security key if the NG-RAN node is requested to activate security for the UE, if supported, stores the received SRVCC operational in the UE context and uses it as specified in TS 23.216, if supported, stores the received NR V2X service authorization information in the UE context, if supported, stores the received LTE V2X service authorization information in the UE context, if supported, stores the received NR ... Store the UE sidelink aggregate maximum bit rate in the UE context and use it for the sidelink communication of the corresponding UE in network scheduled mode for NR V2X services, if supported, store the received LTE UE sidelink aggregate maximum bit rate in the UE context and use it for the sidelink communication of the corresponding UE in network scheduled mode for LTE V2X services, if supported, store the received PC5 QoS parameters in the UE context, TS23.287, if supported, store the received management-based MDT PLMN list information in the UE context, if supported, store the received IAB authorization information in the UE context, if supported, store the received 5G ProSe authorization information in the UE context and use it for sidelink communications for the UE in network-scheduled mode for 5G ProSe services, if supported, store the 5G ProSe UE PC5 aggregate maximum bit rate in the UE context and use it for sidelink communications for the UE in network-scheduled mode for 5G ProSe services, if supported, store the 5G ProSe PC5 QoS parameters in the UE context and use it as specified in TS 23.304.

[0025] If the Mobility Restriction List IE is not included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall consider that no roaming and access restrictions apply to the UE. The NG-RAN node shall also consider that no roaming and access restrictions apply to the UE when one of the QoS flows contains a specific ARP value (TS23.501).

[0026] If the Trace Activation IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, initiate the requested trace functionality as described in TS32.422. In particular, if supported, the NG-RAN node shall initiate the requested trace and MDT sessions as described in TS32.422 if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", and shall initiate the requested MDT session as described in TS32.422 if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", "Recorded MDT Only", the NG-RAN node shall ignore the Interface to Trace IE and the Trace Depth IE, and if the Trace Activation IE includes the MDT Location Information IE in the MDT Configuration IE, it shall store this information and take it into account in the requested MDT session, and if the Trace Activation IE includes the MDT Location Information IE in the MDT Configuration IE, it shall initiate the requested MDT session. If it contains the PLMN List IE, the NG-RAN node may use it to propagate the MDT configuration as described in TS37.320; if the Trace Activation IE contains a Bluetooth Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains a WLAN Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains a Sensor Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains an MDT Configuration IE and the NG-RAN node is a gNB, at least the MDT Configuration-NR IE shall be present, but if the NG-RAN node is an ng-eNB, the MDT Configuration-EUTRA IE shall be present.

[0027] Handover resource allocation is described below.

[0028] The purpose of the handover resource allocation procedure is to reserve resources at the target NG-RAN node for the handover of the UE. The procedure may use UE-related signaling as shown in Figure 3.

[0029] The AMF initiates the procedure by sending a HANDOVER REQUEST message to the target NG-RAN node.

[0030] If the Trace Activation IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, initiate the requested trace functionality as described in TS32.422. In particular, if supported, the NG-RAN node shall initiate the requested trace and MDT sessions as described in TS32.422 if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", and shall initiate the requested MDT sessions as described in TS32.422 if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", "Recorded MDT Only", the target NG-RAN node shall ignore the Interface to Trace IE and the Trace Depth IE, and if the Trace Activation IE includes the MDT Location Information IE in the MDT Configuration IE, it shall store this information and take it into account in the requested MDT session, and if the Trace Activation IE includes the MDT Location Information IE in the MDT Configuration IE, it shall initiate the requested MDT session. If it contains the PLMN List IE, the NG-RAN node may use it to propagate the MDT configuration as described in TS37.320; if the Trace Activation IE contains a Bluetooth Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains a WLAN Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains a Sensor Measurement Configuration IE within the MDT Configuration IE, it shall take it into account for the MDT configuration as described in TS37.320; if the Trace Activation IE contains an MDT Configuration IE and the NG-RAN node is a gNB, at least the MDT Configuration-NR IE shall be present, but if the NG-RAN node is an ng-eNB, the MDT Configuration-EUTRA IE shall be present.

[0031] If the Location Report Request Type IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall perform the requested location reporting functions for the UE as described in subclause 8.12.

[0032] The purpose of the trace initiation procedure is to allow the AMF to request an NG-RAN node to initiate a trace session for the UE. The procedure uses UE-associated signaling as shown in Figure 4. If a UE-associated logical NG connection does not exist, one must be established as part of the procedure.

[0033] The AMF initiates the procedure by sending a TRACE START message. Upon receiving the TRACE START message, the NG-RAN node shall initiate the requested trace session as described in TS32.422.

[0034] If a Trace Activation IE with the MDT Activation IE set to "Immediate MDT and Trace" is included in the TRACE START message, the NG-RAN node shall initiate the requested Trace and MDT sessions as described in TS32.422, if supported.

[0035] If a Trace Activation IE with MDT Activation IE set to "Immediate MDT only" or "Recorded MDT only" is included in the TRACE START message, the NG-RAN node shall initiate the requested MDT session as described in TS32.422, if supported, and the NG-RAN node shall ignore the Interface to Trace IE and the Trace Depth IE.

[0036] If the Trace Activation IE includes an MDT Location Information IE within the MDT Configuration IE, the NG-RAN node shall store this information and take it into account within the requested MDT session, if supported.

[0037] If a Trace Activation IE with MDT Activation IE set to "Immediate MDT only", "Recorded MDT only" is included in the TRACE START message, and if a Signaling-based MDT PLMN List IE is included in the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT configuration as described in TS37.320.

[0038] If the Trace Activation IE contains a Bluetooth Measurement Configuration Information IE within the MDT Configuration IE, the NG-RAN node shall take it into account for MDT configuration as described in TS37.320, if supported.

[0039] If the Trace Activation IE contains a WLAN Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall take it into account for the MDT configuration as described in TS37.320, if supported.

[0040] If the Trace Activation IE includes a Sensor Measurement Configuration Information IE within the MDT Configuration IE, the NG-RAN node shall take it into account for MDT configuration as described in TS37.320, if supported.

[0041] If the trace activation IE includes the MDT configuration IE and the NG-RAN node is a gNB, at least the MDT configuration-NR IE must be present, but if the NG-RAN node is an ng-eNB, the MDT configuration-EUTRA IE must be present.

[0042] FIG. 5 shows an example of a trace activation IE that specifies parameters related to trace session activation.

[0043] FIG. 6 shows an example of an MDT configuration IE that defines MDT configuration parameters.

[0044] Figure 7 shows an example of an MDT PLMN List IE that provides a list of allowed PLMNs for an MDT. Figure 8 shows an example of range boundaries for the MDT PLMN List IE.

[0045] FIG. 9 shows an example of an MDT configuration-NR IE that specifies MDT configuration parameters for NR.

[0046] FIG. 10 shows an example of a range boundary of the MDT configuration-NR IE.

[0047] Fig. 11 shows an example of the area range of a neighboring cell IE that specifies the area range of a neighboring cell for Recorded MDT. Fig. 12 shows an example of the range boundary of the area range of a neighboring cell IE.

[0048] Currently, certain challenges exist. In some instances, problems have been identified with the flexibility of existing solutions in MDT configuration collection with respect to the range of MDT measurements that only support MDT configuration collection in public networks.

[0049] Furthermore, a UE may have access to and subscriptions to several networks or different network types (e.g., SNPN, PNI-NPN, and PLMN). Also, if the UE is capable of a service that requires a specific subscription for registration, the UE may perform registration to a private network (e.g., SNPN). Generally, a UE successfully registers to a private network (e.g., SNPN) if (1) it finds a suitable cell of the SNPN to camp on and (2) registration from the UE is accepted within the registration area of ​​the cell on which the UE is camped. Currently, there is no support for MDT configuration for private networks in the technical specifications. This means that the RAN cannot know whether MDT measurements collected by the UE can also be collected on an NPN network. This may cause several problems, such as (1) lack of continuity of MDT measurements when the UE moves from a PLMN to an NPN and vice versa, and (2) lack of MDT measurement collection when the UE attaches to and moves RRC_Connected in an NPN.

[0050] The above problems also mean that network operators of private networks cannot collect MDT-related information via UEs connected to / moving through other networks. Such UEs can provide measurements on the operator's PLMN cells as seen by UEs served by neighboring NPN cells. Such measurements are beneficial as they allow for optimization of coverage and performance within the PLMN.

[0051] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these and other problems. In some embodiments, a first network node (e.g., an AMF / OAM of a network) may send an MDT configuration to a RAN node, the MDT configuration including an area scope that identifies at least one of the following networks: (1) a PNI-NPN identity; (2) an identity associated with an SNPN; (3) an identity that may include at least a list of NPN PLMN, CAG ID, and NID ID; and (4) an identity associated with a public network (PLMN).

[0052] In some examples where the MDT configuration generated by the first network node includes a region scope spanning across a PN network and an NPN network, the first network node (eg, AMF / OAM) performs the operation.

[0053] In some examples, the operations include configuring, for a particular UE registered in a first network (NPN) and moving between the first network coverage and the second network coverage, respective MDT measurement configurations for second network nodes operating within the NPN, i.e., PNI-NPN and / or SNPN.

[0054] In a further or alternative example, the operations include configuring, for a particular UE registered in a second network (PN) and moving between the first network coverage and the second network coverage, respective MDT measurement configurations for third network nodes operating in other PLMNs associated with the PN.

[0055] In a further or alternative example, the operations include configuring respective MDT measurement configurations for second network nodes operating within the NPN, i.e., PNI-NPN and / or SNPN, for a particular UE registered within the second network (PN) and moving between the first network coverage and the second network coverage.

[0056] In a further or alternative example, the operations include configuring, for a particular UE registered in the first network (NPN) and moving between the first network coverage and the second network coverage, respective MDT measurement configurations for third network nodes operating in other PLMNs associated with the PN.

[0057] An embodiment for the UE in a DC scenario is described below.

[0058] In some examples, the operations include configuring respective MDT measurements for a second network node operating in the PNI-NPN or SNPN as a secondary node (SN) and a third network node as a master node (MN) as a dual connectivity configuration for a particular UE registered in both (first and second) networks.

[0059] In an additional or alternative example, the operations include configuring, for a particular UE registered in both (first and second) networks, respective MDT measurements for a third network node operating in another PLMN associated with the PN as a master node (MN) and the second network node as an SN as a dual connectivity configuration.

[0060] In some embodiments, the area scope for the MDT configuration is extended by including support for different network types: the associated NPN identifier may be included in the area scope for the MDT configuration.

[0061] As used herein, the terms Non-Public Network / Private Network (“NPN”) and Standalone NPN (“SNPN”) / Public Network Integrated NPN (“PNI-NPN”) node are used interchangeably. In some examples, a PNI-NPN network as used herein covers scenarios when a cell advertises a Public Local Mobile Network (“PLMN”)+Closed Access Group (“CAG”) in its NPN identity information in System Information Block 1 (“SIB1”).

[0062] An SNPN network in this specification covers the scenario when a cell publishes a PLMN+Network Identity ("NID") in the NPN identity in SIB1.

[0063] In the case of managed-based minimization of driving tests ("MDT"), the core network ("CN") indicates to a radio access network ("RAN") node whether MDT can be configured by the RAN node for each connected UE by providing the RAN node with a managed-based MDT PLMN list for each user equipment ("UE") (also referred to herein as a communication device).

[0064] In the case of signaling-based MDT, the CN indicates to the RAN node whether MDT can be configured by the RAN node for each connected UE by providing the RAN node with a signaling-based MDT PLMN list for each UE.

[0065] In the case of existing technical specifications, only the signaling-based MDT PLMN list is propagated during intra-PLMN handover and intra-PLMN UE context lookup.

[0066] In some embodiments, a list of network identities, including PN identities and / or NPN identities, constituting the area range within which MDT configuration (management-based or signaling-based) can be configured in the UE, is signaled from the source to the target during intra-PLMN and inter-PLMN movement, intra-system and inter-system movement (e.g., for a UE moving from a PLMN to an SNPN), and during intra-network UE context lookup.

[0067] In a further or alternative embodiment, the operation is performed by a first network node (e.g., a network Access and Mobility Management Function (“AMF”) / Operations, Administration, and Maintenance (“OAM”)) sending an MDT configuration to a RAN node, the MDT configuration including an area scope identifying at least one network. The information includes one or more of the following: (1) an identity of a PNI-NPN (public network integrated NPN), (2) an identity associated with an SNPN (standalone NPN), (3) an identity that may include at least a list of NPN PLMN, CAG ID, and NID ID, and (4) an identity associated with a public network (PLMN).

[0068] Cross-network type configuration is described below: In some embodiments, operations are performed at a first network node operating in one network to configure respective measurements and reports for a second network node (e.g., a private network / NPN for UEs registered only in the first network).

[0069] FIG. 13 shows an example of a UE entering and leaving the second network (shaded area).

[0070] FIG. 14 shows an example of a UE moving within a second network (shaded).

[0071] In some embodiments, the first node advertises an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the PNI-NPN with a respective MDT measurement configuration to be collected also from cells belonging to a second network node in the public network.

[0072] In a further or alternative embodiment, the first node advertises an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the PNI-NPN with a respective MDT measurement configuration to be collected also from cells belonging to a second network node in the SNPN.

[0073] In a further or alternative embodiment, the first node advertises an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the PNI-NPN with a respective MDT measurement configuration to be collected also from cells belonging to second network nodes in other PNI-NPNs.

[0074] In a further or alternative embodiment, the first node advertises an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the SNPN with a respective MDT measurement configuration to be collected exclusively by or additionally from cells belonging to a second network node in the PNI-NPN.

[0075] In a further or alternative embodiment, the first node advertises an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the SNPN with a respective MDT measurement configuration to be collected exclusively by or additionally from cells belonging to a second network node in another SNPN.

[0076] In a further or alternative embodiment, the first node is adapted to advertise an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the SNPN with a respective MDT measurement configuration to be collected exclusively by or additionally from cells belonging to a second network node in the public network.

[0077] In a further or alternative embodiment, the first node is adapted to advertise an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the public network with a respective MDT measurement configuration to be collected exclusively by or additionally from a cell belonging to a second network node in the PNI-NPN.

[0078] In a further or alternative embodiment, the first node is adapted to advertise an MDT configuration for either signaling-based or management-based MDT to enable the RAN node to configure at least one UE served by a cell in the public network with a respective MDT measurement configuration to be collected exclusively by or additionally from cells belonging to a second network node in the SNPN.

[0079] In additional or alternative embodiments, the first network node may be one of the following: a CN node in a public network, an OAM in a public network, a CN node in an SNPN, and an OAM in an SNPN.

[0080] In additional or alternative embodiments, if the MDT configuration is for immediate MDT, the UE collects and immediately reports the MDT measurements to the serving network, which can forward the measurements to a system that analyzes the measurements (e.g., an OAM system).

[0081] In additional or alternative embodiments, if the MDT configuration is for Recorded MDT, the UE records MDT measurements and reports the MDT measurements to the serving network at the Recorded Report time, which can forward the measurements to a system that analyzes the measurements (e.g., an OAM system).

[0082] In additional or alternative embodiments, the entity receiving the MDT measurements collected by the UE and signaled by the serving RAN may be the OAM of the operator managing the public network or the OAM of the operator managing the private network.

[0083] An example implementation is described below.

[0084] In some embodiments, if the serving cell associated with the private network (e.g., SNPN) and PNI-NPN is part of the MDT configuration-NR, the CN requests the network node to configure the particular UE with MDT measurement related information. An example implementation is given in Figures 15-16.

[0085] FIG. 15 shows an example of an MDT configuration-NR IE that specifies MDT configuration parameters for NR.

[0086] FIG. 16 shows an example of a range boundary for the MDT configuration-NR IE.

[0087] In additional or alternative embodiments, the CN requests the network node to configure the particular UE with MDT measurement related information: a list of PLMNs and NPNs for signaling-based MDT. An example implementation is given in Figures 17-18.

[0088] FIG. 17 shows an example of an MDT PLMN List IE that provides a list of allowed PLMN identities for an MDT.

[0089] FIG. 18 shows an example of range boundaries for an MDT PLMN list.

[0090] In additional or alternative embodiments, for signaling-based MDT, Figures 19-20 show example implementations to be optionally added to the following messages: INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or PATH SWITCH REQUEST ACKNOWLEDGE.

[0091] FIG. 19 shows an example of an MDT NPN List IE that provides a list of authorized NPN identities for an MDT.

[0092] FIG. 20 shows an example of range boundaries for an MDT NPN list.

[0093] In an additional or alternative embodiment, an alternative implementation for signaling-based MDT is to add a flag indicating that the neighboring NR physical cell ID belongs to an NPN network, as shown in FIG. 21.

[0094] An implementation in an NPN setting is described below.

[0095] In some embodiments, the operations are performed in a first network node operating within a private network / NPN to configure respective MDT configurations for a second network node that is in the same network as the first network node.

[0096] In additional or alternative embodiments, the CN in the SNPN signals a trace-based message for a particular UE to enable the RAN node to configure at least one UE served by a cell in the SNPN with a respective MDT measurement configuration for cells belonging to the same SNPN.

[0097] In a further or alternative embodiment, the CN in the PNI-NPN signals a trace-based message for a particular UE to enable the RAN node to configure at least one UE served by a cell in the PNI-NPN with a respective MDT measurement configuration for cells belonging to the same PNI-NPN.

[0098] In some examples, the CN requests the network node to configure a particular UE with MDT measurement related information: whether the serving cell (in this context the last suitable cell) associated with the private network, i.e., the SNPN and PNI-NPN, is part of the MDT configuration - NR. An example implementation is shown in Figure 22.

[0099] FIG. 22 shows an example of adding or replacing an MDT Configuration-NR IE that specifies MDT configuration parameters for NR.

[0100] The dual network connectivity configuration is described below.

[0101] In some embodiments, operations performed in dual connectivity (“DC”) are those operating in a first network as a master node (“MN”) and a second network as a secondary node (“SN”) for a particular UE. The UE is performing registration in both (first and second) networks. In MR DC scenarios, the UE may be in (a) a cell operating in the public network as an MN and a cell operating in the PNI-NPN as an SN, and vice versa; (b) a cell operating in the public network as an MN and a cell operating in the SNPN as an SN, and vice versa; and (c) a cell operating in the SNPN as an MN and a cell operating in the PNI-NPN as an SN, and vice versa.

[0102] In additional or alternative embodiments, the first network provides an MDT configuration for both the MN and the SN via the MN, and the MN then forwards the MDT configuration to the SN.

[0103] In additional or alternative embodiments, the second network provides an MDT configuration for both the MN and the SN via the SN, which then forwards the MDT configuration to the MN.

[0104] In additional or alternative embodiments, the second network forwards the associated MDT configuration to the first network and requests the MDT-related configuration from the first network.

[0105] In additional or alternative embodiments, when the first network receives the measurement results, the first network forwards the associated measurement results to the second network (if the measurement results corresponding to each network are not reported separately).

[0106] In additional or alternative embodiments, when the second network receives the measurement results, the first network forwards the associated measurement results to the first network (if the measurement results corresponding to each network are not reported separately).

[0107] In the following description, network node 2600 will be used to describe the functionality of a network node's operation, although the network node may be any of hub 2414, network nodes 2410A-B, core network node 2408, network node 2600, virtualization hardware 2804, virtual machines 2808A, 2808B, or network node 2904. Operation of network node 2600 (implemented using the block diagram structure of FIG. 26) will now be described with reference to the flowchart of FIG. 23 in accordance with some embodiments of the inventive concept. For example, modules may be stored in memory 2604 of FIG. 26 that provide instructions such that, when the modules' instructions are executed by respective network node processing circuitry 2602, the processing circuitry 2602 performs the respective operations of the flowchart.

[0108] FIG. 23 shows operations performed by a network node.

[0109] At block 2310, the processing circuit 2602 determines an MDT configuration including an area range. In some examples, the network node is a core network (“CN”) node, and determining the MDT configuration includes sending the MDT configuration to a radio access network (“RAN”) node. In other examples, the network node is a RAN node, and determining the MDT configuration includes receiving the MDT configuration from a second network node. The second network node may include at least one of a CN node in a PLMN, an OAM in a PLMN, a CN node in a SNPN, and an OAM in a SNPN.

[0110] In some embodiments, the area range identifies at least one of a PNI-NPN identity, an SNPN identity, and a PLMN identity. In some examples, the PNI-NPN identity includes a CAG. In additional or alternative examples, the SNPN identity includes an NID.

[0111] At block 2320, the processing circuit 2602 configures the communication device served by the first cell to collect MDT measurements from the second cell. In some embodiments, the first cell is associated with a first communication network and the second cell is associated with a second communication network. In some examples, the first communication network is an NPN and the second communication network includes at least one of a PLMN, an SNPN, and a PNI-NPN. In other examples, the first communication network is a public network and the second communication network includes at least one of an SNPN and a PNI-NPN.

[0112] In additional or alternative embodiments, the MDT configuration includes an indication that the communications device will report collected MDT measurements as the measurements are collected.

[0113] In additional or alternative embodiments, the MDT configuration includes an indication that the communications device is to record collected MDT measurements as the MDT measurements are collected.

[0114] In a further or alternative embodiment, configuring the communications device includes sending the MDT configuration as part of at least one of an initial context setup request, a handover request, and a path switch request acknowledgement.

[0115] In additional or alternative embodiments, the communication device is operating in dual connectivity. Configuring the communication device includes transmitting an MDT configuration for both a master node (MN) and a secondary node (SN) to at least one of the MN and the SN. In some examples, the first cell is operating in a public network as an MN, and the second cell is operating in an NPN as an SN. In additional or alternative examples, the first cell is operating in an SNPN as an MN, and the second cell is operating in a PNI-NPN as an SN.

[0116] At block 2330, the processing circuit 2602 receives the MDT measurements via the communication interface 2606. In some embodiments, the MDT measurements are received from a communication device. In additional or alternative embodiments, the MDT measurements are received from a second communication device.

[0117] At block 2340, the processing circuit 2602 transmits the MDT measurements via the communication interface 2606. In some embodiments, the MDT measurements are transmitted to a second communication network.

[0118] Various operations shown in FIG. 23 may be optional for some embodiments.

[0119] FIG. 24 illustrates an example of a communication system 2400, according to some embodiments.

[0120] In this example, the communications system 2400 includes a communications network 2402 including an access network 2404, such as a radio access network (RAN), and a core network 2406 including one or more core network nodes 2408. The access network 2404 includes one or more access network nodes, such as network nodes 2410a and 2410b (one or more of which may be collectively referred to as network node 2410), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP access point. Moreover, as will be understood by those skilled in the art, the network node 2410 is not necessarily limited to an implementation in which the radio portion and the band portion are supplied and integrated by a single vendor. That is, it will be understood that the network node 2410 may include disjoint implementations or portions thereof. For example, in some embodiments, the communications network 2402 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node within the communications network 2402 that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate alone or in conjunction with other nodes to implement one or more functions of any node within the communications network 2402, including one or more network nodes 2410 and / or core network node 2408.

[0121] Examples of ORAN network nodes 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-in such as a near-real-time RAN control application (e.g., xApp) or a non-real-time RAN automation application (e.g., rApp), or any combination thereof (the adjective "open" designates support for the ORAN specification). A network node can support the specification by supporting interfaces defined by the ORAN specification, such as, for example, the A1, F1, W1, E1, E2, X2, Xn interfaces, an open fronthaul user plane interface, or an open fronthaul management plane interface. The intent and content-aware notifications described herein may be communicated from a 3GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and / or ORAN Alliance-defined interfaces (e.g., A1, O1). Moreover, an ORAN network node may be a logical node within a physical node. Furthermore, an ORAN network node may be implemented within a virtualized environment (described further below) in which one or more network functions are virtualized. For example, the virtualized environment may include an O-Cloud Computing Platform orchestrated by a service management and orchestration framework over an O-2 interface defined by the O-RAN Alliance. The network node 2410 facilitates direct or indirect connectivity of user equipment (UE), such as by connecting wireless devices 2412a, 2412b, 2412c, and 2412d (one or more of which may be collectively referred to as UE 2412) to the core network 2406 over one or more wireless connections.The network node 2410 facilitates direct or indirect connectivity of user equipment (UE), such as by connecting UEs 2412a, 2412b, 2412c, and 2412d (one or more of which may be collectively referred to as UEs 2412) to the core network 2406 over one or more wireless connections.

[0122] Exemplary wireless communication over a wireless connection includes sending 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, communication system 2400 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or be involved in the communication of data and / or signals, whether via wired or wireless connections. Communication system 2400 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

[0123] The UE 2412 may be any of a wide variety of communications devices, including a wireless device that is positioned, configured, and / or operative to communicate wirelessly with the network node 2410 and other communications devices. Similarly, the network node 2410 is positioned, enabled, configured, and / or operative to communicate directly or indirectly with the UE 2412 and / or other network nodes or equipment within the communications network 2402 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management, within the communications network 2402.

[0124] In the depicted example, the core network 2406 connects the network node 2410 to one or more hosts, such as the host 2416. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 2406 includes one or more core network nodes (e.g., the core network node 2408) constructed of 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, and therefore those descriptions are generally applicable to the corresponding components of the core network node 2408. Exemplary core network nodes include one or more of the following functions: a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0125] The host 2416 may be owned or under the control of, and may be operated by or on behalf of, a service provider other than the operator or provider of the access network 2404 and / or the communication network 2402. The host 2416 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and storing data about various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or optionally interacting with remote devices, functions for an alarm and monitoring center, or any other such function performed by a server.

[0126] 24 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate in accordance with predefined rules or procedures, such as a particular standard, including, but 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 standard, or any available next-generation standard (e.g., 6G), a wireless local area network (WLAN) standard such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communications (NFC), ZigBee, LiFi, and / or any low-power wide area network (LPWAN) standard such as LoRa and Sigfox.

[0127] In some examples, communication network 2402 is a cellular network that implements 3GPP standardized features. Thus, communication network 2402 can support network slicing to provide different logical networks to different devices connected to communication network 2402. For example, communication network 2402 can provide Ultra-Reliable Low-Latency Communications (URLLC) services to some UEs while providing enhanced Mobile Broadband (eMBB) services to other UEs and / or massive machine-based communications (mMTC) / massive IoT services to still further UEs.

[0128] In some examples, the UE 2412 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 2404 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 2404. Furthermore, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may operate in any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0129] In this example, the hub 2414 communicates with the access network 2404 to facilitate indirect communication between one or more UEs (e.g., UEs 2412c and / or 2412d) and a network node (e.g., network node 2410b). In some examples, the hub 2414 may be a controller, a router, a content source, analytics, or any of the other communication devices described herein with respect to UEs. For example, the hub 2414 may be a broadband router that enables access to the core network 2406 for the UE. As another example, the hub 2414 may be a controller that sends commands or instructions to one or more actuators within the UE. The commands or instructions may be received from the UE, the network node 2410, or by executable code, scripts, processes, or other instructions within the hub 2414. As another example, the hub 2414 may be a data collector that serves as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 2414 may be a content source. For example, in the case of a UE that is a VR headset, display, loudspeaker, or other media distribution device, the hub 2414 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2414 then provides to the UE either immediately, after performing local processing, and / or after adding further local content. In yet another example, the hub 2414 acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low energy IoT devices.

[0130] The hub 2414 may have a constant / permanent connection or an intermittent connection to the network node 2410b. The hub 2414 may also enable different communication schemes and / or schedules between the hub 2414 and the UEs (e.g., UEs 2412c and / or 2412d) and between the hub 2414 and the core network 2406. In other examples, the hub 2414 is connected to the core network 2406 and / or one or more UEs via a wired connection. Moreover, the hub 2414 may be configured to connect to an M2M service provider over the access network 2404 and / or to another UE over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 2410 while still connected through the hub 2414 via a wired or wireless connection. In some embodiments, the hub 2414 may be a dedicated hub, i.e., a hub whose primary function is to route communications from UEs to / from the network node 2410b. In other embodiments, the hub 2414 may be a non-dedicated hub, i.e., a device that is capable of operating to route communications between the UE and the network node 2410b, but that is also capable of operating as a communication initiation point and / or communication termination point for a particular data channel.

[0131] Figure 25 illustrates a UE 2500 according to some embodiments. As used herein, a UE refers to a device capable of, set up, configured, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a voice-over-IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a game console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), a vehicle-mounted or vehicle-embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrowband Internet of Things (NB-IoT) UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0132] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but that may not be associated with or initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but that may be associated with or operate for the user's benefit.

[0133] The UE 2500 includes a processing circuit 2502 operatively coupled to an input / output interface 2506, a power source 2508, a memory 2510, a communication interface 2512, and / or any other components, or any combination thereof, via a bus 2504. A particular UE may utilize all or a subset of the components illustrated in FIG. 25. The level of integration between components may vary from UE to UE. Furthermore, a particular UE may incorporate multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0134] The processing circuit 2502 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in the memory 2510. The processing circuit 2502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), programmable logic together with appropriate firmware, one or more stored computer programs such as a microprocessor or digital signal processor (DSP) together with appropriate software, a general-purpose processor, or any combination of the above. For example, the processing circuit 2502 may include multiple central processing units (CPUs).

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

[0136] In some embodiments, the power source 2508 is constructed as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power source 2508 may further include power circuitry for delivering power to various parts of the UE 2500 from the power source 2508 itself and / or from an external power source via an interface, such as an input circuit or a power cable. Delivering power may, for example, be for charging the power source 2508. The power circuitry may perform any formatting, conversion, or other modification of the power from the power source 2508 to make it suitable for each component of the UE 2500 being powered.

[0137] The memory 2510 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 disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, the memory 2510 includes one or more application programs 2514, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 2516. The memory 2510 can store any of a wide variety of operating systems or combinations of operating systems for use by the UE 2500.

[0138] The memory 2510 may be configured to include several physical drive units such as a 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, smart card memory such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs) such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card." The memory 2510 may enable the UE 2500 to access, offload, or upload data, instructions, application programs, etc. stored on a temporary or non-transitory memory medium. An article of manufacture, such as one utilizing a communications system, may be tangibly embodied as or in memory 2510, which may be or comprise a device-readable storage medium.

[0139] The processing circuit 2502 may be configured to communicate with an access network or other networks using a communication interface 2512. The communication interface 2512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2522. The communication interface 2512 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 the access network). Each transceiver may include a transmitter 2518 and / or a receiver 2520 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter 2518 and receiver 2520 may be coupled to one or more antennas (e.g., antenna 2522) and may share circuit components, software, or firmware or be implemented separately.

[0140] In the illustrated embodiment, the communication capabilities of communication interface 2512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, close-range communication, location-based communication such as use of a Global Positioning System (GPS) to determine location, another similar communication capability, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards such as IEEE 802.11, Code Division Multiple 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), etc.

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

[0142] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. The actuator, motor, or switch may change state in response to the received wireless input. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0143] When in the form of an Internet of Things (IoT) device, the UE may be a device for use in one or more application areas, including, but not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are integrated into a connected refrigerator or freezer, a TV, a connected lighting device, an energy meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a water inundation / humidity sensor, an electronic door lock, a connected doorbell, an air conditioning system such as 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 haptic augmentation or sensory augmentation, a water sprinkler, an animal or product tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device comprises, in addition to the other components described with respect to UE 2500 shown in FIG. 25, circuitry and / or software depending on the intended application of the IoT device.

[0144] As yet another particular example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another UE and / or network node. The UE, in this case, may be an M2M device, which may be referred to as an MTC device in the 3GPP context. 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, bus, truck, ship, and airplane, or other equipment capable of monitoring and / or reporting on its operating state or other functionality associated with its operation.

[0145] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated within 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 a user makes changes from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the functions described above. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0146] 26 illustrates a network node 2600 according to some embodiments. As used herein, a network node refers to a device that is capable of, set up, configured, and / or operable to communicate directly or indirectly with UEs and / or other network nodes or devices in a communications network. Examples of a network node include, but are not limited to, an access point (AP) (e.g., a wireless access point), a base station (BS) (e.g., a radio base station, a Node B, an evolved Node B (eNB), an NR Node B (gNB)), an O-RAN node or a component of an O-RAN node (e.g., an intelligent controller, an O-RU, an O-DU, an O-CU).

[0147] Base stations may be classified based on the amount of coverage they provide (or, stated another way, their transmit power level) and may therefore be referred to as femto, pico, micro, or macro base stations depending on the amount of coverage provided. A base station may also be a relay node or relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna, as in an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0148] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization of driving test (MDT).

[0149] The network node 2600 includes a processing circuit 2602, a memory 2604, a communication interface 2606, and a power source 2608. The network node 2600 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 2600 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may, in some instances, be considered a single separate network node. In some embodiments, the network node 2600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 2604 for different RATs) and some components may be reused (e.g., the same antenna 2610 may be shared by different RATs). Network node 2600 may also include multiple sets of the various illustrated components for different wireless technologies, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies, integrated into network node 2600. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node 2600.

[0150] The processing circuit 2602 may comprise one or more combinations 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 coded logic operable, alone or in conjunction with other network node 2600 components, such as memory 2604, to provide the functionality of the network node 2600.

[0151] In some embodiments, the processing circuit 2602 comprises a system on a chip (SOC). In some embodiments, the processing circuit 2602 includes one or more of a radio frequency (RF) transceiver circuit 2612 and a baseband processing circuit 2614. In some embodiments, the radio frequency (RF) transceiver circuit 2612 and the baseband processing circuit 2614 may be on separate chips (or sets of chips), boards, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 2612 and the baseband processing circuit 2614 may be on the same chip or set of chips, board, or unit.

[0152] Memory 2604 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuit 2602. Memory 2604 can store any suitable instructions, data, or information, including computer programs, software, applications that include one or more of logic, rules, code, tables, and / or other instructions that can be executed by processing circuit 2602 and utilized by network node 2600. Memory 2604 may be used to store any calculations performed by processing circuit 2602 and / or any data received via communications interface 2606. In some embodiments, the processing circuit 2602 and the memory 2604 are integrated.

[0153] The communications interface 2606 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As illustrated, the communications interface 2606 includes a port / terminal 2616, for example, for transmitting and receiving data to and from a network via a wired connection. The communications interface 2606 also includes radio front-end circuitry 2618, which is coupled to an antenna 2610 or, in particular embodiments, may be part of the antenna 2610. The radio front-end circuitry 2618 includes a filter 2620 and an amplifier 2622. The radio front-end circuitry 2618 may be connected to the antenna 2610 and the processing circuit 2602. The radio front-end circuitry may be configured to condition signals communicated between the antenna 2610 and the processing circuit 2602. The radio front-end circuitry 2618 may receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuitry 2618 may convert the digital data into radio signals having appropriate channel and bandwidth parameters using a combination of filters 2620 and / or amplifiers 2622. The radio signals may then be transmitted via the antenna 2610. Similarly, when receiving data, the antenna 2610 may collect the radio signals, which are then converted into digital data by the radio front-end circuitry 2618. The digital data may be passed to the processing circuitry 2602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0154] In certain alternative embodiments, network node 2600 does not include a separate radio front-end circuit 2618; instead, processing circuit 2602 includes the radio front-end circuitry and is connected to antenna 2610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2612 is part of communication interface 2606. In still other embodiments, communication interface 2606 includes one or more ports or terminals 2616, radio front-end circuitry 2618, and RF transceiver circuitry 2612 as part of a radio unit (not shown), and communication interface 2606 communicates with baseband processing circuitry 2614 that is part of a digital unit (not shown).

[0155] The antenna 2610 may include one or more antennas or an antenna array configured to transmit and / or receive wireless signals. The antenna 2610 may be coupled to radio front-end circuitry 2618 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In particular embodiments, the antenna 2610 may be separate from the network node 2600 and connectable to the network node 2600 via an interface or port.

[0156] The antenna 2610, the communication interface 2606, and / or the processing circuit 2602 may be configured to perform any receiving operations and / or certain acquisition operations described herein as being performed by a 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 2610, the communication interface 2606, and / or the processing circuit 2602 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0157] The power supply 2608 provides power to the various components of the network node 2600 in a form appropriate for each component (e.g., at the voltage and current levels required for each component). The power supply 2608 may further comprise or be coupled to power management circuitry to provide power to the components of the network node 2600 for performing the functions described herein. For example, the network node 2600 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an interface such as an input circuit or an electrical cable, whereby the external power source provides power to the power circuitry of the power supply 2608. As a further example, the power supply 2608 may comprise a power source in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0158] 26 to provide particular 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, network node 2600 may include user interface devices to enable input of information into network node 2600 and output of information from network node 2600. This may enable a user to perform diagnostic, maintenance, repair, and other management functions on network node 2600.

[0159] 27 is a block diagram of a host 2700, which may be an embodiment of the host 2416 of FIG. 24, in accordance with various aspects described herein. As used herein, the host 2700 may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The host 2700 may provide one or more services to one or more UEs.

[0160] Host 2700 includes a processing circuit 2702 operably coupled via bus 2704 to an input / output interface 2706, a network interface 2708, a power supply 2710, and memory 2712. In other embodiments, other components may be included. Features of these components may be substantially similar to features described with respect to the devices of previous figures, such as Figures 25 and 26, and therefore those descriptions are generally applicable to the corresponding components of host 2700.

[0161] The memory 2712 may include one or more computer programs, including one or more host application programs 2714 and data 2716, which may include user data, e.g., data generated by a UE for the host 2700 or data generated by the host 2700 for the UE. An embodiment of the host 2700 may utilize only a subset or all of the illustrated components. The host application programs 2714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), 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 program 2714 may also provide user authentication and licensing checks and may periodically report health, route, and content availability to a central node, such as a device in or on the edge of the core network. Thus, the host 2700 may select and / or direct different hosts for over-the-top services for the UE. The host application program 2714 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0162] FIG. 28 is a block diagram illustrating a virtualization environment 2800 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization, as used herein, may apply to any device described herein, or components thereof, and relates to implementations in which at least a portion of functionality is implemented therein as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented within one or more virtualization environments 2800 hosted by one or more hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which the virtualized node does not require wireless connectivity (e.g., to a core network node or host), the node may be fully virtualized. In some embodiments, the virtualization environment 2800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a service management and orchestration framework over an O-2 interface.

[0163] An application 2802 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) executes within the virtualized environment Q400 to achieve some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0164] The hardware 2804 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software is executed by the processing circuitry to instantiate one or more virtualization layers 2806 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 2808a and 2808b (one or more of which may be collectively referred to as VMs 2808), and / or perform any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 2806 can present a virtual operating platform that looks like networking hardware to the VMs 2808.

[0165] The VMs 2808 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage and may be executed by a corresponding virtualization layer 2806. Different embodiments of instances of virtual appliances 2802 may be implemented in one or more of the VMs 2808, and the implementation may be done in different ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to aggregate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0166] In the context of NFV, a VM 2808 may be a software implementation of a physical machine that executes programs as if they were running on a physical, non-virtualized machine. Each VM 2808, and the portion of hardware 2804 on which it runs, whether hardware dedicated to that VM and / or hardware shared by that VM and other VMs, forms a separate virtual network element. Furthermore, in the context of NFV, a virtual network function is responsible for handling specific network functions running within one or more VMs 2808 corresponding to applications 2802 on hardware 2804.

[0167] The hardware 2804 may be implemented in a standalone network node having general or specific components. The hardware 2804 may achieve some functionality through virtualization. Alternatively, the hardware 2804 may be part of a larger cluster of hardware (e.g., in a data center or CPE) managed through management and orchestration 2810, where many hardware nodes cooperate and, among other things, oversee the lifecycle management of the application 2802. In some embodiments, the hardware 2804 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with virtual components to provide a virtual node with wireless capabilities, such as a wireless access node or base station. In some embodiments, some signaling may be provided using a control system 2812, which may alternatively be used for communication between the hardware nodes and the radio units.

[0168] 29 illustrates a communication diagram of a host 2902 communicating with a UE 2906, in part over a wireless connection, via a network node 2904, according to some embodiments. Exemplary implementations according to various embodiments of a UE (such as the UE 2412a of FIG. 24 and / or the UE 2500 of FIG. 25), a network node (such as the network node 2410a of FIG. 24 and / or the network node 2600 of FIG. 26), and a host (such as the host 2416 of FIG. 24 and / or the host 2700 of FIG. 27) described in the preceding paragraphs will now be described with reference to FIG. 29.

[0169] Like the host 2700, an embodiment of the host 2902 includes hardware such as a communications interface, processing circuitry, and memory. The host 2902 also includes software stored on or accessible by the host 2902 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 2906, connecting via an over-the-top (OTT) connection 2950 extending between the UE 2906 and the host 2902. In providing services to the remote user, the host application may provide user data that is transmitted using the OTT connection 2950.

[0170] The network node 2904 includes hardware that enables the network node 2904 to communicate with the host 2902 and the UE 2906. The connection 2960 may be direct or may pass through a core network (such as the core network 2406 of FIG. 24) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0171] The UE 2906 includes hardware and software, the software being stored on or accessible by the UE 2906 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 services to a human or non-human user via the UE 2906 with support from the host 2902. A running host application on the host 2902 can communicate with a running client application via an OTT connection 2950 that terminates at the UE 2906 and the host 2902. In providing services to the user, the client application on the UE can receive request data from the host application on the host and provide user data in response to the request data. The OTT connection 2950 can transfer both request data and user data. The client application on the UE can interact with the user and generate user data to provide to the host application through the OTT connection 2950.

[0172] The OTT connection 2950 may extend via a connection 2960 between the host 2902 and the network node 2904 and via a wireless connection 2970 between the network node 2904 and the UE 2906 to provide a connection between the host 2902 and the UE 2906. The connections 2960 and wireless connections 2970 over which the OTT connection 2950 may be provided are depicted abstractly to show communication between the host 2902 and the UE 2906 via the network node 2904, without explicit reference to any intermediate devices and the precise routing of messages through these devices.

[0173] As an example of transmitting data over the OTT connection 2950, ​​in step 2908, the host 2902 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 2906. In other embodiments, the user data is associated with a UE 2906 that shares data with the host 2902 without explicit human interaction. In step 2910, the host 2902 initiates a transmission carrying user data toward the UE 2906. The host 2902 can initiate the transmission in response to a request sent by the UE 2906. The request may be triggered by human interaction with the UE 2906 or by the operation of a client application running on the UE 2906. The transmission can be routed through the network node 2904 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 2912, the network node 2904 transmits the user data carried in the host 2902-initiated transmission to the UE 2906 in accordance with the teachings of the embodiments described throughout this disclosure. In step 2914 , the UE 2906 receives the user data carried in the transmission, which may be executed by a client application running on the UE 2906 associated with the host application executed by the host 2902 .

[0174] In some examples, the UE 2906 executes a client application that provides user data to the host 2902. The user data may be provided in reaction or response to data received from the host 2902. Thus, in step 2916, the UE 2906 can provide the 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 a user via an input / output interface of the UE 2906. Regardless of the particular manner in which the user data is provided, the UE 2906, in step 2918, initiates transmission of the user data toward the host 2902 via the network node 2904. In step 2920, the network node 2904 receives the user data from the UE 2906 and initiates transmission of the received user data toward the host 2902, in accordance with the teachings of embodiments described throughout this disclosure. In step 2922, the host 2902 receives the user data carried in the transmission initiated by the UE 2906.

[0175] One or more of the various embodiments improve the performance of the OTT service provided to the UE 2906 using the OTT connection 2950, ​​of which the radio connection 2970 forms the final segment. More specifically, the teachings of these embodiments can enable reporting of MDT measurement-related information between the SNPN, the PNI-NPN, and the PLMN, enabling the network to optimize inter- and intra-network coverage issues. Note that adding an NPN identifier to the list of networks for which the MDT configuration is valid is not obvious. This is because private networks are separate networks from PLMNs. As an example, an SNPN is not supposed to be connected to a PLMN or a PNI-NPN. Furthermore, a UE under current specifications is not allowed to perform mobility between an SNPN and a network other than the SNPN. Currently, MDT configurations are equivalent to each other and can only be applied to a UE within the set of PLMNs that includes the UE's registered PLMN. Therefore, extending the area scope of the MDT configuration to the NPN is not obvious, as it would require coordination and agreement between the NPN operator and the PLMN operator. However, the advantage of this configuration is that for a UE that can move between an NPN and a PLMN, an operator (either the operator of the PLMN or the NPN) can configure MDT measurements in the UE and, by receiving such measurements, have uniform monitoring of several aspects of the PLMN and the NPN, such as monitoring coverage at the NPN and the PLMN and at the coverage boundary between the PLMN and the NPN, thereby ensuring that coverage between different networks is uniform and that movements between different networks do not suffer from failures due to insufficient coverage, and (2) monitoring performance at the radio and service levels for UEs moving between the PLMN and the NPN, thereby enabling the operator to optimize steering of the UE toward coverage locations where a particular service is best provided and to optimize service coverage where performance is insufficient.

[0176] In an exemplary scenario, factory status information may be collected and analyzed by the host 2902. As another example, the host 2902 may process audio and video data that may have been retrieved from UEs for use in creating maps. As another example, the host 2902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2902 may store surveillance video uploaded by UEs. As another example, the host 2902 may store or control access to media content, such as video, audio, VR, or AR, that the host 2902 may broadcast, multicast, or unicast to UEs. As another example, the host 2902 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demands, location services, presentation services (such as compiling diagrams, etc. from data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0177] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. Additionally, there may be optional network functionality for reconfiguring the OTT connection 2950 between the host 2902 and the UE 2906 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 2902 and / or the UE 2906. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 2950 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above or other physical quantities from which software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2950 may include message formats, retransmission settings, preferred routing, etc.; the reconfiguration need not directly change the operation of the network node 2904. Such procedures and functionality may be known and practiced in the art. In particular embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host 2902. The measurements may be implemented in that software causes messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2950 while monitoring propagation time, errors, etc.

[0178] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices having different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information to other information, comparing the obtained or transformed information to information stored in a network node, and / or performing one or more operations based on the obtained or transformed information and as a result of said processing making a decision. Moreover, while components are depicted as being arranged within a larger box or as a single box nested within multiple boxes, in reality the computing device may comprise multiple different physical components that make up the single illustrated component, and functionality may be partitioned among the separate components. For example, a communications 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 communications interface. In another example, non-computer-intensive functionality of any of such components may be implemented in software or firmware, and computer-intensive functionality may be implemented in hardware.

[0179] In particular embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in particular 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 circuit without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuit may be configured to perform the described functionality regardless of whether or not it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to the processing circuit alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks generally.

Claims

1. 1. A method of operating a radio access network (RAN) node, said method comprising: Public Network Integrated Non-Public Network (PNI-NPN), Standalone Non-Public Networks (SNPNs), and Public Local Mobile Network (PLMN) determining 2310 a Minimization of Driving Test (MDT) configuration including an area range associated with the cell identified by at least one of: configuring 2320 a communication device served by a first cell in a first communication network with the MDT configuration to instruct the communication device to collect MDT measurements from a second cell in a second communication network; A method comprising:

2. the PNI-NPN is identified by a Closed Access Group (CAG); The SNPN is identified by a network identification (NID); The method of claim 1.

3. The method of claim 2 , wherein the PNI-NPN is further identified by the PLMN and the CAG.

4. The method of claim 2 or 3, wherein the SNPN is further identified by the PLMN and the CAG.

5. the first communication network is a PNI-NPN; the second communication network is the first communication network; 5. The method according to any one of claims 1 to 4.

6. the first communication network is an NPN; the second communication network: PLMN, SNPN, and PNI-NPN comprising at least one of:

6. The method according to any one of claims 1 to 5.

7. the first communications network is a public network; the second communication network: SNPN, and PNI-NPN comprising at least one of:

6. The method according to any one of claims 1 to 5.

8. determining the MDT configuration, a core network (CN) node within the PLMN; Operations, Administration and Maintenance (OAM) within the PLMN; CN nodes in the SNPN, and OAM in SNPN receiving the MDT configuration from a second network node comprising at least one of:

8. The method according to any one of claims 1 to 7.

9. The method of claim 1 , wherein the MDT configuration includes an indication that the communications device will report collected MDT measurements as the MDT measurements are collected.

10. The method of claim 1 , wherein the MDT configuration includes an indication that the communications device records collected MDT measurements as the MDT measurements are collected.

11. configuring the communication device, initial context setup request, A handover request, and Route Switch Request Acknowledgment transmitting the MDT configuration as part of at least one of:

11. The method according to any one of claims 1 to 10.

12. the communication device is operating in dual connectivity; and configuring the communication device includes transmitting the MDT configuration for both a master node (MN) and a secondary node (SN) to at least one of the MN and the SN.

12. The method according to any one of claims 1 to 11.

13. The method of claim 12 , wherein the first cell operates in a public network as the MN and the second cell operates in an NPN as the SN.

14. 13. The method of claim 12, wherein the first cell operates in an SNPN as the MN and the second cell operates in a PNI-NPN as the SN.

15. receiving the MDT measurements from the communication device (2330); 15. The method of any one of claims 1 to 14, further comprising:

16. Sending the MDT measurements to the second communications network (2340).

16. The method of claim 15, further comprising:

17. receiving the MDT measurements from the second communications network (2330); 15. The method of any one of claims 1 to 14, further comprising:

18. 1. A method of operating a core network (CN) node, said method comprising: Sending 2310 a Minimization of Driving Test (MDT) configuration to a Radio Access Network (RAN) node, the MDT configuration comprising: Public Network Integrated Non-Public Network (PNI-NPN), Standalone Non-Public Networks (SNPNs), and Public Local Mobile Network (PLMN) transmitting a Minimization of Driving Test (MDT) configuration (2310) including the area range identified by at least one of A method comprising:

19. A network node (2600) operating within a communications network, said network node comprising: A processing circuit (2602); a memory (2604) coupled to the processing circuitry and storing instructions executable by the processing circuitry to cause the network node to perform operations including any of the operations recited in claims 1 to 18; A network node (2600) comprising:

20. 20. A computer program comprising program code to be executed by processing circuitry (2602) of a network node (2600) operating in a communications network, whereby execution of the program code causes the network node to perform operations including any of the operations set forth in claims 1 to 18.

21. 20. A computer program product comprising: a non-transitory storage medium (2604) containing program code to be executed by processing circuitry (2602) of a network node (2600) operating in a communications network, whereby execution of the program code causes the network node to perform operations including any of the operations set forth in claims 1 to 18.

22. 20. A non-transitory computer-readable medium storing instructions executable by a processing circuit (2602) of a network node (2600) operating within a communications network to cause the network node to perform operations including any of the operations recited in claims 1 to 18.

Images