Minimization of drive test configuration range for different network types

Abstract

For example, a radio access network ("RAN") node may determine (2310) a Minimization of Drive Tests ("MDT") configuration comprising a range of areas associated with a cell identified by at least one of: a Public Network Integrated Non-Public Network ("PNI-NPN"); a stand-alone non-public network ("SNPN"); and a Public Land 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 a second communication network.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to minimizing drive test configuration ranges for different network types. Background Art

[0002] Figure 1 An example of a new radio (“NR”) network (e.g., a fifth generation (“5G”) network) is shown, including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base stations (“gNBs”)), and multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] A non-public network ("NPN") is a feature that allows a network to be deployed and / or managed by an entity other than a normal operator. The "normal operator" here is assumed to be the operator of one or more public land mobile networks ("PLMNs"). It should be noted that a PLMN also has an identifier called a PLMN identifier ("ID") or sometimes 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 minimization of drive tests ("MDT") configuration, the MDT configuration including an area scope that identifies at least one of: an identification of a public network integrated non-public network ("PNI-NPN"); an identification of a stand-alone non-public network ("SNPN"); and an identification of a public land mobile network ("PLMN"). The method may also include: configuring a communication device served by a first cell in a first communication network with the MDT configuration to instruct the communication device to collect MDT measurements from a second cell in a second communication network.

[0005] According to other embodiments, a method of operating a core network ("CN") node is provided. The method includes: sending a minimization of drive tests ("MDT") configuration to a radio access network ("RAN") node. The MDT configuration includes an area scope that identifies at least one of: an identification of a public network integrated non-public network ("PNI-NPN"); an identification of a stand-alone non-public network ("SNPN"); and an identification of a public land 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-transitory computer-readable medium, a system or a host is provided to implement one of the above methods.

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

[0008] It is not obvious to add the NPN identifier to the list of networks for which the MDT configuration is valid. The reason why this is not obvious is that a private network is a network separated from a PLMN. For example, a SNPN should not be connected to a PLMN or a PNI NPN. In addition, a UE according to the current specification is not allowed to implement mobility between a SNPN and other networks different from the SNPN. Currently, the MDT configuration can only be applied to the UE within a set of PLMNs that are equivalent to each other and include the registered PLMN for the UE. Therefore, it is not obvious to extend the regional scope of the MDT configuration to the NPN, because it means coordination and agreement between the NPN operator and the PLMN operator. However, the advantage of this configuration is that for UEs that can move between NPN and PLMN, the operator (PLMN or NPN operator) can configure MDT measurements at the UE, and by receiving these measurements, it can monitor several aspects involving PLMN and NPN in a consistent manner. In some examples, the operator can monitor the coverage at the NPN and PLMN and the coverage at the coverage boundary between the PLMN and the NPN. This ensures that the convergence between different networks is consistent and that the mobility between different networks will not fail due to poor coverage. In an additional or alternative example, the operator can monitor the performance at the radio and service level for UEs moving between PLMNs and NPNs. This allows the operator to optimize the guidance of UEs to coverage locations with the best service for a particular service, as well as optimize service coverage in places with poor performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings illustrate certain non-limiting embodiments of the inventive concept, and are included to provide a further understanding of the present disclosure, and are incorporated into and constitute a part of this application. In the drawings:

[0010] Figure 1 is a schematic diagram illustrating an example of a fifth generation ("5G") network;

[0011] Figure 2 is a signal flow diagram illustrating an example of successful operation of initial context setup;

[0012] Figure 3 is a signal flow diagram illustrating an example of successful operation of switching resource allocation;

[0013] Figure 4 is a signal flow diagram illustrating an example of successful operation of trace start;

[0014] Figure 5 is a table showing an example of tracking activation IE;

[0015] Figure 6 is a table showing an example of an MDT Configuration IE;

[0016] Figure 7 is a table showing an example of an MDT PLMN List IE;

[0017] Figure 8 is a table showing examples of range boundaries for an MDT PLMN list;

[0018] Fig. 9 is a table showing an example of MDT configuration NRIE;

[0019] Fig.10 is a table showing an example of the range boundaries of MDT configuration NRs;

[0020] Fig.11 is a table showing an example of the area range IE of a neighboring cell;

[0021] Fig.12 is a table showing examples of range boundaries of area ranges of neighboring cells;

[0022] Fig.13 is a schematic diagram illustrating an example of a communication device moving in and out of a PN / NPN according to some embodiments;

[0023] Fig.14 is a schematic diagram illustrating an example of a communication device moving within a PN / NPN according to some embodiments;

[0024] Fig.15 is a table showing an example of an MDT Configuration NR IE according to some embodiments;

[0025] Fig.16 is a table showing an example of range boundaries for MDT configuration NRs according to some embodiments;

[0026] Fig.17 is a table showing an example of an MDT PLMN List IE according to some embodiments;

[0027] Fig.18 is a diagram showing some embodiments of the present invention. Fig.17 A table of examples of scope boundaries of an MDT PLMN list;

[0028] Fig.19 is a table showing an example of a Cell NID Information IE according to some embodiments;

[0029] Fig. 20 is a table showing an example of an MDT NPN List IE according to some embodiments;

[0030] Fig.21 is a table showing an example of an area range IE of a neighboring cell according to some embodiments;

[0031] Fig. 22 is a table showing another example of an MDT Configuration NR IE according to some embodiments;

[0032] Fig.23 is a flow chart illustrating an example of operations performed by a network node according to some embodiments;

[0033] Fig.24 is a block diagram of a communication system according to some embodiments;

[0034] Fig.25 is a block diagram of a user equipment according to some embodiments;

[0035] Fig.26 is a block diagram of a network node according to some embodiments;

[0036] Fig. 27 is a block diagram of a host computer in communication with a user device according to some embodiments;

[0037] Fig.28 is a block diagram of a virtualization environment according to some embodiments; and

[0038] Fig.29 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION

[0039] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, wherein examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that this disclosure will be thorough and complete, and the scope of the inventive concept will be fully conveyed to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be defaulted to being present / used in another embodiment.

[0040] There are two types of NPN networks, stand-alone NPN ("SNPN") and public network integrated NPN ("PNI-NPN"), which are described below.

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

[0042] SNPN is a type of NPN that is made up 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 the PLMN. For example, it could be a company that owns a factory and deploys a network inside and outside the factory to serve its employees and machines, etc.

[0043] An entity that owns a SNPN does not necessarily own its own PLMN. A SNPN network has an identifier that includes a PLMN identifier and a network identifier ("NID"). As described above, an entity that owns / manages a SNPN may not have its own PLMN identifier. However, since the SNPN includes a PLMN, one way for a SNPN network owner to obtain a SNPN identifier is to sign an agreement with a PLMN operator so that they can use the operator's PLMN. Another method is to use a "virtual" (e.g., "special," "non-normally used," "invalid," or similar) PLMN as part of the SNPN's identifier.

