Wireless communication method, terminal equipment and network equipment

Abstract

The invention provides a wireless communication method, terminal equipment and network equipment. The method comprises the steps that the terminal equipment receives a first low-power-consumption wake-up signal LP-WUS sent by the network equipment; and in response to the received first LP-WUS, the terminal device monitors a physical downlink control channel (PDCCH) in a first time period. In the embodiment of the invention, the terminal equipment responds to the received LP-WUS (also known as' first LP-WUS '), and monitors the PDCCH in the first time period. Compared with the traditional scheme in which the monitoring of the PDCCH is intermittently activated by using the connected discontinuous reception (C-DRX) configuration, the method provided by the invention has the advantages that the unnecessary PDCCH monitoring (such as an inactive time period) can be avoided, so that the power consumption of the terminal equipment is reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment and network equipment. Background Art

[0002] The communication system introduces low-power receivers and low-power wake-up signals (LP-WUS). When the terminal device is idle, the main receiver can be turned off or set to a deep sleep state, and only the low-power receiver is used to listen to LP-WUS, thereby reducing the power consumption of the terminal. However, how to embed LP-WUS into the traditional communication system to further reduce the power consumption of the terminal device is an urgent problem to be solved. Summary of the invention

[0003] The present application provides a wireless communication method, terminal equipment and network equipment. The following introduces various aspects involved in the present application.

[0004] In a first aspect, a method for wireless communication is provided, including: a terminal device receives a first low power wake-up signal LP-WUS sent by a network device; in response to receiving the first LP-WUS, the terminal device monitors a physical downlink control channel (PDCCH) within a first time period.

[0005] In a second aspect, a method for wireless communication is provided, including: a network device sends a first low power wake-up signal LP-WUS to a terminal device; the first LP-WUS is used to trigger the terminal device to monitor a physical downlink control channel PDCCH within a first time period.

[0006] According to a third aspect, a terminal device is provided, including: a receiving unit for receiving a first low power wake-up signal LP-WUS sent by a network device; and a monitoring unit, in response to receiving the first LP-WUS, the monitoring unit is used to monitor a physical downlink control channel PDCCH within a first time period.

[0007] In a fourth aspect, a network device is provided, including: a sending unit, used to send a first low power wake-up signal LP-WUS to a terminal device; the first LP-WUS is used to trigger the terminal device to monitor a physical downlink control channel PDCCH within a first time period.

[0008] In a fifth aspect, a terminal device is provided, comprising a processor, a memory and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer programs in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, a network device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer programs in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0010] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided by the embodiment of the present application.

[0011] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program enables a communication device (for example, a terminal device or a network device) to perform some or all of the steps in the methods of the above aspects.

[0012] In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a communication device (e.g., a terminal device or a network device) to perform some or all of the steps in the above-mentioned various aspects of the method. In some implementations, the computer program product can be a software installation package.

[0013] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] In an embodiment of the present application, the terminal device monitors the PDCCH in a first time period in response to a received LP-WUS (also referred to as a "first LP-WUS"). Compared with the conventional scheme of using a connected discontinuous reception (C-DRX) configuration to intermittently activate the monitoring of the PDCCH, it helps to avoid unnecessary PDCCH monitoring (e.g., inactive time period) to reduce the power consumption of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1This is a wireless communication system 100 applied in an embodiment of the present application.

[0016] Figure 2 It is a schematic flowchart of the wireless communication method of an embodiment of the present application.

[0017] Figure 3 This is an architecture of a second receiver applicable to the embodiments of the present application.

[0018] Figure 4 This is another architecture of a second receiver applicable to the embodiments of the present application.

[0019] Figure 5 This is another architecture of a second receiver applicable to the embodiments of the present application.

[0020] Figure 6 This is an example diagram of the first time offset of an embodiment of the present application.

[0021] Figure 7 This is another example diagram of the first time offset of an embodiment of the present application.

[0022] Figure 8 This is an example diagram of a terminal device sending first confirmation information and second confirmation information.

[0023] Fig. 9 It is a schematic diagram of a terminal device according to an embodiment of the present application.

[0024] Fig.10 It is a schematic diagram of a network device according to an embodiment of the present application.

[0025] Fig.11 It is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0027] Figure 1 The wireless communication system 100 used in the embodiment of the present application may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal device 120 located in the coverage area.

[0028] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

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

