Measurement gap in centralized and distributed unit separation

By coordinating gap information between the CU and DU of the wireless communication system, the problem of low measurement gap management efficiency is solved, the reliability and efficiency of the communication system are improved, and the low latency and high-speed communication needs of the new generation of networks are met.

CN119032597APending Publication Date: 2024-11-26ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094930.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-07-29
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In wireless communication systems, prior art is difficult to effectively coordinate and manage measurement gaps, resulting in insufficient communication efficiency and reliability, especially when frequency ranges and use cases are changed between user equipment and base stations.

Method used

Determine and configure appropriate gap types, purposes and priority by coordinating gap information between centralized units (CUs) and distributed units (DUs), including concurrent gaps, preconfigured gaps, and network controlled small gaps (NCSGs), to determine and configure appropriate gap types, purposes and priorities. level, ensuring communication efficiency of user equipment when performing measurements on the target frequency band.

Benefits of technology

It improves the measurement gap configuration and communication efficiency of user equipment in different frequency ranges, enhances the reliability and flexibility of the communication system, and meets the needs of the new generation of network services for low latency and high-speed communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032597A_ABST
    Figure CN119032597A_ABST
Patent Text Reader

Abstract

When there are separate distributed units (DUs) and centralized units (CUs), wireless communications may be modified to coordinate communications for measuring gaps. The coordination may include a measurement gap configuration. Gap information may be used between a CU, a DU, and a user equipment (UE). The information may include a gap type, such as a concurrent gap, a pre-configured gap, or a network controlled small gap (NCSG). Embodiments include communication examples of handling measurement gaps in separate CUs and DUs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This document relates generally to wireless communications and more particularly to improved communications for measurement gaps in mobile device communications systems. Background Art

[0002] Wireless communication technology is driving the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including but not limited to wireless base stations). The next generation of networks is expected to provide high-speed, low-latency and ultra-reliable communication capabilities and meet the requirements of different industries and users. User mobile stations or user equipment (UE) are becoming more and more complex, and the amount of data communicated is increasing. In order to improve communication and meet the reliability requirements of vertical industries and support the next generation of network services, communication improvements should be made. Summary of the invention

[0003] This document relates to methods, systems, and devices for wireless communications in which there are separate distributed units (DUs) and centralized units (CUs). Despite the separation, measurement gaps can be coordinated. The coordination can include measurement gap configuration. Gap information can be used between the CU, DU, and user equipment (UE). The information can include gap types, such as concurrent gaps, preconfigured gaps, or network controlled small gaps (NCSG). Embodiments include communication examples for handling measurement gaps in separate CUs and DUs.

[0004] In one embodiment, a method for wireless communication includes sending a request message with gap information; and receiving a response message having a gap configuration based on the gap information. The transmission is from a base station centralized unit (CU) to a base station distributed unit (DU), and the response is received by the base station CU from the base station DU. A gap is a period used by a user equipment (UE) to perform measurements or operations on a dedicated use case. The request message includes a user equipment (UE) context establishment request message or a UE context modification request message, wherein the response message includes a UE context establishment response message or a UE context modification response message. The gap information includes: a requested or allowed gap type, a requested or allowed gap purpose, or a requested or allowed gap pattern, the number of requested or allowed gap patterns, a requested or allowed gap combination information, or gap priority information. The gap type includes at least one of the following items: concurrent gaps, preconfigured gaps, or network controlled small gaps (NCSG). The gap purpose or gap pattern includes at least one of the following items: 1 gap per frequency range (FR), a gap per FR2, or a gap per UE. The gap combination information includes at least one of the following items: a bit string or a bit map, each position in the bit string or the bit map indicates whether the corresponding gap combination is requested; or at least one gap combination index. The gap priority information includes at least one of the following items: a gap priority or a list of gap priorities for a gap associated with a dedicated use case; a gap priority or a list of gap priorities for a gap used for an associated measurement frequency or measurement object. The gap information includes at least one of the need for gap (NeedForGap) information or network controlled small gap (NCSG) information to indicate whether the UE needs a measurement gap or NCSG to perform measurements on the target frequency band. The gap information and the NCSG information are encapsulated as an octet string or container within the request message. The method also includes determining a gap association by the CU based on the gap configuration. The method also includes receiving a gap association by the CU from the DU, wherein the gap association is determined by the DU based on the gap configuration. The gap association is used for at least one of the following items: the measurement gap is associated with the measurement object, or the measurement gap is associated with the dedicated use case. Use cases include at least one of the following: positioning reference signaling (PRS) measurements, multiple universal subscriber identity module (MUSIM), non-terrestrial network (NTN) gaps, synchronization signal block (SSB) measurements, channel state information reference signal (CSI-RS) measurements, or E-UTRAN measurements.

[0005] In one embodiment, a method for wireless communication includes receiving a request message with gap information; and sending a response message having a gap configuration based on the gap information. Receiving is performed by a base station distributed unit (DU) from a base station centralized unit (CU), and sending is from the base station DU to the base station CU. A gap is a period used by a user equipment (UE) to perform measurements or operations on a dedicated use case. The request message includes a user equipment (UE) context establishment request message or a UE context modification request message, wherein the response message includes a UE context establishment response message or a UE context modification response message. The gap information includes: a requested or allowed gap type, a requested or allowed gap purpose, a requested or allowed gap pattern, a requested or allowed number of gap patterns, a requested or allowed gap combination information, or gap priority information. The gap type includes at least one of the following items: concurrent gaps, preconfigured gaps, or network controlled small gaps (NCSG). The gap purpose or gap pattern includes at least one of the following items: 1 gap per frequency range (FR), a gap per FR2, or a gap per UE. The gap combination information includes at least one of the following items: a bit string or a bit map, each position in the bit string or the bit map indicates whether the corresponding gap combination is requested; or at least one gap combination index. The gap priority information includes at least one of the following items: a gap priority or a list of gap priorities for gaps associated with a dedicated use case; a gap priority or a list of gap priorities for gaps used for associated measurement frequencies or measurement objects. The gap information includes at least one of the need for gap (NeedForGap) information or network controlled small gap (NCSG) information to indicate whether a user equipment (UE) needs a measurement gap or NCSG to perform measurements on the target frequency band. The gap information and the NCSG information are encapsulated as an octet string or container within the request message. The method also includes determining a gap association by the CU based on the gap configuration. The method also includes determining a gap association by the DU based on the gap configuration; and sending a gap association by the DU to the CU. The gap association is used for at least one of the following items: the measurement gap is associated with the measurement object, or the measurement gap is associated with the dedicated use case. Use cases include at least one of the following: positioning reference signaling (PRS) measurements, multiple universal subscriber identity module (MUSIM), non-terrestrial network (NTN) gaps, synchronization signal block (SSB) measurements, channel state information reference signal (CSI-RS) measurements, or E-UTRAN measurements.

