Patent Description:
Discontinuous reception (Discontinuous Reception, DRX) means: A user terminal (User Equipment, terminal device) periodically enters a sleep state at some time, and does not monitor a physical downlink control channel (Physical Downlink Control Channel, PDCCH) subframe in the sleep state. When needing to monitor the PDCCH subframe, the terminal device is woken up from the sleep state. Therefore, power of the terminal device is saved.

A bandwidth of a <NUM> new radio (<NUM> NeW Radio, <NUM> NR) system can reach a maximum of <NUM>. If all terminal devices are required to support the maximum of <NUM>, a high requirement is imposed on performance of the terminal device. This is adverse to reducing costs of the terminal device. Therefore, a bandwidth adaptation (Bandwidth Adaptation, BA) technology is introduced in <NUM> NR, so that a bandwidth of a BWP of a terminal device may be different from a bandwidth of a serving cell of the terminal device and may be adjusted. In a conventional technology, the BA technology is used by a terminal device to first detect, in a DRX cycle and in a narrowband BWP, whether wake up signaling (Wake Up Signaling, WUS) is received. If the WUS is received, the terminal device switches to a BWP with a higher bandwidth for data sending/receiving. After completing the data sending/receiving, the terminal device switches back to the narrowband BWP used to detect the WUS. If no WUS is detected, the terminal device remains in a sleep state, and is not woken up.

However, the manner in the conventional technology causes unnecessary overheads and power consumption of the terminal device. United States patent application <CIT> describes various examples of a method, an apparatus, and a computer readable medium for multi-state discontinuous reception (DRX) in wireless communications. For example, one of the methods described may include identifying, by a user equipment (UE), at least two states in connected mode, determining, by the UE, one or more triggers for transitioning between the at least two states, and transitioning, by the UE, from a first state of the at least two states to a second state of the at least two states in response to a determination of the one or more triggers. In an aspect, the transitioning comprises transitioning between cross-slot scheduling and same-slot scheduling, or between a narrow bandwidth and a wide bandwidth, or between a larger periodicity and a smaller periodicity for monitoring. <NPL>, considers two basic questions related to UE power consumption adaptation: What conditions cause the system to change the power state of the UE? and What is the general procedure for changing the UE power state?
<NPL>, has the following observation: associating BWP adaptation framework with DRX operation can be leveraged for further power saving. International patent application <CIT> describes techniques for improved WUS operation in a wireless communication system. <NPL>, makes the following proposals: NR supports wake-up signaling (WUS) in C-DRX for UE power saving; WUS is supported by the method of advanced grant indication, which is special DCI that tells UE whether a grant should be expected in the upcoming DRX on duration; based on the advanced grant indication, if a grant should be expected, UE wakes up to perform regular DRX on-duration procedure; otherwise, it goes back to sleep without performing DRX on-duration procedures; and network can configure, activate and deactivate advanced grant indication either on a per UE basis or on a per group basis.

This application provides two BWP adjustment methods and corresponding apparatuses and computer-readable storage mediums, to reduce unnecessary overheads and power consumption of a terminal device.

<FIG> is an architectural diagram of an application system according to this application. Technical solutions of this application are applied to a <NUM> system. The <NUM> system is also referred to as a new radio communications system, a new access technology (New Radio, NR) system, or a next-generation mobile communications system. A base station gNB/NG-eNB of a serving cell of a terminal device is responsible for providing <NUM> NR user plane and control plane protocol functions for the terminal device.

An access network in the <NUM> system may be a radio access network (radio access network, (R)AN), and an (R)AN device in the <NUM> system may include a plurality of <NUM>-(R)AN nodes. The <NUM>-(R)AN nodes may include an access point (access point, AP) in a non-3GPP access network such as a Wi-Fi network, and a next generation NodeB (which may be collectively referred to as a next generation radio access network node (NG-RAN node)). The next generation NodeB includes a new radio NodeB (NR NodeB, gNB), a next generation evolved NodeB (NG-eNB), a gNB in which a central unit (central unit, CU) is separated from a distributed unit (distributed unit, DU), a transmission reception point (transmission receive point, TRP), a transmission point (transmission point, TP), or another node.

As shown in <FIG>, a <NUM> core/next generation core network (<NUM> core/new generation core, 5GC/NGC) includes a plurality of function units such as an access and mobility management function (Access and Mobility Management Function, AMF) network element, a session management function (Session Management Function, SMF) network element, a user plane function (User Plane Function, UPF) network element, an authentication server function (Authentication Server Function, AUSF) network element, a policy control function (Policy Control Function, PCF) network element, an application function (Application Function, AF) network element, a unified data management (unified data management, UDM) network element, and a network slice selection function (Network Slice Selection Function, NSSF) network element.

