RU2773519C1 - Method for detecting a wakeup signal and terminal apparatus - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: method for detecting a wakeup signal includes: the terminal apparatus sending the a first information to the network apparatus, wherein the first information indicates the reported interval; the terminal apparatus receiving the second information sent by the network apparatus, indicating the state of configuration of the first interval and the state of configuration of the second interval; determining the state of configuration of the first interval and the state of configuration of the second interval by the terminal apparatus, based on the second information; determining the target interval by the terminal apparatus, based on the reported interval, the state of configuration of the first interval and the state of configuration of the second interval; and detecting a wakeup signal by the terminal apparatus in the detection position before the initial position of the first paging event in the paging time window, wherein the detection position is determined based on the target interval and the maximum duration of the wakeup signal.

EFFECT: possibility of determining the position for detecting a wakeup signal by the terminal apparatus so as to prevent blind detection of the wakeup signal by the terminal apparatus, thereby reducing the energy consumption of the terminal apparatus.

20 cl, 12 dwg, 2 tbl

Description

Technical field

[0001] The present application relates to the field of communications and, more specifically, to a method for detecting a wake-up signal and a terminal device in a communication system.

State of the art

[0002] The Internet of Things (IoT) is a network focused on Machine Type Communication (MTC), and this is an important type of networks in the field of future communications. IoT communication is mainly applied to smart meter reading, medical detection and monitoring, logistics detection, industrial detection and monitoring, Internet of vehicles, smart community, wearable device communication, etc. There are various IoT application scenarios, from outdoor to indoor and from above ground to underground. Therefore, there are many special requirements for the IoT project.

[0003] Extended coverage: Many IoT terminals are located in areas with poor coverage. For example, electricity and water meters are often located in places with weak wireless network signals, such as indoors or basements. Therefore, coverage enhancement technology is needed to improve communication quality in areas with poor signal coverage.

[0004] A large number of terminals: The number of IoT devices is much greater than the number of devices for communication between people.

[0005] Low Service Rate and Delay Insensitivity: Data packets transmitted by IoT devices are typically small in size and insensitive to delays.

[0006] Extremely low cost: Many IoT applications require very low end device costs to enable large-scale deployment.

[0007] Low power consumption: In most cases, IoT devices are powered by batteries and can be used for more than 10 years without changing batteries. This requires IoT devices to operate with extremely low power consumption.

[0008] To meet these specific requirements, the 3rd Generation Partnership Project (3GPP) Mobile Standards Organization agreed on a new study topic at the 62nd Global System for Mobile Radio Access Network meeting. Mobile Communications, GSM) / Development in terms of increased data rates for GSM (Enhanced Data Rates for GSM Evolution, EDGE) (GSM / EDGE Radio Access Network, GERAN) to explore a method to support an extremely simple and low-cost IoT in a cellular network, and initiated the Narrow Band Internet of Things (NB-IoT) theme at the 69th Radio Access Network (RAN) meeting.

[0009] In a wireless communication system, a terminal device has two modes. One is the connect mode, indicating that the end device has established a connection with the network device and can communicate directly with the network device. The other is idle or also referred to as idle mode, indicating that the terminal device cannot communicate directly with the network device. The idle tag periodically wakes up to monitor the paging message to check if there is a paging indication for the tag. The position at which a terminal wakes up is called a paging occasion (PO). The terminal monitors a Narrow Band Physical Downlink Control Channel (NPDCCH) at the PO. However, in a real application, the probability that the network device will page the terminal device and the probability that the system message will change is usually very low, and most POs may not be paged. In other words, the network device does not send the corresponding NPDCCH to the PO, but the terminal device still needs to monitor the NPDCCH in each PO. This is because the end device only knows if the network device is sending the NPDCCH after blind discovery is completed, which is actually a power consumption expense.

[0010] In order to solve the above problem, a wake-up signal (WUS) is introduced in R15 NB-IoT to indicate whether the tag at the PO needs to wake up to receive and detect a subsequent NPDCCH. In particular, the terminal detects the wake-up signal before the PO. If the WUS signal is detected, the terminal detects the subsequent NPDCCH. If the WUS signal is not detected, the terminal does not detect the subsequent NPDCCH.

[0011] However, the standard does not define the position at which the WUS signal appears. In this case, the terminal can only know by repeatedly performing blind discovery where the network device sends the WUS signal, or even cannot determine whether the network device sends the WUS signal. This significantly increases the power consumption of the terminal device. Therefore, how to reduce the power consumption of the target device caused by blind detection is an actual problem that needs to be solved.

The essence of the invention

[0012] This application proposes a wake-up signal detection method and a tag so that the tag can determine a position to detect the wake-up signal, thereby reducing power consumption of the tag.

[0013] According to a first aspect, a method for detecting a wakeup signal is provided. The method includes the following: The terminal device sends the first information to the network device, where the first information is used to indicate the reported interval; the terminal device receives the second information sent by the network device; the tag determines the configuration state of the first slot and the configuration state of the second slot based on the second information; the tag determines the target slot based on the reported slot, the state of the first slot, and the configuration state of the second slot; and the terminal detects the wakeup signal at a detection position before the start position of the first paging event (PO) in the paging time window (PTW), where the detection position is determined based on the target interval and the maximum duration of the wakeup signal.

[0014] In the above technical solution, the terminal device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, and further determines the position for detecting the wake-up signal, considering the maximum duration of the wake-up signal, so that blind detection can be prevented. wake-up signal terminal device, thereby reducing the power consumption of the terminal device.

[0015] In a possible implementation, the reported interval is 40 ms, 240 ms, 1 or 2 s.

[0016] In an exemplary implementation, the configuration state of the first interval includes the following: The first interval is set to 40 ms, the first interval is set to 80 ms, the first interval is set to 160 ms, and the first interval is set to 240 ms. The configuration state of the second interval includes: The second interval is not configured, the second interval is set to 1 s, and the second interval is set to 2 s.

[0017] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, it is determined that the target interval is 40 ms.

[0018] According to the above-mentioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0019] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0020] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, it is determined that the target interval is 80 ms.

[0021] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0022] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0023] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, it is determined that the target interval is 160 ms.

[0024] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0025] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0026] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[0027] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0028] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0029] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, it is determined that the target interval is 40 ms.

[0030] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0031] In addition, in the above technical solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0032] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, it is determined that the target interval is 80 ms.

[0033] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0034] In addition, in the above technical solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0035] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, it is determined that the target interval is 160 ms.

[0036] According to the above-mentioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0037] In addition, in the above technical solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0038] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[0039] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0040] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[0041] In an exemplary implementation, what the terminal determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 40 ms, 80 ms , 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the third interval, where the third interval is 40 ms, 80 ms, 160 ms, or 240 ms.

[0042] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0043] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure the eDRX long interval, the target interval is a DRX interval. Thus, the network device does not need to further configure the wake-up interval in these cases, thereby reducing the overhead of the network device.

[0044] In an exemplary implementation, the third slot is configured by the network device for the tag.

[0045] In an exemplary implementation, what the tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 40 ms, 80 ms , 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the fourth interval, where the fourth interval is 40 ms, 80 ms, 160 ms, or 240 ms.

[0046] According to the above-mentioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0047] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure the eDRX long interval, the target interval is a DRX interval. Thus, the network device does not need to further configure the wake-up interval in these cases, thereby reducing the overhead of the network device.

[0048] In an exemplary implementation, the fourth slot is configured by the network device for the tag.

[0049] In an exemplary implementation, that the tag determines the target interval based on the reported interval, the first interval configuration state, and the second interval configuration state includes the following: When the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms or 160 ms, the target interval is determined to be the fifth interval, where the fifth interval is 40 ms, 80 ms, 160 ms. , or 240 ms.

[0050] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[0051] In addition, in the above solution, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[0052] In an exemplary implementation, the fifth slot is configured by the network device for the tag.

