A bandwidth adaptation method and device

Abstract

The application discloses a bandwidth adaptation method and device. A network side determines configuration information for configuring at least two sub-profiles in an active BWP for a terminal, including limited bandwidth and wideband sub-profiles; and transmits a switching instruction for switching from a current sub-profile to a target sub-profile in the current active BWP. All sub-profiles share the core control configuration of the BWP, including CORESET, PDCCH monitoring occasions, DCI formats and sizes. In the limited bandwidth sub-profile, the terminal judges RBs exceeding the limited bandwidth as invalid, and PDCCH monitoring is limited in the bandwidth range. The application solves the problems of large BWP switching delay, weak robustness, insufficient energy consumption adaptation flexibility and low scheduling efficiency, and realizes fast anti-misalignment adaptation of multiple sub-profiles in a single BWP.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a bandwidth adaptation method and apparatus. Background Technology

[0002] In 5G NR communication systems, the BWP is the core resource configuration unit, whose core function is to balance communication rate and energy consumption requirements by dynamically adjusting the UE's working bandwidth.

[0003] The 5G NR BWP handover mechanism typically employs a logic of "multiple independent BWP configurations combined with full parameter adjustment," with the specific process as follows: The network side configures multiple independent BWPs for the UE (such as initial BWP, default BWP, active BWP, etc.). Each BWP corresponds to a complete configuration set, including key parameters such as bandwidth, subcarrier spacing, control resource set, physical downlink control channel listening timing, downlink control information format / size, etc. When service traffic changes, the network sends a BWP handover command to the UE via DCI dynamic triggering or RRC semi-static triggering. After receiving the command, the UE needs to adjust all BWP-related parameters, including a complete reboot and initialization of the radio frequency and baseband modules; A fixed "BWP handover gap" needs to be reserved during the handover process, which is usually several symbols, during which the UE pauses data transmission and reception. After the UE completes the parameter adjustment, it needs to send HARQ confirmation of data transmission back to the network before the network can schedule data on the new BWP.

[0004] The design of multi-BWP handover caters to a range of scenarios: it supports terminals with different capabilities; for example, in a 100MHz cell, there might be low-cost IoT devices that only support 20MHz bandwidth, as well as high-end mobile phones that support 100MHz. By configuring multiple BWPs, both types of terminals can be served simultaneously. It also supports different service types; for example, by configuring different parameter sets on different BWPs, frequency division multiplexing on the same carrier can provide high bandwidth for eMBB services while ensuring low latency for URLLC services. Furthermore, it provides a default "safe zone," such as the standard-defined default BWP, which can automatically switch back to low bandwidth after the UE's inactive timer expires, forcing the UE into a power-saving state. However, this comprehensive framework is cumbersome and inefficient when dealing with simple bandwidth adaptation scenarios. Traditional BWP handover mechanisms suffer from high handover latency, weak robustness, insufficient flexibility in energy consumption adaptation, and low scheduling efficiency. Large switching latency: The time required for switching between full parameter adjustments and the switching interval is relatively long, which cannot meet the fast traffic matching requirements of high-frequency data burst scenarios.

[0005] Weak robustness: Different BWPs have different core control configurations such as CORESET and PDCCH listening timing. If the UE misses the handover command, it may cause inaccuracy with the network and easily lead to link interruption. Specifically, in 5G NR, when a UE is instructed to hand over a BWP, the CORESET configuration of the target BWP may be different from that of the source BWP, especially when the BWP bandwidth is different. Although this mechanism allows the network to optimize the CORESET configuration parameters individually for each BWP, if the UE misses the DCI indicating the BWP handover, it will be unable to decode subsequent DCIs, further exacerbating the risk of link interruption.

[0006] Insufficient flexibility in energy consumption adaptation: BWP switching overhead is large, making it difficult to switch quickly between low-load and high-load scenarios, resulting in energy waste; and if a wideband CORESET is configured to achieve shared PDCCH listening opportunities across BWPs, the UE will not be able to narrow its radio frequency operating range, which significantly increases energy consumption compared to a narrowband CORESET that adapts to active bandwidth.

[0007] Low scheduling efficiency: After the network sends a handover command, it needs to wait for the UE to confirm before scheduling can proceed. This process is cumbersome and affects the continuity of data transmission. Summary of the Invention

[0008] This application proposes a bandwidth adaptation method and device to solve the problems of large handover latency, weak robustness, insufficient energy consumption adaptation flexibility and low scheduling efficiency in the existing BWP handover mechanism. It is especially suitable for bandwidth adaptation scenarios of terminal equipment in 5G NR and subsequent mobile communication systems.

[0009] Firstly, this application proposes a bandwidth adaptation method, comprising the following steps: Within the active bandwidth portion (BWP) currently configured for the terminal-side device, at least two sub-profiles are configured for the terminal-side device, the sub-profiles including at least a limited bandwidth sub-profile and a wideband sub-profile.

[0010] A sub-profile switching instruction is transmitted, which is used to switch from the current sub-profile to the target sub-profile within the currently active BWP.

[0011] The at least two sub-configuration files are configured within the active BWP.

[0012] In one embodiment, the sub-configuration file shares the core control configuration of the active BWP, which includes at least the control resource set (CORESET) configuration, the physical downlink control channel (PDCCH) monitoring timing configuration, and the downlink control information (DCI) format and size configuration being monitored.

[0013] In one embodiment, the adaptation parameters of the sub-configuration file are a minimum configuration set that affects the power consumption of the terminal-side device. The minimum configuration set includes at least one or more of the following: maximum bandwidth, maximum rank, and search space group SSSG period.

[0014] In one embodiment, the condition for triggering the sub-profile switching is: the size of the service data packets of the terminal device increases to exceed the carrying capacity of the current limited bandwidth sub-profile, or the amount of service data decreases to below the carrying requirements of the broadband sub-profile.

[0015] In one embodiment, the bandwidth of the broadband sub-profile is consistent with the bandwidth of the single active BWP.

