Method and apparatus for monitoring and processing low-power wake-up signal, and related device

Abstract

The present application belongs to the technical field of communications. Disclosed are a method and apparatus for monitoring and processing a low-power wake-up signal (LP-WUS), and a related device. The method for monitoring and processing an LP-WUS in the embodiments of the present application comprises: a terminal receiving LP-WUS-related configuration information from a network-side device; and the terminal monitoring an LP-WUS on the basis of the LP-WUS-related configuration information, wherein the LP-WUS-related configuration information includes target information associated with an LP-WUS monitoring occasion, and the target information includes at least one of the following: first information and second information, the first information being used for indicating at least one LP-WUS codepoint or at least one LP-WUS sequence associated with the terminal, and the second information being used for indicating at least one LP-WUS codepoint or at least one LP-WUS sequence associated with the LP-WUS monitoring occasion.

Description

Low-power wake-up signal monitoring and processing methods, devices and related equipment

[0001] Cross-reference of related applications

[0002] This application claims priority to Chinese Patent Application No. 202411917328.X, filed in China on December 24, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, and specifically relates to a method, apparatus and related equipment for monitoring and processing low-power wake-up signals. Background Technology

[0004] With the development of communication technology, Low-Power Wake-Up Signals (LP-WUS) have been introduced into communication systems to control terminals to enter or exit power-saving modes. Currently, network-side equipment typically configures a set of LP-WUS codepoints or LP-WUS sequences for each terminal. The terminal uses this configured set of LP-WUS codepoints or LP-WUS sequences to listen for LP-WUS signals during LP-WUS monitoring occupancy (MO). This results in a relatively small total number of LP-WUS codepoints or LP-WUS sequences associated with the terminal, leading to a higher probability of false wake-ups. Summary of the Invention

[0005] This application provides a method, apparatus, and related equipment for monitoring and processing low-power wake-up signals, which can solve the problem that the small number of total LP-WUS code points or LP-WUS sequences associated with the terminal leads to a high probability of false wake-up.

[0006] Firstly, a low-power wake-up signal monitoring and processing method is provided, including:

[0007] The terminal receives LP-WUS-related configuration information from the network-side device.

[0008] The terminal performs LP-WUS monitoring according to the LP-WUS related configuration information;

[0009] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0010] First information;

[0011] Second information;

[0012] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0013] Secondly, a low-power wake-up signal monitoring and processing method is provided, including:

[0014] The network-side device sends a low-power wake-up signal (LP-WUS) and related configuration information to the terminal.

[0015] The network-side device sends LP-WUS according to the LP-WUS related configuration information;

[0016] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0017] First information;

[0018] Second information;

[0019] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0020] Thirdly, a low-power wake-up signal monitoring and processing device is provided, comprising:

[0021] The first receiving module is used to receive low-power wake-up signal (LP-WUS) related configuration information from the network-side device; and to perform LP-WUS monitoring according to the LP-WUS related configuration information.

[0022] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0023] First information;

[0024] Second information;

[0025] The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS monitoring time.

[0026] Fourthly, a low-power wake-up signal monitoring and processing device is provided, comprising:

[0027] The second transmitting module is used to send low-power wake-up signal (LP-WUS) related configuration information to the terminal; and to send LP-WUS according to the LP-WUS related configuration information.

[0028] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0029] First information;

[0030] Second information;

[0031] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0032] Fifthly, a low-power wake-up signal monitoring and processing apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0033] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0034] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to send third information to a network-side device, and the third information is used for the LP-WUS to listen;

[0035] The third information includes at least one of the following:

[0036] Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection;

[0037] Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

[0038] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0039] In a ninth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send low-power wake-up signal (LP-WUS) related configuration information to a terminal; and to send LP-WUS according to the LP-WUS related configuration information;

[0040] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0041] First information;

[0042] Second information;

[0043] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0044] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0045] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.

[0046] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0047] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0048] This application embodiment receives LP-WUS-related configuration information from a network-side device via a terminal. The terminal performs LP-WUS monitoring based on the LP-WUS-related configuration information. The LP-WUS-related configuration information includes target information associated with the LP-WUS monitoring timing. The target information includes at least one of the following: first information; second information. The first information indicates at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information indicates at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS monitoring timing. This expands the total number of LP-WUS sequences or LP-WUS code points compared to all LP-WUS monitoring timings corresponding to all LP-WUS sequences or LP-WUS code points. Therefore, this application embodiment reduces the probability of false wake-ups while increasing the coverage of the low-power wake-up signal sent by the network-side device. Attached Figure Description

[0049] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;

[0050] Figure 2 is a flowchart illustrating a low-power wake-up signal monitoring method provided in an embodiment of this application;

[0051] Figure 3 is a flowchart illustrating another low-power wake-up signal monitoring method provided in an embodiment of this application;

[0052] Figure 4 is a schematic diagram of a low-power wake-up signal monitoring and processing device provided in an embodiment of this application;

[0053] Figure 5 is a schematic diagram of another low-power wake-up signal monitoring and processing device provided in an embodiment of this application;

[0054] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0055] Figure 7 is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0056] Figure 8 is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0057] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0058] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0059] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0060] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical term. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0061] For ease of understanding, the following describes some aspects of the embodiments of this application:

[0062] I. Low-power receiver.

[0063] A low-power receiver can be understood as a low-power wake-up radio (LP-WUR) or an almost zero-power wake-up radio (AZP-WUR). The basic working principle of an LP-WUR is that the receiver includes a first module and a second module. The first module is the main communication module, used for transmitting and receiving mobile communication data. The second module is a low-power receiver module (also called a low-power wake-up receiver module), used to receive the wake-up signal. In power-saving mode, the terminal activates the low-power receiver module to listen for LP-WUR and disables the main communication module. When downlink data arrives, the network sends a wake-up signal to the terminal. After the terminal detects the wake-up signal through the low-power receiver module, it triggers the main communication module to turn on after a series of checks. At this time, the low-power receiver module transitions from an active state to a disabled state. The low-power wake-up receiver module can be continuously or intermittently activated, and when activated, it can receive low-power wake-up signals.

[0064] II. Low-power wake-up signal.

[0065] To reduce receiving activity in standby mode and effectively shut down the radio frequency (RF) and modem modules, thereby significantly reducing power consumption during communication reception, this can be achieved by introducing a near-zero power receiver into the terminal's receiver module. This near-zero power receiver eliminates the need for complex RF module signal detection (such as amplification, filtering, quantization, etc.) and modem signal processing, relying solely on passive matched filtering and low-power signal processing.

[0066] On the base station side, by triggering a wake-up signal on demand, the receiver with near-zero power can be activated to receive the activation notification, thereby triggering a series of processes within the terminal, such as turning on the radio frequency transceiver and baseband processing modules.

[0067] These wake-up signals are typically simple on-off keying signals, as shown in the figure. The receiver can then detect the wake-up notification through simple energy detection and subsequent sequence detection and recognition. Furthermore, while the terminal is activating its low-power wake-up receiver to receive the wake-up signal, the main receiver module can maintain a low power consumption level, thus saving power by receiving the wake-up signal.

[0068] Optionally, the reception of the low-power wake-up signal can be applied to terminals in the RRC_idle / inactive state or terminals in the RRC_connected state, thereby achieving terminal energy saving.

[0069] 3.1.3 UE Assistance Information (UAI) and UE capability information.

[0070] UE capability reporting needs to be triggered by the network side, while UAI can be reported at any time; UE capability is typically reported before Radio Resource Control (RRC) reconfigure, while UAI is typically adjusted after RRC reconfigure; UE capability information is static, while UAI is dynamic. The differences between the two are as follows:

[0071] 1. UE capability information can only be sent in response to a base station request, while UE auxiliary information can be sent at any time when the UE wants to send it.

[0072] 2. UE capability information is usually sent before RRCReconfiguration to help the base station avoid configuring content beyond the UE's capabilities, while UEassistanceInformation is sent after RRCReconfiguration to help the base station configure the parameters best suited for the UE for a specific time / duration.

[0073] 3. UE capability information usually indicates its maximum capability, while UE auxiliary information indicates the capability at a specific time (UE capability information is more of a static set of information, while UE auxiliary information is more of a dynamic set of information).

[0074] It should be noted that currently, there is no unified solution in the discussions regarding LP-WUS regarding how to configure LP-WUS MO and the LP-WUS information carrying method (codepoint, bitmap, or a combination of both). Furthermore, different LP-WUS information carrying methods and MO configuration methods require different numbers of codepoints or sequences that the terminal can associate or detect.

[0075] Therefore, when selecting the MO configuration or LP-WUS information carrying method, it is necessary to consider the number of terminal associations or detectable codepoints or sequences. To this end, the low-power wake-up signal monitoring processing method of this application is proposed.

[0076] The method for monitoring and processing low-power wake-up signals provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0077] Referring to Figure 2, this application embodiment provides a method for monitoring and processing a low-power wake-up signal. As shown in Figure 2, the method for monitoring and processing a low-power wake-up signal includes:

[0078] Step 201: The terminal receives low-power wake-up signal (LP-WUS) related configuration information from the network-side device;

[0079] Step 202: The terminal performs LP-WUS monitoring according to the LP-WUS related configuration information;

[0080] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0081] First information;

[0082] Second information;

[0083] The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal. That is, the first information can be terminal-specific, such as a terminal-level configuration. The second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with LP-WUS monitoring. That is, the second information can be shared by all terminals, such as a cell-level configuration.

[0084] In this embodiment, when at least one LP-WUS code point or at least one LP-WUS sequence is configured to be associated with an LP-WUS listening opportunity, it can be understood that this configuration is not applied to all MOs corresponding to the terminal or cell, but rather to each MO, with associated LP-WUS code points or LP-WUS sequences configured individually. By associating LP-WUS MOs with LP-WUS code points or LP-WUS sequences, the total number of LP-WUS sequences or LP-WUS code points is increased compared to a scheme that configures LP-WUS sequences or LP-WUS code points for all LP-WUS listening opportunities. Simultaneously, different LP-WUS code points or LP-WUS sequences can be associated or detected on different LP-WUS MOs, thus increasing the total number of LP-WUS code points or LP-WUS sequences that the terminal can detect, thereby reducing the probability of false wake-ups and improving the coverage of low-power wake-up signals sent by network-side devices.

