Methods for node for wireless communication, and apparatus

Abstract

Provided are methods for a node for wireless communication, and an apparatus. A method comprises: a first node determining a monitoring occasion of a wake-up signal; when the first node receives a first wake-up signal, the first node starting a first timer at a first moment; and the first node monitoring a subsequent wake-up signal within a time window in which a time domain overlap occurs between the monitoring occasion and the running time of the first timer.

Description

Methods and apparatus for nodes used in wireless communication

[0001] This application claims priority to Chinese patent application 202510125711.X, filed on January 27, 2025, entitled “Method and Apparatus in a Node for Wireless Communication”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a method and apparatus for use in a node for wireless communication. Background Technology

[0003] The 5G New Radio (NR) standard introduced discontinuous reception (DRX) technology to save power consumption in terminal devices. To further reduce power consumption, a low-power receiver (LR) was introduced to receive a low-power wake-up signal (LP-WUS). However, how LP-WUS is transmitted and how terminal devices listen for it are issues that need to be considered after its introduction. Summary of the Invention

[0004] This application provides a method and apparatus for use in a node for wireless communication. The various aspects of this application will be described below.

[0005] In a first aspect, a method for a first node in wireless communication is provided, comprising: determining a listening time for a wake-up signal; starting a first timer at a first moment when a first wake-up signal is received; and listening for subsequent wake-up signals within a time window in which the listening time and the running time of the first timer overlap in the time domain.

[0006] The beneficial effects of this method embodiment are as follows: by utilizing the characteristic of data arriving in clusters, when the second node configures the first node to listen for non-continuous or continuous wake-up signals, the first node triggers the execution of the first timer upon receiving the first wake-up signal. The first node monitors subsequent wake-up signals within the time window in which the execution time of the first timer overlaps with the listening opportunity. When the first timer expires, the current listening cycle no longer listens, which helps to reduce the duration of listening for wake-up signals and further reduce power consumption.

[0007] In a second aspect, a method for a second node in wireless communication is provided, comprising: determining a listening time for a wake-up signal; sending a first wake-up signal; the first wake-up signal being used to trigger a first node to start a first timer at a first moment; and listening for subsequent wake-up signals within a time window in which the running time of the first timer overlaps with the listening time in the time domain.

[0008] The beneficial effects of this method embodiment are as follows: the second node can take advantage of the characteristic of data arriving in clusters to configure the first node to listen for non-continuous or continuous wake-up signals. When the first node receives the first wake-up signal, it triggers the execution of the first timer. During the time window in which the execution time of the first timer and the listening opportunity overlap, the node monitors subsequent wake-up signals. When the first timer expires, the current listening cycle will no longer listen, which helps to reduce the duration of listening for wake-up signals and further reduce power consumption.

[0009] Thirdly, a method for a first node in wireless communication is provided, comprising: determining the listening timing of a wake-up signal and configuration information of discontinuous reception periods of varying lengths; determining the corresponding PDCCH detection timing based on the type of the currently assigned discontinuous reception period; and listening to the wake-up signal within the listening timing of the wake-up signal associated with the corresponding PDCCH detection timing.

[0010] In one possible embodiment, the method further includes: determining the current assigned discontinuous reception short period when the discontinuous reception short period timer times out; and determining the current assigned discontinuous reception long period when the discontinuous reception short period timer starts at least twice and does not time out.

[0011] In another possible embodiment, the conditions for starting or restarting the discontinuous reception short-cycle timer satisfy at least one of the following:

[0012] Received wake-up signal;

[0013] Data is received within a discontinuous reception time window or within a discontinuous reception time extension window;

[0014] The scheduling information is received within the discontinuous reception time window or within the discontinuous reception time extension window;

[0015] Stop MR monitoring of PDCCH;

[0016] Upon receiving scheduling information, or upon receiving a notification to stop listening, the scheduling information triggers the inactivation of a timer.

[0017] In other possible embodiments, the time to start or restart the discontinuous reception short-cycle timer is any of the following:

[0018] The moment the wake-up signal is received;

[0019] The moment the scheduling information is received;

[0020] The moment when MR stops listening to PDCCH;

[0021] The moment when a wake-up signal is received and MR listening to the PDCCH stops;

[0022] The moment when the wake-up signal is received and the scheduling information is received;

[0023] The wake-up signal is received, and subsequently, scheduling information is received, and the scheduling information triggers the inactivation of the timer timeout or the stop listening notification is received.

[0024] The beneficial effect of this method embodiment is that it clarifies the assistance method for listening to the long and short periods of discontinuous reception and the timing of wake-up signals, so that the first node can effectively reduce the listening time and save power consumption.

[0025] Fourthly, a method is provided for a second node in wireless communication, comprising: determining the timing of listening for a wake-up signal and configuration information for receiving discontinuous long and short periods; and sending a wake-up signal.

[0026] In one possible embodiment, the method further includes: determining the current assigned discontinuous reception short period when the discontinuous reception short period timer times out; and determining the current assigned discontinuous reception long period when the discontinuous reception short period timer starts at least twice and does not time out.

[0027] In another possible embodiment, the conditions for starting or restarting the discontinuous reception short-cycle timer satisfy at least one of the following:

[0028] Received wake-up signal;

[0029] Data is received within a discontinuous reception time window or within a discontinuous reception time extension window;

[0030] The scheduling information is received within the discontinuous reception time window or within the discontinuous reception time extension window;

[0031] Stop MR monitoring of PDCCH;

[0032] Upon receiving scheduling information, or upon receiving a notification to stop listening, the scheduling information triggers the inactivation of a timer.

[0033] In other possible embodiments, the time to start or restart the discontinuous reception short-cycle timer is any of the following:

[0034] The moment the wake-up signal is received;

[0035] The moment the scheduling information is received;

[0036] The moment when MR stops listening to PDCCH;

[0037] The moment when a wake-up signal is received and MR listening to the PDCCH stops;

[0038] The moment when the wake-up signal is received and the scheduling information is received;

[0039] The wake-up signal is received, and subsequently, scheduling information is received, and the scheduling information triggers the inactivation of the timer timeout or the stop listening notification is received.

[0040] The beneficial effect of this method embodiment is that it clarifies the assistance method for listening to the long and short periods of discontinuous reception and the timing of wake-up signals, so that the first node can effectively reduce the listening time and save power consumption.

[0041] Fifthly, a first node for wireless communication is provided, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the first node to perform the method as described in the first or third aspect.

[0042] A sixth aspect provides a second node for wireless communication, comprising a transceiver, a memory, and a processor, wherein the memory stores a program, the processor invokes the program in the memory, and controls the transceiver to receive or transmit signals to cause the second node to perform the method as described in the second or fourth aspect.

[0043] In a seventh aspect, embodiments of this application provide a communication system including the aforementioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or second node as described in the embodiments of this application.

[0044] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0045] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0046] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects. Attached Figure Description

[0047] Figure 1 is a system architecture example diagram of a wireless communication system that can be applied to the embodiments of this application.

[0048] Figure 2 is a schematic diagram of a network architecture applicable to embodiments of this application.

[0049] Figures 3A and 3B are schematic diagrams of wireless protocol stack structures applicable to embodiments of this application.

[0050] Figures 4A and 4B are schematic diagrams of the DRX mechanism applicable to embodiments of this application.

[0051] Figure 5A is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.

[0052] Figure 5B is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.

[0053] Figure 5C is a schematic diagram of another possible structure of the low-power wake-up module applicable to the embodiments of this application.

[0054] Figure 6 is a flowchart illustrating a method for a first node in wireless communication according to an embodiment of this application.

[0055] Figure 7 is a flowchart illustrating a method for a first node and a second node in wireless communication according to an embodiment of this application.

[0056] Figure 8 shows an example of the methods illustrated in Figures 6 and 7.

[0057] Figure 9 shows another example of the methods illustrated in Figures 6 and 7.

[0058] Figure 10 shows another example of the methods illustrated in Figures 6 and 7.

[0059] Figure 11 is a schematic diagram of the implementation method of extended timer.

[0060] Figure 12 is a flowchart illustrating another method for a first node in wireless communication provided in an embodiment of this application.

[0061] Figure 13 is a schematic diagram illustrating the cooperation between the DRX mechanism and the LP-WUS mechanism.

[0062] Figure 14 is a schematic diagram of the structure of a first node for wireless communication provided in an embodiment of this application.

[0063] Figure 15 is a schematic diagram of the structure of a second node for wireless communication provided in an embodiment of this application.

[0064] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0065] Figure 17 is a schematic diagram of the hardware module of the communication device provided in the embodiment of this application. Detailed Implementation

[0066] Communication system architecture

[0067] The wireless communication system of this application embodiment may include a network device and a terminal device. The network device may be a device that communicates with the terminal device. The network device may provide communication coverage for a specific geographical area and may communicate with terminal devices located within that coverage area.