[0030] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes an NR system for illustrative purposes, and NR terms are used in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as future communication systems (such as the sixth generation (6 th The wireless communication system includes terminal equipment and network equipment.

[0031] The terminal device in the embodiment of the present application may 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 the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a laptop computer or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device (wearable device), a virtual reality (VR) device, an augmented reality (AR) device, a robot, a vehicle user equipment (VUE), a pedestrian user equipment (PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a smart city, etc. The wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, cellular phones and cars communicate with each other using sidelink signals.The cellular phone and the smart home device communicate with each other without relaying the communication signal through the base station. It should be noted that the specific type of the terminal device is not limited in the embodiment of the present application.

[0032] The network device in the embodiment of the present application may be a device for communicating with a terminal device, and may include an access network device or a core network device, wherein the access network device may also be referred to as a wireless access network device, a wireless access network device, a wireless access network (RAN), a wireless access network function, or a wireless access network unit, such as an access network device may be a base station WLAN access point or a WiFi node, etc. The access network device in the embodiment of the present application may refer to a wireless access network node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home B node, home evolved B node, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (central The base station may be a mobile switching center, a device that performs the function of a base station in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communications, a network side device in a 6G network, a device that performs the function of a base station in future communication systems, etc. The base station may also refer to a communication module, a modem or a chip that is provided in the aforementioned device or apparatus. The base station may also be a mobile switching center, and a device that performs the function of a base station in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communications, a network side device in a 6G network, and a device that performs the function of a base station in a future communication system. The base station may support networks with the same or different access technologies.The embodiments of the present application do not limit the specific technology and specific device form used by the network equipment. It should be noted that in the embodiments of the present application, only the base station in the NR system is introduced as an example, and the specific type of the base station is not limited.

[0033] 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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0034] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0035] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0036] It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

[0037] In cellular networks, typically end devices (e.g., end devices in 5G networks) consume tens of milliwatts even when not transmitting or receiving any data. This idle power consumption is due to the fact that the end device must make periodic measurements and check for potential paging messages. Therefore, without the support of an external power supply, IoT devices are difficult to implement in practice.

[0038] To solve the above problems, communication systems (e.g., NR) have introduced low-power receivers and LP-WUS. When the terminal device is idle, the main receiver can be turned off or set to a deep sleep state, and only the low-power receiver can be used to monitor LP-WUS, thereby reducing the power consumption of the terminal. However, how to embed LP-WUS into traditional communication systems to further reduce the power consumption of terminal devices is an urgent problem to be solved.

[0039] For example, when the main receiver of the terminal device is awakened, the terminal device enters the radio resource control (RRC) connected state (CONNECTED), and the low-power receiver of the terminal device can be continuously turned on to receive LP-WUS. Therefore, the low-power receiver is independent of the main receiver, that is, the main receiver can be turned off when the low-power receiver is active and searching for potential LP-WUS. Considering that the moment when the terminal device monitors LP-WUS may occur during the reduced-power PDCCH monitoring (monitor) time period, LP-WUS can be applied to C-DRX to further reduce the power consumption of the terminal device, but there is currently no relevant solution. In addition, when multiple terminal devices monitor LP-WUS at the same time, there may be a case of false wake-up.

[0040] In view of the above problems, an embodiment of the present application proposes a wireless communication method, in which a terminal device monitors a PDCCH in a first time period in response to a received LP-WUS (hereinafter referred to as a "first LP-WUS"). Compared with the conventional solution of using C-DRX configuration to intermittently activate PDCCH monitoring, it helps to avoid unnecessary PDCCH monitoring (for example, inactive time period) to reduce the power consumption of the terminal device.

[0041] Combined with the following Figure 2 A wireless communication method according to an embodiment of the present application is introduced. Figure 2 It is a schematic flowchart of the wireless communication method of an embodiment of the present application. Figure 2 The illustrated solution includes step S210 and step S220.

[0042] In step S210, the network device sends a first LP-WUS to the terminal device. Correspondingly, the terminal device receives the first LP-WUS sent by the network device.

[0043] In some implementations, the terminal device includes a first receiver and a second receiver, the power consumption of the first receiver is higher than that of the second receiver, and the first LP-WUS is received by the second receiver of the terminal device, or in other words, the first LP-WUS is monitored by the terminal device through the second receiver.

[0044] In some implementations, the power consumption of the first receiver is higher than that of the second receiver. Therefore, the first receiver may be the main receiver (MR) mentioned above, and the second receiver may be the low-power receiver (LR) mentioned above.

[0045] In some implementations, the first receiver may also be referred to as a "main communication module", and the second receiver may also be referred to as a low power wake up module or a low power wake up receiver (LP-WUR).

[0046] When the first LP-WUS is embedded in a conventional communication system, it is necessary to seamlessly integrate the generation of the first LP-WUS into the signal generation in the conventional communication system. To facilitate receiving the first LP-WUS, in some implementations, the architecture of the second receiver suitable for receiving the first LP-WUS includes one or more of the following: an architecture with radio frequency (RF) envelope detection; a heterodyne architecture with intermediate frequency envelope detection; a homodyne or zero intermediate frequency architecture with baseband envelope detection.

[0047] In some implementations, the architecture of the second receiver may be an architecture with RF envelope detection. Figure 3 , the RF signal is directly converted to a baseband signal through an RF envelope detector, without a local oscillator (LO) and a phase-locked loop (PLL), which can achieve relatively low power consumption. A 1-bit or multi-bit analog to digital converter (ADC) can be applied, and some components such as a low noise amplifier (LNA) for RF and / or asymmetric multi-processing (AMP) for baseband, a high-Q matching network and / or a band pass filter (BPF) for RF and / or a low-pass filter (LPF) for baseband can be optionally applied. Supporting multiple frequency bands and / or carriers may require multiple high-Q matching networks and / or RF BPFs or multiple off-chip components, which can be used to suppress adjacent channel interference or interference from signals in conventional communication systems and / or other LP-WUS on adjacent subcarriers, and can support frequency band and / or carrier tuning.

[0048] In some implementations, the architecture of the second receiver may be a heterodyne architecture with intermediate frequency envelope detection. Figure 4, the RF signal is down-converted to an intermediate frequency (IF) signal through an RF mixer with an LO. The IF signal is converted to a baseband signal by IF envelope detection. Depending on the design, there may be one or more intermediate frequency stages, and lower power consumption can be achieved by relaxing the accuracy and stability requirements of the LO. A 1-bit or multi-bit ADC can be applied. 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 other signals in a conventional communication system on adjacent subcarriers and / or other LP WUS. Some components, such as an RFLNA and / or an IF AMP and / or a BB AMP, can be optionally applied. Band and / or carrier tuning can be achieved by tuning the LO frequency, and an RF LNA and / or an IF AMP can be applied to improve sensitivity.

[0049] In some implementations, the architecture of the second receiver may be a homodyne or zero-IF architecture with baseband envelope detection. Figure 5 , band and / or carrier tuning can be achieved by tuning the LO frequency. It is more efficient and simpler to use BB BPF / LPF instead of high-Q matching network and / or RF BPF to suppress adjacent channel interference or interference from other signals in the conventional communication system and / or other LP-WUS on adjacent subcarriers. RF LNA can be applied to improve sensitivity, and baseband envelope detection can be done in the analog domain (before ADC) or in the digital domain (after ADC).

[0050] It should be noted that the above three second receiver architectures can be applicable to binary on-offkeying (OOK) modulation. Of course, some of the architectures can also be applicable to other modulations, such as frequency shift keying (FSK).

[0051] In some implementations, in a multi-carrier on-off keying (MC-OOK) system based on orthogonal frequency division multiplexing (OFDM), a network device may perform a multi-carrier amplitude shift keying (MC-ASK) waveform using coded bits to generate a first LP-WUS.

[0052] In some implementations, the first LP-WUS can support a bandwidth of 5MHz to 20M, so when the first LP-WUS is embedded in a traditional communication system, it can be two receiving modules or integrated into one receiving module, that is, the first receiver and the second receiver are two separate modules or the first receiver and the second receiver are integrated into one module.

[0053] In step 220, in response to receiving the first LP-WUS, the terminal device monitors the PDCCH during a first time period.

[0054] In some implementations, in response to receiving the first LP-WUS, the terminal device monitors the PDCCH in the first time period. It can be understood that the terminal device triggers the monitoring of the PDCCH in the first time period based on the first LP-WUS, or in other words, the first LP-WUS is used to trigger the terminal device to monitor the PDCCH in the first time period. The first LP-WUS can not only be used to wake up the terminal device in the idle (IDLE) / inactive state (INACTIVE), but also can wake up the terminal device in the connected state to monitor the PDCCH. Considering that the performance of the first LP-WUS is much worse than that of the ordinary PDCCH, the number of bits will also be very limited, so it helps to save power of the terminal device.

[0055] In some implementations, the first LP-WUS triggers PDCCH monitoring in a connected state. For example, for a terminal device in a connected state, C-DRX can configure LP-WUS, that is, the terminal device receives the first LP-WUS, which can trigger PDCCH monitoring configured by C-DRX in a first time period.

[0056] In some implementations, if the terminal device monitors the PDCCH in the first time period, it can continue to monitor the data scheduled by the PDCCH, that is, the terminal device continues to monitor the data transmitted by the transmission resources indicated by the downlink control information (DCI) carried by the PDDCH.

[0057] In some implementations, the first receiver monitors the PDCCH. For example, the second receiver of the terminal device receives the first LP-WUS, wakes up the first receiver in a sleep state, and causes the first receiver to enter a PDCCH monitoring state in a first time period.

[0058] In some implementations, the terminal device monitors PDCCH within the first time period, which can be understood as the terminal device monitors PDCCH within the first time period. If PDCCH is monitored, the terminal device continues to monitor data transmitted on the transmission resource indicated by the DCI carried by the PDCCH.

[0059] In some implementations, the first LP-WUS triggers the terminal device to monitor the PDCCH within a first time period, that is, the first time period is the monitoring duration of the PDCCH triggered by the first LP-WUS.

[0060] For the monitoring of the PDCCH triggered by the first LP-WUS, the focus is on how to configure the monitoring duration of the PDCCH triggered only by the first LP-WUS. In some implementations, the first time period is determined based on a first timer.

[0061] In some implementations, the first time period is determined based on the first timer, which can be understood as the first time period being determined based on the duration of the first timer. For example, the first time period can be determined based on the start time of the first timer, the start time of the first time period is the start time of the first timer, and the end time of the first time period is the time within the duration of the first timer or the time after the end time of the first timer.

[0062] In some implementations, the first time period is determined based on the first timer, which can be understood as the first time period being the duration of the first timer, that is, the start time of the first time period is the start time of the first timer, and the end time of the first time period is the end time of the first timer. In this case, the terminal device triggers monitoring of the PDCCH in the first time period based on the first LP-WUS, which can be understood as the first LP-WUS triggers the start of the first timer, and the terminal device monitors the PDCCH during the operation of the first timer.

[0063] In some implementations, the first timer includes an existing timer and / or a newly defined timer.

[0064] In some implementations, the existing timer may be a discontinuous reception (DRX) inactivity timer (drx-InactivityTimer) of an existing C-DRX configuration. For example, the first timer is drx-InactivityTimer, and the terminal device receives the first LP-WUS, triggering the start of drx-InactivityTimer.

[0065] In some implementations, the existing timer may be a DRX duration timer (drx-onDurationTimer) configured in an existing C-DRX. For example, the first timer is drx-onDurationTimer, and the terminal device receives the first LP-WUS, triggering the start of drx-onDurationTimer.

[0066] In some implementations, the newly defined timer may be understood as a timer triggered by the first LP-WUS, or a dedicated timer of the LP-WUS, or a timer newly designed for the LP-WUS.

[0067] In some implementations, the duration of the dedicated timer for the LP-WUS may be less than or equal to the drx-onDurationTimer.

[0068] In order to determine which timer can be triggered by the first LP-WUS, or to trigger different timers in different scenarios, the terminal device should determine which timer is triggered by the first LP-WUS according to specific conditions in different scenarios. In some implementations, the first timer is determined based on one or more of the following: service type; data transmission mode; data flow characteristics; service quality requirements; network load information.

[0069] In some implementations, the service type may be understood as the service type of the data scheduled by the PDCCH. For example, the service type of the data scheduled by the PDCCH may be voice or video.

[0070] In some implementations, the data transmission mode may be understood as a transmission rule of data scheduled by the PDCCH. For example, the data transmission mode scheduled by the PDCCH may be periodic or aperiodic, predictable or unpredictable.

[0071] In some implementations, the traffic characteristics of data can be understood as traffic characteristics during the data transmission process scheduled by the PDCCH, for example, the rate of the traffic, whether the traffic is continuous, etc. during the data transmission process scheduled by the PDCCH.

[0072] In some implementations, the service quality requirement can be understood as a service quality (QoS) indicator of the data scheduled by the PDCCH, for example, bandwidth, delay, packet loss rate, jitter, etc. of the data.

[0073] In some implementations, the network load information may be understood as the current network load condition.

[0074] In some implementations, the first timer is determined based on the data transmission mode. For example, for periodically transmitted data, the time of traffic arrival is predictable, and the first timer can be drx-onDurationTimer, because maintaining the listening state for a short period of time before each transmission can ensure timely data reception while saving power consumption. For another example, for non-periodically transmitted data, the first timer can be drx-InactivityTimer to ensure that the terminal device maintains a long listening state after the start of data transmission, which is suitable for applications in uncertain data transmission modes.

[0075] In some implementations, the first timer is determined based on the quality of service requirements. For example, when the application data is sensitive to latency and has high requirements for service quality (such as video calls, online games), the first timer should be drx-onDurationTimer to ensure that the terminal device can respond quickly to downlink data and maintain low latency. For another example, for scenarios with low quality of service requirements (such as periodic data synchronization, Internet of Things (IoT) applications), the first timer can be a dedicated timer for LP-WUS to ensure that the terminal device remains active for a short time when needed and is in a low power state as much as possible at other times.

[0076] In some implementations, the first timer is determined based on network load information. For example, in a high-load network, the terminal device may need more time to process data transmission, so the first timer may be a drx-InactivityTimer, so that the terminal device remains active during the transmission process and avoids frequent wake-up from sleep when the load is high. For another example, when the network load is low, the first timer may be a drx-onDurationTimer or a dedicated timer of LP-WUS, so that the terminal device wakes up only when needed and maintains low power consumption.

[0077] In some implementations, the first timer is determined based on the data transmission mode, the traffic characteristics of the data, and the quality of service. For example, when the terminal device detects the possibility of downlink data arriving at a higher rate based on the first LP-WUS, or real-time communications such as voice over internet protocol (VoIP) are sensitive to latency and have periodic data transmission, the first timer may be drx-onDurationTimer, and starting drx-onDurationTimer can ensure that the terminal device remains activated for a short time so as to receive data in time. Because drx-onDurationTimer is responsible for controlling the time that the terminal device maintains the PDCCH monitoring state in each DRX cycle. When this timer is started, the terminal device will continue to monitor the PDCCH to receive potential data transmission. For another example, when the first LP-WUS wakes up the terminal device, or when continuous downlink data transmission (such as file download or video streaming) is expected, the first timer is drx-InactivityTimer, and starting drx-InactivityTimer at this time helps to keep the terminal device active to continue to receive data. Because drx-InactivityTimer can be started when the terminal device is in an active state, it is used to enter DRX mode when there is no data transmission. If the data transmission ends and the timer has not expired, the terminal device remains in the active state and continues to monitor the PDCCH; if the timer expires and there is no new data, the terminal device will enter a low power consumption state.

[0078] In some implementations, a start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

[0079] In some implementations, the first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer. Accordingly, the start time of the first timer can be determined based on the start time of the first time window and the first time offset.

[0080] In some implementations, the first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer. Figure 6 , the first time offset is minTimeGap, and the start time of the first timer can be determined based on the end time of the first time window and minTimeGap.

[0081] In some implementations, the first time offset is used to indicate a time interval between a reception time of the first LP-WUS and a start time of the first timer within the first time window. Figure 6, the first time offset is WUS-offset, and the start time of the first timer can be determined based on the reception time of the first LP-WUS and WUS-offset.

[0082] In some implementations, the first time offset is configured by a network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by a sub-carrier space (SCS); location information of the terminal device; resource scheduling congestion level; data transmission period; wake-up delay of the terminal device; processing delay of the terminal device; and listening period of the first LP-WUS.

[0083] In some implementations, the one or more candidate values ​​of the first time offset reported by the terminal device can be understood as part or all of the one or more first time offsets supported by the terminal device reported by the terminal device to the network device.

[0084] In some implementations, the subcarrier spacing may be understood as the frequency spacing between multiple subcarriers. For example, the subcarrier spacing may be one or more of the following: 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz.

[0085] In some implementations, the one or more candidate values ​​of the first time offset supported by the SCS may be understood as one or more first time offsets supported by the predefined or preconfigured SCS. For example, the protocol stipulates that the SCS is 15 kHz and supports 3 first time offsets.

[0086] In some implementations, the one or more candidate values ​​of the first time offset supported by the SCS can be understood as one or more first time offsets supported by the SCS reported by the terminal device. For example, the terminal device determines one or more first time offsets supported by each SCS value based on the SCS and the sleep state of the terminal device.

[0087] In some implementations, the location information of the terminal device can be understood as the absolute position or relative position of the terminal device, which is used to calculate the transmission delay of data.

[0088] In some implementations, the resource scheduling congestion level may be understood as the congestion level of transmission resources scheduled by a network device for transmitting data.

[0089] In some implementations, the wake-up delay of the terminal device can be understood as indicating the transition time of the first receiver of the terminal device from the sleep state to the PDCCH monitoring state.

[0090] In some implementations, the processing delay of the terminal device can be understood as the protocol interaction time required for the terminal device to detect the first LP-WUS and trigger the start of the first timer.

[0091] In some implementations, the monitoring period of the first LP-WUS may be understood as a period during which the terminal device monitors the first LP-WUS, that is, a period of the first time window.

[0092] In some implementations, if the first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer, the first time offset may be determined based on the data transmission period, the wake-up delay of the terminal device, and the listening period of the first LP-WUS. For example, the data scheduled by the PDCCH is VoIP, and its transmission period is T VoIP , the wake-up delay of the terminal device is Δt on , the monitoring period of the first LP-WUS is T LP―WUS , then the first time offset can be expressed by the formula Δt1 = T VoIP ―Δt on ―T LP―WUS Sure.

[0093] In some implementations, if the first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer, the start time of the first time window can be determined based on the start time of the first timer and the first time offset. At this time, the first time offset can be called the monitoring advance time of the first LP-WUS, that is, the monitoring of the first LP-WUS starts at the first time offset before the start time of the first timer. The monitoring advance time of the first LP-WUS can ensure that the terminal device has enough time to complete the monitoring of the first LP-WUS and the wake-up of the terminal device before the data arrives.

[0094] In some implementations, if the first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer, the first time offset may be determined based on one or more candidate values ​​of the first time offset reported by the terminal device, one or more candidate values ​​of the first time offset supported by the SCS, the location information of the terminal device, and the resource scheduling congestion level. For example, based on the resource scheduling congestion level and the location information of the terminal device, the network device selects a suitable first time offset for the terminal device from multiple first time offset candidate values ​​to adapt to different scenarios.

[0095] In some implementations, one or more candidate values ​​for the first time offset are determined based on one or more of: the time for the terminal device to process the first LP-WUS; the transition time for switching from the second receiver of the terminal device to the first receiver of the terminal device; the synchronization duration of the first receiver; the SCS; the sleep type supported by the terminal device; the data transmission delay requirement; and the network status information.

[0096] In some implementations, the time taken by the terminal device to process the first LP-WUS may be understood as the time taken by the terminal device to receive and decode the first LP-WUS.

[0097] In some implementations, the transition time from the second receiver of the terminal device to the first receiver of the terminal device can be understood as the time it takes for the terminal device to switch from the second receiver in the on state to the first receiver in the dormant state and wake up the first receiver in the dormant state. Figure 7 When the second receiver of the terminal device receives the first LP-WUS, the terminal device switches from the second receiver to the first receiver in the sleep state, and the time for waking up the first receiver in the sleep state is the transition time.

[0098] In some implementations, the synchronization duration of the first receiver may be understood as the duration of the first receiver performing time or frequency synchronization. Figure 7 After the second receiver of the terminal device receives the first LP-WUS, it triggers the wake-up of the first receiver after the reception and processing time of the first LP-WUS. After the first receiver wakes up from the sleep state, before monitoring the PDCCH, the first receiver needs to perform time or frequency synchronization to facilitate monitoring of the PDCCH.

[0099] In some implementations, the data transmission delay requirement may be understood as the transmission delay requirement of data scheduled by the PDCCH. For example, the data transmission delay requirement may be a packet delay budget (PDB).

[0100] In some implementations, the network status information may be understood as an indicator that can indicate the network status. For example, the network status information may be signal strength, network load, and the like.

[0101] In some implementations, the sleep type supported by the terminal device can be understood as the sleep type supported by the first receiver of the terminal device. For example, the sleep type supported by the first receiver of the terminal device includes deep sleep and / or shallow sleep.

[0102] In some implementations, the candidate value of the first time offset is determined based on the time for the terminal device to process the first LP-WUS. For example, different terminal devices may have different processing capabilities for the first LP-WUS. The stronger the processing capability, the faster the terminal device can complete the detection and decoding of the first LP-WUS, thereby shortening the first time offset. Therefore, the terminal device can select a suitable candidate value based on its own processing capability.

[0103] In some implementations, the candidate value of the first time offset is determined based on network status information. For example, under actual network conditions, factors such as signal strength and network load will also affect the selection of the first time offset. The candidate value of the first time offset can be selected based on the strength level of the signal received by the first receiver, and each strength level corresponds to a candidate value of the first time offset. For another example, under weak signal conditions, the first receiver of the terminal device may require more time to synchronize, so the candidate value of the first time offset may be larger.

[0104] In some implementations, the candidate value of the first time offset is determined based on the SCS. For example, because the SCS determines the bandwidth and time domain characteristics of the signal, when the SCS is larger (such as 60kHz or 120kHz), the time synchronization requirements are higher, and the response time of the terminal device may need to be shortened, then the first time offset is also smaller; when the SCS is smaller (such as 15kHz or 30kHz), the synchronization process of the first receiver may require more time, then the first time offset is also larger. Therefore, the terminal device needs to report a suitable candidate value for each SCS.

[0105] In some implementations, a candidate value for the first time offset can be determined based on an SCS.

[0106] In some implementations, multiple candidate values ​​of the first time offset may be determined based on one SCS. For example, due to different factors (such as SCS, sleep state, network conditions, etc.) having different requirements for the first time offset, multiple candidate values ​​of the first time offset may be determined based on each SCS.

[0107] In some implementations, the candidate values ​​of the first time offset are determined based on the SCS and the sleep types supported by the terminal device. For example, each SCS corresponds to multiple candidate values, which correspond to different sleep types of terminal devices, and the sleep type of the terminal device determines the wake-up time. In deep sleep, the terminal device completely shuts down most of the circuit modules, so it takes a long time to restart the process. In shallow sleep, some modules remain activated and can be awakened faster. This means that under different sleep types, the terminal device may choose different first time offsets to balance power consumption and communication efficiency.

[0108] In some implementations, the candidate value of the first time offset is determined based on the data transmission delay requirement and the sleep type supported by the terminal device. For example, assume that the terminal device supports two sleep types: micro-sleep with a transition time of 0ms and deep sleep with a transition time of 20ms. Then when the PDB of the data scheduled by the PDCCH is greater than 20ms, the terminal device can report a candidate value of the first time offset greater than 20ms, or when the PDB of the traffic is less than 20ms, report a candidate value of the first time offset less than 20ms. The network device will be more flexibly configured with the first time offset for the terminal device according to the different types of services transmitted.

[0109] In some implementations, the candidate value of the first time offset is determined based on the SCS, the sleep type supported by the terminal device, and the time when the terminal device processes the first LP-WUS. For example, the candidate value of the first time offset can be determined by the formula Δt1=Δt sync (SCS)+Δt sleep (Type)+Δt wus (Processing) Determine, where Δt sync (SCS) is the time required for time synchronization determined by SCS. The larger the SCS, the smaller the value, and the smaller the SCS, the larger the value; Δt sleep (Type) is the wake-up time determined by the sleep type supported by the terminal device. The smaller the value is in light sleep, the larger the value is in deep sleep; Δt wus (Processing) is the time for the terminal device to process the first LP-WUS. The smaller the value is when the processing capability of the terminal device is strong, and the larger the value is when the processing capability is weak. For another example, the SCS may be 15kHz and 60kHz, the sleep types supported by the terminal device may be light sleep and deep sleep, the time for the terminal device to process the first LP-WUS may be fast processing and slow processing, and the candidate value of the first time offset may be determined based on the permutations and combinations of the SCS in Table 1, the sleep types supported by the terminal device, and the time for the terminal device to process the first LP-WUS.

[0110] Table 1

[0111]

[0112]

[0113] In some implementations, the one or more candidate values ​​of the first time offset reported by the terminal device may be reported by the terminal device to the network device via a capability report.

[0114] In some implementations, the network device may configure the first time offset to the terminal device via DCI. For example, the network device may configure the first time offset to the terminal device using DCI format 2_6 or other DCI formats.

[0115] In some implementations, the duration of the first timer is determined based on a data transmission duration.

[0116] In some implementations, the data transmission duration may be understood as the total transmission duration of data scheduled by the PDCCH.

[0117] In some implementations, the duration of the first timer is determined based on the data transmission duration. It can be understood that the duration of the first timer is determined based on the data transmission duration and the second time offset.

[0118] In some implementations, the second time offset can be understood as redundant time used to ensure that the terminal device does not enter sleep too early, and can usually be set to a compensation time for network propagation delay or data transmission fluctuation.

[0119] In order to enable the terminal device to receive all data scheduled by the PDCCH, in some implementations, the duration of the first timer is calculated by the formula Determine, where t data is the data transmission duration, is the second time offset.

[0120] In some implementations, a period of the first timer is determined based on a data transmission period.

[0121] In some implementations, the data transmission period may be understood as a transmission period of data scheduled by the PDCCH.

[0122] In order to ensure that the first timer cooperates efficiently in each DRX cycle, the period of the first timer, that is, the period of the DRX, should match the triggering moment of the first LP-WUS. In some implementations, the period of the first timer is greater than the data transmission period to ensure that even in some cases, if the first LP-WUS fails to be ready for detection, the terminal device still has the opportunity to re-monitor the PDCCH in the next DRX cycle.

[0123] In some implementations, the period of the first timer is determined based on the data transmission period, which can be understood as the period of the first timer being determined based on the data transmission period and the third time offset.

[0124] In some implementations, the third time offset can be understood as a small time compensation to prevent the device from missing the PDCCH monitoring due to random fluctuations in the first LP-WUS monitoring or data transmission. Generally, it is recommended that the third time offset be 1 to 2 milliseconds.

[0125] In some implementations, the period of the first timer is given by the formula T timer1 =Tdata +δ is determined by, where T data is the data transmission period, and δ is the third time offset.

[0126] In some implementations, a period of the first timer is an integer multiple of a listening period of the first LP-WUS.

[0127] In some implementations, the monitoring period of the first LP-WUS can be understood as the period of the terminal device monitoring the first LP-WUS, that is, the period of the first time window. Therefore, it can also be said that the period of the first timer is an integer multiple of the period of the first time window.

[0128] In some implementations, the first time window includes multiple first LP-WUS listening opportunities to increase the flexibility of network device scheduling and LP-WUS transmission. Figure 6 The first time window includes multiple monitoring occasions (MO), where MO is the monitoring occasion of the first LP-WUS. If the terminal device detects the first LP-WUS in multiple MOs, the start time of the first timer is determined based on the first time window and the first time offset.

[0129] In some implementations, the monitoring opportunities of multiple first LP-WUS may be discontinuous, which helps to better handle the situation where the monitoring resources of the first LP-WUS are used for other channels / signals or other purposes (such as conflict with UL time slots). Of course, in the embodiment of the present application, the monitoring opportunities of multiple first LP-WUS may also be continuous.

[0130] In some implementations, the monitoring timing of the first LP-WUS may be determined based on one or more of the following: a system frame number; a subframe number; a monitoring period of the first LP-WUS; or a monitoring start offset of the first LP-WUS.

[0131] In the traditional standard protocol, the non-integer C-DRX cycle is defined to match the non-integer service cycle (e.g., extended reality (XR) cycle). Considering low power consumption, a small-granularity first LP-WUS listening cycle (e.g., a value of 1ms) can be used to match the non-integer C-DRX cycle, and the non-integer first LP-WUS listening cycle is not defined. Since the traditional drx-startOffset is defined to determine the start timing of PDCCH monitoring, the first LP-WUS listening start offset (drx-WusStartOffset) can be used to determine the listening timing of LP-WUS.

[0132] In some implementations, the monitoring timing of the first LP-WUS can be determined by the formula [(SFN×10)+subframenumber-(drx-WusStartOffset-timeOffset)]mod(LP-WUS-cycle), wherein SFN is the system frame number, subframe number is the subframe number, LP-WUS-cycle is the monitoring cycle of the first LP-WUS, drx-WusStartOffset is the monitoring start offset of the first LP-WUS, and timeOfFset is an offset used to adjust the monitoring timing of the first LP-WUS. That is to say, the system frame and subframe that meet the condition [(SFN×10)+subframe number-(drx-WusStartOffset-timeOffset)]mod(LP-WUS-cycle) can be used as the monitoring timing of the first LP-WUS.

[0133] In some implementations, the start time of the first time window is determined based on one or more of the following: a start time of data transmission; and a listening period of the first LP-WUS.

[0134] In some implementations, the data transmission start time may be understood as the data transmission start time scheduled by the PDCCH.

[0135] In some implementations, the start time of the first time window is determined based on the data transmission start time and the listening period of the first LP-WUS.

[0136] The first timer may be responsible for controlling when the terminal device enters the PDCCH listening state. In order to start the timer before the data frame arrives at the terminal device, the start time of the first time window should be slightly earlier than the transmission period of the data frame. In some implementations, the start time of the first time window is calculated by the formula t time window 1 = t data -T wus Determine, where t data is the start time of data transmission, T wus For example, for periodic traffic such as VoIP, there is usually a stable transmission period (such as transmitting a voice frame every 20ms). First, we need to know the data transmission period T VoIP, and clearly know when data will arrive in each cycle. The typical VoIP transmission cycle usually ranges from 20ms to 50ms. For applications such as VoIP, the timing of data transmission is predictable because the transmission rate of voice frames is usually fixed. Therefore, the network device can configure the appropriate listening time of the first LP-WUS in advance by understanding these characteristics, that is, the start time of the first time window. In order to reasonably start the first timer before the VoIP data arrives, the terminal device needs to listen to the first LP-WUS at a reasonable advance time point. This advance time point should be early enough to ensure that the device has time to wake up and prepare to receive data, but it should not be too early to avoid wasting power. Assume that the transmission period of VoIP traffic is T VoIP , the transmission start time is t0, in order to wake up the device and start the first timer before the data arrives, so the monitoring start time of the first LP-WUS, that is, the start time of the first time window should be calculated by the formula t time window 1=t0-T wus Sure.

[0137] In order to efficiently utilize LP-WUS, the network device and the terminal device need to coordinately configure the DRX and LP-WUS mechanisms so that the LP-WUS monitoring period is adapted to the data transmission period, and the terminal device can be woken up in advance before each data traffic period arrives, while maintaining a low power consumption state when not needed. In some implementations, the first LP-WUS monitoring period should be the same as the data transmission period, that is, the period of the first time window is the same as the data transmission period.

[0138] In some implementations, the parameters of the first time window and / or the first timer are determined based on the network load and / or traffic information using a model. For example, the historical data transmission mode and network load are analyzed by the model, and the future traffic and load conditions are predicted. Based on the prediction results of the model, the period of the first timer, the first time offset, and the period of the first timer and other parameters are dynamically adjusted to achieve a more accurate energy saving effect. For another example, the listening period of the first LP-WUS can be dynamically adjusted. If the model predicts a decrease in traffic or a decrease in network load, the listening period of the first LP-WUS can be extended to reduce the wake-up frequency, which can be calculated by formula T wus =max{T data -Δt on , Δt1} determines the listening period of the first LP-WUS, where T data is the data transmission period, Δt on is the wake-up delay of the terminal device, and Δt1 is the first time offset.

[0139] In some implementations, during the operation of the first timer, the content reported by the terminal device can be determined based on the type of the timer.

[0140] In some implementations, if the first timer is drx-onDurationTimer or drx-InactivityTimer, the terminal device may perform periodic channel state information (CSI) / layer-1 reference signal received power (L1-RSRP) reporting. For example, if the first LP-WUS triggers drx-onDurationTimer, periodic CSI / L1-RSRP should be reported in the dynamic PDCCH monitoring state.

[0141] Uplink (UL) / downlink (DL) transmission may require CSI reporting, but L1-RSRP reporting is unnecessary. In some implementations, if the first timer is drx-onDurationTimer, the terminal device may choose not to report L1-RSRP.

[0142] In some implementations, if the first timer is a dedicated timer for LP-WUS, it is possible to configure, as needed, whether the terminal device periodically reports CSI / L1-RSRP during the operation of the dedicated timer for LP-WUS.

[0143] In order to adapt the terminal device to different data traffic types, in some implementations, the terminal device can monitor the first LP-WUS both outside and within the traditional C-DRX active time. For example, the first timer is drx-onDurationTimer, and the first LP-WUS monitoring before drx-onDurationTimer can be applicable to predictable periodic traffic such as VoIP, while the first LP-WUS monitoring outside the traditional C-DRX active time is designed for unpredictable or unaligned periodic services such as XR, see Table 2 for details.

[0144] Table 2

[0145]

[0146] Since LP-WUS monitoring consumes much less power of the terminal device than PDCCH monitoring, a smaller LP-WUS monitoring period can reduce service delay. In some implementations, the first LP-WUS monitoring period is smaller than the period of the first timer. For example, if the period of the first timer is the period of C-DRX, the first LP-WUS monitoring period is smaller than the long period of C-DRX and / or the short period of C-DRX.

[0147] In some implementations, the first LP-WUS carries one or more of the following: an identifier of a terminal device; information for instructing the terminal device to trigger monitoring of a PDCCH; information for instructing the terminal device to monitor a carrier of a PDCCH.

[0148] In some implementations, the terminal device identifier may be a radio network temporary identity (RNTI). For example, a 16-bit RNTI is used to uniquely identify a specific terminal device in a connected state, and the first LP-WUS carries the RNTI, which helps the terminal device determine whether the first LP-WUS is used to wake itself up to avoid false wake-up.

[0149] In some implementations, the first LP-WUS carries information for instructing the terminal device to trigger monitoring of PDCCH. It can be understood that when the terminal device receives the first LP-WUS, it can trigger monitoring of PDCCH in the first time period based on the information carried by the first LP-WUS for instructing the terminal device to trigger monitoring of PDCCH.

[0150] In some implementations, the first LP-WUS carries information for indicating the carrier on which the terminal device monitors the PDCCH. It can be understood that the terminal device receives the first LP-WUS and can determine the carrier on which it monitors the PDCCH based on the first LP-WUS. The terminal device supports LP-WUS when carrier aggregation (CA) is configured in the connected state. For CA, supporting LP-WUS to wake up only some carriers helps save power of the terminal device.

[0151] Supporting LP-WUS for carrier aggregation (CA) in connected mode can save power by waking up only some carriers. By flexibly managing the activity status of multiple carriers, LP-WUS can help terminal devices wake up only some carriers, thereby reducing unnecessary power consumption. In the scenario of carrier aggregation, terminal devices may use multiple carriers (such as primary and secondary carriers) at the same time. Normally, the RF components of multiple carriers remain active, but in many cases not all carriers are required to transmit data.

[0152] In some implementations, the information used to indicate the carriers on which the terminal device monitors the PDCCH can be a bitmap, using the bitmap to indicate one or more carriers. This approach allows flexible data scheduling and energy-saving opportunities, and some terminal devices can turn off the RF components of certain specific carriers, so there is no need to turn all carriers on or off. When wake-up is required, the bitmap indicates which carriers need to participate in data transmission instead of activating all carriers at the same time. A bitmap is a mechanism for indicating the wake-up state of a carrier. Through the bitmap, network devices can flexibly control which carriers need to be woken up and which carriers can remain turned off or in a low-power state.

[0153] In some implementations, each bit of the bitmap corresponds to a specific carrier. If the bit is "1", it means that the carrier needs to wake up and prepare to receive data; if the bit is "0", it means that the carrier can remain dormant or turned off. This mechanism reduces unnecessary power consumption and quickly wakes up the carrier for data transmission when needed. For example, in certain scenarios, network devices may only need to use a small number of carriers to transmit data, thereby avoiding unnecessary carrier switching and signal interference. Such scheduling flexibility helps optimize the utilization of network resources while improving overall energy efficiency.

[0154] Based on the information of the carrier on which the terminal device monitors the PDCCH indicated by the LP-WUS, one or more service cells to which the LP-WUS applies can be determined, or the LP-WUS applies to all activated service cells. In general, the power saving mode is more suitable for the single CA case. However, it should also work in CA mode. This mechanism may not be optimal. Considering that if the RF of the first receiver and the RF of the second receiver are in different carriers, they will be very independent, making it difficult to support cross-carrier association of the LP-WUS. In some implementations, a service cell should be indicated only by the first LP-WUS in the same carrier.

[0155] In order to avoid any misalignment between the network device and the terminal device when activating LP-WUS to monitor PDCCH, the terminal device may send a confirmation message to the network device. In some implementations, the terminal device sends first confirmation information to the network device, and the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

[0156] In some implementations, before the terminal device monitors the first LP-WUS, the terminal device receives a trigger message sent by the network device, where the trigger message is used to trigger a first receiver of the terminal device to wake up a second receiver of the terminal device, and the power consumption of the first receiver is higher than that of the second receiver.

[0157] In some implementations, the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device. It can be understood that the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device and trigger the second receiver of the terminal device to monitor the first LP-WUS. For example, see Figure 8 The first receiver is MR and the second receiver is LR. Before receiving the trigger message, MR is in the on state and LR is in the off state. When MR receives the trigger message, MR is triggered to wake up LR. After LR enters the on state, it starts to monitor the first LP-WUS.

[0158] In some implementations, the terminal device sends second confirmation information to the network device, where the second confirmation information is used to indicate that the terminal device has received the trigger message.

[0159] In some implementations, the first confirmation information and the second confirmation information may be carried in the same request. For example, after the second receiver of the terminal device receives the first LP-WUS, the first receiver of the terminal device sends a request carrying the first confirmation information and the second confirmation information to confirm that the terminal device has received the trigger message and the first LP-WUS.

[0160] In some other implementations, the first confirmation information and the second confirmation information may be carried in different requests. Figure 8 , the first receiver is MR, the second receiver is LR, the network device sends a trigger request to the MR of the terminal device, and after the MR of the terminal device receives the trigger message, it triggers the LR to switch from the closed state to the open state. The MR of the terminal device sends a second confirmation request to the network device, and the second confirmation request carries the second confirmation information to confirm that the MR has successfully received the trigger message. The LR of the terminal device listens to the first LP-WUS in the open state. When the LR of the terminal device receives the first LP-WUS, the MR of the terminal device sends a first confirmation request to the network device, and the first confirmation request carries the first confirmation information to confirm that the LR has successfully received the first LP-WUS. After the handshake process, the network device and the terminal device establish a reliable consensus on the use of MR or LR to avoid transmission or reception loss between the network device and the terminal device.

[0161] In some implementations, if the network device misses the first confirmation message and the second confirmation message, the network device may resend the trigger message or the first LP-WUS until receiving the confirmation message.

[0162] In some implementations, after the terminal device sends the first confirmation information, the first receiver of the terminal device enters a sleep state. Figure 8The first receiver is MR, the second receiver is LR, and after MR sends the first confirmation information to the network device, MR enters the sleep state after a delay from the on state.

[0163] As can be seen from the above, the terminal device may include a first receiver and a second receiver. An important question is the assumption about whether the first receiver and the second receiver can receive DL signals at the same time. In some implementations, this capability is closely related to the implementation of the terminal device. For example, if there is a switch between the antenna and the first receiver or the second receiver, the terminal device can definitely only use one of the two receivers at a time. If the first receiver and the second receiver are connected to the antenna without a switch, the terminal device can use both receivers at the same time, but since the total received power is divided into different branches (corresponding to different receivers), there may be some signal power loss. If the power is evenly distributed to the two branches (ie, two receivers), both receivers may introduce a few dB signal-to-noise ratio loss. When the terminal device has only one receiver, in the connected state mode, when DL traffic arrives, LP-WUS can at least trigger PDCCH monitoring.

[0164] In some implementations, if the terminal device includes two receivers, namely the first receiver and the second receiver mentioned above, the terminal device may also allow the first receiver to receive the DL signal from the network device based on its own capabilities and implementation mechanism.

[0165] The LP-WUS indication in the connected state triggers the PDCCH monitoring of the first receiver, and the LP-WUS only affects the PDCCH monitoring of the first receiver. For DL ​​configured resources, such as DL semi-persistent scheduling (SPS), since the network device allocates DL SPS resources knowing that LP-WUS is enabled, the network device hopes that the terminal device performs traditional operations on the DL SPS resources, and there is no mismatch between the terminal device and the network device in the monitoring of the first receiver or the second receiver. In some implementations, the terminal device should monitor the DL SPS resources through the first receiver to avoid losing any DL data.

[0166] However, for UL configured resources, such as configured grant type 1 or configured grant category 2 (UL SPS), sometimes there are UL configured assets, but the terminal device has no UL data for transmission. If UL skipping is not enabled, the terminal device should still send padding bits in the UL configured resources, which will result in additional power consumption. In some implementations, if the terminal device is using the first LP-WUS to trigger PDCCH monitoring, if there is no UL data available, the UL configuration is skipped. In this way, the terminal device does not need to turn on the first receiver and continue to monitor the LP-WUS, which helps to further reduce the power consumption of the terminal device.

[0167] Since the power consumption of monitoring the first LP-WUS at the second receiver is much lower than the power consumption of monitoring PDCCH at the first receiver, the monitoring of PDCCH can be additionally triggered according to the traditional C-DRX cycle. If the first timer needs to be started according to the business mode or other factors, and the timer is not started by the first LP-WUS, the terminal device needs to confirm whether it needs to monitor the second LP-WUS during the operation of the first timer.

[0168] In some implementations, if the start of the first timer is not triggered by the first LP-WUS, the terminal device performs one or more of the following operations during the operation of the first timer: not monitoring the second LP-WUS, where the second LP-WUS is sent by the network device to the terminal device after the first LP-WUS; monitoring the second LP-WUS; and determining whether to monitor the second LP-WUS based on the first LP-WUS.

[0169] In some implementations, the start of the first timer is not triggered by the first LP-WUS, which can be understood as the terminal device does not monitor or receive the first LP-WUS, and the first timer is started by the traditional C-DRX configuration.

[0170] In some implementations, the start of the first timer is not triggered by the first LP-WUS, which can be understood as the terminal device receives the first LP-WUS, the first LP-WUS does not indicate triggering the start of the first timer, and the first timer is started by the traditional C-DRX configuration.

[0171] In some implementations, determining whether to monitor the second LP-WUS based on the first LP-WUS can be understood as follows: the terminal device receives the first LP-WUS, the first LP-WUS does not indicate triggering the start of the first timer, the first timer is started by a traditional C-DRX cycle, and during the operation of the first timer, the terminal device determines whether to monitor the second LP-WUS based on the information indicated by the first LP-WUS.

[0172] Combination of the above Figures 1 to 8, describes the method embodiment of the present application in detail, and the following is combined with Figures 9 to 11 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0173] Fig. 9 It is a schematic diagram of a terminal device according to an embodiment of the present application. Fig. 9 The terminal device 900 shown includes: a receiving unit 910 and a monitoring unit 920 .

