Measurement gap configuration for frequency range equal to or greater than 52.6 ghz
By defining a specific measurement gap configuration for the high frequency range (FRH), the problem of unoptimized measurement gap configuration in 5G networks is solved, communication throughput is improved, and efficient data transmission within the frequency range is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- APPLE INC
- Filing Date
- 2021-05-04
- Publication Date
- 2026-04-28
AI Technical Summary
In 5G networks, the measurement gap configuration in the high frequency range has not been effectively optimized, resulting in wasted communication throughput. Existing technologies struggle to provide efficient measurement gap configurations for frequency range 1 (FR1), frequency range 2 (FR2), and high frequency range (FRH).
Define specific measurement gap configurations for the high frequency range (FRH), including shorter measurement gap lengths and repetition periods. Optimize measurement gaps by adjusting the subcarrier spacing (SCS), reduce frequency retuning time, and improve communication efficiency.
By optimizing the measurement gap configuration, the frequency retuning time is reduced, communication throughput in the high-frequency range is improved, and resource waste is avoided.
Smart Images

Figure CN115633544B_ABST
Abstract
Description
[0001] Fifth-generation mobile networks (5G) are wireless standards designed to improve data transmission speed, reliability, availability, and more. While still under development, the standard includes many details related to cell reselection, such as the ability of user equipment (UE) to communicate with the network using channels within one or more frequency ranges. Attached Figure Description
[0002] Figure 1 An example of a network environment according to some implementation schemes is shown.
[0003] Figure 2 An example of a measurement gap according to some implementation schemes is shown.
[0004] Figure 3 An example of radio frequency (RF) retuning time and measurement window forming a measurement gap is shown according to some implementation schemes.
[0005] Figure 4 An example of a comparison between measurement gaps that vary depending on the frequency range, according to some implementation schemes, is shown.
[0006] Figure 5 An example of a sequence diagram between a user equipment (UE) and a network node associated with a measurement gap configuration according to some implementation schemes is shown.
[0007] Figure 6 An example of the UE's operation flow / algorithm structure configured using measurement gaps according to some implementation schemes is shown.
[0008] Figure 7 An example of the operational flow / algorithm structure for setting the measurement gap configuration of a network node is shown according to some implementation schemes.
[0009] Figure 8 An example of a receiving component according to some implementation schemes is shown.
[0010] Figure 9 Examples of UEs according to some implementation schemes are shown.
[0011] Figure 10 Examples of base stations according to some implementation schemes are shown. Detailed Implementation
[0012] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B).
[0013] Typically, a User Equipment (UE) can communicate with a network using channels in different frequency ranges, such as communicating with one or more base stations or other network nodes. Available frequency ranges include Frequency Range 1 (FR1), between 40 MHz and 7.125 GHz, and Frequency Range 2 (FR2), between 24.25 GHz and 52.6 GHz. Additional frequency ranges can be deployed, and these ranges may include frequencies greater than 52.6 GHz. This frequency range is referred to herein as the “High Frequency Range” (FRH). In the example, the High Frequency Range includes frequencies between 52.6 GHz and 71 GHz and may be referred to as Frequency Range 3 (FR3) or Frequency Range 2 Extension (FR2x). Of course, the upper limit of the High Frequency Range may differ from 71 GHz. In contrast, its lower limit may be equal to or greater than 52.6 GHz and does not overlap with the FR2 frequency range.
[0014] The UE can use a measurement gap to perform measurements on a reference signal (RS) within a frequency range (e.g., any of FR1, FR2, or FRH). The measurement gap can be configured with an indication duration (referred to as the measurement gap length (MGL)) and a repetition period (referred to as the measurement gap repetition period (MGRP)). Transmission and reception of data on one or more channels within the frequency range can cease for the duration of the measurement gap, allowing the UE to retune its radio frequency (RF) circuitry and receive the reference signal at least during the measurement gap. Transmission and reception can then resume. The measurement gap can be repeated according to the repetition period.
[0015] In the time domain, communication using the high frequency range (FRH) can utilize shorter time slots relative to the FR1 and FR2 frequency ranges. To optimize data transmission / reception and RS measurements within the high frequency range (FRH), a measurement gap configuration specific to this frequency range can be used. This measurement gap configuration, relative to FR1 and FR2, indicates shorter durations and shorter repetition periods.
[0016] In the example, the UE can indicate to the network node its support for per-frequency range (FR) measurement gap configurations, such as whether its measurement gaps support sub-combinations of FR1, FR2, and FRH, and / or whether it supports all three frequency ranges. This per-FR measurement gap configuration is referred to as an independent measurement gap configuration. If not supported, the UE uses a per-UE measurement gap configuration applicable to measurements of all frequency ranges FR1, FR2, and FRH.
[0017] Conversely, and depending on the UE's capabilities, the network node can configure one or more per-FR measurement gap configurations and / or per-UE measurement gap configurations, and send the relevant configuration information to the UE. This configuration information is also used to schedule RSs to be measured by the UE.
[0018] The following is a glossary of terms that may be used in this disclosure.
[0019] As used herein, the term "circuit" refers to, is part of, or includes: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs) configured to provide said functions. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.
[0020] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).
[0021] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.
[0022] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" may be considered synonymous and may refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.
[0023] As used herein, the term "base station" refers to a device with radio communication capabilities, i.e., a network of communication networks (or more simply, a network), and can be configured as an access node within that communication network. The UE's access to the communication network can be managed at least partially by the base station, thereby connecting the UE to the base station to access the communication network. Depending on the Radio Access Technology (RAT), a base station may be referred to as a gNodeB (gNB), eNodeB (eNB), access point, etc.
[0024] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.
[0025] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.
[0026] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.
[0027] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.
[0028] The term "connection" can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.
[0029] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.
[0030] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.
[0031] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include UE 104 and gNB 108. gNB 108 may be a base station providing a radio access cell such as a 3GPP New Radio (NR) cell, through which UE 104 can communicate with gNB 108. UE 104 and gNB 108 can communicate via an air interface compatible with 3GPP technical specifications such as those defining the 5G NR system standard.
[0032] The gNB 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels and transport channels on transport channels to physical channels. Logical channels can transmit data between the Radio Link Control (RLC) and MAC layers; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels can include the Physical Broadcast Channel (PBCH), the Physical Downlink Control Channel (PDCCH), and the Physical Downlink Shared Channel (PDSCH).
[0033] The PBCH can be used to broadcast system information that UE 104 can use to initially access the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. UE 104 can use the SS / PBCH block (SSB) during the cell search process (including cell selection and reselection), and the SSB can be used for beam selection.
[0034] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (other than MIBs), and paging messages.
[0035] The PDCCH can transmit DCIs used by the gNB 108 scheduler to allocate uplink and downlink resources. DCIs can also be used to provide uplink power control commands, configure time slot formats, or indicate when preemption has occurred.
[0036] The gNB 108 can also transmit various reference signals to the UE 104. These reference signals may include demodulation reference signals (DMRS) for the PBCH, PDCCH, and PDSCH. The UE 104 can compare the received DMRS version with a known DMRS sequence transmitted to estimate the effects of the propagation channel. The UE 104 can then apply the backpropagation channel during the demodulation process transmitted on the corresponding physical channel.
[0037] The reference signal may also include a Channel State Information Reference Signal (CSI-RS). The CSI-RS can be a multi-purpose downlink transmit signal that can be used for CSI reporting, beam management, connectivity mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.
[0038] Reference signals and information from the physical channel can be mapped to resources in the resource grid. For a given antenna port, subcarrier spacing configuration, and transmit direction (e.g., downlink or uplink), a resource grid exists. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by a subcarrier in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include a PRB in the frequency domain and an OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a set of resources used to transmit the PDCCH. One CCE can map to multiple REGs, for example, six REGs.
[0039] UE 104 can transmit data and control information to gNB 108 using physical uplink channels. Different types of physical uplink channels are possible, including, for example, the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). However, the PUCCH carries control information from UE 104 to gNB 108, such as uplink control information (UCI), while the PUSCH carries data services (e.g., end-user application data) and may also carry UCI.
[0040] UE 104 and gNB 108 can perform beam management operations to identify and maintain the required beams for transmission in the uplink and downlink directions. Beam management can be applied to PDSCH and PDCCH in the downlink direction and PUSCH and PUCCH in the uplink direction.
[0041] In the example, communication with the gNB 108 and / or the base station can utilize channels in the Frequency Range 1 (FR1) band, Frequency Range 2 (FR2) band, and / or the High Frequency Range (FRH) band. The FR1 band includes both licensed and unlicensed bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of Radio Access Technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A Listen-Before-Speak (LBT) procedure can be used to avoid or minimize conflicts between different RATs in the NR-U, whereby the device should apply a Clear Channel Assessment (CCA) check before using the channel.
[0042] like Figure 1As further shown, network environment 100 may further include base station 112 to which UE 104 can also connect. Base station 112 supports the same RAT as gNB 108 (e.g., base station 112 is also a gNB). Alternatively, base station 112 may support a different RAT (e.g., LTE eNB).
[0043] In the example, UE 104 supports carrier aggregation (CA), allowing UE 104 to simultaneously connect and exchange data with gNB 108 and / or base station 112 via multiple component carriers (CCs). CCs can belong to the same frequency band, in which case they are referred to as intra-band CCs. Intra-band CCs can be continuous or discontinuous. CCs can also belong to different frequency bands, in which case they are referred to as inter-band CCs. Serving cells can be configured for UE 104 to use CCs. Serving cells can be primary cells (PCell), primary-secondary cells (PSCell), or secondary cells (SCell). Multiple SCells can be activated via an SCell activation procedure, where the component carriers of these serving cells can be intra-band continuous, intra-band discontinuous, or inter-band. Serving cells can be co-located or non-co-located.
[0044] UE 104 can also support dual connectivity (DC), where the UE can simultaneously transmit and receive data from two serving nodes or cell groups (primary node (MN) and secondary node (SN)) on multiple CCs. DC capability can be used with two serving nodes operating in the same RAT or different RATs (e.g., MN operates in NR, while SN operates in LTE). These different DC modes include, for example, Evolved Universal Terrestrial Radio Access - New Radio (EN) - DC, NR-DC, and NE-DC (MN is an NR gNB, and SN is an LTE eNB).
[0045] Figure 2 An example of a measurement gap 200 according to some implementation schemes is shown. Typically, the UE, for example... Figure 1 UE 104 requires its RF circuitry to measure reference signals (e.g., SSBs) on neighboring cell signals and other component carriers. Such measurements may affect data transmission and / or reception with the serving cell, where such data transmission and / or reception depends on the RF circuitry. For inter-frequency and / or other RAT reference signal measurements, the UE stops data transmission and / or reception and retunes its RF circuitry to a configured frequency (e.g., depending on the configured measurement object). After the measurement, the UE can retune its RF circuitry again and then resume data transmission and / or reception with the serving cell. The two retunings and the duration of the stoppage in receiving reference signals and data transmission and / or reception can be defined as the measurement gap 200.
[0046] A measurement gap configuration can be defined for measurement gap 200, and this configuration can be signaled from the network to the UE. For example... Figure 2 As shown, the measurement gap configuration includes a measurement gap length 210 and a measurement repetition period 220, but additional measurement gap parameters are also possible. The measurement gap length 210 can represent the length of the measurement gap. This length can be a duration expressed in milliseconds (or some other unit). The measurement gap repetition period 220 can represent the periodicity of the repetition of the measurement gap 200 (e.g., in milliseconds or some other unit). The measurement gap length 210 and the measurement repetition period 220 can together represent a measurement gap pattern. The network can refer to a measurement gap pattern with a measurement gap pattern index "m". Other measurement gap parameters include, for example, measurement gap timing advance, which can represent the duration by which the UE (e.g., by advancing the start of RF circuit retuning) advances the start of the measurement gap.
[0047] like Figure 2 The frame structure is shown below. Typically, a radio frame is ten milliseconds long and can be represented by a System Frame Number (SFN). Figure 2 Two radio frames, labeled SFN, are shown. i 202 and SFN i+k 204, where three dots indicate that "k-1" radio frames exist between these two radio frames. Each radio frame consists of ten subframes, each one millisecond long (shown in boxes numbered "1" to "10"). Each subframe includes multiple time slots ( Figure 2 (Not shown in the image). The length of a time slot and the number of time slots per subframe can depend on the subcarrier spacing (SCS). Different SCSs are possible depending on the frequency range. FR1 and FR2 support SCSs of 15, 30, 60, 120, and 240 kHz, and these SCSs are represented by the digital symbols "μ" with the numbers "0", "1", "2", "3", and "4". FRH can support additional SCSs, including, for example, 480, 960, and 1920 kHz, which can be represented by the digital symbols "μ" with the numbers "5", "6", and "7". Variations in the subcarrier spacing allow for some flexibility in the length and number of time slots within a subframe. For example, the higher the digital symbol, the shorter the time slot can be. The number of symbols within a time slot does not change based on the subcarrier spacing but can change depending on the time slot configuration type. For time slot configuration 0, the number of symbols in a time slot is fourteen. In contrast, for time slot configuration 1, the number is seven.
[0048] exist Figure 2In the illustrative example, measurement gap 200 occupies four subframes (e.g., subframes "5", "6", "7", and "8" shown in diagonal dashed boxes). Measurement gap 200 also repeats every "k" radio frames. In this illustration, the duration of the measurement gap is four milliseconds (equal to four one-millisecond subframes). If "k" is four, the measurement gap repetition period is forty milliseconds (equal to four ten-millisecond radio frames).
[0049] Figure 3 Examples of RF retuning times 310 and 320 and a measurement window 330 forming a measurement gap 300 according to some embodiments are shown. In the illustrative example, data and / or other signaling information can be transmitted and / or received during subframes "1" to "4" and "9" to "10" of a radio frame, while the measurement gap 300 corresponds to subframes "5" to "8" of the radio frame. The measurement gap is configured with a first RF retuning time 310, a second RF retuning time 320, and a measurement window 330. The first RF retuning time 310 represents the time required during the measurement window 330 to retune the UE's RF circuitry from transmission / reception at subframe "4" to reception of the RS signal (e.g., SSB 340). Conversely, the second RF retuning time 320 represents the time required to retune the RF circuitry back at subframe "9" to resume transmission / reception. These retuning times 310 and 320 can be referred to as handover times to indicate that the UE's operation is switching (e.g., between transmit / receive and RS receive). Measurement window 330 can represent a time window of expected reference signals, which will be measured by the UE. In the example, the reference signal is the SSB. In this case, measurement window 330 includes an SSB-based RRM Measurement Timing Configuration (SMTC) window 340. The SSB can be scheduled by the network and received by the UE at different time slots (or more specifically, a set of resource elements including symbols in the time domain) within subframes "5" through "8". Typically, SMTC window 350 (and generally measurement window 330) does not overlap with the handover time.
[0050] Figure 4 Examples comparing measurement gaps depending on the frequency range according to some implementations are shown. As explained above, in the case of the high frequency range (FRH), the SCS can be increased (e.g., by utilizing the digital symbols "5", "6", or "7"), resulting in shorter time slots and / or shorter symbols. Because the reference signal (e.g., SSB) is encoded in the time slot (or resource elements distributed in one or more symbols of the time slot in the time domain), the measurement gap configuration for FRH can differ from the measurement gap configurations for FR1 and / or FR2 (e.g., the measurement gap duration can be shorter and / or the measurement gap repetition period can be shorter).
[0051] Figure 4 The top portion shows radio frame 402 used in a channel with frequencies less than 52.6 GHz (e.g., FR2). For illustrative purposes only, the numerical symbol "3" corresponds to a 120 kHz SCS and eight time slots 410 per subframe, each time slot 410 being 0.125 ms long. Other frame structures are also possible. Two SSBs are transmitted for the UE to measure, and as shown in the horizontal dashed box, these two SSBs are transmitted in two of the eight time slots 410, separated by the time slots. The measurement gap is defined as including an SMTC window of at least three time slots long (e.g., including two "SSB time slots" and an "intermediate time slot") or 0.375 ms.
[0052] In comparison, Figure 4 The bottom portion shows radio frame 404 used in a channel with a frequency range equal to or greater than 52.6 GHz (e.g., FR2). For illustrative purposes only, the numerical symbol "5" corresponds to a 480 kHz SCS and 32 slots 420 per subframe, each slot 420 being 0.03125 milliseconds long. Other frame structures are also possible. Two SSBs are also transmitted here for the UE to measure, as shown in the horizontal dashed box, and these two SSBs are separated by slots. The measurement gap is defined as an SMTC window including at least three slot lengths (e.g., including two "SSB slots" and an "intermediate slot"). However, the slots carrying the SSBs here are shorter, and the time length corresponding to three slots is 0.09375 milliseconds.
[0053] Based on the above comparison, a shorter measurement gap can be defined for communication in the high frequency range (FRH) compared to communication in FR1 and FR2. Otherwise, the measurement gap may be too long, potentially wasting opportunities to increase communication throughput.
[0054] Figure 5 An example of a sequence diagram 500 between a UE 510 and a network node 520 associated with a measurement gap configuration according to some implementations is shown. The network node 520 can be a primary or secondary node and can include a gNB or eNB, depending on the connectivity mode (e.g., EN-DC, NR-DC, NE-DC, NR standalone (SA), etc.). During UE attachment ( Figure 5 (Not shown in the image), after establishing the radio bearer, network node 520 sends the measurement gap configuration to UE 510 based on mobility-triggered events and policy settings. The measurement gap configuration may be included in RRC reconfiguration signaling and / or RRC recovery signaling.
[0055] In the example, sequence diagram 500 includes UE 510 sending capability information to network node 520, whereby the capability information can be used to determine whether the UE supports per-FR measurement gaps. For example, UE 510 indicates to network node 520 whether UE 510 supports measurement gaps in the high frequency range (FRH) that are in combination with or replace either of the measurement gaps FR1 and FR2, in addition to the measurement gaps FR1 and FR2. If per-FR measurement gaps are not supported, UE 510 indicates that they are not supported, and by default, network node 520 determines that UE 510 only supports per-UE measurement gaps. Alternatively, UE 510 may indicate that it only supports per-UE measurement gaps. Different methods are also possible and one or more information elements (IEs) and / or other messages may be used to indicate whether per-FR measurement gaps, including high frequency range (FRH) measurement gaps, are supported.
[0056] In the first example method, the capability information is a single indication of whether the UE can support at least three measurement gap configurations corresponding to the three frequency ranges FR1, FR2, and FRH. For example, UE 510 sends an "independentGapConfig" indication. "IndependentGapConfig" can be defined in the technical specification as a field indicating whether the UE supports three independent measurement gap configurations for FR1, FR2, and FRH (e.g., FR3 or FR2x). This field also indicates whether the UE supports gapless FR2 RAT inter-measurement when (NG)EN-DC is not configured, and whether the UE supports gapless FRH RAT inter-measurement (FRH measurement LTE / 3G / 2G) when (NG)EN-DC is not configured.
[0057] In the second example method, the capability information includes first capability information and second capability information. The first capability information indicates whether the UE 510 can support two measurement gap configurations corresponding to two of the three frequency ranges (e.g., any pair of (FR1, FR2), (FR1, FRH), or (FR2, FRH)). The second capability information indicates whether the UE 510 can support three measurement gap configurations corresponding to the three frequency ranges FR1, FR2, and FR3. The second capability information is set to indicate that the UE 510 can support three measurement gap configurations only if the first capability information is set to indicate that the UE 510 can support two measurement gap configurations. For example, the first capability information is "independentGapConfig," indicating whether the UE supports two independent measurement gap configurations: FR1 and FR2; or FR1 and FRH; or FR2 and FRH. If independentGapConfig is not supported, it means that the UE only supports per-UE measurement gaps. The second capability information is "new_independentGapConfig," which indicates whether the UE supports three independent measurement gap configurations: FR1, FR2, and FRH. This field is only applicable if "independentGapConfig" is set to "Supported".
[0058] In the third example method, the capability information includes first capability information and second capability information. The first capability information is common to both FR1 and FR2 and indicates whether UE 510 can support a first measurement gap configuration for FR1 and a second measurement gap configuration for FR2. The second capability information is specific to FRH and indicates whether UE 510 can support a third measurement gap configuration for FRH. The second capability information is only set to indicate that UE 510 can support the third measurement gap configuration if the first capability information is set to indicate that UE 510 can support both the first and second measurement gap configurations. For example, the first capability information is "independentGapConfig," indicating whether the UE supports both independent measurement gap configurations for FR1 and FR2. The second capability information is "FRHGapConfig," indicating whether the UE can support the FRH measurement gap. If "independentGapConfig" indicates that the UE can only support per-UE measurement gap, then "FRHGapConfig" can be "false" or "not configured" (FRH measurement gaps are not supported). If "independentGapConfig" indicates that the UE can support each FR measurement gap, then "FRHGapConfig" indicates whether the UE can support two independent measurement gap configurations for FR1 and FR2, or whether the UE can support three independent measurement gap configurations for FR1, FR2, and FRH. Specifically, if "FRHGapConfig" is set to true, it indicates that the UE supports independent measurement gaps for FR1, FR2, and FR3. Conversely, if "FRHGapConfig" is set to false, it indicates that the UE only supports independent measurement gaps for FR1 and FR2.
[0059] In the fourth example method, the capability information includes measurement gap capability information and band combination capability information. The measurement gap capability information indicates whether the UE 510 can support at least two measurement gap configurations (e.g., any pair or all three FR1, FR2, and FRH of (FR1, FR2), (FR1, FRH), or (FR2, FRH)). The band combination capability information indicates whether the UE 510 can support at least two band combinations. The measurement gap capability information and the band combination capability information together indicate the supported measurement gap configurations. For example, the capability information is “independentGapConfig”, indicating whether the UE supports the measurement gap configuration of FR1 and FR2 (but in this “independentGapConfig”, there is no such indication available for FRH). If “independentGapConfig” is not supported, the UE only supports per-UE measurement gap. Otherwise, if the UE supports the FR1+FR2+FRH band combination (as indicated by the band combination capability information), then being set to supported “independentGapConfig” means that the UE can support three independent measurement gap configurations of FR1, FR2, and FRH. In contrast, if the UE supports the FR1+FR2 or FR1+FRH or FR2+FRH band combination, then being set to supported "independentGapConfig" means that the UE can support two independent measurement gap configurations for FR1+FR2 or FR1+FRH or FR2+FRH respectively, which may depend on the band combination capability information notified by the signal.
[0060] In the fifth example method, the capability information includes a bitmap indicating that the UE 510 supports each frequency range of the corresponding measurement gap configuration. The bitmap can be signaling indicating which per-FR measurement gap is supported. For example, the bitmap may include three bits: the first bit corresponds to FR1, the second bit to FR2, and the third bit to FRH. A "0" value indicates that the corresponding per-FR measurement gap is not supported. A "1" value indicates that the corresponding per-FR measurement gap is supported. All "0" bits indicate that the UE can only support the per-UE measurement gap.
[0061] In the sixth example method, the capability information includes an IE for each frequency range, indicating that the UE 510 supports the measurement gap configuration for that frequency range. Individual IEs can be used, one for FR1, one for FR2, and one for FRH. Each IE can represent support (or non-support) for the FR1, FR2, and FRH measurement gaps, respectively.
[0062] In the example, sequence diagram 500 also includes network node 520 sending information about one or more measurement gap configurations to UE 510 based on capability information. This information can be sent via RRC signaling. RRC signaling can depend on the communication mode. For example, in (NG)EN-DC or NE-DC, the per-FRH measurement gap “gapFRH” can only be set by the NR RRC (e.g., the LTE RRC cannot configure measurement gaps for FRH frequency ranges). In NR-DC, “gapFRH” can only be established in the measConfig associated with the primary cell group.
[0063] Typically, if UE 510 only supports per-UE measurement gaps, network node 520 configures only per-UE measurement gaps. If UE 510 supports per-FRH measurement gaps but not per-FR1 and per-FR2 measurement gaps, network node 520 configures per-UE measurement gaps available for FR1 and FR2 and per-FRH measurement gaps available for FRH. As further described below, per-UE measurement gaps, rather than per-FRH measurement gaps, can be used for FRH based on the measurement object and serving cell. If the UE only supports per-FR measurement gaps for a pair of frequency ranges (e.g., (FR1, FR2), (FR1, FRH), or (FR2, FRH)), network node 520 configures per-FR measurement gaps for the two supported frequency ranges and per-UE measurement gaps available for the remaining frequency ranges. If the UE supports per-FR for all frequency ranges (e.g., FR1, FR2, and FRH), network node 520 configures per-FR measurement gaps for all three supported frequency ranges.
[0064] The measurement gap configuration can be "gapFR1" for the FR1 frequency range, "gapFR2" for the FR2 frequency range, "gapFRH" for the FRH frequency range, and "gapUE" for each UE measurement gap. Typically, the measurement gap configuration includes different parameters for the measurement gap, such as measurement gap length, measurement gap repetition, and measurement gap timing advance. Alternatively, the measurement gap configuration can include a measurement gap pattern index "m" from which at least some measurement gap parameters (e.g., a measurement gap pattern including measurement gap length and measurement gap repetition period) can be derived.
[0065] A measurement gap configuration specific to the FRH frequency range (e.g., including frequencies equal to and / or greater than 52.6 GHz) has a measurement gap mode index "m" value greater than twenty-five (e.g., twenty-six and above) and is used to indicate the measurement gap mode for the FRH. Values less than or equal to twenty-five may be associated with frequency ranges having frequencies less than 52.6 GHz (e.g., FR1 and FR2) and may indicate the measurement gap mode for such frequency ranges.
[0066] Multiple measurement gap modes can be defined for the FRH frequency range. Each mode can represent a combination of measurement gap length (MGL) and measurement gap repetition period (MGRP), where this combination is associated with a specific value (greater than twenty-five) of the measurement gap mode index "m". At least one of the measurement gap length and measurement gap repetition period is based on an FRH frequency equal to or greater than 52.6 GHz. For example, and return to reference. Figure 4 Such frequencies can use SCS greater than 240 kHz, and therefore can be associated with shorter measurement gap lengths to increase communication throughput. Similarly, the measurement gap repetition period can be shortened.
[0067] In the example, the measurement gap length includes two switching times (e.g., corresponding to...). Figure 3 The two RF retuning times (310 and 320) and the measurement gap duration (e.g., corresponding to...) Figure 3 The measurement window is 330. Switching times can be equal and can be set to "0.25 / 2". k "milliseconds, where "k = 0, 1, or 2" and "2 k "k" represents two raised to the power of two. Using "k" equal to "1" or "2" indicates a reduction in switching time of at least 50% or 75% compared to the usual 0.25 millisecond value used for FR1 and FR2. Specific values for "k" can be defined in the technical specifications and stored by the UE510 according to those specifications. The measurement gap duration can be selected from a set of {5, 3, 1, y} milliseconds, where "y" is less than one millisecond. For example, "y" is equal to 0.5, 0.25, or 0.125 milliseconds. Specific values for "y" can also be defined in the technical specifications and stored by the UE510 according to those specifications. The measurement gap length is set as follows:
[0068] ), where "k = 0, 1, or 2" and "y = 0.5, 0.25, or 0.125".
[0069] In the example, the measurement interval repetition can be set to "20 / 2". j "milliseconds, where "j = 0, 1, or 2" and "2 j "j" is two raised to the power of "j". Using "j" equal to "1" or "2" indicates that the repetition cycle for FR1 and FR2 has been reduced by at least fifty percent or seventy-five percent. Specific values for "j" can be defined in the technical specifications and are stored by UE 510 according to the technical specifications.
[0070] Based on the definitions of measurement gap length and measurement gap repetition, the following table can be defined for the FRH frequency range. This table associates the measurement gap pattern index "m" with the measurement gap length and measurement gap repetition, where the value of "m" is greater than twenty-five. This table can be defined in the technical specifications and stored by UE 510 according to the technical specifications.
[0071]
[0072] Furthermore, the Measurement Interval Timing Advance (MGTA) can be defined based on the switching time definition described above. For example, the Measurement Interval Timing Advance can be equal to zero milliseconds (when network node 520 indicates that no timing advance should be applied to the measurement interval), or equal to "0.25 / 2 k "millisecond.
[0073] As indicated above, measurement gap parameters, including measurement gap length, measurement gap repetition period, and measurement gap timing advance, can be included in the RRC signaling. An example of this approach is provided below, where MGL, MGRP, and switching time are based on the definitions above.
[0074]
[0075] As indicated above, RRC signaling may additionally or alternatively include the measurement gap index “m”. An example of this approach is provided below, where “m” is signaled to have one or more values between “0” and “37”. “m” values greater than 25 are derived from the MGL and MGRP definitions above, where “k” equals one and “y” equals 0.5 milliseconds, and are applicable to the FRH frequency range.
[0076] Gap mode identifier Measurement gap length (MGL, ms) Measurement interval repetition period (MGRP, ms) 0 6 40 1 6 80 2 3 40 3 3 80 4 6 20 5 6 160 6 4 20 7 4 40 8 4 80 9 4 160 10 3 20 11 3 160 12 5.5 20 13 5.5 40 14 5.5 80 15 5.5 160 16 3.5 20 17 3.5 40 18 3.5 80 19 3.5 160 20 1.5 20 21 1.5 40 22 1.5 80 23 1.5 160 24 10 80 25 20 160 26 5.25 20 27 5.25 10 28 5.25 5 29 3.25 20 30 3.25 10 31 3.25 5 32 1.25 20 33 1.25 10 34 1.25 5 35 0.75 20 36 0.75 10 37 0.75 5
[0077] In the two steps described above in sequence diagram 500, a description of signaling UE capabilities and configuring measurement gaps is provided. When FRH is FR3, UE capability signaling can be specific to FR1, FR2, and FR3. Furthermore, a per-FR measurement gap can be configured for each of FR1, FR2, and FR3. When FRH is FR2x, UE capability signaling can be specific to FR1 and FR2, where FR2 signaling also applies to FR2x. In this case, a per-FR measurement gap can be configured for each of FR1 and FR2, where the measurement gap of FR2 signaling extends to FR2x and includes MGL, MGP, and MGTA as defined above (e.g., ), k=0,1,or 2, MGRP=20 / 2 j j = 0, 1, or 2, and ).
[0078] Despite Figure 5 Not shown, but network node 520 can provide additional configuration information related to measurement gaps via, for example, RRC signaling. This information may generally be referred to as "measurement configuration" and may include measurement gap configuration. The measurement configuration can configure UE 510 to perform NR measurements and / or inter-RAT measurements. The measurement configuration can also configure UE 510 to report measurement information based on SSB and CSI-RS resources, measurement results for each SSB, measurement results for each cell based on SSB, SSB index, measurement results for each CSI-RS resource, measurement results for each cell based on CSI-RS resources, and / or CSI-RS resource measurement identifiers. For example, the measurement configuration may additionally include measurement objects (MOs), reporting configurations, measurement identifiers (Meas IDs), and quantity configurations. The MO provides a list of objects on which UE 510 will perform intra-frequency and inter-frequency measurements. The MO indicates the frequency / time location and subcarrier spacing of the RS to be measured.
[0079] In the example, sequence diagram 500 also includes UE 510 performing measurements on RS (e.g., SSB and / or CSI-RS) when measurement gap conditions are met. This step represents the behavior of UE 510, where, depending on the configured MO and the serving cell with which UE 510 may communicate, the UE performs measurements using a configured measurement gap.
[0080] Regarding the per-FRH measurement gap (e.g., "FRHgap"), this gap can be used for EN-DC, NR-DC, NE-DC, and NR SAUE, as follows. If UE 510 has an FRH serving cell and can support "FRHgap", the per-FRH measurement gap can be used when the configured MO includes an FRH MO. The use of "FRHgap" is limited to FRH measurements and transmit / receive on the FRH serving cell (e.g., data-related). "FRHgap" cannot be used for FR2 or FR1 measurements or interruptions on the FR2 or FR1 serving cell. Even when UE 510 is configured with "FRHgap", if the configured MO does not include an FRH MO, the measurement gap will not be applied to the FRH serving cell, and no data interruption will be applied to the FRH serving cell.
[0081] If UE 510 can only support per-UE measurement gaps (e.g., "UEgap"), then one of two scenarios can be supported. In the first scenario, when UE 510 has no serving cell in FR1 or FR2 but only in FRH and the configured MO only includes FRH MO, the FRH MG mode (with a measurement gap mode index "m", where the value of "m" is greater than twenty-five) can be used as "UEgap" (e.g., the "UE" gap is set to associate MGL and MGP with the value of "m") to perform FRH measurements and interrupt the transmission and / or reception of the FRH serving cell (e.g., for data). Otherwise, in the second scenario, the FRH measurement gap mode (e.g., derived from the value of "m") cannot be used as "UEgap" applied to the serving cell. In other words, these two scenarios represent the use of "UEgap" configured by network node 520, unless the serving cell of UE 510 only uses the FRH frequency range and the MO configured for the UE is only FRH MO, in which case a shorter "FRHgap" (derived from the value of "m") will be used. This approach implies the use of a longer "UEgap" strategy unless only FRH communication occurs.
[0082] Figure 6 An example of an operational flow / algorithm structure 600 for a UE configured using measurement gaps according to some embodiments is shown. The UE can implement the operational flow / algorithm structure 600 to determine and use each FR measurement gap, including a “FRHgap”. The operational flow / algorithm structure 600 can be executed or implemented by the UE (such as UE 104, 510, 900) or its components (e.g., processor 904). The UE can communicate with a network (e.g., network nodes including, for example, gNBs and / or eNBs) using multiple frequency ranges including FR1, FR2, and / or FRH.
[0083] The operation flow / algorithm structure 600 may include, at 602, sending capability information to the network indicating whether the UE can support multiple measurement gap configurations, where each measurement gap configuration in the multiple measurement gap configurations corresponds to a corresponding frequency range in multiple frequency ranges. For example, "FR1" gap corresponds to the FR1 frequency range, "FR2gap" corresponds to the FR2 frequency range, and "FR3gap" corresponds to the FRH frequency range. The UE may indicate that it supports any, a combination of, or all per-FR measurement gaps. If no support is provided, the UE may indicate that it supports per-UE measurement gaps or does not support per-FR measurement gaps. A single capability indication may be used for each frequency range, a single capability indication may be used for a combination of but not all three frequency ranges, a single capability indication may be used for all three frequency ranges, and / or a combination of measurement gap configuration capability indications and frequency band combination capability information may be used.
[0084] The operation flow / algorithm structure 600 may include, at 604, receiving configuration information from the network based on capability information, indicating the configuration of measurement gaps for multiple frequency ranges, wherein the frequency ranges include frequencies equal to and greater than 52.6 GHz. For example, RRC signaling may be used to send information to the UE. This information may indicate the measurement gap length, measurement gap repetition period, and measurement gap timing advance configuration. In the example, this measurement gap may be “FRHgap”. If the network defines additional measurement gap configurations for the UE, the UE may similarly receive information about each configuration in the per-FR measurement gap configuration. The UE may also receive information about per-UE measurement gap configurations.
[0085] The operation flow / algorithm structure 600 may include, at 606, determining the measurement gap length and measurement gap repetition period based on configuration information. At least one of the measurement gap length or measurement gap repetition period is based on a frequency equal to or greater than 52.6 GHz. Measurement timing advance can also be determined based on configuration information and can be set based on a frequency equal to or greater than 52.6 GHz. In the example, RRC signaling directly indicates these parameters. In another example, RRC signaling indicates the measurement gap mode index "m," the value of which can be used to determine the parameters. Here, if the network defines additional measurement gap configurations for the UE, the UE can similarly determine the measurement gap configuration parameters for each FR measurement gap or each UE measurement gap.
[0086] The operation flow / algorithm structure 600 may include, at 608, performing measurements on reference signals transmitted within a frequency range based on the measurement gap length and the measurement gap repetition period. For example, receiving SSB and / or CSI-RS on a channel within the FRH frequency range. Given the configured "FRHgap," the UE suspends data transmission / reception on the FRH serving cell during the measurement gap length of the "FRHgap" and performs at least SSB and / or CSIS-RS measurements. Thereafter, the UE resumes data transmission / reception on the FRH serving cell until the next measurement gap based on the measurement gap repetition period occurs. Here, if the network defines additional measurement gap configurations for the UE, the UE can similarly perform measurements on reference signals transmitted on channels within other frequency ranges (e.g., FR1 and / or FR2) based on the corresponding per-FR measurement gap or per-UE measurement gap. Typically, UE behavior depends on the configured MOs (e.g., whether they include FR1 MOs, FR2 MOs, and / or FRH MOs), the serving cells (e.g., whether they use the FR1 frequency range, FR2 frequency range, and / or FR3 frequency range), and the configured measurement gaps. Specifically, if a per-FR measurement gap is configured for a frequency range (or a per-UE measurement gap can be used), the MOs for that frequency range are defined, and the UE cannot interrupt data transmission / reception on serving cells using other frequency ranges, then the UE can perform measurements on reference signals transmitted via channels within that frequency range.
[0087] Figure 7 An example of an operational flow / algorithm structure 700 for setting measurement gap configurations for a network node, according to some embodiments, is shown. The network node can implement the operational flow / algorithm structure 700 to define the per-FR measurement gap for the UE, including a “FRHgap”. The operational flow / algorithm structure 700 can be executed or implemented by the network node (e.g., gNB 108, network node 520, gNB 900) or its components (e.g., processor 1004, different types of base stations, or radio network cores). The UE can communicate with the network, including the network node, using multiple frequency ranges including FR1, FR2, and / or FRH.
[0088] The operation flow / algorithm structure 700 may include, at 702, receiving UE capability information indicating whether the UE can support a measurement gap configuration including a frequency range equal to or greater than 52.6 GHz. For example, this frequency range is the High Frequency Range (FRH). The capability information indicates whether the UE supports the "FRHgap". As described above, the capability information may also indicate whether the UE supports per FR measurement gap for FR1 and / or FR2, or only per UE measurement gap. A single capability indication can be used for each frequency range, a single capability indication can be used for a combination of but not all three frequency ranges, a single capability indication can be used for all three frequency ranges, and / or a combination of measurement gap configuration capability indication and frequency band combination capability information can be used.
[0089] The operation flow / algorithm structure 700 may include, at 704, sending configuration information to the UE based on capability information, indicating the configuration of measurement gaps for a frequency range, wherein at least one of the measurement gap length or measurement gap repetition period is based on a frequency equal to or greater than 52.6 GHz. The configuration information may be sent via, for example, RRC signaling, and may include, for example, the measurement gap length, measurement gap repetition period, and / or measurement gap timing advance for the measurement gap (e.g., “FRHgap”). The configuration information may additionally or alternatively include a measurement gap index pattern “m” for measurement configuration, where the value of “m” is greater than twenty-five. Similar configuration information may be sent for “FR1gap”, “FR2gap”, and “UEgap”. Typically, if the UE supports per-FR measurement gaps, configuration information for the corresponding frequency range is defined and sent to the UE. If per-FR measurement gaps are not supported, the configuration information is specific to “UEgap”. In this case, the measurement gap index pattern “m”, where the value of “m” is greater than twenty-five, may also be sent, where the corresponding measurement gap pattern is used instead of “UEgap” depending on the configured MO and serving cell, as described above. Figure 5 The configuration information may include other information types related to the measurement gap, including, for example, the configured MO, report configuration, measurement identifier, and / or quantity configuration.
[0090] The operation flow / algorithm structure 700 may include, at 706, transmitting reference signals within a frequency range to the UE for measurement based on the measurement gap length and the measurement gap repetition period. For example, the network node schedules SSB and / or CSI-RS and transmits the SSB and / or CSI-RS to the UE, whereby the scheduling of these reference signals depends on the measurement gap length and the measurement gap repetition period.
[0091] Figure 8A receiver component 800 of a UE 84 according to some embodiments is shown. The receiver component 800 may include an antenna panel 804 that includes a plurality of antenna elements. The panel 804 is shown as having four antenna elements, but other embodiments may include other numbers.
[0092] Antenna panel 804 can be coupled to an analog beamforming (BF) component comprising multiple phase shifters 808(1)–808(4). Phase shifters 808(1)–808(4) can be coupled to radio frequency (RF) chain 812. RF chain 812 can amplify received analog RF signals, downconvert RF signals to baseband, and convert analog baseband signals into digital baseband signals that can be provided to a baseband processor for further processing.
[0093] In various implementations, control circuitry residing in the baseband processor may provide phase shifters 808(1)–808(4) with BF weights (e.g., W1–W4) that can represent phase shift values to provide a receive beam at antenna panel 804. These BF weights may be determined based on channel-based beamforming.
[0094] Figure 9 A UE 900 according to some implementation schemes is shown. The UE 900 may be similar to... Figure 1 The UE104 is essentially interchangeable with it.
[0095] Similar to the description above regarding UE 104, UE 900 can be any mobile or non-mobile computing device, such as a mobile phone, computer, tablet computer, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, and actuators), video surveillance / monitoring devices (e.g., cameras and camcorders), wearable devices, or relaxed-IoT devices. In some implementations, the UE can be a reduced-capacity UE or an NR lightweight UE.
[0096] UE 900 may include a processor 904, RF interface circuitry 908, memory / storage device 912, user interface 916, sensor 920, drive circuitry 922, power management integrated circuit (PMIC) 924, and battery 928. Components of UE 900 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 9The block diagram is intended to show a high-level view of some of the components of the UE 900. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.
[0097] The components of UE 900 can be coupled to various other components via one or more interconnects 932, which can represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.
[0098] Processor 904 may include processor circuitry such as baseband processor circuitry (BB) 904A, central processing unit circuitry (CPU) 904B, and graphics processing unit circuitry (GPU) 904C. Processor 904 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 912) to cause UE 900 to perform the operations described herein.
[0099] In some implementations, the baseband processor circuitry 904A can access the communication protocol stack 936 in the memory / storage device 912 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuitry 904A can access the communication protocol stack to perform the following operations: user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access stratum (NAS) layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuitry 908.
[0100] The baseband processor circuit 904A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.
[0101] The baseband processor circuit 904A can also access group information 924 from the memory / storage device 912 to determine the search space group for which the PDCCH can be replayed a certain number of times.
[0102] The memory / storage device 912 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 900. In some embodiments, some of the memory / storage devices 912 may be located on the processor 904 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 912 may be located external to the processor 904 but accessible via a memory interface. The memory / storage device 912 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.
[0103] The RF interface circuitry 908 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 900 to communicate with other devices via a radio access network. The RF interface circuitry 908 may include various components arranged in the transmit or receive path. These components may include switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.
[0104] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 924 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 904.
[0105] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 924.
[0106] In various implementations, the RF interface circuit 908 can be configured to transmit / receive signals in a manner compatible with NR access technology.
[0107] Antenna 924 may include multiple antenna elements, each of which converts electrical signals into radio waves to travel through the air and converts received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 924 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 924 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 924 may have one or more panels designed for a specific frequency band included in FR1 or FR2.
[0108] User interface circuitry 916 includes various input / output (I / O) devices designed to enable users to interact with UE 900. User interface 916 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 900.
[0109] Sensor 920 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular, inertial measurement units comprising: accelerometers; gyroscopes; or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems comprising: three-axis accelerometers; three-axis gyroscopes; or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.
[0110] The driving circuitry 922 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 900. The driving circuitry 922 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 900. For example, the driving circuitry 922 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings from sensor circuitry 920 and controlling and allowing access to sensor circuitry 920; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; or an audio driver for controlling and allowing access to one or more audio devices.
[0111] The PMIC 924 manages the power supplied to various components of the UE 900. Specifically, relative to the processor 904, the PMIC 924 controls power selection, voltage scaling, battery charging, or DC-DC conversion.
[0112] In some implementations, the PMIC 924 can control or otherwise become part of various power-saving mechanisms of the UE 900. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, it can enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the UE 900 can power down for short intervals to conserve power. If there is no data traffic activity over an extended period, the UE 900 can transition to the RRC_Idle state, where the device disconnects from the network and does not perform operations such as channel quality feedback or handover. The UE 900 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network before powering down again. The UE 900 may not receive data in this state; to receive data, the platform must transition back to the RRC_Connected state. Additional power-saving modes can allow the device to be unable to use the network for longer than the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will result in significant latency, which is assumed to be acceptable.
[0113] Battery 928 can power UE 900, but in some examples, UE 900 may be mounted in a fixed location and may have a power source coupled to the mains. Battery 928 may be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 928 may be a typical lead-acid automotive battery.
[0114] Figure 10 A gNB 1000 according to some embodiments is shown. The gNB node 1000 may be similar to and substantially interchangeable with gNB 108. Base stations (such as base station 102) may have the same or similar components as gNB 1000.
[0115] The gNB 1000 may include a processor 1004, an RF interface circuit 1008, a core network (CN) interface circuit 1012, and a memory / storage device circuit 1016.
[0116] The gNB 1000 components can be coupled to various other components via one or more interconnects 1028.
[0117] The processor 1004, RF interface circuit 1008, memory / storage device circuit 1016 (including communication protocol stack 1010), antenna 1024, and interconnect 1028 can be similar to those in the reference. Figure 8 Similar named elements are shown and described.
[0118] The CN interface circuitry 1012 can provide connectivity to a core network (e.g., a 5th generation core network (5GC) using a 5GC-compatible network interface protocol (such as Carrier Ethernet) or some other suitable protocol). Network connectivity can be provided to / from the gNB 1000 via fiber optic or wireless backhaul. The CN interface circuitry 1012 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN controller circuitry 1012 may include multiple controllers for providing connectivity to other networks using the same or different protocols.
[0119] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
[0120] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. As another example, the circuitry associated with a UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth in the Examples section below.
[0121] Example
[0122] Further exemplary implementations are provided in the following sections.
[0123] Example 1 includes a method. The method is implemented on a user equipment (UE). The method includes: sending capability information to a network indicating whether the UE can support multiple measurement gap configurations, wherein each of the multiple measurement gap configurations corresponds to a corresponding frequency range among multiple frequency ranges; receiving configuration information from the network based on the capability information, indicating the configuration of measurement gaps for the frequency ranges among the multiple frequency ranges, wherein the frequency ranges include frequencies equal to and greater than 52.6 GHz; determining a measurement gap length and a measurement gap repetition period based on the configuration information, wherein at least one of the measurement gap length or the measurement gap repetition period is based on the frequency equal to or greater than 52.6 GHz; and performing measurements on reference signals transmitted within the frequency range based on the measurement gap length and the measurement gap repetition period.
[0124] Example 2 includes a method. The method is implemented on a user equipment (UE). The method includes: sending capability information to a network indicating whether the UE can support a measurement gap configuration including a frequency range equal to or greater than 52.6 GHz; receiving configuration information from the network based on the capability information, indicating the configuration of the measurement gap within the frequency range; determining a measurement gap length and a measurement gap repetition period based on the configuration information, wherein at least one of the measurement gap length or the measurement gap repetition period is based on the frequency equal to or greater than 52.6 GHz; and performing measurements on reference signals transmitted within the frequency range based on the measurement gap length and the measurement gap repetition period.
[0125] Example 3 includes the method according to any one of Examples 1-2 above, wherein the plurality of frequency ranges include a first frequency range (FR1) between 40 MHz and 7.125 GHz, a second frequency range (FR2) between 24.25 GHz and 52.6 GHz, and a third frequency range (FR3) between 52.6 GHz and 71 GHz, wherein the frequency range is the third frequency range (FR3).
[0126] Example 4 includes the method according to any one of Examples 1-2 above, wherein the plurality of frequency ranges includes three frequency ranges, and wherein the capability information indicates whether the UE is capable of supporting at least three measurement gap configurations corresponding to the three frequency ranges.
[0127] Example 5 includes the method according to any one of Examples 1-2 above, wherein the plurality of frequency ranges includes three frequency ranges, wherein the capability information includes first capability information and second capability information, wherein the first capability information indicates whether the UE can support two measurement gap configurations corresponding to two frequency ranges of the three frequency ranges, and wherein the second capability information indicates whether the UE can support three measurement gap configurations corresponding to the three frequency ranges.
[0128] Example 6 includes the method according to Example 5, wherein the second capability information is set to indicate that the UE can support the three measurement gap configurations only if the first capability information is set to indicate that the UE can support the two measurement gap configurations.
[0129] Example 7 includes the method according to any one of Examples 1-2 above, wherein the plurality of frequency ranges includes a first frequency range, a second frequency range and a third frequency range, wherein the capability information includes first capability information and second capability information, wherein the first capability information indicates whether the UE can support a first measurement gap configuration of the first frequency range and a second measurement gap configuration of the second frequency range, and wherein the second capability information indicates whether the UE can support a third measurement gap configuration of the third frequency range.
[0130] Example 8 includes the method according to Example 7, wherein the second capability information is set to indicate that the UE can support the third measurement gap configuration only if the first capability information is set to indicate that the UE can support the first measurement gap configuration and the second measurement gap configuration.
[0131] Example 9 includes the method according to any one of Examples 1-4 above, wherein the capability information includes measurement gap capability information and band combination capability information, wherein the measurement gap capability information indicates whether the UE can support at least two measurement gap configurations, wherein the band combination capability information indicates whether the UE can support at least two band combinations, and wherein the measurement gap capability information and the band combination capability information together indicate the supported measurement gap configurations.
[0132] Example 10 includes the method according to any one of Examples 1-4 above, wherein the capability information includes a bitmap indicating that the UE supports each frequency range corresponding to the measurement gap configuration.
[0133] Example 11 includes the method according to any one of Examples 1-4 above, wherein the capability information includes information elements of the frequency range, the information elements indicating that the UE supports a measurement gap configuration of the frequency range.
[0134] Example 12 includes the method according to any one of Examples 1-11 above, wherein the frequency range is a first frequency range, wherein the UE is configured to transmit and receive in a plurality of frequency ranges including a second frequency range having a frequency of less than 52.6 GHz, wherein the configuration information includes a measurement gap index having a first value greater than 25 and associated with the first frequency range, and wherein the second frequency range is associated with a value less than or equal to 25 of the measurement gap index.
[0135] Example 13 includes the method according to any one of Examples 1-12 above, wherein the configuration information includes a measurement gap index, wherein the measurement gap length is determined from a first set of values based on the measurement gap index, and wherein the first set of values is defined as Milliseconds, where “k” equals 0, 1, or 2.
[0136] Example 14 includes the method according to Example 13, wherein “measurement gap duration” comes from a second set of values {5,3,1,y} milliseconds, where “y” is less than one millisecond.
[0137] Example 15 includes the method according to Example 13, wherein the configuration information further includes equal to The measurement interval in milliseconds is advanced.
[0138] Example 16 includes the method according to any one of Examples 1-12 above, wherein the configuration information includes a measurement gap index, wherein the measurement gap repetition period is determined from a set of values based on the measurement gap index, and wherein the set of values is defined as Milliseconds, where "j" equals 0, 1, or 2.
[0139] Example 17 includes the method according to any one of Examples 1-16 above, wherein the configuration information includes the measurement gap length, the measurement gap repetition period, and the measurement gap timing advance, wherein the measurement gap length is equal to "milliseconds", where "k" equals 0, 1, or 2, and "measurement gap duration" comes from a set of values {5, 3, 1, y}, where "y" is less than one millisecond, wherein the measurement gap repetition period is equal to Milliseconds, where "j" equals 0, 1, or 2, and where the measurement interval timing advance is equal to millisecond.
[0140] Example 18 includes the method according to any one of Examples 1-17 above, wherein the capability information indicates the UE's ability to support measurement gap configuration for the frequency range, wherein a measurement object is configured for the UE within the frequency range, and wherein the measurement is performed only based on the measurement object.
[0141] Example 19 includes a method according to any one of Examples 1-17 above, wherein the UE is configured to transmit and receive in a plurality of frequency ranges including the frequency range, wherein the measurement gap configuration is a per-frequency-range measurement gap configuration, wherein the capability information indicates that the UE only supports the capability of the per-UE measurement gap configuration, wherein when the UE has no serving cell in the remaining frequency ranges of the plurality of frequency ranges and the configured measurement object is only used for the frequency range, the per-frequency-range measurement gap configuration instead of the per-UE measurement gap configuration is used to determine the measurement gap length and the measurement gap repetition period.
[0142] Example 20 includes a method. The method is implemented on a network node. The method includes: receiving from a user equipment (UE) capability information indicating whether the UE can support a measurement gap configuration including a frequency range equal to or greater than 52.6 GHz; sending to the UE configuration information indicating the configuration of the measurement gap within the frequency range based on the capability information, wherein at least one of the measurement gap length or the measurement gap repetition period is based on the frequency equal to or greater than 52.6 GHz; and sending to the UE a reference signal within the frequency range for the UE to perform measurements based on the measurement gap length and the measurement gap repetition period.
[0143] Example 21 includes the method according to any one of Examples 1-20 above, wherein the frequency range is a first frequency range, wherein communication with the UE uses a plurality of frequency ranges including a second frequency range having a frequency less than 52.6 GHz, wherein the configuration information includes a measurement gap index having a first value greater than 25 and associated with the first frequency range, and wherein the second frequency range is associated with a value less than or equal to 25 of the measurement gap index.
[0144] Example 22 includes the method according to any one of Examples 1-20 above, wherein the configuration information includes the measurement gap length, the measurement gap repetition period, and the measurement gap timing advance, wherein the measurement gap length is equal to "milliseconds", where "k" equals 0, 1, or 2, and "measurement gap duration" comes from a set of values {5, 3, 1, y}, where "y" is less than one millisecond, wherein the measurement gap repetition period is equal to Milliseconds, where "j" equals 0, 1, or 2, and where the measurement interval timing advance is equal to millisecond.
[0145] Example 23 includes a UE comprising means for performing one or more elements of the method described or associated with any one of Examples 1-19.
[0146] Example 24 includes one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by one or more processors of the UE, cause the UE to perform one or more elements of the method described or associated with any one of Examples 1-19.
[0147] Example 25 includes a UE comprising logic, modules, or circuitry to perform one or more elements of the method described or associated with any one of Examples 1-19.
[0148] Example 26 includes a UE comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method described or associated with any one of Examples 1-19.
[0149] Example 27 includes a system comprising means for performing one or more elements of the method according to or related to any one of Examples 1-19.
[0150] Example 28 includes a network node comprising means for performing one or more elements of the method described or associated with any one of Examples 20-22 and Examples 3-19.
[0151] Example 29 includes one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by one or more processors of a network node, cause the network node to perform one or more elements of the method described or associated with any one of Examples 20-22 and Examples 3-19.
[0152] Example 30 includes a network node comprising logic, modules, or circuitry to perform one or more elements of the methods described or associated with any one of Examples 20-22 and Examples 3-19.
[0153] Example 31 includes a network node comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method described or associated with any one of Examples 20-22 and Examples 3-19.
[0154] Example 32 includes a network node comprising means for performing one or more elements of the method described or associated with any one of Examples 20-22 and Examples 3-19.
[0155] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.
[0156] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.
Claims
1. A method, the method comprising: This enables the network to send capability information indicating whether a user equipment (UE) can support multiple per-frequency-range measurement gap configurations within a frequency range, wherein the capability information includes first capability information and second capability information, wherein the first capability information indicates whether the UE can support two measurement gap configurations corresponding to two of the three frequency ranges, wherein the second capability information indicates whether the UE can support three measurement gap configurations corresponding to the three frequency ranges, and wherein the second capability information is set to indicate that the UE can support the three measurement gap configurations only if the first capability information is set to indicate that the UE can support the two measurement gap configurations; Based on the capability information, the configuration information received from the network indicates the configuration of the measurement gaps in the frequency range; The measurement gap length and the measurement gap repetition period are determined based on the configuration information, wherein at least one of the measurement gap length or the measurement gap repetition period is based on a frequency in the frequency range; as well as Measurements are performed on the reference signal transmitted within the frequency range based on the measurement gap length and the measurement gap repetition period.
2. The method of claim 1, wherein the capability information indicates whether the UE is capable of supporting a plurality of per-frequency-range measurement gap configurations within each of a plurality of frequency ranges, wherein the plurality of frequency ranges includes a first frequency range between 40 MHz and 7.125 GHz, a second frequency range between 24.25 GHz and 52.6 GHz, and a third frequency range between 52.6 GHz and 71 GHz.
3. The method according to claim 1 or 2, wherein the first capability information indicates whether the UE can support a first measurement gap configuration for a first frequency range and a second measurement gap configuration for a second frequency range, and wherein the second capability information indicates whether the UE can support a third measurement gap configuration for a third frequency range.
4. The method of claim 3, wherein the second capability information is set to indicate that the UE can support the third measurement gap configuration only if the first capability information is set to indicate that the UE can support the first measurement gap configuration and the second measurement gap configuration.
5. The method according to claim 1 or 2, wherein the capability information includes measurement gap capability information and frequency band combination capability information, wherein the measurement gap capability information indicates whether the UE can support at least two measurement gap configurations, wherein the frequency band combination capability information indicates whether the UE can support at least two frequency band combinations, and wherein the measurement gap capability information and the frequency band combination capability information together indicate the supported measurement gap configurations.
6. The method of claim 1 or 2, wherein the capability information includes a bitmap indicating that the UE supports each frequency range corresponding to the measurement gap configuration.
7. The method according to claim 1 or 2, wherein the capability information includes an information element of the frequency range, the information element indicating that the UE supports a measurement gap configuration for the frequency range.
8. An apparatus comprising: Processing circuit, the processing circuit being configured to: This enables the network to send capability information indicating whether a user equipment (UE) can support multiple measurement gap configurations per frequency range, including frequency ranges equal to and greater than 52.6 GHz. The capability information includes first capability information and second capability information. The first capability information indicates whether the UE can support two measurement gap configurations corresponding to two of the three frequency ranges. The second capability information indicates whether the UE can support three measurement gap configurations corresponding to the three frequency ranges. The second capability information is only set to indicate that the UE can support the three measurement gap configurations if the first capability information is set to indicate that the UE can support the two measurement gap configurations. Based on the capability information, the configuration information received from the network indicates the configuration of the measurement gaps in the frequency range; The measurement gap length and the measurement gap repetition period are determined based on the configuration information, wherein at least one of the measurement gap length or the measurement gap repetition period is based on a frequency in the frequency range; as well as Measurements are performed on the reference signal transmitted within the frequency range based on the measurement gap length and the measurement gap repetition period.
9. The apparatus of claim 8, wherein the frequency range is a first frequency range, wherein the UE is configured to transmit and receive in a plurality of frequency ranges including a second frequency range having a frequency less than 52.6 GHz, wherein the configuration information includes a measurement gap index having a first value greater than 25 and associated with the first frequency range, and wherein the second frequency range is associated with a value less than or equal to 25 of the measurement gap index.
10. The apparatus of claim 8 or 9, wherein the configuration information includes a measurement gap index, wherein the measurement gap length is determined from a first set of values based on the measurement gap index, and wherein the first set of values is defined as " + Measurement gap duration in milliseconds, where " k "Equals 0, 1 or 2." 11. The apparatus of claim 10, wherein the "measurement gap duration" is derived from a second set of values {5, 3, 1, ...} y } milliseconds, where " y "Less than one millisecond." 12. The apparatus of claim 10, wherein the configuration information further includes an amount equal to " "The measurement interval in milliseconds is advanced." 13. The apparatus of claim 8 or 9, wherein the configuration information includes a measurement gap index, wherein the measurement gap repetition period is determined from a set of values based on the measurement gap index, and wherein the set of values is defined as " "milliseconds, of which" j "Equals 0, 1 or 2." 14. The apparatus according to claim 8 or 9, wherein the configuration information includes the measurement gap length, the measurement gap repetition period, and the measurement gap timing advance, wherein the measurement gap length is equal to " + Measurement gap duration in milliseconds, where " k "Equals 0, 1, or 2, and 'Measurement gap duration' comes from a set of values {5, 3, 1, ...}". y },in" y "Less than one millisecond, wherein the repetition period of the measurement interval is equal to" "milliseconds, of which" j "equals 0, 1, or 2, and wherein the measurement interval timing advance is equal to" "millisecond.
15. A method, the method comprising: The user equipment (UE) receives capability information indicating whether the UE can support multiple measurement gap configurations per frequency range, including a frequency range. The capability information includes first capability information and second capability information. The first capability information indicates whether the UE can support two measurement gap configurations corresponding to two of the three frequency ranges. The second capability information indicates whether the UE can support three measurement gap configurations corresponding to the three frequency ranges. The second capability information is set to indicate that the UE can support the three measurement gap configurations only if the first capability information is set to indicate that the UE can support the two measurement gap configurations. Based on the capability information, configuration information is sent to the UE to indicate the configuration of the measurement gap in the frequency range, wherein the configuration information is used to determine the measurement gap length or the measurement gap repetition period, and wherein at least one of the measurement gap length or the measurement gap repetition period is based on the frequency; as well as The reference signal within the frequency range is sent to the UE based on the measurement gap length and the measurement gap repetition period for the UE to perform measurements.
16. The method of claim 15, wherein the frequency range is a first frequency range having a first frequency greater than 52.6 GHz, wherein communication with the UE uses a plurality of frequency ranges including a second frequency range having a second frequency less than 52.6 GHz, wherein the configuration information includes a measurement gap index having a first value greater than twenty-five and associated with the first frequency range, and wherein the second frequency range is associated with a value less than or equal to twenty-five of the measurement gap index.
17. The method according to claim 15 or 16, wherein the configuration information includes the measurement gap length, the measurement gap repetition period, and the measurement gap timing advance, wherein the measurement gap length is equal to " + Measurement gap duration in milliseconds, where " k "Equals 0, 1, or 2, and 'Measurement gap duration' comes from a set of values {5, 3, 1, ...}". y },in" y "Less than one millisecond, wherein the repetition period of the measurement interval is equal to" "milliseconds, of which" j "equals 0, 1, or 2, and wherein the measurement interval timing advance is equal to" "millisecond.
Citation Information
Patent Citations
NR cell measurement method and terminal equipment
CN112512076A
Measurement gap configuration for new radio (NR) systems
US20190174343A1
Configuration of multiple measurement gap patterns
US20190342801A1