[0044] The PNI-NPN feature is another type of NPN. Similar to SNPN, PNI-NPN can be deployed to provide services to a specific group of users, such as to employees and machines of a company. The main difference between SNPN and PNI-NPN is that PNI-NPN is integrated into the PLMN. Therefore, PNI-NPN can be managed by the operator of the PLMN in which the PNI-NPN is integrated.

[0045] The PNI-NPN has an identifier called a Closed Access Group ("CAG") instead of the NID identifier used by the SNPN. A CAG is associated with each cell that forms the PNI-NPN. UEs that are employees, machines, and the like of a company that should be given access to the PNI-NPN are configured with the associated CAG. Other UEs cannot access the PNI-NPN and are not configured to use the CAG. In general, when determining whether a UE can connect to a PNI-NPN by checking whether the UE is configured with a CAG, both the UE and the network are performing checks, and the UE is only given access to the PNI-NPN if the UE is configured with a CAG.

[0046] The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG-RAN node when needed, including protocol data unit ("PDU") session context, security keys, mobility restriction list, UE radio capabilities and UE security capabilities, etc. The Access and Mobility Management Function ("AMF") may initiate the Initial Context Setup procedure if there is a logical NG connection associated with the UE for the UE, or if the AMF has received the RAN UE NGAP ID IE in the INITIAL UE MESSAGE, or if the NG-RAN node has initiated a logical NG connection associated with the UE by sending an INITIAL UE MESSAGE via another NG interface instance. The procedure may be performed using a protocol data unit ("PDU") session context, security keys, mobility restriction list, UE radio capabilities and UE security capabilities, etc. Figure 2 Signaling associated with the UE is shown.

[0047] For signalling-only connections, and if no UE Context Request IE is received in the initial UE message, then the AMF may be configured to trigger this procedure for all NAS procedures, or on a per NAS procedure basis, depending on the operator's configuration.

[0048] In the case of establishing a PDU session, the 5GC shall be ready to receive user data before receiving the INITIAL CONTEXT SETUP RESPONSE message by the AMF. If there is no logical NG connection associated with the UE, a logical NG connection associated with the UE shall be established upon receiving the INITIAL CONTEXT SETUP REQUEST message.

[0049] The Initial Context Setup Request message shall contain the index for the RAT / Frequency Selection Priority IE (if available in the AMF).

[0050] If the NAS-PDU IE is included in the Initial Context Setup Request message, the NG-RAN node shall pass it transparently to the UE.

[0051] If the Masked IMEISV IE is included in the Initial Context Setup Request message, the target NG-RAN node SHOULD (if supported) use it to determine the characteristics of the UE for subsequent processing.

[0052] Upon receipt of the Initial Context Setup Request message, the NG-RAN node shall: attempt to perform the requested PDU Session Configuration; store the received UE aggregate maximum bit rate in the UE context and use the received UE aggregate maximum bit rate for the non-GBR QoS flows of the associated UE as specified in TS23.501; store the received mobility restriction list in the UE context; store the received UE radio capabilities in the UE context; store the received index for RAT / frequency selection priority in the UE context and use it as defined in TS23.501; store the received UE security capabilities in the UE context; store the received security key in the UE context and use it if the NG-RAN node is required to activate security for the UE; if supported, store the received SRVCC operation possibly in the UE context and use it as defined in TS23.216; if supported, store the received NRV2X service authorization information in the UE context; if supported, the V2X service authorization information is stored in the UE context; if supported, the received NR UE side link aggregate maximum bit rate is stored in the UE context and used for sidelink communications of the associated UE in network scheduling mode for NR V2X services; if supported, the received LTE UE side link aggregate maximum bit rate is stored in the UE context and used for sidelink communications of the associated UE in network scheduling mode for LTE V2X services; if supported, the received PC5 QoS parameters are stored in the UE context and used as defined in TS23.287; if supported, the received management-based MDT PLMN list information is stored in the UE context; if supported, the received IAB authorization information is stored in the UE context; if supported, the received 5G ProSe authorization information is stored in the UE context and used for sidelink communications of the associated UE in network scheduling mode for 5G ProSe services; if supported, the 5G ProSe UE PC5 aggregate maximum bit rate is stored in the UE context and used for sidelink communications of the associated UE in network scheduling mode for 5G ProSe services; and if supported, the 5G ProSe PC5 The QoS parameters are stored in the UE context and used as defined in TS 23.304.

[0053] If the Mobility Restriction List IE is not included in the Initial Context Setup Request message, the NG-RAN node shall assume that no roaming and no access restrictions apply to the UE. The NG-RAN node shall also assume that no roaming and no access restrictions apply to the UE when one of the QoS flows includes a specific ARP value (TS 23.501).

[0054] If the Trace Activation IE is included in the Initial Context Setup Request message, the NG-RAN node shall (if supported) enable the requested tracing functionality as described in TS 32.422. In particular, if supported, the NG-RAN node shall: if the Trace Activation IE includes an MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422; if the Trace Activation IE includes an MDT Activation IE set to "Immediate MDT Only", "Logged MDT Only", initiate the requested MDT session as described in TS 32.422, and the NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE for tracing; if the Trace Activation IE includes an MDT Location Information IE within the MDT Configuration IE, store the information and take the information into account in the requested MDT session; if the Trace Activation IE includes a Signaling Based MDT PLMN List within the MDT Configuration IE, PLMN List) IE, the NG-RAN node may use it to propagate the MDT configuration as described in TS 37.320; if the trace activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, it is considered for the MDT configuration as described in TS 37.320; if the trace activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, it is considered for the MDT configuration as described in TS 37.320; if the trace activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, it is considered for the MDT configuration as described in TS 37.320; if the trace activation IE includes the MDT Configuration IE, and if the NG-RAN node is a gNB, at least the MDT Configuration NR (MDT Configuration-NR) IE shall be present, and if the NG-RAN node is an ng-eNB, at least the MDT Configuration EUTRA (MDT Configuration-EUTRA) IE shall be present.

[0055] The handover resource allocation is described below.

[0056] The purpose of the handover resource allocation procedure is to reserve resources at the target NG-RAN node for the handover of the UE. Figure 3 Signaling associated with the UE is performed as shown.

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

[0058] If the Trace Activation IE is included in the Handover Request message, the target NG-RAN node shall (if supported) start the requested tracing functionality as described in TS 32.422. In particular, if supported, the NG-RAN node shall: if the Trace Activation IE includes an MDT Activation IE set to "Immediate MDT and Tracing", initiate the requested trace session and MDT session as described in TS 32.422; if the Trace Activation IE includes an MDT Activation IE set to "Immediate MDT Only", "Logged MDT Only", initiate the requested MDT session as described in TS 32.422, and the target NG-RAN node shall ignore the Interface IE for Tracing and the Trace Depth IE; if the Trace Activation IE includes an MDT Location Information IE within the MDT Configuration IE, store the information and take it into account in the requested MDT session; if the Trace Activation IE includes a Signaling-based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT configuration as described in TS 37.320; if the trace activation IE includes the Bluetooth measurement configuration IE within the MDT configuration IE, it is considered for MDT configuration as described in TS 37.320; if the trace activation IE includes the WLAN measurement configuration IE within the MDT configuration IE, it is considered for MDT configuration as described in TS 37.320; if the trace activation IE includes the sensor measurement configuration IE within the MDT configuration IE, it is considered for MDT configuration as described in TS 37.320; if the trace activation IE includes the MDT configuration IE, and if the NG-RAN node is a gNB, at least the MDT configuration NR IE should be present, and if the NG-RAN node is an ng-eNB, at least the MDT configuration EUTRA IE should be present.

