Wireless communication method, terminal device and network device

Abstract

A wireless communication method, a terminal device and a network device are beneficial to reducing resource overhead and wakeup time delay brought by waking up a main receiver of the terminal device by the network device through a wakeup signal, the method comprising: in a first communication state, the terminal device receives downlink information by using the main receiver of the terminal device according to first information, in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, the WUS is used for waking up a main receiver of the terminal device, and the first information comprises at least one of the following items: a timer, an uplink transmission demand of the terminal device, and a downlink receiving demand of the terminal device.

Description

Wireless communication method, terminal device and network device Technical Field

[0001] The embodiments of the present application relate to the field of communications, and specifically to a wireless communication method, terminal device, and network device. Background Art

[0002] In some scenarios, to save power on terminal devices, a wake-up receiver (WUR) can be used to receive a wake-up signal (WUS) and activate the primary receiver based on the WUS's instructions. Wake-up receivers are characterized by extremely low cost, low complexity, and low power consumption. However, this mechanism for activating the primary receiver still requires further optimization.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device and network device, which are conducive to reducing the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through a wake-up signal.

[0005] In a first aspect, a method for wireless communication is provided, comprising: in a first communication state, a terminal device uses a main receiver of the terminal device to receive downlink information according to first information, and in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device, wherein the first information includes at least one of the following: a timer, an uplink transmission requirement of the terminal device, and a downlink reception requirement of the terminal device.

[0006] According to a second aspect, a method for wireless communication is provided, comprising: in a first communication state, when a terminal device sends first indication information to a network device, using a main receiver of the terminal device to receive downlink information, and in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device.

[0007] According to a third aspect, a method for wireless communication is provided, comprising: a network device sends downlink information to a terminal device in a first communication state based on first information, wherein, in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up a main receiver of the terminal device, and the downlink information is received by the terminal device using the main receiver, and the first information includes at least one of the following: a timer, an uplink transmission requirement of the terminal device, and a downlink reception requirement of the terminal device.

[0008] According to a fourth aspect, a wireless communication method is provided, comprising: receiving, by a network device, first indication information sent by a terminal device, the first indication information being sent by the terminal device in a first communication state; in the first communication state, detecting, by a wake-up receiver of the terminal device, a wake-up signal WUS, the WUS being used to wake up a main receiver of the terminal device;

[0009] The first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is turned on, or the main receiver of the terminal device is used to start receiving downlink information.

[0010] In a fifth aspect, a terminal device is provided for executing the method in any one of the first to second aspects or their respective implementations.

[0011] Specifically, the terminal device includes a functional module for executing the method in any one of the first to second aspects or their respective implementations.

[0012] In a sixth aspect, a network device is provided for executing the method in any one of the third to fourth aspects or their respective implementations.

[0013] Specifically, the network device includes a functional module for executing the method in any one of the third to fourth aspects or their respective implementations.

[0014] In a seventh aspect, a terminal device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of any one of the first to second aspects or their respective implementations.

[0015] In an eighth aspect, a network device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of any one of the third to fourth aspects or their respective implementations.

[0016] In a ninth aspect, a chip is provided for implementing the method described in any one of the first to fourth aspects or their respective implementations. Specifically, the chip includes a processor configured to retrieve and execute a computer program from a memory, causing a device equipped with the chip to perform the method described in any one of the first to fourth aspects or their respective implementations.

[0017] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method of any one of the first to fourth aspects or its various implementations.

[0018] In an eleventh aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method of any one of the first to fourth aspects or any of their implementations.

[0019] In the twelfth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the above-mentioned first to fourth aspects or their respective implementations.

[0020] Through the above technical solution, the terminal device can use the main receiver of the terminal device to receive downlink information based on the timer, at least one of the uplink transmission requirements and the downlink reception requirements, or autonomously turn on the main receiver. On the one hand, it can reduce the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through the wake-up signal. On the other hand, it enriches the start-up mechanism of the main receiver of the terminal device, and can reduce the impact of turning on the main receiver only through WUS on the communication of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0022] FIG2 is a schematic diagram showing the composition of a DRX cycle.

[0023] FIG3 is a schematic diagram showing how to instruct a terminal whether to monitor a PDCCH through an energy-saving signal.

[0024] FIG4 is a schematic diagram of a PF position within a paging DRX cycle and a PO position within a PF.

[0025] FIG5 is a schematic diagram showing how to indicate to UEs in a paging subgroup whether to receive paging by using an energy-saving signal.

[0026] FIG6 is a block diagram of a WUS-based receiver system.

[0027] FIG7 is a schematic diagram of generating a wake-up signal through OOK modulation.

[0028] FIG8 is a schematic diagram of a wireless communication method provided according to an embodiment of the present application.

[0029] FIG9 is a schematic diagram of a state of a primary receiver controlled based on a timer according to an embodiment of the present application.

[0030] FIG10 is a schematic diagram of a WUS resource according to an embodiment of the present application.

[0031] FIG11 is a schematic diagram of another wireless communication method provided according to an embodiment of the present application.

[0032] FIG12 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0033] FIG13 is a schematic block diagram of another terminal device provided according to an embodiment of the present application.

[0034] FIG14 is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0035] Figure 15 is a schematic block diagram of another network device provided according to an embodiment of the present application.

[0036] FIG16 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0037] FIG17 is a schematic block diagram of a chip provided according to an embodiment of the present application.

[0038] Figure 18 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system, cellular Internet of Things system, cellular passive Internet of Things system or other communication systems, etc.

[0041] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0042] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0043] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0044] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), 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, etc.

[0045] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a cellular Internet of Things, or a network device in a cellular passive Internet of Things, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0046] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0047] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0048] The terminal device can be a station (ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, a terminal device in a cellular Internet of Things, a terminal device in a cellular passive Internet of Things, etc.

[0049] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0050] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0051] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0052] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0053] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0054] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0055] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0056] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0057] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0058] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0059] In the embodiments of the present application, "pre-defined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

[0060] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0061] In some scenarios, in order to save energy on terminal devices, a discontinuous reception (DRX) mechanism is introduced. During each on duration, the terminal device needs to continuously detect the physical downlink control channel (PDCCH) to determine whether the base station has scheduled data transmission to it. The DRX mechanism includes configuring a DRX cycle for a UE in the Radio Resource Control (RRC) connected (RRC_CONNECTED) state. As shown in Figure 2, a DRX cycle consists of an on duration and an opportunity for DRX (Opportunity for DRX). During the on duration, the UE monitors and receives downlink channels and signals including the PDCCH; during the opportunity for DRX, the UE does not receive downlink channels and signals such as the PDCCH to reduce power consumption.

[0062] However, for most UEs, there may be no need to receive data transmission for a long time, but it is still necessary to maintain a regular wake-up mechanism to monitor possible downlink transmissions. For this type of UE, there is room for further optimization of power saving. In some scenarios, energy-saving signals are introduced for energy saving of UEs in the RRC_CONNECTED state to achieve further energy saving. The energy-saving signal is used in conjunction with the DRX mechanism, and the terminal receives an indication of the energy-saving signal before the DRX ON duration. When the terminal has data transmission in a DRX cycle, the energy-saving signal "wakes up" the terminal to monitor the PDCCH during the DRX On duration; otherwise, when the terminal has no data transmission in a DRX cycle, the energy-saving signal does not "wake up" the terminal, and the terminal does not need to monitor the PDCCH during the DRX On duration. Among them, the energy-saving signal is carried on the PDCCH channel and is carried by DCI format 2_6.

[0063] FIG3 shows a process of instructing the terminal whether to monitor the PDCCH during the DRX On Duration by using the energy-saving signal.