The AMF network element is mainly responsible for services such as mobility management and access management. The SMF network element is mainly responsible for session management, address management and assignment of a terminal device, a dynamic host configuration protocol function, selection and control of a user plane function, and the like. The UPF is mainly responsible for functions related to external connection to a data network (data network, DN), user plane data packet routing and forwarding, packet filtering, quality of service (quality of service, QoS) control, and the like. The AUSF is mainly responsible for an authentication function of the terminal device, and the like. The PCF network element is mainly responsible for providing a unified policy framework for network behavior management, providing a policy rule of a control plane function, obtaining registration information related to a policy decision, and so on. It should be noted that these function units may work independently, or may be combined together to implement some control functions, for example, access control and mobility management functions such as access authentication, security encryption, and location registration of the terminal device, and session management functions such as establishment, release, and change of a user plane transmission path.

The function units in the 5GC may communicate with each other through a next generation (next generation, NG) network interface. For example, the terminal device may transmit a control plane message with the AMF network element through an NG interface <NUM> (N1 for short). The RAN device may establish a user plane data transmission channel with the UPF through an NG interface <NUM> (N3 for short). The AN/RAN device may establish a control plane signaling connection to the AMF network element through an NG interface <NUM> (N2 for short). The UPF may exchange information with the SMF network element through an NG interface <NUM> (N4 for short). The UPF may exchange user plane data with the data network DN through an NG interface <NUM> (N6 for short). The AMF network element may exchange information with the SMF network element through an NG interface <NUM> (N11 for short). The SMF network element may exchange information with the PCF network element through an NG interface <NUM> (N7 for short). The AMF network element may exchange information with the AUSF through an NG interface <NUM> (N12 for short). It should be noted that <FIG> is merely an architectural diagram used an example. The network architecture may further include another function unit in addition to the function units shown in <FIG>.

In this application, a network side device sends indication information to a terminal device, to indicate an operating BWP to be used by the terminal device to receive and/or send data, so that the operating BWP of the terminal device can be dynamically adjusted based on a size of a data volume of data to be actually received and/or sent. Because the operating BWP of the terminal device is more appropriate, unnecessary overheads and power consumption can be reduced. The operating BWP is a BWP used for data transmission.

The following describes the technical solutions of this application by using several specific embodiments. For same or similar descriptions, refer to each other. Details are not described in this application one by one.

<FIG> is a schematic flowchart of an embodiment of a BWP adjustment method according to the claimed invention. As shown in <FIG>, the method in this embodiment is as follows:
S201: A network side device sends first indication information to a terminal device in a first BWP.

The first indication information is used to indicate information about a second BWP to be used by the terminal device to receive and/or send data, and is used to indicate the terminal device to enter a sleep state or a wake-up state.

The network side device may determine the second BWP based on a size of a data volume of data to be received and/or sent.

The first BWP may be the same as or different from the second BWP. This is not limited in this application.

The first BWP may be a fixed BWP and specially used to send/receive the first indication information, and is usually a narrowband BWP. In this case, the first BWP is different from the second BWP, and a bandwidth of the second BWP is higher than the bandwidth of the second BWP.

Alternatively, the first BWP may be a BWP that may be used both to receive and/or send data and to send/receive the first indication information. In this case, the first BWP may be the same as or different from the second BWP. This is not limited in this application.

An implementation in which the network side device sends the first indication information to the terminal device in the first BWP includes but is not limited to the following implementations:.

The network side device sends a go to sleep (Go To Sleep, GTS) signal to the terminal device in the first BWP, where the GTS signal includes the information about the second BWP.

The GTS is a signal that may be sent to the terminal device when DRX is configured for the terminal device. The signal enables the terminal device to switch from an active state to the sleep state in a DRX cycle and in a serving cell of the terminal device.

In another possible implementation,
the network side device sends WUS to the terminal device in the first BWP, where the WUS includes the information about the second BWP.

The WUS is a signal that may be sent to the terminal device when DRX is configured for the terminal device. In a DRX cycle, the terminal device first detects the signal. If the signal is detected, the terminal device is woken up when on duration (On Duration) of the DRX cycle arrives, and enters an active state.

S202: The terminal device receives and/or sends the data in the second BWP.

After receiving the first indication information, the terminal device obtains the second BWP indicated by using the first indication information.

If the second BWP is the same as the first BWP, an operating BWP is not switched, and the data is received and/or sent in the second BWP when the terminal device is in the active state.

If the second BWP is different from the first BWP, an operating BWP is switched from the first BWP to the second BWP, and the data is received and/or sent in the second BWP when the terminal device is in the active state.

The network side device sends the indication information to the terminal device, to indicate that the operating BWP to be used by the terminal device to receive and/or send the data is the second BWP, so as to dynamically adjust the operating BWP of the terminal device. A BWP for receiving and/or sending data may be determined based on a data volume of data to be actually received and/or sent. Therefore, the operating BWP of the terminal device is more appropriate. In this way, unnecessary overheads and power consumption can be reduced.

<FIG> is a schematic flowchart of another embodiment of a BWP adjustment method according to this application. <FIG> is based on the embodiment shown in <FIG>, and optionally, before step S201, the method may further include the following step:
S200: The network side device sends BWP configuration information to the terminal device.

Optionally, the network side device may send RRC signaling to the terminal device, and include the BWP configuration information in the RRC signaling.