[0016] The method described in any embodiment of the first aspect of this application, used in a terminal-side device, includes the following steps: The system receives configuration information, which is used to configure at least two sub-profiles for the terminal device within the configured active bandwidth portion (BWP). The sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile.

[0017] Receive sub-configuration file switching instructions.

[0018] According to the switching instruction, switch from the current sub-profile to the target sub-profile within the currently active BWP.

[0019] In one embodiment, the terminal-side device is currently configured with only one active BWP.

[0020] In one embodiment, the terminal-side device maintains the BWP-level core control configuration unchanged during the sub-profile switching process.

[0021] In one embodiment, in the limited bandwidth sub-profile, resource blocks (RBs) exceeding the bandwidth limit of the sub-profile are determined to be invalid.

[0022] In one embodiment, in the limited bandwidth sub-profile, physical downlink control channel (PDCCH) monitoring is limited only to the control resource set (CORESET) portion within the limited bandwidth range, ignoring PDCCH monitoring opportunities outside the limited bandwidth range.

[0023] In one embodiment, when the terminal-side device misses the handover instruction, it decodes the subsequent DCI based on the shared BWP-level core control configuration and aligns it with the network focus according to the subsequent DCI.

[0024] In one embodiment, the core control configuration is a fixed configuration pre-configured by the network side to the terminal device via Radio Resource Control (RRC) signaling, and the terminal device does not modify the core control configuration during the sub-configuration file switching process.

[0025] The method described in any embodiment of the first aspect of this application, used in a network-side device, includes the following steps: Within the active bandwidth portion (BWP) configured for the terminal-side device, at least two sub-profiles are configured for the terminal-side device, the sub-profiles including at least a limited bandwidth sub-profile and a wideband sub-profile.

[0026] In response to changes in the service traffic demands of the terminal-side device, a sub-profile switching command is sent to the terminal-side device via downlink control information (DCI) or MAC CE.

[0027] After sending the switching command, the terminal-side device is scheduled according to the resource configuration of the target sub-configuration file.

[0028] In one embodiment, the network-side device configures one and only one active BWP for the terminal-side device.

[0029] In one embodiment, the network-side device does not modify the BWP-level core control configuration during the sub-configuration file switching process.

[0030] In one embodiment, under the limited bandwidth sub-configuration file, the terminal-side device is scheduled only on resource blocks (RBs) within the limited bandwidth range, without exceeding the allocated resources within the limited bandwidth.

[0031] In one embodiment, after sending the handover command, the network-side device does not need to wait for the handover confirmation from the terminal-side device, and directly schedules the terminal-side device according to the resource configuration of the target sub-configuration file.

[0032] In one embodiment, if the terminal device misses the handover instruction, the network side will reissue the handover instruction or current scheduling information via DCI during the next shared PDCCH listening opportunity to assist the terminal device in realigning based on the shared BWP-level core control configuration.

[0033] In one embodiment, the core control configuration is a fixed configuration pre-configured by the network side to the terminal device via Radio Resource Control (RRC) signaling, and the network side does not modify the core control configuration during the sub-configuration file switching process.

[0034] Secondly, this application also proposes a network-side device for implementing the method described in any one of the first aspects of this application, wherein at least one module in the network-side device is used for at least one of the following functions: Within the active bandwidth portion (BWP) configured for the terminal-side device, at least two sub-profiles are configured for the terminal-side device, each sub-profile including at least a limited bandwidth sub-profile and a wideband sub-profile. In response to changes in the service traffic demands of the terminal-side device, a sub-profile switching instruction is sent to the terminal-side device via downlink control information (DCI). After sending the switching instruction, the terminal-side device is scheduled according to the resource configuration of the target sub-profile.

[0035] This application also proposes a terminal-side device for implementing the method described in any one of the first aspects of this application, wherein at least one module in the terminal-side device is used for at least one of the following functions: The system receives configuration information, which is used to configure at least two sub-profiles for the terminal device within the configured active bandwidth portion (BWP). The sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile. The system also receives a sub-profile switching instruction and, according to the switching instruction, switches from the current sub-profile to the target sub-profile within the current active BWP.

[0036] Thirdly, this application also proposes a communication device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method as described in any embodiment of the first aspect of this application.

[0037] This application also proposes a computer-readable medium on which a computer program is stored, which, when executed by a processor, implements the steps of the method as described in any embodiment of the first aspect of this application.

[0038] Fourthly, this application also proposes a mobile communication system comprising at least one network-side device as described in any embodiment of this application and / or at least one terminal-side device as described in any embodiment of this application.

[0039] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects: The technical solution of this application achieves rapid misalignment adaptation of multiple sub-profiles within a single BWP. This solution, through a fixed core control set and flexible adjustment of data parameters, enables fast and reliable switching of UE power consumption and bandwidth within a single BWP, balancing low latency, high robustness, and low power consumption.

[0040] Traditional BWP handover requires reloading the entire set of parameters, including CORESET, PDCCH listening timing, and DCI format, resulting in millisecond-level latency. This solution, however, uses a shared BWP-level core control configuration across all sub-configuration files, adjusting only the effective RB range and PDCCH listening area, reducing latency to microseconds. There is no control parameter resynchronization process or out-of-sync window; even if the UE does not receive a sub-configuration handover indication, it can still decode subsequent DCI messages normally, significantly improving link stability. Therefore, traditional BWP handover requires a full parameter reconfiguration, while this solution achieves the same effect but saves time and effort. Attached Figure Description