[0064] In some scenarios, the energy saving of the UE receiving paging messages in the RRC idle (RRC_IDLE) or RRC inactive (RRC_INACTIVE) state is optimized, and similar energy-saving signals are introduced. When receiving paging messages through DRX, there is a paging occasion (PO) within a DRX cycle. The UE only receives paging messages during the PO, and does not receive paging messages outside of the paging occasion, in order to achieve the purpose of saving power. PF indicates which system frame number the paging message should appear on, and PO indicates the time when it may appear. A PF frame may include one or more POs. For each DRX cycle or paging cycle (Paging Cycle), the UE only needs to monitor its own PO. The UE calculates its corresponding PF and the position of the PO in the PF based on its own ID. Figure 4 shows a schematic diagram of the PF position and the PO position in the PF within a paging DRX cycle.

[0065] However, in real-world scenarios, the probability of a UE being paged may be low. The UE periodically checks the PDCCH at the corresponding point of call (PO). If it fails to detect a paging indication sent to it, power is wasted. A further energy-saving signal, called Paging Early Indication (PEI), is introduced to indicate whether the UE will receive a paging PDCCH at the target PO before the target PO arrives. This energy-saving signal is carried on the PDCCH using DCI format 2_7.

[0066] As shown in FIG5 , a power saving signal indicates whether UEs in one or more paging subgroups receive paging on the corresponding PF or PO.

[0067] In some scenarios, energy conservation for UEs in the RRC_CONNECTED state continues to be enhanced, such as the introduction of an enhanced solution for search space set group switching and a solution for skipping PDCCH detection when necessary to save power, namely PDCCH skipping. Control information related to search space set group switching and PDCCH skipping is also carried on the PDCCH.

[0068] In order to further save power for the UE, in some scenarios, it is considered to introduce a wake-up receiver (WUR) to receive a wake-up signal (WUS). The wake-up receiver has the characteristics of extremely low cost, extremely low complexity and extremely low power consumption. It mainly receives the wake-up signal based on envelope detection. Therefore, the WUS received by the wake-up receiver is different from the modulation method, waveform, etc. of the signal carried by the PDCCH. The wake-up signal can be an envelope signal obtained by ASK modulation of the carrier signal. The demodulation of the envelope signal is also mainly based on the energy provided by the wireless radio frequency signal to drive the low-power circuit, so it can be passive. The wake-up receiver can also be powered by the terminal. Regardless of the power supply method, the wake-up receiver greatly reduces power consumption compared to the traditional receiver of the UE. In a specific implementation, the wake-up receiver can be combined with the UE, or it can be used as an additional module of the UE receiver, or it can be used as a wake-up function module of a UE alone.

[0069] In some implementations, a WUS-based receiver system block is shown in FIG6 , where the wake-up receiver receives a wake-up signal. If the UE needs to turn on the main receiver, the wake-up signal may instruct the UE to turn on the main receiver. Otherwise, the UE's main receiver may be in a turned-off state.

[0070] The WUR does not need to be turned on and off to save power like a traditional receiver. Instead, it can be activated by the WUS at any time and receive a wake-up signal. For example, the WUS signal used in 802.11 technology uses on-off keying (OOK) modulation. The modulation principle of OOK is to modulate the amplitude of the carrier signal to non-zero and zero values, corresponding to On and Off, respectively, to represent the information bit. OOK is also known as binary amplitude shift keying (2ASK). As shown in Figure 7, bit 1 is modulated to On and bit 0 is modulated to Off.

[0071] Waking up the UE's primary receiver through a wake-up receiver can further save power. However, if the UE's primary receiver is off, simply turning it on through a wake-up signal can affect communications. For example, the off state of the primary receiver can cause communication interruptions. Therefore, optimizing the mechanism for turning on the primary receiver is an urgent issue.

[0072] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0073] FIG8 is a schematic diagram of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG8 , the method 200 includes at least part of the following:

[0074] S210, in the first communication state, the terminal device uses the main receiver of the terminal device to receive downlink information according to the first information. In the first communication state, the wake-up receiver of the terminal device detects the wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device.

[0075] Correspondingly, the network device can send downlink information to the terminal device in the first communication state based on the first information.

[0076] In some embodiments of the present application, the method 200 further includes:

[0077] In the first communication state, the terminal device turns on the main receiver of the terminal device according to the first information.

[0078] In some embodiments, the first information may include other reasons other than detecting a WUS that trigger the terminal device to use the primary receiver (or turn on the primary receiver) for signal reception, such as urgent uplink transmission, regular downlink reception, insufficient ability to wake up the receiver to perform a specific operation, or insufficient accuracy of performing a specific operation by waking up the receiver, requiring the primary receiver to be turned on to perform the operation, etc. For example, when the primary receiver is off, the terminal device can perform certain measurements by waking up the receiver, which can assist in determining whether the primary receiver needs to be turned on for more accurate measurements.

[0079] In some embodiments, the first information includes but is not limited to at least one of the following:

[0080] Timer, uplink transmission requirements of the terminal device, and downlink reception requirements of the terminal device.

[0081] In the embodiment of the present application, the behaviors of the network device and the terminal device side are corresponding, and both have the same understanding of the status of the main receiver.

[0082] For example, the network device can send downlink information based on a timer, wherein, during the operation of the timer, the network device believes that the terminal device can use the main receiver to receive downlink information, or in other words, the main receiver of the terminal device is in the turned-on state. Correspondingly, the terminal device can use the main receiver to receive downlink information based on the timer.

[0083] For another example, the terminal device can perform uplink transmission when there is an uplink transmission demand. When the network device receives the uplink transmission, it determines that the terminal device can use the main receiver to receive downlink information or the main receiver of the terminal device is in the turned-on state. Then, the network device can send downlink information. Further, the terminal device can use the main receiver to receive the downlink information.

[0084] For another example, the network device may perform downlink transmission periodically or regularly, and correspondingly, the terminal device may use the main receiver periodically or regularly to receive the downlink transmission of the network device.

[0085] The following is an example of a terminal device using a main receiver to receive downlink information based on the first information. The behavior on the network device side corresponds to that on the terminal device side, and for the sake of brevity, it will not be repeated here.

[0086] Example 1:

[0087] In some embodiments, the terminal device may use a main receiver of the terminal device to receive downlink information based on a timer, and / or, based on a timer, turn on the main receiver of the terminal device.

[0088] Correspondingly, the network device can send downlink information to the terminal device according to the timer.

[0089] In some embodiments, the downlink information may be downlink common control information, such as system information, slot format indicator information (SFI), or downlink scheduling information.

[0090] In the related art, when the main receiver is turned off, if the terminal device has not received a wake-up signal to wake up the main receiver of the terminal device, the main receiver of the terminal device will remain in the off state. However, some communication needs require the terminal device to implement regularly, such as performing Radio Resource Management (RRM) measurements, receiving system messages, receiving downlink public control information, etc. For communication needs that need to be implemented by the main receiver, if the main receiver of the terminal device is awakened by the wake-up signal of the network device, it will bring resource overhead and wake-up delay of the wake-up signal. After waking up the main receiver, if there is no other communication demand, it is necessary to turn off the main receiver of the terminal device again through a certain mechanism, which adds some overhead. In some embodiments of the present application, the terminal device uses the main receiver of the terminal device to receive downlink information based on a timer, or turns on the main receiver of the terminal device based on a timer, which is conducive to reducing the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through the wake-up signal.

[0091] In some embodiments, the terminal device may periodically use the main receiver of the terminal device to receive downlink information based on a timer, or periodically turn on the main receiver of the terminal device based on a timer.

[0092] In some embodiments, while the timer is running, the terminal device may measure the serving cell and the neighboring cell, or receive downlink control information, such as receiving a system message.

