Gap configuration methods, electronic devices, and computer program products in wireless communication systems
By uniformly configuring Gap information for user equipment and combining the purpose and type of multiple Gaps, the problem of chaotic Gap configuration in 5G networks has been solved, achieving efficient resource management and business continuity, and improving system performance and user experience.
Patent Information
- Application Number
- CN202510621387.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-17
AI Technical Summary
In 5G networks, Gap configuration is chaotic and inefficient due to differences in different scenarios and versions, making it impossible to uniformly consider all needs, resulting in Gap configuration conflicts and insufficient resource utilization.
By uniformly configuring Gap configuration information for user equipment, and combining the uses of multiple Gaps, including Gap ID, purpose, type, granularity, time domain configuration and priority, Gap retention information is used to resolve conflicts, activate or deactivate Gaps to adapt to UE requirements, and use RRC signaling and underlying signaling for information transmission.
It enables unified and efficient management of Gap configurations, improves resource utilization, ensures correct operation and business continuity in different scenarios, and reduces signaling interaction and latency.
Smart Images

Figure CN123124089A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and more specifically, to a gap configuration method, electronic device, and computer program product in a wireless communication system. Background Technology
[0002] In 5G discussions, various scenarios require the network to configure gaps for the UE, such as MUSIM (Multi-Universal Subscriber Identity Module) scenarios, positioning scenarios, and measurement scenarios. Furthermore, different versions of 5G have upgraded the gap configuration for different scenarios, leading to chaotic 5G gap configuration and an inability to consider all gap requirements, resulting in low gap configuration / usage efficiency. Facing the more diverse scenarios of 6G, a unified gap design architecture is needed. Currently, gap priority configurations are designed within a single gap type; for example, the Measurement Gap has its own priority system, and the MUSIM Gap has its own priority system. This leads to complex designs when gap conflicts occur. Summary of the Invention
[0003] This application provides a gap configuration method, electronic device, and computer program product in a wireless communication system to at least solve the problems of chaotic and inefficient gap configuration caused by different scenarios and versions when configuring gaps for UEs in the network.
[0004] According to one embodiment of this application, a gap configuration method in a wireless communication system is provided, including:
[0005] The user equipment (UE) is configured with unified gap configuration information by combining multiple gaps for different purposes or by combining gaps for different purposes.
[0006] Send the Gap configuration information to the UE.
[0007] According to another embodiment of this application, a gap configuration method in a wireless communication system is provided, including:
[0008] The base station receives interval gap configuration information, wherein the gap configuration information is configured by the base station for the UE in a unified manner, combining multiple interval gaps for different purposes or combining multiple gaps for different purposes.
[0009] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.
[0010] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0011] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.
[0012] Through the above embodiments of this application, Gap configuration information is uniformly configured for User Equipment (UE) by combining multiple gap uses or multiple gaps with different uses; sending the Gap configuration information to the UE can at least solve the problem of chaotic and inefficient Gap configuration caused by different scenarios and versions when configuring Gap for UE in the network in related technologies. By combining multiple gap uses to uniformly configure Gap configuration information for UE, it is possible to configure Gap for different scenarios. Attached Figure Description
[0013] Figure 1 This is a schematic diagram of the hardware structure of the mobile terminal used in the embodiments of the method of this application;
[0014] Figure 2 This is a flowchart of a gap configuration method in a wireless communication system according to an embodiment of this application. Figure 1 ;
[0015] Figure 3 This is a flowchart of a gap configuration method in a wireless communication system according to an embodiment of this application. Figure 2 ;
[0016] Figure 4 This is a schematic diagram of the positioning measurement gap activation / deactivation request MAC CE structure in related technologies;
[0017] Figure 5 This is a schematic diagram of the MAC CE structure for positioning and measurement gap activation / deactivation commands in related technologies;
[0018] Figure 6 This is a schematic diagram of a unified Gap architecture according to embodiments of this application;
[0019] Figure 7 This is a schematic diagram of a GapID bit Map according to an embodiment of this application;
[0020] Figure 8 This is a schematic diagram of the Gap type extension according to the embodiments of this application. Figure 1 ;
[0021] Figure 9This is a schematic diagram of the Gap type extension according to the embodiments of this application. Figure 2 ;
[0022] Figure 10 This is a flowchart of the Gap configuration according to an embodiment of this application;
[0023] Figure 11 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 1 ;
[0024] Figure 12 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 2 ;
[0025] Figure 13 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 3 ;
[0026] Figure 14 This is a flowchart of a DU-based Gap configuration according to an embodiment of this application;
[0027] Figure 15 This is a schematic diagram of the underlying signaling according to an embodiment of this application. Detailed Implementation
[0028] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.
[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.
[0030] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a schematic diagram of the hardware structure of the mobile terminal used in the embodiments of the method of this application. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.
[0031] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the Gap configuration method in the wireless communication system of this application embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0032] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.
[0033] This embodiment provides a gap configuration method for a wireless communication system running on the aforementioned mobile terminal or network architecture. Figure 2 This is a flowchart of a gap configuration method in a wireless communication system according to an embodiment of this application. Figure 1 ,like Figure 2 As shown, the process includes the following steps:
[0034] Step S202: Configure Gap configuration information for the User Equipment (UE) in a unified manner, taking into account the uses of multiple Gap intervals;
[0035] Step S204: Send Gap configuration information to the UE.
[0036] Through the above steps S202 to S204, the problems of chaotic and inefficient Gap configuration caused by different scenarios and versions when configuring Gap for UE in the network can be solved at least. By combining multiple Gap uses, Gap configuration information can be uniformly configured for UE, enabling the configuration of Gap for different scenarios.
[0037] In wireless communication systems, gap configuration refers to specific time intervals set for user equipment (UE) on the network side. These intervals are primarily used for UEs to perform special functions, such as measurement, positioning, or sensing. By uniformly configuring gap information, the network can more effectively manage and schedule UE resources, ensuring that the UE can perform the required operations at the correct time for different purposes without interfering with normal communication activities. For example, when a UE needs to perform neighbor cell measurements to support Radio Resource Management (RRM), the network will configure one or more gaps to ensure that the UE can stop receiving data and perform measurements during these gap periods. This configuration method can resolve potential conflicts between multi-purpose gaps and improve system resource utilization.
[0038] In one embodiment of this application, the above-mentioned Gap configuration information may include a Gap list, which includes multiple Gap information, and each Gap information includes at least one of the following: Gap ID, Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information.
[0039] The Gap list is the core of the Gap configuration information, describing the specific parameters of each Gap. The Gap ID uniquely identifies each Gap; the Gap purpose defines the use case of the Gap, such as for RRM, MUSIM management, and location services; the Gap type distinguishes the nature of different Gaps, such as static, semi-persistent, and dynamic; the Gap granularity is set according to the UE's spectrum resources or bandwidth requirements, such as based on the UE level, frequency range, or carrier level; the Gap time-domain configuration includes periodic and aperiodic Gaps, with periodic Gaps further subdivided into multiple sub-periods to adapt to different timing requirements; Gap priority is used as the basis for decision-making when resolving Gap conflicts; Gap retention information is used to preserve certain important Gaps from being discarded due to lower priority during Gap conflicts, and this mechanism is generally used in multiple Gap configurations. For example, if a UE participates in both RRM and location services simultaneously, the network can configure Gaps for these two purposes separately through the Gap list, specifying that the location service Gap has a higher priority, thereby prioritizing the continuity of location services when resources are scarce.
[0040] In one embodiment, the aforementioned gap configuration information also includes gap retention information. Gap retention information is an important supplement to gap configuration, allowing the UE to retain a portion of the gaps without discarding them when multiple gaps conflict. This is particularly important for frequently used gaps or high-priority gaps. For example, if the UE is performing a critical artificial intelligence task that relies on periodic gaps for data collection and processing, the network can use gap retention information when configuring gaps to ensure that this critical task is not affected.
[0041] In this embodiment of the application, step S202 may include: receiving Gap configuration assistance information reported by the UE, wherein the Gap configuration assistance information includes at least one of the following: Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information; and uniformly configuring Gap configuration information for the UE according to the Gap configuration assistance information.
[0042] The gap configuration assistance information reported by the UE is a crucial basis for the network to perform gap configuration. For example, a UE may report that it needs location services. After receiving this information, the network can configure the corresponding gap according to the UE's location requirements, ensuring the accuracy and timeliness of location. This mechanism enhances the flexibility and specificity of network configuration, making gap configuration more aligned with the actual needs of the UE.
[0043] In one embodiment of this application, receiving Gap configuration assistance information reported by the UE may include: receiving Gap configuration assistance information reported by the UE through radio resource configuration completion messages (e.g., RRC Resume Complete, RRC Reconfiguration Complete) or user assistance information (UE Assistance Information, UAI).
[0044] The RRC (Radio Resource Control) layer protocol provides a means for the UE and the network to exchange gap configuration assistance information. For example, the UE can report its need for Multi-User Multiple SIM (MUSIM) management in the RRC Resume Complete message, and the network can adjust the gap configuration accordingly to meet the UE's MUSIM requirements. This approach reduces unnecessary signaling interactions and improves configuration efficiency.
[0045] In one embodiment of this application, the Gap configuration assistance information further includes Gap retention indication information, which indicates which GAPs are to be retained. The Gap retention indication information is used by the UE to inform the network which GAPs it wishes to retain in the event of a GAP conflict. For example, if the UE is performing a task that requires continuous GAP support, it will use the Gap retention indication information to inform the network of the configuration information of the GAPs it wishes to retain in the event of a conflict. This helps maintain the UE's critical service continuity and reduces the potential risks arising from Gap configuration changes.
[0046] Furthermore, gap retention indication information is provided through a gap ID list or a gap purpose list. Using this list, the UE can explicitly specify the gaps it wishes to retain. For example, the UE can list all gap IDs associated with location services, or directly specify location services as the retention purpose. Upon receiving this information, the network determines whether to configure retention information for these gaps or their intended purposes. This approach simplifies the retention indication process and improves configuration accuracy.
[0047] In one embodiment of this application, the Gap configuration assistance information may further include a mechanism combining Gap priority and Gap retention indication. By combining Gap priority and Gap retention indication, the network can handle Gap configuration more intelligently. For example, when a UE reports that it is performing a high-priority artificial intelligence task, the network will not only configure the corresponding Gap but also mark it as a retention target. Even in the event of a conflict, it will prioritize retaining this Gap to ensure the smooth progress of the artificial intelligence task.
[0048] In one embodiment of this application, sending Gap configuration information to the UE may include sending the Gap configuration information to the UE via Radio Resource Control (RRC) signaling or underlying signaling. The network can send the Gap configuration information to the UE via RRC signaling or underlying signaling. RRC signaling is suitable for initial configuration issuance and significant changes, while underlying signaling is more suitable for quickly responding to immediate changes in the UE's needs, such as dynamic Gap configuration. For example, when a UE enters a new environment requiring urgent awareness, the network can quickly configure the awareness Gap via underlying signaling to help the UE quickly adapt to the new environment.
[0049] In one embodiment of this application, sending Gap configuration information to the UE via underlying signaling may include: sending underlying signaling to the UE via a distributed unit (DU), wherein the underlying signaling includes header information and encoded Gap configuration information.
[0050] The use of underlying signaling further improves the efficiency of gap configuration. For example, when a UE is in a high-speed mobile state and needs to frequently adjust its gap configuration to adapt to the rapidly changing environment, the network can quickly send underlying signaling through the DU (Distributed Unit), which contains encoded gap configuration information, ensuring that the UE can receive the latest gap configuration in a timely manner, while reducing signaling transmission latency and overhead.
[0051] In one embodiment of this application, the above method may further include: activating or deactivating one or more gaps, one or more gap IDs, or one or more gap types.
[0052] One or more gaps refer to one or more gaps of the same type or under the same gap ID. For example, a gap with a period of 40ms means there will be a gap every 40ms. This can indicate one or more gaps within this periodic gap. Activating or deactivating one or more gap types means activating or deactivating all gaps corresponding to a single gap ID, or all gaps corresponding to multiple gap IDs.
[0053] In this embodiment, a Gap can be understood as all the Gaps corresponding to a Gap ID. For a certain Gap ID or Gap type, it can be further understood as one or more Gaps under that Gap ID or Gap type.
[0054] The network can dynamically adjust the state of gaps based on the UE's needs, i.e., activate or deactivate gaps. For example, when the UE no longer needs to perform neighbor cell measurements, the network can deactivate the relevant gaps, freeing up resources for other uses. Conversely, when the UE starts a new task, such as communication or sensing, the network can activate the corresponding gaps to ensure the smooth execution of the task.
[0055] Furthermore, before activating or deactivating one or more gaps, gap types, or gap IDs, the above method may further include: receiving an activation or deactivation request sent by the UE, the activation or deactivation request being used to request the activation or deactivation of one or more gaps, gap types, or gap IDs. The UE can proactively request the network to activate or deactivate gaps to adapt to its constantly changing service needs. For example, after completing a location task, the UE can send a request to deactivate the location gap. Upon receiving the request, the network can promptly release these resources for other purposes or to reduce the UE's energy consumption. This mechanism strengthens the interaction between the UE and the network and improves the intelligence level of resource allocation.
[0056] In this application embodiment, the use of a gap may include at least one of the following: a gap for radio resource management (RRM), a gap for multi-user multi-SIM management (MUSIM), a gap for location services, a gap for communication and sensing, and a gap for artificial intelligence (AI) tasks. In this case, a gap may correspond to one or more different gap uses, and different gaps may correspond to the same or different gap uses.
[0057] The versatility of gap usage reflects the complex service requirements of wireless communication systems. For example, the same gap can be used for both RRM and MUSIM management, meaning that the UE can simultaneously perform neighbor cell measurements and multi-card handover management within the same time interval, improving resource reuse. Different gaps can be dedicated to location services or AI tasks, ensuring these specific needs are fully met, demonstrating the flexibility and efficiency of gap configuration.
[0058] In this application embodiment, the gap type includes at least one of the following: static gap, semi-persistent gap, dynamic gap, conditional gap, pre-configured type, and automatic autonomous gap.
[0059] The classification of gap types allows the network to manage gaps in a refined manner for different scenarios and needs. For example, static gaps are typically used for measurements at fixed intervals, such as neighbor cell scanning; dynamic gaps can be flexibly adjusted according to the real-time needs of the UE, such as being activated immediately when a new signal source is detected; conditional gaps are activated only when specific conditions are met, such as activating the location gap when the UE enters a specific geographical area; pre-configured gaps are set in advance when the UE has anticipated needs, such as configuring the MUSIM gap before the UE enters multi-SIM handover mode; and automatic gaps are managed autonomously by the UE according to its own needs without network intervention. This classification mechanism improves the adaptability and efficiency of gap configuration.
[0060] In this application embodiment, the gap granularity includes at least one of the following: based on UE level, based on frequency range level, based on band group level, based on cell level, based on carrier level, and based on BWP level.
[0061] The granularity of gap allocation takes into account the resource allocation and management needs of UEs. For example, UE-level gap configuration ensures that all UEs can obtain gap resources fairly; frequency range-based gap configuration is suitable for scenarios with dense spectrum resources, such as sensing in millimeter-wave bands; bandwidth group-based gap configuration considers the bandwidth requirements of UEs and can reserve sufficient gap time for UEs when they need high-bandwidth transmission; cell or carrier-level gap configuration focuses more on local optimization of network resources; and BWP (Bandwidth Part)-level gap configuration adapts to the flexible bandwidth allocation characteristics of 5G networks and can accurately match the service needs of UEs. This multi-layered configuration mechanism improves the accuracy and efficiency of resource allocation.
[0062] In this embodiment, the time-domain configuration of the gap includes periodic gaps and aperiodic gaps, wherein a periodic gap may include one or more sub-cycles. The flexibility of the time-domain configuration of the gap is reflected in the distinction between periodic and aperiodic gaps. Periodic gaps are suitable for activities that need to be performed regularly, such as periodic neighbor cell measurements. They can be further subdivided into multiple sub-cycles so that the UE can perform specific measurements or tasks in each sub-cycle. Aperiodic gaps are used to deal with sudden or unpredictable needs, such as emergency location services. This time-domain configuration method ensures that the UE can obtain the necessary gap support in various scenarios, improving the overall system performance and user experience.
[0063] This application also provides a gap configuration method in a wireless communication system. Figure 3 This is a flowchart of a gap configuration method in a wireless communication system according to an embodiment of this application. Figure 2 ,like Figure 3 As shown, the process includes the following steps:
[0064] Step S302: Receive interval gap configuration information sent by the base station. The gap configuration information is configured by the base station for the UE in a unified manner, combining the uses of multiple interval gaps or combining multiple gaps with different uses.
[0065] By following the steps above, the problems of chaotic and inefficient Gap configuration caused by different scenarios and versions when configuring Gap for UE in the network can be solved at least. By combining multiple Gap uses to uniformly configure Gap configuration information for UE, it is possible to configure Gap for different scenarios.
[0066] In wireless communication systems, a gap refers to a time window reserved for measurements on other frequencies or between systems. For example, in a 5G NR system, a UE may need to perform measurements on different frequency bands to support advanced features such as carrier aggregation and dual connectivity. Unified gap configuration by the base station means that the base station comprehensively considers the different needs of UEs and network conditions, pre-planning a series of gaps instead of configuring them individually for specific purposes. This greatly simplifies the configuration process, reduces signaling overhead, and improves the overall operating efficiency of the system. Unified gap configuration solves the problems of uneven resource allocation and frequent signaling interactions inherent in traditional gap configuration methods, achieving effective management and efficient utilization of gap resources.
[0067] In this embodiment, the Gap configuration information includes a Gap list, which contains multiple Gap information items. Each Gap information item includes at least one of the following: Gap ID, Gap purpose, Gap type, Gap granularity, Gap time-domain configuration, Gap priority, and Gap retention information. The Gap ID is used to uniquely identify each Gap, similar to a serial number, facilitating Gap referencing and management between the UE and the base station. The Gap purpose specifies the specific application scenario of the Gap, such as for NR co-frequency measurement, NR inter-frequency measurement, EUTRA co-frequency measurement, etc. The Gap type distinguishes whether the Gap is continuous or discontinuous; continuous Gaps are typically used for long-period measurements, while discontinuous Gaps are suitable for short-period measurement requirements. The Gap granularity defines the duration of the Gap, for example, it could be 6 symbols, 11 symbols, etc. The Gap time-domain configuration refers to the specific position and repetition period of the Gap on the time axis, such as repeating every 10ms for 6 symbols each time. The Gap priority is used as the decision-making basis for resolving Gap conflicts; higher-priority Gaps are executed first. Gap retention information indicates which gaps should be retained even in the event of a conflict. With this detailed gap information, the UE can accurately understand the base station's intentions, rationally plan its own measurement activities, avoid unnecessary resource conflicts and waste, and ensure the smooth execution of various measurement tasks.
[0068] Furthermore, the Gap configuration information can also include Gap retention information. The introduction of Gap retention information allows the UE to have clear guidelines for deciding which gaps should be retained when encountering gap conflicts, thereby ensuring the completion of critical measurement tasks. For example, when a gap used for emergency services conflicts with a gap used for normal data transmission, the retention information can instruct the UE to prioritize retaining the gap for emergency services, ensuring that service quality is not affected. This mechanism effectively solves common conflict problems in gap configuration and improves system stability and reliability.
[0069] In one embodiment, the method further includes: reporting Gap configuration assistance information to the base station, wherein the Gap configuration assistance information includes at least one of the following: Gap purpose, Gap type, Gap granularity, Gap time-domain configuration, and Gap priority configuration information. The UE reports Gap configuration assistance information to the base station so that the base station can better understand the UE's actual measurement needs and capabilities, thereby making a more reasonable Gap configuration. For example, if the UE is performing a task requiring high-precision measurement, it can report smaller Gap granularity information to prompt the base station to configure a finer Gap to meet the measurement accuracy requirements. This two-way communication mechanism makes Gap configuration more dynamic and flexible, adapting to constantly changing network environments and UE needs.
[0070] Furthermore, reporting Gap configuration assistance information to the base station can include: reporting Gap configuration assistance information to the base station via Radio Resource Configuration Complete messages (e.g., RRC Resume Complete, RRC Reconfiguration Complete) or User Assistance Information (UAI). RRC Resume Complete and RRC Reconfiguration Complete are two ways the UE responds to the base station's RRC signaling. Reporting Gap configuration assistance information through these means ensures that the base station receives the UE's status updates in a timely manner and adjusts the Gap configuration strategy. User Assistance Information (UAI) is a more general reporting mechanism that allows the UE to report its measurement needs and capabilities to the base station at any time, enhancing the UE's autonomy and the system's adaptability. The use of these reporting mechanisms ensures information synchronization between the base station and the UE, promoting the optimization of Gap configuration.
[0071] Furthermore, the gap configuration assistance information can also include gap retention indication information, which indicates which gaps should be retained. This information is fed back from the UE to the base station, informing the base station which gaps are critical to the UE and should not be easily changed or cancelled. For example, if the UE is performing a long-term tracking measurement task, it may instruct the base station to retain the corresponding gaps to ensure task continuity. Upon receiving this information, the base station can consider it in subsequent gap configurations, avoiding interference with the UE's critical tasks. This mechanism strengthens the collaboration between the base station and the UE, improving the accuracy and effectiveness of gap configuration.
[0072] Furthermore, gap retention indication information can be provided through either a gap ID list or a gap purpose list. Using a gap ID list, the UE can directly list the IDs of the gaps that need to be retained, a method that is intuitive, easy to understand, and simple to operate. Using a gap purpose list, on the other hand, lists the intended use of the gaps to be retained from a functional perspective. The base station can then determine whether to retain the corresponding gap based on the importance of its purpose. The combined use of these two indication methods allows the base station to have a more comprehensive understanding of the UE's needs, making more reasonable gap configuration decisions and further improving the system's flexibility and efficiency.
[0073] Furthermore, the gap configuration assistance information can also include a mechanism that combines gap priority with gap retention indication. This combination means that the UE can not only report the priority of gaps to the base station, but also indicate which gaps should remain unchanged. For example, the UE can report that a gap used for critical services has the highest priority and simultaneously instruct the base station to keep this gap unchanged. This mechanism ensures that the UE's measurement requirements are met to the greatest extent possible, while also reducing the configuration burden on the base station, avoiding unnecessary gap adjustments, and improving the overall system performance.
[0074] In this embodiment, step S302 may include: receiving Gap configuration information sent by the base station via Radio Resource Control (RRC) signaling or lower-level signaling. RRC signaling is a higher-level protocol used to control the configuration and management of radio resources. Receiving Gap configuration information via RRC signaling ensures the accuracy and stability of the configuration. Lower-level signaling involves direct communication at the physical layer. Receiving Gap configuration information via lower-level signaling allows for rapid response to network changes and reduces latency. The combined use of these two signaling methods ensures both the timeliness and accuracy of Gap configuration, achieving efficient and stable Gap management.
[0075] Furthermore, receiving Gap configuration information from the base station via lower-level signaling can include: receiving lower-level signaling from the base station via the UE, where the lower-level signaling includes header information and encoded Gap configuration information. The use of lower-level signaling, especially the inclusion of header information and encoded Gap configuration information, can improve transmission efficiency and security. The header information identifies the type and purpose of the signaling, while the encoded Gap configuration information can compress the amount of data transmitted, reducing bandwidth consumption. This design not only speeds up the transmission of Gap configuration information but also protects information security, preventing potential network attacks and data leaks, and enhancing the security and reliability of the wireless communication system.
[0076] In one embodiment, the method further includes sending an activation or deactivation request to the base station. The activation or deactivation request is used to request the activation or deactivation of one or more gaps, one or more gap types, or one or more gap IDs. The UE can proactively send activation or deactivation requests to the base station to indicate its current measurement needs. For example, when the UE enters power-saving mode, it can request to deactivate certain unnecessary gaps to save power consumption. Conversely, when the UE needs to perform additional measurement tasks, it can request to activate more gaps. This mechanism gives the UE greater control, enabling it to flexibly adjust gap configurations according to its own needs and network conditions, achieving fine-grained resource management.
[0077] In another embodiment, the method further includes handling the Gap conflict based on Gap information and Gap retention information when multiple Gaps conflict. In complex network environments, multiple Gaps may overlap in time, leading to Gap conflicts. In this case, the UE needs to determine how to handle these conflicts based on Gap information and Gap retention information. For example, if two Gaps have the same priority, but one Gap is marked as unchanged, the UE should prioritize executing that Gap. This conflict handling mechanism ensures that critical measurement tasks are completed preferentially under limited resource conditions, improving overall system performance and user experience.
[0078] Furthermore, handling Gap conflicts among multiple Gaps based on Gap information and Gap retention information can include processing Gap conflicts based on at least one of the following: Gap priority, Gap retention information, maximum Gap repetition period processing, Gap purpose, Gap granularity, Gap type, and Gap time-domain configuration. When handling Gap conflicts, the UE can comprehensively consider multiple factors such as Gap priority, retention information, purpose, granularity, type, and time-domain configuration to formulate the optimal execution strategy. For example, if two Gaps are used for emergency services and normal data transmission, respectively, even if the latter has a higher priority, the UE may prioritize the former based on retention information to ensure the continuity of emergency services. This multi-layered conflict handling mechanism not only solves the Gap conflict problem but also optimizes resource allocation, ensures the efficient completion of various measurement tasks, and improves the overall performance and user experience of the wireless communication system.
[0079] In 5G (NR) systems, the Measurement Gap is a dedicated time window configured by the base station (gNB) for the user terminal (UE). It allows the UE to suspend data transmission and reception on its current frequency and switch to other frequencies or standards (such as different frequency bands in LTE and NR) to perform neighbor cell measurements, supporting mobility management (such as handover and reselection). Gap configuration is used in the following scenarios:
[0080] Measurement of cells operating on the same frequency within the same system;
[0081] Measurement of cells with the same frequency but different frequencies within the same system;
[0082] Measurement of cells under L-type inter-system conditions;
[0083] Measurement gaps are configured by sending measurement gap parameters via RRC signaling (such as RRC Reconfiguration), for example:
[0084] Gap Pattern: A periodic time interval pattern, including:
[0085] Gap Length: Usually 3-6ms (6ms is commonly used for 5G).
[0086] Gap Offset: Determines the starting position of the first gap.
[0087] Gap Repetition Period: such as 40ms, 80ms, 160ms, etc.
[0088] Gap Type:
[0089] Per-UE Gap: A global gap for the entire UE (affecting all carriers).
[0090] Per-FR Gap: Local gaps for specific frequency ranges (FR1 or FR2) (introduced in 5G Rel-16 for greater flexibility).
[0091] A typical configuration example is as follows:
[0092] Mode 1: Gap Length = 6ms, Period = 40ms (suitable for low-frequency measurements).
[0093] Mode 2: Gap Length = 3ms, Period = 80ms (suitable for high-frequency, fast measurements).
[0094] In the R15 5G NR system, the measurement gap (MG) is divided into two types:
[0095] Per-UE Gap (global gap, affecting all carriers);
[0096] Per-FR Gap (local gap configured according to frequency range FR1 / FR2).
[0097] However, current measurement gap designs have some limitations that directly affect the implementation flexibility of the network and UE. To optimize Radio Resource Management (RRM) efficiency, Rel-17 introduces the following enhancements, including NetworkControl-led Small Gap (NCSG):
[0098] Network control gaps (NCSG);
[0099] Multiple concurrent and independent MG patterns;
[0100] Pre-configured MG mode based on BWP (Quick MG Configuration).
[0101] The core objectives of NCSG are: to reduce measurement interruptions to services by replacing traditional long gaps (6ms) with shorter gaps (e.g., 1ms or 0.75ms) to improve throughput; to dynamically adapt to UE capabilities by flexibly configuring the measurement based on UE hardware support (e.g., whether it supports gapless measurement or fast RF switching); and to optimize high-frequency (FR2) measurements by reducing synchronization and data scheduling limitations for millimeter-wave beam management requirements.
[0102] NCSG is implemented in the following way:
[0103] UE capability reporting and network configuration follow the NeedForGap mechanism of Rel-16:
[0104] The network configures the NCSG reporting function through the RRCReconfiguration or RRCResume message, which instructs the UE to report needforGap information. The network indicates the frequency point information that the UE needs to report.
[0105] The UE reports NCSG support capabilities in the RRCReconfigurationComplete or RRCResumeComplete message:
[0106] needForGapNCSG-InfoEUTRA: Report NCSG requirements for LTE bands.
[0107] needForGapNCSG-InfoNR: Report NCSG requirements for the NR band.
[0108] NCSG gap pattern design, 24 predefined NCSG patterns:
[0109] Visible Interruption Length (VIL):
[0110] FR1: 1ms (interruption 1ms before and after measurement).
[0111] FR2: 0.75ms (interruption 0.75ms before and after measurement).
[0112] Measurement Length (ML): During the ML period, the UE can continue to receive downlink (DL) or transmit uplink (UL) data.
[0113] New timing adjustment: Introduce a 0.75ms MG timing advance to accommodate short intervals.
[0114] Then, further enhancements were made in R18, which eliminated the need for even the NCSG gap type and required only a shorter interrupt. That is, when the UE has stronger Rx capabilities, only a few interrupts (such as those for frequency modulation) are needed to complete the measurement.
[0115] Thus, the gap types required for UE measurement can be divided into the following four categories:
[0116] 1. No gap, no interuption.
[0117] 2. No gap but with interuption, meaning interuption is required but a gap is not needed;
[0118] 3. NCSG Gap: and the NCSG Gap mentioned above;
[0119] 4. Normal Gap: The most common type of gap.
[0120] In 5G NR Rel-17, 3GPP introduced the concept of Concurrent Gap, aiming to further optimize the UE's measurement mechanism, especially in mobility management scenarios with multiple frequency bands and multiple standards coexisting. This feature addresses the limitations of traditional Measurement Gap, allowing the UE to perform multiple measurement tasks in parallel within a single gap, thereby improving efficiency and reducing service interruptions. In Rel-16 and earlier, the UE needed to configure independent measurement gaps for different frequency bands or RATs (such as NR FR1, FR2, LTE). If multiple frequency bands needed to be measured, the UE had to frequently switch gap modes, leading to a further decrease in throughput: multiple gaps overlapping would consume more service time. Measurement latency increased: measurements of different frequency bands needed to be completed serially.
[0121] As UE capabilities improve, high-end UEs may support multiple radio chains (such as simultaneously receiving FR1 and FR2 signals), but traditional gaps do not fully utilize this capability. Within the same measurement gap window, the UE can simultaneously measure multiple frequency bands or standards (such as NRFR1+FR2, or NR+LTE), instead of switching sequentially. Since a measurement gap can be shared by multiple frequency band groups, the UE switches radio chains by group within the gap.
[0122] Under this concept, the network can be configured with multiple gap patterns, each with its own priority. When multiple gap patterns conflict, the priority information determines which gap to retain. The association between these gap IDs and measurement frequencies indicates the relevant gap ID in the measurement object, thus identifying the gap corresponding to each measurement object.
[0123] The pre-configured measurement gap (MG) mode based on BWP (Fast MG Configuration), based on the technical specification (TS) 38.300 of Release 15 / R16, has overly strict rules for configuring measurement gaps. For example, for measurements based on the same-frequency synchronization signal block (SSB), if any portion of the user equipment's (UE) configured bandwidth (excluding the initial bandwidth portion of the BWP) does not contain the measured SSB, the network needs to configure a measurement gap. This means that even if the UE's active bandwidth portion already covers the SSB, the network cannot schedule the UE during the measurement gap. Therefore, pre-configured measurement gaps (MG) are introduced to avoid unnecessary interruptions and improve the efficiency of measurement gap utilization. In Release 17, PreconfiguredGap was introduced.
[0124] Under this mechanism, the network can configure GAPs per UE or per FR, and then indicate whether these GAPs are activated / deactivated by the Preconfigured Gap status in the configuration of each BWP. Specifically, when configuring the GAP, the "preconfigured indicator (preConfigInd)" indicates whether the measurement gap is a preconfigured measurement gap. The "preconfigured gap status (preConfGapStatus)" indicates whether the preconfigured measurement gap (i.e. the gap configured by the preconfigured indicator (preConfigInd)) is activated or deactivated when switching to the Bandwidth Part (BWP). If this field is configured, the user equipment (UE) should use the network control mechanism to activate and deactivate the preconfigured measurement gap; otherwise, the user equipment should use the autonomous activation / deactivation mechanism, as specified in Technical Specification (TS) 38.133
[14] . The first (leftmost) bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to the measurement gap with gap ID 2, and so on. A value of 0 indicates that the corresponding pre-configured measurement gap is disabled, and a value of 1 indicates that the corresponding pre-configured measurement gap is activated. If the corresponding measurement gap is not a pre-configured measurement gap, the user equipment should ignore this bit.
[0125] 2. The traditional MUSIM gap and its subsequent enhancements: With the evolution of 5G technology (such as 3GPP Release 17), the widespread adoption of Multi-USIM (MUSIM) devices (e.g., dual-SIM dual-standby phones) has presented new challenges to network and terminal design. These devices need to serve multiple USIMs (User Identity Modules) simultaneously, potentially involving different operators or network standards (e.g., 5G / 4G / 3G). Due to limitations in the terminal's radio frequency (RF) link, only one USIM can be active at a time, thus requiring fast time-sharing to enable multi-SIM services. Release 17 introduced the concept of the MUSIM Gap, with the following process:
[0126] Step 1: The network instructs the UE in the OtherConfig of Reconfiguration that it can report the UAI of the UE's MUSIM Gap;
[0127] Step 2: The UE reports the configuration information of the UE-suggested gap in the UAI, including periodic gap and non-periodic gap;
[0128] Step 3: Configure the network for the gap in the UE. This configuration can be based on the UAI information reported by the UE.
[0129] In steps two and three above, the periodic gap indicates the period of the gap, the length of the gap, and the offset of the starting point, while the non-periodic gap indicates the starting point of the gap and the length of the gap.
[0130] In Release 18, since the network can be configured with both MUSIM and the aforementioned measurement gaps simultaneously, a corresponding conflict resolution mechanism is needed when conflicts occur between these gaps. Therefore, the concept of priority and a maintenance mechanism were introduced for MUSIM gaps. Specific conflict resolution methods can be found in the section "Conflict Handling Methods for Various Gaps" below.
[0131] Traditional positioning gaps can have multiple gap patterns configured. Each gap pattern has a gap ID, gap period, gap length, and start point offset, etc. The network can activate or deactivate one or more gap patterns through MAC CE. The UE can also request the network to activate or deactivate one or more gap patterns.
[0132] (1) The location measurement gap activation / deactivation request MAC CE is identified by the eLCID (Extended Logical Channel Identifier) in the MAC subheader, which uses a fixed 8-bit format. Figure 4This is a schematic diagram of the positioning measurement gap activation / deactivation request MAC CE structure in related technologies, such as... Figure 4 As shown, it includes:
[0133] Positioning Measurement Gap ID: Used to indicate the pre-configured positioning measurement gap identifier. Field length: 4 bits;
[0134] Activation / Deactivation Indicator (A / D): Used to control the activation status of positioning measurement gap. Setting it to 1 indicates activation, and other values indicate deactivation. Field length: 1 bit.
[0135] Reserved bit (R): Reserved field, always set to 0.
[0136] (2) The positioning measurement gap activation / deactivation command MAC CE is identified by the eLCID (Extended Logical Channel ID) in the MAC sub-header, which has a fixed length of 8 bits. Figure 5 This is a schematic diagram of the MAC CE structure for positioning and measuring gap activation / deactivation commands in related technologies, such as... Figure 5 As shown, it includes:
[0137] Positioning MG ID: This field indicates the pre-configured positioning measurement gap identifier, which is 4 bits long.
[0138] A / D (Activation / Deactivation Indicator): This field controls the activation or deactivation of the positioning measurement gap: setting it to 1 indicates activation, and other values indicate deactivation. The field length is 1 bit.
[0139] R (Reserved bit): Reserved bit, always set to 0.
[0140] Various methods for handling gap conflicts, including:
[0141] Conflict handling between MUSIM Gap instances is considered to be in conflict if at least one of the following conditions is met: MUSIM Gap instances completely overlap in the time domain, or MUSIM Gap instances partially overlap in the time domain, or the time interval between two MUSIM Gap instances is equal to or less than 4ms.
[0142] The time interval between two MUSIM Gap instances is defined as the time difference between the end time of the first Gap instance and the start time of the second Gap instance (provided that the first MUSIM Gap instance is earlier than the second in time).
[0143] If "keep solution" is not used, the periodic MUSIM Gap instance will be discarded when it conflicts with an aperiodic MUSIM Gap instance. When a conflict occurs between periodic MUSIM Gap instances, conflict resolution will be based on the assigned MUSIM Gap priority. Conflicts are processed in descending order of priority, with the highest priority Gap instance being retained and the lower priority Gap instances being discarded.
[0144] A conflict between a MUSIM Gap and a measurement Gap instance is considered to occur if at least one of the following conditions is met:
[0145] The MUSIM Gap and the measurement Gap instance completely overlap in the time domain, or the MUSIM Gap and the measurement Gap instance partially overlap in the time domain, or the time interval between the MUSIM Gap and the measurement Gap instance is equal to or less than 4ms.
[0146] The time interval between two Gap instances is defined as the time difference between the end time of the first Gap instance and the start time of the second Gap instance (provided the first Gap instance is earlier than the second). A Gap instance can be a MUSIM Gap instance or a measurement Gap instance. The conflict resolution rules are as follows:
[0147] Measurement gap instances that conflict with non-periodic MUSIM gaps will be discarded.
[0148] For MUSIM gaps that are configured and assigned priorities via GapConfig-r17 and conflict with measurement gaps:
[0149] Conflict resolution is based on the allocation priority, and conflicts are handled in descending order of priority.
[0150] In each conflict, the highest priority Gap instance (MUSIM Gap or Measurement Gap) is retained, and the lower priority Gap instances are discarded.
[0151] The remaining MUSIM Gap conflicts are handled according to clauses 9.1.10.3 and 9.1.10.4. If "keepsolution" is configured, "keep solution" is applied to the remaining MUSIM Gap after resolving the measurement Gap and MUSIM Gap conflicts based on priority.
[0152] For MUSIM gaps that are configured via GapConfig or via GapConfig-r17 but without assigned priority, and for conflicts with measurement gaps:
[0153] Conflict resolution is performed based on the Measurement Gap Repetition Period (MGRP) of the conflict gap, and the conflicts are processed in descending order of MGRP length.
[0154] In each conflict, the gap instance with the longer MGRP (MUSIM Gap or Measurement Gap) is retained, and the gap instance with the shorter MGRP is discarded.
[0155] The remaining MUSIM Gap conflicts are handled in the same way as the MUSIM Gap conflicts described above. If "keep solution" is configured, then after resolving the measurement Gap and MUSIM Gap conflicts based on MGRP, "keep solution" is applied to the remaining MUSIM Gap.
[0156] As can be seen from the above, the main methods for conflict resolution are as follows:
[0157] 1. Priority-based solution.
[0158] For MUSIM Gap, the UE can assign a priority (absolute gap priority) to all periodic gaps, and the network can configure priorities to maintain relative priorities. Lower-priority gaps will be dropped. Aperiodic gaps have the highest priority (higher than periodic MUSIM gaps and measurement gaps).
[0159] Measurement gaps are selected, and gaps with lower priority are discarded.
[0160] 2. The Period Length Based Solution is only applicable to conflicts between MUSIMGap and measurement Gap (when no Gap priority is assigned); Gaps with longer MGRP (Measurement Gap Repetition Period) have higher priority.
[0161] 3. The Keep Indication Based Solution applies only to MUSIM gaps, meaning it retains all conflicting gaps (including periodic and aperiodic MUSIM gaps). For conflicts between MUSIM gaps and measurement gaps (when gap priorities are assigned): the priority-based drop rule is executed first, followed by the keep rule. For conflicts between MUSIM gaps and measurement gaps (when no gap priorities are assigned): the MGRP-based drop rule is executed first, followed by the keep rule.
[0162] When transmitting gap information on the CU-DU interface, if the CU-DU RRC information element (IE) of the UE CONTEXT SETUP REQUEST message (or UE CONTEXT MODIFICATION REQUEST) message contains a MeasConfig IE, the gNB-DU should determine that a measurement configuration change needs to be applied. When the MeasConfig IE contains a measObjectToAddModList IE, the frequency points listed therein will be activated. At this time, the gNB-DU needs to independently determine whether a measurement gap needs to be configured. If configuration is required, the measurement gap configuration scheme should be fed back to the gNB-CU through the MeasGapConfig IE in the DU-CU RRC information element of the UE CONTEXT SETUP RESPONSE message (or UE CONTEXT MODIFICATION RESPONSE message).
[0163] When the CU to DU RRC information element of the UE CONTEXT SETUP REQUEST message (or UE CONTEXTMODIFICATION REQUEST) contains NeedForGapsInfoNR IE, if the gNB-DU supports this function, it should be processed in accordance with the TS 38.331[8] specification. Similarly, if NeedForGapNCSG-InfoNR IE exists and the gNB-DU supports this function, it should also be executed in accordance with the TS 38.331[8] specification.
[0164] If the CU to DU RRC information unit contains NeedForGapNCSG-InfoEUTRA IE, and gNB-DU supports it, the relevant operations should be performed in accordance with the TS 38.331[8] specification. When NeedForInterruptionInfoNR IE exists, gNB-DU that supports this function also needs to be configured and processed in accordance with the TS 38.331[8] specification.
[0165] If the CU to DU RRC information element (IE) contained in the UE CONTEXT SETUP REQUEST message or the UE CONTEXT MODIFICATION REQUEST message contains a MUSIM-GapConfig IE, then the gNB-DU, if supporting this function, should decide whether to use this IE for MUSIM gap configuration, or select another configuration scheme based on the received UE Assistance Information IE. When the gNB-DU selects a MUSIM gap configuration different from the received UE Assistance Information IE, it must feed back the selected MUSIM gap configuration information to the gNB-CU through the MUSIM-GapConfig IE in the DU to CU RRC information element of the UE CONTEXT SETUP RESPONSE message (or the UE CONTEXT MODIFICATION RESPONSE message).
[0166] If the CU-DU RRC information element does not contain a MUSIM-GapConfig IE, the gNB-DU supporting this function should, based on the received UEAssistanceInformation IE, send the selected MUSIM gap configuration to the gNB-CU via the MUSIM-GapConfig IE in the DU-CU RRC information element of the UE context setup response message. When the gNB-CU receives the MUSIM-GapConfig IE, it should adopt this configuration value.
[0167] Of these three processes, the first is the traditional MeasurementGap configuration process, the second is the Gap (need for gap) indication process, and the third is the MUSIM Gap request and configuration process.
[0168] There are two ways to report Gap from the network configuration UE:
[0169] There are two methods in the relevant technologies for configuring the UE to report Gap-related information, including:
[0170] Method 1: Indicate this in the RRC recovery or reconfiguration message, such as RRCResume or ReconfigurationMessage. This message can carry some information, such as frequency point information, so that the UE can report whether gap information needs to be reported on these frequency points and the serving frequency points.
[0171] Method 2: Explicitly or implicitly indicate in the "Other configure" section of the RRC Reconfiguration message: for example, instruct the UE to report the MUSIM Gap's timer disabling, priority indication, etc.
[0172] The difference between the two mechanisms is that Method 1 has a higher priority than Method 2, so it is sent immediately with a complete message, resulting in less latency, and it is still effective for networks that have not yet implemented User Assistance Information (UAI) functionality.
[0173] Based on the auxiliary information reported by the UE, the auxiliary information reported by the UE to the network in the relevant protocols includes the following two categories:
[0174] For MUSIM, this includes: the gap pattern, start point, and gap length of aperiodic gaps (e.g., (MUSIM) gaps); gap priority indication: the user equipment (UE) can indicate a priority preference for (MUSIM) gaps; and gap retention indication: indicating the retention of gaps with different priorities.
[0175] For (MUSIM) cases, only NR Gap requirement information (NeedForGapsInfoNR-r16) is included. For Gap requirements (needforGap), the following are included: Gap type: no gap without interruption / no gap with interruption / NCSG / normal gap; Frequency type: for co-frequency, it is each serving cell, and for inter-frequency (including different radio access technologies (Inter RAT)), it is each frequency band.
[0176] From the perspective of the gaps in network configuration of UEs, it includes:
[0177] Gap types include:
[0178] Normal Measurement Gap;
[0179] NCSG Gap (and no-gap, no-interruption mode);
[0180] MUSIM Gap;
[0181] Positioning Gap;
[0182] Pre-Configured Gap: Supports configuration based on BWP level or location requirements;
[0183] Concurrent Gap.
[0184] Gap attributes include:
[0185] Gap granularity: UE-based gap / frequency band (FR)-based gap (such as measurement gap);
[0186] Gap Time Domain Configuration;
[0187] Gap priority configuration (e.g., measuring Gap / MUSIM Gap);
[0188] Gap configuration retention (such as MUSIM Gap);
[0189] Gap activation and deactivation, based on BWP, are performed via RRC configuration / MAC CE or UE self-execution.
[0190] In 5G discussions, various scenarios require the network to configure gaps for the UE, such as MUSIM (Multi-SIM Device) scenarios, positioning scenarios, and measurement scenarios. Furthermore, different versions of 5G have upgraded the gap configuration for different scenarios, leading to chaotic 5G gap configuration and an inability to consider all gap requirements, resulting in low gap configuration / usage efficiency. Facing the more diverse scenarios of 6G, a unified gap design architecture is needed. Currently, gap priority configurations in related technologies are designed within a single gap type; for example, the Measurement Gap has its own priority, and the MUSIM Gap has its own priority, rather than a unified priority design. This results in complex designs when gap conflicts occur.
[0191] Only the MUSIM Gap allows the UE to provide auxiliary information to the network. Other Gap types, such as measurement Gap and positioning Gap, cannot provide auxiliary information to the UE. If the above unified Gap architecture design is used, the base station needs the UE to provide more comprehensive auxiliary information.
[0192] Figure 6 This is a schematic diagram of a unified Gap architecture according to embodiments of this application, such as... Figure 6 As shown, the unified Gap architecture can be used for UE to report auxiliary Gap information and for configuring Gap information for UE. The unified Gap architecture includes the following:
[0193] The Gap list (GapIDList) contains all the Gap information, and each Gap includes the following configuration:
[0194] Gap applications include: RRM, MUSIM, positioning, sensing, AI, etc.
[0195] Gap type: For example, whether it is pre-configured, dynamically activated, semi-statically configured, or static.
[0196] Gap granularity: for example, based on UE level, Frequency Range level, Band Group level, Cell Group level, Cell level, Carrier level, BWP level, etc.;
[0197] Gap time domain configuration, such as periodic, aperiodic, and small periods contained in large periods;
[0198] Gap priority configuration: This means giving all gaps the same priority.
[0199] Keep information identifies which gaps need to be kept, without prioritizing them. This keep information can be used for a variety of different purposes.
[0200] (2) Use the above process 3 as the basic process (but the above unified Gap architecture can also use the above processes 1 and 2), that is, the UE can provide auxiliary information for various Gap purposes, which is convenient for the network to make unified configuration.
[0201] 1. Unify the Gap List in the Gap architecture, such as Figure 6 As shown, the Gap list (GapIDList), which contains all the Gap information, includes the following configuration for each Gap:
[0202] Gap applications: RRM, MUSIM, positioning, sensing, AI, etc.;
[0203] Gap types: pre-configured, dynamically activated, semi-statically configured, static;
[0204] Gap granularity: based on UE level, frequency range level, band group level, cell group level, cell level, carrier level, BWP level, etc.
[0205] Gap time domain configuration: periodic, non-periodic, etc.;
[0206] Gap priority configuration: All gaps are given a uniform priority. This information can be configured by the network to the UE, or it can be provided by the UE to the network (the network can refer to this auxiliary information provided by the UE to make relevant configurations).
[0207] Gap Usage: A gap can be used for one or more different purposes, and different gaps can be used for the same or different purposes. These purposes can include RRM, MUSIM, positioning, sensing, AI, etc. Each purpose can be further refined to finer granularity. For example, RRM can be further specified as NCSG, same-frequency measurement, different-frequency measurement, different-RAT measurement, etc. MUSIM can be further specified as being used for paging monitoring, synchronization, system message monitoring, network connection establishment, etc. The protocol can limit the maximum number of gaps, restricting the total number of gaps or the number of gaps for each purpose. When reporting capabilities, the UE can indicate the maximum number of gaps it supports, the number of gaps supported for each purpose, or the combination types of various supported gap numbers, such as combination 1 (2 measurement gaps + 2 MUSIM gaps), combination 2 (2 measurement gaps + 1 MUSIM gap + 1 positioning gap), etc.
[0208] Gap types include: Static Gap: Similar to traditional Gap / Gap type / ID configuration, it takes effect once configured and remains so until it is released by the network or modified; Semi-persistent Gap: After the Gap / Gap type / ID is configured, it is activated and deactivated by signaling, or activation and deactivation instructions can be given during configuration. Activation / deactivation signaling includes: lower-level control signaling (i.e., layers lower than RRC), such as the Media Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI) to support it. User Equipment (UE) can also indicate its preference for activating Gap modes for this mechanism; this indication can be RRC signaling or lower-level control signaling. The UE can send activation / deactivation requests to the network, which can target one or more Gaps or Gap types. As mentioned earlier, one or more Gaps refer to one or more Gaps of the same type or under the same Gap ID. For example, a Gap with a period of 40ms means there is a Gap every 40ms; this can indicate one or more Gaps within this period. Activating or deactivating one or more Gap types means activating or deactivating all Gaps corresponding to one Gap ID, or all Gaps corresponding to multiple Gap IDs.
[0209] For example, through RRC signaling, lower-level control signaling (i.e., a layer lower than RRC), Medium Access Control (MAC) control unit (CE), or downlink control information (DCI); the UE's indication or the network's activation / deactivation indication can be different from the configuration granularity of the Gap itself (see the granularity below); the lower-level control signaling or MAC CE can be implemented by including an encoded container in a lower-level SDU.
[0210] For example, using MAC CE. Gap activation / deactivation commands (or UE requests) are identified via MAC CE through certain indications in the MAC sub-header (e.g., logical channel ID). Figure 7 This is a schematic diagram of the GapID bit Map according to an embodiment of this application, as shown below. Figure 7 As shown, GapID bit Map: This field indicates the corresponding Gap ID. Each bit corresponds to one Gap. For example, if a system is configured with 6 Gap IDs, the first bit corresponds to Gap ID 1, and so on. This field controls the activation or deactivation of the Gap: setting it to 1 indicates activation, and other values indicate deactivation. R (Reserved bit): Reserved bit, fixed at 0.
[0211] For example, using RRC signaling, UE requests can be reported via UAI (UE assistance information). A GapID bit map is generated: this field indicates the corresponding Gap ID, with each bit corresponding to one Gap. For example, if a system is configured with 6 Gap IDs, the first bit corresponds to Gap ID 1, and so on. This field controls the activation or deactivation of the Gap: setting it to 1 indicates activation, and other values indicate deactivation. Network configuration is similar, using a GapID bit map (or GapIDStatus bit map): this field indicates the corresponding Gap ID, with each bit corresponding to one Gap. For example, if a system is configured with 6 Gap IDs, the first bit corresponds to Gap ID 1, and so on. This field controls the activation or deactivation of the Gap: setting it to 1 indicates activation, and other values indicate deactivation. The above describes the method using a bit map; it can also be indicated using a displayed Gap ID list.
[0212] Dynamic: This means that after configuring one or more Gap types or Gap IDs, the network can dynamically activate or deactivate one or more Gaps. These one or more Gaps can come from a single Gap type / ID or from multiple Gap types / IDs. As mentioned earlier, one or more Gaps refer to one or more Gaps under the same type or the same Gap ID. For example, a Gap with a period of 40ms means there will be a Gap every 40ms. Here, it can indicate one or more Gaps within this periodic Gap. Activating or deactivating one or more Gap types means activating or deactivating all Gaps corresponding to a Gap ID, or all Gaps corresponding to multiple Gap IDs. Activation or deactivation can also indicate whether to skip a Gap. The instruction can be for one or more gaps of one or more gap types / IDs, or for gaps under all gap types / IDs, or for all gaps under one or more gap types / IDs; the instruction can indicate the start of skipping, the end of skipping, or the skipping of one or more gaps or gap types / IDs after the instruction, or the skipping of gaps or gap types / IDs within a certain time period. This instruction can be RRC / LLCE / DCI, etc.; the UE can report auxiliary information on whether to skip gaps, which can be for gaps of one gap type / ID, or for gaps under all gap types / IDs, or for all gaps under one or more gap types / IDs; the UE can also indicate whether to skip one or more gaps or gap types / IDs, or indicate the skipping of gaps or gap types / IDs within a certain time period, or indicate the start or end of skipping for gaps under one or more gap types / IDs. This instruction can be RRC / LLCE / UCI, etc.
[0213] Conditional Gap: This refers to a gap that only takes effect when certain conditions are met. When configuring a gap, the network can configure corresponding conditions, which can apply to one or more gap types / IDs. When the conditions are met, the network / UE initiates the use of the corresponding gap or gap type / ID. Alternatively, when a certain type of service (e.g., sensing, AI, etc.) is triggered, the corresponding gap / gap type / ID is activated. Multiple different conditions can also be set for a single gap / gap type / ID; for example, different conditions can correspond to different usage methods for that gap / gap type / ID (e.g., usage ratio, where condition 1 corresponds to usage ratio 1, condition 2 corresponds to usage ratio 2, and the usage ratio is the proportion of the gap actually used by the UE).
[0214] Preconfiguration refers to the pre-configuration type. Under this type, the UE can activate / deactivate the corresponding Gap / Gap type / ID based on the network configuration, or the UE can activate / deactivate the corresponding Gap / Gap type / ID independently. UE management can be based on per BWP or per CC granularity. That is, the actual management granularity (e.g., the granularity of network configuration activation / deactivation) is inconsistent with the granularity of Gap configuration. For example, the granularity of Gap configuration is at the UE level, but the actual activation / deactivation is at the per BWP level. When the network configuration is used to activate / deactivate the corresponding Gap / Gap type / ID, it can be indicated through bit mapping, with each bit corresponding to a different Gap / Gap type / ID.
[0215] Autonomous Gap, or automatic gap, refers to the number of gaps the UE can use within a certain period, denoted as T, and the maximum length of each gap, denoted as L. The UE can also indicate suggested parameter values such as T / N / L.
[0216] Gap granularity: for example, based on UE level, Frequency Range level, Band Group level, Cell Group level, Cell level, Carrier level, BWP level, etc.
[0217] Per Carrier (Per CC): This means that the Gap / or Gap type / ID is for one or more carriers. For example, in a MUSIM scenario, the Gap can be set for each carrier based on the current operating frequency band of another network. In this way, the corresponding carrier information can be indicated. It can also include related frequency information (such as carrier component (CC) index, absolute radio frequency channel number (ARFCN), synchronization signal block / signal measurement timing configuration (SSB / SMTC) / channel state information reference signal (CSI-RS) configuration index, etc.).
[0218] Each carrier group (Per CG): for example, MCG (Master Cell Group), SCG (Secondary Cell Group);
[0219] Per band group: Radio frequency (RF) is designed based on band groups, so the frequency bands in the band group will be affected simultaneously. In this method, the corresponding band group information can be indicated, for example: Low Band (LB): 617 MHz to 960 MHz; Mid / High Band (MHB): 1.7 GHz to 2.7 GHz; Ultra High Band (UHB): 3.3 GHz to 5 GHz.
[0220] Each cell, i.e., the gap or gap type / ID, is used only for one or more cells. In this scenario, the corresponding cell index can be indicated.
[0221] Each BWP: This refers to the configuration based on each BWP, which can indicate the corresponding cell ID and BWP ID;
[0222] Distinguish between uplink (UL) and downlink (DL): allow only downlink reception or only uplink transmission;
[0223] Any combination of the above particle sizes.
[0224] Gap time-domain configuration, such as periodic and aperiodic, can be further extended to include the following gap types in addition to periodic and aperiodic gaps.
[0225] Figure 8 This is a schematic diagram of the Gap type extension according to the embodiments of this application. Figure 1 ,like Figure 8 As shown, larger cycles further contain smaller cycle-type gaps. For example, gaps 1 and 2 in the diagram repeat with cycle T1. Gap 1 / 2 further contains sub-gaps that repeat with cycle T2. These sub-gaps can also have different cycles, such as T2 / T3.
[0226] Figure 9 This is a schematic diagram of the Gap type extension according to the embodiments of this application. Figure 2 ,like Figure 9 As shown, a gap that repeats over a period of time can be defined as a start time, an end time, or the duration from the start time to the end time, or the number of repetitions.
[0227] Gap priority configuration: This means giving all gaps the same priority.
[0228] In traditional solutions, gap priorities are set individually for each gap purpose; for example, measurement gaps have measurement gap priorities, and MUSIM gaps have MUSIM gap priorities. Priorities can be set for one, multiple, or all gap purposes. Multi-level priority mechanisms can also be implemented, such as first setting priorities according to different purposes (e.g., measurement > MUSIM > positioning), and then setting sub-priorities under each purpose, which are only used within their respective purposes. The overall mechanism for combining priorities with Keep info usage is described below. Features of the aforementioned gaps can also be used interchangeably; that is, one feature can be a sub-feature of another. For example, when a gap is used for multiple different purposes, other features (such as granularity features) can be assigned to each purpose.
[0229] 2. Unify the handling of Keep Info and Priority in the Gap architecture.
[0230] In related technologies, gap priorities are set separately for each gap application; for example, measurement gaps have a specific priority, while MUSIM gaps have a different priority. Under a unified gap architecture, priority handling can be implemented in the following ways:
[0231] Method 1: Consider only gap priority-based processing (this method can also be used without keep info), i.e., it does not adopt a keep / maximum gap repetition period (MGRP) based mechanism. For example, the network always configures priorities and always provides different priorities. When a gap collision occurs, the UE follows the priority order, with higher-priority gaps knocking out lower-priority gaps. Specifically, the network configures priorities for all gaps (possibly excluding non-continuous reception gap groups (NCSG) and pre-configured gaps); if priorities are only configured for some gaps, gaps without configured priorities can be considered the lowest priority.
[0232] Method 2: Priority-based and KeepInfo-based approach, where keepInfo can also be implemented using the same priority method. Option 2a: Allows the network to configure the same priority (priority + keep) for the gaps it intends to retain; Option 2b: Explicit keep indication. This specifies which gaps / gap types / IDs can be retained, for example, by gap ID; it specifies which types, granularities, or purposes of gaps can be retained. Retention means that within these gaps set to keep, priority information can be completely retained. Gaps not set to keep are still discarded based on priority. See Table 1.
[0233] Table 1
[0234] Gap Priority 1 2 3 4 Gap ID Gap 2 Gap 3 Gap 1 Gap 4
[0235] The network intends to retain Gap 3 and Gap 4. Using option 2a, Gap 4 must be configured with priority 2, making it higher than Gap 1. Using option 2b, some Gap opportunities in Gap 3 will be discarded based on Gap 2, while some Gap opportunities in Gap 4 will be discarded based on both Gap 2 and Gap 1. The remaining Gap opportunities in Gap 3 and Gap 4 will then be retained.
[0236] Method 3: Priority + Maximum Gap Repetition Period (MGRP). Gaps with configured priorities have higher priority than those without; for gaps without configured priorities, gaps with longer Maximum Gap Repetition Period (MGRP) have higher priority.
[0237] Method 4: Priority + Keep + Maximum Gap Repetition Period (MGRP). For gaps with a keep instruction, after performing a discard operation based on priority, the remaining gaps are retained (gaps with a keep instruction will not perform a discard operation based on priority within the keep group); for gaps with neither priority nor keep instruction, gaps with a longer maximum gap repetition period (MGRP) have higher priority.
[0238] The above only uses priority, keep, and maximum gap repetition period (MGRP) as examples. However, as mentioned earlier, when handling gap conflicts, factors such as gap purpose, gap granularity, gap type, gap granularity, and gap time domain configuration can also be combined. For example, certain purposes can be defined, or certain types of gaps can have high priority.
[0239] Figure 10 This is a flowchart of the Gap configuration according to an embodiment of this application, such as... Figure 10 As shown, it includes:
[0240] Step S1001: The network instructs the UE in OtherConfig of Reconfiguration that the UE can report the UAI of the UE's MUSIMGap;
[0241] Step S1002: The UE reports the configuration information of the UE-suggested gap in the UAI, including periodic gap and non-periodic gap;
[0242] In step S1003, the network sends the configured Gap configuration information to the UE. The Gap configuration information can be configured with reference to the UAI information reported by the UE.
[0243] 1. The network instructs the UE to report the preferred gap configuration.
[0244] There are two methods in the relevant technologies for configuring the UE to report Gap-related information, including:
[0245] Method 1: Indicate this in the RRC recovery or reconfiguration message, such as RRCResume or ReconfigurationMessage. This message can carry some information, such as frequency point information, so that the UE can report whether gap information needs to be reported on these frequency points and the serving frequency points.
[0246] Method 2: Explicitly or implicitly indicate in the "Other configure" section of the RRC Reconfiguration message: for example, instruct the UE to report the MUSIM Gap's timer disabling, priority indication, etc.
[0247] The difference between the two mechanisms is that Method 1 has a higher priority than Method 2, so it is sent immediately with a complete message, resulting in less latency, and it is still effective for networks that have not yet implemented User Assistance Information (UAI) functionality.
[0248] Enhancements to the current mechanism: A unified configuration for "instructing the UE to report Gap-related information" can be implemented (e.g., in "Other Configurations"). This can be achieved through RRC messages such as Resume / Reconfigure / System Messages. Additional instructions can be added to specify where "User Assistance Information (UAI)" should be reported, such as only in the completion message, only in UAI, or both. The network can modify this instruction according to its own needs. For example, when the network currently requires a certain type / purpose of Gap, it can require the UE to immediately report that type / purpose of Gap through the corresponding completion message (e.g., Resume / Reconiguration Complete). For instance, in the first configuration, the UE is expected to report measurement-related Gap information in the complete message; in the second configuration, the UE is expected to report AI / sensing / MUSIM / location-related Gap information in the compete message.
[0249] Request the user equipment (UE) to report more auxiliary information. In addition to the traditional auxiliary information used for MUSIM Gap configuration, the UE can also be instructed to report auxiliary information for other purposes, such as measurement, positioning, sensing, AI, etc.
[0250] Network to UE (NW to UE): The network can provide relevant information to the UE so that the UE can report relevant auxiliary information. For example, it can carry information such as the synchronization signal block / signal measurement timing configuration (SSB / SMTC) configuration for inter-frequency measurements, or the channel state information reference signal (CSI-RS) configuration to the UE.
[0251] The network provides configuration instructions for the number of gaps, such as the number of gaps used for various purposes, the total number of gaps, or instructions on which gaps need to be reported.
[0252] 2. The UE reports auxiliary information for Gap configuration.
[0253] In the relevant protocols, the auxiliary information reported by the UE to the network includes the following two categories:
[0254] For MUSIM, the gap pattern, start point, and gap length of aperiodic gaps (e.g., (MUSIM) gaps); gap priority indication: the user equipment (UE) can indicate a priority preference for (MUSIM) gaps; gap retention indication: indicating the retention of gaps with different priorities;
[0255] In the case of (MUSIM), only "NR's Gap Requirement Information (NeedForGapsInfoNR-r16)" is included.
[0256] For gap requirements, gap types are: no gap with no interruption / no gap with interruption / NCSG / normal gap; frequency types are: for intra-frequency use, each serving cell; for inter-frequency use (including different radio access technologies (Inter RAT)), each frequency band.
[0257] Enhancements to the current mechanism: The UE can report more auxiliary information so that the network can configure gaps in positioning, measurement, sensing, AI, etc. This auxiliary information can be in User Assisted Information (UAI) or other RRC messages such as RRC ResumeComplete, RRC reconfiguration Complete, etc.
[0258] Option 1: Provide auxiliary information for gaps for different purposes (e.g., gaps for positioning, measurement, sensing, AI, MUSIM).
[0259] Auxiliary information for gaps of different purposes (or different granularities, different types, different time-domain configuration methods, etc.) can be reported separately. Gaps of different purposes may have overlapping parts, and the following auxiliary information can be reported for gaps of different purposes.
[0260] Gap type: For example, whether it is pre-configured, dynamically activated, semi-statically configured, or static.
[0261] Gap granularity: for example, based on UE level, Frequency Range level, Band Group level, Cell Group level, Cell level, Carrier level, BWP level, etc.
[0262] For different granularities, granularity-related information can be further included, such as frequency range information, band group information, cell group information, cell information, carrire information, and BWP information.
[0263] It may also include relevant frequency information (such as carrier component (CC) index, absolute radio frequency channel number (ARFCN), synchronization signal block / signal measurement timing configuration (SSB / SMTC) / channel state information reference signal (CSI-RS) configuration index, etc.).
[0264] Gap time-domain configuration, such as periodic, aperiodic, gaps that contain smaller periods within a larger period, gaps that repeat over a period of time, etc.
[0265] Gap priority configuration: This means giving all gaps the same priority.
[0266] Keep information.
[0267] The network side determines the gap configuration for the UE by combining the auxiliary information of each gap.
[0268] Among the aforementioned auxiliary information, gap requirement information can be combined with suggested measurement gap auxiliary information. That is, providing gap information for a certain frequency point indicates that a gap is needed.
[0269] Option 2: Use a unified structure to report auxiliary information. A single user auxiliary information indicator applies to various gaps. Similar to the unified gap structure mentioned above, this means users submit a unified gap configuration request based on their various gap needs.
[0270] Gap uses: such as RRM, MUSIM, positioning, sensing, AI, etc. (one gap can be used for multiple purposes).
[0271] Gap type: For example, whether it is pre-configured, dynamically activated, semi-statically configured, or static.
[0272] Gap granularity: for example, based on UE level, Frequency Range level, Band Group level, Cell Group level, Cell level, Carrier level, BWP level, etc.
[0273] For different granularities, granularity-related information can be further included, such as frequency range information, band group information, cell group information, cell information, carrire information, and BWP information.
[0274] It may also include relevant frequency information (such as carrier component (CC) index, absolute radio frequency channel number (ARFCN), synchronization signal block / signal measurement timing configuration (SSB / SMTC) / channel state information reference signal (CSI-RS) configuration index, etc.).
[0275] Gap time-domain configuration, such as periodic, aperiodic, gaps that contain smaller periods within a larger period, gaps that repeat over a period of time, etc.
[0276] Gap priority configuration: This means giving all gaps the same priority.
[0277] Option 3: A hybrid option based on Options 1 and 2. For example, some gaps for certain purposes are reported together, while gaps for other purposes are reported separately; for example, UE MUSIM GAP 1 and 2 measurements require Gap 3, and Positioning Gap 4 are as follows:
[0278] Figure 11 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 1 ,like Figure 11 As shown, the UE reports the pattern of each of the above gaps respectively.
[0279] Figure 12 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 2 ,like Figure 12 As shown, it is unified into a Gap type / ID. In some scenarios, it may be unified into multiple Gap types / IDs.
[0280] Figure 13 This is a schematic diagram of GAP reporting according to an embodiment of this application. Figure 3 ,like Figure 13 As shown, the gap between MUSIM and meas is unified. At this time, when the UE reports, the unified gap and the positioning gap can be reported separately.
[0281] The above solutions can also be used on the network configuration side. Solution 1 is the traditional solution, Solution 2 is a unified GAP architecture configuration solution, and Solution 3 is a unified GAP architecture configuration solution based on some GAP uses / types.
[0282] When configuring gaps for the UE, the network can use a unified gap architecture, which can be transmitted via RRC signaling or via lower-level signaling (below the RRC layer). During configuration, the network can also uniformly configure some or all gaps.
[0283] In this application embodiment, the impact on other interfaces, the enhancement of interface processes, and the reporting of UE capabilities include:
[0284] 1. Impact on other interfaces: In related technologies, regarding "Gap information transmission on the CU-DU interface," it can be seen that gaps for various purposes are managed separately on the CU-DU interface. However, by using a unified gap structure, the CU and DU interfaces can also transmit this unified gap architecture. Specifically:
[0285] If the CU to DU RRC information element (IE) contained in the UE CONTEXT SETUP REQUEST message or the UE CONTEXT MODIFICATION REQUEST message contains a Unified-GapConfig IE, then the gNB-DU, if supporting this function, should decide whether to use this IE for gap configuration or select another configuration scheme based on the received UE Assistance Information IE. When the gNB-DU selects a gap configuration different from the received UE Assistance Information IE, it must feed back the selected gap configuration information to the gNB-CU through the Unified-GapConfig IE in the DU to CU RRC information element of the UE CONTEXT SETUP RESPONSE message (or the UE CONTEXT MODIFICATION RESPONSE message).
[0286] If the CU-DU RRC information element does not contain a Unified-GapConfig IE, the gNB-DU supporting this function should, based on the received UEAssistanceInformation IE, send the selected Gap configuration to the gNB-CU via the MUSIM-GapConfig IE in the DU-CU RRC information element of the UE context establishment response message. When the gNB-CU receives the Unified-GapConfig IE, it should adopt this configuration value.
[0287] Similarly, this unified gap architecture can also be used for transmission on the Xn port, such as handover, and transmission between nodes under dual links.
[0288] 2. Process Enhancement: In related technologies, "Gap Information Transmission on the CU-DU Interface" shows that the CU is the signaling processing center, while the actual gap is controlled by the DU. Interaction between the CU and DU is required, and the generation of the gap configuration is completed at the DU.
[0289] Interaction between CU and DU will introduce additional latency. To reduce this latency, a lower-level signaling transmission mechanism can be introduced. Figure 14 This is a flowchart of a DU-based Gap configuration according to an embodiment of this application, such as... Figure 14 As shown, it includes:
[0290] The Gap UAI report config contains the same content as the "Gap configuration that the network instructs the UE to report" in Part 2. However, here it is directly encoded and decoded by the DU and sent. The underlying signaling from the DU to the UE includes header information and encoded Gap UAIreport config information.
[0291] UAI or Gap preference information is sent directly to DU, which uses underlying signaling to send it. The underlying signaling includes header information and encoded Gap preference information.
[0292] Figure 15 This is a schematic diagram of the underlying signaling according to an embodiment of this application, such as... Figure 15 As shown, GapConfig contains the same content as the unified Gap architecture described above, but here it is directly encoded and decoded by the DU and sent. The underlying signaling from the DU to the UE includes header information and encoded GapConfig information.
[0293] 3. UE capability reporting: UE capabilities can report the following information:
[0294] Whether a unified gap architecture is supported can also be implicitly indicated by certain capabilities under the unified architecture, such as the configuration mentioned earlier that indicates the maximum number of gaps it supports, the number of gaps supported for each purpose, or the combination of various gap numbers it supports.
[0295] Support unified gap configuration (including UE reporting) for which gap uses (or types, granularity, and other characteristics);
[0296] Does it support gap configuration based on underlying signaling?
[0297] Which gap types are supported, such as pre-configured, dynamically activated, semi-statically configured, or statically configured;
[0298] Supported gap granularities: such as UE-level, Frequency Range-level, BandGroup-level, Cell Group-level, Cell-level, Carrier-level, BWP-level, etc.
[0299] Supported gap time domain configurations: such as periodic, aperiodic, gaps that contain smaller periods within a larger period, gaps that repeat over a period of time, etc.
[0300] Does it support unified gap priority configuration: that is, giving uniform priority to all gaps? Or, which gaps for which purposes can be given uniform priority configuration?
[0301] Does it support a keep mechanism, or which types of gaps can be configured with a unified keep configuration?
[0302] This application's embodiments address the issues of inflexible gap configuration and inefficient resource management in related wireless communication systems, achieving unified planning, intelligent management, and conflict coordination of gap resources, thereby improving system stability and efficiency. The combined use of these technical features not only optimizes the gap configuration process and reduces signaling interaction but also enhances UE autonomy and network adaptability, providing advanced gap management strategies for future 5G and 6G networks. For example, by using technical features including but not limited to gap lists, gap holding information, gap configuration auxiliary information reporting, and a mechanism combining gap priority and holding indication, this solution can handle complex, multi-purpose gap configurations, ensuring that UE measurement requirements are met and communication quality is guaranteed in various network scenarios.
[0303] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0304] This embodiment also provides a gap configuration device in a wireless communication system, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated. The device includes:
[0305] The configuration module is used to uniformly configure gap configuration information for user equipment (UE) by combining the purposes of multiple gaps;
[0306] The sending module is used to send the Gap configuration information to the UE.
[0307] This embodiment also provides a gap configuration device in a wireless communication system, the device comprising:
[0308] The receiving module is used to receive interval gap configuration information sent by the base station, wherein the gap configuration information is configured by the base station for the UE in a unified manner in combination with the purpose of multiple interval gaps.
[0309] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.
[0310] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.
[0311] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.
[0312] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0313] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.
[0314] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.
[0315] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.
[0316] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.
Claims
1. A gap configuration method in a wireless communication system, characterized in that, include: Combine the uses of multiple gaps to uniformly configure gap configuration information for user equipment (UE); Send the Gap configuration information to the UE.
2. The method according to claim 1, characterized in that, The Gap configuration information includes a Gap list, wherein the Gap list includes multiple Gap information, and each Gap information includes at least one of the following: Gap ID, Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information.
3. The method according to claim 2, characterized in that, The Gap configuration information also includes Gap retention information.
4. The method according to claim 2, characterized in that, Combining multiple gap usage purposes, the UE is uniformly configured with gap configuration information including: Receive Gap configuration assistance information reported by UE, wherein the Gap configuration assistance information includes at least one of the following: Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information; The Gap configuration information is configured uniformly for the UE based on the Gap configuration auxiliary information.
5. The method according to claim 4, characterized in that, The Gap configuration assistance information reported by the UE includes: Receive the Gap configuration assistance information reported by the UE through the radio resource configuration completion message or the User Assistance Information (UAI).
6. The method according to claim 4, characterized in that, The Gap configuration assistance information also includes Gap retention indication information, wherein the Gap retention indication information is used to indicate the GAP that is retained.
7. The method according to claim 6, characterized in that, The gap retention indication information is indicated through a gap ID list or a gap usage list.
8. The method according to claim 6, characterized in that, The Gap configuration assistance information also includes a mechanism for combining Gap priority with Gap retention instructions.
9. The method according to claim 1, characterized in that, Sending the Gap configuration information to the UE includes: The Gap configuration information is sent to the UE via Radio Resource Control (RRC) signaling or underlying signaling.
10. The method according to claim 9, characterized in that, Sending the Gap configuration information to the UE via underlying signaling includes: The underlying signaling is sent to the UE through a distributed unit (DU), wherein the underlying signaling includes header information and encoded gap configuration information.
11. The method according to claim 2, characterized in that, The method further includes: Activate or deactivate one or more gaps, one or more gap types, or one or more gap IDs.
12. The method according to claim 11, characterized in that, Before activating or deactivating one or more gaps, one or more gap types, or one or more gap IDs, the method further includes: The system receives an activation or deactivation request sent by the UE, wherein the activation or deactivation request is used to request activation or deactivation of one or more Gaps, one or more Gap types, and one or more GapIDs.
13. The method according to claim 2, characterized in that, The Gap uses include at least one of the following: a Gap for Radio Resource Management (RRM), a Gap for Multi-User Multi-SIM (MUSIM) Management, a Gap for Location Services, a Gap for Communication and Sensing, and a Gap for Artificial Intelligence (AI) Tasks. In this case, one Gap corresponds to one or more different Gap uses, and different Gaps correspond to the same or different Gap uses.
14. The method according to claim 2, characterized in that, The gap type includes at least one of the following: static gap, semi-persistent gap, dynamic gap, conditional gap, pre-configured type, and autonomous gap.
15. The method according to claim 2, characterized in that, The gap granularity includes at least one of the following: based on UE level, based on frequency range level, based on band group level, based on cell level, based on carrier level, and based on BWP level.
16. The method according to claim 2, characterized in that, The time-domain configuration of the gap includes: periodic gap and aperiodic gap, wherein the periodic gap includes one or more sub-periods.
17. A gap configuration method in a wireless communication system, characterized in that, include: The base station receives interval gap configuration information, wherein the gap configuration information is configured by the base station for the UE in a unified manner, taking into account the uses of multiple interval gaps.
18. The method according to claim 17, characterized in that, The Gap configuration information includes a Gap list, wherein the Gap list includes multiple Gap information, and each Gap information includes at least one of the following: Gap ID, Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information.
19. The method according to claim 18, characterized in that, The Gap configuration information also includes Gap retention information.
20. The method according to claim 18, characterized in that, The method further includes: The base station is reported with Gap configuration assistance information, which includes at least one of the following: Gap purpose, Gap type, Gap granularity, Gap time domain configuration, Gap priority, and Gap retention information.
21. The method according to claim 20, characterized in that, Reporting Gap configuration assistance information to the base station includes: The Gap configuration assistance information is reported to the base station via a wireless resource configuration completion message or user assistance information (UAI).
22. The method according to claim 20, characterized in that, The Gap configuration assistance information also includes Gap retention indication information, wherein the Gap retention indication information is used to indicate the GAP that is retained.
23. The method according to claim 22, characterized in that, The gap retention indication information is indicated through a gap ID list or a gap usage list.
24. The method according to claim 22, characterized in that, The Gap configuration assistance information also includes a mechanism for combining Gap priority with Gap retention instructions.
25. The method according to claim 18, characterized in that, The interval gap configuration information received from the base station includes: The Gap configuration information sent by the base station is received through Radio Resource Control (RRC) signaling or underlying signaling.
26. The method according to claim 25, characterized in that, Receiving the Gap configuration information sent by the base station via underlying signaling includes: The UE receives the underlying signaling sent by the base station, wherein the underlying signaling includes header information and encoded Gap configuration information.
27. The method according to claim 18, characterized in that, The method further includes: Send an activation or deactivation request to the base station, wherein the activation or deactivation request is used to request the activation or deactivation of one or more gaps, one or more gap types, and one or more gap IDs.
28. The method according to claim 18, characterized in that, The method further includes: When multiple gaps conflict, the gap conflict is handled according to the gap information and the gap retention information.
29. The method according to claim 28, characterized in that, Handling gap conflicts of the multiple gaps based on the gap information and the gap retention information includes: Gap conflicts of the multiple gaps are handled based on at least one of the following: Gap priority, Gap retention information, maximum Gap repetition cycle processing, Gap purpose, Gap granularity, Gap type, Gap granularity, and Gap time-domain configuration.
30. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 16, 17 to 29.
31. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, implements the steps of the method described in any one of claims 1 to 16, 17 to 29.
