BWP control method and apparatus, terminal and network-side device

Abstract

The present application belongs to the technical field of communications, and discloses a BWP control method and apparatus, a terminal, and a network-side device. The BWP control method in an embodiment of the present application comprises: when a terminal meets a first condition, the terminal adjusts a bwp-inactivityTimer of a first BWP or performs BWP switching. The first BWP is a BWP in an active state, and the first condition comprises at least one of the following : an LP-WUS being detected, the LP-WUS being used for triggering the terminal to monitor a PDCCH; and uplink transmission being required to be performed during LP-WUS monitoring.

Description

BWP control methods, devices, terminals, and network-side equipment

[0001] Cross-references

[0002] This disclosure claims priority to Chinese Patent Application No. 202411051972.3, filed on August 1, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a BWP control method, device, terminal, and network-side equipment. Background Technology

[0004] In related technologies, to reduce terminal power consumption, a low-power receiver module, namely a Low Power Wake-Up Radio (LP-WUR) or an Almost Zero Power Wake-Up Radio (AZP-WUR), is introduced into the terminal. In power-saving mode, the terminal activates the LP-WUR to listen for the Low Power Wake-Up Signal (LP-WUS), while the terminal's main communication module (or main receiver module) is either off or in sleep mode. When downlink data arrives, the network-side device sends LP-WUS to the terminal. After the terminal detects LP-WUS through the LP-WUS receiver module, it can activate or wake up the main communication module to receive downlink data. Furthermore, if uplink data needs to be transmitted while the terminal is listening for LP-WUS through the LP-WUS receiver module, it can also activate or wake up the main communication module to transmit uplink data. However, in related technologies, there is no corresponding solution for bandwidth part (BWP) control when data transmission occurs while the terminal is listening for LP-WUS. Summary of the Invention

[0005] This application provides a BWP control method, apparatus, terminal, and network-side device, which can adjust the BWP inactivity timer of the active BWP or perform BWP switching in a timely manner when data transmission occurs while the terminal is monitoring LP-WUS, thus helping to ensure data transmission.

[0006] Firstly, a BWP control method is provided, the method comprising:

[0007] If the terminal meets the first condition, the terminal adjusts the BWP inactivity timer (bwp-inactivityTimer) of the first bandwidth portion BWP or performs BWP switching;

[0008] Wherein, the first BWP is a BWP that is in an active state, and the first condition includes at least one of the following:

[0009] A low-power wake-up signal LP-WUS is detected, which is used to trigger the terminal to listen to the Physical Downlink Control Channel (PDCCH).

[0010] Uplink transmission is required during LP-WUS listening.

[0011] Secondly, a BWP control device is provided, the device comprising:

[0012] The processing module is used to adjust the BWP inactivity timer bwp-inactivityTimer of the first bandwidth portion BWP or to switch the BWP when the terminal meets the first condition.

[0013] Wherein, the first BWP is a BWP that is in an active state, and the first condition includes at least one of the following:

[0014] A low-power wake-up signal LP-WUS is detected, and the LP-WUS is used to trigger the terminal to listen to the physical downlink control channel PDCCH.

[0015] Uplink transmission is required during LP-WUS listening.

[0016] Thirdly, a BWP control method is provided, which includes:

[0017] The network-side device performs a second operation, which includes at least one of the following:

[0018] Send a low-power wake-up signal LP-WUS to the terminal, wherein the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes BWP related information;

[0019] The terminal receives first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS.

[0020] Send a second instruction message to the terminal;

[0021] The first indication information is used to indicate any of the following:

[0022] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0023] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0024] There is data scheduling for the terminal;

[0025] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs;

[0026] The second indication information is used to indicate at least one of the following:

[0027] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0028] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0029] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0030] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0031] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0032] The first BWP is an active BWP.

[0033] Fourthly, a BWP control device is provided, the device comprising:

[0034] A processing module is configured to perform a second operation, the second operation including at least one of the following:

[0035] Send a low-power wake-up signal LP-WUS to the terminal, wherein the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes bandwidth portion (BWP) related information;

[0036] The terminal receives first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS.

[0037] Send a second instruction message to the terminal;

[0038] The first indication information is used to indicate any of the following:

[0039] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0040] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0041] There is data scheduling for the terminal;

[0042] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs;

[0043] The second indication information is used to indicate at least one of the following:

[0044] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0045] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0046] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0047] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0048] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0049] The first BWP is an active BWP.

[0050] Fifthly, a BWP-controlled device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect.

[0051] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0052] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to adjust the BWP inactivity timer bwp-inactivityTimer of the first bandwidth portion BWP or to perform BWP switching when the terminal meets a first condition.

[0053] Wherein, the first BWP is a BWP that is in an active state, and the first condition includes at least one of the following:

[0054] A low-power wake-up signal LP-WUS is detected, and the LP-WUS is used to trigger the terminal to listen to the physical downlink control channel PDCCH.

[0055] Uplink transmission is required during LP-WUS listening.

[0056] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0057] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the processor is configured to perform a second operation, the second operation including at least one of the following:

[0058] Send a low-power wake-up signal LP-WUS to the terminal, wherein the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes BWP related information;

[0059] The terminal receives first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS.

[0060] Send a second instruction message to the terminal;

[0061] The first indication information is used to indicate any of the following:

[0062] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0063] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0064] There is data scheduling for the terminal;

[0065] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs;

[0066] The second indication information is used to indicate at least one of the following:

[0067] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0068] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0069] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0070] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0071] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0072] The first BWP is an active BWP.

[0073] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the third aspect.

[0074] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the BWP control method as described in the first aspect, and the network-side device can be used to perform the steps of the BWP control method as described in the third aspect.

[0075] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect.

[0076] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the third aspect.

[0077] In this embodiment, when the terminal meets a first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch; wherein, the first BWP is an active BWP, and the first condition includes at least one of the following: detecting LP-WUS, the LP-WUS being used to trigger the terminal to listen to the PDCCH; and needing to perform uplink transmission during the DRX inactive time. That is, in this embodiment, when the terminal is listening to LP-WUS, the bwp-inactivityTimer of the active BWP can be adjusted or a BWP switch can be performed in a timely manner when data transmission is present, which helps to ensure data transmission. Attached Figure Description

[0078] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0079] Figure 2 is a schematic diagram of the LP WUR operation provided by related technologies;

[0080] Figure 3 is a schematic diagram of the on / off key control signal provided by the related technology;

[0081] Figure 4 is a flowchart of a BWP control method provided in an embodiment of this application;

[0082] Figure 5a is a schematic diagram of the bwp-InactivityTimer expiring during the time period from receiving LP-WUS to listening to PDCCH, provided by an embodiment of this application.

[0083] Figure 5b is a schematic diagram of the expiration of bwp-InactivityTimer within the time period from the terminal waking up the main communication module to receiving the pre-configured uplink grant or the uplink grant dynamically scheduled by PDCCH, as provided in the embodiments of this application.

[0084] Figure 6 is a flowchart of another BWP control method provided in an embodiment of this application;

[0085] Figure 7 is a structural diagram of a BWP control device provided in an embodiment of this application;

[0086] Figure 8 is a structural diagram of another BWP control device provided in an embodiment of this application;

[0087] Figure 9 is a structural diagram of the communication device provided in an embodiment of this application;

[0088] Figure 10 is a structural diagram of the terminal provided in an embodiment of this application;

[0089] Figure 11 is a structural diagram of the network-side device provided in an embodiment of this application. Detailed Implementation

[0090] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0091] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0092] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0093] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0094] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0095] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0096] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0097] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0098] I. Low-power receiver module

[0099] The low-power receiver module, also known as a low-power wake-up receiver or near-zero power receiver, works on the principle that the terminal's receiver comprises a first module and a second module, as shown in Figure 2. The first module is the main communication module (also called the main receiving module, main receiver, or main radio module, etc.), used for transmitting and receiving mobile communication data. The second module is the low-power receiver module (also called the low-power wake-up receiver module or low-power receiver module), used to receive the wake-up signal. In power-saving mode, the terminal activates the low-power receiver module to listen for the low-power wake-up signal, while the main communication module is off or in sleep mode. When downlink data arrives, the network sends a wake-up signal to the terminal. After the terminal detects the wake-up signal through the low-power receiver module, it triggers the main communication module to turn on or be woken up after a series of checks. At this time, the low-power receiver module transitions from the active state to the off state. The low-power wake-up receiver module can be continuously or intermittently activated, and when activated, it can receive the low-power wake-up signal.

[0100] II. Low-power wake-up signal

[0101] To reduce receiving activity in standby mode and effectively shut down the radio frequency (RF) and baseband modules (e.g., modem), thereby significantly reducing power consumption during communication reception, this can be achieved by introducing a near-zero power receiver into the terminal's receiver module. This near-zero power receiver eliminates the need for complex signal detection (such as amplification, filtering, quantization, etc.) in the RF module and signal processing in the baseband module, relying solely on passive matched filtering and low-power signal processing.