[0093] In some embodiments, the main receiver of the terminal device may be periodically turned on for a certain length of time, that is, the main receiver of the terminal device has a certain working cycle, and works for a certain length of time in each working cycle.

[0094] For example, as shown in Figure 9, at the start of each cycle, a timer is started or restarted, and the terminal device turns on the primary receiver, or uses the primary receiver of the terminal device to receive downlink information. When the timer expires, the primary receiver is turned off, or the primary receiver of the terminal device is no longer used to receive downlink information. This timer can be used to control the duration that the terminal device's primary receiver is turned on.

[0095] In some embodiments, the activation period of the main receiver of the terminal device and the activation duration within a period can be predefined, or configured by the network device, or determined based on the detection period of the downlink information (such as the RRM measurement period).

[0096] That is, the terminal device and the network device have the same understanding of the status of the terminal device's primary receiver.

[0097] In some embodiments, the activation period of the terminal device's primary receiver can be determined based on the detection period of the WUS. For example, the activation period of the primary receiver can be N times the detection period of the WUS, where N is a positive integer. As shown in Figure 10, the terminal device's wake-up receiver can be periodically activated to receive the WUS. The time domain resources carrying the WUS can be periodic, and this period can be referred to as a duty cycle.

[0098] In some embodiments, during the operation of the timer, the main receiver of the terminal device may be kept in the on state at all times, or the terminal device may turn on the main receiver according to the detection timing of downlink reception. For example, during the operation of the timer, the main receiver is only used for downlink reception at the detection timing of downlink reception, that is, the main receiver is only turned on at the detection timing of downlink reception.

[0099] In some embodiments, based on control information from the network device, the terminal device periodically uses the primary receiver to receive downlink information according to a timer, or periodically turns on the primary receiver according to a timer. That is, the network device can control the turning on and off of the periodic turning-on mechanism of the primary receiver.

[0100] For example, the network device may carry the control information via the WUS to control whether the terminal device periodically turns on the main receiver based on a timer, or whether the terminal device periodically receives downlink information based on a timer.

[0101] For another example, the network device may carry the control information via high-layer signaling to control whether the terminal device periodically turns on the main receiver based on a timer, or whether the terminal device periodically receives downlink information based on a timer.

[0102] In some embodiments, the terminal device may stop using the main receiver of the terminal device to receive downlink information or turn off the main receiver of the terminal device according to a timer.

[0103] For example, when the timer times out, the main receiver of the terminal device is stopped from receiving downlink information or is turned off.

[0104] Embodiment 2: The terminal device uses a main receiver to receive downlink information based on uplink transmission requirements.

[0105] Correspondingly, the network device sends downlink information based on the uplink transmission requirement of the terminal device. For example, when the network device receives the uplink transmission associated with the uplink transmission requirement of the terminal device, it sends the downlink information associated with the uplink transmission.

[0106] In some embodiments, the terminal device may use a main receiver of the terminal device to receive downlink information and / or turn on the main receiver of the terminal device when there is an uplink transmission requirement.

[0107] Specifically, although the uplink transmission requirement is the transmission requirement of the terminal device, after the terminal device performs uplink transmission, it will need to receive corresponding downlink information, such as scheduling information, etc. Therefore, the terminal device can use the main receiver to receive the downlink information based on the uplink transmission requirement, that is, turn on the main receiver.

[0108] In some embodiments, the uplink transmission demand may be an uplink transmission demand triggered by a terminal device, that is, the network device cannot be aware of the uplink transmission demand. Therefore, the network device cannot wake up the main receiver of the terminal device in advance through a wake-up signal. In this case, the terminal device can autonomously turn on the main receiver of the terminal device, or exit the off state of the main receiver and use the main receiver to receive downlink information, which is conducive to reducing the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through a wake-up signal.

[0109] In some embodiments, the terminal device may also stop using the main receiver to receive downlink information, or turn off the main receiver, based on the completion status of the uplink transmission demand.

[0110] For example, when the uplink transmission associated with the uplink transmission requirement is completed, the main receiver is stopped from receiving downlink information, or the main receiver is turned off.

[0111] For another example, when the uplink transmission associated with the uplink transmission requirement is completed and there is no new communication requirement, the main receiver is stopped from receiving downlink information, or the main receiver is turned off.

[0112] In some embodiments, completing the uplink transmission associated with the uplink transmission may include the uplink transmission being successfully transmitted, for example, if no retransmission scheduling of the uplink transmission is received, the uplink transmission may be considered to be successfully transmitted, or if a new transmission scheduling of the network device is received, the uplink transmission may be considered to be successfully transmitted.

[0113] In some embodiments, the uplink transmission associated with the uplink transmission demand of the terminal device may refer to uplink transmission triggered by the terminal device, or temporary uplink transmission, emergency uplink transmission, etc., for example, including but not limited to at least one of the following:

[0114] Small Data Transmissions (SDT), random access, Scheduling Request (SR) transmission, and scheduling-free uplink transmission.

[0115] For example, for a terminal device in the RRC_IDLE state or the RRC_INACTIVE state, when there is a small data transmission requirement, the main receiver of the terminal device is used to receive downlink information, and / or the main receiver of the terminal device is turned on.

[0116] For another example, for a terminal device in the RRC_IDLE state or the RRC_INACTIVE state, when random access needs to be initiated, the main receiver of the terminal device is used to receive downlink information, and / or the main receiver of the terminal device is turned on.

[0117] For another example, for a terminal device in the RRC_CONNECTED state, when initiating an unscheduled uplink transmission, the main receiver of the terminal device is used to receive downlink information, and / or the main receiver of the terminal device is turned on.

[0118] For another example, for a terminal device in the RRC_CONNECTED state, when scheduling-based uplink transmission is required, the main receiver of the terminal device is used to receive downlink information, and / or the main receiver of the terminal device is turned on.

[0119] In some embodiments, the downlink information received by the terminal device using the main receiver and the uplink transmission associated with the uplink transmission demand of the terminal device have an associated relationship.

[0120] That is, when the terminal device has an uplink transmission requirement, the terminal device may use the main receiver to receive downlink information associated with the uplink transmission, or turn on the main receiver to receive downlink information associated with the uplink transmission.

[0121] In some embodiments, the uplink transmission is a small data transmission, and the associated downlink information includes a downlink reference signal and / or downlink scheduling information.

[0122] In some embodiments, the uplink transmission is random access, and the associated downlink information includes a downlink reference signal and / or downlink information in a random access process.

[0123] In some embodiments, the uplink transmission is SR transmission, and the associated downlink information includes downlink scheduling information.

[0124] In some embodiments, the uplink transmission is a scheduling-free uplink transmission, and the associated downlink information includes downlink scheduling information.

[0125] In some embodiments, the downlink reference signal may include but is not limited to a synchronization signal block (Synchronization Signal Block, SSB) and a channel state information reference signal (Channel State Information Reference Signal, CSI-RS).

[0126] In some embodiments, the SDT may be an SDT based on a random access procedure (SDT over RACH, RA-SDT) or an SDT based on a pre-configured resource (Configured Grant, CG) (SDT over Configured Grant, CG-SDT).

[0127] In some embodiments, the random access may be a random access triggered by RA-SDT, or it may be a random access triggered by other reasons, such as RRC connection establishment or re-establishment, switching, RRC recovery (RRC request), system information request (SI request), beam failure recovery (Beam Failure Recovery, BFR), timing advance acquisition, etc.

