Minimization of drive test area configuration

Abstract

A first network node (14-1) is configured for minimization of drive test, MDT, measurements in a communication network (10). The first network node (14-1) receives, from a second network node (14-2), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration (16) indicates the one or more areas in terms of one or more network slices (20). In other embodiments, the MDT configuration (16) indicates one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

Description

[0001] MINIMIZATION OF DRIVE TEST AREA CONFIGURATION

[0002] TECHNICAL FIELD

[0003] The present application relates generally to minimization of drive tests in a communication network, and relates more particularly to area configuration for such minimization of drive tests.

[0004] BACKGROUND

[0005] Traditionally, a communication network operator conducted drive tests dedicated to collecting radio measurements for self-organizing network (SON) tasks, such as network planning, network optimization, network parameter tuning, and / or positioning (e.g., RF pattern matching based positioning). Using drive tests for SON thereby proved costly and burdensome.

[0006] So-called minimization of drive test (MDT) measurements minimize the drive tests that a communication network operator must conduct for SON tasks. MDT in this regard exploits subscribers’ own communication devices for performing the radio measurements, relieving the need for the operator to itself conduct drive tests. The MDT measurements may for example include radio measurements and location measurements, usable for analyzing radio coverage and performance in different locations.

[0007] A communication device can perform MDT measurements when the communication device has an established connection with the network, e.g., when the communication device is in a radio resource control (RRC) connected state. The communication device in such a case performs the MDT measurements and reports the results of the MDT measurements, i.e., immediately. MDT measurements in this case may be referred to as immediate MDT measurements.

[0008] By contrast, a communication device can alternatively or additionally perform MDT measurements even when the communication device does not have an established connection with the network, e.g., when the communication device is in a radio resource control (RRC) idle or inactive state. In this case, the communication device can log the MDT measurements at the device, e.g., storable for up to 48 hours. The communication device can then report the logged MDT measurements later on once the communication device has an established connection with the network, e.g., once the communication device transitions to an RRC connected state. MDT measurements in this case may be referred to as logged MDT measurements.

[0009] Network slicing however introduces challenges for MDT measurement collection. A network slice is a logical network that provides specific network capabilities and network characteristics. An operator can deploy multiple network slices to provide different logical networks for providing different respective network capabilities and network characteristics. For example, different network slices may be dedicated to different respective services, such as Internet of Things (loT) services, mission-critical services, mobile broadband services, etc. Although such network slicing proves advantageous in a number of respects, it creates some challenges for MDT measurement collection. MDT measurements are heretofore agnostic as to any network slices in a communication network, since they are configured, collected, and reported without regard to network slicing. MDT measurements are therefore incapable of providing visibility into performance on a slice by slice basis, at least without lengthy and resource-intensive post-processing. Furthermore, MDT measurements collected without regard to network slicing may contain data associated with multiple network slices, and reporting the results of those MDT measurements to an entity that manages or owns one slice risks exposing data associated with other slices to which the entity should not be privy.

[0010] SUMMARY

[0011] Some embodiments herein enable slice-based MDT measurement configuration, collection, and / or reporting. Some embodiments herein advantageously provide MDT measurement configuration, collection, and / or reporting at the network slice level, e.g., to improve observability of performance and / or efficiency on a slice by slice basis. This slicespecific observability may, for example, be used to monitor whether service level agreements for a specific network slice are fulfilled. In fact, some embodiments enable such observability in an efficient way, without requiring lengthy and resource-intensive post-processing. Alternatively or additionally, some embodiments advantageously confine MDT measurement configuration, collection, and / or reporting to be slice-specific, so as to avoid over-exposure of slice-specific data and thereby improve data privacy.

[0012] More particularly, embodiments herein include a method performed by a first network node for minimization of drive test, MDT, measurements in a communication network. The method comprises receiving, from a second network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

[0013] In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices by defining the one or more areas as including, or being restricted to, the one or more network slices. In some embodiments, the MDT configuration includes an area scope parameter that defines an area scope of the MDT measurements as being slice-based. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices by indicating one or more network slices that are included in the area scope of the MDT measurements. In some embodiments, the area scope parameter comprises a list of one or more respective identifiers of the one or more network slices that are included in the area scope. In other embodiments, the area scope parameter comprises a list of one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices that are included in the area scope. In some embodiments, the one or more areas are one or more first areas, wherein the MDT configuration indicates the one or more first areas in terms of one or more network slices. In some embodiments, the method further comprises determining one or more second areas that each supports at least one of the one or more network slices, and transmitting, to one or more communication devices, an MDT configuration that indicates an area scope for collection of the MDT measurements as including the one or more second areas.

[0014] In some embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more cells, one or more frequencies, one or more tracking areas, one or more routing areas, or one or more location areas.

[0015] In some embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected. In some embodiments, the method further comprises determining which one or more of the one or more areas indicated by the MDT configuration support at least one of the one or more network slices indicated by the MDT configuration, and transmitting, to one or more communication devices, an MDT configuration that indicates an area scope for collection of the MDT measurements as including the one or more determined areas.

[0016] In some embodiments, the network node is a radio network node, and wherein the another network node is a core network node or an OAM node.

[0017] In some embodiments, the method further comprises configuring one or more communication devices according to the MDT configuration.

[0018] In some embodiments, the method further comprises collecting results of the MDT measurements, and transmitting, to a trace collection entity, a report of the results of the MDT measurements as collected.

[0019] Other embodiments herein include a method performed by a second network node for minimization of drive test, MDT, measurements in a communication network. The method comprises transmitting, from the second network node to a first network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected. In some embodiments, the second network node is a core network node or an OAM node, and wherein the first network node is a radio network node.

[0020] Other embodiments herein include a method performed by a first network node for minimization of drive test, MDT, measurements in a communication network. The first network node is configured to receive, from a second network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

[0021] In some embodiments, the first network node is configured to perform the method described above for a first network node for MDT measurements in a communication network.

[0022] Other embodiments herein include a method performed by a second network node for minimization of drive test, MDT, measurements in a communication network. The second network node is configured to transmit, from the second network node to a first network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

[0023] In some embodiments, the second network node is a core network node or an OAM node, and the first network node is a radio network node.

[0024] In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a first network node, causes the first network node to perform the steps described above for a first network node for MDT measurements in a communication network

[0025] In some embodiments, computer program comprising instructions which, when executed by at least one processor of a second network node, causes the second network node to perform the steps described above for a second network node for MDT measurements in a communication network.

[0026] In some embodiments, a carrier containing the computer program, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0027] Other embodiments herein include a first network node for minimization of drive test, MDT, measurements in a communication network. The first network node comprises communication circuitry and processing circuitry. The processing circuitry is configured to receive, from a second network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

[0028] In some embodiments, the processing circuitry configured to perform the steps described above for a first network node for MDT measurements in a communication network.

[0029] Other embodiments herein include a second network node for minimization of drive test, MDT, measurements in a communication network. The second network node comprises communication circuitry and processing circuitry. The processing circuitry is configured to transmit, from the second network node to a first network node, an MDT configuration that indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration indicates the one or more areas in terms of one or more network slices. In other embodiments, the MDT configuration indicates one or more network slices, at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

[0030] In some embodiments, the second network node is a core network node or an OAM node, and wherein the first network node is a radio network node.

[0031] Embodiments herein also include corresponding apparatus, computer programs, and carriers of those computer programs.

[0032] BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 is a block diagram of a communication network according to some embodiments.

[0034] Figures 2A-2B illustrate block diagrams of measurement configurations according to particular embodiments.

[0035] Figure 3 depicts a method performed by a communication device for minimization of drive test, MDT, measurement in a communication network in accordance with particular embodiments.

[0036] Figure 4 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments.

[0037] Figure 5 depicts a method performed by a communication device configured for use in a communication network in accordance with other particular embodiments.

[0038] Figure 6 depicts a method performed by a network node for minimization of MDT measurements in a communication network in accordance with other particular embodiments.

[0039] Figure 7 depicts a method performed by a network node configured for use in a communication network in accordance with other particular embodiments.

[0040] Figure 8 depicts a method performed by a network for MDT measurements in a communication network in accordance with other particular embodiments. Figure 9 illustrates a block diagram of shared or dedicated Radio Access Network, RAN, infrastructure according to particular embodiments.

[0041] Figure 10 is a block diagram of a communication device according to some embodiments.

[0042] Figure 11 is a block diagram of a network node according to some embodiments.

[0043] Figure 12 is a block diagram of a communication system in accordance with some embodiments.

[0044] Figure 13 is a block diagram of a user equipment according to some embodiments. Figure 14 is a block diagram of a network node according to some embodiments. Figure 15 is a block diagram of a host according to some embodiments.

[0045] Figure 16 is a block diagram of a virtualization environment according to some embodiments.

[0046] DETAILED DESCRIPTION

[0047] Figure 1 shows a communication network 10 (e.g., a 5G network) according to some embodiments. The communication network 10 is configured to provide communication service to one or more communication devices, one of which is shown as communication device 12.

[0048] The communication network 10 configures collection of minimization of drive test (MDT) measurements. MDT measurements may for example include radio measurements and location measurements, usable for analyzing radio coverage and performance in different locations. The MDT measurements may be immediate MDT measurements or logged MDT measurements.

[0049] Figure 1 in this regard shows that network node 14-2 (e.g., a core network node) transmits an MDT configuration 16 to network node 14-1 (e.g., a radio network node). The MDT configuration 16 defines parameters for collection of MDT measurements. The MDT measurements may be collected by network node 14-1 itself, by one or more other network nodes (not shown), and / or by one or more communication devices such as communication device 12. In embodiments where communication device 12 is to collect the MDT measurements, network node 14-1 correspondingly transmits a measurement configuration 18 to the communication device 12, e.g., via radio resource control (RRC) signaling. Where the MDT measurements to be collected are logged MDT measurements, for example, the measurement configuration 18 may be a logged measurement configuration. Either way, the measurement configuration 18 configures the communication device 12 to perform measurements according to the MDT configuration 16.

[0050] Notably, though, the communication network 10 deploys multiple network slices 10S- 1 ...10S-N, generally referred to as network slices 10S. Each one of the network slices 10S is a logical network that provides specific network capabilities and network characteristics. The network slices 10S may thereby provide different logical networks for providing different respective network capabilities and network characteristics. For example, different network slices 10S may be dedicated to different respective services, such as Internet of Things (loT) services, mission-critical services, mobile broadband services, etc.

[0051] In this context, the MDT configuration 16 from network node 14-2 to network node 14-1 notably indicates one or more network slices 20 for which the MDT measurements are to be collected. The network slice(s) 20 for which the MDT measurements are to be collected may include a subset of the network slices 10S in the communication network 10. The MDT configuration 16 may for example include a list of one or more respective identifiers of the one or more network slices 10S. Or, the MDT configuration 16 may include a list of one or more network slice group identifiers that identify one or more respective network slice groups, where each of the one or more network slice groups includes one or more of the network slice(s) 20.