In a possible implementation, the BWP configuration information includes configuration information of an active BWP, an initial BWP, and a default BWP.

The second BWP is the active BWP, the initial BWP, or the default BWP.

In another possible implementation, the BWP configuration information includes at least two sets of BWP configuration information, and the at least two sets of BWP configuration information may be customized by a base station.

The second BWP is a BWP corresponding to one of the at least two sets of BWP configuration information that are included in the BWP configuration information.

Optionally, in a possible implementation, same common DRX configuration information is used for all the sets of BWP configuration information. The common DRX configuration information may be agreed upon, and does not need to be configured by the network side device when the network side device configures the BWP configuration information for the terminal device.

In another possible implementation, alternatively, RRC signaling may include DRX configuration information corresponding to the at least two sets of BWP configuration information. The DRX configuration information includes but is not limited to a specific DRX on duration timer, a DRX static timer parameter, a DRX uplink retransmission timer parameter, a DRX downlink retransmission timer parameter, or the like. This is not limited in this application.

Different BWP configuration information may correspond to same or different DRX configuration information. This is not limited in this application.

Optionally, the network side device may further send BWP reconfiguration information to the terminal device, to update the at least two sets of BWP configuration information.

S201: The network side device sends the first indication information to the terminal device in the first BWP.

For detailed descriptions of steps S201 and S202, refer to the embodiment shown in <FIG>.

In this application, the network side device sends the BWP configuration information to the terminal device. The network side device may dynamically select a second BWP from the BWP configuration information based on a size of a data volume of data to be actually received and/or sent, and send the first indication information to the terminal device, to indicate the second BWP to be used by the terminal device to receive and/or send the data. Because the operating BWP of the terminal device is more appropriate, unnecessary overheads and power consumption can be reduced.

A GTS signal-based DRX mechanism scenario and a WUS-based DRX mechanism scenario are mainly considered in this application, but this application is not limited to the foregoing two scenarios. The following provides descriptions separately for the two scenarios.

<FIG> are for the GTS signal-based DRX mechanism scenario.

<FIG> is a schematic flowchart of still another embodiment of a BWP adjustment method according to the claimed invention. This embodiment is as follows:
S401: A network side device sends a GTS signal to a terminal device in a first BWP.

The GTS signal includes information about the second BWP.

Optionally, in a possible implementation, the GTS signal is downlink control information DCI, the DCI includes a bandwidth indication field, and the bandwidth indication field is used to indicate the second BWP. After receiving the GTS signal, the terminal device determines, based on the bandwidth indication field, that the second BWP indicated by using the field is an operating BWP for receiving and/or sending data.

In another possible implementation, the GTS signal is a sequence-based signal, and the sequence-based signal corresponds to the second BWP. Different sequence codes correspond to different BWP configuration information. Therefore, after receiving the GTS signal, the terminal device may determine, based on a correspondence between a sequence code of a GTS signal and BWP configuration information, that the second BWP corresponding to a sequence code of the GTS signal is an operating BWP for receiving and/or sending data.

S402: The terminal device determines whether the first BWP is the same as the second BWP.

If the first BWP is the same as the second BWP, perform step S403. If the first BWP is different from the second BWP, perform step S404.

S403: The terminal device controls the terminal device to enter a sleep state, and maintains the first BWP as the operating BWP.

S404: The terminal device controls the terminal device to enter a sleep state, and switches the operating BWP from the first BWP to the second BWP.

The terminal device controls the terminal device to enter the sleep state, and switches the operating BWP from the first BWP to the second BWP in the sleep state.

S405: The terminal device receives and/or sends the data in the second BWP.

The network side device sends the GTS signal to the terminal device in the first BWP. The terminal device determines, depending on whether the first BWP is the same as the second BWP, whether to switch the operating BWP in the sleep state. Because the terminal device switches the operating BWP in the sleep state, the terminal device may send/receive the data in the second BWP immediately after being woken up, and does not need to switch the operating BWP by occupying a time period in which the terminal device is in an active state. In this way, unnecessary power consumption and overheads are further reduced.

The following uses two examples to describe the technical solution shown in <FIG>. As shown in <FIG> is a schematic diagram of a GTS signal-based DRX mechanism scenario according to this application.

<FIG> is a schematic diagram of another GTS signal-based DRX mechanism scenario according to this application. In <FIG>, the second BWP is an active BWP, an initial BWP, or a default BWP. As shown in <FIG>:.

<FIG> are for the WUS-based DRX mechanism scenario.

<FIG> is a schematic flowchart of yet another embodiment of a BWP adjustment method according to this application. This embodiment is as follows:
S701: A network side device sends WUS to a terminal device in a first BWP.

The WUS includes information about the second BWP.

The first BWP may be a fixed BWP and specially used to send/receive the WUS, and is usually a narrowband BWP. The second BWP is used to receive and/or send data, and a bandwidth of the second BWP is higher than the bandwidth of the second BWP.