[0059] If the Location Reporting Request Type IE is included in the Handover Request message, the target NG-RAN node shall implement the requested location reporting functionality for the UE as described in subclause 8.12.

[0060] The purpose of the Trace Start procedure is to allow the AMF to request the NG-RAN node to initiate a trace session for the UE. Figure 4 Signaling associated with the UE is shown. If no logical NG connection associated with the UE exists, a logical NG connection associated with the UE should be established as part of the process.

[0061] The AMF initiates the process by sending a TRACE START message. Upon receipt of the TRACE START message, the NG-RAN node shall initiate the requested trace session as described in TS 32.422.

[0062] If the Trace Activation IE is included in the Trace Start message, which includes the MDT Activation IE set to "MDT and Trace Immediately", the NG-RAN node shall (if supported) initiate the requested trace session and MDT session as described in TS 32.422.

[0063] If the Trace Activation IE is included in the Trace Start message, which includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT Only", the NG-RAN node shall (if supported) initiate the requested MDT session as described in TS 32.422, and the NG-RAN node shall ignore the Interface IE for Tracing and the Trace Depth IE.

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

[0065] If the Trace Activation IE is included in the Trace Start message, which includes the MDT Activation IE set to "MDT Immediate Only", "MDT Logged Only", and if the Signaling Based MDT PLMN List IE is included in the MDT Configuration IE, the NG-RAN node can use it to propagate the MDT configuration as described in TS 37.320.

[0066] If the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node SHOULD (if supported) consider it for MDT configuration as described in TS 37.320.

[0067] If the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node shall (if supported) consider it for MDT configuration as described in TS 37.320.

[0068] If the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, the NG-RAN node SHOULD (if supported) consider it for MDT configuration as described in TS 37.320.

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

[0070] Figure 5 An example of a trace activation IE defining parameters related to trace session activation is shown.

[0071] Figure 6 An example of an MDT configuration IE defining MDT configuration parameters is shown.

[0072] Figure 7 An example of an MDT PLMN List IE providing a list of PLMNs allowed for MDT is shown. Figure 8 An example of the scope boundary of the MDT PLMN List IE is shown.

[0073] Fig. 9 An example of an MDT Configuration NR IE defining MDT configuration parameters for NR is shown.

[0074] Fig.10 An example of the scope boundary of the MDT configuration NRIE is shown.

[0075] Fig.11 An example of a Neighbor Cell Area Range IE is shown, which defines the area range of neighbor cells for logged MDT. Fig.12 An example of a range boundary of an Area Range IE of a neighboring cell is shown.

[0076] Certain challenges currently exist. In some examples, problems have been identified with existing solutions in MDT configuration collection in terms of flexibility with respect to MDT measurement scope (which only supports MDT configuration collection in public networks).

[0077] In addition, the UE may access and subscribe to several networks or different network types (e.g., SNPN, PNI-NPN, and PLMN). In addition, if the UE is capable of having services that require a specific subscription for registration, the UE may implement registration on a private network (e.g., SNPN). Generally speaking, a UE is successfully registered on a private network (e.g., SNPN) if (1) the UE has found a suitable cell for the SNPN to reside in; and (2) the registration from the UE has been accepted in the registration area of ​​the cell in which the UE resides. Currently, there is no support in the technical specifications for MDT configuration for private networks. This means that the RAN cannot know whether the MDT measurements collected by the UE can also be collected on the NPN network. This may cause many problems, such as: (1) lack of MDT measurement continuity when the UE moves from a PLMN to an NPN and vice versa; and (2) lack of MDT measurement collection when the UE attaches within an NPN and moves to RRC_Connected.

[0078] The above problem also means that network operators of private networks cannot collect MDT-related information via UEs connecting / moving to other networks. From the perspective of UEs served by neighboring NPN cells, such UEs can provide measurements on the operator's PLMN cells. Such measurements are beneficial because they allow optimization of coverage and performance within the PLMN.

[0079] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. In some embodiments, a first network node (e.g., an AMF / OAM of a network) may send an MDT configuration to a RAN node, wherein the MDT configuration includes an area scope that identifies at least one of the following networks. The information includes one or more of the following: (1) an identifier of a PNINPN; (2) an identifier associated with a SNPN; (3) the identifier may include at least a list of NPN PLMNs, CAG IDs, and NIDIDs; and (4) an identifier associated with a public network (PLMN).

[0080] In some examples, where the MDT configuration generated by the first network node includes an area scope spanning PN and NPN networks, the first network node (eg, AMF / OAM) implements operations.

[0081] In some examples, the operations include configuring corresponding MDT measurement configurations for a second network node operating in a first network (NPN) (ie, PNI-NPN and / or SNPN) for a specific UE registered in the first network (NPN) and moving between first and second network coverages.

[0082] In an additional or optional example, the operations include, for a specific UE registered in a second network (PN) and moving between first and second network coverage, configuring a corresponding MDT measurement configuration for a third network node operating in other PLMNs associated with the PN.

[0083] In an additional or optional example, the operation includes: for a specific UE registered in the second network (PN) and moving between the first and second network coverage, configuring a corresponding MDT measurement configuration for a second network node operating in an NPN (i.e., PNI-NPN and / or SNPN).

[0084] In an additional or optional example, the operations include, for a specific UE registered in the first network (NPN) and moving between the first and second network coverages, configuring a corresponding MDT measurement configuration for a third network node operating in other PLMNs associated with the PN.

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

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

[0087] In an additional or optional example, the operation includes: for a specific UE registered in two (first and second) networks, configuring corresponding MDT measurements for a second network node that acts as a SN as a dual connectivity configuration and a third network node that operates as a master node MN in other PLMNs associated with the PN.

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

[0089] Herein, the terms non-public network / private network ("NPN") and stand-alone NPN ("SNPN") / public network integrated NPN ("PNI-NPN") nodes may be used interchangeably. In some examples, the PNI-NPN network herein covers scenarios when a cell advertises a public land mobile network ("PLMN") + closed access group ("CAG") in the NPN identity in the system information block 1 ("SIB1").

[0090] The SNPN network in this article covers the scenario when the cell announces the PLMN+network identity ("NID") in the NPN identity in SIB1.

[0091] For management-based minimization of drive tests (“MDT”), a core network (“CN”) indicates to a radio access network (“RAN”) node whether to allow MDT to be configured for each connected user equipment (“UE”) (also referred to herein as a communication device) by the RAN node, by providing a management-based MDT PLMN list for each UE.

[0092] For signaling-based MDT, by providing a signaling-based MDT PLMN list for each UE, the CN indicates to the RAN node whether to allow the RAN node to configure MDT for each connected UE.

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

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