[0006] In one embodiment, a wireless communication device comprises a processor and a memory, and the processor is configured to read code from the memory and implement any of the embodiments discussed above.

[0007] In one embodiment, a computer program product includes computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the embodiments discussed above.

[0008] In some embodiments, there is a wireless communication device including a processor and a memory, wherein the processor is configured to read code from the memory and implement any method described in any embodiment. In some embodiments, a computer program product includes a computer-readable program medium code stored thereon, which, when executed by the processor, causes the processor to implement any method described in any embodiment. The above and other aspects and their implementations are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example base station is shown.

[0010] Figure 2 An example random access (RA) messaging environment is shown.

[0011] Figure 3 The network architecture of the base station central unit (CU) and the base station distributed unit (DU) is shown.

[0012] Figure 4 One embodiment of communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0013] Figure 5 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0014] Figure 6 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0015] Figure 7 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0016] Figure 8 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0017] Fig. 9 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0018] Fig.10 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown.

[0019] Fig.11 An example of measurement gap timing is shown.

[0020] Fig.12 One embodiment of communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. DETAILED DESCRIPTION

[0021] The present disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of the present disclosure and show specific examples of embodiments by way of illustration. However, it is noted that the present disclosure may be embodied in a variety of different forms and, therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0022] Throughout the specification and claims, terms may have nuanced meanings that are implied or suggested in the context rather than explicitly defined. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the terms "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, the claimed subject matter includes combinations of exemplary embodiments or implementations (in whole or in part).

[0023] In general, terms can be understood at least in part from usage in context. For example, terms used herein (such as "and", "or", "and / or") can include multiple meanings, which can depend at least in part on the context in which such terms are used. Typically, "or" if used in an associative list, such as A, B, or C, means A, B, and C, which are used here in an inclusive sense, and A, B, or C, which are used here only in an exclusive sense. In addition, the terms "one or more" or "at least one" used herein (depending at least in part on the context) can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as "a", "an", or "the" can also be understood to convey singular or plural usage, which depends at least in part on the context. In addition, the term "based on" or "determined by..." can be understood to not necessarily be intended to convey a set of exclusive factors, but rather, other factors that are not necessarily explicitly described can be allowed to exist, which again depends at least in part on the context.

[0024] Radio Resource Control ("RRC") is a protocol layer between the UE and the base station at the IP layer (network layer). There may be various Radio Resource Control (RRC) states, such as RRC connected (RRC_CONNECTED), RRC inactive (RRC_INACTIVE), and RRC idle (RRC_IDLE) states. RRC messages are transmitted via the Packet Data Convergence Protocol ("PDCP"). As described above, the UE may send data via a random access channel ("RACH") protocol scheme or a configuration grant ("CG") scheme. CG may be used to reduce the waste of periodically allocated resources by enabling multiple devices to share periodic resources. A base station or node may allocate CG resources to eliminate packet transmission delays and increase the utilization of allocated periodic radio resources. The CG scheme is merely one example of a protocol scheme for communication, and other examples (including but not limited to RACH) are also possible. The wireless communication described herein may be performed over radio access.

[0025] There may be a master node ("MN") and one or more secondary nodes ("SN"). The MN may include a master cell group ("MCG"), and each SN may include a secondary cell group ("SCG"). The MCG is a group of cells provided by the master node ("MN"), and the SCG is a group of cells provided by the secondary node ("SN"). The MCG may include a primary cell ("PCell") and one or more secondary cells ("SCell"). The SCG may include a primary secondary cell ("PSCell") and one or more secondary cells ("SCell"). Each primary cell may be connected to multiple secondary cells. The primary cell (PCell, PSCell) is the primary cell of its corresponding group (MCG, SCG, respectively), and initial access may be initiated. The primary cell may be used for signaling and may be referred to as a special cell ("spCell"), where spCell=PCell+PSCell. The mobility between cells described in these embodiments may be based on PCell, PSCell and / or SCell. However, as described above, they may be referred to as source cells and target cells. When a user equipment ("UE") moves from a source cell to a target cell, the UE device may move between nodes or cells, in which case handover or change / add operations may occur to improve the network reliability of the UE.

[0026] As follows about Figures 1 to 3As described, a network provider may include multiple network nodes (i.e., base stations) for providing network access to user equipment ("UE") devices. In some embodiments, the network node is referred to as a base station. When there are separate distributed unit (DU) base stations and centralized unit (CU) base stations, the CU or DU may transmit gap information for coordinating gap measurements. In the case of CU / DU separation, the CU may coordinate some measurement gap assistance information with the DU to help the DU generate a measurement gap configuration. The DU may respond to the CU with a measurement gap related configuration. Some interaction / coordination processes for measurement gaps are described below, which may improve the current F1 interface. Figures 4 to 11 An example of CU / DU communication for gap measurement is shown. Figure 3 The measurement gap is further described.

[0027] Figure 1 An example base station 102 is shown. A base station may also be referred to as a radio network node and may be Figure 3 A to Figure 7 B shows network nodes (e.g., master node ("MN"), secondary node ("SN"), and source / target node). Base station 102 can be further identified as nodeB (NB, such as eNB or gNB) in the context of mobile telecommunications. An example base station may include a radio Tx / Rx circuit system 113 for receiving and transmitting with user equipment (UE) 104. The base station may also include a network interface circuit system 116 for coupling the base station to the core network 110, such as an optical or wired interconnect, Ethernet and / or other data transmission media / protocols.

[0028] The base station may also include system circuitry 122. System circuitry 122 may include processor(s) 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130. Operations 128 may include instructions for execution on one or more processors 124 to support the functionality of the base station. For example, the operations may process random access transmission requests from multiple UEs. Control parameters 130 may include parameters or support the execution of operations 128. For example, control parameters may include network protocol settings, random access message delivery format rules, bandwidth parameters, radio frequency mapping allocations, and / or other parameters.

[0029] Figure 2 An example random access messaging environment 200 is shown. In the random access messaging environment, the UE 104 can communicate with the base station 102 over a random access channel 252. In this example, the UE 104 supports one or more subscriber identity modules (SIMs), such as SIM1 202. An electrical and physical interface 206 connects SIM1 202 to the rest of the user equipment hardware, such as through a system bus 210.

[0030] The mobile device 200 includes a communication interface 212, a system logic 214, and a user interface 218. The system logic 214 may include any combination of hardware, software, firmware, or other logic. The system logic 214 may be implemented, for example, with one or more systems on a chip (SoC), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuit systems. The system logic 214 is part of the implementation of any desired function in the UE 104. In this regard, the system logic 214 may include logic that facilitates, for example, decoding and playing music and videos, for example, MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, such as Internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 218. The user interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of input 228 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0031] The system logic 214 may include one or more processors 216 and memory 220. The memory 220 stores, for example, control instructions 222 that are executed by the processor 216 to perform the desired functions of the UE 104. The control parameters 224 provide and specify configuration and operating options for the control instructions 222. The memory 220 may also store any BT, WiFi, 3G, 4G, 5G, or other data 226 that the UE 104 will send or has received through the communication interface 212. In various implementations, system power may be provided by a power storage device such as a battery 282.

