WO2021081838A1

WO2021081838A1 - Drx configuration method and apparatus, and terminal device and network device

Info

Publication number: WO2021081838A1
Application number: PCT/CN2019/114474
Authority: WO
Inventors: 石聪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2019-10-30
Filing date: 2019-10-30
Publication date: 2021-05-06
Also published as: CN114270917A; CN114270917B

Abstract

Provided are a DRX configuration method and apparatus, and a terminal device and a network device. The method comprises: a terminal device receiving first configuration information sent by a network device, wherein the first configuration information is used to determine DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; the terminal device receiving second configuration information sent by the network device, wherein the second configuration information is used to determine one or more scaling parameters; and the terminal device monitoring a physical downlink control channel (PDCCH) on the basis of the first configuration information and the second configuration information.

Description

A DRX configuration method and device, terminal equipment, network equipment

Technical field

The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a discontinuous reception (Discontinuous Reception, DRX) configuration method and device, terminal equipment, and network equipment.

Background technique

In the (New Radio, NR) system, each media access control entity (Media Access Control entity, MAC entity) has a DRX configuration. In a DRX cycle (DRX cycle), the terminal device needs to blindly check the Physical Downlink Control Channel (PDCCH) during the DRX activation time.

cDRX refers to DRX (connected DRX) in the RRC connected state. For Carrier Aggregation (CA) scenarios, a cDRX enhancement solution is currently proposed. Specifically, for the carrier aggregation scenarios of FR1 and FR2 in NR, the behavior of the terminal device in blindly detecting the PDCCH on FR1 and FR2 is very different. If a common cDRX configuration is configured for the carrier of FR1 and FR2, it may cause the terminal device to blindly check the FR2 for too long, which will lead to additional power consumption.

Summary of the invention

The embodiments of the present application provide a DRX configuration method and device, terminal equipment, and network equipment.

The DRX configuration method provided by the embodiment of the application includes:

The terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;

Receiving, by the terminal device, second configuration information sent by the network device, where the second configuration information is used to determine one or more scaling parameters;

The terminal device monitors the PDCCH based on the first configuration information and the second configuration information.

The network device sends first configuration information to the terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;

Sending, by the network device, second configuration information to the terminal device, where the second configuration information is used to determine one or more scaling parameters;

Wherein, the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.

The DRX configuration device provided by the embodiment of the present application includes:

The receiving unit is configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; 2. Configuration information, where the second configuration information is used to determine one or more scaling parameters;

The processing unit is configured to monitor the PDCCH based on the first configuration information and the second configuration information.

A sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; sending a second configuration to the terminal device Information, the second configuration information is used to determine one or more scaling parameters;

The terminal device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned DRX configuration method.

The network device provided by the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned DRX configuration method.

The chip provided in the embodiment of the present application is used to implement the above-mentioned DRX configuration method.

Specifically, the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned DRX configuration method.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned DRX configuration method.

The computer program product provided by the embodiments of the present application includes computer program instructions that cause a computer to execute the above-mentioned DRX configuration method.

The computer program provided in the embodiments of the present application, when running on a computer, causes the computer to execute the above-mentioned DRX configuration method.

Through the above technical solutions, a method for terminal equipment to monitor the control channel discontinuously is proposed. Through the configured scaling parameters, the network side has sufficient flexibility in the scheduling of PDCCH, and at the same time, the energy saving of the terminal equipment is taken into account, so that the terminal equipment is There is a better compromise between scheduling flexibility and energy saving.

Description of the drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The exemplary embodiments and descriptions of the application are used to explain the application, and do not constitute an improper limitation of the application. In the attached picture:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of the running time of drx-onDurationTimer provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of a DRX configuration method provided by an embodiment of the application;

FIG. 4 is a schematic diagram of time and position of Example 1 provided by an embodiment of this application;

FIG. 5 is a schematic diagram of time and position of Example 2 provided by an embodiment of this application;

6 is a schematic diagram 1 of the structural composition of the DRX configuration device provided by an embodiment of the application;

FIG. 7 is a second schematic diagram of the structural composition of the DRX configuration device provided by an embodiment of the application;

FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application;

FIG. 10 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), system, 5G communication system or future communication system.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area. Optionally, the network device 110 may be an evolved base station (Evolutional Node B, eNB, or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or The network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.

The communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110. The "terminal" used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device. Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.

Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; The device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article. The term "and/or" in this article is only an association relationship that describes associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

NR cDRX

In NR, each MAC entity has a DRX configuration. The DRX configuration includes the following parameters: drx-onDurationTimer, drx-SlotOffset, drx-StartOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycle, drx-ShortCycle , Drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.

In NR, if the terminal device is configured with a DRX configuration, the terminal device needs to detect the PDCCH in the DRX Active Time (DRX Active Time). DRX activation time is determined by the following factors:

1) The running period of any one of the following timers belongs to the DRX activation time:

drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer.

2) The pending state after the scheduling request (Scheduling Request, SR) is transmitted belongs to the DRX activation time.

3) After successfully receiving the random access response (Random Access Response, RAR) corresponding to the random access preamble (Random Access Preamble), the period during which the PDCCH indicating the newly transmitted data is not received belongs to the DRX activation time.

For drx-onDurationTimer, its start/restart is started at a fixed time point based on the configured DRX cycle, as shown in Figure 2. Specifically, the startup rules of drx-onDurationTimer are as follows:

If Short DRX Cycle is used, and [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drx-StartOffset)modulo(drx-ShortCycle); Or, if LongDRXCycle is used, and [(SFN ×10)+subframe number] modulo(drx-LongCycle)=drx-StartOffset, then: the drx-onDurationTimer is started after the drx-SlotOffset time from the start time of the subframe.

For the drx-InactivityTimer, the condition for the terminal device to start or restart the drx-InactivityTimer is: if the terminal device receives a PDCCH indicating downlink or uplink initial transmission (that is, new transmission), the terminal device starts or restarts the drx-InactivityTimer.

CDRX enhancement in NR CA scenarios

For the carrier aggregation scenarios of FR1 and FR2 in NR, the behavior of the terminal equipment in blindly detecting the PDCCH on FR1 (mainly frequency bands below 6 GHz) and FR2 (mainly frequency bands above 6 GHz) is very different. Generally speaking, the basic parameter set (numerology) adopted by the FR2 carrier is larger than that of the FR1 carrier. Therefore, for the same time, such as 10 ms, the FR2 carrier has a much larger number of time slots than the FR1 carrier. The blind detection of PDCCH is based on the configuration of control resource set (CORESET) and search space (SEARCHSPACE), and its granularity can reach symbol level. If FR1 and FR2 have the same requirements for blind detection of PDCCH, the time required for FR2 Will be shorter than FR1. In other words, in the same time, the overhead of blind PDCCH detection on FR2 will be greater than that of FR1.

If a common cDRX configuration is configured for the carriers of FR1 and FR2, it may cause the terminal device to blindly detect the PDCCH on the FR2 for too long, thereby causing additional power consumption.

In order to optimize the power consumption of FR2, two sets of DRX configurations can be configured, that is, for FR2 carriers, the network can configure an additional set of DRX configurations, which can be called a secondary DRX (secondaryDRX) configuration. In the secondaryDRX configuration, the network can configure a shorter blind detection timer, so the blind detection overhead of the terminal device on the FR2 can be optimized. However, in this way, each carrier needs to be configured with an additional set of DRX configuration, which will increase the load of configuration signaling. For this reason, the following technical solutions of the embodiments of the present application are proposed. The technical solutions of the embodiments of the present application are intended to enhance the DRX configuration in the NR CA scenario.

FIG. 3 is a schematic flowchart of a DRX configuration method provided by an embodiment of the application. As shown in FIG. 3, the DRX configuration method includes the following steps:

Step 301: The terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer.

In the embodiment of the present application, the network device sends the first configuration information to the terminal device. Accordingly, the terminal device receives the first configuration information sent by the network device, and the first configuration information is used to determine the DRX configuration. Further, optionally, the network device is a base station, such as a gNB.

In an optional implementation manner, the first configuration information is carried in first configuration signaling.

In an example, the terminal device receives the first configuration information sent by the network device. The first configuration information may be recorded as DRX-config. The DRX-config is configured in MAC-CellGroupConfig, where MAC-CellGroupConfig is used for the cell group ( cell group) Configure MAC parameters, where the MAC parameters include DRX configuration.

In the embodiment of the present application, the DRX configuration is used to determine the configuration parameter of at least one timer. Here, the timer in the DRX configuration may also be referred to as a DRX timer. Optionally, the at least one timer includes at least one of the following:

DRX continuous timer (drx-onDurationTimer);

DRX inactivity timer (drx-InactivityTimer);

DRX uplink retransmission timer (drx-RetransmissionTimerDL);

DRX downlink retransmission timer (drx-RetransmissionTimerUL).

In an optional implementation manner, the DRX configuration is a DRX configuration in an RRC connected state (ie, a cDTX configuration).

