Transmission processing method and device, terminal and network side equipment

Abstract

The invention discloses a transmission processing method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the transmission processing method comprises the steps that under the condition that the terminal is configured with wakeup signal WUS monitoring, the terminal executes a first operation, the first operation comprises at least one of the following items: under the condition that the terminal is not configured to use downlink control information (DCP) scrambled by an energy-saving radio network temporary identifier, determining a first monitoring behavior of the WUS based on configuration information of discontinuous reception (DRX); and under the condition that the terminal is configured with the DCP, determining at least one of a second monitoring behavior of the WUS based on the monitoring condition of the DCP and a third monitoring behavior of the DCP based on the monitoring result of the WUS.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a transmission processing method, apparatus, terminal and network side equipment. Background Art

[0002] With the development of communication technology, mobile communication terminals introduce low power wake up radio (LP-WUR) to receive low power signals (low power signal), so that the main communication module is in a closed or ultra-deep sleep state, which can effectively reduce the power consumption of the terminal. The low power signal can also be called a low power wake up signal (LP-WUS) or a wake-up signal. However, there are currently energy-saving mechanisms such as discontinuous reception (DRX) and downlink control information scrambled by PS-RNTI (DCI with CRC Scrambled by PS-RNTI, DCP). Therefore, after the introduction of WUS, how to use it in combination with related energy-saving mechanisms has become an urgent problem to be solved. Summary of the invention

[0003] The embodiments of the present application provide a transmission processing method, apparatus, terminal and network-side equipment, which can solve the problem of how to combine with related energy-saving mechanisms after the introduction of WUS.

[0004] In a first aspect, a transmission processing method is provided, comprising:

[0005] When the terminal is configured with the wake-up signal WUS monitoring, the terminal performs a first operation, where the first operation includes at least one of the following:

[0006] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0007] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0008] In a second aspect, a transmission processing method is provided, including:

[0009] The network-side device performs a second operation, where the second operation includes any one of the following:

[0010] The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured;

[0011] Configure WUS configuration information for the terminal, but do not configure DCP;

[0012] Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS;

[0013] Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP;

[0014] The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

[0015] In a third aspect, a transmission processing device is provided, including:

[0016] The first execution module is configured to execute a first operation when the terminal is configured with the wake-up signal WUS monitoring, wherein the first operation includes at least one of the following:

[0017] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0018] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0019] In a fourth aspect, a transmission processing device is provided, including:

[0020] The second execution module is configured to execute a second operation, where the second operation includes any one of the following:

[0021] The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured;

[0022] Configure WUS configuration information for the terminal, but do not configure DCP;

[0023] Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS;

[0024] Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP;

[0025] The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

[0026] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0027] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to perform a first operation when the terminal is configured with a wake-up signal WUS monitoring, and the first operation includes at least one of the following:

[0028] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0029] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0030] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0031] In an eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to perform a second operation, and the second operation includes any one of the following:

[0032] The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured;

[0033] Configure WUS configuration information for the terminal, but do not configure DCP;

[0034] Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS;

[0035] Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP;

[0036] The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

[0037] In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0038] In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0039] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.

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

[0041] In the embodiment of the present application, when the terminal is configured with the wake-up signal WUS monitoring, the terminal performs the first operation, and the first operation includes at least one of the following: when the terminal is not configured with the downlink control information DCP encrypted with the energy-saving wireless network temporary identifier, the first monitoring behavior of WUS is determined based on the configuration information of the discontinuous reception DRX; when the terminal is configured with DCP, at least one of the second monitoring behavior of WUS is determined based on the monitoring situation of DCP and the third monitoring behavior of DCP is determined based on the monitoring result of WUS. In this way, the monitoring behavior of WUS and DCP when WUS is used in conjunction with the energy-saving mechanism of DRX and DCP is clarified, and the joint work of WUS and other power-saving mechanisms is realized to save the functions of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0043] Figure 2 This is the terminal wake-up schematic;

[0044] Figure 3 It is a flow chart of a transmission processing method provided in an embodiment of the present application;

[0045] Figures 4 to 9 This is an example diagram of WUS monitoring in a transmission processing method provided in an embodiment of the present application;

[0046] Fig.10 This is an example diagram of WUS monitoring in another transmission processing method provided in an embodiment of the present application;

[0047] Fig.11 It is a structural diagram of a transmission processing device provided in an embodiment of the present application;

[0048] Fig.12 is a structural diagram of another transmission processing device provided in an embodiment of the present application;

[0049] Fig.13 It is a structural diagram of a communication device provided in an embodiment of the present application;

[0050] Fig.14 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0051] Fig.15 It is a structural diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0053] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0054] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 thGeneration, 6G) communication system.

[0055] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0056] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0057] For ease of understanding, some contents involved in the embodiments of the present application are described below:

[0058] 1. Low power receiver.

[0059] The low power receiver can be called LP-WUR or almost zero power wakeup radio (AZP-WUR). The basic working principle of LP-WUR is that the receiving end includes a first module and a second module. The first module is a main communication module for sending and receiving mobile communication data, and the second module is a low power receiving module (also called a low power wakeup receiving module) for receiving the above low power wakeup signal. Figure 2 As shown. When the terminal is in idle or inactive state, the terminal turns on the low-power receiving module in energy-saving state or ultra-deep sleep state to monitor LP-WUS and turns off the main communication module. When downlink data arrives, the network-side device sends a wake-up signal to the terminal. After the terminal monitors the wake-up signal through the low-power receiving module, it triggers the main communication module from off to on after a series of judgments, and at this time the low-power receiving module enters the off state from the working state. The low-power wake-up receiving module can receive the low-power wake-up signal when it is turned on.

[0060] 2. Low power wake up signal (LP-WUS).

[0061] In order to reduce the receiving activity of the terminal in the standby state, the RF (Radio Frequency, RF) and baseband (MODEM) modules of the terminal's receiving module are truly turned off, thereby greatly reducing the power consumption of communication reception. This can be achieved by introducing a near "zero" power receiver in the terminal's receiving module. This near "zero" power receiver does not require complex RF module signal detection (such as amplification, filtering, quantization, etc.) and MODEM signal processing, but only relies on passive matching filtering and signal processing with low power consumption.

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

[0063] Such wake-up signals are usually some relatively simple on-off keying (OOK) signals, so that the receiver can obtain the wake-up notification through simple energy detection and subsequent possible sequence detection and recognition processes.

