CN111050423B

CN111050423B - Discontinuous reception processing method and terminal

Info

Publication number: CN111050423B
Application number: CN201811198615.4A
Authority: CN
Inventors: 莫毅韬; 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-10-15
Filing date: 2018-10-15
Publication date: 2022-01-04
Anticipated expiration: 2038-10-15
Also published as: CN111050423A

Abstract

The invention discloses a processing method and a terminal for discontinuous reception, wherein the method comprises the following steps: under the condition that network equipment configures cross-carrier scheduling for a terminal, starting a DRX timer in target DRX configuration after monitoring a Physical Downlink Control Channel (PDCCH) within the activation time of a Discontinuous Reception (DRX) cycle; the PDCCH is used for scheduling or authorizing data transmission of the terminal in the scheduled cell, the target DRX configuration is associated with the scheduling cell, the scheduling cell is a cell transmitting the PDCCH, or the target DRX configuration is associated with the scheduled cell. When the embodiment of the invention is scheduled in a cross-carrier mode, the terminal can determine which DRX configuration timer should be started in uplink and downlink transmission, thereby ensuring that a plurality of independent DRX configurations are processed correctly.

Description

Discontinuous reception processing method and terminal

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a processing method and a terminal for discontinuous reception.

Background

The Discontinuous Reception (DRX) mechanism may allow a terminal in a Radio Resource Control (RRC) Connected state (Connected) to monitor a Physical Downlink Control Channel (PDCCH) subframe only at certain times of a DRX cycle (cycle), thereby achieving balance between scheduling flexibility and power saving. As shown in fig. 1, the DRX cycles are divided into consecutive DRX cycles in the time domain, and each DRX cycle includes an On Duration (On Duration) and a sleep Duration (Opportunity for DRX). The terminal monitors the PDCCH for a long duration, and does not monitor the PDCCH during a sleep period to save power.

When the channel quality of some cells is not good or the channel blocking rate is high, the network device may configure cross-carrier scheduling for the terminal. The cross-carrier scheduling is to configure a control channel in a cell with better channel quality (i.e. a scheduling cell, such as a primary cell), and schedule data of other cells (i.e. scheduled cells, such as a secondary cell) in a cross-carrier manner. The scheduling cell may schedule its own cell and one or more other scheduled cells than itself. The scheduled cell has no PDCCH and can only be scheduled by the scheduling cell. When the network device configures cross-carrier scheduling, if the network device configures a plurality of independent DRX configurations for the terminal, and an MAC entity of the terminal performs uplink/downlink transmission, the terminal cannot determine how to perform processing of the plurality of independent DRX configurations, and thus cannot determine parameters of a timer related to DRX.

Disclosure of Invention

The embodiment of the invention provides a discontinuous reception processing method and a terminal, which aim to solve the configuration problem of DRX (discontinuous reception) of cross-carrier scheduling.

In a first aspect, an embodiment of the present invention provides a method for processing discontinuous reception, which is applied to a terminal, and includes:

under the condition that a terminal is configured with cross-carrier scheduling, after a Physical Downlink Control Channel (PDCCH) is monitored in the activation time of a Discontinuous Reception (DRX) cycle, starting a DRX timer in target DRX configuration;

the PDCCH is used for data transmission of a scheduling terminal in a scheduled cell, the target DRX configuration is associated with the scheduling cell, the scheduling cell is a cell which sends the PDCCH, or the target DRX configuration is associated with the scheduled cell.

In a second aspect, an embodiment of the present invention further provides a terminal, including:

a starting module, configured to start a DRX timer in a target DRX configuration after monitoring a physical downlink control channel PDCCH within an activation time of a discontinuous reception DRX cycle when a terminal is configured with cross-carrier scheduling;

In a third aspect, an embodiment of the present invention provides a terminal, where the terminal includes a processor, a memory, and a computer program stored in the memory and running on the processor, and when the computer program is executed by the processor, the steps of the processing method for discontinuous reception are implemented.

In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements the steps of the processing method for discontinuous reception described above.

Thus, when the terminal of the embodiment of the invention performs cross-carrier scheduling, the terminal can determine which DRX configuration timer should be started in uplink and downlink transmission, so as to determine parameters of the relevant timers and ensure that a plurality of single DRX configurations are correctly processed.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.

Figure 1 shows a schematic time domain diagram of a DRX cycle;

fig. 2 shows a block diagram of a mobile communication system to which an embodiment of the present invention is applicable;

fig. 3 is a flow chart illustrating a processing method of discontinuous reception according to an embodiment of the present invention;

fig. 4 is a schematic block diagram of a terminal according to an embodiment of the present invention;

fig. 5 shows a block diagram of a terminal according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In the description and in the claims "and/or" means at least one of the connected objects.

The techniques described herein are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various 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), and other systems. The terms "system" and "network" are often used interchangeably. The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes the NR system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications.