[0052] Correspondingly, in some embodiments, the measurement configuration 18 from network node 14-1 to communication device 12 likewise indicates the network slice(s) 20 for which MDT measurements are to be collected. The measurement configuration 18 may for example include a list of one or more respective identifiers of the one or more network slices 10S. Or, the measurement configuration 18 may include a list of one or more network slice group identifiers that identify one or more respective network slice groups, where each of the one or more network slice groups includes one or more of the network slice(s) 20.

[0053] In some embodiments, the MDT configuration 16 and / or the measurement configuration 18 indicates the network slice(s) 20 for which the MDT measurements are to be collected by defining area(s) in which the MDT measurements are to be collected in terms of the network slice(s) 20.

[0054] As shown in Figure 2A, for example, the MDT configuration 16 in some embodiments indicates an area scope 22. The area scope 22 indicates that the MDT measurements are to be collected in one or more areas. In some embodiments, the MDT configuration 16 indicates these one or more areas in terms of the one or more network slices 20 for which the MDT measurements are to be collected, i.e., the area scope 22 is slice-based. That is, the MDT configuration 16 indicates the one or more network slices 20 are included in the area scope 22 of the MDT measurements, e.g., the area scope 22 may include a list of network slice identifiers and / or a list of network slice group identifiers as described above. The area(s) in which the MDT measurements are to be collected thereby include, or are restricted to, the network slice(s) 20.

[0055] Alternatively or additionally, as shown in Figure 2B, the measurement configuration 18 may include an area configuration 24. The area configuration 24 indicates that the MDT measurements are to be collected in one or more areas. In some embodiments, the measurement configuration 18 indicates these one or more areas in terms of the one or more network slices 20 for which the MDT measurements are to be collected, i.e., the area configuration 24 is slice-based. That is, the measurement configuration 18 indicates the one or more network slices 20 are included in the area configuration 24 of the MDT measurements, e.g., the area configuration 24 may include a list of network slice identifiers and / or a list of network slice group identifiers as described above. The area(s) in which the MDT measurements are to be collected thereby include, or are restricted to, the network slice(s) 20.

[0056] In some embodiments as shown, then, the area(s) in which the MDT measurements are to be collected are themselves defined in terms of network slice(s) 20. In other embodiments not shown, though, the area(s) in which the MDT measurements are to be collected may be defined apart from network slice(s) 20, e.g., as including certain cells, tracking areas, routing areas, or location areas. In this case, the network slice(s) 20 for which the MDT measurements are to be collected operate as an additional restriction on whether MDT measurements are to actually be collected in those area(s). The network slice(s) 20 for which MDT measurements are to be collected may in this case be specified as one or more network slices that need to be supported and / or available in an area in order for the communication device 12 to collect the MDT measurements for that area.

[0057] Regardless, with MDT measurement collection configured in this or other ways on a slice by slice basis, the MDT measurements may correspondingly be collected (e.g., performed and / or logged) on a slice by slice basis. In the embodiments of Figures 2A and 2B, for example, the communication device 12 collects the MDT measurements in a cell on which the communication device 12 is served or camped if at least one of the one or more network slices 20 supported and / or available in the cell is included in the one or more areas. Towards this end, the communication device 12 may identify one or more network slices that are supported and / or available in the cell on which the communication device 12 is served or camped. If at least one of the one or more identified network slices 20 is included in the one or more areas, the communication device 12 collects the MDT measurements.

[0058] The MDT measurements may furthermore be reported in a way that indicates for which network slice(s) the MDT measurements were collected.

[0059] Some embodiments herein thereby advantageously provide MDT measurement configuration, collection, and / or reporting at the network slice level, e.g., to improve observability of performance and / or efficiency on a slice by slice basis. This slice-specific observability may, for example, be used to monitor whether service level agreements for a specific network slice are fulfilled. In fact, some embodiments enable such observability in an efficient way, without requiring lengthy and resource-intensive post-processing. Alternatively or additionally, some embodiments advantageously confine MDT measurement configuration, collection, and / or reporting to be slice-specific, so as to avoid over-exposure of slice-specific data and thereby improve data privacy.

[0060] Figures 3-8 describe additional aspects of some embodiments herein, with further reference to Figures 1 and 2A-2B. Figure 3 depicts a method performed by a communication device 12 for minimization of drive test, MDT, measurement in a communication network 10 in accordance with particular embodiments. The method includes receiving, from a network node 14-1 in the communication network 10, a measurement configuration 18 that configures the communication device 12 to collect MDT measurements and that indicates one or more network slices 20 for which to collect MDT measurements (Block 300).

[0061] In some embodiments, the measurement configuration 18 indicates one or more areas for which the communication device 12 is to collect MDT measurements. In some embodiments, the measurement configuration 18 indicates the one or more areas in terms of one or more network slices 20.

[0062] In some embodiments, the one or more areas include, or are restricted to, the one or more network slices 20.

[0063] In some embodiments, the method further comprises determining that the communication device 12 is in one of the one or more areas. In some embodiments, the method further comprises, based on the communication device 12 being in one of the one or more areas according to said determining, collecting the MDT measurements.

[0064] In some embodiments, the communication device 12 is to collect the MDT measurements in a cell on which the communication device 12 is served or camped if at least one of the one or more network slices supported and / or available in the cell is included in the one or more areas.

[0065] In some embodiments, the method further comprises identifying one or more network slices that are supported and / or available in the cell on which the communication device 12 is served or camped. In some embodiments, the method further comprises, if at least one of the one or more identified network slices is included in the one or more areas, collecting the MDT measurements.

[0066] In some embodiments, the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices is supported and / or available.

[0067] In some embodiments, the communication device 12 is to collect the MDT measurements in a cell on which the communication device 12 is served or camped if the cell is included in the one or more areas.

[0068] In some embodiments, the measurement configuration 18 is a logged measurement configuration 18 that configures the communication device 12 to log results of the MDT measurements while in an idle or inactive state. In some embodiments, the logged measurement configuration 18 includes an area configuration that indicates the one or more areas as one or more areas for which the communication device 12 is requested to perform logging of the results of the MDT measurements. In some embodiments, the method further comprises, if at least one of any network slices supported by and / or available in a cell on which the communication device 12 is camped in the idle or inactive state is included in the one or more areas, performing logging of results of the MDT measurements.

[0069] In some embodiments, the measurement configuration 18 includes an area configuration that indicates one or more areas for which the communication device 12 is to collect the MDT measurements. In some embodiments, the communication device 12 is to collect the MDT measurements in an indicated area if at least one of the one or more network slices 20 is supported and / or available in the area. In some embodiments, the method further comprises determining that the communication device 12 is in an area for which the area configuration indicates the communication device 12 is to collect the MDT measurements. In some embodiments, the method further comprises identifying one or more network slices that are supported and / or available in the area. In some embodiments, the method further comprises, if the one or more identified network slices include at least one of the one or more network slices 20 indicated by the measurement configuration, collecting the MDT measurements.

[0070] In some embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slices 20 that need to be supported and / or available in an area in order for the communication device 12 to collect the MDT measurements for that area. In other embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slices 20, at least one of which needs to be supported and / or available in any area for which the communication device 12 collects the MDT measurements. In some embodiments, an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area. In some embodiments, the measurement configuration 18 is included in a configuration that configures the communication device 12 to collect the MDT measurements for any area in which at least one of the one or more network slices 20 are supported and / or available.

[0071] In some embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more respective identifiers of the one or more network slices 20. In some embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices 20.

[0072] In some embodiments, the network node is a radio network node and / or the measurement configuration 18 is received via radio resource control, RRC, signaling. In some embodiments, the measurement configuration 18 includes a list of one or more respective identifiers of the one or more network slices 20. In other embodiments, the measurement configuration 18 includes a list of one or more network slice group identifiers that identify one or more respective network slice groups. In some embodiments, each of the one or more network slice groups includes one or more of the one or more network slices 20.

[0073] In some embodiments, the method further comprises collecting the MDT measurements for one or more of the one or more network slices 20 indicated by the measurement configuration 18 (Block 310). In some embodiments, collecting the MDT measurements comprises performing the MDT measurements. In some embodiments, collecting the MDT measurements comprises logging and / or reporting results of the performed MDT measurements.

[0074] In some embodiments, the method further comprises identifying one or more network slices that are supported and / or available in an area. In some embodiments, the method further comprises, if the one or more identified network slices include at least one of the one or more network slices 20 for which the communication device 12 is to collect the MDT measurements, collecting the MDT measurements. In some embodiments, the area is an area on which the communication device 12 is served or on which the communication device 12 is camped. In some embodiments, the area is a neighbor area that neighbors an area on which the communication device 12 is served or on which the communication device 12 is camped. In some embodiments, the neighbor area is a neighbor cell. In some embodiments, said collecting comprises performing cell reselection to switch to camping on the neighbor cell. In some embodiments, said collecting comprises, after camping on the neighbor cell, collecting the MDT measurements.

[0075] In some embodiments, said identifying comprises reading and / or decoding System Information broadcast in the area. In some embodiments, the System Information includes slicespecific information for slice-specific random access or slice-specific cell selection, and said identifying comprises determining the one or more network slices that are supported and / or available in the area from the slice-specific information included in the System Information.

[0076] In some embodiments, said identifying comprises receiving, from a core network node, non-access stratum, NAS, signaling indicating the one or more network slices that are supported and / or available in the area. In some embodiments, the NAS signaling indicates, for each of one or more areas, a list of one or more network slices that are supported and / or available in that area. In other embodiments, the NAS signaling indicates, for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available

[0077] In some embodiments, the measurement configuration 18 is specific to a certain measurement session. In some embodiments, the MDT measurements include logged MDT measurements.

[0078] In some embodiments, the MDT measurements include immediate MDT measurements.

[0079] Figure 4 depicts a method performed by a communication device 12 configured for use in a communication network 10 in accordance with other particular embodiments. The method includes receiving, from a network node in the communication network 10, signaling indicating one or more network slices that are supported and / or available in an area (Block 400).

[0080] In some embodiments, the signaling is System Information signaling broadcast for the area. In some embodiments, the System Information signaling includes slice-specific information for slice-specific random access or slice-specific cell selection.

[0081] In some embodiments, the signaling is non-access stratum, NAS, signaling.

[0082] In some embodiments, the signaling indicates, for each of one or more areas, a list of one or more network slices that are supported and / or available in that area. In other embodiments, the signaling indicates, for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available.

[0083] In some embodiments, an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0084] In some embodiments, the signaling indicates one or more network slices that are supported and / or available in the area by indicating one or more respective identifiers of the one or more network slices. In other embodiments, the signaling indicates one or more network slices that are supported and / or available in the area by indicating one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0085] In some embodiments, the signaling is radio resource control, RRC, signaling.

[0086] In some embodiments, the signaling is non-access stratum, NAS, signaling.

[0087] In some embodiments, the area is a cell on which the communication device 12 is served or on which the communication device 12 camps.

[0088] In some embodiments, the area is a neighbor cell that neighbors a cell on which the communication device 12 is served or on which the communication device 12 camps.