[0068] Figure 1 exemplarily illustrates a wireless communication system 100 including a network device 110 and multiple terminal devices, such as terminal devices 120a to 120j in the figure. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area; this application embodiment does not limit this.

[0069] Optionally, the wireless communication system may also include other network entities such as a network controller and a mobility management entity, which is not limited in this application embodiment.

[0070] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th-generation (5G) systems or new radio (NR) systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, advanced long-term evolution (LTE-A) systems, enhanced 5G (5G advanced) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th-generation (6G) mobile communication systems, satellite communication systems, etc.

[0071] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal device in the embodiments of this application may be a mobile phone, tablet computer, laptop computer, handheld computer, camera equipment, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Optionally, the terminal device may be used to act as a base station. For example, the terminal device may act as a scheduling entity, providing sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D) connections. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices can communicate without relaying communication signals through base stations.

[0072] The network device in this application embodiment can be a device for communicating with terminal devices. This network device can also be called an access network device or a radio access network device, such as a base station (BS). In this application embodiment, the network device can refer to a radio access network (RAN) node or a next-generation RAN (NG-RAN) node (or device) that connects user equipment to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, transmitting and receiving node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0073] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0074] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0075] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0076] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0077] Figure 2 illustrates a schematic diagram of a network architecture 200 according to an embodiment of this application. This network architecture 200 describes the network architecture of a 5G NR / LTE / LTE-A system, which can also be referred to as a 5G system (5GS) / evolved packet system (EPS) network architecture. The network architecture 200 includes at least one of the following: network device 110, terminal device 120, 5G core network (5GC) / evolved packet core (EPC) 210, home subscriber server (HSS) / unified data management (UDM) 220, and Internet service 230. The network device and terminal device in Figure 2 are illustrated using RAN and UE as examples, respectively.

[0078] As shown in Figure 2, network device 110 provides user plane and control plane protocol termination to terminal device 120. Network device 110 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes a mobility management entity (MME) / authentication management field (AMF) / session management function (SMF) 211, other MMEs / AMFs / SMFs 214, a service gateway (S-GW) / user plane function (UPF) 212, and a packet data network gateway (P-GW) / UPF 213. MME / AMF / SMF 211 is the control node that handles signaling between terminal device 120 and 5GC / EPC 210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF212, which is itself connected to the P-GW / UPF213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-compliant Internet Protocol services, specifically including the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched streaming services. It is evident that network architecture 200 provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented herein can be extended to networks providing circuit-switched services or other cellular networks.

[0079] Figures 3A and 3B respectively illustrate a schematic diagram of a wireless protocol stack structure according to an embodiment of this application. Figures 3A and 3B use a 5G wireless protocol stack as an example for illustration. The 5G wireless protocol stack is divided into two planes: the user plane (UP) protocol stack and the control plane (CP) protocol stack. The user plane protocol stack is the protocol suite used for user data transmission, and the control plane protocol stack is the protocol suite used for control signaling transmission in the 5G system. The specific names of each protocol stack layer are as follows:

[0080] As shown in Figure 3A, the user plane protocol stack includes, from top to bottom, the following layers: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer.

[0081] As shown in Figure 3B, the control plane protocol stack includes, from top to bottom: non-access stratum (NAS); radio resource control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0082] It should be understood that the different layers in the above protocol stack have different functions, and they work together through inter-layer interaction to achieve communication between terminal devices and network devices. With the development of artificial intelligence technology, AI-assisted computing has permeated the processing implementation methods of the above protocol stack. For example, the scheduling algorithm of the MAC layer and the encoding / decoding algorithm of the PHY layer can apply artificial intelligence algorithms to improve the performance of communication algorithms.

[0083] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the first node in this application.

[0084] As an example, the wireless protocol architecture in Figures 3A and 3B is applicable to the second node in this application.

[0085] It should be understood that some functionalities in a wireless protocol architecture can also be implemented in one or more devices. For example, the functions of different layers in the control plane protocol stack can be implemented by multiple nodes on the network side.

[0086] It should be understood that the interpretation of the terminology in the embodiments of this application may refer to the TS36, TS37 and TS38 series of specifications of the 3rd generation partnership project (3GPP), but may also refer to the specifications of the Institute of Electrical and Electronics Engineers (IEEE).

[0087] To facilitate understanding, some technical terms used in the embodiments of this application will be explained below:

[0088] 1) Low-power wake-up module and main communication module

[0089] Terminal devices can use a separate low-power wake-up module to receive wake-up signals. The wake-up signal received by the terminal device using this low-power wake-up module can be called a low-power wake-up signal (LPWUS).

[0090] This low-power wake-up module can be implemented using a simple, single small circuit or chip with low power consumption. This low-power wake-up module can be referred to as a wake-up radio (WUR), a wake-up circuit, or simply LR, or a low-power wake-up receiver (LP-WUR), etc. This application does not limit its naming. For ease of explanation, it will be uniformly described as a low-power wake-up module below. Furthermore, for ease of explanation, the signal received by the terminal device using the low-power wake-up module will be referred to as the wake-up signal.

[0091] The main communication module of a terminal device can also be called the main radio (MR) or main receiver. When the MR is woken up, the terminal device can enter the radio resource control (RRC) connected state. For example, when the terminal device is idle, it can turn off the main communication module or put it into deep sleep mode, listening to the LP-WUS via the LP-WUR, thereby reducing the power consumption of the terminal device. As another example, for a terminal device in connected state, it can run either MR or LR.

[0092] 2) On-off keying (OOK) modulation

[0093] To reduce power consumption in the wake-up circuit, LP-WUS can employ OOK modulation, and the corresponding wake-up circuit can use envelope detection to receive the wake-up signal. When using OOK modulation, each (encoded) bit corresponds to a symbol (also called a chip). When the bit is 1, a signal is emitted within the symbol length (i.e., the signal power within the symbol length is not 0), which can be conveniently referred to as the ON signal. Conversely, when the bit is 0, no signal is emitted within the symbol length (i.e., the signal power within the symbol length is 0), which can be conveniently referred to as the OFF signal.

[0094] 5G NR systems employ OFDM modulation, and network equipment in 5G NR systems can transmit signals modulated by orthogonal frequency division multiplexing (OFDM). To ensure compatibility with 5G NR systems as much as possible, the aforementioned OOK signal can be implemented using an OFDM-modulated transmitter. One possibility is that the length of an OOK symbol can be the same as the length of an OFDM symbol. In this case, when an ON signal of one symbol length is needed, the transmitter sends a specific signal, making its contour within the symbol length resemble a square wave as closely as possible. When an OFF signal is needed, the transmitter turns off the signal for one symbol length. Another possibility is that an OFDM transmitter can transmit multiple OOK symbols within the length of one OFDM symbol, thus shortening the OOK symbol length and allowing more OOK symbols to be transmitted in the same amount of time, thereby increasing the data rate.

[0095] 3) Frequency Shift Keying (FSK) Modulation

[0096] LP-WUS can also use FSK modulation. When using FSK modulation, different information uses different frequency resources. For example, 2FSK can carry 1 bit of information. When the information bit is 0, the information can be transmitted on frequency resource f0 and not on frequency resource f1; when the information bit is 1, the information can be transmitted on frequency resource f1 and not on frequency resource f0.

[0097] FSK can also support higher modulation orders to carry more information. For example, 4FSK can carry 2 bits of information. When the information bit is 00, information can be transmitted on frequency resource f0, and not on frequency resources f1, f2, and f3; when the information bit is 01, information can be transmitted on frequency resource f1, and not on frequency resources f0, f2, and f3; when the information bit is 10, information can be transmitted on frequency resource f2, and not on frequency resources f0, f1, and f3; when the information bit is 11, information can be transmitted on frequency resource f3, and not on frequency resources f0, f1, and f2. Similarly, the receiving end can compare the power levels on multiple frequency resources to determine what information is being transmitted.

[0098] 4) Discontinuous reception (DRX)

[0099] The DRX mechanism allows terminal devices to periodically enter sleep mode for certain periods, thereby saving power consumption. Terminal devices in radio resource control (RRC) connected mode use connected discontinuous reception (C-DRX).

[0100] For example, a DRX cycle includes a "wake-up time (DRXON)" portion and a "sleep time (DRXOFF)" portion. During the wake-up time, the terminal device listens for and receives the physical downlink control channel (PDCCH); during the sleep time, the terminal device has the opportunity to not listen for or receive the PDCCH to reduce power consumption. Specifically, the DRX mechanism includes a persistent timer (onDurationTimer or drx-onDurationTimer), as shown in Figure 4A. At the beginning of each DRX cycle (i.e., the beginning of the onDuration phase of each DRX cycle), the terminal device needs to start the drx-onDurationTimer. When the drx-onDurationTimer times out, it indicates that the "onDuration" phase has ended, and the terminal device enters the "Opportunity for DRX" phase. The DRX mechanism also includes a deactivation timer (InactivityTimer or drx-InactivityTimer), as shown in Figure 4B. Each time the terminal device receives a DCI that schedules a new data packet, it starts / restarts the drx-InactivityTimer. The runtime of both drx-OnDurationTimer and drx-InactivityTimer is referred to as the Active Time. During the Active Time, the terminal device monitors the PDCCH, receives the Channel State Information Reference Signal (CSI-RS), provides CSI feedback, and sends a Sounding Reference Signal (SRS). In this embodiment, outside of the Active Time, the terminal device does not monitor the PDCCH, does not provide periodic CSI feedback or semi-persistent CSI feedback, and does not send periodic SRS or semi-persistent SRS. The C-DRX cycle length, the drx-OnDurationTimer length, and the drx-InactivityTimer length are all configured by the network device for the terminal device.

