WO2026026913A1 - Bwp控制方法、装置、终端及网络侧设备 - Google Patents

Bwp控制方法、装置、终端及网络侧设备

Info

Publication number
WO2026026913A1
WO2026026913A1 PCT/CN2025/111810 CN2025111810W WO2026026913A1 WO 2026026913 A1 WO2026026913 A1 WO 2026026913A1 CN 2025111810 W CN2025111810 W CN 2025111810W WO 2026026913 A1 WO2026026913 A1 WO 2026026913A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
terminal
wus
inactivitytimer
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/111810
Other languages
English (en)
French (fr)
Inventor
王洋洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2026026913A1 publication Critical patent/WO2026026913A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application belongs to the field of communication technology, specifically relating to a BWP control method, device, terminal, and network-side equipment.
  • 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.
  • the terminal activates the low-power receiver module to listen for the Low Power Wake Up Signal (LP-WUS), while the terminal's main communication module (or main receiver module) remains off or in sleep mode.
  • LP-WUS Low Power Wake Up Signal
  • main communication module main receiver module
  • main receiver module main receiver module
  • the network-side device sends LP-WUS to the terminal. After the terminal detects LP-WUS through the low-power receiver module, it can activate or wake up the main communication module to receive downlink data.
  • uplink data needs to be transmitted while the terminal is listening for LP-WUS through the low-power receiver module, it can also activate or wake up the main communication module to send uplink data.
  • BWP bandwidth part
  • 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.
  • a BWP control method comprising:
  • the terminal adjusts the BWP inactivity timer (bwp-inactivityTimer) of the first bandwidth portion BWP or performs BWP switching;
  • the first BWP is a BWP that is in an active state
  • the first condition includes at least one of the following:
  • 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).
  • PDCH Physical Downlink Control Channel
  • Uplink transmission is required during LP-WUS listening.
  • a BWP control device comprising:
  • 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.
  • the first BWP is a BWP that is in an active state
  • the first condition includes at least one of the following:
  • 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.
  • Uplink transmission is required during LP-WUS listening.
  • a BWP control method which includes:
  • the network-side device performs a second operation, which includes at least one of the following:
  • 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;
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the first BWP is an active BWP.
  • a BWP control device comprising:
  • a processing module is configured to perform a second operation, the second operation including at least one of the following:
  • 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;
  • BWP bandwidth portion
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the first BWP is an active BWP.
  • 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.
  • a 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.
  • a terminal 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.
  • the first BWP is a BWP that is in an active state
  • the first condition includes at least one of the following:
  • 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.
  • Uplink transmission is required during LP-WUS listening.
  • a 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.
  • 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:
  • 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;
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the first BWP is an active BWP.
  • a readable storage medium 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.
  • a wireless communication system 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.
  • a 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.
  • 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.
  • the terminal 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.
  • Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application
  • Figure 2 is a schematic diagram of the LP WUR operation provided by related technologies
  • Figure 3 is a schematic diagram of the on/off key control signal provided by the related technology
  • FIG. 4 is a flowchart of a BWP control method provided in an embodiment of this application.
  • 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.
  • Figure 5b is a schematic diagram of the expiration of bwp-InactivityTimer during the time period from when the terminal wakes up the main communication module to when it receives the pre-configured uplink grant or the uplink grant dynamically scheduled by PDCCH, according to an embodiment of this application.
  • FIG. 6 is a flowchart of another BWP control method provided in an embodiment of this application.
  • FIG. 7 is a structural diagram of a BWP control device provided in an embodiment of this application.
  • FIG. 8 is a structural diagram of another BWP control device provided in an embodiment of this application.
  • Figure 9 is a structural diagram of the communication device provided in an embodiment of this application.
  • Figure 10 is a structural diagram of the terminal provided in an embodiment of this application.
  • Figure 11 is a structural diagram of the network-side device provided in an embodiment of this application.
  • first and second 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.
  • “or” in this application indicates at least one of the connected objects.
  • 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.
  • 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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • NR New Radio
  • FIG. 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.
  • 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.
  • PDA personal digital assistant
  • UMPC ultra-mobile personal computer
  • MID mobile internet device
  • AR augmented reality
  • VR virtual reality
  • 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
  • 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.
  • 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.
  • WLAN Wireless Local Area Network
  • WiFi Wireless Fidelity
  • a base station may be referred to as a 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 base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for introduction, and the specific type of base station is not limited.
  • 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), and Unified Data Warehouse (UDM).
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • EASDF Edge Application Server Discovery Function
  • UDM Unified Data Management
  • UDM Unified Data Management
  • UDM Unified Data Warehouse
  • the core network equipment includes: Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF).
  • UDR Data Repository
  • HSS Home Subscriber Server
  • CNC Centralized Network Configuration
  • NEF Network Exposure Function
  • L-NEF Local NEF
  • BSF Binding Support Function
  • AF Application Function
  • LMF Location Management Function
  • GMLC Gateway Mobile Location Centre
  • NWDAF Network Data Analytics Function
  • 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).
  • a platform e.g., a cloud platform
  • 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 includes 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.
  • 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.
  • 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 turns off from its active 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the LP-WUS in the connection state is used to trigger PDCCH listening, specifically including:
  • Radio Access Network Work Group 1 For RRC connection mode, from the perspective of Radio Access Network Work Group 1 (RAN1), the following LP-WUS procedure to trigger PDCCH monitoring is further investigated:
  • Case 1 PDCCH listening is triggered by LP-WUS with a connected discontinuous reception (C-DRX) configuration.
  • 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.
  • 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.
  • 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.
  • Option 1-2-2 When listening to LP-WUS, the traditional C-DRX cycle and DRX-OnDurationTimer will not trigger PDCCH listening.
  • 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.
  • RAN1 does not discuss C-DRX-related timers other than DRX-OnDurationTimer, which depends on RAN Work Group 2 (RAN2).
  • a currently connected User Equipment i.e., terminal
  • BWPs Block Devices
  • 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 control 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).
  • MAC Media Access Control
  • one bwp-InactivityTimer is configured for each serving cell, and one active BWP is associated with one bwp-InactivityTimer.
  • 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:
  • the BWP received a PDCCH indicating downlink allocation or uplink grant scrambled with Cell Radio Network Temporary Identity (C-RNTI) / Configured Scheduling Radio Network Temporary Identity (CS-RNTI);
  • C-RNTI Cell Radio Network Temporary Identity
  • CS-RNTI Configured Scheduling Radio Network Temporary Identity
  • G-RNTI Group Radio Network Temporary Identity
  • G-CS-RNTI Group Configured Scheduling Radio Network Temporary Identity
  • a PDCCH indicating downlink allocation or uplink authorization was received for the activated BWP with C-RNTI/CS-RNTI scrambling.
  • Protocol Data Unit was transmitted on the configured grant and no LBT failure indication was received from the underlying layer;
  • a unicast-related MAC PDU or a multicast and broadcast service (MBS)-related MAC PDU was received on the downlink allocation.
  • the initial BWP is the BWP configured for the initial downlink BWP.
  • the initial BWP is either the initial downlink BWP-RedCap configuration (if configured) or the initial downlink BWP (if the initial downlink BWP-RedCap is not configured).
  • the UE When the bwp-InactivityTimer associated with the active BWP expires, if a default BWP is configured, the UE performs a BWP handover and switches to the default BWP; otherwise, the UE switches to the initial BWP.
  • the UE 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.
  • a UE 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.
  • RACH Random Access Channel
  • the UE 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.
  • FIG 4 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:
  • Step 401 If the terminal meets the first condition, the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.
  • the first BWP is a BWP that is in an active state
  • the first condition includes at least one of the following:
  • LP-WUS is detected, and the LP-WUS is used to trigger the terminal to listen to the PDCCH.
  • Uplink transmission is required during LP-WUS listening.
  • 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.
  • 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.
  • 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.
  • the aforementioned LP-WUS is used to trigger the terminal to listen to the PDCCH.
  • 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.
  • 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.
  • the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or switch the BWP based on the first BWP. For instance, if the first BWP is not the default BWP or initial BWP, the bwp-inactivityTimer of the first BWP can be adjusted; if the first BWP is the default BWP or initial BWP, a BWP switching can be performed; or, the terminal can decide to adjust the bwp-inactivityTimer of the first BWP based on the detected LP-WUS. Alternatively, a BWP handover can be performed.
  • the BWP control information carried by the LP-WUS can be used to determine whether to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover.
  • the adjustment of the bwp-inactivityTimer of the first BWP or a BWP handover can be determined based on the protocol agreement.
  • the terminal adjusts the bwp-inactivityTimer of the first BWP when the first condition is met; if the protocol stipulates that a BWP handover is performed when the terminal meets a first condition, then the terminal performs a BWP handover when the first condition is met.
  • 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:
  • Scenario 1 When the BWP (i.e., the first BWP) working on the terminal 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 current working BWP may expire, as shown in Figure 5a. At this time, the BWP working on the terminal will switch to the default BWP or the initial BWP. However, if LP-WUS triggers PDCCH listening for downlink scheduling, it means that there may be a large amount of data transmission to be performed later.
  • the BWP i.e., the first BWP
  • this embodiment can adjust the bwp-InactivityTimer of the currently working BWP (i.e., the first BWP) when LP-WUS is detected.
  • the bwp-inactivityTimer of the first BWP can be enabled, restarted, or stopped. This helps to reduce the occurrence of the bwp-InactivityTimer of the currently working BWP expiring before the terminal listens to the PDCCH, thereby helping to ensure the throughput of downlink transmission.
  • 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.
  • the first BWP 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.
  • 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.
  • this embodiment can adjust the bwp-InactivityTimer of the terminal's currently working BWP (i.e., the first BWP) when uplink transmission is needed during LP-WUS listening.
  • 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.
  • Scenario 4 If the BWP used by the terminal is the default BWP or 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.
  • the bwp-InactivityTimer of the terminal's working BWP (i.e., the first BWP) can be adjusted.
  • 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.
  • a BWP switch can be performed. For example, it can be switched to a pre-configured BWP to improve the throughput of data transmission.
  • the terminal 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.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • 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.
  • DRX Discontinuous Reception
  • the UE i.e., the aforementioned terminal
  • 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.
  • 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.
  • the terminal adjusts the bwp-inactivityTimer of the first BWP, including:
  • the terminal enables, restarts, or stops the bwp-inactivityTimer of the first BWP.
  • the bwp-inactivityTimer of the first BWP 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.
  • the first condition includes the terminal detecting the LP-WUS;
  • the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch, including:
  • the terminal adjusts the bwp-inactivityTimer of the first BWP or performs a BWP switch.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation or uplink authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • the terminal 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.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • the terminal 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.
  • the second condition includes at least one of the following:
  • the terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold
  • the terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold
  • the terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold
  • the terminal requires the data transmission volume to be higher than or equal to the fourth threshold.
  • the terminal requires a data throughput rate higher than or equal to the fifth threshold.
  • the terminal requires data transmission latency to be higher than or equal to the sixth threshold.
  • the terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.
  • 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.
  • the bwp-inactivityTimer of the first BWP may be adjusted or a BWP may be switched if the first condition is met:
  • the UE is a type of UE with a large data transmission volume
  • the UE is a type of UE with a high data throughput.
  • the UE is a type of UE that is relatively sensitive to data transmission latency
  • the UE has high requirements for data transmission volume
  • the UE has high data throughput requirements
  • the UE has high requirements for data transmission latency
  • the UE supports adjusting the bwp-inactivityTimer based on LP-WUS or supports BWP handover based on LP-WUS.
  • 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, this can be agreed upon in the protocol.
  • the bwp-inactivityTimer of the first BWP is adjusted; or it can be agreed by agreement that if the second condition is met, and the terminal meets the first condition, then a BWP switch is performed; or, if the second condition is met, and the terminal meets the first condition, then the terminal decides to adjust the bwp-inactivityTimer of the first BWP or perform a BWP switch based on the first BWP.
  • the bwp-inactivityTimer of the first BWP can be adjusted; if the first BWP is the default BWP or the initial BWP, then a BWP switch can be performed.
  • the terminal may still control the BWP based on relevant technology or a traditional (legacy) BWP control method if the first 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.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • 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.
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the terminal meets the first condition when the second indication information indicates at least one of the following:
  • the terminal allows adjustment of bwp-inactivityTimer according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal When the terminal detects that LP-WUS has triggered the terminal to listen to PDCCH, it adjusts the bwp-inactivityTimer of the first BWP.
  • the serving cell of the terminal supports the terminal in adjusting bwp-inactivityTimer according to LP-WUS;
  • 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.
  • the second indication information indicates at least one of the following:
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal performs a BWP handover when it detects an LP-WUS that triggers the terminal to listen to the PDCCH.
  • the serving cell of the terminal supports the terminal in performing BWP handover based on LP-WUS;
  • 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.
  • the terminal can adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover.
  • the terminal can decide to adjust the bwp-inactivityTimer of the first BWP or perform a BWP handover based on the first 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.
  • 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.
  • SIB System Information Block
  • 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.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the network-side device 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:
  • the terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold
  • the terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold
  • the terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold
  • the terminal requires the data transmission volume to be higher than or equal to the fourth threshold.
  • the terminal requires a data throughput rate higher than or equal to the fifth threshold.
  • the terminal requires data transmission latency to be higher than or equal to the sixth threshold.
  • the terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.
  • 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.
  • NAS Non-access Stratum
  • AS Access Stratum
  • the method further includes:
  • the terminal When the terminal receives updated second indication information from the network-side device, the terminal adjusts the bwp-inactivityTimer of the first BWP.
  • the network-side device 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.
  • the terminal can adjust the bwp-inactivityTimer of the first BWP again or perform a BWP switch.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • the terminal adjusts the bwp-inactivityTimer of the first BWP;
  • the terminal performs a BWP switch
  • the second BWP is a BWP determined based on the BWP-related information.
  • the terminal 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.
  • the terminal when the second BWP is different from the first BWP, the terminal performs a BWP switch, including at least one of the following:
  • 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.
  • the terminal deactivates the first BWP and activates the second 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.
  • 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.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • the terminal 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.
  • the SpCell mentioned above may include the primary cell (PCell) and the PSCell.
  • 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.
  • CA Carrier Aggregation
  • 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.
  • the terminal 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.
  • the terminal 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.
  • Scell secondary cell
  • the terminal 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.
  • 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.
  • 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.
  • 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.
  • the terminal activates the first operation, that is, the terminal performs BWP control in the manner described in the first operation.
  • 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.
  • the terminal 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.
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • the terminal 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.
  • CA carrier aggregation
  • the first cell includes any one of the following:
  • 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.
  • 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.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the first cell mentioned above which is a cell in the cell group associated with the detected LP-WUS that has data transmission
  • LP-WUS is detected in the MCG
  • PCell of the MCG has data that needs to be transmitted
  • only the bwp-inactivityTimer of the PCell can be adjusted or a BWP handover can be performed on the PCell
  • SCell of the MCG has data that needs to be transmitted
  • 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
  • LP-WUS is detected in the SCG
  • PSCell of the SCG has data that needs to be transmitted
  • only the bwp-inactivityTimer of the PSCell can be adjusted or a BWP handover can be performed on the PSCell
  • the SCell of the SCG has data that needs to be transmitted, then only the bwp-
  • the step of adjusting the bwp-inactivityTimer of the first BWP or switching BWPs includes:
  • the terminal 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.
  • DC dual connectivity
  • 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.
  • 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.
  • the LP-WUS detection timing includes the frequency point and time domain location corresponding to the LP-WUS detection timing.
  • the LP-WUS detection timing of the MCG corresponds to frequency point 1
  • 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.
  • the detection timing of LP-WUS of MCG corresponds to time domain position 1
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 6 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:
  • Step 601 The network-side device performs a second operation, which includes at least one of the following:
  • 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;
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the first BWP is an active BWP.
  • 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.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • the terminal can be, but is not limited to, the type of terminal 11 listed above
  • 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.
  • the BWP control device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware.
  • the processing module can be implemented by a processor.
  • 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.
  • the BWP control device 700 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.
  • 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.
  • the first BWP is a BWP that is in an active state
  • the first condition includes at least one of the following:
  • 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.
  • Uplink transmission is required during LP-WUS listening.
  • processing module is specifically used for:
  • the terminal 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.
  • processing module is specifically used for:
  • the first condition includes the terminal detecting the LP-WUS;
  • the processing module is specifically used for:
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • processing module is specifically used for:
  • 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.
  • the second condition includes at least one of the following:
  • the terminal is a type of terminal whose data transmission volume is greater than or equal to the first threshold
  • the terminal is a type of terminal with a data throughput rate greater than or equal to the second threshold
  • the terminal is a type of terminal whose data transmission latency is less than or equal to the third threshold
  • the terminal requires the data transmission volume to be higher than or equal to the fourth threshold.
  • the terminal requires a data throughput rate higher than or equal to the fifth threshold.
  • the terminal requires data transmission latency to be higher than or equal to the sixth threshold.
  • the terminal supports adjusting bwp-inactivityTimer according to LP-WUS or switching BWP according to LP-WUS.
  • processing module is specifically used for:
  • 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.
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the device further includes:
  • 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.
  • processing module is further configured to:
  • the bwp-inactivityTimer of the first BWP is adjusted.
  • processing module is specifically used for:
  • 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.
  • 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.
  • processing module is specifically used for at least one of the following:
  • the second BWP is the same as the first BWP, adjust the bwp-inactivityTimer of the first BWP;
  • the second BWP is a BWP determined based on the BWP-related information.
  • processing module is specifically used for at least one of the following:
  • 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.
  • 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.
  • processing module is specifically used for:
  • 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.
  • processing module is further configured to perform at least one of the following:
  • 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).
  • Scell secondary cell
  • 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.
  • 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.
  • processing module is specifically used for:
  • 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.
  • CA carrier aggregation
  • the first cell includes any one of the following:
  • processing module is specifically used for:
  • 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.
  • 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.
  • 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.
  • the BWP control device 800 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:
  • 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;
  • 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.
  • 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 authorization information
  • the LP-WUS is used to trigger the terminal to receive a PDCCH containing downlink allocation information related to multicast configuration
  • 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 LP-WUS or to perform BWP switching according to LP-WUS;
  • the serving cell of the terminal supports guaranteeing at least one of the terminal's data transmission throughput and data transmission latency
  • the terminal 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.
  • 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.
  • 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.
  • the first BWP is an active BWP.
  • 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.
  • processing module is further configured to:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.
  • 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.
  • 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.
  • 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.
  • 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.
  • the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
  • 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.).
  • 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).
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct memory bus RAM
  • the memory 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.
  • 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.
  • 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.
  • bwp-inactivityTimer BWP inactivity timer
  • 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.
  • 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.
  • the radio frequency device 1102 receives information through the antenna 1101 and sends the received information to the baseband device 1103 for processing.
  • 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.
  • 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.
  • 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.
  • the network-side device may also include a network interface 1106, such as a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • 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.
  • This application also provides a readable storage medium storing a program or instructions.
  • the 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.
  • 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.
  • ROM computer read-only memory
  • RAM random access memory
  • magnetic disk magnetic disk
  • optical disk optical disk
  • the readable storage medium may be a non-transient readable storage medium.
  • 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.
  • 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.
  • 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.
  • 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
  • the network-side device can be used to execute the steps of the BWP control method described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种BWP控制方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的BWP控制方法包括：在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：检测到LP-WUS，所述LP-WUS用于触发所述终端监听PDCCH；在LP-WUS监听期间需要进行上行传输。