[0095] In an additional or optional embodiment, the operation is performed by a first network node (e.g., an access and mobility management function ("AMF") / operation, administration, and maintenance ("OAM") of the network) to send an MDT configuration to a RAN node, the MDT configuration including an area scope identifying at least one network. The information includes one or more of the following: (1) an identification of a PNI NPN (public network integrated NPN); (2) an identification associated with a SNPN (standalone NPN); (3) an identification that may include at least a list of NPN PLMNs, CAGIDs, and NID IDs; and (4) an identification associated with a public network (PLMN).

[0096] The cross-network type configuration is described below.In some embodiments, operations are performed at a first network node operating in one network to configure corresponding measurements and reporting for a second network node (eg, a private network / NPN for UEs registered only in the first network).

[0097] Fig.13 An example of a UE moving into and out of a second network (shaded area) is shown.

[0098] Fig.14 An example of a UE moving within a second network (shadow) is shown.

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

[0100] In an additional or alternative embodiment, the first node signals an MDT configuration for signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the PNI-NPN with a corresponding MDT measurement configuration that will also be collected from cells belonging to the second network node in the SNPN.

[0101] In an additional or alternative embodiment, the first node signals an MDT configuration for signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the PNI-NPN with a corresponding MDT measurement configuration that will also be collected from cells belonging to the second network node in other PNI-NPNs.

[0102] In an additional or optional embodiment, the first node signals an MDT configuration for a signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the SNPN with a corresponding MDT measurement configuration to be collected exclusively by a cell belonging to a second network node in the PNI-NPN or to be additionally collected from a cell belonging to a second network node in the PNI-NPN.

[0103] In an additional or optional embodiment, the first node signals an MDT configuration for a signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the SNPN with a corresponding MDT measurement configuration that will be collected exclusively by a cell belonging to a second network node in other SNPNs or with a corresponding MDT measurement configuration that will be collected additionally from a cell belonging to a second network node in other SNPNs.

[0104] In an additional or optional embodiment, the first node signals an MDT configuration for a signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the SNPN with a corresponding MDT measurement configuration to be collected exclusively by a cell belonging to a second network node in a public network or to be collected additionally from a cell belonging to a second network node in a public network.

[0105] In an additional or alternative embodiment, the first node signals an MDT configuration for signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the public network with a corresponding MDT measurement configuration to be collected exclusively by a cell belonging to a second network node in the PNI-NPN or to be collected additionally from a cell belonging to the second network node in the PNI-NPN.

[0106] In an additional or optional embodiment, the first node signals an MDT configuration for a signaling-based or management-based MDT to allow the RAN node to configure at least one UE served by a cell in the public network with a corresponding MDT measurement configuration to be collected exclusively by a cell belonging to a second network node in the SNPN or to be additionally collected from a cell belonging to a second network node in the SNPN.

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

[0108] In an additional or alternative embodiment, if the MDT configuration is for immediate MDT, the UE collects MDT measurements and reports them immediately to the serving network. The serving network may forward the measurements to a system (eg, an OAM system) that analyzes the measurements.

[0109] In an additional or alternative embodiment, if the MDT is configured for logged MDT, the UE logs the MDT measurements and reports them to the serving network at the time of the logged report. The serving network may forward the measurements to a system (eg, an OAM system) that analyzes the measurements.

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

[0111] An implementation example is described below.

[0112] In some embodiments, if a serving cell associated with a private network (eg, SNPN) and a PNI-NPN is part of an MDT configured NR, the CN requests the network node to configure a specific UE with MDT measurement related information. Figure 15 to Figure 16 An implementation example is given in .

[0113] Fig.15 An example of an MDT Configuration NR IE defining MDT configuration parameters for NR is shown.

[0114] Fig.16 An example of the scope boundary of the MDT configuration NR is shown.

[0115] In an additional or alternative embodiment, the CN requests the network node to configure a specific UE with MDT measurement related information: PLMN and NPN list for signaling based MDT. Figure 17 to Figure 18 An implementation example is given in .

[0116] Fig.17 An example of an MDT PLMN List IE providing a list of PLMN identities allowed for MDT is shown.

[0117] Fig.18 An example of the scope boundary of the MDT PLMN list is shown.

[0118] In an additional or optional embodiment, for signaling-based MDT, Figure 19 to Figure 20 An implementation example is shown which may be optionally added to the following messages: INITIAL CONTEXT SETUP REQUEST; HANDOVER REQUEST; or PATH SWITCH REQUEST ACKNOWLEDGE.

[0119] Fig.19 An example of an MDT NPN List IE providing a list of NPN identities allowed for MDT is shown.

[0120] Fig. 20 An example of a range boundary of an MDT NPN list is shown.

[0121] In an additional or optional embodiment, an alternative implementation of signaling-based MDT is to add a flag indicating that the neighboring NR physical cell ID belongs to the NPN network, such as Fig.21 shown.

[0122] Embodiments within an NPN configuration are described below.

[0123] In some embodiments, operations are performed at a first network node operating in a private network / NPN to configure corresponding MDT measurements for a second network node located in the same network as the first network node.

[0124] In an additional or alternative embodiment, the CN in the SNPN signals a trace-based message for a specific UE to allow the RAN node to configure at least one UE served by a cell in the SNPN with a corresponding MDT measurement configuration for cells belonging to the same SNPN.

[0125] In an additional or alternative embodiment, the CN in the PNI-NPN signals a trace-based message for a specific UE to allow the RAN node to configure at least one UE served by the cell PNI-NPN with a corresponding MDT measurement configuration for cells belonging to the same PNI-NPN.

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

[0127] Fig. 22 An additional or alternative example of an MDT Configuration NR IE defining MDT configuration parameters for NR is shown.

[0128] A dual network connection configuration is described below.

[0129] In some embodiments, operations are implemented in dual connectivity ("DC") operations (operating as a primary node ("MN") at a first network and as a secondary node ("SN") at a second network) for a particular UE. The UE is registering in both networks (first and second). In the MR-DC scenario: (a) a cell operating as a MN in a public network and a cell operating as a SN in a PNI-NPN, and vice versa; (b) a cell operating as a MN in a public network and a cell operating as a SN in a SNPN, and vice versa; and (c) a cell operating as a MN in a SNPN and a cell operating as a SN in a PNI-NPN, and vice versa.

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

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

[0132] In an additional or optional embodiment, the second network forwards the associated MDT configuration to the first network, requesting the first network to perform MDT-related configuration.

[0133] In an additional or alternative embodiment, after the first network receives the measurement results, the first network forwards the associated measurement results to the second network (if the corresponding measurement results for each network are not reported separately).

[0134] In an additional or alternative embodiment, after the second network receives the measurement results, the first network forwards the associated measurement results to the first network (if the corresponding measurement results for each network are not reported separately).

[0135] In the following description, although the network node may be any one of the hub 2414, the network nodes 2410A-B, the core network node 2408, the network node 2600, the virtualized hardware 2804, the virtual machines 2808A, 2808B, or the network node 2904, the network node 2600 should be used to describe the functionality of the operation of the network node. Reference will now be made to some embodiments of the inventive concept. Fig.23 The operation of network node 2600 is discussed in detail with reference to the flowchart of FIG. Fig.26 For example, the modules can be stored in Fig.26 The modules are stored in the memory 2604, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding network node processing circuit 2602, the processing circuit 2602 implements the corresponding operations of the flowchart.

