CN111726891B

CN111726891B - Method and equipment for starting DRX (discontinuous reception) cycle

Info

Publication number: CN111726891B
Application number: CN201910212985.7A
Authority: CN
Inventors: 谌丽; 赵亚利
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2019-03-20
Filing date: 2019-03-20
Publication date: 2022-07-22
Anticipated expiration: 2039-03-20
Also published as: CN111726891A

Abstract

The invention provides a method and equipment for starting a DRX (discontinuous reception) cycle, which are used for solving the problem that in the prior art, due to the fact that a resource scheduling unit is not matched with a starting point and a counting unit of the length of the DRX cycle, the short DRX cycle is completely invalid, and scheduling and transmission delay are increased. The terminal determines that DRX-inactivity timer is overtime or receives a DRX Command MAC CE; the terminal starts a short DRX cycle at a subframe capable of receiving a scheduling command. After determining that the DRX-inactivity timer is overtime or receiving the DRX Command MAC CE, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling Command, and does not need to enter an active time at the start of the next long DRX cycle to receive the scheduling Command, so that the time for entering the active time to receive the scheduling Command is shortened, and the time delay of data transmission and scheduling is reduced.

Description

Method and equipment for starting DRX (discontinuous reception) cycle

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a method and a device for starting a DRX cycle.

Background

In DRX (Discontinuous Reception mechanism), at the time of receiving a data signal discontinuously, a terminal may enter an inactive state, so as to achieve the effects of saving power, and prolonging the standby time and the service life of a battery.

In the 5G system, a terminal may have two states of continuous reception and DRX (Radio Resource Control) in an RRC (Radio Resource Control) connected state, namely, an activity time (active time) and an activity time (inactive time). The DRX adopts periodic configuration, and the length of the DRX period is uniquely allocated to the terminal by RRC signaling. A short continuous reception state called on duration is entered at the beginning of each DRX cycle, and the duration of the on duration is determined by the DRX on duration timer. The DRX onDurationTimer is a period of monitoring a PDCCH (Physical Downlink Control Channel) from the beginning of the DRX cycle, and has a unit of ms. In the on duration, the terminal needs to monitor the PDCCH and determine whether there is resource allocation for itself.

If the terminal does not perform data scheduling and data transmission in the on duration, the terminal enters an inactive state, and can not receive downlink transmission again until a DRX-on duration timer is started in the next DRX cycle; as shown in fig. 1, a schematic diagram of a periodic configuration of DRX when there is no data scheduling.

If the terminal receives a scheduling command and downlink data transmission in the on duration, starting a following timer;

DRX-inactivity timer (DRX inactivity timer): starting the next symbol after receiving the PDCCH of the scheduling data, and monitoring the PDCCH by the terminal during the starting period; when determining that the DRX-inactivity timer times out or receives a DRX Command MAC CE (DRX Command MAC Control Element) that is terminated forcibly, the DRX-inactivity timer is stopped, where the DRX-inactivity timer length is ms, but the starting point of the DRX-inactivity timer is not necessarily whole ms.

DRX-ShortCycleTimer (short DRX cycle timer): and the number of the continuous short DRX cycles after the terminal enters the short DRX cycle from the long DRX cycle. For example, if the long DRX cycle is 40ms, the short DRX cycle is 10ms, and DRX-ShortCycleTimer is 1, then only one short DRX cycle is entered from the long DRX cycle, and then the long DRX cycle is entered.

Wherein, DRX-inactivity timer times out or the time when the DRX Command MAC CE is received may be in the middle of a subframe, for example, at the 7 th symbol of the 10ms subframe, and DRX-LongCycle is 40ms, DRX-ShortCycle is 10ms, DRX-StartOffest is 0, DRX-ShortCycle timer is 1, DRX-ShortCycle (short DRX cycle) needs to be calculated from the 10 th ms, that is, the 10 th ms is the start point of the short DRX cycle; as can be seen from fig. 2, there is a CORESET (Control Resource Set) in the first 7 symbols of the 10ms, and the CORESET includes PDCCH occasion (PDCCH Resource); starting a short DRX period at a 10ms subframe, recording 1 short DRX period by a short DRX period timer, entering a long DRX period, and stopping timing by the short DRX period timer; and CORESET in the short DRX period started in the 10ms subframe is contained in DRX-InactivetyTimer, no resource capable of sending and receiving the scheduling command exists in the started short DRX period, the short DRX period is invalid, the next long DRX period can be entered only after the DRX period is ended, the scheduling command is received at the starting point of the next long DRX period within the activation time, and the data transmission and the scheduling delay are increased.

In summary, since the symbol-level resource scheduling unit introduced in 5G is not matched with the counting unit (ms) of the starting point and the length of the DRX cycle, there is no available scheduling resource after the short DRX cycle is started, so that the short DRX cycle is completely disabled, resulting in a problem of increased resource scheduling and transmission delay.