[0041] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a flowchart illustrating an embodiment of the method of this application; Figure 2 This is a flowchart illustrating an embodiment of the method of this application used in a network-side device; Figure 3 This is a flowchart illustrating an embodiment of the method of this application used in a terminal-side device; Figure 4 This is a schematic diagram of an embodiment of a network-side device; Figure 5 This is a schematic diagram of an embodiment of the terminal-side device; Figure 6 This is a schematic diagram of the structure of a network-side device according to another embodiment of the present invention; Figure 7 This is a block diagram of a terminal-side device according to another embodiment of the present invention. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] From its inception, the 5G standard defined a Baseband Window (BWP) as an independent resource entity carrying a complete set of identity information, not just a bandwidth segment. Each BWP contains an independent and complete set of configuration parameters: frequency domain location (the starting position and width of the BWP in the system bandwidth), parameter set (Numerology, including subcarrier spacing and cyclic prefix length), and dedicated control resources (each BWP can configure its own set of CORESET and PDCCH listening times). During multi-BWP handover, the latency sources in existing technologies include: radio frequency (RF) tuning overhead (when switching to a BWP with a different center frequency, the UE needs to adjust the local oscillator frequency and filter bandwidth); baseband parameter reconfiguration (requiring updates to RB mapping, control channel (CORESET / PDCCH) parameters, etc., with some parameter changes increasing processing time); and control channel resynchronization (if the control resource sets of the old and new BWPs are different, the UE needs to re-perform PDCCH blind detection, further increasing latency and mismatch risk).

[0044] To adapt to bandwidth changes, if multiple BWP handover is not performed, one possible method is to directly modify the BWP configuration. However, directly changing the configuration of this BWP faces the following obstacles under the standard framework: the bandwidth of a BWP is strongly bound to its parameter set and CORESET configuration. Changing the bandwidth usually means redefining the entire BWP configuration set, which constitutes a "handover" at the protocol level. Dynamically modifying the BWP configuration may also cause inconsistencies in the UE's and network's understanding of the current state of the BWP, introducing new risks of desynchronization. The reason why existing technologies choose to switch the entire BWP rather than adjust the configuration within the same BWP is precisely because the 5G standard was designed from the outset to define a BWP as an independent resource entity carrying a complete set of identity information.

[0045] Within the scope permitted by the standard framework of this application, the two logical concepts of sub-configuration files and effective RB range are creatively introduced to achieve bandwidth adaptation by modifying the UE's usage conventions for BWP resources. The core technical solution of this invention is: to build a unified limited adaptation mechanism based on DCI within a single active BWP, and to achieve rapid switching and anti-misalignment adaptation of UE energy consumption parameters by configuring multiple sub-configuration files that share core control parameters. The network side configures a single active BWP for the UE as the core working bandwidth carrier of the UE, avoiding the overhead of full parameter adjustment during multi-BWP switching. Within the single active BWP, at least two sub-configuration files are configured for the UE, including: a limited bandwidth sub-configuration file—adapted to low-load scenarios, with bandwidth less than or equal to the active BWP bandwidth, where the UE does not expect scheduling exceeding the limited bandwidth, and resource blocks (RBs) exceeding the limit are deemed invalid; and all sub-configuration files share BWP-level core control configuration, including but not limited to CORESET configuration, PDCCH listening timing configuration, and DCI format / size configuration being listened to, to avoid link interruption caused by control parameter misalignment. Furthermore, to address the issue that sharing CORESET may increase energy consumption in narrow bandwidth scenarios, this solution is designed such that when the UE switches to a narrow bandwidth sub-profile, PDCCH monitoring is limited to the CORESET portion within that narrow bandwidth range, ignoring monitoring opportunities outside the bandwidth. This ensures shared monitoring opportunities across sub-profiles while avoiding increased energy consumption due to expanded radio frequency range.

[0046] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0047] Figure 1 This is a flowchart illustrating an embodiment of the method of this application.

[0048] The method of this application includes steps 110 to 130.

[0049] Step 110: Determine configuration information. The configuration information is used to configure at least two sub-configuration files for the terminal-side device within the configured active bandwidth portion (BWP). The sub-configuration files include at least a limited bandwidth sub-configuration file and a wideband sub-configuration file.

[0050] In this step, the configuration information is determined by the network-side device and sent to the terminal-side device, or the terminal-side device receives it from the network side and determines its content; this determination action covers both the generation and acquisition of configuration information. The network-side device configures parameter sets (maximum bandwidth, maximum rank, SSSG period, etc.) for at least two sub-configuration files within the single active BWP via RRC signaling. The UE receives and stores multiple sub-configuration file parameters, specifying the "effective resource range" and energy consumption parameters corresponding to each configuration file, preparing for subsequent dynamic handover.

[0051] The at least two sub-configuration files are configured within the active BWP. All sub-configuration files share the core control configuration of the active BWP, which includes at least the control resource set (CORESET) configuration, the physical downlink control channel (PDCCH) monitoring timing configuration, and the downlink control information (DCI) format and size configuration being monitored.

[0052] In one specific embodiment, the active BWP bandwidth is configured to 100MHz, and the network is configured with two sub-profiles, with the following specific parameters:

[0053] The adaptation parameters of the sub-configuration file are the minimum configuration set that affects the power consumption of the terminal-side device. The minimum configuration set includes at least one or more of the following: maximum bandwidth, maximum rank, and search space group SSSG period. These parameters directly affect the UE's RF front-end operating bandwidth (determining the RF / FFT scale), MIMO computation (maximum rank), and PDCCH blind detection frequency (SSSG period).

[0054] The bandwidth of the broadband sub-profile is consistent with the bandwidth of the single active BWP. In one embodiment, when the active BWP is 100MHz, the bandwidth of the broadband sub-profile is 100MHz; when the active BWP is 40MHz, the bandwidth of the broadband sub-profile is 40MHz.

[0055] Step 120: Transmit a sub-configuration file switching instruction, which is used to switch from the current sub-configuration file to the target sub-configuration file within the currently active BWP.

[0056] In this step, the switching instruction is transmitted from the network-side device to the terminal-side device, or transmitted by the network-side device and then received by the terminal-side device; the transmission action covers both sending and receiving.