[0064] The reception of the low-power wake-up signal can be applied to a terminal in a Radio Resource Control (RRC) idle (RRC_idle) / inactive (inactive) state, and can also be applied to a terminal in an RRC connected state (RRC_connected), thereby achieving terminal energy saving.

[0065] In one embodiment, the wake-up signal mentioned in the present application is the wake-up signal received and monitored by the low-power receiver, that is, the low-power wake-up signal.

[0066] 3. Discontinuous Reception in Connected State (Connected Discontinuous Reception, C-DRX).

[0067] C-DRX can also be understood or replaced by DRX, which allows the UE to periodically enter a sleep state and not monitor the physical downlink control channel (PDCCH). When monitoring, it wakes up from the sleep state (Wake Up), thereby achieving the purpose of saving power. The above-mentioned "sleep" means that the terminal does not monitor the cell radio network temporary identifier (C-RNTI), modulation and coding scheme (MCS) cell radio network temporary identifier (MCS-C-RNTI), control information RNTI (CI-RNTI), configuration scheduling RNTI (cs-rnti), interruption RNTI (Interruption RNT, INT-RNTI), time slot format indication RNTI (SlotFormat Indication RNTI, SFI-RNTI), semi-persistent channel state information RNTI (Semi-PersistentChannel State Information RNTI, SP-CSI-RNTI), transmit power control physical uplink control channel RNTI (Transmit Power Control Physical Uplink Control Channel RNTI, TPC-PUCCH-RNTI), TPC physical uplink shared channel RNTI (TPC Physical Uplink Shared Channel RNTI, TPC-PUSCH-RNTI), TPC sounding reference signal RNTI (TPC Sounding Reference Signal RNTI, TPC-SRS-RNTI), Availability Indicator RNTI (AI-RNTI), Sidelink RNTI (SL-RNTI), Sidelink Configured Scheduling RNTI (SLCS-RNTI) and SL Semi-Persistent Scheduling V-RNTI scrambled PDCCH. On the contrary, "wake up" refers to the time when the UE is "awake", which is used to monitor the above PDCCH, etc. The awake time is collectively referred to as the active time, including the following situations:

[0068] DRX duration timer (drx-onDurationTimer): At this time, the UE is monitoring whether there is PDCCH;

[0069] DRX inactivity timer (drx-InactivityTimer): At this time, the UE detects the PDCCH and is receiving downlink data;

[0070] DRX downlink retransmission timer (drx-RetransmissionTimerDL) or DRX uplink retransmission timer drx-RetransmissionTimerUL: At this time, the UE is waiting for retransmission;

[0071] Random access contention resolution timer (ra-ContentionResolutionTimer) or message B response window (msgB-ResponseWindow): At this time, the UE is waiting to receive Msg2 or Msg4;

[0072] SR is sent on PUCCH: After the UE sends a Scheduling Request (SR), the UE is waiting for an uplink grant (UL grant);

[0073] After the non-contention random access UE receives a random access response (Rach access response, RAR): At this time, the UE is waiting to receive the DCI scrambled by the C-RNTI, which is used to indicate uplink resource scheduling.

[0074] 4. DCP.

[0075] The DCI format of DCP is DCI format 2_6, which is scrambled by the Power Saving Radio Network Temporary Identity (PS-RNTI) and sent in the Common Search Space, for example, in the Type 3-PDCCH Common Search Space Set (Type3-PDCCH CSS set). The reason why DCP is sent in the Common Search Space is that DCP can be shared by multiple UEs, that is, the network side device can use one DCP to control whether multiple UEs start the DRX duration timer (drx-onDurationTimer) in the next DRX long cycle. Optionally, long-cycle DRX can be equipped with DCP, but short-cycle DRX cannot be equipped with DCP.

[0076] Optionally, each long DRX cycle (Long DRX Cycle) has a corresponding DCP monitoring occasion (DCP MO). The UE monitors DCI format 2_6 in the DCP MO. Once the UE detects DCI in a certain MO, it reads the content and reports the wake-up indication (Wake-up indicate) to the Media Access Control (MAC) layer. The MAC entity will start the drx-onDurationTimer of the next DRX Cycle accordingly (that is, the UE wakes up at on duration) or keep the UE asleep. If both the short DRX cycle (Short DRX Cycle) and the long DRX cycle (Long DRX Cycle) are configured at the same time, the WUS is only for the Long DRX Cycle, and the Short DRX Cycle is still the original process. The terminal does not monitor DCP during DRX active time (The UE does not monitor DCP during DRX active time).

[0077] Once no DCI is detected in the DCP MO, the UE does not report any information. At this time, the high-level parameter ps-WakeUp configured by the network takes effect.

[0078] Configuring it to 1 means: if the UE does not detect DCI, it will wake up in the next DRX cycle;

[0079] Configuring it to 0 or the default value means: if the UE does not detect DCI, it will remain asleep in the next DRX Cycle.

[0080] For a certain DRX Cycle, the start time of UE monitoring DCP MO is indicated by the parameter ps-Offset in slots, that is, the UE starts DCP monitoring from ps-Offset slots ahead of the start time of the DRX Cycle, and monitors until the distance from the start time of the DRX Cycle reaches a minimum value. In other words, there is a minimum gap (Min Gap) from the end of DCP monitoring to the start of the DRX Cycle. The size of Min Gap is the capability of the UE, which the UE will report to the network side device when reporting the capability. This Gap is mainly used to process the DCP time.

[0081] In addition, when the UE cannot or does not need to monitor the DCP MO, for example, when the DCP MO overlaps with the synchronization signal block (Synchronization Signal and PBCH block, SSB), or due to reasons such as the measurement gap, the drx-onDurationTimer must be turned on in the next DRX Cycle.

[0082] The transmission processing method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0083] Reference Figure 3 , the embodiment of the present application provides a transmission processing method, such as Figure 3 As shown, the transmission processing method includes:

[0084] Step 301: When the terminal is configured with a wake-up signal WUS monitoring function, the terminal performs a first operation, where the first operation includes at least one of the following:

[0085] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0086] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0087] In the embodiment of the present application, when the terminal is not configured with DCP and the configuration information of DRX is configured, WUS needs to be used together with the power saving mechanism associated with DRX. When the terminal is configured with the configuration information of WUS and DCP is configured, WUS needs to be used together with the power saving mechanism associated with DCP or WUS needs to be used together with the power saving mechanism associated with DRX and DCP.