[0032] In the communication interface 212, radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 230 handles the transmission and reception of signals through one or more antennas 232. The communication interface 212 may include one or more transceivers. A transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium.

[0033] The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 212 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the techniques described below are applicable to other wireless communication technologies, whether produced by the Third Generation Partnership Project (3GPP), the GSM Association, 3GPP2, the IEEE, or other partners or standards bodies.

[0034] Multiple RAN nodes with the same or different radio access technologies ("RAT") (e.g., eNB, gNB) may be deployed in the same or different frequency carriers in certain geographic areas and may cooperate with each other via dual connectivity operations to provide joint communication services for (multiple) the same target UEs. A multi-RAT dual connectivity ("MR-DC") architecture may have a non-colocated master node ("MN") and a secondary node ("SN"). The access mobility function ("AMF") and the session management function ("SMF") may be control plane entities, while the user plane function ("UPF") is a user plane entity in a new radio ("NR") or 5GC. The signaling connection between the AMF / SMF and the master node ("MN") may be a next generation control plane ("NG-C") / MN interface. The signaling connection between the MN and the SN may be an Xn control plane ("Xn-C") interface. The signaling connection between the MN and the UE is a Uu control plane ("Uu-C") RRC interface. All of these connections manage the configuration and operation of MR-DC. The user plane connection between the user plane function ("UPF") and the MN may be an instance of the NG-U(MN) interface.

[0035] Figure 3 The network architecture of the base station central unit (CU) and the base station distributed unit (DU) is shown. Figure 3 A base station (labeled "gNB") is shown communicating with the entire network (labeled ("5GC")). The base stations can communicate with each other via a control plane interface ("Xn-C"). One base station is shown with one CU connected to two DUs via an F1 interface. This is just one example of an arrangement of a base station. In some embodiments, there may be one or any number of DUs connected to a single CU.

[0036] A base station can be divided into two physical entities, named a centralized unit ("CU") and a distributed unit ("DU"). Typically, a CU can provide support for higher layers of a protocol stack (such as SDAP, PDCP, and RRC), while a DU provides support for lower layers of a protocol stack (such as RLC, MAC, and physical layers). A CU may include operations for transmission of user data, mobility control, radio access network sharing, session management, etc., except for those functions specifically assigned to a DU. (Multiple) DUs are (multiple) logical nodes with a subset of base station functionality and may be controlled by a CU.

[0037] The CU may be a logical node that hosts the RRC, SDAP, and PDCP protocols of a base station, or controls the RRC and PDCP protocols of a base station that operates one or more DUs. The DU may be a logical node that hosts the RLC, MAC, and PHY layers of a base station, and its operation may be at least partially controlled by the CU. A single DU may support one or more cells. However, each cell is supported by only a single DU. Each base station may support many cells.

[0038] A measurement gap is a period during which a user equipment (UE) performs measurements at different frequencies. During the gap, there may be no communication and the UE may turn off the radio. The UE may measure neighboring cell signals and / or other carrier components. The measurements may be performed using the same module as used for communication, so there may be a measurement gap. The UE may measure neighboring signals that are transmitted on the same frequency while sending and receiving data from the serving cell. When used to measure cells operating at different frequencies (e.g., inter-frequency neighbors) and other RATs (LTE is an other RAT for 5G NR), the UE may suspend communication (Tx / Rx) with the serving cell and needs to tune the communication module to the configured frequency (e.g., the configured measurement object) and resume connection with the serving cell after the gap, which is the duration that the UE suspends communication with the serving cell to measure inter-frequency neighbors or other RAT neighbors.

[0039] Depending on the UE's ability to support independent FR (frequency range) measurements and network preferences, there may be two types of measurement gaps. One measurement gap is per UE and the other measurement gap is per FR. In each FR gap, two independent gap patterns (i.e., FR1 gap and FR2 gap) are defined for FR1 and FR2, respectively. The per-UE gap is applicable to both FR1 (E-UTRA and NR) and FR2 (NR) frequencies. Frequency range (FR) FR1 is a frequency band gap in which the network stops communicating with FR1 cells but still maintains communication with other cells (e.g., FR2). FR2 is a frequency band gap in which the network stops communicating with FR2 cells but still maintains communication with other cells (e.g., FR1). In particular, the measurement gap may be a period during which the UE can use to perform measurements.

[0040] In New Radio (NR) or 5G, there can be at least three different configurations (measurement gaps). The first configuration is gapFR1, which is a gap configuration applied to FR1. The second configuration is gapFR2, which is a configuration applied to FR2. Similar to gapFR1, gapFR2 may not be configured with gapUE. The third configuration is gapUE. If gapUE is configured, neither gapFR1 nor gapFR2 can be configured. With this measurement gap configuration, the UE can measure FR1, FR2, and non-NR RAT.

[0041] In the CU / DU separation example, the CU and DU may coordinate and interact for measurement and measurement gap related configurations. The interaction may include a user equipment (UE) context establishment procedure and / or a UE context modification (base station CU initiated) procedure, where the CU sends the measurement frequency to the DU. These interactions are further described below.

[0042] UE context establishment

[0043] When the base station centralized unit (CU) includes SMTC information of (multiple) measurement frequencies in the MeasurementTimingConfiguration information element (IE) of the CU to DU RRC information IE included in the UE context setup request message, the base station distributed unit (DU) will generate measurement gaps based on the received SMTC information. The base station DU can send measurement gap information to the base station CU in the MeasGapConfig IE of the DU to CU RRC information IE included in the UE context setup response message. An example of IE is shown in the following table.

[0044] When the MeasConfig IE is included in the CU to DU RRC Information IE in the UE Context Setup Request message, the base station DU can infer the change to the measurement configuration to be applied. If the measObjectToAddModList IE is included in the MeasConfig IE, the frequency added to the IE can be activated. The base station DU can decide whether a measurement gap is required. When necessary, the base station DU can send measurement gap information to the base station CU in the MeasGapConfig IE of the DU to CU RRC Information IE included in the UE Context Setup Response message. When the measObjectToRemoveList IE is included in the MeasConfig IE, the base station DU should ignore it. IE examples are shown in the following table.

[0045] UE Context Modification

[0046] If the base station CU includes SMTC information of (multiple) measurement frequencies in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE included in the UE Context Modification Request message, the base station DU can generate the measurement gap based on the received SMTC information. The base station DU can send the measurement gap information to the base station CU in the MeasGapConfig IE of the DU to CURRC Information IE included in the UE Context Modification Response message.

[0047] When the MeasConfig IE is included in the CU to DU RRC Information IE in the UE Context Modification Request message, the base station DU can infer that a change in the configuration of the measurement needs to be applied. The base station DU can consider the received information (e.g., measObjectToAddModList IE and / or measObjectToRemoveList IE) when generating measurement gaps and when deciding whether measurement gaps are needed.

