WO2021045672A1 - Commande de mesure de brouillage entre liaisons (cli) au niveau d'un équipement d'utilisateur - Google Patents

Commande de mesure de brouillage entre liaisons (cli) au niveau d'un équipement d'utilisateur Download PDF

Info

Publication number
WO2021045672A1
WO2021045672A1 PCT/SE2020/050836 SE2020050836W WO2021045672A1 WO 2021045672 A1 WO2021045672 A1 WO 2021045672A1 SE 2020050836 W SE2020050836 W SE 2020050836W WO 2021045672 A1 WO2021045672 A1 WO 2021045672A1
Authority
WO
WIPO (PCT)
Prior art keywords
measurements
cli
wireless device
reference signals
measurement configuration
Prior art date
Application number
PCT/SE2020/050836
Other languages
English (en)
Inventor
Icaro L. J. Da Silva
Lian ARAUJO
Jonas SEDIN
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 WO2021045672A1 publication Critical patent/WO2021045672A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/541—Allocation or scheduling criteria for wireless resources based on quality criteria using the level of interference

Definitions

  • Embodiments of the present disclosure relate to wireless networks, and particularly to methods, apparatus and machine-readable media for performing measurements in a wireless network.
  • New Radio supports flexible downlink (DL)/uplink (UL) transmission directions in both paired and unpaired spectrum.
  • DL downlink
  • UL uplink
  • paired spectrum there is dedicated frequency for DL and for UL (typically Frequency division Duplex - FDD).
  • unpaired spectrum there is a single carrier frequency for DL and UL (typically Time Division Duplex - TDD).
  • NR supports paired and unpaired spectrum and strives to maximize commonality between the technical solutions, allowing FDD operation on a paired spectrum, different transmission directions in either part of a paired spectrum, TDD operation on an unpaired spectrum where the transmission direction of time resources is not dynamically changed, and TDD operation on an unpaired spectrum where the transmission direction of most time resources can be dynamically changing.
  • DL and UL transmission directions at least for data can be dynamically assigned on a per-slot basis at least in a TDM manner. It is noted that transmission directions include all of downlink, uplink, sidelink, and backhaul link.
  • NR supports at least semi-statically assigned DL/UL transmission direction as gNB operation, i.e., the assigned DL/UL transmission direction can be signaled to UE by higher layer signaling.
  • This flexible design in NR allows Orthogonal Frequency Division Multiplexing (OFDM) symbols in a slot to be classified as 'downlink', 'flexible', or 'uplink'.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the slot formats defined in subclause 11.1 of 3GPP TS 38.213 v15.5.0 can be used in combination with Radio Resource Control, RRC, signaling to inform the transmission direction in OFDM symbols, valid for one or more slots.
  • Subclause 11.1 provides slot formats for formats 1-255 for normal cyclic prefix.
  • formats 0-55 symbols numbered 0-13 are assigned as either downlink (D), uplink (U) or flexible (F). Formats 56- 254 are reserved.
  • format 255 the UE determines the slot format for a slot based on TDD-UL-DL- ConfigurationCommon, or TDD-UL-DL-ConfigDedicated and, if any, on detected DCI formats.
  • the scheduler may dynamically determine the transmission direction, called dynamic TDD.
  • dynamic TDD the transmission direction
  • it can actually be applicable to half-duplex FDD as well or even full-duplex operation, although in this case there may be limited need to coordinate uplink and downlink scheduling decisions.
  • This provides NR with a flexible framework that can cope with rapid traffic variations, e.g. during periods of high DL data transmission, most of the slots could be defined as downlink to accommodate those transmissions.
  • CLI cross-link interference
  • Figure 1 shows an illustration of interference (in dashed boxes) due to different TDD configurations in network A and B.
  • Figure 1 shows six consecutive time resources e.g., slots, OFDM symbols, etc. for two networks or cells. Interference may occur in the fourth and sixth time resources, as they are respectively defined as DL and UL in Network A, and UL and DL in Network B.
  • Cross-link interference may occur in at least two cases.
  • a UE-1 is connected to a TRP-A (e.g. a cell A) and is using a resource-X for its UL transmissions, while another TRP-B (e.g. cell-B) is using that same resource for the downlink (DL) of a UE-2 connected to it.
  • TRP-A e.g. a cell A
  • another TRP-B e.g. cell-B
  • UE-2 connected to TRP- B will suffer interference in its DL caused by the UL transmissions of UE-1 to TRP-A i.e. causing DL degradation to UE-2.
  • there is an UL degradation to a UE i.e. the problem is in the UL of the UE-1, which receives interference from UE-2 whose DL transmissions are on the same resources.
  • the interference caused by the DL’s TRP-B in the UE’s UL transmissions to TRP-A, corresponding to the first case of UL degradation, may be considered more critical than the case where the DL of UE-2 connected to TRP-B is interfered by the UL of UE-1.
  • Figure 2 illustrates this cross-link interference scenario, considering a scheduling on the same or partially-overlapping time-frequency resources in which UE-1 is scheduled for UL in Cell A and UE-2 is scheduled for DL in Cell B.
  • the DL from Cell B may be a source of interference for the UL reception scheduled in Cell A, called TRP-to-TRP cross-link interference (CLI) or DL-to-UL interference.
  • CLI TRP-to-TRP cross-link interference
  • the UL of UE1 can cause significant degradation in DL reception for UE2, called UE-to-UE CLI or UL-to-DL interference.
  • techniques were investigated in the 3GPP study item (TR 38.802 v14.2.0) for both TRP-to-TRP and UE-to-UE CLI.
  • ⁇ Specify cross-link interference measurements and reporting at a UE e.g., CLI-Reference Signal Strength Indicator, RSSI, and/or CLI-Reference Signal/Symbol Received Power (RSRP)
  • ⁇ Specify network coordination mechanism(s) including at least exchange of intended DL/UL configuration
  • the number of SRS to be monitored by the UE should not exceed 8 within a slot
  • Network may configure more than 8 SRSs over different slots
  • the UE is not required to perform time tracking or time adjustment other than a constant offset relative to its own DL timing in order to perform SRS-RSRP measurement
  • - UE is not required to measure SRS using different SCS compared to the downlink active BWP SCS of the same carrier
  • the network may configure a parameter called s-Measure in the measurement configuration so that the UE is only required to perform measurements associated to neighbour cells if the PCell RSRP goes below a certain configured level.
  • the measurements may be, for example, all Radio Resource Management, RRM/L3 configured measurements except Primary Cell’s (PCell’s) RSRP and Reference Signal/Symbol Received Quality (RSRQ).
  • PCell Primary Cell
  • RSRQ Reference Signal/Symbol Received Quality
  • EN-DC i.e. dual connectivity provided by at least one LTE base station and at least one NR base station
  • the UE shall:
  • the s-Measure defines when the UE is required to perform measurements. The UE is however allowed to perform measurements also when the PCell RSRP exceeds s-Measure, e.g., to measure cells broadcasting a CSG identity following use of the autonomous search function as defined in TS 36.304 [4]
  • a similar s-Measure threshold also exists in NR with the main difference that in NR the network may configure the UE to perform RRM/L3 measurements based on different reference signals that may be beamformed in different ways: Synchronization Signal (SS)/Physical Broadcast Channel (PBCH) Block(s) (SSBs), which may be transmitted with wide beams, or Channel State Information (CSI)-Reference Signal (RS), which may be transmitted in narrow beams.
  • SS Synchronization Signal
  • PBCH Physical Broadcast Channel
  • SSBs Physical Broadcast Channel
  • CSI Channel State Information
  • the UE behavior based on configured s-Measure when that is configured by NG- RAN is specified as follows (TS 38.331, v 15.6.0):
  • s-MeasureConfig is set to ssb-RSRP, set parameter ssb-RSRP of s-MeasureConfig within VarMeasConfig to the lowest value of the RSRP ranges indicated by the received value of s-MeasureConfig;
  • s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or
  • s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP ' .
  • reportQuantityRS-lndexes and maxNrofRS-lndexesToReport for the associated reportConfig are configured:
  • Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells.
  • Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS.
  • a first problem is that if s-Measure is configured, non-serving cell measurements are only performed if the measured PCell RSRP is below the configured s-Measure RSRP threshold. Hence, it is not clear whether if the network configures CLI measurements and configures a s-Measure threshold, the UE would not be required to perform CLI measurements while the PCell is with good RSRP. Hence, there could be cases where the network expects the UE to measure and possibly report CLI measurements independently of the RSRP of the PCell i.e. independent of the PCell coverage since CLI is more related to interference.
  • a second problem may still exist in some scenarios.
  • Current design of s-Measure is based on RSRP PCell in existing RRC specifications, which is a coverage related metric translating the downlink coverage of the PCell that does not take interference into account and/or uplink quality/coverage.
  • the potential degradation from CLI for a given UE, such as UE-2 in our example in the background is more caused by another interfering UE, such as UE-1 causing interference to that UE-2’s DL as shown in our example in the background.
  • CLI is more driven by DL interference rather than coverage in some scenarios.
  • this second problem relates to the fact that an RSRP threshold based on PCell RSRP may not be the best s-Measure metric to control the starting of CLI measurements.
  • a third problem relates to the facts that CLI may occur in any serving frequency for which the UE may be scheduled, not only the PCell.
  • SCells e.g. associated to a master cell group or secondary cell group, for that UE may suffer DL interference while DL in the PCell may not be specially affected.
  • s-Measure is configured and only based on PCell RSRP, there is a risk that UE may not perform CLI measurements on another serving frequency and not report it, despite its DL problems caused by interference from a UE in a neighbour TRP transmitting in the same resources.
  • s-Measure associated to a PScell
  • the UE is in any of the MR-DC scheme, e.g. EN-DC, NR-NR DC, and NR master and LTE secondary, etc.
  • s-Measure would be defined based on the PSCell RSRP, while that secondary cell group may also have SCells that suffer DL interference due to CLI.
  • s-Measure is only based on PCell RSRP, there is a risk that UE may not perform CLI measurements on another serving frequency, such as MCG Secondary Cell, SCell, frequencies, PSCell frequencies, or SCG SCell frequencies, and not report it.
  • s-Measure is linked to PCell measurements per RS type SSB or CSI-RS, in the s-Measure configuration.
  • CLI measurements may be performed on specific reference signals only for that purpose, at least in the case of measurements performed on RSs transmitted by an interfering UE.
  • s-measure per RS type e.g. SSB or CSI-RS
  • the disclosure provides a method in which, upon having both an s-Measure configuration and a Cross Link Interference (CLI) measurement configuration, a User Equipment (UE) performs CLI measurements regardless of its SpCell RSRP conditions, as if CLI measurements were defined as serving cell measurements that shall be performed upon reception of a measurement configuration. In that case, no conditions may be configured for performance of CLI measurements.
  • CLI Cross Link Interference
  • the disclosure provides a method at a wireless device/terminal (also called a User Equipment - UE) for performing CLI measurements in a power-efficient manner.
  • the method comprises:
  • a condition controlling when the UE shall start performing CLI measurements e.g. a parameter that is a threshold for a given measurement guantity
  • the configured condition may comprise at least one of the following conditions or any combination thereof: o PCell RSRP below a configured s-measure like threshold; o PCell RSRQ below a configured s-measure like threshold; o PCell SI NR below a configured s-measure like threshold;
  • PCell is used as an example.
  • PSCell the term PCell could be replaced by PSCell.
  • SpCell which can either be a PCell or PSCell according to the NR RRC specifications.
  • Cell-X Measurement quantity below a configured threshold (which may be different and specifically defined for CLI measurements).
  • Cell X refers to any cell, such as a serving cell (SPcell orSCell) or a non-serving cell such as a neighbouring cell.
  • Measurement quantity is any suitable measurement quantity or parameter, such as RSRP, RSRQ, SINR, RSSI, etc.
  • Cell-X can be an SCell associated to the measurement object (MO) where CLI measurements are configured.
  • the logic here is that CLI may occur in a given serving carrier that is not the SpCell carrier. In that case, it can make sense to only start these CLI measurements if the SCell quality (e.g. RSRP, RSRQ, SINR, etc.) falls below a threshold.
  • SCell quality e.g. RSRP, RSRQ, SINR, etc.
  • CLI measurements may comprise at least SRS-RSRP and CLI-RSSI measurements i.e. CLI measurements also comprise SRS-RSRP.
  • an overall advantage of the disclosed solutions is to avoid ambiguities if the UE is configured to perform CLI measurements and is also configured with an s-Measure threshold.
  • the current usage of the s-Measure parameter defines the UE shall only performing non-serving cell measurements if the SpCell RSRP is below the configured s-Measure threshold.
  • the UE treats the CLI measurements as some type of serving cell measurements, e.g. with the reasoning that CLI measurement configuration can be associated to a serving cell measurement object and/or frequency where a serving cell is configured.
  • the advantage here is that the CLI measurements are unambiguously excluded from the PCell or PSCell conditions to be checked before starting to perform the CLI measurements. In other words, regardless if s-Measure is configured or not, the UE starts to perform CLI measurements upon the reception of CLI measurement configuration, which potentially speeds up the availability of CLI measurements regardless of the quality (e.g. RSRP) of the PCell or PSCell or any other serving cell.
  • the quality e.g. RSRP
  • CLI measurements may be associated to an SCell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) and, in that case, the initiation of associated CLI measurement should not be controlled by the conditions in the PCell since it may be an SCell that is suffering from CLI.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the advantage of this alternative is that in some scenarios where PCell or PSCell RSRP is good, e.g. above s-Measure, but the UE is possibly suffering from CLI, the UE performs CLI measurements and may trigger a CLI measurement report to the network, so the CLI problem may be known by the network and possibly mitigated.
  • the UE only performs CLI measurements if the PCell RSRP is below a configured threshold, which may be the existing s-Measure threshold based on PCell RSRP.
  • a configured threshold which may be the existing s-Measure threshold based on PCell RSRP.
  • the solution addresses some scenarios where CLI occurs when the UE is close to cell border. It is of interest to perform CLI measurements when CLI is probably happening which probably happens in these scenarios in the cell border when PCell RSRP is below s-Measure.
  • this solution defines that the existing s-Measure threshold that may be configured by the network also determines the condition for the UE to perform CLI measurements.
  • the benefit here is that the UE also has some power/energy saving benefits when configured to perform CLI measurements by only starting the CLI measurements when the PCell or PSCell is below the s-Measure threshold i.e. when it is more likely that CLI is happening.
  • a configured threshold like s-Measure is to be applicable for each serving cell, not necessarily an SpCell.
  • CLI measurements associated to a given serving cell via measurement object which it is configured are only performed when the serving cell RSRP is below a configured threshold. In that case, it is the coverage of an SCell associated to a given frequency, i.e. the SCell RSRP, that determines if the UE shall start performing CLI measurements on that frequency. If the SCell RSRP is below the threshold, the UE shall perform CLI measurements on that frequency, e.g. associated to that same SCell measurement object.
  • the threshold may be the s-Measure, which gains a different meaning, or a new s-Measure like threshold (possibly configured in MeasConfig or within each measurement object).
  • a configured threshold e.g. an s-Measure based on RSRQ or SI NR
  • CLI typically occurs when the UE has some interference being detected in the DL of its PCell or, in the case of MR-DC, SpCell, or any other SCell associated to an SpCell.
  • s-Measure based on an interference related metric controls when the UE starts CLI measurements, and the UE gets the power saving benefits of an s-Measure like threshold tailored for CLI measurements i.e. if s-Measure-CLI is configured, to only perform CLI measurements on nonserving cells if the PCell interference value is above a certain threshold.
  • a configured threshold to be applicable for each serving cell, e.g. CLI measurements associated to a given serving cell are only performed when the serving cell interference measurement quality is below a configured threshold.
  • FIG. 1 is a schematic diagram illustrating interference due to different Time Divisional Duplex (TDD) configurations in networks A and B;
  • TDD Time Divisional Duplex
  • Figure 2 is an illustration of a situation in which cross-link interference may occur
  • Figure 3 is a schematic diagram illustrating a wireless network according to some embodiments.
  • Figure 4 is a schematic diagram illustrating a user equipment according to some embodiments.
  • Figure 5 is a schematic block diagram illustrating a virtualization environment according to some embodiments.
  • Figure 6 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments
  • Figure 7 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments
  • FIG. 8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment
  • FIG. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment
  • FIG. 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment
  • Figure 12 depicts a method in accordance with particular embodiments of the disclosure.
  • Figure 13 depicts a method in accordance with particular embodiments of the disclosure.
  • Figure 14 illustrates a schematic block diagram of an apparatus in a wireless network
  • Figure 15 depicts a method in accordance with particular embodiments of the disclosure
  • Figure 16 illustrates a schematic block diagram of an apparatus in a wireless network.
  • the present disclosure provides methods at a wireless device/terminal, also called a User Equipment - UE, for performing Cross-Link Interference, CLI, measurements.
  • the wireless device or UE may, in some embodiments correspond to the wireless device 310, the UE 400 and/or the virtual apparatus 1400 described below with respect to Figures 3, 4 and 14.
  • the cells described below, such as a PCell, SCell, SpCell, neighbouring cell, etc., may be provided by a network node such as the network node 360 described below with respect to Figure 3 or the virtual apparatus 1600 described with respect to Figure 16. Further detail regarding these steps according to certain embodiments of the disclosure is set out below.
  • CLI measurement configuration in the context of the present disclosure, it may be at least one of the following: time/frequency resources where reference signals to be measured are transmitted, reference signals configuration possibly transmitted by another UE and/or network node e.g. or detecting uplink and/or downlink CLI, measurement object associated to the frequency where the resources to be measured for CLI detection are transmitted, reporting configuration, measurement identifier to be included in the measurement report, information of what other measurements are to be included in CLI measurement reports.
  • CLI measurements can be defined as if they were a type of non-serving cell measurements;
  • the measurement object where CLI measurements are configured is any measurement object that are not associated to a serving cell e.g. in the frequency of the PCell, PSCell, SpCell and/or any configured SCell.
  • the measurement object where CLI measurements are configured is one of the measurement objects associated to a serving cell, e.g. in the frequency of the PCell, PSCell, SpCell and/or any configured SCell.
  • these CLI measurements are anyway considered as nonserving cell CLI measurements because the reference signals that are configured to be measured and reported for CLI such as Sounding Reference Signals are being transmitted by a possibly interfering UE that is connected to a non-serving cell (hence the name non-serving cell CLI measurements), and not by a signal transmitted by a serving cell.
  • CLI measurements can be defined as if they were a type of serving cell measurements
  • measurement object where CLI measurements are configured is measurement object that are associated to a serving cell e.g. in the frequency of the PCell, PSCell, SpCell and/or any configured SCell.
  • CLI measurements are not defined as serving cell measurements or nonserving cell measurements
  • the CLI measurement configuration may be received when the UE is operating in NR Standalone or in any form of Multi-connectivity with NR or any other RAT where CLI may occur, for example:
  • NR PCell may be suffering from CLI in Standalone case, but also when operating in DC forms where NR is the PCell.
  • the advantage in supporting these scenarios comes from the fact that the NR PSCell may also suffer from CLI and may want to independently configure CLI measurements to be performed.
  • the method also comprises that CLI measurement configuration can be provided via SRB1 or SRB3, for example in case of an NR PSCell configuring CLI measurements.
  • the method also comprises that CLI measurement configuration can be provided by another RAT.
  • CLI measurement configuration can be provided by another RAT.
  • it may be the case that while the UE is in EN-DC, it is LTE PCell that configures the UE to perform CLI measurements.
  • the UE Upon having both an s-Measure configuration and a CLI measurement configuration, the UE performs CLI measurements regardless of its SpCell RSRP conditions, as if CLI measurements were defined as serving cell measurements that shall be performed upon reception of a measurement configuration. o
  • the UE upon receiving that parameter associated with a condition, such as an s-Measure threshold as defined in measConfig for controlling non-serving cell measurements, the UE ignores the parameter and anyways starts to perform CLI measurements regardless of whether the condition is fulfilled or not for the PCell.
  • the UE treats CLI measurements associated to a given measurement object as non-serving cell measurements (as defined in TS 38.331 v 15.6.0, sub-clause 5.5).
  • ⁇ is an s-Measure parameter that contains an RSRP value. If the UE is configured with that s-Measure and CLI measurements, the UE measures the RSRP of its PCell and the configured CLI measurements cells regardless of the PCell RSRP quality compared to the s-Measure threshold. o In a variant of that solution, upon receiving that parameter associated with a condition, such as an s-Measure threshold as defined in measConfig for controlling non-serving cell measurements, the UE ignores the parameter if the CLI measurements are associated to measurement objects that are not the same as the measurement object for the PCell. In other words, if the condition is fulfilled i.e. PCell quality below s-Measure, the UE performs CLI measurements associated to measurement object for the PCell.
  • a condition such as an s-Measure threshold as defined in measConfig for controlling non-serving cell measurements
  • RS reference signal
  • a second case is where a possibly interfering UE is transmitting a reference signal, RS, e.g. Sounding Reference Signal, which the UE is being configured to measure and possibly report, as a way to detect interference being caused by a possibly interfering UE connected to a non-serving cell and transmitting in the UL to this non-serving cell and interfering in its DL transmission(s).
  • RS Sounding Reference Signal
  • CLI measurements may be performed regardless of the quality of the serving cell or any other cell on which the UE is performing measurements.
  • An example according to this aspect is given below, where two cases are considered in which CLI measurements are associated to a serving cell measurements object and a non-serving cell measurements object. Suggested changes to the specification, TS 38.331, are underlined.
  • An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results in RRC_CONNECTED the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting.
  • the network can configure RSRP, RSRQ or SINR as trigger quantity.
  • Reporting quantities can be any combination of quantities (i.e. only RSRP: only RSRQ: only SINR: RSRP and RSRQ: RSRP and SINR: RSRQ and SINR: RSRP, RSRQ and SINRL irrespective of the trigger quantity.
  • the network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)), derived as described in 5.5.3.3a. If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering as specified in 5.5.3.2. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent.
  • the UE shall:
  • the reportConfig associated with at least one measld included in the measMList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS- IndexesToReport and contains an rsType set to ssb:
  • the reportConfig associated with at least one measld included in the measMList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS- IndexesToReport and contains an rsType set to csi-rs:
  • s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
  • the IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.
  • the method comprises steps of: receiving a CLI measurement configuration; receiving a configuration of a condition controlling when the UE shall start to perform CLI measurements ; and starting CLI measurement upon the fulfillment of a configured condition.
  • Receiving the configuration of the condition may comprise receiving a parameter that is a threshold for a given measurement quantity.
  • step 2 recited above may be replaced by the following steps 2 and 3: 2/ Receiving the configuration of a condition controlling when the UE shall start to perform CLI measurements (e.g.
  • a parameter that is a threshold for a given measurement quantity o Regarding how the UE receives the configuration of a condition controlling when the UE shall start to perform CLI measurements, that may be received when the UE is operating in NR Standalone or in any form of Multi-connectivity with NR (or any other RAT where CLI may occur), for example:
  • the advantage in supporting these scenarios comes from the fact that the NR PCell may be suffering from CLI in Standalone case, but also when operating in DC forms where NR is the PCell. And, by supporting the configuration of the condition in these scenarios, the UE reduce its power consumption in these scenarios.
  • ⁇ ii) receiving the configuration of a condition via an NR PSCell for a UE operating in NR-NR Dual Connectivity, EN-DC or any other form of DC where NR is a PSCell;
  • the method also comprises that the configuration of a condition can be provided via SRB1 or SRB3, for example in case of an NR PSCell configuring CLI measurements and a condition for starting the CLI measurements.
  • the method also comprises that the configuration of a condition configuration can be provided by another RAT.
  • another RAT it may be the case that while the UE is in EN-DC, it is LTE PCell that configures the UE to perform CLI measurements and with a condition for the UE to start performing these CLI measurements.
  • o There may be different solutions depending on the exact configured condition, as described in step 2/ and/or how the CLI measurement configuration and the condition are configured e.g. if they are provided by a PCell, PSCell, via signaling radio bearers, SRB, such as SRB1 or SRB3.
  • o Configured conditions may be a threshold per measurement quantity based on the quality of a reference measurement (e.g. a reference cell). For example, an RSRP threshold for the PCell as the reference cell.
  • UE performs CLI measurements if the PCell/PSCell RSRP, i.e. SpCell RSRP, is below the configured s-Measure threshold, e.g.
  • This solution addresses some scenarios where CLI occurs when the UE is close to cell border. It is of interest to perform CLI measurements when CLI is probably happening which probably happens in these scenarios in the cell border when PCell RSRP is below s-Measure. Hence, this solution defines that the existing s-Measure threshold that may be configured by the network also determines the condition for the UE to perform CLI measurements.
  • UE performs CLI measurements if the SCell RSRP associated to that CLI measurement, e.g. configured in the same measurement object associated to that SCell, is below the configured s-Measure threshold.
  • SCell RSRP associated to that CLI measurement e.g. configured in the same measurement object associated to that SCell.
  • condition configuration is an s-Measure-CLI parameter or equivalent that contains a threshold value for a given measurement quantity and for a given cell as a reference.
  • the measurement quantity may be an SINR, RSRQ, RSRP, RSSI, or any other measurement reflecting some level of interference and/or UL degradation and/or DL degradation.
  • the UE measures the RSRP of its PCell and only starts to perform the configured CLI measurements when the configured condition in s-Measure-CLI is fulfilled i.e. when the RSRP PCell is lower than the configured s-Measure-CLI threshold.
  • Other examples may be based on RSRQ or SINR which are more metrics reflecting better the interference situation compared to RSRP.
  • the UE only starts to perform the configured CLI measurements if the configured condition in s-Measure-CLI is fulfilled e.g. if the RSRP for the associated serving cell is lower than the configured s- Measure-CLI threshold.
  • Other examples may be based on RSRQ or SINR measurements of the PCell to be compared with the threshold.
  • the method also comprises the usage of combinations e.g. RSRP and RSRQ conditions being fulfilled.
  • the method comprises the s-Measure-CLI parameter being a new parameter in measConfig or the existing s-Measure threshold that is currently based on PCell RSRP.
  • RSRP PCell measurements are performed and if s-Measure is configured, CLI measurements are only performed if the PCell RSRP is lower than the configured s-Measure.
  • the threshold(s)/condition for starting the CLI measurements at the UE may be configured per frequency, as in the examples above i.e. per measurement object where the CLI measurements are being configured. In that case, the CLI measurements for that measurement object are only started when the quality of the serving cell associated to the same measurement object is below the threshold or another configured condition indicating that CLI may be happening is fulfilled.
  • the threshold(s)/condition(s) for starting the CLI measurements at the UE may be configured per reporting configuration, i.e. per reportConfig where the CLI measurements are being configured.
  • a quality/coverage threshold e.g. based on RSRP, RSRQ, SINR, RSSI, etc.
  • a parameter is an s-Measure-CLI parameter that contains a value for a given measurement quantity reflecting the UL quality e.g. UL throughput, delay, etc.
  • the UE only starts to perform the configured CLI measurements when the UL degradation condition is fulfilled.
  • the UE receives a lower layer signaling, e.g. Medium Access Control, MAC, CE, activating a CLI measurement configuration that been previously provided, e.g. in RRC signaling. That may be provided from the network when the source node identifies some UL interference possibly caused by CLI. Then, upon receiving this lower layer signaling the UE starts to perform configured CLI measurements indicated by that signaling e.g. via a measurement configuration identifiers in the lower layer signaling like a measurement identifier.
  • a lower layer signaling e.g. Medium Access Control, MAC, CE
  • the method comprises that cell measurements used as reference to be compared with the threshold may be based on different reference signals, RS, types, such as SSBs or CSI-RS.
  • SSB cell measurements are used as reference for the condition i.e. when we refer above to PCell RSRP/RSRQ/SINR we mean RSRP/RSRQ/SINR measurements based on SSB, as a default solution. In that we may not need to configure a RS type for this threshold configuration for CLI.
  • CSI-RS cell measurements are used as reference for the condition i.e. when we refer above to PCell RSRP/RSRQ/SINR we mean RSRP/RSRQ/SINR measurements based on CSI-RS, as a default solution. In that we may not need to configure a RS type for this threshold configuration for CLI.
  • either SSB or CSI-RS cell measurements may be used as reference for the condition, that being configured by the network i.e. when we refer above to PCell RSRP/RSRQ/SINR we mean RSRP/RSRQ/SINR measurements based on CSI-RS if RS type in CLI configuration is based on CSI-RS or when we refer above to PCell RSRP/RSRQ/SINR we mean RSRP/RSRQ/SINR measurements based on SSB if RS type in CLI configuration is based on SSB. For that case, UE is configured with a threshold per RS type.
  • the method may also comprise the possibility of the UE being configured by the network with multiple measurement objects, each of them containing its own CLI measurement configuration and its own s-Measure-CLI threshold.
  • the UE measures a cell associated to that measurement object, such as a serving cell associated to that measurement object, and if that cell’s RSRP is below the s-Measure-CLI-threshold configured in that measurement object, the UE performs CLI measurements configured in the same measurement object. If the s- Measure-CLI condition is fulfilled for multiple cells, e.g. each associated for each measurement object, the UE performs multiple associated CLI measurements.
  • a non-serving cell is transmitting a reference signal (RS) which the UE is being configured to measure and possibly report, as a way to detect interference being caused by a non-serving cell in its UL transmission(s);
  • RS reference signal
  • a second case is where a possibly interfering UE is transmitting a reference signal (RS), e.g. Sounding Reference Signal, which the UE is being configured to measure and possibly report, as a way to detect interference being caused by a possibly interfering UE connected to a non-serving cell and transmitting in the UL to this non-serving cell and interfering in its DL transmission(s).
  • RS reference signal
  • An RRC CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results in RRC CONNECTED the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting.
  • the network can configure RSRP, RSRQ or SINR as trigger quantity.
  • Reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR), irrespective of the trigger quantity.
  • the UE shall:
  • s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured: 7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
  • the IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.
  • RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results in RRC_CONNECTED the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting.
  • the network can configure RSRP, RSRQ or SINR as trigger quantity.
  • Reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR), irrespective of the trigger quantity.
  • the UE shall:
  • s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
  • reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
  • the IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.
  • a wireless network such as the example wireless network illustrated in Figure 3.
  • the wireless network of Figure 3 only depicts network 306, network nodes 360 and 360b, and wireless devices 310, 310b, and 310c.
  • 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.
  • network node 360 and wireless device (WD) 310 are depicted with additional detail.
  • 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 5 th Generation (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
  • 5G 2G, 3G, 4G, or 5 th Generation
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave
  • Network 306 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.
  • Network node 360 and WD 310 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self Optimised Network, SON, nodes, positioning nodes (e.g., Evolved-Serving Mobile Location Centres, 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
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • 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 360 includes processing circuitry 370, device readable medium 380, interface 390, auxiliary equipment 384, power source 386, power circuitry 387, and antenna 362.
  • network node 360 illustrated in the example wireless network of Figure 3 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 360 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 380 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 360 may be composed of multiple physically separate components (e.g., a NodeB component and a Radio Network Controller, RNC, component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • RNC Radio Network Controller
  • BTS and BSC 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 360 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate device readable medium 380 for the different RATs) and some components may be reused (e.g., the same antenna 362 may be shared by the RATs).
  • Network node 360 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 360, such as, for example, GSM, Wide CDMA (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 360.
  • Processing circuitry 370 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 370 may include processing information obtained by processing circuitry 370 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 370 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 370 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 360 components, such as device readable medium 380, network node 360 functionality.
  • processing circuitry 370 may execute instructions stored in device readable medium 380 or in memory within processing circuitry 370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 370 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 370 may include one or more of radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374.
  • radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374 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 372 and baseband processing circuitry 374 may be on the same chip or set of chips, boards, or units
  • processing circuitry 370 executing instructions stored on device readable medium 380 or memory within processing circuitry 370.
  • some or all of the functionality may be provided by processing circuitry 370 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 370 alone or to other components of network node 360, but are enjoyed by network node 360 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 380 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 370.
  • 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
  • Device readable medium 380 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 370 and, utilized by network node 360.
  • Device readable medium 380 may be used to store any calculations made by processing circuitry 370 and/or any data received via interface 390.
  • processing circuitry 370 and device readable medium 380 may be considered to be integrated.
  • Interface 390 is used in the wired or wireless communication of signalling and/or data between network node 360, network 306, and/or WDs 310. As illustrated, interface 390 comprises port(s)/terminal(s) 394 to send and receive data, for example to and from network 306 over a wired connection. Interface 390 also includes radio front end circuitry 392 that may be coupled to, or in certain embodiments a part of, antenna 362. Radio front end circuitry 392 comprises filters 398 and amplifiers 396. Radio front end circuitry 392 may be connected to antenna 362 and processing circuitry 370. Radio front end circuitry may be configured to condition signals communicated between antenna 362 and processing circuitry 370.
  • Radio front end circuitry 392 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 392 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 398 and/or amplifiers 396. The radio signal may then be transmitted via antenna 362. Similarly, when receiving data, antenna 362 may collect radio signals which are then converted into digital data by radio front end circuitry 392. The digital data may be passed to processing circuitry 370. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 360 may not include separate radio front end circuitry 392, instead, processing circuitry 370 may comprise radio front end circuitry and may be connected to antenna 362 without separate radio front end circuitry 392. Similarly, in some embodiments, all or some of RF transceiver circuitry 372 may be considered a part of interface 390. In still other embodiments, interface 390 may include one or more ports or terminals 394, radio front end circuitry 392, and RF transceiver circuitry 372, as part of a radio unit (not shown), and interface 390 may communicate with baseband processing circuitry 374, which is part of a digital unit (not shown). Antenna 362 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 362 may be coupled to radio front end circuitry 390 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 362 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 362 may be separate from network node 360 and may be connectable to network node 360 through an interface or port.
  • Antenna 362, interface 390, and/or processing circuitry 370 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 362, interface 390, and/or processing circuitry 370 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 387 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 360 with power for performing the functionality described herein. Power circuitry 387 may receive power from power source 386. Power source 386 and/or power circuitry 387 may be configured to provide power to the various components of network node 360 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 386 may either be included in, or external to, power circuitry 387 and/or network node 360. For example, network node 360 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 387.
  • an external power source e.g., an electricity outlet
  • power source 386 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 387.
  • 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 360 may include additional components beyond those shown in Figure 3 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 360 may include user interface equipment to allow input of information into network node 360 and to allow output of information from network node 360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 360.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term 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
  • 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 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 310 includes antenna 311, interface 314, processing circuitry 320, device readable medium 330, user interface equipment 332, auxiliary equipment 334, power source 336 and power circuitry 337.
  • WD 310 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 310, 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 310.
  • Antenna 311 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 314. In certain alternative embodiments, antenna 311 may be separate from WD 310 and be connectable to WD 310 through an interface or port. Antenna 311, interface 314, and/or processing circuitry 320 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. In some embodiments, radio front end circuitry and/or antenna 311 may be considered an interface. As illustrated, interface 314 comprises radio front end circuitry 312 and antenna 311. Radio front end circuitry 312 comprise one or more filters 318 and amplifiers 316.
  • Radio front end circuitry 314 is connected to antenna 311 and processing circuitry 320, and is configured to condition signals communicated between antenna 311 and processing circuitry 320.
  • Radio front end circuitry 312 may be coupled to or a part of antenna 311.
  • WD 310 may not include separate radio front end circuitry 312; rather, processing circuitry 320 may comprise radio front end circuitry and may be connected to antenna 311.
  • processing circuitry 320 may comprise radio front end circuitry and may be connected to antenna 311.
  • some or all of RF transceiver circuitry 322 may be considered a part of interface 314.
  • Radio front end circuitry 312 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry 312 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 318 and/or amplifiers 316. The radio signal may then be transmitted via antenna 311. Similarly, when receiving data, antenna 311 may collect radio signals which are then converted into digital data by radio front end circuitry 312. The digital data may be passed to processing circuitry 320. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 320 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 310 components, such as device readable medium 330, WD 310 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 320 may execute instructions stored in device readable medium 330 or in memory within processing circuitry 320 to provide the functionality disclosed herein.
  • processing circuitry 320 includes one or more of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 320 of WD 310 may comprise a SOC.
  • RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 324 and application processing circuitry 326 may be combined into one chip or set of chips, and RF transceiver circuitry 322 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 322 and baseband processing circuitry 324 may be on the same chip or set of chips, and application processing circuitry 326 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 322 may be a part of interface 314.
  • RF transceiver circuitry 322 may condition RF signals for processing circuitry 320.
  • processing circuitry 320 executing instructions stored on device readable medium 330, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 320 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 320 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 320 alone or to other components of WD 310, but are enjoyed by WD 310 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 320 may be configured to perform any determining, calculating, or similar operations such as certain obtaining operations described herein as being performed by a WD. These operations, as performed by processing circuitry 320, may include processing information obtained by processing circuitry 320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 310, 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 330 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 320.
  • Device readable medium 330 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 320.
  • processing circuitry 320 and device readable medium 330 may be considered to be integrated.
  • User interface equipment 332 may provide components that allow for a human user to interact with WD 310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 332 may be operable to produce output to the user and to allow the user to provide input to WD 310. The type of interaction may vary depending on the type of user interface equipment 332 installed in WD 310. For example, if WD 310 is a smart phone, the interaction may be via a touch screen; if WD 310 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).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 332 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 332 is configured to allow input of information into WD 310, and is connected to processing circuitry 320 to allow processing circuitry 320 to process the input information. User interface equipment 332 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 332 is also configured to allow output of information from WD 310, and to allow processing circuitry 320 to output information from WD 310. User interface equipment 332 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 332, WD 310 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 334 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 334 may vary depending on the embodiment and/or scenario.
  • Power source 336 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 310 may further comprise power circuitry 337 for delivering power from power source 336 to the various parts of WD 310 which need power from power source 336 to carry out any functionality described or indicated herein.
  • Power circuitry 337 may in certain embodiments comprise power management circuitry.
  • Power circuitry 337 may additionally or alternatively be operable to receive power from an external power source; in which case WD 310 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 337 may also in certain embodiments be operable to deliver power from an external power source to power source 336. This may be, for example, for the charging of power source 336. Power circuitry 337 may perform any formatting, converting, or other modification to the power from power source 336 to make the power suitable for the respective components of WD 310 to which power is supplied.
  • Figure 4 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user such as a smart sprinkler controller.
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 400 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 400 as illustrated in Figure 4, is one example of a wireless device, WD, configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 4 is a UE, the components discussed herein are equally applicable to a WD, and vice- versa.
  • UE 400 includes processing circuitry 401 that is operatively coupled to input/output interface 405, radio frequency (RF) interface 409, network connection interface 411, memory 415 including random access memory (RAM) 417, read-only memory (ROM) 419, and storage medium 421 or the like, communication subsystem 431, power source 433, and/or any other component, or any combination thereof.
  • Storage medium 421 includes operating system 423, application program 425, and data 427. In other embodiments, storage medium 421 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 4, or only a subset of the components. The level of integration between the components may vary from one UE to another UE.
  • processing circuitry 401 may be configured to process computer instructions and data.
  • Processing circuitry 401 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 405 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 400 may be configured to use an output device via input/output interface 405.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 400.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 400 may be configured to use an input device via input/output interface 405 to allow a user to capture information into UE 400.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 411 may be configured to provide a communication interface to network 443a.
  • Network 443a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 443a may comprise a Wi-Fi network.
  • Network connection interface 411 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 411 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 417 may be configured to interface via bus 402 to processing circuitry 401 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 419 may be configured to provide computer instructions or data to processing circuitry 401.
  • ROM 419 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 421 may be configured to include operating system 423, application program 425 such as a web browser application, a widget or gadget engine or another application, and data file 427.
  • Storage medium 421 may store, for use by UE 400, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 421 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external harddisk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • smartcard memory such as a subscriber identity module or a removable
  • Storage medium 421 may allow UE 400 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 421, which may comprise a device readable medium.
  • processing circuitry 401 may be configured to communicate with network 443b using communication subsystem 431.
  • Network 443a and network 443b may be the same network or networks or different network or networks.
  • Communication subsystem 431 may be configured to include one or more transceivers used to communicate with network 443b.
  • communication subsystem 431 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • CDMA Code Division Multiplexing Access
  • Each transceiver may include transmitter 433 and/or receiver 435 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 433 and receiver 435 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 431 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 443b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 443b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 413 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 400.
  • the features, benefits and/or functions described herein may be implemented in one of the components of UE 400 or partitioned across multiple components of UE 400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware.
  • communication subsystem 431 may be configured to include any of the components described herein.
  • processing circuitry 401 may be configured to communicate with any of such components over bus 402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 401 perform the corresponding functions described herein.
  • any of such components may be partitioned between processing circuitry 401 and communication subsystem 431.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 5 is a schematic block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 500 hosted by one or more of hardware nodes 530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 520 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 520 are run in virtualization environment 500 which provides hardware 530 comprising processing circuitry 560 and memory 590.
  • Memory 590 contains instructions 595 executable by processing circuitry 560 whereby application 520 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 500 comprises general-purpose or special-purpose network hardware devices 530 comprising a set of one or more processors or processing circuitry 560, which may be commercial off- the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 560 which may be commercial off- the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 590-1 which may be non-persistent memory for temporarily storing instructions 595 or software executed by processing circuitry 560.
  • Each hardware device may comprise one or more network interface controllers (NICs) 570, also known as network interface cards, which include physical network interface 580.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 590-2 having stored therein software 595 and/or instructions executable by processing circuitry 560.
  • Software 595 may include any type of software including software for instantiating one or more virtualization layers 550 (also referred to as hypervisors), software to execute virtual machines 540 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 540 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 550 or hypervisor. Different embodiments of the instance of virtual appliance 520 may be implemented on one or more of virtual machines 540, and the implementations may be made in different ways.
  • processing circuitry 560 executes software 595 to instantiate the hypervisor or virtualization layer 550, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer 550 may present a virtual operating platform that appears like networking hardware to virtual machine 540.
  • hardware 530 may be a standalone network node with generic or specific components. Hardware 530 may comprise antenna 5225 and may implement some functions via virtualization. Alternatively, hardware 530 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 5100, which, among others, oversees lifecycle management of applications 520.
  • CPE customer premise equipment
  • MANO management and orchestration
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 540 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 540, and that part of hardware 530 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 540, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 5200 that each include one or more transmitters 5220 and one or more receivers 5210 may be coupled to one or more antennas 5225.
  • Radio units 5200 may communicate directly with hardware nodes 530 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signalling can be effected with the use of control system 5230 which may alternatively be used for communication between the hardware nodes 530 and radio units 5200.
  • Figure 6 shows a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes a telecommunication network 610, such as a 3GPP-type cellular network, which comprises access network 611, such as a radio access network, and core network 614.
  • Access network 611 comprises a plurality of base stations 612a, 612b, 612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 613a, 613b, 613c.
  • Each base station 612a, 612b, 612c is connectable to core network 614 over a wired or wireless connection 615.
  • a first UE 691 located in coverage area 613c is configured to wirelessly connect to, or be paged by, the corresponding base station 612c.
  • a second UE 692 in coverage area 613a is wirelessly connectable to the corresponding base station 612a. While a plurality of UEs 691, 692 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 612.
  • Telecommunication network 610 is itself connected to host computer 630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 630 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 621 and 622 between telecommunication network 610 and host computer 630 may extend directly from core network 614 to host computer 630 or may go via an optional intermediate network 620.
  • Intermediate network 620 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 620, if any, may be a backbone network or the Internet; in particular, intermediate network 620 may comprise two or more subnetworks (not shown).
  • the communication system of Figure 6 as a whole enables connectivity between the connected UEs 691 , 692 and host computer 630.
  • the connectivity may be described as an over-the-top (OTT) connection 650.
  • Host computer 630 and the connected UEs 691, 692 are configured to communicate data and/or signaling via OTT connection 650, using access network 611, core network 614, any intermediate network 620 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 650 may be transparent in the sense that the participating communication devices through which OTT connection 650 passes are unaware of routing of uplink and downlink communications.
  • base station 612 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 630 to be forwarded (e.g., handed over) to a connected UE 691. Similarly, base station 612 need not be aware of the future routing of an outgoing uplink communication originating from the UE 691 towards the host computer 630.
  • Figure 7 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 710 comprises hardware 715 including communication interface 716 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 700.
  • Host computer 710 further comprises processing circuitry 718, which may have storage and/or processing capabilities.
  • processing circuitry 718 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 710 further comprises software 711 , which is stored in or accessible by host computer 710 and executable by processing circuitry 718.
  • Software 711 includes host application 712.
  • Host application 712 may be operable to provide a service to a remote user, such as UE 730 connecting via OTT connection 750 terminating at UE 730 and host computer 710. In providing the service to the remote user, host application 712 may provide user data which is transmitted using OTT connection 750.
  • Communication system 700 further includes base station 720 provided in a telecommunication system and comprising hardware 725 enabling it to communicate with host computer 710 and with UE 730.
  • Hardware 725 may include communication interface 726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 700, as well as radio interface 727 for setting up and maintaining at least wireless connection 770 with UE 730 located in a coverage area (not shown in Figure 7) served by base station 720.
  • Communication interface 726 may be configured to facilitate connection 760 to host computer 710. Connection 760 may be direct or it may pass through a core network (not shown in Figure 7) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 725 of base station 720 further includes processing circuitry 728, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 720 further has software 721 stored internally or accessible via an external connection.
  • Communication system 700 further includes UE 730 already referred to. Its hardware 735 may include radio interface 737 configured to set up and maintain wireless connection 770 with a base station serving a coverage area in which UE 730 is currently located. Hardware 735 of UE 730 further includes processing circuitry 738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 730 further comprises software 731, which is stored in or accessible by UE 730 and executable by processing circuitry 738.
  • Software 731 includes client application 732. Client application 732 may be operable to provide a service to a human or non-human user via UE 730, with the support of host computer 710.
  • an executing host application 712 may communicate with the executing client application 732 via OTT connection 750 terminating at UE 730 and host computer 710.
  • client application 732 may receive request data from host application 712 and provide user data in response to the request data.
  • OTT connection 750 may transfer both the request data and the user data.
  • Client application 732 may interact with the user to generate the user data that it provides.
  • host computer 710, base station 720 and UE 730 illustrated in Figure 7 may be similar or identical to host computer 630, one of base stations 612a, 612b, 612c and one of UEs 691, 692 of Figure 6, respectively.
  • the inner workings of these entities may be as shown in Figure 7 and independently, the surrounding network topology may be that of Figure 6.
  • OTT connection 750 has been drawn abstractly to illustrate the communication between host computer 710 and UE 730 via base station 720, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 730 or from the service provider operating host computer 710, or both. While OTT connection 750 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 770 between UE 730 and base station 720 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 730 using OTT connection 750, in which wireless connection 770 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate (e.g., through reducing interference such as CLI) and thereby provide benefits such as reduced user waiting time and higher quality streaming.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 750 may be implemented in software 711 and hardware 715 of host computer 710 or in software 731 and hardware 735 of UE 730, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 711 , 731 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 720, and it may be unknown or imperceptible to base station 720. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 710’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 711 and 731 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 750 while it monitors propagation times, errors etc.
  • FIG. 8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 6 and 7. For simplicity of the present disclosure, only drawing references to Figure 8 will be included in this section.
  • the host computer provides user data.
  • substep 811 (which may be optional) of step 810, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 830 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 840 the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 6 and 7. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 930 (which may be optional), the UE receives the user data carried in the transmission.
  • FIG. 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 6 and 7. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section.
  • the UE receives input data provided by the host computer. Additionally or alternatively, in step 1020, the UE provides user data.
  • substep 1021 (which may be optional) of step 1020 the UE provides the user data by executing a client application.
  • substep 1011 (which may be optional) of step 1010, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1030 (which may be optional), transmission of the user data to the host computer. In step 1040 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 6 and 7. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1130 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIG. 12 depicts a method in accordance with particular embodiments.
  • the method may be performed by a wireless device or UE (such as the wireless device 310 or the UE 400 described above).
  • the wireless device may be operating using any radio-access technology (RAT), such as NR, LTE, etc.
  • RAT radio-access technology
  • the wireless device may be operating using any radio-access technology in which CLI may occur.
  • the wireless device may be communicating with one or multiple network nodes using one or more multiple RATs, e.g., NR Standalone, Multiconnectivity with NR.
  • the method begins at step 1202, in which the wireless device receives an indication of a measurement configuration for performing measurements, such as radio measurements, to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • Step 1202 may correspond substantially to step 1302 described below.
  • the indication of the measurement configuration may be received from a serving network node or cell such as, e.g., a PCell, PSCell, etc.
  • the indication may comprise a measconfig information element, IE.
  • the measurement configuration comprises a CLI measurement configuration.
  • the measurement configuration may define measurements performed on transmissions by the one or more of the one or more other wireless devices and the one or more non-serving network nodes.
  • the transmissions may comprise reference signals, for example.
  • the transmissions by the other wireless device(s) may comprise sounding reference signals.
  • the transmissions by the network node(s) may comprise one or more of cell-specific reference signals, beam-specific reference signals, channel-state information reference signals, sounding reference signals, demodulation reference signals and phase-tracking reference signals.
  • the measurements defined in the measurement configuration may be of one or more radio parameters, such as one or more of reference signal received power and received signal strength indicator.
  • the measurement configuration defines the measurement of one or more of SRS-RSRP and CLI- RSSI.
  • the wireless device performs measurements according to the measurement configuration as if the measurement configuration related to serving cell measurements.
  • the measurements may be performed upon reception of the measurement configuration (rather than some other trigger).
  • the measurement configuration may comprise a measurement object associated to a serving cell.
  • the wireless device may perform measurements according to the measurement configuration regardless of the fulfillment or not of any condition for performing the measurements.
  • the wireless device may be configured with s-measure configuration, defining a threshold that a serving cell radio parameter (e.g., RSRP) must fall below before starting measurements on other network nodes or wireless devices.
  • RSRP serving cell radio parameter
  • the measurements may be reported to the network (e.g., a serving network node).
  • the transmission of such reports may be subject to triggers, such as the fulfilment of one or more criteria, expiry of a timer, etc.
  • FIG. 13 depicts a method in accordance with particular embodiments.
  • the method may be performed by a wireless device or UE (such as the wireless device 3310 or the UE 4400 described above).
  • the wireless device may be operating using any radio-access technology (RAT), such as NR, LTE, etc.
  • RAT radio-access technology
  • the wireless device may be operating using any radio-access technology in which CLI may occur.
  • the wireless device may be communicating with one or multiple network nodes using one or more multiple RATs, e.g., NR Standalone, Multiconnectivity with NR.
  • the method begins at step 1302, in which the wireless device receives an indication of a measurement configuration for performing measurements (e.g., radio measurements) to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • the indication of the measurement configuration may be received from a serving network node or cell (e.g., PCell, PSCell, etc).
  • the indication may comprise a measconfig information element (IE).
  • the measurement configuration comprises a CLI measurement configuration.
  • the measurement configuration may define measurements performed on transmissions (e.g., reference signals) by the one or more of the one or more other wireless devices and the one or more non-serving network nodes.
  • the transmissions by the other wireless device(s) may comprise sounding reference signals.
  • the transmissions by the network node(s) may comprise one or more of cell-specific reference signals, beam-specific reference signals, channel-state information reference signals, sounding reference signals, demodulation reference signals and phase-tracking reference signals.
  • the measurements defined in the measurement configuration may be of one or more radio parameters, such as one or more of reference signal received power and received signal strength indicator.
  • the measurement configuration defines the measurement of one or more of SRS-RSRP and CLI- RSSI.
  • the wireless device receives an indication of a condition, the fulfilment of which causes the wireless device (in step 1306) to perform measurements according to the measurement configuration received in step 1302.
  • the indication of the condition may be received from a serving network node (e.g., the same serving network node as sent the measurement configuration in step 1302) and may be received in the same or different transmission or message as the measurement configuration.
  • the condition may comprise multiple subconditions; in different embodiments, the fulfilment of one, some or all of these sub-conditions may be required for the condition as a whole to be considered fulfilled and measurements performed.
  • the condition is dedicated to the measurement configuration for performing measurements to evaluate interference.
  • the condition may be specific to CLI measurements.
  • the condition may additionally or alternatively re-use conditions specified for other purposes, such as the condition for performing mobility-related measurements on neighbouring cells (e.g., s-measure, as defined above).
  • the condition may define one or more thresholds for one or more respective radio parameters that are to be met for fulfillment of the condition.
  • one or more of the one or more radio parameters may relate to a serving cell such as, for example, a PCell, SCell, PSCell or SpCell etc. That is, the radio parameters may be measured based on transmissions by a serving cell.
  • one or more of the one or more radio parameters may relate to a non-serving cell. That is, the radio parameters may be measured based on transmissions by a non-serving cell.
  • the one or more radio parameters may comprise one or more of: reference signal received power, reference signal received quality, received signal-strength indicator, and signal-to-noise- and-interference ratio.
  • the one or more radio parameters are selected from a plurality of radio parameters selectable for the purposes of controlling triggering of measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes. That is, the radio parameters and associated thresholds may be selected particularly for the purposes of evaluating interference in different scenarios. In a first scenario, for example, where the wireless device is suspected by the network of experiencing UE-to-UE CLI, a first condition may be specified; in a second scenario, where the network node is experiencing interference when receiving UL transmissions from the wireless device, a second, different condition may be specified.
  • the condition may comprise reception of an instruction to commence performance of measurements according to the measurement configuration.
  • the instruction may be received from a serving network node.
  • Such an instruction may be triggered based on radio quality reports from the wireless device related to a serving cell, e.g., SpCell (PCell or PSCell) or an associated SCell.
  • a serving cell e.g., SpCell (PCell or PSCell) or an associated SCell.
  • the measurements may be reported to the network.
  • the measurements may be reported to a serving network node.
  • the transmission of such reports may be subject to further triggers, such as the fulfilment of additional or different criteria, expiry of a timer, etc.
  • Figure 14 shows virtualization apparatus in accordance with some embodiments.
  • Figure 14 illustrates a schematic block diagram of an apparatus 1400 in a wireless network (for example, the wireless network shown in Figure 33).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 3310 or network node 3360 shown in Figure 33).
  • Apparatus 1400 is operable to carry out one or more of the example methods described with reference to Figures 13 and 12 and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of Figures 13 and 12 are not necessarily carried out solely by apparatus 1400. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1400 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving unit 1402 and measuring unit 1404, and any other suitable units of apparatus 1400 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1400 includes receiving unit 1402 and measuring unit 1404.
  • receiving unit 1402 is configured to receive an indication of a measurement configuration for performing measurements (e.g., radio measurements) to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • Receiving unit 1402 is further configured to receive an indication of a condition.
  • Measuring unit 1404 is configured to perform measurements according to the measurement configuration upon fulfilment of the condition (or responsive to a determination that the condition has been fulfilled or met).
  • receiving unit 1402 is configured to receive an indication of a measurement configuration for performing measurements (e.g., radio measurements) to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • Measuring unit 1404 is configured to perform measurements according to the measurement configuration as if the measurement configuration related to serving cell measurements.
  • Figure 15 depicts a method in accordance with particular embodiments.
  • the method may be performed by a network node or base station (such as the network node 3360 described above).
  • the network node may operate using any radio-access technology (RAT), such as NR, LTE, etc. Particularly, the network node may operate using any radio-access technology in which CLI may occur.
  • RAT radio-access technology
  • the network node may communicate with a wireless device which is communicating with one or multiple network nodes using one or more multiple RATs, e.g., NR Standalone, Multi-connectivity with NR.
  • the network node may be a serving network node for such a wireless device.
  • the method begins at step 1502, in which the network node causes transmission, to a wireless device, of an indication of a measurement configuration for performing measurements, such as radio measurements, to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • the indication of the measurement configuration may be received from a serving network node or cell such as, for example, a PCell or PSCell, etc.
  • the indication may comprise a measconfig information element (IE).
  • the measurement configuration comprises a CLI measurement configuration.
  • the measurement configuration may define measurements performed on transmissions by the one or more of the one or more other wireless devices and the one or more non-serving network nodes.
  • the transmissions may comprise reference signals, for example.
  • the transmissions by the other wireless device(s) may comprise sounding reference signals.
  • the transmissions by the network node(s) may comprise one or more of cell-specific reference signals, beam-specific reference signals, channel-state information reference signals, sounding reference signals, demodulation reference signals and phase-tracking reference signals.
  • the measurements defined in the measurement configuration may be of one or more radio parameters, such as one or more of reference signal received power and received signal strength indicator.
  • the measurement configuration defines the measurement of one or more of SRS-RSRP and CLI- RSSI.
  • the network node causes transmission, to the wireless device, of an indication of a condition, the fulfilment of which causes the wireless device to perform measurements according to the measurement configuration transmitted in step 1502.
  • the indication of the condition may be transmitted in the same or different transmission or message as the measurement configuration.
  • the condition may comprise multiple sub-conditions; in different embodiments, the fulfilment of one, some or all of these subconditions may be required for the condition as a whole to be considered fulfilled and measurements performed.
  • the condition is dedicated to the measurement configuration for performing measurements to evaluate interference.
  • the condition may be specific to CLI measurements.
  • the condition may additionally or alternatively re-use conditions specified for other purposes, such as the condition for performing mobility-related measurements, such as s-measure as defined above, on neighbouring cells.
  • the condition may define one or more thresholds for one or more respective radio parameters that are to be met for fulfillment of the condition.
  • one or more of the one or more radio parameters may relate to a serving cell (e.g., PCell, SCell, PSCell, SpCell etc). That is, the radio parameters may be measured based on transmissions by a serving cell.
  • a serving cell e.g., PCell, SCell, PSCell, SpCell etc. That is, the radio parameters may be measured based on transmissions by a serving cell.
  • a non-serving cell e.g., the radio parameters may relate to a non-serving cell. That is, the radio parameters may be measured based on transmissions by a nonserving cell.
  • the one or more radio parameters may comprise one or more of: reference signal received power, reference signal received quality, received signal-strength indicator, and signal-to-noise-and-interference ratio.
  • the one or more radio parameters are selected from a plurality of radio parameters selectable for the purposes of controlling triggering of measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes. That is, the radio parameters and associated thresholds may be selected particularly for the purposes of evaluating interference in different scenarios. In a first scenario, for example, where the wireless device is suspected by the network of experiencing UE-to-UE CLI, a first condition may be specified; in a second scenario, where the network node is experiencing interference when receiving UL transmissions from the wireless device, a second, different condition may be specified.
  • the one or more radio parameters may be selected by, for example, the network node or another network node.
  • the condition may comprise reception of an instruction to commence performance of measurements according to the measurement configuration.
  • the instruction may be transmitted by the network node.
  • Such an instruction may be triggered based on radio quality reports received from the wireless device related to a serving cell, e.g., SpCell (PCell or PSCell) or an associated SCell.
  • a serving cell e.g., SpCell (PCell or PSCell) or an associated SCell.
  • the measurements may be reported by the wireless device to the network node or another network node.
  • the transmission of such reports may be subject to further triggers, such as the fulfilment of additional or different criteria, expiry of a timer, etc.
  • Figure 16 shows virtualization apparatus in accordance with some embodiments.
  • Figure 16 illustrates a schematic block diagram of an apparatus 1600 in a wireless network (for example, the wireless network shown in Figure 33).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 3310 or network node 3360 shown in Figure 33).
  • Apparatus 1600 is operable to carry out the example method described with reference to Figure 15 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 15 is not necessarily carried out solely by apparatus 1600. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1600 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause transmitting unit 1602, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure.
  • apparatus 1600 includes transmitting unit 1602.
  • Transmitting unit 1602 is configured to cause transmission, to a wireless device, of an indication of a measurement configuration for performing measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • Transmitting unit 1602 is further configured to cause transmission, to the wireless device, of an indication of a condition, upon the fulfillment of which, the wireless device is to perform measurements according to the measurement configuration.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • a method performed by a wireless device comprising:
  • condition defines one or more thresholds for one or more respective radio parameters that are to be met for fulfillment of the condition.
  • one or more of the one or more radio parameters relate to a serving cell (e.g., PCell, SCell, PSCell, SpCell etc).
  • a serving cell e.g., PCell, SCell, PSCell, SpCell etc.
  • radio parameters comprise one or more of: reference signal received power, reference signal received quality, received signal- strength indicator, and signal-to-noise-and-interference ratio.
  • radio parameters are selected from a plurality of radio parameters selectable for the purposes of controlling triggering of measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • a method performed by a wireless device comprising: receiving an indication of a measurement configuration for performing measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes; and performing measurements according to the measurement configuration as if the measurement configuration related to serving cell measurements.
  • the measurement configuration comprises a measurement object associated to a serving cell.
  • the indication of the measurement configuration for performing measurements to evaluate interference comprises a measconfig information element.
  • the measurement configuration for performing measurements to evaluate interference is a cross-link interference, CLI measurement configuration.
  • the indication of the measurement configuration for performing measurements to evaluate interference is received from a serving network node.
  • the measurements comprise measurements of one or more of: reference signal received power and received signal strength indicator.
  • a method performed by a base station comprising:
  • one or more of the one or more radio parameters relate to a serving cell (e.g., PCell, SCell, PSCell, SpCell etc).
  • a serving cell e.g., PCell, SCell, PSCell, SpCell etc.
  • the one or more radio parameters comprise one or more of: reference signal received power, reference signal received quality, received signal- strength indicator, and signal-to-noise-and-interference ratio.
  • the one or more radio parameters are selected from a plurality of radio parameters selectable for the purposes of controlling triggering of measurements to evaluate interference as a result of transmissions by one or more of: one or more other wireless devices; and one or more non-serving network nodes.
  • a wireless device comprising:
  • a base station configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the base station.
  • a user equipment comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • UE user equipment
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • UE user equipment
  • the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • UE user equipment
  • a communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the processing circuitry of the host computer is configured to execute a host application
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • UE user equipment
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