[0088] Optionally, determining the first monitoring behavior of WUS based on the configuration information of DRX can be understood as determining the monitoring time of WUS based on the configuration information of DRX, for example, monitoring WUS within the DRX activation time.

[0089] Optionally, determining the second monitoring behavior of WUS based on the monitoring situation of DCP can be understood as: determining the monitoring behavior of WUS according to whether DCP is monitored or whether the monitoring behavior of WUS is determined by monitoring DCP, and determining the monitoring behavior of WUS according to the indication information carried by the monitored DCP.

[0090] In the embodiment of the present application, when the terminal is configured with the wake-up signal WUS monitoring, the terminal performs the first operation, and the first operation includes at least one of the following: when the terminal is not configured with the downlink control information DCP encrypted with the energy-saving wireless network temporary identifier, the first monitoring behavior of WUS is determined based on the configuration information of the discontinuous reception DRX; when the terminal is configured with DCP, at least one of the second monitoring behavior of WUS is determined based on the monitoring situation of DCP and the third monitoring behavior of DCP is determined based on the monitoring result of WUS. In this way, the monitoring behavior of WUS and DCP when WUS is used in conjunction with the energy-saving mechanism of DRX and DCP is clarified, and the joint work of WUS and other power-saving mechanisms is realized to save the functions of the terminal.

[0091] It should be noted that the DRX mentioned in the embodiments of the present application can be understood as C-DRX.

[0092] Optionally, in some embodiments, the first monitoring behavior satisfies at least one of the following:

[0093] Monitor WUS during the DRX activation time;

[0094] Monitor WUS outside the DRX active time or during the DRX non-active time.

[0095] Optionally, outside the DRX activation time or within the DRX inactivation time may include at least one of the following:

[0096] During non-drx-onDurationTimer operation;

[0097] During the operation of the non-DRX inactivity timer (drx-InactivityTimer);

[0098] During the operation of the non-downlink retransmission timer (drx-RetransmissionTimerDL) or the non-uplink retransmission timer (drx-RetransmissionTimerUL);

[0099] Not in drx-LongCycle.

[0100] Optionally, in some embodiments, the first monitoring behavior is determined based on at least one of the following: protocol agreement and configuration or instruction by a network side device through target signaling.

[0101] In the implementation of the present application, the above-mentioned target signaling may include at least one of RRC signaling, layer 1 signaling and layer 2 signaling.

[0102] Optionally, the content included in the above target signaling can be set according to actual needs. For example, in some embodiments, the target signaling includes any of the following:

[0103] first indication information, where the first indication information is used to indicate a first monitoring behavior;

[0104] The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

[0105] In the embodiment of the present application, the target signaling includes the first indication information, which can be understood as the network side device displaying and indicating the first monitoring behavior. When the target signaling only includes the second indication information, it can be understood as the network side device implicitly indicating the first monitoring behavior, and the first monitoring behavior can be determined according to the location of the WUS MO.

[0106] Optionally, when the network side device is not configured with the WUS cycle, the WUS cycle is consistent with the DRX cycle by default.

[0107] Optionally, in some embodiments, if WUS monitoring requires additional signaling activation, such as activating WUS monitoring through RRC signaling, layer 1 signaling, or layer 2 signaling, the WUS MO may be understood as an activated WUS MO.

[0108] Optionally, in some embodiments, when the terminal is configured with at least two DRX groups, the at least two DRX groups satisfy any of the following:

[0109] The first monitoring behavior corresponding to each DRX group is determined separately;

[0110] The first monitoring behaviors corresponding to all DRX groups are the same;

[0111] The terminal considers or expects that the first monitoring behaviors corresponding to all DRX groups are the same;

[0112] The terminal does not expect that the first monitoring behaviors corresponding to all DRX groups are different.

[0113] In the case where the first monitoring behavior corresponding to each DRX group is determined separately, with respect to WUS MO, each DRX group is independently configured, indicated, activated, deactivated or monitored.

[0114] Optionally, when used in common for the at least two DRX groups, in the at least two DRX groups, the first monitoring behaviors corresponding to all DRX groups are the same, or the terminal believes or expects that the first monitoring behaviors corresponding to all DRX groups are the same; or the terminal does not expect that the first monitoring behaviors corresponding to all DRX groups are different. For example, in the at least two DRX groups, the terminal monitors WUS in DRX Active Time or DRX non-Active Time, or the terminal monitors WUS in DRX Active Time and DRX non-Active Time.

[0115] Optionally, in some embodiments, the second monitoring behavior satisfies any of the following:

[0116] When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring;

[0117] In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated;

[0118] In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

[0119] In the embodiment of the present application, DCP monitoring is performed before WUS monitoring. At this time, whether to monitor WUS and how to monitor WUS are determined based on the DCP detection result.

[0120] Optionally, the target DCI may be understood as DCI of DCI format 2_6, i.e., DCP. It should be understood that the target DCI carries a wake-up indication, and when the wake-up indication is "0", it indicates that the target DCI indicates not to turn on drx-onDurationTimer, and the terminal monitors WUS or activates WUS monitoring.

[0121] Optionally, the second monitoring behavior including monitoring WUS can be understood as the second monitoring behavior including starting WUS monitoring or resuming WUS monitoring. For example, in some embodiments, the second monitoring behavior specifically includes any of the following situations:

[0122] Case 1: The terminal monitors LP-WUS only in the first time period, which is the time period from the end of the monitoring opportunity of the last target DCI to the start of drx_onDurationTimer. If WUS is detected in the first time period, the drx-onDurationTimer of the DRX Cycle is turned on; otherwise, the drx-onDurationTimer of the DRX Cycle is not turned on.

[0123] Case 2: The terminal starts or resumes WUS monitoring or activates WUS monitoring until the next DCP MO.

[0124] Case 3: The terminal starts or resumes WUS monitoring or activates WUS monitoring until WUS is detected.

