Communication processing method and apparatus, device, and readable storage medium

Abstract

The present application discloses a communication processing method and apparatus, a device, and a readable storage medium. The method comprises: a terminal receives configuration information, the configuration information comprising a plurality of DRX configurations, and the plurality of DRX configurations being used for the same serving cell or the same serving cell list; and if the terminal receives a PDCCH within overlapping active periods of at least two DRX configurations, the terminal controls drx-InactivityTimer of at least one DRX configuration among the at least two DRX configurations; or, if the terminal performs transmission on a scheduling resource, the terminal controls a timer in a DRX configuration corresponding to the transmission, or the terminal controls, on the basis of received DRX control signaling, the plurality of DRX configurations or the DRX configuration corresponding to the DRX control signaling to enter an inactive period.

Description

Communication processing method, device, equipment and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311232407.2 filed on September 21, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a communication processing method, apparatus, device and readable storage medium. Background Art

[0004] Extended Reality (XR) services include video data, audio data, and some control signaling and special data with control functions. Therefore, service flows with different cycles may run in parallel. Due to the different service cycles and scheduling latency requirements of each service flow in a multi-stream service, in order to better support the power saving needs of multi-stream service XR devices, it may support the simultaneous configuration of multiple sets of discontinuous reception (DRX) configurations. When multiple sets of DRX configurations are provided at the same time, if the timers related to all DRX configurations run simultaneously, the terminal may remain in an active state, and the purpose of power saving cannot be achieved.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication processing method, apparatus, device, and readable storage medium to solve the problem of how to meet the power saving requirements of devices supporting multi-stream services.

[0007] In a first aspect, a communication processing method is provided, comprising:

[0008] The terminal receives configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0009] If the terminal receives a PDCCH within the activation time in which at least two DRX configurations overlap, the terminal controls the drx-InactivityTimer of at least one of the at least two DRX configurations; or, if the terminal transmits on the scheduled resources, the terminal controls the timer in the DRX configuration corresponding to the transmission, or, the terminal controls the multiple DRX configurations according to the received DRX control signaling, or the DRX configuration corresponding to the DRX control signaling enters the inactive time.

[0010] In a second aspect, a communication processing method is provided, comprising:

[0011] The network side device sends configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0012] The network side device sends a DRX control signaling, where the DRX control command is used to control the multiple DRX configurations, or to control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

[0013] According to a third aspect, a communication processing device is provided, including:

[0014] a first receiving module, configured to receive configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0015] The first processing module is used to control the drx-InactivityTimer of at least one DRX configuration among the at least two DRX configurations if the terminal receives a PDCCH within the activation time overlapping with at least two DRX configurations; or, if the terminal transmits on the scheduled resources, control the timer in the DRX configuration corresponding to the transmission, or, according to the received DRX control signaling, control the multiple DRX configurations, or the DRX configuration corresponding to the DRX control signaling to enter the inactive time.

[0016] According to a fourth aspect, a communication processing device is provided, including:

[0017] A first sending module is configured to send configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0018] The second sending module is used to send DRX control signaling, where the DRX control command is used to control the multiple DRX configurations, or control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

[0019] In a fifth aspect, a terminal is provided, comprising: a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0020] In the sixth aspect, a network side device is provided, comprising: a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the second aspect.

[0021] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by the processor of the terminal, the steps of the method described in the first aspect are implemented, or when the program or instruction is executed by the processor of the network side device, the steps of the method described in the second aspect are implemented.

[0022] In an eighth 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 configured to run a program or instructions to implement the steps of the method described in the first aspect or the second aspect.

[0023] In a ninth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.

[0024] In the tenth aspect, a communication system is provided, which includes a terminal and a network side device, the terminal is used to execute the steps of the method described in the first aspect, and the network side device is used to execute the steps of the method described in the second aspect.

[0025] In an embodiment of the present application, a terminal receives configuration information, where the configuration information includes multiple DRX configurations. If the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap, the terminal controls the drx-InactivityTimer of at least one of the at least two DRX configurations; or, if the terminal transmits on a scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, or, the terminal controls the multiple DRX configurations according to the received DRX control signaling, or the DRX configuration corresponding to the DRX control signaling enters an inactive time, thereby meeting the power saving requirements of equipment supporting multi-stream services. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG1 is a schematic diagram of a DRX long cycle and a DRX short cycle;

[0027] FIG2 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the present application;

[0028] FIG3 is a flow chart of a communication processing method according to an embodiment of the present application;

[0029] FIG4 is a second flowchart of the communication processing method provided in an embodiment of the present application;

[0030] FIG5 is a schematic diagram of one of the multiple DRX configuration operations provided in an embodiment of the present application;

[0031] FIG6 is a second schematic diagram of multiple DRX configuration operations provided in an embodiment of the present application;

[0032] FIG7 is a schematic diagram of a communication processing device according to an embodiment of the present application;

[0033] FIG8 is a second schematic diagram of a communication processing device provided in an embodiment of the present application;

[0034] FIG9 is a schematic diagram of a terminal provided in an embodiment of the present application;

[0035] FIG10 is a schematic diagram of a network-side device provided in an embodiment of the present application;

[0036] FIG11 is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0038] The terms "first", "second", etc. in this 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 the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0039] The term "indication" in this application can be either 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, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0040] 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 this application are often used interchangeably, and the technology described 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 example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR system applications, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0041] To facilitate understanding of the embodiments of this application, the following technical points are first introduced:

[0042] 1. About Discontinuous Reception (DRX) in connected state.

[0043] In the connected state, DRX is used to save power. Terminals in DRX mode do not need to connect and monitor the control channel. However, if a terminal does not monitor the control channel for an extended period, data transmission latency will increase once data arrives. To balance power conservation and transmission latency, the fifth-generation (5G) media access control (MAC) supports two DRX cycles: long DRX-Cycle and short DRX-Cycle, depending on how long the terminal monitors the channel, as shown in Figure 1. If the terminal's data volume is predicted to be frequent or the service is latency-sensitive, the network can configure the terminal to use the short DRX cycle. If the terminal's data volume is predicted to be sparse and latency-insensitive, the network can configure the terminal to use only the long DRX cycle. To facilitate switching between the long and short DRX cycles, the long DRX cycle must be an integer multiple of the short DRX cycle, ensuring that the onDurations of the two cycles are aligned.

[0044] To support the DRX mechanism, the base station configures DRX-related timers and parameters for the terminal, including:

[0045] (1) Discontinuous reception short cycle (drx-ShortCycle): used to configure the short DRX cycle, the unit of the cycle is milliseconds;

[0046] (2) Discontinuous reception slot offset (drx-SlotOffset): The delay for the terminal to start the discontinuous reception duration timer (drx-onDurationTimer). This parameter sets the offset of the start time of DRX onDuration relative to the start of the subframe. The offset is an integer multiple of 1 / 32 milliseconds.

[0047] (3) Discontinuous Reception Short Cycle Timer (drx-ShortCycleTimer): This timer is used to control the duration of the short DRX cycle used by the terminal. The unit is an integer, i.e., the timer length is an integer multiple of the short cycle. The terminal enters a long cycle after a certain number of short cycles without receiving the Physical Downlink Control Channel (PDCCH). This timer is started when the drx-InactivityTimer expires and a short cycle is configured.

[0048] (4) drx-onDurationTimer: DRX continuous monitoring timer. During this timer, the terminal needs to continuously monitor the network's PDCCH control channel. This is the duration that the terminal (e.g., user equipment) UE monitors the PDCCH within a DRX cycle. Once started, it cannot be restarted.

[0049] (5) Discontinuous reception inactivity timer (drx-InactivityTimer): The duration of monitoring the PDCCH after receiving a PDCCH indicating a new transmission. This timer is started or restarted at the first symbol after the reception of the PDCCH indicating a new transmission (uplink (UL) or downlink (DL)). The timer is stopped when a discontinuous reception command medium access control element (DRX command MAC CE) is received.