Disclosure of Invention

The invention provides a method and equipment for starting a DRX (discontinuous reception) cycle, which are used for solving the problem that in the prior art, due to the fact that a resource scheduling unit is not matched with a starting point and a counting unit of the length of the DRX cycle, the short DRX cycle is completely invalid, and scheduling and transmission delay are increased.

In a first aspect, an embodiment of the present invention provides a method for starting a DRX cycle, where the method includes:

the terminal determines that DRX-InactivityTimer is overtime or receives DRX Command MAC CE;

the terminal starts a short DRX cycle at a subframe capable of receiving a scheduling command.

In the method, after the terminal determines that the DRX-inactivity timer is overtime or receives the DRX Command MAC CE, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling Command. After the terminal determines that the DRX-inactivity timer is overtime or receives the DRX Command MAC CE, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling Command, and does not need to wait to enter the next long DRX cycle, and enters an active time at the start of the long DRX cycle to receive the scheduling Command.

In a possible implementation manner, after the terminal determines that the DRX-inactivity timer times out or receives the DRX Command MAC CE, the terminal starts the DRX-ShortCycleTimer when a subframe capable of receiving the scheduling Command starts a short DRX cycle.

In a possible implementation manner, when the terminal starts the DRX-ShortCycleTimer, the terminal starts the DRX-ShortCycleTimer in a next subframe after the DRX-inactivytimeter times out or the DRX Command MAC CE is received.

In a possible implementation manner, when the terminal starts a DRX-ShortCycleTimer, the terminal starts the DRX-ShortCycleTimer at the next symbol after the DRX-inactivitytimeter times out or receives a DRX Command MAC CE.

The method gives the position of starting the DRX-ShortCycleTimer to ensure that the started DRX-ShortCycle is accurately timed after the short DRX cycle is started, and the started short DRX cycle avoids the PDCCH occase occupied by the previous active time period.

In one possible implementation manner, the terminal starts a DRX-ShortCycleTimer when the DRX-inactivytimer times out or receives a next symbol of a DRX Command MAC CE;

when the terminal starts a short DRX period in a subframe capable of receiving a scheduling Command, the terminal judges whether available scheduling resources exist in a DRX-onDuration timer of the short DRX period corresponding to the time when the DRX-InactivetyTimer is started after the DRX-InactivetyTimer is overtime or a DRX Command MAC CE is received;

if available scheduling resources exist, starting a DRX-onDurationTimer corresponding to the short DRX period at the starting subframe position of the short DRX period corresponding to the starting DRX-ShortCycleTimer;

otherwise, starting the DRX-onDurationTimer corresponding to the short DRX period at the starting subframe position of the next short DRX period after the DRX-shortCycleTimer is started.

In the method, when the DRX-inactivity timer is determined to be overtime or the next symbol of the DRX Command MAC CE is received, a DRX-ShortCycleTimer is started, whether available scheduling resources exist in a short DRX cycle corresponding to the time of starting the DRX-ShortCycleTimer is judged, if the available scheduling resources exist, a DRX-onDurationTimer is started at a starting subframe position of the short DRX cycle corresponding to the DRX-ShortCycleTimer to monitor, otherwise, a DRX-onDurationTimer is started at the starting subframe position of the next short DRX cycle to monitor, so that the short DRX cycle does not completely fail, and therefore, it is not necessary to wait for entering of a scheduling Command at the starting point of the next long DRX cycle to receive the activation time, the time for entering of the activation time to receive the scheduling Command is shortened, and the time delay of data transmission and scheduling is reduced.

In a possible implementation manner, the terminal starts a DRX-ShortCycleTimer after the DRX-inactivity timer times out or receives a DRX Command MAC CE or receives a next symbol of the DRX Command MAC CE;

when the terminal starts a short DRX period in a subframe capable of receiving a scheduling Command, the terminal judges whether the number of available scheduling resources in a DRX-onDurationTimer of the short DRX period corresponding to the time when the terminal starts the DRX-shortCycleTimer reaches a threshold or not after the DRX-InactivityTimer is overtime or receives a DRX Command MAC CE;

if so, starting a DRX-onDurationTimer corresponding to the short DRX period at the starting subframe position of the short DRX period corresponding to the starting DRX-shortcycleTimer;

In one possible implementation, the threshold is specified by a terminal-specific scheduling command configuration or protocol.

In the method, the terminal determines which position starts the DRX-onDurationTimer of the short DRX cycle according to whether the available scheduling resource in the subframe of the DRX-ShortCycleTimer reaches the threshold after the DRX-inactivity timer is overtime or receives the DRX Command MAC CE, starts the DRX-onDurationTimer corresponding to the short DRX cycle at the starting subframe position of the short DRX cycle corresponding to the starting DRX cycle after the DRX-ShortCycleTimer is started after determining that the available scheduling resource reaches the threshold, otherwise starts the DRX-onduration timer corresponding to the short DRX cycle at the starting subframe position of the next short DRX cycle after the DRX-ShortCycleTimer is started, so that the short DRX cycle does not completely fail, and does not need to wait for entering of an activation time receiving scheduling Command at the starting point of the next long DRX cycle, the time for entering of the activation time receiving scheduling Command is shortened, and the time delay of data transmission and scheduling is reduced.