[0085] Optionally, in some embodiments, the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring. Here, at least one LP-WUS code point can be understood as an LP-WUS code point in a set of LP-WUS code points or multiple LP-WUS code point sets, and at least one LP-WUS sequence can be understood as an LP-WUS sequence in a set of LP-WUS sequences or multiple LP-WUS sequence sets. By associating LP-WUS MO with LP-WUS code points or LP-WUS sequences, the total number of LP-WUS sequences or LP-WUS code points is expanded compared to all LP-WUS monitoring times corresponding to all LP-WUS sequences or LP-WUS code points. Meanwhile, the terminal can be configured to associate or detect different LP-WUS code points or LP-WUS sequences on different LP-WUS MOs within the LP-WUS MO set. This increases the total number of LP-WUS code points or LP-WUS sequences that the terminal can detect, thereby reducing the probability of false wake-ups and improving the coverage of low-power wake-up signals sent by network-side devices.

[0086] Optionally, the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS listening can be understood as: the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during at least one LP-WUS listening time, or the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during all LP-WUS listening times.

[0087] It should be noted that the LP-WUS listening time can include multiple LP-WUS listening times, such as one or more LP-WUS listening times from the LP-WUS MO set. Each LP-WUS listening time can be associated with the same first or second information, or all LP-WUS listening times can be associated with different LP-WUS listening times, or some LP-WUS listening times can be associated with the same first or second information, and some LP-WUS listening times can be associated with different first or second information. For example, at least two LP-WUS listening times in an LP-WUS MO set may be associated with different first or second information. Another example is that the same LP-WUS MO set may be associated with the same first or second information, while different LP-WUS MO sets may be associated with different first or second information. Taking the example of different LP-WUS listening times being associated with different first information, this can be understood as the LP-WUS code points or LP-WUS sequences associated with different LP-WUS listening times being at least partially different. If LP-WUS listening timing 1 is associated with LP-WUS code point 1, LP-WUS code point 2, and LP-WUS code point 3, and LP-WUS listening timing 2 meets the target conditions, then LP-WUS listening timing 1 and LP-WUS listening timing 2 are considered to be associated with different first pieces of information: the target conditions include any of the following:

[0088] The LP-WUS code points associated with LP-WUS listening time 2 are partially different from those associated with LP-WUS listening time 1. For example, the LP-WUS code points associated with LP-WUS listening time 2 include LP-WUS code point 2, LP-WUS code point 3 and LP-WUS code point 4.

[0089] The LP-WUS code points associated with LP-WUS listening time 2 are all different from those associated with LP-WUS listening time 1. For example, the LP-WUS code points associated with LP-WUS listening time 2 include LP-WUS code points 4, LP-WUS code points 5 and LP-WUS code points 6.

[0090] Optionally, at least two LP-WUS listening times that are associated with different first or second information can be understood as at least one of the following:

[0091] When the LP-WUS related configuration information includes the first information, the terminal associates different LP-WUS code points or LP-WUS sequences associated or detected by the terminal on at least two LP-WUS MOs;

[0092] When the LP-WUS related configuration information includes second information, different second information is associated at least two LP-WUS listening times.

[0093] Optionally, the LP-WUS code points or LP-WUS sequences associated on each LP-WUS MO can include LP-WUS code points or LP-WUS sequences associated with multiple terminals. This is because multiple terminals can perform detection on a single MO. There is no specific limitation on which terminals are associated with or detected on a particular MO. Furthermore, there is no limitation on which LP-WUS code points or sequences associated by a terminal on different MOs. For example, a terminal may listen for LP-WUS code points or sequences for all terminals on MO1; a terminal may listen for LP-WUS code point 1 or sequence 1 associated with it on MO2; and a terminal may listen for LP-WUS code points 2, 3, 4… or sequences 2, 3, 4… associated with it on MO3. Optionally, code point 1 or sequence 1 may be associated solely with the terminal or the packet to which the terminal belongs; code points 2, 3, 4… or sequences 2, 3, 4… may be associated with other terminals or the packets to which other terminals belong, in addition to being associated with the terminal or the packet to which the terminal belongs.

[0094] This application embodiment receives LP-WUS-related configuration information from a network-side device via a terminal. The terminal performs LP-WUS monitoring based on the LP-WUS-related configuration information. The LP-WUS-related configuration information includes target information associated with the LP-WUS monitoring timing. The target information includes at least one of the following: first information; second information. The first information indicates at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information indicates at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS monitoring timing. This expands the total number of LP-WUS sequences or LP-WUS code points compared to all LP-WUS monitoring timings corresponding to all LP-WUS sequences or LP-WUS code points. Therefore, this application embodiment reduces the probability of false wake-ups while increasing the coverage of the low-power wake-up signal sent by the network-side device.

[0095] Optionally, in some embodiments, the LP-WUS related configuration information further includes at least one of the following:

[0096] Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window;

[0097] Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method;

[0098] Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether Cyclic Redundancy Check (CRC) scrambling is used and information indicating the CRC length;

[0099] Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets;

[0100] The target orthogonal frequency-division multiplexing (OFDM) sequence is configured to be superimposed on an on-off keying (OOK) waveform.

[0101] Optionally, an LP-WUS listening window may include one or more LP-WUS MO sets.