[0128] In some embodiments, when the SDT transmission conditions are met, the terminal device can proactively initiate SDT via RA-SDT or CG-SDT. This SDT process is not controlled by the network device, so the network device cannot preemptively wake up the terminal device's primary receiver via a wake-up signal. In this case, the terminal device can autonomously turn on the primary receiver, or in other words, exit the primary receiver's off state, to receive SDT-related downlink information, such as the SDT retransmission schedule.

[0129] In some embodiments, the random access process initiated by the terminal device is not controlled by the network device, so the network device cannot pre-awaken the terminal device's primary receiver with a wake-up signal. In this case, the terminal device can autonomously turn on the terminal device's primary receiver, or in other words, exit the primary receiver's off state, to receive downlink messages during the random access process, such as Msg2 or Msg4.

[0130] In some embodiments, since uplink services are initiated by terminal devices, the network device will only initiate reasonable scheduling after learning about the uplink service requirements. When a terminal device needs uplink transmission, it first needs to send an SR to the network device, requesting that the network device schedule uplink resources for the terminal device. The terminal device's sending of the SR is not controlled by the network device, so the network device cannot wake up the terminal device's main receiver in advance through a wake-up signal. In this case, the terminal device can autonomously turn on the terminal device's main receiver, or in other words, exit the main receiver's off state to receive downlink scheduling information from the network device.

[0131] In some embodiments, unscheduled uplink transmission may refer to the network device pre-allocating uplink transmission resources for the terminal device, and the terminal device may directly initiate uplink transmission on the pre-allocated resources according to business needs, such as uplink transmission based on CG resources. The unscheduled uplink transmission is not scheduled by the network device, so the network device cannot wake up the main receiver of the terminal device in advance through a wake-up signal. In this case, the terminal device can autonomously turn on the main receiver of the terminal device, or exit the off state of the main receiver to receive downlink information related to the unscheduled uplink transmission, such as receiving retransmission scheduling information of the unscheduled uplink transmission.

[0132] In some embodiments, the receiver and transmitter of the terminal device are usually integrated. Turning on the transmitter but not the receiver does not bring additional power savings. Therefore, when the terminal device needs to perform uplink transmission, it needs to use the transmitter, and accordingly, the main receiver of the terminal device can also be turned on.

[0133] In some embodiments, the time when the terminal device performs uplink transmission is associated with the time when the terminal device uses the main receiver to receive information, or in other words, the time when the terminal device performs uplink transmission is associated with the time when the terminal device turns on the main receiver.

[0134] For example, the main receiver of the terminal device is turned on before the terminal device performs uplink transmission.

[0135] For another example, after the terminal device performs uplink transmission, the main receiver of the terminal device is turned on.

[0136] In some specific implementations, starting from a first time before the terminal device performs an uplink transmission, a primary receiver of the terminal device is used to receive downlink information or the primary receiver of the terminal device is turned on, wherein a first duration is separated from the time when the terminal device starts performing the uplink transmission and the first time. Optionally, the first duration can be predefined or configured by the network device.

[0137] In other implementations, starting from a second time after the terminal device performs an uplink transmission, the terminal device's primary receiver is used to receive downlink information or the terminal device's primary receiver is turned on, wherein a second duration exists between the time when the terminal device completes the uplink transmission and the second time. Optionally, the second duration may be predefined or configured by the network device.

[0138] In some embodiments, in a CG-SDT scenario, the terminal device may turn on the main receiver at a first time before the start of CG-SDT, wherein the first time is separated from the start time of executing CG-SDT by a first duration. Optionally, the terminal device may measure a downlink reference signal (e.g., SSB) within the first duration to determine a downlink reference signal that meets the conditions (e.g., SSB that meets the signal quality threshold), that is, the terminal device may obtain downlink beam information for initiating CG-SDT within the first duration, and further select CG resources for SDT based on the downlink reference signal (e.g., SSB).

[0139] In some embodiments, in a CG-SDT scenario, the terminal device needs to receive scheduling information from the network device after executing CG-SDT. Therefore, the terminal device can turn on the main receiver after executing CG-SDT to receive the retransmission scheduling information or new transmission scheduling information of the CG-SDT.

[0140] In some specific implementations, after the terminal device transmits the first uplink message using CG resources, it starts the configuration authorization SDT retransmission timer (cg-SDT-RetransmissionTimer). During the operation of cg-SDT-RetransmissionTimer, the terminal device does not turn off the main receiver of the terminal device. Optionally, if during the operation of cg-SDT-RetransmissionTimer, the terminal device receives a retransmission schedule for the uplink message, the terminal device may restart the cg-SDT-RetransmissionTimer after retransmitting the uplink message, or, if the terminal device receives a new transmission schedule, the terminal device may send a new uplink message and restart the cg-SDT-RetransmissionTimer, and will not turn off the main receiver of the terminal device before the cg-SDT-RetransmissionTimer times out. Optionally, when the terminal device determines that the CG-based uplink transmission is successful, the terminal device may turn off the main receiver, or, when the uplink transmission is successful and there is no new uplink transmission, turn off the main receiver. For example, if the terminal device does not receive the retransmission schedule and new transmission schedule from the network device during the operation of cg-SDT-RetransmissionTimer, the terminal device can turn off the main receiver.

[0141] In some embodiments, for a random access scenario, the terminal device may turn on the primary receiver at a first time before the start of the random access, where the first time is separated from the start of the random access by a first duration. Optionally, the terminal device may measure a downlink reference signal (e.g., an SSB) within the first duration to determine a downlink reference signal that meets the conditions (e.g., an SSB that meets a signal quality threshold), and further select a PRACH resource for random access based on the downlink reference signal (e.g., an SSB).

[0142] In some embodiments, for a random access scenario, the terminal device may turn on a main receiver after sending the first message in the random access to receive downlink information in the random access process, such as Msg2 or Msg4.

[0143] In some embodiments, the terminal device may stop using the main receiver to receive downlink information, or turn off the main receiver after completing the random access process. Alternatively, the terminal device may stop using the main receiver to receive downlink information, or turn off the main receiver, depending on the triggering cause of the random access process. For example, when the triggering cause of the random access process is RRC connection establishment or re-establishment, the terminal device may not turn off the main receiver. This is because the RRC connection establishment is mainly to convert the RRC state of the terminal device to the RRC-CONNECTED state, thereby transmitting data. For another example, when the triggering cause of the random access process is SDT, the terminal device may turn off the main receiver after the SDT is completed.

[0144] In some embodiments, for unscheduled uplink transmission, the terminal device may start a configured grant timer (configuredGrantTimer) after performing uplink transmission through CG resources. Optionally, during the operation of configuredGrantTimer, the main receiver of the terminal device is in an on state, or in other words, the terminal device uses the main receiver to receive downlink scheduling information. Optionally, when configuredGrantTimer times out, if the terminal device does not receive a retransmission schedule for the uplink transmission and there is no new unscheduled uplink transmission, the terminal device may turn off the main receiver of the terminal device, or in other words, the terminal device stops using the main receiver to receive downlink scheduling information.

[0145] Embodiment 3: Based on downlink reception requirements, the terminal device uses a main receiver to receive downlink information and / or turns on the main receiver.

[0146] Correspondingly, the network device can send downlink information based on the downlink reception requirements of the terminal device or the downlink transmission requirements of the network device.

[0147] In some embodiments, the downlink information associated with the downlink reception requirement of the terminal device includes downlink information regularly received by the terminal device, or downlink information periodically received, such as downlink public control information and system messages.

[0148] As an example but not a limitation, the downlink common control information includes but is not limited to slot format indicator information (Slot Format Indicator, SFI).

[0149] In some embodiments, for specific downlink transmissions from a terminal device, the network device can use a wake-up signal to wake up the terminal device's primary receiver, thereby enabling reception of the downlink transmission. For some downlink common control information, such as SFI, which requires periodic acquisition by the terminal device, the terminal device can autonomously activate its primary receiver to receive the downlink common control information.