Step 302: The terminal device receives second configuration information sent by the network device, where the second configuration information is used to determine one or more scaling parameters.

In the embodiment of the present application, the network device sends second configuration information to the terminal device. Accordingly, the terminal device receives the second configuration information sent by the network device, and the second configuration information is used to determine one Or multiple scaling parameters. Further, optionally, the network device is a base station, such as a gNB.

In an optional implementation manner, the second configuration information is carried in second configuration signaling. The second configuration signaling and the first configuration signaling in the above solution are two independent configuration signalings.

In the embodiment of the present application, the second configuration information is used to determine (or indicate) one or more scaling parameters, where the scaling parameters are used to scale the PDCCH monitoring duration.

Step 303: The terminal device monitors the PDCCH based on the first configuration information and the second configuration information.

In the embodiment of the present application, at least one timer in the DRX configuration may be associated with the same common scaling parameter, or different timers in the DRX configuration may be associated with different scaling parameters (that is, the difference between the timer and the scaling parameter). The association relationship is a one-to-one correspondence). The following describes how the terminal device monitors the PDCCH in combination with different association situations.

The second configuration information is used to determine a scaling parameter.

Here, the scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer; wherein, the first cell needs to monitor the PDCCH The cell whose monitoring time is scaled.

In an optional implementation manner, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.

In this case, the way the terminal device monitors the PDCCH is:

1) For the first cell that needs to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, wherein the first time period is less than or equal to the maximum time period. Long PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.

2) For the second cell that does not need to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the second cell during the running of the first timer.

In the above solution, the first timer is any timer in the DRX configuration.

In the above solution, the start time of the first duration is the start time of the first timer.

In an optional implementation manner, the terminal device determines the longest PDCCH monitoring duration corresponding to the first cell according to the scaling parameter and the duration of the first timer, which can be determined by the following formula (1.1) or formula (1.2 )to realise:

The longest PDCCH monitoring duration = Timer/ScalingFactor (1.1)

The longest PDCCH monitoring duration=Timer×ScalingFactor (1.2)

Wherein, Timer is the duration of the first timer, and ScalingFactor is the scaling parameter.

It should be noted that the above formula (1) is only exemplary, and the technical solution of the embodiment of the present application is not limited to this. For example, the longest PDCCH monitoring duration can also be implemented by the following formula (2.1) or formula (2.2):

The longest PDCCH monitoring duration = floor(Timer/ScalingFactor) (2.1)

The longest PDCCH monitoring duration = floor(Timer×ScalingFactor) (2.2)

Among them, floor represents the round-down operation.

The second configuration information is used to determine multiple scaling parameters.

Here, different scaling parameters in the plurality of scaling parameters have an association relationship with different timers; each scaling parameter in the plurality of scaling parameters is used to determine the running period of the timer associated with the scaling parameter, the terminal The longest PDCCH monitoring duration of the device on the first cell; wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.

In this case, the way the terminal device monitors the PDCCH is:

1) For the first cell that needs to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, wherein the first time period is less than or equal to the maximum time period. Long PDCCH monitoring duration, the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.

In the above solution, the first timer is any timer in the DRX configuration.

In an optional implementation manner, the terminal device determines the longest PDCCH monitoring duration corresponding to the first cell according to the duration of the first timer and the first scaling parameter associated with the first timer, which may refer to the foregoing Formula (1.1) or formula (1.2) or formula (2.1) or formula (2.2) can be realized. It should be pointed out that because different timers are associated with different scaling parameters, when the above formula is used to calculate the longest PDCCH monitoring duration, the selection of scaling parameters is not uniform, but different scaling parameters are selected for different timers.

It should be noted that the condition for the terminal device to start the timer (such as on-durationTimer, drx-inactivityTimer) will not change with the scaling parameter. For example, if the terminal device receives a PDCCH for indicating newly transmitted data during the operation of the drx-onDurationTimer, the drx-InactivityTimer is started.

It should be noted that the description of “cell” involved in the embodiments of the present application can also be replaced with “carrier”.

In the technical solution of the embodiment of the present application, by configuring the scaling parameters, the terminal equipment monitors the PDCCH on some serving cells during the operation of one or more DRX timers to scale, so as to reduce the terminal equipment’s presence in these serving cells. The purpose of monitoring the PDCCH duration. Wherein, the configuration method of the scaling parameter may be: 1) configure a common scaling parameter for at least one DRX timer that needs to scale the PDCCH monitoring duration (that is, the above-mentioned second configuration information is used to determine a related solution for the scaling parameter); Or, 2) configure a scaling parameter for each DRX timer that needs to scale the PDCCH monitoring duration (that is, the above-mentioned second configuration information is used to determine a related solution for multiple scaling parameters). Among them, 1) the advantage of the solution is at least that the signaling overhead is less; 2) the advantage of the solution is that it can at least support a more flexible configuration.