[0174] A receiving unit 910 is configured to receive a first low power consumption wake-up signal LP-WUS sent by a network device;

[0175] The monitoring unit 920, in response to receiving the first LP-WUS, is configured to monitor a physical downlink control channel PDCCH within a first time period.

[0176] In some implementations, the first time period is determined based on a first timer, and the first timer includes one or more of the following: a non-continuous reception DRX inactivity timer; a DRX continuous timer; and a timer triggered by the first LP-WUS.

[0177] In some implementations, the first timer is determined based on one or more of the following: service type; data transmission mode; data flow characteristics; quality of service requirements; and network load information.

[0178] In some implementations, the start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

[0179] In some implementations, the first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or the first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

[0180] In some implementations, the first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; location information of the terminal device; resource scheduling congestion level; data transmission period; wake-up delay of the terminal device; processing delay of the terminal device; and listening period of the first LP-WUS.

[0181] In some implementations, the candidate value is determined based on one or more of: the time for the terminal device to process the first LP-WUS; the transition time of switching from the second receiver of the terminal device to the first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; the synchronization duration of the first receiver; SCS; the sleep type supported by the terminal device; data transmission latency requirements; and network status information.

[0182] In some implementations, the duration of the first timer is determined based on a data transmission duration.

[0183] In some implementations, a period of the first timer is determined based on a data transmission period.