[0050] (6) DRX Command MAC CE or Long DRX Command MAC CE: Both can stop the drx-InactivityTimer and drx-onDurationTimer, thus causing the UE to leave the active time. The Long DRX Command MAC CE can be used to stop the drx-ShortCycleTimer and enter Long DRX. For the DRX Command MAC CE, if short cycle DRX is configured, the drx-ShortCycleTimer is started or restarted, and the UE enters short cycle DRX. Otherwise, the UE enters long cycle DRX.

[0051] (7) Discontinuous Reception Downlink Hybrid Automatic Repeat Request Round Trip Timer (drx-HARQ-RTT-TimerDL) or Discontinuous Reception Uplink Hybrid Automatic Repeat Request Round Trip Timer (drx-HARQ-RTT-TimerUL): This timer is a per-HARQ process parameter that indicates the minimum time interval for waiting for retransmission. The timer is started at the first symbol after the end of the transmission of an Acknowledgement (ACK) or Negative Acknowledgement (NACK). During the timer's operation, the corresponding MAC does not monitor the PDCCH. When the timer expires, the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL of the corresponding Hybrid Automatic Repeat Request (HARQ) process is started.

[0052] (8) Discontinuous Reception Downlink Retransmission Timer (drx-RetransmissionTimerDL): This timer is a per-HARQ Process parameter that indicates the maximum number of PDCCH slots that the UE needs to continuously monitor in order to receive the desired downlink retransmission data. This timer starts at the first symbol after the drx-HARQ-RTT-TimerDL times out when the data in the corresponding HARQ process is not successfully decoded. This timer stops when a PDCCH indicating a downlink retransmission is received.

[0053] (9) Discontinuous Reception Uplink Retransmission Timer (drx-RetransmissionTimerUL): This timer is a per-HARQ Process parameter that indicates the maximum number of PDCCH slots that the UE monitors to receive an uplink retransmission grant. This timer starts at the first symbol after the drx-HARQ-RTT-TimerUL expires. It stops when an uplink retransmission grant is received.

[0054] 2. About Multiple DRX.

[0055] Extended Reality (XR) services include video data, audio data, and some control signaling and special data with control functions. Therefore, service flows with different periods may run in parallel. When there are multiple staggered and parallel service flows, configuring only one DRX configuration for each service cell cannot match the traffic characteristics of all service flows, which may result in lower energy-saving gains or long scheduling delays. Introducing multiple DRX configurations in the same service cell can solve this problem. However, multiple DRX configurations mean that the UE needs to monitor the Physical Downlink Control Channel (PDCCH) within the active time of each DRX configuration, which may result in wasted power consumption when the service volume is low.

[0056] FIG2 shows a block diagram of a wireless communication system applicable to embodiments of the present application. The wireless communication system includes a terminal 21 and a network-side device 22 .

[0057] The terminal 21 may be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: 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. In addition to the above-mentioned terminal devices, the terminal involved in this application can also be a chip within the terminal, such as a modem chip or a system-on-chip (SoC). It should be noted that the specific type of the terminal 21 is not limited in the embodiments of this application.

[0058] The network-side device 22 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 device, a radio access network (RAN), 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 (WLAN) access point (AS), or a wireless fidelity (WiFi) node. A base station may be referred to as a Node B (NB), an evolved Node B (eNB), the 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 art. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment 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.