[0102] On the base station side, by triggering a wake-up signal on demand, the receiver with near-zero power can be activated to receive the activation notification, thereby triggering a series of processes within the terminal, such as turning on the radio frequency transceiver and baseband processing modules.

[0103] These wake-up signals are typically simple on-off keying signals, the time-domain representation of which is shown in Figure 3. The receiver can then detect the wake-up notification through simple energy detection and subsequent sequence detection and recognition. Furthermore, while the terminal activates its low-power wake-up receiver to receive the wake-up signal, the main receiving module can enter sleep mode or shut down to maintain a low power consumption level, thus saving power by receiving the wake-up signal. The wake-up signal can also warn the receiver of the presence of physical downlink control channel transmission or other communication.

[0104] III. RRC Connected State (RRC_CONNECTED) LP-WUS

[0105] In related technologies, the LP-WUS in the connection state is used to trigger PDCCH listening, specifically including:

[0106] For RRC connection mode, from the perspective of Radio Access Network Working Group 1 (RAN1), the following LP-WUS procedure to trigger PDCCH monitoring is further investigated:

[0107] Case 1: PDCCH listening is triggered by LP-WUS with a Connected Discontinuous Reception (C-DRX) configuration.

[0108] Option 1-1: Triggers drx-OnDurationTimer startup based on the LP-WUS listener configuration before the DRX duration timer (drx-OnDurationTimer). This option can replace the DCP function.

[0109] Option 1-2: Based on the LP-WUS listening configuration, perform LP-WUS listening at least outside of the traditional C-DRX activation time to trigger PDCCH listening. PDCCH monitoring may be unrelated to DRX-OnDurationTimer.

[0110] Option 1-2-1: When listening to LP-WUS, PDCCH listening can be additionally triggered based on the traditional C-DRX cycle and DRX-OnDurationTimer.

[0111] If this approach is adopted, it should be configured together with option 1-1 to achieve energy savings compared to the conventional C-DRX.

[0112] Option 1-2-2: When listening to LP-WUS, the traditional C-DRX cycle and DRX-OnDurationTimer will not trigger PDCCH listening.

[0113] Options 1-3: Based on the LP-WUS listening configuration, perform LP-WUS listening for at least the traditional C-DRX activity period to trigger PDCCH listening.

[0114] The combination of options in Case 1 should be considered. RAN1 does not discuss C-DRX-related timers other than DRX-OnDurationTimer, as this depends on RAN Work Group 2 (RAN2).

[0115] It should be noted that the above does not exclude the possibility of supporting a fallback mechanism to trigger PDCCH listening.

[0116] IV. BWP Switching Method

[0117] A currently connected User Equipment (UE) (i.e., terminal) can be configured with one or more Block Devices (BWPs) within a serving cell. BWP handover is used to simultaneously activate an inactive BWP and deactivate an active BWP. BWP handover methods include control using PDCCH, control using bwp-InactivityTimer, control using RRC signaling, or handover by the Media Access Control (MAC) entity itself when performing random access procedures or detecting consecutive Listen Before Talk (LBT) failures on a Special Cell (SpCell).

[0118] For BWP handover controlled by bwp-InactivityTimer, one bwp-InactivityTimer is configured for each serving cell, and one active BWP is associated with one bwp-InactivityTimer. When the currently active BWP is not the default BWP (indicated by defaultDownlinkBWP-Id) or not the initial BWP (when defaultDownlinkBWP-Id is not configured), and when dormantBWP-Id is configured but not a dormant BWP (associated with dormantBWP-Id), and when scheduling is involved, the following applies:

[0119] The BWP received a PDCCH indicating downlink allocation or uplink authorization scrambled with Cell Radio Network Temporary Identity (C-RNTI) / Configured Scheduling Radio Network Temporary Identity (CS-RNTI);

[0120] Alternatively, an instruction to allocate a downlink PDCCH was received, scrambled with the Group Radio Network Temporary Identity (G-RNTI) / Group Configured Scheduling Radio Network Temporary Identity (G-CS-RNTI) configured for multicast.

[0121] Alternatively, a PDCCH indicating downlink allocation or uplink authorization was received for the activated BWP with C-RNTI / CS-RNTI scrambling.

[0122] Alternatively, a Protocol Data Unit (PDU) was transmitted on the configured grant and no LBT failure indication was received from the underlying layer;

[0123] Alternatively, a unicast-related MAC PDU or a Multicast and Broadcast Service (MBS)-related MAC PDU was received on the downlink allocation.

[0124] If there is no running random access in the serving cell or the running random access process has successfully completed after receiving the C-RNTI scrambled PDCCH, then start or restart the bwp-InactivityTimer related to the BWP.

[0125] For non-Reduced Capability (RedCap) UEs, the initial BWP is the BWP configured for the initial downlink BWP. For RedCap UEs, the initial BWP is either the initial downlink BWP-RedCap configuration (if configured) or the initial downlink BWP (if not configured).

[0126] When the bwp-InactivityTimer associated with the active BWP expires, if a default BWP is configured, the UE will perform a BWP handover and switch to the default BWP; otherwise, the UE will switch to the initial BWP.

[0127] When the UE receives a PDCCH for BWP handover, and the active BWP indicated by the PDCCH is not the default BWP (the BWP indicated by defaultDownlinkBWP-Id) or not the initial BWP (when defaultDownlinkBWP-Id is not configured), and is not the dormitory BWP when dormitoryBWP-Id is configured, then the UE starts or restarts the bwp-InactivityTimer associated with that BWP.

[0128] When a UE performs a Random Access Channel (RACH) procedure in a serving cell, after selecting a carrier, the UE stops the bwp-inactivityTimer of the active BWP associated with that serving cell for that carrier. If the cell is a secondary cell (SCell), the UE also stops the bwp-inactivityTimer of the active BWP of the SCell.

[0129] When the configuration of bwp-InactivityTimer is released in the RRC signaling issued by the network side, the UE must stop the bwp-InactivityTimer of the active BWP of the serving cell.

[0130] The BWP control method provided in this application will be described in detail below with reference to the accompanying drawings, through some embodiments and application scenarios.

[0131] Please refer to Figure 4, which is a flowchart of a BWP control method provided in an embodiment of this application. This method can be executed by a terminal, and as shown in Figure 4, it includes the following steps:

[0132] Step 401: If the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0133] Wherein, the first BWP is a BWP that is in an active state, and the first condition includes at least one of the following:

[0134] LP-WUS is detected, and the LP-WUS is used to trigger the terminal to listen to the PDCCH.

[0135] Uplink transmission is required during LP-WUS listening.

[0136] In this embodiment, the first BWP can be the BWP that the terminal is currently active in, that is, the first BWP is the BWP that the terminal is currently working on. The first BWP can be a BWP configured by the network-side device, and is not a default BWP or an initial BWP; or the first BWP can be a default BWP or an initial BWP.

[0137] The aforementioned adjustments to the bwp-inactivityTimer of the first BWP may include, but are not limited to, enabling, re-enabling, or stopping the bwp-inactivityTimer of the first BWP, or adjusting the timer duration of the bwp-inactivityTimer of the first BWP. For example, if the first BWP is not the default BWP or the initial BWP, the bwp-inactivityTimer of the first BWP can be enabled, re-enabling, or stopped.

[0138] The aforementioned BWP switching can be understood as switching the terminal's operating BWP from the first BWP to a different BWP. For example, if the first BWP is the default BWP or the initial BWP, the terminal's operating BWP can be switched from the first BWP to another pre-configured BWP.

[0139] The aforementioned LP-WUS is used to trigger the terminal to listen to the PDCCH. In some optional embodiments, the aforementioned LP-WUS may include BWP control-related information, for example, the aforementioned BWP control-related information may include at least one of BWP-related information and indication information for BWP control.

[0140] The aforementioned uplink transmission is required during LP-WUS listening. For example, if information sent by a non-access stratum is received during LP-WUS listening, this information is used to trigger uplink transmission.

[0141] Regarding the aforementioned terminal adjusting the bwp-inactivityTimer of the first BWP or switching BWPs, for example, the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or switch BWPs based on the first BWP. For instance, if the first BWP is not the default BWP or the initial BWP, the bwp-inactivityTimer of the first BWP can be adjusted; if the first BWP is the default BWP or the initial BWP, the bwp-inactivityTimer of the first BWP can be adjusted. In the case of a BWP, a BWP handover can be performed; alternatively, the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover based on the detected LP-WUS. For example, it can decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover based on the BWP control-related information carried by the aforementioned LP-WUS; or, it can decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover based on the protocol agreement. For example, if the protocol stipulates that the bwp-inactivityTimer of the first BWP is adjusted when the terminal meets a first condition, then the terminal adjusts the bwp-inactivityTimer of the first BWP when the first condition is met; if the protocol stipulates that the terminal performs a BWP handover when the first condition is met, then the terminal performs a BWP handover when the first condition is met.