[0053] According to a second aspect, a method for sending a wake-up signal is provided. The method includes the following: the network device receives the first information sent by the terminal device, where the first information is used to indicate the reported interval; the network device sends the second information to the terminal device, where the second information is used to indicate the configuration state of the first slot and the configuration state of the second slot; the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval; and the network device sends a wake-up signal at a discovery position before the start position of the first paging event in the paging time window (PTW), where the discovery position is determined based on the target interval and the maximum duration of the wake-up signal.

[0054] In an exemplary implementation, the configuration state of the first interval includes the following: The first interval is set to 40 ms, the first interval is set to 80 ms, the first interval is set to 160 ms, and the first interval is set to 240 ms. The configuration state of the second interval includes: The second interval is not configured, the second interval is set to 1 s, and the second interval is set to 2 s.

[0055] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, it is determined that the target interval is 40 ms.

[0056] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, it is determined that the target interval is 80 ms.

[0057] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, it is determined that the target interval is 160 ms.

[0058] In an exemplary implementation, what the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[0059] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, it is determined that the target interval is 40 ms.

[0060] In an exemplary implementation, what the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, it is determined that the target interval is 80 ms.

[0061] In an exemplary implementation, what the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, it is determined that the target interval is 160 ms.

[0062] In an exemplary implementation, what the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[0063] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 1 s, the first interval is set to 40 ms, 80 ms , 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the third interval, where the third interval is 40 ms, 80 ms, 160 ms, or 240 ms.

[0064] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 2 s, the first interval is set to 40 ms, 80 ms , 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the fourth interval, where the fourth interval is 40 ms, 80 ms, 160 ms, or 240 ms.

[0065] In an exemplary implementation, that the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval includes the following: When the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms or 160 ms, the target interval is determined to be the fifth interval, where the fifth interval is 40 ms, 80 ms, 160 ms, or 240 ms.

[0066] According to a third aspect, a terminal device is provided, including a module configured to perform a method according to any of the first aspect or implementations of the first aspect.

[0067] According to a fourth aspect, a network device is provided, including a module configured to perform the method of any of the second aspect or implementations of the second aspect.

[0068] According to a fifth aspect, a terminal device is provided. The terminal device includes a processor, a memory, and an instruction that is stored in the memory and can be executed in the processor. When the instruction is executed, the terminal is caused to execute a method according to any of the first aspect or implementations of the first aspect.

[0069] According to a sixth aspect, a network device is provided. The network device includes a processor, a memory, and an instruction that is stored in the memory and can be executed on the processor. When the instruction is executed, the network device is caused to execute a method according to any of the second aspect or implementations of the second aspect.

[0070] According to a seventh aspect, there is provided a chip configured to perform the method of any of the first aspect or possible implementations of the first aspect.

[0071] According to an eighth aspect, there is provided a chip configured to perform the method of any of the second aspect or possible implementations of the second aspect.

[0072] According to a ninth aspect, a computer-readable storage medium is provided, including an instruction. When the computer-readable storage medium operates in the communication device, the communication device is provided to perform the method according to any of the first aspect or possible implementations of the first aspect.

[0073] According to a tenth aspect, a computer-readable storage medium is provided, including an instruction. When the computer-readable storage medium operates in the communication device, the communication device is provided to perform the method according to any of the second aspect or possible implementations of the second aspect.

[0074] According to an eleventh aspect, a computer program product including an instruction is provided. When the computer program product is running on the communication device, the communication device is provided to perform the method of any of the first aspect or possible implementations of the first aspect.

[0075] According to a twelfth aspect, a computer program product including an instruction is provided. When the computer program product is running on the communication device, the communication device is provided to perform the method of any of the second aspect or possible implementations of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

[0076] FIG. 1 is a schematic diagram of a communication system architecture to which the present application may apply;

[0077] FIG. 2 is a schematic diagram of paging from a terminal point of view;

[0078] FIG. 3 is a schematic diagram of a paging indication signal from the point of view of a network device;

[0079] FIG. 4 is a schematic block diagram of a wake-up signal detection method according to an embodiment of the present application;

[0080] FIG. 5 is a schematic diagram of an eDRX in standby mode according to an embodiment of the present application;

[0081] FIG. 6 is a schematic diagram of a relationship between a DRX interval, a short eDRX interval, and a long eDRX interval according to an embodiment of the present application;

[0082] FIG. 7 is a schematic block diagram of a method for sending a wake-up signal according to an embodiment of the present application;

[0083] FIG. 8 is a schematic diagram of a paging indication signal when the target slot is a DRX slot;

[0084] FIG. 9 is a schematic block diagram of a terminal device according to an embodiment of this application;

[0085] FIG. 10 is a schematic block diagram of a network device according to an embodiment of this application;

[0086] FIG. 11 is a schematic block diagram of a terminal device according to another embodiment of the present application; and

[0087] FIG. 12 is a schematic block diagram of a network device according to another embodiment of the present application.

Description of Embodiments

[0088] Technical solutions according to this application are described below with reference to the accompanying drawings.

[0089] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as the global system for mobile communications (Global System for Mobile Communications, GSM), code division multiple access (CDMA) system, broadband system Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Frequency Division Duplex System Duplex, FDD LTE, Time Division Duplex (TDD) LTE, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access, WiMAX ), future 5th generation system (5t h Generation, 5G), a new radio communication system (New Radio, NR), a new network system, and the like.

[0090] The terminal device in the embodiments of the present application may be a user equipment, an access terminal, a subscriber device, a subscriber station, a mobile station, a mobile console, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or user device. The terminal device may alternatively be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (PDA), a handheld a device having a wireless communication function, a computing device, another data processing device connected to a wireless modem, a device installed in a vehicle, a wearable device, a terminal device in the future 5G network, a terminal device in the future Public Enhanced Land Mobile Network (Public Land Mobile Network, PLMN), etc. In embodiments of the present application, this is not limited.