[0101] In addition, network devices can also configure other DRX parameters for terminal devices, such as short DRX cycle and long DRX cycle.

[0102] In the DRX mechanism, a long DRX cycle can be configured as the default, while a short DRX cycle can be configured as an option. For terminal devices configured with a short DRX cycle, the conversion between long and short DRX cycles can be achieved in the following way:

[0103] Generally, a terminal device uses a short DRX cycle when any of the following conditions are met: 1. During the operation of the shortDRX cycle timer;

[0104] Generally, a terminal device uses a long DRX cycle when any of the following conditions are met: 1. The short DRX cycle timer (Drx-shortCycleTimer) times out; 2. The terminal device receives a long DRX command MCA CE (long DRX command MAC 20CE).

[0105] In some embodiments, LP-WUS can support bandwidths of 5MHz-20MHz. When LP-WUS is embedded in a related communication system, the main communication module (or MR) and the low-power wake-up module (LP-WUR or LR) on the terminal device side can be two modules or integrated together as a single module. LP-WUR can support various receiver architectures. The following description uses the three receiver architectures shown in Figures 5A to 5C as examples to illustrate LP-WUR.

[0106] Figure 5A is a schematic diagram of an LP-WUR based on radio frequency (RF) envelope detection. The receiver architecture shown in Figure 5A includes a matching network 2001, an RF bandpass filter (BPF) 2002, an RF low noise amplifier (LNA) 2003, an RF envelope detector 2004, a baseband (BB) asymmetric processing (AMP) 2005, a BB low pass filter (LPF) 2006, a 1-bit or multi-bit analog-to-digital converter (ADC) 2007, and digital BB processing 2008.

[0107] In the architecture shown in Figure 5A, the RF signal is directly converted into a baseband signal via an RF envelope detector. Relatively low power consumption can be achieved due to the absence of a local oscillator (LO) and phase-locked loop (PLL). Optionally, the architecture may include a 1-bit or multi-bit ADC, an RF LNA and / or a BB AMP, a high-Q matching network and / or an RF BPF and / or a BB LPF. Optionally, to support multiple frequency bands and / or carriers, multiple high-Q matching networks and / or RF BPFs or multiple off-chip components may be required to suppress adjacent channel interference or interference from conventional NR signals and / or other LP WUS from adjacent subcarriers, and to support frequency band and / or carrier tuning.

[0108] Figure 5B shows a schematic architecture of an LP-WUR based on heterodyne architecture with intermediate frequency (IF) envelope detection. The receiver architecture shown in Figure 5B includes a matching network 3001, an RF BPF 3002, an RFLNA 3003, a mixer 3004, a receiver-over-frequency (LO) 3005, an IF AMP 3006, an IF BPF 3007, an IF envelope detector 3008, a BB AMP 3009, a BB LPF 3010, a 1-bit or multi-bit ADC 3011, and a digital BB processor 3012.

[0109] In the architecture shown in Figure 5B, the RF signal is converted to an intermediate frequency (IF) signal by an RF mixer with a LO. The IF signal is then converted to a baseband signal via IF envelope detection. Depending on the design, there may be one or more IF stages, achieving lower power consumption by relaxing the accuracy and stability requirements of the LO. This architecture can employ a 1-bit or multi-bit ADC. A high-Q matching network and / or an RF BPF and / or an IF BPF (and / or a BB LPF) can be used to suppress adjacent channel interference or interference from conventional NR signals and / or other LP WUS from adjacent subcarriers. Optionally, the architecture can incorporate components to improve sensitivity, such as an RF LNA and / or an IF AMP and / or a BB AMP. Optionally, the architecture can achieve band and / or carrier tuning by tuning the LO frequency.

[0110] Figure 5C shows a schematic architecture of an LP-WUR based on a homodyne or zero-IF architecture with baseband (BB) envelope detection. The receiver architecture shown in Figure 5C includes a matching network 4001, an RF BPF 4002, an RFLNA 4003, a mixer 4004, a receiver-on-a-band (LO) 4005, a BB AMP 4006, a BB LPF / BPF 4007, a 1-bit or multi-bit ADC 4008, and a digital BB processor 4009.

[0111] In the architecture shown in Figure 5C, band and / or carrier tuning can be achieved by tuning the LO frequency. Using a BB BPF / LPF instead of a high-Q matched network and / or an RF BPF allows for more effective and simpler suppression of adjacent channel interference or interference from conventional NR signals and / or other LP WUS on adjacent subcarriers. An RF LNA can be applied to improve sensitivity. Baseband envelope detection (not shown in the figure) can be performed in the analog domain (before the ADC) or the digital domain (after the ADC).

[0112] The preceding text, with reference to Figures 5A to 5C, introduced various LP-WUR architectures. All LP-WUR architectures are applicable to on-off keying (OOK) modulation. Some architectures are also applicable to other modulations, such as frequency-shift keying (FSK).

[0113] The preceding text introduced various LP-WUR architectures and LP-WUS generation methods. When network devices send LP-WUS, how the LP-WUS is transmitted and how the LP-WUR in the terminal device receives it are issues that need to be addressed. Furthermore, during PDCCH monitoring, the DRX and LP-WUS mechanisms are two energy-saving mechanisms; how to coordinate these two mechanisms is also a problem that needs to be considered.

[0114] Based on this, this application proposes a method for wireless communication. To further save power consumption when receiving LP-WUS, the first node determines the listening time of LP-WUS. When the first node receives the first LP-WUS, it triggers the first node to receive subsequent LP-WUS during the operation of the first timer, so that the first node does not receive LP-WUS at other times in the current cycle, thereby achieving greater power saving gain.

[0115] For ease of understanding, the method for wireless communication according to an embodiment of this application is described below with reference to FIG6. FIG6 is a schematic flowchart of the method for wireless communication in the first node according to an embodiment of this application. FIG6 is described from the perspective of the first node.

[0116] As an example, the first node can be a network-controlled repeater (NCR).

[0117] As an example, the first node can be a terminal device. For example, terminal devices 120a to 120j shown in Figure 1. The second node can be a network device. For example, the second node is an access network device or a core network device. Another example is a gNB. Yet another example is an LMF. The following embodiments are basically illustrated with the UE as the first node and the gNB as the second node.

[0118] As an example, the first node can be a relay, such as a relay terminal.

[0119] As an example, the first node can be any type of network device, such as network device 110 shown in Figure 1.

[0120] In some embodiments, the first node may be in a connected state.

[0121] The method shown in Figure 6 may include steps S600 to S640, which are described below.

[0122] In S610, the first node determines when to listen for the wake-up signal.

[0123] In one possible embodiment, the first node, according to the protocol, determines the zeroth preset duration before the wake-up time (DRXON) as the timing for listening to the wake-up signal. The value of the zeroth preset duration is set according to actual needs.

[0124] In another possible embodiment, the first node can determine the timing for listening to the wake-up signal based on configuration information from the second node. For example, the second node can send first information to the first node, which directly or indirectly indicates the timing for listening to the wake-up signal.

[0125] For example, the first information includes at least one of the following parameters: the long listening period of the wake-up signal, the short listening period of the wake-up signal, the time offset of the wake-up signal, or the continuous listening duration of the wake-up signal. The first node calculates the LPWUS listening timing based on these parameters.

[0126] In some embodiments, the first information may be RRC parameters, and the first information may be carried in RRC signaling or other control signaling.

[0127] As an example, the number of listeners required for a wake-up signal can be determined based on higher-level configuration. Multiple listeners can be used to send at least one wake-up signal. In some embodiments, multiple listeners can repetition a single wake-up signal. In some embodiments, multiple listeners can each send multiple wake-up signals.

[0128] The following explanation uses LP-WUS as an example to illustrate the concept.

[0129] In step S620, when the first node receives the first wake-up signal, it starts the first timer at the first moment.

[0130] In some embodiments, in addition to receiving the first LP-WUS, the triggering condition for the first node to start the first timer also includes at least one of the following: a. receiving scheduling information within a first set duration after listening to the first LP-WUS; b. receiving scheduling information within a second set duration after the end of the listening time corresponding to the first LP-WUS. The values ​​of the first set duration and the second set duration are set according to actual needs. The values ​​of different set durations can be the same or different.

