WO2020119790A1 - Beam management method and apparatus - Google Patents

Abstract

The present application provides a beam management method and apparatus, which helps maintaining the communicative connection between a terminal device in a sleeping state and a network device. The method comprises: the terminal device receives a first signal and enters the sleeping state; the terminal device performs, on the basis of the quality strength of the first signal or first indication information carried in the first signal, beam management in the sleeping state.

Description

Beam management method and device

This application requires the priority of a Chinese patent application filed on December 14, 2018 in the Chinese Patent Office with the application number 201811536167.4 and the application name "Beam Management Method and Device", the entire contents of which are incorporated by reference in this application.

Technical field

The present application relates to the field of communications, and more specifically, to a beam management method and device.

Background technique

The network device configures a DRX cycle for the terminal device in the connected state. The terminal device detects data during a period of time in the DRX cycle (the period of time is identified by the DRX duration timer drx-onDurationTimer in the 3GPP standard), and does not detect data at other times. In order to save power consumption of terminal devices, the industry introduced sleep signals (go to sleep, GTS) or wake up signals (wake up signal (WUS). If the terminal device receives the sleep signal before the drx-onDurationTimer times out, it will no longer listen to the physical downlink control channel (PDCCH) during drx-onDurationTimer timing.

The problem in the prior art is that if the sleep signal is received in multiple consecutive DRX cycles, the terminal device will always be in the sleep state. This will affect the connection status of the terminal device, which may result in the following situations: for example, inaccurate uplink and downlink synchronization of the terminal device, a serious change in channel quality, a change in the signal beam, and so on.

Summary of the invention

In view of this, the present application provides a beam management method and apparatus. For a terminal device in a sleep state, it helps to maintain a communication connection between the terminal device and a network device.

In a first aspect, a method of beam management is provided, which includes: a terminal device receives a first signal and enters a sleep state; based on the quality strength of the first signal or the first indication information carried in the first signal, it is performed in the sleep state Beam management. Therefore, for a terminal device that enters a sleep state, the terminal device may decide whether to perform beam management based on the quality strength of the first signal, or the first indication information carried in the first signal, to avoid affecting the communication between the terminal device and the network device .

In a possible implementation, if the terminal device does not receive the first signal from the network device before the first duration timer starts, the terminal device performs any one of the following operations: the terminal device initiates Random access; or, the terminal device listens to the physical downlink control channel PDCCH after the second duration timer starts, and the second duration timer has the same length as the first duration timer. In this way, if the terminal device does not receive the first signal, it may re-access or continue to listen to the PDCCH after the second duration timer is turned on to avoid communication between the terminal device and the network device.

Here, the first duration timer is the OndurationTimer of the first DRX cycle, and the second duration timer is the OndurationTimer of the next DRX cycle.

In a possible implementation, the terminal device performs beam management based on the quality strength of the first signal, including: if the value of the quality strength of the first signal is greater than or equal to a first threshold, then the The terminal device does not perform beam management; or if the value of the quality strength of the first signal is greater than the second threshold and less than the first threshold, the terminal device performs beam management in the sleep state. Therefore, the terminal device may decide whether to perform beam management based on the quality strength value of the first signal.

In a possible implementation manner, the terminal device receives the first threshold and/or the second threshold from the network device. Therefore, the terminal device can receive the above threshold from the network device, that is, the source of the threshold is more flexible. Optionally, the first threshold and/or the second threshold may also be predefined by the protocol.

In a possible implementation manner, the terminal performing beam management based on the first indication information carried in the first signal includes: if the first indication information instructs the terminal device to perform beam management, then Beam management is performed for the first duration; if the first indication information indicates that the terminal device does not perform beam management, beam management is not performed in the sleep state. Therefore, the terminal device may determine whether to perform beam management according to the content indicated by the first indication information carried in the first signal.

In a possible implementation, if the terminal device performs beam management in the sleep state, the method further includes: the terminal device receives information indicating resources from the network device, and the resources include all The network device configures a dedicated search space for the terminal device, or a physical uplink shared channel PUSCH, or a physical uplink control channel PUCCH; the terminal device uses the resources to perform beam measurement. Therefore, the terminal device can acquire resources configured by the network device for use in beam measurement.

In a possible implementation, if the terminal device does not receive the first signal from the network device before the first duration timer starts, the terminal device initiates random access, including: during the second duration Detect the first signal before the timer starts; if the first signal is not received before the second duration timer starts, initiate random access, the second duration timer and the first signal The duration of a duration timer is the same. Therefore, if the terminal device does not receive the first signal before the second duration timer starts, it may initiate random access to avoid affecting the communication between the terminal device and the network device.

In a possible implementation manner, the first duration is a period of time in the first discontinuous reception cycle, and the second duration is a period of time in the next DRX cycle, and the DRX cycle includes DRX short cycle and DRX long cycle.

In a possible implementation, when the first duration timer is a period of time in a DRX short period, if the terminal device does not receive the first signal in N DRX short periods, the terminal The device uses the DRX long period to receive the first signal; the N is an integer greater than or equal to 1. Therefore, if the terminal device does not receive the first signal in N DRX short periods in the DRX short period, the terminal device may switch to the DRX long period to receive the first signal, so as to save power consumption.

In a possible implementation, the first signal is received again; if the values of the quality of the first signal received for the first time and the second signal received for the second time are greater than or equal to the third Threshold, no beam reporting;

If the quality strength of at least one of the first signal received for the first time and the second signal received for the second time is less than the third threshold, beam reporting is performed.

Here, the terminal device may receive multiple first signals before the first duration timer starts, that is, the network device transmits the first signal multiple times, and the terminal device receives the first signal multiple times. If the value of the quality intensity of each first signal of the plurality of first signals is greater than a third threshold, the terminal device does not perform beam reporting; if there is quality intensity of at least one signal among the plurality of first signals The value of is less than the third threshold, and the terminal device reports a beam to the network device. Therefore, in a case where the terminal device receives multiple first signals before the same drx-onDurationTimer is turned on, the terminal device may also decide whether to report the beam based on the magnitude relationship between the value of the quality strength of the first signal and the threshold.

In a possible implementation manner, the first signal includes a main signal, and the main signal is used to instruct the terminal device to notify the network device that the beam corresponding to the first duration timer and the previous signal Whether the beam corresponding to the duration timer has changed compared to the beam. Therefore, the terminal device may notify the network device of the change of the beam based on the main signal.

Optionally, the main signal may be configured by a network device.

The first signal may be a wake-up signal (WUS), a sleep signal (go to sleep signal (GTS), a CSI-RS signal, a demodulation reference signal (DMRS) signal, and a tracking reference signal TRS or synchronization signal/physical broadcast channel block ((Synchronization signal/physical broadcast channel channel block, SS/PBCH block signal, downlink control information (downlink control information, DCI), sequence signal, etc.

In a second aspect, a beam management method is provided, including: a terminal device receives a first signal and enters a sleep state; the terminal device performs beam management based on a first cycle, and the first cycle is based on the first signal The number of receptions is determined. Therefore, the terminal device can perform beam management based on the first period, so as to save power consumption.

Alternatively, the first cycle may be represented by K DRX cycles or drx-onDurationTimer. For example, the terminal equipment performs beam management at intervals of K DRX cycles or drx-onDurationTimer.

Alternatively, the first period may be determined based on the count times of receiving the first signal.

In a possible implementation manner, the terminal device performs beam management based on the first period includes: the terminal device adds 1 to the count every time the terminal device receives the first signal, and when the count reaches K, the The terminal device performs beam management, and K is an integer greater than 1; or, each time the terminal device receives the first signal, the count decreases by 1 from K, and when the count reaches 0, the terminal device performs beam management.

In a third aspect, an apparatus for beam management is provided. The apparatus includes a module for performing the method of the first aspect or various implementations thereof, or includes a module for performing the second aspect or Modules of methods in various implementations.

Optionally, the device is a terminal device.

According to a fourth aspect, a communication device is provided. The communication device may be a terminal device in the above method design, or a chip provided in the terminal device. The communication device includes: a processor. Optionally, the communication apparatus may further include a memory, and the processor is coupled to the memory and may be used to execute instructions in the memory to implement the first aspect or the second aspect and any possible implementation manner of the terminal device. The method of execution. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

When the communication device is a terminal device, the communication interface may be a transceiver or an input/output interface.

When the communication device is a chip provided in the terminal device, the communication interface may be an input/output interface.

Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

According to a fifth aspect, a program is provided, which, when executed by a processor, is used to execute the method provided in any one of the first aspect or the second aspect.

According to a sixth aspect, there is provided a program product, the program product comprising: program code, when the program code is run by a communication unit, a processing unit or a transceiver, or a processor of a communication device (eg, terminal device), such that The communication device performs any one of the methods of the first aspect or the second aspect and its possible implementations.

In a seventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium stores a program that causes a communication device (eg, terminal device) to perform the first aspect or the second aspect described above and its possible Any method in the embodiment.

In an eighth aspect, a system is provided, the system including a terminal device and a network device, the terminal device may be used to perform the steps performed by the terminal device in the first aspect or the second aspect and its possible implementation manners, so The network device may be used to perform steps corresponding to the terminal device side.

In a possible implementation manner, the system may further include other devices (such as core network devices) that interact with the terminal device and/or network device provided in the embodiments of the present application.

According to a ninth aspect, there is provided a chip which can be applied to a communication device. The chip includes at least one processor. When the at least one processor executes an instruction, the chip or the communication device performs any of the above aspects. In a possible implementation method, the chip may further include a memory, which may be used to store the instructions involved.

BRIEF DESCRIPTION

FIG. 1 is a system architecture diagram applying an embodiment of the present application;

Fig. 2 is a schematic diagram of a discontinuous reception DRX cycle;

3 is a schematic interaction diagram of a beam management method according to an embodiment of the present application;

4 is a schematic interaction diagram of a beam management method according to another embodiment of the present application;

5 is a schematic block diagram of an apparatus for beam management according to an embodiment of the present application;

6 is a schematic structural diagram of an apparatus for beam management according to an embodiment of the present application.

detailed description

The technical solutions in this application will be described below with reference to the drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global mobile communication (global system for mobile communications, GSM) system, code division multiple access (code division multiple access (CDMA) system, broadband code division multiple access) (wideband code division multiple access (WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (time division duplex, TDD), universal mobile communication system (universal mobile telecommunication system, UMTS), global interconnected microwave access (worldwide interoperability for microwave access, WiMAX) communication system, fifth generation (5th generation, 5G) System or new radio (NR), etc.

The terminal device in the embodiment of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or User device. Terminal devices can also be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (wireless local loop (WLL) stations, personal digital assistants (personal digital assistants, PDAs), wireless communication Functional handheld devices, computing devices, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, industrial control (industrial controls) Wireless terminal in self-driving, wireless terminal in self-driving, wireless terminal in remote surgery, wireless terminal in smart grid, wireless terminal in transportation safety , Wireless terminals in smart cities (smart cities), wireless terminals in smart homes (smart homes), terminal devices in 5G networks, or terminal devices in public land mobile communication networks (PLMN) that will evolve in the future The embodiments of the present application do not limit this.

The network device in the embodiment of the present application may be a device for communicating with a terminal device, for example, a radio access network (RAN) node that connects the terminal device to a wireless network. The network equipment may be a global mobile communication (global system for mobile communications, GSM) system or a base station (base transceiver) (BTS) in code division multiple access (CDMA) or broadband code division multiple access (wideband code division multiple access (WCDMA) system base station (NodeB, NB), it can also be an evolved base station (evolved NodeB, eNB or eNodeB) in the LTE system, or a cloud wireless access network (cloud radio access) network, CRAN) scenario, or the network device may be a transmission and reception point (TRP), a relay station, an access point, an in-vehicle device, a wearable device, a home base station (for example, home evolved NodeB, Or home Node B (HNB), baseband unit (BBU), or wireless fidelity (Wifi) access point (AP) and network equipment in the future 5G network or future evolved PLMN Network devices and the like in the network are not limited in the embodiments of the present application. In a network structure, the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.

In the embodiments of the present application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes central processing unit (CPU), memory management unit (memory management unit, MMU), and memory (also called main memory) and other hardware. The operating system may be any one or more computer operating systems that implement business processes through processes, for example, a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer includes browser, address book, word processing software, instant messaging software and other applications. Moreover, the embodiment of the present application does not specifically limit the specific structure of the execution body of the method provided in the embodiment of the present application, as long as it can run the program that records the code of the method provided by the embodiment of the present application to provide according to the embodiment of the present application The method may be used for communication. For example, the execution body of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call a program and execute the program.

In addition, various aspects or features of the present application may be implemented as methods, devices, or articles using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, the computer-readable medium may include, but is not limited to: magnetic storage devices (for example, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (for example, compact discs (CDs), digital universal discs (digital discs, DVDs)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

FIG. 1 is a schematic diagram of an application scenario of this application. As shown in FIG. 1, the terminal 130 accesses a wireless network to obtain services of an external network (such as the Internet) through the wireless network, or communicates with other terminals through the wireless network. The wireless network includes a RAN 110 and a core network (CN) 120, where the RAN 110 is used to access the terminal 130 to the wireless network, and the CN 120 is used to manage the terminal 130 and provide a gateway for communication with an external network.

For ease of understanding, the following describes the terms or concepts involved in the embodiments of the present application.

1. Beam (beam): The beam can be embodied in the NR protocol as a spatial filter (spatial filter), or as a spatial filter (spatial filter) or spatial parameters (spatial parameters). The beam used to send a signal can be called a transmission beam (transmission beam, Tx beam), can be called a spatial transmission filter (spatial domain domain transmit filter) or a spatial transmission parameter (spatial domain domain transmission parameter); the beam used to receive a signal can It is called the reception beam (reception beam, Rx beam), and it can be called the spatial reception filter (spatial domain reception filter) or the spatial reception parameter (spatial domain reception parameter).

The transmit beam may refer to the signal intensity distribution formed in different directions of the space after the signal is transmitted through the antenna, and the receive beam may refer to the signal intensity distribution of the wireless signal received from the antenna in different directions of the space.

It should be understood that the embodiment of the NR protocol listed above for the beam is only an example, and should not constitute any limitation to this application. This application does not exclude the possibility of defining other terms to mean the same or similar meanings in future agreements.

In addition, the beam may be a wide beam, or a narrow beam, or other types of beams. The technique of forming a beam may be a beam forming technique or other techniques. The beamforming technology may specifically be a digital beamforming technology, an analog beamforming technology, or a hybrid digital/analog beamforming technology. Different beams can be considered as different resources. The same information or different information can be sent through different beams.

Optionally, multiple beams with the same or similar communication characteristics are regarded as one beam. One or more antenna ports can be included in a beam to transmit data channels, control channels, and sounding signals. One or more antenna ports forming a beam can also be regarded as a set of antenna ports.

The beams in the embodiments of the present application may be expressed using a transmission configuration (TCI) status, or may be expressed using a quasi-co-location (QCL) relationship. QCL indicates that at least one of Doppler frequency shift, average gain, average delay, delay spread, spatial domain reception parameter, and Doppler spread of the two signals has the same value.

In NR, the beam indication used by the beam used by the downlink channel or the reference signal to transmit the corresponding beam is achieved by associating the reference resource index in the TCI state table of the transmission configuration indication.

The network equipment configures a TCI state table (corresponding to TCI-states in 3GPP standard 38.331) through radio resource control (RRC) high-level signaling. Each TCI state table contains several TCI states (corresponding to 3GPP standard 38.331 TCI-RS-Set). Each TCI state includes TCI state ID (TCI-RS-SetID), one or two quasi-coordinated QCL type indications (QCL-type A/B/C/D), and the reference signal index RS-ID corresponding to each type indication . QCL types include the following:

QCL-TypeA: {Doppler frequency shift, Doppler spread, average delay, delay spread}

QCL-Type B: {Doppler frequency shift, Doppler extension}

QCL-TypeC: {average delay, Doppler frequency shift}

QCL-Type D: {Space receiving parameter}

2. Beam management: The network device sends one or more channel state information reference signals (channel state indicator (CSI-RS) or one or more other sequence signals. The terminal device measures or finely synchronizes the signals. After the measurement Use PUCCH or PUSCH for reporting. The CSI-RS sent by the network device can be configured using the CSI-RS resource set. The configured CSI-RS resource set contains one or more CSI-RS resources. These CSI-RS resources can have the same The TCI states may have the same QCL relationship, or have different TCI states or have different QCL relationships. The terminal equipment measures the reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference and noise ratio (signal to interference, plus noise ratio, SINR) of these signals, Reference signal strength indicator (reference signal strength indicator (RSSI)), channel status information (channel status information (CSI), channel quality indicator (channel quality indicator (CQI), precoding matrix indicator (precoding matrix indicator (PMI), precoding type At least one of indication (precoding type indicator, PTI), diversity indication (rank indication, RI), LI, il, and CSI-RS resource index (CSI-RS index, CRI), where LI is a layer indication, used to indicate A data layer index (which can be used to configure the phase tracking reference signal), i1 is the wideband codebook. PMI is used to select multiple-input multiple-output (MIMO) codebooks. PTI is used to indicate the type of precoding. RI is used to indicate the rank of the antenna matrix in multi-antenna MIMO. The reported amount includes at least one of RSRP, RSRQ, RSSI, SINR, CSI, CQI, PMI, RI, LI, il, and CRI. The configured CSI-RS can also be replaced by SS/PBCH. It should be understood that, if it is fine synchronization, the beam management signal may be a tracking reference signal (TRS). It should be understood that the above is only an example of the information that the terminal device may measure and report, and may also include other measurement information, which is not limited. If the terminal equipment is configured with non-zero power channel state information reference signal resources (non-zero power channel information-reference signal (NZP-CSI-RS-ResourceSet)) to configure the measured signal and measured parameters, if the measured parameters It contains repetition set to on or off. When measuring, the network device or terminal device can also set the parameter repetition.

3. Discontinuous reception (DRX): The terminal device enters the activation period only during the necessary time period to receive downlink data and signaling, and enters the sleep state at other times to stop receiving downlink data and signaling. Working mode to save power consumption of terminal equipment. DRX mainly includes the time period (onDuration) that needs to be intercepted and the time period that it is possible to enter DRX. Figure 2 shows a schematic diagram of the DRX cycle.

The following is a brief introduction to some timers in the DRX cycle.

1) Duration timer (drx-onDurationTimer)

drx-onDurationTimer indicates a period of time during which the terminal device needs to continuously listen to the physical downlink control channel (physical downlink control channel, PDCCH). The terminal equipment must start this timer at the beginning of each new DRX cycle. As shown in Figure 2, drx-onDurationTimer is part of the DRX cycle. drx-onDurationTimer is the timer corresponding to the time period (onDuration). When drx-onDurationTimer starts, it enters the onDuration period until the end of drx-onDurationTimer. The terminal device continuously listens to the PDCCH only during the time period (onDuration) of the DRX cycle. This time period is realized by a timer (drx-onDurationTimer).

If the DRX short cycle (short cycle DRX) and DRX long cycle (long cycle DRX) are configured for the terminal device at the same time, the length of drx-onDurationTimer under the two DRX types is the same. Among them, the DRX short cycle can be realized by a DRX short cycle timer (short cycle timer), and the DRX long cycle can be realized by a DRX long cycle timer (long cycle timer).

Specifically, when the following conditions are met, the terminal device starts the drx-OndurationTimer timer in the DRX cycle:

When the terminal device is in a short DRX cycle, the following conditions are met:

[(SFN*10)+subframe numbers]modulo(shortDRX-Cycle)=(drxStartOffset)modulo(shortDRX-Cycle);

When the terminal equipment is in the long DRX cycle, the following conditions are met:

[(SFN*10)+subframe numbers]modulo(longDRX-Cycle)=drxStartOffset

Among them, SFN is the current system frame number, subframe number is the subframe number, modulo is the remainder, shortDRX-Cycle is the DRX short cycle, drxstartoffset is the starting position of the DRX cycle, the starting position of the DRX cycle can be a subframe, Time slot, symbol; longDRX-Cycle is DRX long cycle.

2) DRX inactivity timer (drx-InactivityTimer)

drx-InactivityTimer indicates a period of time during which the terminal device should continue to listen to the PDCCH. This period of time is in units of downlink subframes. This timer is started or restarted when the terminal device successfully demodulates the PDCCH indicating the first transmission data belonging to the terminal device (that is, does not include retransmission data); as shown in FIG. 2, the PDCCH of the first transmission data is received again After the instruction, the drx-InactivityTimer is restarted. As shown in FIG. 2, when the drx-InactivityTimer times out, the UE enters the sleep state.

If the sleep signal is received in multiple consecutive DRX cycles, the terminal device will always be in the sleep state, thereby affecting the communication between the terminal device and the network device. To solve this problem, the embodiment of the present application intends to determine whether to perform beam management according to the quality strength of the first signal or the first indication information carried in the first signal, which is helpful to ensure the communication connection between the terminal device and the network device.

FIG. 3 shows a schematic flowchart of a beam management method 300 according to an embodiment of the present application. As shown in FIG. 3, the method 300 includes:

S310. The terminal device receives the first signal and enters a sleep state.

The terminal device receives the first signal before the drx-onDurationTimer is turned on, and enters a sleep state after the drx-onDurationTimer is turned on, and does not listen to the PDCCH. Among them, the above-mentioned sleep state (also called sleep state, or sleep state, the terminal device is not disconnected from the network device in the sleep state) refers to: the terminal device does not need to listen to the PDCCH and/or after drx-onDurationTimer is turned on Perform reference signal measurement and reporting. Specifically, the sleep state can be understood as: the terminal device receives the first signal before the drx-onDurationTimer is turned on, so that the terminal device does not receive all data or do not perform part of the data after the associated drx-onDurationTimer or the next drx-onDurationTimer is turned on. Reception of data. Wherein, the partial data includes at least one of PDCCH data, Physical Downlink Shared Channel (Physical Downlink Share Channel, PDSCH) data and measurement signal data.

The first signal is sent by the network device to the terminal device. The first signal may be a wake-up signal (WUS), a sleep signal (go to sleep signal (GTS), a CSI-RS signal, a demodulation reference signal (DMRS) signal, and a tracking reference signal TRS or synchronization signal/physical broadcast channel (Synchronization/signal/broadcast, SS/PBCH) block signal, downlink control information (downlink control information, DCI), sequence signal and so on. Alternatively, the first signal may be another signal for saving power consumption of the terminal device, which is not limited. Among them, the SS/PBCH block contains a primary signal (primary synchronization signal, PSS), a secondary signal (secondary synchronization signal, SSS), and a physical broadcast channel (physical broadcast channel, PBCH). The signal represented by the sequence signal is a sequence, and the sequence may be a golden sequence, a golden sequence, an m sequence, or a ZC (Zadoff-Chu) sequence, which is not specifically limited.

Exemplarily, when the first signal is a sequence signal, the network device may configure the sequence signal to indicate whether the terminal device wakes up during the next drx-onDurationTimer by carrying indication information, or may directly indicate the terminal device whether there is a sequence signal Whether to wake up during the next drx-onDurationTimer timing. For example, if the sequence signal exists, the terminal device is instructed to wake up during the next drx-onDurationTimer timing; or, if the sequence signal does not exist, the terminal device is instructed not to wake up during the next drx-onDurationTimer timing. Otherwise, it can. Alternatively, "whether the sequence signal exists" may be determined in the following manner: the terminal device detects the sequence signal, and if the sequence signal meets a predetermined threshold (for example, less than a certain threshold), it is considered that the sequence signal exists.

Alternatively, the terminal device may decide whether to enter the sleep state according to whether the first signal is received. Taking the first signal as WUS as an example, if the terminal device receives WUS before drx-onDurationTimer is turned on, then the terminal device wakes up after drx-onDurationTimer is turned on; if the terminal device does not receive WUS before drx-onDurationTimer is turned on, then the terminal The device goes to sleep after drx-onDurationTimer is turned on. Taking the first signal as GTS as an example, if the terminal device receives the GTS before the drx-onDurationTimer is turned on, then the terminal device enters the sleep state after the drx-onDurationTimer is turned on; if the terminal device does not receive the GTS before the drx-onDurationTimer is turned on, then The terminal device wakes up after drx-onDurationTimer is turned on.

The TCI state or QCL relationship of the first signal may be configured by the network device. Exemplarily, the network device can be configured through RRC signaling and activated through medium access control layer (medium access control element (MAC) CE) signaling; or, it can also be configured through MAC-CE signaling. Activation through DCI signaling; alternatively, configuration through RRC signaling and activation through DCI signaling; or, configuration through RRC signaling and MAC-CE signaling and activation through DCI signaling.

Optionally, the DCI signaling for configuring the TCI state or QCL relationship of the first signal may not start or restart the drx-InactivityTimer. The TCI state of the first signal may also be scrambled with the last cell-radio network temporary identifier (C-RNTI) or other wireless network temporary identifier (radio network identifier) (RNTI) detected by the terminal device. The TCI of the PDCCH is the same, or the same as the TCI state of the last physical downlink shared channel (PDSCH) received by the terminal device.

Optionally, the network device may configure multiple time signal or frequency domain positions of the first signal for the terminal device, and each time or frequency domain position may correspond to a TCI state. The TCI state or QCL relationship of the first signal used by the network device or the first signal of the service changes as the TCI state of the DCI changes or as the TCI state of the PDSCH changes. For example, the TCI state of the DCI of the terminal device has changed, and the first signal at its corresponding position is activated. The number of configured positions of the first signal may be the same as the number of TCI states configured by the network device for DCI through RRC signaling, or the number of TCI states configured for the first signal by the network device through RRC signaling or MAC-CE signaling the same. When the network device uses MAC-CE to activate the TCI state of DCI, the first signal in its corresponding position is also activated. For example, the network device configures 8 TCI states through RRC signaling. When the TCI state of DCI activated by MAC-CE is the first TCI state, the first signal in the first position is also activated, and the terminal device is in the first The position detects its first signal. The first signal detected at the first location may carry grouping information or group information or indication information of the terminal device to indicate whether to wake up to listen to the PDCCH during the next drx-onDurationTimer timing. The first signals at other locations do not carry the grouping information or group information or indication information indicating whether to wake up at the next drx-onDurationTimer to listen to the PDCCH.

In the embodiment of the present application, the terminal device may adopt one or more of the following ways to perform beam management: method one, perform beam management according to the quality strength of the first signal; method two, according to the first carried in the first signal Indication information for beam management; method three, periodic beam management. The beam management can be understood as: the terminal device measures the quality strength of the first signal, and reports the measurement result to the network device.

The above three methods will be described in detail below.

method one

S320. Based on the quality strength of the first signal, the terminal device performs beam management in the sleep state.

Specifically, the terminal device measures the quality strength of the first signal, and then performs beam management in the sleep state according to the measurement result of the quality strength. The quality strength of the first signal may be characterized by one or more of the following: reference signal received power RSRP, reference signal received quality RSRQ, signal-to-interference and noise ratio SINR, reference signal strength indicator RSSI, etc., There are no restrictions on this.

As an implementation manner, the terminal device may decide whether to perform beam management in the sleep state based on the quality intensity threshold. Based on the quality intensity of the first signal, the terminal device performs beam management in the sleep state, including: if the value of the quality intensity of the first signal is greater than or equal to a first threshold, the terminal device does not perform beam Management; or, if the value of the quality strength of the first signal is greater than the second threshold and less than the first threshold, the terminal device performs beam management in the sleep state.

Taking the RSRP value characterization of the quality of the first signal as an example for description: After receiving the first signal, the terminal device measures the RSRP value of the first signal, if the terminal device measures the RSRP value of the received first signal If it is greater than or equal to the first threshold, no beam management is required; if the RSRP value of the first signal measured by the terminal device is less than the first threshold and greater than the second threshold, it is necessary to perform beam management during the drx-onDurationTimer timing.

Optionally, the first threshold and/or the second threshold may be configured by the network device for the terminal device, or may be reported by the terminal device to the network device, or may be predefined by the protocol, There are no restrictions on this.

Method two

S320. The terminal device performs beam management in the sleep state based on the first indication information carried in the first signal.

For the network device, the network device may carry the first indication information in the first signal to inform the terminal device whether to perform beam management during the drx-onDurationTimer timing. Correspondingly, the terminal device can decide whether to perform beam management according to the first indication information carried in the first signal.

Exemplarily, the network device may instruct the terminal device to perform beam management or beam measurement in the sleep state drx-onDurationTimer through a sequence signal, or RRC signaling, or MAC-CE, or DCI signaling. For example, the first indication information may be DCI or individual data bits in the sequence; or, the first indication information may also be multiplexed to indicate whether to wake up to listen to the data bits of the PDCCH at the next drx-onDurationTimer, so as to reduce bit overhead . When the first indication information is transmitted through DCI, it can be configured using DCI format 0_0 or format 0_1. Optionally, the DCI can also carry PUSCH resources, which are used for reporting measurement information.

Exemplarily, if the first indication information is used to instruct the terminal device not to perform beam management, the terminal device does not perform beam management in the sleep state; if the first indication information is used to instruct the terminal device to perform beam management, then The terminal device performs beam management in the sleep state.

If the terminal device is in a low-speed state or a medium-speed motion state, the terminal device may report information or configuration information according to the quality strength of the first signal (corresponding manner 1) or the first indication information (corresponding manner 2) carried in the first signal To determine whether to perform beam management. Here, the configuration information is used to indicate whether the terminal device performs beam reporting; the reporting information is used to indicate whether the terminal device performs beam reporting.

Way three

As shown in FIG. 4, the method 400 includes:

S410. The terminal device receives the first signal and enters a sleep state.

It should be understood that step S410 is the same as step S310, and the related explanation or description of step S410 can be referred to the description of step S310 in the foregoing.

S420. The terminal device performs beam management based on a first period, which is determined according to the number of times the first signal is received.

The terminal device may periodically perform beam management based on the first period. For the terminal device, whether the first cycle is reached can be determined by the number of times the first signal is received. The terminal device may count the number of receptions of the first signal through a counter, and perform beam management when the number of receptions reaches the first period.

The first cycle may be configured by the network device. For example, the network device may determine the first cycle based on the size of the DRX cycle or drx-onDurationTimer. The first cycle may be a multiple of the DRX cycle, such as K times the DRX cycle.

Taking the first cycle being K DRX cycles as an example, the terminal device may wake up to perform beam management at intervals of K DRX cycles, or may wake up to perform beam management at intervals of K drx-onDurationTimers. The terminal device may perform beam management in any of the following ways: each time the terminal device receives the first signal or when a DRX cycle elapses, the count is increased by 1, and when the count reaches K, the terminal The device performs beam management, K is an integer greater than 1;

Alternatively, each time the terminal device receives the first signal or when one DRX cycle elapses, the count is decreased from K by 1, and when the count reaches 0, the terminal device performs beam management.

That is to say, the terminal device can count the number of times the first signal is received by the counter. Each time the first signal is received, the count is increased by 1. When the count reaches K, the terminal device performs beam management. Or, the terminal device performs beam management by a countdown method. Each time the first signal is received, the count is subtracted from K, and when the count reaches 0, the terminal device performs beam management. Here, the purpose of the terminal equipment to perform beam management at intervals of K cycles or drx-onDurationTimer is to ensure the performance of the communication link while saving power consumption of the terminal equipment. In the above two counting scenarios, optionally, if the terminal device wakes up or listens to the PDCCH, K is recounted; or, the terminal device may also recount K based on the instruction of the network device. Here, the terminal device may decide whether to wake up based on the specific content of the received first signal. For example, the first signal is WUS. If the terminal device receives WUS, the terminal device wakes up; if it does not receive WUS, the terminal device does not wake up. For another example, if the first signal is GTS, if the terminal device receives the GTS, the terminal device does not wake up; if the GTS is not received, the terminal device wakes up.

The terminal device can also be configured by the network device to perform beam management during any drx-onDurationTimer timing of K drx-onDurationTimers. For example, the terminal device is configured by the network device to any drx-onDurationTimer timing period from 0 to K-1 Beam management. The terminal device can also be configured by the network device to perform beam management during any drx-onDurationTimer of K+1 drx-onDurationTimers. For example, the network device is configured to perform beam management during any drx-onDurationTimer from 0 to K. . The terminal device can also be configured by the network device to perform beam management during any drx-onDurationTimer timing of K+2 drx-onDurationTimers, for example, be configured to perform beam management during any drx-onDurationTimer timing from 0 to K+1 .

Optionally, the value of K may be configured by the network device for the terminal device, or may be reported by the terminal device to the network device, or may be predefined by a protocol, which is not specifically limited.

When the value of K is determined based on the DRX cycle or the size of drx-onDurationTimer, the value of K can be determined according to any one of the following situations: When the DRX cycle or drx-onDurationTimer is relatively large, a smaller value can be configured K value; when the DRX cycle or drx-onDurationTimer is relatively small, you can configure a larger K value. For example, when the length of the DRX cycle is 80ms, the value of K is 2, that is, the terminal device performs beam management at intervals of 2 DRX cycles; when the length of the DRX cycle is 40ms, the value of K can be 4, that is, the terminal device Beam management is performed at intervals of 4 DRX cycles.

Optionally, the value of K may have different values according to different cells, or different values according to different bandwidth parts (BWP). For example, the value of K can be part or all of the following values: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 ,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32. Among them, when the value of K is 0, it means that the terminal device needs to perform beam management or signal measurement every DRX cycle or drx-onDurationTimer.

The first period may also be a fixed constant, for example, T time-domain units. The constant may be configured by a network device, or may be predefined by a protocol, which is not limited. The time domain unit may be any one of drx-onDurationTimer, millisecond (ms), time slot, mini-slot, frame, and subframe. For example, T can take constants such as 10ms, or 20ms or 40ms.

The network device can also set one or some drx-onDurationTimer as the drx-onDurationTimer that the terminal device must wake up, then the terminal device will perform beam management during this type of drx-onDurationTimer timing. This type of drx-onDurationTimer refers to one or more drx-onDurationTimers set to have to wake up.

In the above manner three, the terminal device periodically performs beam management. Alternatively, the terminal device can always perform beam management to prevent link failure. Exemplarily, the terminal device may also perform beam management during the drx-onDurationTimer timing. Here, the CSI-RS or SS/PBCH or sounding reference signal (SRS) configured by the beam management may be periodic, and the reported resource is also periodic or semi-persistent. The resource used by the terminal device to report the beam may be a physical uplink control channel (physical uplink control channel, PUCCH) or may be a physical uplink shared channel (physical uplink link, shared channel, PUSCH).

For the network device, the network device can also perform beam management by K DRX cycles or K drx-onDurationTimers.

It should be understood that the above three methods can be arbitrarily combined, not limited to the above three methods. For example, the terminal device may be used for a certain period of time and mode 2 for a certain period of time; or, may be used for a certain period of time and mode 3 for a period of time.

In the above manners 1 to 3, if the terminal device performs beam management, the network device may also configure resources for the terminal device, so that the terminal device uses the configured resources to report the measurement result. Optionally, the method 300 or the method 400 further includes:

The network device sends information indicating resources to the terminal device, where the resources include a dedicated search space configured by the network device for the terminal device, or a dedicated physical uplink shared channel PUSCH, or a dedicated physical uplink control channel PUCCH. The resource refers to a dedicated resource configured by the network device for the terminal device in the sleep state. Correspondingly, the terminal device receives information indicating the resource sent by the network device; the terminal device uses the resource to perform beam measurement.

Specifically, the network device may configure a PUCCH or a dedicated search space (SearchSpace) for the terminal device. The configuration of the PUCCH or dedicated search space (SearchSpace) is different from the configuration of the terminal device in the awake state to receive the PDCCH, and may have a larger period and different offset positions, which can reduce the power consumption of the terminal device. In other words, in addition to configuring resources for the terminal device in the awake state, the network device must also configure resources for the terminal device in the sleep state. The dedicated search space configured by the network device for the terminal device may be a dedicated search space set or a control resource set. The network device configures the PDCCH of these resources for the terminal device, or the PDCCH configuring RRC signaling, may have a separate search space.

Optionally, the PDCCH or DCI in the search space set or control resource set will not affect the timer in the DRX cycle. The PDCCH or DCI received by the terminal device in the above search space set or control resource set does not cause the terminal device or the network device to start drx-InactivityTimer or restart drx-InactivityTimer.

For the case where the terminal device does not receive the first signal during the drx-ondurationTimer timing, optionally, the method 300 further includes:

If the terminal device does not receive the first signal from the network device before starting the first duration timer, the terminal device performs any of the following operations:

The terminal device initiates random access; or,

The terminal device listens to the physical downlink control channel PDCCH after the second duration timer starts, and the second duration timer has the same timing length as the first duration timer.

The above first duration can be understood as the time period corresponding to one drx-onDurationTimer in the DRX cycle, and the second duration can be understood as the time period corresponding to the drx-onDurationTimer in the next DRX cycle, and the DRX cycle includes a DRX short cycle And DRX long cycle.

As a first implementation, if the terminal device does not receive the first signal sent by the network device before turning on drx-onDurationTimer, the terminal device may directly initiate a random access or scheduling request (SR) to re-access Or get scheduling resources. The random access may be contention-based or non-contention-based. The terminal device may use contention-based random access first, and if the network device does not respond, then use the non-contention-based random access channel.

Optionally, in the above implementation, if the terminal device does not receive the first signal before the first duration timer starts, the terminal device initiating random access includes:

The terminal device detects the first signal before starting the second duration timer;

If the terminal device does not receive the first signal before the second duration timer starts, the terminal device initiates random access.

Specifically, if the terminal device does not receive the first signal before turning on the drx-onDurationTimer in one DRX cycle, it can continue to detect whether there is a first signal before turning on the drx-onDurationTimer in the next DRX cycle until N DRX cycle. If the drx-onDurationTimer for N consecutive DRX cycles does not receive the first signal before starting, the terminal device determines that the connection fails, and initiates random access to the network device.

When the first duration is a period in the DRX short cycle, if the terminal device does not receive the first signal in N DRX short cycles, the terminal device changes the DRX short cycle to the DRX long cycle, That is, the terminal device uses the DRX long period to receive the first signal, so as to save power consumption of the terminal device. The N is an integer greater than or equal to 1.

The value of N may be configured by the network device for the terminal device, or may be determined by the terminal device itself, or may be predefined by the protocol, which is not limited. For example, the value of N may be at least one of 1,2,3,4,5,6,7,8,9,10.

Exemplarily, taking the first signal as WUS as an example, if the terminal device works in the DRX short cycle and the DRX short cycle does not time out, the terminal device receives WUS N1 times and is not awakened, the network device may The DRX short cycle of the terminal device is changed to the DRX long cycle, which is convenient for saving the power consumption of the terminal device. If the terminal device receives the WUS indication and needs to wake up, N1 restarts counting. Optionally, in a situation where the count of N1 is in progress, if the DRX short period times out, the terminal device enters the DRX long period, and then counts based on the DRX long period, and N1 is an integer greater than or equal to 1.

If the terminal device does not receive WUS before turning on the current drx-onDurationTimer, the terminal device listens to the PDCCH during the next drx-onDurationTimer timing, and determines whether to recount or continue counting according to whether the PDCCH is heard.

If the terminal device does not listen to the PDCCH during the next drx-onDurationTimer timing, the terminal device continues to receive WUS with a short DRX cycle; if it receives WUS before turning on the next drx-onDurationTimer, the counting of N1 continues. If the WUS is not received before the next drx-onDurationTimer is turned on, the terminal device changes the DRX short period to the DRX long period, clears the count of N1, and receives WUS before the drx-onDurationTimer that starts the DRX long period; if Before the DRX long-period drx-onDurationTimer is turned on and no WUS is received, the terminal device initiates a random access RACH or scheduling request.

As a second implementation, if the terminal device does not receive the first signal sent by the network device before starting a drx-onDurationTimer, the terminal device may listen to the physical downlink control channel PDCCH or perform measurement during the next drx-onDurationTimer timing. Alternatively, the scheduling request SR is sent through the PUCCH during a drx-onDurationTimer. If the terminal device listens to the PDCCH during the next drx-onDurationTimer, the terminal device may listen to the PDCCH based on the search space (SearchSpace) that is not in sleep state; or, the terminal device may configure based on the PUCCH or PUSCH that is not in sleep state. The network device reports the status, channel quality, or measurement result of the terminal device; or, the terminal device can listen to the PDCCH according to the sleep state search space; Channel quality or measurement results, which helps save power consumption.

The above describes the case where the terminal device receives a first signal before starting a drx-onDurationTimer, and the following describes the case where the terminal device receives multiple first signals before starting a drx-onDurationTimer. It should be understood that for related terms or concepts involved in the case where the terminal device receives multiple first signals, reference may be made to the previous introduction of the terminal device receiving a first signal, and for the sake of brevity, no further description is provided here.

The number of multiple first signals received by the terminal device may be configured by the network device. N2 represents the number of the first signal, and the value of N2 may be an integer greater than 1. In particular, if the value of N2 is 0, it means that the first signal is not supported. Here, the terminal device does not support the first signal means that the network device has not configured or sent the first signal for the terminal device.

Optionally, the method 300 further includes:

The terminal device receives the first signal N2 times;

If the value of the quality strength of the first signal received by the terminal device N2 times is greater than or equal to a third threshold, the terminal device does not perform beam reporting;

If the quality strength of at least one of the first signals received by the terminal device N2 times is less than the third threshold, the terminal device performs beam reporting, and N2 is greater than or equal to 2.

For the plurality of first signals received N2 times, the plurality of first signals may include a main signal, and the main signal is used to instruct the terminal device to notify the network device of the first duration timer Whether the corresponding beam has changed compared with the beam or measurement value corresponding to the last wake-up duration timer, wherein the main signal is configured by the network device in the plurality of first signals.

Specifically, in the case of multiple first signals, the terminal device may decide whether to perform beam reporting based on the quality strength of the multiple first signals. For example, if the quality strength values of multiple first signals received by the terminal device are all greater than the third threshold, the terminal device may not perform beam reporting; if there is at least one first signal among the multiple first signals received by the terminal device If the value of the signal strength is less than the third threshold, or the value of the quality strength of the main signal is less than the third threshold, the terminal device reports the beam. Alternatively, the terminal device may determine whether to perform beam reporting according to the quality strength of multiple first signals, and/or configuration information or reporting information. Here, the configuration information is used to indicate whether the terminal device performs beam reporting; the reporting information is used to indicate whether the terminal device performs beam reporting.

The third threshold may be configured by the network device, may be pre-defined by the protocol, or may be reported by the terminal device to the network device, which is not limited. The third threshold may also be a difference, and the difference is a difference between the first signal and a signal having a QCL relationship with the first signal. For example, the signal having a QCL relationship with the first signal may be SS/PBCH block or CSI-RS or DMRS or the own signal (wherein the own signal refers to the first signal). Here, each of the plurality of first signals has a corresponding difference value. The network device may select one of the plurality of differences as the third threshold, or may use the difference corresponding to the main signal among the plurality of first signals as the third threshold.

For the network device, if the terminal device does not report the beam, the network device defaults that the TCI of the terminal device does not change or the channel quality does not change. Once reported, it indicates that the beam performance of the terminal device has deteriorated or the channel quality has changed, almost Cannot communicate, need to re-measure the report or replace the beam.

If the first signal received by the terminal device before turning on drx-onDurationTimer this time is too weak to support communication compared to the last signal received before turning on drx-onDurationTimer, then the terminal device can initiate random access Or perform beam recovery.

In the case of multiple first signals, the resources used by the terminal device when reporting the beam may be configured by the network device. The reporting resource configured by the network device for the terminal device may be periodic, acyclic, or semi-persistent. When the reported resource is a period, the period corresponding to the resource used by the terminal device for beam reporting is the same as the resource period configured by the network device. The resource used by the terminal device to report the beam may be PUCCH or PUSCH.

The network device may configure the terminal device with multiple PUCCH resources used for reporting beams. The TCI state of these PUCCH resources may be the same as the TCI state of the first signal, that is, each PUCCH resource has one or more corresponding first signals having a QCL relationship with it. The terminal device uses one or more of the PUCCH resources for beam reporting according to the PUCCH resources configured by the network device. As a possible implementation, if the reported information received by the network device is sent using the desired PUCCH or the desired PUSCH, the network device uses the TCI state of the PDCCH corresponding to the last waking drx-onDurationTimer to send the corresponding PDCCH.

As another possible implementation, if the reported information received by the network device is not sent using the desired PUCCH or PUSCH, the network device may select the beam reported by the terminal device or the TCI to send the PDCCH.

As another possible implementation manner, if the reported information received by the network device is not sent using the desired PUCCH or PUSCH, the network device may select all beams or TCI corresponding to the first signal to send the PDCCH.

After receiving the report information of the terminal device, the network device may determine the beam to deliver the PDCCH according to the beam of the PUCCH reported by the terminal device, and the two have a beam correspondence relationship.

In the case of multiple first signals, the terminal device may also perform beam management at intervals of L DRX cycles or drx-onDurationTimer. Here, the value of L can be similar to the value of K above, and the value of L can also refer to the description of the value of K above.

Exemplarily, the terminal device receives a plurality of first signals (the plurality of first signals are regarded as a group of signals) before starting a drx-onDurationTimer. Each time the terminal device receives a group of signals or passes a DRX cycle, the count is incremented by 1. When the count reaches L, the terminal device performs beam management, L is an integer greater than 1; or, the terminal device When a group of signals is received or when a DRX cycle elapses, the count is decremented from L, and when the count reaches 0, the terminal device performs beam management.

If the terminal device wakes up, L recounts. Alternatively, the terminal device may recount L based on the instruction of the network device.

The value of L may be configured by the network device, or may be reported by the terminal device, or may be predefined by the protocol, which is not limited. Optionally, the value of L may have different configurations according to different cells, or different configurations according to different BWP.

For example, the value of L can be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21 , 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32 some or all of the values.

Optionally, the value of L can be determined according to the length of the DRX cycle or drx-onDurationTimer. When the length of the DRX cycle or drx-onDurationTimer is large, a smaller value of L can be configured. When the DRX cycle or drx-onDurationTimer When the length of time is small, you can configure a larger L value. For example, when the length of the DRX cycle is 80ms, the value of L is 2, that is, the terminal device performs beam management by 2 DRX cycles; when the length of the DRX cycle is 40ms, the value of L can be 4, that is, the terminal device interval is 4 Beam management for each DRX cycle.

When the value of L is 0, it means that the terminal device needs to report the beam every DRX cycle or drx-onDurationTimer timing period. In this case, if the terminal device does not report the beam, the network device considers that the connection of the terminal device has failed and needs to re-establish the connection, and the terminal device initiates a random access or scheduling request SR. Optionally, the terminal device may not report at all times, and initiate random access for beam recovery when the connection with the network device fails.

For the case where the terminal device receives multiple first signals, the terminal device may report multiple beams, or multiple reference signal index RSRPs. Correspondingly, the network device may determine the reported beam according to the reference signal index reported by the terminal device, or determine the reported beam according to the maximum value of the RSRP of multiple reference signals reported by the terminal device. The terminal device may change the beam according to the reporting sequence, for example, the first beam is the updated TCI state.

The above-mentioned embodiment regarding one first signal and the embodiment regarding multiple first signals may be used in combination. For example, the terminal device receives multiple first signals at intervals of M DRX cycles, and at the same time, receives one first signal in the remaining DRX cycles.

Optionally, the value of M may be configured by the network device, or may be reported by the terminal device, or may be predefined by the protocol, which is not limited. The value of M may have different configurations according to different cells, or different configurations according to different BWP. For example, the value of M can be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21 , 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32 some or all of the values.

When the network device configures the terminal device with a signal for measurement, the network device may configure the terminal device with measurement signals and/or report resources at intervals of M2 DRX cycles, and the remaining DRX cycles do not configure measurement signals and/or report resources. This measurement signal can be used as a beam management or tracking reference signal. The sending or receiving time of the measurement signal may be during the drx-onDurationTimer timing, or it may be before the drx-onDurationTimer is turned on, or it may be concentrated in a time window (Window), which is not limited. The M2 DRX cycles may refer to the number of DRX cycles in which the terminal device is in a sleep state during drx-onDurationTimer timing, or may refer to the number of DRX cycles in which the terminal device is not in a sleep state during drx-onDurationTimer timing, or may refer to the above The sum of the two numbers.

The value of M2 may be configured by the network device, or may be reported by the terminal device, or may be predefined by the protocol, which is not limited. The value of M2 may have different configurations according to different cells, or different configurations according to different BWP. For example, the value of M2 can be 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21 , 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32 some or all of the values. In particular, if the value of M2 is 0, it means that the network device is configured with a measurement signal and/or reporting resource for each DRX cycle for the terminal device, that is, the period of the measurement signal or the period of the window corresponding to the measurement signal, which is the Are the same.

The network device may also configure the number of windows corresponding to the measurement signals, or the number of measurement signals, for example, the number of windows corresponding to the measurement signals or the number of measurement signals may be configured as 1, 2, 3, 4, 5 ,6,7,8 any value.

The network device may also configure the DRX index corresponding to the DRX cycle of the measurement signal in the M2 DRX cycles, so that the terminal device performs measurement in the corresponding DRX cycle based on the DRX index. This can reduce the number of measurements of the terminal device, thereby reducing the power consumption of the terminal device.

The network device can also configure or send the first signal once for the terminal device at intervals of M2 DRX cycles. The primary first signal may be multiple first signals or a single first signal. The first signal may indicate that the terminal device does not need to wake up in one or more DRX cycles. For example, the network device instructs the terminal device not to wake up during the drx-onDurationTimer of M3 DRX cycles among M2 DRX cycles. The drx-onDurationTimer of M3 DRX cycles may be continuous or discontinuous.

The value of M3 may be configured by the network device, or may be indicated through bit mapping. The value range of M3 may be an integer from 1 to M2 or 1 to M2-1. The value of M3 may also be fixed, for example, as agreed in the protocol, or agreed between the terminal device and the network device. The value of M3 may be indicated by the first signal, or the bit-mapped bits of the drx-onDurationTimer of M3 DRX cycles may also be indicated by the first signal. Taking M3=3 as an example, 3 bits can be used to indicate whether the terminal device wakes up during 3 drx-onDurationTimer timings, such as joint bit 111, indicating that the terminal device needs to wake up during 3 drx-onDurationTimer timings.

In the above embodiment where the terminal device receives a first signal or multiple first signals before starting drx-onDurationTimer, the following description about the first signal applies. The first indication information may instruct the terminal device to measure the measurement signal, and report the measurement result to the network device. Correspondingly, the network device needs to configure a measurement signal for the terminal device in order to measure the quality intensity of each beam. The first signal may also indicate the report type of the measurement signal, for example, the report type may be RSRP, RSRQ, RSSI, SINR, CSI, CQI, PMI, PTI, RI, LI, il, and CSI-RS resource index (CSI-RS index, CRI). The first signal may also indicate the index or sequence number of the reported configuration of the measurement signal, such as reportConfigId or CSI-ReportConfigId. The terminal device may measure the measurement signal according to the index configured for reporting to measure parameters such as the position of the measurement signal associated with the index and the reported amount associated with the index. The reporting quantity is a measurement value corresponding to at least one of the reporting types described above, for example, the reporting quantity is RI-PMI-CQI, or, RI-i1, or, RI-i1-CQI, or, RI-CQI , Or, RSRP, or, RI-LI-PMI-CQI.

Among them, the index of the report configuration relates to the time domain position and frequency domain position of the reference signal measured by the report amount, the port, the codebook, the reference signal type, the report amount and other parameters. The network device also configures different measurement windows according to different reporting configuration indexes, or uses the first signal to indicate the reporting configuration indexes within the measurement window.

In order to avoid redundant description, here is a unified description. In the embodiment of the present application, when the network device configures or sends one or more of the following to the terminal device: the first indication information, the first threshold, the The second threshold, the third threshold, the related configuration of the above first cycle (such as the value of K, or the value of T, etc.), resources, the number of multiple first signals, the value of N, and the value of L The value, the value of M, the TCI status or QCL relationship of the first signal, the value of M2, etc., can be configured or sent through RRC signaling, MAC-CE, DCI signaling or system information signaling. The application examples do not specifically limit this.

It should be understood that, for related terms or concepts involved in the case where the terminal device receives multiple first signals, reference may be made to the introduction in the foregoing embodiment in which the terminal device receives one first signal, and for brevity, details are not described here.

It should also be understood that the various solutions of the embodiments of the present application can be used in a reasonable combination, and the explanation or description of each term appearing in the embodiments can be referred to or explained in each embodiment, which is not limited.

It should also be understood that, in various embodiments of the present application, the size of the sequence numbers of the above processes does not mean that the execution order is sequential, and the execution order of each process should be determined by its function and inherent logic, and should not be implemented in this application. The implementation process of the examples constitutes no limitation.

The beam management method according to an embodiment of the present application is described in detail above with reference to FIGS. 1 to 4. The beam management apparatus according to an embodiment of the present application will be described below with reference to FIGS. 5 to 6. It should be understood that the technical features described in the method embodiments are also applicable to the following device embodiments.

FIG. 5 shows a schematic block diagram of a beam management apparatus 500 according to an embodiment of the present application. Optionally, the specific form of the apparatus 500 may be a terminal device or a chip in the terminal device, which is not limited in this embodiment of the present application. The device 500 includes:

The transceiver module 510 is used to receive the first signal and enter the sleep state;

The processing module 520 is configured to perform beam management in the sleep state based on the quality strength of the first signal or the first indication information carried in the first signal.

In a possible implementation, the processing module 520 is also used to:

If the device does not receive the first signal before starting the first duration timer, perform any of the following operations:

Initiate random access; or,

Listening to the physical downlink control channel PDCCH after the second duration timer is started, the second duration timer and the first duration timer have the same timing length.

In a possible implementation manner, the processing module 520 is configured to perform beam management in the sleep state based on the quality strength of the first signal, specifically including:

If the value of the quality strength of the first signal is greater than or equal to the first threshold, no beam management is performed; or

If the value of the quality strength of the first signal is greater than the second threshold and less than the first threshold, beam management is performed in the sleep state.

In a possible implementation manner, the transceiver module is further configured to receive the first threshold or the second threshold from a network device.

In a possible implementation manner, the processing module 520 is configured to perform beam management in the sleep state based on the first indication information carried in the first signal, specifically including:

If the first indication information instructs the terminal device to perform beam management, perform beam management in the sleep state;

If the first information indicates that the terminal device does not perform beam management, beam management is not performed in the sleep state.

In a possible implementation, if the device performs beam management in the sleep state, the transceiver module 510 is further configured to:

Receiving information indicating resources from the network device, the resources including a dedicated search space configured by the network device for the device, or a physical uplink shared channel PUSCH, or a physical uplink control channel PUCCH;

The processing module 520 is configured to perform beam measurement using the resources.

In a possible implementation, if the device does not receive the first signal before the first duration, the processing module 520 is used to initiate random access, specifically including:

Receiving the first signal before starting the second duration timer;

If the terminal device does not receive the first signal before starting the second duration timer, the terminal device initiates random access.

In a possible implementation, the first duration timer is a period of time in the first discontinuous reception cycle, and the second duration timer is a period of time in the next DRX cycle. The DRX cycle includes a DRX short cycle and a DRX long cycle.

In a possible implementation, the transceiver module 510 is also used to:

When the first duration timer is a period in the DRX short cycle, if the terminal device does not receive the first signal in N DRX short cycles, the terminal device uses the DRX long cycle to receive the first A signal

The N is an integer greater than or equal to 1.

In a possible implementation, the transceiver module 510 is also used to:

Receive the first signal again;

Wherein, the processing module 520 is used to:

If the values of the quality of the first signal received for the first time and the second signal received for the second time are greater than or equal to a third threshold, no beam reporting is performed;

If the quality strength of at least one of the first signal received for the first time and the second signal received for the second time is less than the third threshold, beam reporting is performed.

In a possible implementation manner, the plurality of first signals include a main signal, and the main signal is used to instruct the apparatus to notify the network device that the beam and the beam corresponding to the first duration timer are Whether the beam corresponding to a wake-up duration timer has changed compared to the beam.

Optionally, the first signal is a wake-up signal WUS, or a sleep signal GTS.

It should be understood that the beam management apparatus 500 according to an embodiment of the present application may correspond to the method of the terminal device in the foregoing method embodiment, for example, the method in FIG. 3, and the above and other management operations of each module in the apparatus 500 and/or Or the functions are respectively to implement the corresponding steps of the method of the terminal device in the foregoing method embodiments, so the beneficial effects in the foregoing method embodiments can also be achieved, and for the sake of brevity, they will not be repeated here.

Alternatively, the device 500 may also perform the following functions, specifically including:

The transceiver module 510 is used to receive the first signal and enter the sleep state;

The processing module 520 is configured to perform beam management based on a first period, which is determined according to the number of times the first signal is received.

In a possible implementation, the processing module 520 is used to perform beam management based on the first period, which specifically includes:

Each time the transceiver module 510 receives the first signal, the count increases by 1, and when the count reaches K, beam management is performed, where K is an integer greater than 1;

Alternatively, each time the transceiver module 510 receives the first signal, the count is decremented from K, and when the count reaches 0, beam management is performed.

It should be understood that the beam management apparatus 500 according to an embodiment of the present application may correspond to the method of the terminal device in the foregoing method embodiment, for example, the method in FIG. 4, and the above and other management operations of each module in the apparatus 500 and/or Or the functions are respectively to implement the corresponding steps of the method of the terminal device in the foregoing method embodiments, so the beneficial effects in the foregoing method embodiments can also be achieved, and for the sake of brevity, they will not be repeated here.

It should also be understood that each module in the device 500 may be implemented in the form of software and/or hardware, which is not specifically limited. In other words, the device 500 is presented in the form of functional modules. The “module” here may refer to an application-specific integrated circuit ASIC, a circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions. Alternatively, in a simple embodiment, those skilled in the art may think that the device 500 may adopt the form shown in FIG. 6. The processing module 520 may be implemented by the processor 601 shown in FIG. 6. The transceiver module 510 can be implemented by the transceiver 603 shown in FIG. 6. Specifically, the processor is implemented by executing the computer program stored in the memory. Optionally, when the device 500 is a chip, the transceiving function and/or the transceiving implementation process of the device 500 may also be implemented through pins or circuits. Optionally, the memory is a storage unit in the chip, such as a register, a cache, etc. The storage unit may also be a storage unit in the computer device located outside the chip, as shown in FIG. 6 602.

FIG. 6 shows a schematic structural diagram of an apparatus 600 for beam management according to an embodiment of the present application. As shown in FIG. 6, the device 600 includes: a processor 601.

In a possible implementation manner, the processor 601 is used to call an interface to receive a first signal and enter a sleep state; the processor 601 is used to determine whether the first signal is based on the quality strength of the first signal or Carrying the first indication information to perform beam management in the sleep state.

Or, in a possible implementation manner, the processor 601 is used to call an interface to receive a first signal and enter a sleep state; the processor 601 is also used to perform beam management based on a first period, the first period It is determined according to the number of times the first signal is received.

It should be understood that the processor 601 may call an interface to perform the above-mentioned sending and receiving actions. Exemplarily, the called interface may be a logical interface or a physical interface, which is not limited. Alternatively, the physical interface may be implemented by a transceiver. Optionally, the device 600 further includes a transceiver 603.

Optionally, the device 600 further includes a memory 602, and the memory 602 may store the program code in the foregoing method embodiment, so that the processor 601 can call it.

Exemplarily, if the device 600 includes a processor 601, a memory 602, and a transceiver 603, the processor 601, the memory 602, and the transceiver 603 communicate with each other through an internal connection channel, and transfer control and/or data signals. In a possible design, the processor 601, the memory 602, and the transceiver 603 may be implemented on a chip, and the processor 601, the memory 602, and the transceiver 603 may be implemented on the same chip, or may be implemented on different chips respectively. Or any two of them can be combined in one chip. The memory 602 may store program codes, and the processor 601 calls the program codes stored in the memory 602 to implement the corresponding functions of the device 600.

It should be understood that the apparatus 600 may also be used to perform other steps and/or operations on the terminal device side in the foregoing embodiments, and for brevity, details are not described herein.

As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed, the method on the terminal device side in the above method embodiment is executed.

As another form of this embodiment, a computer program product containing instructions is provided, and when the instructions are executed, the method on the terminal device side in the foregoing method embodiment is executed.

As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed, the method on the network device side in the above method embodiment is executed.

As another form of this embodiment, a computer program product containing instructions is provided, and when the instructions are executed, the method on the network device side in the foregoing method embodiment is performed.

The method disclosed in the above embodiments of the present application may be applied to a processor, or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components, can also be a system chip (system on chip, SoC), it can also be a central processor (central processor (unit), CPU, or network processor (network processor (NP), can also be a digital signal processing circuit (digital signal processor, DSP), can also be a microcontroller (micro controller (unit), MCU), can also be a programmable controller (programmable logic device (PLD) or other Integrated chip. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erasable programmable read only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (random access memory, RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous RAM, SDRAM), double data rate synchronous dynamic random access memory (double data SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct RAMbus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to these and any other suitable types of memories.

It should be understood that the term "and/or" in this article is merely an association relationship describing the associated objects, and indicates that there may be three relationships, for example, A and/or B, which may indicate: A exists alone, and A and B exist at the same time. , There are three cases of B alone. In addition, the character "/" in this article generally indicates that the related objects before and after are in an "or" relationship.

Those of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (28)

1. A method of beam management, which includes:

   The terminal device receives the first signal and enters the sleep state;

   Based on the quality strength of the first signal or the first indication information carried in the first signal, the terminal device performs beam management in the sleep state.
2. The method according to claim 1, wherein the method further comprises:

   If the terminal device does not receive the first signal before starting the first duration timer, the terminal device performs any of the following operations:

   The terminal device initiates random access; or,

   The terminal device listens to the physical downlink control channel PDCCH after the second duration timer starts, and the second duration timer has the same timing length as the first duration timer.
3. The method according to claim 1, characterized in that, based on the quality strength of the first signal, the terminal device performing beam management in the sleep state includes:

   If the value of the quality strength of the first signal is greater than or equal to the first threshold, the terminal device does not perform beam management; or

   If the value of the quality strength of the first signal is greater than the second threshold and less than the first threshold, the terminal device performs beam management in the sleep state.
4. The method according to claim 3, wherein the terminal device receives the first threshold or the second threshold from a network device.
5. The method of claim 1, wherein:

   Based on the first indication information carried in the first signal, the terminal device performing beam management in the sleep state includes:

   If the first indication information instructs the terminal device to perform beam management, the terminal device performs beam management in the sleep state;

   If the first indication information indicates that the terminal device does not perform beam management, the terminal device does not perform beam management in the sleep state.
6. The method according to any one of claims 3-5, wherein if the terminal device performs beam management in the sleep state, the method further comprises:

   The terminal device receives information indicating resources from the network device, where the resource includes a dedicated search space configured by the network device for the terminal device, or, a physical uplink shared channel PUSCH, or a physical uplink control channel PUCCH;

   The terminal device uses the resources to perform beam measurement.
7. The method according to claim 2, wherein if the terminal device does not receive the first signal before the first duration timer starts, the terminal device initiating random access includes:

   The terminal device detects the first signal before starting the second duration timer;

   If the terminal device does not receive the first signal before the second duration timer starts, the terminal device initiates random access.
8. The method according to any one of claims 2-7, wherein the first duration is a period of time in a discontinuous reception DRX cycle, and the second duration is a period in the next DRX cycle For a period of time, the DRX cycle includes a short DRX cycle and a long DRX cycle.
9. The method according to claim 8, wherein the method further comprises:

   When the first duration is a period of DRX short period, if the terminal device does not receive the first signal in N DRX short periods, the terminal device uses the DRX long period to receive the first signal ;

   The N is an integer greater than or equal to 1.
10. The method according to any one of claims 1-9, wherein the method further comprises:

    The terminal device receives the first signal again;

    If the values of the quality of the first signal received by the terminal device for the first time and the second signal received for the second time are greater than or equal to a third threshold, the terminal device does not perform beam reporting;

    If the quality strength of at least one of the first signal received by the terminal device for the first time and the second signal received for the second time is less than the third threshold, the terminal device performs beam reporting.
11. The method according to claim 10, wherein the first signal comprises a main signal, and the main signal is used to instruct the terminal device to notify the network device that the beam corresponding to the first duration is Whether the duration of a wake up has changed compared to the beam.
12. The method according to any one of claims 1-11, wherein the first signal is a wake-up signal WUS, or a sleep signal GTS.
13. A method of beam management, which includes:

    The terminal device receives the first signal and enters the sleep state;

    The terminal device performs beam management based on a first period, which is determined according to the number of receptions of the first signal.
14. The method according to claim 13, wherein the terminal device performs beam management based on the first period, including:

    Each time the terminal device receives the first signal, the count increases by 1, and when the count reaches K, the terminal device performs beam management, where K is an integer greater than 1;

    Or, each time the terminal device receives the first signal, the count is decremented from K, and when the count reaches 0, the terminal device performs beam management.
15. An apparatus for beam management is characterized in that it includes:

    The transceiver module is used to receive the first signal and enter the sleep state;

    The processing module is configured to perform beam management in the sleep state based on the quality strength of the first signal or the first indication information carried in the first signal.
16. The apparatus according to claim 15, wherein the processing module is further configured to:

    If the device does not receive the first signal before starting the first duration timer, perform any of the following operations:

    Initiate random access; or,

    Listening to the physical downlink control channel PDCCH after the second duration timer is started, the second duration timer and the first duration timer have the same timing length.
17. The apparatus according to claim 15, wherein the processing module is configured to perform beam management in the sleep state based on the quality intensity of the first signal, specifically including:

    If the value of the quality strength of the first signal is greater than or equal to the first threshold, no beam management is performed; or

    If the value of the quality strength of the first signal is greater than the second threshold and less than the first threshold, beam management is performed in the sleep state.
18. The apparatus according to claim 17, wherein the transceiver module is further configured to receive the first threshold or the second threshold from a network device.
19. The apparatus according to claim 15, wherein the processing module is configured to perform beam management in the sleep state based on the first indication information carried in the first signal, specifically including:

    If the first indication information instructs the terminal device to perform beam management, perform beam management in the sleep state;

    If the first indication information indicates that the terminal device does not perform beam management, beam management is not performed in the sleep state.
20. The device according to any one of claims 17-19, wherein if the device performs beam management in the sleep state, the transceiver module is further configured to:

    Receiving information indicating resources from a network device, the resources including a dedicated search space configured by the network device for the device, or, a physical uplink shared channel PUSCH, or a physical uplink control channel PUCCH;

    The processing module is used to perform beam measurement using the resources.
21. The device according to claim 16, wherein if the device does not receive the first signal before the first duration timer starts, the processing module is used to initiate random access, specifically including:

    Detecting the first signal before starting the second duration timer;

    If the first signal is not received before the second duration timer starts, random access is initiated.
22. The device according to any one of claims 16 to 21, wherein the first duration is a period of time in a first discontinuous reception cycle, and the second duration is the next DRX cycle In a period of time, the DRX cycle includes a DRX short cycle and a DRX long cycle.
23. The apparatus according to claim 22, wherein the transceiver module is further configured to:

    When the first duration is a period of DRX short period, if the terminal device does not receive the first signal in N DRX short periods, the terminal device uses the DRX long period to receive the first signal ;

    The N is an integer greater than or equal to 1.
24. The device according to any one of claims 15-23, wherein the transceiver module is further used to:

    Receive the first signal again;

    Among them, the processing module is used for:

    If the values of the quality of the first signal received for the first time and the second signal received for the second time are greater than or equal to a third threshold, no beam reporting is performed;

    If the quality strength of at least one of the first signal received for the first time and the second signal received for the second time is less than the third threshold, beam reporting is performed.
25. The apparatus according to any one of claims 15-24, wherein the first signal includes a main signal, and the main signal is used to instruct the apparatus to notify the network device of the first duration Whether the corresponding beam has changed compared with the beam corresponding to the last wake-up duration.
26. The device according to any one of claims 15-25, wherein the first signal is a wake-up signal WUS, or a sleep signal GTS.
27. An apparatus for beam management is characterized in that it includes:

    The transceiver module is used to receive the first signal and enter the sleep state;

    The processing module is configured to perform beam management based on a first period, which is determined according to the number of times the first signal is received.
28. The apparatus according to claim 27, wherein the processing module is used to perform beam management based on the first period, specifically including:

    Each time the transceiver module receives the first signal, the count increases by 1, and when the count reaches K, beam management is performed, where K is an integer greater than 1;

    Or, each time the transceiver module receives the first signal, the count is decremented from K, and when the count reaches 0, beam management is performed.

Images