Minimum setting range for operational testing 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 a wireless communication system, and more particularly to a minimized setting range for operation tests for different network types.

Background Art

[0002] FIG. 1 shows an example of a New Radio (NR) network (e.g., a 5G network) including a 5th Generation (5G) Core (5GC) network 130, network nodes 120a - 120b (e.g., 5G base stations (gNBs)), and a plurality of communication devices 110 (also referred to as User Equipment (UE)).

[0003] A Non - Public Network (NPN) is a mechanism that enables a network to be deployed and / or managed by an entity other than a regular operator. In this specification, a "regular operator" is assumed to be an operator of one or more Public Land Mobile Networks (PLMNs). Note that a PLMN also has an identifier that may be called a PLMN Identifier (ID) or simply "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 Minimized Drive Test (MDT) setting including a region range identifying at least one of identification information of a Public Network Integrated Non - Public Network (PNI - NPN), identification information of a Stand - Alone Non - Public Network (SNPN), and identification information of a Public Land Mobile Network (PLMN). The method may further include setting the communication device using the MDT setting to instruct the communication device served by a first cell in a first communication network to collect MDT measurement values from a second cell in a second communication network.

[0005] According to other embodiments, a method for operating a core network ("CN") node is provided. The method includes transmitting a Minimized Test ("MDT") configuration to a Radio Access Network ("RAN") node. The MDT configuration includes a region range that identifies at least one of the following: a public network integrated nonpublic network ("PNI-NPN"), a standalone nonpublic network ("SNPN"), and a public regional mobile network ("PLMN").

[0006] According to other embodiments, a RAN node, a CN node, a communication device, a computer program, a computer program product, a non-temporary computer-readable medium, a system, or a host is provided to perform one of the methods described above.

[0007] Certain embodiments may provide one or more of the following technical advantages. In some embodiments, it is possible to report MDT measurement-related information between SNPN, PNI-NPN, and PLMN, enabling the network to optimize inter-network issues and coverage issues within the network.

[0008] Adding NPN identifiers to the list of networks where MDT settings are enabled is not obvious. This is because private networks are separate networks from PLMNs. For example, SNPNs are not intended to connect to PLMNs or PNI-NPNs. Furthermore, under the current specification, UEs are not permitted to perform movement between SNPNs and other networks different from SNPNs. Currently, MDT settings can only be applied to UEs within a set of PLMNs that are equivalent to each other and include registered PLMNs for the UE. Therefore, extending the scope of MDT settings to NPNs is not obvious, as it would imply coordination and agreement between NPN operators and PLMN operators. However, the advantage of this setting is that, for UEs that can move between NPNs and PLMNs, an operator (PLMN operator or NPN operator) can set MDT measurements in the UE and, by receiving such measurements, can have uniform monitoring of several aspects of PLMNs and NPNs. In some examples, an operator can monitor coverage in NPNs and PLMNs, and at the coverage boundary between PLMNs and NPNs. This ensures uniform coverage across different networks and guarantees that movement between networks does not suffer failures due to insufficient coverage. In an additional or alternative example, operators can monitor radio and service level performance for UEs moving between PLMN and NPN. This allows operators to optimize the maneuvering of UEs toward coverage locations where specific services are best delivered, as well as optimize service coverage where performance is insufficient.

[0009] To provide a further understanding of this disclosure, the accompanying drawings, which are included and incorporated into this application and form part of this application, illustrate certain non-limiting embodiments of the inventive concept. [Brief explanation of the drawing]

[0010] [Figure 1]This is a schematic diagram illustrating an example of a fifth-generation ("5G") network. [Figure 2] This is a signal flow diagram illustrating an example of a successful initial context setup. [Figure 3] This is a signal flow diagram illustrating an example of successful handover resource allocation. [Figure 4] This is a signal flow diagram illustrating an example of a successful trace initiation operation. [Figure 5] This table shows an example of trace-activated IE. [Figure 6] This table shows an example of MDT settings IE. [Figure 7] This table shows an example of an MDT PLMN list IE. [Figure 8] This table shows an example of a range boundary for an MDT PLMN list. [Figure 9] This table shows an example of MDT settings - NR IE. [Figure 10] This table shows an example of a range boundary for MDT settings - NR. [Figure 11] This table shows an example of the area range of a neighboring cell IE. [Figure 12] This table shows an example of a range boundary for the area of ​​neighboring cells. [Figure 13] This is a schematic diagram showing an example of a communication device that takes PN / NPN signals in and out, according to several embodiments. [Figure 14] This is a schematic diagram showing an example of a communication device moving within a PN / NPN according to several embodiments. [Figure 15] This table shows examples of MDT settings - NR IEs according to several embodiments. [Figure 16] This table shows examples of range boundaries for MDT settings-NR according to several embodiments. [Figure 17] This table shows an example of an MDT PLMN list IE according to several embodiments. [Figure 18]A table showing an example of a range boundary for the MDT PLMN list according to some embodiments. [Figure 19] A table showing an example of a cell NID information IE according to some embodiments. [Figure 20] A table showing an example of an MDT NPN list IE according to some embodiments. [Figure 21] A table showing an example of the area range of a neighboring cell IE according to some embodiments. [Figure 22] A table showing another example of an MDT configuration - NR IE according to some embodiments. [Figure 23] A flowchart showing an example of an operation performed by a network node according to some embodiments. [Figure 24] A block diagram of a communication system according to some embodiments. [Figure 25] A block diagram of a user equipment according to some embodiments. [Figure 26] A block diagram of a network node according to some embodiments. [Figure 27] A block diagram of a host computer communicating with a user equipment according to some embodiments. [Figure 28] A block diagram of a virtualized environment according to some embodiments. [Figure 29] A block diagram of a host computer communicating with a user equipment via a base station through a partial wireless connection according to some embodiments.

Modes for Carrying Out the Invention

[0011] Next, some of the embodiments considered herein are described more fully with reference to the accompanying drawings. Embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art, illustrating examples of embodiments of the inventive concept. However, the inventive concept may be embodied in many different forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments are provided to make this disclosure complete and comprehensive and to fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It may be implicitly assumed that components from one embodiment exist / are used in another embodiment.

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

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

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

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

[0016] The PNI-NPN mechanism is a different type of NPN. Similar to SNPN, PNI-NPN may be deployed to serve a specific set of users, such as corporate employees and machines. The main difference between SNPN and PNI-NPN is that PNI-NPN is integrated into PLMN. Therefore, PNI-NPN may be managed by the operator of the PLMN into which it is integrated.