[0125] Optionally, when it is detected that the wake-up indication carried by a target DCI associated with a DRX cycle is "1", it means that the target DCI instructs the terminal to start the DRX duration timer, and the terminal starts or resumes WUS monitoring, or activates WUS monitoring. In this embodiment of the present application, the terminal only monitors WUS in the second time period, and the second time period is the time period from the subsequent symbol / time slot where the target DCI indicating that the Wake-up indication of the UE is "1" is detected to the start of drx_onDurationTimer. If LP-WUS is detected in the second time period, the drx-onDurationTimer of the DRX Cycle is turned on; otherwise, the drx-onDurationTimer of the DRX Cycle is not turned on.

[0126] Optionally, when the start conditions of drx-onDurationTimer are met, the terminal can determine that the DRX duration timer of the DRX cycle is started. At this time, the terminal does not monitor WUS monitoring or WUS monitoring is deactivated; wherein, the start conditions of the above-mentioned drx-onDurationTimer can refer to the relevant technology and are not repeated here. For example, in some embodiments, when it is detected that a target DCI associated with a DRX cycle indicates that the terminal starts the DRX duration timer, it can be determined that the DRX duration timer of the DRX cycle is started.

[0127] Optionally, in some embodiments, WUS may be used to supplement DCP monitoring, that is, the terminal needs to monitor WUS when it does not monitor DCP due to some factors.

[0128] Optionally, in some embodiments, when all DCP monitoring opportunities associated with a DRX cycle do not detect the target DCI or it is determined that the DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP, the method further includes:

[0129] When the first condition is met, the terminal determines that a DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP;

[0130] The first condition includes at least one of the following:

[0131] The DCP monitoring opportunity is within the DRX activation time;

[0132] The DCP monitoring opportunity is during the bandwidth part BWP switching interruption time or measurement gap;

[0133] During the operation of the random access response time window, the media access control MAC entity monitors the physical downlink control channel PDCCH of the random access response identified by the cell radio network temporary identifier c-RNTI in the special cell SpCell.

[0134] Optionally, in some embodiments, the third monitoring behavior satisfies at least one of the following:

[0135] In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication;

[0136] When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP;

[0137] The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

[0138] In the embodiment of the present application, WUS monitoring is performed before DCP monitoring, and at least one of whether to monitor DCP and how to monitor DCP is determined depending on the WUS detection result.

[0139] Optionally, WUS can instruct UE whether to monitor DCP. If it is instructed to monitor DCP, the terminal monitors DCP. At this time, if there is still a WUS monitoring opportunity after monitoring DCP, the monitoring behavior of the subsequent WUS monitoring opportunity WUS (i.e., the first monitoring behavior) can be determined according to the monitoring result of DCP; if there is no WUS monitoring opportunity after monitoring DCP, the behavior of the terminal is consistent with the monitoring DCP behavior of version 16 (R16).

[0140] Optionally, if the WUS indicates not to monitor the DCP, the terminal behavior is consistent with detecting that the Wake-up indication in the DCP is 1, that is, starting the DRX duration timer (drx-onDurationTimer for the next long DRX cycle).

[0141] Optionally, if the third monitoring behavior is not to monitor DCP, the terminal behavior is consistent with detecting that the Wake-up indication in the DCP is 1, that is, turning on drx-onDurationTimer for the next long DRX cycle.

[0142] Optionally, if the above-mentioned third monitoring behavior is monitoring DCP, at this time, if there is still a WUS listening opportunity after monitoring DCP, the listening behavior of the subsequent WUS listening opportunity WUS (ie, the first listening behavior) can be determined according to the monitoring results of DCP; if there is no WUS listening opportunity after monitoring DCP, the behavior of the terminal is consistent with the monitoring DCP behavior of the 16th version.

[0143] Optionally, in some embodiments, the method further comprises:

[0144] When the terminal detects the WUS, the terminal performs a target behavior, where the target behavior includes at least one of the following:

[0145] The first behavior is: determining at least one of a state of a primary receiver and monitoring a target PDCCH according to an instruction of the WUS;

[0146] The second behavior: monitoring PDCCH;

[0147] The third behavior is: starting and running a first timer, and monitoring the PDCCH during the running period of the first timer;

[0148] The fourth behavior is: stop monitoring WUS or continue monitoring WUS.

[0149] Optionally, the state of the main receiver can be understood as one of a wake-up state, a light sleep state, and a micro sleep state that lasts for X duration units, where X is greater than or equal to 1, can be indicated by a high-level configuration or WUS, and the time unit includes milliseconds, time slots, or symbols.

[0150] Optionally, if the WUS indicates wake up, the terminal monitors the PDCCH; otherwise, the terminal is not required to monitor the PDCCH or the terminal does not monitor the PDCCH.

[0151] Optionally, the method further comprises:

[0152] During the operation of the first timer, when a PDCCH is detected, the terminal starts and runs a second timer;

[0153] When a PDCCH is detected during the running of the second timer, the terminal restarts the second timer.

[0154] Optionally, the method further comprises:

[0155] When the second condition is met, the terminal stops monitoring the PDCCH and resumes monitoring the WUS;

[0156] The second condition includes at least one of the following:

[0157] The first timer times out;

[0158] The network side device instructs the first timer to stop running or terminate running;

[0159] The second timer times out;

[0160] The network side device instructs the second timer to stop running or terminate running.

[0161] In the embodiment of the present application, the network side device may instruct the first timer to stop running or terminate running through at least one of the following signaling:

[0162] Newly defined signaling;

[0163] DRX Command Media Access Control Controller (Command MAC CE);

[0164] Long DRX Command MAC CE.

[0165] Similarly, the network-side device may instruct the second timer to stop running or terminate running through at least one of the following signalings:

[0166] Newly defined signaling

[0167] DRX Command MAC CE;

[0168] Long DRX Command MAC CE.

[0169] Optionally, in some embodiments, the first timer may be equal to the second timer, that is, the first timer may be replaced by the second timer, or the second timer may be replaced by the first timer.

[0170] Optionally, in some embodiments, at least one of the first timer and the second timer includes at least one of the following:

[0171] Newly defined timer;

[0172] DRX duration timer;

[0173] DRX inactivity timer.

[0174] Optionally, in some embodiments, stopping monitoring WUS includes:

[0175] Stop monitoring the WUS monitoring opportunity in the current WUS cycle, and continue monitoring the WUS monitoring opportunity in the next WUS cycle.

[0176] Optionally, in some embodiments, the target PDCCH includes at least one of the following:

[0177] PDCCH scheduled by DCI format agreed upon by protocol, configured by higher layers or indicated by the WUS;

[0178] PDCCH scrambled by RNTI as agreed in the protocol, configured by a higher layer or indicated by the WUS;

[0179] The search space set or PDCCH on the search space set specified by protocol, configured by higher layers or indicated by the WUS.

[0180] Optionally, in some embodiments, a target behavior corresponding to a WUS detected within a DRX activation time is different from a target behavior corresponding to a WUS detected outside the DRX activation time or within a DRX inactive time.

[0181] For example, when the WUS detects in the DRX Active Time, the terminal executes at least the first behavior; when the WUS detects in the DRX non-Active Time, the terminal executes at least one of the second behavior and the third behavior.

[0182] Optionally, in some embodiments, the function and working mechanism of WUS are the same as R16 DCP, and the terminal does not expect to configure the use of LP-WUS and DCP functions at the same time or the terminal does not expect to configure the use of LP-WUS and DCP functions in the same DRX group; or the network ensures that only the use of LP-WUS is configured, or only the use of DCP is configured.

[0183] In order to better understand the present application, some specific examples are given below for detailed description.

[0184] In some embodiments, assuming that according to the configuration or instructions specified in the protocol or displayed by the signaling, the terminal only monitors WUS in DRX non-Active Time, it can also be understood that the configured or activated WUS MO is only effective or valid in DRX non-Active Time.

[0185] Optionally, WUS configuration or monitoring timing is as follows:

[0186] WUS period (Periodicity / Cycle): 10;

[0187] WUS Monitoring Window: 5;

[0188] Window Start Offset: 2;

[0189] The WUS monitoring occasion (MO) within the window may be continuous, discrete, periodic or aperiodic.

[0190] like Figure 4 As shown, assuming that the terminal receives PDCCH at the 0th millisecond of the first long DRX cycle, WUS is monitored at the 4th millisecond of the first long DRX cycle and from the 2nd millisecond to the 4th millisecond of the second long DRX cycle, or WUS MO is activated, and WUSMO is considered to be valid.

[0191] It should be noted that, in the embodiment of the present application, not monitoring WUS may include at least one of the following understandings:

[0192] The network-side device assumes or thinks that the terminal does not need to monitor WUS, or the terminal does not monitor WUS;

[0193] The network-side device does not require the terminal to monitor WUS;

[0194] Depending on the terminal implementation, the terminal may or may not monitor the WUS.

[0195] Optionally, the transmission of WUS may be a single transmission or multiple transmissions, such as repeated transmission.

[0196] In some embodiments, the terminal monitors the WUS according to the time domain position of the WUS MO configured or indicated by signaling.

[0197] One example is: depending on the time domain position of the WUS MO, the terminal can only listen to the WUS during the non-drx-onDurationTimer operation period.

[0198] Optionally, WUS configuration or monitoring timing is as follows:

[0199] WUS period (Periodicity / Cycle): 10;

[0200] WUS Monitoring Window: 8;

[0201] Window Start Offset: 2;

[0202] The WUS monitoring occasion within the window can be continuous, discrete, periodic or aperiodic.

[0203] like Figure 5 As shown, assuming that the terminal receives PDCCH at the 0th millisecond of the first long DRX cycle, WUS is monitored at the 4th millisecond, 6th millisecond and 8th millisecond of the first long DRX cycle and the 2nd millisecond, 4th millisecond, 6th millisecond and 8th millisecond of the second long DRX cycle, or WUS MO is activated, and WUS MO is considered valid.

[0204] Another example is: depending on the time domain position of the WUS MO, the terminal can monitor the LP-WUS during the drx-onDurationTimer operation period, and can also monitor the WUS during the non-drx-onDurationTimer operation period.

[0205] Optionally, WUS configuration or monitoring timing is as follows:

[0206] WUS period (Periodicity / Cycle): 10;

[0207] WUS Monitoring Window: 6;

[0208] Window Start Offset: 0;

[0209] The WUS monitoring occasion within the window can be continuous, discrete, periodic or aperiodic.

[0210] like Figure 6 As shown, assuming that the terminal receives the PDCCH at the 0th millisecond of the first long DRX cycle, the WUS is monitored at the 0th millisecond, the 1st millisecond, the 3rd millisecond and the 4th millisecond of the long DRX cycle, or the WUS MO is activated, and it is considered that the WUS MO is valid.

[0211] Another example is: depending on the time domain position of the WUS MO, the terminal may continuously monitor the WUS.

[0212] Optionally, WUS configuration or monitoring timing is as follows:

[0213] WUS period (Periodicity / Cycle): 10;

[0214] WUS Monitoring Window: 8;

[0215] Window Start Offset: 2;

[0216] The WUS monitoring occasion within the window can be continuous, discrete, periodic or aperiodic.

[0217] like Figure 7 As shown, assuming that the terminal receives the PDCCH at the 0th millisecond of the first long DRX cycle, the WUS is monitored from the 2nd millisecond to the 9th millisecond of the long DRX cycle, or the WUS MO is effective, and it is considered that the WUS MO is valid.

[0218] Another example is that the WUS cycle (or the WUS monitoring cycle) is greater than the DRX cycle.

[0219] Optionally, WUS configuration or monitoring timing is as follows:

[0220] WUS period (Periodicity / Cycle): 15;

[0221] WUS Monitoring Window: 10;

[0222] Window Start Offset: 2;

[0223] The WUS monitoring occasion within the window can be continuous, discrete, periodic or aperiodic.

[0224] like Figure 8 As shown, assuming that the terminal receives PDCCH at the 0th millisecond of the first long DRX cycle, WUS is monitored from the 3rd millisecond to the 8th millisecond of the first long DRX cycle and from the 8th millisecond to the 9th millisecond of the second long DRX cycle, or WUS MO is activated, and WUS MO is considered valid.

[0225] Another example is: the WUS cycle is smaller than the DRX cycle.

[0226] Optionally, WUS configuration or monitoring timing is as follows:

[0227] WUS period (Periodicity / Cycle): 5;

[0228] WUS Monitoring Window: 3;

[0229] Window Start Offset: 2;

[0230] The WUS monitoring occasion within the window can be continuous, discrete, periodic or aperiodic.