[0184] In some implementations, the first time window includes multiple listening opportunities of the first LP-WUS, and the listening opportunities are determined based on one or more of the following: system frame number; subframe number; listening period of the first LP-WUS; and listening start offset of the first LP-WUS.

[0185] In some implementations, the start time of the first time window is determined based on one or more of the following: a start time of data transmission; and a listening period of the first LP-WUS.

[0186] In some implementations, parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

[0187] In some implementations, the first LP-WUS carries one or more of the following: an identifier of the terminal device; information for instructing the terminal device to trigger monitoring of the PDCCH; and information for instructing the terminal device to monitor a carrier of the PDCCH.

[0188] In some implementations, the terminal device further includes: a sending unit, configured to send first confirmation information to the network device, wherein the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

[0189] In some implementations, the terminal device also includes: before the listening unit listens to the first LP-WUS, the receiving unit 910 is also used to receive a trigger message sent by the network device, and the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device, and the power consumption of the first receiver is higher than the power consumption of the second receiver.

[0190] In some implementations, the terminal device further includes: the sending unit is further used to send second confirmation information to the network device, and the second confirmation information is used to indicate that the terminal device has received the trigger message.

[0191] In some implementations, the terminal device further includes: an execution unit, wherein if the start of the first timer is not triggered by the first LP-WUS, the execution unit is used to perform one or more of the following operations during the operation of the first timer: not monitoring a second LP-WUS, where the second LP-WUS is sent by the network device to the terminal device after the first LP-WUS; monitoring the second LP-WUS; and determining whether to monitor the second LP-WUS based on the first LP-WUS.