[0102] Optionally, the above mapping method is indicated by the set of values ​​of X, that is, the mapping method is a mapping of 1 LP-WUS code point to X terminals or packets.

[0103] Optionally, the configuration related to OFDM sequences may include, for example, the number of candidate OFDM sequences on an OOK chip or an OFDM symbol, and the length of the OFDM sequence.

[0104] Optionally, in some embodiments, different first information is associated with the LP-WUS listening times in the LP-WUS listening time set, and the terminal performs LP-WUS listening according to the LP-WUS related configuration information, including:

[0105] The terminal performs LP-WUS listening at LP-WUS listening times corresponding to different first information in the LP-WUS listening time set until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

[0106] In this embodiment of the application, the terminal can perform LP-WUS listening at all LP-WUS listening times in the LP-WUS listening time set until the terminal detects that the LP-WUS carries the first information.

[0107] Optionally, when the terminal detects the LP-WUS code point or LP-WUS sequence indicated by the first information, it indicates that the terminal has detected the first indication information to wake up the terminal. That is, the terminal performs LP-WUS listening at the LP-WUS listening time in the LP-WUS listening time set until the terminal detects the first information indicating to wake up the terminal, at which point the terminal stops or exits LP-WUS listening. Here, stopping LP-WUS listening can be understood as the terminal stopping listening to subsequent LP-WUS MOs. Further, if the terminal resumes LP-WUS listening, it can continue LP-WUS listening.

[0108] Optionally, in some embodiments, the LP-WUS listening time sets within the LP-WUS listening time sets are associated with the same first information, the LP-WUS listening window includes at least two LP-WUS listening time sets, and the at least two LP-WUS listening time sets are associated with different first information. The terminal performing LP-WUS listening according to the LP-WUS related configuration information includes:

[0109] The terminal performs LP-WUS listening at at least some (partial or all) of the LP-WUS listening time sets corresponding to different first information until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

[0110] In this embodiment of the application, the terminal may not perform LP-WUS listening on all LP-WUS listening opportunities in the set of LP-WUS listening opportunities, thereby reducing the terminal's energy consumption.

[0111] Optionally, in some embodiments, the terminal performing LP-WUS monitoring based on the LP-WUS related configuration information includes:

[0112] The terminal performs LP-WUS listening at at least two LP-WUS listening times associated with different first information, and stops or exits LP-WUS listening when the terminal listens for the LP-WUS code point or LP-WUS sequence indicated by the first information.

[0113] Optionally, in some embodiments, the method further includes:

[0114] The terminal sends third information to the network-side device, and the third information is used for LP-WUS monitoring;

[0115] The third information includes at least one of the following:

[0116] Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection;

[0117] Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

[0118] In this embodiment, the number of LP-WUS code points or LP-WUS sequences that the terminal supports detecting can be understood as the maximum number of LP-WUS code points or LP-WUS sequences that the terminal supports detecting. Since the terminal reports information about the first capability and the second capability, it can provide more information to the network-side device, thereby facilitating the network-side device to configure a more reasonable LP-WUS-related configuration for the terminal.

[0119] In one embodiment, the terminal sending third information to the network-side device is not limited to steps 201 and 202. That is, the terminal sending third information to the network-side device can be independent of steps 201 and 202. In other words, in some embodiments, without omitting steps 201 and 202, the terminal can also perform the step of sending third information to the network-side device independently.

[0120] It is understood that the first capability includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports detecting, which is equivalent to the first capability including the number of LP-WUS code points or LP-WUS sequences that the terminal supports being configured to be associated.

[0121] It is understood that the number of OFDM sequences that the terminal supports detecting on the on / off keying OOK chip or on an OFDM symbol is equivalent to the number of OFDM sequences that the terminal supports being configured to be associated on the on / off keying OOK chip or on an OFDM symbol.

[0122] Optionally, the above OOK chip can be understood or replaced with the OOK ON chip (high-level portion).

[0123] Optionally, in some embodiments, the network-side device is configured or the protocol specifies target candidate values, which include at least one of the following:

[0124] The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected.

[0125] The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

[0126] Optionally, the first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M;

[0127] Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

[0128] For example, in some embodiments, both Y and M are 1.

[0129] Optionally, in some embodiments, the method further includes:

[0130] The terminal does not expect the network-side device to configure LP-WUS-related configuration information that exceeds the first capability or the second capability.

[0131] In this embodiment of the application, if the network-side device is configured with LP-WUS-related configuration information that exceeds the first capability or the second capability, the terminal may consider the network-side configuration to be incorrect and thus not apply the LP-WUS-related configuration information, such as not performing LP-WUS monitoring.

[0132] Optionally, in some embodiments, the third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

[0133] Optionally, in some embodiments, when the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following:

[0134] Triggered based on the request message sent by the network-side device;

[0135] Based on event triggering;

[0136] Periodic triggering.

[0137] For example, if a network-side device sends an RRC message to inquire about the terminal's relevant recommendations / preferences, the terminal will be triggered to report terminal auxiliary information, which includes the aforementioned third information.