[0059] 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 (MME), access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data storage (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( 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.

[0060] The communication processing method, apparatus, communication device, and readable storage medium provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0061] 3 , an embodiment of the present application provides a communication processing method, which is executed by a terminal. The specific steps include: step 301 and step 302 .

[0062] Step 301: The terminal receives configuration information, where the configuration information includes multiple DRX configurations, and the multiple DRX configurations are used for the same serving cell or the same serving cell list.

[0063] For example, the configuration information includes N DRX configurations, and M of the N DRX configurations can be applicable to the same service cell (M DRX configurations are associated with the same service cell), or the same service cell list (M DRX configurations are associated with the same service cell list), N is greater than or equal to M, and both N and M are greater than 1.

[0064] Optionally, the timer or parameter in the DRX configuration may include at least one of the following:

[0065] (1)drx-onDurationTimer;

[0066] (2)drx-SlotOffset;

[0067] (3)drx-InactivityTimer;

[0068] (4)drx-RetransmissionTimerDL;

[0069] (5)drx-RetransmissionTimerUL;

[0070] (6) Discontinuous reception long cycle start offset (drx-LongCycleStartOffset);

[0071] (7)drx-ShortCycle;

[0072] (8) Discontinuous reception short cycle timer (drx-ShortCycleTimer);

[0073] (9)drx-HARQ-RTT-TimerDL;

[0074] (10)drx-HARQ-RTT-TimerUL;

[0075] (11) Discontinuous reception secondary link retransmission timer (drx-RetransmissionTimerSL);

[0076] (12) Discontinuous reception secondary link hybrid automatic repeat request round trip time timer (drx-HARQ-RTT-TimerSL);

[0077] (13) Power saving wakeup (ps-Wakeup);

[0078] (14) Energy-saving transmission of other periodic channel state information (ps-TransmitOtherPeriodicCSI);

[0079] (15) Energy-saving transmission periodic layer 1 reference signal received power (ps-TransmitPeriodicL1-RSRP);

[0080] (16) Uplink Hybrid Automatic Repeat Request Mode (uplink HARQ-Mode).

[0081] It is understandable that the above contents included in different DRX configurations may be different, or the contents in different DRX configurations may be configured separately.

[0082] In one embodiment of the present application, during the operation of drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, or drx-RetransmissionTimerUL of any one of the multiple DRX configurations associated with the serving cell, the UE is in active time in the serving cell.

[0083] In one embodiment of the present application, multiple DRX configurations associated with a serving cell may periodically start a drx-OnDurationTimer according to their respective discontinuous reception cycles (DRX cycles) and drx-StartOffset configurations.

[0084] Step 302: If the terminal receives a PDCCH within the activation time of at least two DRX configurations overlapping, the terminal controls the drx-InactivityTimer of at least one DRX configuration among the at least two DRX configurations; or, if the terminal transmits on the scheduled resources, the terminal controls the timer in the DRX configuration corresponding to the transmission, or, the terminal controls the multiple DRX configurations according to the received DRX control signaling, or the DRX configuration corresponding to the DRX control signaling enters the inactive time.

[0085] Optionally, the scheduling resources may be obtained by receiving a PDCCH for scheduling uplink transmission or downlink transmission, or by granting scheduling resources based on a configuration of uplink transmission or downlink transmission.

[0086] In one embodiment of the present application, when any one of the multiple DRX configurations associated with the serving cell is in the active time, the terminal monitors the PDCCH on the serving cell. If the PDCCH indicates a new transmission (for example, a new downlink transmission or a new uplink transmission or a new sub-link transmission), the terminal starts or restarts the drx-InactivityTimer of the DRX configuration corresponding to the current active time at the first symbol after the PDCCH reception ends.

[0087] In one embodiment of the present application, if the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap, the terminal controls a drx-InactivityTimer of at least one DRX configuration of the at least two DRX configurations, including:

[0088] If the terminal receives a first PDCCH within a first time, where the first PDCCH is used to indicate a new transmission (for example, a new downlink transmission, a new uplink transmission, or a new sublink transmission), the terminal starts or restarts a first drx-InactivityTimer;

[0089] The first time includes an activation time when at least two DRX configurations associated with the serving cell overlap;

[0090] The first drx-InactivityTimer includes at least one of the following: the drx-InactivityTimers of the at least two DRX configurations, and the longest drx-InactivityTimer of the at least two DRX configurations.

[0091] For example, at least two DRX configurations include DRX configuration 1 and DRX2, and the terminal can start or restart the drx-InactivityTimer of DRX configuration 1 and DRX2; or, when the value of the drx-InactivityTimer of DRX1 is greater than the value of the drx-InactivityTimer of DRX2, the terminal can start or restart the drx-InactivityTimer of DRX1.

[0092] In one embodiment of the present application, if the terminal transmits on the scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, including:

[0093] If the terminal receives a Medium Access Control (MAC) Protocol Data Unit (PDU) in a configured downlink grant, the terminal performs a first operation on a first symbol after completing downlink Hybrid Automatic Repeat Request (HARQ) feedback transmission;

[0094] The first operation includes at least one of the following:

[0095] (1) Start or restart the drx-HARQ-RTT-TimerDL of multiple DRX configurations associated with the first HARQ process;

[0096] (2) Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the first HARQ process;

[0097] (3) Stop the drx-RetransmissionTimerDL of multiple DRX configurations associated with the first HARQ process;

[0098] The first HARQ is the HARQ corresponding to the downlink HARQ feedback.

[0099] Exemplarily, if the terminal receives a MAC PDU in a configured downlink assignment, the terminal starts the drx-HARQ-RTT-TimerDL of at least two DRX configurations corresponding to the HARQ process in the first symbol after completing the downlink HARQ feedback transmission, or starts the drx-HARQ-RTT-TimerDL with the smallest drx-HARQ-RTT-TimerDL value among at least two DRX configurations corresponding to the HARQ process; or stops the drx-RetransmissionTimerDL of at least two DRX configurations corresponding to the HARQ process.

[0100] In one embodiment of the present application, if the terminal transmits on the scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, including:

[0101] If the terminal transmits a MAC PDU in a configured uplink grant, the terminal performs a second operation in a first symbol after completing a first corresponding PUSCH transmission;

[0102] The second operation includes at least one of the following:

[0103] (1) Start or restart the drx-HARQ-RTT-TimerUL of multiple DRX configurations associated with the corresponding HARQ process;

[0104] (2) Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the corresponding HARQ process;

[0105] (3) Stop the drx-RetransmissionTimerUL of multiple DRX configurations associated with the corresponding HARQ process.

[0106] Exemplarily, if the MAC PDU is transmitted in the configured uplink grant resources and no listen before talk (LBT) failure indication is received from the underlying layer; or, if the serving cell is not configured with an uplink HARQ mode (uplinkHARQ-Mode), or is configured with uplinkHARQ-Mode and the corresponding HARQ process is configured as HARQ mode A (HARQ Mode A); the terminal starts the drx-HARQ-RTT-TimerUL of multiple DRX configurations associated with the corresponding HARQ process in the first symbol after completing the first corresponding PUSCH transmission, or starts the drx-HARQ-RTT-TimerUL with the smallest drx-HARQ-RTT-TimerUL value among the multiple DRX configurations associated with the corresponding HARQ process; or stops the drx-RetransmissionTimerUL of multiple DRX configurations associated with the corresponding HARQ process.

[0107] In one embodiment of the present application, if the terminal transmits on the scheduled resource, controlling, by the terminal, a timer in a DRX configuration corresponding to the transmission, includes:

[0108] If the terminal receives a second PDCCH within the second time, the terminal starts or restarts the at least two DRX configuration drx-HARQ-RTT-Timers or the shortest drx-HARQ-RTT-Timer among the at least two DRX configurations;

[0109] The second time includes activation times of at least two overlapping DRX configurations.

[0110] Optionally, the terminal starts or restarts the at least two DRX configuration drx-HARQ-RTT-Timers or the shortest drx-HARQ-RTT-Timer among the at least two DRX configurations, including:

[0111] The terminal performs a third operation on a first symbol after completing downlink HARQ feedback transmission;

[0112] The third operation includes at least one of the following:

[0113] (1) Start or restart the drx-HARQ-RTT-TimerDL of multiple DRX configurations associated with the third HARQ process;

[0114] (2) Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the third HARQ process;

[0115] (3) Stop the drx-RetransmissionTimerDL associated with multiple DRX configurations associated with the third HARQ process.

[0116] The third HARQ is the HARQ corresponding to the downlink HARQ feedback transmission.

[0117] Exemplarily, if any one of at least two DRX configurations is in the active time, the terminal monitors the second PDCCH of the serving cell; if the second PDCCH is used to indicate a downlink transmission, or the second PDCCH is used to indicate a single (one-shot) HARQ feedback, or the second PDCCH is used for the retransmission of a HARQ feedback, if at least two DRX configurations are in the active time at the same time, the terminal starts or restarts the drx-HARQ-RTT-TimerDL of multiple DRX configurations associated with the corresponding HARQ process in the first symbol after completing the downlink HARQ feedback transmission, or starts or restarts the drx-HARQ-RTT-TimerDL with the smallest value in the DRX configuration of the corresponding HARQ process; or the terminal stops the drx-RetransmissionTimerDL of the DRX configuration of the corresponding HARQ process.

[0118] In one embodiment of the present application, if the terminal transmits on the scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, including:

[0119] If the terminal receives a third PDCCH within a third time, the third time includes activation times of at least two overlapping DRX configurations, and the third PDCCH is used to indicate a new uplink transmission, the terminal performs a fourth operation in a first symbol after completing a first corresponding physical uplink shared channel (PUSCH) transmission.

[0120] The fourth operation includes at least one of the following:

[0121] (1) Start or restart the drx-HARQ-RTT-TimerUL of multiple DRX configurations associated with the fourth HARQ process;

[0122] (2) Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the fourth HARQ process;

[0123] (3) Stop the drx-RetransmissionTimerUL of multiple DRX configurations associated with the fourth HARQ process.

[0124] The fourth HARQ is the HARQ corresponding to the PUSCH transmission.

[0125] Exemplarily, if any one of multiple DRX configurations is in active time, the terminal monitors the PDCCH of the serving cell; if the PDCCH indicates a new uplink transmission; or, if the serving cell is not configured with uplinkHARQ-Mode or is configured with uplinkHARQ-Mode and the corresponding HARQ process is configured as HARQ Mode A; or if at least two DRX configurations are in active time at the same time, the terminal starts or restarts the drx-HARQ-RTT-TimerUL of multiple DRX configurations associated with the corresponding HARQ process in the first symbol after completing the first corresponding PUSCH transmission, or starts or restarts the drx-HARQ-RTT-TimerUL with the smallest drx-HARQ-RTT-TimerUL value in at least two DRX configurations of the corresponding HARQ process; or stops the drx-RetransmissionTimerUL of multiple DRX configurations associated with the corresponding HARQ process.

[0126] In one embodiment of the present application, if the drx-HARQ-RTT-TimerDL of any one of multiple DRX configurations times out and the data of the corresponding HARQ process is not successfully decoded, the terminal starts the drx-RetransmissionTimerDL of the corresponding DRX configuration in the first symbol after the drx-HARQ-RTT-TimerDL times out. If the drx-HARQ-RTT-TimerDL of at least two DRX configurations times out at the same time, the drx-RetransmissionTimerDL of at least two DRX configurations is started.

[0127] In one embodiment of the present application, if any one of the drx-HARQ-RTT-TimerUL in multiple DRX configurations times out, the terminal starts the drx-RetransmissionTimerUL of the corresponding DRX configuration in the first symbol after the drx-HARQ-RTT-TimerUL times out. If at least two drx-HARQ-RTT-TimerULs of the DRX configurations time out at the same time, the drx-RetransmissionTimerUL of at least two DRX configurations is started.

[0128] In one embodiment of the present application, if the drx-InactivityTimer of a certain DRX configuration times out; if the current DRX is configured with a short DRX cycle, the first symbol after the drx-InactivityTimer times out starts or restarts the drx-ShortCycleTimer of the corresponding DRX configuration; if at least two DRX configurations have drx-InactivityTimers that time out at the same time and are both configured with a short DRX cycle, the terminal starts or restarts the drx-ShortCycleTimers of the at least two DRX configurations; if the drx-ShortCycleTimer of a certain DRX configuration times out, the long DRX cycle of the corresponding DRX configuration is used.

[0129] In one embodiment of the present application, if the terminal transmits on the scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, including:

[0130] If the terminal receives a fourth PDCCH within a fourth time, determining, according to the scheduling type of the fourth PDCCH, a drx-HARQ-RTT-Timer of a controlled DRX configuration;

[0131] The fourth time is the time when the drx-RetransmissionTimer of the first DRX configuration set and the activation time of the second DRX configuration set overlap, and the first DRX configuration set and the second DRX configuration set include at least one DRX configuration of the multiple DRX configurations.

[0132] In one embodiment of the present application, determining, according to the scheduling type of the fourth PDCCH, a drx-HARQ-RTT-Timer of a controlled DRX configuration includes:

[0133] If the fourth PDCCH is used to indicate scheduling retransmission of a fifth HARQ process, and the identifier of the fifth HARQ process is the same as the identifier of the sixth HARQ process, and the sixth HARQ process is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the first DRX configuration set, then the terminal starts or restarts the drx-HARQ-RTT-Timer corresponding to the sixth HARQ process, or stops the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL of the sixth HARQ process;

[0134] The drx-HARQ-RTT-Timer includes drx-HARQ-RTT-TimerDL or drx-HARQ-RTT-TimerUL; and the drx-RetransmissionTimer includes drx-RetransmissionTimerDL or drx-RetransmissionTimerUL.

[0135] In one embodiment of the present application, determining, according to the scheduling type of the fourth PDCCH, a drx-HARQ-RTT-Timer of a controlled DRX configuration includes:

[0136] If the fourth PDCCH is used to indicate the scheduling of new transmission or retransmission of the seventh HARQ process, and the identifier of the seventh HARQ is different from the identifier of the eighth HARQ, the eighth HARQ is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the started first DRX set, then the terminal starts or restarts the drx-HARQ-RTT-TimerDL corresponding to all HARQ processes of the DRX configuration that are in the activation time, or the terminal stops the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL corresponding to all HARQ processes of the DRX configuration that are in the activation time.

[0137] In one embodiment of the present application, the terminal controls, according to the received DRX control signaling, a timer in a DRX configuration corresponding to the DRX control signaling, including:

[0138] The terminal receives first DRX control signaling;

[0139] The terminal performs a fifth operation according to the first DRX control signaling;

[0140] The fifth operation includes at least one of the following:

[0141] (1) Stop the drx-onDurationTimer or drx-InactivityTimer of each DRX configuration, where the first DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CEE, for example, stop the drx-onDurationTimer or drx-InactivityTimer of M DRX configurations;

[0142] (2) Stop the discontinuous reception short cycle timer drx-ShortCycleTimer of each DRX configuration, where the first DRX control signaling is Long DRX Command MAC CE, for example, stop the drx-ShortCycleTimers of M DRX configurations.

[0143] (3) In the first symbol after receiving the first DRX control signaling, start or restart the drx-ShortCycleTimers of the multiple DRX configurations, and use the short DRX cycles of the multiple DRX configurations, where the first DRX control signaling is a DRX Command MAC CE. For example, start or restart the drx-ShortCycleTimers of the M DRX configurations, and use the short DRX cycles of the M DRX configurations.

[0144] In an embodiment of the present application, if the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, a long discontinuous reception cycle (Long DRX cycle) of the first DRX configuration is used.

[0145] Exemplarily, if the terminal receives a DRX Command MAC CE or a Long DRX Command MAC CE, the terminal stops the drx-onDurationTimer and drx-InactivityTimer of each DRX configuration;

[0146] Exemplarily, if a DRX Command MAC CE is received, if multiple DRXs are configured with a short DRX cycle, the drx-ShortCycleTimers of the multiple DRX configurations are started or restarted in the first symbol after the DRX Command MAC CE is received, and the short DRX cycle of the corresponding DRX configuration is used. For the DRX configuration that is not configured with a short DRX cycle, the long DRX cycle is used;

[0147] Exemplarily, if a Long DRX Command MAC CE is received, the drx-ShortCycleTimer of each DRX configuration is stopped.

[0148] In one embodiment of the present application, the method further includes:

[0149] The terminal controls, according to the received DRX control signaling, a timer in a DRX configuration corresponding to the DRX control signaling, including:

[0150] The terminal receives second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations;

[0151] The terminal performs a sixth operation according to the second DRX control signaling;

[0152] The sixth operation includes at least one of the following:

[0153] (1) stopping the drx-onDurationTimer or drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE;

[0154] (2) stopping the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a Long DRX Command MAC CE;

[0155] (3) In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, and use the short DRX cycle of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is the DRX Command MAC CE.

[0156] Optionally, the first information may be a second DRX configuration identifier (Identity, ID) or index.

[0157] In one embodiment of the present application, if the one or more second DRX configurations include a third DRX configuration that is not configured with a short DRX cycle, then for the third DRX configuration, the Long DRX cycle of the third DRX configuration is used.

[0158] Exemplarily, the DRX Command MAC CE or Long DRX Command MAC CE carries a DRX configuration indication, and the terminal stops indicating one or more drx-onDurationTimer and drx-InactivityTimer of the fourth DRX configuration.

[0159] Exemplarily, if a DRX Command MAC CE is received, if one or more fourth DRX configurations indicated in the DRX Command MAC CE are configured with a short DRX cycle, then the drx-ShortCycleTimer of the one or more fourth DRX configurations indicated by the first symbol after receiving the DRX Command MAC CE is started or restarted, and the short DRX cycle of the corresponding DRX configuration is used; for the DRX configuration that is not configured with a short DRX cycle, the long DRX cycle is used;

[0160] Exemplarily, if a Long DRX Command MAC CE is received, the drx-ShortCycleTimer of one or more fourth DRX configurations indicated in the MAC CE is stopped.

[0161] In an embodiment of the present application, a terminal receives configuration information, where the configuration information includes multiple DRX configurations. If the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap, the terminal controls the drx-InactivityTimer of at least one of the at least two DRX configurations; or, if the terminal transmits on a scheduled resource, the terminal controls the timer in the DRX configuration corresponding to the transmission, or, the terminal controls the multiple DRX configurations according to the received DRX control signaling, or the DRX configuration corresponding to the DRX control signaling enters an inactive time, thereby meeting the power saving requirements of equipment supporting multi-stream services.

[0162] 4 , an embodiment of the present application provides a communication processing method, which is executed by a network-side device. The specific steps include: step 401 and step 402 .

[0163] Step 401: The network-side device sends configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list.

[0164] Step 402: The network side device sends a DRX control signaling, where the DRX control command is used to control the multiple DRX configurations, or to control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

[0165] For example, the configuration information includes N DRX configurations, and M of the N DRX configurations can be applicable to the same service cell (M DRX configurations are associated with the same service cell), or the same service cell list (M DRX configurations are associated with the same service cell list), N is greater than or equal to M, and both N and M are greater than 1.

[0166] In this embodiment, the DRX control command may be used to control M DRX configurations to enter the inactive time, or to control the DRX configuration corresponding to the DRX control signaling to enter the inactive time.

[0167] In one embodiment of the present application, the network side device sends the DRX control signaling, including:

[0168] The network-side device sends first DRX control signaling, where the first DRX control signaling is used to instruct the terminal to perform a fifth operation;

[0169] The fifth operation includes at least one of the following:

[0170] (1) Stopping the drx-onDurationTimer or drx-InactivityTimer of each DRX configuration, where the first DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE, for example, stopping the drx-onDurationTimer or drx-InactivityTimer of M DRX configurations;

[0171] (2) stopping the drx-ShortCycleTimer of each DRX configuration, where the first DRX control signaling is a LongDRX Command MAC CE, for example, stopping the drx-ShortCycleTimer of M DRX configurations;

[0172] (3) In the first symbol after receiving the first DRX control signaling, start or restart the drx-ShortCycleTimers of the multiple DRX configurations, and use the short DRX cycles of the multiple DRX configurations, where the first DRX control signaling is a DRX Command MAC CE. For example, start or restart the drx-ShortCycleTimers of the M DRX configurations, and use the short DRX cycles of the M DRX configurations.

[0173] In an embodiment of the present application, if the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, the long DRX cycle of the first DRX configuration is used.

[0174] In one embodiment of the present application, the network side device sends the DRX control signaling, including:

[0175] The network-side device sends second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations;

[0176] The second DRX control signaling is used to instruct execution of a sixth operation, where the sixth operation includes at least one of the following:

[0177] (1) stopping the drx-onDurationTimer or drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE;

[0178] (2) stopping the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a Long DRX Command MAC CE;

[0179] (3) In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, and use the short DRX cycle of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is the DRX Command MAC CE.

[0180] In an embodiment of the present application, if the one or more fourth DRX configurations include a fifth DRX configuration not configured with a short DRX cycle, then for the fifth DRX configuration, the long DRX cycle of the fifth DRX configuration is used.

[0181] In one embodiment of the present application, if the one or more second DRX configurations include a third DRX configuration that is not configured with a short DRX cycle, then for the third DRX configuration, the Long DRX cycle of the third DRX configuration is used.

[0182] In an embodiment of the present application, the network side device sends configuration information, and the configuration information includes multiple DRX configurations, and the multiple DRX configurations are used for the same service cell, or the same service cell list; the network side device sends DRX control signaling, and the DRX control command is used to control the multiple DRX configurations, or control the DRX configuration corresponding to the DRX control signaling to enter the inactive time, so as to meet the power saving requirements of the equipment supporting multi-stream services.

[0183] The following describes the implementation of the present application in conjunction with Examples 1 to 4.

[0184] Example 1: Operation of drx-InactivityTimer.

[0185] Step 0: The UE receives network configuration information, which includes two DRX configurations, DRX1 and DRX2, and is associated with serving cell #1. The drx-InactivityTimer of DRX2 is larger than that of DRX1. For example, the drx-InactivityTimer of DRX1 is 10 milliseconds (ms), and the drx-InactivityTimer of DRX2 is 20 ms.

[0186] Step 1: As shown in Figure 5.

[0187] -T1: The UE receives a PDCCH indicating a new transmission during the active time of DRX1, and the UE starts or restarts the drx-InactivityTimer of DRX1;

[0188] -T2: The UE receives a PDCCH indicating a new transmission during the DRX2 active time, and the UE starts or restarts the DRX2 drx-InactivityTimer;

[0189] -T3: The UE receives a PDCCH indicating a new transmission during the overlapping active time of DRX1 and DRX2. The UE starts or restarts the drx-InactivityTimer of DRX1 and DRX2, or the UE starts or restarts the drx-InactivityTimer with the largest value, such as starting or restarting the drx-InactivityTimer of DRX2.

[0190] Example 2: drx-HARQ-RTT-Timer and drx-RetransmissionTimer.

[0191] Step 0: The UE receives network configuration information, which includes two DRX configurations, DRX1 and DRX2, and is associated with Serving Cell #1. The drx-HARQ-RTT-TimerDL and drx-RetransmissionTimerDL of DRX1 and DRX2 are configured separately, where the drx-HARQ-RTT-TimerDL value of DRX2 is shorter than that of DRX1. For example, the drx-HARQ-RTT-TimerDL value of DRX1 is 20 symbols, and the drx-HARQ-RTT-TimerDL value of DRX2 is 10 symbols.

[0192] Step 1: As shown in Figure 5.

[0193] -T1 moment: The UE receives the PDCCH scheduling downlink transmission during the active time of DRX1. The UE starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process of DRX1. After the timer times out, the UE starts the drx-RetransmissionTimerDL of the corresponding HARQ process of DRX1.

[0194] -T2: The UE receives the PDCCH scheduling downlink transmission during the DRX2 active time. The UE starts the drx-HARQ-RTT-TimerDL of DRX2. After the timer expires, the UE starts the drx-RetransmissionTimerDL of DRX2.

[0195] -T3: The UE receives a PDCCH scheduling downlink transmission during the active time of the overlap between DRX1 and DRX2.

[0196] Method 1: UE starts drx-HARQ-RTT-TimerDL of the corresponding HARQ processes of DRX1 and DRX2 at the same time. When drx-HARQ-RTT-TimerDL of DRX1 times out, UE starts drx-RetransmissionTimerDL of the corresponding HARQ process of DRX1; when drx-HARQ-RTT-TimerDL of DRX2 times out, UE starts drx-RetransmissionTimerDL of the corresponding HARQ process of DRX2

[0197] Method 2: The UE turns on the drx-HARQ-RTT-TimerDL corresponding to the DRX with the shortest drx-HARQ-RTT-TimerDL value, such as turning on the drx-HARQ-RTT-TimerDL of the HARQ process corresponding to DRX2. When the drx-HARQ-RTT-TimerDL of DRX2 times out, the UE turns on the drx-RetransmissionTimerDL of the HARQ process corresponding to DRX2.

[0198] Example 3: The drx-RetransmissionTimer of DRX1 and the Active time of DRX2 overlap.

[0199] Step 0: The UE receives network configuration information, which includes two sets of DRX configurations, DRX1 and DRX2, and associates with Serving Cell #1.

[0200] Step 1: At time T1, the UE receives the PDCCH scheduling downlink for HARQ process #0. The UE starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process of DRX2. If the drx-HARQ-RTT-TimerDL times out and the data of the corresponding HARQ process is not successfully decoded, the UE starts the drx-RetransmissionTimerDL for the DRX2 corresponding HARQ process, see Figure 6.

[0201] Step 2: The UE receives the PDCCH at time T2. At this time, the drx-RetransmissionTimerDL of DRX2 is running and DRX1 is in the On duration.

[0202] - If the PDCCH schedules retransmission of HARQ process #0, the UE starts the drx-HARQ-RTT-TimerDL for HARQ process #0 in DRX2, or stops the drx-RetransmissionTimerDL for HARQ process #0;

[0203] -If the PDCCH schedules the initial transmission of HARQ process #0 or the transmission of other HARQ processes, the UE starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ processes of DRX1 and DRX2, or stops the drx-RetransmissionTimerDL for the corresponding HARQ processes.

[0204] Example 4: About DRX Command MAC CE.

[0205] Scenario 1: All DRX configurations perform the same operation

[0206] Step 0: The UE receives network configuration information, which includes two DRX configurations, DRX1 and DRX2, which are associated with Serving Cell #1. Both DRX1 and DRX2 are configured with a short DRX cycle. The drx-onDurationTimer, drx-InactivityTimer, and drx-ShortCycleTimer of DRX1 and DRX2 are configured separately.

[0207] Step 1:

[0208] -When the UE receives the DRX Command MAC CE or Long DRX Command MAC CE, the UE stops the drx-onDurationTimer and drx-InactivityTimer of DRX1 and DRX2;

[0209] -The UE receives the DRX Command MAC CE. The UE starts or restarts the drx-ShortCycleTimer of DRX1 and DRX2 in the first symbol after receiving the DRX Command MAC CE.

[0210] -The UE receives the Long DRX Command MAC CE and stops the drx-ShortCycleTimer of DRX1 and DRX2. Both DRX1 and DRX2 use the long DRX cycle.

[0211] Scenario 2: Specific DRX execution operation.

[0212] Step 0: The UE receives network configuration information, which includes two sets of DRX configurations, DRX1 and DRX2, which are associated with Serving Cell #1. Both DRX1 and DRX2 are configured with a short DRX cycle. The drx-onDurationTimer, drx-InactivityTimer, and drx-ShortCycleTimer of DRX1 and DRX2 are configured separately. DRX1 and DRX2 are associated with different configuration IDs or configuration indexes.

[0213] Step 1:

[0214] -The UE receives a DRX Command MAC CE or Long DRX Command MAC CE, which carries a DRX configuration ID or configuration index indication. The UE stops the drx-onDurationTimer and drx-InactivityTimer corresponding to the DRX configuration indicated in the MAC CE. For example, if the MAC CE indicates the configuration ID or index associated with DRX1, the UE stops the drx-onDurationTimer and drx-InactivityTimer for DRX1. Alternatively, if the MAC CE indicates the configuration ID or index associated with both DRX1 and DRX2, the UE stops the drx-onDurationTimer and drx-InactivityTimer for both DRX1 and DRX2.

[0215] -The UE receives the DRX Command MAC CE. The UE starts or restarts the drx-ShortCycleTimer of the DRX configuration indicated in the MAC CE in the first symbol after receiving the DRX Command MAC CE.

[0216] -When the UE receives the Long DRX Command MAC CE, the UE stops the drx-ShortCycleTimer of the DRX configuration indicated in the MAC CE and starts using the Long DRX cycle for the corresponding DRX configuration.

[0217] 7 , an embodiment of the present application provides a communication processing device, which is applied to a terminal. The device 700 includes:

[0218] A first receiving module 701 is configured to receive configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0219] The first processing module 702 is configured to control the drx-InactivityTimer of at least one of the at least two DRX configurations if the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap; or, if the terminal transmits on a scheduled resource, control the timer in the DRX configuration corresponding to the transmission, or, based on received DRX control signaling, control the multiple DRX configurations, or the DRX configuration corresponding to the DRX control signaling, to enter an inactive time.