[0192] Fig.10 It is a schematic diagram of a network device according to an embodiment of the present application. Fig.10 The network device 1000 shown includes: a sending unit 1010 .

[0193] The sending unit 1010 is used to send a first low power wake-up signal LP-WUS to a terminal device; the first LP-WUS is used to trigger the terminal device to monitor a physical downlink control channel PDCCH within a first time period.

[0194] In some implementations, the first time period is determined based on a first timer, and the first timer includes one or more of the following: a non-continuous reception DRX inactivity timer; a DRX continuous timer; and a timer triggered by the first LP-WUS.

[0195] In some implementations, the first timer is determined based on one or more of the following: service type; data transmission mode; data flow characteristics; quality of service requirements; and network load information.

[0196] In some implementations, the start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

[0197] In some implementations, the first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or the first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

[0198] In some implementations, the first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; location information of the terminal device; resource scheduling congestion level; data transmission period; wake-up delay of the terminal device; processing delay of the terminal device; and listening period of the first LP-WUS.

[0199] In some implementations, the candidate value is determined based on one or more of: the time for the terminal device to process the first LP-WUS; the transition time of switching from the second receiver of the terminal device to the first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; the synchronization duration of the first receiver; the subcarrier spacing SCS; the sleep type supported by the terminal device; the data transmission delay requirement; and the network status information.