The following describes the technical solutions of the embodiments of the present application with specific application examples.

Example one

In this example, taking the first cell as FR2 or Scell as an example, by configuring a common scaling parameter, the power consumption of the terminal device in blind detection of the PDCCH on the FR2 or Scell is saved. Specifically, each MAC entity is configured with one DRX configuration (that is, each MAC entity is configured with only one DRX configuration). In the scenario of carrier aggregation, all aggregated carriers use this DRX configuration. For FR2 or any other aggregated carrier, the network device can configure a scaling parameter. When the terminal device starts blind detection of the PDCCH according to the DRX configuration, for the carrier configured with the scaling parameter, the terminal device will scale the PDCCH monitoring duration during the operation of the corresponding timer, so that the blind detection time on the corresponding carrier is reduced to save power the goal of. In this way, only one set of DRX configuration can be maintained, and the power consumption saving on FR2 can be achieved at the same time. The following describes the specific steps.

1. The terminal device receives first configuration information sent by the network device, where the first configuration information includes DRX configuration (that is, DRX-config), where DRX-config is configured in MAC-CellGroupConfig.

2. The terminal device receives second configuration information sent by the network device. The second configuration information is different from the first configuration information. The second configuration information carries the first indication information and is used to indicate a scaling parameter. Scale the PDCCH monitoring duration during the running of one or more timers in the DRX-config. Specifically, the longest PDCCH monitoring duration of the terminal device on the SCell during the running of the timer is determined based on the duration of the timer and the scaling parameter. Here, the SCell is only exemplary, and represents a cell that needs to scale the PDCCH monitoring duration. For each cell (or carrier) that needs to scale the PDCCH monitoring duration, the longest PDCCH monitoring duration needs to be determined separately.

Optionally, one or more timers in DRX-config (that is, timers that need to scale the PDCCH monitoring duration) include at least one of the following:

drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL.

Optionally, the second configuration information is configured for a carrier (or cell), that is, for a certain carrier, if the second configuration information is configured, it means that the terminal device needs to scale the PDCCH monitoring duration on the carrier. For each carrier (or cell) whose PDCCH monitoring duration needs to be scaled, its carrier configuration (or cell configuration) includes the second configuration information. For example, the second configuration information is carried in SCellConfig in CellGroupConfig.

3. The terminal device starts on-durationtimer at a fixed time based on DRX-config. The behavior of terminal equipment monitoring PDCCH on each serving cell during on-durationtimer operation is as follows:

a) For the SCell configured with scaling parameters (ie the first cell), the terminal device scales the on-durationTimer duration according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to the on-durationTimer. The terminal device is in the on-durationTimer operation period , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period. Optionally, the longest PDCCH monitoring duration is obtained by dividing or multiplying the on-durationTimer by the scaling parameter.

b) For the SpCell and the Cell without scaling parameters (that is, the second cell), the terminal device monitors the PDCCH on the Cell during the on-duration timer operation.

4. If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the DRX activation time, the terminal device starts the drx-InactivityTimer. The behavior of terminal equipment monitoring PDCCH on each serving cell during the operation of drx-InactivityTimer is as follows:

c) For the SCell configured with scaling parameters (ie the first cell), the terminal device scales the duration of drx-inactivityTimer according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to drx-inactivityTimer. The terminal device is in the operation period of drx-inactivityTimer , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period. Optionally, the longest PDCCH monitoring duration is obtained according to the drx-inactivityTimer divided by or multiplied by the scaling parameter.

d) For the SpCell and the Cell without scaling parameters (that is, the second cell), the terminal device monitors the PDCCH on the Cell during the operation of the drx-inactivityTimer.

This example will be described in detail below in conjunction with FIG. 4.

1. The terminal device receives the RRC configuration signaling sent by the network device, and the content of the RRC configuration signaling is as follows:

a) First configuration information: The first configuration information includes the DRX configuration, and the DRX parameters included in the DRX configuration include long DRX cycle, drx-onDurationTimer, drx-InactivityTimer, etc.

b) Second configuration information: The second configuration information is used to configure a scaling parameter for the terminal device, and the scaling parameter is 2.