[0220] In one embodiment of the present application, the first processing module 702 is further configured to:

[0221] If the terminal receives a MAC PDU in a configured downlink grant, performing a first operation on a first symbol after completing downlink hybrid automatic repeat request HARQ feedback transmission;

[0222] The first operation includes at least one of the following:

[0223] Start or restart the downlink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerDL in multiple DRX configurations associated with the first HARQ process;

[0224] Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the first HARQ process;

[0225] Stop the downlink discontinuous reception retransmission timer drx-RetransmissionTimerDL in the multiple DRX configurations associated with the first HARQ process;

[0226] The first HARQ is the HARQ corresponding to the downlink HARQ feedback transmission.

[0227] In one embodiment of the present application, the first processing module 702 is further configured to:

[0228] If the terminal transmits a MAC PDU in a configured uplink grant, performing a second operation in a first symbol after completing a first corresponding physical uplink shared channel (PUSCH) transmission;

[0229] The second operation includes at least one of the following:

[0230] Start or restart the uplink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerUL in multiple DRX configurations associated with the second HARQ process;

[0231] Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the second HARQ process;

[0232] Stop the uplink discontinuous reception retransmission timer drx-RetransmissionTimerUL in multiple DRX configurations associated with the second HARQ process;

[0233] The second HARQ is the HARQ corresponding to the PUSCH transmission.