[0136] Fig.23 Operations performed by a network node are shown.

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

[0138] In some embodiments, the area scope identifies at least one of: an identification of a PNI-NPN; an identification of a SNPN; and an identification of a PLMN. In some examples, the identification of the PNI-NPN includes a CAG. In additional or optional examples, the identification of the SNPN includes a NID.

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

[0140] In an additional or alternative embodiment, the MDT configuration includes an indication that the communications device reports the collected MDT measurements when the MDT measurements are collected.

[0141] In an additional or alternative embodiment, the MDT configuration includes an indication that the communications device logs the collected MDT measurements when the MDT measurements are collected.

[0142] In additional or alternative embodiments, configuring the communication device includes: sending the MDT configuration as part of at least one of: an initial context setup request; a handover request; and a path switch request acknowledgement.

[0143] In an additional or optional embodiment, the communication device operates in dual connectivity. Configuring the communication device includes: sending an MDT configuration for both a master node MN and a secondary node SN to at least one of the MN and the SN. In some examples, the first cell operates as a MN in a public network and the second cell operates as a SN in an NPN. In an additional or optional example, the first cell operates as a MN in an SNPN and the second cell operates as a SN in a PNI-NPN.

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

[0145] At block 2340, the processing circuit 2602 sends the MDT measurements via the communication interface 2606. In some embodiments, the MDT measurements are sent to the second communication network.

[0146] For some embodiments, Fig.23 Various operations shown in may be optional.

[0147] Fig.24 An example of a communication system 2400 is shown in accordance with some embodiments.

[0148] In this example, the communication system 2400 includes a telecommunications 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 generally referred to as network nodes 2410), or any other similar third generation partnership project (3GPP) access node or non-3GPP access point. In addition, as will be appreciated by those skilled in the art, the network node 2410 is not necessarily limited to an implementation in which the radio portion and the baseband portion are provided and integrated by a single vendor. Therefore, it should be understood that the network node 2410 may include a decomposed implementation or part thereof. For example, in some embodiments, the telecommunications network 2402 includes one or more open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunications network 2402 that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate alone or in conjunction with other nodes to implement one or more functions of any node in the telecommunications network 2402, including one or more network nodes 2410 and / or core network nodes 2408.

[0149] Examples of ORAN network nodes include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near real-time or non-real-time) hosting software or software plug-ins, such as a near real-time RAN control application (e.g., xApp) or a non-real-time RAN automation application (e.g., rApp), or any combination thereof (the adjective "open" indicates support for ORAN specifications). The network node can support the specifications by, for example, supporting interfaces defined by the ORAN specifications, such as A1, F1, W1, E1, E2, X2, Xn interfaces, open fronthaul user plane interfaces, or open fronthaul management plane interfaces. The intent and content-aware notifications described herein can be communicated from a 3GPP network node or an ORAN network node through 3GPP defined interfaces (e.g., N2, N3) and / or ORAN Alliance defined interfaces (e.g., A1, O1). In addition, an ORAN network node can be a logical node in a physical node. In addition, the ORAN network node can be implemented in a virtualized environment (described further below) in which one or more network functions are virtualized. For example, the virtualized environment can include an O-Cloud computing platform orchestrated by a service management and orchestration framework via an O-2 interface defined by the O-RAN Alliance. The network node 2410 facilitates direct or indirect connection of user equipment (UE), such as connecting wireless devices 2412a, 2412b, 2412c, and 2412d (one or more of which may be generally referred to as UE 2412) to the core network 2406 via one or more wireless connections. The network node 2410 facilitates direct or indirect connection of user equipment (UE), such as connecting UE 2412a, 2412b, 2412c, and 2412d (one or more of which may be generally referred to as UE 2412) to the core network 2406 via one or more wireless connections.

[0150] Example wireless communications over wireless connections include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transferring information without the use of wires, cables, or other material conductors. Additionally, in various 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 may facilitate or participate in the communication of data and / or signals, whether over a wired or wireless connection. The communication system 2400 may include and / or interface to any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.

[0151] UE 2412 can be any of a variety of communication devices, including wireless devices arranged, configured and / or operable to communicate wirelessly with network node 2410 and other communication devices. Similarly, network node 2410 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 2412 and / or with other network nodes or devices in telecommunication network 2402 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management in telecommunication network 2402.

[0152] In the depicted example, the core network 2406 connects the network node 2410 to one or more hosts, such as the host 2416. These connections may be direct or may be indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 2406 includes one or more core network nodes (e.g., core network node 2408) constructed with hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, network node, and / or host, so that the description thereof is generally applicable to the corresponding components of the core network node 2408. The example core network node includes a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection agent (SEPP), a network open function (NEF), and / or a user plane function (UPF) One or more functions.

[0153] The host 2416 may be owned or controlled by a service provider other than the operator or provider of the telecommunications network 2402 and / or the access network 2404, and may be operated by or on behalf of the service provider. The host 2416 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services such as retrieving and compiling data of various environmental conditions detected by multiple UEs, analytical functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions implemented by a server.

[0154] Overall, Fig.24The communication system 2400 enables connections between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standards (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low power wide area network (LPWAN) standards such as LoRa and Sigfox.

[0155] In some examples, telecommunication network 2402 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 2402 can support network slicing to provide different logical networks to different devices connected to telecommunication network 2402. For example, telecommunication network 2402 can provide ultra-reliable low-latency communication (URLLC) services to some UEs, enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine type communication (mMTC) / massive IoT services to other UEs.

[0156] In some examples, UE 2412 is configured to send and / or receive information without direct human interaction. For example, the UE can be designed to send information to access network 2404 according to a predetermined schedule when triggered by an internal or external event, or in response to a request from access network 2404. In addition, the UE can be configured to operate in a single RAT or multi-RAT or multi-standard mode. For example, the UE can operate using any one or a combination of WiFi, NR (New Radio) and LTE, that is, configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0157] In this example, the hub 2414 communicates with the access network 2404 to facilitate indirect communication between one or more UEs (e.g., UE 2412c and / or 2412d) and a network node (e.g., network node 2410b). In some examples, the hub 2414 may be a controller, a router, a content source and analysis, or any other communication device described herein with respect to the UE. For example, the hub 2414 may be a broadband router that enables the UE to access the core network 2406. As another example, the hub 2414 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 2410, or may be received by an executable code, a script, a process, or other instructions in the hub 2414. As another example, the hub 2414 may be a data collector that acts as a temporary storage for UE data, and in some embodiments, analysis or other processing of the data may be implemented. As another example, the hub 2414 may be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the hub 2414 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 2414 provides it directly to the UE, provides it to the UE after implementing local processing, and / or provides it to the UE after adding additional local content. In another example, the hub 2414 acts as a proxy server or orchestrator for the UE, especially when one or more UEs are low-energy IoT devices.