The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Referring to fig. 2, fig. 2 is a block diagram of a wireless communication system to which an embodiment of the present invention is applicable. The wireless communication system includes a terminal 21 and a network device 22. The terminal 21 may also be referred to as a terminal Device or a User Equipment (UE), where the terminal 21 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a vehicle-mounted Device, and the specific type of the terminal 21 is not limited in the embodiment of the present invention. The network device 22 may be a Base Station or a core network, wherein the Base Station may be a 5G or later-version Base Station (e.g., a gNB, a 5G NR NB, etc.), or a Base Station in other communication systems (e.g., an eNB, a WLAN access point, or other access points, etc.), wherein the Base Station may be referred to as a node B, an evolved node B, an access point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, or some other suitable terminology in the field, 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 invention, only the Base Station in the NR system is taken as an example, but does not limit the specific type of base station.

The base stations may communicate with the terminals 21 under the control of a base station controller, which may be part of the core network or some of the base stations in various examples. Some base stations may communicate control information or user data with the core network through a backhaul. In some examples, some of the base stations may communicate with each other, directly or indirectly, over backhaul links, which may be wired or wireless communication links. A wireless communication system may support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals on the multiple carriers simultaneously. For example, each communication link may be a multi-carrier signal modulated according to various radio technologies. Each modulated signal may be transmitted on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, and so on.

The base stations may communicate wirelessly with the terminals 21 via one or more access point antennas. Each base station may provide communication coverage for a respective coverage area. The coverage area of an access point may be divided into sectors that form only a portion of the coverage area. A wireless communication system may include different types of base stations (e.g., macro, micro, or pico base stations). The base stations may also utilize different radio technologies, such as cellular or WLAN radio access technologies. The base stations may be associated with the same or different access networks or operator deployments. The coverage areas of different base stations (including coverage areas of base stations of the same or different types, coverage areas utilizing the same or different radio technologies, or coverage areas belonging to the same or different access networks) may overlap.

The communication links in a wireless communication system may comprise an Uplink for carrying Uplink (UL) transmissions (e.g., from terminal 21 to network device 22) or a Downlink for carrying Downlink (DL) transmissions (e.g., from network device 22 to terminal 21). The UL transmission may also be referred to as reverse link transmission, while the DL transmission may also be referred to as forward link transmission. Downlink transmissions may be made using licensed frequency bands, unlicensed frequency bands, or both. Similarly, uplink transmissions may be made using licensed frequency bands, unlicensed frequency bands, or both.

An embodiment of the present invention provides a processing method for discontinuous reception, as shown in fig. 3, the method includes the following steps:

step 31: under the condition that the terminal is configured with cross-carrier scheduling, after a Physical Downlink Control Channel (PDCCH) is monitored in the Active Time (Active Time) of a Discontinuous Reception (DRX) cycle, a DRX timer in a target DRX configuration is started.

Wherein, the activation time of the DRX period includes but is not limited to: duration, and/or a DRX duration timer (DRX-onDurationTimer), a DRX deactivation timer (DRX-inactivity timer), a downlink discontinuous reception retransmission timer (DRX-retransmission timer), an uplink discontinuous reception retransmission timer (DRX-retransmission timer ul), a contention resolution timer (ra-ContentionResolutionTimer), etc. The PDCCH is used for scheduling or authorizing data transmission of the terminal in the scheduled cell, and the target DRX configuration may be associated with the scheduling cell, where the scheduling cell is a cell that sends the PDCCH, that is, a cell where the PDCCH monitored by the terminal is located, that is, the target DRX configuration is associated with the cell where the PDCCH is monitored. The target DRX configurations may be in one-to-one correspondence with the scheduling cells, that is, the network device configures respective DRX configurations for each scheduling cell, and the DRX configurations corresponding to different scheduling cells may be the same or different. The corresponding relationship between the target DRX configuration and the scheduling cell may be one-to-many, that is, the network device configures the same DRX configuration for multiple scheduling cells, for example, the network device configures one DRX configuration for the licensed band and configures another DRX configuration for the unlicensed band, so that all scheduling cells in the licensed band correspond to the same DRX configuration, and all scheduling cells in the unlicensed band correspond to the same DRX configuration. The correspondence of the target DRX configuration to the scheduling cell may also be many-to-one, i.e. the network device configures multiple DRX configurations for one scheduling cell, for example, the target DRX configuration may be associated with a Bandwidth Part (BWP) of the scheduling cell, and when multiple BWPs are included in the scheduling cell, one BWP corresponds to one DRX configuration, where the DRX configurations corresponding to different BWPs may be the same or different.

Alternatively, the target DRX configuration may be associated with a scheduled cell, which is a cell that receives downlink data or transmits uplink data. The PDCCH may be used for scheduling downlink data transmission and may also be used for performing uplink grant data transmission. Accordingly, the target DRX configuration may be associated with a cell in which Downlink data, such as a Physical Downlink Shared Channel (PDSCH), is received, or associated with a cell in which Uplink data, such as a Physical Uplink Shared Channel (PUSCH), is transmitted. The target DRX configurations may be in one-to-one correspondence with the scheduled cells, that is, the network device configures respective DRX configurations for each scheduled cell, and the DRX configurations corresponding to different scheduled cells may be the same or different. The corresponding relationship between the target DRX configuration and the scheduled cell may be one-to-many, that is, the network device configures the same DRX configuration for multiple scheduled cells, for example, the network device configures one DRX configuration for the licensed band and configures another DRX configuration for the unlicensed band, then the scheduled cells in all licensed bands correspond to the same DRX configuration, and the scheduled cells in all unlicensed bands correspond to the same DRX configuration. The correspondence of the target DRX configuration to the scheduled cell may also be many-to-one, i.e. the network device configures multiple DRX configurations for one scheduled cell, for example, the target DRX configuration may be associated with BWP of the scheduled cell, and when multiple BWPs are included in the scheduled cell, one BWP corresponds to one DRX configuration, where the DRX configurations corresponding to different BWPs may be the same or different.