[0089] In some embodiments, the method further comprises, if the one or more network slices include at least one of one or more network slices 20 for which the communication device 12 is to collect MDT measurements, collecting the MDT measurements for the area (Block 410). In some embodiments, the area is a neighbor cell that neighbors a cell on which the communication device 12 is served or on which the communication device 12 camps. In some embodiments, said collecting comprises performing cell reselection to switch to camping on the neighbor cell. In some embodiments, said collecting comprises, after camping on the neighbor cell, collecting the MDT measurements for the neighbor cell. In some embodiments, the method further comprises logging the collected MDT measurements at the communication device 12. In other embodiments, the method further comprises alternatively or additionally reporting the collected MDT measurements to the communication network 10. In some embodiments, the MDT measurements include logged MDT measurements. In some embodiments, the MDT measurements include immediate MDT measurements.

[0090] In some embodiments, the method further comprises determining, based on the one or more network slices that are supported and / or available in the area according to the signaling, whether or not the communication device 12 is to collect MDT measurements in the area (Block 420). In some embodiments, the method further comprises, if it is determined to collect MDT measurements in the area, collecting MDT measurements in the area (Block 430).

[0091] Figure 5 depicts a method performed by a communication device 12 configured for use in a communication network 10 in accordance with other particular embodiments. The method includes transmitting, to a network node in the communication network 10, capability signaling indicating that the communication device 12 is capable of performing slice-based MDT measurements (Block 500).

[0092] Figure 6 depicts a method performed by a network node 14-1 for minimization of drive test, MDT, measurements in a communication network 10 in accordance with other particular embodiments. The method includes transmitting, to a communication device 12, a measurement configuration 18 that configures the communication device 12 to collect MDT measurements and that indicates one or more network slices 20 for which to collect MDT measurements (Block 600).

[0093] In some embodiments, the measurement configuration 18 indicates one or more areas for which the communication device 12 is to collect MDT measurements, wherein the measurement configuration 18 indicates the one or more areas in terms of one or more network slices 20. In some embodiments, the one or more areas include, or are restricted to, the one or more network slices 20. In some embodiments, the communication device 12 is to collect the MDT measurements in a cell on which the communication device 12 is served or camped if at least one of the one or more network slices supported and / or available in the cell is included in the one or more areas. In some embodiments, the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices 20 is supported and / or available. In some embodiments, the communication device 12 is to collect the MDT measurements in a cell on which the communication device 12 is served or camped if the cell is included in the one or more areas. In some embodiments, the measurement configuration 18 is a logged measurement configuration 18 that configures the communication device 12 to log results of the MDT measurements while in an idle or inactive state. In some embodiments, the logged measurement configuration 18 includes an area configuration that indicates the one or more areas as one or more areas for which the communication device 12 is requested to perform logging of the results of the MDT measurements. In some embodiments, the communication device 12 is to perform logging of results of the MDT measurements if at least one of any network slices supported by and / or available in a cell on which the communication device 12 is camped in the idle or inactive state is included in the one or more areas.

[0094] In some embodiments, the measurement configuration 18 includes an area configuration that indicates one or more areas for which the communication device 12 is to collect the MDT measurements. In some embodiments, the communication device 12 is to collect the MDT measurements in an indicated area if at least one of the one or more network slices 20 is supported and / or available in the area.

[0095] In some embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slices 20 that need to be supported and / or available in an area in order for the communication device 12 to collect the MDT measurements for that area. In other embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slices 20, at least one of which needs to be supported and / or available in any area for which the communication device 12 collects the MDT measurements. In some embodiments, an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area. In some embodiments, the measurement configuration 18 is included in a configuration that configures the communication device 12 to collect the MDT measurements for any area in which at least one of the one or more network slices 20 are supported and / or available.

[0096] In some embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more respective identifiers of the one or more network slices 20. In other embodiments, the measurement configuration 18 indicates one or more network slices 20 for which the communication device 12 is to collect the MDT measurements by indicating one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices 20.

[0097] In some embodiments, the network node is a radio network node and / or wherein the measurement configuration is transmitted via radio resource control, RRC, signaling.

[0098] In some embodiments, the measurement configuration 18 includes a list of one or more respective identifiers of the one or more network slices 20. In other embodiments, the measurement configuration 18 includes a list of one or more network slice group identifiers that identify one or more respective network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices 20.

[0099] In some embodiments, the measurement configuration 18 is specific to a certain measurement session. In some embodiments, the MDT measurements include logged MDT measurements.

[0100] In some embodiments, the MDT measurements include immediate MDT measurements.

[0101] Figure 7 depicts a method performed by a network node configured for use in a communication network 10 in accordance with other particular embodiments. The method includes transmitting, to a communication device 12, signaling indicating one or more network slices that are supported and / or available in an area (Block 700).

[0102] In some embodiments, the signaling is System Information signaling broadcast for the area. In some embodiments, the System Information signaling includes slice-specific information for slice-specific random access or slice-specific cell selection.

[0103] In some embodiments, the signaling is non-access stratum, NAS, signaling.

[0104] In some embodiments, the signaling indicates, for each of one or more areas, a list of one or more network slices that are supported and / or available in that area. In other embodiments, the signaling indicates, for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available.

[0105] In some embodiments, an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0106] In some embodiments, the signaling indicates one or more network slices that are supported and / or available in the area by indicating one or more respective identifiers of the one or more network slices. In other embodiments, the signaling indicates one or more network slices that are supported and / or available in the area by indicating one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0107] In some embodiments, the signaling is radio resource control, RRC, signaling.

[0108] In some embodiments, the signaling is non-access stratum, NAS, signaling.

[0109] In some embodiments, the area is a cell on which the communication device 12 is served or on which the communication device 12 camps.

[0110] In some embodiments, the area is a neighbor cell that neighbors a cell on which the communication device 12 is served or on which the communication device 12 camps.

[0111] Figure 8 depicts a method performed by a network node 14-1 , 14-2 for minimization of drive test, MDT, measurements in a communication network 10 in accordance with other particular embodiments. The method includes transmitting to, or receiving from, another network node 14-2, 14-1 an MDT configuration 16 that indicates one or more network slices 20 for which MDT measurements are to be collected (Block 800).

[0112] In some embodiments, the MDT configuration 16 indicates one or more areas for which the MDT measurements are to be collected. In some embodiments, the MDT configuration 16 indicates the one or more areas in terms of one or more network slices 20. In some embodiments, the one or more areas include, or are restricted to, the one or more network slices 20. In some embodiments, the MDT measurements are to be collected in a cell if at least one of the one or more network slices 20 supported and / or available in the cell is included in the one or more areas. In some embodiments, the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices 20 is supported and / or available. In some embodiments, the MDT measurements are to be collected in a cell if the cell is included in the one or more areas.

[0113] In some embodiments, the MDT configuration 16 indicates one or more network slices 20 for which the MDT measurements are to be collected by indicating one or more network slices 20 that need to be supported and / or available in an area in order for the MDT measurements to be collected for that area. In other embodiments, the MDT configuration 16 indicates one or more network slices 20 for which the MDT measurements are to be collected by indicating one or more network slices 20, at least one of which needs to be supported and / or available in any area for the MDT measurements are collected. In some embodiments, an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0114] In some embodiments, the MDT configuration 16 indicates one or more network slices 20 for which MDT measurements are to be collected by indicating one or more network slices 20 that are included in an area scope of the MDT measurements.

[0115] In some embodiments, the MDT configuration 16 defines configuration parameters for the MDT measurements. In some embodiments, the MDT configuration 16 is indicated by an area scope parameter that defines an area scope of the MDT measurements as being slicebased. In some embodiments, the area scope parameter comprises a list of one or more respective identifiers of the one or more network slices 20. In other embodiments, the area scope parameter comprises a list of one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices 20.

[0116] In some embodiments, said transmitting or receiving comprises transmitting the MDT configuration 16. In some embodiments, the network node is an operations and maintenance, OAM, node, and the another network node is a core network node. In some embodiments, the network node is a core network node or an OAM node, and the another network node is a radio network node.

[0117] In some embodiments, said transmitting or receiving comprises receiving the MDT configuration 16. In some embodiments, the network node is a core network node, and the another network node is an operations and maintenance, OAM, node. In some embodiments, the network node is a radio network node, and the another network node is a core network node or an OAM node. In some embodiments, the method further comprises configuring one or more communication device 12s according to the MDT configuration 16 (Block 810). In some embodiments, the method further comprises selecting the one or more communication device 12s based on capability signaling received from the one or more communication device 12s indicating that each of the one or more communication device 12s supports slice-based MDT measurement collection (Block 820). In some embodiments, the method further comprises collecting the MDT measurements for the one or more network slices 20 (Block 830).

[0118] In some embodiments, the method further comprises transmitting, to a trace collection entity, a report of results of the MDT measurements as collected (Block 840). In some embodiments, the report indicates the one or more network slices 20 for which the MDT measurements were collected.

[0119] In some embodiments, the MDT measurements include logged MDT measurements.

[0120] In some embodiments, the MDT measurements include immediate MDT measurements. Consider now various examples of some embodiments herein, where the communication device 12 is exemplified as a user equipment (UE).

[0121] In some embodiments, a network slice may constitute a logical network serving a defined business purpose or customer, consisting of all required network resources end-to-end. This means that a network slice may consist of all Network Functions and both Control Plane and User Plane required to provide given service(s). Some functions can be shared (i.e., the same Network Function can be in multiple Network Slices), but a network slice consists of all network functions and is not just a subset. A network slice may be identified by a network slice identifier, e.g., in the form of a single network slice selection assistance information (S-NSSAI).

