Radio resource management measurement adaptation
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-06
- Publication Date
- 2026-08-13
Smart Images

Figure CN2025075932_13082026_PF_FP_ABST
Abstract
Description
RADIO RESOURCE MANAGEMENT MEASUREMENT ADAPTATIONTECHNICAL FIELD
[0001] This application relates generally to wireless communication systems, including systems, apparatuses, and methods for radio resource management measurement adaptation.BACKGROUND
[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc. ) and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) , 3GPP new radio (NR) (e.g., 5G) , and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as ) .
[0003] As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a network device of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE) . 3GPP RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and / or Next-Generation Radio Access Network (NG-RAN) .
[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the network device and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE) , and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR) . In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.
[0005] A network device used by a RAN may correspond to that RAN. One example of an E-UTRAN network device is an E-UTRAN Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) . One example of an NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
[0006] A RAN provides its communication services with external entities through its connection to a core network (CN) . For example, E-UTRAN may utilize an Evolved Packet Core (EPC) , while NG-RAN may utilize a 5G Core Network (5GC) .BRIEF DESCRIPTION OF THE DRAWINGS
[0007] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0008] FIG. 1 shows an example wireless communication system, according to one or more aspects described herein.
[0009] FIG. 2A shows an example communication block diagram, according to one or more aspects described herein.
[0010] FIG. 2B shows an example communication block diagram, according to one or more aspects described herein.
[0011] FIG. 3 shows an example communication block diagram, according to one or more aspects described herein.
[0012] FIG. 4 shows an example method of wireless communication at a UE, according to one or more aspects described herein.
[0013] FIG. 5 shows another example method of wireless communication network device, according to one or more aspects described herein.
[0014] FIG. 6 illustrates an example architecture of a wireless communication system, according to one or more aspects described herein.
[0015] FIG. 7 illustrates an example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein.DETAILED DESCRIPTION
[0016] Various embodiments are described with regard to a processor (e.g., baseband processor) , wireless device (e.g., a user equipment (UE) ) , or a network device. However, reference to a processor, wireless device, or network device is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component or device that may establish a wireless connection and is configured with the hardware, software, and / or firmware to exchange information and data over the wireless connection. Therefore, the processors, wireless devices, and network devices described herein are used to represent any appropriate electronic components or devices.
[0017] In some wireless communication networks, radio resource management (RRM) involves a set of functionalities and procedures to efficiently manage and optimize radio resources in the network. RRM measurements are used to provide the network with information about the radio environment, allowing the network to make informed decisions for resource allocation, handovers, and other optimization strategies. In the network, a UE may measure references signals transmitted by a network device to determine reference signal received power (RSRP) and reference signal received quality (RSRQ) for a downlink, and report such measurements to the network device. In the case of a serving cell, the UE may determine channel state information (CSI) , including a channel quality indicator (CQI) , rank indicator (RI) , and / or precoding matrix indicator (PMI) based on measuring CSI reference signals (CSI-RSs) transmitted by the network device. Other exemplary measurements for RRM may include interference measurements from neighboring cells, event-trigger measurements, mobility and handover-related measurements, determination of cell identify and cell identity groups for neighboring network devices, beam management measurements, UE positioning measurement, and network synchronization measurements. Measurements from neighboring cells may include measurements of synchronization signal blocks (SSBs) transmitted by the network devices of neighboring cells.
[0018] In some cases, the overhead required for reference signal measurements for RRM purposes can be high. In many cases these reference signal measurements are of SSBs or CSI-RS. A UE may be configured to measure reference signals during a particular time window, including measurement gaps (MGs) or SSB-based RRM measurement timing configuration (SMTC) windows. A measurement gap may be a periodic time duration during which the UE may tune away from a serving frequency (e.g., a particular component carrier) to another frequency to perform measurements of reference signals (e.g., SSBs, CSI-RS) . An SMTC window may also be a periodic time window during which the UE may perform measurements of SSBs. As used herein, a “measurement occasion” may refer to either one or both of an MG and / or SMTC window.
[0019] In some cases, resources used for measurement occasions (whether MG or SMTC window) may use a considerable number of resources. As an example, for an SMTC periodicity of 20 ms, the SMTC overhead in a Frequency Range 2 (FR2) may be about 25%, especially for FR2 using a 5 ms SSB burst length. As such, reducing overhead for RRM measurements is desirable to increase available resources for communication.
[0020] In addition, some use cases like extended reality (XR) (e.g., including augmented reality and / or virtual reality) may benefit from low latency communications. As such, techniques that allow a network device to skip measurement occasion may be desired. Skipping the measurement occasion may allow the network device to schedule uplink or downlink communications during the measurement occasion dynamically, increasing communication performance and reducing latency.
[0021] In order to skip a measurement occasion, a UE may be configured to skip the measurement occasions responsive to a downlink control information (DCI) message from a network device that includes an indication for a measurement occasion to be skipped. For example, a DCI message may carry an explicit indication, such as a bit value of “1” in a measurement occasion skipping field of the DCI. The bit value of “1” indicates that a next measurement occasion (e.g., a MG or SMTC window) is to be skipped for measurement by the UE, and thus may be available for communication (e.g., uplink or downlink communications) . The same DCI message that indicates for the measurement occasion to be skipped may schedule resources for the UE to perform uplink communication (e.g., an uplink grant via DCI format 0_3) or downlink communications (e.g., a downlink grant via DCI format 1_3) .
[0022] A first DCI message received at a UE may indicate that a next measurement occasion is to be skipped, having a value of “1” for a measurement skipping indication. A second DCI message received at the UE (after the first DCI message, but before the next measurement occasion) may include a second value of “0” for the measurement skipping indication. In a first set of examples, the value of “0” in the second DCI message indicates that that the next measurement occasion is not to be skipped, but the UE ignores this indication and skips the measurement occasion based on the first DCI message. Stated differently, in the first set of examples, once the UE is indicated to skip a next measurement occasion, such measurement occasion remains skipped (e.g., irrespective of later-received DCI signaling) . In a second set of examples, the value of “0” in the second DCI message indicates that that the next measurement occasion is not to be skipped, and the UE does not skip the next measurement occasion because of the value of “0” received in the second DCI message. Stated differently, up until a deadline (e.g., a lead time, or minimum time in advance of the next measurement gap) , as long as the last signaling indicates that the measurement occasion is to be skipped, the measurement occasion is skipped. Otherwise, the measurement occasion is not skipped.
[0023] A UE may communicate with a network device using multiple component carriers using a carrier aggregation (CA) configuration, or with multiple network devices in a dual connectivity (DC) configuration. Such multiple component carrier configurations may require further resources for RRM measurements, for example due to performing measurements on each of the component carriers. A UE that is communicating using multiple component carriers may utilize cross-carrier scheduling, where a DCI message received on a first component carrier may schedule communications (e.g., provide an uplink grant and / or a downlink grant) on a second component carrier.
[0024] In the case of self-scheduling, an explicit indication in a DCI message may be used to indicate for the UE to skip a measurement occasion (e.g., a 1-bit indication in a DCI format 0_1 or 1_1) . In the case of cross-carrier scheduling, an explicit indication in a DCI message may be used to indicate for the UE to skip a measurement occasion corresponding to a scheduled cell (e.g., a 1-bit indication in a DCI format 0_1, 1_1, 0_2, or 1_2) . In the case of an explicit indication for the UE to skip a particular measurement occasion, the explicit indication can be configured for each DCI format individually by higher layer.
[0025] In the case of cross-carrier scheduling, an indication for the UE to skip a measurement occasion may be provided in addition via a DCI message that schedules multiple carriers (e.g., a 1-bit indication in a DCI format 0_3 or 1_3) . In some examples, scheduling multiple carriers may be referred to as co-scheduling or multi-cell scheduling. When a measurement skipping indication is includes in the DCI message, indication may be applied to a next measurement occasion (e.g., measurement gap or scheduling restriction, such as SMTC window) . The “next measurement occasion” following the DCI may also be referred to as the first measurement occasion after the DCI message.
[0026] In order for the UE to have time to process and implement the DCI message, the DCI message needs to have been received at least a minimum time duration (which may be referred to as a “lead time” ) in advance of the measurement occasion that is affected by the DCI message (e.g., a DCI format 0_1, 1_1, 0_2, 1_2, 0_3 or 1_3) . The lead time may start from the end of the last symbol of the PDCCH that includes the corresponding DCI message. In some cases, different component carriers and / or different frequency ranges may have different lead times. Such lead times may also depend on UE capabilities. In some case, a measurement gap timing advance may also be applied for a UE. where the UE advances the start time of the measurement gap before the actual scheduled period to alight measurements with the expected arrival time of signals from the measured cells (e.g., for a distant cell) .
[0027] According to the second set of examples described above, if the last-received DCI message (e.g., the DCI message closest in time to the next measurement occasion) indicates for the measurement occasion to be skipped, then the measurement occasion is skipped. However, in the context of cross-carrier scheduling, the meaning of certain DCI messages may be ambiguous, or otherwise unclear. This lack of clarity may lead to unpredictable behavior by the UE.
[0028] Further described herein are techniques that allow adaptation of measurement occasions (e.g., measurement gaps and / or SMTC windows) , including in connection with RRM measurements. The UE and / or baseband processor of the UE can receive control signaling configuring first and second measurement occasions (e.g., measurement gaps or scheduling restrictions) on component carriers in different frequency ranges. A first DCI message may be received indicating to skip measurement of a next measurement occasion, followed by a second DCI message identifying the next measurement occasions is to be measured. Whether to skip measurement of the next measurement occasion based on the second DCI message is then determined according to one or more measure skipping applicability rules. In the case of the skipping the next measurement occasion, the UE may then proceed to communicate with the network device (e.g., transmit to or receive from the network device) during the next measurement occasion based on a determination to skip measurements during the next measurement occasion.
[0029] FIG. 1 shows an example wireless communications system 100, according to one or more aspects described herein. In one or more embodiments, wireless communications system 100 supports one or more aspects of radio resource management measurement adaptation, as further described herein.
[0030] Wireless communications system 100 includes a UE 102 and a network device 104. One or more UEs including the UE 102 may be being served by (e.g., has an established radio resource control (RRC) connection with) the network device 104 via a communication link, which may include at least a first component carrier 120 in a first frequency range (FR1) and a second component carrier 121 in a second frequency range (FR2) . Coverage area 110 (e.g., a cell or serving cell) is the service area for the RF spectrum band utilized by network device 104. In one or more embodiments, communication link may include a downlink connection and / or uplink connection. In some example, the network device 104 may communicate with the UE 102 using a set of beams 106. The UE 102 may receive messages 122 on the first component carrier, and one or more messages 124 on the second component carrier 120b.
[0031] Wireless communications system 100 further includes a neighboring network device 108. In some examples, measurement occasions (e.g., measurement gaps and / or SMTC windows) may be used by the UE 102 to measure reference signals 112 (e.g., SSBs, CSI-RS) transmitted by the neighboring network device 108.
[0032] According to the example shown with reference to the wireless communications system 100, the UE 102 may receive a DCI message 130 on the first component carrier 120. The DCI message 130 may include a measurement skipping indication identifying the next measurement occasion to be skipped for measurement. As shown with reference to the wireless communications system 100, measurement gap 136 is the next measurement gap following the DCI message 130. The measurement gap 136 may be scheduled to start at time 140.
[0033] A measurement occasion may typically be associated with a lead time duration from (e.g., a minimum time duration before) the measurement occasion before which a DCI message is to be received in order to skip measurements on that measurement occasion. The lead time duration may different between different carriers, frequency ranges, and / or subcarrier spacing, dependent on whether the DCI message is for a same carrier (e.g., in same carrier scheduling) , or is for a different carrier (e.g., in cross carrier scheduling) . Additionally, a measurement gap may have a different lead time duration than an SMTC window.
[0034] In the example shown for wireless communications system 100, the measurement gap 136 may have a lead time duration 142 with reference to the first component carrier 120, and a lead time duration 144 with reference to the second component carrier 121. As such, in order for a DCI message that includes a measurement skipping indication to affect the measurement gap 136, such measurement skipping indication needs to be received consistent with lead time duration 142 and / or lead time duration 144. For example, if DCI message 132 indicates a measurement skipping indication that measurement gap 136 is to be or not to be skipped, the measurement skipping indication can be considered for measurement gap 136 as long as received before the start of lead time duration 142. Similarly, if DCI message 134 indicates a measurement skipping indication that measurement gap 136 is to be or not to be skipped, the measurement skipping indication can be considered for measurement gap 136 as long as received before the start of lead time duration 144.
[0035] In some examples, one or more types of measurement gaps may be configured via RRC signaling, such as GapConfig. A first measurement gap type may lack priority information, whereas a second measurement gap type may include such priority information. Such priority information may be used with the UE 102 is configured with concurrent gaps and collision occurs between two measurement gaps. In the case of such collisions, the lower priority will be dropped. In some examples, the collision rules may apply between measurement gaps. In other examples, the collision rules may apply between both measurement gaps and SMTC windows. In some examples, layer one (L1) measurements may be omitted from adaptation considerations. In the context of SMTC measurements, two searchers may be assumed. In such cases, the UE 102 may select how if there are three colliding SMTC windows (e.g., in place of DCI message 130, DCI message 132, and DCI message 134) for neighboring cell measurements (e.g., of reference signals 112 from the neighboring network device 108) may be handled. From the perspective of the network device 104, the network device 104 may assume a scheduling restriction for all three component carriers corresponding to the three colliding SMTC windows. In some examples, the network device 104 may provide signaling to allow synchronization between the network and the UE 102.
[0036] In some examples, the measurement occasion configuration (e.g., a measurement gap configuration) may provide a periodic pattern derived from a configuration received via RRC signaling. The measurement occasion configuration may be control signaling configuring a first set of measurement occasions for the first component carrier 120 in the first frequency range (FR1) and configuring a second set of measurement occasions for the second component carrier 121 in the second frequency range (FR2) . The measurement occasion configuration, when a measurement gap configuration, may include a measurement gap length identifying the length of measurement gap in milliseconds; a measurement gap repetition period indicating the periodicity at which the measurement gap is repeated; and a measurement gap timing advance indicating the timing advance of the measurement gap. The configuration may also include a gapOffset that indicates the slot offset of the measurement gap pattern, which has a value from 0 to one less than the measurement gap repetition period. The UE 102 may calculate the system frame number (SFN) and subframe number of the first subframe for each gap.
[0037] The combinations of measurement gaps across different frequency ranges that are support include a UE-based measurement, where the measurement gap (e.g., or other measurement occasion such as an SMTC window) is applicable for the UE 102 generally. In other examples where the UE 102 can communicate in one or more frequency ranges, the measurement gap may be indicated as applicable for a particular frequency range, such as a first frequency range, a second frequency range, or both the first and second frequency ranges.
[0038] In one or more examples may configure measurement gaps using control signaling configuring a first set of measurement occasions (e.g., a measurement gap) for a first component carrier in a first frequency range and a second set of measurement occasions (e.g., a measurement gap) for a second component carrier in a second frequency range.
[0039] When a measurement gap is configured for one frequency range (e.g., one of FR1 or FR2) only, the DCI message (e.g., dynamic signaling with a measurement skipping indication) on a scheduled cell is for the frequency range the scheduled cell is associated with. When the dynamic signaling (e.g., DCI message 130 or DCI message 132) for the first component carrier 120 is detected, then the dynamic signaling applies for FR1 (e.g., for measurement gap 136 on the first component carrier 120) . When the dynamic signaling (e.g., DCI message 134) for the second component carrier 121 is detected, then the dynamic signaling applies for FR2 (e.g., for a measurement gap 138 on the first component carrier 120) .
[0040] When measurement gap is configured for both frequency ranges (e.g., both FR1 and FR2) , the dynamic signaling (e.g., DCI message 130, DCI message 132, or DCI message 134) on a scheduled cell is for the frequency range the scheduled cell is associated with. For example, if the first component carrier 120 is in FR1, then when dynamic signaling for the first component carrier 120 is detected (e.g., the DCI message 130 or DCI message 132) ) , then the dynamic signaling applies to measurement gaps for both FR1 and FR2. Similarly, if the second component carrier 121 is in FR2, then when dynamic signaling for the second component carrier 121 is detected (e.g., the DCI message 134) , then the dynamic signaling applies to measurement gaps for both FR1 and FR2.
[0041] Although discussed with reference to measurement occasions that may include both measurement gaps and scheduling restrictions (e.g., SMTC windows) , in some examples, measurement gaps may be skipped using the described techniques, but not scheduling restrictions. In other examples, both measurement gaps and scheduling restrictions may be considered for skipping.
[0042] According to a first set of examples, the first measurement gap after a PDCCH (e.g., that carries one of DCI message 130, DCI message 132, or DCI message 134) plus the associated lead time is identified. A measurement gap (e.g., measurement gap 136) may then be marked as skippable according to the measurement skipping indication of the associated DCI message, for example if that measurement gap was not previously configured as non-skippable (e.g., via RRC signaling) . Overlap of measurement gaps are then further resolved to find surviving measurement gaps. According to this procedure, measurement gaps are first marked as skippable. A measurement skipping applicability rule may then be run to determine which measurement gaps marked as skippable are the measurement gap or gaps referenced by the measurement skipping indication of the DCI message.
[0043] In the following set of examples, the measurement gaps are eligible for adaptation, but scheduling restrictions (e.g., layer 3 scheduling restrictions and layer 1 scheduling restrictions) are not eligible for adaptation according to the DCI messages carrying measurement skipping indications. In a first example, among measurement gap occasions that start at the same time, the measurement gap occasion with the shortest duration is referred by the dynamic signaling (e.g., one of the DCI messages) (e.g., measurement gap 138) . In a second example, among, measurement gap occasions start at the same time, the measurement gap occasion with the longest duration is referred by the dynamic signaling (e.g., one of the DCI messages) (e.g., measurement gap 136) . In a third example, among measurement gap occasions overlapping one another, the measurement gap occasion with the shortest duration is referred by the dynamic signaling (e.g., one of the DCI messages) . In a fourth example, among measurement gap occasions overlapping one another, the measurement gap occasion with the longest duration is referred by the dynamic signaling (e.g., one of the DCI messages) . In a fifth example, among measurement gap occasions overlapping one another, the measurement gap occasion which finishes earliest is referred by the dynamic signaling (e.g., one of the DCI messages) . In a sixth example, among measurement gap occasions overlapping one another, the measurement gap occasion which finishes last is referred by the dynamic signaling (e.g., one of the DCI messages) . In a seventh example, among measurement gap occasions overlapping one another, the measurement gap occasion which starts earliest is referred by the dynamic signaling (e.g., one of the DCI messages) . In an eighth example, among measurement gap occasions overlapping one another, the measurement gap occasion which starts last is referred by the dynamic signaling (e.g., one of the DCI messages) .
[0044] In the following set of examples, the measurement gaps and certain scheduling restrictions (e.g., layer 3 scheduling restrictions) are eligible for adaptation, but other scheduling restrictions (e.g., layer 1 scheduling restrictions) are not eligible for adaptation according to the DCI messages carrying measurement skipping indications. In a first example, among measurement gap and / or L3 scheduling restriction occasions start at the same time, the measurement gap occasion with the shortest duration is referred by the dynamic signaling (e.g., measurement gap 138) . In a second example, among measurement gap and / or L3 scheduling restriction occasions start at the same time, the measurement gap occasion with the longest duration is referred by the dynamic signaling (e.g., measurement gap 136) . In a third example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion with the shortest duration is referred by the dynamic signaling. In a fourth example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion with the longest duration is referred by the dynamic signaling. In a fifth example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion which finishes earliest is referred by the dynamic signaling. In a sixth example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion which finishes last is referred by the dynamic signaling. In a seventh example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion which starts earliest is referred by the dynamic signaling. In an eighth example, among measurement gap and / or L3 scheduling restriction occasions overlapping one another, the measurement gap occasion which starts last is referred by the dynamic signaling.
[0045] In one or more examples, where a scheduling restriction is considered, the scheduling restriction (e.g., a SMTC window) may map the applicable component carrier to frequency layer according to a measurement object configuration (e.g., MeasObjectNR) for the UE 102. The relevant parameters mapping the scheduling restriction to frequency may include the SSB frequency, SSB subcarrier spacing, a SMTC1 configuration, and / or an SMTC2 configuration.
[0046] In one or more example, partial skipping of measurement for a measurement occasion (e.g., a measurement gap and / or scheduling restriction) may be disallowed. For example, partial skipping of measurement occasions may result in undesired complexity and processing at the UE 102. As such, in some examples, the network device 104 does not provide measurement skipping indications, and the UE 102 does not expect to receive signaling, such that partial skipping of measurement occasions would occur. For example, a rule (whether preconfigured or via configuration) for the UE 102 may exist at the UE 102 and network device 104 such that measurement occasions that are previously indicated as “skipped” cannot be “revived” by later signaling. In other words, any skipped measurement occasion cannot later be configured by the network device 104 to be used for measurements. In another example, the rule may be that a measurement occasion which is not skipped cannot be skipped as a result of the UE 102 skipping an overlapping measurement occasion.
[0047] In some examples, it may be ambiguous at the UE 102, i.e., left for UE implementation, to handle signaling from the network device 104 (e.g., a DCI message) that would lead to partial skipping of a measurement occasion.
[0048] In yet other examples, the UE 102 may follow a rule such that a first measurement occasion that is not skipped cannot be skipped by the UE 102 as a result due to the skipping of an overlapping measurement occasion. Additionally, in this example, a second measurement occasion that at least partially (e.g., partially, or fully) overlaps with a first skipped measurement occasion is also skipped.
[0049] In some examples, the UE 102 starts with a skipped measurement occasion (e.g., a measurement gap and / or scheduling restriction indicated for skipping by the network) , and a set S consisting of OFDM symbols / time duration of the skipped measurement occasion. The UE 102 may then determine, it there is any skippable measurement occasion (e.g., a second measurement occasion) which overlaps with S, then S <= Union of (S, second measurement occasion) , …until S cannot be expanded further. According to this example, S may be the time unit for the skipping signaling (e.g., a first DCI message) . Then, the UE 102 does not expect to receive a signaling (e.g., a second DCI message) from the network device 104 to indicate “not skipped” for any duration fully or partially covered by S. According to this proposed approach, in some examples, signaling from the network device 104 may be disallowed from revert a measurement occasion from being skipped to not being skipped if the measurement occasion is in the proper superset S. In some examples, a measurement occasion (e.g., and not other measurement occasions) may be reverted to not skipped if the measurement occasion is at the beginning of a superset S (e.g., measurement gap 310 illustrated with reference to FIG. 3 below) .
[0050] FIGs. 2A and 2B show example communication block diagrams 201 and 202, according to one or more aspects described herein. In one or more embodiments, communication block diagrams 201 and 202 support one or more aspects of radio resource management measurement adaptation, as further described herein. Similarly numbered parts or signals from FIG. 1 may refer to the same parts and signals in the context of communication block diagrams 201 and 202.
[0051] In the example communication block diagrams 201 and 202, a measurement occasion for purposes of determining a next measurement occasion may refer to a measurement gap 210 that spans both the first component carrier 120 and the second component carrier 121 for purposes of determining the lead time duration. In some examples, the measurement gap 210 may be configured for the first component carrier 120, but the lead time duration determined on both the first component carrier 120 and the second component carrier 121 as if the measurement gap 210 spans both component carriers. As such, the lead time duration 142 and the lead time duration 144 may considered to start from measurement gap 210.
[0052] As shown in the context of the example communication block diagram 201, a measurement occasion may be considered to have been formed by the inclusion of one or more SMTC windows, such as SMTC window 212 in the first component carrier 120 and an SMTC window 214 in the second component carrier 121. As such, the lead time durations for each of the first component carrier 120 and the second component carrier 121 may start from the combined measurement occasion.
[0053] As shown in the context of the example communication block diagram 202, each SMTC window may also be considered separately. As shows, a lead time duration 220 may start from SMTC window 216 in the first component carrier 120. Similarly, the lead time duration 222 may start from SMTC window 218 in the second component carrier 121.
[0054] FIG. 3 shows an example communication block diagram 300, according to one or more aspects described herein. In one or more embodiments, communication block diagram 300 supports one or more aspects of radio resource management measurement adaptation, as further described herein. Similarly numbered parts or signals from FIGS. 1, 2A, or 2B may refer to the same parts and signals in the context of communication block diagram 300.
[0055] In some examples, to establish a processing sequence for RRM measurement adaptation, overlap of measurement occasions may be first resolved, for example where measurement gaps and scheduling restrictions (e.g., SMTC windows) are considered following (e.g., following the last symbol of) a PDCCH that contains the DCI message that indicates RRM measurement skipping (e.g., the DCI message, such as DCI message 130, that includes a measurement skipping indication) . The processing sequence window 302 may thus be the shortest time duration enclosing measurement occasions (e.g., including both measurement gaps and scheduling restrictions) overlap before a time duration (e.g., at least one orthogonal frequency division multiplexing (OFDM) symbol) after the processing window which is not occupied by any configured measurement occasion (e.g., any measurement gap and / or scheduling restriction) .
[0056] As further described herein, a processing sequence may be established using a processing sequence window 302. A processing sequence window may include one or more measurement occasions of a first set of measurement occasions and the second set of measurement occasions that overlap in time with the next measurement occasion. The determination of whether to skip measurement of the next measurement occasion may apply to the each of the one or more measurement occasions of the processing sequence window.
[0057] As illustrated in the example of communication block diagram 300, measurement gap 310, measurement gap 312, and SMTC window 314 overlap in time before a time duration 318 that is not occupied by any configured measurement occasion, As such, the processing sequence window 302 includes the measurement gap 310, measurement gap 312, and SMTC window 314 (and excludes SMTC window 316) .
[0058] In view of the processing sequence window 302, the DCI message 130 and the DCI message 132 (e.g., the measurement skipping indications thereof) may be applied to the measurement occasions within the processing sequence window 302 (e.g., measurement gap 310, measurement gap 312, and SMTC window 314) . DCI message 134 is not applied to the measurement occasions of the processing sequence window 302.
[0059] However, once the processing sequence window 302 is skipped for the DCI message 134 (e.g., even though DCI message 134 precedes the lead time duration 344) , the DCI message 134 is applied to a subsequent measurement occasion, which may include at least the SMTC window 316, where the DCI message 134 precedes a lead time duration associated with the SMTC window 316.
[0060] FIG. 4 shows an example method 400 of wireless communication by a UE, according to one or more aspects described herein. In some cases, the UE may be the wireless device 702 or UE 102. In some cases, the method 400 may be performed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores, and memory that is coupled to the processor core (s) . The memory may store instructions that, when executed by the processor core (s) , causes the baseband processor to perform the operations of the method 400. As the baseband processor performs the operations of the method 400, the baseband processor may also cause other components of the UE to perform, or discontinue, various operations.
[0061] At 402, the method 400 includes receiving control signaling configuration a first set of measurement occasions in a first component carrier. In some embodiments, the method 400 includes receiving control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range.
[0062] At 404, the method 400 includes receiving a first DCI message with a measurement skipping indication. In some embodiments, the method 400 includes receiving, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement.
[0063] At 406, the method 400 includes receiving a second DCI message indicating for the next measurement occasion to be measured. In some embodiments, the method 400 includes receiving, on the second component carrier after receiving the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured.
[0064] At 408, the method 400 includes determining whether to skip the next measurement occasion. In some embodiments, the method 400 includes determining, according to a measurement skipping applicability rule, whether to skip measurement of the next measurement occasion.
[0065] At 410, the method 400 includes, in the case that the answer to 408 is affirmative, receiving data or transmitting data to the network device based on determining to skip the next measurement occasion. In some embodiments, the method 400 includes transmitting a data message to or receiving the data message from the network device during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion.
[0066] At 412, the method 400 includes, in the case that the answer to 408 is negative, performing measurements of reference signals during the next measurement occasion. In some embodiments, the method 400 includes performing measurements of reference signals received during the next measurement occasion based at least in part on a determination to perform measurements during the next measurement occasion.
[0067] In some embodiments, the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in a same frequency range; and the determination to skip the measurements during the next measurement occasion is based at least in part on the first DCI message being received in the same frequency range as the measurement gap. In some embodiments, the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in any frequency range; and the determination to perform the measurements of reference signals received during the next measurement occasion is based at least in part on the measurement skipping applicability rule.
[0068] In one or more embodiments, the method further includes identifying, for DCI messages in the first component carrier, a first lead time duration from the next measurement occasion; identifying, for DCI messages in the second component carrier, a second lead time duration from the next measurement occasion; and determining whether the second DCI message is received before the first lead time duration and the second lead time duration.
[0069] In some embodiments, the next measurement occasion includes an SMTC window on one or both of the first component carrier or the second component carrier.
[0070] In one or more embodiments, the method further includes determining the next measurement occasion from the first set of measurement occasions and the second set of measurement occasions based at least in part on a duration of the next measurement occasion, an ending time of the next measurement occasion, or a starting time of the next measurement occasion.
[0071] In one or more embodiments, the method further includes determining a processing sequence window that includes one or more measurement occasions of the first set of measurement occasions and the second set of measurement occasions that overlap in time with the next measurement occasion, where the determination of whether to skip measurement of the next measurement occasion applies to the each of the one or more measurement occasions of the processing sequence window.
[0072] In some embodiments, the measurement skipping applicability rule disallows a measurement occasion to be partial skipped for measurement. In some embodiments, the measurement skipping applicability rule disallows a measurement occasion previously indicated as skipped for measurement to be partially available for measurement.
[0073] In some embodiments, one or both of the first set of measurement occasions include a first set of measurement gaps or the second set of measurement occasions include a second set of measurement gaps. In some embodiments, one or both of the first set of measurement occasions include a first set of SMTC windows or the second set of measurement occasions include a second set of SMTC windows.
[0074] The method 400 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
[0075] FIG. 5 shows an example method 500 of wireless communication by a network device, according to one or more aspects described herein. In one or more embodiments, method 500 supports one or more aspects of radio resource management measurement adaptation, as further described herein. In some cases, the network device may be the network device 104, network device 720, or one of the other network devices described herein. The method 500 may be performed using a processor, a transceiver, or other components of the network device.
[0076] At 502, the method 500 includes transmitting control signaling configuration a first set of measurement occasions in a first component carrier. In some embodiments, the method 500 includes transmitting, to a UE, control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range.
[0077] At 504, the method 500 includes transmitting a first DCI message with a measurement skipping indication. In some embodiments, the method 500 includes transmitting, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement.
[0078] At 506, the method 500 includes transmitting a second DCI message indicating for the next measurement occasion to be measured. In some embodiments, the method 500 includes transmitting, on the second component carrier after transmitting the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured.
[0079] At 508, the method 500 includes determine whether to skip the next measurement occasion according to a measurement skipping applicability rule. In some embodiments, the method 500 includes determining, according to a measurement skipping applicability rule, whether the UE is to skip measurement of the next measurement occasion.
[0080] At 510, the method 500 includes receiving data from the UE or transmitting data to the UE based on determining to skip the next measurement occasion. In some embodiments, the method 500 includes receiving a data message from the UE or transmitting the data message to the UE during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion.
[0081] In some embodiments, the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in a same frequency range; and the determination to skip the measurements during the next measurement occasion is based at least in part on the first DCI message being transmitted in the same frequency range as the measurement gap. In some embodiments, the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in any frequency range.
[0082] In one or more embodiments, the method further includes identifying, for DCI messages in the first component carrier, a first lead time duration from the next measurement occasion; identifying, for DCI messages in the second component carrier, a second lead time duration from the next measurement occasion; and determining whether the second DCI message is transmitted before the first lead time duration and the second lead time duration.
[0083] In some embodiments, the next measurement occasion includes an SMTC window on one or both of the first component carrier or the second component carrier. In one or more embodiments, the method further includes determining the next measurement occasion from the first set of measurement occasions and the second set of measurement occasions based at least in part on a duration of the next measurement occasion, an ending time of the next measurement occasion, or a starting time of the next measurement occasion.
[0084] In one or more embodiments, the method further includes determining a processing sequence window that includes one or more measurement occasions of the first set of measurement occasions and the second set of measurement occasions that overlap in time with the next measurement occasion, where the determination of whether to skip measurement of the next measurement occasion applies to the each of the one or more measurement occasions of the processing sequence window.
[0085] In some embodiments, the measurement skipping applicability rule disallows a measurement occasion to be partial skipped for measurement. In some embodiments, the measurement skipping applicability rule disallows a measurement occasion previously indicated as skipped for measurement to be partially available for measurement.
[0086] In some embodiments, one or both of the first set of measurement occasions include a first set of measurement gaps or the second set of measurement occasions include a second set of measurement gaps. In some embodiments, one or both of the first set of measurement occasions include a first set of SMTC windows or the second set of measurement occasions include a second set of SMTC windows.
[0087] The method 500 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
[0088] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 400 or 500. In the context of method 400, this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) . In the context of method 500, this non-transitory computer-readable media may be, for example, a memory of a network device (such as a memory 724 of a network device 720, as described herein) .
[0089] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method 400 or 500. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE) . In the context of method 500, this apparatus may be, for example, an apparatus of a network device (such as a network device 720, as described herein) .
[0090] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 400 or 500. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE, as described herein) . In the context of the method 500, this apparatus may be, for example, an apparatus of a network device (such as a network device 720, as described herein) .
[0091] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 400, or 500.
[0092] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method 400 or 500. In the context of method 400, the processor may be a processor of a UE (such as a processor (s) 704 of a wireless device 702 that is a UE, as described herein) , and the instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) . In the context of method 500, the processor may be a processor of a network device (such as a processor (s) 722 of a network device 720, as described herein) , and the instructions may be, for example, located in the processor and / or on a memory of the network device (such as a memory 724 of a network device 720, as described herein) .
[0093] FIG. 6 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example wireless communication system 600 that operates in conjunction with the LTE system standards or specifications and / or 5G or NR system standards or specifications, as provided by 3GPP technical specifications.
[0094] As shown, the wireless communication system 600 includes UE 602 and UE 604 (although any number of UEs may be used) . In this example, the UE 602 and the UE 604 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.
[0095] The UE 602 and UE 604 may be configured to communicatively couple with a RAN 606. In embodiments, the RAN 606 may be NG-RAN, E-UTRAN, etc. The UE 602 and UE 604 utilize connections (or channels) (shown as connection 608 and connection 610, respectively) with the RAN 606, each of which comprises a physical communications interface. The RAN 606 can include one or more network devices, such as base station 612 and base station 614, that enable the connection 608 and connection 610.
[0096] In this example, the connection 608 and connection 610 are air interfaces to enable such communicative coupling and may be consistent with RAT (s) used by the RAN 606, such as, for example, an LTE and / or NR.
[0097] In some embodiments, the UE 602 and UE 604 may also directly exchange communication data via a sidelink interface 616. The UE 604 is shown to be configured to access an access point (shown as AP 618) via connection 620. By way of example, the connection 620 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 618 may comprise a router. In this example, the AP 618 may be connected to another network (for example, the Internet) without going through a CN 624.
[0098] In embodiments, the UE 602 and UE 604 can be configured to communicate using OFDM communication signals with each other or with the base station 612 and / or the base station 614 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0099] In some embodiments, all or parts of the base station 612 or base station 614 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 612 or base station 614 may be configured to communicate with one another via interface 622. In embodiments where the wireless communication system 600 is an LTE system (e.g., when the CN 624 is an EPC) , the interface 622 may be an X2 interface. The X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 600 is an NR system (e.g., when CN 624 is a 5GC) , the interface 622 may be an Xn interface. The Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 612 (e.g., a gNB) connecting to the 5GC and an eNB, and / or between two eNBs connecting to the 5GC (e.g., CN 624) .
[0100] The RAN 606 is shown to be communicatively coupled to the CN 624. The CN 624 may comprise one or more network elements 626, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 602 and UE 604) who are connected to the CN 624 via the RAN 606. The components of the CN 624 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0101] In embodiments, the CN 624 may be an EPC, and the RAN 606 may be connected with the CN 624 via an S1 interface 628. In embodiments, the S1 interface 628 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 612 or base station 614 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 612 or base station 614 and mobility management entities (MMEs) .
[0102] In embodiments, the CN 624 may be a 5GC, and the RAN 606 may be connected with the CN 624 via an NG interface 628. In embodiments, the NG interface 628 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 612 or base station 614 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 612 or base station 614 and access and mobility management functions (AMFs) .
[0103] Generally, an application server 630 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 624 (e.g., packet switched data services) . The application server 630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 602 and UE 604 via the CN 624. The application server 630 may communicate with the CN 624 through an IP communications interface 632.
[0104] FIG. 7 illustrates an example system 700 for performing signaling 738 between a wireless device 702 and a network device 720, according to embodiments described herein. The system 700 may be a portion of a wireless communication system as herein described. The wireless device 702 may be, for example, a UE of a wireless communication system. The network device 720 may be, for example, a base station (e.g., an eNB or a gNB) or a radio head of a wireless communication system.
[0105] The wireless device 702 may include one or more processor (s) 704. The processor (s) 704 may execute instructions such that various operations of the wireless device 702 are performed, as described herein. The processor (s) 704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0106] The wireless device 702 may include a memory 706. The memory 706 may be a non-transitory computer-readable storage medium that stores instructions 708 (which may include, for example, the instructions being executed by the processor (s) 704) . The instructions 708 may also be referred to as program code or a computer program. The memory 706 may also store data used by, and results computed by, the processor (s) 704.
[0107] The wireless device 702 may include one or more transceiver (s) 710 (also collectively referred to as a transceiver 710) that may include radio frequency (RF) transmitter and / or receiver circuitry that use the antenna (s) 712 of the wireless device 702 to facilitate signaling (e.g., the signaling 738) to and / or from the wireless device 702 with other devices (e.g., the network device 720) according to corresponding RATs.
[0108] The wireless device 702 may include one or more antenna (s) 712 (e.g., one, two, four, eight, or more) . For embodiments with multiple antenna (s) 712, the wireless device 702 may leverage the spatial diversity of such multiple antenna (s) 712 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) . MIMO transmissions by the wireless device 702 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 702 that multiplexes the data streams across the antenna (s) 712 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) . Some embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
[0109] In some embodiments having multiple antennas, the wireless device 702 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 712 are relatively adjusted such that the (joint) transmission of the antenna (s) 712 can be directed (this is sometimes referred to as beam steering) .
[0110] The wireless device 702 may include one or more interface (s) 714. The interface (s) 714 may be used to provide input to or output from the wireless device 702. For example, a wireless device 702 that is a UE may include interface (s) 714 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 710 / antenna (s) 712 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
[0111] The wireless device 702 may include measurement adaptation manager 716. The measurement adaptation manager 716 may be implemented via hardware, software, or combinations thereof. For example, the measurement adaptation manager 716 may be implemented as a processor, circuit, and / or instructions 708 stored in the memory 706 and executed by the processor (s) 704. In some examples, the measurement adaptation manager 716 may be integrated within the processor (s) 704 and / or the transceiver (s) 710. For example, the measurement adaptation manager 716 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 704 or the transceiver (s) 710.
[0112] The measurement adaptation manager 716 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-7, from a wireless device or UE perspective. The measurement adaptation manager 716 may be configured, for example, to perform receiving control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range; receiving, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement; receiving, on the second component carrier after receiving the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured; determining, according to a measurement skipping applicability rule, whether to skip measurement of the next measurement occasion; and transmitting a data message to or receiving the data message from the network device during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion, or performing measurements of reference signals received during the next measurement occasion based at least in part on a determination to perform measurements during the next measurement occasion.
[0113] The network device 720 may include one or more processor (s) 722. The processor (s) 722 may execute instructions such that various operations of the network device 720 are performed, as described herein. The processor (s) 722 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0114] The network device 720 may include a memory 724. The memory 724 may be a non-transitory computer-readable storage medium that stores instructions 726 (which may include, for example, the instructions being executed by the processor (s) 722) . The instructions 726 may also be referred to as program code or a computer program. The memory 724 may also store data used by, and results computed by, the processor (s) 722.
[0115] The network device 720 may include one or more transceiver (s) 728 (also collectively referred to as a transceiver 728) that may include RF transmitter and / or receiver circuitry that use the antenna (s) 730 of the network device 720 to facilitate signaling (e.g., the signaling 738) to and / or from the network device 720 with other devices (e.g., the wireless device 702) according to corresponding RATs.
[0116] The network device 720 may include one or more antenna (s) 730 (e.g., one, two, four, or more) . In embodiments having multiple antenna (s) 730, the network device 720 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
[0117] The network device 720 may include one or more interface (s) 732. The interface (s) 732 may be used to provide input to or output from the network device 720. For example, a network device 720 of a RAN (e.g., a base station, a radio head, etc. ) may include interface (s) 732 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 728 / antenna (s) 730 already described) that enables the network device 720 to communicate with other equipment in a network, and / or that enables the network device 720 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the network device 720 or other equipment operably connected thereto.
[0118] The network device 720 may include at least one measurement adaptation manager 734. The measurement adaptation manager 734 may be implemented via hardware, software, or combinations thereof. For example, the measurement adaptation manager 734 may be implemented as a processor, circuit, and / or instructions 726 stored in the memory 724 and executed by the processor (s) 722. In some examples, the measurement adaptation manager 734 may be integrated within the processor (s) 722 and / or the transceiver (s) 728. For example, the measurement adaptation manager 734 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 722 or the transceiver (s) 728.
[0119] The measurement adaptation manager 734 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-7, from a network device perspective. The measurement adaptation manager 734 may be configured, for example, to perform transmitting, to a UE, control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range; transmitting, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement; transmitting, on the second component carrier after transmitting the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured; determining, according to a measurement skipping applicability rule, whether the UE is to skip measurement of the next measurement occasion; and receiving a data message from the UE or transmitting the data message to the UE during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion.
[0120] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor (or processor) as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, network device, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
[0121] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0122] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) . The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.
[0123] The systems described herein pertain to specific embodiments but are provided as examples. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems, or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.
[0124] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein but may be modified within the scope and equivalents of the appended claims.
Claims
1.A baseband processor comprising a memory and configured to:receive control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range;receive, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement;receive, on the second component carrier after receiving the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured; anddetermine, according to a measurement skipping applicability rule, whether to skip measurement of the next measurement occasion; andtransmitting a data message to or receiving the data message from the network device during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion, orperforming measurements of reference signals received during the next measurement occasion based at least in part on a determination to perform measurements during the next measurement occasion.2.The baseband processor of claim 1, wherein:the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in a same frequency range; andthe determination to skip the measurements during the next measurement occasion is based at least in part on the first DCI message being received in the same frequency range as the measurement gap.3.The baseband processor of claim 1, wherein:the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in any frequency range; andthe determination to perform the measurements of reference signals received during the next measurement occasion is based at least in part on the measurement skipping applicability rule.4.The baseband processor of claim 1, further configured to:identify, for DCI messages in the first component carrier, a first lead time duration from the next measurement occasion;identify, for DCI messages in the second component carrier, a second lead time duration from the next measurement occasion; anddetermine whether the second DCI message is received before the first lead time duration and the second lead time duration.5.The baseband processor of claim 1, wherein:the next measurement occasion comprises an SMTC window on one or both of the first component carrier or the second component carrier.6.The baseband processor of claim 1, further configured to:determine the next measurement occasion from the first set of measurement occasions and the second set of measurement occasions based at least in part on a duration of the next measurement occasion, an ending time of the next measurement occasion, or a starting time of the next measurement occasion.7.The baseband processor of claim 1, further configured to:determine a processing sequence window that includes one or more measurement occasions of the first set of measurement occasions and the second set of measurement occasions that overlap in time with the next measurement occasion, wherein the determination of whether to skip measurement of the next measurement occasion applies to the each of the one or more measurement occasions of the processing sequence window.8.The baseband processor of claim 1, wherein:the measurement skipping applicability rule disallows a measurement occasion to be partial skipped for measurement.9.The baseband processor of claim 1, wherein:the measurement skipping applicability rule disallows a measurement occasion previously indicated as skipped for measurement to be partially available for measurement.10.A method of wireless communication at a network device, comprising:transmitting, to a UE, control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range;transmitting, to the UE on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement;transmitting, to the UE on the second component carrier after transmitting the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured;determining, according to a measurement skipping applicability rule, whether the UE is to skip measurement of the next measurement occasion; andreceiving a data message from the UE or transmitting the data message to the UE during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion.11.The method of claim 10, wherein:the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in a same frequency range; andthe determination to skip the measurements during the next measurement occasion is based at least in part on the first DCI message being transmitted in the same frequency range as the measurement gap.12.The method of claim 10, wherein:the measurement skipping applicability rule indicates that each measurement skipping indication applies to component carriers in any frequency range.13.The method of claim 10, further comprising:identifying, for DCI messages in the first component carrier, a first lead time duration from the next measurement occasion;identifying, for DCI messages in the second component carrier, a second lead time duration from the next measurement occasion; anddetermining whether the second DCI message is transmitted before the first lead time duration and the second lead time duration.14.The method of claim 10, wherein:the next measurement occasion comprises an SMTC window on one or both of the first component carrier or the second component carrier.15.The method of claim 10, wherein:the measurement skipping applicability rule disallows a measurement occasion to be partial skipped for measurement.16.The method of claim 10, wherein:the measurement skipping applicability rule disallows a measurement occasion previously indicated as skipped for measurement to be partially available for measurement.17.A method of wireless communication at a UE, comprising:receiving control signaling configuring a first set of measurement occasions for a first component carrier in a first frequency range and a second set of measurement occasions for a second component carrier in a second frequency range;receiving, on the first component carrier, a first DCI message comprising a measurement skipping indication for a next measurement occasion of the first set of measurement occasions, the measurement skipping indication identifying the next measurement occasion to be skipped for measurement;receiving, on the second component carrier after receiving the first DCI message and prior to the next measurement occasion, a second DCI message comprising a measurement skipping indication identifying the next measurement occasion is to be measured; anddetermining, according to a measurement skipping applicability rule, whether to skip measurement of the next measurement occasion; andtransmitting a data message to or receiving the data message from the network device during the next measurement occasions based at least in part on a determination to skip measurements during the next measurement occasion, orperforming measurements of reference signals received during the next measurement occasion based at least in part on a determination to perform measurements during the next measurement occasion.18.The method of claim 17, wherein / further comprising:identifying, for DCI messages in the first component carrier, a first lead time duration from the next measurement occasion;identifying, for DCI messages in the second component carrier, a second lead time duration from the next measurement occasion; anddetermining whether the second DCI message is received before the first lead time duration and the second lead time duration.19.The method of claim 17, wherein / further comprising:determining the next measurement occasion from the first set of measurement occasions and the second set of measurement occasions based at least in part on a duration of the next measurement occasion, an ending time of the next measurement occasion, or a starting time of the next measurement occasion.20.The method of claim 17, wherein / further comprising:determining a processing sequence window that includes one or more measurement occasions of the first set of measurement occasions and the second set of measurement occasions that overlap in time with the next measurement occasion, wherein the determination of whether to skip measurement of the next measurement occasion applies to the each of the one or more measurement occasions of the processing sequence window.