In a second aspect, an embodiment of the present invention provides an apparatus for starting a DRX cycle, where the apparatus includes: a processor, a memory, and a transceiver;

the processor is used for determining that DRX-inactivity timer is overtime or receives a DRX Command MAC CE;

the short DRX cycle is started at a subframe where the scheduling command can be received.

In one possible implementation, the processor is further configured to:

the drx-ShortCycleTimer is started.

In one possible implementation, the processor is specifically configured to:

and starting a DRX-ShortCycleTimer at the next subframe after the DRX-inactivytimer times out or receives the DRX Command MAC CE.

In one possible implementation, the processor is specifically configured to:

and starting a DRX-ShortCycleTimer at the next symbol after the DRX-inactivytytimer times out or receives the DRX Command MAC CE.

In one possible implementation, the processor starts a DRX-ShortCycleTimer upon expiration of the DRX-inactivytimer or receipt of a next symbol of a DRX Command MAC CE;

the processor is specifically configured to:

judging whether available scheduling resources exist in a DRX-onDuration timer of a corresponding short DRX period when the DRX-InactivityTimer is started after the DRX-InactivityTimer is overtime or a DRX Command MAC CE is received;

In one possible implementation, the processor starts a DRX-ShortCycleTimer after the DRX-inactivity timer times out or receives a DRX Command MAC CE or receives a next symbol of the DRX Command MAC CE;

the processor is specifically configured to:

judging whether the number of available scheduling resources in a DRX-onDuration timer of a corresponding short DRX period reaches a threshold or not when the DRX-InactivityTimer is overtime or after a DRX Command MAC CE is received and the DRX-short cycleTimer is started;

In a third aspect, an embodiment of the present invention provides an apparatus for DRX cycle startup, where the apparatus includes:

the determining module is used for determining that the DRX-inactivity timer is overtime or receives a DRX Command MAC CE;

a starting module for starting a short DRX cycle at a subframe capable of receiving a scheduling command.

In a fourth aspect, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, where the computer program is executed by a processor to perform any of the steps of DRX cycle starting.

In addition, for technical effects brought by any one implementation manner of the second aspect to the fourth aspect, reference may be made to technical effects brought by different implementation manners of the first aspect, and details are not described herein again.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings described below 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 the drawings without creative efforts.

Fig. 1 is a schematic diagram of a periodic configuration of DRX when there is no data scheduling;

figure 2 is a schematic diagram of short DRX cycle failure;

fig. 3 is a flowchart of a method for starting a DRX cycle according to an embodiment of the present invention;

fig. 4 is a schematic diagram illustrating a first DRX cycle start according to an embodiment of the present invention;

fig. 5 is a diagram illustrating a second DRX cycle start according to an embodiment of the present invention;

fig. 6 is a diagram illustrating a third DRX cycle start according to an embodiment of the present invention;

fig. 7 is a structural diagram of a device for starting a first DRX cycle according to an embodiment of the present invention;

fig. 8 is a structural diagram of a device for starting a second DRX cycle according to an embodiment of the present invention.

Detailed Description

Hereinafter, some terms in the embodiments of the present invention are explained to facilitate understanding by those skilled in the art.

(1) In the embodiments of the present invention, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning of the terms.

(2) The term "plurality" in the embodiments of the present invention means two or more, and other terms are similar thereto.

(3) "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

When the terminal and the network side equipment perform data interaction, the terminal monitors a downlink PDCCH subframe all the time and checks whether information from the network side equipment exists or not; however, in reality, the terminal does not always perform effective information interaction with the network side device, does not always perform services such as uploading or downloading, and does not transmit data in real time, so that there is no information interaction between the terminal and the network side device in many times, and the terminal monitors downlink PDCCH subframes when there is no information interaction, which causes resource waste.

As shown in fig. 1, when a terminal monitors a PDCCH in a monitoring period, because the duration of data transmission is longer than the duration of the monitoring period, the terminal enters the inactive period after the monitoring period expires, at this time, the terminal does not transmit data, the untransmitted data needs to wait for the next monitoring period of a cycle to transmit, and the processing delay of a service is increased, so that a DRX-inactivity timer is added in the DRX mechanism; and starting a drx-inactivity timer at the next symbol of data transmission determined in the monitoring period, and when the drx-inactivity timer is running, the terminal still continues to monitor the downlink PDCCH subframe even if the originally configured on duration time is ended until the drx-inactivity timer times out. After a DRX-inactivity timer mechanism is added, the processing time delay of data is reduced, but when DRX-inactivity timer does not arrive after data transmission is finished, the terminal monitors a PDCCH to cause resource waste, so that a DRX Command MAC CE is introduced to quickly enter a sleep state after data transmission is finished;