[0158] Hub 2414 can have constant / persistent or intermittent connection to network node 2410b. Hub 2414 can also allow different communication schemes and / or scheduling between hub 2414 and UE (such as UE 2412c and / or 2412d) and hub 2414 and core network 2406. In other examples, hub 2414 is connected to core network 2406 and / or one or more UE via wired connection. In addition, hub 2414 can be configured to be connected to M2M service provider and / or connected to another UE by direct connection through access network 2404. In some scenes, UE can establish wireless connection with network node 2410, while still connected via hub 2414 by wired or wireless connection. In some embodiments, hub 2414 can be a dedicated hub, that is, its main function is to route communication from network node 2410b to UE or from UE to the hub of network node 2410b. In other embodiments, the hub 2414 may be a non-dedicated hub, ie, a device operable to route communications between the UE and the network node 2410b, but which is also operable as a communications origin and / or destination for a particular data channel.

[0159] Fig.25 UE 2500 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular 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 devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, notebook computers, notebook embedded devices (LEEs), notebook mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted or vehicle-mounted embedded / integrated wireless devices, etc. 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.

[0160] A UE may support device-to-device (D2D) communications, such as by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user owning and / or operating an associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but may not be associated with a specific human user (e.g., a smart sprinkler controller), or may not initially be associated with one. Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart meter).

[0161] UE 2500 includes processing circuit IQ 202, which is operatively coupled to input / output interface 2506, power supply 2508, memory 2510, communication interface 2512 and / or any other components, or any combination thereof, via bus 2504. Some UEs may utilize Fig.25 All or a subset of the components shown in . The level of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0162] The processing circuit 2502 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 2510 as a machine-readable computer program. The processing circuit 2502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 2502 may include multiple central processing units (CPUs).

[0163] In this example, the input / output interface 2506 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 2500. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide input devices and output devices.

[0164] In some embodiments, the power supply 2508 is configured as a battery or a battery pack. Other types of power supplies may be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. The power supply 2508 may also include a power supply circuit for delivering power from the power supply 2508 itself and / or an external power supply to the various components of the UE 2500 through an input circuit or an interface such as a power cable. For example, the delivered power may be used to charge the power supply 2508. The power supply circuit may implement any formatting, conversion, or other modifications to the power from the power supply 2508 so that the power is suitable for the corresponding components of the UE 2500 to which the power is supplied.

[0165] The memory 2510 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 2510 includes one or more application programs 2514, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 2516. The memory 2510 may store any one of a variety of different operating systems or a combination of operating systems for use by the UE 2500.

[0166] The memory 2510 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory, such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as USIM and / or ISIM, other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 2510 may allow the UE 2500 to access instructions, applications, etc. stored on a transient or non-transient storage medium to offload data or upload data. An article of manufacture (eg, an article of manufacture utilizing a communication system) may be tangibly embodied as or in memory 2510 , which may be or include a device-readable storage medium.

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

[0168] In the illustrated embodiment, the communication functionality of the communication interface 2512 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near field communication), location-based communication (such as using a global positioning system (GPS) to determine location), another similar communication functionality, or any combination thereof. Communication may be implemented according to 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 network (SONET), asynchronous transfer mode (ATM), QUIC, hypertext transfer protocol (HTTP), etc.

[0169] Regardless of the type of sensor, the UE can provide an output of the data captured by its sensor via a wireless connection to a network node through its communication interface 2512. The data captured by the UE's sensor can be transmitted to the network node via another UE through a wireless connection. The output can be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to balance the load of reports from several sensors), in response to a trigger event (e.g., when humidity is detected, an alarm is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0170] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts a control surface or rotor of a drone in flight based on the received input, or adjusts a robotic arm that performs a medical procedure based on the received input.

[0171] When the UE is in the form of an Internet of Things (IoT) device, it can be a device for one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are the following devices or devices embedded in the following devices: connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, self-driving cars, surveillance systems, weather monitoring devices, parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for tactile enhancement or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical equipment, such as heart rate monitors or remotely controlled surgical robots. In addition to including, for example, in combination with Fig.25 In addition to the other components described in the UE 2500 shown in FIG, circuits and / or software may also be included depending on the intended application of the IoT device.

[0172] As another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and sends the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, airplane, or other device capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0173] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated in a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE that is a remote controller for operating the drone. When the user implements changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first and / or second UE may also include one or more of the above functions. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0174] Fig.26 A network node 2600 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), O-RAN nodes, or components of O-RAN nodes (e.g., intelligent controllers, O-RUs, O-DUs, O-CUs).

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

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

[0177] The network node 2600 includes a processing circuit 2602, a memory 2604, a communication interface 2606, and a power supply 2608. The network node 2600 may include multiple physically separated components (e.g., a node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding component. In a specific scenario where the network node 2600 includes multiple individual components (e.g., a BTS and a BSC component), one or more individual components may be shared between several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, in some instances, each unique node B and RNC pair may be considered as a single individual network node. In some embodiments, the network node 2600 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be repeated (e.g., separate memories 2604 for different RATs), and some components may be reused (e.g., the same antenna 2610 may be shared by different RATs). The network node 2600 may also include multiple sets of the various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies) integrated into the network node 2600. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 2600.

[0178] The processing circuit 2602 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, a combination of one or more of resources, or a combination of hardware, software and / or encoded logic that is operable to provide network node 2600 functionality alone or in combination with other network node 2600 components (such as memory 2604).

[0179] In some embodiments, processing circuitry 2602 includes a system on a chip (SOC). In some embodiments, processing circuitry 2602 includes one or more of radio frequency (RF) transceiver circuitry 2612 and baseband processing circuitry 2614. In some embodiments, radio frequency (RF) transceiver circuitry 2612 and baseband processing circuitry 2614 may be on separate chips (or a set of chips), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuitry 2612 and baseband processing circuitry 2614 may be on the same chip or a set of chips, boards, or units.

[0180] The memory 2604 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transient device-readable and / or computer-executable storage device that stores information, data and / or instructions that can be used by the processing circuit 2602. The memory 2604 may store any suitable instructions, data or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables and / or other instructions that can be executed by the processing circuit 2602 and utilized by the network node 2600). The 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.

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

[0182] In certain alternative embodiments, the network node 2600 does not include a separate radio front end circuit 2618, but rather 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 circuit 2612 is part of the communication interface 2606. In other embodiments, the communication interface 2606 includes one or more ports or terminals 2616, the radio front end circuit 2618, and the RF transceiver circuit 2612 as part of a radio unit (not shown), and the communication interface 2606 communicates with the baseband processing circuit 2614 as part of a digital unit (not shown).

[0183] Antenna 2610 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 2610 may be coupled to radio front end circuit 2618 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 2610 is separate from network node 2600 and may be connected to network node 2600 via an interface or port.

[0184] Antenna 2610, communication interface 2606 and / or processing circuit 2602 may be configured to implement any receiving operation and / or certain acquisition operations implemented by a network node as described herein. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, antenna 2610, communication interface 2606 and / or processing circuit 2602 may be configured to implement any sending operation implemented by a network node as described herein. Any information, data and / or signal may be sent to a UE, another network node and / or any other network device.

