WO2021028811A1 - Minimisation de tests de couverture sur la base de faisceaux configurés - Google Patents

Minimisation de tests de couverture sur la base de faisceaux configurés Download PDF

Info

Publication number
WO2021028811A1
WO2021028811A1 PCT/IB2020/057497 IB2020057497W WO2021028811A1 WO 2021028811 A1 WO2021028811 A1 WO 2021028811A1 IB 2020057497 W IB2020057497 W IB 2020057497W WO 2021028811 A1 WO2021028811 A1 WO 2021028811A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
mdt
detected
user equipment
cell
Prior art date
Application number
PCT/IB2020/057497
Other languages
English (en)
Inventor
Wei Shen
Malik Wahaj ARSHAD
Pradeepa Ramachandra
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2021028811A1 publication Critical patent/WO2021028811A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering

Definitions

  • the present disclosure relates generally to wireless communications systems and, more particularly, to performing minimization of drive tests (MDT) based on configured beams in a radio communication network.
  • MDT minimization of drive tests
  • MDT Long Term Evolution
  • NR New Radio
  • Use cases for MDT in 3GPP TR 36.805, Rel-9 include:
  • MDT types based on radio resource control generally include two types of MDT measurement logging, referred to as Logged MDT and Immediate MDT.
  • a user equipment (UE) in RRCJDLE state may be configured to perform periodical MDT logging after receiving the MDT configurations from the network.
  • the UE may report the downlink (DL) pilot strength measurements (reference signal received power (RSRP)/reference signal received quality (RSRQ.) together with time information, detailed location information if available, and wireless local area network (WLAN), Bluetooth to the network using the UE information framework when it is in RRC_CONNECTED state.
  • the DL pilot strength measurement of Logged MDT may be collected based on the existing measurements required for cell reselection purpose, without imposing the UE to perform additional measurements.
  • Figure 1 illustrates an example of measurement logging for Logged MDT.
  • a UE may receive MDT configurations including logginginterval and loggingduration in an RRC message, e.g., LoggedMeasurementConfiguration, from the network.
  • a timer e.g., T330
  • the UE may perform periodical MDT logging with the interval set to logginginterval (e.g., 1.28 s - 61.44 s) when the UE is in RRCJDLE.
  • An example of MDT logging is illustrated in Figure 2.
  • Immediate MDT may be performed by a radio access node (RAN) and a UE.
  • RAN radio access node
  • M1-M9 A number of measurements (M1-M9) may be included for RAN measurements and UE measurements.
  • M1-M9 may be included for RAN measurements and UE measurements.
  • UE measurements a MDT configuration is based on existing RRC measurement procedures for configuration and reporting with some extensions for location information.
  • An example of measurement quantities for Immediate MDT is shown in Figure 3.
  • reporting of Immediate MDT may include the following:
  • Ml o Event-triggered measurement reports according to existing RRM configuration for events Al, A2, A3, A4, A5 A6, B1 or B2. o Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration.
  • gNB eNodeB
  • eNB user equipment
  • UE user equipment
  • network node can be any wireless communication device, including but not limited to cloud deployment
  • UE can also be any wireless communication device, and these two devices communicate with each other over a radio channel.
  • a method performed by a user equipment in a radio communication network includes receiving from the radio communication network a minimization of drive tests (MDT) configuration comprising a beam configuration.
  • the beam configuration comprises at least the identity of a beam and a cell identity of the beam.
  • the method further includes detecting at least one beam of a cell proximate to the user equipment.
  • the method further includes determining from the beam configuration whether the at least one detected beam is included in the beam configuration.
  • MDT minimization of drive tests
  • the method further includes performing MDT measurements; performing logging of the MDT measurements at an interval of a periodic logging interval when the at least one detected beam is included in the beam configuration; and omitting logging of the MDT measurements at an interval of the periodic logging interval when the at least one detected beam is not included in the beam configuration.
  • the method further includes storing the MDT measurements when the at least one detected beam is included in the beam configuration, and reporting the MDT measurements to the radio communication network when the at least one detected beam is included in the beam configuration.
  • the method further includes one of: receiving a configuration from a master node or a secondary node of the radio communication network for dual connectivity comprising a configuration for monitoring beams based on configured beams of a master cell group, a secondary cell group, or both a master cell group and a secondary cell group provided in an MDT area configuration; receiving a configuration from a master node of the radio communication network for dual connectivity comprising a configuration for both a master cell group and a secondary cell group or providing a separate configuration for a master cell group and a secondary cell group; and receiving a configuration from the radio communication network for carrier aggregation comprising a configuration for monitoring beams based on configured beams provided in an MDT area configuration.
  • MDT has not been specified for NR in involved standards in RAN2, RAN3 and SA5 groups. MDT may provide value for coverage detection and QoS verification. Performing MDT, however, may incur costs including, e.g., UE memory use, traffic overhead, etc. While a more accurate area selected by Operations,
  • OAM Administration, and Maintenance
  • Operational advantages may include enabling a UE to perform measurements logging when a beam configuration condition is fulfilled.
  • the network may collect more data which is relevant to the found problems (e.g., beam coverage issue) for a given logged MDT duration, interval and fixed reserved UE memory.
  • a UE may not need to store all of the measurements at each configured logging interval; instead, a UE may only store the corresponding measurements when the beam configuration condition is met, which may save UE memory. As a consequence, costs of MDT may be lower.
  • Figure 1 illustrates a measurement logging for Logged MDT
  • Figure 2 illustrates an example of a Logged MDT procedure
  • Figure 3 is a table illustrating measurement quantities for Immediate MDT
  • Figure 4 illustrates an SSB-lndex information element from 3GPP TS 38.331
  • Figure 5 illustrates a SSB-MTC information element from 3GPP TS 38.331
  • Figure 6 illustrates SSB-MTC field descriptions from 3GPP TS 38.331
  • Figure 7 is a table illustrating choices of area scope in MDT configuration received by eNB as defined in 3GPP TS 36.413;
  • Figure 8 illustrates an AreaConfiguration information element that may be sent to a UE as described in 3GPP TS 36.331;
  • Figure 9 illustrates operations of a UE camping normally on a cell for checking if the serving cell is part of an Area Scope if configured as described in 3GPP TS 36.331;
  • Figure 10 illustrates a Logged MDT procedure, in accordance with some embodiments of the present disclosure
  • Figure 11 illustrates UE beam detecting, in accordance with some embodiments of the present disclosure
  • Figure 12 illustrates a LoggedMeasurementConfiguration message, in accordance with some embodiments of the present disclosure
  • Figure 13 illustrates an AreaConfiguration information element included in a LoggedMeasurementConfiguration message
  • Figure 14 illustrates a BeamConfiguration information element included in a LoggedMeasurementConfiguration message, in accordance with some embodiments of the present disclosure
  • Figures 15-19 are flowcharts of operations that may be performed by a user equipment, in accordance with some embodiments of the present disclosure
  • Figures 20-23 are flowcharts of operations that may be performed by a network node, in accordance with some embodiments of the present disclosure
  • Figure 24 is a block diagram of elements of a user equipment that are configured according to some embodiments of the present disclosure.
  • Figure 25 is a block diagram of elements of a network node that are configured according to some embodiments of the present disclosure.
  • Figure 26 is a block diagram of a wireless network in accordance with some embodiments of the present disclosure.
  • a UE may perform cell selection and reselection based on measurements on downlink signals.
  • a Synchronization Signal (SS) block may include time-division multiplexed components each with the duration of one symbol as follows: (a) Primary Synchronization Signal (PSS), (b) Physical Broadcast Channel (PBCH), (c) Secondary Synchronization Signal (SSS) and finally (d) PBCH.
  • PSS Primary Synchronization Signal
  • PBCH Physical Broadcast Channel
  • SSS Secondary Synchronization Signal
  • PBCH may carry a small part of the system information, sometimes referred to as the Master Information Block (MIB).
  • MIB Master Information Block
  • the PSS+PBCH+SSS+PBCH structure may be denoted SS Block (SSB).
  • beamforming may be used to distribute the SSB over the coverage area of a cell.
  • Each SSB instance may be beamformed in a certain direction, either to ensure coverage or to provide beam finding support for subsequent link establishment.
  • the SS Block may be transmitted using beam sweeping where SSB is transmitted sequentially through pre-determined beam patterns that together cover the desired area.
  • Another approach for improving coverage may be repetition of wide (even omnidirectional) beam transmissions. Both beam sweeping and repetition may involve multiple transmissions.
  • Synchronization Signal (SSS) and Demodulation Reference Signal (DMRS) of PBCH may be used for Downlink (DL) based radio resource management (RRM) measurement for a UE in RRCJDLE or RRCJNACTIVE state.
  • RRM radio resource management
  • a UE in RRCJDLE or RRCJNACTIVE state may perform cell selection and re-selection based on measurements on the SS Blocks associated to cells.
  • 3GPP TS 38.331 (vl5.6.0) defines an SSB-lndex, as illustrated in Figure 4.
  • An information element may identify an SS-Block within an SS-Burst. See 3GPP TS 38.213, clause 4.1.
  • An IE SSB-MTC may be used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs.
  • a SSB-MTC IE is illustrated in Figure 5.
  • Figure 6 illustrates SSB-MTC field descriptions.
  • a RAN node may select UEs and activate MDT functionality to the selected UEs. A UE which is outside of the area scope may not been selected by the RAN node.
  • Figure 7 illustrates choices of area scope in MDT configuration received by eNB as defined in 3GPP TS 36.413. Referring to Figure 7, in the case of tracking area (TA) based, the tracking area identity (TAI) is derived using the current public land mobile network (PLMN).
  • PLMN public land mobile network
  • a UE does not check the area scope since the MDT configuration is not sent to the UE.
  • the UE may receive the area scope when the MDT configuration is sent to the UE.
  • a corresponding IE may be called AreaConfiguration as defined in 3GPP TS 36.331.
  • Figure 8 illustrates an AreaConfiguration IE that may be sent to a UE as described in 3GPP TS 36.331.
  • a UE camping normally on a cell may check if the serving cell is part of the area scope if configured, as illustrated in TS 36.331 and in Figure 9.
  • a UE camping normally in a cell may perform MDT logging if the serving cell is part of the configured area (i.e., AreaConfiguration).
  • the area scope can be also included in the MDT configuration.
  • MME OAM and mobility management entity
  • MME may send Trace Start containing the MDT configuration to the serving eNode B (eNB) of the UE, if the area scope criterion is specified and satisfied. If the area criterion is specified and is not satisfied, the MME may keep the MDT configuration first and then forward it to the serving eNB only when the area criterion is satisfied.
  • the eNB may store the MDT configuration and configure the UE when the UE moves to a cell in the eNB (intra eNB handover) that satisfies the area scope.
  • an eNB may propagate the MDT parameters to the target cell regardless of whether the source or target cell is part of the configured area scope in case of an Intra- PLMN handover over interfaces X2 or SI.
  • Best beam index (e.g., SSB index) of the camped cell may be included as part of the logged MDT report. Other measurements may be for further study.
  • An attempted SSB index can be indicated as part of random access procedure (RACH) failure information.
  • RACH random access procedure
  • SSB related information including an SSB index and number of preambles sent for each tried SSB in the RACH information report may be included.
  • SS Block index, channel state information reference signal (CSI-RS) index for both of serving and neighbouring cells could be included in the NR radio link failure (RLF) report.
  • RLF radio link failure
  • CSI-RS index and the corresponding number of preambles sent for each tried beam carrying CSI-RS index could be included in the NR RLF report also, if it is RACH procedure failure leading to the RLF.
  • Both of SSB index of the downlink beams of both serving cell and neighbour cells and supplementary uplink (SUL)/normal uplink (NUL) carrier information could be included in the 5G NR RRC connection failure reporting.
  • Beam RSRP/RSRQ. of the best beam of camped cell could be included in logged MDT report.
  • the number of good beams associated to the cells within the rangeToBestCell of the R value of the highest ranked cell could be included as part of the beam level measurements in the logged MDT report.
  • a UE may detect beams of a cell and derive the cell quality of a cell amongst the beams corresponding to the same cell based on SS/PBCH block.
  • existing approaches for performing MDT may incur costs including, e.g., UE memory use, traffic overhead, etc. While it may have been agreed in 3GPP RAN2 meetings that some beam information may be provided in Logged MDT, Immediate MDT, RLF Report, and accessibility measurement report, existing MDT approaches may not provide sufficient granularity to lower MDT costs.
  • a method may be provided for a radio communication network to configure a UE with BeamConfiguration in a Logged MDT configuration.
  • a UE may perform MDT measurements logging when a beam index of a detected beam matches with a configured beam index in a BeamConfiguration.
  • Advantages of various embodiments may enable a UE to only perform measurements logging when a beam configuration condition is fulfilled.
  • the network may collect more data which is relevant to the found problems (e.g., beam coverage issue) for a given logged MDT duration, interval and fixed reserved UE memory.
  • a UE may not need to store all of the measurements at each configured logging interval; instead, a UE may only store the corresponding measurements when the beam configuration condition is met, which may save UE memory.
  • a UE may detect beams of a cell and derive the cell quality of a cell amongst the beams corresponding to the same cell based on SS/PBCH block which is referred to as SSB. Furthermore, in an existing Logged MDT mechanism, a UE may perform logging when if the serving cell of the UE is part of the area indicated AreaConfiguration.
  • a Beam Configuration for MDT may be included.
  • the Beam Configuration (also referred to herein as beam configuration and BeamConfiguration) may include at least the identity of a beam and a cell identity of the beam. Beam Configuration may also include the identities of multiple beams and corresponding cell identities for each of the beams. Beam Configuration may be included in a list, a table, a mapping, a message, an information element, etc. Beam Configuration may include one or more beam indexes and each beam index may identify a beam and a cell identity of the beam. The Beam Configuration may also, or alternatively, include one or more beam indexes and each beam index may identify a beam, a cell identity of the beam, and a beam threshold. Further, the beam index may include a SSB index.
  • the beam configuration may be configured by the network to a UE as a port of the logged MDT configuration.
  • the UE may perform measurement logging based on the configured logging interval specified in the existing MDT configuration; otherwise, the UE may not need to store the measurements.
  • Figure 10 illustrates a Logged MDT procedure in accordance with some embodiments of the present disclosure.
  • the UE may perform measurement logging at the configured regular time intervals if the beam configuration condition is fulfilled.
  • the beam configuration may contain one or more than one beam indexes and each beam index may include one or more than one beam indexes and a cell identity of the beams.
  • the beam configuration may contain one or more than one beam indexes and each beam index may include one or more than one beam indexes, a cell identity of the beams and a beam threshold.
  • the beam threshold may be a defined value.
  • a UE may use a strongest beam to check if the beam configuration is fulfilled.
  • the UE may check if the strongest beam among the detected beams of the serving cell is a part of the BeamConfiguration. If so, the UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, the UE may not store the corresponding measurement result.
  • Figure 11 illustrates an example of a UE detecting beams SSB Al, SSB A2, and SSB A3 during one measurement on the serving cell. For example, if SSB A2 is the strongest beam, the UE may check to determine whether SSB A2 is a part of the BeamConfiguration.
  • the UE may check if the strongest beam among the detected beams of the neighboring cell is a part of the BeamConfiguration. If so, the UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, UE may not store the corresponding measurement result.
  • a UE may check if the strongest beam among the detected beams of the serving cell and the neighboring cell is a part of the BeamConfiguration. If either the strongest beam of the serving cell or the strongest beam of the neighbor cell or both fulfil the beam configuration, UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, UE may not store the corresponding measurement result. Referring to the example in Figure 11, if the strongest beam of the neighboring cell B is SSB B2 and the BeamConfiguration contains SSB A2 or SSB B2 or both, the BeamConfiguration is fulfilled.
  • a UE may use all detected beams to check if a
  • the UE may check if at least one beam among the detected beams of the serving cell is a part of the BeamConfiguration. If so, the UE may store the corresponding measurement result and reports to the network during the reporting procedure.
  • a UE may check if at least one beam among the detected beams of the neighboring cell is a part of the BeamConfiguration. If so, the UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, UE may not store the corresponding measurement result.
  • the UE may check if at least one beam among the detected beams of the serving cell and the neighboring cell is a part of the BeamConfiguration.
  • a UE may use beams within a range to the strongest beam to check if BeamConfiguration is fulfilled.
  • a UE may check if at least one beam which is within a range to the strongest beam among the detected beams of the serving cell is a part of the BeamConfiguration. If so, UE may store the corresponding measurement result and reports to the network during the reporting procedure.
  • a UE may check if at least one beam which is within a range to the strongest beam among the detected beams of the neighboring cell is a part of the BeamConfiguration. If so, the UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, the UE may not store the corresponding measurement result.
  • the UE may check if at least one beam which is within a range to the strongest beam among the detected beams of the serving cell and the neighboring cell is a part of the BeamConfiguration. If either the beams of the serving cell or the beams of the neighbor cell or both fulfill the beam configuration, the UE may store the corresponding measurement result and reports to the network during the reporting procedure. Otherwise, the UE may not store the corresponding measurement result.
  • whether a beam is within a range to the strongest beam among the detected beams may be determined by a defined beam threshold which is configured by the network.
  • Figure 12 illustrates a LoggedMeasurementConfiguration message, in accordance with some embodiments of the present disclosure
  • Figure 13 illustrates an AreaConfiguration information element included in a LoggedMeasurementConfiguration message
  • Figure 14 illustrates a BeamConfiguration information element included in a LoggedMeasurementConfiguration message, in accordance with some embodiments of the present disclosure
  • the UE can perform the following operations:
  • the UE may add a logged measurement entry in a UE variable (for example, in a VarLogMeasReport).
  • the measurement entry can include at least the following fields:
  • the measurement entry can include at least the following fields
  • the SSB index of the beam which is a part of the configured BeamConfiguration
  • the RSRQ value of the beam which is a part of the configured BeamConfiguration.
  • the measurement entry can include at least the following fields:
  • the SSB index of the beam which is a part of the configured BeamConfiguration
  • the RSRP value of the beam which is a part of the configured BeamConfiguration The RSRQ value of the beam which is a part of the configured BeamConfiguration;
  • MDT configured beam in dual connectivity and carrier aggregation scenarios
  • Various embodiments described in the present disclosure also apply to dual connectivity scenarios which means that the UE can be configured by a secondary node (SN) or a master node (MN) to only monitor the beams based on configured beams of a master cell group (MCG) or a secondary cell group (SCG) or both, provided in MDT area configuration.
  • SN secondary node
  • MN master node
  • MCG master cell group
  • SCG secondary cell group
  • a MN can provide a common area configuration that covers both MCG and SCG or separate configuration for MCG and SCG. This may be useful in multi radio access technology (RAT) DC scenarios since only NR RAT would support the beam concept and it may be relevant to provide MDT configuration including beam specification for NR RAT only.
  • RAT radio access technology
  • Various embodiments described in the present disclosure also apply to carrier aggregation scenarios which means that a UE can be configured to monitor beams based on configured beams provided in MDT area configuration.
  • Presently disclosed embodiments may provide potential advantages including, but not limited to, enabling a UE to only perform measurements logging when the beam configuration is fulfilled.
  • the network may collect more data, which may be relevant to found problems (e.g., a beam coverage issue) for a given logged MDT duration, interval and fixed reserved UE memory.
  • a UE may not need to store all of the measurements at each configured logging interval. Instead, a UE may store the corresponding measurements when the beam configuration is met, which may save UE memory.
  • Figures 15-19 are flowcharts of operations that may be performed by a UE.
  • Figures 20-23 are flowcharts of operations that may be performed by a network node.
  • operations can be performed by a UE (e.g., 2400 in Fig. 24) in a radio communication network.
  • the operations include receiving (1500) from the radio communication network a MDT configuration including a beam configuration.
  • the beam configuration may include at least the identity of a beam and a cell identity of the beam.
  • the operations further include detecting (1502) at least one beam of a cell proximate to the user equipment.
  • the operations further include determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration; performing (1506) MDT measurements; and performing (1508) logging of the MDT measurements at an interval of a periodic logging interval when the at least one detected beam is included in the beam configuration.
  • the operations further include omitting (1510) logging of the MDT measurements at an interval of the periodic logging interval when the at least one detected beam is not included in the beam configuration.
  • the MDT configuration is a logged MDT configuration.
  • the MDT configuration is an immediate MDT configuration.
  • the beam configuration includes one or more beam indexes and each beam index identifies a beam and a cell identity of the beam.
  • the beam configuration includes one or more beam indexes and each beam index identifies a beam, a cell identity of the beam, and a beam threshold.
  • the beam index includes a synchronization signal block (SSB) index.
  • SSB synchronization signal block
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting a strongest beam of a serving cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the detected strongest beam is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting a strongest beam of a neighboring cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the detected strongest beam is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting at least one strongest beam of a serving cell and/or a neighboring cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the at least one detected strongest beam of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a serving cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected multiple beams is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a neighboring cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected multiple beams is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a serving cell and/or a neighboring cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected multiple beams of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a serving cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a neighboring cell; and where the determining (15604) from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams is included in the beam configuration.
  • the UE can perform operations where the detecting (1502) at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a serving cell and/or a neighboring cell; and where the determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration comprises identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration
  • detecting (1502) at least one beam within a range to a detected strongest beam among detected beams may be based on a defined beam threshold configured by the network.
  • further operations that can be performed by the UE can include storing (1600) the MDT measurements when the at least one detected beam is included in the beam configuration. Further operations can include reporting (1602) the MDT measurements to the radio communication network when the at least one detected beam is included in the beam configuration.
  • storing (1600) the MDT measurements can include one or more of: an SSB index of a best beam; a reference signal received power value of the best beam; a reference signal received quality value of the best beam; an SSB index of the beam that is part of the beam configuration; a reference signal received power value of the beam that is part of the beam configuration; and a reference signal received quality value of the beam that is part of the beam configuration.
  • further operations that can be performed by the UE can include receiving (1700) a configuration from a master node (2500) or a secondary node (2500) of the radio communication network for dual connectivity including a configuration for monitoring beams based on configured beams of a master cell group, a secondary cell group, or both a master cell group and a secondary cell group provided in an MDT area configuration.
  • further operations that can be performed by the UE can include receiving (1800) a configuration from a master node (2500) of the radio communication network for dual connectivity including a configuration for both a master cell group and a secondary cell group or providing a separate configuration for a master cell group and a secondary cell group.
  • Figure 20 is a flowchart of operations that can be performed by a network node in a radio communications network (e.g., 2500 in Fig. 25) in accordance with some embodiments.
  • a network node in a radio communications network (e.g., 2500 in Fig. 25) in accordance with some embodiments.
  • the operations include sending (2000), to a user equipment (2400), a MDT configuration including a beam configuration.
  • the beam configuration can include at least the identity of a beam and a cell identity of the beam.
  • the operations further include receiving (2002), from the user equipment, MDT measurements during an interval of a periodic logging interval when the user equipment detected at least one beam included in the beam configuration.
  • the MDT configuration is a logged MDT configuration.
  • the MDT configuration is an immediate MDT configuration.
  • the beam configuration can include one or more beam indexes and each beam index identifies a beam and a cell identity of the beam. [00138] In some embodiments, the beam configuration can include one or more beam indexes and each beam index identifies a beam, a cell identity of the beam, and a beam threshold.
  • the beam index includes a synchronization signal block (SSB) index.
  • SSB synchronization signal block
  • further operations that can be performed by the network node can include sending (2100), to the user equipment, a configuration for dual connectivity including a configuration for monitoring beams based on configured beams of a master cell group, a secondary cell group, or both a master cell group and a secondary cell group provided in an MDT area configuration.
  • further operations that can be performed by the network node can include sending (2200), to the user equipment, a configuration for dual connectivity including a configuration for both a master cell group and a secondary cell group or providing a separate configuration for a master cell group and a secondary cell group.
  • further operations that can be performed by the network node can include sending (2300), to the user equipment, a configuration for carrier aggregation including a configuration for monitoring beams based on configured beams provided in an MDT area configuration.
  • FIG. 24 is a block diagram illustrating an exemplary UE 2400 that is configured according to some embodiments.
  • the UE 2400 can include, without limitation, a wireless terminal, a wireless communication device, a wireless communication terminal, a terminal node/UE/device, etc.
  • the UE 2400 includes a RF front-end 2430 comprising one or more power amplifiers the transmit and receive through antennas of an antenna array 2440 to provide uplink and downlink radio communications with a radio network node (e.g., a base station, eNB, gNB, etc.) of a radio communications network.
  • a radio network node e.g., a base station, eNB, gNB, etc.
  • UE 2400 further includes at least one processor circuit 2410 (also referred to as at least one processor) coupled to the RF front end 2430 and a memory circuit 2420 (also referred to as memory).
  • the memory 2420 stores computer readable program code that when executed by the at least one processor 2410 causes the at least one processor 2410 to perform operations according to embodiments disclosed herein.
  • FIG. 25 is a block diagram illustrating an exemplary network node 2500 (e.g., a base station, gNB, etc.) of a radio communications network.
  • the network node 2500 includes at least one processor circuit 2510 (also referred to as at least one processor), a memory circuit 2520 (also referred to as memory), and a network interface 2550 (e.g., wired network interface and/or wireless network interface) configured to communicate with other network nodes.
  • the network node 2500 may be configured as a radio network node containing a RF front end with one or more power amplifiers 2430 that transmit and receive through antennas of an antenna array 2540.
  • the memory 2520 stores computer readable program code that when executed by the at least one processor 2510 causes the at least one processor 2510 to perform operations according to embodiments disclosed herein.
  • Example Embodiments are discussed below. Reference numbers/letters are provided in parenthesis by way of example/illustration without limiting example embodiments to particular elements indicated by reference numbers/letters.
  • Embodiment 1 A method performed by a user equipment (2400) in a radio communication network.
  • the method includes receiving (1500) from the radio communication network a minimization of drive tests (MDT) configuration comprising a beam configuration, wherein the beam configuration comprises at least the identity of a beam and a cell identity of the beam.
  • the method further includes detecting (1502) at least one beam of a cell proximate to the user equipment.
  • the method further includes determining (1504) from the beam configuration whether the at least one detected beam is included in the beam configuration.
  • the method further includes performing (1506) MDT measurements.
  • the method further includes performing (1508) logging of the MDT measurements at an interval of a periodic logging interval when the at least one detected beam is included in the beam configuration.
  • the method further includes omitting (1510) logging of the MDT measurements at an interval of the periodic logging interval when the at least one detected beam is not included in the beam configuration.
  • Embodiment 2 The method of Embodiment 1, wherein the MDT configuration is a logged MDT configuration.
  • Embodiment 3 The method of Embodiment 1, wherein the MDT configuration is an immediate MDT configuration.
  • Embodiment 4 The method of any of Embodiments 1 to 3, wherein the beam configuration includes one or more beam indexes and each beam index identifies a beam and a cell identity of the beam.
  • Embodiment 5 The method of any of Embodiments 1 to 3, wherein the beam configuration includes one or more beam indexes and each beam index identifies a beam, a cell identity of the beam, and a beam threshold.
  • Embodiment 6. The method of any of Embodiments 4 to 5, wherein the beam index includes a synchronization signal block (SSB) index.
  • SSB synchronization signal block
  • Embodiment 7 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting a strongest beam of a serving cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the detected strongest beam is included in the beam configuration.
  • Embodiment 8 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting a strongest beam of a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the detected strongest beam is included in the beam configuration.
  • Embodiment 9 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting at least one strongest beam of a serving cell and/or a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether the at least one detected strongest beam of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration.
  • Embodiment 10 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a serving cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected multiple beams is included in the beam configuration.
  • Embodiment 11 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected multiple beams is included in the beam configuration.
  • Embodiment 12 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting multiple beams of a serving cell and/or a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration comprises identifying whether at least one of the detected multiple beams of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration.
  • Embodiment 13 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a serving cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams is included in the beam configuration.
  • Embodiment 14 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams is included in the beam configuration.
  • Embodiment 15 The method of any of Embodiments 1 to 6, wherein the detecting at least one beam of a cell proximate to the user equipment includes detecting at least one beam within a range to a detected strongest beam among detected beams of a serving cell and/or a neighboring cell, and wherein the determining from the beam configuration whether the at least one detected beam is included in the beam configuration includes identifying whether at least one of the detected beams within range to the detected strongest beam among the detected beams of the serving cell, the neighboring cell, and/or the serving cell and the neighboring cell is included in the beam configuration.
  • Embodiment 16 The method of any of Embodiments 13 to 15, wherein the detecting at least one beam within a range to a detected strongest beam among detected beams is based on a defined beam threshold configured by the network.
  • Embodiment 17 The method of any of Embodiments 1 to 16, further including storing (1600) the MDT measurements when the at least one detected beam is included in the beam configuration; and reporting (1602) the MDT measurements to the radio communication network when the at least one detected beam is included in the beam configuration.
  • Embodiment 18 The method of Embodiment 17, wherein storing the MDT measurements includes storing one or more of: an SSB index of a best beam; a reference signal received power value of the best beam; a reference signal received quality value of the best beam; an SSB index of the beam that is part of the beam configuration; a reference signal received power value of the beam that is part of the beam configuration; and a reference signal received quality value of the beam that is part of the beam configuration.
  • Embodiment 19 The method of any of Embodiments 1 to 18, further including receiving (1700) a configuration from a master node (2500) or a secondary node (2500) of the radio communication network for dual connectivity comprising a configuration for monitoring beams based on configured beams of a master cell group, a secondary cell group, or both a master cell group and a secondary cell group provided in an MDT area configuration.
  • Embodiment 20 The method of any of Embodiments 1 to 18, further including receiving (1800) a configuration from a master node (2500) of the radio communication network for dual connectivity comprising a configuration for both a master cell group and a secondary cell group or providing a separate configuration for a master cell group and a secondary cell group.
  • Embodiment 21 The method of any of Embodiments 1 to 18, further including receiving (1900) a configuration from the radio communication network for carrier aggregation comprising a configuration for monitoring beams based on configured beams provided in an MDT area configuration.
  • Embodiment 22 A user equipment (2400) for operating in a radio communication network.
  • the user equipment includes at least one processor (2410); and a memory (2420) coupled with the at least one processor, wherein the memory includes instructions that when executed by the at least one processor causes the user equipment to perform operations according to any of Embodiments 1 to 21.
  • Embodiment 23 A user equipment (2400) adapted to perform according to any of Embodiments 1 to 21.
  • Embodiment 24 A user equipment (2400) for operating in a radio communication network.
  • the user equipment configured to: receive from the radio communication network a minimization of drive tests (MDT) configuration comprising a beam configuration, wherein the beam configuration comprises at least the identity of a beam and a cell identity of the beam; detect at least one beam of a cell proximate to the user equipment; determine from the beam configuration whether the at least one detected beam is included in the beam configuration; perform MDT measurements; perform logging of the MDT measurements at an interval of a periodic logging interval when the at least one detected beam is included in the beam configuration; and omit logging of the MDT measurements at an interval of the periodic logging interval when the at least one detected beam is not included in the beam configuration.
  • MDT minimization of drive tests
  • Embodiment 25 A computer program including program code to be executed by at least one processor (2410) of a user equipment (2400) configured to operate in a radio communication network, whereby execution of the program code causes the user equipment (2400) to perform operations according to any of Embodiments 1 to 21.
  • Embodiment 26 A computer program product including a non-transitory storage medium including program code to be executed by at least one processor (2410) of a user equipment (2400) configured to operate in a radio communication network, whereby execution of the program code causes the user device (2000) to perform operations according to any of Embodiments 1 to 21.
  • Embodiment 27 A method by a network node (2500) in a radio communications network.
  • the method includes: sending (2000), to a user equipment (2400), a minimization of drive tests (MDT) configuration including a beam configuration, wherein the beam configuration includes at least the identity of a beam and a cell identity of the beam; and receiving (2002), from the user equipment, MDT measurements during an interval of a periodic logging interval when the user equipment detected at least one beam included in the beam configuration.
  • MDT minimization of drive tests
  • Embodiment 28 The method of Embodiment 27, wherein the MDT configuration is a logged MDT configuration.
  • Embodiment 29 The method of Embodiment 27, wherein the MDT configuration is an immediate MDT configuration.
  • Embodiment 30 The method of any of Embodiments 27 to 29, wherein the beam configuration includes one or more beam indexes and each beam index identifies a beam and a cell identity of the beam.
  • Embodiment 31 The method of any of Embodiments 27 to 29, wherein the beam configuration includes one or more beam indexes and each beam index identifies a beam, a cell identity of the beam, and a beam threshold.
  • Embodiment 33 The method of any of Embodiments 30 to 31, wherein the beam index includes a synchronization signal block (SSB) index.
  • SSB synchronization signal block
  • Embodiment 34 The method of any of Embodiments 27 to 32, further including: sending (2100), to the user equipment, a configuration for dual connectivity comprising a configuration for monitoring beams based on configured beams of a master cell group, a secondary cell group, or both a master cell group and a secondary cell group provided in an MDT area configuration.
  • Embodiment 35 The method of any of Embodiments 27 to 32, further including: sending (2200), to the user equipment, a configuration for dual connectivity including a configuration for both a master cell group and a secondary cell group or providing a separate configuration for a master cell group and a secondary cell group.
  • Embodiment 36 The method of any of Embodiments 27 to 32, further including: sending (2300), to the user equipment, a configuration for carrier aggregation including a configuration for monitoring beams based on configured beams provided in an MDT area configuration.
  • Embodiment 37 A network node (2500) adapted to perform according to any of Embodiments 27 to 35.
  • Embodiment 38 A network node (2500) for configuring a user equipment (2400) with a beam configuration for a minimization of drive tests (MDT) configuration in a radio communication network.
  • the network node configured to: send, to the user equipment, the MDT configuration comprising a beam configuration, wherein the beam configuration comprises at least the identity of a beam and a cell identity of the beam; and receiving, from the user equipment, MDT measurements during an interval of a periodic logging interval when the user equipment detected at least one beam included in the beam configuration.
  • Embodiment 39 A network node (2500) for configuring a user equipment (2400) with a beam configuration for a minimization of drive tests (MDT) configuration in a radio communication network.
  • the network node including: at least one processor (2510); and a memory (2520) coupled to the at least one processor, wherein the memory stores instructions that when executed by the at least one processor causes the processor to perform operations according to any of Embodiments 27 to 35.
  • Embodiment 40 A computer program including program code to be executed by at least one processor (2510) of a network node (2500) configured to operate in a radio communication network, whereby execution of the program code causes the network node (2500) to perform operations according to any of Embodiments 27 to 35.
  • Embodiment 41 A computer program product including a non-transitory storage medium including program code to be executed by at least one processor (2510) of a network node (2500) configured to operate in a radio communication network, whereby execution of the program code causes the network node (2500) to perform operations according to any of Embodiments 27 to 35.
  • the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open- ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof.
  • the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item.
  • the common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
  • Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits.
  • These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
  • two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
  • the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated.
  • other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts.
  • some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
  • Figure 26 A wireless network in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in Figure 26.
  • the wireless network of Figure 26 only depicts network Q.Q.106, network nodes Q.Q.160 and QQ160b, and WDs Q.Q.110, QQllOb, and QQllOc (also referred to as mobile terminals).
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z- Wave and/or ZigBee standards.
  • Network Q.Q.106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node Q.Q.160 and WD Q.Q.110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • 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)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also 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 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.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • 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).
  • DAS distributed antenna system
  • network nodes include 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node Q.Q.160 includes processing circuitry Q.Q.170, device readable medium Q.Q.180, interface Q.Q.190, auxiliary equipment Q.Q.184, power source Q.Q.186, power circuitry Q.Q.187, and antenna QQ162.
  • network node Q.Q.160 illustrated in the example wireless network of Figure 26 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 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.
  • network node Q.Q.160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB's.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node Q.Q.160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 QQ160.
  • Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 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.
  • processing information obtained by processing circuitry QQ170 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.
  • Processing circuitry QQ170 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 QQ160 components, such as device readable medium QQ180, network node QQ160 functionality.
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry Q.Q.170 may include a system on a chip (SOC).
  • processing circuitry Q.Q.170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.
  • processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 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 processing circuitry QQ170.
  • 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
  • Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry Q.Q.170 and, utilized by network node QQ160.
  • Device readable medium Q.Q.180 may be used to store any calculations made by processing circuitry Q.Q.170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection.
  • Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162.
  • Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196.
  • Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196.
  • the radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface Q.Q.190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna Q.Q.162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry Q.Q.187 and/or network node QQ160.
  • network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry Q.Q.187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node QQ160 may include additional components beyond those shown in Figure 26 that may be responsible 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.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to- vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to- vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD 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 WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE or other terminal implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ110 includes antenna QQ111, interface Q.Q.114, processing circuitry Q.Q.120, device readable medium Q.Q.130, user interface equipment Q.Q.132, auxiliary equipment Q.Q.134, power source Q.Q.136 and power circuitry Q.Q.137.
  • WD Q.Q.110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.
  • Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114.
  • antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port.
  • Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna Q.Q.111 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111.
  • WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 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 WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry Q.Q.120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ110 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry Q.Q.120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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.
  • processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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.
  • Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110.
  • User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110.
  • the type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits.
  • User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry Q.Q.120 to process the input information.
  • User interface equipment Q.Q.132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry.
  • User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry.
  • WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD Q.Q.110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD Q.Q.110 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source Q.Q.136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé mis en œuvre par un équipement d'utilisateur dans un réseau de communication sans fil. Le procédé comprend la réception d'une configuration de minimisation de tests de couverture (MDT) comprenant une configuration de faisceau. La configuration de faisceau comprend au moins l'identité d'un faisceau et l'identité d'une cellule du faisceau. Le procédé comprend, en outre, les étapes consistant à détecter au moins un faisceau d'une cellule à proximité de l'équipement d'utilisateur, déterminer, à partir de la configuration de faisceau, si le ou les faisceaux détectés sont inclus dans la configuration de faisceau, effectuer des mesures MDT, effectuer un enregistrement des mesures MDT à un certain intervalle d'un intervalle d'enregistrement périodique lorsque ledit ou lesdits faisceaux détectés sont inclus dans la configuration de faisceau, et omettre l'enregistrement des mesures MDT à un certain intervalle de l'intervalle d'enregistrement périodique lorsque ledit ou lesdits faisceaux détectés ne sont pas inclus dans la configuration de faisceau.