[0048] CU to DU RRC Information

[0049]

[0050] Table 1 - Example of MeasConfig from CU to DU.

[0051] DU to CU RRC information

[0052]

[0053] Table 2 - Example of MeasConfig from DU to CU.

[0054] Gap Type / Purpose

[0055] The CU notifies / indicates the requested or allowed gap type or gap purpose or gap pattern to the DU. In some examples, the gap type / purpose / mode may include perUE, perFR1, perFR2, concurrent gaps, preconfigured gaps, network controlled small gaps (NCSG), etc. The requested gap type / purpose / mode may be a combination of one or more gap types / purposes / modes. For example, there may be concurrent gaps combined with perUE. In another example, preconfigured gaps may be combined with perUE. In another example, NCSG may be combined with perUE. Measurement gap types and / or measurement gap purposes / modes may be combined and / or transmitted for more efficient communication regarding measurement gaps in separate CU / DU embodiments.

[0056] The requested gap type / purpose / mode may be indicated via one or more indications. For example, there may be an indication of a gap type / purpose / mode (e.g., per UE, per FR1, per FR2). In another example, there may be an indication of another gap type / purpose / mode (e.g., concurrent gaps, preconfigured gaps, NCSG, etc.). The indication (e.g., GapType) may be included as an information element (IE) in an F1-C message (e.g., a UE Context Modification Request message or a UE Context Establishment Request message). The IE may be included in the DU to CU RRC Information IE within the F1-C message.

[0057]

[0058] Table 3 - Example of signalling structure for gap type.

[0059] Concurrency gap

[0060] A concurrent gap is a type of gap and will be described further below. There may be multiple concurrent and independent gap patterns. Multiple gap configurations may correspond to UE capabilities. There may be a mandatory association between a gap and a dedicated use case (e.g., PRS, SSB, CSI-RS, EUTRA) by indicating a gap ID in the measurement target or MG configuration (e.g., for PRS). The measurement behavior of the UE may be well-defined, as the UE may be required to perform measurements associated with the gap during the gap opportunity. For UEs without / with per-FR gap capability, there may be a maximum supported concurrent gap pattern. For UEs without per-FR gap capability, up to two concurrent gap patterns may be configured. For UEs with per-FR gap capability, up to three concurrent gap patterns may be configured (e.g., up to two gaps in one FR).

[0061]

[0062] Table 3 — Examples of gap combinations.

[0063] There may be a close condition of conflicting gap opportunities. When a conflict occurs, the UE will discard the gap with a lower priority level configured by the network. In the discarded gap opportunity, data scheduling can be restored. The corresponding UE requirements on gap interruption, measurement delay, and L1 measurement impact can be updated.

[0064] As a first issue, gap measurement communication may require knowing which node (DU or CU) decides to configure / use concurrent gaps. In one embodiment, the CU sends an indication to the DU via an F1-C message to indicate that concurrent gaps are requested / allowed. In another embodiment, the DU decides this based on UE capabilities. As another issue, there is a decision to decide / generate gap associations. There is a determination about which node (DU or CU) decides the requested or allowed gap information or gap combination information, which may include the number of gap patterns or gap combinations, whether concurrent gaps are required, whether legacy gaps (e.g., indicated by GagConfig IE) or / and R17 gaps (e.g., indicated by GagConfig-R17 IE), requested or allowed gap type / purpose / mode, gap priority, etc. Gap association can associate a measurement object with a measurement gap, which is used for SSB or CSI-RS measurement identified by the associated measurement object. Gap association can associate a dedicated use case with a measurement gap. Use cases may include at least one of the following: positioning / PRS gaps, multi-universal subscriber identity module (MUSIM) gaps, non-terrestrial network (NTN) gaps, gaps for SSB measurements, gaps for CSI-RS measurements, and gaps for E-UTRAN measurements, etc.

[0065]

[0066] Table 5 - Example combinations / options for CU / DU separation.

[0067] Figures 4 to 11 An embodiment of a separate CU and DU for coordinated measurement communications is shown. Figures 4 to 5 An example of Option 1 from Table 5 is shown. Figure 6 to Figure 7 An example of Option 2 from Table 5 is shown. Figure 8 An example of Option 3 from Table 5 is shown. Figures 9 and 10 An example of Option 4 from Table 5 is shown.

[0068] Figure 4An embodiment of communication of an embodiment of a separate distributed unit (DU) and a centralized unit (CU) is shown. In this example, the centralized unit (CU) determines the gap information or gap combination information, and the CU determines the gap association. In box 402, the base station CU initially determines the gap information or gap combination information. In box 404, the CU sends the configured frequency (e.g., via MeasConfig), the requested gap information, or the gap combination information to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 406, the DU generates a measurement ("meas") gap configuration. This may include legacy gaps and / or R17 gaps, and is based on the requested / indicated gap information or gap combination information from the CU. The DU sends the generated measurement gap configuration to the CU via an F1-C message (e.g., a UE context setup / modification response message). In box 408, the CU determines the gap association between the measObject and the measurement gap based on the received measurement gap configuration. The CU reconfigures the measObject configuration to link the measurement gap ID with the measurement object. This may include associatedMeasGapSSB / associatedMeasGapCSIRS into MeasObjectNR and / or associatedMeasGap into MeasObjectEUTRA. In block 410, the CU generates an RRC reconfiguration message (e.g., MeasConfig) including a measurement configuration. The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 412, the CU sends the generated RRC reconfiguration message to the UE via the DU. The UE uses this information to perform measurements on different frequencies.

[0069] Figure 5 Another embodiment of the communication of the separate distributed unit (DU) and centralized unit (CU) embodiments is shown. In this example, the centralized unit (CU) determines the gap information or gap combination information, and the CU determines the gap association. Figure 4 In , the CU determines / generates the gap association after the DU measurement gap configuration. Figure 5 In the example, the timing of gap correlation determination / generation is related to Figure 4 different.

[0070] In block 502, the CU decides a gap association between a measObject and a measurement ("meas") gap. The CU may already have frequency information (e.g., including which frequencies are used for measurement) or / and measurement use case information (e.g., the measurement is used for positioning reference signal (PRS) measurement). In this example, the CU predetermines the gap association. In block 504, the CU sends the configured frequency (e.g., via MeasConfig), the predefined gap association, or / and the requested gap or gap combination to the DU via an F1-C message (e.g., a UE context setup / modify request message). The predefined gap association may be implicitly indicated (e.g., by including a pre-allocated meas measurement gap ID into the measObject within the MeasConfig) or explicitly indicated (e.g., by including the gap association information directly in the F1-C message). In block 506, the DU generates a measurement gap configuration based on the requested / indicated gap information or gap combination information and / or the gap association information from the CU. The DU sends the measurement gap configuration to the CU via an F1-C message (e.g., a UE context setup / modify response message). For some measurement gaps (e.g., configured via GapConfig-r17), the DU includes a gap ID pre-assigned by the CU into the gap configuration. In block 508, the CU generates an RRC reconfiguration message including a measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 510, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0071] Figure 6 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. Figure 6 to Figure 7 An example of Option 2 from Table 5 is shown. Figure 6 In the example shown, the centralized unit (CU) determines the gap information or gap combination information, and the distributed unit (DU) determines the gap association. The DU generates the gap association and sends it to the CU. The CU reconfigures the measObject.