[0142] In practical applications, a terminal in connected mode can listen for LP-WUS via low-power wake-up of the receiver while the main communication module is off or in sleep mode. Upon detecting LP-WUS, it can then activate or wake up the main communication module to perform PDCCH listening. Alternatively, it can activate or wake up the main communication module to perform uplink transmission if uplink transmission is required while listening for LP-WUS. Examples are provided below for each scenario:

[0143] Scenario 1: When the terminal's working BWP (i.e., the first BWP) is not the default BWP or the initial BWP, when the terminal detects LP-WUS, it wakes up the main communication module to listen to the PDCCH. However, between receiving LP-WUS and listening to the PDCCH, the bwp-InactivityTimer of the terminal's currently working BWP may expire, as shown in Figure 5a. In this case, the terminal's working BWP will switch to the default BWP or the initial BWP. However, if LP-WUS triggers PDCCH listening for downlink scheduling, it indicates that there may be a large amount of data transmission to be performed later. Switching the terminal's working BWP to the default BWP or the initial BWP is not conducive to the transmission of large amounts of data. In this case, this embodiment can adjust the bwp-InactivityTimer of the terminal's currently working BWP (i.e., the first BWP) when LP-WUS is detected. For example, the bwp-inactivityTimer of the first BWP can be enabled, re-enabled, or disabled. This helps reduce the occurrence of the bwp-InactivityTimer of the terminal's currently working BWP expiring before the terminal listens to the PDCCH, thereby helping to ensure the throughput of downlink transmission.

[0144] Scenario 2: When the terminal detects LP-WUS, if the LP-WUS includes BWP control-related information, the terminal can adjust the bwp-inactivityTimer of the first BWP or switch BWPs based on this information. For example, if the BWP control-related information includes indication information for BWP control, the terminal can adjust the bwp-inactivityTimer of the first BWP if the indication information instructs it to do so. Alternatively, if the indication information instructs the terminal to switch BWPs, the terminal can switch BWPs. For instance, if the first BWP is a default BWP or an initial BWP, it can switch to the network-preconfigured BWP, which improves data transmission throughput. If the first BWP is not a default BWP or an initial BWP, it can switch to the default BWP or an initial BWP, thus saving power while ensuring data transmission.

[0145] Scenario 3: When the terminal's working BWP is not the default BWP or initial BWP, and the terminal is using a low-power receiver to listen to LP-WUS (i.e., the terminal is not in the PDCCH listening phase), if the terminal has uplink data to transmit, the bwp-InactivityTimer may expire during the time period from when the terminal wakes up the main communication module until it receives the pre-configured uplink grant or the uplink grant dynamically scheduled by the PDCCH, as shown in Figure 5b. In this case, the terminal's working BWP will also switch to the default BWP or initial BWP. In this situation, this embodiment can adjust the bwp-InactivityTimer of the terminal's currently working BWP (i.e., the first BWP) when uplink transmission is required during LP-WUS listening. For example, the bwp-inactivityTimer of the first BWP can be enabled, re-enabled, or disabled. This helps reduce the occurrence of the bwp-InactivityTimer of the terminal's currently working BWP expiring before the terminal performs uplink transmission, thereby helping to ensure the uplink transmission throughput.

[0146] Scenario 4: If the BWP used by the terminal is the default BWP or the initial BWP, and uplink transmission is required during LP-WUS monitoring, the terminal's BWP can be switched to the pre-configured BWP to improve uplink throughput.

[0147] Scenario 5: When the terminal detects LP-WUS and needs to perform uplink transmission, if the BWP that the terminal is working on is not the default BWP or the initial BWP, the bwp-InactivityTimer of the terminal's working BWP (i.e., the first BWP) can be adjusted. For example, the bwp-inactivityTimer of the first BWP can be enabled, re-enabled, or disabled. This helps to reduce the occurrence of the bwp-InactivityTimer of the terminal's currently working BWP expiring before the terminal listens to the PDCCH, thereby helping to ensure the throughput of data transmission. If the terminal's working BWP is the default BWP or the initial BWP, a BWP switch can be performed. For example, it can be switched to a pre-configured BWP to improve the throughput of data transmission.

[0148] In this embodiment, when the terminal meets a first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch; wherein, the first BWP is an active BWP, and the first condition includes at least one of the following: detecting LP-WUS, the LP-WUS being used to trigger the terminal to listen to the PDCCH; and needing to perform uplink transmission during the DRX inactive time. That is, in this embodiment, when data transmission exists while the terminal is listening to LP-WUS, the bwp-inactivityTimer of the active BWP can be adjusted or a BWP switch can be performed, which helps to ensure data transmission.

[0149] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0150] If the terminal listens to LP-WUS during the inactive time of Discontinuous Reception (DRX), and the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0151] For example, if the UE (i.e., the aforementioned terminal) is configured with a low-power receiver, and the network-side device sends LP-WUS configuration information to the UE and activates RRC_CONNECTED UE listening to LP-WUS, the UE is in DRX inactive time and listens to LP-WUS during this time. If the UE meets the first condition while listening to LP-WUS during DRX inactive time, the UE adjusts the bwp-inactivityTimer of the activated BWP or performs a BWP handover.

[0152] In this embodiment, the terminal listens to LP-WUS during the DRX inactive time. If the terminal meets the first condition during the period when the terminal is listening to LP-WUS during the DRX inactive time, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching. This helps to ensure data transmission while saving power.

[0153] Optionally, the terminal adjusts the bwp-inactivityTimer of the first BWP, including:

[0154] The terminal enables, restarts, or stops the bwp-inactivityTimer of the first BWP.

[0155] In this embodiment, when the terminal meets the first condition, the bwp-inactivityTimer of the first BWP is enabled, restarted, or stopped. This helps to reduce the occurrence of the bwp-inactivityTimer of the first BWP expiring before the terminal listens to the PDCCH or before the terminal performs uplink transmission.

[0156] Optionally, the first condition includes the terminal detecting the LP-WUS;

[0157] The terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch, including:

[0158] If the detected LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0159] The first indication information is used to indicate any of the following:

[0160] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0161] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0162] There is data scheduling for the terminal;

[0163] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs.

[0164] It is understood that when the first indication information is used to indicate the adjustment of the bwp-inactivityTimer of the first BWP, the terminal can adjust the bwp-inactivityTimer of the first BWP; when the first indication information is used to indicate BWP switching, the terminal can perform BWP switching. For example, when the first indication information is used to indicate BWP switching, the terminal can switch the working BWP from the first BWP to a pre-configured BWP; or, if the above LP-WUS also includes BWP-related information, the terminal can perform BWP switching based on the BWP-related information. For example, the terminal can switch the working BWP from the first BWP to a BWP determined according to the above BWP-related information.

[0165] For example, the pre-configured BWP mentioned above may be a BWP represented by a BWP identifier carried in the control information received by the terminal from the network-side device. For instance, the terminal receives control information from the network-side device, which includes a BWP identifier to indicate that the terminal will switch to the BWP represented by the BWP identifier if the terminal meets a first condition.

[0166] When the aforementioned first indication information indicates any of the following, the terminal may adjust the bwp-inactivityTimer of the first BWP or perform a BWP switch. For example, it may be agreed through an agreement that the bwp-inactivityTimer of the first BWP may be adjusted when the first indication information indicates any of the following; or it may be agreed through an agreement that a BWP switch may be performed when the aforementioned first indication information indicates any of the following; or, when the aforementioned first indication information indicates any of the following, the terminal may decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP switch based on the first BWP. For example, if the first BWP is not a default BWP or an initial BWP, the bwp-inactivityTimer of the first BWP may be adjusted; if the first BWP is a default BWP or an initial BWP, a BWP switch may be performed.

[0167] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0168] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0169] Data scheduling exists for the terminal.

[0170] In this embodiment, when the detected LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching. This not only helps to improve the flexibility and accuracy of BWP control, but also ensures that the function of the currently detected LP-WUS is to trigger the terminal to perform data scheduling, thereby ensuring the performance of data transmission by adjusting the BWP.

[0171] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0172] If the terminal meets the second condition, then if the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0173] The second condition includes at least one of the following:

[0174] The terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold;

[0175] The terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold;

[0176] The terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold;

[0177] The terminal requires the data transmission volume to be higher than or equal to the fourth threshold.

[0178] The terminal requires a data throughput rate higher than or equal to the fifth threshold.

[0179] The terminal requires data transmission latency to be higher than or equal to the sixth threshold.

[0180] The terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.

[0181] At least one of the first threshold, second threshold, third threshold, fourth threshold, fifth threshold and sixth threshold mentioned above can be reasonably set according to actual needs, and this embodiment does not limit it.

[0182] For example, if the UE satisfies at least one of the following conditions, the bwp-inactivityTimer of the first BWP may be adjusted or a BWP switch may be performed:

[0183] The UE is a type of UE with a large data transmission volume;

[0184] The UE is a type of UE with a high data throughput.

[0185] The UE is a type of UE that is relatively sensitive to data transmission latency;

[0186] The UE has high requirements for data transmission volume;

[0187] The UE has high data throughput requirements;

[0188] The UE has high requirements for data transmission latency;

[0189] The UE supports adjusting the bwp-inactivityTimer based on LP-WUS or supports BWP handover based on LP-WUS.

[0190] It is understood that if the second condition includes the terminal supporting adjustment of bwp-inactivityTimer according to LP-WUS, then the terminal can adjust the bwp-inactivityTimer of the first BWP; if the second condition includes the terminal supporting BWP switching according to LP-WUS, then the terminal performs BWP switching if the first condition is met; if the second condition does not include either the terminal supporting adjustment of bwp-inactivityTimer according to LP-WUS or the terminal supporting BWP switching according to LP-WUS, then the terminal can adjust the bwp-inactivityTimer of the first BWP or perform BWP switching if the first condition is met. For example, it can be agreed that if the terminal meets the first condition, the bwp-inactivityTimer of the first BWP will be adjusted if the second condition is met; or it can be agreed that if the terminal meets the first condition, the BWP will be switched if the second condition is met; or, if the terminal meets the first condition, the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or perform BWP switching based on the first BWP if the second condition is met. For example, if the first BWP is not the default BWP or initial BWP. In the case of a BWP, the bwp-inactivityTimer of the first BWP can be adjusted; when the first BWP is a default BWP or an initial BWP, the BWP can be switched.

[0191] In some alternative embodiments, if the second condition is not met, the terminal may still control the BWP based on relevant technology or a traditional (legacy) BWP control method if the first condition is met.

[0192] In this embodiment, if the second condition is met, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch when the first condition is met. This not only meets the transmission requirements of terminals with relatively high transmission requirements, but also does not affect the BWP control of terminals with relatively low transmission requirements.

[0193] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0194] If the terminal receives the second indication information from the network-side device, then if the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0195] The second indication information is used to indicate at least one of the following:

[0196] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0197] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0198] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0199] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0200] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0201] In this embodiment, if the terminal meets the first condition when the second indication information indicates at least one of the following:

[0202] The terminal allows adjustment of bwp-inactivityTimer according to LP-WUS;

[0203] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0204] When the terminal detects that LP-WUS has triggered the terminal to listen to PDCCH, it adjusts the bwp-inactivityTimer of the first BWP.

[0205] The serving cell of the terminal supports the terminal in adjusting bwp-inactivityTimer according to LP-WUS;

[0206] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0207] If the terminal meets the first condition, and the second indication information indicates at least one of the following:

[0208] Allows BWP switching based on LP-WUS;

[0209] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0210] The terminal performs a BWP handover when it detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0211] The serving cell of the terminal supports the terminal in performing BWP handover based on LP-WUS;

[0212] The serving cell of the terminal supports BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0213] It should be noted that, when the second indication information is only used to indicate that the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency, if the terminal meets the first condition, the terminal can adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover. For example, it can be agreed by protocol that the bwp-inactivityTimer of the first BWP will be adjusted upon receiving the second indication information; or it can be agreed by protocol that if the terminal meets the first condition upon receiving the second indication information, a BWP handover will be performed; or, if the terminal meets the first condition upon receiving the second indication information, the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover based on the first BWP. For example, if the first BWP is not a default BWP or an initial BWP, the bwp-inactivityTimer of the first BWP can be adjusted; if the first BWP is a default BWP or an initial BWP, a BWP handover can be performed.

[0214] For example, the network-side device can send the aforementioned second instruction information to the terminal via a System Information Block (SIB) message or an RRC reconfiguration message.

[0215] In this embodiment, the network-side device sends a second instruction message to the terminal to instruct the terminal to adjust the bwp-inactivityTimer of the first BWP or to switch BWPs. This allows the network control terminal to perform BWP control based on LP-WUS, thereby improving the flexibility of control.

[0216] Optionally, the method further includes:

[0217] The terminal reports first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS, or the capability information is used to indicate whether the terminal supports or does not support BWP switching according to LP-WUS.

[0218] The type of the terminal mentioned above, for example, whether the terminal is a terminal type with a data transmission volume greater than or equal to a first threshold, and / or whether the terminal is a terminal type with a data throughput rate greater than or equal to a second threshold.

[0219] The requirements of the aforementioned terminal for data transmission volume, for example, whether the aforementioned terminal requires data transmission volume to be higher than or equal to the fourth threshold.

[0220] The aforementioned terminal's requirements for data throughput, for example, whether the aforementioned terminal's data throughput requirements are higher than or equal to the fifth threshold.

[0221] The aforementioned terminal's requirements for data transmission latency, for example, whether the aforementioned terminal's requirements for data transmission latency are higher than or equal to the sixth threshold.

[0222] For example, when a terminal reports first information, the network-side device, upon receiving the first information, can determine whether to send second instruction information to the terminal, or whether to send updated second instruction information to the terminal, based on the first information. This improves the rationality of the network-side device instructing the terminal to perform BWP control. For instance, if the first information indicates at least one of the following, the network-side device can send the second instruction information or updated second instruction information to the terminal; otherwise, the network-side device may not send the second instruction information or updated second instruction information to the terminal:

[0223] The terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold;

[0224] The terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold;

[0225] The terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold;

[0226] The terminal requires the data transmission volume to be higher than or equal to the fourth threshold.

[0227] The terminal requires a data throughput rate higher than or equal to the fifth threshold.

[0228] The terminal requires data transmission latency to be higher than or equal to the sixth threshold.

[0229] The terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.

[0230] For example, the terminal can report the first information via Non-access Stratum (NAS) signaling, such as through a registration request message; or, the terminal can report the first information via Access Stratum (AS) signaling, such as through a UE capability reporting message, a UE auxiliary information reporting message, a UE information response message, etc.

[0231] Optionally, before the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch when the terminal meets the first condition, the method further includes:

[0232] When the terminal receives updated second indication information from the network-side device, the terminal adjusts the bwp-inactivityTimer of the first BWP.

[0233] For example, after the network-side device sends the second indication information to the terminal, it receives the first information reported by the terminal. In this case, the network-side device can send updated second indication information to the terminal based on the first information. The terminal can adjust the bwp-inactivityTimer of the first BWP according to the updated second indication information.

[0234] It should be noted that after the terminal adjusts the bwp-inactivityTimer of the first BWP based on the updated second instruction information, if the terminal meets the first condition, the terminal can adjust the bwp-inactivityTimer of the first BWP again or perform a BWP switch.

[0235] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0236] When the terminal detects LP-WUS and the LP-WUS includes BWP-related information, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch based on the BWP-related information.

[0237] For example, the aforementioned BWP-related information may include, but is not limited to, information used to determine the BWP, the timing duration of the bwp-inactivityTimer update for the first BWP, etc.

[0238] In this embodiment, the bwp-inactivityTimer of the first BWP is adjusted or BWP switching is performed based on the BWP-related information carried by LP-WUS. This not only improves the accuracy of BWP control and ensures the throughput of data transmission, but also saves signaling overhead.

[0239] Optionally, the BWP-related information includes a BWP index, which is used to instruct the terminal to listen to the PDCCH on the BWP indicated by the BWP index when it receives the LP-WUS.

[0240] In this embodiment, by carrying a BWP index in the LP-WUS, the terminal can directly listen to the PDCCH on the BWP indicated by the BWP index when the LP-WUS is detected. This not only enables accurate control of the terminal's BWP, but also simplifies the process.

[0241] Optionally, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch based on the BWP-related information, including at least one of the following:

[0242] When the second BWP is the same as the first BWP, the terminal adjusts the bwp-inactivityTimer of the first BWP;

[0243] If the second BWP is different from the first BWP, the terminal performs a BWP switch;

[0244] The second BWP is a BWP determined based on the BWP-related information.

[0245] In this embodiment, when the second BWP is the same as the first BWP, the terminal adjusts the bwp-inactivityTimer of the first BWP; when the second BWP is different from the first BWP, the terminal performs BWP switching, which ensures that the terminal performs PDCCH listening on the BWP indicated by the network-side device.

[0246] Optionally, when the second BWP is different from the first BWP, the terminal performs a BWP switch, including at least one of the following:

[0247] If the second BWP is different from the first BWP, and if the second BWP is not the default BWP or the initial BWP, then the terminal deactivates the first BWP, activates the second BWP, and starts the bwp-inactivityTimer of the second BWP when the second BWP is activated.

[0248] If the second BWP is different from the first BWP, and if the second BWP is the default BWP or the initial BWP, then the terminal deactivates the first BWP and activates the second BWP.