Optionally, in a possible implementation,
the WUS is a sequence-based signal, and the sequence-based signal corresponds to the second BWP. Different sequence codes correspond to different BWP configuration information. Therefore, after receiving the WUS, the terminal device may determine, based on a correspondence between a sequence code of WUS and BWP configuration information, that the second BWP corresponding to a sequence code of the WUS is an operating BWP for receiving and/or sending the data.

S702: The terminal device determines that the terminal device is to enter an active state, and switches the operating BWP from the first BWP to the second BWP.

Optionally, the terminal device switches the operating BWP from the first BWP to the second BWP before determining that the terminal device is to enter the active state.

S703: The terminal device receives and/or sends the data in the second BWP.

S704: The terminal device determines that the active state of the terminal device ends, and switches the operating BWP from the second BWP to the first BWP.

Optionally, the terminal device switches the operating BWP from the second BWP to the first BWP after the active state of ends.

In this embodiment, the network side device sends the WUS to the terminal device in the first BWP. The terminal device switches the operating BWP before entering the active state, and switches the operating BWP from the second BWP to the first BWP after the active state ends. In this way, the terminal device may send/receive the data in the second BWP immediately after being woken up, and does not need to switch the operating BWP by occupying a time period in which the terminal device is in the active state. Therefore, unnecessary power consumption and overheads are further reduced.

<FIG> is a schematic flowchart of yet another embodiment of a BWP adjustment method according to this application. This embodiment is as follows:
S801: A network side device sends WUS to a terminal device in a first BWP.

The first BWP may be a BWP that may be used both to receive and/or send data and to send/receive first indication information. In this case, the first BWP may be the same as or different from the second BWP. This is not limited in this application.

S802: The terminal device determines whether the first BWP is the same as the second BWP.

If the first BWP is the same as the second BWP, perform step S803. If the first BWP is different from the second BWP, perform step S804.

S803: The terminal device maintains the first BWP as the operating BWP.

S804: The terminal device switches the operating BWP from the first BWP to the second BWP before the terminal device enters an active state.

S805: The terminal device receives and/or sends the data in the second BWP.

S806: After the active state ends, the terminal device determines whether a quantity of times for which the terminal device switches from the first BWP to the second BWP is greater than a preset threshold. If yes, perform step S807. If no, perform step S808.

S807: The terminal device maintains the second BWP as the operating BWP.

S808: Switch the operating BWP from the second BWP to the first BWP.

In this embodiment, the network side device sends the WUS to the terminal device in the first BWP. The terminal device determines, depending on whether the first BWP is the same as the second BWP, whether to switch the operating BWP before entering the active state. Because the terminal device switches the operating BWP before entering the active state, the terminal device may send/receive the data in the second BWP immediately after being woken up, and does not need to switch the operating BWP by occupying a time period in which the terminal device is in the active state. In this way, unnecessary power consumption and overheads are further reduced. In addition, if the quantity of times for which the terminal device switches from the first BWP to the second BWP is greater than the preset threshold, the terminal device maintains the second BWP as the operating BWP after the active state of the terminal device ends. Therefore, a quantity of BWP switching times is reduced, and the power consumption and overheads are further reduced.

The following uses two examples to describe the solution shown in <FIG>.

<FIG> is a schematic diagram of a WUS-based DRX mechanism scenario according to this application. As shown in <FIG>:.

<FIG> is a schematic diagram of another WUS-based DRX mechanism scenario according to this application. As shown in <FIG>:.

The following uses an example to describe the solution shown in <FIG>. As shown in <FIG> is a schematic diagram of still another WUS-based DRX mechanism scenario according to this application.

This application further provides an embodiment of a method for determining a monitoring time of WUS. A monitoring time of WUS is determined based on a start moment of an on duration timer, so that a range of the monitoring time of the WUS is smaller and more effective, so as to further reduce power consumption and overheads.

<FIG> are schematic diagrams showing embodiments of determining a monitoring time of WUS.

<FIG> shows a DRX mechanism in a conventional technology. Ton-duration is an on duration start point obtained by using an on duration start point-related calculation formula in an existing DRX mechanism. Δslot-offset is a slot offset (Slot Offset) indicated by a DRX slot offset parameter (drx-SlotOffset) in DRX. In this case, a start moment of a DRX on duration timer is represented as Tstart = Ton-duration + Δslot-offset.

It is assumed that an offset between a monitoring moment TWUS of WUS and the start moment Tstart of the DRX on duration timer is ΔWUS-offset , and the terminal device determines, based on the offset, the moment or a time period of monitoring the WUS.

The monitoring time of the WUS includes but is not limited to the following several possible cases:
In a possible implementation, the monitoring time of the WUS is determined based on the start moment of the on duration timer and a first offset.

The first offset is an offset between a sending moment of the WUS and the start moment of the on duration timer.

Specifically, the start moment of the on duration timer is determined according to Tstart = Ton-duration + Δslot-offset.