[0200] In some implementations, the duration of the first timer is determined based on a data transmission duration.

[0201] In some implementations, a period of the first timer is determined based on a data transmission period.

[0202] In some implementations, the first time window includes multiple listening opportunities of the first LP-WUS, and the listening opportunities are determined based on one or more of the following: system frame number; subframe number; listening period of the first LP-WUS; and listening start offset of the first LP-WUS.

[0203] In some implementations, the start time of the first time window is determined based on one or more of the following: a start time of data transmission; and a listening period of the first LP-WUS.

[0204] In some implementations, parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

[0205] In some implementations, the first LP-WUS carries one or more of the following: an identifier of the terminal device; information for instructing the terminal device to trigger monitoring of the PDCCH; and information for instructing the terminal device to monitor a carrier of the PDCCH.

[0206] In some implementations, the network device further includes: a receiving unit, configured to receive first confirmation information sent by the terminal device, wherein the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

[0207] In some implementations, the network device also includes: before the sending unit 1010 sends the first LP-WUS, the sending unit 1010 is also used to send a trigger message to the terminal device, and the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device, and the power consumption of the first receiver is higher than the power consumption of the second receiver.

[0208] In some implementations, the network device further includes: the receiving unit is further used to receive second confirmation information sent by the terminal device, and the second confirmation information is used to indicate that the terminal device has received the trigger message.