[0091] The network device in embodiments of the present application may be a device configured to communicate with a terminal device. The type of network device is not specifically limited in this application. For example, the network device may be a Base Transceiver Station (BTS) in a Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA) system, or may be Node B (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or may be an evolved NodeB (evolved NodeB, eNB, or eNodeB) in an LTE system, or may be a radio controller in a cloud network radio access (Cloud Radio Access Network, CRAN). Alternatively, the network device may be a repeater, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, a network device in a future advanced PLMN, or the like. In embodiments of the present application, this is not limited.

[0092] In embodiments of the present application, a terminal or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and memory (also referred to as main memory). The operating system may be any one or more computer operating systems that implement service processing using a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as browser, address book, word processing software, and instant communication software. In addition, the specific structure of the execution body of the method proposed in the embodiments of the present application is not specifically limited in the embodiments of the present application, as long as the program in which the code of the method provided by the embodiments of the present application is recorded can be launched to communicate according to the method provided embodiments of the present application. For example, the execution body of the method proposed in the embodiments of the present application may be a terminal device or a network device, or a functional module that can call and execute a program and that resides in a terminal device or network device.

[0093] In addition, each aspect or feature of the present application may be implemented as a method, apparatus, or product using standard programming and/or development techniques. The term "product" as used in this application encompasses a computer program that can be accessed from any machine-readable device, medium or medium. For example, a computer-readable medium may include, but is not limited to, a magnetic storage component (such as a hard disk drive, floppy disk, or magnetic tape), an optical disc (such as a compact disc, CD), or a digital versatile disc (digital versatile disc (DVD)), a smart card, and a flash memory component (eg, Erasable Programmable Read-Only Memory (EPROM), card, module, or dongle storage). Additionally, the various storage media described in this specification may indicate one or more devices and/or other computer-readable media that are adapted to store information. The term "computer-readable medium" may include, without limitation, a wireless channel and various other media that may store, include, and/or carry instructions and/or data.

[0094] The LTE system is used as an example for description below.

[0095] FIG. 1 is a schematic diagram of a communication system architecture to which the present application may apply. As shown in FIG. 1, the network device and terminal device 1 - terminal device 6 form a communication system. In the communication system, terminal device 1 - terminal device 6 may send uplink data to the network device, the network device must receive uplink data sent by terminal device 1 - terminal device 6, and the network device may also send downlink data to the terminal device 1 - terminal device 6. Moreover, terminal device 4 - terminal device 6 can also form a communication system. In this communication system, terminal 4 and terminal 6 may send uplink data to terminal 5, and terminal 5 may also send downlink data to terminal 4 and terminal 6.

[0096] In a wireless communication system, a terminal device has two modes. One is the connect mode, indicating that the end device has established a connection with the network device and can communicate directly with the network device. The other is idle or idle mode, indicating that the terminal device cannot communicate directly with the network device. In order to ensure that the network device can efficiently locate the idle mode terminal, the network device typically paging, in other words, periodically sends a paging signal to the terminal to indicate whether the terminal should switch from idle to connected mode and communicate. with a network device. When there is no service to send or receive, the terminal device can go into sleep mode to reduce power consumption. For an idle terminal device, when the network device needs to send a service to the terminal device, or the terminal device needs to report some services, the network device can notify the terminal device using a paging mechanism. After receiving the paging notification, the terminal may wake up and enter the connected mode to send or receive service data.

[0097] FIG. 2 is a schematic diagram of paging from a terminal point of view. The idle tag periodically wakes up to monitor the paging message to check if there is a paging indication for the tag. As shown in FIG. 2, a cycle in which the terminal periodically wakes up is called a Discontinuous Reception (DRX) cycle, and the DRX cycle may be indicated by a system message. The position at which the terminal wakes up is called a PO (paging occasion, PO) paging event. The terminal monitors the NPDCCH in the PO. The idle mode terminal is idle most of the time in the DRX cycle and wakes up only at the appropriate PO to monitor the NPDCCH. A terminal shall detect only one PO in a DRX cycle.

[0098] In the existing system, the terminal always first detects the target search space to determine if there is an appropriate downlink scheduling (eg, NPDCCH scheduling). If an NPDCCH is detected in the target search space, the terminal receives a Narrow Band Physical Downlink Shared Channel (NPDSCH) based on the indication information carried in the detected NPDCCH. If no NPDCCH is found in the target search space, the terminal does not receive the NPDSCH.

[0099] The terminal typically detects the NPDCCH in a blind discovery manner in the target search space of the NPDCCH. The target NPDCCH search space is a set of potentially suitable positions (candidates) in which the target NPDCCH may appear. The PO indicates the starting position from which the terminal monitors the NPDCCH in order to determine the starting position of the target search space, and blind discovery is performed based on this position. The terminal sequentially blindly discovers various potentially suitable positions in the search space in which the PO position is used as the starting position until the discovery is successful. If discovery fails at all of the potentially suitable positions, the network device is considered not to send the NPDCCH. For the NB-IoT system, the NPDCCH reception time may be relatively long, and the blind detection algorithm is complex. Therefore, the power consumption is very large when the terminal monitors the NPDCCH in the PO.

[00100] As a result, R15 NB-IoT introduced a wake-up signal (WUS) to indicate whether the tag should wake up at the PO to receive and detect a subsequent NPDCCH. In particular, from the point of view of the tag, the tag detects the wake-up signal before the PO. If the WUS signal is detected, the terminal detects the subsequent NPDCCH; if the WUS signal is not detected, the terminal does not detect the subsequent NPDCCH. Fig. 3 is a schematic diagram of a paging indication signal from the point of view of a network device. As shown in FIG. 3, from the point of view of the network device, when there is an NPDCCH in the PO, for example, a terminal device needs to be paged or a system message changes, the network device sends a wake-up signal (WUS) before the PO; when there is no NPDCCH in the PO, the network device does not send any signal, which is Discontinuous Transmission (DTX).

[00101] However, the standard does not specify the position at which the WUS signal appears. In this case, the tag can only know by repeatedly performing blind discovery where the network device sends the WUS signal, or even cannot determine whether the network device sends the WUS signal. This significantly increases the power consumption of the terminal device.

[00102] The present application proposes a wake-up signal detection method and a tag so that the tag can determine a position to detect the wake-up signal, thereby reducing power consumption of the tag.

[00103] FIG. 4 is a schematic block diagram of a wake-up signal detection method according to an embodiment of the present application. The method shown in Fig. 4 may be executed by a terminal and includes at least a portion of the following content.

[00104] 401. The terminal device sends the first information to the network device, where the first information is used to indicate the reported interval.

[00105] 402. The terminal device receives the second information sent by the network device.

[00106] 403. The tag determines the configuration state of the first slot and the configuration state of the second slot based on the second information.

[00107] 404. The tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval.

[00108] 405. The terminal detects a wakeup signal at a detection position before the start position of the first paging event (PO) in the paging time window (PTW), where the detection position is determined based on the target interval and the maximum wakeup signal duration.

[00109] In the above solution, the tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, and determines the position for wake-up signal detection based on the configured maximum wake-up signal duration, so that blind detection by the terminal can be prevented. wake-up signal device, thereby reducing the power consumption of the target device.

[00110] The following separately details steps 401 to 405.

[00111] 401. The terminal device sends the first information to the network device, where the first information is used to indicate the reported interval.

[00112] During WUS discovery, the terminal may only perform sequence correlation. Therefore, most circuits can be disabled to reduce power consumption.

[00113] Only after detecting the WUS does the tag need to turn on other circuitry, load memory, etc. to demodulate the NPDCCH at the PO. This takes time (warm-up time).

[00114] Optionally, the reported interval is the period of time needed to turn on another circuit, load memory, and the like.

[00115] For example, if the reported interval is 40 ms, this means that after detecting the WUS, the terminal device needs at least 40 ms to make preparations for “turning on another circuit, loading memory, etc.” to demodulate the NPDCCH in the PO .

[00116] Therefore, the reported interval may reflect the functionality of the tag. Generally, a longer reported interval indicates poorer target device functionality (slower memory loading).

[00117] Optionally, the terminal is a terminal with an extended discontinuous reception (eDRX) configuration.

[00118] Optionally, an eDRX-configured terminal may be in eDRX mode.

[00119] First, for a tag without an eDRX configuration, the tag is in light sleep at times other than PO, and most circuitry can be disabled to reduce power consumption. The terminal wakes up, on a loop basis, to detect the PO. The cycle is referred to as the DRX cycle. For example, the DRX cycle value could be {1.28s, ..., 10.24s}.

[00120] Therefore, a terminal without eDRX configuration must wake up at least once every 10.24 seconds (because the maximum DRX cycle is 10.24 seconds).

[00121] Compared to a terminal without an eDRX configuration, an eDRX configured terminal has a paging time window (PTW) in the time domain as shown in FIG. 5. An eDRX-configured end device only wakes up inside the PTW, and the behavior inside the PTW is the same as the non-eDRX-configured end device. The maximum PTW cycle is 2.9 hours, which means that an eDRX-configured endpoint can wake up once every 2.9 hours.

[00122] The terminal is in deep sleep mode outside of PTW. Compared with light sleep mode, more circuits can be turned off in deep sleep mode. Therefore, eDRX mode is a mode that saves more power than DRX.

[00123] Similarly, in eDRX, after WUS detection, a longer warm-up time (corresponding to a longer WUS interval) is required.

[00124] It should be understood that the wakeup signal before the first paging event in the PTW may be in the PTW or may be outside the PTW.

[00125] For a terminal device with an eDRX configuration, the terminal device specifically reports the wakeup interval (WUS interval (WUS gap) or WUS gap (WUS offset)). As shown in FIG. 3, the wake-up signal interval is the interval between the start position PO and the end position of the configured maximum wake-up signal duration (configured maximum WUS duration).

[00126] Optionally, the reported interval is a wake-up signal interval.

[00127] Optionally, the range of wakeup interval values may be {40ms, 240ms, 1s, 2s}.

[00128] For example, when an eDRX configured tag reports 240 ms, this means that the tag thinks the tag needs 240 ms to perform a warm-up operation.

[00129] It should be noted here that if a terminal reports 1s and 2s, there is a high probability that the terminal has a special WUS discovery scheme. The tag can turn off the original master circuit and only turn on the special WUS discovery circuit for WUS discovery, and the tag turns on the master circuit only after WUS discovery, achieving ultra-low power consumption.

[00130] Therefore, the functionality of a tag that reports 1 s or 2 s is not necessarily weaker than the functionality of a tag that reports 40 ms or 240 ms, and it is very likely that a tag that reports 1 s or 2 c, has an additional dedicated WUS discovery scheme.

[00131] In this case, due to the fact that the main circuit is completely turned off, the terminal device requires a longer warm-up time. Therefore, 1s and 2s are defined in the standard.

[00132] It should be understood that the fact that the terminal device tells the network device the wake-up interval means that the terminal device tells the network device the minimum period of time required for the terminal device to complete preparations.

[00133] Optionally, the maximum wakeup duration may be signaled by the network device to the tag in advance.

[00134] In addition, for a tag without an eDRX configuration, the tag does not report the wake-up interval.

[00135] 402. The terminal device receives the second information sent by the network device.

[00136] Optionally, the network device may send the second information in a broadcast manner.

[00137] For example, a network device sends broadcast information in a cell to a terminal device in the cell, and the second information may be this broadcast information.

[00138] 403. The tag determines the configuration state of the first slot and the configuration state of the second slot based on the second information.

[00139] Optionally, a network device may configure the same first interval or second interval for multiple terminals in a cell based on the plurality of reported intervals reported by the plurality of terminals.

[00140] Alternatively, a network device may configure different first slots or second slots for multiple terminals in a cell based on the multiple reported slots reported by the multiple terminals.

[00141] Optionally, the first interval may be equal to the reported interval.

[00142] Alternatively, the first interval may not match the reported interval.

[00143] In other words, the first interval configured by the network device for the tag is not necessarily equal to the reported interval reported by the tag. The first interval depends on the implementation of the network device.

[00144] For example, there may be hundreds or thousands of terminals in one cell, and each terminal reports a different reported interval. Therefore, the network device cannot meet the requirements of all end devices.

[00145] Optionally, the terminal is an eDRX configured terminal.

[00146] The network device specifically configures the eDRX short interval for the terminal device with the eDRX configuration.

[00147] Optionally, the first interval may be a short eDRX interval.

[00148] Optionally, the range of eDRX short interval values may be {40 ms, 80 ms, 160 ms, 240 ms}.

[00149] In other words, the configuration state of the first interval may include: The first interval is set to 40 ms, the first interval is set to 80 ms, the first interval is set to 160 ms, and the first interval is set to 240 ms.

[00150] In addition, for a tag without DRX configuration, the network device specifically configures a DRX interval (DRX gap or DRX offset) for the tag.

[00151] Optionally, the range of DRX interval values may be {40 ms, 80 ms, 160 ms, 240 ms}.

[00152] Optionally, the short eDRX interval is greater than or equal to the DRX interval.

[00153] For example, when the DRX interval is 40 ms, the range of short eDRX interval may be {80 ms, 160 ms, 240 ms}.

[00154] FIG. 6 shows the relationship between the DRX interval, the short eDRX interval, and the long eDRX interval. Optionally, the second interval may be a long eDRX interval.

[00155] Optionally, the configuration state of the second interval may include the following: The second interval is not configured, the second interval is set to 1 s, and the second interval is set to 2 s.

[00156] In other words, a network device may configure a long eDRX interval for an eDRX-configured terminal.

[00157] 404. The tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval.

[00158] The target interval is the wake-up signal interval that is actually used by the tag to detect the wake-up signal and that is actually used by the network device to send the wake-up signal.

[00159] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined to be 40 ms.

[00160] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00161] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 20ms, 80ms, etc.