[0234] In one embodiment of the present application, the first processing module 702 is further configured to:

[0235] If the terminal receives a second PDCCH within a second time, the second time includes an activation time of at least two overlapping DRX configurations, and the second PDCCH is used to indicate downlink transmission, or a single HARQ feedback, or a retransmission of HARQ feedback, performing a third operation in a first symbol after completing the downlink HARQ feedback transmission;

[0236] The third operation includes at least one of the following:

[0237] Start or restart drx-HARQ-RTT-TimerDL in multiple DRX configurations associated with the third HARQ process;

[0238] Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the third HARQ process;

[0239] Stopping drx-RetransmissionTimerDL in multiple DRX configurations associated with the third HARQ process;

[0240] The third HARQ is the HARQ corresponding to the downlink HARQ feedback transmission.

[0241] In one embodiment of the present application, the first processing module 702 is further configured to:

[0242] If the terminal receives a third PDCCH within a third time, the third time includes an activation time of at least two overlapping DRX configurations, and the third PDCCH is used to indicate a new uplink transmission, performing a fourth operation in a first symbol after completion of a first corresponding PUSCH transmission;

[0243] The fourth operation includes at least one of the following:

[0244] Start or restart the drx-HARQ-RTT-TimerUL in multiple DRX configurations associated with the fourth HARQ process;