[0072] In box 602, the base station CU determines gap information or gap combination information. In box 604, the CU sends the configured frequency (e.g., via MeasConfig), the requested gap information or gap combination information to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 604, the DU generates a measurement ("meas") gap configuration, which may include legacy gaps and / or R17 gaps. In box 606, the DU determines the gap association (e.g., a list of gap IDs, each gap ID is linked to an associated SSB / CSI-RS frequency or measObject ID) based on the requested gap information from the CU. In box 608, the DU sends the measurement gap configuration and gap association information to the CU via an F1-C message (e.g., a UE context setup / modification response message). The CU reconfigures the measObject configuration to link the measurement object with the associated measurement gap ID based on the gap association information from the DU. In box 610, the CU generates an RRC reconfiguration message including the measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 612, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0073] Figure 7 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. Figure 7 In the example shown, the centralized unit (CU) determines the gap information or gap combination information, and the distributed unit (DU) determines the gap association. Figure 7 In the example, the timing of gap correlation determination / generation is related to Figure 6Different. The DU directly reconfigures / updates the measObject and then sends the updated measObject configuration to the CU. In box 702, the base station CU determines the gap information or the gap combination information. In box 704, the CU sends the configured frequency (e.g., MeasConfig) and the requested gap information to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 706, the DU generates a measurement ("meas") gap configuration, which may include a legacy gap and / or an R17 gap. The DU determines the gap association based on the requested gap information from the CU. The DU reconfigures / updates the measObject configuration to link the measurement object with the associated measurement gap ID. In box 708, the DU sends the measurement gap configuration and the updated measObject configuration to the CU via an F1-C message (e.g., a UE context setup / modification response message). In box 710, the CU generates an RRC reconfiguration message including the measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 712, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0074] Figure 8 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. Figure 8 An example of Option 3 from Table 5 is shown. Figure 8In the example shown, a distributed unit (DU) determines gap information or gap combination information, and a centralized unit (CU) determines gap association. The DU determines gap information or gap combination information, and the CU determines gap association. In box 802, the CU sends a configured frequency (e.g., via MeasConfig) and / or a concurrent gap request indication to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 804, the DU determines gap information or gap combination information. In box 806, the DU generates multiple measurement ("meas") gap configurations, which may include legacy gaps and / or R17 gaps. The DU sends the measurement gap configuration to the CU via an F1-C message (e.g., a UE context setup / modification response message). In box 808, the CU determines a gap association between a measObject and a measurement gap based on the received measurement gap configuration. The CU reconfigures the measObject configuration to link the measurement gap ID with the measurement object (e.g., including associatedMeasGapSSB / associatedMeasGapCSIRS into MeasObjectNR, and / or including associatedMeasGap into MeasObjectEUTRA). In block 810, the CU generates an RRC reconfiguration message including a measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 812, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0075] Fig. 9 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. Figures 9 and 10 An example of Option 4 from Table 5 is shown. Fig. 9 In the example shown, a distributed unit (DU) determines gap information or gap combination information, and the DU determines gap association. Fig. 9 In the example, the timing of gap correlation determination / generation is related to Figure 8Different. The DU generates a gap association and sends it to the CU, and then the CU reconfigures the measObject. In box 902, the CU sends the configured frequency (e.g., via MeasConfig) and / or concurrent gap request indication to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 904, the DU generates multiple measurement ("meas") gap configurations, which may include legacy gaps and / or R17 gaps. The gap association (e.g., a list of gap IDs, each gap ID is linked to an associated SSB / CSI-RS frequency or measObject ID) can be based on the requested gap information from the CU. In box 906, the DU determines the gap association. In box 908, the DU sends the measurement gap configuration and gap association information to the CU via an F1-C message (e.g., a UE context setup / modification response message). Based on the gap association information from the DU, the CU reconfigures the measObject configuration to link the measurement gap ID with the associated measurement object. In block 910, the CU generates an RRC reconfiguration message including a measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 912, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0076] Fig.10 Another embodiment of the communication of separate distributed unit (DU) and centralized unit (CU) embodiments is shown. Fig.10In the example shown, a distributed unit (DU) determines gap information or gap combination information, and the DU determines gap association. The DU directly reconfigures / updates the measObject, and then sends the updated measObject configuration to the CU. In box 1002, the CU sends the configured frequency (e.g., MeasConfig) and / or concurrent gap request indication to the DU via an F1-C message (e.g., a UE context setup / modification request message). In box 1004, the DU generates a measurement ("meas") gap configuration, which may include a legacy gap and / or an R17 gap. The DU determines gap association. The DU reconfigures the measObject configuration to link the measurement object with the associated measurement gap ID. In box 1006, the DU determines the gap association and updates the measObject configuration. In box 1008, the DU sends the measurement gap configuration and the updated measObject configuration to the CU via an F1-C message (e.g., a UE context setup / modification response message). In box 1010, the CU generates an RRC reconfiguration message including the measurement configuration (e.g., MeasConfig). The measurement configuration may include at least one of the following items: a measurement object configuration (e.g., MeasObject), a measurement ID (e.g., MeasId), a measurement report configuration (e.g., MeasReport), or a measurement gap configuration (e.g., MeasGapConfig). In block 1012, the CU sends the generated RRC reconfiguration message to the UE via the DU.

[0077] Figures 4 to 10The example shown is for gap types with concurrent gaps. The gap information or gap combination information may include at least one of the following: the number of requested / allowed gap types / purposes / modes, the requested / allowed gap combinations, an indication of whether it is a legacy gap, gap priority information, measured frequency priority information, or the requested / allowed gap type / purpose / mode. The number of requested / allowed gap types / purposes / modes may include: 1) the total number or maximum number of gap types / purposes / modes allowed to be configured by the DU; or 2) for each gap type / purpose / mode, the number or maximum number of requested gap types / purposes / modes allowed to be configured by the DU (e.g., at most 2 perFR1 gaps, at most 1 perFR2 gap). The requested / allowed gap combination may include: 1) a bit string / bitmap, where each position in the bit string / bitmap indicates whether the corresponding gap combination in the table defined by RAN4 (e.g., Table 5) is requested (e.g., a value of 1 indicates that the corresponding gap combination is requested / allowed, and vice versa); or 2) a gap combination index or a list of gap combination indices allowed to be used / configured by the DU (e.g., a value of 1 indicates the first gap combination in the table defined by RAN4 (e.g., Table 5), and a value of 2 indicates the second gap combination in the table defined by RAN4 (e.g., Table 5)).