The monitoring time of the WUS is determined according to TWUS = Tstart ± ΔWUS-offset. As shown in <FIG>, TWUS is a reference point of the monitoring time of the WUS, Tstart is the start moment of the on duration timer, and ΔWUS-offset is the first offset. The monitoring time of the WUS is the moment TWUS or a time period including the moment TWUS, and the time period including the moment TWUS may be a time period starting from TWUS, or may be a time period starting from a moment that is before TWUS and ending at a moment that is after TWUS.

In another possible implementation, the monitoring time of the WUS is determined based on a start moment of on duration, a second offset, and the first offset, where the second offset is a slot offset of discontinuous reception DRX.

Specifically, the monitoring time of the WUS is determined according to TWUS = Ton-duration + Δslot-offset ± ΔWUS-offset. As shown in <FIG>:
TWUS is a reference point of the monitoring time of the WUS, Ton-duration is the start moment of the on duration, Δslot-offset is the second offset, and ΔWUS-offset is the first offset. The monitoring time of the WUS is the moment TWUS or a time period including the moment TWUS, and the time period including the moment TWUS may be a time period starting from TWUS, or may be a time period starting from a moment that is before TWUS and ending at a moment that is after TWUS.

In still another possible implementation, the start moment of the on duration timer is determined as the monitoring time of the WUS.

That is, TWUS =Tstart. As shown in <FIG>, TWUS is a reference point of the monitoring time of the WUS, and Tstart is the start moment of the on duration timer. The monitoring time of the WUS is the moment TWUS or a time period including the moment TWUS, and the time period including the moment TWUS may be a time period starting from TWUS, or may be a time period starting from a moment that is before TWUS and ending at a moment that is after TWUS.

The start moment of the on duration timer may be determined based on a start moment of on duration and a second offset. Specifically, the start moment of the on duration timer is determined according to Tstart = Ton-duration + Δslot-offset.

In yet another possible implementation, the monitoring time of the WUS is determined based on a start moment of on duration and a second offset. Specifically, the monitoring time of the WUS is determined according to TWUS = Ton-duration + Δslot-offset. As shown in <FIG>, the monitoring time of the WUS is the moment TWUS or a time period including the moment TWUS, and the time period including the moment TWUS may be a time period starting from TWUS, or may be a time period starting from a moment that is before TWUS and ending at a moment that is after TWUS.

In yet another possible implementation, the start moment of the on duration timer is determined based on a start moment of on duration and a second offset, and a time period from the start moment of the on duration to the start moment of the on duration timer is determined as the monitoring time of the WUS. As shown in <FIG>, a time period corresponding to Δslot-offset is the monitoring time of the WUS.

In yet another possible implementation, the start moment of the on duration timer is determined based on a start moment of on duration and a second offset, and a time period that corresponds to the second offset and that is before the start moment of the on duration timer is determined as the monitoring time of the WUS. As shown in <FIG>, a time period corresponding to Δslot-offset is the monitoring time of the WUS.

In yet another possible implementation, a time period that corresponds to a second offset and that is after a start moment of on duration is determined as the monitoring time of the WUS. As shown in <FIG>, a time period corresponding to Δslot-offset is the monitoring time of the WUS.

<FIG> is a schematic structural diagram of an embodiment of a bandwidth part BWP adjustment apparatus according to this application. The apparatus in this embodiment includes a receiver <NUM> and a transmitter <NUM>. The receiver <NUM> is configured to receive, in a first BWP, first indication information sent by a network side device, where the first indication information is used to indicate information about a second BWP to be used by a terminal device to receive and/or send data, and is used to indicate the terminal device to enter a sleep state or a wake-up state.

The receiver <NUM> is further configured to receive the data in the second BWP, and/or the transmitter <NUM> is configured to send the data in the second BWP.

Optionally, the first indication information is a go to sleep GTS signal, and the GTS signal includes the information about the second BWP.

Optionally, if the first BWP is different from the second BWP,
the apparatus further includes:
a processor <NUM>, configured to control the terminal device to enter the sleep state, and switch an operating BWP from the first BWP to the second BWP.

Optionally, the processor <NUM> is specifically configured to control the terminal device to enter the sleep state, and switch the operating BWP from the first BWP to the second BWP in the sleep state.

Optionally, the GTS signal is downlink control information DCI, the DCI includes a bandwidth indication field, and the bandwidth indication field is used to indicate the information about the second BWP.

Optionally, the GTS signal is a sequence-based signal, and the sequence-based signal corresponds to the second BWP.

Optionally, the first indication information is wake up signaling WUS, and the WUS includes the information about the second BWP.

Optionally, if the first BWP is different from the second BWP,
the apparatus further includes:
a processor <NUM>, configured to: determine that the terminal device is to enter an active state, and switch an operating BWP from the first BWP to the second BWP; and determine that the active state of the terminal device ends, and switch the operating BWP from the second BWP to the first BWP.

Optionally, the processor <NUM> is specifically configured to switch the operating BWP from the first BWP to the second BWP before the terminal device enters the active state, and switch the operating BWP from the second BWP to the first BWP after the active state of the terminal device ends.

Optionally, the processor <NUM> is further configured to: if a quantity of times for which the terminal device switches from the first BWP to the second BWP is greater than a preset threshold, maintain, by the terminal device, the second BWP as the operating BWP after the active state of the terminal device ends.