[0245] Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the fourth HARQ process;

[0246] Stopping the drx-RetransmissionTimerUL in the multiple DRX configurations associated with the fourth HARQ process;

[0247] The fourth HARQ is the HARQ corresponding to the PUSCH transmission.

[0248] In one embodiment of the present application, the first processing module 702 is further configured to:

[0249] If the terminal receives a fourth PDCCH within a fourth time, determining a drx-HARQ-RTT-Timer of a controlled DRX configuration according to a scheduling type of the fourth PDCCH;

[0250] The fourth time is the time when the drx-RetransmissionTimer of the first DRX configuration set and the activation time of the second DRX configuration set overlap, and the first DRX configuration set and the second DRX configuration set include at least one DRX configuration of the multiple DRX configurations.

[0251] In one embodiment of the present application, the first processing module 702 is further configured to:

[0252] If the fourth PDCCH is used to indicate the scheduling of retransmission of a fifth HARQ process, and the identifier of the fifth HARQ process is the same as the identifier of the sixth HARQ process, and the sixth HARQ process is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the first DRX configuration set, then start or restart the drx-HARQ-RTT-Timer corresponding to the sixth HARQ process, or stop the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL of the sixth HARQ process;

[0253] The drx-HARQ-RTT-Timer includes drx-HARQ-RTT-TimerDL or drx-HARQ-RTT-TimerUL; and the drx-RetransmissionTimer includes drx-RetransmissionTimerDL or drx-RetransmissionTimerUL.

[0254] In one embodiment of the present application, the first processing module 702 is further configured to:

[0255] If the fourth PDCCH is used to indicate the scheduling of new transmission or retransmission of the seventh HARQ process, and the identifier of the seventh HARQ is different from the identifier of the eighth HARQ, the eighth HARQ is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the started first DRX set, then the terminal starts or restarts the drx-HARQ-RTT-TimerDL corresponding to all HARQ processes of the DRX configuration that are in the activation time, or the terminal stops the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL corresponding to all HARQ processes of the DRX configuration that are in the activation time.

[0256] In one embodiment of the present application, the first processing module 702 is further configured to: receive a first DRX control signaling; and perform a fifth operation according to the first DRX control signaling;

[0257] The fifth operation includes at least one of the following:

[0258] Stopping a discontinuous reception duration timer drx-onDurationTimer or a discontinuous reception inactivity timer drx-InactivityTimer of each DRX configuration, wherein the first DRX control signaling is a discontinuous reception command media access control layer control element DRX Command MAC CE or a long discontinuous reception command media access control layer control element Long DRX Command MAC CE;

[0259] Stopping a discontinuous reception short cycle timer drx-ShortCycleTimer of each DRX configuration, wherein the first DRX control signaling is a LongDRX Command MAC CE;

[0260] In the first symbol after receiving the first DRX control signaling, the drx-ShortCycleTimer of the multiple DRX configurations is started or restarted, and the short discontinuous reception cycle short DRX cycle of the multiple DRX configurations is used, where the first DRX control signaling is DRX Command MAC CE.

[0261] Optionally, if the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, a long discontinuous reception cycle Long DRX cycle of the first DRX configuration is used.

[0262] In one embodiment of the present application, the first processing module 702 is further configured to: receive second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations; and perform a sixth operation according to the second DRX control signaling;

[0263] The sixth operation includes at least one of the following:

[0264] Stopping a drx-onDurationTimer or a drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE;

[0265] Stopping the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a Long DRX Command MAC CE;

[0266] In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, and use the short DRX cycle of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is DRX Command MAC CE.

[0267] Optionally, if the one or more second DRX configurations include a third DRX configuration in which a short DRX cycle is not configured, for the third DRX configuration, the long DRX cycle of the third DRX configuration is used.

[0268] The device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0269] 8 , an embodiment of the present application provides a communication processing device, which is applied to a network-side device. The device 800 includes:

[0270] A first sending module 801 is configured to send configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are for the same serving cell or the same serving cell list;

[0271] The second sending module 802 is configured to send a DRX control signaling command, where the DRX control signaling command is used to control the multiple DRX configurations, or to control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

[0272] In one embodiment of the present application, the second sending module 802 is further configured to:

[0273] Sending first DRX control signaling, where the first DRX control signaling is used to instruct the terminal to perform a fifth operation;

[0274] The fifth operation includes at least one of the following:

[0275] Stopping a discontinuous reception duration timer drx-onDurationTimer or a discontinuous reception inactivity timer drx-InactivityTimer of each DRX configuration, wherein the first DRX control signaling is a discontinuous reception command media access control layer control element DRX Command MAC CE or a long discontinuous reception command media access control layer control element Long DRX Command MAC CE;

[0276] Stopping a discontinuous reception short cycle timer drx-ShortCycleTimer of each DRX configuration, wherein the first DRX control signaling is a LongDRX Command MAC CE;

[0277] In the first symbol after receiving the first DRX control signaling, the drx-ShortCycleTimer of the multiple DRX configurations is started or restarted, and the short discontinuous reception cycle short DRX cycle of the multiple DRX configurations is used, where the first DRX control signaling is DRX Command MAC CE.

[0278] Optionally, if the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, a long discontinuous reception cycle Long DRX cycle of the first DRX configuration is used.

[0279] In one embodiment of the present application, the second sending module 802 is further configured to:

[0280] sending second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations;

[0281] The second DRX control signaling is used to instruct execution of a sixth operation, where the sixth operation includes at least one of the following:

[0282] Stopping a drx-onDurationTimer or a drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE;

[0283] Stopping the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is a Long DRX Command MAC CE;

[0284] In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, and use the short DRX cycle of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is DRX Command MAC CE.

[0285] Optionally, if the one or more second DRX configurations include a third DRX configuration in which a short DRX cycle is not configured, for the third DRX configuration, the long DRX cycle of the third DRX configuration is used.

[0286] The device provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0287] FIG9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application. The terminal 900 includes, but is not limited to, at least some of the components of a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909, and a processor 910.

[0288] Those skilled in the art will appreciate that the terminal 900 may further include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0289] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 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 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0290] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 901 may transmit the data to the processor 910 for processing. Furthermore, the RF unit 901 may send uplink data to the network-side device. Typically, the RF unit 901 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0291] The memory 909 can be used to store software programs or instructions and various data. The memory 909 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 909 may include a volatile memory or a non-volatile memory, or the memory 909 may include a non-transient memory. Among them, the non-volatile memory or non-transient 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0292] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0293] The terminal provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0294] Please refer to Figure 10, which is a structural diagram of the network side device used in the embodiment of the present application.

[0295] As shown in Figure 10, the network side device 1000 includes: a processor 1001, a transceiver 1002, a memory 1003 and a bus interface, wherein the processor 1001 can be responsible for managing the bus architecture and general processing. The memory 1003 can store data used by the processor 1001 when performing operations.

[0296] In one embodiment of the present application, the network side device 1000 further includes: a program stored in the memory 1003 and executable on the processor 1001 , which implements the steps of the method shown in FIG. 4 above when executed by the processor 1001 .

[0297] In Figure 10 , the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 1001 and memory represented by memory 1003. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and are not further described herein. The bus interface provides an interface. The transceiver 1002 can be multiple components, including a transmitter and a receiver, providing a means for communicating with various other devices over a transmission medium.

[0298] Please refer to Figure 11, which is a structural diagram of a communication device applied in an embodiment of the present application. The communication device can be a terminal or a network-side device.

[0299] As shown in Figure 11, an embodiment of the present application also provides a communication device 1100, including a processor 1101 and a memory 1102, and the memory 1102 stores programs or instructions that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instruction is executed by the processor 1101 to implement the various steps of the method embodiment of Figure 3 above. When the communication device 1100 is a network side device, the program or instruction is executed by the processor 1101 to implement the various steps of the method embodiment of Figure 4 above and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0300] 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, the method of Figure 3 or Figure 4 and the various processes of the above-mentioned embodiments are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0302] 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 shown in Figure 3 or Figure 4 and the various method embodiments mentioned above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0303] 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.

[0304] An 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 shown in Figure 3 or Figure 4 and the various method embodiments described above, and can achieve the same technical effects. To avoid repetition, they are not described here.

[0305] An embodiment of the present application also provides a communication system, which includes a terminal and a network-side device. The terminal is used to execute the various processes shown in Figure 3 and the above-mentioned method embodiments, and the network-side device is used to execute the various processes shown in Figure 4 and the above-mentioned method embodiments, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0306] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising 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 statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments 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 the opposite 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.

[0307] Through the description of the above embodiments, 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-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0308] 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 this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A communication processing method, comprising: The terminal receives configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are used for the same serving cell or the same serving cell list; If the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap, the terminal controls a discontinuous reception inactivity timer drx-InactivityTimer of at least one DRX configuration of the at least two DRX configurations; Alternatively, if the terminal transmits on the scheduled resource, the terminal controls a timer in the DRX configuration corresponding to the transmission, Alternatively, the terminal controls the multiple DRX configurations according to the received DRX control signaling, or the DRX configuration corresponding to the DRX control signaling enters the inactive time.

2. The method according to claim 1, wherein: If the terminal receives a PDCCH within an activation time in which at least two DRX configurations overlap, the terminal controls a drx-InactivityTimer of at least one DRX configuration of the at least two DRX configurations, including: If the terminal receives a first PDCCH within a first time, and the first PDCCH is used to indicate a new transmission, the terminal starts or restarts a first drx-InactivityTimer; The first time includes activation times of at least two overlapping DRX configurations; The first drx-InactivityTimer includes at least one of the following: a drx-InactivityTimer in the at least two DRX configurations, and a longest drx-InactivityTimer in the at least two DRX configurations.

3. The method according to claim 1, wherein: If the terminal performs transmission on the scheduled resource, the terminal controls a timer in a DRX configuration corresponding to the transmission, including: If the terminal receives a media access control MAC protocol data unit PDU in a configured downlink grant, the terminal performs a first operation in a first symbol after completing downlink hybrid automatic repeat request HARQ feedback transmission; The first operation includes at least one of the following: Start or restart the downlink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerDL in multiple DRX configurations associated with the first HARQ process; Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the first HARQ process; Stopping the downlink discontinuous reception retransmission timer drx-RetransmissionTimerDL in the multiple DRX configurations associated with the first HARQ process; The first HARQ is the HARQ corresponding to the downlink HARQ feedback transmission.

4. The method according to claim 1, wherein: If the terminal performs transmission on the scheduled resource, the terminal controls a timer of a DRX configuration corresponding to the transmission, including: If the terminal transmits a MAC PDU in the configured uplink grant, the terminal completes the first corresponding physical The second operation is performed on the first symbol after the uplink shared channel PUSCH is transmitted; The second operation includes at least one of the following: Start or restart the uplink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerUL in multiple DRX configurations associated with the second HARQ process; Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the second HARQ process; Stop the uplink discontinuous reception retransmission timer drx-RetransmissionTimerUL in the multiple DRX configurations associated with the second HARQ process; The second HARQ is the HARQ corresponding to the PUSCH transmission.

5. The method according to claim 1, wherein: If the terminal performs transmission on the scheduled resource, the terminal controls a timer in a DRX configuration corresponding to the transmission, including: If the terminal receives a second PDCCH within a second time, the second time includes an activation time in which at least two DRX configurations overlap, and the second PDCCH is used to indicate downlink transmission, or a single HARQ feedback, or a retransmission of HARQ feedback, the terminal performs a third operation at a first symbol after completing the downlink HARQ feedback transmission; The third operation includes at least one of the following: Start or restart drx-HARQ-RTT-TimerDL in multiple DRX configurations associated with the third HARQ process; Start or restart the drx-HARQ-RTT-TimerDL with the smallest value among multiple DRX configurations associated with the third HARQ process; Stopping drx-RetransmissionTimerDL in a plurality of DRX configurations associated with the third HARQ process; The third HARQ is the HARQ corresponding to the downlink HARQ feedback transmission.