[0017] PNI-NPN uses an identifier called a Closed Access Group ("CAG") instead of the NID identifier used by SNPN. A CAG is associated with each cell that makes up the PNI-NPN. UEs such as company employees and machines that should be given access to the PNI-NPN are configured with their associated CAG. Other UEs cannot access the PNI-NPN and are not configured to use a CAG. In general, both the UE and the network perform a check when determining whether a UE can connect to the PNI-NPN by checking whether the UE is configured with a CAG, and only if so is the UE granted access to the PNI-NPN.

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

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

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

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

[0022] If the INITIAL CONTEXT SETUP REQUEST message contains a NAS-PDU IE, the NG-RAN node must transparently pass it to the UE.

[0023] If the INITIAL CONTEXT SETUP REQUEST message contains a Masked IMEISV IE, the target NG-RAN node must use it to determine the UE characteristics for the next handling, if supported.

[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 aggregate maximum bitrate in the UE context, uses the received UE aggregate maximum bitrate for the non-GBR QoS flow for the UE as specified in TS23.501, stores the received mobility restriction list in the UE context, stores the received UE radio capability in the UE context, stores the received index to RAT / frequency selection priority in the UE context and uses it as specified in TS23.501, stores the received UE security capability 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, stores the received SRVCC operability in the UE context and uses it as specified in TS23.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, and receives the received NR The UE sidelink aggregate maximum bitrate is stored in the UE context and used for the sidelink communication of the corresponding UE in network scheduling mode for NR V2X services. If supported, the received LTE UE sidelink aggregate maximum bitrate is stored in the UE context and used for the sidelink communication of the corresponding UE in network scheduling mode for LTE V2X services. If supported, the received PC5 QoS parameters are stored in the UE context and TS23.It must be used as specified in 287, and if supported, the received management-based MDT PLMN list information must be stored in the UE context; if supported, the received IAB authorization information must be stored in the UE context; if supported, the received 5G ProSe authorization information must be stored in the UE context and used for the sidelink communications of the relevant UE in network scheduling mode for 5G ProSe services; if supported, the 5G ProSe UE PC5 aggregate maximum bitrate must be stored in the UE context and used for the sidelink communications of the relevant UE in network scheduling mode for 5G ProSe services; and if supported, the 5G ProSe PC5 QoS parameters must be stored in the UE context and used as specified in TS23.304.

[0025] If the INITIAL CONTEXT SETUP REQUEST message does not contain a roaming restriction list IE, the NG-RAN node must assume that roaming and access restrictions do not apply to the UE. The NG-RAN node must also assume that roaming and access restrictions do not apply to the UE if one of the QoS flows contains a specific ARP value (TS23.501).

[0026] If the INITIAL CONTEXT SETUP REQUEST message contains a trace activation IE, the NG-RAN node must initiate the requested trace functionality as described in TS32.422, if supported. Specifically, if the trace activation IE contains an MDT activation IE set to "Immediate MDT and Trace", the NG-RAN node must initiate the requested trace and MDT sessions as described in TS32.422; if the trace activation IE contains an MDT activation IE set to "Immediate MDT Only" or "Recording MDT Only", the NG-RAN node must initiate the requested MDT session as described in TS32.422; the NG-RAN node must ignore the interface IE to trace and the trace depth IE; if the trace activation IE contains an MDT location information IE within the MDT setup IE, this information must be stored and taken into account within the requested MDT session; and if the trace activation IE contains a signaling-based MDT within the MDT setup IE, this information must be stored and taken into account within the requested MDT session. If a PLMN list IE is included, the NG-RAN node can use it to propagate the MDT settings as described in TS37.320; if the trace activation IE includes a Bluetooth measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; if the trace activation IE includes a WLAN measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; if the trace activation IE includes a sensor measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; and if the trace activation IE includes an MDT settings IE and the NG-RAN node is a gNB, at least an MDT settings-NR IE must exist, but if the NG-RAN node is an ng-eNB, an MDT settings-EUTRA IE must not exist.

[0027] The 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 UE handover. The procedure can utilize UE-related signaling as shown in Figure 3.

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

[0030] If the HANDOVER REQUEST message contains a trace activation IE, the target NG-RAN node must initiate the requested trace functionality as described in TS32.422, if supported. Specifically, if the trace activation IE contains an MDT activation IE set to "Immediate MDT and Trace", the NG-RAN node must initiate the requested trace and MDT sessions as described in TS32.422; if the trace activation IE contains an MDT activation IE set to "Immediate MDT Only" or "Recording MDT Only", the NG-RAN node must initiate the requested MDT session as described in TS32.422; the target NG-RAN node must ignore the interface IE to trace and the trace depth IE; if the trace activation IE contains an MDT location information IE within the MDT configuration IE, this information must be stored and taken into account within the requested MDT session; and if the trace activation IE contains a signaling-based MDT within the MDT configuration IE, this information must be stored and taken into account within the requested MDT session. If a PLMN list IE is included, the NG-RAN node can use it to propagate the MDT settings as described in TS37.320; if the trace activation IE includes a Bluetooth measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; if the trace activation IE includes a WLAN measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; if the trace activation IE includes a sensor measurement settings IE within the MDT settings IE, it should be taken into consideration for the MDT settings as described in TS37.320; and if the trace activation IE includes an MDT settings IE and the NG-RAN node is a gNB, at least an MDT settings-NR IE must exist, but if the NG-RAN node is an ng-eNB, an MDT settings-EUTRA IE must not exist.

[0031] If the HANDOVER REQUEST message contains a location reporting request type IE, the target NG-RAN node should perform the requested location reporting function for the UE as described in subsection 8.12.

[0032] The purpose of the trace initiation procedure is to enable AMF to request the NG-RAN node to initiate a trace session for the UE. The procedure uses UE-related signaling as shown in Figure 4. If a UE-related logical NG connection does not exist, it 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 must start the requested trace session as described in TS32.422.

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

[0035] If a trace activation IE, including an MDT activation IE set to "Immediate MDT only" or "Recorded MDT only," is included in the TRACE START message, the NG-RAN node must start the requested MDT session as described in TS32.422, if supported, and the NG-RAN node must ignore the interface IE to the trace and the trace depth IE.

[0036] If the trace activation IE includes MDT location information IE within the MDT configuration IE, the NG-RAN node must store this information, if supported, and take it into account within the requested MDT session.

[0037] If a trace activation IE containing an MDT activation IE set to "Immediate MDT only" or "Recorded MDT only" is included in the TRACE START message, and a signaling-based MDT PLMN list IE is included in the MDT configuration IE, then the NG-RAN node may use it to propagate the MDT configuration as described in TS37.320.

[0038] If the trace activation IE includes Bluetooth measurement configuration information IE within the MDT configuration IE, the NG-RAN node must take it into account for the MDT configuration as described in TS37.320, if supported.

[0039] If the trace activation IE includes a WLAN measurement configuration IE within the MDT configuration IE, the NG-RAN node must take it into account for the MDT configuration as described in TS37.320, if supported.

[0040] If the trace activation IE includes sensor measurement configuration information IE within the MDT configuration IE, the NG-RAN node must take it into account for the MDT configuration as described in TS37.320, if supported.

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

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

[0043] Figure 6 shows an example of an MDT setting IE that defines the MDT setting parameters.

[0044] Figure 7 shows an example of an MDT PLMN list IE that provides a list of PLMNs permitted for MDT. Figure 8 shows an example of a range boundary for an MDT PLMN list IE.

[0045] Figure 9 shows an example of an MDT setting-NR IE that defines the MDT setting parameters for NR.

[0046] Figure 10 shows an example of the range boundary for the MDT setting-NR IE.

[0047] Figure 11 shows an example of the area range of a neighboring cell IE that defines the area range of neighboring cells for recording MDT. Figure 12 shows an example of the area boundary of the neighboring cell IE.

[0048] Currently, certain challenges exist. In some cases, the problem is identified in the flexibility of existing solutions in MDT configuration collection, particularly regarding the range of MDT measurements that only support MDT configuration collection on public networks.

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

[0050] The above problem also means that network operators in private networks cannot collect MDT-related information via UEs that connect to / travel to other networks. Such UEs can provide measurements on the operator's PLMN cells from the perspective of UEs served by neighboring NPN cells. Such measurements are beneficial because they allow them to optimize coverage and performance within the PLMN.

[0051] Specific aspects of this disclosure and their embodiments can provide solutions to these or other problems. In some embodiments, a first network node (e.g., the AMF / OAM of the network) can transmit an MDT configuration to a RAN node, the MDT configuration including a region range that identifies at least one of the following networks: The information includes one or more of the following: (1) PNI-NPN identification information, (2) identification information associated with an SNPN, (3) identification information which may include a list of at least an NPN PLMN, CAG ID, and NID ID, and (4) identification information associated with a public network (PLMN).

[0052] In some examples, where the MDT configuration generated by the first network node extends across both PN and NPN networks, the first network node (e.g., AMF / OAM) performs the operation.

[0053] In some examples, the operation involves configuring the respective MDT measurement settings for a second network node operating within the NPN, i.e., PNI-NPN and / or SNPN, for a specific UE that is registered within the first network (NPN) and moves between the first and second network coverages.

[0054] In an additional or alternative example, the operation would involve configuring the respective MDT measurement settings for a third network node operating within another PLMN associated with a second network (PN) for a specific UE that is registered within the second network (PN) and moves between the first and second network coverages.

[0055] In an additional or alternative example, the operation would involve configuring the respective MDT measurement settings for the second network node operating within an NPN, i.e., PNI-NPN and / or SNPN, for a specific UE that is registered within the second network (PN) and moves between the first and second network coverages.

[0056] In an additional or alternative example, the operation would involve configuring the respective MDT measurement settings for a third network node operating within another PLMN associated with a first network (NPN) for a specific UE that is registered within the first network (NPN) and moves between the first and second network coverages.

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

[0058] In some examples, the operation involves setting up MDT measurements for a second network node operating within 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 specific UE registered in both (first and second) networks.

[0059] In an additional or alternative example, the operation would involve setting up a dual connectivity configuration for a specific UE registered in both (first and second) networks, with a third network node operating within the other PLMN associated with the PN as the master node (MN), and the respective MDT measurements for the second network node as the SN.

[0060] In some embodiments, the domain range for MDT configuration is extended by including support for different network types. Associated NPN identifiers can be included in the domain range for MDT configuration.

[0061] In this specification, the terms Non-Public Network / Private Network ("NPN") and Standalone NPN ("SNPN") / Public Network Integrated NPN ("PNI-NPN") nodes are used interchangeably. In some examples, the PNI-NPN network in this specification covers a scenario in which a cell publishes a Public Area Mobile Network ("PLMN") + Closed Access Group ("CAG") in the NPN Identification Information in System Information Block 1 ("SIB1").

[0062] In this specification, the SNPN network covers the scenario in which a cell publishes PLMN+ network identification information ("NID") within the NPN identification information in SIB1.

[0063] In the case of Management-Based Operational Test Minimization ("MDT"), the Core Network ("CN") indicates to the Radio Access Network ("RAN") nodes whether an MDT can be configured by the RAN node for each connected UE by providing a Management-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 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 PLMN handovers and PLMN UE context searches.

[0066] In some embodiments, a list of network identifiers, including PN identifiers and / or NPN identifiers, which constitute a range of regions in which MDT settings (management-based or signaling-based) can be configured in the UE, is communicated from source to target during intra-PLMN and inter-PLMN movements, intra-system and inter-system movements (for example, in the case of a UE moving from PLMN to SNPN), and during intra-network UE context lookups.

[0067] In additional or alternative embodiments, the operation is performed by a first network node (e.g., a Network Access and Mobility Management Function ("AMF") / Operation, Management, and Maintenance ("OAM")) that transmits the MDT configuration to a RAN node, the MDT configuration including a domain range that identifies at least one network. The information includes one or more of the following: (1) identification information for a PNI-NPN (Public Network Integrated NPN), (2) identification information associated with an SNPN (Standalone NPN), (3) identification information which may include a list of at least an NPN PLMN, CAG ID, and NID ID, and (4) identification information associated with a public network (PLMN).

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

[0069] Figure 13 shows an example of an UE entering and exiting the second network (shaded area).

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

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

[0072] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by a cell in the PNI-NPN with its respective MDT measurement configuration, which should also be collected from cells belonging to a second network node in the SNPN.

[0073] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by cells in the PNI-NPN with respective MDT measurement configurations that should also be collected from cells belonging to a second network node in the other PNI-NPN.

[0074] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by a cell in the SNPN with each MDT measurement configuration to be collected exclusively by or additionally from a cell belonging to a second network node in the PNI-NPN.

[0075] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by a cell in the SNPN with respective MDT measurement configurations to be collected exclusively by or additionally from a cell belonging to a second network node in the other SNPN.

[0076] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by a cell in the SNPN with respective MDT metric configurations to be collected exclusively by or additionally from a cell belonging to a second network node in the public network.

[0077] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by cells in the public network with respective MDT metric configurations to be collected exclusively by or additionally from cells belonging to a second network node in the PNI-NPN.

[0078] In additional or alternative embodiments, the first node notifies the MDT configuration for either signaling-based or management-based MDT, enabling the RAN node to configure at least one UE served by cells in the public network with respective MDT metric configurations 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 MDT measurements and immediately reports them to the serving network. The serving network can then forward the measurements to a system that analyzes them (e.g., an OAM system).

[0081] In additional or alternative embodiments, if the MDT setting is for recording MDT, the UE records the MDT measurements and reports the MDT measurements to the serving network at the time of recording reporting. The serving network can then forward the measurements to a system that analyzes them (e.g., an OAM system).

[0082] In additional or alternative embodiments, the entity receiving MDT measurements collected by the UE and notified 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 implementation example is shown below.

[0084] In some embodiments, if the serving cells associated with a private network (e.g., SNPN) and PNI-NPN are part of the MDT configuration-NR, the CN requests the network node to configure a specific UE with MDT measurement-related information. Implementation examples are given in Figures 15-16.

[0085] Figure 15 shows an example of an MDT setting-NR IE that defines the MDT setting parameters for NR.

[0086] Figure 16 shows an example of a range boundary for MDT settings - NR IE.

[0087] In additional or alternative embodiments, the CN requests the network node to configure a specific 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] Figure 17 shows an example of an MDT PLMN list IE that provides a list of PLMN identifiers permitted for MDT.