[00162] Optionally, when the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined to be 80 ms.

[00163] Optionally, when the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00164] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 40ms, 160ms, etc.

[00165] Optionally, when the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined to be 160 ms.

[00166] Optionally, when the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00167] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 320ms, etc.

[00168] Optionally, when the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined to be 240 ms.

[00169] Optionally, when the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00170] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 120ms, 480ms, etc.

[00171] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00172] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[00173] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined to be 40 ms.

[00174] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00175] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 20ms, 80ms, etc.

[00176] Optionally, when the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined to be 80 ms.

[00177] Optionally, when the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00178] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 40ms, 160ms, etc.

[00179] Optionally, when the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined to be 160 ms.

[00180] Optionally, when the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00181] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 320ms, etc.

[00182] Optionally, when the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined to be 240 ms.

[00183] Optionally, when the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00184] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 120ms, 480ms, etc.

[00185] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00186] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[00187] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the third interval, where the third interval is 40 ms, 80 ms, 160 ms or 240 ms.

[00188] For example, when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 40 ms; when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 80 ms; when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 160 ms; or when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[00189] Optionally, the third slot is configured by the network device for the tag.

[00190] Optionally, the third interval is a DRX interval.

[00191] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00192] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure the eDRX long interval, it is determined that the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00193] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the fourth interval, where the fourth interval is 40 ms, 80 ms, 160 ms or 240 ms.

[00194] For example, when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 40 ms; when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 80 ms; when the reported interval is 2s, the first interval is set to 40ms, 80ms, 160ms, or 240ms, and the second interval is not configured, it is determined that the target interval is 160ms; or when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[00195] Optionally, the fourth interval is configured by the network device for the terminal device.

[00196] Optionally, the fourth interval is a DRX interval.

[00197] According to the above technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00198] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure the eDRX long interval, it is determined that the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00199] Optionally, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, the target interval is determined to be the fifth interval and the fifth interval is 40 ms, 80 ms, 160 ms. ms, or 240 ms.

[00200] For example, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 40 ms; when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 80 ms; when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 160 ms; or when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 240 ms.

[00201] It should be understood that in this case, the network device may configure the second slot for the tag or may not configure the second slot for the tag.

[00202] Optionally, the fifth interval is configured by the network device for the terminal device.

[00203] Optionally, the fifth interval is a DRX interval.

[00204] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00205] In addition, in the above solution, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00206] It should be understood that the above technical solutions can be used alone or can be used in combination as appropriate. This application is not limited.

[00207] 405. The terminal detects a wakeup signal at a discovery position before the start position of the first paging event (PO) in the paging time window (PTW), where the discovery position is determined based on the target interval and the maximum wakeup signal duration.

[00208] Optionally, the discovery position is the position that is before the start position of the first paging event (PO) in the paging time window (PTW) and that is away from the PO by the sum of the target interval and the maximum wakeup duration.

[00209] For example, if the start position of the PO is T, the target interval is 40 ms, and the maximum duration of the WUS is 128 ms, then the detection position is T - 40-128.

[00210] Optionally, the detection position is determined based on the target interval, the maximum wakeup signal duration, and delay information.

[00211] For example, in NB-IoT, some subframes are invalid subframes or subframes used to transmit a broadcast signal or a synchronization signal. When these subframes are detected, the WUS uses a delay approach so that the subframes cannot be used for WUS transmission and are ignored, in other words, the subframes are skipped. If the PO start position is T, the target interval is 40 ms, the maximum WUS duration is 128 ms, and there are 10 preceding subframes in 128 ms, then the detection position is T - 40-128-10.

[00212] In the above technical solution, the tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, and determines the position for detecting the wake-up signal considering the maximum duration of the wake-up signal, so that blind detection by the terminal can be prevented. wake-up signal device, thereby reducing the power consumption of the target device.

[00213] The present application proposes a method for sending a wake-up signal so that a tag can determine a position to detect the wake-up signal, thereby reducing power consumption of the tag.

[00214] FIG. 7 is a schematic block diagram of a method for sending a wake-up signal according to an embodiment of the present application. The method shown in Fig. 7 may be executed by a network device and includes at least a portion of the following content.