[0249] In this embodiment, when the second BWP is different from the first BWP and is not the default BWP or the initial BWP, the bwp-inactivityTimer of the second BWP can be started when the terminal's working BWP is switched from the first BWP to the second BWP (i.e., the first BWP is deactivated and the second BWP is activated). This allows data to be transmitted through the second BWP before the bwp-inactivityTimer expires, which helps to improve the throughput of data transmission. When the second BWP is different from the first BWP and is the default BWP or the initial BWP, the terminal can switch the terminal's working BWP from the first BWP to the second BWP and transmit data based on the second BWP, which helps to reduce power consumption.

[0250] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0251] If the terminal is in a single-connection state, or if the terminal is only configured with a special cell SpCell, then if the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP handover.

[0252] In this embodiment, the SpCell mentioned above may include the primary cell (PCell) and the PSCell.

[0253] In practical applications, if, under Carrier Aggregation (CA) status, the network-side device sends LP-WUS to transmit PDCCH on the Primary Cell (PCell) or Secondary Cell (SCell) #1, but not on SCell #2, then adjusting the bwp-inactivityTimer of PCell or SCell #1 or performing BWP handover only on PCell or SCell #1 is reasonable. However, adjusting the bwp-inactivityTimer of SCell #2 or performing BWP handover only on SCell #2 is unreasonable. Since LP-WUS does not indicate a specific cell, the UE cannot determine which cell to listen to PDCCH on after receiving LP-WUS. Based on this, this embodiment can adjust the bwp-inactivityTimer of the first BWP or perform BWP switching only when the terminal is in a single connection state or the terminal is only configured with SpCell. In this way, the terminal can clearly identify which cell it is listening to PDCCH on, thereby ensuring that it can control the BWP of that cell.

[0254] In some optional embodiments, when the terminal is in CA state or when the terminal has added an Scell, the terminal can still control the BWP based on relevant technology or the traditional (Legacy) BWP control method if the first condition is met; or, the terminal can adjust only the bwp-inactivityTimer of PCell or SCell#1 or switch only the BWP of PCell or SCell#1 if the first condition is met.

[0255] Optionally, the method further includes at least one of the following:

[0256] When the terminal switches from single connection state to CA state, or when the terminal adds a secondary cell (Scell), the terminal deactivates the first operation.

[0257] When the terminal switches from CA state to single connection state, or when the terminal reverts to configuring SpCell only, the terminal activates the first operation.

[0258] The first operation is: when the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0259] In this embodiment, the Scell ​​is added to the terminal. For example, if the terminal sends a signaling message to add the Scell, it is considered that the terminal has added the Scell.

[0260] The aforementioned terminal deactivates the first operation, that is, the terminal does not perform BWP control in the manner described in the first operation. In other words, when the terminal switches from single connection state to CA state, or when the terminal adds a secondary cell Scell, the terminal no longer executes the aforementioned step 401.

[0261] The terminal activates the first operation, that is, the terminal performs BWP control in the manner described in the first operation. In other words, when the terminal switches from CA state to single connection state, or when the terminal reverts to configuring only SpCell, the terminal continues to execute the above step 401.

[0262] In this embodiment, when the terminal switches from a single-connection state to a CA state, or when an Scell ​​is added to the terminal, the terminal deactivates the first operation; when the terminal switches from a CA state to a single-connection state, or when the terminal reverts to configuring only an SpCell, the terminal activates the first operation. This allows the terminal to control the BWP in different states, thereby improving the flexibility of BWP control.

[0263] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0264] If the terminal is in carrier aggregation (CA) state, or if the terminal is configured with SpCell and SCell, then if the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP of the first cell or performs BWP handover of the first cell.

[0265] The first cell includes any one of the following:

[0266] SpCell;

[0267] Cells in the LP-WUS-associated cell group that are transmitting data were detected;

[0268] Cells configured or pre-configured by network-side equipment;

[0269] Cells indicated by LP-WUS detected.

[0270] In this embodiment, when the terminal is in CA state or the terminal is configured with SpCell and SCell, the bwp-inactivityTimer of the first BWP of the first cell can be adjusted only according to LP-WUS, or the BWP handover of the first cell can be performed only according to LP-WUS.

[0271] For the first cell mentioned above, SpCell, for example, for LP-WUS of the Master Cell Group (MCG), only the bwp-inactivityTimer of the PCell needs to be adjusted or a BWP handover can be performed on the PCell; for LP-WUS of the Secondary Cell Group (SCG), only the bwp-inactivityTimer of the PSCell needs to be adjusted or a BWP handover can be performed on the PSCell.

[0272] For the first cell mentioned above, which is a cell in the cell group associated with the detected LP-WUS that has data transmission, for example, if LP-WUS is detected in the MCG, and if the PCell of the MCG has data that needs to be transmitted, then only the bwp-inactivityTimer of the PCell can be adjusted or a BWP handover can be performed on the PCell; if the SCell of the MCG has data that needs to be transmitted, then only the bwp-inactivityTimer of the SCell of the MCG can be adjusted or a BWP handover can be performed on the SCell of the MCG; if LP-WUS is detected in the SCG, and if the PSCell of the SCG has data that needs to be transmitted, then only the bwp-inactivityTimer of the PSCell can be adjusted or a BWP handover can be performed on the PSCell; if the SCell of the SCG has data that needs to be transmitted, then only the bwp-inactivityTimer of the SCell of the SCG can be adjusted or a BWP handover can be performed on the SCell of the SCG. The cell having data transmission can include at least one of the following: a cell that is not deactivated, a cell that is not dormant, or a cell with a different frequency point or frequency band than the LP-WUS.

[0273] Optionally, when the terminal meets the first condition, the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:

[0274] When the terminal is in a dual connectivity (DC) state, if the terminal detects LP-WUS, the first MAC entity of the terminal adjusts the bwp-inactivityTimer of the first BWP of the first cell group or performs BWP handover on the first cell group according to the LP-WUS associated with the first cell group.

[0275] The first cell group is either the primary cell group (MCG) or the secondary cell group (SCG), and the first MAC entity is the MAC entity associated with the first cell group.

[0276] In this embodiment, each MAC entity of the terminal adjusts the bwp-inactivityTimer of the first BWP of its associated cell group or performs BWP handover to its associated cell group based on the LP-WUS associated with its cell group. The LP-WUS associated with the cell group may include the LP-WUS detected during the LP-WUS detection timing corresponding to that cell group, or it may be determined based on third indication information carried by the LP-WUS, which indicates the cell group associated with the LP-WUS.

[0277] The LP-WUS detection timing includes the frequency point and time domain location corresponding to the LP-WUS detection timing. For example, the LP-WUS detection timing of the MCG corresponds to frequency point 1, and the LP-WUS detection timing of the SCG corresponds to frequency point 2. The UE detects LP-WUS at frequency point 1 and frequency point 2 respectively. If LP-WUS is detected at frequency point 1, the MAC entity corresponding to the UE's MCG performs BWP control based on the LP-WUS detected at frequency point 1; if LP-WUS is detected at frequency point 2, the MAC entity corresponding to the UE's SCG performs BWP control based on the LP-WUS detected at frequency point 2. For example, the detection timing of LP-WUS of MCG corresponds to time domain position 1, and the detection timing of LP-WUS of SCG also corresponds to time domain position 1. The UE detects LP-WUS at time domain position 1 and time domain position 2 respectively. If LP-WUS is detected at time domain position 1, the MAC entity corresponding to the UE's MCG performs BWP control based on the LP-WUS detected at time domain position 1; if LP-WUS is detected at time domain position 2, the MAC entity corresponding to the UE's SCG performs BWP control based on the LP-WUS detected at time domain position 2.

[0278] The aforementioned third indication information can be used to indicate whether the LP-WUS corresponds to the LP-WUS of the MCG or the LP-WUS of the SCG; alternatively, the aforementioned third indication information can be an LP-WUS sequence or bit information carried in the LP-WUS, that is, the LP-WUS sequence indicates the cell group associated with the LP-WUS, for example, LP-WUS sequence 1 is associated with the MCG, and LP-WUS sequence 2 is associated with the SCG. For example, if the indication information carried by the LP-WUS detected by the UE indicates the MCG, then the MAC entity corresponding to the UE's MCG performs BWP control based on the LP-WUS; if the indication information carried by the LP-WUS detected by the UE indicates the SCG, then the MAC entity corresponding to the UE's SCG performs BWP control based on the LP-WUS.

[0279] In this embodiment, each MAC entity of the terminal adjusts the bwp-inactivityTimer of the first BWP of its related cell group or performs BWP handover to its related cell group according to the LP-WUS associated with its related cell group. This ensures that the LP-WUS of different cell groups of the terminal do not interfere with each other, so that the network side can control the MCG and SCG to control the BWP through LP-WUS respectively, which can improve the flexibility of control.

[0280] It should be noted that the various implementation methods described above in this application can be reasonably combined according to actual needs, and this embodiment does not limit this.