[0138] For example, the terminal may proactively trigger the sending of terminal auxiliary information based on its implementation judgment. This terminal auxiliary information carries the aforementioned third information. If the terminal determines that the current offset configuration of the network-side device does not meet its own needs (such as service or communication transmission requirements), it will trigger the sending of terminal auxiliary information. Optionally, if the event is triggered, after the terminal reports terminal auxiliary information, a timer will be started, and the terminal will not report terminal auxiliary information again during the execution of this timer.

[0139] To better understand this application, some examples are provided below.

[0140] In some embodiments, the network-side device configures the terminal to associate and detect different sets of LP-WUS code points on different LP-WUS MOs; the terminal reports third information, which includes: the number of LP-WUS code points or LP-WUS sequences that the terminal supports detecting on an LP-WUS MO.

[0141] Optionally, the network-side device configures the terminal to associate with and detect different LP-WUS code point sets on different LP-WUS MOs. Specifically, LP-WUS MO 0 is associated with LP-WUS code point set 0 or LP-WUS sequence set 0, LP-WUS MO 1 is associated with LP-WUS code point set 1 or LP-WUS sequence set 1, LP-WUS MO 2 is associated with LP-WUS code point set 2 or LP-WUS sequence set 2, and LP-WUS MO 3 is associated with LP-WUS code point set 3 or LP-WUS sequence set 3. For example, LP-WUS codepoint set 0 includes LP-WUS codepoint 0, LP-WUS codepoint 1, LP-WUS codepoint 2 and LP-WUS codepoint 3; LP-WUS codepoint set 1 includes LP-WUS codepoint 4, LP-WUS codepoint 5, LP-WUS codepoint 6 and LP-WUS codepoint 7; LP-WUS codepoint set 2 includes LP-WUS codepoint 8, LP-WUS codepoint 9, LP-WUS codepoint 10 and LP-WUS codepoint 11; and LP-WUS codepoint set 3 includes LP-WUS codepoint 12, LP-WUS codepoint 13, LP-WUS codepoint 14 and LP-WUS codepoint 15. The advantage of this method is that it does not affect or increase the number of LP-WUS codepoints (hereinafter referred to as codepoints) that the terminal needs to support detection on a single MO, but it can expand the total number of codepoints that the terminal can associate by associating different LP-WUS codepoint sets on different LP-WUS MOs. For example, the terminal can support a maximum of 4 codepoints on a single MO. The network-side device is configured with an LP-WUS MO set containing 4 MOs. On different MOs, the terminal associates different LP-WUS codepoint sets, thus expanding the total number of codepoints associated by the terminal to 4 × 4 = 16. The network-side device can be configured to associate more types of codepoints with the terminal. For example, codepoint type 1 means that one codepoint is associated with one terminal or one UE group; codepoint type 2 means that one codepoint is associated with two terminals or two terminal groups... codepoint type n means that one codepoint is associated with n UEs or n UE groups.Network-side devices can be configured to associate a terminal with a codepoint of type 1 and other codepoint types. This increases the number of codepoints associated with the terminal, reducing the probability of false wake-ups or decreasing the overhead of WUS transmissions from the network-side device.

[0142] Optionally, the number of codepoints or sequences (i.e., LP-WUS sequences) contained in different LP-WUS MO-associated LP-WUS codepoint sets or LP-WUS sequence sets can be the same or different.

[0143] It should be noted that the specific codepoint or sequence associated with the terminal by the network-side device is determined by the network-side device itself and is not specified here.

[0144] Optionally, in some embodiments, the terminal reports third information, which includes the number of OFDM sequences that the terminal supports detection on an OOK (e.g., ON) chip or on an OFDM symbol. The network-side device configures the terminal with a suitable number of candidate OFDM sequences based on its terminal capabilities.

[0145] In one embodiment, the terminal needs to provide capability information regarding the number of OFDM sequences that the terminal supports detection on an OOK (e.g., ON) chip or on an OFDM symbol, so that the network-side device can configure the terminal with an appropriate number of candidate OFDM sequences for its terminal capabilities.

[0146] Optionally, the OFDM sequence on an OOK chip refers to an OFDM sequence superimposed on the OOK waveform, such as an OFDM sequence superimposed on each OOK ON chip (high-level portion). Optionally, the length of the OFDM sequence can be configured by the network-side device or agreed upon by the protocol. For example, the network-side device may configure two OFDM sequences associated on the OOK chip, with the two OFDM sequences being 0101 and 1010 respectively.

[0147] Optionally, the OFDM sequence that the terminal supports for detection on one OFDM symbol refers to the following: If the network-side device is configured to include four OOK chips on one OFDM symbol and uses Manchester encoding, then the OOK sequence is 1010. If the network-side device is configured to associate two OFDM symbols on one OOK chip, then the terminal needs to support four OFDM sequences on one OFDM symbol: 0101000001010000, 0101000010100000, 1010000010100000, and 1010000001010000. It should be noted that the sequence corresponding to the OOK OFF chip (low-level part) is 0000.

[0148] It should be noted that there are two ways for network-side devices to configure the LP-WUS codepoint set or LP-WUS sequence set associated with LP-WUS MOs. One approach is to configure each MO to be associated with the same LP-WUS codepoint set or LP-WUS sequence set. In this approach, the network-side device does not need to configure the LP-WUS codepoint set or LP-WUS sequence set associated with the terminal for each MO. The other approach is to configure different LP-WUS codepoint sets or LP-WUS sequence sets associated with different MOs. In this case, the network-side device needs to configure the LP-WUS codepoint set or LP-WUS sequence set associated with the terminal for each MO.