[0089] Figure 18 shows an example of a range boundary for an MDT PLMN list.

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

[0091] Figure 19 shows an example of an MDT NPN list IE that provides a list of NPN identifiers permitted for MDT.

[0092] Figure 20 shows an example of a range boundary 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 the NPN network, as shown in Figure 21.

[0094] The implementation details within the NPN settings are described below.

[0095] In some embodiments, the operation is performed on the first network node, which operates within a private network / NPN, to configure the respective MDT settings for a second network node that is on the same network as the first network node.

[0096] In additional or alternative embodiments, the CN within the SNPN notifies a trace-based message for a specific UE, enabling the RAN node to configure at least one UE served by a cell within the SNPN, with the respective MDT measurement settings for cells belonging to the same SNPN.

[0097] In additional or alternative embodiments, the CN within the PNI-NPN notifies trace-based messages for a specific UE, enabling the RAN node to configure at least one UE served by a cell within the PNI-NPN in its respective MDT measurement settings for cells belonging to the same PNI-NPN.

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

[0099] Figure 22 shows an example of adding or replacing an MDT setting-NR IE that defines the MDT setting parameters for NR.

[0100] The dual network connectivity settings are described below.

[0101] In some embodiments, the operation performed in dual connectivity ("DC") is the operation that operates in a first network as a master node ("MN") and a second network as a secondary node ("SN") for a particular UE. The UE performs registration in both (first and second) networks. In MR DC scenarios, (a) a cell operating as an MN in the public network and a cell operating as an SN in the PNI-NPN and vice versa, (b) a cell operating as an MN in the public network and a cell operating as an SNPN and vice versa, and (c) a cell operating as an MN in the SNPN and a cell operating as an SN in the PNI-NPN and vice versa.

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

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

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

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

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

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