[00215] 701. The network device receives the first information sent by the terminal device, where the first information is used to indicate the reported interval.

[00216] 702. The network device sends the second information to the terminal device, where the second information is used to indicate the configuration state of the first slot and the configuration state of the second slot.

[00217] 703. The network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval.

[00218] 704. The network device sends a wakeup signal at a discovery position before the start position of the first paging event in the paging time window (PTW), where the discovery position is determined based on the target interval and the maximum wakeup signal duration.

[00219] In the above technical solution, the network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, and also determines the position for detecting the wake-up signal, considering the maximum duration of the wake-up signal, so that blind detection by the endpoint can be prevented. wake-up signal device, thereby reducing the power consumption of the terminal device.

[00220] The following describes steps 701 through 704 in detail.

[00221] 701. The network device receives the first information sent by the terminal device, where the first information is used to indicate the reported interval.

[00222] Optionally, the reported interval is the period of time needed to turn on another circuit, load memory, or the like.

[00223] For example, if the reported interval is 40 ms, this means that after detecting the WUS, the terminal needs at least 40 ms to make preparations for "turning on another circuit, loading memory, etc." in order to demodulate NPDCCH in PO.

[00224] Optionally, the reported interval is a wake-up signal interval.

[00225] Optionally, the range of wake-up signal interval values may be {40 ms, 240 ms, 1 s, 2 s}.

[00226] For example, when a terminal with an eDRX configuration reports 240 ms, this means that the terminal considers that the terminal requires 240 ms to perform a warm-up operation.

[00227] It should be understood that the fact that the tag tells the network device the wake-up interval means that the tag tells the network device the minimum amount of time the tag needs to perform preparations.

[00228] 702. The network device sends the second information to the terminal device, where the second information is used to indicate the configuration state of the first slot and the configuration state of the second slot.

[00229] Optionally, the network device may send the second information in a broadcast manner.

[00230] For example, a network device sends broadcast information in a cell to a terminal device in the cell, and the second information may be broadcast information.

[00231] Optionally, a network device may configure the same first slot or the same second slot for multiple terminals in a cell based on the multiple reported slots reported by the multiple terminals.

[00232] Alternatively, a network device may configure different first slots or the same second slot for multiple terminals in a cell based on the multiple reported slots reported by the multiple terminals.

[00233] Optionally, the first interval may be equal to the declared interval.

[00234] Alternatively, the first interval may not be equal to the reported interval.

[00235] In other words, the first interval configured by the network device for the tag is not necessarily equal to the reported interval reported by the tag. The first interval depends on the implementation of the network device.

[00236] For example, there may be hundreds or thousands of tags in a single cell, and each tag reports a different reported interval. Therefore, the network device cannot meet the requirements of all end devices.

[00237] Optionally, the terminal is an eDRX configured terminal.

[00238] The network device specifically configures the eDRX short interval for the terminal device with the eDRX configuration.

[00239] Optionally, the first interval may be a short eDRX interval.

[00240] Optionally, the range of eDRX short interval values may be {40 ms, 80 ms, 160 ms, 240 ms}.

[00241] In other words, the configuration state of the first interval may include: The first interval is set to 40 ms, the first interval is set to 80 ms, the first interval is set to 160 ms, and the first interval is set to 240 ms.

[00242] In addition, for a tag without DRX configuration, the network device specifically configures a DRX interval (DRX gap or DRX offset) for the tag.

[00243] Optionally, the range of DRX interval values may be {40 ms, 80 ms, 160 ms, 240 ms}.

[00244] Optionally, the short eDRX interval is greater than or equal to the DRX interval.

[00245] For example, when the DRX interval is 40 ms, the range of short eDRX interval may be {80 ms, 160 ms, 240 ms}.

[00246] FIG. 6 shows the relationship between the DRX interval, the short eDRX interval, and the long eDRX interval.

[00247] Optionally, the second interval may be a long eDRX interval.

[00248] Optionally, the configuration state of the second interval may include the following: The second interval is not configured, the second interval is set to 1 s, and the second interval is set to 2 s.

[00249] In other words, a network device may configure a long eDRX interval for an eDRX-configured terminal.

[00250] 703. The network device determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval.

[00251] The target interval is the wake-up signal interval that is actually used by the tag to detect the wake-up signal and that is actually used by the network device to send the wake-up signal.

[00252] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined to be 40 ms.

[00253] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00254] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 20ms, 80ms, etc.

[00255] Optionally, when the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined to be 80 ms.

[00256] Optionally, when the reported interval is 1 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00257] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 40ms, 160ms, etc.

[00258] Optionally, when the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined to be 160 ms.

[00259] Optionally, when the reported interval is 1 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00260] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 320ms, etc.

[00261] Optionally, when the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined to be 240 ms.

[00262] Optionally, when the reported interval is 1 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00263] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 480ms, etc.

[00264] According to the above-mentioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00265] In addition, in the above technical solution, when the reported interval is 1 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[00266] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined to be 40 ms.

[00267] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00268] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 20ms, 80ms, etc.

[00269] Optionally, when the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined to be 80 ms.

[00270] Optionally, when the reported interval is 2 s, the first interval is set to 80 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00271] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 40ms, 160ms, etc.

[00272] Optionally, when the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined to be 160 ms.

[00273] Optionally, when the reported interval is 2 s, the first interval is set to 160 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00274] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 320ms, etc.

[00275] Optionally, when the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined to be 240 ms.

[00276] Optionally, when the reported interval is 2 s, the first interval is set to 240 ms, and the second interval is not configured, the target interval is determined based on the first interval (namely, short eDRX interval).

[00277] For example, the target interval may be 1/2, 2, or the like. short eDRX interval, i.e. 80ms, 480ms, etc.

[00278] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00279] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared to the case where the target interval is a DRX interval, the terminal can detect the wake-up signal in the eDRX mode. Thus, the time period during which the terminal is in the eDRX mode can be extended as much as possible, thereby further reducing the power consumption of the terminal.

[00280] Optionally, when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the third interval, where the third interval is 40 ms, 80 ms, 160 ms or 240 ms.

[00281] For example, when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 40 ms; when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 80 ms; when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 160 ms; or when the reported interval is 1 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[00282] Optionally, the third interval is configured by the network device for the terminal device.

[00283] Optionally, the third interval is a DRX interval.

[00284] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00285] In addition, in the above solution, when the reported interval is 1 s and the network device does not configure the eDRX long interval, it is determined that the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00286] Optionally, when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is the fourth interval, where the fourth interval is 40 ms, 80 ms, 160 ms or 240 ms.

[00287] For example, when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 40 ms; when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 80 ms; when the reported interval is 2s, the first interval is set to 40ms, 80ms, 160ms, or 240ms, and the second interval is not configured, it is determined that the target interval is 160ms; or when the reported interval is 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, it is determined that the target interval is 240 ms.

[00288] Optionally, the fourth interval is configured by the network device for the terminal device.

[00289] Optionally, the fourth interval is a DRX interval.

[00290] According to the above-mentioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00291] In addition, in the above solution, when the reported interval is 2 s and the network device does not configure the eDRX long interval, it is determined that the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00292] Optionally, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, the target interval is determined to be the fifth interval and the fifth interval is 40 ms, 80 ms, 160 ms. ms, or 240 ms.

[00293] For example, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 40 ms; when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 80 ms; when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 160 ms; or when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, it is determined that the target interval is 240 ms.

[00294] It should be understood that in this case, the network device may configure the second slot for the tag or may not configure the second slot for the tag.

[00295] Optionally, the fifth slot is configured by the network device for the tag.

[00296] Optionally, the fifth interval is a DRX interval.

[00297] According to the aforementioned technical solution, the terminal device can determine the position for detecting the wake-up signal, so that the terminal device can be prevented from blindly detecting the wake-up signal, thereby reducing the power consumption of the terminal device.