Landscapes

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

Abstract

L'invention concerne, selon un aspect, un procédé réalisé par un dispositif sans fil. Le procédé comporte la réception d'une configuration de mesure servant à réaliser des mesures pour évaluer le brouillage résultant de transmissions par un ou plusieurs dispositifs parmi un ou plusieurs autres dispositifs sans fil et une ou plusieurs cellules hors desserte. Le procédé comporte en outre, suite à la réception de l'indication de la configuration de mesure, la réalisation de mesures selon la configuration de mesure indépendamment du fait qu'une condition de réalisation de mesures de cellules hors desserte soit satisfaite ou non.
PCT/SE2020/050836 2019-09-06 2020-09-04 Commande de mesure de brouillage entre liaisons (cli) au niveau d'un équipement d'utilisateur WO2021045672A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962896812P 2019-09-06 2019-09-06
US62/896,812 2019-09-06

Publications (1)

Publication Number Publication Date
WO2021045672A1 true WO2021045672A1 (fr) 2021-03-11

Family

ID=72473932

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050836 WO2021045672A1 (fr) 2019-09-06 2020-09-04 Commande de mesure de brouillage entre liaisons (cli) au niveau d'un équipement d'utilisateur

Country Status (1)

Country Link
WO (1) WO2021045672A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023055972A1 (fr) * 2021-10-01 2023-04-06 Qualcomm Incorporated Mesure intercellulaire et rapport pour la gestion de faisceau
WO2023240639A1 (fr) * 2022-06-17 2023-12-21 Nec Corporation Procédé, dispositif et support lisible par ordinateur destinés aux communications

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018128469A1 (fr) * 2017-01-05 2018-07-12 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception de données dans un système de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018128469A1 (fr) * 2017-01-05 2018-07-12 Samsung Electronics Co., Ltd. Procédé et appareil d'émission et de réception de données dans un système de communication sans fil

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"Revised WID on Cross Link Interference (CLI) handling and Remote Interference Management (RIM) for NR", RP-182864, December 2018 (2018-12-01)
"Study on new radio access technology Physical layer aspects", TR 38.802
ERICSSON: "Discussion on CLI reporting method and criterion", vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 15 August 2019 (2019-08-15), XP051768667, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_107/Docs/R2-1910902.zip> [retrieved on 20190815] *
ERICSSON: "On S measure for CLI", vol. RAN WG2, no. Chongqing, P.R. China; 20191014 - 20191018, 3 October 2019 (2019-10-03), XP051804326, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_107bis/Docs/R2-1913537.zip R2-1913537 - On s measure for CLI.docx> [retrieved on 20191003] *
NOKIA ET AL: "UE CLI measurement configuration and reporting", vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 15 August 2019 (2019-08-15), XP051766833, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_107/Docs/R2-1909023.zip> [retrieved on 20190815] *
R2-1903009, April 2019 (2019-04-01)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023055972A1 (fr) * 2021-10-01 2023-04-06 Qualcomm Incorporated Mesure intercellulaire et rapport pour la gestion de faisceau
WO2023240639A1 (fr) * 2022-06-17 2023-12-21 Nec Corporation Procédé, dispositif et support lisible par ordinateur destinés aux communications