[0149] Referring to Figure 3, this embodiment of the application also provides a method for monitoring and processing a low-power wake-up signal. As shown in Figure 3, the method for monitoring and processing a low-power wake-up signal includes:

[0150] Step 301: The network-side device sends the Low Power Wake-up Signal (LP-WUS) and related configuration information to the terminal.

[0151] Step 302: The network-side device sends LP-WUS according to the LP-WUS related configuration information;

[0152] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0153] First information;

[0154] Second information;

[0155] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0156] Optionally, the LP-WUS related configuration information may also include at least one of the following:

[0157] Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window;

[0158] Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method;

[0159] Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length.

[0160] Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets;

[0161] The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

[0162] Optionally, the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring.

[0163] Optionally, the method further includes:

[0164] The network-side device receives third information from the terminal, and the third information is used for LP-WUS monitoring;

[0165] The third information includes at least one of the following:

[0166] Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection;

[0167] Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

[0168] Optionally, the network-side device is configured or the protocol specifies target candidate values, which include at least one of the following:

[0169] The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected.

[0170] The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

[0171] Optionally, the first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M;

[0172] Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

[0173] Optionally, the third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

[0174] Optionally, when the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following:

[0175] Triggered based on the request message sent by the network-side device;

[0176] Based on event triggering;

[0177] Periodic triggering.

[0178] The low-power wake-up signal monitoring and processing method provided in this application can be executed by a low-power wake-up signal monitoring and processing device. This application uses the execution of the low-power wake-up signal monitoring and processing method by a low-power wake-up signal monitoring and processing device as an example to illustrate the low-power wake-up signal monitoring and processing device provided in this application.

[0179] This application provides a low-power wake-up signal monitoring and processing device. As an example, the low-power wake-up signal monitoring and processing device can be a communication device or a component in a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0180] The low-power wake-up signal monitoring and processing device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0181] Specifically, referring to Figure 4, when the low-power wake-up signal monitoring and processing device is a terminal or a component within a terminal, the low-power wake-up signal monitoring and processing device 400 includes:

[0182] The first receiving module 401 is used to receive low-power wake-up signal (LP-WUS) related configuration information from the network-side device; and to perform LP-WUS monitoring according to the LP-WUS related configuration information.

[0183] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0184] First information;

[0185] Second information;

[0186] The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS monitoring time.

[0187] Optionally, the LP-WUS related configuration information may also include at least one of the following:

[0188] Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window;

[0189] Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method;

[0190] Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length.

[0191] Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets;

[0192] The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

[0193] Optionally, different first information is associated with the LP-WUS listening time in the LP-WUS listening time set. The first receiving module 401 is specifically used to perform LP-WUS listening on the LP-WUS listening time corresponding to different first information in the LP-WUS listening time set, until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, and then the terminal stops or exits LP-WUS listening.

[0194] Optionally, the LP-WUS listening time sets are associated with the same first information, and the LP-WUS listening window includes at least two LP-WUS listening time sets, and the at least two LP-WUS listening time sets are associated with different first information. The first receiving module 401 is specifically used to perform LP-WUS listening on at least a portion of the LP-WUS listening time sets corresponding to different first information, until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

[0195] Optionally, the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring.

[0196] Optionally, the first receiving module 401 is specifically used to perform LP-WUS listening at at least two LP-WUS listening times associated with different first information, until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

[0197] Optionally, the low-power wake-up signal monitoring and processing device 400 further includes:

[0198] The first sending module is used to send third information to the network-side device, and the third information is used for the LP-WUS to listen;

[0199] The third information includes at least one of the following:

[0200] Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection;

[0201] Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

[0202] Optionally, the network-side device is configured or the protocol specifies target candidate values, which include at least one of the following:

[0203] The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected.

[0204] The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

[0205] Optionally, the first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M;

[0206] Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

[0207] Optionally, the low-power wake-up signal monitoring and processing device 400 further includes:

[0208] The processing module is configured to prevent the network-side device from configuring LP-WUS-related configuration information that exceeds the first capability or the second capability.

[0209] Optionally, the third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

[0210] Optionally, when the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following:

[0211] Triggered based on the request message sent by the network-side device;

[0212] Based on event triggering;

[0213] Periodic triggering.

[0214] Referring to Figure 5, when the low-power wake-up signal monitoring and processing device is a network-side device or a component within a network-side device, the low-power wake-up signal monitoring and processing device 500 includes:

[0215] The second sending module 501 is used to send low-power wake-up signal LP-WUS related configuration information to the terminal; and to send LP-WUS according to the LP-WUS related configuration information.

[0216] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0217] First information;

[0218] Second information;

[0219] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0220] Optionally, the LP-WUS related configuration information may also include at least one of the following:

[0221] Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window;

[0222] Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method;

[0223] Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length.

[0224] Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets;

[0225] The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

[0226] Optionally, the at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring.

[0227] Optionally, the low-power wake-up signal monitoring and processing device 500 further includes:

[0228] The second receiving module is used to receive third information from the terminal, the third information being used for monitoring the LP-WUS;