[00298] In addition, in the above solution, when the reported interval is 240 ms and the first interval is set to 40 ms, 80 ms, or 160 ms, the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00299] It should be understood that the above technical solutions can be used individually or can be used in combination as appropriate. This application is not limited.

[00300] 704. The network device sends a wakeup signal at a discovery position before the start position of the first paging event (PO) in the paging time window (PTW), where the discovery position is determined based on the target interval and the maximum wakeup signal duration.

[00301] Optionally, the discovery position is the position that is before the start position of the first paging event (PO) in the paging time window (PTW) and that is away from the PO by the sum of the target interval and the maximum wakeup duration.

[00302] For example, if the start position of the PO is T, the target interval is 40 ms, and the maximum duration of the WUS is 128 ms, then the detection position is T - 40-128.

[00303] Optionally, the detection position is determined based on the target interval, the maximum duration of the wake-up signal, and delay information.

[00304] For example, in NB-IoT, some subframes are invalid subframes or subframes used to transmit a broadcast or synchronization signal. When these subframes are detected, the WUS uses a delay approach so that the subframes cannot be used for WUS transmission and are not counted, in other words, the subframes are skipped. If the PO start position is T, the target interval is 40 ms, the maximum WUS duration is 128 ms, and there are 10 preceding subframes in 128 ms, then the detection position is T - 40-128-10.

[00305] In the above technical solution, the tag determines the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, and also determines the position for detecting the wake-up signal, taking into account the maximum duration of the wake-up signal, so that blind detection by the terminal can be prevented. wake-up signal device, thereby reducing the power consumption of the target device.

[00306] The following is a more detailed description of this embodiment of the present application with reference to specific examples.

[00307] Table 1 represents the correspondence between the reported interval, the first interval, the second interval, and the target interval in this embodiment of this application. From Table 1 it can be seen that for eDRX, the terminal device can report four values, the network device has 12 configurations, and there are 4×12=48 cases in total. Each case can be uniquely determined by using the reported interval (the value reported by the end device), the first interval, and the second interval (the value configured by the network device for eDRX, and the value configured by the network device for the end device).

[00308] For 12 network device configurations, 40 ms means that the network device sets one short eDRX interval to 40 ms for the terminal device, and the long eDRX interval is not configured. The second interval, in another similar form, where there is only one value corresponding to the value configured by the network device for eDRX, has a similar meaning. 40ms+1s means that the network device sets one short eDRX interval to 40ms and one long eDRX interval to 1s for the end device. A configuration in another similar form, where there are two different values corresponding to the value configured by the network device for eDRX, has a similar meaning.

[00309] For example, a discovery position is a position that is before the start position of the first paging event (PO) in the paging time window (PTW) and that is away from the PO by the sum of the target interval and the configured maximum wakeup duration.

[00310] It is assumed that the DRX interval configured by the network device in this case is 40 ms, and the maximum duration of the wake-up signal is 128 ms.

[00311] When the value reported by the terminal device is 40 ms and the value configured by the network device for eDRX is 240 ms, this means that the terminal device reports the WUS interval as 40 ms and the network device sets only the short eDRX interval to 240ms and does not configure long eDRX interval. In this case, the WUS interval corresponding to the tag is 240ms, in other words, the network device sends the WUS of the tag at 240ms+128ms, and the tag detects the WUS at 240ms+128ms.

[00312] When the value reported by the terminal device is 40 ms and the value configured by the network device for eDRX is 240 ms+1 s, this means that the terminal device reports the WUS interval as 40 ms and the network device sets the interval to short eDRX to 240ms and additionally sets the eDRX long interval to 1s. In this case, the WUS interval corresponding to the tag is 240ms, in other words, the network device sends the WUS of the tag at 240ms+128ms, and the tag detects the WUS at 240ms+128ms.

[00313] When the value reported by the terminal device is 1 s and the value configured by the network device for eDRX is 240 ms+1 s, this means that the terminal device reports the WUS interval as 1 s (indicating that the end device probably has a special WUS discovery scheme), and the network device sets the eDRX short interval to 240 ms and additionally sets the eDRX long interval to 1 s. In this case, the WUS interval corresponding to the terminal is 1s, in other words, the network device sends the WUS of the terminal at 1s+128ms and the terminal detects the WUS at 1s+128ms.

[00314] When the value reported by the terminal device is 1 s and the value configured by the network device for eDRX is 80 ms, this means that the terminal device reports the WUS interval as 1 s and the network device sets the eDRX short interval to 80 ms, and does not configure a long eDRX interval. In this case, the DRX interval corresponding to the terminal is 40ms, in other words, the network device sends the WUS of the terminal at DRX+128ms=40ms+128ms, and the terminal detects the WUS at DRX+128ms=40ms +128 ms as shown in FIG. eight.

[00315] The remaining cases in the table are similar.

Table 1 Correspondence of the declared interval, the first interval, the second interval and the target interval

Value configured for eDRX by network device 40ms 80ms 160ms 240 ms 40ms
+1s 80ms
+1s 160ms
+1s 240 ms
+1s 40ms
+ 2 s 80ms
+ 2 s 160ms
+ 2 s 240 ms
+2 s Value reported by end device 40ms 40ms 80ms 160ms 240 ms 40ms 80ms 160ms 240 ms 40ms 80ms 160ms 240 ms 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms 1 s [DRX Interval] [DRX Interval] [DRX Interval] [DRX Interval] 1 s 1 s 1 s 1 s 2 s 2 s 2 s 2 s 2 s [DRX Interval] [DRX Interval] [DRX Interval] [DRX Interval] 40ms 80ms 160ms 240 ms 2 s 2 s 2 s 2 s

[00316] In the above technical solution, the terminal device determines the target interval based on the reported interval, the first interval and the second interval, and determines the position for detecting the wake-up signal considering the maximum duration of the wake-up signal, so that blind detection of the wake-up signal by the terminal device can be prevented, thereby thereby reducing the power consumption of the terminal device.

[00317] In addition, in the above solution, when the reported interval is 240 ms and the first interval is 40 ms, 80 ms, or 160 ms, and when the reported interval is 1 s or 2 s, and the network device does not configure a long eDRX interval, it is determined that the target interval is a DRX interval. Thus, the network device does not need a wake-up interval, which is further configured in these cases, thereby reducing the overhead of the network device.

[00318] Table 2 represents another correspondence between the reported interval, the first interval, the second interval, and the target interval in this embodiment of the present application. It can be seen from Table 2 that for eDRX, the terminal can report four values, the network device has 12 configurations, and there are 4×12=48 cases in total. Each case can be uniquely identified using the reported interval (the value reported by the end device), the first interval, and the second interval (the value configured by the network device for eDRX, and the value configured by the network device for the end device).

[00319] For 12 network device configurations, 40 ms indicates that the network device sets one short eDRX interval to 40 ms for the tag, and the long eDRX interval is not configured. The second interval, in another similar form, where there is only one value corresponding to the value configured by the network device for eDRX, has a similar meaning. 40ms+1s indicates that the network device sets one short eDRX interval to 40ms and one long eDRX interval to 1s for the end device. A configuration in another similar form, where there are two different values corresponding to the value configured by the network device for eDRX, has a similar meaning.

[00320] Similarly, an example is used in which the discovery position is the position that is before the start position of the first paging event (PO) in the paging time window (PTW) and that is away from the PO by the sum of the target interval and the configured maximum duration wake-up signal.

[00321] It is assumed that the DRX interval configured by the network device in this case is 40 ms, and the maximum wakeup duration is 128 ms.

[00322] When the value reported by the tag is 40 ms and the value configured by the network device for eDRX is 240 ms, this indicates that the tag reports the WUS interval as 40 ms and the network device sets only the short eDRX interval to 240ms and does not configure long eDRX interval. In this case, the WUS interval corresponding to the tag is 240ms, in other words, the network device sends the WUS of the tag at 240ms+128ms, and the tag detects the WUS at 240ms+128ms.