[0122] There may be one shared or dedicated Radio Access Network (RAN) infrastructure that will connect to several core network (CN) instances (with one or more shared NW Functions (NF), interfacing the RAN, plus additional CN functions which may be dedicated for a slice. Such CN instances are shown in the example figure 9 as part of the Central Data Centre (DC). The CN functions are being virtualized. As shown, the Central DC may be partitioned into a dedicated cloud partition and a shared cloud partition. The dedicated cloud partition includes with dedicated NFs that are each dedicated for a slice. The shared cloud partition may include dedicated NFs and / or shared NFs that are each shared amongst multiple slices. The dedicated NFs of the dedicated cloud partition may be associated with dedicated transport capabilities of a backbone to an Edge DC, whereas the NFs of the shared cloud partition are associated with shared transport capabilities of the backbone. The Edge DC may include a shared cloud partition with dedicated NFs and / or a dedicated cloud partition with dedicated NFs. Connection to the access network may be provided via dedicated transport capabilities or shared transport capabilities of an aggregator, depending on whether a network slice, depending on whether a network slice relies on dedicated or shared resources. Services supported on some specific network slices (S-NSSAIs) may be configured and preferably used in dedicated frequency layers. To have a more efficient way of signaling to user equipments (UEs) what network slices are configured on some frequency layer, Network Slice Access Group (NSAG) may be used. The NSAG can be associated with a priority and that priority can be used by a UE to reselect to a specific frequency layer where some NSAG is configured / supported.

[0123] Some embodiments in this context enable specifying that MDT measurements shall be collected in areas where specific network slices are served. With this it is possible for an operator to trigger MDT measurements that can monitor the performance of services for specific network slices.

[0124] Some embodiments accordingly improve visibility of network slice performance. Some embodiments in this regard avoid an operator having to perform lengthy and resource intensive data post processing in order to monitor the performance of services provided by specific network slices. In particular, some embodiments avoid the operator having to define a generic Area Scope for MDT, collect MDT measurements there, and then post process the results to determine where measurements collected by UEs may have applied to services provided via specific slices. In fact, some embodiments enable visibility of network slice performance even under circumstances where it would not even be possible to deduce whether existing measurements apply to specific network slices, e.g., where the Operation and Maintenance (OAM) system may not have information enabling to link the measurement to the network slice for the bearer for which the measurements were collected.

[0125] It should be pointed out that some MDT measurements are not specific to radio bearers, but they are reflecting the signal levels of a radio network. In this case, some embodiments advantageously allow an operator to collect measurements in areas where specific slices are supported, namely to check the radio conditions in areas where specific network slices are served.

[0126] Some embodiments herein apply to Radio Access Networks supporting network slicing. Without loss of generality, the descriptions are detailed by taking a 5G system into account. However, the methods can be applied to any system supporting network slicing.

[0127] In this description the term “list of network slices” is used. This term not only indicates a list of network slice identifiers but it refers also to one or more NSAG, namely Network Slice Access Stratum Group.

[0128] In this description the term list of slice groups is used. The term is not limited to one or more list of network slice identifiers determined from an NSAG, but can be a list of one or more S-NSSAIs or one or more slice group identifiers each associated to a list of network slices and determined by other means or received by signaling. Consider now some embodiments herein where network node 14-1 is exemplified as a first node, network node 14-2 is exemplified as a second node, and communication device 12 is exemplified as a UE.

[0129] In one method a first network node, which may represent a RAN node, receives from a second node, which may represent a core network function or an CAM system, information concerning a list of network slices or list of slice groups, where such network slices are used to derive the RAN areas where the network slices are deployed and where MDT measurements shall be collected. This information may for example be information indicating the network slice(s) 20 in the MDT configuration 16 of Figure 1. Additionally to this information, the first network node may receive information concerning MDT measurements that shall be measured by UEs within the areas where the one or more network slices received are supported or available. Once collected, the UE reports the measurements to a network node (either first network node or a different network node).

[0130] In one embodiment, the first node may use this information to configure immediate MDT measurements, namely MDT measurements collected by UEs in RRC_Connected mode. In this embodiment, the first network node checks the area where a UE is served while in RRC_Connected, where such area may be constituted by, for example, a cell, a tracking area, a registration area, a PLMN. The first network node verifies that the area where the UE is served supports any of the one or more network slices signalled by the second network node. Alternatively, the first network node may verify not only that any of the one or more network slices signalled by the second network node is supported in the area where the UE is served, but that any of such one or more slices are also available in such area. It should be noted that a slice is available in a coverage area if the slice is supported by the cell serving the area and if resources for the slice are available to serve services associated to the slice.

[0131] On the other hand, a network slice may be supported within a cell, but not be available because no resources are available for the slices.

[0132] Upon verifying that any of the one or more network slices signalled by the second network node is supported or available in the area where the UE is served, the first network node configures the UE with MDT measurements, e.g., via measurement configuration 18 in Figure 1. Such MDT measurements configuration may consist of the MDT measurements configuration received from the second network node together with the one or more network slice identifiers.

[0133] In another embodiment, the first network node uses the information received from the second network node to configure a UE with logged MDT measurements, namely measurements logged by the UE while in RRCJdle or RRCJnactive and reported to the network once the UE moves back to RRC Connected. In this embodiment, the first network node will signal to the UE identifiers representing the one or more network slices received from the second network node. Additionally, the first network node can signal to the UE also the MDT measurements configuration that the UE shall collect when camping in any of the areas where the one or more network slices signalled to the UE by the first network node are served or are available.

[0134] In an embodiment the network node selects the UE to configure the MDT configuration based on the UE capabilities on the slicing features. To enable this solution, the network node needs to get an indication on the UE capability concerning support of the slice based cell selection / reselection. Some of the UE capabilities that network can consider selecting the UE to configure the slice based MDT are listed below. For example, the network node selects the UEs only if they support slice based cell selection reselection. This indicates that the UE is able to read slice information from SIB16. In another example the network node selects the UEs only if they support slice based random access (RA) resource selection, i.e., the UE is able to select the random access resources from specific Random Access Channel (RACH) partition and perform random access procedure. This indicates the UE is able to read the RACH partitioning and slice specific RACH partitions in System Information Block #1 (SIB1).

[0135] Upon receiving the information from the first network node, the UE is tasked to read from the broadcast information signalled by the camping cell whether the camping cell supports any of the network slices the UE received from the first network node. The UE can perform such check by, e.g. decoding SIB1 of an NR cell and deriving the NSAGs supported by the cell. If the cell where the UE is camping supports any of the network slices and / or NSAGs the UE received from the first network node, the UE will measure and log the MDT measurements configured by the first network node.

[0136] Alternatively or additionally, the UE may derive information concerning the slices / slice groups / cells supported by neighbour frequencies by, e.g. decoding SIB16 broadcast by the camping cell. With this, the UE may derive the neighbour cells supporting any of the network slices or NSAGs the UE received from the first network node. Hence, if any neighbour cell supports any of the network slices or NSAGs signalled to the UE by the first network node, the UE may reselect to such cell, if possible, and measure and log the MDT measurements configured by the first network node.

[0137] In a variant, the UE collects the measurements of the cells in the frequencies that at least one of the configured slices / slice groups (received as part of or beside the MDT configuration) is served by the network without performing cell reselection to such cells.

[0138] In another variant, the UE that is not performing cell selection / reselection based on network slices or based on network slice information broadcast by the network (e.g., is not configured from core network to perform cell selection / reselection per slices) logs in the MDT measurements an indication that it is not capable to determine an MDT area scope based on slice information, as it is not configured to read the SIB1 and / or SIB16. Generally, then, some embodiments herein include a network node, e.g. a RAN node or function, that receives information consisting of one or more network slices. Such information is used to determine an area where the one or more network slices are supported or available. With this information, the first network node is able to configure UEs with MDT measurements, which are collected by the UE while in radio resource control (RRC) Connected only if the UE is in an area where any of the received network slices is supported or available. Alternatively, the first network node can configure the UE with the list of network slices received and with associated MDT measurements. With this information the UE is able, while in RRC Idle or RRC Inactive to check if any of the camping cell or neighbour cell supports the slices received by the UE. If yes, the UE is able to camp on such cell, measure and log MDT measurements configured.

[0139] Some embodiments allow to enable a framework where MDT measurements are collected in areas where specific slices are supported or available. Therefore, the MDT collection process becomes targeted to areas where UEs are served with services associated with specific slices. The latter enables slice specific observability, which can be used to, for example, monitor whether service level agreements for a specific network slice are fulfilled.

[0140] Certain embodiments may provide one or more of the following technical advantage(s). Some embodiments enable an operator or a network to focus an MDT measurement collection in areas where specific slices are supported or available. This provides the advantage of collecting measurements that are pertinent to services associated with specific network slices and that can, for example, be used to monitor whether service level agreements for specific slices are fulfilled or not. In other words, some embodiments enable the network / operators to build e.g., a coverage map and / or data determining the performance of a slice in a given area of its deployed network based on the provided slices.

[0141] Additionally, some embodiments enable reduction in the amount of data collected when focusing on network slice observability. This implies a reduction of overhead in data uploading from the UE to the network, as well as a reduction of data post processing and filtering at the network because the data collected by UEs are triggered only if the UE is within areas where the network slice that need to be monitored are served.

[0142] Consider now additional details of some embodiments.

[0143] In one embodiment, the first network node, e.g. a RAN node, receives from a second network node, e.g. a core network (CN) function or the CAM system, information revealing the network slices or the groups of network slices that need to be supported or that need to be available in an area where the UE is served or camped. If such network slices or groups of network slices are supported or available in the area, the UE can collect MDT measurements within the area. The MDT measurements that should be collected by the UE in the areas where the slices or slice groups are served may also be signalled to the first network node by the second network node.

[0144] In one example of such embodiment, the first network node is a gNB, or a gNB-CU- CP, and the second network node is the AMF. Here, CU stands for central unit, CP stands for control plane, and AMF stands for Access and Mobility Function. In this non-limiting example, the first network node receives the information from the second network node via the NG interface. One instance of how such information can be signalled to the first network node is by means of modification of the existing MDT Configuration NR. Alternatively, the information can be included in any other suitable existing information element (IE) or in new lEs signalled over the interface connecting the first and second network node directly or indirectly. A possible implementation of how the information can be signalled to the first network node is provided below, using the example of enhancement to the MDT Configuration NR IE in TS 38.413 V17.6.0, as one example of the MDT configuration 16 in Figure 1. New lEs introduced to implement some embodiments are shown below in bold text.

[0145] 9.3.1.169 MDT Configuration-NR

[0146] This IE defines the MDT configuration parameters of NR.

[0147]

[0148]

[0149] From the above, it can be seen that the first network node optionally receives from the AMF a list of S-NSSAIs and / or a list of NSAGs. This information enables the first node to determine which network slices need to be served or need to be available in the areas where MDT measurements shall be collected by the UE.

[0150] In another embodiment, for the second network being an AMF, the AMF determines whether to send S-NSSAIs and / or list of NAGSs or indication of UE support of NSAG or slice based MDT to the first network, NG-RAN, taking into account the UE capabilities the AMF receives from the UE in the UE 5GMM Core Network Capability, e.g. NSAG capability or any additional capability for supporting e.g., slice based MDT. In another embodiment, the first network node may also receive a list of network slices or a list of slice groups that is used to determine the area in which MDT measurements are collected from neighbour cells. In one example, such list of network slices or a list of slice groups may be used to determine how to determine the Area Scope of Neighbour Cells. The area Scope of neighbour cells identifies details of neighbour cells for which MDT measurements shall be collected.

[0151] With the enhancements in this embodiment, the first network node would be informed about the network slices or network slice groups that need to be supported or available at the neighbour cell in order for the UE to collect MDT measurements from the neighbour cell. An example of how the Area Scope of Neighbour Cell may be enhanced is shown below, taking the IE definition in TS 38.413 as a starting point. New lEs introduced to implement some embodiments are shown below in bold text.

[0152] 9.3.1.182 Area Scope of Neighbour Cells

[0153] This IE defines the area scope of neighbour cells for logged MDT.

[0154] In the example above it can be seen that the Area Scope of Neighbour Cells has been enhanced with a list of S-NSSAIs and / or a list of NSAGs. The first network node therefore knows that the UE needs to be configured with this information so that the UE would measure MDT measurements from neighbour cells only if the listed network slices or groups of network slices are supported or available at the neighbour cell.

[0155] In one embodiment, the above enhancements to the MDT Area Scope and / or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE performs mobility or tentatively when the UE is expected to move to another network node for example as part of CHO configuration.

[0156] In one embodiment, the above enhancements to the MDT Area Scope and / or Area Scope of Neighbour Cells is passed from one network node to another. This can happen when the UE is for example in dual-connected mode. As discussed above, the first network node may be required to configure the UE over

[0157] RRC with the information received in the Area Scope of MDT and in the Area Scope of Neighbour Cells. Such configuration may occur by enhancing new lEs in the RRC protocol or by introducing new lEs to carry the information.

[0158] An example of how the information may be signalled to the UE is provided below, as one example of an area configuration 24 in Figure 2B which is included in a measurement configuration 18 of Figure 1 :

[0159] AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqT argetList- r 16 SEQUENCE(SIZE (1 ..maxFreq)) OF lnterFreqTargetlnfo-r16

[0160] OPTIONAL - Need R

[0161] AreaConfiguration-r1700 SEQUENCE { areaConfig-r17 AreaConfig-r16 OPTIONAL, -

[0162] Need R interFreqTargetl_ist-r17 SEQUENCE(SIZE (1 ..maxFreq)) OF lnterFreqTargetlnfo-r16

[0163] OPTIONAL - Need R

[0164] AreaConfiguration-v18xy ::= SEQUENCE {

[0165] NSAG-Area-r18 SEQUENCE (SIZE (1.. maxSlicelnfo-r17)) OF NSAG-ID-r17

[0166] OPTIONAL, - Need R slice-Area-r18 SEQUENCE (SIZE (1 ..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL - Need R

[0167] }

[0168] Below is a further example of how TS 38.331 V17.6.0 may be enhanced, with some embodiments herein introduced with the bold text below:

[0169] 5.5a Logged Measurements

[0170] <text omitted>

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

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

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

[0174] 1 > store the received loggingDuration, reportType and areaconfiguration, if included, in VarLogMeasConfig 1> if the LoggedMeasurementConfiguration message includes plmn-ldentityList.

[0175] 2> set plmn-ldentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-ldentityList

[0176] 1> else:

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

[0178] 1> store the received absoluteTimelnfo, traceReference, traceRecordingSessionRef, and tee- id \n VarLogMeasReport

[0179] 1> store the received bt-NameList, if included, in VarLogMeasConfig;

[0180] 1> store the received wlan-NameList, if included, in VarLogMeasConfig;

[0181] 1> store the received sensor-NameList, if included, in VarLogMeasConfig

[0182] 1 > start timer T330 with the timer value set to the loggingDuration;

[0183] 1> store the received sigLoggedMeasType, if included, in VarLogMeasReport

[0184] 1> store the received earlyMeasindication, if included, in VarLogMeasConfig;

[0185] 1> store the received NSAG-Area, if included, in VarLogMeasConfig;

[0186] 1> store the received slice-Area, if included, in VarLogMeasConfig

[0187] 5.5a.3.2 Initiation

[0188] While T330 is running and SDT procedure is not ongoing, the UE shall:

[0189] 1> if measurement logging is suspended:

[0190] 2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement logging;

[0191] 1> if not suspended, perform the logging in accordance with the following:

[0192] 2> if the reportType is set to periodical in the VarLogMeasConfig-.

[0193] 3> if the UE is in any cell selection state (as specified in TS 38.304

[0020] ):

[0194] 4> perform the logging at regular time intervals, as defined by the logginginterval in the VarLogMeasConfig;

[0195] 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-ldentityList stored in VarLogMeasReport;

[0196] 4> if areaconfiguration is not included in VarLogMeasConfig; or

[0197] 4> if the serving cell is part of the area indicated by areaConfig in areaconfiguration in VarLogMeasConfig; or

[0198] 4> if one of the slices supported by the PCell is included in slice-Area stored in VarLogMeasConfig or

[0199] 4> if one of the NSAG supported by the PCell is included in NSAG-Area stored in VarLogMeasConfig;

[0200] 5> perform the logging at regular time intervals, as defined by the logginginterval in the VarLogMeasConfig; > else if the reportType is set to eventTriggered, and eventType is set to outOfCoverage'.

[0201] 3> perform the logging at regular time intervals as defined by the logginginterval in VarLogMeasConfig only when the UE is in any cell selection state;

[0202] 3> upon transition from any cell selection state to camped normally state in NR:

[0203] 4> if the RPLMN is included in plmn-ldentityList stored in VarLogMeasReport; and

[0204] 4> if areaconfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfig of areaconfiguration in VarLogMeasConfig-.

[0205] 4> if one of the slices supported by the PCell is included in slice-Area stored in VarLogMeasConfig; or

[0206] 4> if one of the NSAG supported by the PCell is included in NSAG-Area stored in VarLogMeasConfig

[0207] 5> perform the logging; > else if the reportType is set to eventTriggered and eventType is set to eventLT.

[0208] 3> if the UE is in camped normally state on an NR cell and if the RPLMN is included in plmn-ldentityList stored in VarLogMeasReport.

[0209] 4> if areaconfiguration is not included in VarLogMeasConfig or

[0210] 4> if the serving cell is part of the area indicated by areaConfig in areaconfiguration in VarLogMeasConfig; or

[0211] 4> if one of the slices supported by the PCell is included in slice-Area stored in VarLogMeasConfig or

[0212] 4> if one of the NSAG supported by the PCell is included in NSAG-Area stored in VarLogMeasConfig;

[0213] 5> perform the logging at regular time intervals as defined by the logginginterval in VarLogMeasConfig only when the conditions indicated by the eventLI are met; >when performing the logging:

[0214] 3> if InterFreqTargetlnfo is configured and if the UE detected IDC problems on at least one of the frequencies included in InterFreqTargetlnfo or any inter-RAT frequency during the last logging interval, or

[0215] 3> if InterFreqTargetlnfo is not configured and if the UE detected IDC problems during the last logging interval:

[0216] 4> if measResultServingCell in the VarLogMeasReport is not empty:

[0217] 5> include InDeviceCoexDetected;

[0218] 5> suspend measurement logging from the next logging interval;

[0219] 4> else:

[0220] 5> suspend measurement logging; 3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged measurement configuration was received;

[0221] 3> if location information became available during the last logging interval, set the content of the locationinfo as in 5.3.3.7:

[0222] 3> if the UE is in any cell selection state (as specified in TS 38.304

[0020] ):

[0223] 4> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;

[0224] 4> if the reportType is set to eventTriggered in the VarLogMeasConfig and

[0225] 4> if the RPLMN at the time of entering the any cell selection state is included in plmn-ldentityList stored in VarLogMeasReport and

[0226] 4> if areaconfiguration is not included in VarLogMeasConfig or if the last suitable cell that the UE was camping on is part of the area indicated by areaConfig of areaconfiguration in VarLogMeasConfig-.

[0227] 5> set the servCellldentity to indicate global cell identity of the last suitable cell that the UE was camping on;

[0228] 5> set the measResultServingCell to include the quantities of the last suitable cell the UE was camping on;

[0229] 4> else if the reportType is set to periodical in the VarLogMeasConfig-.

[0230] 5> set the servCellldentity to indicate global cell identity of the last logged cell that the UE was camping on;

[0231] 5> set the measResultServingCell to include the quantities of the last logged cell the UE was camping on;

[0232] 3> else:

[0233] 4> set the servCellldentity to indicate global cell identity of the cell the UE is camping on;

[0234] 4> set the measResultServingCell to include the quantities of the cell the UE is camping on;

[0235] 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include measurements of neighbouring cell that became available during the last logging interval and according to the following: 4> include measurement results for at most 6 neighbouring cells on the NR serving frequency and for at most 3 cells per NR neighbouring frequency and for the NR neighbouring frequencies in accordance with the following:

[0236] 5> if InterFreqTargetlnfo is included in VarLogMeasConfig-.

[0237] 6> if earlyMeasindication is included in VarLogMeasConfig 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetlnfo and either in measIdleCarrierListNR (within the VarMeasidleConfig) or SIB4;

[0238] 6> else:

[0239] 7> include measurement results for NR neighbouring frequencies that are included in both interFreqTargetlnfo and SIB4:

[0240] 5> else:

[0241] 6> if earlyMeasIndication is included in VarLogMeasConfig

[0242] 7> include measurement results for NR neighbouring frequencies that are included in either measIdleCarrierListNR (within the VarMeasIdleConfig) or SIB4;

[0243] 6> else:

[0244] 7> include measurement results for NR neighbouring frequencies that are included in SIB4;

[0245] 4> include measurement results for at most 3 neighbours per inter-RAT frequency in accordance with the following:

[0246] 5> if earlyMeasIndication is included in VarLogMeasConfig-.

[0247] 6> include measurement results for inter-RAT neighbouring frequencies that are included in either measidleCarrierListEUTRA (within the VarMeasIdleConfig) or S / B5;

[0248] 5> else:

[0249] 6> include measurement results for inter-RAT frequencies that are included in S / B5;

[0250] 4> for each neighbour cell included, include the optional fields that are available;

[0251] NOTE 1 : The UE includes the latest results of the available measurements as used for cell reselection evaluation in RRCJDLE or RRCJNACTIVE, which are performed in accordance with the performance requirements as specified in TS 38.133

[0014] ,

[0252] NOTE 2: For logging the measurements on frequencies (indicated in measIdleCarrierListNR / measidleCarrierListEUTRA) in the logged measurement, the qualityThreshold in measidleConfig should not be applied, and how the UE logs the measurements on the frequencies is left to the UE implementation.

[0253] 2>when the memory reserved for the logged measurement information becomes full, stop timer T330 and perform the same actions as performed upon expiry of T330, as specified in 5.5a.1.4. As explained above, once the UE is configured with the information concerning the network slices and / or groups of network slices that shall be supported or available in an area where the UE is camped or served to enable the UE to collect MDT measurements in such area, the UE may check whether such network slices and / or groups of network slices are supported or available in the area where the UE is camped or served.

[0254] In one embodiment, the UE can do so by decoding SIB1 of a cell and deriving the NSAGs supported by the cell. If the cell where the UE is camping supports any of the network slices and / or NSAGs the UE received from the first network node as part of the Area Scope of MDT, the UE will measure and log the MDT measurements configured by the first network node.

[0255] The UE may also read SIB1 of a neighbour cell and derive the NSAGs supported by that cell. If the neighbour cell supports any of the network slices and / or NSAGs the UE received from the first network node as part of the Area Scope of Neighbour Cells, the UE will measure and log the MDT measurements configured by the first network node for the neighbour cell.

[0256] Alternatively or additionally, the UE may derive information concerning the cells supported by neighbour cells by, e.g. decoding SIB16 broadcast by the camping cell. With this, the UE may derive the neighbour cells supporting any of the network slices or NSAGs the UE received from the first network node either in the Area Scope of MDT or in the Area Scope of Neighbour Cells or both. Hence, if any neighbour cell supports any of the network slices or NSAGs signalled to the UE by the first network node, the UE may perform one or more of the following actions: reselect to such cell, if possible, and measure and log the MDT measurements configured by the first network node, if the slice or group of slices supported by the cell is included in the Area Scope of MDT measure and log the MDT measurements configured by the first network node as part of neighbour cell measurements, if the slice or group of slices supported by the cell is included in the Area Scope of Neighbour Cells

[0257] Extension of the slice-based MDT to the core network

[0258] Some embodiments above assume the UE is aware of the supported / available slices by reading the system information e.g., reading SIB1 to use slice specific random access (RA) resources or reading SIB16 to perform slice-based cell selection / reselection. However, each of the above UE capabilities might have some deficiencies as following. For example, a RAN node may not broadcast all the supported slices / NSAGs as part of random access channel (RACH) partitioning configuration in SIB1 or core network may not configure the UE to perform slice-based cell selection / re-selection.

[0259] An extension of some embodiments to ensure the UE is able to log the MDT measurements based on the supported / available slices in a specific area is to configure the UE over the Non-Access Stratum (NAS) with a list of configured slices / NSAGs for the sake of performing per-slice MDT measurements.

[0260] In another embodiment, the UE may use information already received over NAS or enhancements of such information, which describe to the UE the area of service of a slice or group of slices. The latter information indicates to the UE where a slice or group of slices are supported or available, in terms of e.g. cells and tracking areas. With such NAS configuration the UE will therefore know exactly in which areas of the network a slice is served or available. In this embodiment, when the first node, e.g., the RAN configures the UE with the list of slices and or group of slices received from the second network node (e.g. shown in the example of Area Scope for MDT IE enhancements above), it will be possible for the UE to determine in which area of the network the one or more slices signalled by the RAN to the UE are supported or available, because the UE has been configured via NAS about the Area of Service of such one or more network slices. Hence, the UE will be able to collect MDT measurements in the areas where the slices signalled to the UE by the RAN are supported or available.

[0261] In another embodiment, the UE may receive slice information, optionally including the area of service of the slice or group of slices and / or NSAGs over NAS that the UE do not receive in Configured NSSAI nor Allowed NSSAI / Partially Allowed NSSAI and is therefore not able to use for establishing Protocol Data Unit (PDU) Sessions, but the UE uses the information for the purpose of performing MDT measurements and reporting.

[0262] For a signalling-based MDT, the core network not only sends the MDT configuration to the NG-RAN node to configure the UE with the slice-based MDT configuration, the core network configures the UE over the NAS with information concerning a list of slices supported / available at the network. Examples of such information are provided below. In an embodiment, the core network provides the UE with a list of slice / NSAG IDs associated with a list of cell identities (indicating in which cell each slice is supported or available or where MDT is to be performed e.g. in a subset of the cells where the slice is supported or available). In another embodiment, the core network provides the UE a list of slice / NSAG IDs associated with a list of core network identifier e.g., TAI / TAC (indicating which slices / slice groups are supported / available in which tracking area or where MDT is to be performed e.g. in a subset of the TAIs / TACs where the slice is supported or available). Here, TAI stands for tracking area identity and TAC stands for tracking area code. In another embodiment, the core network provides the UE a list of slice / NSAG IDs associated with a list of frequencies (indicating which slices / slice groups are supported / available in which frequency or where MDT is to be performed e.g. in a subset of the frequencies where the slice is supported or available)

[0263] In a dependent embodiment, and in case of signalling based MDT, the above information / configuration are provided to the core network by the OAM system either as part of MDT configuration or beside the MDT configuration.

[0264] For a management-based MDT, the core network not only sends the MDT configuration to the NG-RAN node to configure the UE with the slice-based MDT configuration, the core network configures the UE over the NAS with information concerning a list of slices supported / available at the network. Examples of such information are provided below. In an embodiment, the core network provides the UE with a list of slice / NSAG IDs associated with a list of cell identities (indicating in which cell each slice is supported or available). In another embodiment, the core network provides the UE a list of slice / NSAG IDs associated with a list of core network identifier e.g., TAI / TAC (indicating which slices / slice groups are supported / available in which tracking area). In another embodiment, the core network provides the UE a list of slice / NSAG IDs associated with a list of frequencies (indicating which slices / slice groups are supported / available in which frequency)

[0265] In a depending embodiment, and in case of management-based MDT, the above information / configuration are provided to the core network by the OAM system or via the NG- RAN nodes upon selecting the UEs to perform the slice based MDT measurements.

[0266] The UE upon receiving the MDT configuration via RRC, including Area scope information including a list of slices or a list of slice groups, and upon receiving a list of slices provided per cell / tracking area / frequency received over NAS, performs the MDT measurements based on to the provided slice information and the MDT measurement configuration. In an embodiment, the UE determines whether to collect the MDT measurements per cell / tracking area / frequency of the serving cell / tracking area / frequency by means of information contained in the NAS configuration. If the cell / tracking area / frequency of the serving cell / tracking area / frequency is part of the provided configuration over NAS the UE collects the MDT measurements in an internal variable e.g., VarLogMeasReport and send to the network upon network request.

[0267] Embodiments herein include corresponding apparatuses. Embodiments herein for instance include a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0268] Embodiments also include a communication device 12 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. The power supply circuitry is configured to supply power to the communication device 12.

[0269] Embodiments further include a communication device 12 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the communication device 12 further comprises communication circuitry.

[0270] Embodiments further include a communication device 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the communication device 12 is configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[0271] Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[0272] Embodiments herein also include a network node 14-1 , 14-2 configured to perform any of the steps of any of the embodiments described above for the network node 14-1 , 14-2.

[0273] Embodiments also include a network node 14-1 , 14-2 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 14-1 , 14-2. The power supply circuitry is configured to supply power to the network node 14-1 , 14-2.

[0274] Embodiments further include a network node 14-1 , 14-2 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the network node 14-1 , 14-2. In some embodiments, the network node 14- 1 , 14-2 further comprises communication circuitry.

[0275] Embodiments further include a network node 14-1 , 14-2 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the network node 14-1 , 14-2 is configured to perform any of the steps of any of the embodiments described above for the network node 14-1 , 14-2.

[0276] More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

[0277] Figure 10 for example illustrates a communication device 12 as implemented in accordance with one or more embodiments. As shown, the communication device 12 includes processing circuitry 1010 and communication circuitry 1020. The communication circuitry 1020 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the communication device 1000.

[0278] The processing circuitry 1010 is configured to perform processing described above, e.g., in Figure 3, 4, and / or 5, such as by executing instructions stored in memory 1030. The processing circuitry 1010 in this regard may implement certain functional means, units, or modules.

[0279] Figure 11 illustrates a network node 14-1 , 14-2 as implemented in accordance with one or more embodiments. As shown, the network node 14-1 , 14-2 includes processing circuitry 1110 and communication circuitry 1120. The communication circuitry 1120 is configured to transmit and / or receive information to and / or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1110 is configured to perform processing described above, e.g., in Figure 6, 7, and / or 8, such as by executing instructions stored in memory 1130. The processing circuitry 1110 in this regard may implement certain functional means, units, or modules.

[0280] Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

[0281] A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

[0282] Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium. In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

[0283] Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

[0284] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.

[0285] In the example, the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1202, including one or more network nodes 1210 and / or core network nodes 1208.

[0286] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

[0287] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0288] The UEs 1212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1210 and other communication devices. Similarly, the network nodes 1210 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1212 and / or with other network nodes or equipment in the telecommunication network 1202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1202.

[0289] In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1206 includes one more core network nodes (e.g., core network node 1208) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1208. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and / or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider. The host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

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

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

[0292] In some examples, the UEs 1212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0293] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212c and / or 1212d) and network nodes (e.g., network node 1210b). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214. As another example, the hub 1214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0294] The hub 1214 may have a constant / persistent or intermittent connection to the network node 1210b. The hub 1214 may also allow for a different communication scheme and / or schedule between the hub 1214 and UEs (e.g., UE 1212c and / or 1212d), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and / or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1210b. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

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