[0185] The power supply 2608 provides power to the various components of the network node 2600 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply 2608 may also include or be coupled to a power management circuit to supply power to the components of the network node 2600 for implementing the functions described herein. For example, the network node 2600 may be connected to an external power source (e.g., a power grid, a power outlet) via an input circuit or interface such as a cable, whereby the external power source supplies power to the power circuit of the power supply 2608. As another example, the power supply 2608 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit. If the external power source fails, the battery may provide backup power.

[0186] An embodiment of the network node 2600 may include Fig.26Additional components other than those shown in the figure may be used to provide certain aspects of the network node functionality, including any functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 2600 may include a user interface device to allow information to be input into the network node 2600 and to allow information to be output from the network node 2600. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 2600.

[0187] Fig. 27 is a block diagram of a host 2700 according to various aspects described herein, and the host 2700 may be Fig.24 2416 of the embodiment of the host. As used herein, the host 2700 can be or include various combinations of hardware and / or software, including a stand-alone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a processing resource in a server farm. The host 2700 can provide one or more services to one or more UEs.

[0188] Host 2700 includes processing circuitry 2702, which is operably coupled to input / output interface 2706, network interface 2708, power supply 2710, and memory 2712 via bus 2704. Other components may be included in other embodiments. The features of these components may be similar to those described with respect to previous figures (such as Fig.25 and Fig.26 ) are substantially similar in features to those described for the devices of the host 2700, so that their description is generally applicable to corresponding components of the host 2700.