[0078] Another example is an indication of whether a legacy gap (e.g., GagConfig) and / or an R17 gap (e.g., GapConfig-r17) is requested / allowed to be configured by the DU. Another example is gap priority information to be used by each measurement gap, which may include a gap priority or a list of gap priorities for gaps of different features / use cases (e.g., positioning / PRS gaps, MUSIM gaps, NTN gaps, gaps for SSB measurements, gaps for CSI-RS measurements, gaps for E-UTRAN measurements, etc.). In some embodiments, a list of gap features / use cases (each linked to a gap priority value), where the priority value of each gap is indicated as an integer (e.g., a value of 1 indicates the highest priority, a value of 2 indicates a second level priority, etc.). The gap with the highest priority may be used, or the gap priority may be associated with the gap feature / use case. A gap priority indication or indicator may be used to indicate which gap has a high priority. The gap priority may also include a gap priority or a list of gap priorities for gaps used for associated frequencies or measObject measurements. For example, a list of SSB / CSI-RS frequencies may be linked to a gap priority value. The priority value for each slot may be represented as an integer (eg, a value of 1 for highest priority, a value of 2 for second-level priority, etc.).

[0079] Another example includes that the frequency priority information for the measurement can be indicated as a list of frequencies or measObjects ordered from high priority to low priority. The receiving node can use this information to generate a gap priority for measuring the gap of the corresponding frequency or measObject. This can be similar to the gap priority of the frequency, where there is a priority for different frequency values.

[0080] Another example is an indication of one or more requested or allowed gap types / purposes / modes (eg, perUE, perFR1, perFR2).

[0081] Another example is an indication indicating whether concurrent gaps are requested / allowed (eg, a "concurrent gap indicator").

[0082] The negotiation process may be considered for gap information or gap combination information coordination between the CU and the DU. The CU sends the proposed gap information or gap combination information to the DU. The DU selects one of the gap information or gap combination information proposed by the CU to generate a measurement gap configuration. Then, if the DU wants to request other gaps or gap combinations, the DU may send the requested gap information or gap combination information to the CU.

[0083] Gap associations may be indicated as: 1) a list of gap IDs, each gap ID linked to one MeasObject ID or a list of MeasObject IDs to be associated with the corresponding gap; 2) a list of gap IDs, each gap ID linked to one SSB / CSI-RS frequency or a list of SSB / CSI-RS frequencies to be associated with the corresponding gap; or 3) a list of MeasObject IDs, each MeasObject linked to one or more gap IDs to be associated with the corresponding MeasObject. For example, for E-UTRAN MeasObject, one MeasObject is associated with one gap ID; for NR MeasObject, one MeasObject is associated with one or more gap IDs (e.g., one gap ID is associated with SSB measurement and another gap ID is associated with CSI-RS measurement). A fourth example may include a list of SSB / CSI-RS frequencies, each SSB / CSI-RS frequency is linked to one or more gap IDs to be associated with the corresponding frequency. A fifth example may include a list of gap IDs, each gap ID is linked to one or more use cases to be associated with the corresponding gap. A sixth example may include a list of use cases, each use case is linked to one gap ID or a list of gap IDs.

[0084] An example of the signaling structure of a gap or gap combination is shown in the following table:

[0085]

[0086] Table 6: Example of signaling structure for a gap or gap combination.

[0087] An example of the signaling structure of the gap association information is shown in the following table:

[0088]

[0089] Table 7: Example of signaling structure of gap association information. Additional examples of signaling structure of gap association information are shown in the following table:

[0090]

[0091] Table 8: Additional examples of signaling structures of gap association information. The following table shows additional examples of signaling structures of gap association information:

[0092]

[0093] Table 9: Additional examples of signaling structures of gap association information. The following table shows additional examples of signaling structures of gap association information:

[0094]

[0095] Table 10: Additional example of signaling structure of gap association information.

[0096] The above gap related information (e.g., gap information or gap combination information, gap association information) may be transmitted between the CU and the DU through at least one of the following options:

[0097] Option 1: Include the gap related information directly as (multiple) information elements in the F1-C message (e.g., UE context setup / modification request message or UE context setup / modification response message). The (multiple) information elements may be included in the CU to DU RRC information IE and / or the DU to CU RRC information IE within the F1-C message.

[0098] Option 2: The gap related information encapsulated as an octet string / container is included in the F1-C message (e.g., UE context setup / modification request message or UE context setup / modification response message). The octet string / container may be included in the CU to DU RRC information IE and / or the DU to CU RRC information IE within the F1-C message.

[0099] Preconfigured gap

[0100] In another gap type, the measurement gap may be preconfigured by the network. There may be (multiple) preconfigured MG modes. In one embodiment, it may be network controlled, or in another embodiment, it may be a user equipment (UE) autonomous mechanism. It may include multiple activation / deactivation mechanisms and corresponding UE capabilities to support these mechanisms. For the network controlled mechanism, the UE follows the per-bandwidth part (BWP) indication in the active serving cell and the per-cell indication in the deactivated serving cell to decide the ON / OFF state of the preconfigured MG.

[0101] For the UE autonomous mechanism, the UE may follow defined rules (e.g., in TS38.133) to decide the ON / OFF state of the pre-configured MG. If the MG is not required for all measurements, the pre-configured gap may be deactivated (OFF). Otherwise, the pre-configured gap may be activated (ON). Events that may trigger the UE to recheck the ON / OFF state include:

[0102] DCI / timer-based BWP switching;

[0103] Activation / deactivation of (multiple) SCells;

[0104] Addition / removal of any (multiple) measurement objects;

[0105] Addition / release / change of Scells according to CA;

[0106] BWP switching by RRC; or

[0107] The initiation of LocationMeasurementIndication.

[0108] There may be an additional delay for preconfigured MG activation / deactivation, which may be five milliseconds (ms) above the traditional procedure delay that may trigger a preconfigured MG state change.There may be updates to corresponding UE requirements regarding gap interruption, measurement delay, and / or L1 measurement impact.

[0109] For preconfigured gaps, there may be a first problem for determining which node decides to configure / use the preconfigured gaps. In one embodiment, the CU may decide to configure / use the preconfigured gaps. In one example, the CU decides whether to use the preconfigured gaps and which type of preconfigured gap mechanism to use. The CU sends an indication to the DU via an F1-C message to indicate whether the preconfigured gap is requested / allowed (e.g., a "preconfigured gap indicator") or / and which type of preconfigured gap mechanism to use (e.g., a "preconfigured gap mechanism" indication, which value may be set to "network controlled mechanism" or "UE autonomous mechanism"). In another example, the CU decides whether to use the preconfigured gaps, and the DU decides which type of preconfigured gap mechanism to use. In another embodiment, the DU may decide to configure / use the preconfigured gaps. The DU may decide this based on UE capabilities.