Optionally, the WUS is a sequence-based signal, and the sequence-based signal corresponds to the second BWP.

Optionally, the receiver <NUM> is further configured to receive BWP configuration information sent by the network side device, where the BWP configuration information includes configuration information of an active BWP, an initial BWP, and a default BWP, and the second BWP is the active BWP, the initial BWP, or the default BWP.

Optionally, the receiver <NUM> is further configured to receive BWP configuration information sent by the network side device, where the BWP configuration information includes at least two sets of BWP configuration information, and the second BWP is a BWP corresponding to one of the at least two sets of BWP configuration information.

Optionally, the receiver <NUM> is further configured to receive radio resource control RRC signaling sent by the network side device, where the RRC signaling includes the BWP configuration information.

Optionally, the RRC signaling further includes DRX configuration information respectively corresponding to the at least two sets of BWP configuration information.

Optionally, the receiver <NUM> is further configured to receive BWP reconfiguration information sent by the network side device. The processor <NUM> is further configured to update the at least two sets of BWP configuration information based on the BWP reconfiguration information.

Optionally, the processor <NUM> is further configured to obtain a sending time of the WUS.

The transmitter <NUM> is further configured to receive, in the first BWP and at the sending time of the WUS, the wake up signaling WUS sent by the network side device.

The apparatus in this embodiment may be correspondingly configured to perform steps performed by the terminal device in the method embodiment shown in any one of <FIG>. Implementation principles and technical effects of the apparatus are similar to those in the method embodiment, and details are not described herein again.

<FIG> is a schematic structural diagram of another embodiment of a bandwidth part BWP adjustment apparatus according to this application. The apparatus in this embodiment includes a processor <NUM> and a transmitter <NUM>. The processor <NUM> is configured to determine a second BWP based on data to be received and/or sent by a terminal device. The transmitter is configured to send first indication information to the terminal device in a first BWP, where the first indication information is used to indicate information about the second BWP to be used by the terminal device to receive and/or send the data, and is used to indicate the terminal device to enter a sleep state or a wake-up state.

Optionally, the transmitter <NUM> is further configured to send BWP configuration information to the terminal device, where the BWP configuration information includes configuration information of an active BWP, an initial BWP, and a default BWP, and the second BWP is the active BWP, the initial BWP, or the default BWP.

Optionally, the transmitter <NUM> is further configured to send BWP configuration information to the terminal device, where the BWP configuration information includes at least two sets of BWP configuration information, and the second BWP is a BWP corresponding to one of the at least two sets of BWP configuration information.

Optionally, the transmitter <NUM> is specifically configured to send radio resource control RRC signaling to the terminal device, where the RRC signaling includes the BWP configuration information.

Optionally, the RRC signaling further includes DRX configuration information corresponding to the at least two sets of BWP configuration information.

The apparatus in this embodiment may be correspondingly configured to perform steps performed by the network device in the method embodiment shown in any one of <FIG>. Implementation principles and technical effects of the apparatus are similar to those in the method embodiment, and details are not described herein again.

This application further provides a schematic structural diagram of an embodiment of an apparatus for determining a monitoring time of wake up signaling WUS. As shown in <FIG>, a processor is configured to obtain a start moment of an on duration timer, and the processor is further configured to determine a monitoring time of the WUS based on the start moment of the on duration timer.

Optionally, the processor is specifically configured to determine the monitoring time of the WUS based on the start moment of the on duration timer and a first offset, where the first offset is an offset between a sending moment of the WUS and the start moment of the on duration timer.

Optionally, the processor is specifically configured to determine the monitoring time of the WUS based on a start moment of on duration, a second offset, and the first offset, where the second offset is a slot offset of discontinuous reception DRX.

Optionally, the processor is specifically configured to:.

Optionally, the processor is specifically configured to determine the start moment of the on duration timer as the monitoring time of the WUS.

Optionally, the processor is further configured to determine the start moment of the on duration timer based on a start moment of on duration and a second offset.

Optionally, the processor is specifically configured to determine the start moment of the on duration timer according to Tstart = Ton-duration + Δslot-offset , where
Ton-duration is the start moment of the on duration, Δslot-offset is the second offset, and Tstart is the start moment of the on duration timer.

Optionally, the processor is specifically configured to determine the monitoring time of the WUS based on a start moment of on duration and a second offset.

Optionally, the processor is specifically configured to determine the monitoring time of the WUS according to TWUS = Ton-duration + Δslot-offset , where
Ton-duration is the start moment of the on duration, Δslot-offset is the second offset, TWUS is a reference point of the monitoring time of the WUS, and the monitoring time of the WUS is the moment TWUS or a time period including the moment TWUS.

Optionally, the processor is specifically configured to: determine the start moment of the on duration timer based on a start moment of on duration and a second offset; and
determine a time period from the start moment of the on duration to the start moment of the on duration timer as the monitoring time of the WUS.