c) Serving cell configuration: Serving cell configuration is used to configure two serving cells, cell0 and cell1, for the terminal device, where cell0 is PCell (corresponding to FR1) and cell1 is SCell (corresponding to FR2). And configure cell1 to use the scaling parameter (that is, configure cell1 as a cell that needs to scale the PDCCH monitoring duration).

2. The terminal device periodically starts the on-durationtimer based on the DRX configuration.

a) For cell0, the terminal device monitors the PDCCH on cell0 during the on-durationtimer operation.

b) For cell1, the terminal device determines its longest PDCCH monitoring duration on cell1 during on-durationTimer operation as floor(on-durationTimer/2) according to the scaling parameters, and does not exceed the maximum PDCCH monitoring time during on-durationTimer operation. The PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.

3. If the terminal device receives a PDCCH indicating a new uplink or downlink transmission during the on-durationTimer operation, the terminal device starts the drx-InactivityTimer.

a) For cell0, the terminal device monitors the PDCCH on the cell0 during the operation of the drx-inactivityTimer.

b) For cell1, the terminal device determines that the longest PDCCH monitoring duration on cell1 during the operation of drx-inactivityTimer is floor (drx-inactivityTimer/2) according to the scaling parameters, and does not exceed the maximum during the operation of drx-inactivityTimer. The PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.

It should be noted that the conditions for the terminal device to start on-durationTimer and drx-inactivityTimer will not change with the scaling parameters. For example, the terminal device blindly detects the PDCCH indicating the uplink or downlink transmission on the PCell. At this time, the terminal device will start the drx-inactivityTimer. The drx-inactivityTimer will apply to PCell and SCell (even when the drx-inactivityTimer is started, the terminal device does not blindly detect the PDCCH on the SCell due to the scaling parameter).

In specific implementation, the Scell needs to be configured with a scaling parameter used to scale the PDCCH monitoring duration. The scaling parameter can be applied to the drx-onDurationTimer or drx-InactivityTimer operation period (A SCell may be configured with a PDCCH monitoring time scaling function when either drx -onDurationTimer or drx-InactivityTimer is running). Among them, the DRX activation time of the Scell can be defined with reference to the definition in Table 1 below. It should be noted that the DRX activation time of the Scell represents the time that the terminal device needs to monitor the PDCCH on the Scell.

Table 1

For the implementation of the second configuration information, it can be based on CellGroupConfig and MAC-CellGroupConfig, where the information element (IE) of CellGroupConfig refers to the following Table 2-1, and the newly added content in Table 2-1 is drxScaling-Config( That is, the second configuration information). Refer to Table 2-2 for its meaning. The IE of MAC-CellGroupConfig refers to the following Table 3-1. The newly added content in Table 3-1 is drx-ScalingFactor (scaling parameter), and its meaning refers to Table 3-2.

table 2-1

Table 2-2

Table 3-1

Table 3-2

Example two

In this example, taking the first cell as FR2 or Scell as an example, scaling parameters are configured for each DRX timer that needs to scale the PDCCH monitoring time to realize the power saving of the terminal device blindly detecting the PDCCH on the FR2 or Scell. Specifically, each MAC entity is configured with one DRX configuration (that is, each MAC entity is configured with only one DRX configuration). In the scenario of carrier aggregation, all aggregated carriers use this DRX configuration. For FR2 or any other aggregated carrier, the network device can configure at least one scaling parameter (such as multiple scaling parameters). When the terminal device starts blind detection of the PDCCH according to the DRX configuration, for the carrier configured with the scaling parameter, the terminal device will scale the PDCCH monitoring duration during the operation of the corresponding timer according to the scaling parameter associated with the timer, so that the corresponding carrier The blind inspection time is shortened to achieve the purpose of power saving. In this way, only one set of DRX configuration can be maintained, and the power consumption saving on FR2 can be achieved at the same time. The following describes the specific steps.

2. The terminal device receives the second configuration information sent by the network device, the second configuration information is different from the first configuration information, and the second configuration information carries the first indication information for indicating at least one scaling parameter (such as multiple scaling parameters). Parameters), where each scaling parameter is used to scale the PDCCH monitoring duration during the running of a timer in DRX-config. Specifically, the longest PDCCH monitoring duration of the terminal device on the SCell during the running of the timer is determined based on the duration of the timer and the scaling parameter associated with the timer. Here, the SCell is only exemplary, and represents a cell that needs to scale the PDCCH monitoring duration. For each cell (or carrier) that needs to scale the PDCCH monitoring duration, the longest PDCCH monitoring duration needs to be determined separately.