[0281] Please refer to Figure 6, which is a flowchart of a BWP control method provided in an embodiment of this application. This method can be executed by a network-side device, and as shown in Figure 6, it includes the following steps:

[0282] Step 601: The network-side device performs a second operation, which includes at least one of the following:

[0283] Send a low-power wake-up signal LP-WUS to the terminal, wherein the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes BWP related information;

[0284] The terminal receives first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS.

[0285] Send a second instruction message to the terminal;

[0286] The first indication information is used to indicate any of the following:

[0287] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0288] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0289] There is data scheduling for the terminal;

[0290] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs;

[0291] The second indication information is used to indicate at least one of the following:

[0292] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0293] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0294] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0295] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0296] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0297] The first BWP is an active BWP.

[0298] Optionally, the BWP-related information BWP index is used to instruct the terminal to listen to the PDCCH on the BWP indicated by the BWP index when it receives the LP-WUS.

[0299] Optionally, the method further includes:

[0300] The network-side device determines, based on the first information, whether to send the second instruction information or an updated second instruction information to the terminal.

[0301] It should be noted that the implementation method of this method can be found in the relevant description of the embodiment shown in Figure 4, and will not be repeated here.

[0302] It should be noted that the BWP control method provided in this application embodiment can be executed by a BWP control device. This application embodiment uses the execution of the BWP control method by a BWP control device as an example to illustrate the BWP control device provided in this application embodiment.

[0303] This application provides a BWP control device. As an example, the BWP control device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0304] The BWP control device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0305] Specifically, referring to Figure 7, when the BWP control device is a terminal or a component in the terminal, the BWP control device 700 includes a processing module 701, which is used to adjust the BWP inactivity timer bwp-inactivityTimer of the first bandwidth portion of the BWP or to perform BWP switching when the terminal meets the first condition.

[0306] Wherein, the first BWP is a BWP that is in an active state, and the first condition includes at least one of the following:

[0307] A low-power wake-up signal LP-WUS is detected, and the LP-WUS is used to trigger the terminal to listen to the physical downlink control channel PDCCH.

[0308] Uplink transmission is required during LP-WUS listening.

[0309] Optionally, the processing module is specifically used for:

[0310] If the terminal is listening to LP-WUS during the non-continuous DRX inactivity time, and the terminal meets the first condition, then the bwp-inactivityTimer of the first BWP is adjusted or a BWP switch is performed.

[0311] Optionally, the processing module is specifically used for:

[0312] Enable, restart, or stop the first BWP's bwp-inactivityTimer.

[0313] Optionally, the first condition includes the terminal detecting the LP-WUS;

[0314] The processing module is specifically used for:

[0315] If the detected LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, adjust the bwp-inactivityTimer of the first BWP or switch the BWP.

[0316] The first indication information is used to indicate any of the following:

[0317] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0318] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0319] There is data scheduling for the terminal;

[0320] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs.

[0321] Optionally, the processing module is specifically used for:

[0322] If the terminal meets the second condition, then if the terminal meets the first condition, adjust the bwp-inactivityTimer of the first BWP or switch BWPs.

[0323] The second condition includes at least one of the following:

[0324] The terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold;

[0325] The terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold;

[0326] The terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold;

[0327] The terminal requires the data transmission volume to be higher than or equal to the fourth threshold.

[0328] The terminal requires a data throughput rate higher than or equal to the fifth threshold.

[0329] The terminal requires data transmission latency to be higher than or equal to the sixth threshold.

[0330] The terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.

[0331] Optionally, the processing module is specifically used for:

[0332] If the terminal receives the second indication information from the network-side device, then if the terminal meets the first condition, the bwp-inactivityTimer of the first BWP is adjusted or a BWP is switched.

[0333] The second indication information is used to indicate at least one of the following:

[0334] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0335] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0336] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0337] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0338] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0339] Optionally, the device further includes:

[0340] The sending module is used to report first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS, or the capability information is used to indicate whether the terminal supports or does not support BWP switching according to LP-WUS.

[0341] Optionally, the processing module is further configured to:

[0342] When the terminal receives updated second instruction information from the network-side device, the bwp-inactivityTimer of the first BWP is adjusted.

[0343] Optionally, the processing module is specifically used for:

[0344] If the terminal detects LP-WUS and the LP-WUS includes BWP-related information, the bwp-inactivityTimer of the first BWP is adjusted or a BWP is switched according to the BWP-related information.

[0345] Optionally, the BWP-related information includes a BWP index, which is used to instruct the terminal to listen to the PDCCH on the BWP indicated by the BWP index when it receives the LP-WUS.

[0346] Optionally, the processing module is specifically used for at least one of the following:

[0347] If the second BWP is the same as the first BWP, adjust the bwp-inactivityTimer of the first BWP;

[0348] If the second BWP is different from the first BWP, perform BWP switching;

[0349] The second BWP is a BWP determined based on the BWP-related information.

[0350] Optionally, the processing module is specifically used for at least one of the following:

[0351] If the second BWP is different from the first BWP, and if the second BWP is not the default BWP or the initial BWP, then the first BWP is deactivated, the second BWP is activated, and the bwp-inactivityTimer of the second BWP is started when the second BWP is activated.

[0352] If the second BWP is different from the first BWP, and the second BWP is the default BWP or the initial BWP, then the first BWP is deactivated and the second BWP is activated.

[0353] Optionally, the processing module is specifically used for:

[0354] If the terminal is in a single-connection state, or if the terminal is only configured with a special cell SpCell, then if the terminal meets the first condition, the bwp-inactivityTimer of the first BWP is adjusted or a BWP handover is performed.

[0355] Optionally, the processing module is further configured to perform at least one of the following:

[0356] The first operation is deactivated when the terminal switches from single connection state to CA state or when the terminal adds a secondary cell (Scell).

[0357] The first operation is activated when the terminal switches from CA state to single connection state, or when the terminal reverts to SpCell configuration only.

[0358] The first operation is: when the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0359] Optionally, the processing module is specifically used for:

[0360] If the terminal is in carrier aggregation (CA) state, or the terminal is configured with SpCell and SCell, then if the terminal meets the first condition, the bwp-inactivityTimer of the first BWP of the first cell is adjusted or the first cell is switched over.

[0361] The first cell includes any one of the following:

[0362] SpCell;

[0363] Cells in the LP-WUS-associated cell group that are transmitting data were detected;

[0364] Cells configured or pre-configured by network-side equipment;

[0365] Cells indicated by LP-WUS detected.

[0366] Optionally, the processing module is specifically used for:

[0367] When the terminal is in dual-connection DC state, if the terminal detects LP-WUS, the first MAC entity adjusts the bwp-inactivityTimer of the first BWP of the first cell group or performs BWP handover on the first cell group according to the LP-WUS associated with the first cell group.

[0368] The first cell group is either the primary cell group (MCG) or the secondary cell group (SCG), and the first MAC entity is the MAC entity associated with the first cell group.

[0369] The BWP control device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG4 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0370] Referring to Figure 8, when the BWP control device is a network-side device or a component within a network-side device, the BWP control device 800 includes a processing module 801 for performing a second operation, the second operation including at least one of the following:

[0371] Send a low-power wake-up signal LP-WUS to the terminal, wherein the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes BWP related information;

[0372] The terminal receives first information, which includes at least one of the following: the type of the terminal, the terminal's data transmission volume requirements, the terminal's data throughput requirements, the terminal's data transmission latency requirements, and the terminal's capability information; the capability information is used to indicate whether the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS.

[0373] Send a second instruction message to the terminal;

[0374] The first indication information is used to indicate any of the following:

[0375] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information;

[0376] The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration;

[0377] There is data scheduling for the terminal;

[0378] Adjust the bwp-inactivityTimer of the first BWP or switch BWPs;

[0379] The second indication information is used to indicate at least one of the following:

[0380] The terminal is allowed to adjust the bwp-inactivityTimer according to LP-WUS or to perform BWP switching according to LP-WUS;

[0381] The serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency;

[0382] When the terminal detects that LP-WUS has triggered the terminal to listen to the PDCCH, it adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.

[0383] The serving cell of the terminal supports the terminal in adjusting the bwp-inactivityTimer according to LP-WUS or supports the terminal in performing BWP handover according to LP-WUS.

[0384] The serving cell of the terminal supports adjusting the bwp-inactivityTimer of the first BWP or performing a BWP handover when the terminal detects an LP-WUS that triggers the terminal to listen to the PDCCH.

[0385] The first BWP is an active BWP.

[0386] Optionally, the BWP-related information BWP index is used to instruct the terminal to listen to the PDCCH on the BWP indicated by the BWP index when it receives the LP-WUS.

[0387] Optionally, the processing module is further configured to:

[0388] Based on the first information, determine whether to send the second instruction information or an updated second instruction information to the terminal.