[0110] For preconfigured gaps, there may be a second question for determining how to generate preconfigured gaps. The DU generates a preconfigured gap (e.g., includes preConfigInd in GapConfig-r17). This may be based on a preconfigured gap indication from the CU or based on its own decision. If the mechanism is network controlled, the DU may configure preConfGapStatus directly in the BWP / SCell configuration (without interacting with the CU), given that the meas measurement gap configuration and BWP / SCell configuration are generated by the DU. The DU sends a measurement ("meas") gap configuration and / or BWP / SCell configuration to the CU via an F1-C message. The CU generates an RRC reconfiguration message (including a measurement gap configuration and / or a BWP / SCell configuration) and sends the message to the UE.

[0111] Network Controlled Small Gap (NCSG)

[0112] NCSG can be a UE capability report based on RRCReconfigurationComplete and RRCResumeComplete messages (similar to NeedForGap). The UE can report whether "no gap no interruption", "ncsg" or "gap" is supported for each target band to be measured based on the UE's current CA configuration. There can be 24 NCSG modes with visible interruptions (VIL1 and VIL2, 1ms for FR1 and 0.75ms for FR2) before and after the measurement length (ML). The UE can be expected to continue download (DL) reception or upload (UL) transmission with the serving cell during the measurement length.

[0113] Fig.11 An example measurement gap timing is shown. This may include a MG timing advance of 0.75 ms.

[0114] The UE may have behaviors when it reports different capabilities regarding "no gap no interruption", "ncsg" or "gap", but has a different network configuration (NCSG or legacy MG) that may be different from the capabilities reported by the UE. When the UE cannot transmit / receive (Tx / Rx) or independent beamforming (FR2 specific) simultaneously, there may be a synchronization indication between the target NR band to be measured and the UE's reference serving cell to reduce OFDM symbols subject to data scheduling restrictions. There may be updates on corresponding UE requirements regarding gap interruptions, scheduling restrictions and measurement delays, as well as the impact on L1 measurements.

[0115] The configuration or use of NCSG can be performed by a centralized unit (CU) base station in one embodiment, or by a distributed unit (DU) base station in another example. For the CU example, the CU can send an indication to the DU via an F1-C message to indicate whether NCSG is requested / allowed (e.g., "NCSG indicator"). For the DU example, the DU decides based on the UE capabilities.

[0116] In some embodiments, the CU may need to transmit the received NeedForGap and / or NCSG information to the DU. The CU transmits the NeedForGap and / or NCSG information to the DU via the F1-C message to indicate whether the UE needs a measurement gap or NCSG to perform measurements on the target frequency band. The NeedForGap and / or NCSG information may be encapsulated in the F1-C message as an octet string / container.

[0117] In one example, the NeedForGapNCSG-InfoNR IE, the NeedForGapNCSG-InfoEUTRA IE and / or the NeedForGapsInfoNR IE may be present in the CU to DU RRC information IE within the F1-C message (e.g., the UE context setup / modification request message). The IE NeedForGapNCSG-InfoNR may indicate whether measurement gaps or NCSG are required for the UE to perform SSB-based measurements on the NR target band when NR-DC or NE-DC is not configured. The IE NeedForGapNCSG-InfoEUTRA indicates whether measurement gaps or NCSG are required for the UE to perform measurements on the EUTRA target band when NR-DC or NE-DC is not configured. The IE NeedForGapsInfoNR indicates whether measurement gaps are required for the UE to perform SSB-based measurements on the NR target band when NR-DC or NE-DC is not configured.

[0118] Fig.12An embodiment of communication of an embodiment of a separated distributed unit (DU) and a centralized unit (CU) is shown. The network can configure NCSG information to UEs with different target frequency bands. In box 1202, the UE sends an RRC reconfiguration / recovery complete message to the DU in box 1202, and sends an RRC reconfiguration / recovery complete message to the CU in box 1204. The message includes NeedForGap and / or NCSG information to indicate whether the UE needs a measurement gap or NCSG to perform measurements on the target frequency band. In box 1206, the CU sends the configured frequency (e.g., via MeasConfig) and / or NeedForGap and / or NCSG information to the DU via an F1-C message (e.g., a UE context establishment / modification request message). In box 1208, the DU generates a measurement gap configuration based on the received frequency (e.g., MeasConfig) and / or NeedForGap and / or NCSG information. The DU sends the measurement gap configuration to the CU via an F1-C message (e.g., a UE context establishment / modification response message). In block 1210 , the CU generates an RRC reconfiguration message including a measurement configuration (including MeasGapConfig), and in block 1212 , sends the generated RRC reconfiguration message to the UE through the DU.

[0119] The following table shows an example of the signaling structure of NeedForGap and / or NCSG information:

[0120]

[0121] Table 11 — Example of signaling structure of NeedForGap and / or NCSG information

[0122] The above systems and processes may be encoded in a signal bearing medium, a computer readable medium such as a memory, programmed in a device such as one or more integrated circuits, one or more processors, or processed by a controller or computer. The data may be analyzed in a computer system and used to generate a spectrum. If the methods are performed by software, the software may reside in a memory that resides in or interfaces to a storage device, a synchronizer, a communication interface, or a non-volatile or volatile memory that communicates with a transmitter. A circuit or electronic device is designed to send data to another location. The memory may include an ordered list of executable instructions for implementing a logical function. The described logical functions or any system elements may be implemented by optical circuit systems, digital circuit systems, source code, analog circuits, analog sources (such as analog electrical, audio or video signals), or a combination thereof. The software may be embodied in any computer readable or signal bearing medium for use or in combination with an instruction executable system, device or device. Such a system may include a computer-based system, a system containing a processor, or another system that can selectively retrieve instructions from an instruction executable system, device or device that can also execute instructions.

[0123] "Computer readable medium", "machine readable medium", "propagating signal" medium and / or "signal bearing medium" may include any device that includes storage, communication, propagation or transmission of software for use by or in conjunction with an instruction executable system, device or apparatus. Machine readable medium may selectively be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, apparatus, device or propagation medium. A non-exhaustive list of machine readable medium examples includes: an electrically connected "electronic device" having one or more wires, a portable magnetic or optical disk, a volatile memory (such as random access memory "RAM", read-only memory "ROM", erasable programmable read-only memory (EPROM or flash memory)), or an optical fiber. Machine readable medium may also include a tangible medium on which the software is printed, as the software may be stored electronically as an image or in another format (e.g., by optical scanning) and then compiled, and / or interpreted or otherwise processed. The processed medium may then be stored in a computer and / or machine memory.

[0124] The illustrations of the embodiments described herein are intended to provide a general understanding of the structures of various embodiments. These illustrations are not intended to be used as a complete description of all elements and features of the devices and systems utilizing the structures or methods described herein. Many other embodiments may be very clear to those skilled in the art after reviewing the present disclosure. Other embodiments may be utilized and other embodiments may be derived from the present disclosure so that structural and logical replacements and changes may be made without departing from the scope of the present disclosure. In addition, these illustrations are only representative and may not be drawn to scale. Some proportions in the illustrations may be exaggerated, while other proportions may be minimized. Therefore, the present disclosure and the accompanying drawings should be considered illustrative and not restrictive.