Optionally, one or more timers in DRX-config (that is, timers that need to scale the PDCCH monitoring duration) include at least one of the following: drx-onDurationTimer, drx-InactivityTimer.

Among them, a scaling parameter is configured for each timer that needs to scale the PDCCH monitoring duration.

a) For the SCell configured with scaling parameters (ie the first cell), the terminal device scales the on-durationTimer duration according to the scaling parameters to obtain the longest PDCCH monitoring duration corresponding to the on-durationTimer. The terminal device is in the on-durationTimer operation period , Monitoring the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period. Optionally, the longest PDCCH monitoring duration is obtained by dividing or multiplying the on-durationTimer by the scaling parameter associated with the on-durationTimer.

c) For the SCell configured with scaling parameters (ie the first cell), the terminal device scales the duration of drx-inactivityTimer according to the scaling parameter associated with drx-inactivityTimer to obtain the longest PDCCH monitoring duration corresponding to drx-inactivityTimer. The terminal device is in During the operation of the drx-inactivityTimer, monitor the PDCCH on the SCell within a time period that does not exceed the longest PDCCH monitoring time period. Optionally, the longest PDCCH monitoring duration is obtained by dividing or multiplying the drx-inactivityTimer by the scaling parameter associated with the drx-inactivityTimer.

This example will be described in detail below with reference to FIG. 5.

b) Second configuration information: The second configuration information is used to configure at least one scaling parameter (such as multiple scaling parameters) for the terminal device. For drx-onDurationTimer, the scaling parameter is 2; for drx-InactivityTimer, the scaling parameter is 4.

b) For cell1, the terminal device determines that its longest PDCCH monitoring duration on cell1 during the operation of drx-inactivityTimer is floor (drx-inactivityTimer/4) according to the scaling parameters, and does not exceed the maximum during the operation of drx-inactivityTimer. The PDCCH is monitored on cell1 within the period of long PDCCH monitoring duration.

In specific implementation, the Scell needs to be configured with a scaling parameter used to scale the PDCCH monitoring duration. The scaling parameter can be applied to the drx-onDurationTimer or drx-InactivityTimer operation period (A SCell may be configured with a PDCCH monitoring time scaling function when either drx -onDurationTimer or drx-InactivityTimer is running). Among them, the DRX activation time of the Scell can be defined with reference to the definition in Table 4 below. It should be noted that the DRX activation time of the Scell represents the time that the terminal device needs to monitor the PDCCH on the Scell.

Table 4

For the implementation of the second configuration information, it can be based on CellGroupConfig and MAC-CellGroupConfig, where the IE of CellGroupConfig refers to the following Table 5-1, and the newly added content in Table 5-1 is drxScaling-Config (that is, the second configuration information), Refer to Table 5-2 for its meaning. The IE of MAC-CellGroupConfig refers to the following Table 6-1. The newly added content in Table 6-1 is drx-ScalingFactor (ie scaling parameter), and its meaning parameter is Table 6-2.

Table 5-1

Table 5-2

Table 6-1

Table 6-2

FIG. 6 is a schematic diagram 1 of the structural composition of the DRX configuration device provided by an embodiment of the application, which is applied to a terminal device. As shown in FIG. 6, the DRX configuration device includes:

The receiving unit 601 is configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; Second configuration information, where the second configuration information is used to determine one or more scaling parameters;

The processing unit 602 is configured to monitor the PDCCH based on the first configuration information and the second configuration information.

In an optional implementation manner, the second configuration information is used to determine a scaling parameter,

The scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.

In an optional implementation manner, the processing unit 602 is configured to monitor the PDCCH on the first cell within the first time period during which the first timer is running for the first cell that needs to scale the PDCCH monitoring time, Wherein, the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.

In an optional implementation manner, the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;

Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;

In an optional implementation manner, the processing unit 602 is configured to monitor the PDCCH on the first cell within the first time period during which the first timer is running for the first cell that needs to scale the PDCCH monitoring time, Wherein, the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.

In an optional embodiment, the start time of the first duration is the start time of the first timer.

In an optional implementation manner, the first timer is any timer in the DRX configuration.

In an optional implementation manner, the processing unit 602 is further configured to monitor the PDCCH on the second cell during the operation of the first timer for the second cell that does not need to scale the PDCCH monitoring time.

In an optional implementation manner, the at least one timer includes at least one of the following:

DRX continuous timer (drx-onDurationTimer);

DRX inactivity timer (drx-InactivityTimer);