[00323] When the value reported by the terminal device is 40 ms and the value configured by the network device for eDRX is 240 ms+1 s, this indicates that the terminal device reports the WUS interval as 40 ms and the network device sets the interval to short eDRX to 240ms and additionally sets the eDRX long interval to 1s. In this case, the WUS interval corresponding to the tag is 240ms, in other words, the network device sends the WUS of the tag at 240ms+128ms, and the tag detects the WUS at 240ms+128ms.

[00324] When the value reported by the terminal device is 1 s and the value configured by the network device for eDRX is 240 ms+1 s, this indicates that the terminal device reports the WUS interval as 1 s (indicating that the end device probably has a special WUS discovery scheme), and the network device sets the eDRX short interval to 240 ms and additionally sets the eDRX long interval to 1 s. In this case, the WUS interval corresponding to the tag is 1 s, in other words, the network device sends the WUS of the tag at 1 s+128 ms, and the tag detects the WUS at 1 s+128 ms.

[00325] When the value reported by the terminal device is 240 ms and the value configured by the network device for eDRX is 80 ms, this indicates that the terminal device reports the WUS interval as 240 ms and the network device sets the eDRX short interval to 80 ms and does not configure a long eDRX interval. In this case, the DRX interval corresponding to the terminal is 40ms, in other words, the network device sends the WUS of the terminal at DRX+128ms=40ms+128ms, and the terminal detects the WUS at DRX+128ms=40ms +128 ms.

[00326] When the value reported by the tag is 1 s and the value configured by the network device for eDRX is 80 ms, this indicates that the tag reports the WUS interval as 1 s and the network device sets the short eDRX interval to 80 ms and does not configure a long eDRX interval. In this case, the short eDRX interval corresponding to the terminal is 80ms, in other words, the network device sends the WUS of the terminal at the short interval eDRX+128ms=80ms+128ms, and the terminal detects the WUS at the short interval eDRX+128ms =80ms+128ms.

[00327] The remaining cases in Table 2 are similar.

Value configured for eDRX by network device 40ms 80ms 160ms 240 ms 40ms
+1s 80ms
+1s 160ms
+1s 240 ms
+1s 40ms
+ 2 s 80ms
+ 2 s 160ms
+ 2 s 240 ms
+ 2 s Value reported by end device 40ms 40ms 80ms 160ms 240 ms 40ms 80ms 160ms 240 ms 40ms 80ms 160ms 240 ms 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms [DRX Interval] [DRX Interval] [DRX Interval] 240 ms 1 s 40ms 80ms 160ms 240 ms 1 s 1 s 1 s 1 s 2 s 2 s 2 s 2 s 2 s 40ms 80ms 160ms 240 ms 40ms 80ms 160ms 240 ms 2 s 2 s 2 s 2 s

Table 2 Other correspondence between reported interval, first interval, second interval and target interval

[00328] In the above technical solution, the terminal device determines the target interval based on the reported interval, the first interval and the second interval, and also determines the position for detecting the wake-up signal, taking into account the maximum duration of the wake-up signal, so that blind detection of the wake-up signal by the terminal device can be prevented, thereby reducing the power consumption of the terminal device.

[00329] In addition, in the above solution, when the reported interval is 1 s or 2 s and the network device does not configure a long eDRX interval, the target interval is a short eDRX interval. Compared with the case in which the target interval is a DRX interval, the tag needs to switch from the eDRX mode to the DRX mode to detect the WUS, the power consumption of the tag increases. In particular, if the PO is not paging (the network device is not sending WUS), the end device can always be in eDRX mode. In other words, the behavior of the end device is as follows: being in eDRX mode → discovering WUS → not discovering WUS → still being in eDRX mode. However, when the target interval is a DRX interval, the terminal must switch from eDRX mode to DRX mode in order to discover the WUS. The length of stay in eDRX mode is shortened and the power consumption of the end device is increased. The behavior of the target device is changed to stay in eDRX mode → stay in DRX mode → discover WUS → not discover WUS → stay in DRX mode, the end device can detect the wake-up signal in eDRX mode, and the time the end device is in eDRX mode , can be extended as much as possible, thereby further reducing the power consumption of the terminal device.

[00330] The present application proposes a terminal device for implementing a wake-up signal detection method as described in any of the above embodiments.

[00331] FIG. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 9, terminal device 900 may include:

a sending unit 901, configured to send the first information to the network device, where the first information is used to indicate a reported interval;

a receiving unit 902, configured to receive second information sent by the network device;

a determination unit 903, configured to determine the configuration state of the first interval and the configuration state of the second interval based on the second information, wherein

the determining unit 903 is further configured to determine the target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval; and

a detection unit 904, configured to detect a wake-up signal at a detection position before the start position of the first paging event in the paging time window (PTW), where the detection position is determined based on the target interval and the maximum up-wake duration.

[00332] It can be understood that for specific implementations and beneficial effects of the blocks in terminal 900 in this embodiment of the present application, reference should be made to the respective descriptions in the method embodiments. Details are not given here again.

[00333] FIG. 10 is a schematic block diagram of a network device according to an embodiment of the present application. As shown in FIG. 10, network device 1000 may include:

a receiving unit 1001, configured to receive the first information sent by the terminal device, where the first information is used to indicate a reported interval;

a sending unit 1002, configured to send the second information to the terminal, where the second information is used to indicate the configuration state of the first slot and the configuration state of the second slot;

a determining unit 1003, configured to determine a target interval based on the reported interval, the configuration state of the first interval, and the configuration state of the second interval, where

the sender 1002 is further configured to send the wakeup signal at a detection position before the start position of the first paging event in the paging time window (PTW), where the detection position is determined based on the target interval and the maximum duration of the wakeup signal.

[00334] It can be understood that for specific implementations and beneficial effects of the blocks in the network device 1000 in this embodiment of the present application, reference should be made to the respective descriptions in the method embodiments. Details are not given here again.

[00335] FIG. 11 is a schematic structural diagram of a terminal device according to another embodiment of the present application. Terminal 1100 of FIG. 11 may implement a method that is for detecting a wake-up signal and is described in any of the above embodiments. Terminal 1100 in FIG. 11 may include a memory 1101 and a processor 1102. The memory 1101 may be used to store a program. The processor 1102 may be used to execute a program stored in memory. When the program stored in memory 1101 is executed, the processor 1102 may be configured to perform a method for detecting a wake-up signal as described in any of the above embodiments.

[00336] FIG. 12 is a schematic structural diagram of a network device according to another embodiment of the present application. The network device 1200 of FIG. 12 may implement a method that is for sending a wake-up signal and that is described in any of the above embodiments. The network device 1200 of FIG. 12 may include a memory 1201 and a processor 1202. The memory 1201 may be used to store a program. The processor 1202 may be used to execute a program stored in memory. When the program stored in memory 1201 is executed, the processor 1202 may be configured to perform a method for sending a wake-up signal, as described in any of the above embodiments.

[00337] An embodiment of the present application further provides a microcircuit (chip). The microcircuit includes a transceiver unit and a processing unit. The transceiver unit may be an I/O circuit or a communications interface. The processing unit is a processor, microprocessor, or integrated circuit integrated into a chip. The chip may implement the terminal-side method in the above embodiments.

[00338] An embodiment of the present application further provides a chip. The microcircuit includes a transceiver unit and a processing unit. The transceiver unit may be an I/O circuit or a communications interface. The processing unit is a processor, microprocessor, or integrated circuit integrated into a chip. The chip may implement the method performed on the side of the network device in the above embodiments.

[00339] Provided herein is a computer-readable storage medium, wherein the computer-readable storage medium stores an instruction; and when the instruction is executed in the computer, the computer executes the method for detecting the wake-up signal and which is described in any of the above embodiments.

[00340] The present application also provides a computer program product including an instruction. When the computer program product is running on the computer, the computer is provided with a method for detecting a wake-up signal, as described in any of the above embodiments.