In the embodiment of the invention, when network equipment configures cross-carrier scheduling for a terminal, the terminal monitors a Physical Downlink Control Channel (PDCCH) within the activation time of a DRX period during uplink and downlink data transmission, and then starts a DRX timer in target DRX configuration. The target DRX configuration may be associated with a scheduling cell or a scheduled cell, and thus, in cross-carrier scheduling, the terminal may select a DRX timer in the target DRX configuration among a plurality of DRX with independent configurations when performing uplink and downlink data transmission. Therefore, when the cross-carrier scheduling is carried out, the terminal can determine which DRX configuration timer should be started in the uplink and downlink transmission, and the DRX transmission is ensured to be normally carried out. The following embodiments of the present invention will further explain the uplink and downlink transmission in combination with different scenarios.

1. Taking PDCCH for scheduling downlink data transmission as an example.

Step 31 comprises: a first timer associated with a Hybrid Automatic Repeat Request (HARQ) process in the target DRX configuration is started at a first OFDM symbol (e.g., a start time) after the response information associated with the downlink data is sent.

Wherein, the HARQ process corresponds to downlink data, and during the data transmission process, there may be multiple HARQ processes simultaneously performed on one carrier (cell), where the HARQ process refers to one or more processes related to downlink data transmission. The parameter value of the first timer is determined from the target DRX configuration, and the PDCCH is not monitored during the timing period of the first timer. Alternatively, the first timer may be a downlink discontinuous reception hybrid automatic repeat request Round Trip Time (RTT) timer (drx-HARQ-RTT-TimerDL).

Assume that a current network device configures cross-Carrier scheduling for a terminal, wherein a PDCCH is transmitted on BWP 1 with BWP Identification (ID) of 1 on serving cell 1 (i.e., scheduling cell) on Component Carrier 1 (CC 1) in a licensed band, the PDCCH can schedule serving cell 2 (i.e., scheduled cell) on Component Carrier CC 2 in an unlicensed band, and the terminal receives a PDSCH on BWP 2 with BWP ID of 2 on serving cell 2. Wherein serving cell 1 and DRX configuration 1 are associated, and serving cell 2 and DRX configuration 2 are associated. Alternatively, BWP 1 and DRX configuration 1 of serving cell 1 are associated and BWP 2 and DRX configuration 2 of serving cell 2 are associated.

If the terminal monitors a PDCCH indicating downlink data transmission, the terminal feeds back response information of the downlink data to the network device after receiving corresponding downlink data (e.g., PDSCH). The terminal starts a first timer (e.g., DRX-HARQ-RTT-TimerDL) associated with the HARQ process in DRX configuration 1 corresponding to the scheduling cell (i.e., the serving cell that monitors the PDCCH) at a first OFDM symbol (e.g., a start time) after sending the response information of the downlink data. Or, the terminal starts a first timer (e.g., DRX-HARQ-RTT-TimerDL) associated with the HARQ process in DRX configuration 2 corresponding to the scheduled cell (i.e., the serving cell receiving the PDSCH) at the start time of the first OFDM symbol after the response information of the downlink data is transmitted.

The response information of the downlink data may be sent through a Physical Uplink Control Channel (PUCCH), that is, a first timer is started at a starting time of a first OFDM symbol after the PUCCH corresponding to the downlink data is sent, where the first timer is DRX-HARQ-RTT-TimerDL associated with an HARQ process in a DRX configuration associated with a serving cell (or BWP) where the terminal monitors the PDCCH or receives the PDSCH. Wherein the parameters of the first timer comprise a duration parameter for determining a DRX-HARQ-RTT-TimerDL timer from the DRX configuration.

Further, after the step of starting the first timer related to the hybrid automatic repeat request HARQ process in the target DRX configuration, the method further comprises: and starting a second timer related to the HARQ process in the target DRX configuration under the condition that the first timer is overtime and the downlink data is not successfully decoded. And the parameter value of the second timer is determined from the target DRX configuration, and the PDCCH is monitored or downlink data is received during the timing period of the second timer. Alternatively, the second timer may be a downlink discontinuous reception retransmission timer (drx-retransmission timerdl).

When a DRX-HARQ-RTT-TimerDL timer corresponding to a HARQ process is expired and data transmitted in the HARQ process is not decoded successfully, e.g., when the HARQ process fails, the terminal starts a second timer (e.g., DRX-retransmission TimerDL) associated with the HARQ process in the target DRX configuration. It is worth noting that the first timer needs to be stopped when the second timer is started.