[0131] In some embodiments, the first moment is any of the following: a. the moment when the first LP-WUS is received; b. the moment when the scheduling information is received; c. the moment when MR listening to PDCCH is stopped.

[0132] In some embodiments, the timing duration of the first timer may be greater than or equal to one LP-WUS short cycle and less than or equal to one LP-WUS long cycle.

[0133] In some embodiments, the LP-WUS listening timing can be multiple non-contiguous time windows in the LP-WUS cycle (as shown in Figure 8 below), or the LP-WUS listening timing can be consecutive time windows in the LP-WUS cycle (as shown in Figure 9 below).

[0134] In some embodiments, a single LP-WUS indicates one or more carriers. When a UE receives a single LP-WUS, it can listen to the PDCCH on one or more carriers. The mapping between LP-WUS and carriers can be configured by the RRC to determine which carriers the UE listens to on, or the mapping between LP-WUS and carriers can be indicated by the LP-WUS.

[0135] In some embodiments, the first node can receive the first LP-WUS via the LP-WUR, thus the LP-WUR is active. In some embodiments, the LP-WUR can be used only to receive the LP-WUS, thereby reducing the power consumption of the first node.

[0136] In some embodiments, the first LP-WUS is used to wake up the MR in the first node. It should be understood that since the LP-WUS can be independent of the first node, the MR being woken up can also be referred to as the first node being woken up. The MR is in a closed state before receiving the first LP-WUS. The first node can determine whether to wake up the MR based on the first LP-WUS. In some embodiments, the first LP-WUS can also be used to wake up other modules in the first node besides the MR.

[0137] In step S630, the wake-up signal is listened for within the time window in which the listening timing and the running time of the first timer overlap in the time domain.

[0138] In some embodiments, during the operation of the first timer, the wake-up signal is listened for according to the listening timing corresponding to the short listening cycle.

[0139] In some embodiments, during the operation of the first timer, the wake-up signal is listened for according to the listening timing corresponding to the long listening period.

[0140] In some embodiments, after the first timer expires, the first node stops listening to subsequent LP-WUS until the LP-WUS listening period corresponding to the next LP-WUS listening opportunity. For example, after the first timer expires, the first node stops listening to subsequent LP-WUS until the next LP-WUS listening long period arrives, and the first node starts listening to LP-WUS within the listening opportunity of that listening long period.

[0141] In some embodiments, after the first timer expires, the first node listens to LP-WUS at a lower frequency. For example, after switching from a short listening period to a long listening period of LP-WUS, the first node listens to LP-WUS during the listening time corresponding to the long listening period of LP-WUS.

[0142] In some embodiments, if a trigger event for restarting the first timer occurs during the operation of the first timer, the first timer is restarted again.

[0143] In some embodiments, the triggering conditions for restarting the first timer include at least one of the following: a. The first node receives LP-WUS; b. Schedule information is received within a set duration after LP-WUS is detected; c. Schedule information is received within a certain duration after the end of the listening time corresponding to LP-WUS is detected; d. MR stops listening to PDCCH. It should be understood that the first node may stop listening to PDCCH on its own, or the base station may notify the first node to stop listening to PDCCH. The specific notification may be a MAC CE or DCI, or it may be another type of signal received by the LR, such as OOK.

[0144] In some embodiments, the timing for the first node to restart the first timer includes at least one of the following: a. when LP-WUS is received; b. when scheduling information is received; c. when MR stops listening to PDCCH.

[0145] Optionally, the conditions for starting / restarting the first timer and the timing for starting / restarting the first timer can be configured independently. For example, when the first node's MR stops listening to the PDCCH, it decides to start or restart the first timer. The timing for starting or restarting the first timer could be receiving the LP-WUS. In this case, the first node would trace back to the moment it received the LP-WUS as the start or restart time of the first timer.

[0146] The method for wireless communication according to an embodiment of this application is described below with reference to Figure 7. Figure 7 is a schematic flowchart of the method in the first node for wireless communication according to an embodiment of this application. Figure 7 is described from the perspective of the interaction between the first node and the second node.

[0147] The method shown in Figure 7 may include steps S700 to S750, which are described below.

[0148] In the S700, the second node determines when to listen for the wake-up signal.

[0149] In one possible embodiment, the second node may determine the timing of listening for the wake-up signal according to the protocol agreement.

[0150] In another possible embodiment, the second node may send configuration parameters to the first node so that the first node can determine when to listen for the wake-up signal.

[0151] In S710, the second node sends the first message to the first node.

[0152] For example, the first information includes at least one of the following parameters: the long listening period of the wake-up signal, the short listening period of the wake-up signal, the time offset of the wake-up signal, or the continuous listening duration of the wake-up signal. The first node calculates the LPWUS listening timing based on these parameters. Other examples can be found above.

[0153] In the S720, the first node determines the timing for listening to the wake-up signal based on the first information received.

[0154] In the S730, the second node sends a first wake-up signal to the first node.

[0155] In the S740, the first timer is started at the first moment.

[0156] In the S750, subsequent wake-up signals are monitored within a time window in which the wake-up timing overlaps with the runtime of the first timer.

[0157] For specific examples of S720, S730 and S750 mentioned above, please refer to the description corresponding to Figure 6 above, which will not be repeated here.

[0158] For ease of understanding, the above method will be explained in detail below with reference to the three embodiments shown in Figures 8 to 10.

[0159] As shown in Figure 8, the base station configures several non-continuous LP-WUS listening opportunities for the UE. Specifically, the base station configures four parameters for the UE: the long period of LP-WUS listening, the short period of LP-WUS listening, the time offset, and the continuous listening duration of LP-WUS. The UE can calculate the LP-WUS listening opportunities based on these four parameters. As shown in Figure 8, the listening opportunities include listening opportunity 1, listening opportunity 2, listening opportunity 3, listening opportunity 4, and listening opportunity 5, which are shown in the boxes in Figure 8.

[0160] When the UE detects the first LP-WUS at time t0 of listening time 1, or detects uplink / downlink scheduling information indicated by DCI, it starts timer 1. During the operation of timer 1 (from time t0 to time t1), the UE listens for subsequent LP-WUS within the configured LP-WUS listening time (as shown in listening time 2 and listening time 3 in Figure 8) (i.e., listens for LP-WUS at a shorter listening period (higher frequency)). In a possible embodiment, if an event to restart timer 1 occurs during the operation of timer 1, timer 1 is restarted. After timer 1 expires, the UE listens for LP-WUS at a lower frequency. Specifically, the UE listens for LP-WUS at listening time 5 corresponding to a longer LP-WUS listening period, and does not listen for LP-WUS at listening time 4. In the above process, the conditions and times for the UE to start / restart timer 1 are the same as in the above embodiment, and will not be repeated here.

[0161] In the embodiment shown in Figure 8, the UE temporarily stops listening to LP-WUS by triggering a "Timer 1 timeout" until the next LP-WUS listening opportunity corresponding to the next long listening period. Alternatively, the base station can notify the UE to pause LP-WUS listening until the next LP-WUS listening opportunity corresponding to the next long listening period. This way, the UE does not need to receive LP-WUS during certain time periods, achieving greater power saving gains.

[0162] As shown in Figure 9, the base station configures continuous LP-WUS listening time for the UE. Specifically, the base station configures two parameters for the UE: the LP-WUS listening long period and the time offset. Alternatively, the base station can configure the time offset to be 0, configuring only the LP-WUS listening long period. The UE starts listening to LP-WUS by default from the beginning of a listening long period. Upon detecting the first LP-WUS, timer 2 is started. During the operation of timer 2 (from time t0' to time t1'), the UE will stop listening to LP-WUS for the remaining time period within the current listening long period under the following two conditions:

[0163] The first scenario: The base station notifies the UE to stop listening to LP-WUS. For example, the specific notification could be MACCE or DCI, or it could be another type of signal received by the LR, such as OOK.

[0164] The second scenario: After timer 2 times out, the remaining time period within the long monitoring cycle will stop monitoring LP-WUS.

[0165] It should be understood that the conditions for starting / restarting timer 2 are the same as those for starting / restarting the first timer described earlier, and will not be repeated here. The times for starting / restarting timer 2 are the same as those for starting / restarting the first timer described earlier, and will not be repeated here.

[0166] The difference from the embodiment shown in Figure 8 is that the embodiment shown in Figure 9 allows the UE to stop listening to LP-WUS for the remaining time period of this long listening cycle, thereby achieving greater power saving gains.

[0167] In another embodiment, in addition to stopping LP-WUS monitoring for the remaining time period of the current long monitoring cycle, the UE can also stop monitoring LP-WUS during the middle period of a long monitoring cycle. Specifically, during the time window in which the runtime of the first timer and the runtime of the second timer overlap in the time domain, the monitoring of the wake-up signal is paused; wherein the duration of the second timer is shorter than the duration of the first timer.

