Methods for enabling and configuring monitoring, devices, terminals, and network-side equipment.
By configuring the first parameter, the terminal can directly start PDCCH listening even when it cannot listen to LP-WUS, which solves the problem of large terminal communication transmission latency and achieves timely wake-up and performance improvement.
Patent Information
- Application Number
- CN202510636320.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-16
- Publication Date
- 2026-11-17
AI Technical Summary
When the terminal is unable to listen to the Low Power Wake-up Signal (LP-WUS), it cannot resume listening to the Physical Downlink Control Channel (PDCCH), resulting in a large communication transmission delay.
A method for enabling PDCCH listening is provided, which enables the terminal to directly enable PDCCH listening when it is unable to listen to LP-WUS by configuring a first parameter. This includes enabling PDCCH listening in the first case when the terminal is configured with a first parameter or a first parameter with a definite value.
This ensures that the terminal can listen to the PDCCH sent by the network-side device in a timely manner, reducing communication transmission latency and improving the transmission performance between the terminal and the network-side device.
Smart Images

Figure CN123123935A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, specifically relating to a method for enabling monitoring, a method for configuring monitoring, an apparatus, a terminal, and a network-side device. Background Technology
[0002] In some communication systems, a wake-up signal (WUS) is introduced to save terminal power consumption. For example, the terminal determines when to listen for WUS during the monitoring occupancy (MO) based on the configuration sent by the network-side device. Upon detecting WUS, the terminal starts listening on the Physical downlink control channel (PDCCH), thus reducing PDCCH listening activity and saving terminal power. However, in practice, because the terminal may be unable to listen for WUS, according to relevant technologies, the terminal can only start listening if it detects the indicated WUS. This means the terminal will be unable to resume PDCCH listening, potentially preventing it from being woken up by the network-side device and resulting in significant communication transmission latency. Summary of the Invention
[0003] This application provides a method for enabling monitoring, a method for configuring monitoring, an apparatus, a terminal, and a network-side device, which can solve the problem of large communication transmission latency of the terminal.
[0004] Firstly, a method for starting a listener is provided, including:
[0005] If the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, the terminal will start listening to the Physical Downlink Control Channel (PDCCH) in the first case.
[0006] The first case includes at least one of the following:
[0007] The terminal cannot listen to the low-power wake-up signal LP-WUS;
[0008] The terminal was not listening to LP-WUS;
[0009] The terminal does not need to monitor LP-WUS;
[0010] The terminal does not expect to listen to LP-WUS.
[0011] Secondly, a listening configuration method is provided, including:
[0012] The network-side device sends configuration information to the terminal. The configuration information may carry a first parameter. The first parameter, or the first parameter that is affirmatively taken, is used by the terminal to enable the listening of the physical downlink control channel (PDCCH) in a first situation.
[0013] The first case includes at least one of the following:
[0014] Cannot listen to the low-power wake-up signal LP-WUS;
[0015] LP-WUS not being monitored;
[0016] No need to monitor LP-WUS;
[0017] I do not expect to monitor LP-WUS.
[0018] Thirdly, a listening activation device is provided, comprising:
[0019] The processing module is used to enable the monitoring of the physical downlink control channel (PDCCH) in the first case if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value.
[0020] The first case includes at least one of the following:
[0021] The terminal cannot listen to the low-power wake-up signal LP-WUS;
[0022] The terminal was not listening to LP-WUS;
[0023] The terminal does not need to monitor LP-WUS;
[0024] The terminal does not expect to listen to LP-WUS.
[0025] Fourthly, a monitoring configuration device is provided, comprising:
[0026] The sending module is used to send configuration information to the terminal. The configuration information may carry a first parameter. The first parameter or the first parameter that is affirmatively taken is used by the terminal to enable the listening of the physical downlink control channel (PDCCH) in a first situation.
[0027] The first case includes at least one of the following:
[0028] Cannot listen to the low-power wake-up signal LP-WUS;
[0029] LP-WUS not being monitored;
[0030] No need to monitor LP-WUS;
[0031] I do not expect to monitor LP-WUS.
[0032] Fifthly, a listening activation device is provided, the device being configured to perform the steps of the method described in the first aspect.
[0033] In a sixth aspect, a monitoring configuration device is provided, the device being configured to perform the steps of the method described in the second aspect.
[0034] In a seventh 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.
[0035] Eighthly, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to enable listening to the Physical Downlink Control Channel (PDCCH) in a first situation if the terminal is configured with a first parameter or is configured with a first parameter having a definite value; wherein the first situation includes at least one of the following: the terminal cannot listen to the Low Power Wake-up Signal (LP-WUS); the terminal is not listening to LP-WUS; the terminal does not need to listen to LP-WUS; the terminal does not expect to listen to LP-WUS.
[0036] A ninth aspect provides a 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 aspect X.
[0037] In a tenth aspect, a network-side device is provided, including a processor and a communication interface, wherein the processor is used to send configuration information to a terminal, the configuration information may carry a first parameter, and the first parameter, or the first parameter having a confirmed value, is used by the terminal to enable listening to the Physical Downlink Control Channel (PDCCH) under a first condition; wherein the first condition includes at least one of the following: unable to listen to the Low Power Wake-up Signal (LP-WUS); not listening to LP-WUS; not needing to listen to LP-WUS; not expecting to listen to LP-WUS.
[0038] Eleventhly, 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.
[0039] In a twelfth aspect, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, and the network-side device is configured to perform the steps of the method described in the second aspect.
[0040] In a thirteenth 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.
[0041] In a fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to perform the steps of the method as described in the second aspect, or the computer program / program product is executed by at least one processor to perform the steps of the method as described in the second aspect.
[0042] In this embodiment, if the terminal is configured with a first parameter or a first parameter with a definite value, the terminal enables PDCCH listening in a first situation. The first situation includes at least one of the following: the terminal cannot listen to the Low Power Wake-up Signal (LP-WUS); the terminal is not listening to LP-WUS; the terminal does not need to listen to LP-WUS; the terminal does not expect to listen to LP-WUS. Thus, if the terminal is configured with the first parameter or a first parameter with a definite value, the terminal enables PDCCH listening in the first situation. This allows the terminal to promptly listen to the PDCCH sent by the network-side device, enabling it to be woken up by the network-side device in a timely manner, thereby reducing communication transmission latency. Furthermore, the first parameter ensures that the terminal and the network-side device have a consistent understanding of enabling PDCCH listening in the first situation, thus improving transmission performance between the terminal and the network-side device. Attached Figure Description
[0043] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;
[0044] Figure 2a This is a schematic diagram illustrating the operation of a receiving terminal according to an embodiment of this application;
[0045] Figure 2b This is a schematic diagram of a waveform provided in an embodiment of this application;
[0046] Figure 3a This is a schematic diagram of a listening device provided in an embodiment of this application;
[0047] Figure 3b This is a schematic diagram of another form of eavesdropping provided in an embodiment of this application;
[0048] Figure 4 This is a flowchart of a method for enabling listening provided in an embodiment of this application;
[0049] Figure 5This is a flowchart of a monitoring configuration method provided in an embodiment of this application;
[0050] Figure 6a This is a schematic diagram of another form of eavesdropping provided in an embodiment of this application;
[0051] Figure 6b This is a schematic diagram of another form of eavesdropping provided in an embodiment of this application;
[0052] Figure 7 This is a structural diagram of a listening configuration device provided in an embodiment of this application;
[0053] Figure 8 This is a structural diagram of a listening activation device provided in an embodiment of this application;
[0054] Figure 9 This is a structural diagram of a communication device provided in an embodiment of this application;
[0055] Figure 10 This is a structural diagram of a terminal provided in an embodiment of this application;
[0056] Figure 11 This is a structural diagram of a network-side device provided in an embodiment of this application. Detailed Implementation
[0057] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments 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 devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, 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 specific technical terms. 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.
[0062] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.
[0063] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).
[0064] Low-power receivers, also known as LP-WUR or near-zero power wake-up radios (AZP-WUR), operate on the principle that the receiver consists of a first module and a second module, as detailed below. Figure 2a As shown, the first module is the main communication module, used for sending 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 monitor LP-WUS and disables the main communication module. When downlink data arrives, the network side 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 from off to on through a series of checks. At this time, the low-power receiver module transitions from an active state to an off or sleep state. The low-power receiver module can be continuously or intermittently activated, and when activated, it can receive the 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, performing only 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, thereby triggering a series of processes inside 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 (OOK) signals, and their time-domain representation is as follows: Figure 2b As shown, the receiver can detect the wake-up signal through simple energy detection and subsequent possible sequence detection and recognition processes. Furthermore, while the terminal activates the low-power wake-up receiver to receive the wake-up signal, the main receiver module can maintain operation at a low power consumption level, thereby saving power by receiving the wake-up signal. The reception of the low-power wake-up signal can be applied to terminals in Radio Resource Control (RRC) idle / inactive states, as well as terminals in RRC connected states, thus achieving terminal energy saving. In addition, different types of low-power receivers can be served by superimposing specific OFDM sequences on the OOK ON chip. One type of low-power receiver is the OOK receiver, which the terminal uses to detect the OOK waveform sequence to obtain the information carried by the wake-up signal. Another type of low-power receiver is the OFDM receiver, which the terminal uses to detect the OFDM sequence on the OOK ON chip to obtain the information carried by the wake-up signal.
[0068] Understandably, the low-power wake-up signal is different from DCI.
[0069] Optionally, in this embodiment, the low-power wake-up signal LP-WUS can be replaced with the wake-up signal WUS. For example, WUS is used in standard protocols to describe the LP-WUS involved in this application.
[0070] In some embodiments, the low power (LP-WUS) option 1-1 scheme is described in detail.
[0071] In the LP-WUS option 1-1 scheme, when the terminal detects WUS, it enables Discontinuous Reception (DRX) and starts a duration timer (onDuration Timer), specifically as follows: Figure 3a As shown. In this scheme, WUS MO is configured relative to the start time of the DRX duration. For example, the terminal is configured with a time offset of 2 ( Figure 3aIn the LP-WUSoffset2), the offset 2 is configured relative to the start time of DRX onduration, and before DRX onduration, the terminal listens for WUS on the first Z WUS MOs after the start position indicated by the time offset 2, where Z is a positive integer.
[0072] In some embodiments, the low power (LP-WUS) option 1-2 schemes are mainly described.
[0073] The LP-WUS option 1-2 scheme is that the terminal detects LP-WUS on the LP-WUS MO. When LP-WUS is detected, a PDCCH monitoring timer is started at a specific time interval, such as the wake-up signal PDCCH monitoring timer (WUS_PDCCH Monitoring Timer). The terminal performs PDCCH monitoring during the operation of the PDCCH monitoring timer.
[0074] In some implementations, the start time of a specific time interval is the start time of a wake-up signal listening opportunity or the start time of the first wake-up signal listening opportunity in a set of wake-up signal listening opportunities. A set of wake-up signal listening opportunities refers to one or more wake-up signal listening opportunities within a wake-up signal cycle.
[0075] In addition, the relationship between the LP-WUS option 1-2 monitoring scheme and the DRX configuration can be at least one of the following:
[0076] When the terminal is configured or using LP-WUS option 1-2, the drx-onDuration Timer is not enabled. It is understood that if the drx-onDuration Timer is not enabled, then the time period corresponding to that drx-onDuration Timer is not considered part of the DRX activation time.
[0077] The PDCCH listening timer triggered by the aforementioned LP-WUS belongs to the DRX activation time;
[0078] The terminal does not perform LP-WUS listening during the DRX activation period.
[0079] In the LP-WUS option 1-2 scheme, the PDCCH listening timer triggered by LP-WUS is different from or not the drx-onDuration Timer.
[0080] In some embodiments, the Radio Resource Control (RRC) connected-state DRX is mainly described, as follows:
[0081] A basic DRX cycle is as follows: Figure 3b As shown, the DRX cycle consists of "On Duration" and "Opportunity for DRX": during the "On Duration" period, the terminal listens to the PDCCH; during the "Opportunity for DRX" period, the terminal does not listen to the PDCCH to save power.
[0082] In addition, the network is configured with a DRX inactivity timer. If a new PDCCH is received within the DRX duration, the drx-inactivity timer will be started or restarted to extend the duration for which the terminal listens for the PDCCH.
[0083] In some embodiments, when DRX is configured, the DRX activation time includes the following:
[0084] The time during which the drx-onDurationTimer or the DRX inactive timer (drx-InactivityTimer) configured within the DRX group is running; or,
[0085] The running time of the DRX downlink retransmission timer (drx-RetransmissionTimerDL), DRX uplink retransmission timer (drx-RetransmissionTimerUL), or DRX secondary link retransmission timer (drx-RetransmissionTimerSL) of any serving cell within the DRX group; or,
[0086] The time that the contention resolution timer (ra) or message B response window (msgB) is running; or,
[0087] When a scheduling request has been sent on the Physical Uplink Control Channel (PUCCH) and is in a pending state. If the serving cell is a non-terrestrial network, the activity period begins at: the time when the scheduling request transmission is completed when the scheduling request counter (SR_COUNTER) configured for all pending scheduling requests (SR) is 0, plus the round-trip delay between the terminal and the base station; or,
[0088] After successfully receiving a random access response, if the Medium Access Control (MAC) entity has not selected a preamble from the contention-based random access preamble, and has not yet received a PDCCH addressing the MAC entity's Cell Radio Network Temporary Identifier (C-RNTI) indicating a new transmission; or
[0089] The time during which a Layer 1 or Layer 2 triggered mobility (L1 / L2-Triggered Mobility, LTM) cell handover is underway without a Random Access Channel (RACH); or,
[0090] The time during which a RACH-less handover is taking place in the terrestrial network.
[0091] In some embodiments, the nominal LP-WUS MO duration includes OFDM symbol resources that may or may not be available for LP-WUS transmission.
[0092] The actual LP-WUS MO duration refers to the actual number of OFDM symbols assumed by the terminal for LP-WUS transmission.
[0093] Based on the above definition, there are two schemes for configuring LP-WUS MO, as follows:
[0094] Option 1: The network-side device only configures the actual LP-WUS MO duration. Starting from the beginning of an LP-WUS MO, this MO extends until the number of OFDM symbols available for actual LP-WUS transmission reaches the configured actual LP-WUS duration. Furthermore, the network-side device can configure the maximum duration of an LP-WUS MO. If the extended length of an LP-WUS MO exceeds the configured maximum duration, then that LP-WUS MO is invalid, and the terminal discards it.
[0095] Option 2: The network-side device configures a nominal LP-WUS MO duration and an actual LP-WUS MO duration. If the number of OFDM symbols available for actual LP-WUS transmission within the nominal LP-WUS MO duration is less than the configured actual LP-WUS duration, the LP-WUS MO is considered invalid (the terminal does not perform LP-WUS listening during an invalid LP-WUS MO). The invalid LP-WUS MO is discarded or delayed until the next valid LP-WUS MO. It is understood that the number of OFDM symbols available for pre-LP-WUS transmission within a nominal MO duration can be different for different LP-WUS MOs.
[0096] The following description, in conjunction with the accompanying drawings, details the monitoring activation method, monitoring configuration method, apparatus, terminal, and network-side device provided in this application through some embodiments and application scenarios.
[0097] Please see Figure 4 , Figure 4 This is a flowchart of a listening start method provided in an embodiment of this application, such as... Figure 4 As shown, it includes the following steps:
[0098] Step 401: If the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, then the terminal starts listening to the PDCCH in the first case.
[0099] The first case includes at least one of the following:
[0100] The terminal cannot listen to LP-WUS;
[0101] The terminal was not listening to LP-WUS;
[0102] The terminal does not need to monitor LP-WUS;
[0103] The terminal does not expect to listen to LP-WUS.
[0104] In some implementations, the first parameter may be used to indicate whether PDCCH listening is enabled in the first situation, or the first parameter may be used to indicate that PDCCH listening is enabled in the first situation, or the first parameter may be used to enable the terminal to enable PDCCH listening in the first situation.
[0105] The above statement that if the terminal is configured with a first parameter or a first parameter with a definite value, then the terminal enables PDCCH listening in the first case can be understood as the terminal being configured with a first parameter or a first parameter with a definite value and the first case being satisfied simultaneously, then enabling PDCCH listening. It can also be expressed as the terminal being configured with a first parameter or a first parameter with a definite value, and in the first case, enabling PDCCH listening.
[0106] If the terminal is configured with a first parameter or a first parameter with a definite value, then enabling PDCCH listening in the first case may include:
[0107] If the terminal is configured with a first parameter, and the first parameter is used to indicate that the terminal that enables PDCCH listening in the first case enables PDCCH listening in the first case; or,
[0108] If the first parameter is used to indicate whether to enable PDCCH listening in the first case, and the terminal is configured with the first parameter having a positive value, then the terminal enables PDCCH listening in the first case; wherein, when the first parameter has a positive value, it indicates that PDCCH listening is enabled in the first case.
[0109] Since the first parameter is used to indicate that the terminal enables PDCCH listening in the first situation, that is, in the embodiments of this application, the terminal being configured with the first parameter or being configured with the first parameter having a definite value can be understood as the terminal being configured to enable PDCCH listening in the first situation.
[0110] Enabling PDCCH listening as described above can mean that the terminal starts listening to PDCCH, or that the terminal initiates the PDCCH listening behavior.
[0111] The inability of the aforementioned terminal to listen to LP-WUS may be due to various reasons, such as behavioral conflicts or resource conflicts, preventing the terminal from listening to LP-WUS in LP-WUS MO.
[0112] The aforementioned "terminal not listening to LP-WUS" can mean that the terminal is not listening to LP-WUS on the LP-WUS MO. Here, "terminal not listening to LP-WUS" means that the terminal is not performing LP-WUS listening (also known as detection), which is different from the case where the terminal is listening to LP-WUS but does not detect WUS. It is understandable that, since the terminal is not listening to LP-WUS in the first case, the terminal does not consume LP-WUS listening power in the first case.
[0113] The terminal may decide not to listen to LP-WUS on the LP-WUS MO. For example, if the LP-WUS MO is invalid, the terminal does not need to listen to it.
[0114] The above statement that the terminal does not expect to listen to LP-WUS can mean that the terminal does not expect to listen to LP-WUS on the LP-WUS MO.
[0115] It should be noted that LP-WUS is not PDCCH, but a wake-up signal that is different from downlink control information format 2-6 (DCI format 2-6).
[0116] In this embodiment, if the terminal is configured with a first parameter or a first parameter with a definite value, the terminal will start listening to the PDCCH in the first case. This allows the terminal to listen to the PDCCH sent by the network-side device in a timely manner, so that the terminal can be woken up by the network-side device in a timely manner, thereby reducing the communication transmission latency of the terminal.
[0117] In addition, the first parameter can make the terminal and the network-side device understand the PDCCH listening in the first case in a consistent way, which can improve the transmission performance between the terminal and the network-side device.
[0118] For example, network-side devices can determine whether to configure a first parameter for the terminal under certain circumstances, meaning the terminal will enable PDCCH listening in that first situation. In other cases, the network-side device will not configure the first parameter for the terminal, meaning the terminal will not enable PDCCH listening in that first situation. This allows for flexible handling and control of terminal behavior under different circumstances.
[0119] As an optional implementation, the method further includes:
[0120] The terminal receives the first parameter sent by the network-side device.
[0121] The first parameter received by the terminal from the network-side device may be the first parameter received by the terminal from the network-side device, configuration information of the first parameter, or the value of the first parameter (such as a definite value). The configuration information is used to configure the first parameter.
[0122] In this embodiment, the network-side device configuring the aforementioned first parameter to the terminal can be understood as the network-side device instructing the terminal to enable PDCCH listening in the first situation.
[0123] In the above embodiments, the network-side device can dynamically configure the first parameter to the terminal, so that the terminal and the network-side device can better understand and agree on the PDCCH listening behavior, further improve the communication performance between the terminal and the network-side device, and better avoid the terminal sending the PDCCH incorrectly to the network-side device.
[0124] It should be noted that in the embodiments of this application, the first parameter mentioned above may also be pre-configured or agreed upon by the protocol, such as the protocol stipulating that the terminal is configured with the first parameter mentioned above.
[0125] In some implementations, if the terminal is not configured with a first parameter or is configured with a first parameter that has a negative value, it can be understood that the terminal does not enable PDCCH listening by default in the first case.
[0126] In some implementations, the first parameter can be configured with one or more first parameters based on different first situations. For example, a corresponding first parameter can be configured for the terminal not being able to listen to LP-WUS, for the terminal not listening to LP-WUS, for not needing to listen to LP-WUS, and for the terminal not expecting to listen to LP-WUS. Each first parameter can be configured independently without affecting each other, which makes the terminal's PDCCH listening behavior more reliable.
[0127] As an optional implementation, the terminal enabling PDCCH monitoring in the first scenario includes:
[0128] The terminal, under a first condition and in a first situation, enables PDCCH monitoring, wherein the first condition includes at least one of the following:
[0129] Condition 1: The terminal does not support simultaneous operation of the main radio (MR) and the low power radio (LR);
[0130] Condition 2: The terminal does not support simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals other than low-power signals.
[0131] It is understandable that the above-mentioned terminal does not support simultaneous operation of MR and LR, meaning that the terminal cannot use MR and LR for communication at the same time.
[0132] The transmission of the aforementioned other channels or other signals can be any channel or signal other than low-power signals, and can also be referred to as non-low-power channels or signals.
[0133] In some implementations, the transmission of other channels or signals mentioned in the embodiments of this application may be any channel or signal other than the low-power wake-up signal LP-WUS. Additionally, the low-power signal may include LP-WUS and may also include a low-power synchronization signal (LP-SS). LP-SS may also conflict or collide with LP-WUS, which may also lead to the occurrence of the first situation.
[0134] The above-mentioned "in the first case and under the first condition, enable PDCCH listening" means that PDCCH listening is enabled only when both the first case and the first condition are met. If the first condition is not met, PDCCH listening is not enabled in the first case.
[0135] In the above embodiments, by adding the aforementioned first condition, such as condition 1, PDCCH monitoring can be enabled only in the first case when the terminal does not support simultaneous operation of MR and LR, thus making PDCCH monitoring more reliable. Alternatively, as in condition 2, PDCCH monitoring can be enabled only in the first case when the terminal does not support simultaneous or parallel processing of low-power signal reception and first transmission, thus making PDCCH monitoring more reliable.
[0136] As an optional implementation, the method further includes:
[0137] If the terminal meets the second condition, and the terminal ignores the indication of the first parameter or does not follow the behavior of starting PDCCH listening in the first case if the first parameter is configured or the first parameter is configured with a definite value;
[0138] The second condition includes at least one of the following:
[0139] The terminal supports simultaneous operation of MR and LR;
[0140] The terminal supports simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals besides low-power signals.
[0141] The above-mentioned instruction to ignore the first parameter can be understood as not executing step 401, that is, not using the first parameter to start PDCCH listening in the first case. The above-mentioned terminal does not follow the behavior of starting PDCCH listening in the first case if the first parameter is configured or configured with a first parameter with a definite value. This behavior can be understood as not starting PDCCH listening in the first case, or ignoring the instruction to ignore the first parameter. Even if the terminal is configured with the first parameter or configured with a first parameter with a definite value, the terminal will not start PDCCH listening in the first case.
[0142] In the above embodiments, when the second condition is met, if the terminal ignores the indication of the first parameter or does not follow the behavior of starting PDCCH listening in the first case if the first parameter is configured or configured with a definite value, the terminal reduces the PDCCH listening behavior of the terminal to save the terminal's power consumption.
[0143] As an optional implementation, enabling PDCCH monitoring as described above includes any of the following:
[0144] Start the DRX-onDuration Timer, during which the terminal listens to the PDCCH;
[0145] Start a PDCCH listening timer triggered by LP-WUS, and the terminal listens to the PDCCH during the execution of the PDCCH listening timer.
[0146] The aforementioned drx-onDuration Timer is different from the PDCCH listener timer triggered by LP-WUS. For example, the starting positions of these two timers are determined differently. The PDCCH listener timer triggered by LP-WUS can be understood as being based on the detection of the PDCCH listener timer corresponding to the LP-WUS. It can be understood that this PDCCH listener timer is determined based on the position of the LP-WUS MO or the position of the LP-WUS MO group to which the detected LP-WUS is located.
[0147] The above-mentioned enabling of drx-onDuration Timer is applicable to terminals configured with LP-WUS option 1-1, and the above-mentioned enabling of PDCCH listening timer triggered by LP-WUS is applicable to terminals configured with LP-WUS option 1-2.
[0148] In the above implementation, different timers can be used to enable PDCCH monitoring to meet the monitoring needs of terminals with different configurations and improve compatibility.
[0149] As an optional implementation, the first situation may occur due to a conflict between the LP-WUS monitoring timing and at least one of the following:
[0150] DRX activation time;
[0151] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0152] Measurement interval;
[0153] Interruption time caused by bandwidth part (BWP) switching;
[0154] Random Access Response (RAR) time window;
[0155] The RAR time window of message B during the random access process;
[0156] The runtime of the random access conflict resolution timer;
[0157] Semi-static transmission;
[0158] Uplink time unit;
[0159] Uplink signal transmission;
[0160] Uplink channel transmission;
[0161] Measurement;
[0162] Periodic reporting of Channel State Information (CSI);
[0163] Periodic reporting of Layer 1 Reference Signal Received Power (RSRP);
[0164] The conversion time between LR and MR.
[0165] The first scenario mentioned above, arising from a conflict between the LP-WUS monitoring timing and at least one of the aforementioned factors, can be understood as the terminal determining at least one of the following due to the conflict between the LP-WUS monitoring timing and at least one of the aforementioned factors:
[0166] Cannot listen to LP-WUS;
[0167] The terminal was not listening to LP-WUS;
[0168] The terminal does not need to monitor LP-WUS;
[0169] The terminal does not expect to listen to LP-WUS.
[0170] In other words, in the aforementioned conflicts, LP-WUS has a lower transmission priority.
[0171] The conflict between the LP-WUS listening timing and at least one of the above can be a conflict between LP-WUS listening or receiving and at least one of the above. For example, if the LP-WUS listening timing conflicts with the DRX activation time, it can be replaced with a conflict between LP-WUS listening or receiving and the DRX activation time. The conflict between the LP-WUS listening timing and other objects can follow the same understanding, which will not be elaborated here.
[0172] In some implementations, the aforementioned conflict may include at least one of a conflict of time-domain resources or a conflict of frequency-domain resources, such as an overlap between the listening timing and the DRX activation time in the time domain.
[0173] In this application, "conflict" can be understood or replaced as "overlap" or "collision". In some implementations, the aforementioned overlap refers to resource overlap, which may include at least one of partial overlap and full overlap. For example, if LP-WUSMO partially conflicts with or partially overlaps with at least one of the aforementioned resources, a conflict or overlap count is recorded.
[0174] The second transmission outside the aforementioned DRX activation time may be due to a conflict or overlap between the LP-WUS monitoring timing and the time or frequency domain resources where the second transmission is located.
[0175] The aforementioned RAR time window can be a RAR time window triggered by a Beam Failure Recovery (BFR) or Scheduling Request (SR) process.
[0176] The aforementioned conflict between the P-WUS listening time and the DRX activation time, and the transmission of NR channels or signals other than low-power signals, can refer to or be replaced by the conflict during the MR activity of the terminal outside the LP-WUS listening time and the DRX activation time.
[0177] In some implementations, the transmission of channels or other signals other than low-power signals may include at least one of the following:
[0178] PDCCH monitoring outside of DRX activation time;
[0179] Outside of the DRX activation time, PDCCH monitors the corresponding Physical downlink shared channel (PDSCH) scheduling.
[0180] Listening to the PDCCH of the first search space type outside of DRX activation time.
[0181] The first search space type mentioned above can be a specific search space type, which can be a protocol agreement or a network-side device configuration. For example, other CSS besides the Type3 Common Search Space (CSS), i.e., LP-WUS listening conflicts with PDCCH listening of other CSS besides Type3 CSS.
[0182] The aforementioned semi-static transport may include semi-persistent scheduling (SPS) PDSCH or configured grant (CG) PUSCH transport.
[0183] The aforementioned uplink time unit may include uplink time slots or uplink symbols.
[0184] The aforementioned uplink signal transmission or uplink channel transmission may include at least one of the following: SR, Physical Random Access Channel (PRACH), or CG-PUSCH.
[0185] The above measurements may include at least one of the following: channel measurement, channel synchronization, synchronization measurement, radio resource management (RRM) measurement, radio link monitoring (RLM) measurement, etc.
[0186] The conversion time between LR and MR mentioned above may include the conversion time from LR to MR, or the conversion time from MR to LR.
[0187] In the above embodiments, the first situation can be determined for at least one of the above-mentioned situations, thereby enabling PDCCH monitoring to be enabled under multiple situations, so as to better save the communication latency of the terminal.
[0188] As an optional implementation, the terminal enabling PDCCH monitoring in the first scenario includes:
[0189] The terminal starts listening to the PDCCH in the first case and under the third condition.
[0190] The third condition includes at least one of the following:
[0191] The terminal experiences the first situation within the first time period;
[0192] The terminal experiences the first situation during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0193] The terminal is configured with a PDCCH listening timer triggered by LP-WUS;
[0194] The terminal is configured with an LP-WUS monitoring period greater than or equal to a preset threshold. This preset threshold can be agreed upon by the protocol or configured by the network-side device.
[0195] The terminal experiences a first situation where the time duration is greater than or equal to a first time length. The first time length can be a protocol agreement or a network-side device configuration. For example, the terminal experiences the aforementioned conflict where the time duration is greater than or equal to the first time length. It is understood that any conflict between the terminal and any of the aforementioned situations can be quantified to a certain duration. For example, if the terminal experiences a conflict or resource overlap with the DRX activation time that is greater than or equal to the first time length, the terminal will start listening to the PDCCH.
[0196] In one embodiment, the third condition and the first condition can be satisfied simultaneously. For example, in the first case, the terminal starts listening to the PDCCH when both the first and third conditions are met. Alternatively, they can be used separately, meaning the third condition and the first condition are not satisfied at the same time. For example, if only the first or third condition is met, listening to the PDCCH is started in the first case, or neither the first nor the third condition is considered.
[0197] The first time period mentioned above may include one or more DRX cycles, which may be agreed upon by the protocol or configured by the network-side device.
[0198] The above-mentioned terminal may start PDCCH listening only when the first situation occurs within the first time period. If the first situation does not occur within the first time period, PDCCH listening may not be started.
[0199] The occurrence of the first situation during X consecutive LP-WUS monitoring times can be either the occurrence of the first situation during all X consecutive LP-WUS monitoring times or the occurrence of the first situation during more than X consecutive LP-WUS monitoring times, as described in at least one of the conflicts described in the above implementation.
[0200] The terminal is configured with a PDCCH listening timer triggered by LP-WUS, which can be understood as the terminal being configured with LP-WUS option 1-2 scheme.
[0201] In the above embodiments, the third condition can limit the behavior of enabling PDCCH monitoring in the first case, so that the terminal's enabling PDCCH monitoring is more reliable and can also save the terminal's power consumption.
[0202] In some implementations, when the third condition includes the occurrence of the first situation by the terminal within a first time period, enabling PDCCH monitoring includes:
[0203] Start listening to PDCCH at or after the end of the first time period.
[0204] The following are examples of PDCCH monitoring that begins at or after the end of the first time period:
[0205] PDCCH listening is started at the end of the first time period, meaning PDCCH listening begins immediately upon the end of the first time period to ensure more timely PDCCH monitoring; or,
[0206] Start listening to the PDCCH after the first time period ends. For example, start listening to the PDCCH at the end of a specific time interval starting from the end of the first time period.
[0207] In some implementations, the terminal starts listening to the PDCCH at or after the end of the first time period, including:
[0208] The terminal starts listening to the PDCCH at the beginning of the DRX cycle n+1.
[0209] The first time period includes the time period in which DRX cycle n is located, the terminal experiences the first situation within the time period in which DRX cycle n is located, and DRX cycle n+1 represents the next DRX cycle of DRX cycle n.
[0210] In some implementations, if the terminal experiences a first event during the time period of the DRX cycle n, the terminal will start listening to the PDCCH at the beginning of the DRX cycle n+1.
[0211] In this implementation, PDCCH monitoring can be enabled in the next DRX cycle to save terminal power consumption.
[0212] It should be noted that the first time period in this application embodiment is not limited to the DRX period, but can also be a newly defined time period or time domain resource in the protocol, and there is no limitation on this.
[0213] As an optional implementation, under the fourth condition, the terminal does not enable PDCCH monitoring in the first condition, and the fourth condition includes at least one of the following:
[0214] The first situation did not occur within the first time period; or, the first situation did not occur within the first time period.
[0215] The terminal does not satisfy the condition that the first condition occurs during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0216] The terminal was not configured with a PDCCH listening timer triggered by LP-WUS;
[0217] The terminal is configured to monitor LP-WUS for a period of less than a preset threshold.
[0218] In the above implementation, limiting PDCCH monitoring to not be enabled in the first case by the fourth condition helps to save terminal power consumption.
[0219] In this embodiment, if the terminal is configured with a first parameter or a first parameter with a definite value, the terminal enables PDCCH listening in the first case. This allows the terminal to listen to the PDCCH sent by the network-side device in a timely manner, thereby enabling the terminal to be woken up by the network-side device in a timely manner, thus reducing the communication transmission latency of the terminal. Furthermore, the first parameter ensures that the terminal and the network-side device have a consistent understanding of enabling PDCCH listening in the first case, which can improve the transmission performance between the terminal and the network-side device.
[0220] Please see Figure 5 , Figure 5 This is a flowchart of a monitoring configuration method provided in an embodiment of this application, such as... Figure 5 As shown, it includes the following steps:
[0221] Step 501: The network-side device sends configuration information to the terminal. The configuration information may carry a first parameter. The first parameter or the first parameter that is affirmatively taken is used by the terminal to enable PDCCH listening in the first case.
[0222] The first case includes at least one of the following:
[0223] Cannot listen to the low-power wake-up signal LP-WUS;
[0224] LP-WUS not being monitored;
[0225] No need to monitor LP-WUS;
[0226] I do not expect to monitor LP-WUS.
[0227] Optionally, the occurrence of the first situation may be due to a conflict between the timing of LP-WUS monitoring and at least one of the following:
[0228] DRX activation time;
[0229] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0230] Measurement interval;
[0231] Interruption time caused by BWP switching in the bandwidth section;
[0232] Random access response RAR time window;
[0233] The RAR time window of message B during the random access process;
[0234] The runtime of the random access conflict resolution timer;
[0235] Semi-static transmission;
[0236] Uplink time unit;
[0237] Uplink signal transmission;
[0238] Uplink channel transmission;
[0239] Measurement;
[0240] Periodic Channel State Information (CSI) reporting;
[0241] Periodic Layer 1 Reference Signal Received Power (RSRP) reporting;
[0242] The conversion time between LR and MR.
[0243] It should be noted that this embodiment is used as a reference for... Figure 4 The implementation methods of the network-side devices shown in the embodiments can be found in the following examples. Figure 4 To avoid repetition, the relevant descriptions of the embodiments shown will not be repeated in this embodiment.
[0244] The methods provided in the embodiments of this application are illustrated below through multiple examples:
[0245] In one embodiment provided in this application, if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, and the terminal cannot listen to LP-WUS, the terminal starts a PDCCH listening timer triggered by LP-WUS.
[0246] It should be noted that the terminal listens to LP-WUS at the designated LP-WUS listening time based on the LP-WUS configuration information. In other words, the terminal's inability to listen to LP-WUS means it cannot listen to the LP-WUS listening time, or that it cannot listen to LP-WUS at the designated LP-WUS listening time. Other cases can be understood in the same way.
[0247] It should be noted that the terminal activating the PDCCH listening timer triggered by LP-WUS means that the terminal is configured with the PDCCH listening timer triggered by LP-WUS.
[0248] In one embodiment provided in this application, if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, and the LP-WUS listening time period configured for the terminal is greater than or equal to a preset threshold, the terminal starts a PDCCH listening timer triggered by LP-WUS when the terminal cannot listen to LP-WUS.
[0249] The preset threshold is determined by the protocol or configured by the network-side device. For example, the first value is 80ms or 160ms. Optionally, the preset threshold is less than or equal to the DRX period.
[0250] In another embodiment provided in this application, regardless of whether the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, if the LP-WUS listening time period configured for the terminal is less than or equal to a preset threshold, the terminal will not start the PDCCH listening timer triggered by LP-WUS when it cannot listen to LP-WUS.
[0251] In another embodiment provided in this application, if the terminal is configured with a first parameter or a first parameter with a definite value, and the terminal cannot listen to LP-WUS, the terminal starts a DRX start duration timer. In this embodiment, the terminal is not configured with a PDCCH listening timer triggered by LP-WUS.
[0252] In some implementations, the network-side device determines whether to configure the first parameter based on the implementation.
[0253] In another embodiment provided in this application, if the terminal is configured with a first parameter or configured with a first parameter that has a definite value, and if the terminal capability does not support simultaneous operation of MR and LR, the terminal enables PDCCH monitoring in the first case; or, if the terminal is configured with a first parameter or configured with a first parameter that has a definite value, and if the terminal capability does not support simultaneous or parallel processing of low-power signal reception and transmission of other NR channels or signals, the terminal enables PDCCH monitoring in the first case.
[0254] In another embodiment, if the terminal capability supports simultaneous or parallel processing of low-power signal reception and other NR channel / signal transmission, the terminal ignores the first parameter, or the terminal does not follow the behavior of enabling PDCCH monitoring in the first case; or, if the terminal capability does not support simultaneous operation of MR and LR, the terminal ignores the first parameter, or the terminal does not follow the behavior of enabling PDCCH monitoring in the first case.
[0255] In some embodiments, this is independent of whether the terminal is configured with the first parameter. For example, if the terminal capability does not support simultaneous operation of MR and LR, the terminal enables PDCCH listening in the first case; or, if the terminal capability does not support simultaneous or parallel processing of low-power signal reception and transmission of other NR channels or signals, the terminal enables PDCCH listening in the first case.
[0256] In another embodiment provided in this application, it is assumed that the first type of terminal supports a low-power wake-up receiver (LP-WUR) based on sequence detection (also known as OFDM-based LP-WUR), and the second type of terminal supports envelope detection LP-WUR based on on-off keying (OOK) (also known as OOK-based LP-WUR).
[0257] In some implementations, if the network-side device provides a second parameter X for a first type of terminal to determine the duration of LP-WUS monitoring, and the network-side device provides a third parameter Y for a second type of terminal to determine the duration of LP-WUS monitoring, where Y ≥ X, the first type of terminal and the second type of terminal determine the start and length of the LP-WUS MO based on the third parameter Y. If the network only provides the second parameter X, the first type of terminal determines the start and length of the LP-WUS MO based on the first parameter X. If the network-side device only provides the third parameter Y, the second type of terminal determines the start and length of the LP-WUS MO based on the third parameter Y; optionally, the first type of terminal also determines the start and length of the LP-WUS MO based on the third parameter Y.
[0258] In some implementations, the length of the LP-WUS MO determined according to the third parameter Y is the actual length of the LP-WUS MO. Figure 1 For example, Y is the length of all time-domain resources in each MO except for time-domain resources that cannot be used in LP-WUS.
[0259] In some implementations, X is configured by the network as N1 OFDM symbols or M1 chips, and Y is configured by the network as N2 OFDM symbols or M2 chips. Alternatively, X is determined by the number of codepoints (or the number of information bits) configured by the network and the number of candidate OFDM sequences in one OOK ON chip, and is also determined according to the number of repetitions configured by the network. Y is determined by the coding block length configured by the network, or the number of chips corresponding to the coding block, or the number of OFDM symbols corresponding to the coding block.
[0260] The terminal determines the length for monitoring the LP-WUS in the LP-WUS MO according to the second parameter X. Optionally, the terminal may also perform blind detection of the LP-WUS in the LP-WUS MO according to the LP-WUS signal length determined by the second parameter X and the third parameter. For example, Figure 6a wherein, in MO#2, the LP-WUS sent by the network is used to wake up both the first-type and second-type terminals, and the length of the sent LP-WUS is Y. The length for the first-type terminal to monitor the WUS is X, where X<Y. The length for the second-type terminal to monitor the WUS is Y. In MO#1, the LP-WUS sent by the network is only used to wake up the first-type terminal, and the length of the sent LP-WUS is X. The length for the first-type terminal to monitor the WUS is X, where X<Y. The length for the second-type terminal to monitor the WUS is Y. The second-type terminal may not correctly demodulate the LP-WUS.
[0261] In some implementations, the second parameter X may be used by the first-type terminal to determine whether an LP-WUS is a valid MO. If in a nominal MO, the length of time resources available for LP-WUS transmission is less than X, the first-type terminal determines that the MO is an invalid MO. The third parameter Y may be used by the second-type terminal to determine whether an LP-WUS is a valid MO. If in a nominal MO, the length of time resources available for LP-WUS transmission is less than Y, the second-type terminal determines that the MO is an invalid MO. If an MO is an invalid MO, the MO is dropped. The dropped MO will not be postponed to the next MO. It is not difficult to see that for the same nominal MO, for different terminal types, this MO may be an invalid MO for one terminal type and a valid MO for another terminal type. To avoid different terminal types making different judgments on the validity of the same MO, which affects subsequent MOs, for example, affecting the SSB beam or QCL assumption associated with the MO, it is reasonable to drop the invalid MO.
[0262] Figure 6bHere's an example. A network configures an LP-WUS Occasion (LO) consisting of 4 MOs. The network provides a second parameter X = 4 OFDM symbols, Y = 6 OFDM symbols, and a fourth parameter Z = 8 OFDM symbols to determine the nominal length of the LP-WUS MO. In MO#1, the available resources for LP-WUS transmission are 4 OFDM symbols, equal to X but less than Y. Therefore, for a first-type terminal, MO#1 is a valid MO, and the first-type terminal listens for LP-WUS in MO#1 according to X. For a second-type terminal, MO#1 is an invalid MO, and the second-type terminal does not listen for LP-WUS in MO#1; this MO is considered discarded. In this MO, the network can send LP-WUS to wake up the first-type terminal; the LP-WUS length is 4 OFDM symbols. In MO#2, the available resources for LP-WUS transmission are 8 OFDM symbols, and it is a valid MO for both types of terminals. The LP-WUS transmitted by the network is used to simultaneously wake up both Type 1 and Type 2 terminals. The length of the transmitted LP-WUS is Y = 6 OFDM symbols. In MO#3, 8 OFDM symbols are available for LP-WUS transmission, which are valid MOs for both types of terminals. The LP-WUS transmitted by the network is used to wake up Type 1 terminals, and the length of the transmitted LP-WUS is X = 4 OFDM symbols. In MO#4, 3 OFDM symbols are available for LP-WUS transmission, which are invalid MOs for both types of terminals. Invalid MOs are discarded and not postponed.
[0263] In some implementations, the second parameter X can be used by a first-type terminal to determine whether an LP-WUS is a valid MO. If, in a nominal MO, the interval between the start and end points of a first time resource available for LP-WUS transmission is greater than the fifth parameter Z1, the first-type terminal determines that the MO is an invalid MO. The length of the first time resource is determined according to the second parameter X. If, in a nominal MO, the interval between the start and end points of a second time resource available for LP-WUS transmission is greater than the fifth parameter Z1, the second-type terminal determines that the MO is an invalid MO. The length of the second time resource is determined according to the third parameter Y.
[0264] by Figure 6aTaking MO#1 as an example, the first time resource consists of OFDM symbols 1, 2, 5, and 6, and the second time resource consists of OFDM symbols 1, 2, 5, 6, 7, and 8. Assuming the fifth parameter Z1 = 6, if the interval between the start and end points of the first time resource is less than 6 OFDM symbols, the first type of terminal determines that the MO is valid. However, if the interval between the start and end points of the second time resource is greater than 6 OFDM symbols, the second type of terminal determines that the MO is invalid.
[0265] The monitoring activation method provided in this application can be executed by a monitoring activation device. This application uses the example of a monitoring activation device executing the monitoring activation method to illustrate the monitoring activation device provided in this application.
[0266] The monitoring configuration method provided in this application can be executed by a monitoring configuration device. This application uses the example of a monitoring configuration device executing the monitoring configuration method to illustrate the monitoring configuration device provided in this application.
[0267] This application provides a listening-on device. As an example, the listening-on device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. For example, the terminal can be of the type listed above (including but not limited to terminal 11), and the network-side device can be of the type listed above (including but not limited to network-side device 12). This application does not impose specific limitations.
[0268] This application provides a monitoring configuration device. As an example, the monitoring configuration device can be a communication device or a component within 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.
[0269] The monitoring activation device or monitoring configuration 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.
[0270] For details, see Figure 7 When the listening activation device is a terminal or a component within a terminal, the listening activation device 700 includes:
[0271] The processing module 701 is used to enable the monitoring of the physical downlink control channel (PDCCH) in the first case if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value.
[0272] The first case includes at least one of the following:
[0273] The terminal cannot listen to the low-power wake-up signal LP-WUS;
[0274] The terminal was not listening to LP-WUS;
[0275] The terminal does not need to monitor LP-WUS;
[0276] The terminal does not expect to listen to LP-WUS.
[0277] Optionally, the device further includes:
[0278] The receiving module is used to receive configuration information sent by the network-side device, and the configuration information may carry the first parameter.
[0279] Optionally, the processing module 701 is configured to enable PDCCH listening in a first case, provided that a first condition is met, wherein the first condition includes at least one of the following:
[0280] The terminal does not support simultaneous operation of the main receiver (MR) and the low-power receiver (LR).
[0281] The terminal does not support simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals other than low-power signals.
[0282] Optionally, the processing module 701 is further configured to ignore the indication of the first parameter or not follow the behavior of the terminal starting PDCCH listening in the first case if the terminal is configured with the first parameter or the first parameter is configured with a definite value when the second condition is met.
[0283] The second condition includes at least one of the following:
[0284] The terminal supports simultaneous operation of MR and LR;
[0285] The terminal supports simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals besides low-power signals.
[0286] Optionally, enabling PDCCH monitoring includes any of the following:
[0287] Start a discontinuous reception DRX enable duration timer, during which the terminal listens to the PDCCH;
[0288] Start a PDCCH listening timer triggered by LP-WUS, and the terminal listens to the PDCCH during the execution of the PDCCH listening timer.
[0289] Optionally, the occurrence of the first situation may be due to a conflict between the timing of LP-WUS monitoring and at least one of the following:
[0290] DRX activation time;
[0291] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0292] Measurement interval;
[0293] Interruption time caused by BWP switching in the bandwidth section;
[0294] Random access response RAR time window;
[0295] The RAR time window of message B during the random access process;
[0296] The runtime of the random access conflict resolution timer;
[0297] Semi-static transmission;
[0298] Uplink time unit;
[0299] Uplink signal transmission;
[0300] Uplink channel transmission;
[0301] Measurement;
[0302] Periodic Channel State Information (CSI) reporting;
[0303] Periodic Layer 1 Reference Signal Received Power (RSRP) reporting;
[0304] The conversion time between LR and MR.
[0305] Optionally, the processing module 701 is used to enable PDCCH listening in the first case and when the third condition is met;
[0306] The third condition includes at least one of the following:
[0307] The terminal experiences the first situation within the first time period;
[0308] The terminal experiences the first situation during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0309] The terminal is configured with a PDCCH listening timer triggered by LP-WUS;
[0310] The terminal is configured with an LP-WUS monitoring period greater than or equal to a preset threshold.
[0311] The terminal experiences a first situation where the time length is greater than or equal to the first time length.
[0312] Optionally, the third condition includes the situation where the terminal experiences the first condition within a first time period, and enabling PDCCH monitoring includes:
[0313] Start listening to PDCCH at or after the end of the first time period.
[0314] Optionally, starting PDCCH monitoring at or after the end of the first time period includes:
[0315] Start listening to PDCCH at the beginning of DRX cycle n+1;
[0316] The first time period includes the time period in which DRX cycle n is located, the terminal experiences the first situation within the time period in which DRX cycle n is located, and DRX cycle n+1 represents the next DRX cycle of DRX cycle n.
[0317] Optionally, under the fourth condition, the terminal does not enable PDCCH monitoring in the first condition, and the fourth condition includes at least one of the following:
[0318] The first situation did not occur within the first time period;
[0319] The terminal does not satisfy the condition that the first condition occurs during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0320] The terminal was not configured with a PDCCH listening timer triggered by LP-WUS;
[0321] The terminal is configured to monitor LP-WUS for a period of less than a preset threshold.
[0322] The aforementioned monitoring activation device can reduce the communication latency of the terminal.
[0323] The listening activation device provided in this application embodiment can achieve... Figure 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.
[0324] See Figure 8 When the monitoring configuration device is a network-side device or a component within a network-side device, the monitoring configuration device 800 includes:
[0325] The sending module 801 is used to send configuration information to the terminal. The configuration information may carry a first parameter. The first parameter or the first parameter that is affirmatively taken is used by the terminal to enable PDCCH listening in a first situation.
[0326] The first case includes at least one of the following:
[0327] Cannot listen to the low-power wake-up signal LP-WUS;
[0328] LP-WUS not being monitored;
[0329] No need to monitor LP-WUS;
[0330] I do not expect to monitor LP-WUS.
[0331] Optionally, the occurrence of the first situation may be due to a conflict between the timing of LP-WUS monitoring and at least one of the following:
[0332] DRX activation time;
[0333] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0334] Measurement interval;
[0335] Interruption time caused by BWP switching in the bandwidth section;
[0336] Random access response RAR time window;
[0337] The RAR time window of message B during the random access process;
[0338] The runtime of the random access conflict resolution timer;
[0339] Semi-static transmission;
[0340] Uplink time unit;
[0341] Uplink signal transmission;
[0342] Uplink channel transmission;
[0343] Measurement;
[0344] Periodic Channel State Information (CSI) reporting;
[0345] Periodic Layer 1 Reference Signal Received Power (RSRP) reporting;
[0346] The conversion time between LR and MR.
[0347] The aforementioned monitoring configuration device can reduce the communication latency of the terminal.
[0348] The monitoring configuration device provided in this application embodiment can achieve... Figure 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.
[0349] like Figure 9 As shown in the illustration, this application also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores programs or instructions that can run on the processor 901. For example, when the communication device 900 is a terminal, the program or instructions executed by the processor 901 implement the various steps of the above-described listening activation method embodiment and achieve the same technical effect. When the communication device 900 is a network-side device, the program or instructions executed by the processor 901 implement the various steps of the above-described listening configuration method embodiment and achieve the same technical effect. To avoid repetition, further details are omitted here.
[0350] This application embodiment 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, for example... Figure 4 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 7 The monitoring activation device is shown. Specifically, Figure 10 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.
[0351] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.
[0352] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 10 The terminal structure shown 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.
[0353] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processor 10041 and a microphone 10042. The graphics processor 10041 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 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 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.
[0354] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1001 can transmit it to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
[0355] The memory 1009 can be used to store software programs or instructions, as well as various data. The memory 1009 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 1009 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 1009 in this embodiment includes, but is not limited to, these and any other suitable types of memory.
[0356] The processor 1010 may include one or more processing units; optionally, the processor 1010 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 the processor 1010.
[0357] The processor 1010 is used to enable the terminal to listen to the physical downlink control channel (PDCCH) in the first case if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value.
[0358] The first case includes at least one of the following:
[0359] The terminal cannot listen to the low-power wake-up signal LP-WUS;
[0360] The terminal was not listening to LP-WUS;
[0361] The terminal does not need to monitor LP-WUS;
[0362] The terminal does not expect to listen to LP-WUS.
[0363] Optionally, the radio frequency unit 1001 is used to receive configuration information sent by the network-side device, the configuration information carrying the first parameter.
[0364] Optionally, enabling PDCCH monitoring in the first case includes:
[0365] In the first case, and under the first condition, PDCCH listening is enabled, wherein the first condition includes at least one of the following:
[0366] The terminal does not support simultaneous operation of the main receiver (MR) and the low-power receiver (LR).
[0367] The terminal does not support simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals other than low-power signals.
[0368] Optionally, the processor 1010 is also used for:
[0369] If the terminal meets the second condition, it ignores the indication of the first parameter or does not follow the behavior of starting PDCCH listening if the first parameter is configured or if the first parameter is configured with a definite value.
[0370] The second condition includes at least one of the following:
[0371] The terminal supports simultaneous operation of MR and LR;
[0372] The terminal supports simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals besides low-power signals.
[0373] Optionally, enabling PDCCH monitoring includes any of the following:
[0374] Start a discontinuous reception DRX enable duration timer, during which the terminal listens to the PDCCH;
[0375] Start a PDCCH listening timer triggered by LP-WUS, and the terminal listens to the PDCCH during the execution of the PDCCH listening timer.
[0376] Optionally, the occurrence of the first situation may be due to a conflict between the timing of LP-WUS monitoring and at least one of the following:
[0377] DRX activation time;
[0378] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0379] Measurement interval;
[0380] Interruption time caused by BWP switching in the bandwidth section;
[0381] Random access response RAR time window;
[0382] The RAR time window of message B during the random access process;
[0383] The runtime of the random access conflict resolution timer;
[0384] Semi-static transmission;
[0385] Uplink time unit;
[0386] Uplink signal transmission;
[0387] Uplink channel transmission;
[0388] Measurement;
[0389] Periodic Channel State Information (CSI) reporting;
[0390] Periodic Layer 1 Reference Signal Received Power (RSRP) reporting;
[0391] The conversion time between LR and MR.
[0392] Optionally, enabling PDCCH monitoring in the first case includes:
[0393] In the first case, and if the third condition is met, enable PDCCH listening;
[0394] The third condition includes at least one of the following:
[0395] The terminal experiences the first situation within the first time period;
[0396] The terminal experiences the first situation during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0397] The terminal is configured with a PDCCH listening timer triggered by LP-WUS;
[0398] The terminal is configured with an LP-WUS monitoring period greater than or equal to a preset threshold.
[0399] The terminal experiences a first situation where the time length is greater than or equal to the first time length.
[0400] Optionally, if the third condition includes the occurrence of the first situation by the terminal within the first time period, enabling PDCCH monitoring includes:
[0401] Start listening to PDCCH at or after the end of the first time period.
[0402] Optionally, starting PDCCH monitoring at or after the end of the first time period includes:
[0403] Start listening to PDCCH at the beginning of DRX cycle n+1;
[0404] The first time period includes the time period in which DRX cycle n is located, the terminal experiences the first situation within the time period in which DRX cycle n is located, and DRX cycle n+1 represents the next DRX cycle of DRX cycle n.
[0405] Optionally, under the fourth condition, the terminal does not enable PDCCH monitoring in the first condition, and the fourth condition includes at least one of the following:
[0406] The first situation did not occur within the first time period;
[0407] The terminal does not satisfy the condition that the first condition occurs during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1;
[0408] The terminal was not configured with a PDCCH listening timer triggered by LP-WUS;
[0409] The terminal is configured to monitor LP-WUS for a period of less than a preset threshold.
[0410] The aforementioned terminals can reduce communication latency.
[0411] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be described again here.
[0412] This application embodiment also provides a network-side device, 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, for example... Figure 5 The steps of the method embodiment shown are illustrated. 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.
[0413] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 8 The monitoring configuration device is shown. (As shown in the image.) Figure 11 As shown, the network-side device 1100 includes: an antenna 1101, a radio frequency (RF) device 1102, a baseband device 1103, a processor 1104, and a memory 1105. The antenna 1101 is connected to the RF device 1102. In the uplink direction, the RF device 1102 receives information through the antenna 1101 and transmits the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be transmitted and sends it to the RF device 1102. The RF device 1102 processes the received information and transmits it through the antenna 1101.
[0414] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1103, which includes a baseband processor.
[0415] The baseband device 1103 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 11 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1105 via a bus interface to call the program or instructions in the memory 1105 to execute the network-side device operation shown in the above method embodiment.
[0416] The network-side device may also include a network interface 1106, such as a Common Public Radio Interface (CPRI).
[0417] The radio frequency device 1102 is used to send configuration information to the terminal. The configuration information may carry a first parameter. The first parameter or the first parameter that is affirmatively taken is used by the terminal to enable PDCCH monitoring in a first situation.
[0418] The first case includes at least one of the following:
[0419] Cannot listen to the low-power wake-up signal LP-WUS;
[0420] LP-WUS not being monitored;
[0421] No need to monitor LP-WUS;
[0422] I do not expect to monitor LP-WUS.
[0423] Optionally, the occurrence of the first situation may be due to a conflict between the timing of LP-WUS monitoring and at least one of the following:
[0424] DRX activation time;
[0425] A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals;
[0426] Measurement interval;
[0427] Interruption time caused by BWP switching in the bandwidth section;
[0428] Random access response RAR time window;
[0429] The RAR time window of message B during the random access process;
[0430] The runtime of the random access conflict resolution timer;
[0431] Semi-static transmission;
[0432] Uplink time unit;
[0433] Uplink signal transmission;
[0434] Uplink channel transmission;
[0435] Measurement;
[0436] Periodic Channel State Information (CSI) reporting;
[0437] Periodic Layer 1 Reference Signal Received Power (RSRP) reporting;
[0438] The conversion time between LR and MR.
[0439] The aforementioned network-side equipment can reduce the communication latency of the terminal.
[0440] Furthermore, the network-side device 1100 in this embodiment of the application also includes: a program or instructions stored in memory 1105 and executable on processor 1104, wherein processor 1104 calls the program or instructions in memory 1105 to execute. Figure 8 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.
[0441] 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 listening start method or listening configuration method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0442] 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.
[0443] 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 monitoring start method or monitoring configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0444] 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.
[0445] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described listening start method or listening configuration method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0446] This application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the listening activation method described above, and the network-side device can be used to perform the steps of the listening configuration method described above.
[0447] 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.
[0448] 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 the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.
[0449] 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 enabling monitoring, characterized in that, include: If the terminal is configured with a first parameter or is configured with a first parameter that has a definite value, then the terminal starts listening to the Physical Downlink Control Channel (PDCCH) in the first case. The first case includes at least one of the following: The terminal cannot listen to the low-power wake-up signal LP-WUS; The terminal was not listening to LP-WUS; The terminal does not need to monitor LP-WUS; The terminal does not expect to listen to LP-WUS.
2. The method of claim 1, wherein, The method further includes: The terminal receives configuration information sent by the network-side device, and the configuration information may carry the first parameter.
3. The method according to claim 1 or 2, characterized in that, The terminal enabling PDCCH monitoring in the first scenario includes: The terminal, under a first condition and in a first situation, enables PDCCH monitoring, wherein the first condition includes at least one of the following: The terminal does not support simultaneous operation of the main receiver (MR) and the low-power receiver (LR). The terminal does not support simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals other than low-power signals.
4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the terminal meets the second condition, and the terminal ignores the indication of the first parameter or does not follow the behavior of starting PDCCH listening in the first case if the first parameter is configured or the first parameter is configured with a definite value; The second condition includes at least one of the following: The terminal supports simultaneous operation of MR and LR; The terminal supports simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals besides low-power signals.
5. The method according to any one of claims 1 to 4, characterized in that, Enabling PDCCH monitoring includes any of the following: Start a discontinuous reception DRX enable duration timer, during which the terminal listens to the PDCCH; Start a PDCCH listening timer triggered by LP-WUS, and the terminal listens to the PDCCH during the execution of the PDCCH listening timer.
6. The method according to any one of claims 1 to 5, characterized in that, The first situation may occur if the timing of LP-WUS monitoring conflicts with at least one of the following: DRX activation time; A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals; Measurement interval; Interruption time caused by BWP switching in the bandwidth section; Random access response RAR time window; The RAR time window of message B during the random access process; The runtime of the random access conflict resolution timer; Semi-static transmission; Uplink time unit; Uplink signal transmission; Uplink channel transmission; Measurement; Periodic Channel State Information (CSI) reporting; Periodic Layer 1 Reference Signal Received Power (RSRP) reporting; The conversion time between LR and MR.
7. The method according to any one of claims 1 to 6, characterized in that, The terminal enabling PDCCH monitoring in the first scenario includes: The terminal starts listening to the PDCCH in the first case and under the third condition. The third condition includes at least one of the following: The terminal experiences the first situation within the first time period; The terminal experiences the first situation during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1; The terminal is configured with a PDCCH listening timer triggered by LP-WUS; The terminal is configured with an LP-WUS monitoring period greater than or equal to a preset threshold. The terminal experiences a first situation where the time length is greater than or equal to the first time length.
8. The method of claim 7, wherein, When the third condition includes the occurrence of the first situation within the first time period, enabling PDCCH monitoring includes: Start listening to PDCCH at or after the end of the first time period.
9. The method of claim 8, wherein, The step of starting PDCCH monitoring at or after the end of the first time period includes: Start listening to PDCCH at the beginning of DRX cycle n+1; The first time period includes the time period in which DRX cycle n is located, the terminal experiences the first situation within the time period in which DRX cycle n is located, and DRX cycle n+1 represents the next DRX cycle of DRX cycle n.
10. The method according to any one of claims 1 to 9, characterized in that, Under the fourth condition, the terminal does not enable PDCCH monitoring under the first condition. The fourth condition includes at least one of the following: The first situation did not occur within the first time period; The terminal does not satisfy the condition that the first condition occurs during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1; The terminal was not configured with a PDCCH listening timer triggered by LP-WUS; The terminal is configured to monitor LP-WUS for a period of less than a preset threshold.
11. A method of configuring a snoop filter, the method comprising: include: The network-side device sends configuration information to the terminal. The configuration information may carry a first parameter. The first parameter, or the first parameter that is affirmatively taken, is used by the terminal to enable the listening of the physical downlink control channel (PDCCH) in a first situation. The first case includes at least one of the following: Cannot listen to the low-power wake-up signal LP-WUS; LP-WUS not being monitored; No need to monitor LP-WUS; I do not expect to monitor LP-WUS.
12. The method of claim 11, wherein, The first situation may occur if the timing of LP-WUS monitoring conflicts with at least one of the following: DRX activation time; A second transmission outside of the DRX activation time, the second transmission including transmissions of other channels or other signals besides low-power signals; Measurement interval; Interruption time caused by BWP switching in the bandwidth section; Random access response RAR time window; The RAR time window of message B during the random access process; The runtime of the random access conflict resolution timer; Semi-static transmission; Uplink time unit; Uplink signal transmission; Uplink channel transmission; Measurement; Periodic Channel State Information (CSI) reporting; Periodic Layer 1 Reference Signal Received Power (RSRP) reporting; The conversion time between LR and MR.
13. A listening-on device, characterized by include: The processing module is used to enable the monitoring of the physical downlink control channel (PDCCH) in the first case if the terminal is configured with a first parameter or is configured with a first parameter that has a definite value. The first case includes at least one of the following: The terminal cannot listen to the low-power wake-up signal LP-WUS; The terminal was not listening to LP-WUS; The terminal does not need to monitor LP-WUS; The terminal does not expect to listen to LP-WUS.
14. The apparatus of claim 13, wherein, The device further includes: The receiving module is used to receive configuration information sent by the network-side device, and the configuration information may carry the first parameter.
15. The apparatus of claim 13 or 14, wherein, The processing module is used to enable PDCCH monitoring in a first situation, and under a first condition, wherein the first condition includes at least one of the following: The terminal does not support simultaneous operation of the main receiver (MR) and the low-power receiver (LR). The terminal does not support simultaneous or parallel processing of the reception of low-power signals and the first transmission, the first transmission including the transmission of other channels or other signals other than low-power signals.
16. The apparatus according to any one of claims 13 to 15, characterized in that, The processing module is used to enable PDCCH monitoring in the first case and when the third condition is met. The third condition includes at least one of the following: The terminal experiences the first situation within the first time period; The terminal experiences the first situation during X consecutive LP-WUS listening times, where X is an integer greater than or equal to 1; The terminal is configured with a PDCCH listening timer triggered by LP-WUS; The terminal is configured with an LP-WUS monitoring period greater than or equal to a preset threshold. The terminal experiences a first situation where the time length is greater than or equal to the first time length.
17. A monitoring configuration device, characterized in that, include: The sending module is used to send configuration information to the terminal. The configuration information may carry a first parameter. The first parameter or the first parameter that is affirmatively taken is used by the terminal to enable PDCCH listening in a first situation. The first case includes at least one of the following: Cannot listen to the low-power wake-up signal LP-WUS; LP-WUS not being monitored; No need to monitor LP-WUS; I do not expect to monitor LP-WUS.
18. A terminal, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the listening start method as described in any one of claims 1 to 10.
19. A network-side device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the listening configuration method as described in claim 11 or 12.
20. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the listening start method as described in any one of claims 1 to 10, or the steps of the listening configuration method as described in claim 11 or 12.
21. A computer program product, characterized in that, The computer program product is stored in a storage medium and is executed by at least one processor to implement the steps of the listening activation method as described in any one of claims 1 to 10, or to implement the steps of the listening configuration method as described in claim 11 or 12.