under the above scenario, there may be a situation that the terminal determines that DRX-inactivity timer times out or a DRX Command MAC CE is received and then enters a next short DRX cycle, the DRX-inactivity timer times out or the DRX Command MAC CE is received and then falls within an on duration of the next short DRX cycle, and all CORESET (Control Resource Set) in the on duration are contained in the DRX-inactivity timer or a symbol before the DRX Command MAC CE is received, so that there is no Resource that can send and receive a scheduling Command in the short cycle, and if DRX-inactivity timer ═ 1, the terminal may only enter an active time receiving scheduling Command at a start point of the next long DEX cycle, so that there is a large delay in data transmission and scheduling of the terminal, as shown in fig. 2;

therefore, the invention provides a method for starting a DRX period under the scene that a terminal and network side equipment carry out data transmission, when the terminal determines that DRX-inactivity timer is overtime or receives a DRX Command MAC CE, the terminal starts a short DRX period at a subframe capable of receiving a scheduling Command, and because the short DRX period is started at the subframe capable of receiving the scheduling Command and enters an activation time at the starting point of the started short DRX period to receive the scheduling Command, the terminal does not need to wait for entering the starting point of the next long DRX period, the waiting time for data transmission is shortened, and the time delay of data transmission and scheduling is reduced.

The terminal is a device with a wireless communication function, can be deployed on land, and comprises an indoor or outdoor terminal, a handheld terminal or a vehicle-mounted terminal; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), etc.; but also various forms of terminals, Mobile Stations (MS), said terminal devices.

The network side device is a device for providing a wireless communication function for the terminal, and includes but is not limited to: a gbb in 5G, a Radio Network Controller (RNC), a Node B (NB), a cell controller (BSC), a Base Transceiver Station (BTS), a home cell (e.g., home evolved node B, or home node B, HNB), a BaseBand Unit (BBU), a transmission point (transmitting and receiving point,

TRP), Transmission Point (TP), mobile switching center, etc.

To make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention with each creative effort belong to the protection scope of the present invention.

To address the foregoing scenario, an embodiment of the present invention provides a flowchart of a method for starting a DRX cycle, and specifically, as shown in fig. 3, the method includes the following steps:

step 300, the terminal determines that DRX-inactivity timer is overtime or receives a DRX Command MAC CE;

in step 310, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling command.

In the method, after the terminal determines that the DRX-inactivity timer is overtime or receives the DRX Command MAC CE, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling Command. After determining that the DRX-inactivity timer is overtime or receiving the DRX Command MAC CE, the terminal starts a short DRX cycle in a subframe capable of receiving a scheduling Command, and does not need to wait for entering a next long DRX cycle, and enters an active time at the beginning of the long DRX cycle to receive the scheduling Command, so that the time for the terminal to wait for entering the active time to receive the scheduling Command is shortened, and the time delay of data transmission and scheduling is further reduced.

In the embodiment of the invention, after the terminal determines that the DRX-inactivity timer is overtime or receives a DRX Command MAC CE, the terminal starts a DRX cycle when a subframe capable of receiving a scheduling Command starts a DRX cycle.

It should be noted that starting the DRX-ShortCycleTimer only means that the DRX-ShortCycleTimer starts to operate, and when it is determined that the short DRX cycle is started, the started DRX-ShortCycleTimer starts to count.

When the terminal starts the DRX-ShortCycleTimer, the DRX-ShortCycleTimer can be started in the next subframe after determining that the DRX-InactivityTimer is overtime or receiving the DRX Command MAC CE; the DRX-ShortCycleTimer may also be started on the next symbol after determining that the DRX-inactivytimeter times out or receiving the DRX Command MAC CE; the above is described in detail by the following examples.

The first embodiment is as follows: and the terminal starts a DRX-ShortCycleTimer at the next subframe after the DRX-inactivytimer times out or receives the DRX Command MAC CE.

In this embodiment, the terminal determines that a DRX-inactivity timer is overtime or receives a DRX Command MAC CE, and starts the DRX-ShortCycleTimer after the current subframe ends;

for example, if it is determined that DRX-inactivity timer times out or receives DRX Command MAC CE at the position of the 10ms 7 th symbol, the DRX-ShortCycleTimer is started at the position of the 11ms subframe;

after the DRX-ShortCycleTimer is started, calculating a short DRX period starting subframe according to a short DRX period starting calculation formula, and starting a short DRX period at the calculated position of the first short DRX period starting subframe;

wherein the starting short DRX period is DRX-on DurationTimer of the starting short DRX period.