DRX uplink retransmission timer (drx-RetransmissionTimerDL);

DRX downlink retransmission timer (drx-RetransmissionTimerUL).

In an optional implementation manner, the processing unit 602 is further configured to start the drx-InactivityTimer if a PDCCH for indicating newly transmitted data is received during the operation of the drx-onDurationTimer.

In an optional implementation manner, the DRX configuration is a DRX configuration in an RRC connected state.

Those skilled in the art should understand that the relevant description of the foregoing DRX configuration apparatus in the embodiment of the present application can be understood with reference to the relevant description of the DRX configuration method in the embodiment of the present application.

FIG. 7 is a second structural diagram of the DRX configuration device provided by an embodiment of the application, which is applied to network equipment. As shown in FIG. 7, the DRX configuration device includes:

The sending unit 701 is configured to send first configuration information to a terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; and a second configuration information is sent to the terminal device. Configuration information, where the second configuration information is used to determine one or more scaling parameters;

DRX continuous timer (drx-onDurationTimer);

DRX inactivity timer (drx-InactivityTimer);

DRX uplink retransmission timer (drx-RetransmissionTimerDL);

DRX downlink retransmission timer (drx-RetransmissionTimerUL).

FIG. 8 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

The memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.

Optionally, as shown in FIG. 8, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Wherein, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 800 may specifically be a network device in an embodiment of the present application, and the communication device 800 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here. .

Optionally, the communication device 800 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application. For the sake of brevity , I won’t repeat it here.

FIG. 9 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9, the chip 900 may further include a memory 920. The processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

The memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

Optionally, the chip 900 may further include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 900 may further include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not described herein again.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.

FIG. 10 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. As shown in FIG. 10, the communication system 1000 includes a terminal device 1010 and a network device 1020.

Wherein, the terminal device 1010 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 1020 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I won’t repeat it here.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Go into details again.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application. When the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which is not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

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

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A discontinuous reception DRX configuration method, the method includes:

The terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;

Receiving, by the terminal device, second configuration information sent by the network device, where the second configuration information is used to determine one or more scaling parameters;

The terminal device monitors the physical downlink control channel PDCCH based on the first configuration information and the second configuration information.
The method according to claim 1, wherein the second configuration information is used to determine a scaling parameter,

The scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The method according to claim 2, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The method according to claim 2 or 3, wherein the terminal device monitoring the PDCCH based on the first configuration information and the second configuration information includes:

For the first cell that needs to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, where the first time period is less than or equal to the longest PDCCH Monitoring duration, the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.
The method according to claim 1, wherein the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;

Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The method according to claim 5, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The method according to claim 5 or 6, wherein the terminal device monitoring the PDCCH based on the first configuration information and the second configuration information includes:

For the first cell that needs to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the first cell during the first time period during which the first timer is running, where the first time period is less than or equal to the longest PDCCH Monitoring duration, the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.
The method according to claim 4 or 7, wherein the start time of the first duration is the start time of the first timer.
The method according to any one of claims 4, 7, 8, wherein the first timer is any one of the timers in the DRX configuration.
The method according to any one of claims 1 to 9, wherein the terminal device monitoring the PDCCH based on the first configuration information and the second configuration information includes:

For the second cell that does not need to scale the PDCCH monitoring time, the terminal device monitors the PDCCH on the second cell during the running of the first timer.
The method according to any one of claims 1 to 10, wherein the at least one timer includes at least one of the following:

DRX continuous timer drx-onDurationTimer;

DRX inactive timer drx-InactivityTimer;

DRX uplink retransmission timer drx-RetransmissionTimerDL;

DRX downlink retransmission timer drx-RetransmissionTimerUL.
The method according to claim 11, wherein the method further comprises:

If the terminal device receives the PDCCH for indicating newly transmitted data during the operation of the drx-onDurationTimer, then the drx-InactivityTimer is started.
The method according to any one of claims 1 to 12, wherein the DRX configuration is a DRX configuration in an RRC connected state.
A DRX configuration method, the method includes:

The network device sends first configuration information to the terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer;

Sending, by the network device, second configuration information to the terminal device, where the second configuration information is used to determine one or more scaling parameters;

Wherein, the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.
The method according to claim 14, wherein the second configuration information is used to determine a scaling parameter,

The scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The method according to claim 14, wherein the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;

Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The method according to claim 15 or 16, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The method according to any one of claims 14 to 17, wherein the at least one timer includes at least one of the following:

DRX continuous timer drx-onDurationTimer;

DRX inactive timer drx-InactivityTimer;