[0296] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0297] The UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

[0300] In some embodiments, the power source 1308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1308 may further include power circuitry for delivering power from the power source 1308 itself, and / or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.

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

[0302] The memory 1310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1310 may allow the UE 1300 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1310, which may be or comprise a device-readable storage medium. The processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1318 and / or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

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

[0305] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1300 shown in Figure 13.

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

[0307] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

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

[0309] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

[0311] The network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. The network node 1400 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1400 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1400. The processing circuitry 1402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1400 components, such as the memory 1404, to provide network node 1400 functionality.

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

[0313] The memory 1404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1402. The memory 1404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and / or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated.

[0314] The communication interface 1406 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1406 comprises port(s) / terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. The communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and / or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0315] In certain alternative embodiments, the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

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

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

[0318] The power source 1408 provides power to the various components of network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein. For example, the network node 1400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1408. As a further example, the power source 1408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0319] Embodiments of the network node 1400 may include additional components beyond those shown in Figure 14 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.

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

[0321] The host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input / output interface 1506, a network interface 1508, a power source 1510, and a memory 1512. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.

[0322] The memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE. Embodiments of the host 1500 may utilize only a subset or all of the components shown. The host application programs 1514 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1514 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1500 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 1514 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. Figure 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

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

[0324] Hardware 1604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs 1608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.