Optionally, the processor is specifically configured to: determine the start moment of the on duration timer based on a start moment of on duration and a second offset; and
determine, as the monitoring time of the WUS, a time period that corresponds to the second offset that is before the start moment of the on duration timer.

Optionally, the processor is specifically configured to determine, as the monitoring time of the WUS, a time period that corresponds to a second offset and that is after a start moment of on duration.

This application further provides a computer-readable storage medium, storing a computer program. When the program is executed by a processor, the bandwidth part BWP adjustment method shown in any one of <FIG> is implemented.

This application further provides a bandwidth part BWP adjustment apparatus, including a memory, a processor, and a program that is stored in the memory and that can run on the processor. When the processor executes the program, the bandwidth part BWP adjustment method shown in any one of <FIG> is implemented.

This application further provides an apparatus for determining a monitoring time of wake up signaling WUS, including a memory, a processor, and a program that is stored in the memory and that can run on the processor. When the processor executes the program, the bandwidth part BWP adjustment method shown in any one of <FIG> is implemented.

An embodiment of this application further provides a communication apparatus, and the communication apparatus may be a terminal device or a circuit. The communication apparatus may be configured to perform an action performed by the terminal device in the foregoing method embodiments.

When a BWP adjustment apparatus is a terminal device, <FIG> is a simplified schematic structural diagram of a terminal device. For ease of understanding and illustration, an example in which the terminal device is a mobile phone is used in <FIG>. As shown in <FIG>, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input/output apparatus. The processor is mainly configured to: process a communication protocol and communication data, control the terminal device, execute a software program, process data of the software program, and so on. The memory is mainly configured to store the software program and the data. The radio frequency circuit is mainly configured to: perform conversion between a baseband signal and a radio frequency signal, and process the radio frequency signal. The antenna is mainly configured to send and receive the radio frequency signal in an electromagnetic wave form. The input/output apparatus such as a touchscreen, a display, or a keyboard is mainly configured to receive data entered by a user and output data to the user. It should be noted that some types of terminal devices may have no input/output apparatus.

When data needs to be sent, the processor performs baseband processing on the to-be-sent data, and outputs a baseband signal to the radio frequency circuit. After performing radio frequency processing on the baseband signal, the radio frequency circuit sends a radio frequency signal in the electromagnetic wave form through the antenna. When data is sent to the terminal device, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data, and processes the data. For ease of description, <FIG> shows only one memory and one processor. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be disposed independent of the processor, or may be integrated into the processor. This is not limited in this embodiment of this application.

In this embodiment of this application, the antenna and the radio frequency circuit that have sending and receiving functions may be considered as a transceiver unit of the terminal device, and the processor that has a processing function may be considered as a processing unit of the terminal device. As shown in <FIG>, the terminal device includes a transceiver unit <NUM> and a processing unit <NUM>. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver apparatus, or the like. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing apparatus, or the like. Optionally, a component for implementing the receiving function in the transceiver unit <NUM> may be considered as a receiving unit, and a component for implementing the sending function in the transceiver unit <NUM> may be considered as a sending unit. In other words, the transceiver unit <NUM> includes the receiving unit and the sending unit. The transceiver unit may also be sometimes referred to as a transceiver, a transceiver, a transceiver circuit, or the like. The receiving unit may also be sometimes referred to as a receiver, a receiver, a receiver circuit, or the like. The sending unit may also be sometimes referred to as a transmitter, a transmitter, a transmitter circuit, or the like.

It should be understood that the transceiver unit <NUM> is configured to perform the sending operation and the receiving operation on a terminal device side in the foregoing method embodiments, and the processing unit <NUM> is configured to perform an operation other than the receiving operation and the sending operation of the terminal device in the foregoing method embodiments.

For example, in an implementation, the transceiver unit <NUM> is configured to perform the sending operation on the terminal device side in step S202 in <FIG>, and/or the transceiver unit <NUM> is further configured to perform other sending and receiving steps on the terminal device side in the embodiments of this application.

For another example, in another implementation, the transceiver unit <NUM> is configured to perform the sending operation on the terminal device side in step S202 in <FIG>, and/or the transceiver unit <NUM> is further configured to perform other sending and receiving steps on the terminal device side in the embodiments of this application.

For still another example, in still another implementation, the transceiver unit <NUM> is configured to perform the sending operation on the terminal device side in step S405 in <FIG>, and/or the transceiver unit <NUM> is further configured to perform other sending and receiving steps on the terminal device side in the embodiments of this application. The processing unit <NUM> is configured to perform the processing steps performed by the terminal device in steps S402, S403, and S404 in <FIG>, and/or the processing unit <NUM> is further configured to perform another processing step on the terminal device side in the embodiments of this application.

When the communication apparatus is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit may be an input/output circuit or a communication interface. The processing unit is a processor, a microprocessor, or an integrated circuit integrated on the chip.