[0108] Figure 23 shows the operations performed by the network node.

[0109] In block 2310, processing circuit 2602 determines an MDT setting that includes a region range. In some examples, the network node is a core network ("CN") node, and determining the MDT setting includes transmitting the MDT setting to a radio access network ("RAN") node. In other examples, the network node is a RAN node, and determining the MDT setting includes receiving the MDT setting 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 an SNPN, and an OAM in an SNPN.

[0110] In some embodiments, the region range identifies at least one of the following: PNI-NPN identification information, SNPN identification information, and PLMN identification information. In some examples, the PNI-NPN identification information includes CAG. In additional or alternative examples, the SNPN identification information includes NID.

[0111] In block 2320, processing circuit 2602 configures a 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 PLMN, SNPN, and PNI-NPN. In other examples, the first communication network is a public network, and the second communication network includes at least one of SNPN and PNI-NPN.

[0112] In additional or alternative embodiments, the MDT setting includes an indication that the communication device reports the collected MDT measurements as the MDT measurements are collected.

[0113] In additional or alternative embodiments, the MDT configuration includes an indication that the communication device records the collected MDT measurements as the MDT measurements are collected.

[0114] In additional or alternative embodiments, configuring a communication device includes sending MDT configuration as part of at least one of the following: an initial context setup request, a handover request, and a route switching request acknowledgment.

[0115] In additional or alternative embodiments, the communication device operates with dual connectivity. Configuring the communication device involves sending MDT settings for both the master node (MN) and the secondary node (SN) to at least one of the MN and SN. In some examples, the first cell operates as the MN within the public network, and the second cell operates as the SN within the NPN. In additional or alternative examples, the first cell operates as the MN within the SNPN, and the second cell operates as the SN within the PNI-NPN.

[0116] In block 2330, the processing circuit 2602 receives 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] In block 2340, the processing circuit 2602 transmits MDT measurements via the communication interface 2606. In some embodiments, the MDT measurements are transmitted to a second communication network.

[0118] The various operations shown in Figure 23 may be optional with respect to some embodiments.

[0119] Figure 24 shows an example of a communication system 2400 according to several embodiments.