[0168] In some possible embodiments, the third timer times out to trigger the start of the second timer, wherein:

[0169] The triggering conditions of the third timer include: receiving scheduling information within a first set duration after the first wake-up signal is detected; receiving scheduling information within a second set duration after the end of the listening time corresponding to the first wake-up signal; and stopping MR listening to PDCCH.

[0170] The third timer is started at any of the following times: when the first wake-up signal is received; when the scheduling information is received; or when MR listening to PDCCH is stopped.

[0171] As shown in Figure 10, the base station configures a long LP-WUS listening period for the UE. First, the UE starts listening to LP-WUS by default from the beginning of a long listening period. Upon detecting the first LP-WUS, timer 2 is started. Under the following two conditions, the UE stops listening to LP-WUS for the remaining time period within the current long listening period.

[0172] Scenario A: Explicit indication; for example, the base station notifies the UE to "pause LP-WUS listening for 12 milliseconds," and the UE resumes LP-WUS listening after 12 milliseconds. Alternatively, the base station may notify the UE to "pause LP-WUS listening from SFN=010 to SFN=020," in which case the UE pauses LP-WUS listening and resumes listening from SFN=021. The specific notification can be MACCE or DCI, or it can be another type of signal received by the LP-WUS, such as OOK.

[0173] Scenario B: Timer Control: The base station configures the start conditions and start time of Timer 3 (also known as the second timer) for the UE to trigger the suspension of LP-WUS monitoring. Additionally, the duration of Timer 3 is configured. When the UE determines that the start conditions of Timer 3 are met, it starts Timer 3, and during the operation of Timer 3, LP-WUS monitoring is suspended. After Timer 3 expires, the UE resumes LP-WUS monitoring. In other words, LP-WUS monitoring is suspended during the time window when the execution times of Timer 2 and Timer 3 overlap.

[0174] In some possible embodiments, the condition for starting timer 3 can be one of the following options: define a new timer 3* (also known as the third timer), and start timer 3 when timer 3* times out. The start / restart conditions of timer 3* are similar to those of the first timer; the start / restart timing of timer 3* is similar to that of the first timer, and will not be repeated here.

[0175] As shown in Figure 10, the UE can stop listening to LP-WUS during the middle and end periods of a long listening period, thereby reducing the duration of LP-WUS listening and further reducing UE power consumption. It should be understood that in one possible embodiment, the UE can also stop listening to LP-WUS only during the middle period of a long listening period; further examples will not be provided here.

[0176] In the embodiments shown in Figures 8 to 10 above, after the UE detects LP-WUS, it starts a dedicated timer, also known as a new timer (or drx-onDurationTimer). The time window of the new timer is called the onDuration window. During the operation of the new timer, the UE listens to the PDCCH.

[0177] In some embodiments, since uplink and downlink data (e.g., uplink resource scheduling or downlink data scheduling) are typically generated in clusters, if the amount of data to be transmitted is too large, it may not be possible to transmit all of it during the operation of the dedicated timer used for PDCCH monitoring. In this case, the first node still needs to continue monitoring the PDCCH until all the data to be transmitted is completed. To address this, this embodiment introduces a new extended timer (EX-Timer).

[0178] In this embodiment, the EX-Timer functions similarly to the inactive timer in the DRX mechanism. When the dedicated timer for PDCCH detection expires, the UE starts the EX-Timer. During the EX-Timer's operation, the UE continues to detect the PDCCH. When the EX-Timer expires and no other timer prompts the UE to detect the PDCCH, the UE stops detecting the PDCCH. In this embodiment, the EX-Timer allows the base station and UE to extend the time window for PDCCH detection, enabling the transmission of more pending data. Optionally, the EX-Timer can be restarted multiple times. Each time the UE receives scheduling information, it starts or restarts the EX-Timer. In special cases, the UE can even continuously detect the PDCCH until the next onDuration window arrives.

[0179] In some embodiments, the value of EX-Timer is configured by the base station or specified by the protocol.

[0180] In some embodiments, a single EX-Timer value or multiple EX-Timer values ​​can be used for the same UE. "Using multiple EX-Timer values" as described here means configuring multiple values ​​simultaneously, with different values ​​used in different situations. For example, each set of DRX configuration parameters corresponds to a single EX-Timer value for the reception timing.

[0181] In some embodiments, when the value of EX-Timer is configured by the base station, the base station can directly configure the specific value of EX-Timer, or it can configure a coefficient k. After the UE obtains the value of k, it considers "k × Inactive Timer value" to be the value of EX-Timer.

[0182] In some embodiments, if the UE uses multiple EX-Timer values, the size of the specific EX-Timer used may be associated with at least one of the following factors:

[0183] Factor A: DCI indicates the scheduling direction: uplink / downlink uses different EX-Timer values.

[0184] Factor B: The type of DCI, i.e., different DCI types such as DCI0-0, DCI0-1, DCI1-0, DCI1-1, etc., correspond to different EX-Timer values.

[0185] Factor C: Downlink Data Indicated by DCI: If DCI schedules downlink, the different LCH data in the data packets of the downlink transport block (TB) correspond to different EX-Timer values. The UE can map different EX-Timer values ​​based on the LCH corresponding to multiple MAC SDUs in the TB, and then select the longest / shortest EX-Timer value for use. In this case, the UE can only determine the EX-Timer value after parsing the TB, but the EX-Timer's start time must be traced back to the time of receiving the DCI.

[0186] For example, in the example shown in Figure 11, the downlink DCI scheduling TB contains three Media Access Control (MAC) Service Data Units (SDUs), originating from LCH1, LCH2, and LCH3, respectively, with corresponding EX-Timer values ​​of 10ms, 15ms, and 8ms. The UE selects the longest EX-Timer, 15ms, as the EX-Timer value used in this instance. It assumes that it will listen to the PDCCH for 15ms starting from the DCI reception time.

[0187] In one possible implementation, the time domain location of the DCI is as follows: different DCI time domains correspond to different EX-Timer values. The UE determines the EX-Timer value to use based on the time domain of the received DCI.

[0188] In some possible implementations, the frequency domain location of the DCI is as follows: different DCI frequency domains correspond to different EX-Timer values. The UE determines the EX-Timer value to use based on the frequency domain of the received DCI.

[0189] In other possible embodiments, the CCE aggregation level corresponding to the DCI is as follows: different DCIs can use different CCE aggregation levels, such as level 2, level 4, level 8, level 16, etc. A higher CCE aggregation level means worse channel quality, requiring a longer time to transmit the same amount of data, thus necessitating a longer EX-Timer value. The UE can pre-obtain the EX-Timer values ​​corresponding to different CCE aggregation levels, and upon receiving the DCI, determine the EX-Timer value to use based on the CCE aggregation level corresponding to the DCI.

[0190] It should be noted that the above-described extended timer operation mechanism can be combined with the embodiments shown in Figures 8 to 10. In another embodiment, the above-described extended timer operation mechanism can also be implemented independently. For example, after receiving LP-WUS, the UE starts a dedicated timer for PDCCH monitoring; during the operation of the dedicated timer, it monitors the PDCCH; when scheduling information is detected, it starts at least one EX-Timer; after the dedicated timer expires, it continues to monitor the PDCCH during the operation of the at least one EX-Timer.

[0191] This application also proposes another method for wireless communication to achieve mutual assistance between the DRX mechanism and the LP-WUS mechanism.

[0192] For ease of understanding, the method for wireless communication according to an embodiment of this application is described below with reference to Figure 12. Figure 12 is described from the perspective of the first node. The possible device forms of the first node can be found in the above embodiments, and will not be repeated here.

[0193] The method shown in Figure 12 may include steps S1210 to S1230, which are described below.

[0194] In S1210, the first node determines the timing of listening to the wake-up signal, as well as the configuration information for the long and short periods of non-continuous reception;

[0195] In S1220, the first node determines the corresponding PDCCH detection timing based on the type of the currently assigned non-continuous reception period;

[0196] In S1230, the first node listens for the wake-up signal within the listening time of the wake-up signal associated with the corresponding PDCCH detection time.

[0197] For example, the following explanation uses LP-WUS as the wake-up signal and DRX period as the duration of non-continuous reception.

[0198] In some possible implementations, when the DRX short-cycle timer (drx-ShortCycleTimer) times out, the current DRX short cycle is determined; when the drx-ShortCycleTimer is started at least twice without timeout, the current DRX long cycle is determined.

[0199] In some possible implementations, if the first node determines that it is currently in a short DRX cycle state, it listens within the LP-WUS listening time corresponding to the DRX onDuration (i.e., the PDCCH detection time) that it should listen for in the short DRX cycle state; if the first node determines that it is currently in a long DRX cycle state, it only listens within the LP-WUS listening time corresponding to the onDuration of the long DRX cycle state.