[0389] The BWP control device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0390] As shown in Figure 9, this application embodiment also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores programs or instructions that can run on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various steps of the above-described BWP control method embodiment and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various steps of the above-described BWP control method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0391] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG4. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the BWP control device shown in FIG7. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0392] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0393] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 10 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0394] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0395] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0396] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0397] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 1010.

[0398] The processor 1010 is configured to adjust the BWP inactivity timer (bwp-inactivityTimer) of the first bandwidth portion BWP or perform BWP switching when the terminal meets a first condition; wherein the first BWP is an active BWP, and the first condition includes at least one of the following: detecting a low-power wake-up signal LP-WUS, wherein the LP-WUS is used to trigger the terminal to listen to the physical downlink control channel (PDCCH); and uplink transmission is required during the LP-WUS listening period.

[0399] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the aforementioned BWP control method embodiment on the terminal side, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0400] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG6. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0401] Specifically, this application embodiment also provides a network-side device, which may be the BWP control device shown in FIG8. As shown in FIG11, the network-side device 1100 includes: an antenna 1101, a radio frequency device 1102, a baseband device 1103, a processor 1104, and a memory 1105. The antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the radio frequency device 1102 receives information through the antenna 1101 and sends the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be transmitted and sends it to the radio frequency device 1102. The radio frequency device 1102 processes the received information and transmits it through the antenna 1101.

[0402] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1103, which includes a baseband processor.

[0403] The baseband device 1103 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG11. One of the chips is, for example, a baseband processor, which is connected to the memory 1105 via a bus interface to call the program in the memory 1105 and execute the network device operation shown in the above method embodiment.

[0404] The network-side device may also include a network interface 1106, such as a Common Public Radio Interface (CPRI).

[0405] Specifically, the network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 1105 and executable on processor 1104. Processor 1104 calls the instructions or programs in memory 1105 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0406] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described BWP control method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0407] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0408] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described BWP control method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0409] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0410] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described BWP control method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0411] This application also provides a wireless communication system, including a terminal and a network-side device. The terminal can be used to execute the steps of the BWP control method described above, and the network-side device can be used to execute the steps of the BWP control method described above.

[0412] It should be noted that, in this document, 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 limitations, 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 that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0413] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0414] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A BWP control method, comprising: adjusting, by a terminal, a BWP inactivity timer bwp-inactivityTimer of a first bandwidth part (BWP) or performing a BWP switching, in a case that the terminal meets a first condition; wherein the first BWP is an active BWP, and the first condition comprises at least one of: detecting a low power wake-up signal (LP-WUS) for triggering the terminal to monitor a physical downlink control channel (PDCCH) ; needing to perform an uplink transmission during an LP-WUS monitoring period.

2. The method of claim 1, wherein, The adjusting, by the terminal, the bwp-inactivityTimer of the first BWP or performing the BWP switching in the case that the terminal meets the first condition comprises: in a case that the terminal monitors an LP-WUS during a discontinuous reception (DRX) inactivity time, if the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs the BWP switching.

3. The method of claim 1 or 2, wherein, The adjusting, by the terminal, the bwp-inactivityTimer of the first BWP comprises: the terminal starts or restarts or stops the bwp-inactivityTimer of the first BWP.

4. The method of any one of claims 1 to 3, wherein, The first condition comprises that the terminal detects the LP-WUS. The adjusting, by the terminal, the bwp-inactivityTimer of the first BWP or performing the BWP switching comprises: in a case that the detected LP-WUS comprises first indication information or a type of the LP-WUS is an LP-WUS type related to the first indication information, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs the BWP switching. The first indication information is used to indicate any one of: the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink grant information; the LP-WUS is used to trigger the terminal to receive a PDCCH containing multicast configuration related downlink allocation information; there is data scheduling for the terminal; adjusting the bwp-inactivityTimer of the first BWP or performing the BWP switching.

5. The method of any one of claims 1 to 4, wherein, The adjusting, by the terminal, the bwp-inactivityTimer of the first BWP or performing the BWP switching in the case that the terminal meets the first condition comprises: if the terminal meets a second condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs the BWP switching in the case that the terminal meets the first condition; The second condition comprises at least one of: the terminal is a terminal type with a data transmission amount greater than or equal to a first threshold value; the terminal is a terminal type with a data throughput rate greater than or equal to a second threshold value; the terminal is a terminal type with a data transmission delay less than or equal to a third threshold value; the terminal has a data transmission amount requirement higher than or equal to a fourth threshold value; the terminal has a data throughput rate requirement higher than or equal to a fifth threshold value; The terminal has a data transmission time delay requirement higher than or equal to a sixth threshold value; The terminal supports adjusting the bwp-inactivityTimer according to the LP-WUS or supports BWP switching according to the LP-WUS.

6. The method of any one of claims 1 to 5, wherein, The terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case where the terminal meets a first condition, including: If the terminal receives second indication information from the network side device, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case where the terminal meets a first condition; The second indication information is used to indicate at least one of the following: Allow the terminal to adjust the bwp-inactivityTimer according to the LP-WUS or allow the terminal to perform BWP switching according to the LP-WUS; The serving cell of the terminal supports guaranteeing at least one of the data transmission throughput and the data transmission time delay of the terminal; The terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case where the terminal detects LP-WUS triggering the terminal to monitor PDCCH; The serving cell of the terminal supports the terminal adjusting the bwp-inactivityTimer according to the LP-WUS or supports the terminal performing BWP switching according to the LP-WUS; The serving cell of the terminal supports the terminal adjusting the bwp-inactivityTimer of the first BWP or performing BWP switching in a case where the terminal detects LP-WUS triggering the terminal to monitor PDCCH.

7. The method of any one of claims 1 to 6, wherein, The method further comprises: The terminal reports first information, and the first information includes at least one of the following: the type of the terminal, the data transmission amount requirement of the terminal, the data throughput requirement of the terminal, the data transmission time delay requirement of the terminal, and the capability information of the terminal; the capability information is used to indicate whether the terminal supports or does not support adjusting the bwp-inactivityTimer according to the LP-WUS, or the capability information is used to indicate whether the terminal supports or does not support BWP switching according to the LP-WUS.

8. The method of claim 6 or 7, wherein, Before the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case where the terminal meets a first condition, the method further comprises: In a case where the terminal receives updated second indication information from the network side device, the terminal adjusts the bwp-inactivityTimer of the first BWP.

9. The method of any one of claims 1 to 8, wherein, The terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case where the terminal meets a first condition, including: In a case that the terminal detects the LP-WUS and the LP-WUS comprises BWP-related information, the terminal adjusts a bwp-inactivityTimer of the first BWP or performs BWP switching according to the BWP-related information.

10. The method of claim 9, wherein, The BWP-related information comprises a BWP index, and the BWP index is used to instruct the terminal to monitor a PDCCH on a BWP indicated by the BWP index in a case that the terminal receives the LP-WUS.

11. The method of claim 9 or 10, wherein, The adjusting the bwp-inactivityTimer of the first BWP or the performing BWP switching according to the BWP-related information comprises at least one of the following: In a case that the second BWP is the same as the first BWP, the terminal adjusts the bwp-inactivityTimer of the first BWP; In a case that the second BWP is different from the first BWP, the terminal performs BWP switching; The second BWP is a BWP determined according to the BWP-related information.

12. The method of claim 11, wherein, The performing BWP switching in a case that the second BWP is different from the first BWP comprises at least one of the following: In a case that the second BWP is different from the first BWP, if the second BWP is not a default BWP or an initial BWP, the terminal deactivates the first BWP, activates the second BWP, and starts a bwp-inactivityTimer of the second BWP in a case that the second BWP is activated; In a case that the second BWP is different from the first BWP, if the second BWP is a default BWP or an initial BWP, the terminal deactivates the first BWP and activates the second BWP.

13. The method of any one of claims 1 to 12, wherein, The adjusting the bwp-inactivityTimer of the first BWP or the performing BWP switching in a case that the terminal satisfies the first condition comprises: In a case that the terminal satisfies the first condition, if the terminal is in a single connection state or the terminal is only configured with a special cell (SpCell), the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching.

14. The method of claim 13, wherein, The method further comprises at least one of the following: In a case that the terminal switches from the single connection state to a CA state or the terminal adds a secondary cell (Scell), the terminal deactivates a first operation; In a case that the terminal switches from the CA state to the single connection state or the terminal is restored to be only configured with the SpCell, the terminal activates the first operation; The first operation is that the terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching in a case that the terminal satisfies the first condition.

15. The method of any one of claims 1 to 12, wherein, The adjusting the bwp-inactivityTimer of the first BWP or the performing BWP switching in a case that the terminal satisfies the first condition comprises: If the terminal is in a carrier aggregation (CA) state or the terminal is configured with an SpCell and an SCell, the terminal adjusts a bwp-inactivityTimer of a first BWP of a first cell or performs a BWP switch of the first cell if the terminal meets a first condition; The first cell includes any of the following: An SpCell; A cell in which there is data transmission in a detected cell group associated with an LP-WUS; A cell configured or preconfigured by a network side device; A cell indicated by a detected LP-WUS.

