Measurement gap sharing with delay critical traffic
By configuring the UE in the wireless communication system to suppress some measurement gaps and share time resources, the problem of measurement gaps and data transmission conflicts in delay-critical services is solved, achieving more efficient data communication and improved service quality for delay-sensitive services.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2024-08-22
- Publication Date
- 2026-04-17
AI Technical Summary
In wireless communication systems, the conflict between measurement gaps and data transmission in delay-critical services leads to data transmission delays, especially during UE mobility events, where the overlap between measurement gaps and DRX cycles causes data transmission delays.
By configuring the UE to suppress some measurement gaps and share time resources, it allows the reception of delayed critical service data during measurement gaps. The use of measurement gaps can be dynamically adjusted by utilizing parameter adjustments and criteria to meet thresholds. Combined with timer and event triggering mechanisms, the timing of measurements and the sharing of data communication can be optimized.
It effectively reduced the data transmission latency of critical services, improved the efficiency of data communication, and enhanced the service quality of latency-sensitive services.
Smart Images

Figure CN121890150A_ABST
Abstract
Description
Cross-references
[0001] This patent application claims priority to U.S. Patent Application No. 18 / 480,247, filed October 3, 2023, entitled “MEASUREMENT GAPSHARING WITH DELAY CRITICAL TRAFFIC”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field
[0002] The following pertains to wireless communications, including the sharing of measurement gaps with latency-critical services. Background Technology
[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Components within a wireless communication system may be coupled to each other (e.g., operationally coupled, communicatively coupled, functionally coupled, electronically coupled, and / or electrically coupled). Summary of the Invention
[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting the sharing of measurement gaps for delay-critical services. For example, the described technology provides a network entity that sends a configuration to a user equipment (UE) including a parameter indicating the number of scheduled measurement gaps available for performing measurements. The UE can perform measurements on signals transmitted from a neighboring network entity as part of a mobility event. In some examples, the number can be a fraction or percentage of the scheduled measurement gaps. The UE can apply the parameter by suppressing one or more measurement gaps and can receive data (e.g., extended reality (XR) services) from the network entity using one or more time resources (e.g., time slots, symbols) associated with the suppressed measurement gaps. The UE can continue performing measurements during measurement gaps that are not dropped. In some examples, the network entity can configure the parameter (e.g., statically, dynamically) based on scheduled XR services, one or more criteria associated with the UE (e.g., signal measurements, the UE's mobility state) meeting a threshold, or any combination thereof. Similarly, the UE may determine whether to activate or deactivate the parameter based on the scheduled XR service, the threshold being met by one or more criteria associated with the UE, or any combination thereof. In some examples, the UE may determine to deactivate (e.g., stop applying) the parameter based on a timer, an event trigger, or both.
[0005] A method for wireless communication by a user equipment (UE) is described. The method may include: receiving an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between measurement execution and data communication; performing a measurement during a first subset of the set of multiple measurement times; and transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement times, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement times, and wherein a first number of measurement times in the first subset of the set of multiple measurement times and a second number of measurement times in the second subset of the set of multiple measurement times are determined based on the parameters.
[0006] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the UE to: receive an instruction for a configuration of a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between measurement execution and data communication; perform a measurement during a first subset of the set of multiple measurement times; and transmit one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement times, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement times, and wherein a first number of measurement times in the first subset of the set of multiple measurement times and a second number of measurement times in the second subset of the set of multiple measurement times are determined based on the parameters.
[0007] Another UE for wireless communication is described. The UE may include: components for receiving an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between measurement execution and data communication; components for performing measurements during a first subset of the set of multiple measurement times; and components for transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement times, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement times, and wherein a first number of measurement times in the first subset of the set of multiple measurement times and a second number of measurement times in the second subset of the set of multiple measurement times are determined based on the parameters.
[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: receive an instruction for a configuration of a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between the execution of measurements and data communication; perform measurements during a first subset of the set of multiple measurement times; and transmit one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement times, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement times, and wherein a first number of measurement times in the first subset of the set of multiple measurement times and a second number of measurement times in the second subset of the set of multiple measurement times are determined based on the parameters.
[0009] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the metric may be a percentage value of the set of multiple measurement moments, a fraction of the set of multiple measurement moments, or any combination thereof.
[0010] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the parameter also includes a second metric for sharing the first subset of the set of multiple measurement opportunities between intra-frequency and inter-frequency measurements.
[0011] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for applying the configuration to the set of multiple measurement times based on data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
[0012] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the data type may be XR services, ultra-reliable and low-latency communications (URLLC) services, or combinations thereof.
[0013] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the one or more criteria include the following criteria: one or more signal measurements performed by the UE on a serving cell associated with a network entity, radio resource management relaxation conditions, the amount of data buffered in a logical channel, or any combination thereof.
[0014] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the one or more signal measurements performed by the UE on the serving cell associated with the network entity include Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or both.
[0015] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for applying the configuration to a set of multiple measurement opportunities over a duration following data communication, based on a timer associated with data transmission to network entities.
[0016] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for pausing the application of this configuration to a set of multiple measurement events based on event triggering.
[0017] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, the event triggering includes radio link failure (RLF), beam failure recovery, candidate beam detection, RSRP meeting a first threshold, RSRQ meeting a second threshold, or any combination thereof.
[0018] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a cell detection period, a synchronization signal block (SSB) index identification period, a measurement period, or any combination thereof based on a scaling factor associated with the parameter.
[0019] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication that the UE may be applying a parameter based on the satisfaction of one or more criteria associated with the UE.
[0020] In some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein, the indication may be received via downlink control information (DCI), media access control-control element (MAC-CE), radio resource control (RRC) signaling, system information (SI) messages, or any combination thereof.
[0021] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0022] A method for wireless communication by a network entity is described. The method may include: sending to a UE an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between performing measurement and data communication; and communicating one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0023] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the network entity to send to a UE an instruction for a configuration of a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between measurement and data communication; and communicating one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0024] Another network entity for wireless communication is described. This network entity may include: components for sending to a UE an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of the set of multiple measurement times for metrics between performing measurement and data communication; and components for communicating one or more data messages with the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: send instructions to a UE indicating a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating metrics for sharing the set of multiple measurement times between performing measurement and data communication; and communicate one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the configuration may be based on data types, one or more criteria associated with the UE satisfying thresholds, or any combination thereof.
[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the data type may be XR services, URLLC services, or a combination thereof.
[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in a logical channel, or any combination thereof.
[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more signal measurements performed by the UE on the serving cell associated with the network entity include RSRP, RSRQ, or both.
[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the metric may be a percentage value of the set of multiple measurement moments, a fraction of the set of multiple measurement moments, or any combination thereof.
[0031] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the parameter also includes a second metric for a second subset of the set for sharing multiple measurement opportunities between intra-frequency and inter-frequency measurements.
[0033] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining cell detection periods, SSB index identification periods, measurement periods, or any combination thereof based on a scaling factor associated with the parameter.
[0034] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication that the UE may apply the parameter based on one or more criteria associated with the UE satisfying a threshold.
[0035] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the instruction may be sent via DCI, MAC-CE, RRC signaling, SI messages, or any combination thereof. Attached Figure Description
[0036] Figure 1 An example of a wireless communication system that supports and delays critical operations by sharing measurement gaps according to one or more aspects of this disclosure is shown.
[0037] Figure 2 An example of a wireless communication system that supports and delays critical operations by sharing measurement gaps according to one or more aspects of this disclosure is shown.
[0038] Figure 3 An example of a communication timeline shared during measurement gaps supporting and delaying critical operations, according to one or more aspects of this disclosure, is shown.
[0039] Figure 4 An example of a process flow for sharing measurement gaps that support and delay critical operations, according to one or more aspects of this disclosure, is shown.
[0040] Figure 5 and Figure 6 A block diagram of an apparatus for sharing measurement gaps that support and delay critical operations, according to one or more aspects of this disclosure, is shown.
[0041] Figure 7 A block diagram of a communication manager for sharing measurement gaps supporting and delay-critical operations, according to one or more aspects of this disclosure, is shown.
[0042] Figure 8 A diagram of a system including a device for sharing measurement gaps that support and delay critical operations, according to one or more aspects of this disclosure, is shown.
[0043] Figure 9 and Figure 10 A block diagram of an apparatus for sharing measurement gaps that support and delay critical operations, according to one or more aspects of this disclosure, is shown.
[0044] Figure 11 A block diagram of a communication manager for sharing measurement gaps supporting and delay-critical operations, according to one or more aspects of this disclosure, is shown.
[0045] Figure 12 A diagram of a system including a device for sharing measurement gaps that support and delay critical operations, according to one or more aspects of this disclosure, is shown.
[0046] Figures 13 to 17 A flowchart illustrating a method for sharing measurement gaps that supports and delays critical operations according to one or more aspects of this disclosure is shown. Detailed Implementation
[0047] In some wireless communication systems, a User Equipment (UE) can communicate with network entities associated with a corresponding serving cell. The UE can be configured to receive delay-sensitive services (e.g., extended reality (XR) services) from the network entity according to a discontinuous reception (DRX) cycle. In some examples, the UE can move within the serving cell and trigger mobility events. In such examples, as part of a mobility event, the network entity can configure the UE with one or more measurement gaps (e.g., timing intervals) to perform measurements on signals transmitted from neighboring network entities (e.g., associated with a neighboring cell). In some cases, neighboring cells may operate using frequencies different from those used by the serving cell. In such cases, the UE can tune away from the serving cell frequency and tune to the neighboring cell frequency to perform measurements on the neighboring cell during one or more measurement gaps. However, the measurement gaps may overlap with the DRX cycle in time, and the UE may not be able to transmit or receive data with (e.g., associated with the serving cell) network entities during the measurement gaps. Additionally or alternatively, the DRX activity duration may expire during the measurement gap, and any data that was not successfully sent to the UE may be deferred to the upcoming DRX activity duration, which may delay data transmission between the UE and network entities.
[0048] Various aspects of this disclosure relate to measurement gap sharing with delay-critical services. In some examples, a network entity may configure a UE with parameters associated with measurement gap sharing. The parameters may define the number of configured measurement gaps available for performing measurements (e.g., inter-frequency, intra-frequency). In some examples, the parameters may be a fraction or percentage of the configured measurement gaps. The UE may suppress one or more measurement gaps based on the parameters and may receive data (e.g., XR services) from the network entity according to a configured DRX cycle. In some examples, the parameters may be configured based on scheduled XR services, one or more criteria associated with the UE (e.g., signal measurements, UE mobility state) meeting a threshold, or any combination thereof. In some examples, the network entity may dynamically adjust the parameters based on changes to scheduled XR services, changes to one or more criteria associated with the UE, the presence of buffered data at the UE, or any combination thereof. Additionally or alternatively, the UE or network entity may determine one or more parameters associated with cell detection, synchronization block index identification, or measurement based on the value of a scaling factor associated with the parameters.
[0049] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are additionally illustrated and described with reference to communication timelines and process flows. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to measurement gaps shared with delay-critical services, and are described with reference to these diagrams.
[0050] Figure 1 An example of a wireless communication system 100 supporting measurement gap sharing for latency-critical services according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0051] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).
[0052] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein can be able to support communication with various types of devices, such as other UE 115s or network entities 105, such as Figure 1 As shown.
[0053] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.
[0054] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.
[0055] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).
[0056] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0057] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.
[0058] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.
[0059] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support measurement gap sharing with latency-critical services as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).
[0060] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein “device” may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as personal electronic devices, such as cellular phones, personal digital assistants (PDAs), multimedia / entertainment devices (e.g., radios, MP3 players, or video devices), cameras, gaming devices, navigation / positioning devices (e.g., GNSS (Global Navigation Satellite System) devices based on, for example, GPS (Global Positioning System), BeiDou system, GLONASS or Galileo system, ground-based devices, etc.), tablet computers, laptop computers, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), drones, robots / robotic devices, vehicles, vehicle equipment, meters (e.g., parking timers, electricity meters, gas meters, water meters), monitors, air pumps, electrical appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / healthcare devices, implants, sensors / actuators, displays, or any other suitable device configured to communicate via wireless or wired media. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which can be implemented in various objects such as appliances or vehicles, meters, etc.
[0061] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown.
[0062] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).
[0063] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0064] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).
[0065] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.
[0066] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).
[0067] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.
[0068] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.
[0069] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.
[0070] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).
[0071] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.
[0072] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.
[0073] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.
[0074] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.
[0075] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system in which each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.
[0076] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0077] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).
[0078] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.
[0079] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.
[0080] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.
[0081] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.
[0082] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).
[0083] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.
[0084] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.
[0085] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).
[0086] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined by listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0087] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.
[0088] In some examples, UE 115 may communicate data to network entity 105 associated with the serving cell (e.g., coverage area 110) according to the DRX cycle. UE 115 may also perform one or more measurements (e.g., inter-frequency, intra-frequency) on signals transmitted by a neighboring (e.g., second) network entity during one or more measurement gaps. In some examples, network entity 105 may configure UE 115 to have parameters associated with measurement gap sharing. For example, this parameter may indicate the number of scheduled measurement gaps available for performing measurements on signals transmitted from neighboring network entity 105. In some examples, this parameter may be a fraction or percentage of scheduled measurement gaps. UE 115 may apply this parameter by suppressing one or more measurement gaps and may receive data (e.g., XR traffic) from network entity 105 using one or more time resources (e.g., time slots, symbols) associated with the suppressed measurement gaps. UE 115 may continue to perform measurements during measurement gaps that are not dropped.
[0089] In some examples, network entity 105 may configure the parameter based on scheduled XR services, one or more criteria associated with UE 115 (e.g., signal measurement, UE mobility state) meeting a threshold, or any combination thereof. Similarly, UE 115 may determine to activate or deactivate the application of the parameter based on scheduled XR services, one or more criteria associated with UE meeting a threshold, or any combination thereof. In some examples, UE 115 may determine to deactivate (e.g., stop application) the parameter based on a timer, event triggering, or both. In some examples, network entity 105 may dynamically adjust the parameter based on changes in scheduled XR services, one or more criteria associated with UE 115, the presence of buffered data at UE 115, or any combination thereof. Additionally or alternatively, UE 115 or network entity 105 may determine one or more parameters associated with cell detection, synchronization block index identification, or measurement based on the value of a scaling factor associated with the parameter.
[0090] Figure 2An example of a wireless communication system 200 supporting measurement gap sharing for latency-critical services according to one or more aspects of this disclosure is shown. The wireless communication system 200 may include a UE 115-a, a network entity 105-a, and a neighboring network entity 105-b. The UE 115-a may communicate with network entity 105-a, neighboring network entity 105-b, or both. Network entity 105-a may be associated with serving cell 205-a, and neighboring network entity 105-b may be associated with neighboring cell 205-b. The UE 115-a may communicate with network entity 105-a via communication links 210-a and 210-b. Similarly, the UE 115-a may receive signaling 215 from a neighboring network entity via a communication link. Communication links 210-a and 210-b may be examples of cellular links (e.g., Uu links).
[0091] In some examples, UE 115-a may be located within serving cell 205-a and may communicate with network entity 105-a according to configuration 220 sent by network entity 105-a. For example, the UE may operate in discontinuous reception (DRX) mode, and network entity 105-a and UE 115-a may transmit one or more data messages 225 according to configuration 220 and DRX mode (e.g., periodically). In some cases, due to the movement of the UE within serving cell 205-a, UE 115-a may trigger a mobility event (e.g., a 5G New Radio (NR) A3 event). In such cases, UE 115-a may perform measurement 230 (e.g., inter-frequency measurement, intra-frequency measurement) on signaling 215 sent by neighboring network entity 105-b. Based on the triggered mobility event, network entity 105-a may configure UE 115-a to perform measurement 230 on candidate neighboring cells including neighboring cell 205-b.
[0092] In some examples, neighboring cell s05-b may use the same frequency as serving cell 205-a. In other examples, neighboring cell 205-b may use a different frequency than serving cell 205-a. In such examples, the UE may tune away from the frequency used by serving cell 205-a and to the frequency used by neighboring cell 205-b. UE 115-a may be configured with one or more measurement gaps (e.g., timings) for performing measurement 230 on signaling 215 sent by neighboring cell 205-b. UE 115-a may not send or receive signaling (e.g., data) with network entity 105-a during measurement gaps. Therefore, measurement gaps may delay data transmission between UE 115-a and network entity 105-a.
[0093] In some examples, network entity 105-a may send configuration 220 to UE 115-a. In such examples, network entity 105-a may configure UE 115-a with shared parameters that define the number of scheduled measurement gaps used to perform measurements. For example, the shared parameters may indicate a fraction of the scheduled measurement gaps available for performing measurement 230 on neighboring cell 205-b. The number of scheduled measurement gaps may be a fractional or percentage value. In some examples, network entity 105-a may use one or more bits to indicate the number of scheduled measurement gaps. For example, network entity 105-a may use a two-bit signaling scheme to indicate a percentage value corresponding to the number of scheduled measurement gaps to be prioritized over the data communicated with network entity 105-a. Table 1 illustrates example bit configurations corresponding to percentages of measurement gaps. Table 1
[0094] In the example in Table 1, measGapDataSharingScheme A bit value “00” indicates that all scheduled measurement gaps should be used to perform measurement 230 (e.g., according to a legacy procedure). A bit value “01” indicates that at least (or approximately) 75% of the scheduled measurement gaps should be used to perform measurement 230, a bit value “10” indicates that at least (or approximately) 50% of the scheduled measurement gaps should be used to perform measurement 230, and a bit value “11” indicates that at least (or approximately) 25% of the scheduled measurement gaps should be used to perform measurement 230. The remaining scheduled measurement gaps indicated as not to be used to perform measurement 230 are suppressed (e.g., discarded, canceled). In some examples, the time slots and symbols corresponding to the suppressed measurement gaps can be used to send and receive one or more data messages 225, which may contain delay-critical data (e.g., extended reality (XR) data, URLLC data).
[0095] Network entity 105-a may configure the UE with shared parameters based on one or more factors, including scheduled data types, one or more criteria associated with the UE satisfying configured thresholds, the amount of buffered data, the UE's ability to support shared parameters, or any combination thereof. For example, network entity 105-a may configure shared parameters based on whether delayed critical services (e.g., XR services, URLLC services) are scheduled between UE 115-a and network entity 105-a. Additionally or alternatively, network entity 105-a may configure shared parameters based on one or more criteria associated with the UE satisfying configured thresholds. UE 115-a may similarly activate the application of configuration 220 (e.g., the application of the shared parameters) based on one or more factors. Network entity 105-a may dynamically, semi-statically, or statically indicate configuration 220 to the UE. For example, network entity 105-a may instruct UE115-a on configuration via downlink control information (DCI), media access control-control element (MAC-CE), radio resource control (RRC) signaling, one or more system information (SI) messages, or any combination thereof.
[0096] In some examples, the criteria associated with the UE may include one or more reported or measured UE signal measurements (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ)) performed on serving cell 205-a, and network entity 105-a may configure shared parameters based on the UE-associated criteria meeting configured thresholds (or UE 115-a may activate the application of configuration 220). In such examples, the configured threshold may be lower than the threshold associated with triggering an initial mobility event (e.g., the initial mobility event triggers the initial configuration or enabling of a measurement gap). In some other examples, UE 115-a may meet one or more radio resource management relaxation conditions (e.g., UE 115-a is stationary, UE 115-a is low-mobility, UE 115-a is not at the edge of serving cell 205-a, or any combination thereof), and may report the results to network entity 105-a. In such examples, if UE 115-a meets more than one radio resource management relaxation condition, the value of the shared parameter may be larger. Similarly, if the UE reports that at least one of the radio resource management (RFM) relaxation conditions is not met, the shared parameter may indicate that measurement gap suppression should be stopped. In some other examples, the UE 115-a may suppress measurement gaps when the amount of buffered data in one or more predetermined logical channels (e.g., high-priority logical channels) meets a threshold. For example, when the amount of buffered data in a high-priority logical channel exceeds the threshold, the UE 115-a may apply configuration 220 and suppress the measurement gap. Similarly, when the amount of buffered data in a high-priority logical channel is below the threshold, the UE 115-a may stop applying configuration 220 and avoid suppressing the measurement gap.
[0097] In some examples, network entity 105-a may dynamically adjust (e.g., reconfigure) the shared parameters included in configuration 220 based on changes in any of one or more factors. For example, network entity 105-a may adjust the sharing factor based on changes in the amount of buffered data, changes in the mobility state at UE 115-a, or any combination thereof. Network entity 105-a may indicate whether to activate or deactivate the application of shared parameters to UE 115-a via DCI, Media Access Control (MAC) signaling, or both.
[0098] UE 115-a may apply shared parameters based on a timer for a duration (e.g., application time). In some examples, UE 115-a may define a timer associated with data transmitted to network entity 105-a scheduled by a specific DCI format. In some examples, UE 115-a may deactivate the application of shared parameters when the timer expires. In such examples, UE 115-a may reapply shared parameters based on a new timer, on the basis of receiving an indication from network entity 105-a, one or more criteria associated with the UE meeting a threshold, or any combination thereof. For example, UE 115-a may reapply shared parameters based on a new timer for the same duration or a new timer for a new duration, on the basis of failing to receive data from network entity 105-a during a timer period, failing to receive a threshold number of transmissions from network entity 105-a during a DRX cycle, or both. Additionally or alternatively, UE may deactivate (e.g., release) the application of shared parameters based on an event trigger. In some examples, event triggering may include radio link failure (RLF) events, beam failure detection (BFD) events, candidate beam detection (CBD) events, RSRP meeting a threshold, RSRQ meeting a threshold, or any combination thereof.
[0099] Upon receiving configuration 220, UE 115-a, network entity 105-a, or both may discard a certain number of scheduled measurement gaps corresponding to the shared parameters indicated in configuration 220. Accordingly, UE 115-a and network entity 105-a may use the time resources (e.g., time slots, symbols) associated with the discarded measurement gaps to transmit one or more data messages 225. UE 115-a may still use the scheduled measurement gaps to perform measurements 230 on signaling 215 sent by the neighboring network entity 105-b. Based on the timing of discarding one or more of the corresponding measurement gaps, UE 115-a and network entity 105-a may experience delays in synchronization signal (e.g., primary synchronization signal (PSS), secondary synchronization signal (SSS)) detection, synchronization signal block (SSB) index identification, measurement, or any combination thereof. In some examples, this can be achieved by defining a scaling factor. To quantify the delay. Can be equal to Multiply the reciprocal of 100, where This represents the number (e.g., percentage) of scheduled measurement gaps indicated by shared parameters. In such an example, the scaling factor can be represented by Equation 1.
[0100] In some examples where UE 115-a does not receive configuration 220 or does not receive the shared parameters included in configuration 220, the scaling factor value may be equal to 1. In some other examples, the shared parameters may indicate that all measurement gaps should be used to perform measurement 230 (e.g., measurement gaps should not be canceled). In such other examples, the scaling factor value may be equal to 1.
[0101] In some examples of scheduling delay-critical services between network entity 105-a and UE 115-a, the number of SSB samples required to perform cell search, measurement, or both using measurement gaps can be scaled by a scaling factor. In such examples, network entity 105-a may dynamically reconfigure shared parameters during cell detection periods, SSB index identification periods, measurement periods, or any combination thereof. Therefore, network entity 105-a may change the scaling factor used during cell detection periods, SSB index identification periods, measurement periods, or any combination thereof, which may result in uncertainty at UE 115-a regarding UE 115-a's requirements (e.g., parameters) for performing the corresponding cell detection, SSB index identification, measurement, or any combination thereof. Therefore, network entity 105-a, UE 115-a, or both may determine updated values for one or more requirements of UE 115-a to account for the changed scaling factor.
[0102] In some examples, the updated value may be determined based on the minimum cell detection period, SSB index identification period, measurement period, or any combination thereof corresponding to the scaling factor before and after the reconfiguration of the shared parameters of network entity 105-a. In other examples, the updated value may be determined based on the maximum cell detection period, SSB index identification period, measurement period, or any combination thereof corresponding to the scaling factor before and after the reconfiguration of the shared parameters of network entity 105-a. In still other examples, the updated value may be determined based on a linear combination of delays corresponding to the scaling factors before and after the reconfiguration of the shared parameters of network entity 105-a, wherein each delay is scaled by the number of samples measured before and after the reconfiguration of the shared parameters of network entity 105-a.
[0103] In some examples, UE 115-a may be configured with additional parameters (e.g., configured by network entity 105-a) that indicate the number (e.g., a percentage value, a fractional value) of scheduled measurement gaps that should be used to perform intra-frequency measurements. For example, the additional parameters may indicate that scheduled measurement gaps should be equally split between intra-frequency and inter-frequency measurements. In such examples, UE 115-a may apply the additional parameters after applying shared parameters. For example, UE 115-a may determine, based on configuration 220, that at least (or approximately) 50% of the scheduled measurement gaps are available to perform measurement 230. UE 115-a may also determine, based on the additional parameters, that the remaining measurement gaps should be equally split between intra-frequency and inter-frequency measurements.
[0104] In some other examples, UE 115-a may not be configured with additional parameters. In such other examples, the shared parameters indicated in configuration 220 may also indicate the sharing (e.g., splitting) of measurement gaps between in-frequency and inter-frequency measurements. For example, network entity 105-a may use a four-bit signaling scheme to indicate the shared parameters, where the two most significant bits of the shared parameters indicate the number of scheduled measurement gaps for performing measurement 230, and the two least significant bits of the shared parameters indicate the sharing of remaining measurement gaps between in-frequency and inter-frequency measurements.
[0105] Figure 3 An example of a communication timeline 300 shared for measurement gaps supporting and delay-critical services according to one or more aspects of this disclosure is shown. The communication timeline 300 may exemplify one or more aspects for implementing a wireless communication system 100. For example, the communication timeline 300 may depict or represent a communication (e.g., signal, message) flow between a UE and a network entity, which may be as described herein (including regarding...). Figure 1 Examples of the corresponding devices described herein. In some examples, the horizontal axis 305-a of the communication timeline 300 may represent the time component of communication between the UE and a network entity, and the horizontal axis 305-c may represent the time component of measurements performed by the UE. In some examples, the UE may operate according to a DRX configuration (e.g., a DRX mode), and the horizontal axis 305-b may represent the time component of a DRX cycle associated with the UE.
[0106] In some examples, the UE may communicate data to a network entity in the form of bursty service 310. Burst service 310 may be associated with periodicity 315 (e.g., a non-integer-based duration of 16.67 ms). The UE may receive data from the network entity according to a DRX pattern. For example, the UE may receive data from the network entity according to a DRX cycle that may include multiple DRX on-durations 320 (e.g., a first DRX on-duration 320-a, a second DRX on-duration 320-b, a third DRX on-duration 320-c, and a fourth DRX on-duration 320-d). The UE may receive bursty service 310 in time during the corresponding DRX on-duration 320. DRX on-durations 320 may be temporally separated (e.g., they may be periodic, semi-periodic, or aperiodic). In some examples, the duration 325 between DRX on-durations 320 may not be uniform. For example, the value of duration 325-a can be the same as the value of duration 325-b (e.g., a duration of 17 ms), but can be different from the value of duration 325-c (e.g., a duration of 16 ms). Duration 325 can be different from periodicity 315.
[0107] The UE may also be configured with one or more measurement gaps 330, including a first measurement gap 330-a, a second measurement gap 330-b, a third measurement gap 330-c, and a fourth measurement gap 330-d. The UE may be configured to perform measurements during one or more measurement gaps 330. In some examples, as part of a mobility event, the UE may perform measurements on signals transmitted from adjacent network entities (e.g., network entities different from those with which the UE is communicating data). Measurement gaps 330 may be associated with integer-based periodicity 335 (e.g., a duration of 20 ms). In some examples, measurement gaps 330 may temporally overlap with a DRX on duration 320 (e.g., partially or completely).
[0108] In some cases, the UE may not receive burst traffic 310 during some or all of the corresponding DRX on-duration duration 320. For example, the UE may be performing a measurement during a portion 340-a of the first DRX on-duration duration 320-a, which corresponds to the time overlap between the first DRX on-duration duration 320-a and the first measurement gap 330-a, and the UE may not be able to receive burst traffic 310 without interrupting the measurement. In such cases, the UE may not receive burst traffic 310 during a portion 340-a of the first DRX on-duration duration 320-a. In some examples, the UE may determine to continue performing the measurement during portion 340-a based on a configuration received from a network entity, which may be as follows: Figure 2An example of the described configuration 220. Similarly, the UE may determine to stop receiving burst traffic 310 during portion 340-b of the fourth DRX on-duration 320-d, which corresponds to the time overlap between the fourth DRX on-duration 320-d and the fourth measurement gap 330-d. In some cases where the DRX on-duration 320 ends during the measurement gap 330 (e.g., the DRX timer expires), the UE may deactivate and postpone the transmission of any remaining data packets of burst traffic 310 until the subsequent DRX on-duration 320 begins.
[0109] This configuration can indicate to the UE the number of measurement gaps 330 to be used for performing measurements. For example, the configuration can (e.g., explicitly) indicate that at least (or approximately) 50% of the measurement gaps 330 should be used to perform measurements, and can (e.g., implicitly) indicate that other (e.g., remaining) measurement gaps 330 can be suppressed (e.g., discarded, canceled). In some examples where the UE is configured with four measurement gaps 330, the UE can determine to perform measurements during two measurement gaps 330 (e.g., the first measurement gap 330-a and the fourth measurement gap 330-d), and can determine to discard the remaining two measurement gaps 330 (e.g., the second measurement gap 330-b and the third measurement gap 330-c).
[0110] In some other cases, the UE may receive burst traffic 310 during all corresponding DRX on-duration durations 320. For example, the UE may apply this configuration and suppress the second measurement gap 330-b and the third measurement gap 330-c. In such other cases, the UE may not be occupied by the measurement and may accordingly receive burst traffic 310 during the DRX on-duration duration 320 that overlaps in time with the discarded measurement gaps 330 (e.g., the second measurement gap 330-b and the third measurement gap 330-c).
[0111] In some examples, network entities may base their decisions on one or more factors (e.g., the type of data that has been scheduled, one or more criteria associated with the UE that meet a threshold, the amount of buffered data, or any combination thereof, such as regarding...). Figure 2 The network entity (as described herein) determines whether to activate or deactivate the application of the configuration and can thus indicate to the UE whether to activate or deactivate the application of the configuration. Additionally or alternatively, the network entity may dynamically adjust the configuration and can indicate to the UE whether to activate or deactivate the application of the updated configuration. In some other examples, the UE may determine whether to activate the application of the configuration based on one or more factors. Additionally or alternatively, the UE may be configured with a timer, event trigger, or both associated with the application configuration (the timer, event trigger, or both can be specified herein (including references)). Figure 2(Examples of the corresponding features described), and the UE can determine whether to activate or deactivate the application of this configuration based on the expiration of the timer, the event triggering a threshold, or both.
[0112] Figure 4 An example of a process flow 400 for sharing measurement gaps to support and delay critical operations, according to one or more aspects of this disclosure, is shown. Process flow 400 can be implemented as described in the reference. Figure 1 , Figure 2 and Figure 3 The described aspects of the wireless communication system 100, wireless communication system 200, and communication timeline 300, or those implemented therein, are relevant. For example, in... Figure 4 In the example, UE115-b can communicate with network entity 105-c, which can be the network entity referenced in this document. Figure 1 or Figure 2 Examples of the described devices. In the following description of process flow 400, the operations between UE 115-b and network entity 105-c may be performed in a different order than shown in the example, or the operations between UE 115-b and network entity 105-c may be performed in a different order at different times. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400.
[0113] At 405, UE 115-b can send capability information to network entity 105-c. The capability information indicates that UE 115-b supports the ability to apply parameters that indicate metrics used to share multiple configured measurement timings between performing measurements and transmitting data.
[0114] At 410, UE 115-b may receive from network entity 105-c an indication of configuration for multiple measurement timings. This configuration may include the periodicity of the multiple measurement timings and parameters indicating metrics for sharing the multiple measurement timings between measurement and data communication. Network entity 105-c may configure UE 115-b with parameters based on capability information received from UE 115-b. In some examples, the metric may be a percentage value of the multiple measurement timings, a fraction of the multiple measurement timings, or any combination thereof. The parameter may include a second metric for sharing a first subset of the multiple measurement timings between intra-frequency and inter-frequency measurements. In some examples, UE 115-b may receive the indication via DCI, MAC-CE, RRC signaling, SI messages, or any combination thereof.
[0115] At 415, UE 115-b may send an indication to network entity 105-c that UE 115-b is applying a parameter based on one or more criteria associated with the UE satisfying a threshold. In some examples, this parameter may indicate a scaling factor associated with one or more delays, including delays in synchronization signal (e.g., PSS, SSS) detection, SSB index identification, measurement, or any combination thereof.
[0116] At 420, UE 115-b, network entity 105-c, or both UE 115-b and network entity 105-c can determine the cell detection period, SSB index identification period, measurement period, or any combination thereof based on a scaling factor associated with the parameter.
[0117] At 425, UE 115-b may apply the configuration to multiple measurement times based at least in part on the data type, one or more criteria associated with UE 115-b satisfying a threshold, or any combination thereof. In some examples, the data type may include XR traffic, URLLC traffic, or any combination thereof. The one or more criteria may include one or more signal measurements performed by UE 115-b on the serving cell associated with network entity 105-c, radio resource management relaxation conditions, the amount of data buffered in the logical channel, or any combination thereof. The one or more signal measurements performed by UE 115-b on the serving cell associated with network entity 105-c may include RSRP, RSRQ, or both. Additionally or alternatively, UE 115-b may apply the configuration to multiple measurement times over a duration following data communication based on a timer associated with data transmission by network entity 105-c.
[0118] At 430, UE 115-b can perform measurements during a first subset of multiple measurement opportunities. In some examples, UE 115-b can perform intra-frequency measurements, inter-frequency measurements, or any combination thereof. UE 115-b can perform measurements based on its configuration. For example, UE 115-b can determine a first subset and a second subset of multiple measurement opportunities based on parameters included in its configuration.
[0119] At 435, UE 115-b may transmit one or more data messages during one or more time periods that at least partially overlap with a second subset of multiple measurement timings. In some examples, at least one measurement is suppressed during the second subset of multiple measurement timings, and UE 115-b may use a time slot, symbol, or both time slot and symbol associated with the at least one suppressed measurement to transmit one or more data messages. UE 115-b may determine a first number of measurement timings in the first subset of multiple measurement timings and a second number of measurement timings in the second subset of multiple measurement timings based on parameters included in the configuration.
[0120] At 440, UE 115-b can pause the application of configuration to multiple measurement events based on event triggering. In some examples, event triggering may include an RLF event, a BFR procedure, a CBD procedure, RSRP meeting a first threshold, RSRQ meeting a second threshold, or any combination thereof. In other examples, UE 115-b can pause the application of configuration to multiple measurement events based on timer expiration.
[0121] Figure 5 A block diagram 500 of a device 505 for sharing measurement gaps supporting and delay-critical services according to one or more aspects of this disclosure is shown. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).
[0122] Receiver 510 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels shared with measurement gaps related to delay-critical services). Information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.
[0123] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels shared with measurement gaps related to delay-critical services). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.
[0124] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of measurement gaps shared with delay-critical operations as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.
[0125] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), graphics processing unit (GPU), neural processing unit (NPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).
[0126] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, GPU, NPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).
[0127] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.
[0128] According to the examples disclosed herein, the communication manager 520 may support wireless communication. For example, the communication manager 520 may be capable of, configured to, or operable to support components for receiving instructions on a configuration for a set of multiple measurement moments, the configuration including the periodicity of the set of multiple measurement moments and parameters indicating the sharing of metrics of the set of multiple measurement moments between the performance of measurements and data communication. The communication manager 520 may be capable of, configured to, or operable to support components for performing measurements during a first subset of the set of multiple measurement moments. The communication manager 520 may be capable of, configured to, or operable to support components for transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement moments, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement moments, and wherein a first number of measurement moments in the first subset of the set of multiple measurement moments and a second number of measurement moments in the second subset of the set of multiple measurement moments are determined based on parameters.
[0129] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., at least one processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can support techniques for reducing power consumption and improving the utilization of communication resources.
[0130] Figure 6 A block diagram 600 of a device 605 supporting measurement gap sharing for latency-critical services according to one or more aspects of this disclosure is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).
[0131] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with measurement gaps related to delay-critical services). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.
[0132] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with measurement gaps related to delay-critical services). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.
[0133] Device 605 or its various components may be examples of parts used to perform various aspects of measurement gaps shared with delay-critical operations as described herein. For example, communication manager 620 may include configuration component 625, measurement component 630, message sending and receiving component 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.
[0134] According to the examples disclosed herein, the communication manager 620 may support wireless communication. The configuration component 625 is capable of, configured to, or operable to support components for receiving instructions for a configuration of a set of multiple measurement moments, the configuration including the periodicity of the set of multiple measurement moments and parameters indicating the sharing of the measurements of the set of multiple measurement moments between the performance of measurements and data communication. The measurement component 630 is capable of, configured to, or operable to support components for performing measurements during a first subset of the set of multiple measurement moments. The message sending and receiving component 635 is capable of, configured to, or operable to support components for transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement moments, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement moments, and wherein a first number of measurement moments in the first subset of the set of multiple measurement moments and a second number of measurement moments in the second subset of the set of multiple measurement moments are determined based on the parameters.
[0135] Figure 7A block diagram 700 of a communication manager 720 supporting measurement gap sharing for latency-critical services according to one or more aspects of this disclosure is shown. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of measurement gap sharing for latency-critical services as described herein. For example, the communication manager 720 may include a configuration component 725, a measurement component 730, a message sending and receiving component 735, an application component 740, a triggering component 745, a scaling component 750, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).
[0136] According to the examples disclosed herein, the communication manager 720 may support wireless communication. The configuration component 725 is capable of, configured to, or operable to support components for receiving instructions for a configuration of a set of multiple measurement moments, the configuration including the periodicity of the set of multiple measurement moments and parameters indicating the sharing of metrics of the set of multiple measurement moments between the performance of measurements and data communication. The measurement component 730 is capable of, configured to, or operable to support components for performing measurements during a first subset of the set of multiple measurement moments. The message sending and receiving component 735 is capable of, configured to, or operable to support components for transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement moments, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement moments, and wherein a first number of measurement moments in the first subset of the set of multiple measurement moments and a second number of measurement moments in the second subset of the set of multiple measurement moments are determined based on the parameters.
[0137] In some examples, the metric is a percentage value of the set across multiple measurement points, a score of the set across multiple measurement points, or any combination thereof.
[0138] In some examples, the parameter also includes a second metric for the first subset of the set used to share multiple measurement opportunities between intra-frequency measurements and inter-frequency measurements.
[0139] In some examples, application component 740 is capable of, configured to, or able to operate to support components for applying the configuration to the set of multiple measurement times based on data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
[0140] In some examples, this data type is Extended Reality (XR) services, Ultra-Reliable and Low-Latency Communication (URLLC) services, or a combination thereof.
[0141] In some examples, the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in the logical channel, or any combination thereof.
[0142] In some examples, the one or more signal measurements performed by the UE on the serving cell associated with the network entity include reference signal received power, reference signal received quality, or both.
[0143] In some examples, application component 740 is capable of, configured to, or able to operate to support components for: configuring the set of multiple measurement opportunities for a duration following data communication based on and associated with timers for data transmission to network entities.
[0144] In some examples, trigger component 745 is capable of, can be configured to, or can operate to support components for pausing the application of this configuration to a set of multiple measurement times based on event triggering.
[0145] In some examples, the event triggering includes radio link failure, beam failure recovery, candidate beam detection, reference signal received power meeting a first threshold, reference signal received quality meeting a second threshold, or any combination thereof.
[0146] In some examples, scaling component 750 is capable of, configured to, or able to operate to support components for determining cell detection periods, synchronization signal block index identification periods, measurement periods, or any combination thereof based on a scaling factor associated with the parameter.
[0147] In some examples, the indication is received via downlink control information, media access control-control elements, radio resource control signaling, system information messages, or any combination thereof.
[0148] In some examples, the measurement component 730 is capable of, can be configured to, or is operable to support components for performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0149] Figure 8A diagram of a system 800 including device 805 supporting measurement gap sharing with latency-critical services, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).
[0150] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.
[0151] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links, as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.
[0152] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0153] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, NPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks shared with measurement gaps for latency-critical operations). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.
[0154] According to the examples disclosed herein, the communication manager 820 may support wireless communication. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving instructions on a configuration for a set of multiple measurement moments, the configuration including the periodicity of the set of multiple measurement moments and parameters indicating the sharing of metrics of the set of multiple measurement moments between the performance of measurements and data communication. The communication manager 820 may be capable of, configured to, or operable to support components for performing measurements during a first subset of the set of multiple measurement moments. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement moments, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement moments, and wherein a first number of measurement moments in the first subset of the set of multiple measurement moments and a second number of measurement moments in the second subset of the set of multiple measurement moments are determined based on the parameters.
[0155] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for reducing latency and improving user experience associated with reduced power consumption and improving the utilization of communication resources.
[0156] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects as described herein for measurement gaps shared with delay-critical services, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.
[0157] Figure 9A block diagram 900 of a device 905 for sharing measurement gaps supporting and delay-critical operations according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).
[0158] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
[0159] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.
[0160] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of measurement gaps shared with delay-critical operations as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.
[0161] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, GPU, NPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).
[0162] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, GPU, NPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).
[0163] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.
[0164] According to the examples disclosed herein, the communication manager 920 may support wireless communication. For example, the communication manager 920 may be capable of, configured to, or operable to support components for sending instructions to the UE regarding a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of the measurement of the set of multiple measurement times between performing measurement and data communications. The communication manager 920 may be capable of, configured to, or operable to support components for communicating one or more data messages with the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0165] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., at least one processor that controls or otherwise couples to receiver 910, transmitter 915, communication manager 920, or a combination thereof) can support techniques for reducing power consumption and improving the utilization of communication resources.
[0166] Figure 10 A block diagram 1000 of a device 1005 for sharing measurement gaps supporting and delay-critical operations according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).
[0167] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
[0168] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.
[0169] Device 1005 or its various components may be examples of parts used to perform various aspects of measurement gaps shared with delay-critical operations as described herein. For example, communication manager 1020 may include configuration manager 1025, message sending and receiving manager 1030, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.
[0170] According to the examples disclosed herein, the communication manager 1020 may support wireless communication. The configuration manager 1025 is capable of, configured to, or operable to support components for sending instructions to the UE regarding a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of the metrics of the set of multiple measurement times between performing measurement and data communication. The message sending and receiving manager 1030 is capable of, configured to, or operable to support components for transmitting one or more data messages with the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0171] Figure 11A block diagram 1100 of a communication manager 1120 supporting measurement gap sharing for latency-critical services according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of components for performing various aspects of measurement gap sharing for latency-critical services as described herein. For example, the communication manager 1120 may include a configuration manager 1125, a message sending and receiving manager 1130, a measurement manager 1135, a scaling manager 1140, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.
[0172] According to the examples disclosed herein, the communication manager 1120 may support wireless communication. The configuration manager 1125 is capable of, configured to, or operable to support components for sending instructions to the UE regarding a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of the metrics of the set of multiple measurement times between performing measurement and data communication. The message sending and receiving manager 1130 is capable of, configured to, or operable to support components for transmitting one or more data messages with the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0173] In some examples, the configuration is based on the data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
[0174] In some examples, this data type is Extended Reality (XR) services, Ultra-Reliable and Low-Latency Communication (URLLC) services, or a combination thereof.
[0175] In some examples, the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in the logical channel, or any combination thereof.
[0176] In some examples, the one or more signal measurements performed by the UE on the serving cell associated with the network entity include reference signal received power, reference signal received quality, or both.
[0177] In some examples, the metric is a percentage value of the set across multiple measurement points, a score of the set across multiple measurement points, or any combination thereof.
[0178] In some examples, the measurement manager 1135 is capable of, configured to, or able to operate to support components for performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0179] In some examples, the parameter also includes a second metric for a second subset of the set used to share multiple measurement opportunities between intra-frequency and inter-frequency measurements.
[0180] In some examples, the scaling manager 1140 is capable of, configured to, or able to operate to support components for determining cell detection periods, synchronization signal block index identification periods, measurement periods, or any combination thereof based on a scaling factor associated with that parameter.
[0181] In some examples, the instruction is sent via downlink control information, media access control-control elements, radio resource control signaling, system information messages, or any combination thereof.
[0182] Figure 12 A diagram of a system 1200 including device 1205 supporting measurement gap sharing for latency-critical services, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or a component including device 905, device 1005, or network entity 105. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and enabling communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).
[0183] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to be coupled to said one or more processors or one or more memory components, said one or more processors or memory components being operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).
[0184] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1225 may also include a BIOS that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).
[0185] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, GPUs, NPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks shared with measurement gaps for latency-critical operations). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1230) host functions for performing the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operated to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.
[0186] In some examples, bus 1240 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1240 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one component of different components or partitioned between different components).
[0187] In some examples, the communication manager 1220 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 can manage the transfer of data communication between client devices (such as one or more UEs 115). In some examples, the communication manager 1220 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1220 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.
[0188] According to the examples disclosed herein, the communication manager 1220 may support wireless communication. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for sending instructions to the UE regarding a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics for the set of multiple measurement times between performing measurement and data communications. The communication manager 1220 may be capable of, configured to, or operable to support components for communicating one or more data messages with the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement times.
[0189] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for reducing latency and improving user experience associated with reduced power consumption and improving the utilization of communication resources.
[0190] In some examples, the communication manager 1220 may be configured to use or otherwise coordinate with the transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by the transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors of at least one processor 1235 to cause device 1205 to perform various aspects shared with the measurement gaps of latency-critical operations as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.
[0191] Figure 13 A flowchart illustrating a method 1300 for sharing measurement gaps supporting and delay-critical services according to various aspects of this disclosure is shown. Operation of method 1300 may be implemented by a UE or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0192] At 1305, the method may include receiving an instruction for a configuration of a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between the performance of measurement and data communication. Operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 7 The configuration component 725 described is used to execute.
[0193] At 1310, the method may include performing measurements during a first subset of the set of multiple measurement times. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 7 The measurement component 730 described is used to perform this.
[0194] At 1315, the method may include communicating one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement opportunities, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement opportunities, and wherein a first number of measurement opportunities in the first subset of the set of multiple measurement opportunities and a second number of measurement opportunities in the second subset of the set of multiple measurement opportunities are determined at least partially based on the parameter. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 7 The message receiving and sending component 735 described is used to perform this.
[0195] Figure 14 A flowchart illustrating a method 1400 for sharing measurement gaps supporting and delay-critical services according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0196] At 1405, the method may include receiving an instruction for a configuration of a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between the performance of measurement and data communication. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 7 The configuration component 725 described is used to execute.
[0197] At 1410, the method may include performing measurements during a first subset of the set of multiple measurement times. The operation of box 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 7 The measurement component 730 described is used to perform this.
[0198] At 1415, the method may include applying the configuration to the set of multiple measurement moments, at least in part based on and associated with a timer for data transmission by the network entity, over a duration following data communication. Operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1415 may be provided by reference to [reference needed]. Figure 7 The application component 740 described is used to execute this.
[0199] At 1420, the method may include communicating one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement opportunities, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement opportunities, and wherein a first number of measurement opportunities in the first subset of the set of multiple measurement opportunities and a second number of measurement opportunities in the second subset of the set of multiple measurement opportunities are determined at least partially based on parameters. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be derived from references... Figure 7 The message receiving and sending component 735 described is used to perform this.
[0200] Figure 15 A flowchart illustrating a method 1500 for sharing measurement gaps supporting and delay-critical services according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0201] At 1505, the method may include receiving an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of metrics of the set of multiple measurement times between the performance of measurement and data communication. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 7 The configuration component 725 described is used to execute.
[0202] At 1510, the method may include applying the configuration to the plurality of measurement moments, at least in part based on and associated with a timer for data transmission by a network entity, for a duration following data communication. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to [reference needed]. Figure 7 The application component 740 described is used to execute this.
[0203] At 1515, the method may include performing measurements during a first subset of the set of multiple measurement times. The operation of box 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 7 The measurement component 730 described is used to perform this.
[0204] At 1520, the method may include communicating one or more data messages during one or more time periods that at least partially overlap with a second subset of the set of multiple measurement opportunities, wherein one or more measurements are suppressed during the second subset of the set of multiple measurement opportunities, and wherein a first number of measurement opportunities in the first subset of the set of multiple measurement opportunities and a second number of measurement opportunities in the second subset of the set of multiple measurement opportunities are determined at least partially based on the parameter. The operation of block 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 7 The message receiving and sending component 735 described is used to perform this.
[0205] At 1525, the method may include pausing the application of the configuration to the set of multiple measurement times, at least in part based on event triggering. The operation of box 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1525 may be provided by reference to [reference needed]. Figure 7 The described triggering component 745 is executed.
[0206] Figure 16 A flowchart illustrating a method 1600 for sharing measurement gaps supporting and delay-critical services according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.
[0207] At 1605, the method may include sending to the UE an indication of a configuration for a set of multiple measurement times, the configuration including the periodicity of the set of multiple measurement times and parameters indicating the sharing of the metrics of the set of multiple measurement times between performing measurement and data communication. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference]. Figure 11 The configuration manager 1125 described is used to execute this.
[0208] At 1610, the method may include communicating one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement opportunities. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to... Figure 11 The message sending and receiving manager 1130 described is used to execute this.
[0209] Figure 17 A flowchart illustrating a method 1700 for sharing measurement gaps supporting and delay-critical services according to various aspects of this disclosure is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.
[0210] At 1705, the method may include sending to the UE an indication of a configuration for a set of multiple measurement opportunities, the configuration including the periodicity of the set of multiple measurement opportunities and parameters indicating the sharing of metrics for the set of multiple measurement opportunities between performing measurement and data communication. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 11 The configuration manager 1125 described is used to execute this.
[0211] At 1710, the method may include communicating one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the set of multiple measurement opportunities. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be provided by reference to [reference needed]. Figure 11 The message sending and receiving manager 1130 described is used to execute this.
[0212] At 1715, the method may include performing intra-frequency measurements, inter-frequency measurements, or any combination thereof. The operation of block 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be derived from references... Figure 11 The measurement manager 1135 described is used to perform this.
[0213] The following provides an overview of the various aspects of this disclosure:
[0214] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving an indication of a configuration for a plurality of measurement timings, the configuration including periodicity of the plurality of measurement timings and parameters indicating metric sharing of the plurality of measurement timings between measurement execution and data communication; performing a measurement during a first subset of the plurality of measurement timings; and transmitting one or more data messages during one or more time periods that at least partially overlap with a second subset of the plurality of measurement timings, wherein one or more measurements are suppressed during the second subset of the plurality of measurement timings, and wherein a first number of measurement timings in the first subset of the plurality of measurement timings and a second number of measurement timings in the second subset of the plurality of measurement timings are determined at least partially based on the parameters.
[0215] Aspect 2: According to the method of aspect 1, wherein the metric is a percentage value of the plurality of measurement moments, a fraction of the plurality of measurement moments, or any combination thereof.
[0216] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the parameter further includes a second metric for sharing the first subset of measurement opportunities between intra-frequency measurements and inter-frequency measurements.
[0217] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: applying the configuration to the plurality of measurement times based at least in part on data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
[0218] Aspect 5: According to the method described in aspect 4, the data type is an XR service, a URLLC service, or a combination thereof.
[0219] Aspect 6: The method according to any one of Aspects 4 to 5, wherein the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in the logical channel, or any combination thereof.
[0220] Aspect 7: The method according to aspect 6, wherein the one or more signal measurements performed by the UE on the serving cell associated with the network entity include RSRP, RSRQ, or both.
[0221] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: applying the configuration to the plurality of measurement timings for a duration following data communication, based at least in part on a timer associated with and connected to the data transmitted by the network entity.
[0222] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: pausing the application of the configuration to the plurality of measurement occasions at least in part based on event triggering.
[0223] Aspect 10: The method according to aspect 9, wherein the event triggering includes RLF, beam fault recovery, candidate beam detection, RSRP satisfying a first threshold, RSRQ satisfying a second threshold, or any combination thereof.
[0224] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: determining a cell detection period, a synchronization signal block index identification period, a measurement period, or any combination thereof based at least in part on a scaling factor associated with the parameter.
[0225] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: sending an indication that the UE is applying the parameter based at least in part on one or more criteria associated with the UE satisfying a threshold.
[0226] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the indication is received via downlink control information, media access control-control element, radio resource control signaling, system information message or any combination thereof.
[0227] Aspect 14: The method according to any one of aspects 1 to 13, the method further comprising performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0228] Aspect 15: A method for wireless communication by a network entity, the method comprising: sending to a UE an indication of a configuration for a plurality of measurement timings, the configuration including periodicity of the plurality of measurement timings and parameters indicating a metric for sharing the plurality of measurement timings between performing measurement and data communication; and communicating one or more data messages to the UE during one or more time periods that at least partially overlap with a subset of the plurality of measurement timings.
[0229] Aspect 16: The method according to aspect 15, wherein the configuration is based at least in part on a data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
[0230] Aspect 17: The method according to aspect 16, wherein the data type is extended reality (XR) service, ultra-reliable and low-latency communication (URLLC) service, or a combination thereof.
[0231] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in the logical channel, or any combination thereof.
[0232] Aspect 19: According to the method of aspect 18, the one or more signal measurements performed by the UE on the serving cell associated with the network entity include reference signal received power, reference signal received quality, or both.
[0233] Aspect 20: The method according to any one of Aspects 15 to 19, wherein the metric is a percentage value of the plurality of measurement moments, a fraction of the plurality of measurement moments, or any combination thereof.
[0234] Aspect 21: The method according to any one of aspects 15 to 20, the method further comprising performing intra-frequency measurements, inter-frequency measurements, or any combination thereof.
[0235] Aspect 22: According to the method of aspect 21, wherein the parameter further includes a second metric for sharing a second subset of the plurality of measurement opportunities between intra-frequency measurements and inter-frequency measurements.
[0236] Aspect 23: The method according to any one of Aspects 15 to 22, the method further comprising: determining a cell detection period, a synchronization signal block index identification period, a measurement period, or any combination thereof based at least in part on a scaling factor associated with the parameter.
[0237] Aspect 24: The method according to any one of aspects 15 to 23, the method further comprising: receiving an indication that the UE is applying the parameter based at least in part on one or more criteria associated with the UE satisfying a threshold.
[0238] Aspect 25: The method according to any one of Aspects 15 to 24, wherein the indication is transmitted via downlink control information, media access control-control element, radio resource control signaling, system information message or any combination thereof.
[0239] Aspect 26: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the UE to perform a method according to any one of Aspects 1 to 14.
[0240] Aspect 27: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 1 to 14.
[0241] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the method according to any one of aspects 1 to 14.
[0242] Aspect 29: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the network entity to perform a method according to any one of Aspects 15 to 25.
[0243] Aspect 30: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 15 to 25.
[0244] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the method according to any one of aspects 15 to 25.
[0245] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.
[0246] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDM, and other systems and radio technologies not explicitly mentioned herein, including future systems and radio technologies.
[0247] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0248] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, NPU, FPGA, or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.
[0249] The functionality described herein can be implemented using hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, firmware, hardwired, or any combination thereof. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.
[0250] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase-change memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.
[0251] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., including enumerations of items ending with phrases such as "at least one of..." or "one or more of...") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means, for example, A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as containing components A, B and / or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.
[0252] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".
[0253] The terms "determine" or "identify" encompass a variety of actions, and therefore, "determine" or "identify" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), ascertainment, etc. Additionally, "determine" or "identify" can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determination, receiving information or signaling for identification), accessing (such as accessing data in memory or accessing information), etc. Furthermore, "determine" or "identify" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.
[0254] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.
[0255] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.
[0256] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive instructions for a configuration for multiple measurement timings, the configuration including the periodicity of the multiple measurement timings and parameters indicating the sharing of metrics of the multiple measurement timings between measurement execution and data communication; Measurements are performed during a first subset of the plurality of measurement opportunities; and One or more data messages are communicated during one or more time periods that at least partially overlap with a second subset of the plurality of measurement times, wherein one or more measurements are suppressed during the second subset of the plurality of measurement times, and wherein a first number of measurement times in the first subset of the plurality of measurement times and a second number of measurement times in the second subset of the plurality of measurement times are determined at least partially based on the parameters.
2. The UE of claim 1, wherein the metric is a percentage value of the plurality of measurement times, a fraction of the plurality of measurement times, or any combination thereof.
3. The UE of claim 1, wherein the parameters further include a second metric for sharing the first subset of the plurality of measurement opportunities between intra-frequency measurements and inter-frequency measurements.
4. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The configuration is applied to the plurality of measurement times based at least in part on the data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
5. The UE according to claim 4, wherein the data type is Extended Reality (XR) service, Ultra Reliable and Low Latency Communication (URLLC) service, or a combination thereof.
6. The UE of claim 4, wherein the one or more criteria include the following criteria: one or more signal measurements performed by the UE on the serving cell associated with a network entity, radio resource management relaxation conditions, the amount of data buffered in a logical channel, or any combination thereof.
7. The UE of claim 6, wherein the one or more signal measurements performed by the UE on the serving cell associated with the network entity include reference signal received power, reference signal received quality, or both.
8. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The configuration is applied to the plurality of measurement opportunities for a duration following data communication, based at least in part on a timer associated with the data transmission by the network entity.
9. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The application of the configuration to the multiple measurement times is paused, at least in part, based on event triggering.
10. The UE of claim 9, wherein the event triggering includes radio link failure, beam failure recovery, candidate beam detection, reference signal received power satisfying a first threshold, reference signal received quality satisfying a second threshold, or any combination thereof.
11. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The cell detection period, synchronization signal block index identification period, measurement period, or any combination thereof is determined at least in part based on a scaling factor associated with the parameter.
12. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The indication that the UE is applying the parameter is sent at least in part based on one or more criteria associated with the UE satisfying a threshold.
13. The UE of claim 1, wherein the indication is received via downlink control information, media access control-control element, radio resource control signaling, system information message or any combination thereof.
14. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Perform intra-frequency measurements, inter-frequency measurements, or any combination thereof.
15. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Send to user equipment (UE) an instruction for a configuration for multiple measurement timings, the configuration including the periodicity of the multiple measurement timings and parameters indicating the sharing of metrics of the multiple measurement timings between measurement and data communication; as well as One or more data messages are communicated to the UE during one or more time periods that at least partially overlap with a subset of the plurality of measurement times.
16. The network entity of claim 15, wherein the configuration is based at least in part on a data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.
17. The network entity of claim 16, wherein the data type is Extended Reality (XR) service, Ultra Reliable and Low Latency Communication (URLLC) service, or a combination thereof.
18. The network entity of claim 16, wherein the one or more criteria include one or more signal measurements performed by the UE on the serving cell associated with the network entity, radio resource management relaxation conditions, the amount of data buffered in a logical channel, or any combination thereof.
19. The network entity of claim 18, wherein the one or more signal measurements performed by the UE on the serving cell associated with the network entity include reference signal received power, reference signal received quality, or both.
20. The network entity of claim 15, wherein the metric is a percentage value of the plurality of measurement moments, a fraction of the plurality of measurement moments, or any combination thereof.
21. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Perform intra-frequency measurements, inter-frequency measurements, or any combination thereof.
22. The network entity of claim 21, wherein the parameters further include a second metric for sharing a second subset of the plurality of measurement opportunities between intra-frequency measurements and inter-frequency measurements.
23. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The cell detection period, synchronization signal block index identification period, measurement period, or any combination thereof is determined at least in part based on a scaling factor associated with the parameter.
24. The network entity of claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: The indication that the UE is applying the parameter is received, at least in part, based on one or more criteria associated with the UE satisfying a threshold.
25. The network entity of claim 15, wherein the indication is transmitted via downlink control information, media access control-control element, radio resource control signaling, system information message, or any combination thereof.
26. A method for wireless communication by a user equipment (UE), the method comprising: Receive instructions for a configuration for multiple measurement timings, the configuration including the periodicity of the multiple measurement timings and parameters indicating the sharing of metrics of the multiple measurement timings between measurement execution and data communication; Measurements are performed during a first subset of the plurality of measurement opportunities; and One or more data messages are communicated during one or more time periods that at least partially overlap with a second subset of the plurality of measurement times, wherein one or more measurements are suppressed during the second subset of the plurality of measurement times, and wherein a first number of measurement times in the first subset of the plurality of measurement times and a second number of measurement times in the second subset of the plurality of measurement times are determined at least partially based on the parameters.
27. The method according to claim 26, further comprising: The configuration is applied to the plurality of measurement opportunities for a duration following data communication, based at least in part on a timer associated with the data transmission by the network entity.
28. The method according to claim 26, further comprising: The application of the configuration to the multiple measurement times is paused, at least in part, based on event triggering.
29. A method for wireless communication by a network entity, the method comprising: Send to user equipment (UE) an instruction for a configuration for multiple measurement timings, the configuration including the periodicity of the multiple measurement timings and parameters indicating the sharing of metrics of the multiple measurement timings between measurement and data communication; as well as One or more data messages are communicated to the UE during one or more time periods that at least partially overlap with a subset of the plurality of measurement times.
30. The method of claim 29, wherein the configuration is at least in part based on a data type, one or more criteria associated with the UE satisfying a threshold, or any combination thereof.