[0200] For example, taking Figure 13 as an example, before each OnDuration time, the LP-WUS listening time for the UE is configured. If the UE determines that it is currently in a short DRX cycle state, it listens for LP-WUS within the corresponding LP-WUS listening time before OnDuration1, OnDuration2, OnDuration3, OnDuration4, and OnDuration5, that is, it listens for LP-WUS at all the dashed arrows in the figure; if the UE determines that it is currently in a long DRX cycle state, it listens for LP-WUS within the corresponding LP-WUS listening time before OnDuration1 and OnDuration5, that is, it listens for LP-WUS at the dashed arrows before OnDuration1 and OnDuration5 in Figure 13.

[0201] In other possible embodiments, the first node starts or restarts the drx-ShortCycleTimer under the following conditions: A. The first node receives LP-WUS; B. Data or uplink / downlink scheduling information is received within the OnDuration, or in other words, data or uplink / downlink scheduling information is received within a discontinuous reception time window; C. Data or uplink / downlink scheduling information is received within an inactive timer, or in other words, data or uplink / downlink scheduling information is received within a discontinuous reception time extension window; D. MR listening to PDCCH is stopped; E. The first node receives uplink / downlink scheduling information, and the inactive timer triggered by the uplink / downlink scheduling information times out or is notified to stop listening.

[0202] In other possible embodiments, the first node starts or restarts the drx-ShortCycleTimer at any of the following times: a. when the first node receives the LP-WUS; b. when the first node receives the uplink / downlink scheduling information; c. when the first node stops MR listening to the PDCCH; d. when the first node receives the LP-WUS and stops MR listening to the PDCCH; e. when the first node receives the LP-WUS and the scheduling information; f. when the first node receives the LP-WUS and the uplink / downlink scheduling information, and the inactive timer triggered by the uplink / downlink scheduling times out or is notified to stop listening.

[0203] It should be understood that the conditions under which the UE starts drx-ShortCycleTimer in the above example are related to, or can be set independently, the timing of starting drx-ShortCycleTimer. The implementation mechanism of drx-LongCycleTimer is similar, and will not be repeated in this embodiment.

[0204] In some embodiments, when the first node receives LP-WUS but does not detect uplink or downlink scheduling during the subsequent OnDuration period or within the time window of a dedicated timer, the first node may process the data according to at least one of the following configured behaviors:

[0205] Behavior Mode A: After the first node listens to the PDCCH at the current OnDuration, it listens to the PDCCH at intervals T1 and continues to listen to the PDCCH for a duration of T2. Specifically, the durations of T1 and T2 can be configured by the base station or specified by the protocol. For example, the UE unconditionally listens to the PDCCH in the next OnDuration, regardless of whether it receives an LP-WUS notification.

[0206] Behavior Mode B: After the current OnDuration timer expires, the first node continues to listen to the PDCCH for a duration T3. Specifically, the duration of T3 can be configured by the base station or specified by the protocol. For example, the UE can start a timer of duration T3 when the OnDuration timer expires, and listen to the PDCCH during the timer's execution. Another example is that the UE starts an Inactive timer when the OnDuration timer expires, and listens to the PDCCH during the timer's execution; yet another example is that the UE continues to listen to the PDCCH after the OnDuration timer expires until the next LP-WUS listening opportunity, or the OnDuration corresponding to the next LP-WUS listening opportunity.

[0207] Behavior C: The first node initiates random access.

[0208] Behavior Mode D: The first node counts. If the first node receives another LP-WUS notification within the next LP-WUS listening period, but does not receive uplink / downlink scheduling, the counter continues to increment by 1. This process repeats until the counter reaches its maximum value, at which point the first node initiates random access. The maximum value of the counter is specified by the protocol or configured by the base station.

[0209] In another possible implementation, if the first node does not receive LP-WUS but receives DCI scheduling within the OnDuration time window corresponding to LP-WUS, the first node reports this situation to the second node. For example, the UE reports via MAC CE or PUCCH to the base station. After receiving the report, the base station can modify the LP-WUS configuration for the UE; specifically, it can modify the frequency domain configuration of LP-WUS within the bandwidth, or modify the band where LP-WUS resides.

[0210] The method embodiments of this application have been described in detail above with reference to Figures 1 to 13. The apparatus embodiments of this application will be described in detail below with reference to Figures 14 to 17. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0211] Figure 14 illustrates a first node for wireless communication provided in an embodiment of this application. The first node can be a terminal device or a network device. As shown in Figure 14, the first node 1400 includes a first processing module 1410 and a first transceiver module 1420.

[0212] The first processing module 1410 is used to determine the timing of listening to the wake-up signal;

[0213] The first transceiver module 1420 is used to receive the first wake-up signal and start the first timer at the first moment;

[0214] The first processing module 1410 is used to listen for subsequent wake-up signals within a time window in which the listening timing and the running time of the first timer overlap in the time domain.

[0215] In some possible embodiments, the first transceiver module 1420 is further configured to: receive first information, the first information being used to indicate the timing of listening to the wake-up signal.

[0216] In some possible embodiments, the first information includes at least one of the following: the long period of listening to the wake-up signal, the short period of listening to the wake-up signal, the time offset of the wake-up signal, or the continuous listening duration of the wake-up signal.

[0217] In some possible embodiments, the first processing module 1410 is further configured to: after the first timer expires, listen for subsequent wake-up signals within the listening time corresponding to the long period of the wake-up signal listening.

[0218] In some possible embodiments, the triggering condition for starting the first timer may include at least one of the following: receiving scheduling information within a set time period after the first wake-up signal is detected; or receiving scheduling information within a period of time after the end of the listening time corresponding to the first wake-up signal.

[0219] In some possible embodiments, the first moment is any of the following moments:

[0220] The moment the first wake-up signal is received;

[0221] The moment the scheduling information is received;

[0222] The moment when MR stops listening to PDCCH.

[0223] In some possible embodiments, the first transceiver module 1420 is further configured to: receive second information, the second information being used to indicate that the wake-up signal is not listened to before the listening long period of the next wake-up signal arrives.

[0224] In some possible embodiments, the first transceiver module 1420 is further configured to: listen for a wake-up signal at a listening time corresponding to a short listening period during the operation of the first timer; or, listen for a wake-up signal at a listening time corresponding to a long listening period during the operation of the first timer.

[0225] In some possible embodiments, the first transceiver module 1420 is further configured to: receive a stop listening notification of a wake-up signal at a second time, wherein the stop listening notification is used to instruct the first timer to stop listening to the wake-up signal for the remaining running time period after the second time.

[0226] In some possible embodiments, the first transceiver module 1420 is further configured to: receive a pause monitoring notification for the wake-up signal at a third time point, wherein the pause monitoring notification is used to indicate that the monitoring of the wake-up signal will be paused for a set period of time after the second time point.

[0227] In some possible embodiments, the first processing module 1410 is further configured to: pause listening to the wake-up signal during a time window in which the running time of the first timer and the running time of the second timer overlap in the time domain; wherein the duration of the second timer is less than the duration of the first timer.

[0228] In some possible embodiments, the third timer timeout triggers the start of the second timer, wherein: the triggering conditions of the third timer include: receiving scheduling information within a first set duration after the first wake-up signal is detected; receiving scheduling information within a second set duration after the end of the listening time corresponding to the first wake-up signal; stopping MR listening to PDCCH; the start time of the third timer is any of the following times: the time when the first wake-up signal is received; the time when the scheduling information is received; the time when MR listening to PDCCH is stopped.

[0229] In some possible embodiments, the first processing module 1410 is further configured to: start a dedicated timer after receiving a first wake-up signal; and perform PDCCH monitoring during the operation of the dedicated timer.

[0230] In some possible embodiments, the first processing module 1410 is further configured to: start at least one extended timer when scheduling information is detected; and perform PDCCH monitoring during the operation of the at least one extended timer after the dedicated timer arrives.

[0231] In some possible embodiments, the value of the extended timer is related to at least one of the following:

[0232] The scheduling direction indicated by downlink control information;

[0233] Types of downlink control information;

[0234] Downlink control information indicates downlink data;

[0235] The time domain location of the downlink control information;

[0236] The frequency domain location where the downlink control information is located;

[0237] The aggregation level of the control channel element (CCE) corresponding to the downlink control information.

[0238] As one embodiment, the first processing module 1410 may be a processor 1610. The first node 1400 may also include a memory 1620 and a transceiver 1630, as shown in FIG16.

[0239] Figure 15 illustrates a second node for wireless communication provided in an embodiment of this application. The second node can be a device or entity used for positioning on the network side, such as an LMF. As shown in Figure 15, the second node 1500 includes a second processing module 1510 and a second transceiver module 1520.

[0240] The second processing module 1510 is also used to determine the timing of listening to the wake-up signal;

[0241] The second transceiver module 1520 is also used to send a first wake-up signal; the first wake-up signal is used to trigger the first node to start a first timer at a first moment; and to listen for subsequent wake-up signals within a time window in which the running time of the first timer overlaps with the listening opportunity.