[0057] The conditions that trigger the switching of the sub-profile are: the size of the service data packets of the terminal device increases to exceed the carrying capacity of the current limited bandwidth sub-profile, or the amount of service data decreases to below the carrying capacity requirement of the broadband sub-profile.

[0058] In one embodiment, when a UE is making a video call, the data packet size increases. The network detects the traffic increase through PDCP layer statistics, determines that the limited bandwidth sub-profile (e.g., 20MHz) cannot meet the demand, and triggers a switch to the wideband sub-profile.

[0059] In another embodiment, when the UE switches from a video call to a standby state, the amount of service data decreases significantly, and the network determines that it is not necessary to maintain a broadband sub-profile (e.g., 100MHz), triggering a switch to a limited bandwidth sub-profile.

[0060] Step 130: According to the switching instruction, switch from the current sub-configuration file to the target sub-configuration file within the currently active BWP.

[0061] In this step, the terminal device responds to the handover command transmitted by the network device and performs a handover from the current sub-profile to the target sub-profile.

[0062] The terminal-side equipment maintains the core control configuration unchanged during handover. Specifically, when switching sub-profiles, the UE is strictly prohibited from modifying or reconfiguring local core control configuration parameters (including CORESET configuration, PDCCH listening timing configuration, and DCI format and size configuration) to ensure that the PDCCH decoding link remains consistent across all sub-profiles. Therefore, the handover time between different sub-profiles is less than the BWP handover interval in a 5G NR communication system.

[0063] Under the limited bandwidth sub-profile, the terminal device will determine that resource blocks (RBs) exceeding the bandwidth limit of the sub-profile are invalid, and will not expect the network to schedule resources exceeding the bandwidth limit. For example, when the UE is operating under the 20MHz limited bandwidth sub-profile, all RBs exceeding 20MHz will be determined to be invalid.

[0064] Furthermore, under the limited bandwidth sub-profile, PDCCH monitoring is restricted to the CORESET portion within that limited bandwidth range, ignoring PDCCH monitoring opportunities outside the limited bandwidth range. This design ensures shared monitoring opportunities across sub-profiles while avoiding increased power consumption due to expanded RF range.

[0065] When the terminal-side device misses the handover command, it decodes the subsequent DCI based on the shared BWP-level core control configuration and aligns it with the network focus according to the subsequent DCI. For example, if the UE misses the handover command sent by the network from 20MHz to 100MHz, the UE can still decode the subsequent DCI normally because the core control configurations such as CORESET and PDCCH listening timing remain unchanged. When the UE finds that the scheduling RB in the subsequent DCI exceeds the 20MHz range or contains a new configuration file index, it can automatically identify the misalignment and align it with the network focus.

[0066] It should be noted that the above steps are used for network entities in a wireless communication system, including terminal-side devices, network-side devices, or other intermediate devices; the above steps can also be used for service devices that provide information processing for the network entity devices; the above steps can also be used for any device, system, subsystem, circuit, chip, or software entity that provides information reception, transmission, identification, and processing for terminal-side devices or network-side devices.

[0067] Figure 2 This is a flowchart illustrating an embodiment of the method of this application used in a network-side device.

[0068] refer to Figure 2 The method described in any embodiment of the first aspect of this application, used in a network-side device, includes the following steps 210 to 240.

[0069] Step 210: The network-side device configures a single active bandwidth portion (BWP) for the terminal-side device as the core working bandwidth carrier of the UE.

[0070] In this step, the network-side device configures only one always-active BWP (e.g., 100MHz) for the UE via RRC signaling, without configuring any additional initial BWP, default BWP, or other active BWPs. This single active BWP serves as the UE's sole operating bandwidth range within the cell, and the UE no longer listens for or anticipates handover commands from other BWPs.

[0071] Step 220: Within the single active BWP, the network-side device configures at least two sub-profiles for the terminal-side device, wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile.

[0072] In this step, the network side configures two sub-profiles within the single active BWP via RRC signaling: a limited bandwidth sub-profile adapted for low-load scenarios, with a bandwidth less than or equal to the active BWP bandwidth; and a wide bandwidth sub-profile with the same bandwidth as the single active BWP.

[0073] All the sub-configuration files share the BWP-level core control configuration of the single active BWP. This BWP-level core control configuration includes at least the control resource set (CORESET) configuration, the physical downlink control channel (PDCCH) monitoring timing configuration, and the monitored downlink control information (DCI) format and size configuration. The network-side device does not modify the BWP-level core control configuration during sub-configuration file switching.

[0074] Step 230: In response to changes in the service traffic demand of the terminal-side device, the network-side device sends a sub-profile switching instruction to the terminal-side device through downlink control information (DCI) or MAC CE.

[0075] In this step, the network side detects that the size of the UE's service data packets has increased to exceed the carrying capacity of the current limited bandwidth sub-profile. It then sends a handover command to the UE via DCI, instructing it to switch to the wideband sub-profile. The network side may implicitly or explicitly instruct the UE to only listen to the CORESET portion within that narrow bandwidth range when operating in limited bandwidth mode.

[0076] After sending the switching command, the network-side device does not need to wait for the terminal-side device to confirm the switching, and directly schedules the terminal-side device according to the resource configuration of the target sub-configuration file.

[0077] Step 240: After sending the switching command, the network-side device schedules the terminal-side device according to the resource configuration of the target sub-configuration file.

[0078] In this step, after the network sends the DCI switching command, it does not start a waiting timer or wait for HARQ confirmation, but directly performs PDSCH / PUSCH scheduling according to the constraints of the target sub-configuration file (such as the new effective RB range).

[0079] Under the limited bandwidth sub-profile, the network-side device schedules the terminal-side device only on resource blocks (RBs) within the limited bandwidth range, without exceeding the allocated resources beyond the limited bandwidth. For example, when a UE is switched to the 20MHz limited bandwidth sub-profile, the network only schedules the UE within the RB range corresponding to 20MHz, and does not schedule any resources exceeding that range.