[0125] One or more embodiments of the present disclosure may be referred to herein individually and / or collectively by the term "invention", merely for convenience, and without intending to voluntarily limit the scope of the present application to any particular invention or inventive concept. In addition, although specific embodiments have been shown and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar purpose may replace the specific embodiments shown. The present disclosure is intended to cover any and all subsequent adaptations or variations of the various embodiments. The combination of the above embodiments and other embodiments not specifically described herein will be clear to those skilled in the art after reviewing the description.

[0126] The phrase "coupled" is defined to mean directly connected or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. The arrangement and type of components may be varied without departing from the spirit or scope of the claims set forth herein. More, different or fewer components may be provided.

[0127] The above disclosed subject matter is considered to be illustrative, not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present invention. Therefore, to the maximum extent permitted by law, the scope of the present invention will be determined by the broadest permissible interpretation of the following claims and their equivalents, and should not be restricted or limited by the foregoing detailed description. Although various embodiments of the present invention have been described, it is clear to those of ordinary skill in the art that more embodiments and implementations are possible within the scope of the present invention. Therefore, except in accordance with the appended claims and their equivalents, the present invention is not limited.

Claims

1. A method for wireless communication, comprising: Sending a request message with gap information; as well as A response message is received, the response message having a gap configuration based on the gap information.

2. The method of claim 1, wherein the sending is from a base station centralized unit (CU) to a base station distributed unit (DU), and the response is received by the base station CU from the base station DU.

3. The method of claim 1, wherein the gap is a period during which a user equipment (UE) performs measurements or operations related to a dedicated use case.

4. The method of claim 1, wherein the request message comprises a user equipment (UE) context establishment request message or a UE context modification request message, and wherein the response message comprises a UE context establishment response message or a UE context modification response message.

5. The method according to claim 1, wherein the gap information comprises: A requested or allowed gap type, a requested or allowed gap purpose, or a requested or allowed gap pattern, a requested or allowed number of gap patterns, a requested or allowed gap combination information, or gap priority information.

6. The method of claim 5, wherein the gap type comprises at least one of: a concurrent gap, a preconfigured gap, or a network controlled small gap (NCSG).

7. The method of claim 5, wherein the gap purpose or gap pattern comprises at least one of the following: gap per frequency range (FR) 1, gap per FR2, or gap per UE.

8. The method according to claim 5, wherein the gap combination information comprises at least one of the following items: a bit string or a bitmap, each position in the bit string or the bitmap indicating whether the corresponding gap combination is requested; or at least one gap combination index.

9. The method of claim 5, wherein the gap priority information comprises at least one of: a gap priority or a list of gap priorities for the gap associated with a dedicated use case; a gap priority or a list of gap priorities for the gap used for an associated measurement frequency or measurement object.

10. The method according to claim 1, wherein the gap information comprises at least one of need for gap (NeedForGap) information or network controlled small gap (NCSG) information to indicate whether a measurement gap or NCSG is required for the UE to perform measurement on the target frequency band.

11. The method of claim 10, wherein the required gap information and the NCSG information are encapsulated as an octet string or container within the request message.

12. The method according to claim 2, further comprising: A gap association is determined by the CU based on the gap configuration.

13. The method according to claim 2, further comprising: A gap association is received by the CU from the DU, wherein the gap association is determined by the DU based on the gap configuration.

14. The method according to claim 12 or 13, wherein the gap association is used for at least one of the following items: a measurement gap is associated with a measurement object, or a measurement gap is associated with a dedicated use case.

15. The method of any one of claims 3, 9 or 14, wherein the use case comprises at least one of: positioning reference signaling (PRS) measurements, multiple universal subscriber identity module (MUSIM), non-terrestrial network (NTN) gaps, synchronization signal block (SSB) measurements, channel state information reference signal (CSI-RS) measurements, or E-UTRAN measurements.

16. A method for wireless communication, comprising: receiving a request message with gap information; as well as A response message is sent, the response message having a gap configuration based on the gap information.

17. The method of claim 16, wherein the receiving is performed by a base station distributed unit (DU) from a base station centralized unit (CU), and the sending is from the base station DU to the base station CU.

18. The method of claim 17, wherein the gap is a period during which a user equipment (UE) performs measurements or operations related to a dedicated use case.

19. The method of claim 16, wherein the request message comprises a User Equipment (UE) Context Establishment Request message or a UE Context Modification Request message, and wherein the response message comprises a UE Context Establishment Response message or a UE Context Modification Response message.

20. The method of claim 16, wherein the gap information comprises: A requested or allowed gap type, a requested or allowed gap purpose, a requested or allowed gap pattern, a requested or allowed number of gap patterns, a requested or allowed gap combination information, or gap priority information.

21. The method of claim 20, wherein the gap type comprises at least one of: a concurrent gap, a preconfigured gap, or a network controlled small gap (NCSG).

22. The method of claim 20, wherein the gap purpose or gap pattern comprises at least one of: gaps per frequency range (FR) 1, gaps per FR2, or gaps per UE.

23. The method according to claim 20, wherein the gap combination information comprises at least one of the following items: a bit string or a bit map, each position in the bit string or the bit map indicates whether the corresponding gap combination is requested; or at least one gap combination index.

24. The method of claim 20, wherein the gap priority information comprises at least one of: a gap priority or a list of gap priorities for the gap associated with a dedicated use case; a gap priority or a list of gap priorities for the gap used for an associated measurement frequency or measurement object.

25. The method of claim 16, wherein the gap information comprises at least one of need for gap (NeedForGap) information or network controlled small gap (NCSG) information to indicate whether a user equipment (UE) needs a measurement gap or NCSG to perform measurement on a target frequency band.

26. The method of claim 25, wherein the required gap information and the NCSG information are encapsulated as an octet string or container within the request message.

27. The method of claim 17, further comprising: A gap association is determined by the CU based on the gap configuration.

28. The method of claim 17, further comprising: determining, by the DU, a gap association based on the gap configuration; as well as The gap association is sent by the DU to the CU.

29. The method according to claim 27 or 28, wherein the gap association is used for at least one of: a measurement gap is associated with a measurement object, or a measurement gap is associated with a dedicated use case.

30. The method of any one of claims 18, 24, or 29, wherein the use case comprises at least one of: positioning reference signaling (PRS) measurements, multiple universal subscriber identity module (MUSIM), non-terrestrial network (NTN) gaps, synchronization signal block (SSB) measurements, channel state information reference signal (CSI-RS) measurements, or E-UTRAN measurements.

31. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read a code from the memory and implement the method according to any one of claims 1 to 30.

32. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 30.