[0242] In some possible embodiments, the second transceiver module 1520 is further configured to: send first information, the first information being used to indicate the timing of listening to the wake-up signal.

[0243] In some possible embodiments, the first information includes at least one of the following: the long period of listening to the wake-up signal, the short period of listening to the wake-up signal, the time offset of the wake-up signal, or the continuous listening duration of the wake-up signal.

[0244] In some possible embodiments, the second transceiver module 1520 is further configured to: send second information, the second information being configured to instruct the first node not to listen for the wake-up signal before the next long period of the wake-up signal is reached.

[0245] In some possible embodiments, the second transceiver module 1520 is further configured to: receive a stop listening notification for sending a wake-up signal at a second time, the stop listening notification being used to instruct the remaining running time of the first timer after the second time to stop listening to the wake-up signal.

[0246] In some possible embodiments, the second transceiver module 1520 is further configured to: send a pause listening notification for the wake-up signal at a third time, the pause listening notification being used to indicate that listening to the wake-up signal will be paused for a set period of time after the second time.

[0247] As one embodiment, the second processing module 1510 may be a processor 1610. The second node 1500 may also include a memory 1620 and a transceiver 1630, as shown in FIG16.

[0248] Figure 16 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 16 indicate that the unit or module is optional. This device 1600 can be used to implement the methods described in the above method embodiments. Device 1600 can be a chip, user equipment, or network device.

[0249] Apparatus 1600 may include one or more processors 1610. The processor 1610 may support apparatus 1600 in implementing the methods described in the preceding method embodiments. The processor 1610 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0250] The apparatus 1600 may further include one or more memories 1620. The memories 1620 store a program that can be executed by the processor 1610, causing the processor 1610 to perform the methods described in the preceding method embodiments. The memories 1620 may be independent of the processor 1610 or integrated within the processor 1610.

[0251] The device 1600 may also include a transceiver 1630. The processor 1610 can communicate with other devices or chips via the transceiver 1630. For example, the processor 1610 can send and receive data with other devices or chips via the transceiver 1630.

[0252] Figure 17 is a schematic diagram of the hardware modules of the communication device provided in this application embodiment. Specifically, Figure 17 shows a block diagram of a first communication device 1750 and a second communication device 1710 communicating with each other in the access network.

[0253] The first communication device 1750 includes a controller / processor 1759, a memory 1760, a data source 1767, a transmitter processor 1768, a receiver processor 1756, a multi-antenna transmitter processor 1757, a multi-antenna receiver processor 1758, a transmitter / receiver 1754, and an antenna 1752.

[0254] The second communication device 1710 includes a controller / processor 1775, a memory 1776, a data source 1777, a receiver processor 1770, a transmitter processor 1716, a multi-antenna receiver processor 1772, a multi-antenna transmitter processor 1771, a transmitter / receiver 1718, and an antenna 1720.

[0255] In the transmission from the second communication device 1710 to the first communication device 1750, at the second communication device 1710, upper-layer data packets from the core network or from the data source 1777 are provided to the controller / processor 1775. The core network and data source 1777 represent all protocol layers above the L2 layer. The controller / processor 1775 implements the functionality of the L2 layer. In the transmission from the second communication device 1710 to the first communication device 1750, the controller / processor 1775 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication device 1750 based on various priority metrics. The controller / processor 1775 is also responsible for retransmitting lost packets and signaling to the first communication device 1750. The transmit processor 1716 and the multi-antenna transmit processor 1771 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 1716 performs encoding and interleaving to facilitate forward error correction at the second communication device 1710, and mapping of signal clusters based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). Multi-antenna transmit processor 1771 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 1716 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 1771 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 1718 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 1771 into an radio frequency stream, which is then provided to different antennas 1720.

[0256] In the transmission from the second communication device 1710 to the first communication device 1750, at the first communication device 1750, each receiver 1754 receives a signal through its corresponding antenna 1752. Each receiver 1754 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 1756. The receiver processor 1756 and the multi-antenna receiver processor 1758 implement various signal processing functions of Layer 1. The multi-antenna receiver processor 1758 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 1754. The receiver processor 1756 uses a Fast Fourier Transform to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 1756, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 1758 after multi-antenna detection to recover any spatial stream destined for the first communication device 1750. Symbols on each spatial stream are demodulated and recovered in the receive processor 1756, generating soft decisions. The receive processor 1756 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the second communication device 1710 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 1759. The controller / processor 1759 implements the functions of Layer 2. The controller / processor 1759 may be associated with a memory 1760 storing program code and data. The memory 1760 may be referred to as computer-readable media. In the transmission from the second communication device 1710 to the first communication device 1750, the controller / processor 1759 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the second communication device 1710. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.

[0257] In the transmission from the first communication device 1750 to the second communication device 1710, at the first communication device 1750, upper-layer data packets are provided to the controller / processor 1759 using a data source 1767. The data source 1767 represents all protocol layers above Layer 2. Similar to the transmission functions at the second communication device 1710 described in the transmission from the second communication device 1710 to the first communication device 1750, the controller / processor 1759 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logic and transport channels, implementing Layer 2 functions for the user plane and control plane. The controller / processor 1759 is also responsible for retransmitting lost packets and signaling to the second communication device 1710. Transmit processor 1768 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 1757 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 1768 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 1757, the stream is provided to different antennas 1752 via transmitter 1754. Each transmitter 1754 first converts the baseband symbol stream provided by multi-antenna transmit processor 1757 into a radio frequency symbol stream before providing it to antenna 1752.

[0258] In the transmission from the first communication device 1750 to the second communication device 1710, the function at the second communication device 1710 is similar to the receiving function at the first communication device 1750 described in the transmission from the second communication device 1710 to the first communication device 1750. Each receiver 1718 receives radio frequency signals through its corresponding antenna 1720, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 1772 and the receiving processor 1770. The receiving processor 1770 and the multi-antenna receiving processor 1772 jointly implement the L1 layer function. The controller / processor 1775 implements the L2 layer function. The controller / processor 1775 may be associated with a memory 1776 that stores program code and data. The memory 1776 may be referred to as computer-readable media. In the transmission from the first communication device 1750 to the second communication device 1710, the controller / processor 1775 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover the upper-layer data packets from the first communication device 1750. The upper-layer data packets from the controller / processor 1775 can be provided to the core network or all protocol layers above Layer 2, and various control signals can also be provided to the core network or Layer 3 for Layer 3 processing.

[0259] As one embodiment, the first communication device 1750 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor.

[0260] As one embodiment, the first communication device 1750 includes: a memory storing a computer-readable instruction program that produces action when executed by at least one processor.

[0261] As an example, the first communication device 1750 corresponds to the first node in this application.

[0262] As an example, the second communication device 1710 corresponds to the second node in this application.

[0263] As an example, the first communication device 1750 is a user equipment that can act as a relay node.

[0264] As an example, the first communication device 1750 is a network control relay (NCR).

[0265] As an example, the first communication device 1750 is a relay wireless repeater.

[0266] As an example, the first communication device 1750 is a relay.

[0267] As one embodiment, the second communication device 1710 is a Location Management Function (LMF).

[0268] As an example, the first communication device 1750 corresponds to the first node in this application, and the controller / processor 1159 is used to execute the above method.

[0269] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.

[0270] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.

[0271] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device, network device, or core network entity in the various embodiments of this application.

[0272] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0273] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0274] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0275] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0276] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including user equipment and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0277] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0278] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0279] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0280] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0281] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0282] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0283] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0284] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for a first node in wireless communication, characterized in that, include: Determine when to listen for the wake-up signal; Upon receiving the first wake-up signal, the first timer is started at the first moment; The wake-up signal is listened for within the time window in which the listening timing and the running time of the first timer overlap.

2. The method according to claim 1, characterized in that, Also includes: Receive first information, which is used to indicate the timing of listening to the wake-up signal.

3. The method according to claim 1, characterized in that, Within a time window in which the listening timing and the execution time of the first timer overlap in the time domain, the wake-up signal is listened for, including: During the operation of the first timer, the wake-up signal is listened for according to the listening timing corresponding to the short listening cycle; or, During the operation of the first timer, the wake-up signal is listened for according to the listening timing corresponding to the long listening period.

4. The method according to claim 2, characterized in that, The first information includes at least one of the following: the long period of the wake-up signal monitoring, the short period of the wake-up signal monitoring, the time offset of the wake-up signal, or the continuous monitoring duration of the wake-up signal.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: After the first timer expires, during the listening period corresponding to the long period of the wake-up signal listening, the system listens for subsequent wake-up signals.

6. The method according to any one of claims 1 to 5, characterized in that, The triggering condition for starting the first timer also includes at least one of the following: Within a set time period after the first wake-up signal is detected, scheduling information is received; Within a certain period of time after the end of the listening time corresponding to the first wake-up signal, the scheduling information is received.