[0231] like Fig. 9 As shown, assuming that the terminal receives the PDCCH at the 0th millisecond of the first long DRX cycle, the WUS is monitored from the 2nd millisecond to the 4th millisecond and from the 7th millisecond to the 9th millisecond of the long DRX cycle, or the WUS MO is activated, and it is considered that the WUS MO is valid.

[0232] Reference Fig.10 , the embodiment of the present application also provides a transmission processing method, such as Fig.10 As shown, the transmission processing method includes:

[0233] Step 1001: The network side device performs a second operation, where the second operation includes any one of the following:

[0234] The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured;

[0235] Configure WUS configuration information for the terminal, but do not configure DCP;

[0236] Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS;

[0237] Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP;

[0238] The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

[0239] In the embodiment of the present application, the above-mentioned PDCCH search space set switching can be understood as the 16th version of the search space set switching (c) R16 Search Space Set Group switching). The above-mentioned configuration information of skipping PDCCH monitoring can include the 17th version of skipping PDCCH monitoring (d) R17 skipping of PDCCH monitoring).

[0240] Optionally, for the terminal side: the UE indicating support for WUS should also indicate support for R17 PDCCH skipping function (including at least one of pdcch-SkippingWithoutSSSG-r17 and pdcch-SkippingWithSSSG-r17) or R16 SSSG switching or drx-Adaptation-r16, drx-Adaptation-r17.

[0241] For the network side: The network side device should also configure at least one of DRX, DCP, R17 PDCCHskipping and R16 SSSG switching when configuring WUS.

[0242] Optionally, the first monitoring behavior satisfies at least one of the following:

[0243] Monitor WUS during the DRX activation time;

[0244] Monitor WUS outside the DRX activation time or during the DRX inactivation time.

[0245] Optionally, the method further comprises:

[0246] The network side device sends a target signaling to the terminal, where the target signaling is used to configure or instruct the first monitoring behavior.

[0247] Optionally, the target signaling includes at least one of the following:

[0248] first indication information, where the first indication information is used to indicate a first monitoring behavior;

[0249] The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

[0250] Optionally, the second monitoring behavior satisfies any of the following:

[0251] When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring;

[0252] In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated;

[0253] In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

[0254] Optionally, the third monitoring behavior satisfies at least one of the following:

[0255] In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication;

[0256] When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP;

[0257] The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

[0258] The transmission processing method provided in the embodiment of the present application can be executed by a transmission processing device. In the embodiment of the present application, the transmission processing device provided in the embodiment of the present application is described by taking the transmission processing method executed by the transmission processing device as an example.

[0259] Reference Fig.11 , the embodiment of the present application also provides a transmission processing device, such as Fig.11 As shown, the transmission processing device 1100 includes:

[0260] The first execution module 1101 is configured to execute a first operation when the terminal is configured with the wake-up signal WUS monitoring, where the first operation includes at least one of the following:

[0261] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0262] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0263] Optionally, the first monitoring behavior satisfies at least one of the following:

[0264] Monitor WUS during the DRX activation time;

[0265] Monitor WUS outside the DRX activation time or during the DRX inactivation time.

[0266] Optionally, the first monitoring behavior is determined based on at least one of the following: protocol agreement and configuration or instruction by a network side device through target signaling.

[0267] Optionally, the target signaling includes at least one of the following:

[0268] first indication information, where the first indication information is used to indicate a first monitoring behavior;

[0269] The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

[0270] Optionally, when the network side device is not configured with the WUS cycle, the WUS cycle is consistent with the DRX cycle by default.

[0271] Optionally, when the terminal is configured with at least two DRX groups, the at least two DRX groups satisfy any one of the following:

[0272] The first monitoring behavior corresponding to each DRX group is determined separately;

[0273] The first monitoring behaviors corresponding to all DRX groups are the same;

[0274] The terminal considers or expects that the first monitoring behaviors corresponding to all DRX groups are the same;

[0275] The terminal does not expect that the first monitoring behaviors corresponding to all DRX groups are different.

[0276] Optionally, the second monitoring behavior satisfies any of the following:

[0277] When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring;

[0278] In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated;

[0279] In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

[0280] Optionally, when all DCP monitoring opportunities associated with a DRX cycle do not detect the target DCI or it is determined that the DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP, the transmission processing device 1100 further includes:

[0281] A determination module, configured to determine that a DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP when a first condition is met;

[0282] The first condition includes at least one of the following:

[0283] The DCP monitoring opportunity is within the DRX activation time;

[0284] The DCP monitoring opportunity is during the bandwidth part BWP switching interruption time or measurement gap;

[0285] During the operation of the random access response time window, the media access control MAC entity monitors the physical downlink control channel PDCCH of the random access response identified by the cell radio network temporary identifier c-RNTI in the special cell SpCell.

[0286] Optionally, the third monitoring behavior satisfies at least one of the following:

[0287] In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication;

[0288] When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP;

[0289] The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

[0290] Optionally, the first execution module 1101 is further configured to: execute a target behavior when the terminal detects the WUS, and the target behavior includes at least one of the following:

[0291] Determine at least one of a state of a primary receiver and a monitoring target PDCCH according to an instruction of the WUS;

[0292] Monitor PDCCH;

[0293] Starting and running a first timer, and monitoring the PDCCH during the running of the first timer;

[0294] Stop monitoring WUS or continue monitoring WUS.

[0295] Optionally, the first execution module 1101 is further used to:

[0296] During the operation of the first timer, when a PDCCH is detected, starting and running a second timer;

[0297] When a PDCCH is detected during the running of the second timer, the second timer is restarted.

[0298] Optionally, the first execution module 1101 is further configured to: when a second condition is met, the terminal stops monitoring the PDCCH and resumes monitoring the WUS;

[0299] The second condition includes at least one of the following:

[0300] The first timer times out;

[0301] The network side device instructs the first timer to stop running or terminate running;

[0302] The second timer times out;

[0303] The network side device instructs the second timer to stop running or terminate running.

[0304] Optionally, at least one of the first timer and the second timer includes at least one of the following:

[0305] Newly defined timer;

[0306] DRX duration timer;

[0307] DRX inactivity timer.

[0308] Optionally, stopping monitoring WUS includes:

[0309] Stop monitoring the WUS monitoring opportunity in the current WUS cycle, and continue monitoring the WUS monitoring opportunity in the next WUS cycle.

[0310] Optionally, the target PDCCH includes at least one of the following:

[0311] PDCCH scheduled by DCI format agreed upon by protocol, configured by higher layers or indicated by the WUS;

[0312] PDCCH scrambled by RNTI as agreed in the protocol, configured by a higher layer or indicated by the WUS;

[0313] The search space set or PDCCH on the search space set specified by protocol, configured by higher layers or indicated by the WUS.

[0314] Optionally, a target behavior corresponding to a WUS detected within a DRX activation time is different from a target behavior corresponding to a WUS detected outside the DRX activation time or within a DRX inactive time.

[0315] Reference Fig.12 , the embodiment of the present application also provides a transmission processing device, such as Fig.12 As shown, the transmission processing device 1200 includes:

[0316] The second execution module 1201 is configured to execute a second operation, where the second operation includes any one of the following:

[0317] The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured;

[0318] Configure WUS configuration information for the terminal, but do not configure DCP;

[0319] Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS;

[0320] Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP;

[0321] The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

[0322] Optionally, the first monitoring behavior satisfies at least one of the following:

[0323] Monitor WUS during the DRX activation time;

[0324] Monitor WUS outside the DRX activation time or during the DRX inactivation time.

[0325] Optionally, the method further comprises:

[0326] The network side device sends a target signaling to the terminal, where the target signaling is used to configure or instruct the first monitoring behavior.

[0327] Optionally, the target signaling includes at least one of the following:

[0328] first indication information, where the first indication information is used to indicate a first monitoring behavior;

[0329] The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

[0330] Optionally, the second monitoring behavior satisfies any of the following:

[0331] When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring;

[0332] In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated;

[0333] In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

[0334] Optionally, the third monitoring behavior satisfies at least one of the following:

[0335] In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication;

[0336] When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP;

[0337] The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

[0338] The transmission processing device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0339] The transmission processing device provided in the embodiment of the present application can achieve Figures 3 to 10 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0340] like Fig.13 As shown, an embodiment of the present application also provides a communication device 1300, including a processor 1301 and a memory 1302, and the memory 1302 stores a program or instruction that can be executed on the processor 1301. When the program or instruction is executed by the processor 1301, the various steps of the above-mentioned transmission processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0341] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 3 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Fig.14 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0342] The terminal 1400 includes but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409 and at least some of the components of the processor 1410.

[0343] Those skilled in the art will appreciate that the terminal 1400 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1410 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.14 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0344] It should be understood that in the embodiment of the present application, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042, and the graphics processor 14041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1406 may include a display panel 14061, and the display panel 14061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1407 includes a touch panel 14071 and at least one of other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include two parts: a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0345] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 1401 can transmit the data to the processor 1410 for processing; in addition, the radio frequency unit 1401 can send uplink data to the network side device. Generally, the radio frequency unit 1401 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

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

[0347] The processor 1410 may include one or more processing units; optionally, the processor 1410 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1410.

[0348] The radio frequency unit 1401 is configured to perform a first operation when the terminal is configured with the wake-up signal WUS monitoring, where the first operation includes at least one of the following:

[0349] When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX;

[0350] In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

[0351] It can be 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 repeated here.

[0352] The embodiment of the present application 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 a program or instruction to implement the following Fig.10 The steps of the method embodiment shown. This network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation mode of the above method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.

[0353] Specifically, the embodiment of the present application also provides a network side device. Fig.15 As shown, the network side device 1500 includes: an antenna 151, a radio frequency device 152, a baseband device 153, a processor 154 and a memory 155. The antenna 151 is connected to the radio frequency device 152. In the uplink direction, the radio frequency device 152 receives information through the antenna 151 and sends the received information to the baseband device 153 for processing. In the downlink direction, the baseband device 153 processes the information to be sent and sends it to the radio frequency device 152. The radio frequency device 152 processes the received information and sends it out through the antenna 151.

[0354] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 153, which includes a baseband processor.

[0355] The baseband device 153 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.15 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 155 through a bus interface to call the program in the memory 155 to execute the network device operations shown in the above method embodiment.

[0356] The network side device may further include a network interface 156, which is, for example, a Common Public Radio Interface (CPRI).

[0357] Specifically, the network side device 1500 of the embodiment of the present application further includes: instructions or programs stored in the memory 155 and executable on the processor 154, and the processor 154 calls the instructions or programs in the memory 155 to execute. Fig.12 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0358] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned transmission processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0359] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0360] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned transmission processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0361] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0362] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned transmission processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0363] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the transmission processing method of the terminal side as described above, and the network side device can be used to execute the steps of the transmission processing method of the network side device as described above.

[0364] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0365] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0366] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A transmission processing method, characterized in that: include: When the terminal is configured with the wake-up signal WUS monitoring, the terminal performs a first operation, where the first operation includes at least one of the following: When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX; In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

2. The method according to claim 1, characterized in that The first monitoring behavior satisfies at least one of the following: Monitor WUS during the DRX activation time; Monitor WUS outside the DRX activation time or during the DRX inactivation time.

3. The method according to claim 2, characterized in that The first monitoring behavior is determined based on at least one of the following: protocol agreement and configuration or instruction by a network side device through target signaling.

4. The method according to claim 3, characterized in that The target signaling includes at least one of the following: first indication information, where the first indication information is used to indicate a first monitoring behavior; The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

5. The method according to claim 4, characterized in that When the network side device does not configure the WUS cycle, the WUS cycle is consistent with the DRX cycle by default.

6. The method according to claim 1, characterized in that In a case where the terminal is configured with at least two DRX groups, the at least two DRX groups satisfy any one of the following: The first monitoring behavior corresponding to each DRX group is determined separately; The first monitoring behaviors corresponding to all DRX groups are the same; The terminal considers or expects that the first monitoring behaviors corresponding to all DRX groups are the same; The terminal does not expect that the first monitoring behaviors corresponding to all DRX groups are different.

7. The method according to claim 1, characterized in that The second monitoring behavior satisfies any of the following: When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring; In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated; In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

8. The method according to claim 7, characterized in that In a case where the target DCI is not detected in all DCP monitoring opportunities associated with a DRX cycle or it is determined that the DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP, the method further includes: When the first condition is met, the terminal determines that a DCP monitoring opportunity associated with a DRX cycle does not monitor the DCP; The first condition includes at least one of the following: The DCP monitoring opportunity is within the DRX activation time; The DCP monitoring opportunity is during the bandwidth part BWP switching interruption time or measurement gap; During the operation of the random access response time window, the media access control MAC entity monitors the physical downlink control channel PDCCH of the random access response identified by the cell radio network temporary identifier c-RNTI in the special cell SpCell.