[0229] The third information includes at least one of the following:

[0230] Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection;

[0231] Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

[0232] Optionally, the network-side device is configured or the protocol specifies target candidate values, which include at least one of the following:

[0233] The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected.

[0234] The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

[0235] Optionally, the first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M;

[0236] Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

[0237] Optionally, the third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

[0238] Optionally, when the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following:

[0239] Triggered based on the request message sent by the network-side device;

[0240] Based on event triggering;

[0241] Periodic triggering.

[0242] The low-power wake-up signal monitoring and processing device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2 to 3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0243] As shown in Figure 6, this application embodiment also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores a program or instructions that can run on the processor 601. When the program or instructions are executed by the processor 601, they implement the various steps of the above-mentioned low-power wake-up signal monitoring processing method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0244] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be a low-power wake-up signal monitoring and processing device as shown in FIG4. Specifically, FIG7 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0245] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0246] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. The terminal structure shown in Figure 7 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0247] It should be understood that, in this embodiment, the input unit 704 may include a graphics processor 7041 and a microphone 7042. The graphics processor 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0248] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0249] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0250] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0251] The radio frequency unit 701 is used to receive low-power wake-up signal (LP-WUS) related configuration information from the network-side device and to perform LP-WUS monitoring according to the LP-WUS related configuration information.

[0252] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0253] First information;

[0254] Second information;

[0255] The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS monitoring time.

[0256] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the terminal side method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0257] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG3. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0258] Specifically, this application embodiment also provides a network-side device, which can be a low-power wake-up signal monitoring and processing device as shown in FIG. 5. As shown in FIG. 8, the network-side device 800 includes: an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804, and a memory 805. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be transmitted and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and transmits it through the antenna 801.

[0259] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 803, which includes a baseband processor.

[0260] The baseband device 803 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG8. One of the chips is, for example, a baseband processor, which is connected to the memory 805 via a bus interface to call the program or instructions in the memory 805 to execute the network-side device operation shown in the above method embodiment.

[0261] The network-side device may also include a network interface 806, such as a Common Public Radio Interface (CPRI).

[0262] The radio frequency device 802 is used to send low-power wake-up signal LP-WUS related configuration information to the terminal; and to send LP-WUS according to the LP-WUS related configuration information.

[0263] The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following:

[0264] First information;

[0265] Second information;

[0266] Wherein, the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal; the second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time.

[0267] In addition, the network-side device 800 in this application embodiment also includes: a program or instructions stored in a memory 805 and executable on a processor 804. The processor 804 calls the program or instructions in the memory 805 to execute the methods executed by each module shown in FIG6 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0268] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described low-power wake-up signal monitoring and processing method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0269] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0270] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described low-power wake-up signal monitoring and processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0271] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0272] This application also provides a computer program / program product, which includes computer instructions. The computer program / program product is executed by at least one processor to implement the various processes of the above-described low-power wake-up signal monitoring processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0273] This application also provides a wireless communication system, including: a terminal and a network-side device. The terminal can be used to perform the steps of the terminal-side low-power wake-up signal monitoring and processing method described above, and the network-side device can be used to perform the steps of the network-side device low-power wake-up signal monitoring and processing method described above.

[0274] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0275] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0276] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for monitoring and processing low-power wake-up signals, comprising: The terminal receives LP-WUS-related configuration information from the network-side device. The terminal performs LP-WUS monitoring according to the LP-WUS related configuration information; The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes: First information; wherein the first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal.

2. The method according to claim 1, wherein, The LP-WUS related configuration information also includes at least one of the following: The second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time; Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window; Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method; Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length. Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets; The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

3. The method according to claim 1 or 2, wherein, The LP-WUS listening time set is associated with different first information on the LP-WUS listening time, and the terminal performs LP-WUS listening according to the LP-WUS related configuration information, including: The terminal performs LP-WUS listening at LP-WUS listening times corresponding to different first information in the LP-WUS listening time set until the terminal listens to the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

4. The method according to claim 1 or 2, wherein, The LP-WUS listening time sets are associated with the same first information, the LP-WUS listening window includes at least two LP-WUS listening time sets, and the at least two LP-WUS listening time sets are associated with different first information. The terminal performs LP-WUS listening according to the LP-WUS related configuration information, including: The terminal performs LP-WUS listening at at least a portion of the LP-WUS listening time sets corresponding to different first information until the terminal detects the LP-WUS code point or LP-WUS sequence indicated by the first information, at which point the terminal stops or exits LP-WUS listening.

5. The method according to claim 1, wherein, The at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring.

6. The method according to claim 1, wherein, The terminal performs LP-WUS monitoring based on the LP-WUS related configuration information, including: The terminal performs LP-WUS listening at at least two LP-WUS listening times associated with different first information, and stops or exits LP-WUS listening when the terminal listens for the LP-WUS code point or LP-WUS sequence indicated by the first information.

7. The method according to any one of claims 1 to 6, wherein the method further comprises: The terminal sends third information to the network-side device, and the third information is used for LP-WUS monitoring; The third information includes at least one of the following: Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection; Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

8. The method according to claim 7, wherein, The network-side device configuration or protocol specifies the target candidate value, which includes at least one of the following: The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected. The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

9. The method according to claim 8, wherein, The first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M; Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