The starting point calculation formula of the short DRX period is as follows: [ (SFN × 10) + subframe number ] modulo (drx-ShortCycle) — (drx-StartOffset) modulo (drx-ShortCycle);

the System Frame Number (SFN), the subframe Number (subframe Number), the DRX-ShortCycle (short DRX cycle length) unit is ms, and the DRX-StartOffset (DRX cycle starting offset) unit is ms;

if the configuration parameters are: DRX-LongCycle 40ms means that one long DRX cycle is 40 ms; DRX-ShortCycle 10ms means that one short DRX cycle is 10 ms; the DRX-ShortCycleTimer is 1, which means that after 1 short DRX cycle, the short DRX cycle ends, and the terminal enters the active time from the beginning of the next long DRX cycle to receive a scheduling command; DRX-StartOffset ═ 0 denotes a radio frame SFN ═ 0, and subframe number ═ 0 is the starting point of the long DRX cycle; drx-onDurationTimer 1ms indicates that the duration of the listening period is 1 ms.

If the 7 th symbol DRX-inactivity timer in the 10 th subframe is overtime or receives a DRX Command MAC CE, the DRX-ShortCycleTimer is started in the next subframe after the DRX-inactivity timer is overtime or receives the DRX Command MAC CE, that is, the DRX-ShortCycleTimer is started in the 11 th subframe, and the number of the passed short DRX cycles is counted;

the position of the first subframe calculated according to the above formula is a 20ms subframe, so that a short DRX cycle is started at the 20ms subframe position, mainly a DRX-onDurationTimer for starting the short DRX cycle, that is, within the DRX-onDurationTimer, the terminal monitors the base station scheduling, and enters an inactive time (i.e., DRX state) if there is no scheduling and data transmission. After the short DRX period is finished, determining that the DRX period of a DRX-ShortCycleTimer terminal is reached, entering a long DRX period at the moment, and starting a DRX-onDurationtimer of the long DRX period from the position of a subframe of 40 ms.

In implementation, a DRX-ShortCycleTimer is started at the next subframe after the DRX-inactivity timer times out or the DRX Command MAC CE is received, so that the starting subframe position of the short DRX cycle avoids the PDCCH occasion that may be occupied by the previous active period.

Example two: and the terminal starts a DRX-ShortCycleTimer at the next symbol after the DRX-inactivytytimer times out or receives a DRX Command MAC CE.

In the embodiment of the invention, after the terminal starts a DRX-ShortCycleTimer at the next symbol, when a subframe capable of receiving a scheduling command starts a short DRX cycle, the terminal determines whether to start the short DRX cycle from the calculated starting subframe position of the first short DRX cycle or start the short DRX cycle from the starting subframe position of the next short DRX cycle according to whether the calculated first short DRX cycle has available scheduling resources; or

And after the terminal starts a DRX-ShortCycleTimer at the next symbol, when a short DRX cycle is started at a subframe capable of receiving a scheduling command, the terminal determines whether to start the short DRX cycle from the calculated starting subframe position of the first short DRX cycle or start the short DRX cycle from the starting subframe position of the next short DRX cycle according to whether the calculated available scheduling resource amount of the first short DRX cycle is greater than a configuration threshold.

The following is a detailed description of the two cases.

The first condition is as follows: and determining which short DRX cycle is started according to whether the calculated first short DRX cycle has available scheduling resources.

Optionally, the terminal starts a DRX-ShortCycleTimer when the DRX-inactivytytimer times out or receives a next symbol of the DRX Command MAC CE;

for example, if the terminal determines that the DRX-inactivity timer times out or receives a DRX Command MAC CE at the 7 th symbol of the 10ms subframe, it starts a DRX-ShortCycleTimer at the 8 th symbol of the 10ms subframe;

the terminal starts a short DRX period in a subframe capable of receiving a scheduling command, and the method comprises the following steps:

the terminal judges whether available scheduling resources exist in a DRX-onDuration timer of a corresponding short DRX period when the DRX-InactivityTimer is started after the DRX-InactivityTimer is overtime or a DRX Command MAC CE is received;

The available scheduling resource refers to a CORESET that the terminal can monitor the PDCCH, which is also called PDCCH occase.

If the configuration parameters are: 40ms represents that one long DRX period is 40 ms; DRX-ShortCycle 10ms means that one short DRX cycle is 10 ms; the DRX-ShortCycleTimer is 1, which means that after 1 short DRX cycle, the short DRX cycle ends, and the terminal enters an active time receiving scheduling command from the beginning of the next long DRX cycle; DRX-StartOffset ═ 0 denotes a radio frame SFN ═ 0, and subframe number ═ 0 is the starting point of the long DRX cycle; drx-onDurationTimer 1ms indicates that the duration of the listening period is 1 ms.