[0325] The VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1608, and that part of hardware 1604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1608 on top of the hardware 1604 and corresponds to the application 1602.

[0326] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.

[0327] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

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

[0329] Embodiments herein also include those enumerated below as examples.

[0330] Group A Embodiments

[0331] A1 . A method performed by a communication device for minimization of drive test, MDT, measurement in a communication network, the method comprising: receiving, from a network node in the communication network, a measurement configuration that configures the communication device to collect MDT measurements and that indicates one or more network slices for which to collect MDT measurements.

[0332] A2. The method of embodiment A1 , wherein the measurement configuration indicates one or more areas for which the communication device is to collect MDT measurements, wherein the measurement configuration indicates the one or more areas in terms of the one or more network slices.

[0333] A3. The method of embodiment A2, wherein the one or more areas include, or are restricted to, the one or more network slices.

[0334] A4. The method of embodiment A3, further comprising: determining that the communication device is in one of the one or more areas; and based on the communication device being in one of the one or more areas according to said determining, collecting the MDT measurements.

[0335] A5. The method of embodiment A3, wherein the communication device is to collect the MDT measurements in a cell on which the communication device is served or camped if at least one of the one or more network slices supported and / or available in the cell is included in the one or more areas.

[0336] A6. The method of embodiment A5, further comprising: identifying one or more network slices that are supported and / or available in the cell on which the communication device is served or camped; and if at least one of the one or more identified network slices is included in the one or more areas, collecting the MDT measurements.

[0337] A7. The method of embodiment A2, wherein the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices is supported and / or available.

[0338] A8. The method of embodiment A7, wherein the communication device is to collect the MDT measurements in a cell on which the communication device is served or camped if the cell is included in the one or more areas.

[0339] A9. The method of any of embodiments A2-A8, wherein the measurement configuration is a logged measurement configuration that configures the communication device to log results of the MDT measurements while in an idle or inactive state, wherein the logged measurement configuration includes an area configuration that indicates the one or more areas as one or more areas for which the communication device is requested to perform logging of the results of the MDT measurements.

[0340] A10. The method of embodiment A9, further comprising, if at least one of any network slices supported by and / or available in a cell on which the communication device is camped in the idle or inactive state is included in the one or more areas, performing logging of results of the MDT measurements.