[0209] In an optional embodiment, the receiving unit 910 may be a transceiver 1130, and the monitoring unit 920 may also be a transceiver 1130. The terminal device 900 may also include a processor 1110 and a memory 1120. Fig.11 shown.

[0210] In an optional embodiment, the sending unit 1010 may be a transceiver 1130. The network device 1000 may further include a processor 1110 and a memory 1120. Fig.11 shown.

[0211] Fig.11 It is a schematic structural diagram of a communication device according to an embodiment of the present application. Fig.11 The dotted line in the figure indicates that the unit or module is optional. The device 1100 can be used to implement the method described in the above method embodiment. The device 1100 can be a chip, a terminal device or a network device.

[0212] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the above method embodiment. The processor 1110 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 also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0213] The apparatus 1100 may further include one or more memories 1120. The memory 1120 stores a program, which can be executed by the processor 1110, so that the processor 1110 executes the method described in the above method embodiment. The memory 1120 may be independent of the processor 1110 or integrated in the processor 1110.

[0214] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips through the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips through the transceiver 1130.

[0215] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0216] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0217] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal or network device in each embodiment of the present application.

[0218] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0219] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

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

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

[0222] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0223] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

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

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

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

[0227] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0228] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a first low power consumption wake-up signal LP-WUS sent by the network device; In response to receiving the first LP-WUS, the terminal device monitors a physical downlink control channel PDCCH within a first time period.

2. The method according to claim 1, characterized in that The first time period is determined based on a first timer, and the first timer includes one or more of the following: Discontinuous reception DRX inactivity timer; DRX duration timer; The first LP-WUS triggers a timer.

3. The method according to claim 2, characterized in that The first timer is determined based on one or more of the following: Type of business; Data transmission mode; Data traffic characteristics; Service quality requirements; Network load information.

4. The method according to claim 2 or 3, characterized in that The start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

5. The method according to claim 4, characterized in that The first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or The first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

6. The method according to claim 5, characterized in that The first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; The location information of the terminal device; Resource scheduling congestion level; Data transmission cycle; The wake-up delay of the terminal device; The processing delay of the terminal device; The monitoring period of the first LP-WUS.

7. The method according to claim 6, characterized in that The candidate values ​​are determined based on one or more of the following: time for the terminal device to process the first LP-WUS; a transition time for switching from a second receiver of the terminal device to a first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; a synchronization duration of the first receiver; SCS; The sleep type supported by the terminal device; Data transmission delay requirements; Network status information.

8. The method according to any one of claims 2 to 7, characterized in that The duration of the first timer is determined based on the data transmission duration.

9. The method according to any one of claims 2 to 8, characterized in that The period of the first timer is determined based on a data transmission period.

10. The method according to claim 4, characterized in that The first time window includes a plurality of monitoring opportunities of the first LP-WUS, and the monitoring opportunities are determined based on one or more of the following: System frame number; Subframe number; a monitoring period of the first LP-WUS; The monitoring start of the first LP-WUS is offset.

11. The method according to claim 4 or 10, characterized in that The start time of the first time window is determined based on one or more of the following: The data transmission start time; The monitoring period of the first LP-WUS.

12. The method according to claim 4, characterized in that Parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

13. The method according to any one of claims 1 to 12, characterized in that The first LP-WUS carries one or more of the following: The identification of the terminal device; Information used to instruct the terminal device to trigger monitoring of the PDCCH; Information used to instruct the terminal device to monitor the carrier of the PDCCH.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: The terminal device sends first confirmation information to the network device, where the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: Before the terminal device monitors the first LP-WUS, the terminal device receives a trigger message sent by the network device, where the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device, and the power consumption of the first receiver is higher than that of the second receiver.

16. The method according to claim 15, characterized in that The method further comprises: The terminal device sends second confirmation information to the network device, where the second confirmation information is used to indicate that the terminal device has received the trigger message.

17. The method according to any one of claims 2 to 16, characterized in that The method further comprises: If the start of the first timer is not triggered by the first LP-WUS, the terminal device performs one or more of the following operations during the operation of the first timer: not monitoring a second LP-WUS, where the second LP-WUS is sent by the network device to the terminal device after the first LP-WUS; monitoring the second LP-WUS; and determining whether to monitor the second LP-WUS based on the first LP-WUS.

18. A wireless communication method, characterized in that: include: The network device sends a first low power consumption wake-up signal LP-WUS to the terminal device; The first LP-WUS is used to trigger the terminal device to monitor a physical downlink control channel PDCCH within a first time period.

19. The method according to claim 18, characterized in that The first time period is determined based on a first timer, and the first timer includes one or more of the following: Discontinuous reception DRX inactivity timer; DRX duration timer; The first LP-WUS triggers a timer.

20. The method of claim 19, wherein: The first timer is determined based on one or more of the following: Type of business; Data transmission mode; Data traffic characteristics; Service quality requirements; Network load information.

21. The method according to claim 19 or 20, characterized in that The start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

22. The method according to claim 21, characterized in that The first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or The first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

23. The method of claim 22, wherein: The first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; The location information of the terminal device; Resource scheduling congestion level; Data transmission cycle; The wake-up delay of the terminal device; The processing delay of the terminal device; The monitoring period of the first LP-WUS.

24. The method of claim 23, wherein: The candidate values ​​are determined based on one or more of the following: time for the terminal device to process the first LP-WUS; a transition time for switching from a second receiver of the terminal device to a first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; a synchronization duration of the first receiver; SCS; The sleep type supported by the terminal device; Data transmission delay requirements; Network status information.

25. The method according to any one of claims 19 to 24, characterized in that The duration of the first timer is determined based on the data transmission duration.

26. The method according to any one of claims 19 to 25, characterized in that The period of the first timer is determined based on a data transmission period.

27. The method of claim 21, wherein: The first time window includes a plurality of monitoring opportunities of the first LP-WUS, and the monitoring opportunities are determined based on one or more of the following: System frame number; Subframe number; a monitoring period of the first LP-WUS; The monitoring start of the first LP-WUS is offset.