[0120] In this example, the communication system 2400 includes a communication network 2402 which includes an access network 2404 such as a radio access network (RAN) and a core network 2406 which includes 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. Furthermore, 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 bandwidth portion are supplied and integrated by a single vendor. That is, it will be understood that the network node 2410 may include separate implementations or parts thereof. For example, in some embodiments, the communication network 2402 includes one or more open RAN (ORAN) network nodes. An ORAN network node is a node in the communications network 2402 that supports the ORAN specification (for example, a specification 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 in the communications network 2402, including one or more network nodes 2410 and / or core network node 2408.

[0121] Examples of ORAN network nodes include open radio units (O-RUs), open distributed units (O-DUs), open central units (O-CUs) including O-CU control planes (O-CU-CPs) or O-CU user planes (O-CU-UPs), RAN intelligent controller (near-real-time or non-real-time) hosting software or software plugins such as quasi-real-time RAN control applications (e.g., xApps) or non-real-time RAN automation applications (e.g., rApps), or any combination thereof (the adjective "open" specifies support for the ORAN specification). Network nodes can support the specification by supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, open fronthaul user plane interfaces, or open fronthaul management plane interfaces. Intent and content-aware notifications described herein may be communicated from 3GPP network nodes or ORAN network nodes over 3GPP defined interfaces (e.g., N2, N3) and / or ORAN Alliance defined interfaces (e.g., A1, O1). Furthermore, an ORAN network node may be a logical node within a physical node. In addition, an ORAN network node may be implemented within a virtualized environment in which one or more network functions are virtualized (as further described below). For example, the virtualized environment may include an O-Cloud Computing Platform organized by a service management and organization framework via an O-2 interface defined by the O-RAN Alliance. Network node 2410 facilitates direct or indirect connection of user equipment (UEs) by connecting wireless devices 2412a, 2412b, 2412c, and 2412d (one or more of which may be collectively referred to as UE2412) to the core network 2406 over one or more wireless connections.The network node 2410 facilitates direct or indirect connection of user equipment (UEs) by connecting UE2412a, 2412b, 2412c, and 2412d (one or more of which may be collectively referred to as UE2412) to the core network 2406 over one or more wireless connections.

[0122] Exemplary wireless communication on a wireless connection includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information, without using wires, cables, or other material conductors. Furthermore, in different embodiments, the 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 participate in the communication of data and / or signals, whether or not via a wired or wireless connection. The 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] UE2412 may be any of a wide variety of communication devices, including wireless devices that are configured, set up, and / or capable of communicating wirelessly with network node 2410 and other communication devices. Similarly, network node 2410 may be configured, capable, set up, and / or capable of communicating directly or indirectly with UE2412 and / or other network nodes or devices in the communication network 2402 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management, within the communication network 2402.

[0124] In the described example, core network 2406 connects network node 2410 to one or more hosts, such as host 2416. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 2406 includes one or more core network nodes (e.g., core network node 2408) constructed from hardware and software components. Since the characteristics of these components may be substantially similar to those described for UEs, network nodes, and / or hosts, their descriptions are generally applicable to the corresponding components of core network node 2408. An exemplary core network node includes one or more functions from among the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0125] Host 2416 may be owned or controlled by a service provider other than the operator or provider of the access network 2404 and / or the communication network 2402, and may be operated by or on behalf of the service provider. Host 2416 may host a variety of 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 on various ambient conditions detected by multiple UEs, analytical functions, social media, functions for controlling or optionally interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0126] Overall, the communication system 2400 in Figure 24 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, including, but not limited to, specific standards, such as the Pan-European Digital Mobile Telephone System (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any available next-generation standard (e.g., 6G), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as Global Interoperability for Microwave Access (WiMAX), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide area network (LPWAN) standards such as LoRa and Sigfox.

[0127] In some examples, the communication network 2402 is a cellular network implementing 3GPP standardization features. Therefore, the communication network 2402 can support network slicing to provide different logical networks to different devices connected to the communication network 2402. For example, the communication network 2402 can provide ultra-high reliability low latency communication (URLLC) services to several UEs while providing extended mobile broadband (eMBB) services to other UEs and / or massive machine-type communications (mMTC) / massive IoT services to even further UEs.

[0128] In some examples, UE2412 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 2404 on a predetermined schedule when triggered by an internal or external event, or in response to a request from access network 2404. Furthermore, the UE may be configured to operate in single, multi-RAT, or multi-standard modes. For example, the UE can operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., it can be 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, hub 2414 communicates with access network 2404 to facilitate indirect communication between one or more UEs (e.g., UE2412c and / or 2412d) and a network node (e.g., network node 2410b). In some examples, hub 2414 may be a controller, router, content source and analytics, or any other communication device described herein with respect to the UE. For example, hub 2414 may be a broadband router that enables access to core network 2406 for the UE. In another example, hub 2414 may be a controller that sends commands or instructions to one or more actuators within the UE. Commands or instructions may be received from the UE, network node 2410, or by executable code, scripts, processes, or other instructions within hub 2414. In yet another example, hub 2414 may be a data collector that functions as temporary storage for UE data, and in some embodiments can perform analysis or other processing on the data. In yet another example, 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 perceptual information via network nodes, and then the hub 2414 provides them to the UE either immediately, after performing local processing, and / or after adding further local content. In yet another example, the hub 2414 can function as a proxy server or orchestrator for the UE, especially if one or more of the UEs are low-energy IoT devices.

[0130] Hub 2414 can have a permanent / persistent or intermittent connection to network node 2410b. Hub 2414 can also enable different communication methods and / or communication schedules between Hub 2414 and UEs (e.g., UE2412c and / or 2412d), as well as between Hub 2414 and the core network 2406. In other examples, Hub 2414 connects to the core network 2406 and / or one or more UEs via wired connections. Furthermore, Hub 2414 may be configured to connect to an M2M service provider on the access network 2404 and / or another UE via a direct connection. In some scenarios, a UE can establish a wireless connection with network node 2410 while still connected via Hub 2414 via wired or wireless connections. In some embodiments, Hub 2414 may be a dedicated hub, i.e., a hub whose primary function is to route communication from UEs to network node 2410b and from network node 2410b to UEs. In other embodiments, the hub 2414 may be a non-dedicated hub, i.e., a device capable of routing communication between the UE and the network node 2410b, but also capable of acting as a communication start point and / or communication end point for a particular data channel.

[0131] Figure 25 shows the UE2500 in several embodiments. As used herein, UE refers to a device that is capable of, configured, and / or operated to communicate wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and vehicle-mounted or vehicle-embedded / integrated wireless devices. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

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

[0133] The UE2500 includes processing circuitry 2502 that is operably coupled via bus 2504 to an input / output interface 2506, a power supply 2508, memory 2510, a communication interface 2512, and / or any other components, or any combination thereof. A particular UE may utilize all or a subset of the components shown in Figure 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, memory, transceivers, transmitters, and receivers.

[0134] The processing circuit 2502 is configured to process instructions and data and may be configured to implement any sequential state machine capable of executing instructions stored in memory 2510 as machine-readable computer programs. The processing circuit 2502 may be implemented as one or more hardware-implemented state machines (for example, in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), one or more stored computer programs such as programmable logic with appropriate firmware, a microprocessor or digital signal processor (DSP) 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 input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to take in information to the UE2500. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors for detecting user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0136] In some embodiments, the power supply 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 supply 2508 may further include a power circuit for delivering power to various parts of the UE2500 from the power supply 2508 itself and / or 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 supply 2508. The power circuit may perform any formatting, conversion, or other modifications to the power from the power supply 2508 to make it suitable for each component of the UE2500 being powered.