6. The method according to claim 1, wherein: If the terminal performs transmission on the scheduled resource, the terminal controls a timer in a DRX configuration corresponding to the transmission, including: If the terminal receives a third PDCCH within a third time, the third time includes activation times of at least two overlapping DRX configurations, and the third PDCCH is used to indicate a new uplink transmission, the terminal performs a fourth operation at the first symbol after completing the first corresponding PUSCH transmission; The fourth operation includes at least one of the following: Start or restart the drx-HARQ-RTT-TimerUL in multiple DRX configurations associated with the fourth HARQ process; Start or restart the drx-HARQ-RTT-TimerUL with the smallest value among multiple DRX configurations associated with the fourth HARQ process; Stopping drx-RetransmissionTimerUL in a plurality of DRX configurations associated with the fourth HARQ process; The fourth HARQ is the HARQ corresponding to the PUSCH transmission.

7. The method according to claim 1, wherein: If the terminal performs transmission on the scheduled resource, the terminal controls a timer in a DRX configuration corresponding to the transmission, including: If the terminal receives a fourth PDCCH within a fourth time, determining a drx-HARQ-RTT-Timer of a controlled DRX configuration according to a scheduling type of the fourth PDCCH; The fourth time is the time when the drx-RetransmissionTimer of the first DRX configuration set and the activation time of the second DRX configuration set overlap, and the first DRX configuration set and the second DRX configuration set include at least one DRX configuration of the multiple DRX configurations.

8. The method according to claim 7, wherein: Determining, according to the scheduling type of the fourth PDCCH, a drx-HARQ-RTT-Timer of a controlled DRX configuration, including: If the fourth PDCCH is used to indicate the scheduling of retransmission of the fifth HARQ process, and the identifier of the fifth HARQ process is the same as the identifier of the sixth HARQ process, and the sixth HARQ process is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the first DRX configuration set, the terminal starts or restarts the drx-HARQ-RTT-Timer corresponding to the sixth HARQ process, or stops the sixth HARQ process drx-RetransmissionTimerDL or drx-RetransmissionTimerUL; The drx-HARQ-RTT-Timer includes drx-HARQ-RTT-TimerDL or drx-HARQ-RTT-TimerUL; and the drx-RetransmissionTimer includes drx-RetransmissionTimerDL or drx-RetransmissionTimerUL.

9. The method according to claim 7, wherein: Determining, according to the scheduling type of the fourth PDCCH, a drx-HARQ-RTT-Timer of a controlled DRX configuration, including: If the fourth PDCCH is used to indicate the scheduling of new transmission or retransmission of the seventh HARQ process, and the identifier of the seventh HARQ is different from the identifier of the eighth HARQ, and the eighth HARQ is a HARQ process associated with the drx-RetransmissionTimer of one or more DRX configurations in the started first DRX set, then the terminal starts or restarts the drx-HARQ-RTT-TimerDL corresponding to all HARQ processes of the DRX configuration that are in the activation time, or the terminal stops the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL corresponding to all HARQ processes of the DRX configuration that are in the activation time.

10. The method according to claim 1, wherein: The terminal controls, according to the received DRX control signaling, a timer in a DRX configuration corresponding to the DRX control signaling, including: The terminal receives a first DRX control signaling; The terminal performs a fifth operation according to the first DRX control signaling; The fifth operation includes at least one of the following: Stopping a discontinuous reception duration timer drx-onDurationTimer or a discontinuous reception inactivity timer drx-InactivityTimer configured for each DRX, wherein the first DRX control signaling is a discontinuous reception command media access control layer control element DRX Command MAC CE or a long discontinuous reception command media access control layer control element Long DRX Command MAC CE; Stopping a discontinuous reception short cycle timer drx-ShortCycleTimer configured for each DRX, wherein the first DRX control signaling is a LongDRX Command MAC CE; In the first symbol after receiving the first DRX control signaling, the drx-ShortCycleTimer of the multiple DRX configurations is started or restarted, and the short discontinuous reception cycle short DRX cycle of the multiple DRX configurations is used, and the first DRX control signaling is DRX Command MAC CE.

11. The method according to claim 10, wherein: If the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, a long discontinuous reception cycle Long DRX cycle of the first DRX configuration is used.

12. The method according to claim 1, wherein: The terminal controls, according to the received DRX control signaling, a timer in a DRX configuration corresponding to the DRX control signaling, including: The terminal receives second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations; The terminal performs a sixth operation according to the second DRX control signaling; The sixth operation includes at least one of the following: Stop the drx-onDurationTimer or drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is DRX Command MAC CE or Long DRX Command MAC CE; Stop the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is Long DRX Command MAC CE; In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, use the short DRX cycle of one or more second DRX configurations indicated by the first information, and the second DRX control signaling is DRX Command MAC CE.

13. The method according to claim 12, wherein: If the one or more second DRX configurations include a third DRX configuration in which a short DRX cycle is not configured, for the third DRX configuration, the Long DRX cycle of the third DRX configuration is used.

14. A communication processing method, comprising: The network side device sends configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are used for the same serving cell or the same serving cell list; The network side device sends a DRX control signaling, where the DRX control command is used to control the multiple DRX configurations, or to control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

15. The method according to claim 14, wherein: The network side device sends the DRX control signaling, including: The network side device sends a first DRX control signaling, where the first DRX control signaling is used to instruct the terminal to perform a fifth operation; The fifth operation includes at least one of the following: Stopping a drx-onDurationTimer or a drx-InactivityTimer of each DRX configuration, wherein the first DRX control signaling is a DRX Command MAC CE or a Long DRX Command MAC CE; Stop the drx-ShortCycleTimer of each DRX configuration, wherein the first DRX control signaling is LongDRX Command MAC CE; In the first symbol after receiving the first DRX control signaling, the drx-ShortCycleTimer of the multiple DRX configurations is started or restarted, and the short DRX cycle of the multiple DRX configurations is used. The signaling is DRX Command MAC CE.

16. The method according to claim 15, wherein: If the multiple DRX configurations include a first DRX configuration in which a short DRX cycle is not configured, for the first DRX configuration, the Long DRX cycle of the first DRX configuration is used.

17. The method according to claim 14, wherein: The network side device sends the DRX control signaling, including: The network side device sends a second DRX control signaling, where the second DRX control signaling includes first information, where the first information is used to indicate one or more second DRX configurations; The second DRX control signaling is used to instruct execution of a sixth operation, and the sixth operation includes at least one of the following: Stop the drx-onDurationTimer or drx-InactivityTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is DRX Command MAC CE or Long DRX Command MAC CE; Stop the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, where the second DRX control signaling is Long DRX Command MAC CE; In the first symbol after receiving the second DRX control signaling, start or restart the drx-ShortCycleTimer of one or more second DRX configurations indicated by the first information, use the short DRX cycle of one or more second DRX configurations indicated by the first information, and the second DRX control signaling is DRX Command MAC CE.

18. The method according to claim 17, wherein: If the one or more second DRX configurations include a third DRX configuration in which a short DRX cycle is not configured, for the third DRX configuration, the Long DRX cycle of the third DRX configuration is used.

19. A communication processing device, comprising: A first receiving module is configured to receive configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are used for the same serving cell or the same serving cell list; The first processing module is used to control the drx-InactivityTimer of at least one DRX configuration among the at least two DRX configurations if the terminal receives a PDCCH within the activation time when at least two DRX configurations overlap; or, if the terminal transmits on the scheduled resources, control the timer in the DRX configuration corresponding to the transmission, or, according to the received DRX control signaling, control the multiple DRX configurations, or the DRX configuration corresponding to the DRX control signaling to enter the inactive time.

20. A communication processing device, comprising: A first sending module, configured to send configuration information, where the configuration information includes multiple DRX configurations, where the multiple DRX configurations are used for the same serving cell or the same serving cell list; The second sending module is used to send DRX control signaling, where the DRX control command is used to control the multiple DRX configurations, or control the DRX configuration corresponding to the DRX control signaling to enter an inactive time.

21. A terminal comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction implements the steps of the method according to any one of claims 1 to 13 when executed by the processor.

22. A network side device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method as claimed in any one of claims 14 to 18.

23. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor of a terminal, implements the steps of the method according to any one of claims 1 to 18.

Images