PCT/IB2020/057497 2019-08-15 2020-08-08 Minimisation de tests de couverture sur la base de faisceaux configurés WO2021028811A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962887269P 2019-08-15 2019-08-15
US62/887,269 2019-08-15

Publications (1)

Publication Number Publication Date
WO2021028811A1 true WO2021028811A1 (fr) 2021-02-18

Family

ID=72086935

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/057497 WO2021028811A1 (fr) 2019-08-15 2020-08-08 Minimisation de tests de couverture sur la base de faisceaux configurés

Country Status (1)

Country Link
WO (1) WO2021028811A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020038374A1 (fr) * 2018-08-21 2020-02-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de mesurage de faisceau, dispositif de réseau, et équipement utilisateur

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020038374A1 (fr) * 2018-08-21 2020-02-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de mesurage de faisceau, dispositif de réseau, et équipement utilisateur

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
3GPP TR 36.805
3GPP TS 38.213, CLAUSE 4.1
3GPP TS 38.331 (V15.6.0
CMCC: "Beam Related Measurements for NR MDT", vol. RAN WG2, no. Xi'an, China; 20190408 - 20190412, 29 March 2019 (2019-03-29), XP051693565, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F105bis/Docs/R2%2D1904345%2Ezip> [retrieved on 20190329] *
CMCC: "Network aspects of MDT for NR", vol. RAN WG3, no. Athens, Greece; 20190225 - 20190301, 16 February 2019 (2019-02-16), XP051604506, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F103/Docs/R3%2D190568%2Ezip> [retrieved on 20190216] *
ERICSSON ET AL: "Details of beam level measurements to be included in MDT", vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), XP051730326, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN2/Docs/R2%2D1906874%2Ezip> [retrieved on 20190513] *
HUAWEI ET AL: "Considerations on MDT configurations", vol. RAN WG2, no. Reno, Nevada, USA; 20190513 - 20190517, 3 May 2019 (2019-05-03), XP051711972, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5F106/Docs/R2%2D1907692%2Ezip> [retrieved on 20190503] *