[0150] In some embodiments, the SFI information is carried through DCI format 2-0. The SFI information can simultaneously configure the time slot formats of multiple service cells. The network device configures the cell index and the position of the starting bit of the time slot format combination identifier (slotFormatCombinationId) corresponding to the cell index in DCI format 2-0 through radio resource control (RRC) signaling. The network device configures multiple time slot format combinations (slotFormatCombination), each time slot format combination corresponds to an identification information (slotFormatCombinationId) and a time slot format configuration of a group of time slots, and each time slot format configuration is used to configure the time slot format of a time slot. The SFI information includes an SFI index (SFI-index), which corresponds to the slotFormatCombinationId, and a group of time slot formats can be determined according to the SFI index. The time slot format indicated by the SFI information is applicable to multiple consecutive time slots starting from the time slot carrying the SFI signaling, and the number of time slots indicated by the SFI is greater than or equal to the monitoring period of the PDCCH carrying the SFI.

[0151] In some embodiments, the downlink common control information is received using a main receiver of the terminal device according to a detection timing of the downlink common control information.

[0152] For example, the downlink common control information is received using the main receiver of the terminal device at the detection timing of the downlink common control information, or the downlink common control information is received using the main receiver of the terminal device before the detection timing of the downlink common control information.

[0153] In some embodiments, the main receiver of the terminal device is turned on according to the detection timing of the downlink public control information.

[0154] For example, when detecting downlink public control information, the main receiver of the terminal device is turned on.

[0155] For example, since it takes a certain amount of time from when the main receiver is turned on to when the main receiver is ready to receive downlink public control information (this period of time is also called the wake-up time of the main receiver), the main receiver of the terminal device can be turned on before the detection time of the downlink public control information.

[0156] In some embodiments, the downlink common control information is detected periodically, and the terminal device may periodically use the main receiver of the terminal device to receive the downlink common control information, or periodically turn on the main receiver of the terminal device.

[0157] For example, the activation period of the main receiver is determined according to the detection period of the downlink public control information (for example, the activation period of the main receiver is an integer multiple of the detection period of the downlink public control information), and / or the activation duration of the main receiver is determined according to the duration of the detection opportunity of the downlink public control information.

[0158] In a specific example, the activation period of the primary receiver can be determined according to the detection period of the PDCCH carrying the SFI, for example, an integer multiple of the PDCCH detection period, and the activation duration is the duration of the PDCCH monitoring opportunity.

[0159] In some embodiments, the terminal device may also stop using the main receiver to receive downlink information, or turn off the main receiver, based on the completion of the downlink reception requirement.

[0160] For example, when the uplink reception associated with the downlink reception requirement is completed, the main receiver is stopped from receiving downlink information, or the main receiver is turned off.

[0161] For another example, when the downlink reception associated with the downlink reception requirement is completed, the main receiver is stopped from receiving downlink information, or the main receiver is turned off.

[0162] For another example, when the downlink reception associated with the downlink reception requirement is completed and there is no new transmission requirement, the main receiver is stopped from receiving downlink information, or the main receiver is turned off.

[0163] It should be understood that in the embodiments of the present application, the above-mentioned embodiments 1 to 3 can be implemented separately or in combination, and the present application does not limit this. For example, when a primary receiver is used to receive downlink information based on a timer, and the timer is determined according to the detection period of the downlink common control information, it can be understood that the terminal device uses the primary receiver to receive the downlink common control information according to the reception requirement of the downlink common control information.

[0164] It should be understood that in the embodiment of the present application, the terminal device may also stop using the main receiver of the terminal device to receive downlink information, or turn off the main receiver based on the indication information or timer of the network device.

[0165] For example, when the indication information of the network device is received or the timer times out, the main receiver of the terminal device is stopped from being used to receive downlink information, or the main receiver is turned off, wherein the indication information is used to indicate to fall back to the first communication state (i.e., fall back to the main receiver awakened based on WUS) or stop using the main receiver of the terminal device or turn off the main receiver of the terminal device.

[0166] In some embodiments, the indication information of the network device may be explicit indication information or implicit indication information. This application does not limit the specific indication method.

[0167] In some embodiments of the present application, the method 200 further includes:

[0168] The terminal device sends first indication information to the network device;

[0169] Correspondingly, the network device receives first indication information from the terminal device, wherein the first indication information is used to indicate a change in the communication state of the terminal device, or a change in the state of the main receiver.

[0170] For example, the first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is turned on, or the main receiver of the terminal device is started to receive downlink information.

[0171] Therefore, in an embodiment of the present application, in the first communication state, when the terminal device determines to use the primary receiver to receive downlink information based on the first information, or turns on the primary receiver, it can send first indication information to the network device to notify the network device of the current communication state of the terminal device, thereby ensuring that the terminal device and the network device have a consistent understanding of the communication state. Furthermore, the network device can communicate with the terminal device without waking up the terminal device's primary receiver through a wake-up signal.

[0172] In some embodiments, for a terminal device in the RRC-CONNECTED state, the network device may be notified of the current communication state of the terminal device via first indication information.

[0173] In some embodiments, the first indication information is sent via uplink signaling, which may be, for example, a physical uplink control channel (PUCCH). Optionally, the first indication information may further include activation duration information of the primary receiver.

[0174] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0175] In some embodiments, the main receiver of the terminal device may be sent before sending the first indication information, or may be sent after sending the first indication information.

[0176] In summary, in the embodiments of the present application, the terminal device can use the main receiver of the terminal device to receive downlink information based on a timer, uplink transmission requirements or downlink reception requirements, or autonomously turn on the main receiver. On the one hand, it can reduce the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through a wake-up signal. On the other hand, it enriches the start-up mechanism of the main receiver of the terminal device, and can reduce the impact of turning on the main receiver only through WUS on the communication of the terminal device.

[0177] FIG11 is a schematic diagram of a wireless communication method 300 according to an embodiment of the present application. As shown in FIG11 , the method 300 includes at least part of the following:

[0178] S310, in the first communication state, when the terminal device sends the first indication information to the network device, the main receiver of the terminal device is used to receive downlink information and / or turn on the main receiver of the terminal device. In the first communication state, the wake-up receiver of the terminal device detects the wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device.

[0179] In some embodiments, the main receiver of the terminal device may be sent before sending the first indication information, or may be sent after sending the first indication information.

[0180] In some embodiments, the first indication information is used to indicate a change in the communication state of the terminal device, or a change in the state of the primary receiver. For example, the first indication information is used to indicate exiting the first communication state, or turning on the primary receiver of the terminal device, or starting to use the primary receiver of the terminal device to receive downlink information.

[0181] It should be understood that method 300 does not limit the reason why the terminal device turns on the main receiver or uses the main receiver to receive downlink information in the first communication state. For example, it may be the triggering reason in method 200, such as based on a timer, or based on the uplink transmission requirements and downlink reception requirements of the terminal device. Alternatively, when the main receiver is in the off state, the receiver may be woken up to perform certain measurements to assist in determining whether to turn on the main receiver and perform more accurate measurements.

[0182] Therefore, in an embodiment of the present application, the terminal device can autonomously turn on the main receiver or autonomously use the main receiver to receive downlink information, and notify the network device of the communication status of the terminal device (or the status of the main receiver), thereby ensuring that the terminal device and the network device have a consistent understanding of the communication status of the terminal device, facilitating the network device's scheduling of the terminal device.

[0183] In some embodiments, the first indication information is sent via uplink signaling, which may be, for example, a physical uplink control channel (PUCCH). Optionally, the first indication information may further include activation duration information of the primary receiver.