28. The method according to claim 21 or 27, characterized in that The start time of the first time window is determined based on one or more of the following: The data transmission start time; The monitoring period of the first LP-WUS.

29. The method of claim 21, wherein: Parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

30. The method according to any one of claims 18 to 29, characterized in that The first LP-WUS carries one or more of the following: The identification of the terminal device; Information used to instruct the terminal device to trigger monitoring of the PDCCH; Information used to instruct the terminal device to monitor the carrier of the PDCCH.

31. The method according to any one of claims 18 to 30, characterized in that The method further comprises: The network device receives first confirmation information sent by the terminal device, where the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

32. The method according to any one of claims 18 to 31, characterized in that The method further comprises: Before the network device sends the first LP-WUS, the network device sends a trigger message to the terminal device, where the trigger message is used to trigger a first receiver of the terminal device to wake up a second receiver of the terminal device, and power consumption of the first receiver is higher than that of the second receiver.

33. The method of claim 32, wherein: The method further comprises: The network device receives second confirmation information sent by the terminal device, where the second confirmation information is used to indicate that the terminal device has received the trigger message.

34. A terminal device, characterized in that: include: A receiving unit, configured to receive a first low power consumption wake-up signal LP-WUS sent by a network device; The monitoring unit is configured to monitor a physical downlink control channel (PDCCH) within a first time period in response to receiving the first LP-WUS.

35. The terminal device according to claim 34, characterized in that: The first time period is determined based on a first timer, and the first timer includes one or more of the following: Discontinuous reception DRX inactivity timer; DRX duration timer; The first LP-WUS triggers a timer.

36. The terminal device according to claim 35, characterized in that The first timer is determined based on one or more of the following: Type of business; Data transmission mode; Data traffic characteristics; Service quality requirements; Network load information.

37. The terminal device according to claim 35 or 36, characterized in that: The start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

38. The terminal device according to claim 37, characterized in that: The first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or The first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

39. The terminal device according to claim 38, characterized in that: The first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; The location information of the terminal device; Resource scheduling congestion level; Data transmission cycle; The wake-up delay of the terminal device; The processing delay of the terminal device; The monitoring period of the first LP-WUS.

40. The terminal device according to claim 39, characterized in that: The candidate values ​​are determined based on one or more of the following: time for the terminal device to process the first LP-WUS; a transition time for switching from a second receiver of the terminal device to a first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; a synchronization duration of the first receiver; SCS; The sleep type supported by the terminal device; Data transmission delay requirements; Network status information.

41. The terminal device according to any one of claims 35 to 40, characterized in that: The duration of the first timer is determined based on the data transmission duration.

42. The terminal device according to any one of claims 35 to 41, characterized in that: The period of the first timer is determined based on a data transmission period.

43. The terminal device according to claim 37, characterized in that: The first time window includes a plurality of monitoring opportunities of the first LP-WUS, and the monitoring opportunities are determined based on one or more of the following: System frame number; Subframe number; a monitoring period of the first LP-WUS; The monitoring start of the first LP-WUS is offset.

44. The terminal device according to claim 37 or 43, characterized in that: The start time of the first time window is determined based on one or more of the following: The data transmission start time; The monitoring period of the first LP-WUS.

45. The terminal device according to claim 37, characterized in that: Parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

46. ​​The terminal device according to any one of claims 34 to 45, characterized in that: The first LP-WUS carries one or more of the following: The identification of the terminal device; Information used to instruct the terminal device to trigger monitoring of the PDCCH; Information used to instruct the terminal device to monitor the carrier of the PDCCH.

47. The terminal device according to any one of claims 34 to 46, characterized in that: The terminal device further includes: A sending unit is used to send first confirmation information to the network device, where the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

48. The terminal device according to any one of claims 34 to 47, characterized in that: The terminal device further includes: Before the monitoring unit monitors the first LP-WUS, the receiving unit is also used to receive a trigger message sent by the network device, wherein the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device, and the power consumption of the first receiver is higher than that of the second receiver.

49. The terminal device according to claim 48, characterized in that The terminal device further includes: The sending unit is further used to send second confirmation information to the network device, where the second confirmation information is used to indicate that the terminal device has received the trigger message.

50. The terminal device according to any one of claims 35 to 49, characterized in that: The terminal device further includes: An execution unit, wherein if the start of the first timer is not triggered by the first LP-WUS, the execution unit is configured to perform one or more of the following operations during the operation of the first timer: not monitoring a second LP-WUS, where the second LP-WUS is sent by the network device to the terminal device after the first LP-WUS; monitoring the second LP-WUS; and determining whether to monitor the second LP-WUS based on the first LP-WUS.

51. A network device, characterized in that: include: A sending unit, configured to send a first low power consumption wake-up signal LP-WUS to a terminal device; The first LP-WUS is used to trigger the terminal device to monitor a physical downlink control channel PDCCH within a first time period.

52. The network device according to claim 51, characterized in that The first time period is determined based on a first timer, and the first timer includes one or more of the following: Discontinuous reception DRX inactivity timer; DRX duration timer; The first LP-WUS triggers a timer.

53. The network device according to claim 52, characterized in that The first timer is determined based on one or more of the following: Type of business; Data transmission mode; Data traffic characteristics; Service quality requirements; Network load information.

54. The network device according to claim 52 or 53, characterized in that: The start time of the first timer is determined based on a first time window and a first time offset, and the first time window is used to monitor the first LP-WUS.

55. The network device according to claim 54, characterized in that The first time offset is used to indicate the time interval between the start time of the first time window and the start time of the first timer; or The first time offset is used to indicate the time interval between the end time of the first time window and the start time of the first timer.

56. The network device according to claim 55, characterized in that The first time offset is configured by the network device, and the first time offset is determined based on one or more of the following: one or more candidate values ​​of the first time offset reported by the terminal device; one or more candidate values ​​of the first time offset supported by the subcarrier spacing SCS; The location information of the terminal device; Resource scheduling congestion level; Data transmission cycle; The wake-up delay of the terminal device; The processing delay of the terminal device; The monitoring period of the first LP-WUS.

57. The network device according to claim 56, characterized in that The candidate values ​​are determined based on one or more of the following: time for the terminal device to process the first LP-WUS; a transition time for switching from a second receiver of the terminal device to a first receiver of the terminal device, the power consumption of the first receiver being higher than the power consumption of the second receiver; a synchronization duration of the first receiver; SCS; The sleep type supported by the terminal device; Data transmission delay requirements; Network status information.

58. The network device according to any one of claims 52 to 57, characterized in that: The duration of the first timer is determined based on the data transmission duration.

59. The network device according to any one of claims 52 to 58, characterized in that: The period of the first timer is determined based on a data transmission period.

60. The network device according to claim 54, characterized in that The first time window includes a plurality of monitoring opportunities of the first LP-WUS, and the monitoring opportunities are determined based on one or more of the following: System frame number; Subframe number; a monitoring period of the first LP-WUS; The monitoring start of the first LP-WUS is offset.

61. The network device according to claim 54 or 60, characterized in that: The start time of the first time window is determined based on one or more of the following: The data transmission start time; The monitoring period of the first LP-WUS.

62. The network device according to claim 54, characterized in that Parameters of the first time window and / or the first timer are determined using a model based on network load and / or traffic information.

63. The network device according to any one of claims 51 to 62, characterized in that: The first LP-WUS carries one or more of the following: The identification of the terminal device; Information used to instruct the terminal device to trigger monitoring of the PDCCH; Information used to instruct the terminal device to monitor the carrier of the PDCCH.

64. The network device according to any one of claims 51 to 63, characterized in that: The network device also includes: The receiving unit is used to receive first confirmation information sent by the terminal device, where the first confirmation information is used to indicate that the terminal device has received the first LP-WUS.

65. The network device according to any one of claims 51 to 64, characterized in that: The network device also includes: Before the sending unit sends the first LP-WUS, the sending unit is also used to send a trigger message to the terminal device, wherein the trigger message is used to trigger the first receiver of the terminal device to wake up the second receiver of the terminal device, and the power consumption of the first receiver is higher than that of the second receiver.

66. The network device according to claim 65, characterized in that The network device also includes: The receiving unit is further used to receive second confirmation information sent by the terminal device, where the second confirmation information is used to indicate that the terminal device has received the trigger message.

67. A terminal device, characterized in that: The terminal comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal executes the method as described in any one of claims 1 to 17.

68. A network device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method as described in any one of claims 18-33.

69. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to cause the device to execute a method as claimed in any one of claims 1 to 33.

70. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as described in any one of claims 1 to 33.

71. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 33.

72. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 33.

73. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 33.

Images