Similar Documents

Publication Publication Date Title
US20220086738A1 (en) Device, Network, and Method for Network Adaptation and Utilizing a Downlink Discovery Reference Signal
US20220386154A1 (en) Methods of configuring ssb/pci for use by a ue and related user equipment and network nodes
JP2019537903A (ja) アクティブモードモビリティ測定のための測定設定
US11223983B2 (en) Automatic neighbour relation (ANR) based on detection and reporting of unknown cell based on measurement triggering criterion
JP2020530692A (ja) ユーザ機器の測定設定
US11218897B2 (en) System and method for controlling measurement gaps in a communication system
EP3571863B1 (fr) Planification de segment sc-mcch pour femtc et enb-iot
US20230269790A1 (en) Overlayed cell access handling
US20230121925A1 (en) Cell Quality Derivation Configuration
US20230403590A1 (en) Simultaneous quality of experience measurement configurations for incapable user equipments
US20230239937A1 (en) Enhanced event reporting for multiple-trp cell mobility
US20230060444A1 (en) System Information Message Transmission Indication
US11259287B2 (en) Methods and apparatus relating to synchronization sequence detection in a wireless communication network
WO2022234540A1 (fr) Impacts d&#39;interface et d&#39;architecture de mobilité centrée l1/l2
EP4193635A1 (fr) Procédés permettant un transfert de mesures entre des noeuds ran
WO2021028811A1 (fr) Minimisation de tests de couverture sur la base de faisceaux configurés
US20230164609A1 (en) Measurement identities coordination between master node and secondary node
US11956739B2 (en) Methods providing system frame number offset over application protocol interface and related networks and network nodes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20756974

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20756974

Country of ref document: EP

Kind code of ref document: A1