[0184] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0185] In some embodiments of the present application, the method 300 further includes:

[0186] According to the timer and / or the reception of downlink information, the main receiver of the terminal device is stopped from receiving downlink information and / or the main receiver is turned off. Correspondingly, the network device can send downlink information to the terminal device according to the timer.

[0187] For example, when the timer times out, the main receiver of the terminal device stops being used to receive downlink information and / or the main receiver is turned off.

[0188] For another example, when the downlink information is received successfully, the main receiver of the terminal device is stopped from receiving the downlink information and / or the main receiver is turned off.

[0189] For another example, when downlink information is received successfully and there is no new communication demand, the main receiver of the terminal device is stopped from receiving downlink information and / or is turned off.

[0190] In some implementations, determining whether to stop using a primary receiver of the terminal device to receive downlink information based on a timer and / or a reception status of downlink information includes:

[0191] When sending the first indication information to the network device, start a first timer;

[0192] When the first timer times out, stop using the main receiver of the terminal device to receive downlink information and / or turn off the main receiver.

[0193] In some implementations, stopping using a primary receiver of the terminal device to receive downlink information based on a timer and / or a reception status of downlink information includes:

[0194] When receiving downlink control information DCI of the network device, starting a second timer;

[0195] If no DCI is received before the second timer runs, stop using the main receiver of the terminal device to receive downlink information and / or turn off the main receiver.

[0196] In a specific example, when the network device receives the first indication information, it can be informed that the terminal device has turned on the main receiver. Therefore, DCI can be sent to the terminal device. The DCI is used to carry scheduling information. Each time the terminal device receives DCI, it starts or restarts the second timer. If no new DCI is received before the second timer expires, the terminal device stops using the main receiver to receive downlink information and / or turns off the main receiver when the second timer times out.

[0197] In summary, in the embodiments of the present application, the terminal device can autonomously turn on the main receiver or autonomously use the main receiver to receive downlink information, and notify the network device of the communication status of the terminal device, thereby ensuring that the terminal device and the network device have a consistent understanding of the communication status of the terminal device. On the one hand, it can reduce the resource overhead and wake-up delay caused by the network device waking up the main receiver of the terminal device through a wake-up signal. On the other hand, it enriches the startup mechanism of the main receiver of the terminal device, and can reduce the impact of only turning on the main receiver through WUS on the communication of the terminal device.

[0198] The above text, in combination with Figures 8 to 11, describes in detail the method embodiment of the present application. The following text, in combination with Figures 12 to 18, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0199] FIG12 shows a schematic block diagram of a terminal device 1000 according to an embodiment of the present application. As shown in FIG12 , the terminal device 1000 includes:

[0200] The communication unit 1010 is configured to, in a first communication state, use a main receiver of the terminal device to receive downlink information according to first information, wherein in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device, wherein the first information includes at least one of the following:

[0201] Timer, uplink transmission requirements of the terminal device, and downlink reception requirements of the terminal device.

[0202] In some embodiments, the terminal device further includes:

[0203] A processing unit is configured to start a main receiver of the terminal device according to the first information in the first communication state.

[0204] In some embodiments, the uplink transmission associated with the uplink transmission requirement of the terminal device includes at least one of the following:

[0205] Small data transmission, random access, scheduling request SR transmission, and scheduling-free uplink transmission.

[0206] In some embodiments, the uplink transmission and the downlink information are associated.

[0207] In some embodiments, the uplink transmission is small data transmission, and the downlink information includes a downlink reference signal and / or downlink scheduling information.

[0208] In some embodiments, the uplink transmission is random access, and the downlink information includes a downlink reference signal and / or downlink information in a random access process.

[0209] In some embodiments, the uplink transmission is SR transmission, and the downlink information includes downlink scheduling information.

[0210] In some embodiments, the uplink transmission is scheduling-free uplink transmission, and the downlink information includes downlink scheduling information.

[0211] In some embodiments, the downlink reception requirement of the terminal device includes receiving downlink public control information.

[0212] In some embodiments, the downlink common control information includes time slot format indication information.

[0213] In some embodiments, the communication unit 1010 is further configured to:

[0214] The downlink common control information is received by using a primary receiver of the terminal device according to a detection timing of the downlink common control information.

[0215] In some embodiments, the terminal device further includes:

[0216] A processing unit is used to turn on the main receiver of the terminal device according to the detection timing of the downlink public control information.

[0217] In some embodiments, the downlink public control information is periodically detected, the activation period of the primary receiver is determined according to the detection period of the downlink public control information, and / or the activation duration of the primary receiver is determined according to the duration of the detection opportunity of the downlink public control information.

[0218] In some embodiments, the communication unit 1010 is further configured to:

[0219] According to the timer, the main receiver of the terminal device is periodically used to receive downlink information.

[0220] In some embodiments, the communication unit 1010 is further configured to:

[0221] Based on the control information of the network device, the main receiver of the terminal device is used to receive downlink information periodically according to the timer.

[0222] In some embodiments, the terminal device further includes:

[0223] A processing unit is used to periodically turn on the main receiver of the terminal device according to the timer.

[0224] In some embodiments, the communication unit 1010 is further configured to:

[0225] Sending first indication information to the network device, where the first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is in the turned-on state, or starting to use the main receiver of the terminal device to receive downlink information.

[0226] In some embodiments, the first indication information is sent via a physical uplink control channel PUCCH.

[0227] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0228] In some embodiments, the communication unit 1010 is further configured to:

[0229] When the first condition is met, stopping using the main receiver of the terminal device to receive downlink information;

[0230] The first condition includes at least one of the following:

[0231] The timer times out, the uplink transmission associated with the uplink transmission requirement of the terminal device is completed, the downlink reception associated with the downlink reception requirement of the terminal device is completed, and the indication information of the network device is received, and the indication information is used to instruct to fall back to the first communication state or stop using the main receiver of the terminal device or turn off the main receiver of the terminal device.

[0232] In some embodiments, the terminal device further includes:

[0233] a processing unit, configured to shut down a main receiver of the terminal device when a first condition is met;

[0234] The first condition includes at least one of the following:

[0235] The timer times out, the uplink transmission associated with the uplink transmission requirement of the terminal device is completed, the downlink reception associated with the downlink reception requirement of the terminal device is completed, and the indication information of the network device is received, and the indication information is used to instruct to fall back to the first communication state or stop using the main receiver of the terminal device or turn off the main receiver of the terminal device.

[0236] Optionally, in some embodiments, the receiving unit may be a communication interface or a receiver, or an input / output interface of a communication chip or a system on chip.

[0237] It should be understood that the terminal device 1000 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 1000 are respectively for realizing the corresponding processes of the terminal device in the method shown in Figures 8 to 10. For the sake of brevity, they will not be repeated here.

[0238] FIG13 shows a schematic block diagram of a terminal device 1100 according to an embodiment of the present application. As shown in FIG13 , the terminal device 1100 includes:

[0239] The communication unit 1110 is used to use the main receiver of the terminal device to receive downlink information in a first communication state when the terminal device sends a first indication information to the network device. In the first communication state, the wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device.

[0240] In some embodiments, the first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is turned on, or the main receiver of the terminal device is started to receive downlink information.

[0241] In some embodiments, the first indication information is sent via a physical uplink control channel PUCCH.

[0242] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0243] In some embodiments, the communication unit 1110 is further configured to:

[0244] According to the timer and / or the reception status of the downlink information, stop using the main receiver of the terminal device to receive the downlink information.

[0245] In some embodiments, the terminal device further includes:

[0246] a processing unit, configured to start a first timer when sending the first indication information to the network device;

[0247] In some embodiments, the communication unit 1110 is further configured to:

[0248] When the first timer times out, stop using the main receiver of the terminal device to receive downlink information.

[0249] In some embodiments, the terminal device further includes:

[0250] a processing unit, configured to start a second timer when receiving downlink control information DCI of a network device;

[0251] In some embodiments, the communication unit 1110 is further configured to:

[0252] If no DCI is received before the second timer runs, stop using the main receiver of the terminal device to receive downlink information.

[0253] In some embodiments, the communication unit 1110 is further configured to:

[0254] According to the timer and / or the reception status of downlink information, the main receiver of the terminal device is turned off.

[0255] In some embodiments, the terminal device further includes:

[0256] a processing unit, configured to start a first timer when sending the first indication information to the network device;

[0257] When the first timer times out, the main receiver of the terminal device is turned off.

[0258] In some embodiments, the terminal device further includes:

[0259] a processing unit, configured to start a second timer when receiving downlink control information DCI of a network device;

[0260] If no DCI is received before the second timer runs, the main receiver of the terminal device is turned off. Optionally, in some embodiments, the receiving unit may be a communication interface or receiver, or an input / output interface of a communication chip or a system on chip.

[0261] It should be understood that the terminal device 1100 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 1100 are respectively for realizing the corresponding processes of the terminal device in the method shown in Figure 11. For the sake of brevity, they will not be repeated here.

[0262] FIG14 shows a schematic block diagram of a network device 1200 according to an embodiment of the present application. As shown in FIG14 , the network device 1200 includes:

[0263] The communication unit 1210 is configured to send downlink information to a terminal device in a first communication state based on first information, wherein in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up a main receiver of the terminal device. The downlink information is received by the terminal device using the main receiver, and the first information includes at least one of the following:

[0264] Timer, uplink transmission requirements of the terminal device, and downlink reception requirements of the terminal device.

[0265] In some embodiments, the uplink transmission associated with the uplink transmission requirement of the terminal device includes at least one of the following:

[0266] Small data transmission, random access, scheduling request SR transmission, and scheduling-free uplink transmission.

[0267] In some embodiments, the uplink transmission and the downlink information are associated.

[0268] In some embodiments, the downlink reception requirement of the terminal device includes receiving downlink public control information.

[0269] In some embodiments, the downlink common control information includes time slot format indication information.

[0270] In some embodiments, the communication unit 1210 is further configured to:

[0271] Receive the first indication information sent by the terminal device, where the first indication information is used to instruct the terminal device to exit the first communication state, or the main receiver of the terminal device is in the turned-on state, or to start using the main receiver of the terminal device to receive downlink information.

[0272] In some embodiments, the first indication information is sent via a physical uplink control channel PUCCH.

[0273] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0274] Optionally, in some embodiments, the receiving unit may be a communication interface or a receiver, or an input / output interface of a communication chip or a system on chip.

[0275] It should be understood that the network device 1200 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 1200 are respectively for realizing the corresponding processes of the network device in the method shown in Figures 8 to 10. For the sake of brevity, they will not be repeated here.

[0276] FIG15 shows a schematic block diagram of a network device 1300 according to an embodiment of the present application. As shown in FIG15 , the network device 1300 includes:

[0277] a communication unit 1310 configured to receive first indication information sent by a terminal device, where the first indication information is sent by the terminal device in a first communication state, where a wake-up receiver of the terminal device detects a wake-up signal WUS, where the WUS is used to wake up a main receiver of the terminal device;

[0278] The first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is turned on, or the main receiver of the terminal device is used to start receiving downlink information.

[0279] In some embodiments, the first indication information is sent via a physical uplink control channel PUCCH.

[0280] In some embodiments, the first indication information is sent by configuring authorized CG resources.

[0281] In some embodiments, the communication unit 1310 is further configured to:

[0282] According to the timer, downlink scheduling information is sent to the terminal device.

[0283] Optionally, in some embodiments, the sending unit may be a communication interface or a transmitter, or an input / output interface of a communication chip or a system on chip.

[0284] It should be understood that the network device 1300 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 500 are respectively for implementing the corresponding processes of the network device in the method shown in Figure 11. For the sake of brevity, they will not be repeated here.

[0285] Figure 16 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in Figure 16 includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0286] Optionally, as shown in FIG16 , the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0287] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0288] Optionally, as shown in FIG16 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0289] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

[0290] Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0291] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0292] Figure 17 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in Figure 17 includes a processor 710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0293] Optionally, as shown in FIG17 , the chip 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0294] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0295] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0296] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0297] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0298] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0299] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0300] FIG18 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG18 , the communication system 900 includes a terminal device 910 and a network device 920 .

[0301] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0302] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. 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.

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

[0304] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0305] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0306] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0307] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0308] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0309] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0310] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0311] The embodiment of the present application also provides a computer program.

[0312] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0313] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0314] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0315] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0316] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0317] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

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

[0319] 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 this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0320] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for wireless communication, characterized in that, including: In a first communication state, the terminal device receives downlink information using the main receiver of the terminal device according to first information. In the first communication state, the wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device. Wherein, the first information includes at least one of the following: a timer, the uplink transmission requirement of the terminal device, and the downlink reception requirement of the terminal device.

2. The method according to claim 1, characterized in that, The method further includes: In the first communication state, according to the first information, turn on the main receiver of the terminal device.

3. The method according to claim 1 or 2, characterized in that, The uplink transmission associated with the uplink transmission requirement of the terminal device includes at least one of the following: small data transmission, random access, scheduling request SR transmission, and grant-free uplink transmission.

4. The method according to claim 3, wherein There is an association relationship between the uplink transmission and the downlink information.

5. The method according to claim 4, characterized in that The uplink transmission is small data transmission, and the downlink information includes downlink reference signals and / or downlink scheduling information.

6. The method according to claim 4, characterized in that, The uplink transmission is random access, and the downlink information includes downlink reference signals and / or downlink information during the random access process.

7. The method according to claim 4, wherein The uplink transmission is SR transmission, and the downlink information includes downlink scheduling information.

8. The method according to claim 4, wherein The uplink transmission is grant-free uplink transmission, and the downlink information includes downlink scheduling information.

9. The method according to any one of claims 1-8, characterized in that, The downlink reception requirement of the terminal device includes receiving downlink common control information.

10. The method according to claim 9, characterized in that, The downlink common control information includes time slot format indication information.

11. The method according to claim 9 or 10, characterized in that, The terminal device receives downlink information using the main receiver of the terminal device according to first information, including: According to the detection timing of the downlink common control information, use the main receiver of the terminal device to receive the downlink common control information.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: According to the detection timing of the downlink common control information, turn on the main receiver of the terminal device.

13. The method according to claim 12, wherein The downlink common control information is detected periodically, the opening period of the main receiver is determined according to the detection period of the downlink common control information, and / or the opening duration of the main receiver is determined according to the duration of the detection timing of the downlink common control information.

14. The method according to claim 1, characterized in that, The terminal device receives downlink information using the main receiver of the terminal device according to first information, including Periodically use the main receiver of the terminal device to receive downlink information according to the timer.

15. The method according to claim 14, wherein The periodically using the main receiver of the terminal device to receive downlink information according to the timer includes: Based on the control information of the network device, periodically use the main receiver of the terminal device to receive downlink information according to the timer.

16. The method according to claim 1, 14 or 15, characterized in that, The method further includes: Periodically turn on the main receiver of the terminal device according to the timer.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: The terminal device sends first indication information to the network device, and the first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is in an on state, or starting to use the main receiver of the terminal device to receive downlink information.

18. The method according to claim 17, characterized in that, The first indication information is sent through a physical uplink control channel PUCCH.