Similar Documents

Publication Publication Date Title
US10601556B2 (en) Measurement gap configuration
US20230422113A1 (en) Method for determination between intra- and inter-frequency operations
US20220104260A1 (en) Control Signalling for Transmission in Unlicensed Frequency Spectrum
US11405091B2 (en) Energy efficient camping with optimal beam finding before access
US20220191966A1 (en) Extension of a discontinuous reception active time
US11622285B2 (en) Performing measurements in multicarrier operation
US11489576B2 (en) Resolving ambiguities related to NR cell quality derivation
US20200053583A1 (en) Method, network node and ue for handling rrm measurements on a carrier comprising a plurality of synchronization sequence blocks
US20230189338A1 (en) COT/FFP Scheduling in Unlicensed Spectrum
US20230043789A1 (en) Wake Up Signal Monitoring Span Capability Signaling
WO2022031206A1 (fr) Configuration de mesure pour groupe de cellules secondaires désactivées
US20230284145A1 (en) Rlm for scg in power-saving mode
US20230079204A1 (en) Wireless device grouping mechanisms and network configuration for false paging reduction
US20220377705A1 (en) Master information block extension in a new radio cell
US20220166539A1 (en) Channel Quality Reporting in LTE-M and NB-IoT
US20220210681A1 (en) Radio Link Monitoring
US20240073982A1 (en) Measurement configuration for deactivated secondary cell group
WO2021045672A1 (fr) Commande de mesure de brouillage entre liaisons (cli) au niveau d&#39;un équipement d&#39;utilisateur
US20230396302A1 (en) Adapting channel monitoring patterns under power saving
WO2022152843A1 (fr) Robustesse améliorée de réception de radiomessagerie assistée par pei
US20240172029A1 (en) Transitioning Between Pre-Configured Measurement Gap Patterns and Normal Measurement Gap Patterns
US20220346021A1 (en) PSM and ANR Handling for Power Limited Devices
US20220167371A1 (en) Methods, apparatus and computer-readable mediums relating to uplink transmissions
US20230388077A1 (en) Methods of provision of csi-rs for mobility to idle user equipments
US20230308995A1 (en) User equipment positioning for new radio (nr)

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: 20771641

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: 20771641

Country of ref document: EP

Kind code of ref document: A1