Description

BWP控制方法、装置、终端及网络侧设备
交叉引用
本公开要求于2024年8月1日提交的申请号为202411051972.3的中国专利申请的优先权，该中国专利申请的全部内容通过引用全部并入本文。
技术领域
本申请属于通信技术领域，具体涉及一种BWP控制方法、装置、终端及网络侧设备。
背景技术
在相关技术中，为了降低终端功耗，在终端引入了低功耗接收模块，即低功耗唤醒接收机(Low Power Wake Up Radio，LP-WUR)或近零功耗接收机(Almost Zero Power Wake Up Radio，AZP-WUR)。终端在节能状态下开启低功耗接收模块来监听低功耗唤醒信号(Low Power Wake Up Signal，LP-WUS)，而终端的主通信模块(或者称为主接收模块或主接收机)处于关闭状态或睡眠状态。当有下行数据到达时，网络侧设备会发送LP-WUS给终端，终端在通过低功耗接收模块监听到LP-WUS后可以开启或唤醒主通信模块进行下行数据接收；此外，在终端在通过低功耗接收模块监听LP-WUS期间有上行数据需要传输的情况下也可以开启或唤醒主通信模块进行上行数据发送。然而相关技术中，对于在终端监听LP-WUS的情况下存在数据传输时如何进行带宽部分(Bandwidth Part，BWP)控制，还没有对应的解决方案。
发明内容
本申请实施例提供一种BWP控制方法、装置、终端及网络侧设备，能够在终端监听LP-WUS的情况下，存在数据传输时及时调整激活的BWP的BWP非激活定时器或者进行BWP切换，这样有利于保证数据的传输。
第一方面，提供了一种BWP控制方法，该方法包括：
在终端满足第一条件的情况下，所述终端调整第一带宽部分BWP的BWP非激活定时器(bwp-inactivityTimer)或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道(Physical Downlink Control Channel，PDCCH)；
在LP-WUS监听期间需要进行上行传输。
第二方面，提供了一种BWP控制装置，该装置包括：
处理模块，用于在终端满足第一条件的情况下，调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；
在LP-WUS监听期间需要进行上行传输。
第三方面，提供了一种BWP控制方法，该方法包括：
网络侧设备执行第二操作，所述第二操作包括如下至少一项：
向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括BWP相关信息；
从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
向终端发送第二指示信息；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP。
第四方面，提供了一种BWP控制装置，该装置包括：
处理模块，用于执行第二操作，所述第二操作包括如下至少一项：
向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括带宽部分BWP相关信息；
从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
向终端发送第二指示信息；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP。
第五方面，提供了一种BWP控制的装置，所述装置被配置为执行如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第六方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第七方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于在终端满足第一条件的情况下，调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；
在LP-WUS监听期间需要进行上行传输。
第八方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第九方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述处理器用于执行第二操作，所述第二操作包括如下至少一项：
向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括BWP相关信息；
从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
向终端发送第二指示信息；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十一方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的BWP控制方法的步骤，所述网络侧设备可用于执行如第三方面所述的BWP控制方法的步骤。
第十二方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法的步骤，或实现如第三方面所述的方法的步骤。
第十三方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或实现如第三方面所述的方法的步骤。
在本申请实施例中，在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：检测到LP-WUS，所述LP-WUS用于触发所述终端监听PDCCH；在处于DRX非激活时间的情况下需要进行上行传输，也即本申请实施例可以在终端监听LP-WUS的情况下，存在数据传输时及时调整激活态的BWP的bwp-inactivityTimer或者进行BWP切换，这样有利于保证数据的传输。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是相关技术提供的LP WUR工作的示意图；
图3是相关技术提供的开关键控信号的示意图；
图4是本申请实施例提供的一种BWP控制方法的流程图；
图5a是本申请实施例提供的在收到LP-WUS到监听到PDCCH的时间段内bwp-InactivityTimer过期的示意图；
图5b是本申请实施例提供的终端唤醒主通信模块至接收到预配置的上行授权或者PDCCH动态调度的uplink grant的时间段内bwp-InactivityTimer过期的示意图；
图6是本申请实施例提供的另一种BWP控制方法的流程图；
图7是本申请实施例提供的一种BWP控制装置的结构图；
图8是本申请实施例提供的另一种BWP控制装置的结构图；
图9是本申请实施例提供的通信设备的结构图；
图10是本申请实施例提供的终端的结构图；
图11是本申请实施例提供的网络侧设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”的保护范围至少涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三：既包括A又包括B。此外，术语“A和/或B”、“A和B中的至少一项”、“A或B中的至少一项”也分别至少涵盖上述三种方案。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载用户设备(Vehicle User Equipment，VUE)、船载设备、行人用户设备(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AS)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmit/Receive Point，TRP)或所属领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备也可以称为核心网节点、核心网功能或核心网网元等，其包含但不限于如下至少一项：移动管理实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)、位置管理功能(Location Management Function，LMF)、网关的移动位置中心(Gateway Mobile Location Centre，GMLC)、网络数据分析功能(Network Data Analytics Function，NWDAF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型，如果在后续协议版本(例如6G)中本申请实施例提到的核心网设备的名称发生变化，也在本申请的保护范围内。
可选的，核心网设备可以由一个设备中的一个或多个功能模块实现，也可以由多个设备共同实现，本申请实施例对此不作具体限定。可以理解的是，上述功能模块既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能模块，或者是平台(例如，云平台)上实例化的虚拟化功能模块。
为了方便理解，以下对本申请实施例涉及的一些内容进行说明：
一、低功耗接收模块
低功耗接收模块，即低功耗唤醒接收机或称为近零功耗接收机，其基本原理为终端的接收端包含第一模块和第二模块，具体可以如图2所示，第一模块为主通信模块(或称为主接收模块或者主接收机或者主射频(Main Radio)模块等)，用于移动通信数据的收发，第二模块为低功耗接收模块(也称低功耗唤醒接收模块或者低功耗接收模块)，用于接收上述唤醒信号。终端在节能状态下开启低功耗接收模块来监听低功耗唤醒信号且主通信模块关闭或进入睡眠状态。当有下行数据到达时，网络会发送唤醒信号给终端，终端通过低功耗接收模块监听到唤醒信号后通过一系列的判断后触发主通信模块从关闭到开启或被唤醒，而此时低功耗接收模块从工作态进入关闭状态。低功耗唤醒接收模块可以连续开启，或间歇性开启，在开启时可接收低功耗唤醒信号。
二、低功耗唤醒信号
为了减少终端在待机状态下的接收活动，使得射频(Radio Frequency，RF)和基带模块(例如，基带调制解调器(Modem))真正的关闭从而大大降低通信接收的功耗，可以通过在终端的接收模块中引入了一个近“零”功率的接收机从而实现。这个近“零”功率的接收机不需要复杂的RF模块的信号检测(如放大、滤波、量化等等)和基带模块的信号处理，只靠被动的匹配滤波和较小功耗的信号处理。
在基站侧，通过按需(on-demand)触发唤醒信号，就可以激活近“零”功率的接收机获知激活的通告，从而触发终端内部的一系列流程，例如，打开射频收发以及基带处理等模块。
这种唤醒信号通常来说是一些比较简单的开关键控信号(on-off keying)，开关键控信号的时域样式如图3所示，那样接收机就可以通过简单的能量检测，以及之后的可能的序列检测识别等过程获知唤醒通告。此外，在终端开启低功耗唤醒接收机来接收唤醒信号的同时，主接收模块可以进入睡眠或关闭以维持在一个较低耗电水平，从而通过接收唤醒信号来实现功耗节省。唤醒信号可警告接收机存在物理下行链路控制信道传输或者其他通信。
三、RRC连接态(RRC_CONNECTED)LP-WUS
相关技术中连接态的LP-WUS是用于触发PDCCH监听的，具体包括：
对于RRC连接模式，从无线接入网工作组1(RAN Work Group 1，RAN1)的角度，进一步研究以下LP-WUS过程以触发PDCCH监控：
情况1：PDCCH监听由具有连接态下的非连续接收(Connected Discontinuous Reception，C-DRX)配置的LP-WUS触发。
选项(Option)1-1：根据DRX持续时间定时器(drx-OnDurationTimer)前的LP-WUS监听配置的LP-WUS监听，触发drx-OnDurationTimer启动。此选项可替代DCP功能。
选项1-2：根据LP-WUS监听配置，在至少传统C-DRX激活时间之外进行LP-WUS监听，以触发PDCCH监听。PDCCH监控可能与DRX-OnDurationTimer无关。
选项1-2-1：当监听LP-WUS时，可以基于传统C-DRX周期和DRX-OnDurationTimer来额外触发PDCCH监听。
如果采用这种方式，则应将其与选项1-1一起配置，以实现与传统C-DRX相比的节能增益。
选项1-2-2：当监听LP-WUS时，传统C-DRX周期和DRX-OnDurationTimer不会触发PDCCH监听。
选项1-3：根据LP-WUS监听配置，在至少传统C-DRX活动时间内进行LP-WUS监听，以触发PDCCH监听。
应考虑情况1中的选项组合。RAN1不讨论除DRX-OnDurationTimer之外的C-DRX相关定时器，此取决于无线接入网工作组2(RAN Work Group 2，RAN2)。
需要注意的是，以上并不排除支持回退机制以触发PDCCH监听。
四、BWP切换方法
当前连接态的用户设备(User Equipment，UE)(即终端)在一个服务小区可以被配置一个或多个BWP，BWP切换用于同时激活一个非激活的BWP和去激活一个激活的BWP。BWP切换的方法有使用PDCCH控制，使用bwp-InactivityTimer控制，使用RRC信令控制，或者当执行随机接入流程/在特殊小区(Special Cell，SpCell)上检测到连续的先听后说(Listen Before Talk，LBT)失败的情况下媒体接入控制(Media Access Control，MAC)实体自己控制。
对于bwp-InactivityTimer控制的BWP切换，每个服务小区配置一个bwp-InactivityTimer，一个激活的BWP关联一个bwp-InactivityTimer。当当前激活的BWP不是默认(default)BWP(defaultDownlinkBWP-Id指示的BWP)或者不是初始(initial)BWP(当defaultDownlinkBWP-Id没有配置的时候)，且当dormantBWP-Id配置的情况下不是睡眠状态的(dormant)BWP(dormantBWP-Id关联的BWP)，当有调度的情况下，包括如下：
在该BWP上收到了小区无线网络临时标识(Cell Radio Network Temporary Identity，C-RNTI)/配置调度无线网络临时标识(Configured Scheduling Radio Network Temporary Identity，CS-RNTI)加扰的指示下行分配或上行授权的PDCCH；
或者，收到了为多播配置的组无线网络临时标识(Group Radio Network Temporary Identity，G-RNTI)/组配置调度无线网络临时标识(Group Configured Scheduling Radio Network Temporary Identity，G-CS-RNTI)加扰的指示下行分配PDCCH；
或者，收到了针对该激活的BWP的C-RNTI/CS-RNTI加扰的指示下行分配或上行授权的PDCCH；
或者，在配置授权(configured grant)上传输了MAC协议数据单元(Protocol Data Unit，PDU)且未从底层收到LBT失败指示；
或者，在下行分配上收到了一个单播相关的MAC PDU或多播和广播服务(Multicast and Broadcast Service，MBS)相关的MAC PDU。
且当前该服务小区没有正在运行的随机接入或者正在运行的随机接入流程在收到这个C-RNTI加扰的PDCCH之后就成功完成了，则启动或者重新启动该BWP相关的bwp-InactivityTimer。
上述initial BWP对于非(non)降低性能(Reduced Capability，RedCap)UE来说，为初始下行BWP(initialDownlinkBWP)配置的BWP，对于RedCap UE来说，initial BWP为initialDownlinkBWP-RedCap(如果配置)配置或initialDownlinkBWP(如果未配置initialDownlinkBWP-RedCap)的BWP。
当激活的BWP相关的bwp-InactivityTimer过期之后，如果配置了default BWP，则UE执行BWP切换并切换到default BWP，否则UE切换到initial BWP。
当UE收到用于BWP切换的PDCCH，且PDCCH指示的激活的BWP不是default BWP(defaultDownlinkBWP-Id指示的BWP)或者不是initial BWP(当defaultDownlinkBWP-Id没有配置的时候)且当dormantBWP-Id配置的情况下不是dormant BWP，则UE启动或者重新启动该BWP相关的bwp-InactivityTimer。
当UE在一个服务小区执行随机接入(Random Access Channel，RACH)流程的时候，在选择完载波后，对于选择的载波对应的服务小区，UE在停止该服务小区关联的激活的BWP的bwp-InactivityTimer。如果该小区为辅小区(Secondary Cell，SCell)，则也要停止SpCell的激活的BWP的bwp-InactivityTimer。
当网络侧下发的RRC信令中释放了bwp-InactivityTimer的配置时，UE要停止该服务小区的激活的BWP的bwp-InactivityTimer。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的BWP控制方法进行详细地说明。
请参见图4，图4是本申请实施例提供的一种BWP控制方法的流程图，该方法可以由终端执行，如图4所示，包括以下步骤：
步骤401、在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
检测到LP-WUS，所述LP-WUS用于触发所述终端监听PDCCH；
在LP-WUS监听期间需要进行上行传输。
本实施例中，上述第一BWP可以为上述终端当前处于激活状态的BWP，也即第一BWP为上述终端当前工作的BWP。其中，上述第一BWP可以为网络侧设备配置的BWP，不为默认BWP或者初始BWP；或者上述第一BWP可以为默认BWP或者初始BWP。
上述调整第一BWP的bwp-inactivityTimer可以包括但不限于开启或者重新开启或者停止第一BWP的bwp-inactivityTimer、或者调整第一BWP的bwp-inactivityTimer的定时时长等。例如，在上述第一BWP不为默认BWP或者初始BWP的情况下，可以开启或者重新开启或者停止第一BWP的bwp-inactivityTimer。
上述BWP切换可以理解为将终端的工作的BWP由第一BWP切换为与第一BWP不同的BWP。例如，在上述第一BWP为默认BWP或者初始BWP的情况下，将终端的工作的BWP由第一BWP切换为预先配置的其它BWP。
上述LP-WUS用于触发所述终端监听PDCCH。在一些可选的实施例中，上述LP-WUS可以包括BWP控制相关信息，例如，上述BWP控制相关信息可以包括BWP相关信息和用于BWP控制的指示信息等中的至少一项。
上述在LP-WUS监听期间需要进行上行传输，例如，在LP-WUS监听期间接收到非接入层发送的信息，该信息用于触发进行上行传输。
对于上述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，示例性地，终端可以根据所述第一BWP来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，在第一BWP不为default BWP或者initial BWP的情况下，可以调整第一BWP的bwp-inactivityTimer；在第一BWP为default BWP或者initial BWP的情况下，可以进行BWP切换；或者，终端可以根据检测到的LP-WUS来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，可以根据上述LP-WUS携带的BWP控制相关信息来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换；或者，可以基于协议约定来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，若协议约定在终端满足第一条件的情况下调整第一BWP的bwp-inactivityTimer，则终端在满足第一条件下调整第一BWP的bwp-inactivityTimer；若协议约定终端满足第一条件的情况下进行BWP切换，则终端在满足第一条件下进行BWP切换。
实际应用中，处于连接态下的终端可以在主通信模块处于关闭或睡眠状态期间，通过低功耗唤醒接收机监听LP-WUS，并在监听到LP-WUS的情况下开启或唤醒主通信模块进行PDCCH监听，或者可以在监听LPWUS期间需要进行上行传输的情况下开启或唤醒主通信模块进行上行传输。以下分情况进行举例说明：
情况一：在终端工作的BWP(即第一BWP)不为default BWP或者initial BWP的情况下，当终端检测到LP-WUS的时候，唤醒主通信模块去监听PDCCH，但是在收到LP-WUS到监听到PDCCH之间，终端当前工作的BWP的bwp-InactivityTimer可能过期了，如图5a所示，此时终端工作的BWP就会切换为default BWP或者initial BWP，但是如果LP-WUS触发PDCCH监听是为了下行调度，证明后面有可能会有大量的数据传输要执行，此时将终端的工作的BWP切换为default BWP或者initial BWP不利于大量数据的传输。在该情况下，本实施例可以在检测到LP-WUS的情况下，调整终端当前工作的BWP(即第一BWP)的bwp-InactivityTimer，例如，可以开启或者重新开启或者停止第一BWP的bwp-inactivityTimer，这样有利于减少在终端监听到PDCCH之前，终端当前工作的BWP的bwp-InactivityTimer过期的情况发生，进而有利于保证下行传输的吞吐量。
情况二：当终端检测到LP-WUS的时候，若该LP-WUS包括BWP控制相关信息，则终端可以基于该BWP控制相关信息调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，若上述BWP控制相关信息包括用于BWP控制的指示信息，则可以在该用于BWP控制的指示信息指示终端调整第一BWP的bwp-inactivityTimer的情况下，终端可以调整第一BWP的bwp-inactivityTimer；在该用于BWP控制的指示信息指示终端切换BWP的情况下，终端可以切换BWP，例如，在第一BWP为default BWP或者initial BWP的情况下，可以切换至网络预配置的BWP，这样有利于提高数据传输的吞吐量；在第一BWP不为default BWP或者initial BWP的情况下，可以切换至default BWP或者initial BWP，这样可以在保证数据传输的同时，节省电量。
情况三：在终端工作的BWP不为default BWP或者initial BWP的情况下，当终端使用低功耗接收机监听LP-WUS期间(即终端未处于PDCCH监听阶段)，终端有上行数据要传输时，也会出现在终端唤醒主通信模块至接收到预配置的上行授权(uplink grant)或者PDCCH动态调度的uplink grant的时间段内bwp-InactivityTimer过期的问题，如图5b所示，此时终端工作的BWP也会切换到default BWP或者initial BWP。在该情况下，本实施例可以在监听LP-WUS期间需要进行上行传输的情况下，调整终端当前工作的BWP(即第一BWP)的bwp-InactivityTimer，例如，可以开启或者重新开启或者停止第一BWP的bwp-inactivityTimer，这样有利于减少在终端进行上行传输之前，终端当前工作的BWP的bwp-InactivityTimer过期的情况发生，进而有利于保证上行传输的吞吐量。
情况四：在终端工作的BWP为default BWP或者initial BWP的情况下，若监听LP-WUS期间需要进行上行传输，则可以将终端的工作的BWP切换为预配置的BWP，以提高上行传输的吞吐量。
情况五：在终端检测到LP-WUS且需要进行上行传输的情况下，若终端工作的BWP不为default BWP或者initial BWP的情况下，则可以调整终端工作的BWP(即第一BWP)的bwp-InactivityTimer，例如，可以开启或者重新开启或者停止第一BWP的bwp-inactivityTimer，这样有利于减少在终端监听到PDCCH之前，终端当前工作的BWP的bwp-InactivityTimer过期的情况发生，进而有利于保证数据传输的吞吐量；若终端工作的BWP为default BWP或者initial BWP的情况下，则可以进行BWP切换，例如，可以切换至预配置的BWP，以提高数据传输的吞吐量。
在本申请实施例中，在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：检测到LP-WUS，所述LP-WUS用于触发所述终端监听PDCCH；在处于DRX非激活时间的情况下需要进行上行传输，也即本申请实施例可以在终端监听LP-WUS的情况下存在数据传输时，调整激活态的BWP的bwp-inactivityTimer或者进行BWP切换，这样有利于保证数据的传输。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
在所述终端在非连续接收(Discontinuous Reception，DRX)非激活时间监听LP-WUS的情况下，若终端满足第一条件，则所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
示例性地，在UE(即上述终端)配置了低功耗接收机，且网络侧设备向该UE发送了LP-WUS的配置信息，并激活了RRC_CONNECTED UE监听LP-WUS的情况下，该UE处于DRX非激活时间，并在处于DRX非激活时间内监听LP-WUS。在UE在DRX非激活时间内监听LP-WUS的情况下，若该UE满足第一条件，则该UE调整激活的BWP的bwp-inactivityTimer或者进行BWP切换。
本实施例中，终端在DRX非激活时间监听LP-WUS，并在所述终端在DRX非激活时间监听LP-WUS的期间若终端满足第一条件，则所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，这样有利于在节省电量的同时保证数据传输。
可选地，所述终端调整第一BWP的bwp-inactivityTimer，包括：
所述终端开启或者重新开启或者停止第一BWP的bwp-inactivityTimer。
本实施例中，在终端满足第一条件的情况下，开启或者重新开启或者停止第一BWP的bwp-inactivityTimer，这样有利于减少在终端监听到PDCCH之前或者在终端进行上行传输之前，第一BWP的bwp-InactivityTimer过期的情况发生。
可选地，所述第一条件包括所述终端检测到所述LP-WUS；
所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
在检测到的所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可以理解的是，在第一指示信息用于指示调整第一BWP的bwp-inactivityTimer的情况下，终端可以调整第一BWP的bwp-inactivityTimer；在第一指示信息用于指示进行BWP切换的情况下，终端可以进行BWP切换，示例性地，在第一指示信息用于指示进行BWP切换的情况下，终端可以将工作的BWP由第一BWP切换至预配置的BWP；或者，若上述LP-WUS还包括BWP相关信息，则终端可以基于BWP相关信息进行BWP切换，例如，终端可以将工作的BWP由第一BWP切换至根据上述BWP相关信息确定的BWP。
示例性地，上述预配置的BWP可以是终端从网络侧设备接收的控制信息中所携带的BWP标识所表示的BWP，例如，终端从网络侧设备接收控制信息，该控制信息包括BWP标识，用于指示在终端满足第一条件的情况下切换至基于该BWP标识所表示的BWP。
在上述第一指示信息用于指示如下任一项的情况下，终端可以调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，可以协议约定在第一指示信息用于指示如下任一项的情况下调整第一BWP的bwp-inactivityTimer；或者可以协议约定在上述第一指示信息用于指示如下任一项的情况下进行BWP切换；或者，可以在上述第一指示信息用于指示如下任一项的情况下，终端根据第一BWP来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，在第一BWP不为default BWP或者initial BWP的情况下，可以调整第一BWP的bwp-inactivityTimer；在第一BWP为default BWP或者initial BWP的情况下，可以进行BWP切换：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度。
本实施例中，在检测到的LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型的情况下，终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，这样不仅有利于提高BWP控制的灵活性和准确性，还可以保证当前检测到的LP-WUS的功能就是触发终端进行数据调度，从而通过调整BWP保证数据传输的性能。
可选地，所述在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
若所述终端满足第二条件，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二条件包括如下至少之一：
所述终端为数据传输量大于或等于第一阈值的终端类型；
所述终端为数据吞吐率大于或等于第二阈值的终端类型；
所述终端为数据传输时延小于或等于第三阈值的终端类型；
所述终端对数据传输量要求高于或等于第四阈值；
所述终端对数据吞吐率要求高于或等于第五阈值；
所述终端对数据传输时延要求高于或等于第六阈值；
所述终端支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
上述第一阈值、第二阈值、第三阈值、第四阈值、第五阈值和第六阈值中的至少一项可以根据实际需求进行合理设置，本实施例对此不做限定。
示例性地，可以在UE满足如下至少一项的情况下，若满足第一条件则调整第一BWP的bwp-inactivityTimer或者进行BWP切换：
所述UE为数据传输量较大的UE类型；
所述UE为数据吞吐率较大的UE类型；
所述UE为对数据传输时延比较敏感的UE类型；
所述UE对数据传输量要求高；
所述UE对数据吞吐率要求高；
所述UE对数据传输时延要求高；
所述UE支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
可以理解的是，若所述第二条件包括所述终端支持根据LP-WUS调整bwp-inactivityTimer，则终端可以调整第一BWP的bwp-inactivityTimer；若所述第二条件包括所述终端支持根据LP-WUS进行BWP切换，则在终端满足第一条件的情况下终端进行BWP切换；若所述第二条件未包括所述终端支持根据LP-WUS调整bwp-inactivityTimer和所述终端支持根据LP-WUS进行BWP切换中的任一项，则在终端满足第一条件的情况下终端可以调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，可以协议约定在满足第二条件的情况下，若终端满足第一条件则调整第一BWP的bwp-inactivityTimer；或者可以协议约定在满足第二条件的情况下，若终端满足第一条件则进行BWP切换；或者，可以在满足第二条件的情况下，若终端满足第一条件则终端根据第一BWP来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，在第一BWP不为default BWP或者initial BWP的情况下，可以调整第一BWP的bwp-inactivityTimer；在第一BWP为default BWP或者initial BWP的情况下，可以进行BWP切换。
在一些可选的实施例中，在不满足第二条件的情况下，所述终端可以在满足第一条件的情况下仍基于相关技术或传统(Legacy)的BWP控制方式对BWP进行控制。
本实施例中，若满足第二条件，则在所述终端满足第一条件的情况下所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，这样不仅可以满足那些对传输要求相对较高的终端的传输要求，还可以不影响对传输要求相对较低的终端的BWP控制。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
若所述终端从网络侧设备接收到第二指示信息，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
本实施例中，在所述第二指示信息用于指示如下至少一项的情况下，若终端满足第一条件，则所述终端可以调整第一BWP的bwp-inactivityTimer：
所述终端允许根据LP-WUS调整bwp-inactivityTimer；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer；
所述终端的服务小区支持在终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer。
在所述第二指示信息用于指示如下至少一项的情况下，若终端满足第一条件，则所述终端可以进行BWP切换：
允许根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下进行BWP切换。
需要说明的是，在所述第二指示信息仅用于指示所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项的情况下，若终端满足第一条件，则终端可以调整第一BWP的bwp-inactivityTimer或进行BWP切换，例如，可以协议约定在接收到第二指示信息的情况下调整第一BWP的bwp-inactivityTimer；或者可以协议约定在接收到第二指示信息的情况下，若终端满足第一条件，则进行BWP切换；或者，可以在接收到第二指示信息的情况下，若终端满足第一条件，则终端根据第一BWP来决定调整第一BWP的bwp-inactivityTimer或者进行BWP切换，例如，在第一BWP不为default BWP或者initial BWP的情况下，可以调整第一BWP的bwp-inactivityTimer；在第一BWP为default BWP或者initial BWP的情况下，可以进行BWP切换。
示例性地，网络侧设备可以通过系统信息块(System Information Block，SIB)消息或者RRC重配置消息向终端发送上述第二指示信息。
本实施例中，由网络侧设备向终端发送第二指示信息来指示终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，这样可以实现网络控制终端是否可以根据LP-WUS进行BWP控制，从而可以提高控制的灵活性。
可选地，所述方法还包括：
所述终端上报第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量的要求，所述终端对数据吞吐率的要求，所述终端对数据传输时延的要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer，或者所述能力信息用于指示所述终端支持或不支持根据LP-WUS进行BWP切换。
上述终端的类型，例如，上述终端是否为数据传输量大于或等于第一阈值的终端类型，和/或者，上述终端是否为数据吞吐率大于或等于第二阈值的终端类型。
上述终端对数据传输量的要求，例如，上述终端对数据传输量要求是否高于或等于第四阈值。
上述终端对数据吞吐率的要求，例如，上述终端对数据吞吐率要求是否高于或等于第五阈值。
上述终端对数据传输时延的要求，例如，上述终端对数据传输时延要求是否高于或等于第六阈值。
示例性地，终端上报第一信息，网络侧设备在接收到第一信息的情况下，可以根据第一信息确定是否向终端发送第二指示信息，或者可以根据第一信息确定是否向终端发送更新的第二指示信息，这样有利于提高网络侧设备指示终端进行BWP控制的合理性。例如，在上述第一信息用于指示如下至少一项的情况下，网络侧设备可以向终端发送第二指示信息或者更新的第二指示信息，否则网络侧设备可以不向终端发送第二指示信息或者更新的第二指示信息：
所述终端为数据传输量大于或等于第一阈值的终端类型；
所述终端为数据吞吐率大于或等于第二阈值的终端类型；
所述终端为数据传输时延小于或等于第三阈值的终端类型；
所述终端对数据传输量要求高于或等于第四阈值；
所述终端对数据吞吐率要求高于或等于第五阈值；
所述终端对数据传输时延要求高于或等于第六阈值；
所述终端支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
示例性地，终端可以通过非接入层(Non-access Stratum，NAS)信令上报上述第一信息，例如，可以通过注册请求消息上报上述第一信息；或者，终端可以通过接入层(Access Stratum，AS)信令上报上述第一信息，例如，可以通过UE能力上报消息、UE辅助信息上报消息，UE信息响应消息等上报上述第一信息。
可选地，所述在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换之前，所述方法还包括：
在所述终端从所述网络侧设备接收到更新的第二指示信息的情况下，所述终端调整第一BWP的bwp-inactivityTimer。
示例性地，网络侧设备向终端发送第二指示信息之后，接收到终端上报的第一信息，在该情况下，网络侧设备可以基于上述第一信息，向终端发送更新的第二指示信息，终端可以根据更新的第二指示信息调整所述第一BWP的bwp-inactivityTimer。
需要说明的是，在终端基于更新的第二指示信息调整第一BWP的bwp-inactivityTimer之后，若终端满足第一条件，则终端可以再次调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
在所述终端检测到LP-WUS且所述LP-WUS包括BWP相关信息的情况下，所述终端根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换。
示例性地，上述BWP相关信息可以包括但不限于用于确定BWP的信息、第一BWP的bwp-inactivityTimer更新的定时时长等。
本实施例中基于LP-WUS携带的BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换，这样不仅可以提高BWP控制的准确性，保证数据传输的吞吐量，还可以节省信令开销。
可选地，所述BWP相关信息包括BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
本实施例中，通过在LP-WUS携带BWP索引，这样终端在检测到LP-WUS的情况下，可以直接在其所携带的BWP索引所指示的BWP上去监听PDCCH，不仅可以实现对终端BWP的准确控制，还实现较为简单。
可选地，所述终端根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换，包括如下至少一项：
在第二BWP与所述第一BWP相同的情况下，所述终端调整所述第一BWP的bwp-inactivityTimer；
在第二BWP与所述第一BWP不相同的情况下，所述终端进行BWP切换；
其中，所述第二BWP为根据所述BWP相关信息确定的BWP。
本实施例中，在第二BWP与所述第一BWP相同的情况下，所述终端调整所述第一BWP的bwp-inactivityTimer；在第二BWP与所述第一BWP不相同的情况下，所述终端进行BWP切换，这样可以保证终端在网络侧设备所指示的BWP上进行PDCCH监听。
可选地，所述在第二BWP与所述第一BWP不相同的情况下，所述终端进行BWP切换，包括如下至少一项：
在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP不为默认BWP或初始BWP，则所述终端去激活所述第一BWP，激活所述第二BWP，并在激活所述第二BWP的情况下启动所述第二BWP的bwp-inactivityTimer；
在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP为默认BWP或初始BWP，则所述终端去激活所述第一BWP，并激活所述第二BWP。
本实施例中，在第二BWP与所述第一BWP不相同且第二BWP不为默认BWP或初始BWP的情况下，可以在将终端工作的BWP由第一BWP切换至第二BWP(即去激活所述第一BWP，激活所述第二BWP)的情况下，启动所述第二BWP的bwp-inactivityTimer，进而可以在第二BWP的bwp-inactivityTimer超期前通过第二BWP传输数据，这样有利于提高数据传输的吞吐量；在第二BWP与所述第一BWP不相同且第二BWP为默认BWP或初始BWP的情况下，终端可以在将终端工作的BWP由第一BWP切换至第二BWP，并基于第二BWP传输数据，这样有利于降低功耗。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
若所述终端处于单连接状态、或者所述终端仅配置了特殊小区SpCell，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
本实施例中，上述SpCell可以包括主小区(Primary Cell，PCell)和PSCell。
实际应用中，若在载波聚合(Carrier Aggregation，CA)状态下，网络侧设备发送LP-WUS是为了在主小区(Primary Cell，PCell)或者辅小区(Secondary Cell，SCell)#1上发送PDCCH，而在SCell#2上不会发送PDCCH，则在该情况下，调整PCell或者SCell#1的bwp-inactivityTimer或只对PCell或者SCell#1进行BWP切换是合理的，而对SCell#2的bwp-inactivityTimer或只对SCell#2进行BWP切换是不合理的，但由于LP-WUS没有指示特定小区的功能，因此UE无法在收到LP-WUS之后确定在哪个小区上监听PDCCH。基于此，本实施例可以仅在终端处于单连接状态、或者所述终端仅配置了SpCell的情况下，若终端满足第一条件，则所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，这样终端可以明确在哪个小区上监听PDCCH，进而可以保证对该小区的BWP进行控制。
在一些可选的实施例中，在所述终端处于CA状态、或者所述终端添加了Scell的情况下，所述终端可以在满足第一条件的情况下仍基于相关技术或传统(Legacy)的BWP控制方式对BWP进行控制；或者，所述终端可以在满足第一条件的情况下只调整PCell或者SCell#1的bwp-inactivityTimer或只对PCell或者SCell#1进行BWP切换。
可选地，所述方法还包括如下至少一项：
在所述终端由单连接状态切换至CA状态、或者所述终端添加了辅小区Scell的情况下，所述终端去激活第一操作；
在所述终端由CA状态切换至单连接状态、或者所述终端恢复为仅配置SpCell的情况下，所述终端激活第一操作；
其中，所述第一操作为：在所述终端满足第一条件的情况下所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
本实施例中，对于上述终端添加了Scell，例如，若终端发送了Scell添加的信令，则认为终端添加了Scell。
上述终端去激活第一操作，也即终端不按照上述第一操作的方式进行BWP控制，也就是说，在所述终端由单连接状态切换至CA状态、或者所述终端添加了辅小区Scell的情况下，终端不再执行上述步骤401。
上述终端激活第一操作，也即终端按照上述第一操作的方式进行BWP控制，也就是说，在所述终端由CA状态切换至单连接状态、或者所述终端恢复为仅配置SpCell的情况下，终端继续执行上述步骤401。
本实施例在所述终端由单连接状态切换至CA状态、或者所述终端添加了Scell的情况下，所述终端去激活第一操作；在所述终端由CA状态切换至单连接状态、或者所述终端恢复为仅配置SpCell的情况下，所述终端激活第一操作，这样可以实现终端在不同状态下对BWP的不同控制方式，进而可以提高BWP控制的灵活性。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
若所述终端处于载波聚合CA状态、或者所述终端配置了SpCell和SCell，则在所述终端满足第一条件的情况下，所述终端调整第一小区的第一BWP的bwp-inactivityTimer或者对第一小区进行BWP切换；
其中，所述第一小区包括如下任一项：
SpCell；
检测到的LP-WUS关联的小区组中存在数据传输的小区；
网络侧设备配置或预配置的小区；
检测到的LP-WUS指示的小区。
本实施例中，在所述终端处于CA状态、或者所述终端配置了SpCell和SCell的情况下，可以仅根据LP-WUS调整第一小区的第一BWP的bwp-inactivityTimer或者仅根据LP-WUS对第一小区进行BWP切换。
对于上述第一小区为SpCell，例如，对于主小区组(Master Cell Group，MCG)的LP-WUS，可以只调整PCell的bwp-inactivityTimer或对PCell进行BWP切换；对于辅小区组(Secondary Cell Group，SCG)的LP-WUS，可以只调整PSCell的bwp-inactivityTimer或对PSCell进行BWP切换。
对于上述第一小区为检测到的LP-WUS关联的小区组中存在数据传输的小区，例如，若在MCG检测到LP-WUS，则若MCG的PCell存在数据需要传输，则可以只调整PCell的bwp-inactivityTimer或对PCell进行BWP切换；若MCG的SCell存在数据需要传输，则可以只调整MCG的SCell的bwp-inactivityTimer或对MCG的SCell进行BWP切换；若在SCG检测到LP-WUS，则若SCG的PSCell存在数据需要传输，则可以只调整PSCell的bwp-inactivityTimer或对PSCell进行BWP切换；若SCG的SCell存在数据需要传输，则可以只调整SCG的SCell的bwp-inactivityTimer或对SCG的SCell进行BWP切换。其中，所述存在数据传输的小区可以包括如下至少一项：不为去激活的小区，不为休眠的小区，与LP-WUS所在频点或频段不同的小区。
可选地，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
在所述终端处于双连接(Dual Connectivity，DC)状态的情况下，若所述终端检测到LP-WUS，则所述终端的第一MAC实体根据第一小区组关联的LP-WUS，调整所述第一小区组的第一BWP的bwp-inactivityTimer或对所述第一小区组进行BWP切换；
其中，所述第一小区组为主小区组MCG或辅小区组SCG，所述第一MAC实体为所述第一小区组关联的MAC实体。
本实施例中，终端的各个MAC实体分别根据其相关的小区组关联的LP-WUS，调整其相关的小区组的第一BWP的bwp-inactivityTimer或对其相关的小区组进行BWP切换。其中，上述小区组关联的LP-WUS可以包括在该小区组对应的LP-WUS检测时机检测到的LP-WUS，或根据LP-WUS携带的第三指示信息确定，所述第三指示信息用于指示该LP-WUS关联的小区组。
其中，所述LP-WUS检测时机包括LP-WUS的检测时机对应的频点，时域位置等。例如，MCG的LP-WUS检测时机对应频点1，SCG的LP-WUS的检测时机对应频点2，UE分别在频点1和频点2检测LP-WUS，如果在频点1检测到LP-WUS，则UE的MCG对应的MAC实体根据在频点1检测到的LP-WUS进行BWP控制；如果在频点2检测到LP-WUS，则UE的SCG对应的MAC实体根据在频点2检测到的LP-WUS进行BWP控制。又例如，MCG的LP-WUS的检测时机对应时域位置1，SCG的LP-WUS的检测时机对应时域位置1，UE分别在时域位置1和时域位置2检测LP-WUS，如果在时域位置1检测到LP-WUS，则UE的MCG对应的MAC实体根据在时域位置1检测到的LP-WUS进行BWP控制；如果在时域位置2检测到LP-WUS，则UE的SCG对应的MAC实体根据在时域位置2检测到的LP-WUS进行BWP控制。
上述第三指示信息可以用于指示该LP-WUS对应的是MCG的LP-WUS还是SCG的LP-WUS；或者，上述第三指示信息可以为LP-WUS序列或LP-WUS中携带的比特信息，即通过LP-WUS序列来指示该LP-WUS关联的小区组，例如，LP-WUS序列1关联MCG，LP-WUS序列2关联SCG。示例性地，若UE检测到的LP-WUS携带的指示信息指示MCG，则UE的MCG对应的MAC实体根据该LP-WUS进行BWP控制；若UE检测到的LP-WUS携带的指示信息指示SCG，则UE的SCG对应的MAC实体根据该LP-WUS进行BWP控制。
本实施例中，终端的各个MAC实体分别根据其相关的小区组关联的LP-WUS，调整其相关的小区组的第一BWP的bwp-inactivityTimer或对其相关的小区组进行BWP切换，这样可以保证终端不同的小区组的LP-WUS是互不干扰的，从而网络侧可以分别控制MCG和SCG通过LP-WUS进行BWP的控制，可以提高控制的灵活性。
需要说明的是，本申请实施例的上述各个实施方式之间可以根据实际需求进行合理组合，本实施例对此不做限定。
请参见图6，图6是本申请实施例提供的一种BWP控制方法的流程图，该方法可以由网络侧设备执行，如图6所示，包括以下步骤：
步骤601、网络侧设备执行第二操作，所述第二操作包括如下至少一项：
向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括BWP相关信息；
从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
向终端发送第二指示信息；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP。
可选地，所述BWP相关信息BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
可选地，所述方法还包括：
所述网络侧设备根据所述第一信息，确定是否向所述终端发送所述第二指示信息或者更新的第二指示信息。
需要说明的是，该实施方式的实现方式可以参见图4所示的实施例的相关说明，此处不作赘述。
需要说明的是，本申请实施例提供的BWP控制方法，执行主体可以为BWP控制装置。本申请实施例中以BWP控制装置执行BWP控制方法为例，说明本申请实施例提供的BWP控制装置。
本申请实施例提供一种BWP控制装置，作为一种示例，BWP控制装置可以是通信设备或通信设备中的部件，例如芯片。该通信设备可以是终端、网络侧设备或服务器等。示例性的，终端可以包括但不限于上述所列举的终端11的类型，网络侧设备可以包括但不限于上述所列举的网络侧设备12的类型，本申请实施例不作具体限定。
BWP控制装置包括接收模块、发送模块和处理模块。其中，接收模块、发送模块和处理模块可以是通过软件实现，也可以通过硬件实现。当通过硬件实现时，处理模块可以由处理器实现，示例性的，处理器可以包括通用处理器、专用处理器等，例如包括中央处理单元(Central Processing Unit，CPU)、微处理器、数字信号处理器(Digital Signal Processor，DSP)、人工智能(Artificial Intelligent，AI)处理器、图形处理器(Graphics Processing Unit，GPU)、专用集成电路(Application Specific Integrated Circuit，ASIC)、网络处理器(Network Processor，NP)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、门电路、晶体管、分立硬件组件等。接收模块和发送模块可以由通信接口实现，通信接口可以包括收发器、管脚、电路、总线、射频单元等其中一种或多种。
具体的，参见图7，当BWP控制装置为终端或终端中的部件时，BWP控制装置700包括处理模块701，用于在终端满足第一条件的情况下，调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；
在LP-WUS监听期间需要进行上行传输。
可选地，所述处理模块具体用于：
在所述终端在非连续接收DRX非激活时间监听LP-WUS的情况下，若终端满足第一条件，则调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述处理模块具体用于：
开启或者重新开启或者停止第一BWP的bwp-inactivityTimer。
可选地，所述第一条件包括所述终端检测到所述LP-WUS；
所述处理模块具体用于：
在检测到的所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述处理模块具体用于：
若所述终端满足第二条件，则在所述终端满足第一条件的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二条件包括如下至少之一：
所述终端为数据传输量大于或等于第一阈值的终端类型；
所述终端为数据吞吐率大于或等于第二阈值的终端类型；
所述终端为数据传输时延小于或等于第三阈值的终端类型；
所述终端对数据传输量要求高于或等于第四阈值；
所述终端对数据吞吐率要求高于或等于第五阈值；
所述终端对数据传输时延要求高于或等于第六阈值；
所述终端支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
可选地，所述处理模块具体用于：
若所述终端从网络侧设备接收到第二指示信息，则在所述终端满足第一条件的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述装置还包括：
发送模块，用于上报第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量的要求，所述终端对数据吞吐率的要求，所述终端对数据传输时延的要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer，或者所述能力信息用于指示所述终端支持或不支持根据LP-WUS进行BWP切换。
可选地，所述处理模块还用于：
在所述终端从所述网络侧设备接收到更新的第二指示信息的情况下，调整第一BWP的bwp-inactivityTimer。
可选地，所述处理模块具体用于：
在所述终端检测到LP-WUS且所述LP-WUS包括BWP相关信息的情况下，根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换。
可选地，所述BWP相关信息包括BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
可选地，所述处理模块具体用于如下至少一项：
在第二BWP与所述第一BWP相同的情况下，调整所述第一BWP的bwp-inactivityTimer；
在第二BWP与所述第一BWP不相同的情况下，进行BWP切换；
其中，所述第二BWP为根据所述BWP相关信息确定的BWP。
可选地，所述处理模块具体用于如下至少一项：
在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP不为默认BWP或初始BWP，则去激活所述第一BWP，激活所述第二BWP，并在激活所述第二BWP的情况下启动所述第二BWP的bwp-inactivityTimer；
在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP为默认BWP或初始BWP，则去激活所述第一BWP，并激活所述第二BWP。
可选地，所述处理模块具体用于：
若所述终端处于单连接状态、或者所述终端仅配置了特殊小区SpCell，则在所述终端满足第一条件的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述处理模块还用于如下至少一项：
在所述终端由单连接状态切换至CA状态、或者所述终端添加了辅小区Scell的情况下，去激活第一操作；
在所述终端由CA状态切换至单连接状态、或者所述终端恢复为仅配置SpCell的情况下，激活第一操作；
其中，所述第一操作为：在所述终端满足第一条件的情况下所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
可选地，所述处理模块具体用于：
若所述终端处于载波聚合CA状态、或者所述终端配置了SpCell和SCell，则在所述终端满足第一条件的情况下，调整第一小区的第一BWP的bwp-inactivityTimer或者对第一小区进行BWP切换；
其中，所述第一小区包括如下任一项：
SpCell；
检测到的LP-WUS关联的小区组中存在数据传输的小区；
网络侧设备配置或预配置的小区；
检测到的LP-WUS指示的小区。
可选地，所述处理模块具体用于：
在所述终端处于双连接DC状态的情况下，若所述终端检测到LP-WUS，则通过第一MAC实体根据第一小区组关联的LP-WUS，调整所述第一小区组的第一BWP的bwp-inactivityTimer或对所述第一小区组进行BWP切换；
其中，所述第一小区组为主小区组MCG或辅小区组SCG，所述第一MAC实体为所述第一小区组关联的MAC实体。
本申请实施例提供的BWP控制装置能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
参见图8，当BWP控制装置为网络侧设备或网络侧设备中的部件时，BWP控制装置800包括处理模块801，用于执行第二操作，所述第二操作包括如下至少一项：
向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括BWP相关信息；
从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
向终端发送第二指示信息；
其中，所述第一指示信息用于指示如下任一项：
所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
存在对所述终端的数据调度；
调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第二指示信息用于指示如下至少一项：
允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
其中，所述第一BWP为处于激活状态的BWP。
可选地，所述BWP相关信息BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
可选地，所述处理模块还用于：
根据所述第一信息，确定是否向所述终端发送所述第二指示信息或者更新的第二指示信息。
本申请实施例提供的BWP控制装置能够实现图6的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
如图9所示，本申请实施例还提供一种通信设备900，包括处理器901和存储器902，存储器902上存储有可在所述处理器901上运行的程序或指令，例如，该通信设备900为终端时，该程序或指令被处理器901执行时实现上述BWP控制方法实施例的各个步骤，且能达到相同的技术效果。该通信设备900为网络侧设备时，该程序或指令被处理器901执行时实现上述BWP控制方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图4所示方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。该终端可以是图7所示的BWP控制装置。具体地，图10为实现本申请实施例的一种终端的硬件结构示意图。
该终端1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009以及处理器1010等中的至少部分部件。
本领域技术人员可以理解，终端1000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器10 10逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图10中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1004可以包括图形处理器10041和麦克风10042，图形处理器10041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1006可包括显示面板10061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板10061。用户输入单元1007包括触控面板10071以及其他输入设备10072中的至少一种。触控面板10071，也称为触摸屏。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1001接收来自网络侧设备的下行数据后，可以传输给处理器1010进行处理；另外，射频单元1001可以向网络侧设备发送上行数据。通常，射频单元1001包括但不限于天线、放大器、收发器、耦合器、低噪声放大器、双工器等。
存储器1009可用于存储软件程序或指令以及各种数据。存储器1009可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1009可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1009包括但不限于这些和任意其它适合类型的存储器。
处理器1010可包括一个或多个处理单元；可选的，处理器1010集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
其中，处理器1010，用于在终端满足第一条件的情况下，调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；在LP-WUS监听期间需要进行上行传输。
可以理解，本实施例中提及的各实现方式的实现过程可以参照前述终端侧的BWP控制方法实施例的相关描述，并达到相同或相应的技术效果，为避免重复，在此不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图6所示的方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备，该网络侧设备可以是图8所示的BWP控制装置。如图11所示，该网络侧设备1100包括：天线1101、射频装置1102、基带装置1103、处理器1104和存储器1105。天线1101与射频装置1102连接。在上行方向上，射频装置1102通过天线1101接收信息，将接收的信息发送给基带装置1103进行处理。在下行方向上，基带装置1103对要发送的信息进行处理，并发送给射频装置1102，射频装置1102对收到的信息进行处理后经过天线1101发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置1103中实现，该基带装置1103包括基带处理器。
基带装置1103例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图11所示，其中一个芯片例如为基带处理器，通过总线接口与存储器1105连接，以调用存储器1105中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口1106，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备1100还包括：存储在存储器1105上并可在处理器1104上运行的指令或程序，处理器1104调用存储器1105中的指令或程序执行图8所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述BWP控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述BWP控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述BWP控制方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的BWP控制方法的步骤，所述网络侧设备可用于执行如上所述的BWP控制方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (30)

  1. 一种BWP控制方法，包括：
    在终端满足第一条件的情况下，所述终端调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
    检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；
    在LP-WUS监听期间需要进行上行传输。
  2. 根据权利要求1所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    在所述终端在非连续接收DRX非激活时间监听LP-WUS的情况下，若终端满足第一条件，则所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  3. 根据权利要求1或2所述的方法，其中，所述终端调整第一BWP的bwp-inactivityTimer，包括：
    所述终端开启或者重新开启或者停止第一BWP的bwp-inactivityTimer。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述第一条件包括所述终端检测到所述LP-WUS；
    所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    在检测到的所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一指示信息用于指示如下任一项：
    所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
    所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
    存在对所述终端的数据调度；
    调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    若所述终端满足第二条件，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第二条件包括如下至少之一：
    所述终端为数据传输量大于或等于第一阈值的终端类型；
    所述终端为数据吞吐率大于或等于第二阈值的终端类型；
    所述终端为数据传输时延小于或等于第三阈值的终端类型；
    所述终端对数据传输量要求高于或等于第四阈值；
    所述终端对数据吞吐率要求高于或等于第五阈值；
    所述终端对数据传输时延要求高于或等于第六阈值；
    所述终端支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
  6. 根据权利要求1至5中任一项所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    若所述终端从网络侧设备接收到第二指示信息，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第二指示信息用于指示如下至少一项：
    允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
    所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  7. 根据权利要求1至6中任一项所述的方法，其中，所述方法还包括：
    所述终端上报第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量的要求，所述终端对数据吞吐率的要求，所述终端对数据传输时延的要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer，或者所述能力信息用于指示所述终端支持或不支持根据LP-WUS进行BWP切换。
  8. 根据权利要求6或7所述的方法，其中，所述在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换之前，所述方法还包括：
    在所述终端从所述网络侧设备接收到更新的第二指示信息的情况下，所述终端调整第一BWP的bwp-inactivityTimer。
  9. 根据权利要求1至8中任一项所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    在所述终端检测到LP-WUS且所述LP-WUS包括BWP相关信息的情况下，所述终端根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换。
  10. 根据权利要求9所述的方法，其中，所述BWP相关信息包括BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
  11. 根据权利要求9或10所述的方法，其中，所述终端根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换，包括如下至少一项：
    在第二BWP与所述第一BWP相同的情况下，所述终端调整所述第一BWP的bwp-inactivityTimer；
    在第二BWP与所述第一BWP不相同的情况下，所述终端进行BWP切换；
    其中，所述第二BWP为根据所述BWP相关信息确定的BWP。
  12. 根据权利要求11所述的方法，其中，所述在第二BWP与所述第一BWP不相同的情况下，所述终端进行BWP切换，包括如下至少一项：
    在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP不为默认BWP或初始BWP，则所述终端去激活所述第一BWP，激活所述第二BWP，并在激活所述第二BWP的情况下启动所述第二BWP的bwp-inactivityTimer；
    在所述第二BWP与所述第一BWP不相同的情况下，若所述第二BWP为默认BWP或初始BWP，则所述终端去激活所述第一BWP，并激活所述第二BWP。
  13. 根据权利要求1至12中任一项所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一带宽部分BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    若所述终端处于单连接状态、或者所述终端仅配置了特殊小区SpCell，则在所述终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  14. 根据权利要求13所述的方法，其中，所述方法还包括如下至少一项：
    在所述终端由单连接状态切换至CA状态、或者所述终端添加了辅小区Scell的情况下，所述终端去激活第一操作；
    在所述终端由CA状态切换至单连接状态、或者所述终端恢复为仅配置SpCell的情况下，所述终端激活第一操作；
    其中，所述第一操作为：在所述终端满足第一条件的情况下所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  15. 根据权利要求1至12中任一项所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    若所述终端处于载波聚合CA状态、或者所述终端配置了SpCell和SCell，则在所述终端满足第一条件的情况下，所述终端调整第一小区的第一BWP的bwp-inactivityTimer或者对第一小区进行BWP切换；
    其中，所述第一小区包括如下任一项：
    SpCell；
    检测到的LP-WUS关联的小区组中存在数据传输的小区；
    网络侧设备配置或预配置的小区；
    检测到的LP-WUS指示的小区。
  16. 根据权利要求1至15中任一项所述的方法，其中，所述在终端满足第一条件的情况下，所述终端调整第一BWP的bwp-inactivityTimer或者进行BWP切换，包括：
    在所述终端处于双连接DC状态的情况下，若所述终端检测到LP-WUS，则所述终端的第一MAC实体根据第一小区组关联的LP-WUS，调整所述第一小区组的第一BWP的bwp-inactivityTimer或对所述第一小区组进行BWP切换；
    其中，所述第一小区组为主小区组MCG或辅小区组SCG，所述第一MAC实体为所述第一小区组关联的MAC实体。
  17. 一种BWP控制方法，包括：
    网络侧设备执行第二操作，所述第二操作包括如下至少一项：
    向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括BWP相关信息；
    从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
    向终端发送第二指示信息；
    其中，所述第一指示信息用于指示如下任一项：
    所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
    所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
    存在对所述终端的数据调度；
    调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第二指示信息用于指示如下至少一项：
    允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
    所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一BWP为处于激活状态的BWP。
  18. 根据权利要求17所述的方法，其中，所述BWP相关信息BWP索引，所述BWP索引用于指示所述终端在收到所述LP-WUS的情况下，在所述BWP索引指示的BWP上去监听PDCCH。
  19. 根据权利要求17或18所述的方法，其中，所述方法还包括：
    所述网络侧设备根据所述第一信息，确定是否向所述终端发送所述第二指示信息或者更新的第二指示信息。
  20. 一种BWP控制装置，包括：
    处理模块，用于在终端满足第一条件的情况下，调整第一带宽部分BWP的BWP非激活定时器bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一BWP为处于激活状态的BWP，所述第一条件包括如下至少一项：
    检测到低功耗唤醒信号LP-WUS，所述LP-WUS用于触发所述终端监听物理下行控制信道PDCCH；
    在LP-WUS监听期间需要进行上行传输。
  21. 根据权利要求20所述的装置，其中，所述第一条件包括所述终端检测到所述LP-WUS；
    所述处理模块具体用于：
    在检测到的所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一指示信息用于指示如下任一项：
    所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
    所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
    存在对所述终端的数据调度；
    调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  22. 根据权利要求20或21所述的装置，其中，所述处理模块具体用于：
    若所述终端满足第二条件，则在所述终端满足第一条件的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第二条件包括如下至少之一：
    所述终端为数据传输量大于或等于第一阈值的终端类型；
    所述终端为数据吞吐率大于或等于第二阈值的终端类型；
    所述终端为数据传输时延小于或等于第三阈值的终端类型；
    所述终端对数据传输量要求高于或等于第四阈值；
    所述终端对数据吞吐率要求高于或等于第五阈值；
    所述终端对数据传输时延要求高于或等于第六阈值；
    所述终端支持根据LP-WUS调整bwp-inactivityTimer或者支持根据LP-WUS进行BWP切换。
  23. 根据权利要求20至22中任一项所述的装置，其中，所述处理模块具体用于：
    若从网络侧设备接收到第二指示信息，则在所述终端满足第一条件的情况下，调整第一BWP的bwp-inactivityTimer；
    其中，所述第二指示信息用于指示如下至少一项：
    允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
    所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换。
  24. 根据权利要求20至23中任一项所述的装置，其中，所述装置还包括：
    发送模块，用于上报第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量的要求，所述终端对数据吞吐率的要求，所述终端对数据传输时延的要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer，或者所述能力信息用于指示所述终端支持或不支持根据LP-WUS进行BWP切换。
  25. 根据权利要求20至24中任一项所述的装置，其中，所述处理模块具体用于：
    在所述终端检测到LP-WUS且所述LP-WUS包括BWP相关信息的情况下，根据所述BWP相关信息调整第一BWP的bwp-inactivityTimer或进行BWP切换。
  26. 一种BWP控制装置，包括：
    处理模块，用于执行第二操作，所述第二操作包括如下至少一项：
    向终端发送低功耗唤醒信号LP-WUS，所述LP-WUS包括第一指示信息或所述LP-WUS的类型为与第一指示信息相关的LP-WUS类型，和/或，所述LP-WUS包括带宽部分BWP相关信息；
    从终端接收第一信息，所述第一信息包括如下至少一项：所述终端的类型，所述终端对数据传输量要求，所述终端对数据吞吐率要求，所述终端对数据传输时延要求，所述终端的能力信息；所述能力信息用于指示所述终端支持或不支持根据LP-WUS调整bwp-inactivityTimer；
    向终端发送第二指示信息；
    其中，所述第一指示信息用于指示如下任一项：
    所述LP-WUS用于触发所述终端接收包含下行分配或上行授权信息的PDCCH；
    所述LP-WUS用于触发所述终端接收包含多播配置相关的下行分配信息的PDCCH；
    存在对所述终端的数据调度；
    调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第二指示信息用于指示如下至少一项：
    允许所述终端根据LP-WUS调整bwp-inactivityTimer或者允许所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持保证所述终端的数据传输吞吐率和数据传输时延中的至少一项；
    所述终端在检测到触发所述终端监听PDCCH的LP-WUS的情况下，调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    所述终端的服务小区支持所述终端根据LP-WUS调整bwp-inactivityTimer或者支持所述终端根据LP-WUS进行BWP切换；
    所述终端的服务小区支持在所述终端检测到触发所述终端监听PDCCH的LP-WUS的情况下调整第一BWP的bwp-inactivityTimer或者进行BWP切换；
    其中，所述第一BWP为处于激活状态的BWP。
  27. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至16任一项所述的BWP控制方法的步骤。
  28. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求17至19任一项所述的BWP控制方法的步骤。
  29. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至16任一项所述的BWP控制方法的步骤，或者实现权利要求17至19任一项所述的BWP控制方法的步骤。
  30. 一种计算机程序产品，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至16任一项所述的BWP控制方法的步骤，或者实现权利要求17至19任一项所述的BWP控制方法的步骤。
PCT/CN2025/111810 2024-08-01 2025-07-31 Bwp控制方法、装置、终端及网络侧设备 Pending WO2026026913A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202411051972.3 2024-08-01
CN202411051972.3A CN121463241A (zh) 2024-08-01 2024-08-01 Bwp控制方法、装置、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2026026913A1 true WO2026026913A1 (zh) 2026-02-05

Family

ID=98581902

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/111810 Pending WO2026026913A1 (zh) 2024-08-01 2025-07-31 Bwp控制方法、装置、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN121463241A (zh)
WO (1) WO2026026913A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109496454A (zh) * 2018-10-17 2019-03-19 北京小米移动软件有限公司 带宽部分切换方法及装置
CN111212448A (zh) * 2018-11-21 2020-05-29 中国移动通信集团山东有限公司 一种bwp自适应选择调制方法及系统
WO2020243933A1 (zh) * 2019-06-05 2020-12-10 Oppo广东移动通信有限公司 一种工作带宽切换方法、用户设备及网络设备
WO2021155592A1 (zh) * 2020-02-07 2021-08-12 Oppo广东移动通信有限公司 带宽部分bwp的处理方法、设备及存储介质
CN114424658A (zh) * 2019-09-27 2022-04-29 高通股份有限公司 用于能力降低的用户设备的物理下行链路共享信道资源
US20220182940A1 (en) * 2019-11-12 2022-06-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Discontinuous reception processing method, and terminal device
WO2023115353A1 (zh) * 2021-12-21 2023-06-29 Oppo广东移动通信有限公司 Bwp切换方法、装置、设备及存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109496454A (zh) * 2018-10-17 2019-03-19 北京小米移动软件有限公司 带宽部分切换方法及装置
CN111212448A (zh) * 2018-11-21 2020-05-29 中国移动通信集团山东有限公司 一种bwp自适应选择调制方法及系统
WO2020243933A1 (zh) * 2019-06-05 2020-12-10 Oppo广东移动通信有限公司 一种工作带宽切换方法、用户设备及网络设备
CN114424658A (zh) * 2019-09-27 2022-04-29 高通股份有限公司 用于能力降低的用户设备的物理下行链路共享信道资源
US20220182940A1 (en) * 2019-11-12 2022-06-09 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Discontinuous reception processing method, and terminal device
WO2021155592A1 (zh) * 2020-02-07 2021-08-12 Oppo广东移动通信有限公司 带宽部分bwp的处理方法、设备及存储介质
WO2023115353A1 (zh) * 2021-12-21 2023-06-29 Oppo广东移动通信有限公司 Bwp切换方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN121463241A (zh) 2026-02-03

Similar Documents

Publication Publication Date Title
US20210076450A1 (en) Data service processing method, network side device, terminal device, and storage medium
WO2023138510A1 (zh) 配置确定方法、装置、终端及网络侧设备
WO2023160604A1 (zh) 非连接态终端的确定方法、终端及网络侧设备
US20260019994A1 (en) Paging method and communication device
US20230336968A1 (en) Method for controlling secondary cell group, terminal, and network-side device
US20250358895A1 (en) Transmission processing method, transmission processing apparatus, terminal, and network-side device
WO2026026913A1 (zh) Bwp控制方法、装置、终端及网络侧设备
CN117082600A (zh) 小区处理方法、网络侧设备及可读存储介质
WO2026016988A1 (zh) 传输处理方法、装置、终端及网络侧设备
US20260075530A1 (en) Assistance information sending method and receiving method, terminal, and network side device
WO2026012216A1 (zh) 节能方法、装置、终端及网络侧设备
WO2026032159A1 (zh) Lp-wus的配置方法、终端及网络侧设备
US20260129583A1 (en) Low-power wake-up signal indication methods and apparatuses, device and readable storage medium
WO2025055861A1 (zh) 连接态非连续接收的配置方法、终端及网络侧设备
WO2025241964A1 (zh) 通信模式确定方法、装置、ue及网络侧设备
CN119676806A (zh) 通信处理方法、装置、设备及可读存储介质
WO2026067366A1 (zh) 控制信息的传输方法、终端及网络侧设备
WO2026056750A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2024208124A1 (zh) 通信方法、装置、终端、无线接入网设备及核心网设备
WO2024250996A1 (zh) 寻呼处理方法、装置、终端及网络侧设备
WO2026026888A1 (zh) 唤醒信号监听处理方法、装置及终端
WO2025232708A1 (zh) 信号监听方法、信号发送方法、装置、终端及网络侧设备
WO2025011424A1 (zh) Pdcch监听方法、信息发送方法、装置及设备
WO2025087134A1 (zh) 监听处理方法、装置、终端及网络侧设备
CN119300124A (zh) 传输处理方法、装置、终端及网络侧设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25847364

Country of ref document: EP

Kind code of ref document: A1