[0137] Memory 2510 is or may be configured to include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and other types of memory. For example, memory 2510 may include one or more application programs 2514, such as an operating system, a web browser application, a widget, a gadget engine, or other application, along with corresponding data 2516. Memory 2510 can store a wide variety of operating systems or combinations of operating systems for use by the UE2500.

[0138] Memory 2510 may be configured to include several physical drive units such as a redundant array of independent disks (RAID), flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-density digital versatile disk (HD-DVD) optical disc drives, internal hard disk drives, Blu-ray optical disc drives, holographic digital data storage (HDDS) optical disc drives, external mini dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smart card memory such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as 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". Memory 2510 can enable the UE2500 to access instructions, application programs, etc., stored on temporary or non-temporary memory media, offload data, or upload data. Products that utilize communication systems, etc., may be materialized as memory 2510 or tangibly within memory 2510, and memory 2510 may be a device-readable storage medium or may include 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, including or communicatively coupled to an antenna 2522. The communication interface 2512 may include one or more transceivers used for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 2518 and / or receiver 2520 suitable for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter 2518 and receiver 2520 may be coupled to one or more antennas (e.g., antenna 2522), and may share or implement separately circuit components, software, or firmware.

[0140] In the illustrated embodiments, the communication functions of the communication interface 2512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) for location determination, other similar communication functions, or any combination thereof. The communication 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, and Hypertext Transfer Protocol (HTTP).

[0141] Regardless of the sensor type, the UE can provide an output of the data captured by its sensor through its communication interface 2512 via a wireless connection to a network node. The data captured by the UE's sensor can be communicated via another UE through a wireless connection to a network node. The output may be periodic (e.g., once every 15 minutes if it reports the temperature it detected), random (e.g., to equalize 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, a UE may include an actuator, motor, or switch related to a communication interface configured to receive radio input from a network node via a wireless connection. The state of the actuator, motor, or switch may change in response to the received radio input. For example, a UE may include a motor that adjusts the 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 taken in the form of an Internet of Things (IoT) device, a UE can be a device for use in one or more application areas, which include, but are not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-exclusive examples of such IoT devices are devices that are or are incorporated into such devices, such as connected refrigerators or freezers, TVs, connected lighting devices, energy meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, immersion / humidity sensors, electronic door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearables for haptic enhancement or perceptual enhancement, water sprinklers, animal or product tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device such as a heart rate monitor or remotely controlled surgical robot. The UE in the form of an IoT device comprises circuitry and / or software that depends on the intended application of the IoT device, in addition to the other components described with respect to the UE2500 shown in Figure 25.

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

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

[0146] Figure 26 shows a network node 2600 according to several embodiments. As used herein, a network node refers to a device that is configured, set up, and / or capable of communicating directly or indirectly with UEs and / or other network nodes or devices in a communication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node B, evolved node B (eNB), NR node B (gNB)), O-RAN nodes or components of O-RAN nodes (e.g., intelligent controllers, O-RUs, O-DUs, O-CUs).