9. The method according to claim 1, characterized in that: The third monitoring behavior satisfies at least one of the following: In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication; When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP; The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: When the terminal detects the WUS, the terminal performs a target behavior, where the target behavior includes at least one of the following: Determine at least one of a state of a primary receiver and a monitoring target PDCCH according to an instruction of the WUS; Monitor PDCCH; Starting and running a first timer, and monitoring the PDCCH during the running of the first timer; Stop monitoring WUS or continue monitoring WUS.

11. The method according to claim 10, characterized in that The method further comprises: During the operation of the first timer, when a PDCCH is detected, the terminal starts and runs a second timer; When a PDCCH is detected during the running of the second timer, the terminal restarts the second timer.

12. The method according to claim 11, characterized in that The method further comprises: When the second condition is met, the terminal stops monitoring the PDCCH and resumes monitoring the WUS; The second condition includes at least one of the following: The first timer times out; The network side device instructs the first timer to stop running or terminate running; The second timer times out; The network side device instructs the second timer to stop running or terminate running.

13. The method according to claim 11, characterized in that At least one of the first timer and the second timer includes at least one of the following: Newly defined timer; DRX duration timer; DRX inactivity timer.

14. The method according to claim 10, characterized in that The stopping of monitoring WUS comprises: Stop monitoring the WUS monitoring opportunity in the current WUS cycle, and continue monitoring the WUS monitoring opportunity in the next WUS cycle.

15. The method according to claim 10, characterized in that The target PDCCH includes at least one of the following: PDCCH scheduled by DCI format agreed upon by protocol, configured by higher layers or indicated by the WUS; PDCCH scrambled by RNTI as agreed in the protocol, configured by a higher layer or indicated by the WUS; The search space set or PDCCH on the search space set specified by protocol, configured by higher layers or indicated by the WUS.

16. The method according to any one of claims 10 to 15, characterized in that The target behavior corresponding to detecting a WUS during the DRX activation time is different from the target behavior corresponding to detecting a WUS outside the DRX activation time or during the DRX inactive time.

17. A transmission processing method, characterized in that: include: The network-side device performs a second operation, where the second operation includes any one of the following: The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured; Configure WUS configuration information for the terminal, but do not configure DCP; Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS; Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP; The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

18. The method according to claim 17, characterized in that The first monitoring behavior satisfies at least one of the following: Monitor WUS during the DRX activation time; Monitor WUS outside the DRX activation time or during the DRX inactivation time.

19. The method according to claim 18, characterized in that The method further comprises: The network side device sends a target signaling to the terminal, where the target signaling is used to configure or instruct the first monitoring behavior.

20. The method according to claim 19, characterized in that The target signaling includes at least one of the following: first indication information, where the first indication information is used to indicate a first monitoring behavior; The second indication information is used to configure at least one of a WUS period, a measurement window within the WUS period, and a WUS listening opportunity within the measurement window.

21. The method according to claim 17, characterized in that The second monitoring behavior satisfies any of the following: When it is detected that at least one target downlink control information DCI associated with a DRX cycle indicates that the terminal does not start the DRX duration timer, the second monitoring behavior includes monitoring WUS or activating WUS monitoring; In the case where it is detected that at least one target DCI associated with a DRX cycle indicates that the terminal starts a DRX duration timer or the terminal determines that the DRX duration timer of the DRX cycle is started, the second monitoring behavior includes not monitoring the WUS or the WUS monitoring is deactivated; In a case where the target DCI is not detected in all DCP monitoring occasions associated with a DRX cycle or it is determined that the DCP monitoring occasion associated with a DRX cycle does not monitor the DCP, the second monitoring row includes monitoring the WUS or activating the WUS monitoring.

22. The method according to claim 17, characterized in that The third monitoring behavior satisfies at least one of the following: In the case where a WUS is detected at the target monitoring opportunity, the third monitoring behavior includes any one of the following: determining whether to monitor the DCP, not monitor the DCP, and monitor the DCP based on the WUS indication; When no WUS is detected at the target monitoring opportunity, the third monitoring behavior is monitoring DCP; The target monitoring opportunity is a WUS monitoring opportunity before the DCP monitoring opportunity within the DRX cycle.

23. A transmission processing device, characterized in that: include: The first execution module is configured to execute a first operation when the terminal is configured with the wake-up signal WUS monitoring, wherein the first operation includes at least one of the following: When the terminal is not configured with downlink control information DCP scrambled using an energy-saving radio network temporary identity, determining a first monitoring behavior of the WUS based on the configuration information of the discontinuous reception DRX; In the case where the terminal is configured with DCP, at least one of a second monitoring behavior of the WUS is determined based on the monitoring situation of the DCP and a third monitoring behavior of the DCP is determined based on the monitoring result of the WUS.

24. A transmission processing device, characterized in that: include: The second execution module is configured to execute a second operation, where the second operation includes any one of the following: The terminal is configured with downlink control information DCP scrambled with energy-saving wireless network temporary identification, and configuration information of the wake-up signal WUS is not configured; Configure WUS configuration information for the terminal, but do not configure DCP; Configure WUS configuration information and discontinuous reception DRX configuration information for the terminal, and do not configure DCP, where the DRX configuration information is used to determine a first monitoring behavior of the WUS; Configuring configuration information of DCP and WUS for the terminal, wherein the monitoring of the DCP and the monitoring of the WUS satisfy at least one of the following: the monitoring result of the DCP is used to determine the second monitoring behavior of the WUS, and the monitoring result of the WUS is used to determine the third monitoring behavior of the DCP; The terminal is configured with configuration information of the WUS and configuration information of skipping monitoring of the physical downlink control channel PDCCH or switching of the PDCCH search space set, and the monitoring result of the WUS is used to determine whether the terminal executes the target behavior.

25. A terminal, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission processing method according to any one of claims 1 to 16 are implemented.

26. A network side device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission processing method according to any one of claims 17 to 22 are implemented.

27. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the transmission processing method according to any one of claims 1 to 22 are implemented.

Images