[0080] Two-level DCI triggering implementation example - network side perspective In one embodiment, the network side issues a handover command through a two-level DCI. The network side sends the first-level DCI to the UE through the PDCCH on the currently active BWP; the first-level DCI adopts the DCI1_1 (downlink) or DCI0_1 (uplink) format, and only contains the target BWP index (bandwidth part indicator field) and the scheduling information of the second-level DCI. The scheduling information includes the time-frequency resource location of the second-level DCI on the physical downlink shared channel and the K0 / K2 value (time slot offset between PDSCH and PDCCH).

[0081] After sending the first-level DCI, the network side carries the second-level DCI on the PDSCH. The second-level DCI contains the service scheduling information of the target BWP (including RB allocation, modulation and coding scheme MCS, etc.).

[0082] If the network receives a NACK from the UE in the HARQ-ACK feedback, or does not receive the expected feedback, the two-level DCI handover command will be reissued.

[0083] MAC CE Solution Implementation Examples – Network Side Perspective In another embodiment, the network side utilizes the CRC check mechanism of MAC CE to ensure reliable transmission of BWP handover commands. Based on service requirements (such as QoS changes or UE service state switching), the network side generates BWP handover commands and encapsulates them into a MAC CE BWP Switch control element. The MAC CE BWP Switch uses a fixed-length format, containing only the target BWPID field (2-3 bits), reducing signaling overhead.

[0084] The network side will transmit the MAC protocol data unit (MAC PDU) encapsulated with the MAC CE BWP Switch to the UE through the PDSCH on the source BWP.

[0085] Inaccuracy Recovery Mechanism – Network Side Perspective In one embodiment, if the terminal device misses the handover instruction, the network side will reissue the handover instruction or current scheduling information via DCI during the next shared PDCCH listening opportunity to assist the terminal device in realigning based on the shared BWP-level core control configuration.

[0086] Specifically, since the core control configuration remains unchanged, even if the UE misses a previous handover command, it can still decode subsequent PDCCH DCI messages normally. When the network does not receive the expected data or feedback from the UE under a certain sub-profile, no special handling is required; it only needs to resend the handover command or current scheduling information via DCI at the next shared PDCCH listening opportunity. When the UE discovers that the scheduling RB in the DCI exceeds the range of the current sub-profile or contains a new profile index, it can automatically align with the network side.

[0087] Figure 3 This is a flowchart illustrating an embodiment of the method of this application used in a terminal-side device.

[0088] refer to Figure 3 The method described in any embodiment of the first aspect of this application, used in a terminal-side device, includes the following steps 310 to 340.

[0089] Step 310: The terminal device receives configuration information, which is used to configure at least two sub-configuration files for the terminal device within the configured active bandwidth portion (BWP). The sub-configuration files include at least a limited bandwidth sub-configuration file and a wideband sub-configuration file.

[0090] In this step, the UE receives configuration information from the network side via RRC signaling. The configuration information indicates that there are two sub-profiles within a single active BWP: a limited bandwidth sub-profile (20MHz bandwidth) and a wide bandwidth sub-profile (100MHz bandwidth), and both share the same CORESET#0 configuration, PDCCH listening period (10ms), and DCI format 1_0.

[0091] The terminal-side device currently has only one active BWP configured. This means that the UE does not need to listen for or expect switching commands from other BWPs, and all bandwidth adaptation operations are completed within the currently active BWP.

[0092] Step 320: The terminal device receives the sub-configuration file switching instruction.

[0093] In this step, the UE receives the DCI sent by the network side via the PDCCH. The DCI contains a sub-profile switching indication, which is used to instruct the UE to switch from the current sub-profile to the target sub-profile.

[0094] Step 330: The terminal device switches from the current sub-profile to the target sub-profile within the currently active BWP according to the switching instruction.

[0095] In this step, after the UE is powered on, it will access the limited bandwidth sub-configuration file (20MHz) by default and only listen to RBs within the 20MHz bandwidth. RBs outside the 20MHz bandwidth will be deemed invalid. The radio frequency module will only activate the frequency band corresponding to 20MHz, and the baseband module will run in a low computing power mode, thus reducing power consumption.

[0096] When the network instructs the UE to switch to a wideband sub-profile via DCI, the UE adjusts only the corresponding baseband / RF parameters (such as maximum bandwidth, maximum rank, SSSG period, etc.) according to the received sub-profile index, without involving reinitialization of other physical layer or MAC layer parameters. The UE's RF and baseband bandwidths increase synchronously, the working BWP range is widened, and full-bandwidth transmission can be supported to meet high throughput requirements.

[0097] The terminal-side device maintains the core control configuration unchanged during the sub-profile switching process. Specifically, the UE does not reconfigure core control parameters such as CORESET, PDCCH listening timing, and DCI format and size due to profile changes.

[0098] Step 340: The terminal device performs the corresponding listening and sending / receiving operations under the target sub-configuration file.

[0099] In the limited bandwidth sub-profile, the terminal-side device will determine that resource blocks (RBs) exceeding the bandwidth limit of the sub-profile as invalid. For example, under the 20MHz sub-profile, the UE will directly treat all RBs exceeding 20MHz as invalid resources, without caching, attempting demodulation, or expecting the network to schedule them.

[0100] In the limited bandwidth sub-configuration file, PDCCH monitoring is limited to the CORESET portion within the limited bandwidth range, ignoring PDCCH monitoring opportunities outside the limited bandwidth range. For example, the UE actively narrows the radio frequency bandwidth to 20MHz, only monitoring the CORESET portion within the 20MHz range, ignoring monitoring opportunities outside the bandwidth.

[0101] When the terminal-side device misses the handover command, it decodes the subsequent DCI based on the shared BWP-level core control configuration and aligns it with the network focus according to the subsequent DCI. For example, if the UE misses the DCI sent by the network to switch from 20MHz to 100MHz, the UE can still decode the subsequent DCI normally because the core control configurations such as CORESET and PDCCH listening timing remain unchanged. When the UE finds that the scheduling RB in the subsequent DCI exceeds the 20MHz range or contains a new configuration file index, it can automatically identify the misalignment and align it with the network focus.