[0147] Base stations may be classified based on the amount of coverage they provide (or, in other words, the base station's transmit power level), and therefore may be called femto base stations, pico base stations, micro base stations, or macro base stations depending on the amount of coverage they provide. A base station may also be a relay node or relay donor node that controls relays. 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), which may be called a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be called nodes in a distributed antenna system (DAS).

[0148] Other examples of network nodes include multi-transmit point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BS, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base station transceiver stations (BTSs), transmit points, transmit nodes, multi-cell / multicast coordinated entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes (e.g., evolved serving mobile location centers (E-SMLCs)), and / or minimization of operational testing (MDT).

[0149] Network node 2600 includes processing circuitry 2602, memory 2604, communication interface 2606, and power supply 2608. Network node 2600 may consist of multiple physically separate components (e.g., node B components and RNC components, or BTS components and BSC components), each of which may have its own separate components. In certain scenarios where network node 2600 has multiple separate components (e.g., BTS components and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique node B-RNC pair may, in some cases, be considered a single separate network node. In some embodiments, network node 2600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2604 for different RATs), and some components may be reused (e.g., the same antenna 2610 may be shared by different RATs). The network node 2600 may also include multiple sets of various illustrated components for different wireless technologies integrated into the network node 2600, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within the network node 2600.

[0150] The processing circuit 2602 may comprise one or more combinations of hardware, software, and / or coding logic capable of operating to provide the functionality of the network node 2600, either alone or together with other components of the network node 2600 such as memory 2604, including a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device or resource.

[0151] In some embodiments, the processing circuit 2602 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 2602 includes one or more of the radio frequency (RF) transceiver circuit 2612 and the 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 radio and digital units. 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 include, but is not limited to, any form of volatile or non-volatile computer-readable memory devices that store information, data, and / or instructions that can be used by the processing circuit 2602, including 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 disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile non-temporary device-readable and / or computer-executable memory devices. Memory 2604 may store any appropriate instructions, data, or information, including computer programs, software, and applications that include one or more logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuit 2602 and made available to the network node 2600. Memory 2604 may be used to store any calculations performed by the processing circuit 2602 and / or any data received via the communication interface 2606. In some embodiments, the processing circuit 2602 and the memory 2604 are integrated.

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

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

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

[0156] Antenna 2610, communication interface 2606, and / or 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 the UE, another network node, and / or any other network equipment. Similarly, antenna 2610, communication interface 2606, and / or 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 the UE, another network node, and / or any other network equipment.

[0157] Power supply 2608 powers the various components of network node 2600 in a form appropriate to each component (for example, at the voltage and current levels required for each component). Power supply 2608 may further include, or be coupled to, a power management circuit to supply power to the components of network node 2600 for performing the functions described herein. For example, 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 electrical cable, thereby the external power source powers the power circuit of power supply 2608. As a further example, power supply 2608 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery can provide backup power if the external power supply fails.

[0158] Embodiments of the network node 2600 may include further components other than those shown in Figure 26 to provide a particular aspect of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the subject matter described herein. For example, the network node 2600 may include user interface equipment to enable input of information to and output of information from the network node 2600. This may enable a user to perform diagnostic, maintenance, repair, and other management functions on the network node 2600.

[0159] Figure 27 is a block diagram of a host 2700, which may be one embodiment of host 2416 in Figure 24, according to various aspects described herein. As used herein, host 2700 is or may comprise various combinations of hardware and / or software, including standalone servers, blade servers, cloud implementation servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 2700 can provide one or more services to one or more UEs.

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

[0161] Memory 2712 may contain one or more computer programs including one or more host application programs 2714 and data 2716, the data 2716 may contain user data, for example, data generated by the UE for host 2700, or data generated by host 2700 for the UE. Embodiments of host 2700 may utilize only a subset or all of the components shown. Host application programs 2714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multipurpose 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 implementation forms of UE (e.g., handsets, desktop computers, wearable display systems, head-up display systems). The host application program 2714 can also provide user authentication and licensing checks and periodically report health, route, and content availability to central nodes such as devices within or on the edge of the core network. Thus, host 2700 can select and / or direct different hosts for over-the-top services for the UE. The host application program 2714 can support various protocols such as HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and Dynamic Adaptive Streaming over HTTP (MPEG-DASH).

[0162] Figure 28 is a block diagram showing a virtualization environment 2800 in which functions implemented by several embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and networking resources. The virtualization used herein can be applied to any device or its components described herein and relates to an implementation in which at least a portion of the functions are implemented therein as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components run by one or more virtual machines (VMs) implemented within one or more virtualization environments 2800, which are hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments where the virtual nodes do not require wireless connectivity (e.g., core network nodes or hosts), the nodes 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 organized by a service management and organization framework via an O-2 interface.

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

[0164] Hardware 2804 includes processing circuits, memory for storing software and / or instructions executable by the hardware processing circuits, and / or other hardware devices described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuits to instantiate one or more virtualization layers 2806 (also called a hypervisor or virtual machine monitor (VMM)), providing VM2808a and 2808b (one or more of which may be collectively referred to as VM2808), and / or performing 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 appears to the VM2808 as networking hardware.

[0165] VM2808 features virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may run on the corresponding virtualization layer 2806. Different embodiments of instances of the virtual appliance 2802 may be implemented in one or more of the VM2808s, and the implementation may be done in different ways. Hardware virtualization is referred to as network function virtualization (NFV) in some contexts. NFV may be used to aggregate many types of network equipment on industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.

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

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

[0168] Figure 29 shows a communication diagram of host 2902 communicating with UE 2906 via network node 2904, partially over a wireless connection, in several embodiments. Exemplary implementations of various embodiments of the UEs (such as UE 2412a in Figure 24 and / or UE 2500 in Figure 25), network nodes (such as network node 2410a in Figure 24 and / or network node 2600 in Figure 26), and hosts (such as host 2416 in Figure 24 and / or host 2700 in Figure 27), as described in the preceding paragraphs, are now described with reference to Figure 29.

[0169] Like host 2700, an embodiment of host 2902 includes hardware such as a communication interface, processing circuitry, and memory. Host 2902 also includes software that is stored in or accessible by host 2902 and executable by the processing circuitry. The software may include a host application that can operate to serve remote users, such as UE2906, which connects via an over-the-top (OTT) connection 2950 extending between UE2906 and host 2902. When serving remote users, the host application may provide user data transmitted using the OTT connection 2950.

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

[0171] UE2906 includes hardware and software, the software being stored in or accessible by UE2906 and executable by the UE's processing circuitry. The software may include client applications, such as a web browser or operator-specific “app,” which may operate to serve human or non-human users via UE2906 with the support of host 2902. On host 2902, a running host application can communicate with a running client application via an OTT connection 2950 terminating at UE2906 and host 2902. When serving a user, the UE's client application can receive request data from the host's host application and provide user data in response to the request data. The OTT connection 2950 can transfer both request data and user data. The UE's client application can interact with the user and generate user data to provide to the host application via the OTT connection 2950.

[0172] The OTT connection 2950 can provide a connection between host 2902 and UE 2906 by extending through connection 2960 between host 2902 and network node 2904, and through the wireless connection 2970 between network node 2904 and UE 2906. Connections 2960 and wireless connection 2970, which the OTT connection 2950 may provide, are depicted abstractly to illustrate communication between host 2902 and UE 2906 through network node 2904 without explicitly referring to any intermediate devices and the exact routing of messages through these devices.

[0173] As an example of transmitting data via the OTT connection 2950, ​​in step 2908, host 2902 provides user data, which may be done by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 2906. In other embodiments, the user data is associated with UE 2906 sharing data with host 2902 without explicit human interaction. In step 2910, host 2902 initiates a transmission carrying user data toward UE 2906. Host 2902 may initiate a transmission in response to a request sent by UE 2906. The request may be triggered by human interaction with UE 2906 or by the operation of a client application running on UE 2906. The transmission may pass through network node 2904 in accordance with the teachings of embodiments described throughout this disclosure. Thus, in step 2912, network node 2904 transmits the user data carried in the transmission initiated by host 2902 toward UE 2906 in accordance with the teachings of embodiments described throughout this disclosure. In step 2914, UE2906 receives the user data carried in the transmission, which may be executed by a client application running on UE2906 associated with a host application run by host 2902.

[0174] In some examples, UE2906 runs a client application that provides user data to host 2902. User data may be provided in response to or in reaction to data received from host 2902. Thus, in step 2916, UE2906 may provide user data, which may be done by running a client application. When providing user data, the client application may further consider user input received from the user via the input / output interface of UE2906. Regardless of the particular manner in which the user data is provided, in step 2918, UE2906 initiates a transmission of the user data toward host 2902 via network node 2904. In step 2920, in accordance with the teachings of embodiments described throughout this disclosure, network node 2904 receives user data from UE2906 and initiates a transmission of the received user data toward host 2902. In step 2922, host 2902 receives the user data carried in the transmission initiated by UE2906.

[0175] One or more of the various embodiments improve the performance of OTT services provided to UE 2906 by using OTT connection 2950, ​​in which wireless connection 2970 forms the final segment. More specifically, the teachings of these embodiments can enable the reporting of MDT measurement-related information between SNPN, PNI-NPN, and PLMN, allowing the network to optimize coverage issues between and within the network. Note that adding NPN identifiers to the list of networks for which MDT configuration is enabled is not obvious. The reason this is not obvious is that private networks are separate networks from PLMN. For example, SNPN is not intended to connect to PLMN or PNI-NPN. Furthermore, under the current specification, UEs are not permitted to perform movement between SNPN and other networks different from SNPN. Currently, MDT configurations can only be applied to UEs within a set of PLMNs that are equivalent to each other and include registered PLMNs for the UE. Thus, extending the scope of MDT configuration to NPN is not obvious, as it would imply coordination and agreement between NPN operators and PLMN operators. However, the advantage of this configuration is that, in the case of a UE that can move between NPN and PLMN, the operator (the PLMN or NPN operator) can set MDT measurements on the UE and, by receiving such measurements, can have (1) uniform monitoring of several aspects of PLMN and NPN, such as monitoring of coverage between NPN and PLMN and coverage boundaries between PLMN and NPN. This makes it possible to ensure that coverage is uniform across different networks and that movement between different networks does not suffer failures due to insufficient coverage, as well as (2) monitoring of radio and service level performance for UEs moving between PLMN and NPN. This makes it possible for the operator to optimize the maneuvering of the UE toward coverage locations where a particular service is best delivered, as well as optimizing service coverage where performance is insufficient.

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

[0177] In some embodiments, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve. Furthermore, optional network functions may exist for reconfiguring the OTT connection 2950 between host 2902 and UE 2906 in response to variations in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host 2902 and / or UE 2906. In some embodiments, sensors (not shown) may be deployed in or in relation to other devices through which the OTT connection 2950 passes, and the sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguring the OTT connection 2950 may include message formatting, retransmission settings, preferred routing, etc., and the reconfiguration does not need to directly change the operation of network node 2904. Such procedures and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements such as throughput, propagation time, and latency by host 2902. The measurements may be implemented in such a way that software uses the OTT connection 2950 to ensure that messages, particularly empty or "dummy" messages, are sent while monitoring propagation time, errors, etc.

[0178] The computing devices described herein (e.g., UEs, network nodes, hosts) may include illustrated combinations of hardware components, but other embodiments may include computing devices having different combinations of components. It should be understood that these computing devices may have any preferred 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 circuits, which may process information by, for example, converting obtained information to other information, comparing the obtained or converted information to information stored in the network node, and / or performing one or more operations based on the obtained or converted information and as a result of the processing making a decision. Furthermore, although components are depicted as being located within a larger box or as a single box nested within multiple boxes, in practice, computing devices may comprise multiple different physical components constituting a single illustrated component, and functions may be compartmentalized between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functions of the components may be separated between the processing circuit and the communication interface. In another example, the non-computer-intensive functions of any of such components may be implemented in software or firmware, while the computer-intensive functions may be implemented in hardware.

[0179] In certain embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by a processing circuit without executing instructions stored in a separate or individual device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, the processing circuit can be configured to perform the described functions, with or without executing instructions stored in a non-temporary computer-readable storage medium. The benefits provided by such functions are enjoyed by the computing device as a whole, and / or generally by the end user and the wireless network, not limited to the processing circuit alone or other components of the computing device.

Claims

1. A method for operating a wireless access network (RAN) node, wherein the method is Public Network Integrated Non-Public Network (PNI-NPN), and A standalone non-public network (SNPN) that is identified by network identification information (NID). Determining a minimum test (MDT) setting for a test run that includes a range of areas associated with a cell identified by at least one of the following (2310): Configuring a communication device using the MDT settings to instruct a communication device served by a first cell in a first communication network to collect MDT measurements from a second cell in a second communication network (2320) Methods that include...

2. The method according to claim 1, wherein the PNI-NPN is identified by a closed access group (CAG).

3. The method according to claim 2, wherein the PNI-NPN is further identified by a Public Area Mobile Network (PLMN) and the CAG.

4. The method according to claim 2, wherein the SNPN is further identified by a Public Area Mobile Network (PLMN) and the NID.

5. The first communication network is PNI-NPN, The second communication network is the first communication network. The method according to claim 1.

6. The first communication network is an NPN, The second communication network described above, PLMN, SNPN, and PNI-NPN comprising at least one of the following: The method according to claim 1.

7. The first communication network is a public network, The second communication network described above, SNPN, and PNI-NPN comprising at least one of the following: The method according to claim 1.

8. Determining the aforementioned MDT settings is Core network (CN) nodes within PLMN, Operation, management, and maintenance (OAM) within PLMN, CN nodes within SNPN, and OAM within SNPN This includes receiving the MDT settings from a second network node having at least one of the following: The method according to claim 1.

9. The method according to claim 1, wherein the MDT setting includes an indication that a communication device reports the collected MDT measurements as the MDT measurements are collected.

10. The method according to claim 1, wherein the MDT setting includes an indication that a communication device records the collected MDT measurements as the MDT measurements are collected.

11. Setting up the aforementioned communication device Initial context setup request, Handover requests, and Route switching request acknowledgment This includes transmitting the MDT settings as part of at least one of the following: The method according to claim 1.

12. The aforementioned communication device is operating in dual connectivity mode. Configuring the communication device includes transmitting the MDT settings for both the master node (MN) and the secondary node (SN) to at least one of the MN and the SN in order to configure the communication device. The method according to claim 1.

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

14. The method according to claim 12, wherein the first cell operates within an SN as the MN, and the second cell operates within a PNI-NPN as the SN.

15. Receiving the MDT measurement value from the communication device (2330) The method according to claim 1, further comprising:

16. Transmitting the MDT measurement value to the second communication network (2340) The method according to claim 15, further comprising:

17. Receiving the MDT measurement value from the second communication network (2330) The method according to claim 1, further comprising:

18. A method for operating a core network (CN) node, wherein the method is Transmitting the Minimize Test Time (MDT) setting to a Wireless Access Network (RAN) node (2310), wherein the MDT setting is Public Network Integrated Non-Public Network (PNI-NPN), and A standalone non-public network (SNPN) that is identified by network identification information (NID). To transmit a Minimize Test (MDT) setting for the operational test, which includes the region range identified by at least one of the (2310) Methods that include...

19. A network node (2600) operating within a communication network, wherein the network node is Processing circuit (2602), A memory (2604) coupled to the processing circuit, which stores instructions that can be executed by the processing circuit to cause the network node to perform the method described in any one of claims 1 to 18, and A network node (2600) equipped with the following.

20. A computer program comprising program code to be executed by a processing circuit (2602) of a network node (2600) operating within a communication network, wherein the execution of the program code causes the network node to execute the method described in any one of claims 1 to 18.

21. A computer program product comprising a non-temporary storage medium (2604) containing program code to be executed by a processing circuit (2602) of a network node (2600) operating within a communication network, wherein the execution of the program code causes the network node to execute the method according to any one of claims 1 to 18.

22. A non-temporary computer-readable medium storing instructions that can be executed by a processing circuit (2602) of a network node (2600) operating in a communication network, causing the network node (2600) to perform the method according to any one of claims 1 to 18.

Images