19. The method according to claim 17 or 18, characterized in that, The first indication information is sent through a configured grant CG resource.

20. The method according to any one of claims 1-19, characterized in that, The method further includes: When the first condition is met, stop using the main receiver of the terminal device to receive downlink information; Among them, the first condition includes at least one of the following: The timer expires, the uplink transmission associated with the uplink transmission requirement of the terminal device is completed, the downlink reception associated with the downlink reception requirement of the terminal device is completed, the indication information sent by the network device is received, and the indication information is used to indicate a fallback to the first communication state or stop using the main receiver of the terminal device or turn off the main receiver of the terminal device. The method further includes:

21. The method according to any one of claims 1-20, characterized in that, When the first condition is met, turn off the main receiver of the terminal device; Among them, the first condition includes at least one of the following: The timer expires, the uplink transmission associated with the uplink transmission requirement of the terminal device is completed, the downlink reception associated with the downlink reception requirement of the terminal device is completed, the indication information sent by the network device is received, and the indication information is used to indicate a fallback to the first communication state or stop using the main receiver of the terminal device or turn off the main receiver of the terminal device. It includes:

22. A method for wireless communication, characterized in that, In the first communication state, when the terminal device sends the first indication information to the network device, use the main receiver of the terminal device to receive downlink information. In the first communication state, the wake-up receiver of the terminal device detects the wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device. The first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is in the on state, or start using the main receiver of the terminal device to receive downlink information.

23. The method according to claim 22, wherein The first indication information is sent through the physical uplink control channel PUCCH.

24. The method according to claim 22 or 23, characterized in that, The first indication information is sent through the configured grant CG resource.

25. The method according to any one of claims 22 - 24, characterized in that, The method further includes:

26. The method according to any one of claims 22-25, characterized in that, Stop using the main receiver of the terminal device to receive downlink information according to the timer and / or the reception situation of downlink information. Determining whether to stop using the main receiver of the terminal device to receive downlink information according to the timer and / or the reception situation of downlink information includes:

27. The method according to claim 26, wherein When sending the first indication information to the network device, start the first timer; When the first timer expires, stop using the main receiver of the terminal device to receive downlink information. Stopping using the main receiver of the terminal device to receive downlink information according to the timer and / or the reception situation of downlink information includes:

28. The method according to claim 26, wherein When receiving the downlink control information DCI of the network device, start the second timer; If DCI has not been received before the second timer runs, stop using the main receiver of the terminal device to receive downlink information. The method further includes:

29. The method according to any one of claims 22-28, characterized in that, Turn off the main receiver of the terminal device according to the timer and / or the reception situation of downlink information. Turning off the main receiver of the terminal device according to the timer and / or the reception situation of downlink information includes:

30. The method according to claim 29, wherein When sending the first indication information to the network device, start the first timer; When the first timer expires, turn off the main receiver of the terminal device. ​ 31. The method according to any one of claims 22-30, characterized in that, Turning off the main receiver of the terminal device according to the timer and / or the reception of downlink information includes: When receiving downlink control information DCI from a network device, start a second timer; If DCI has not been received before the second timer runs, turn off the main receiver of the terminal device.

32. A method for wireless communication, characterized in that, It includes: The network device sends downlink information to the terminal device in the first communication state according to the first information. In the first communication state, the wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device. The downlink information is received by the terminal device using the main receiver. The first information includes at least one of the following: A timer, the uplink transmission requirement of the terminal device, and the downlink reception requirement of the terminal device.

33. The method according to claim 32, wherein The uplink transmission associated with the uplink transmission requirement of the terminal device includes at least one of the following: Small data transmission, random access, scheduling request SR transmission, and grant-free uplink transmission.

34. The method according to claim 33, characterized in that, There is an association relationship between the uplink transmission and the downlink information.

35. The method according to any one of claims 32 - 34, characterized in that, The downlink reception requirement of the terminal device includes receiving downlink common control information.

36. The method according to claim 35, characterized in that, The downlink common control information includes time slot format indication information.

37. The method according to any one of claims 32 - 36, characterized in that, The method further includes: The network device receives first indication information sent by the terminal device. The first indication information is used to indicate that the terminal device exits the first communication state, or the main receiver of the terminal device is in an on state, or starts to receive downlink information using the main receiver of the terminal device.

38. The method according to claim 37, wherein The first indication information is sent through a physical uplink control channel PUCCH.

39. The method according to claim 37 or 38, characterized in that, The first indication information is sent through a configured grant CG resource.

40. A method for wireless communication, characterized in that, It includes: The network device receives first indication information sent by the terminal device. The first indication information is sent by the terminal device in the first communication state. In the first communication state, the wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device; wherein, the first indication information is used to indicate exiting the first communication state, or the main receiver of the terminal device is in an on state, or starts to receive downlink information using the main receiver of the terminal device.

41. The method according to claim 40, wherein, The first indication information is sent through a physical uplink control channel PUCCH.

42. The method according to claim 40 or 41, characterized in that, The first indication information is sent through a configured grant CG resource.

43. The method according to any one of claims 40 - 42, characterized in that, The method further includes: Sending downlink scheduling information to the terminal device according to the timer.

44. A terminal device, characterized in that, It includes: A communication unit, configured to, in the first communication state, receive downlink information using the main receiver of the terminal device according to the first information. In the first communication state, the wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the main receiver of the terminal device. The first information includes at least one of the following: A timer, the uplink transmission requirement of the terminal device, and the downlink reception requirement of the terminal device.

45. A terminal device, characterized in that, It includes: A communication unit, configured to, in a first communication state, when a first indication message is sent from a terminal device to a network device, receive downlink information using a primary receiver of the terminal device; in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the primary receiver of the terminal device.

46. A network device, characterized in that, Comprising: A communication unit, configured to send downlink information to a terminal device in a first communication state according to first information, where, in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, the WUS is used to wake up the primary receiver of the terminal device, the downlink information is received by the terminal device using the primary receiver, and the first information includes at least one of the following: A timer, an uplink transmission requirement of the terminal device, and a downlink reception requirement of the terminal device.

47. A network device, characterized in that, Comprising: A communication unit, configured to receive a first indication message sent by a terminal device, where the first indication message is sent by the terminal device in a first communication state, and in the first communication state, a wake-up receiver of the terminal device detects a wake-up signal WUS, and the WUS is used to wake up the primary receiver of the terminal device; wherein the first indication message is used to indicate exiting the first communication state, or the primary receiver of the terminal device is in an on state, or starting to receive downlink information using the primary receiver of the terminal device.

48. A terminal device, characterized in that, Comprising: A processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 21, or the method according to any one of claims 22 to 31.

49. A network device, characterized in that, Comprising: A processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 32 to 39, or the method according to any one of claims 40 to 43.

50. A chip, characterized in that, Comprising: A processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 21, or the method according to any one of claims 22 to 31, or the method according to any one of claims 32 to 39, or the method according to any one of claims 40 to 43.

51. A computer-readable storage medium, characterized in that, For storing a computer program, where the computer program causes a computer to execute the method according to any one of claims 1 to 21, or the method according to any one of claims 22 to 31, or the method according to any one of claims 32 to 39, or the method according to any one of claims 40 to 43.

52. A computer program product, characterized in that, Including computer program instructions, where the computer program instructions cause a computer to execute the method according to any one of claims 1 to 21, or the method according to any one of claims 22 to 31, or the method according to any one of claims 32 to 39, or the method according to any one of claims 40 to 43.

53. A computer program, characterized in that, The computer program causes the computer to execute the method according to any one of claims 1 to 21, or the method according to any one of claims 22 to 31, or the method according to any one of claims 32 to 39, or the method according to any one of claims 40 to 43.

Images