[0341] A11 . The method of embodiment A1 , wherein the measurement configuration includes an area configuration that indicates one or more areas for which the communication device is to collect the MDT measurements, wherein the communication device is to collect the MDT measurements in an indicated area if at least one of the one or more network slices is supported and / or available in the area.

[0342] A12. The method of embodiment A11 , further comprising: determining that the communication device is in an area for which the area configuration indicates the communication device is to collect the MDT measurements; identifying one or more network slices that are supported and / or available in the area; and if the one or more identified network slices include at least one of the one or more network slices indicated by the measurement configuration, collecting the MDT measurements.

[0343] A13. The method of embodiment A1 , wherein the measurement configuration indicates the one or more network slices for which the communication device is to collect the MDT measurements by indicating: one or more network slices that need to be supported and / or available in an area in order for the communication device to collect the MDT measurements for that area; or one or more network slices, at least one of which needs to be supported and / or available in any area for which the communication device collects the MDT measurements.

[0344] A14. The method of any of embodiments A11-A13, wherein an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0345] A15. The method of any of embodiments A11-A14, wherein the measurement configuration is included in a configuration that configures the communication device to collect the MDT measurements for any area in which at least one of the one or more network slices are supported and / or available.

[0346] A16. The method of any of embodiments A1-A15, wherein the measurement configuration indicates the one or more network slices for which the communication device is to collect the MDT measurements by indicating: one or more respective identifiers of the one or more network slices; or one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0347] A17. The method of any of embodiments A1-A16, wherein the network node is a radio network node and / or wherein the measurement configuration is received via radio resource control, RRC, signaling.

[0348] A18. The method of any of embodiments A1-A17, wherein the measurement configuration includes: a list of one or more respective identifiers of the one or more network slices; or a list of one or more network slice group identifiers that identify one or more respective network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0349] A19. The method of any of embodiments A1-A18, further comprising collecting the MDT measurements for one or more of the one or more network slices indicated by the measurement configuration.

[0350] A20. The method of embodiment A19, wherein collecting the MDT measurements comprises: performing the MDT measurements; and logging and / or reporting results of the performed MDT measurements.

[0351] A21 . The method of any of embodiments A1-A20, further comprising: identifying one or more network slices that are supported and / or available in an area; and if the one or more identified network slices include at least one of the one or more network slices for which the communication device is to collect the MDT measurements, collecting the MDT measurements.

[0352] A22. The method of embodiment A21 , wherein the area is an area on which the communication device is served or on which the communication device is camped.

[0353] A23. The method of embodiment A21 , wherein the area is a neighbor area that neighbors an area on which the communication device is served or on which the communication device is camped.

[0354] A24. The method of embodiment A23, wherein the neighbor area is a neighbor cell, and wherein said collecting comprises: performing cell reselection to switch to camping on the neighbor cell; and after camping on the neighbor cell, collecting the MDT measurements.

[0355] A25. The method of any of embodiments A21-A24, wherein said identifying comprises reading and / or decoding System Information broadcast in the area.

[0356] A26. The method of embodiment A25, wherein the System Information includes slice-specific information for slice-specific random access or slice-specific cell selection, and wherein said identifying comprises determining the one or more network slices that are supported and / or available in the area from the slice-specific information included in the System Information. / 27. The method of any of embodiments A21-A24, wherein said identifying comprises receiving, from a core network node, non-access stratum, NAS, signaling indicating the one or more network slices that are supported and / or available in the area.

[0357] A28. The method of embodiment A27, wherein the NAS signaling indicates: for each of one or more areas, a list of one or more network slices that are supported and / or available in that area; or for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available.

[0358] A29. The method of any of embodiments A1-A28, wherein the measurement configuration is specific to a certain measurement session.

[0359] A30. The method of any of embodiments A1-A29, wherein the MDT measurements include logged MDT measurements.

[0360] A31 . The method of any of embodiments A1-A29, wherein the MDT measurements include immediate MDT measurements.

[0361] AA1 . A method performed by a communication device configured for use in a communication network, the method comprising: receiving, from a network node in the communication network, signaling indicating one or more network slices that are supported and / or available in an area.

[0362] AA2. The method of embodiment AA1 , wherein the signaling is System Information signaling broadcast for the area.

[0363] AA3. The method of embodiment AA2, wherein the System Information signaling includes slicespecific information for slice-specific random access or slice-specific cell selection.

[0364] AA4. The method of embodiment AA1 , wherein the signaling is non-access stratum, NAS, signaling.

[0365] AA5. The method of any of embodiments AA1-AA4, wherein the signaling indicates: for each of one or more areas, a list of one or more network slices that are supported and / or available in that area; or for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available.

[0366] AA6. The method of any of embodiments AA1-AA5, wherein an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0367] AA7. The method of any of embodiments AA1-AA6, wherein the signaling indicates one or more network slices that are supported and / or available in the area by indicating: one or more respective identifiers of the one or more network slices; or one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0368] AA8. The method of any of embodiments AA1-AA7, wherein the signaling is radio resource control, RRC, signaling.

[0369] AA9. The method of any of embodiments AA1-AA7, wherein the signaling is non-access stratum, NAS, signaling.

[0370] AA10. The method of any of embodiments AA1 -AA9, wherein the area is a cell on which the communication device is served or on which the communication device camps.

[0371] AA11 . The method of any of embodiments AA1 -AA10, wherein the area is a neighbor cell that neighbors a cell on which the communication device is served or on which the communication device camps.

[0372] AA12. The method of any of embodiments AA1-AA11 , further comprising, if the one or more network slices include at least one of one or more network slices for which the communication device is to collect MDT measurements, collecting the MDT measurements for the area.

[0373] AA13. The method of embodiment AA12, wherein the area is a neighbor cell that neighbors a cell on which the communication device is served or on which the communication device camps, and wherein said collecting comprises: performing cell reselection to switch to camping on the neighbor cell; and after camping on the neighbor cell, collecting the MDT measurements for the neighbor cell.

[0374] AA14. The method of any of embodiments AA12-AA13, further comprising: logging the collected MDT measurements at the communication device; and / or reporting the collected MDT measurements to the communication network.

[0375] AA15. The method of any of embodiments AA12-AA14, wherein the MDT measurements include logged MDT measurements.

[0376] AA16. The method of any of embodiments AA12-AA14, wherein the MDT measurements include immediate MDT measurements.

[0377] AA17. The method of any of embodiments AA1-AA16, further comprising: determining, based on the one or more network slices that are supported and / or available in the area according to the signaling, whether or not the communication device is to collect MDT measurements in the area; and if it is determined to collect MDT measurements in the area, collecting MDT measurements in the area.

[0378] AAA1 . A method performed by a communication device configured for use in a communication network, the method comprising: transmitting, to a network node in the communication network, capability signaling indicating that the communication device is capable of performing slice-based MDT measurements.

[0379] AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.

[0380] Group B Embodiments

[0381] B1 . A method performed by a network node for minimization of drive test, MDT, measurements in a communication network, the method comprising: transmitting, to a communication device, a measurement configuration that configures the communication device to collect MDT measurements and that indicates one or more network slices for which to collect MDT measurements.

[0382] B2. The method of embodiment B1 , wherein the measurement configuration indicates one or more areas for which the communication device is to collect MDT measurements, wherein the measurement configuration indicates the one or more areas in terms of one or more network slices. B3. The method of embodiment B2, wherein the one or more areas include, or are restricted to, the one or more network slices.

[0383] B4. Reserved.

[0384] B5. The method of embodiment B3, wherein the communication device is to collect the MDT measurements in a cell on which the communication device is served or camped if at least one of the one or more network slices supported and / or available in the cell is included in the one or more areas.

[0385] B6. Reserved

[0386] B7. The method of embodiment B2, wherein the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices is supported and / or available.

[0387] B8. The method of embodiment B7, wherein the communication device is to collect the MDT measurements in a cell on which the communication device is served or camped if the cell is included in the one or more areas.

[0388] B9. The method of any of embodiments B2-B8, wherein the measurement configuration is a logged measurement configuration that configures the communication device to log results of the MDT measurements while in an idle or inactive state, wherein the logged measurement configuration includes an area configuration that indicates the one or more areas as one or more areas for which the communication device is requested to perform logging of the results of the MDT measurements.

[0389] B10. The method of embodiment B9, wherein the communication device is to perform logging of results of the MDT measurements if at least one of any network slices supported by and / or available in a cell on which the communication device is camped in the idle or inactive state is included in the one or more areas.

[0390] B11 . The method of embodiment B1 , wherein the measurement configuration includes an area configuration that indicates one or more areas for which the communication device is to collect the MDT measurements, wherein the communication device is to collect the MDT measurements in an indicated area if at least one of the one or more network slices is supported and / or available in the area. B12. Reserved

[0391] B13. The method of embodiment B1 , wherein the measurement configuration indicates one or more network slices for which the communication device is to collect the MDT measurements by indicating: one or more network slices that need to be supported and / or available in an area in order for the communication device to collect the MDT measurements for that area; or one or more network slices, at least one of which needs to be supported and / or available in any area for which the communication device collects the MDT measurements.

[0392] B14. The method of any of embodiments B11-B13, wherein an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0393] B15. The method of any of embodiments B11-B14, wherein the measurement configuration is included in a configuration that configures the communication device to collect the MDT measurements for any area in which at least one of the one or more network slices are supported and / or available.

[0394] B16. The method of any of embodiments B1-B15, wherein the measurement configuration indicates the one or more network slices for which the communication device is to collect the MDT measurements by indicating: one or more respective identifiers of the one or more network slices; or one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0395] B17. The method of any of embodiments B1-B16, wherein the network node is a radio network node and / or wherein the measurement configuration is transmitted via radio resource control, RRC, signaling.

[0396] B18. The method of any of embodiments B1-B17, wherein the measurement configuration includes: a list of one or more respective identifiers of the one or more network slices; or a list of one or more network slice group identifiers that identify one or more respective network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices. B19. The method of any of embodiments B1-B18, wherein the measurement configuration is specific to a certain measurement session.

[0397] B20. The method of any of embodiments B1-B19, wherein the MDT measurements include logged MDT measurements.

[0398] B21 . The method of any of embodiments B1-B19, wherein the MDT measurements include immediate MDT measurements.

[0399] BB1 . A method performed by a network node configured for use in a communication network, the method comprising: transmitting, to a communication device, signaling indicating one or more network slices that are supported and / or available in an area.

[0400] BB2. The method of embodiment BB1 , wherein the signaling is System Information signaling broadcast for the area.

[0401] BB3. The method of embodiment BB2, wherein the System Information signaling includes slicespecific information for slice-specific random access or slice-specific cell selection.

[0402] BB4. The method of embodiment BB1 , wherein the signaling is non-access stratum, NAS, signaling.

[0403] BB5. The method of any of embodiments BB1-BB4, wherein the signaling indicates: for each of one or more areas, a list of one or more network slices that are supported and / or available in that area; or for each of one or more network slices, a list of one or more areas in which the network slice is supported and / or available.