Further, when the starting condition of the second timer is satisfied, that is, when the first timer is out of time and the downlink data is not successfully decoded, the starting time of the second timer may be: and the first OFDM symbol after the first timer is overtime. That is, when the first timer expires and the downlink data is not successfully decoded, the second timer is started at the first OFDM symbol (e.g., the start time) after the first timer expires. The parameters of the first timer and the second timer may be obtained from the same DRX configuration, or may be obtained from different DRX configurations.

For example: the terminal monitors a PDCCH indicating downlink data transmission. Then, after receiving the corresponding downlink data (e.g. PDSCH), the terminal feeds back response information of the downlink data to the network device. And the terminal starts DRX-HARQ-RTT-TimerDL associated with the HARQ process in DRX configuration 1 corresponding to the scheduling cell at the starting time of the first OFDM symbol after the response information of the downlink data is sent. And under the condition that the DRX-HARQ-RTT-TimerDL is overtime and the related downlink data of the HARQ process is not successfully decoded, starting DRX-retransmission TimerDL in DRX configuration 1 or DRX configuration 2 at the starting moment of the first OFDM symbol after the DRX-HARQ-RTT-TimerDL is overtime. Or the terminal starts DRX-HARQ-RTT-TimerDL associated with the HARQ process in DRX configuration 2 corresponding to the scheduled cell at the start time of the first OFDM symbol after the response information of the downlink data is sent. And under the condition that the DRX-HARQ-RTT-TimerDL is overtime and the related downlink data of the HARQ process is not successfully decoded, starting DRX-retransmission TimerDL in DRX configuration 1 or DRX configuration 2 at the starting moment of the first OFDM symbol after the DRX-HARQ-RTT-TimerDL is overtime.

That is, in case that DRX-HARQ-RTT-TimerDL is expired and downlink data associated with a HARQ process is not successfully decoded, the terminal starts a DRX-retransmission TimerDL timer associated with the HARQ process in a DRX configuration associated with a scheduling cell (i.e., a serving cell that monitors a PDCCH) or a scheduled cell (i.e., a serving cell that receives a PDSCH) at a start time of a first OFDM symbol after the DRX-HARQ-RTT-TimerDL timer is expired, and determines a parameter value of the DRX-retransmission TimerDL timer from the DRX configuration.

Further, after the step of starting the second timer, the method further comprises: and if the PDCCH is monitored or downlink data is received, stopping the second timer. Taking drx-retransmission timerdl as an example, the terminal monitors the PDCCH or PDSCH during drx-retransmission timerdl timing, and stops drx-retransmission timerdl when drx-retransmission timerdl times out, monitors the PDCCH, or receives the PDSCH.

2. Take PDCCH for authorizing transmission of uplink data as an example.

Step 31 comprises: and starting a third timer related to the HARQ process in the target DRX configuration on the first OFDM symbol (such as the starting time) after uplink data is sent on a radio Resource Block (RB) of the uplink grant.

Wherein, the HARQ process corresponds to uplink data, and during the data transmission process, there may be multiple HARQ processes simultaneously performed on one carrier (cell), where the HARQ process refers to one or more processes related to uplink data transmission. And the parameter value of the third timer is determined from the target DRX configuration, and the PDCCH is not monitored during the timing period of the third timer. Optionally, the third timer is an uplink discontinuous reception hybrid automatic repeat request round trip time timer (drx-HARQ-RTT-timerll).

Assume that a current network device configures cross-Carrier scheduling for a terminal, wherein a PDCCH is transmitted on BWP 1 with BWP Identification (ID) of 1 on serving cell 1 (i.e., scheduling cell) on Component Carrier 1 (CC 1) in a licensed band, the PDCCH can schedule serving cell 2 (i.e., scheduled cell) on Component Carrier CC 2 in an unlicensed band, and the terminal transmits a PUSCH on BWP 2 with BWP ID of 2 on serving cell 2. Wherein serving cell 1 and DRX configuration 1 are associated, and serving cell 2 and DRX configuration 2 are associated. Alternatively, BWP 1 and DRX configuration 1 of serving cell 1 are associated and BWP 2 and DRX configuration 2 of serving cell 2 are associated.

If the terminal monitors a PDCCH indicating uplink transmission, the terminal starts a third timer (e.g., DRX-HARQ-RTT-timerll) associated with the HARQ process in DRX configuration 1 corresponding to the scheduling cell (i.e., the serving cell monitoring the PDCCH) at the start time of the first OFDM symbol after transmitting the uplink data. Or, the terminal starts a third timer (e.g., DRX-HARQ-RTT-timerll) associated with the HARQ process in DRX configuration 2 corresponding to the scheduled cell (i.e., the serving cell transmitting the PUSCH) at the start time of the first OFDM symbol after the uplink data is transmitted.