[0189] The memory 2712 may include one or more computer programs (including one or more host applications 2714 and data 2716), and the data 2716 may include user data, such as data generated by the UE for the host 2700 or data generated by the host 2700 for the UE. An embodiment of the host 2700 may utilize only a subset of the components shown or utilize all of the components shown. The host application 2714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., general 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 categories, types or implementations of UE (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). The host application 2714 may also provide user authentication and authorization checks, and may periodically report health status, routing, and content availability to a central node (such as a device in a core network or at the edge). Thus, the host 2700 can select and / or indicate different hosts for over-the-top services of the UE. The host application 2714 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0190] Fig.28 2800 in which the functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of a device or apparatus, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 2800 hosted by one or more hardware nodes (such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments where a virtual node does not require a radio connection (e.g., a core network node or host), the node may be fully virtualized. In some embodiments, the virtualized environment 2800 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a service management and orchestration framework via an O-2 interface.

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

[0192] Hardware 2804 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 2806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2808a and 2808b (one or more of which may be generally referred to as VMs 2808), and / or implement any functionality, features, and / or benefits associated with some embodiments described herein. Virtualization layer 2806 may present a virtual operating platform that appears to be network hardware to VMs 2808.

[0193] VM 2808 includes virtual processing, virtual memory, virtual network or interface and virtual storage, and can be operated by corresponding virtualization layer 2806. Different embodiments of instances of virtual device 2802 can be implemented on one or more VM 2808, and can be implemented in different ways. Virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV can be used to integrate many network equipment types onto industry-standard high-volume server hardware, physical switches and physical storage, which can be located in data centers and customer premises equipment.

[0194] In the context of NFV, VM 2808 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each VM 2808 and a portion of the hardware 2804 on which the VM executes, whether hardware dedicated to the VM and / or hardware shared by the VM with other VMs, form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 2808 on the hardware 2804 and corresponds to an application 2802.

[0195] Hardware 2804 can be implemented in a standalone network node with general or specific components. Hardware 2804 can implement some functions through virtualization. Optionally, hardware 2804 can be part of a larger hardware cluster (for example, like in a data center or CPE), where many hardware nodes work together and are managed through management and orchestration 2810, where management and orchestration 2810 oversees the life cycle management of application 2802. In some embodiments, hardware 2804 is coupled to one or more radio units, each of which includes one or more transmitters that can be coupled to one or more antennas and one or more receivers. The radio unit can communicate directly with other hardware nodes through one or more appropriate network interfaces, and can be used in conjunction with virtual components to provide radio capabilities for virtual nodes, such as radio access nodes or base stations. In some embodiments, a control system 2812 can be used to provide some signaling, and the control system 2812 can optionally be used for communication between hardware nodes and radio units.

[0196] Fig.29 A communication diagram is shown in which a host 2902 communicates with a UE 2906 via a network node 2904 over a partially wireless connection according to some embodiments. Fig.29 To describe the UE discussed in the preceding paragraphs (such as Fig.24 UE 2412a and / or Fig.25 UE 2500), network nodes (such as Fig.24 The network node 2410a and / or Fig.26 network nodes 2600) and hosts (such as Fig.24 Host 2416 and / or Fig. 27 An example implementation of host 2700).

[0197] Similar to the host 2700, an embodiment of the host 2902 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 2902 also includes software, which is stored in the host 2902 or accessible by the host 2902 and can be executed by the processing circuit. The software includes a host application, which is operable to provide services to a remote user (e.g., a UE 2906 connected via an over-the-top (OTT) connection 2950 extending between the UE 2906 and the host 2902). When providing services to the remote user, the host application can provide user data sent using the OTT connection 2950.

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

[0199] UE 2906 includes hardware and software, which is stored in UE 2906 or accessible by UE 2906, and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "app", which is operable to provide services to human or non-human users through UE 2906 with the support of host 2902. In host 2902, the executed host application can communicate with the executed client application via an OTT connection 2950 terminated at UE 2906 and host 2902. When providing services to the user, the client application of the UE can receive request data from the host application of the host and provide user data in response to the request data. The OTT connection 2950 can transmit both request data and user data. The client application of the UE can interact with the user to generate user data that it provides to the host application through the OTT connection 2950.

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

[0201] As an example of sending data via the OTT connection 2950, ​​in step 2908, the host 2902 provides user data, which can be implemented by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 2906. In other embodiments, the user data is associated with the UE 2906, and the UE 2906 shares the data with the host 2902 without explicit human-computer interaction. In step 2910, the host 2902 initiates a transmission carrying the user data to the UE 2906. The host 2902 may initiate the transmission in response to a request sent by the UE 2906. The request may be caused by human-computer interaction with the UE 2906, or by the operation of a client application executed on the UE 2906. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via the network node 2904. Therefore, in step 2912, according to the teachings of the embodiments described throughout the present disclosure, the network node 2904 sends the user data carried in the transmission initiated by the host 2902 to the UE 2906. In step 2914 , UE 2906 receives the user data carried in the transmission, which may be implemented by a client application executing on UE 2906 that is associated with a host application executed by host 2902 .

[0202] In some examples, UE 2906 executes a client application that provides user data to host 2902. The user data may be provided as a reaction or response to data received from host 2902. Therefore, in step 2916, UE 2906 may provide user data, which may be implemented by executing a client application. When providing user data, the client application may also take into account user input received from a user via an input / output interface of UE 2906. Regardless of the specific manner in which the user data is provided, in step 2918, UE 2906 initiates transmission of the user data to host 2902 via network node 2904. In step 2920, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 2904 receives user data from UE 2906 and initiates transmission of the received user data to host 2902. In step 2922, host 2902 receives the user data carried in the transmission initiated by UE 2906.

[0203] One or more of the various embodiments improve the performance of OTT services provided to UE 2906 using OTT connection 2950, ​​wherein wireless connection 2970 forms the last segment. More specifically, the teachings of these embodiments may make it possible to report MDT measurement related information between SNPN, PNI-NPN and PLMN, which allows the network to optimize inter-network and intra-network coverage issues. It should be noted that it is not obvious to add NPN identifiers to the list of networks for which MDT configuration is valid. The reason why this is not obvious is that private networks are networks separated from PLMNs. For example, SNPNs should not be connected to PLMNs or PNI NPNs. In addition, UEs according to current specifications are not allowed to implement mobility between SNPNs and other networks different from SNPNs. Currently, MDT configurations can only be applied to UEs within a group of PLMNs that are equivalent to each other and include a registered PLMN for UEs. Therefore, it is not obvious to extend the regional scope of MDT configuration to NPNs, because this means coordination and agreement between NPN operators and PLMN operators. However, the advantage of this configuration is that for UEs that can move between NPN and PLMN, the operator (PLMN or NPN operator) can configure MDT measurements at the UE, and by receiving these measurements, it can consistently monitor several aspects involving PLMN and NPN, such as: (1) monitoring coverage at NPN and PLMN and at the coverage boundary between PLMN and NPN. This allows ensuring that convergence between different networks is consistent and that mobility between different networks does not fail due to poor coverage; and (2) monitoring performance at the radio and service level for UEs moving between PLMN and NPN. This allows the operator to optimize the guidance of UEs to coverage locations that provide the best service for a particular service, as well as optimize service coverage in places with poor performance.

[0204] In an example scenario, host 2902 may collect and analyze plant status information. As another example, host 2902 may process audio and video data that may have been retrieved from UE for use in creating maps. As another example, host 2902 may collect and analyze real-time data to help control vehicle congestion (e.g., control traffic lights). As another example, host 2902 may store surveillance videos uploaded by UE. As another example, host 2902 may store or control access to media content, such as video, audio, VR, or AR, which may broadcast, multicast, or unicast the media content to UE. As other examples, host 2902 may be used for energy pricing, remote control of non-time-critical power loads to balance power generation demand, location services, presentation services (such as compiling charts based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or sending data.

[0205] In some examples, a measurement process may be provided for monitoring data rates, delays, and other factors improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 2950 between the host 2902 and the UE 2906 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection may be implemented in the software and hardware of the host 2902 and / or the UE 2906. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 2950 passes; the sensors may participate in the measurement process by providing the values ​​of the monitored quantities of the above examples or by providing the values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2950 may include message formatting, retransmission settings, preferred routing, etc.; the reconfiguration does not require direct changes to the operation of the network node 2904. These processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 2902 to measure throughput, propagation time, delay, etc. The measurements may be implemented in software that causes messages (particularly empty or 'dummy' messages) to be sent using the OTT connection 2950, ​​while monitoring propagation times, errors, etc.

[0206] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to implement the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be implemented by a processing circuit, which may process information by, for example, converting the acquired information into other information, comparing the acquired information or the converted information with the information stored in the network node, and / or implementing one or more operations based on the acquired information or the converted information, and making a determination as a result of the processing. In addition, although the components are described as a single box located within a larger box, or a single box nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functions may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functions of the components may be divided between a processing circuit and a communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0207] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit that executes instructions stored in a memory, which may be a computer program product in the form of a non-transient computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, the processing circuit may be configured to implement the described functionality, regardless of whether instructions stored on a non-transient computer-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits or other components of a computing device, but are generally enjoyed by the entire computing device and / or by end users and wireless networks.

Claims

1. A method of operating a Radio Access Network (RAN) node, the method comprising: Determining (2310) a minimization of drive tests (MDT) configuration, the MDT configuration comprising an area range associated with a cell identified by at least one of: Public network integrated non-public network PNI-NPN; Independent non-public network SNPN; as well as Public Land Mobile Network PLMN; as well as A communication device served by a first cell in a first communication network is configured (2320) with the MDT configuration to instruct the communication device to collect MDT measurements from a second cell in a second communication network.

2. The method according to claim 1, wherein: The PNI-NPN is identified by a closed access group CAG, and The SNPN is identified by a network identifier NID.

3. The method according to claim 2, wherein: The PNI-NPN is also identified by the PLMN and the CAG.

4. The method according to any one of claims 2 to 3, wherein: The SNPN is also identified by the PLMN and the NID.

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

6. The method according to any one of claims 1 to 5, wherein: The first communication network is an NPN, and The second communication network includes at least one of the following: PLMN; SNPN; and PNI-NPN.

7. The method according to any one of claims 1 to 5, wherein: The first communication network is a public network, and The second communication network includes at least one of the following: SNPN; and PNI-NPN.

8. The method according to any one of claims 1 to 7, wherein: Determining the MDT configuration includes: receiving the MDT configuration from a second network node, the second network node including at least one of the following: Core network CN node in PLMN; Operation, Administration and Maintenance (OAM) in PLMN; CN nodes in SNPN; and OAM in SNPN.

9. The method according to any one of claims 1 to 8, wherein: The MDT configuration includes an indication that the communications device reports the collected MDT measurements when the MDT measurements are collected.

10. The method according to any one of claims 1 to 8, wherein: The MDT configuration includes an indication that the communications device records the collected MDT measurements when the MDT measurements are collected.

11. The method according to any one of claims 1 to 10, wherein: Configuring the communication device includes sending the MDT configuration as part of at least one of: Initial context setup request; Handover request; and Path switch request confirmation.

12. The method according to any one of claims 1 to 11, wherein: The communication device operates in dual connectivity, and The configuring the communication device comprises: sending the MDT configuration for both the MN and the SN to at least one of a master node MN and a secondary node SN.

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

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

15. The method according to any one of claims 1 to 14, further comprising: The MDT measurements are received (2330) from the communications device.

16. The method according to claim 15, further comprising: The MDT measurements are sent (2340) to the second communication network.

17. The method according to any one of claims 1 to 14, further comprising: The MDT measurements are received (2330) from the second communication network.

18. A method for operating a core network CN node, the method comprising: A minimization of drive tests (MDT) configuration is sent (2310) to a radio access network RAN ​​node, the MDT configuration comprising an area scope identified by at least one of: Public network integrated non-public network PNI-NPN; SNPN (Separate Non-Public Network); and Public Land Mobile Network PLMN.

19. A network node (2600) operating in a communication network, the network node comprising: Processing circuit (2602); as well as A memory (2604) coupled to the processing circuit and having instructions stored therein, the instructions being executable by the processing circuit to cause the network node to perform operations including any of the operations according to claims 1-18.

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

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

22. A non-transitory computer readable medium having instructions stored therein executable by a processing circuit (2602) of a network node (2600) operating in a communication network to cause the network node to perform operations including any of the operations according to claims 1-18.

Images