16. The method of any one of claims 1 to 15, wherein, The terminal adjusts the bwp-inactivityTimer of the first BWP or performs the BWP switch if the terminal meets the first condition, including: If the terminal detects an LP-WUS when the terminal is in a dual connectivity (DC) state, a first MAC entity of the terminal adjusts a bwp-inactivityTimer of a first BWP of a first cell group or performs a BWP switch of the first cell group according to an LP-WUS associated with the first cell group; The first cell group is a master cell group (MCG) or a secondary cell group (SCG), and the first MAC entity is a MAC entity associated with the first cell group.

17. A BWP control method, comprising: A network side device performs a second operation, including at least one of the following: Sends a low power wake-up signal (LP-WUS) to a terminal, the LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information, and / or the LP-WUS includes BWP related information; Receives first information from the terminal, the first information includes at least one of the following: the type of the terminal, the data transmission amount requirement of the terminal, the data throughput rate requirement of the terminal, the data transmission delay requirement of the terminal, and the capability information of the terminal; the capability information is used to indicate whether the terminal supports or does not support adjusting the bwp-inactivityTimer according to the LP-WUS; Sends second indication information to the terminal; The first indication information is used to indicate any of the following: The LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink grant information; The LP-WUS is used to trigger the terminal to receive a PDCCH containing multicast configuration related downlink allocation information; There is data scheduling for the terminal; Adjusts the bwp-inactivityTimer of the first BWP or performs the BWP switch; The second indication information is used to indicate at least one of the following: The terminal is allowed to adjust the bwp-inactivityTimer according to the LP-WUS or the terminal is allowed to perform the BWP switch according to the LP-WUS; The serving cell of the terminal supports guaranteeing at least one of the data transmission throughput rate and the data transmission delay of the terminal; The terminal adjusts a bwp-inactivityTimer of a first BWP or performs BWP switching in a case where the terminal detects an LP-WUS triggering the terminal to monitor a PDCCH. A serving cell of the terminal supports the terminal to adjust a bwp-inactivityTimer according to an LP-WUS or supports the terminal to perform BWP switching according to an LP-WUS. A serving cell of the terminal supports the terminal to adjust a bwp-inactivityTimer of a first BWP or perform BWP switching in a case where the terminal detects an LP-WUS triggering the terminal to monitor a PDCCH. The first BWP is a BWP in an active state.

18. The method of claim 17, wherein, The BWP-related information includes a BWP index, and the BWP index is used to instruct the terminal to monitor a PDCCH on a BWP indicated by the BWP index in a case where the terminal receives the LP-WUS.

19. The method of claim 17 or 18, wherein, The method further includes: The network-side device determines whether to send the second indication information or updated second indication information to the terminal according to the first information.

20. A BWP control apparatus, comprising: a processing module configured to adjust a BWP inactivity timer bwp-inactivityTimer of a first bandwidth part BWP or perform BWP switching in a case where a terminal meets a first condition; The first BWP is a BWP in an active state, and the first condition includes at least one of the following: detecting a low-power wake-up signal LP-WUS, the LP-WUS being used to trigger the terminal to monitor a physical downlink control channel PDCCH; uplink transmission is needed during LP-WUS monitoring.

21. The apparatus of claim 20, wherein, The first condition includes that the terminal detects the LP-WUS. The processing module is specifically configured to: adjust the bwp-inactivityTimer of the first BWP or perform BWP switching in a case where the detected LP-WUS includes first indication information or the type of the LP-WUS is an LP-WUS type related to the first indication information. The first indication information is used to indicate any of the following: the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink grant information; the LP-WUS is used to trigger the terminal to receive a PDCCH containing multicast configuration-related downlink allocation information; there is data scheduling for the terminal; adjust the bwp-inactivityTimer of the first BWP or perform BWP switching.

22. The apparatus of claim 20 or 21, wherein, The processing module is specifically configured to: if the terminal meets a second condition, then adjust the bwp-inactivityTimer of the first BWP or perform BWP switching in a case where the terminal meets the first condition; The second condition includes at least one of the following: the terminal is a terminal type with a data transmission amount greater than or equal to a first threshold value; the terminal is a terminal type with a data throughput rate greater than or equal to a second threshold value; The terminal is a terminal type with a data transmission delay less than or equal to a third threshold value; The terminal has a data transmission amount requirement higher than or equal to a fourth threshold value; The terminal has a data throughput rate requirement higher than or equal to a fifth threshold value; The terminal has a data transmission delay requirement higher than or equal to a sixth threshold value; The terminal supports adjusting the bwp-inactivityTimer according to the LP-WUS or supports BWP switching according to the LP-WUS.

23. The apparatus of any one of claims 20-22, wherein, The processing module is specifically configured to: If the second indication information is received from the network side device, the bwp-inactivityTimer of the first BWP is adjusted if the terminal meets the first condition; The second indication information is used to indicate at least one of the following: The terminal is allowed to adjust the bwp-inactivityTimer according to the LP-WUS or is allowed to perform BWP switching according to the LP-WUS; The serving cell of the terminal supports at least one of the data transmission throughput rate and the data transmission delay of the terminal; The terminal adjusts the bwp-inactivityTimer of the first BWP or performs BWP switching when detecting the LP-WUS triggering the terminal to listen to the PDCCH; The serving cell of the terminal supports the terminal adjusting the bwp-inactivityTimer according to the LP-WUS or supports the terminal performing BWP switching according to the LP-WUS; The serving cell of the terminal supports the terminal adjusting the bwp-inactivityTimer or performing BWP switching when the terminal detects the LP-WUS triggering the terminal to listen to the PDCCH.

24. The apparatus of any one of claims 20-23, wherein, The apparatus further comprises: The sending module is configured to report first information, the first information comprising at least one of the following: the type of the terminal, the data transmission amount requirement of the terminal, the data throughput rate requirement of the terminal, the data transmission delay requirement of the terminal, and the capability information of the terminal; the capability information is used to indicate whether the terminal supports or does not support adjusting the bwp-inactivityTimer according to the LP-WUS, or the capability information is used to indicate whether the terminal supports or does not support performing BWP switching according to the LP-WUS.

25. The apparatus of any one of claims 20-24, wherein, The processing module is specifically configured to: In a case where the terminal detects the LP-WUS and the LP-WUS comprises BWP related information, the bwp-inactivityTimer of the first BWP is adjusted or BWP switching is performed according to the BWP related information.

26. A BWP control apparatus, comprising: A processing module configured to perform a second operation, the second operation comprising at least one of the following: sending a low-power wake-up signal (LP-WUS) to a terminal, the LP-WUS comprising first indication information or the type of the LP-WUS being an LP-WUS type related to the first indication information, and / or the LP-WUS comprising bandwidth part (BWP) related information; receiving first information from a terminal, the first information comprising at least one of: a type of the terminal, a data transmission amount requirement of the terminal, a data throughput rate requirement of the terminal, a data transmission delay requirement of the terminal, capability information of the terminal; the capability information indicating that the terminal supports or does not support adjusting bwp-inactivityTimer according to LP-WUS; sending second indication information to the terminal; wherein the first indication information indicates any one of: the LP-WUS is used to trigger the terminal to receive PDCCH containing downlink allocation or uplink grant information; the LP-WUS is used to trigger the terminal to receive PDCCH containing multicast configuration related downlink allocation information; there is data scheduling to the terminal; adjusting bwp-inactivityTimer of a first BWP or performing BWP switching; wherein the second indication information indicates at least one of: the terminal is allowed to adjust bwp-inactivityTimer according to LP-WUS or the terminal is allowed to perform BWP switching according to LP-WUS; a serving cell of the terminal supports guaranteeing at least one of data transmission throughput rate and data transmission delay of the terminal; the terminal adjusts bwp-inactivityTimer of a first BWP or performs BWP switching in a case where the terminal detects LP-WUS triggering the terminal to monitor PDCCH; a serving cell of the terminal supports the terminal adjusting bwp-inactivityTimer according to LP-WUS or the terminal performing BWP switching according to LP-WUS; a serving cell of the terminal supports the terminal adjusting bwp-inactivityTimer or performing BWP switching in a case where the terminal detects LP-WUS triggering the terminal to monitor PDCCH; wherein the first BWP is a BWP in an active state. 27.A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement steps of the BWP control method according to any one of claims 1 to 16. 28.A network side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement steps of the BWP control method according to any one of claims 17 to 19. 29.A readable storage medium, the readable storage medium storing programs or instructions, the programs or instructions being executed by a processor to implement steps of the BWP control method according to any one of claims 1 to 16, or to implement steps of the BWP control method according to any one of claims 17 to 19.

30. A computer program product, which is executed by at least one processor to implement the steps of the BWP control method according to any one of claims 1 to 16, or to implement the steps of the BWP control method according to any one of claims 17 to 19.

Images