[0404] BB6. The method of any of embodiments BB1-BB5, wherein an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0405] BB7. The method of any of embodiments BB1-BB6, wherein the signaling indicates one or more network slices that are supported and / or available in the area by indicating: one or more respective identifiers of the one or more network slices; or one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0406] BB8. The method of any of embodiments BB1-BB7, wherein the signaling is radio resource control, RRC, signaling.

[0407] BB9. The method of any of embodiments BB1-BB7, wherein the signaling is non-access stratum, NAS, signaling.

[0408] BB10. The method of any of embodiments BB1-BB9, wherein the area is a cell on which the communication device is served or on which the communication device camps.

[0409] BB11. The method of any of embodiments BB1-BB10, wherein the area is a neighbor cell that neighbors a cell on which the communication device is served or on which the communication device camps.

[0410] Group X Embodiments

[0411] X1 . A method performed by a network node for minimization of drive test, MDT, measurements in a communication network, the method comprising: transmitting to, or receiving from, another network node an MDT configuration that indicates one or more network slices for which MDT measurements are to be collected.

[0412] X2. The method of embodiment X1 , wherein the MDT configuration indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration indicates the one or more areas in terms of the one or more network slices.

[0413] X3. The method of embodiment X2, wherein the one or more areas include, or are restricted to, the one or more network slices.

[0414] X4. The method of any of embodiments X2-X3, wherein the MDT measurements are to be collected in a cell if at least one of the one or more network slices supported and / or available in the cell is included in the one or more areas.

[0415] X5. The method of embodiment X2, wherein the one or more areas include, or are restricted to, cells in which at least one of the one or more network slices is supported and / or available.

[0416] X6. The method of embodiment X5, wherein the MDT measurements are to be collected in a cell if the cell is included in the one or more areas.

[0417] X7. The method of embodiment X1 , wherein the MDT configuration indicates the one or more network slices for which the MDT measurements are to be collected by indicating: one or more network slices that need to be supported and / or available in an area in order for the MDT measurements to be collected for that area; or one or more network slices, at least one of which needs to be supported and / or available in any area for the MDT measurements are collected.

[0418] X8. The method of embodiment X7, wherein an area is, or corresponds to, a cell, a frequency, a tracking area, a routing area, or a location area.

[0419] X9. The method of any of embodiments X1-X8, wherein the MDT configuration indicates the one or more network slices for which MDT measurements are to be collected by indicating the one or more network slices that are included in an area scope of the MDT measurements.

[0420] X10. The method of any of embodiments X1-X9, wherein the MDT configuration defines configuration parameters for the MDT measurements.

[0421] X11. Reserved

[0422] X12. The method of embodiment X10, wherein the MDT configuration includes an area scope parameter that defines an area scope of the MDT measurements as being slice-based.

[0423] X13. The method of embodiment X12, wherein the area scope parameter comprises: a list of one or more respective identifiers of the one or more network slices; or a list of one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices.

[0424] X14. Reserved.

[0425] X15. The method of any of embodiments X1-X14, wherein said transmitting or receiving comprises transmitting the MDT configuration.

[0426] X16. The method of embodiment X15, wherein the network node is an operations and maintenance, OAM, node, and wherein the another network node is a core network node. X17. The method of embodiment X15, wherein the network node is a core network node or an OAM node, and wherein the another network node is a radio network node.

[0427] X18. The method of any of embodiments X1-X14, wherein said transmitting or receiving comprises receiving the MDT configuration.

[0428] X19. The method of embodiment X18, wherein the network node is a core network node, and wherein the another network node is an operations and maintenance, OAM, node.

[0429] X20. The method of embodiment X18, wherein the network node is a radio network node, and wherein the another network node is a core network node or an OAM node.

[0430] X21 . The method of any of embodiment X18-X20, further comprising configuring one or more communication devices according to the MDT configuration.

[0431] X22. The method of embodiment X21 , further comprising selecting the one or more communication devices based on capability signaling received from the one or more communication devices indicating that each of the one or more communication devices supports slice-based MDT measurement collection.

[0432] X23. The method of any of embodiment X18-X22, further comprising collecting the MDT measurements for the one or more network slices.

[0433] X24. The method of any of embodiments X1-X23, further comprising transmitting, to a trace collection entity, a report of results of the MDT measurements as collected.

[0434] X25. The method of embodiment X24, wherein the report indicates the one or more network slices for which the MDT measurements were collected.

[0435] X26. The method of any of embodiments X1-X25, wherein the MDT measurements include logged MDT measurements.

[0436] X27. The method of any of embodiments X1-X25, wherein the MDT measurements include immediate MDT measurements.

[0437] Group C Embodiments

[0438] C1 . A communication device configured to perform the method of any of the Group A embodiments.

[0439] C2. A communication device comprising processing circuitry configured to perform the method of any of the Group A embodiments.

[0440] C3. A communication device comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group A embodiments.

[0441] C4. A communication device comprising: processing circuitry configured to perform the method of any of the Group A embodiments; and power supply circuitry configured to supply power to the communication device.

[0442] C5. A communication device comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication device is configured to perform the method of any of the Group A embodiments.

[0443] C6. The communication device of any of embodiments C1-C5, wherein the communication device is a wireless communication device.

[0444] C7. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform the method of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. C8. A computer program comprising instructions which, when executed by at least one processor of a communication device, causes the communication device to perform the method of any of the Group A embodiments.

[0445] C9. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0446] C10. A network node configured to perform the method of any of the Group B or Group X embodiments.

[0447] C11 . A network node comprising processing circuitry configured to perform the method of any of the Group B or Group X embodiments.

[0448] C12. A network node comprising: communication circuitry; and processing circuitry configured to perform the method of any of the Group B or Group X embodiments.

[0449] C13. A network node comprising: processing circuitry configured to perform the method of any of the Group B or Group X embodiments; power supply circuitry configured to supply power to the network node.

[0450] C14. A network node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the network node is configured to perform the method of any of the Group B or Group X embodiments.

[0451] C15. The network node of any of embodiments C10-C14, wherein the network node is a base station.

[0452] C16. A computer program comprising instructions which, when executed by at least one processor of a network node, causes the network node to perform the method of any of the Group B or Group X embodiments.

[0453] C17. The computer program of embodiment C16, wherein the network node is a base station. C18. A carrier containing the computer program of any of embodiments C16-C17, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Claims

CLAIMS1 . A method performed by a first network node (14-1) for minimization of drive test, MDT, measurements in a communication network (10), the method comprising: receiving, from a second network node (14-2), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

2. The method of claim 1 , wherein the MDT configuration (16) indicates the one or more areas in terms of one or more network slices (20).

3. The method of claim 2, wherein the MDT configuration (16) indicates the one or more areas in terms of one or more network slices (20) by defining the one or more areas as including, or being restricted to, the one or more network slices (20).

4. The method of any of claims 2-3, wherein the MDT configuration (16) includes an area scope parameter that defines an area scope (22) of the MDT measurements as being slicebased.

5. The method of claim 4, wherein the MDT configuration (16) indicates the one or more areas in terms of one or more network slices (20) by indicating one or more network slices (20) that are included in the area scope (22) of the MDT measurements.

6. The method of claim 5, wherein the area scope parameter comprises: a list of one or more respective identifiers of the one or more network slices (20) that are included in the area scope (22); or a list of one or more network slice groups, wherein each of the one or more network slice groups includes one or more of the one or more network slices (20) that are included in the area scope (22).

7. The method of any of claims 2-6, wherein the one or more areas are one or more first areas, wherein the MDT configuration (16) indicates the one or more first areas in terms of one or more network slices (20), wherein the method further comprises: determining one or more second areas that each supports at least one of the one ormore network slices (20); and transmitting, to one or more communication devices (12), an MDT configuration (16) that indicates an area scope (22) for collection of the MDT measurements as including the one or more second areas.

8. The method of claim 1 , wherein the MDT configuration (16) indicates one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

9. The method of claim 8, wherein the MDT configuration (16) indicates the one or more areas in terms of one or more cells, one or more frequencies, one or more tracking areas, one or more routing areas, or one or more location areas.

10. The method of any of claims 8-9, wherein the MDT configuration (16) indicates one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected, wherein the method further comprises: determining which one or more of the one or more areas indicated by the MDT configuration (16) support at least one of the one or more network slices (20) indicated by the MDT configuration (16); and transmitting, to one or more communication devices (12), an MDT configuration (16) that indicates an area scope (22) for collection of the MDT measurements as including the one or more determined areas.

11. The method of any of claims 1-10, wherein the network node is a radio network node, and wherein the another network node is a core network node or an OAM node.

12. The method of any of claims 1-11 , further comprising configuring one or more communication devices (12) according to the MDT configuration (16).

13. The method of any of claims 1-12, further comprising: collecting results of the MDT measurements; and transmitting, to a trace collection entity, a report of the results of the MDT measurements as collected.

14. A method performed by a second network node (14-2) for minimization of drive test, MDT, measurements in a communication network (10), the method comprising: transmitting, from the second network node (14-2) to a first network node (14-1), anMDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

15. The method of claim 14, wherein the second network node (14-2) is a core network node or an OAM node, and wherein the first network node (14-1) is a radio network node.

16. A first network node (14-1) for minimization of drive test, MDT, measurements in a communication network (10), the first network node (14-1) configured to: receive, from a second network node (14-2), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

17. The first network node (14-1) of claim 16, configured to perform the method of any of claims 2-13.

18. A second network node (14-2) for minimization of drive test, MDT, measurements in a communication network (10), the second network node (14-2) configured to: transmit, from the second network node (14-2) to a first network node (14-1), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

19. The second network node (14-2) of claim 18, wherein the second network node (14-2) is a core network node or an OAM node, and wherein the first network node (14-1) is a radio network node.

20. A computer program comprising instructions which, when executed by at least one processor of a first network node (14-1), causes the first network node (14-1) to perform the method of any of claims 1-13.

21. A computer program comprising instructions which, when executed by at least one processor of a second network node (14-2), causes the second network node (14-2) to perform the method of any of claims 14-15.

22. A carrier containing the computer program of any of claims 20-21 , wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

23. A first network node (14-1) for minimization of drive test, MDT, measurements in a communication network (10), the first network node (14-1) comprising: communication circuitry (1120); and processing circuitry (1110) configured to receive, from a second network node (14-2), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

24. The first network node (14-1) of claim 23, the processing circuitry (1110) configured to perform the method of any of claims 2-13.

25. A second network node (14-2) for minimization of drive test, MDT, measurements in a communication network (10), the second network node (14-2) comprising: communication circuitry (1120); and processing circuitry (1110) configured to transmit, from the second network node (14-2) to a first network node (14-1), an MDT configuration (16) that indicates one or more areas for which the MDT measurements are to be collected, wherein the MDT configuration (16) indicates: the one or more areas in terms of one or more network slices (20); or one or more network slices (20), at least one of which needs to be supported and / or available in any area for which the MDT measurements are collected.

26. The first network node (14-1) of claim 25, wherein the second network node (14-2) is a core network node or an OAM node, and wherein the first network node (14-1) is a radio network node.

Images