DRX uplink retransmission timer drx-RetransmissionTimerDL;

DRX downlink retransmission timer drx-RetransmissionTimerUL.
The method according to any one of claims 14 to 18, wherein the DRX configuration is a DRX configuration in an RRC connected state.
A DRX configuration device, the device includes:

The receiving unit is configured to receive first configuration information sent by a network device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; 2. Configuration information, where the second configuration information is used to determine one or more scaling parameters;

The processing unit is configured to monitor the PDCCH based on the first configuration information and the second configuration information.
The apparatus according to claim 20, wherein the second configuration information is used to determine a scaling parameter,

The scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The apparatus according to claim 21, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The device according to claim 21 or 22, wherein the processing unit is configured to, for the first cell that needs to scale the PDCCH monitoring time, be in the first cell during the first time period during which the first timer is running. Monitoring the PDCCH, wherein the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the scaling parameter and the duration of the first timer.
The apparatus according to claim 20, wherein the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;

Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The apparatus according to claim 24, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The apparatus according to claim 24 or 25, wherein the processing unit is configured to, for the first cell that needs to scale the PDCCH monitoring time, be in the first cell during the first time period during which the first timer is running. Monitoring the PDCCH, wherein the first duration is less than or equal to the longest PDCCH monitoring duration, and the longest PDCCH monitoring duration is determined according to the duration of the first timer and the first scaling parameter associated with the first timer.
The device according to claim 23 or 26, wherein the start time of the first duration is the start time of the first timer.
The apparatus according to any one of claims 23, 26, 27, wherein the first timer is any one of the timers in the DRX configuration.
The apparatus according to any one of claims 20 to 28, wherein the processing unit is further configured to: for a second cell that does not need to scale the PDCCH monitoring time, perform the first timer during the operation of the first timer. The PDCCH is monitored on the second cell.
The device according to any one of claims 20 to 29, wherein the at least one timer comprises at least one of the following:

DRX continuous timer drx-onDurationTimer;

DRX inactive timer drx-InactivityTimer;

DRX uplink retransmission timer drx-RetransmissionTimerDL;

DRX downlink retransmission timer drx-RetransmissionTimerUL.
The apparatus according to claim 30, wherein the processing unit is further configured to start the drx-InactivityTimer if a PDCCH for indicating newly transmitted data is received during the operation of the drx-onDurationTimer.
The apparatus according to any one of claims 20 to 31, wherein the DRX configuration is a DRX configuration in an RRC connected state.
A DRX configuration device, the device includes:

A sending unit, configured to send first configuration information to a terminal device, where the first configuration information is used to determine a DRX configuration, and the DRX configuration is used to determine a configuration parameter of at least one timer; sending a second configuration to the terminal device Information, the second configuration information is used to determine one or more scaling parameters;

Wherein, the first configuration information and the second configuration information are used by the terminal device to monitor the PDCCH.
The apparatus according to claim 33, wherein the second configuration information is used to determine a scaling parameter,

The scaling parameter is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of each of the at least one timer;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The apparatus according to claim 33, wherein the second configuration information is used to determine a plurality of scaling parameters, and different scaling parameters of the plurality of scaling parameters have an association relationship with different timers;

Each of the multiple scaling parameters is used to determine the longest PDCCH monitoring duration of the terminal device on the first cell during the operation of the timer associated with the scaling parameter;

Wherein, the first cell is a cell that needs to scale the PDCCH monitoring time.
The apparatus according to claim 34 or 35, wherein, for the first cell that needs to scale the PDCCH monitoring time, the second configuration information is carried in the cell configuration of the first cell.
The device according to any one of claims 33 to 36, wherein the at least one timer comprises at least one of the following:

DRX continuous timer drx-onDurationTimer;

DRX inactive timer drx-InactivityTimer;

DRX uplink retransmission timer drx-RetransmissionTimerDL;

DRX downlink retransmission timer drx-RetransmissionTimerUL.
The apparatus according to any one of claims 33 to 37, wherein the DRX configuration is a DRX configuration in an RRC connected state.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 13 Methods.
A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 14 to 19 Methods.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 13.
A chip comprising: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 14 to 19.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 1 to 13.
A computer-readable storage medium for storing a computer program that enables a computer to execute the method according to any one of claims 14 to 19.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 13.
A computer program product comprising computer program instructions that cause a computer to execute the method according to any one of claims 14 to 19.
A computer program that causes a computer to execute the method according to any one of claims 1 to 13.
A computer program that causes a computer to execute the method according to any one of claims 14 to 19.