10. The method according to any one of claims 7 to 9, wherein the method further comprises: The terminal does not expect the network-side device to configure LP-WUS-related configuration information that exceeds the first capability or the second capability.

11. The method according to any one of claims 7 to 10, wherein, The third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

12. The method according to claim 11, wherein, When the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following: Triggered based on the request message sent by the network-side device; Based on event triggering; Periodic triggering.

13. A method for monitoring and processing low-power wake-up signals, comprising: The network-side device sends a low-power wake-up signal (LP-WUS) and related configuration information to the terminal. The network-side device sends LP-WUS according to the LP-WUS related configuration information; The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following: First information; The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal.

14. The method according to claim 13, wherein, The LP-WUS related configuration information also includes at least one of the following: The second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time; Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window; Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method; Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length. Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets; The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

15. The method according to claim 14, wherein, The at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal includes at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal during LP-WUS monitoring, or at least one LP-WUS code point or at least one LP-WUS sequence that the terminal needs to detect during LP-WUS monitoring.

16. The method according to any one of claims 13 to 15, wherein the method further comprises: The network-side device receives third information from the terminal, and the third information is used for LP-WUS monitoring; The third information includes at least one of the following: Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection; Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

17. The method according to claim 16, wherein, The network-side device configuration or protocol specifies the target candidate value, which includes at least one of the following: The terminal supports the first candidate value of the number of LP-WUS code points or LP-WUS sequences to be detected. The second candidate value for the number of OFDM sequences that the terminal supports detecting on an OOK chip or an OFDM symbol.

18. The method according to claim 17, wherein, The first candidate value includes at least one of the following: 1, 2, 2 L-Y and 2 X -M; Where L is the information bit length of the LP-WUS; X is determined based on the number of LP-WUS groups associated with LP-WUS code points; and Y and M are both positive integers.

19. The method according to any one of claims 16 to 18, wherein, The third information is carried by at least one of terminal capability reporting information and terminal auxiliary information.

20. The method according to claim 19, wherein, When the third information is carried through terminal auxiliary information, the triggering method of the third information includes at least one of the following: Triggered based on the request message sent by the network-side device; Based on event triggering; Periodic triggering.

21. A low-power wake-up signal monitoring and processing device, comprising: The first receiving module is used to receive configuration information related to the Low Power Wake-up Signal (LP-WUS) from the network-side device. Perform LP-WUS monitoring based on the aforementioned LP-WUS configuration information; The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following: First information; The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal.

22. The apparatus according to claim 21, wherein, The LP-WUS related configuration information also includes at least one of the following: The second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time; Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window; Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method; Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length. Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets; The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

23. The apparatus of claim 21, further comprising a processing module, wherein, The first receiving module is further configured to perform LP-WUS listening at the at least two LP-WUS listening times when different first information is associated at the at least two LP-WUS listening times; The processing module is used to stop or exit LP-WUS listening when the terminal detects that LP-WUS is carrying the first information.

24. The apparatus according to any one of claims 21 to 23, further comprising: The first sending module is used to send third information to the network-side device, and the third information is used for the LP-WUS to listen; The third information includes at least one of the following: Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection; Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

25. A low-power wake-up signal monitoring and processing device, comprising: The second transmitting module is used to send low-power wake-up signal LP-WUS related configuration information to the terminal. Send LP-WUS according to the LP-WUS related configuration information; The LP-WUS related configuration information includes target information associated with the LP-WUS monitoring timing, and the target information includes at least one of the following: First information; The first information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the terminal.

26. The apparatus according to claim 25, wherein, The LP-WUS related configuration information also includes at least one of the following: The second information is used to indicate at least one LP-WUS code point or at least one LP-WUS sequence associated with the LP-WUS listening time; Configuration information for LP-WUS listening timing, wherein the configuration information for LP-WUS listening timing includes at least one of the following: configuration information for the LP-WUS listening timing set and configuration information for the LP-WUS listening window; Information used to indicate the information bit carrying method of LP-WUS, wherein the carrying method includes at least one of bitmap method and code point method; Information used to indicate the scrambling method of LP-WUS information bits includes at least one of information indicating whether CRC scrambling is used and information indicating the CRC length. Information used to indicate the code point type, which represents the mapping method between LP-WUS code points and LP-WUS packets; The target orthogonal frequency division multiplexing (OFDM) sequence is configured to be superimposed on the on / off keying OOK waveform.

27. The apparatus according to claim 25 or 26, further comprising: The second receiving module is used to receive third information from the terminal, the third information being used for monitoring the LP-WUS; The third information includes at least one of the following: Information on the first capability, which includes the number of LP-WUS code points or LP-WUS sequences that the terminal supports for detection; Information on the second capability, which includes the number of OFDM sequences that the terminal supports detection on an on / off keying OOK chip or on an OFDM symbol.

28. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the low-power wake-up signal monitoring processing method as described in any one of claims 1 to 12.

29. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the low-power wake-up signal monitoring processing method as described in any one of claims 13 to 20.

30. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the low-power wake-up signal monitoring method as described in any one of claims 1 to 20.

31. A computer program product comprising computer instructions that, when executed by a processor, implement the steps of the low-power wake-up signal monitoring processing method as described in any one of claims 1 to 20.

Images