After monitoring a PDCCH indicating uplink transmission, the terminal starts, at the start time of the first OFDM symbol after the PUSCH corresponding to the PDCCH is first transmitted, to monitor DRX-HARQ-RTT-timerll associated with the HARQ process in a DRX configuration associated with a serving cell (or BWP) where the PDCCH or the PUSCH is transmitted, and may determine a duration parameter of a DRX-HARQ-RTT-timerll timer from the DRX configuration.

Further, the step of starting a third timer related to the HARQ process in the target DRX configuration further includes: and starting a fourth timer related to the HARQ process in the target DRX configuration under the condition that the third timer is overtime. And determining a parameter value of a fourth timer from the target DRX configuration, and monitoring the PDCCH during the timing period of the fourth timer. Optionally, the fourth timer may be an uplink discontinuous reception retransmission timer (drx-retransmission timer ul).

When the DRX-retransmission timerll timer corresponding to a HARQ process is over, the terminal starts a fourth timer (e.g., DRX-retransmission timerll) associated with the HARQ process in the target DRX configuration. It is worth noting that the third timer needs to be stopped when the fourth timer is started.

Further, when the starting condition of the fourth timer is satisfied, that is, in the case that the third timer times out, the starting time of the fourth timer may be: and the first OFDM symbol after the third timer is overtime. That is, the step of starting the fourth timer related to the HARQ process in the target DRX configuration includes: the fourth timer is started at the first OFDM symbol (e.g., the start time) after the third timer expires. The parameters of the third timer and the fourth timer may be obtained from the same DRX configuration, or may be obtained from different DRX configurations.

For example: the terminal monitors a PDCCH indicating uplink scheduled data transmission, and then starts DRX-HARQ-RTT-timerll associated with the HARQ process in DRX configuration 1 corresponding to the scheduling cell at the start time of the first OFDM symbol after transmitting corresponding uplink data. And under the condition that the DRX-HARQ-RTT-TimerUL is overtime, starting the DRX-retransmission TimerUL in the DRX configuration 1 or the DRX configuration 2 at the starting time of the first OFDM symbol after the DRX-HARQ-RTT-TimerUL is overtime. Or the terminal starts DRX-HARQ-RTT-timerll associated with the HARQ process in DRX configuration 2 corresponding to the scheduled cell at the start time of the first OFDM symbol after the uplink data is transmitted. And under the condition that the DRX-HARQ-RTT-TimerUL is overtime, starting the DRX-retransmission TimerUL in the DRX configuration 1 or the DRX configuration 2 at the starting time of the first OFDM symbol after the DRX-HARQ-RTT-TimerUL is overtime.

That is, the terminal starts a DRX-retransmission timerll timer associated with the HARQ process in a DRX configuration associated with a scheduling cell (i.e., a serving cell that monitors a PDCCH) or a scheduled cell (i.e., a serving cell that receives a PDSCH) at a start time of a first OFDM symbol after the DRX-HARQ-RTT-timerll timer expires, and may determine a parameter value of the DRX-retransmission timerll timer from the DRX configuration.

Further, the step of starting a fourth timer related to the HARQ process in the target DRX configuration further includes: and if the PDCCH is monitored, stopping the fourth timer. Taking drx-retransmission timerll as an example, the terminal keeps monitoring the PDCCH during drx-retransmission timerll timing, and stops drx-retransmission timerll when drx-retransmission timerll times out or monitors the PDCCH.

That is to say, when performing uplink/downlink data transmission, the terminal according to the embodiment of the present invention starts a DRX Timer associated with an HARQ process in a DRX configuration associated with a serving cell (scheduling cell) that monitors a PDCCH or a serving cell (scheduled cell) that receives a PDSCH or transmits a PUSCH, and determines a duration parameter of the DRX Timer corresponding to the HARQ process from the DRX configuration.

When the DRX-HARQ-RTT-Timer corresponding to a certain HARQ process is expired, starting a DRX-retransmission Timer associated with the HARQ process in a DRX configuration associated with a serving cell (scheduling cell) that monitors a PDCCH or a serving cell (scheduled cell) that receives a PDSCH or transmits a PUSCH, and determining a duration parameter of the DRX-retransmission Timer corresponding to the HARQ process from the DRX configuration.

In the discontinuous reception processing method of the embodiment of the invention, when the terminal is scheduled in a cross-carrier mode, the terminal can determine which DRX configuration timer should be started in uplink and downlink transmission, thereby ensuring that a plurality of independent DRX configurations are correctly processed and the DRX transmission is normally carried out.

The foregoing embodiments describe processing methods for discontinuous reception in different scenarios, and further describe terminals corresponding to the foregoing embodiments with reference to the accompanying drawings.

As shown in fig. 4, the terminal 400 according to the embodiment of the present invention can implement details of starting a DRX timer method in a target DRX configuration after monitoring a physical downlink control channel PDCCH within an active time of a discontinuous reception DRX cycle in the case that the terminal is configured with cross-carrier scheduling in the foregoing embodiment, and achieve the same effect, where the PDCCH is used for scheduling data transmission of the terminal in a scheduled cell, the target DRX configuration is associated with the scheduling cell, and the scheduling cell is a cell that transmits the PDCCH, or the target DRX configuration is associated with the scheduled cell. The terminal 400 specifically includes the following functional modules:

a starting module 410, configured to start a DRX timer in a target DRX configuration after monitoring a physical downlink control channel PDCCH within an active time of a discontinuous reception DRX cycle under a condition that a terminal is configured with cross-carrier scheduling;

the PDCCH is used for scheduling or authorizing data transmission of the terminal in the scheduled cell, the target DRX configuration is associated with the scheduling cell, the scheduling cell is a cell transmitting the PDCCH, or the target DRX configuration is associated with the scheduled cell.

Wherein, the PDCCH is used for scheduling downlink data transmission, and the starting module 410 includes:

a first starting submodule, configured to start a first timer associated with a hybrid automatic repeat request HARQ process in a target DRX configuration on a first OFDM symbol after response information associated with downlink data is sent;

the HARQ process corresponds to downlink data, the parameter value of the first timer is determined from the target DRX configuration, and the PDCCH is not monitored during the timing period of the first timer.

The first timer is a downlink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerDL.

Wherein, the starting module 410 further comprises:

a second starting submodule, configured to start a second timer related to the HARQ process in the target DRX configuration when the first timer is overtime and downlink data is not successfully decoded;

and the parameter value of the second timer is determined from the target DRX configuration, and the PDCCH is monitored or downlink data is received during the timing period of the second timer.

Wherein the second starter sub-module comprises:

and the first starting unit is used for starting the second timer on the first OFDM symbol after the first timer is overtime.

Wherein, the starting module 410 further comprises:

and the first stopping submodule is used for stopping the second timer if the PDCCH is monitored or the downlink data is received.

Wherein, the second timer is a downlink discontinuous reception retransmission timer drx-retransmission timerdl.

Wherein, the PDCCH is used for authorizing transmission of uplink data, and the starting module 410 further includes:

a third starting submodule, configured to start a third timer related to the HARQ process in the target DRX configuration on a first OFDM symbol after uplink data is sent on a radio resource block of the uplink grant;

and the HARQ process corresponds to uplink data, the parameter value of the third timer is determined from the target DRX configuration, and the PDCCH is not monitored during the timing period of the third timer.

Wherein, the third timer is an uplink discontinuous reception hybrid automatic repeat request round trip time timer drx-HARQ-RTT-TimerUL.

Wherein, the starting module 410 further comprises:

a fourth starting submodule, configured to start a fourth timer related to the HARQ process in the target DRX configuration when the third timer is overtime;

and the parameter value of the fourth timer is determined from the target DRX configuration, and the PDCCH is monitored during the timing period of the fourth timer.

Wherein the fourth starter sub-module comprises:

and the second starting unit is used for starting the fourth timer on the first OFDM symbol after the third timer is overtime.

Wherein, the starting module 410 further comprises:

and the second stopping submodule is used for stopping the fourth timer if the PDCCH is monitored.

Wherein, the fourth timer is an uplink discontinuous reception retransmission timer drx-retransmission timerll.

Wherein the target DRX configuration is associated with a bandwidth part BWP of the scheduling cell; alternatively, the target DRX configuration is associated with BWP of the scheduled cell.

It is worth pointing out that, when the terminal in the embodiment of the present invention performs cross-carrier scheduling, it can be determined which DRX configuration timer should be started in uplink and downlink transmission, so as to ensure that multiple individual DRX configurations are correctly processed, and ensure that DRX transmission is normally performed.

It should be noted that the division of each module of the above terminal is only a division of a logical function, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the determining module may be a processing element separately set up, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the function of the determining module is called and executed by a processing element of the apparatus. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), etc. For another example, when some of the above modules are implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can invoke the program code. As another example, these modules may be integrated together, implemented in the form of a system-on-a-chip (SOC).

To better achieve the above object, further, fig. 5 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present invention, where the terminal 50 includes, but is not limited to: a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the terminal configuration shown in fig. 5 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

Wherein, the radio frequency unit 51 is configured to receive and transmit data under the control of the processor 510;

a processor 510, configured to, in a case that a terminal is configured with cross-carrier scheduling, start a DRX timer in a target DRX configuration after monitoring a physical downlink control channel PDCCH within an active time of a discontinuous reception DRX cycle; the PDCCH is used for scheduling or authorizing data transmission of a terminal in a scheduled cell, the target DRX configuration is associated with the scheduling cell, the scheduling cell is a cell for sending the PDCCH, or the target DRX configuration is associated with the scheduled cell;

the terminal of the embodiment of the invention can determine which DRX configuration timer should be started in uplink and downlink transmission when the terminal is scheduled in a cross-carrier mode, thereby ensuring that a plurality of independent DRX configurations are processed correctly and ensuring that DRX transmission is carried out normally.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 51 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. Typically, the radio frequency unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 51 may also communicate with a network and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user via the network module 52, such as assisting the user in sending and receiving e-mails, browsing web pages, and accessing streaming media.

The audio output unit 53 may convert audio data received by the radio frequency unit 51 or the network module 52 or stored in the memory 59 into an audio signal and output as sound. Also, the audio output unit 53 may also provide audio output related to a specific function performed by the terminal 50 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 53 includes a speaker, a buzzer, a receiver, and the like.