The method comprises the steps that a terminal starts a DRX-ShortCycleTimer at the 8 th symbol of a 10ms subframe, the short DRX period corresponding to the terminal starting DRX-ShortCycleTimer is a short DRX period of 10ms-20ms, the starting subframe position of the short DRX period is the position of the 10ms subframe, the DRX-onDuration timer of the short DRX period is started for 10ms-11ms, and whether available CORESET exists or not is monitored in the 10ms-11ms subframe; since the symbol position with CORESET may be occupied by DRX-inactivytimer, CORESET in the symbol occupied by DRX-inactivytimer is not available, and therefore available CORESET is CORESET which is monitored on the symbol which is not occupied by DRX-inactivytimer in the monitoring period in the short DRX cycle;

therefore, whether available scheduling resources exist in the DRX-onDurationTimer of the short DRX cycle corresponding to the time when the DRX-ShortCycleTimer is started after the DRX-inactivity timer is overtime or the DRX Command MAC CE is received is judged, that is, whether available CORESET exists in the subframes from the 8 th symbol to the 11 th ms in the 10ms subframe is judged;

if available scheduling resources exist, starting a short DRX period at the position of a 10ms subframe, starting counting by the started DRX-ShortCycleTimer, entering a long DRX period after the DRX-ShortCycleTimer passes short DRX periods, namely starting a DRX-onDurationtimer corresponding to the short DRX period at the starting position of the 10ms subframe after determining that available CORESET exists from the 8 th symbol in the 10ms subframe to the 11ms subframe;

fig. 5 is a schematic diagram illustrating a second DRX cycle start according to an embodiment of the present invention; as can be seen from fig. 5, when DRX inactivity timer times out or receives DRX Command MAC CE at the position of the 7 th symbol of the 10ms subframe, DRX-ShortCycleTimer is started at the position of the 8 th symbol of the 10ms subframe, CORESET exists in the 11 th symbol from the 8 th symbol to the 10ms subframe of the 10ms subframe, that is, after DRX inactivity timer times out or receives DRX Command MAC CE, there is available scheduling resource in DRX-onDurationTimer of the short DRX cycle corresponding to when DRX-ShortCycleTimer is started, so DRX-onduration of the short DRX cycle is started at the start position of the 10ms subframe.

Or

If no available scheduling resource exists, otherwise, starting a DRX-onDurationTimer corresponding to the short DRX period at the starting subframe position of the next short DRX period, namely starting the DRX-onDurationTimer corresponding to the short DRX period at the starting position of the 20ms subframe after determining that CORESET is not monitored in the subframes from the 8 th symbol to the 11ms in the 10ms subframe;

fig. 6 is a schematic diagram illustrating a third DRX cycle start according to an embodiment of the present invention; as can be seen from fig. 5, when the DRX Command MAC CE is received or DRX-inactivity timer times out at the position of the 7 th symbol of the 10ms subframe, the DRX-shorttimetimer is started at the position of the 8 th symbol of the 10ms subframe, the CORESET is present in the first 7 symbols of the 10ms subframe, but the CORESET is timed out at the position of the 7 th symbol of the 10ms subframe or the DRX Command MAC CE is received, so that the CORESET present in the first 7 symbols of the 10ms subframe is not available, the CORESET is not present in the 11 th symbols of the 10ms subframe from the 8 th symbol to the 10ms subframe, that is, after the DRX-inactivity timer times out or the DRX Command MAC CE is received, the duiontimer is not available in the DRX-on timer of the corresponding short DRX cycle when the DRX cycle is started, and the starting of the DRX cycle is started at the position of the 20 th DRX subframe.

In implementation, when determining that the DRX-inactivity timer is overtime or receives the next symbol of the DRX Command MAC CE, starting a DRX-ShortCycleTimer, and determining whether there is available scheduling resources in a short DRX cycle corresponding to the DRX-ShortCycleTimer, if there is available scheduling resources, starting a DRX-onDurationTimer at a starting subframe position of the short DRX cycle corresponding to the DRX-ShortCycleTimer to monitor, otherwise, starting a DRX-onDurationTimer at the starting subframe position of the next short DRX cycle to monitor, so that the short DRX cycle does not completely fail, and therefore, it is not necessary to wait for entering an activation time at the starting point of the next long DRX cycle to receive a scheduling Command, and the time for entering the activation time to receive the scheduling Command is shortened, thereby reducing the time delay of data transmission and scheduling.

Case two: and determining which short DRX cycle is started according to whether the calculated number of the available scheduling resources in the first short DRX cycle reaches a configuration threshold.

The terminal starts a DRX-ShortCycleTimer when the DRX-inactivytimer is overtime or receives the next symbol of a DRX Command MAC CE;

the terminal judges whether the number of available scheduling resources in a DRX-onDuration timer of a corresponding short DRX period reaches a threshold or not when the DRX-InactivityTimer is started after the DRX-InactivityTimer is overtime or a DRX Command MAC CE is received;