[00341] Provided herein is a computer-readable storage medium, wherein the computer-readable storage medium stores an instruction; and when the instruction is executed in the computer, the computer executes the method for sending the wake-up signal, which is described in any of the above embodiments.

[00342] The present application also provides a computer program product including instructions. When the computer program product is running on the computer, the computer is enabled to execute the method for sending a wake-up signal as described in any of the above embodiments.

[00343] One skilled in the art may be aware that the blocks and steps of the algorithm in the examples described with reference to the embodiments disclosed herein may be implemented using electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on the particular application and design constraints. A person skilled in the art may use other methods to implement the described functions for each particular application, but such an implementation should not be considered outside the scope of this application.

[00344] One of ordinary skill in the art may appreciate that, for convenience and conciseness, for the detailed operating process of the described system, device, and unit, reference should be made to the corresponding process in the aforementioned method embodiments.

[00345] In several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method can be implemented in other ways. For example, the device embodiments described are merely examples. For example, the division into blocks is just a division of logical functions, and there may be another division in the actual implementation. For example, many blocks or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the interconnections or direct links or communication connections shown or described may be implemented using certain interfaces. Indirect links or communication connections between devices or units may be implemented in electronic form, mechanical form, or other form.

[00346] Blocks described as separate parts may or may not be physically separate, and parts shown as blocks may or may not be physical blocks, may be located in the same location, or may be distributed over multiple network blocks. Some or all of the blocks may be selected based on actual requirement to achieve the goals of the decisions according to the embodiments.

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

[00348] When functions are implemented in the form of a software functional block and sold or used as an independent product, the functions may be stored on a computer-readable storage medium. Based on this understanding, the technical solutions of the present application per se, or part contributing to the current technology, or some of the technical solutions can be implemented in the form of a software product. The software product is stored on a storage medium and includes several instructions for causing a computing device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes any medium on which program code can be stored, such as a USB flash drive, removable hard disk, read only memory (ROM), random access memory (RAM), magnetic disk. or CD.

[00349] The foregoing description represents only specific implementations of the present application, but is not intended to limit the scope of protection of this application. Any variation, change or substitution readily detectable by a person skilled in the art within the technical scope disclosed in this application should fall within the protection scope of this application. Therefore, the scope of protection of this application is determined by the scope of protection of the claims.

Claims (48)

1. A method for detecting a wake-up signal, comprising the steps of: sending, by means of the terminal device, first information to the network device, the first information indicating a reported interval; receiving, by the tag, second information from the network device, the second information indicating a configuration state of the first slot and a configuration state of the second slot; determining, by the terminal, a first slot configuration state and a second slot configuration state based on the second information, the terminal being an extended discontinuous reception (eDRX) configuration terminal; when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, determining by the terminal that the target interval is the first interval; and detecting, by the terminal, a wake-up signal at a detection position prior to the start position of the first paging event in the paging time window, wherein the detection position is determined based on the target interval and the maximum duration of the wake-up signal. 2. The method of claim 1, wherein the first interval is a short eDRX interval, the second interval is a long eDRX interval, and the long eDRX interval is greater than the short eDRX interval. 3. The method of claim 1 or 2, wherein the reported interval is a wake-up interval. 4. A method for sending a wake-up signal, comprising the steps of: receive by the network device the first information from the terminal device, the first information indicates the reported interval; sending, via the network device, second information to the terminal, the second information indicating a configuration state of the first slot and a configuration state of the second slot, the terminal being an extended discontinuous reception (eDRX) configuration terminal; when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, determining by the network device that the target interval is the first interval; and sending, by means of the network device, a wake-up signal at a detection position before the start position of the first paging event in the paging time window, wherein the detection position is determined based on the target interval and the maximum duration of the wake-up signal. 5. The method of claim 4, wherein the first interval is a short eDRX interval, the second interval is a long eDRX interval, and the long eDRX interval is greater than the short eDRX interval. 6. The method of claim 4 or 5, wherein the reported interval is a wake-up interval. 7. A terminal device configured to detect a wake-up signal, wherein the terminal device contains a memory and a processor, the memory being adapted to store a program, and the program, when executed by the processor, instructs the terminal device: send first information to the network device, wherein the first information indicates a reported interval; receive second information from the network device, the second information indicating a configuration state of the first slot and a configuration state of the second slot based on the second information; determine a configuration state of the first slot and a configuration state of the second slot based on the second information, wherein the terminal is an extended discontinuous reception (eDRX) configuration terminal; when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, determine that the target interval is the first interval; and detect a wake-up signal at a detection position before the start position of the first paging event (PO) in the paging time window, wherein the detection position is determined based on the target interval and the maximum duration of the wake-up signal. 8. The terminal of claim 7, wherein the first slot is a short eDRX slot, the second slot is a long eDRX slot, and the long eDRX slot is greater than the short eDRX slot. 9. The terminal according to claim 7 or 8, wherein the reported interval is the wake-up interval. 10. A network device capable of sending a wake-up signal, wherein the network device comprises a memory and a processor, the memory being adapted to store a program, and the program, when executed by the processor, instructs the network device to: receive first information from the terminal, the first information indicating a reported interval; send second information to the terminal, the second information indicating a configuration state of the first slot and a configuration state of the second slot, the terminal being an extended discontinuous reception (eDRX) configuration terminal; when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, determine that the target interval is the first interval; and send a wake-up signal at a detection position before the start position of the first paging event in the paging time window (PTW), wherein the detection position is determined based on the target interval and the maximum duration of the wake-up signal. 11. The network device of claim 10, wherein the first interval is a short eDRX interval, the second interval is a long eDRX interval, and the long eDRX interval is greater than the short eDRX interval. 12. The network device of claim 10 or 11, wherein the reported interval is the wakeup interval. 13. A computer-readable storage medium adapted to store instructions, wherein when the instructions are executed in the communication device, the communication device is provided with the execution of the method according to any one of claims 1-3. 14. A computer-readable storage medium adapted to store instructions, wherein when the instructions are executed in the communication device, the communication device is enabled to execute the method according to any one of claims 4-6. 15. A terminal device configured to detect a wake-up signal, while the terminal device contains: a sending unit (901), configured to send the first information to the network device, the first information indicating a reported interval; a receiving unit (902) configured to receive second information from the network device, the second information indicating a first slot configuration state and a second slot configuration state; a determination block (903) configured to: determine the configuration state of the first slot and the configuration state of the second slot based on the second information, wherein the terminal is an extended discontinuous reception (eDRX) configuration terminal, and when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, determine that the target interval is the first interval; and a detection unit (904) configured to detect a wakeup signal at a detection position before the start position of the first paging event in the paging time window, wherein the detection position is determined based on the target interval and the maximum duration of the wakeup signal. 16. The terminal of claim 15, wherein the first slot is a short eDRX slot, the second slot is a long eDRX slot, and the long eDRX slot is greater than the short eDRX slot. 17. The terminal according to claim 15 or 16, wherein the reported interval is the wake-up interval. 18. A network device configured to send a wake-up signal, wherein the network device comprises: a receiving unit (1001), configured to receive first information from the terminal, the first information indicating a reported interval; a sender (1002) configured to send second information to the terminal, the second information indicating a first slot configuration state and a second slot configuration state, the terminal being an extended discontinuous reception (eDRX) configuration terminal; and a determination unit (1003) configured: when the reported interval is 1 s or 2 s, the first interval is set to 40 ms, 80 ms, 160 ms, or 240 ms, and the second interval is not configured, to determine that the target interval is the first interval , wherein the sender (1002) is further configured to send a wakeup signal at a detection position prior to the start position of the first paging event in the paging time window, the detection position being determined based on the target interval and the maximum duration of the wakeup signal. 19. The network device of claim 18, wherein the first interval is a short eDRX interval, the second interval is a long eDRX interval, and the long eDRX interval is greater than the short eDRX interval. 20. The network device of claim 18 or 19, wherein the reported interval is the wake-up interval.

Images