The input unit 54 is used to receive audio or video signals. The input Unit 54 may include a Graphics Processing Unit (GPU) 541 and a microphone 542, and the Graphics processor 541 processes image data of a still picture or video obtained by an image capturing device (such as a camera) in a video capture mode or an image capture mode. The processed image frames may be displayed on the display unit 56. The image frames processed by the graphic processor 541 may be stored in the memory 59 (or other storage medium) or transmitted via the radio frequency unit 51 or the network module 52. The microphone 542 may receive sound, and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 51 in case of the phone call mode.

The terminal 50 also includes at least one sensor 55, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 561 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 561 and/or the backlight when the terminal 50 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 55 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be described in detail herein.

The display unit 56 is used to display information input by the user or information provided to the user. The Display unit 56 may include a Display panel 561, and the Display panel 561 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 57 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 57 includes a touch panel 571 and other input devices 572. The touch panel 571, also referred to as a touch screen, can collect touch operations by a user (e.g., operations by a user on the touch panel 571 or near the touch panel 571 using a finger, a stylus, or any suitable object or attachment). The touch panel 571 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 510, and receives and executes commands sent by the processor 510. In addition, the touch panel 571 can be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 57 may include other input devices 572 in addition to the touch panel 571. In particular, the other input devices 572 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 a joystick, which are not described herein.

Further, the touch panel 571 can be overlaid on the display panel 561, and when the touch panel 571 detects a touch operation on or near the touch panel 571, the touch panel is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 provides a corresponding visual output on the display panel 561 according to the type of the touch event. Although the touch panel 571 and the display panel 561 are shown in fig. 5 as two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 571 and the display panel 561 may be integrated to implement the input and output functions of the terminal, and the implementation is not limited herein.

The interface unit 58 is an interface for connecting an external device to the terminal 50. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 58 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 50 or may be used to transmit data between the terminal 50 and an external device.

The memory 59 may be used to store software programs as well as various data. The memory 59 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 59 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 510 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 59 and calling data stored in the memory 59, thereby performing overall monitoring of the terminal. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The terminal 50 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 via a power management system, so that functions of managing charging, discharging, and power consumption are performed via the power management system.

In addition, the terminal 50 includes some functional modules that are not shown, and will not be described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, which includes a processor 510, a memory 59, and a computer program stored in the memory 59 and capable of running on the processor 510, where the computer program, when executed by the processor 510, implements each process of the above discontinuous reception processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again. A terminal may be a wireless terminal or a wired terminal, and a wireless terminal may be a device providing voice and/or other service data connectivity to a user, a handheld device having a wireless connection function, or other processing devices connected to a wireless modem. Wireless terminals, which may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers having mobile terminals, such as portable, pocket, hand-held, computer-included, or vehicle-mounted mobile devices, may communicate with one or more core networks via a Radio Access Network (RAN), which may exchange language and/or data with the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). A wireless Terminal may also be referred to as a system, a Subscriber Unit (Subscriber Unit), a Subscriber Station (Subscriber Station), a Mobile Station (Mobile), a Remote Station (Remote Station), a Remote Terminal (Remote Terminal), an Access Terminal (Access Terminal), a User Terminal (User Terminal), a User Agent (User Agent), and a User Device or User Equipment (User Equipment), which are not limited herein.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the discontinuous reception processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.

Claims

1. A processing method of discontinuous reception is applied to a terminal, and is characterized by comprising the following steps:

under the condition that the terminal is configured with cross-carrier scheduling, after a Physical Downlink Control Channel (PDCCH) is monitored in the activation time of a Discontinuous Reception (DRX) cycle, starting a DRX timer in a target DRX configuration;

wherein the PDCCH is used for scheduling or authorizing data transmission of the terminal in a scheduled cell, the target DRX configuration is associated with a scheduling cell, the scheduling cell is a cell for transmitting the PDCCH, or the target DRX configuration is associated with the scheduled cell;

the PDCCH is used for scheduling downlink data transmission;

the step of starting a DRX timer in the target DRX configuration includes:

starting a first timer related to a hybrid automatic repeat request (HARQ) process in the target DRX configuration on a first OFDM symbol after the response information related to the downlink data is sent;

or

The PDCCH is used for authorizing transmission of uplink data;

the step of starting a DRX timer in the target DRX configuration includes:

and starting a third timer related to the HARQ process in the target DRX configuration on the first OFDM symbol after the uplink data is sent on the wireless resource block of the uplink grant.

2. The method of claim 1, wherein the HARQ process corresponds to the downlink data, a parameter value of the first timer is determined from the target DRX configuration, and the PDCCH is not monitored during a timing period of the first timer.

3. The method of claim 2, wherein the first timer is a downlink HARQ round trip time timer (drx-HARQ-RTT-TimerDL).

4. The method for handling discontinuous reception according to claim 2, wherein after the step of starting the first timer related to the hybrid automatic repeat request HARQ process in the target DRX configuration, the method further comprises:

starting a second timer related to the HARQ process in the target DRX configuration under the condition that the first timer is overtime and the downlink data is not successfully decoded;

and the parameter value of the second timer is determined from the target DRX configuration, and the PDCCH is monitored or the downlink data is received during the timing period of the second timer.

5. The method for handling discontinuous reception according to claim 4, wherein the step of starting the second timer related to the HARQ process in the target DRX configuration comprises:

and starting the second timer on the first OFDM symbol after the first timer is overtime.

6. The method for handling discontinuous reception according to claim 4, wherein after the step of starting the second timer related to the HARQ process in the target DRX configuration, the method further comprises:

and stopping the second timer if the PDCCH is monitored or the downlink data is received.

7. The method of claim 4, wherein the second timer is a downlink DRX retransmission timer (drx-retransmission TimerDL).

8. The method of claim 1, wherein the HARQ process corresponds to the uplink data, a parameter value of the third timer is determined from the target DRX configuration, and the PDCCH is not monitored during a timing period of the third timer.

9. The method of claim 8, wherein the third timer is an uplink drx hybrid automatic repeat request round trip time timer drx-HARQ-RTT-timerll.

10. The method for handling discontinuous reception according to claim 8, wherein after the step of starting the third timer related to the HARQ process in the target DRX configuration, the method further comprises:

starting a fourth timer in the target DRX configuration related to the HARQ process if the third timer times out;

11. The method for handling discontinuous reception according to claim 10, wherein the step of starting a fourth timer related to the HARQ process in the target DRX configuration comprises:

and starting the fourth timer on the first OFDM symbol after the third timer is overtime.

12. The method for handling discontinuous reception according to claim 10, wherein after the step of starting a fourth timer related to the HARQ process in the target DRX configuration, the method further comprises:

and if the PDCCH is monitored, stopping the fourth timer.

13. The drx processing method of claim 10, wherein the fourth timer is an uplink drx retransmission timer drx-retransmission timerll.

14. The method for handling discontinuous reception according to any of claims 1 to 13, wherein the target DRX configuration is associated with a bandwidth portion BWP of the scheduling cell; alternatively, the target DRX configuration is associated with BWP of the scheduled cell.

15. A terminal, comprising:

a starting module, configured to start a DRX timer in a target DRX configuration after monitoring a physical downlink control channel PDCCH within an activation time of a discontinuous reception DRX cycle when the terminal is configured with cross-carrier scheduling;

the PDCCH is configured to schedule downlink data transmission, and the starting module includes:

a first starting sub-module, configured to start a first timer associated with a hybrid automatic repeat request HARQ process in the target DRX configuration on a first OFDM symbol after sending the response information associated with the downlink data;

or

The PDCCH is configured to authorize transmission of uplink data, and the starting module further includes:

a third starting sub-module, configured to start a third timer related to the HARQ process in the target DRX configuration on a first OFDM symbol after the uplink data is sent on a radio resource block of an uplink grant.

16. The terminal of claim 15, wherein the HARQ process corresponds to the downlink data, wherein a parameter value of the first timer is determined from the target DRX configuration, and wherein the PDCCH is not monitored during timing of the first timer.

17. The terminal of claim 16, wherein the first timer is a downlink drx hybrid automatic repeat request round trip time timer (drx-HARQ-RTT-TimerDL).

18. The terminal of claim 16, wherein the initiating module further comprises:

a second starting submodule, configured to start a second timer related to the HARQ process in the target DRX configuration when the first timer is overtime and the downlink data is not successfully decoded;

19. The terminal of claim 18, wherein the second initiator sub-module comprises:

a first starting unit, configured to start the second timer on a first OFDM symbol after the first timer expires.

20. The terminal of claim 18, wherein the enabling module further comprises:

21. The terminal of claim 18, wherein the second timer is a downlink drx retransmission timer drx-retransmission timerdl.

22. The terminal of claim 15, wherein the HARQ process corresponds to the uplink data, wherein a parameter value of the third timer is determined from the target DRX configuration, and wherein the PDCCH is not monitored during the timing of the third timer.

23. The terminal of claim 22, wherein the third timer is an uplink drx hybrid automatic repeat request round trip time timer drx-HARQ-RTT-timerll.

24. The terminal of claim 22, wherein the initiating module further comprises:

25. The terminal of claim 24, wherein the fourth start-up sub-module comprises:

a second starting unit, configured to start the fourth timer on the first OFDM symbol after the third timer expires.

26. The terminal of claim 24, wherein the enabling module further comprises:

27. The terminal of claim 24, wherein the fourth timer is an uplink drx retransmission timer drx-retransmission timerll.

28. Terminal according to any of claims 15 to 27, wherein the target DRX configuration is associated with a bandwidth part BWP of the scheduling cell; alternatively, the target DRX configuration is associated with BWP of the scheduled cell.

29. A terminal characterized in that it comprises a processor, a memory and a computer program stored on the memory and running on the processor, which computer program, when executed by the processor, implements the steps of the discontinuous reception processing method according to any one of claims 1 to 14.

30. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, implements the steps of the method for processing discontinuous reception according to any one of claims 1 to 14.