[0102] Two-level DCI triggering implementation example – terminal side perspective In one embodiment, the terminal device receives a handover command from the network side via a two-level DCI. On the currently active BWP (source BWP), the UE receives the first-level DCI via PDCCH, which contains the target BWP index and scheduling information for the second-level DCI. The UE then receives a PDSCH based on this scheduling information, which carries the second-level DCI, containing service scheduling information for the target BWP.

[0103] After the UE successfully decodes the second-level DCI, it immediately performs BWP handover, including radio frequency tuning, BWP configuration parameter update, and sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) to the network side on the target BWP after handover. If the UE fails to decode the second-level DCI (e.g., CRC check fails), the handover command is deemed invalid, and the UE continues to listen to the PDCCH from the source BWP to avoid service interruption.

[0104] If the HARQ-ACK response is NACK, the network side will reissue the two-level DCI handover command.

[0105] MAC CE Solution Implementation Examples – Terminal Side Perspective In another embodiment, the terminal device receives a BWP handover command issued by the network side via MAC CE. The UE receives and decodes the MAC PDU on the source BWP and performs CRC verification on the MAC CE BWP switch. If the verification passes, the target BWP ID is parsed, and BWP handover is performed at the specified time slot boundary. After handover to the target BWP, data transmission and reception or HARQ feedback is started immediately. If the verification fails, ignore the MAC CE and maintain the current active state of the source BWP.

[0106] After the handover is complete, the UE receives and schedules according to the broadband sub-configuration file, supporting full-bandwidth transmission and meeting high throughput requirements. After the handover, the UE's radio frequency and baseband bandwidth increase synchronously, and the working BWP range is widened; the PDSCH can occupy more bandwidth resources after the handover, meeting the transmission requirements of large data packets.

[0107] The core control configuration is a fixed configuration pre-configured by the network side to the terminal device through Radio Resource Control (RRC) signaling. The terminal device does not modify the core control configuration during the sub-configuration file switching process.

[0108] The technical solution of this application can be summarized into three layers: the first layer (infrastructure layer) is a single BWP + shared control plane, which is the premise for realizing all subsequent operations; the second layer (performance optimization layer) quickly and energy-efficiently switches the activity range based on the design of the first layer, which is the core advantage that brings commercial value; the third layer (reliability hardening layer) ensures that synchronization is automatically restored using a fixed control plane when the wireless environment is harsh.

[0109] Figure 4 This is a schematic diagram of an embodiment of a network-side device.

[0110] This application also proposes a network-side device for implementing the method of any embodiment of this application. The network-side device is configured to: configure at least two sub-profiles for the terminal-side device within the active bandwidth portion (BWP) configured for the terminal-side device, wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile; in response to changes in the service traffic demand of the terminal-side device, send a sub-profile switching instruction to the terminal-side device via downlink control information (DCI); and after sending the switching instruction, schedule the terminal-side device according to the resource configuration of the target sub-profile.

[0111] To implement the above technical solution, this application proposes a network-side device 400, which includes a network transmitting module 401, a network determining module 402, and a network receiving module 403 that are interconnected.

[0112] The network determination module 402 is used to configure the Active Bandwidth Part (BWP) and sub-profiles for the terminal-side device. Specifically, the network determination module 402 is used to perform the following functions: within the Active Bandwidth Part (BWP) configured for the terminal-side device, it configures at least two sub-profiles for the terminal-side device, wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile. This module can also be used to detect changes in the service traffic demand of the terminal-side device and determine whether a switching command needs to be sent. The functionality of this module can be achieved through... Figure 2 The detection portion in steps 210, 220, and 230 of the embodiment is used to achieve this.

[0113] The network sending module 401 is used to send configuration information and switching instructions to the terminal-side device. Specifically, the network sending module 401 is used to perform the following functions: responding to changes in the service traffic requirements of the terminal-side device, it sends a sub-profile switching instruction to the terminal-side device through downlink control information (DCI). The switching instruction is used to switch from the current sub-profile to the target sub-profile within the currently active BWP. The functionality of this module can be achieved through... Figure 2 The sending part of step 230 in the embodiment is implemented.

[0114] The network receiving module 403 is used to receive data and feedback information from the terminal-side device. This module's function includes... Figure 2 In this embodiment, the scheduling execution process is implemented in conjunction with step 240.

[0115] In one embodiment, the network determination module 402 configures a single 100MHz active BWP for the UE, and within this BWP, configures a 20MHz limited bandwidth sub-profile and a 100MHz wideband sub-profile, both sharing the same CORESET and PDCCH configurations. The network transmission module 401 sends a handover command to the UE via DCI. After sending the handover command, the network-side equipment does not need to wait for the UE's handover confirmation and directly schedules the terminal-side equipment according to the resource configuration of the target sub-profile.

[0116] The specific methods for implementing the functions of the network sending module, network determining module, and network receiving module are as described in the various method embodiments of this application, and will not be repeated here.

[0117] The network-side equipment described in this application may refer to base station facilities, network-side equipment or servers connected to base stations, systems that provide services for the aforementioned equipment, or any system, subsystem, module, circuit, chip or software operating device that provides information reception, transmission, identification and processing for the aforementioned equipment.

[0118] Figure 5 This is a schematic diagram of an embodiment of the terminal-side device.

[0119] This application also proposes a terminal-side device for implementing the method of any embodiment of this application. The terminal-side device is configured to: receive configuration information, the configuration information being configured to configure at least two sub-profiles for the terminal-side device within a configured active bandwidth portion (BWP), the sub-profiles including at least a limited bandwidth sub-profile and a wideband sub-profile; receive a sub-profile switching instruction; and, according to the switching instruction, switch from the current sub-profile to a target sub-profile within the current active BWP.