7. The method according to any one of claims 1 to 4, characterized in that, The first time point is any of the following: The moment the first wake-up signal is received; The moment the scheduling information is received; The moment when MR stops listening to PDCCH.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: Receive a second message, which indicates that the wake-up signal should not be listened to until the listening long period of the next wake-up signal arrives.

9. The method according to any one of claims 1 to 7, characterized in that, Also includes: A stop listening notification is received at the second time point, which is used to instruct the first timer to stop listening for the wake-up signal for the remaining running time period after the second time point.

10. The method according to any one of claims 1 to 7, characterized in that, Also includes: A pause listening notification is received at the third moment when a wake-up signal is received. The pause listening notification is used to indicate that listening to the wake-up signal will be paused for a set period of time after the second moment.

11. The method according to any one of claims 1 to 7, characterized in that, Also includes: During the time window in which the execution time of the first timer and the execution time of the second timer overlap in the time domain, the listening for the wake-up signal is paused. The duration of the second timer is less than the duration of the first timer.

12. The method according to claim 11, characterized in that, The third timer timeout triggers the start of the second timer, wherein: The triggering conditions for the third timer include: Within a first set time period after the first wake-up signal is detected, scheduling information is received; The scheduling information is received within a second set time period after the end of the listening time corresponding to the first wake-up signal; Stop MR monitoring of PDCCH; The third timer is started at any of the following times: The moment the first wake-up signal is received; The moment the scheduling information is received; The moment when MR stops listening to PDCCH.

13. The method according to any one of claims 1 to 11, characterized in that, Also includes: A dedicated timer is started upon receiving the first wake-up signal; PDCCH monitoring is performed during the operation of the dedicated timer.

14. The method according to claim 13, characterized in that, Also includes: Upon receiving a scheduling message, start at least one extended timer; After the dedicated timer arrives, PDCCH monitoring is performed during the operation of the at least one extended timer.

15. The method according to claim 14, characterized in that, The value of the extended timer is related to at least one of the following: The scheduling direction indicated by downlink control information; Types of downlink control information; Downlink control information indicates downlink data; The time domain location of the downlink control information; The frequency domain location where the downlink control information is located; The aggregation level of the Control Channel Unit (CCE) corresponding to the downlink control information.

16. A method for a second node in wireless communication, characterized in that, include: Determine when to listen for the wake-up signal; Send a first wake-up signal; the first wake-up signal is used to trigger the first node to start the first timer at a first moment; And within the time window in which the first timer's running time overlaps with the listening opportunity, subsequent wake-up signals are monitored.

17. The method according to claim 16, characterized in that, Also includes: Send a first message, which is used to indicate the timing of listening to the wake-up signal.

18. The method according to claim 17, characterized in that, The first information includes at least one of the following: the long period of the wake-up signal monitoring, the short period of the wake-up signal monitoring, the time offset of the wake-up signal, or the continuous monitoring duration of the wake-up signal.

19. The method according to any one of claims 16 to 18, characterized in that, After the first timer times out, it also includes: Send a second message, which instructs the first node not to listen for the wake-up signal until the next long period of the wake-up signal listening period arrives.

20. The method according to any one of claims 16 to 18, characterized in that, Also includes: At the second moment, a stop listening notification is sent to indicate that listening for the wake-up signal will cease during the first timer running period after the second moment.

21. The method according to any one of claims 16 to 18, characterized in that, Also includes: A pause notification for listening to the wake-up signal is sent at the third moment, the pause notification indicating that listening to the wake-up signal will be paused for a set period of time after the second moment.

22. A first node for wireless communication, characterized in that, It includes a first processing module and a first transceiver module; The first processing module is used to determine the timing of listening for the wake-up signal; The first transceiver module is used to receive the first wake-up signal and start the first timer at the first moment; The first processing module is used to listen for subsequent wake-up signals within a time window in which the listening timing and the running time of the first timer overlap in the time domain.

23. The first node according to claim 22, characterized in that, The first transceiver module is further configured to: Receive first information, which is used to indicate the timing of listening to the wake-up signal.

24. The first node according to claim 23, characterized in that, The first information includes at least one of the following: the long period of the wake-up signal monitoring, the short period of the wake-up signal monitoring, the time offset of the wake-up signal, or the continuous monitoring duration of the wake-up signal.

25. The first node according to any one of claims 22 to 24, characterized in that, The first processing module is further configured to: After the first timer expires, during the listening period corresponding to the long period of the wake-up signal listening, the system listens for subsequent wake-up signals.

26. The first node according to any one of claims 22 to 25, characterized in that, The triggering condition for starting the first timer also includes at least one of the following: Within a set time period after the first wake-up signal is detected, scheduling information is received; Within a certain period of time after the end of the listening time corresponding to the first wake-up signal, the scheduling information is received.

27. The first node according to any one of claims 22 to 24, characterized in that, The first time point is any of the following: The moment the first wake-up signal is received; The moment the scheduling information is received; The moment when MR stops listening to PDCCH.

28. The first node according to any one of claims 22 to 27, characterized in that, The first transceiver module is further configured to: Receive a second message, which indicates that the wake-up signal should not be listened to until the listening long period of the next wake-up signal arrives.

29. The first node according to any one of claims 22 to 27, characterized in that, The first transceiver module is further configured to: A stop listening notification is received at the second time point, which is used to instruct the first timer to stop listening for the wake-up signal for the remaining running time period after the second time point.

30. The first node according to any one of claims 22 to 27, characterized in that, The first transceiver module is further configured to: A pause listening notification is received at the third moment when a wake-up signal is received. The pause listening notification is used to indicate that listening to the wake-up signal will be paused for a set period of time after the second moment.

31. The first node according to any one of claims 22 to 27, characterized in that, The first processing module is further configured to: During the time window in which the execution time of the first timer and the execution time of the second timer overlap in the time domain, the listening for the wake-up signal is paused. The duration of the second timer is less than the duration of the first timer.

32. The first node according to claim 31, characterized in that, The third timer timeout triggers the start of the second timer, wherein: The triggering conditions for the third timer include: Within a first set time period after the first wake-up signal is detected, scheduling information is received; The scheduling information is received within a second set time period after the end of the listening time corresponding to the first wake-up signal; Stop MR monitoring of PDCCH; The third timer is started at any of the following times: The moment the first wake-up signal is received; The moment the scheduling information is received; The moment when MR stops listening to PDCCH.

33. The first node according to any one of claims 22 to 31, characterized in that, The first processing module is further configured to: A dedicated timer is started upon receiving the first wake-up signal; PDCCH monitoring is performed during the operation of the dedicated timer.

34. The first node according to claim 33, characterized in that, The first processing module is further configured to: Upon receiving a scheduling message, start at least one extended timer; After the dedicated timer arrives, PDCCH monitoring is performed during the operation of the at least one extended timer.

35. The first node according to claim 34, characterized in that, The value of the extended timer is related to at least one of the following: The scheduling direction indicated by downlink control information; Types of downlink control information; Downlink control information indicates downlink data; The time domain location of the downlink control information; The frequency domain location where the downlink control information is located; The aggregation level of the Control Channel Unit (CCE) corresponding to the downlink control information.

36. A second node for wireless communication, characterized in that, Includes a second transceiver module and a second processing module: The second processing module is also used to determine the timing of listening for the wake-up signal; The second transceiver module is also used to send a first wake-up signal; the first wake-up signal is used to trigger the first node to start a first timer at a first moment; and to listen for subsequent wake-up signals within a time window in which the running time of the first timer overlaps with the listening time.

37. The second node according to claim 36, characterized in that, The second transceiver module is also used for: Send a first message, which is used to indicate the timing of listening to the wake-up signal.

38. The second node according to claim 37, characterized in that, The first information includes at least one of the following: the long period of the wake-up signal monitoring, the short period of the wake-up signal monitoring, the time offset of the wake-up signal, or the continuous monitoring duration of the wake-up signal.

39. The second node according to any one of claims 36 to 38, characterized in that, The second transceiver module is also used for: Send a second message, which instructs the first node not to listen for the wake-up signal until the next long period of the wake-up signal listening period arrives.

40. The second node according to any one of claims 36 to 38, characterized in that, The second transceiver module is also used for: At the second time point, a stop listening notification is sent to indicate that the listening for the wake-up signal will cease during the remaining running time of the first timer after the second time point.

41. The second node according to any one of claims 36 to 38, characterized in that, The second transceiver module is also used for: A pause notification for listening to the wake-up signal is sent at the third moment, the pause notification indicating that listening to the wake-up signal will be paused for a set period of time after the second moment.

42. A node used for wireless communication, characterized in that, The device includes a transceiver, a memory, and a processor. The memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or send signals so that the node performs the method as described in any one of claims 1-15 or 16-21.

43. A communication device, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-15 or 16-21.

44. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-15 or 16-20.

45. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-15 or 16-21.

46. ​​A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-15 or 16-21.

47. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-15 or 16-21.

Images