The threshold is specified by a dedicated scheduling command RRC command configuration or protocol sent to the terminal by the base station, and when the terminal scheduling command configuration is provided, the threshold of the available scheduling resource amount may be configured based on the number of CORESET or the number of subframes.

The number of available scheduling resources may be the number of subframes containing scheduling resources within the onDuration of the short DRX cycle or the number of PDCCH occasions (physical layer mapping to CORESET) that the terminal may monitor.

After the terminal times out the DRX-inactivity timer or receives the DRX Command MAC CE, determining to start the short DRX cycle at the starting subframe position of the short DRX cycle corresponding to the start DRX-ShortCycleTimer according to whether the number of available scheduling resources of the short DRX cycle corresponding to the start of the DRX-ShortCycleTimer reaches a threshold; or starting the short DRX cycle at the starting subframe position of the next short DRX cycle;

the start short DRX cycle is DRX-onDurationTimer that starts the short DRX cycle.

And if the number of the scheduling resources reaches the threshold, starting the short DRX period at the starting subframe position of the short DRX period corresponding to the starting DRX-ShortCycleTimer, otherwise, entering the short DRX period at the starting subframe position of the next short DRX period.

For example, if the configuration parameter is that the threshold of the number of subframes containing the scheduling resources is 2ms, and DRX-onDurationTimer is configured to be 2ms, if two subframes containing the scheduling resources are contained in the DRX-onDurationTimer of the short DRX cycle corresponding to the time when the DRX-ShortCycleTimer is started, the short DRX cycle is entered from the starting point of the short DRX; otherwise, entering a short DRX period at the next short DRX starting point.

In implementation, the terminal determines at which position a DRX-onDurationTimer of a short DRX cycle is started according to whether an available scheduling resource in a subframe of the DRX-ShortCycleTimer reaches a threshold after the DRX-inactivity timer is overtime or a DRX Command MAC CE is received, starts a DRX-onDurationTimer corresponding to the short DRX cycle at a starting subframe position of the short DRX cycle corresponding to the DRX-ShortCycleTimer when it is determined that the available scheduling resource reaches the threshold, and starts a DRX-onDurationTimer corresponding to the short DRX cycle at a starting subframe position of a next short DRX cycle after the DRX-ShortCycleTimer is started, otherwise, starts a DRX-onDurationTimer corresponding to the short DRX cycle at a starting subframe position of a next short DRX cycle after the DRX-ShortCycleTimer is started, so that the short DRX cycle does not completely fail, and does not need to wait for entering of an activation time receiving scheduling Command at a starting point of the next long DRX cycle, the time of entering of the activation time receiving scheduling Command is shortened, and the time delay of data transmission and scheduling is reduced.

Based on the same inventive concept, the embodiment of the present invention further provides a device for starting a DRX cycle, and since the method corresponding to the device is the method for starting the DRX cycle in the embodiment of the present invention, and the principle of the device for solving the problem is similar to the method, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 7, a first apparatus for performing cell handover according to an embodiment of the present invention includes a processor 700, a memory 701, and a transceiver 702;

the processor 700 is responsible for managing the bus architecture and general processing, and the memory 701 may store data used by the processor 700 in performing operations. The transceiver 702 is used to receive and transmit data under the control of the processor 700.

The bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 700, and various circuits, represented by memory 701, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 700 is responsible for managing the bus architecture and general processing, and the memory 701 may store data used by the processor 700 in performing operations.

The processes disclosed in the embodiments of the present invention may be applied to the processor 700, or implemented by the processor 700. In implementation, the steps of the signal processing flow may be performed by instructions in the form of hardware, integrated logic circuits, or software in the processor 700. The processor 700 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like that implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 701, and the processor 700 reads the information in the memory 701, and completes the steps of the signal processing flow in combination with the hardware thereof.

Specifically, the processor 700 is configured to determine that DRX-inactivity timer times out or receives a DRX Command MAC CE;

Optionally, the processor 700 is further configured to:

the drx-ShortCycleTimer is started.

Optionally, the processor 700 is specifically configured to:

and starting a DRX-ShortCycleTimer at the next symbol after the DRX-inactivytimer times out or receives a DRX Command MAC CE.

Optionally, the processor 700 starts a DRX-ShortCycleTimer when the DRX-inactivytimer times out or receives a next symbol of the DRX Command MAC CE;

the processor 700 is specifically configured to:

if available scheduling resources exist, starting a DRX-onDurationTimer corresponding to a short DRX period at a starting subframe position of the corresponding short DRX period when starting the DRX-shortCycleTimer;

Optionally, the processor 700 starts a DRX-ShortCycleTimer after the DRX-inactivity timer times out or receives a DRX Command MAC CE, or receives a next symbol of the DRX Command MAC CE;

the processor 700 is specifically configured to:

judging whether the number of available scheduling resources in a DRX-onDurationTimer of a corresponding short DRX period reaches a threshold or not when the DRX-InactivityTimer is started after the DRX-InactivityTimer is overtime or after a DRX Command MAC CE is received;

Optionally, the threshold is defined by a terminal-specific scheduling command configuration or a protocol.

As shown in fig. 8, a structure diagram of a device for starting a DRX cycle according to the second embodiment of the present invention includes a determining module 800, a starting module 810;

a determining module 800, configured to determine that DRX-inactivity timer times out or receives a DRX Command MAC CE;

an initiating module 810 for initiating a short DRX cycle at a subframe where a scheduling command can be received.

Optionally, the starting module 810 is further configured to:

the drx-ShortCycleTimer is started.

Optionally, the starting module 810 is specifically configured to:

Optionally, the starting module 810 starts a DRX-ShortCycleTimer when the DRX-inactivytimer times out or receives a next symbol of the DRX Command MAC CE;

the starting module 810 is specifically configured to:

Optionally, the starting module 810 starts a DRX short cycletimer after the DRX inactivity timer times out or receives a DRX Command MAC CE or receives a next symbol of the DRX Command MAC CE;

the starting module 810 is specifically configured to:

Embodiments of the present invention further provide a computer-readable medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the method described in fig. 3.

The present invention is described above with reference to block diagrams and/or flowchart illustrations of methods, apparatus (systems) and/or computer program products according to embodiments of the invention. It will be understood that one block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.

Accordingly, the present invention may also be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Furthermore, the invention can take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A discontinuous reception mechanism (DRX) cycle starting method is characterized by comprising the following steps:

the terminal determines that a DRX non-activation timer DRX-inactivity timer is overtime or receives a DRX control media access layer control unit DRX Command MAC CE;

the terminal starts a DRX short cycle timer DRX-ShortCycleTimer and starts a short DRX cycle in a subframe capable of receiving a scheduling command;

wherein, the terminal starts drx-ShortCycleTimer, including:

the terminal starts a DRX-ShortCycleTimer at the next subframe after the DRX-inactivytimer times out or receives a DRX Command MAC CE;

or the terminal starts the DRX-ShortCycleTimer at the next symbol after the DRX-inactivytimer times out or receives the DRX Command MAC CE.

2. The method of claim 1, wherein the terminal starts a DRX-ShortCycleTimer at the DRX-inactivytimer timeout or the next symbol of a DRX Command MAC CE is received;

the terminal judges whether available scheduling resources exist in a DRX monitoring period timer DRX-onDurationtimer of a short DRX period corresponding to the time of the DRX-ShortCycleTimer after the DRX-inactivity timer is overtime or receives a DRX Command MAC CE;

3. The method of claim 1, wherein the terminal starts a DRX-ShortCycleTimer after the DRX-inactivity timer times out or receives a DRX Command MAC CE or receives a next symbol of the DRX Command MAC CE;

if so, starting a DRX-onDurationTimer corresponding to the short DRX period at the starting subframe position of the corresponding short DRX period when starting the DRX-shortCycleTimer;

4. The method of claim 3, wherein the threshold is specified by a terminal-specific scheduling command configuration or protocol.

5. An apparatus for DRX cycle start, the apparatus comprising: a processor, a memory, and a transceiver;

the processor is configured to determine that DRX-inactivity timer is timed out or receives a DRX Command MAC CE;

starting DRX-ShortCycleTime, and starting a short DRX cycle at a subframe capable of receiving a scheduling command;

wherein the processor is specifically configured to:

starting a DRX-ShortCycleTimer at the next subframe after the DRX-inactivytytimer is overtime or the DRX Command MAC CE is received;

or starting a DRX-ShortCycleTimer at the next symbol after the DRX-inactivytytimer times out or receives a DRX Command MAC CE.

6. The apparatus of claim 5, wherein the processor starts a DRX-ShortCycleTimer upon expiration of the DRX-inactivytimer or receipt of a next symbol of a DRX Command MAC CE;

the processor is specifically configured to:

7. The apparatus of claim 5, wherein the processor starts a DRX-ShortCycleTimer after the DRX-inactivity timer times out or receives a DRX Command MAC CE or receives a next symbol of the DRX Command MAC CE;

the processor is specifically configured to:

8. The apparatus of claim 7, wherein the threshold is specified by a terminal-specific scheduling command configuration or protocol.

9. An apparatus for DRX cycle start, the apparatus comprising:

a starting module, which is used for starting DRX-ShortCycleTime and starting a short DRX period in a subframe capable of receiving a scheduling command;

wherein the starting module is specifically configured to:

or starting a DRX-ShortCycleTimer at the next symbol after the DRX-inactivytimer times out or receives a DRX Command MAC CE.

10. A computer-storable medium on which a computer program is stored which, when being executed by a processor, carries out the steps of the method as claimed in any one of the claims 1 to 4.