[0120] To implement the above technical solution, this application proposes a terminal-side device 500, which includes a terminal transmitting module 501, a terminal determining module 502, and a terminal receiving module 503 that are interconnected.

[0121] The terminal receiving module 503 is used to receive configuration information and switching instructions from the network side. Specifically, the terminal receiving module 503 is used to perform the following functions: receiving configuration information, which is used to configure at least two sub-profiles for the terminal device within the configured active bandwidth portion (BWP), wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile; and receiving sub-profile switching instructions. The functionality of this module can be achieved through... Figure 3 This is achieved through steps 310 and 320 in the embodiment.

[0122] The terminal determination module 502 is used to perform sub-profile switching according to the switching instruction. Specifically, the terminal determination module 502 is used to perform the following function: according to the switching instruction, switching from the current sub-profile to the target sub-profile within the currently active BWP. This module's function can be achieved through... Figure 3 This is achieved through steps 330 and 340 in the embodiment.

[0123] The terminal determination module 502 is further configured to: under the limited bandwidth sub-configuration file, determine resource blocks (RBs) that exceed the bandwidth limit of the sub-configuration file as invalid; under the limited bandwidth sub-configuration file, limit PDCCH listening to only the CORESET portion within the limited bandwidth range, and ignore listening opportunities that exceed the limited bandwidth range; when a switching instruction is missed, decode subsequent DCIs based on the shared core control configuration and perform realignment.

[0124] The terminal sending module 501 is used to send data and feedback information to the network side. This module's function includes... Figure 3 The switching process in the embodiment is executed in conjunction with the completion of the switching.

[0125] In one embodiment, the terminal receiving module 503 receives configuration information from the network, instructing the configuration of two sub-profiles, 20MHz and 100MHz, within the 100MHz active BWP, sharing CORESET#0. The terminal determining module 502, based on the received switching instruction, switches from the current sub-profile to the target sub-profile within the 100MHz active BWP, maintaining the core control configuration unchanged during the switching process. After the switching is complete, the terminal determining module 502 adjusts the RF and baseband parameters according to the target sub-profile.

[0126] The specific methods for implementing the functions of the terminal sending module, the terminal determining module, and the terminal receiving module are as described in the various method embodiments of this application, and will not be repeated here.

[0127] The terminal-side equipment described in this application may refer to user equipment (UE), personal mobile terminal, smart terminal, mobile phone, computer with communication function, system that provides services for the above-mentioned equipment, or any system, subsystem, module, circuit, chip or software running device that provides information reception, transmission, identification and processing for the above-mentioned equipment.

[0128] Figure 6 A schematic diagram of a network-side device according to another embodiment of the present invention is shown. As shown, the network-side device 600 includes a processor 601, a wireless interface 602, and a memory 603. The wireless interface may consist of multiple components, including a transmitter and a receiver, providing a unit for communication with various other devices over a transmission medium. The wireless interface implements communication functions with the terminal-side device, processes wireless signals through receiving and transmitting devices, and the data carried by the signals is communicated with the memory or processor via an internal bus structure. The memory 603 contains a computer program that executes any embodiment of this application, and the computer program runs or modifies the processor 601. When the memory, processor, and wireless interface circuit are connected through a bus system, the bus system includes a data bus, a power bus, a control bus, and a status signal bus, which will not be described in detail here.

[0129] Figure 7 This is a block diagram of a terminal-side device according to another embodiment of the present invention. The terminal-side device 700 includes at least one processor 701, a memory 702, a user interface 703, and at least one wireless network interface 704. The various components in the terminal-side device 700 are coupled together via a bus system. The bus system is used to enable communication between these components. The bus system includes a data bus, a power bus, a control bus, and a status signal bus.

[0130] User interface 703 may include a display, keyboard, or clicking device, such as a mouse, trackball, touchpad, or touchscreen.

[0131] The memory 702 stores executable modules or data structures. The memory may store an operating system and application programs. The operating system includes various system programs, such as a framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application programs include various applications, such as media players and browsers, used to implement various application functions.

[0132] In an embodiment of the present invention, the memory 702 contains a computer program that executes any embodiment of the present application, the computer program being run on or modified by the processor 701.

[0133] The memory 702 includes a computer-readable storage medium. The processor 701 reads the information in the memory 702 and, in conjunction with its hardware, completes the steps of the above-described method. Specifically, the computer-readable storage medium stores a computer program, which, when executed by the processor 701, implements the steps of the method embodiments described in any of the above embodiments.

[0134] Processors 601 and 701 may be integrated circuit chips with signal processing capabilities. In implementation, each step of the method in this application can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, off-the-shelf programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor.

[0135] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. In a typical configuration, the device of this application includes one or more processors (CPUs), an input / output user interface, a network interface, and memory.

[0136] Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0137] Therefore, this application also proposes a computer-readable medium storing a computer program that, when executed by a processor, implements the steps of the method described in any embodiment of this application. For example, the memory 603, 702 of the present invention may include non-permanent memory in the form of computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM.

[0138] Based on the embodiments of the above-described apparatus in this application, this application also proposes a mobile communication system, including at least one embodiment of any terminal-side device in this application and / or at least one embodiment of any network-side device in this application.

[0139] It should be noted that the specific mobile communication technology described in this invention is not limited, and can be WCDMA, CDMA2000, TD-SCDMA, WiMAX, LTE / LTE-A, LAA, MuLTEfire, 5G NR, and the sixth-generation and Nth-generation mobile communication technologies that may appear in the future.

[0140] The terminal described in this invention refers to a terminal-side product that can support the communication protocols of terrestrial mobile communication systems, and a specially designed wireless modem module that can be integrated into various types of terminal forms such as mobile phones, tablets, and data cards to complete communication functions.

[0141] For ease of description, a fifth-generation mobile communication system is used as an example, where the mobile communication terminal can be represented as UE (User Equipment), and the network-side access equipment can be represented as a base station or access point.