When a BWP adjustment apparatus in this embodiment is a terminal device, refer to a device shown in <FIG>. In an example, the device can implement a function similar to the function of the processor <NUM> in <FIG>. In <FIG>, the device includes a processor <NUM>, a data sending processor <NUM>, and a data receiving processor <NUM>. The processor <NUM> in the foregoing embodiment may be the processor <NUM> in <FIG>, and completes a corresponding function. The receiver <NUM> or the transmitter <NUM> in the foregoing embodiment may be the data sending processor <NUM> and/or the data receiving processor <NUM> in <FIG>. Although <FIG> shows a channel encoder and a channel decoder, it may be understood that these modules are merely examples, and do not constitute a limitation on this embodiment.

<FIG> shows another form of this embodiment. A processing apparatus <NUM> includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem. The BWP adjustment apparatus in this embodiment may be used as the modulation subsystem in the processing apparatus <NUM>. Specifically, the modulation subsystem may include a processor <NUM> and an interface <NUM>. The processor <NUM> implements a function of the processing module <NUM>, and the interface <NUM> implements a function of the transceiver module <NUM>. In another variation, the modulation subsystem includes a memory <NUM>, a processor <NUM>, and a program that is stored in the memory <NUM> and that can run on the processor. When executing the program, the processor <NUM> implements the method on the terminal device side in the foregoing method embodiments. It should be noted that the memory <NUM> may be a non-volatile memory, or may be a volatile memory. The memory <NUM> may be located in the modulation subsystem, or may be located in the processing apparatus <NUM>, provided that the memory <NUM> can be connected to the processor <NUM>.

When the apparatus in this embodiment is a network device, the network device may be shown in <FIG>. An apparatus <NUM> includes one or more radio frequency units, such as a remote radio unit (remote radio unit, RRU) <NUM> and one or more baseband units (baseband unit, BBU) (which may also be referred to as digital units, digital units, DUs) <NUM>. The RRU <NUM> may be referred to as a transceiver module, and corresponds to the transmitter <NUM> in <FIG>. Optionally, the transceiver module may also be referred to as a transceiver, a transceiver circuit, a transceiver, or the like, and may include at least one antenna <NUM> and a radio frequency unit <NUM>. The RRU <NUM> is mainly configured to: send and receive a radio frequency signal, and perform conversion between the radio frequency signal and a baseband signal. For example, the RRU <NUM> is configured to send indication information to a terminal device. The BBU <NUM> is mainly configured to: perform baseband processing, control a base station, and so on. The RRU <NUM> and the BBU <NUM> may be physically disposed together, or may be physically separated, in other words, in a distributed base station.

The BBU <NUM> is a control center of the base station, and may also be referred to as a processing module. The BBU <NUM> may correspond to the processor <NUM> in <FIG>, and is mainly configured to implement a baseband processing function such as channel coding, multiplexing, modulation, or spreading. For example, the BBU (processing module) may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiments, for example, generate the foregoing indication information.

In an example, the BBU <NUM> may include one or more boards, and a plurality of boards may jointly support a radio access network (such as an LTE network) having a single access standard, or may separately support radio access networks (for example, an LTE network, a <NUM> network, or another network) having different access standards. The BBU <NUM> further includes a memory <NUM> and a processor <NUM>. The memory <NUM> is configured to store necessary instructions and data. The processor <NUM> is configured to control the base station to perform a necessary action, for example, is configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiments. The memory <NUM> and the processor <NUM> may serve the one or more boards. In other words, a memory and a processor may be independently disposed on each board, or a plurality of boards may share a same memory and a same processor. In addition, a necessary circuit may be further disposed on each board.

It should be understood that, the processor mentioned in the embodiments of the present invention may be a central processing unit (Central Processing Unit, CPU), or may be another general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

It should be further understood that the memory mentioned in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), used as an external cache. Through example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DR RAM).

It should be noted that when the processor is a general purpose processor, a DSP, an ASIC, an FPGA or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component, the memory (a storage module) is integrated into the processor.

It should be further understood that "first", "second", "third", "fourth", and various numbers in this specification are merely used for differentiation for ease of description, and are not construed as a limitation to the scope of this application.

In addition, the character "/" in this specification generally indicates an "or" relationship between associated objects.

The execution sequences of the processes should be determined according to functions and internal logic of the processes, and should not be construed as any limitation on the implementation processes of the embodiments of the present invention.

For example, the division into units is merely division into logical functions and may be other division in an actual implementation. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, in other words, may be located in one position, or may be distributed on a plurality of network units.

When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in the embodiments of this application. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disc.

Claim 1:
A bandwidth part, BWP, adjustment method, comprising:
receiving (S401), by a terminal device, in a first BWP, first indication information from a network side device, wherein the first indication information is used to indicate information about a second BWP to be used by the terminal device to receive and/or send data, and is used to indicate the terminal device to enter a sleep state; wherein the first indication information is a go to sleep, GTS, signal, and the GTS signal comprises the information about the second BWP;
determining (S402), by the terminal device, that the first BWP is different from the second BWP;
controlling (S404), by the terminal device, the terminal device to enter the sleep state, and switching, by the terminal device, an operating BWP from the first BWP to the second BWP; and
receiving and/or sending (S405), by the terminal device, the data in the second BWP immediately after being woken up.