[0142] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0143] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be understood that when a device or component is “connected” to another device or component, it may be directly connected to the other device or component, or there may be an intermediary device or component. Furthermore, the term “connection” as used herein may include partially wireless connections as well as partially wired connections.

[0144] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0145] The above description is merely an embodiment of this application and is not intended to limit the scope of 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 spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A bandwidth adaptation method, characterized in that, Includes the following steps: The configuration information is determined, which is used to configure at least two sub-profiles for the terminal-side device within the configured active bandwidth portion (BWP). The sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile. A sub-profile switching instruction is transmitted, which is used to switch from the current sub-profile to the target sub-profile within the currently active BWP.

2. A bandwidth adaptation method for terminal-side equipment, characterized in that, include: Receive configuration information, which is used to configure at least two sub-profiles for the terminal device within the configured active bandwidth portion (BWP), wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile; Receive sub-configuration file switching instructions; According to the switching instruction, switch from the current sub-profile to the target sub-profile within the currently active BWP.

3. The method according to claim 2, characterized in that, The terminal-side device currently has only one active BWP configured.

4. The method according to claim 2, characterized in that, The terminal-side device maintains its BWP-level core control configuration unchanged during the sub-configuration file switching process; the core control configuration is a fixed configuration pre-configured to the terminal-side device by the network side through Radio Resource Control (RRC) signaling.

5. The method according to claim 2, characterized in that, Under the limited bandwidth sub-configuration file, resource blocks (RBs) exceeding the bandwidth limit of the sub-configuration file are determined to be invalid.

6. The method according to claim 2, characterized in that, Under the limited bandwidth sub-configuration file, physical downlink control channel (PDCCH) monitoring is limited to the control resource set (CORESET) portion within the limited bandwidth range, ignoring PDCCH monitoring opportunities outside the limited bandwidth range.

7. The method according to claim 2, characterized in that, When the terminal device misses the handover instruction, it decodes the subsequent DCI based on the shared core control configuration and aligns it with the network focus according to the subsequent DCI.

8. A bandwidth adaptation method for network-side equipment, characterized in that, include: Within the active bandwidth portion (BWP) configured for the terminal-side device, at least two sub-profiles are configured for the terminal-side device, and the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile. In response to changes in the service traffic demands of the terminal-side device, a sub-profile switching instruction is sent to the terminal-side device via downlink control information (DCI) or MAC CE. After sending the switching command, the terminal-side device is scheduled according to the resource configuration of the target sub-configuration file.

9. The method according to claim 8, characterized in that, The network-side device is configured with one and only one active BWP for the terminal-side device.

10. The method according to claim 8, characterized in that, The network-side device does not modify the BWP-level core control configuration during the sub-configuration file switching process; the core control configuration is a fixed configuration pre-configured by the network side to the terminal-side device through Radio Resource Control (RRC) signaling.

11. The method according to claim 8, characterized in that, Under the limited bandwidth sub-configuration file, the terminal-side device is scheduled only on resource blocks (RBs) within the limited bandwidth range, without exceeding the allocated resources within the limited bandwidth.

12. The method according to claim 8, characterized in that, After sending the switching command, the network-side device does not require the terminal-side device to confirm the switching, and directly schedules the terminal-side device according to the resource configuration of the target sub-configuration file.

13. The method according to claim 8, characterized in that, If the terminal device misses the handover instruction, the network side will resend the handover instruction or current scheduling information via DCI during the next shared PDCCH listening opportunity.

14. The method according to any one of claims 1 to 13, characterized in that, The sub-configuration files share the core control configuration of the active BWP. The core control configuration includes at least the control resource set (CORESET) configuration, the physical downlink control channel (PDCCH) monitoring timing configuration, and the downlink control information (DCI) format and size configuration being monitored.

15. The method according to any one of claims 1 to 13, characterized in that, The adaptation parameters of the sub-configuration file are the minimum configuration set that affects the power consumption of the terminal-side device. The minimum configuration set includes at least one or more of the following: maximum bandwidth, maximum rank, and search space group SSSG period.

16. The method according to any one of claims 1 to 13, characterized in that, The conditions that trigger the switching of the sub-profile are: the size of the service data packets of the terminal device increases to exceed the carrying capacity of the current limited bandwidth sub-profile, or the amount of service data decreases to below the carrying capacity requirement of the broadband sub-profile.

17. The method according to any one of claims 1 to 13, characterized in that, The bandwidth of the broadband sub-profile is consistent with the bandwidth of the single active BWP.

18. The method according to any one of claims 1 to 13, characterized in that, Both of the at least two sub-configuration files are configured within the active BWP.

19. A network-side device for implementing the method according to any one of claims 1 to 20, characterized in that, At least one module in the network-side device is configured to perform at least one of the following functions: within the active bandwidth portion (BWP) configured for the terminal-side device, configure at least two sub-profiles for the terminal-side device, wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile; in response to changes in the service traffic requirements of the terminal-side device, send a sub-profile switching instruction to the terminal-side device via downlink control information (DCI); and after sending the switching instruction, schedule the terminal-side device according to the resource configuration of the target sub-profile.

20. A terminal-side device for implementing the method according to any one of claims 1 to 18, characterized in that, At least one module in the terminal-side device is configured to perform at least one of the following functions: receiving configuration information, wherein the configuration information is configured to configure at least two sub-profiles for the terminal-side device within the configured active bandwidth portion (BWP), wherein the sub-profiles include at least a limited bandwidth sub-profile and a wideband sub-profile; Receive a sub-profile switching instruction; according to the switching instruction, switch from the current sub-profile to the target sub-profile within the currently active BWP.

21. A communication device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 18.

22. A computer-readable medium storing a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 18.

23. A mobile communication system comprising at least one network-side device as described in claim 19 and / or at least one terminal-side device as described in claim 20.

Images