Activation state alignment method of network side and terminal side in DRX connection state and base station

Abstract

The invention discloses an activated state alignment method of a network side and a terminal side in a DRX connection state and a base station. The method comprises the following steps: recording a first time point when downlink control information is sent to terminal equipment under the condition that an activated state triggering behavior is detected; under the condition that the feedback information is detected, determining a second time point when the feedback information is received; under the condition that the difference value between the second time point and the first time point is not larger than the configured duration, the network side is set to be in an activated state, the first duration is maintained in the activated state, so that the time periods of the network side and the terminal equipment in the activated state in the DRX connection state are aligned, the first duration is consistent with the remaining duration needing to be maintained by the terminal equipment in the activated state, and the first duration is consistent with the remaining duration needing to be maintained by the terminal equipment in the activated state. The first time length is obtained by carrying out difference operation on the configuration time length and the difference value. According to the method and the device, the technical problems of scheduling resource waste and continuous power consumption of the terminal caused by the fact that the time periods of the network side and the terminal side in the activated state are not aligned are solved.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method and a base station for aligning activation states between a network side and a terminal side in a DRX connection state. Background Art

[0002] The discontinuous reception (DRX) mechanism allows user equipment (UE) to configure different parameter values ​​according to different services, so that the parameters match the service type to achieve the best energy saving effect. For example, when the UE is in an active state, the network happens to schedule the UE, and the UE can also detect the corresponding downlink control information (DCI); when the network does not schedule the UE, the UE is in a dormant state, which does not affect data transmission, and the UE sleeps in the gaps when there is no data transmission, saving the UE's power.

[0003] Therefore, when configuring DRX parameters, it is crucial to align the parameters between the network and the UE. If the discontinuous reception parameters on the network side and the terminal side are misaligned, that is, the time periods when the network side and the terminal device are in the active state under the DRX connection state are not aligned, the network will think that the UE is in the active state and send scheduling information, but the actual UE is in the sleep state; or the network thinks that the UE is in the sleep state and is not scheduled on the channel, but in fact the UE is in the active state and has been listening to the messages in the channel. This not only affects the quality of data transmission and wastes scheduling resources, but also consumes too much UE power.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] An embodiment of the present application provides a method and base station for aligning the activation states of the network side and the terminal side in a DRX connection state, so as to at least solve the technical problems of waste of scheduling resources and continuous consumption of terminal power caused by the misalignment of the activation time periods between the network side and the terminal side.

[0006] According to one aspect of an embodiment of the present application, a method for aligning the activation states of the network side and the terminal side in a DRX connection state is provided, comprising: in the case of detecting an activation state triggering behavior, recording a first time point of sending downlink control information to a terminal device, wherein the activation state triggering behavior is a behavior for triggering the network side to enter an activation state and maintain a configured duration in the activation state in a discontinuous reception DRX connection state; in the case of detecting feedback information, determining a second time point at which the feedback information is received, wherein the feedback information is information returned by the terminal device in response to the downlink control information; in the case where the difference between the second time point and the first time point is not greater than the configured duration, setting the network side to be in an activation state, and maintaining a first duration in the activation state, so as to align the time period in which the network side and the terminal device are in the activation state in the DRX connection state, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference.

[0007] Optionally, the activation state triggering behavior includes at least one of the following: detecting a scheduling request sent by a terminal device on a physical uplink control channel; and sending the first downlink control information to the terminal device during data transmission.

[0008] Optionally, in the activation state triggering behavior, when a scheduling request sent by a terminal device is detected, when the activation state triggering behavior is detected, the method also includes: keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration; in the activation state triggering behavior, when the first downlink control information is sent to the terminal device, when the activation state triggering behavior is detected, the method also includes: obtaining the signal-to-noise ratio of the system, and when the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold, keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration.

[0009] Optionally, after acquiring the signal-to-noise ratio of the system, the method further includes: when the signal-to-noise ratio is not less than a preset signal-to-noise ratio threshold, entering an activation state when transmitting the first downlink control information to the terminal device.

[0010] Optionally, the inactivity timer is used to control whether the network side enters an activated state. When the network side needs to be in an inactive state, the inactivity timer is set to an inactive state; when the network side needs to be in an activated state, the inactivity timer is set to an activated state.

[0011] Optionally, the uplink scheduling process and the downlink scheduling process of data transmission correspond to a preset signal-to-noise ratio threshold respectively.

[0012] Optionally, in the activation state triggering behavior, when a scheduling request sent by a terminal device is detected, after the activation state triggering behavior is detected, the method also includes: decoding the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information, and when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device fails to normally receive the downlink control information sent by the network side in response to the scheduling request.

[0013] Optionally, when the activation state triggering behavior is to send the first downlink control information to the terminal device, after detecting the activation state triggering behavior, the method also includes: decoding the data transmitted in the physical transmission shared channel corresponding to the downlink control information to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information; and when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device has failed to normally receive the downlink control information.

[0014] Optionally, the method also includes: in the case where no feedback information is detected, determining whether the number of times the downlink control information is sent to the terminal device exceeds a preset number threshold, wherein the preset number threshold is not greater than the maximum number of retransmissions in the hybrid automatic repeat request set in the system; in the case where the number of times the downlink control information is sent does not exceed the preset number threshold, resending the downlink control information to the terminal device; in the case where the number of times the downlink control information is sent exceeds the preset number threshold, stopping resending the downlink control information to the terminal device, and setting the network side to an inactive state.

[0015] Optionally, the uplink scheduling process and the downlink scheduling process of data transmission respectively correspond to a preset number threshold.

[0016] Optionally, the method further includes: when the difference between the second time point and the first time point is greater than the configured duration, setting the network side to an inactive state.

[0017] According to another aspect of an embodiment of the present application, a communication base station is also provided, including: a memory and a processor, the processor being used to run a program stored in the memory, wherein when the program is running, an activation state alignment method between the network side and the terminal side in a DRX connection state is executed.

[0018] According to another aspect of an embodiment of the present application, a non-volatile storage medium is also provided, the non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the activation state alignment method between the network side and the terminal side in the DRX connection state by running the computer program.

[0019] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a computer program, which, when executed by a processor, implements the steps of a method for aligning activation states between a network side and a terminal side in a DRX connected state.

[0020] In an embodiment of the present application, when an activation state triggering behavior is detected, a first time point of sending downlink control information to a terminal device is recorded, wherein the activation state triggering behavior is a behavior for triggering the network side to enter an activation state and maintain the configured duration in the activation state in a discontinuous reception DRX connection state; when feedback information is detected, a second time point at which the feedback information is received is determined, wherein the feedback information is information returned by the terminal device in response to the downlink control information; when the difference between the second time point and the first time point is not greater than the configured duration, the network side is set to be in an activation state, and the first duration is maintained in the activation state, so that the network side and the terminal device are aligned in the activation state in the DRX connection state. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference. By adjusting the conditions for the network side to enter the activation state, the DRX parameters of the network and the UE are aligned, thereby achieving the purpose of reducing the waste of scheduling resources and the continuous consumption of UE power, thereby solving the technical problems of the waste of scheduling resources and the continuous consumption of terminal power caused by the misalignment of the activation time periods between the network side and the terminal side. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0022] Figure 1 is a schematic diagram of a DRX cycle pattern provided according to an embodiment of the present application;

[0023] Figure 2 It is a schematic diagram of a method flow for aligning activation states of a network side and a terminal side in a DRX connected state according to an embodiment of the present application;

[0024] Figure 3 It is a schematic diagram of a drx-InactivityTimer start process when a PUCCH SR is detected according to an embodiment of the present application;

[0025] Figure 4 It is a schematic diagram of a method flow for enabling a drx-InactivityTimer after a PUCCH SR is detected according to an embodiment of the present application;

[0026] Figure 5 It is a schematic diagram of a drx-InactivityTimer validation process in uplink scheduling provided according to an embodiment of the present application;

[0027] Figure 6 It is a schematic diagram of a method flow for taking effect of a drx-InactivityTimer in uplink scheduling provided in an embodiment of the present application;

[0028] Figure 7 It is a schematic diagram of a drx-InactivityTimer validation process in downlink scheduling provided according to an embodiment of the present application;

[0029] Figure 8 It is a schematic diagram of a method flow for taking effect of a drx-InactivityTimer in downlink scheduling provided in an embodiment of the present application;

[0030] Fig. 9 is a schematic diagram of a DRX processing potential misalignment architecture provided according to an embodiment of the present application;

[0031] Fig.10 It is a structural diagram of an activation state alignment device of a network side and a terminal side in a DRX connection state provided according to an embodiment of the present application;

[0032] Fig.11 It is a hardware structure block diagram of a computer terminal (or electronic device) according to an embodiment of the present application, which is provided for realizing a method for aligning the activation states of the network side and the terminal side in the DRX connection state. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] In order to facilitate those skilled in the art to better understand the embodiments of the present application, the discontinuous reception DRX mechanism involved in the embodiments of the present application is now explained:

[0036] DRX configures a series of parameters of the UE to determine the activation time and sleep time of the UE. The UE monitors the physical downlink control channel (PDCCH) only during the activation time and does not monitor the PDCCH channel during the sleep time. To achieve the above purpose, DRX configures a set of parameters to form a repetitive periodic cycle, such as Figure 1 As shown, within a DRX cycle, the time when the UE can detect the PDCC H channel is the activation time, which is determined by the discontinuous reception activation timer drx-onDurationTimer. When there is data transmission between the network and the UE, there is a high probability that there will still be data transmission in the next period of time, so the discontinuous reception inactivity timer drx-InactivityTimer is designed. During this timer, the UE can detect the PDCCH channel, which is the activation time. Whenever there is a new DCI, the drx-InactivityTimer will be updated or restarted, that is, only when there is a new PDCCH DCI, the drx-InactivityTimer will be started or updated.

[0037] The above series of parameters of DRX can be configured to UE by the network side through Radio Resource Control (RRC). The specific combination of a set of parameters is called a DRX profile. For example, if DRX-cycle is configured to 320ms, drx-InactivityTimer is configured to 80ms, drx-onDurationTimer is configured to 20ms, etc., it is a DRX profile. When one of drx-onDurationTimer and drx-InactivityTimer is running or the Physical Uplink Control Channel (PUCCH) SR sent by the UE is still in the pending state, it is considered to be in the activated state of DRX.

[0038] In related technologies, UE energy saving has always been an important issue in wireless communications. The 3rd Generation Partnership Project (3GPP) has also customized many functions for it to achieve the effect of UE energy saving, among which DRX is a key one.

[0039] DRX allows UE to configure different parameter values ​​according to different services, that is, different DRX profiles, so that the parameters match the service type to achieve the best energy saving effect. For example, when the UE is in an active state, the network happens to schedule the UE, and the UE can also detect the corresponding DCI; when the network does not schedule the UE, the UE is in a dormant state, which does not affect data transmission, and the UE sleeps in the gaps when there is no data transmission, saving the UE's power.

[0040] Since the UE detects PDCCH only during the active time and not during the sleep time, if the network and UE have inconsistent understandings of the parameter alignment time, it will seriously affect the data transmission quality between the network and the UE, not only failing to achieve UE energy saving, but also causing serious waste of scheduling resources on the network side.

[0041] For example, when the network believes that it is during the DRX activation time and sends DCI, but the UE is actually in the sleep time, it will lead to a waste of network scheduling resources; when the network believes that it is during the DRX sleep time and does not transmit the scheduling DCI on the PDCCH, but the UE is in the DRX activation time and has been monitoring the DCI information of the PDCCH channel, it will not only increase the delay of the network scheduling data, but also waste the UE's power.

[0042] Therefore, when configuring DRX parameters, it is crucial for the network and UE to align the parameters. If the parameters cannot be aligned, the scenario described above will occur, which will not only affect the quality of data transmission, waste scheduling resources, but also consume too much UE power.

[0043] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0044] According to an embodiment of the present application, a method embodiment for aligning the activation state of the network side and the terminal side in the DRX connection state is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0045] The embodiment of the present application provides a method for aligning activation states of a network side and a terminal side in a DRX connected state. Figure 2 is a schematic diagram of a method flow for aligning the activation state of the network side and the terminal side in a DRX connected state according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0046] Step S202, when an activation state triggering behavior is detected, recording the first time point of sending downlink control information to the terminal device, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state in the discontinuous reception DRX connection state and maintain the configured time in the activation state;

[0047] In some embodiments of the present application, the above-mentioned activation state triggering behavior includes at least one of the following: detecting a scheduling request sent by a terminal device on a physical uplink control channel, for example, after the network side detects a scheduling request (Scheduling Request, SR) on the PUCCH, the behavior of sending a PDCCH uplink Grant scheduling DCI; during data transmission, sending the first downlink control information to the terminal device, for example, the behavior of sending the first transmission DCI during the uplink scheduling process of data transmission, and the behavior of sending the first transmission DCI during the downlink scheduling process of data transmission.

[0048] Step S204, in the case where feedback information is detected, determining a second time point at which the feedback information is received, wherein the feedback information is information returned by the terminal device in response to the downlink control information;

[0049] In the embodiment of the present application, the feedback information may include: positive acknowledgment (ACK) or negative acknowledgment (NACK).

[0050] Step S206, when the difference between the second time point and the first time point is not greater than the configured duration, set the network side to be in an activated state, and maintain the first duration in the activated state, so that the network side and the period when the terminal device is in the activated state in the DRX connection state are aligned, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activated state, and the first duration is obtained by taking the difference between the configured duration and the difference.

[0051] Through the above steps, by adjusting the conditions for activation state, the DRX parameters of the network and UE are aligned, that is, the time periods when the network side and the terminal device are in the activation state in the DRX connection state are aligned, thereby achieving the purpose of reducing the waste of scheduling resources and the continuous consumption of UE power, thereby solving the technical problem of waste of scheduling resources and continuous consumption of terminal power caused by the misalignment of the time periods when the network side and the terminal side are in the activation state.

[0052] The following further introduces the activation state alignment method between the network side and the terminal side in the DRX connection state in steps S202 to S206 of the embodiment of the present application.

[0053] When an activation state triggering behavior is detected, in addition to recording the first time point of sending downlink control information to the terminal device, the embodiment of the present application will also perform the following steps.

[0054] In some embodiments of the present application, when the activation state triggering behavior is to detect a scheduling request sent by a terminal device, when the activation state triggering behavior is detected, the method also includes the following steps: keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration; when the activation state triggering behavior is to send the first downlink control information to the terminal device, when the activation state triggering behavior is detected, the method also includes the following steps: obtaining the signal-to-noise ratio of the system, and when the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold, keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration.

[0055] Specifically, when the activation state triggering behavior is the detection of a scheduling request sent by a terminal device, that is, when the network side detects a PUCCH SR, the network side will initiate a DCI to schedule the UE corresponding to this SR (send an uplink Grant), but after sending the DCI, it will not enter the activation state, but only record the first time point when the downlink control information is sent to the terminal device, and put the network side in an inactive state.

[0056] During the uplink scheduling process or downlink scheduling process of data transmission, when the first DCI is sent to the terminal device, it is necessary to first determine whether the system's signal-to-noise ratio is greater than the preset signal-to-noise ratio threshold; if the system's current signal-to-noise ratio Sinr (Signal to Interference plus Noise Ratio, abbreviated as: signal-to-noise ratio) is less than the preset signal-to-noise ratio threshold, it is considered that the probability that the first transmitted DCI can be correctly received by the terminal is small. At this time, the system will not enter the activated state at the time when the first transmitted DCI is sent, but only record the first time point of transmitting the first downlink control information, and make the network side in an inactive state.

[0057] In addition, if the signal-to-noise ratio of the system is greater than or equal to the preset signal-to-noise ratio threshold, the following steps are performed.

[0058] In some embodiments of the present application, after acquiring the signal-to-noise ratio of the system, the method further includes the following steps: when the signal-to-noise ratio is not less than a preset signal-to-noise ratio threshold, entering an activation state when transmitting the first downlink control information to the terminal device.

[0059] Specifically, if the current Sinr of the system is greater than or equal to a preset signal-to-noise ratio threshold, it is considered that the first transmission DCI can be correctly received. At this time, the network side is set to enter the activation state directly at the first time point when the first transmission DCI is sent.

[0060] It should be noted that the uplink scheduling process and the downlink scheduling process of data transmission may respectively correspond to a preset signal-to-noise ratio threshold, that is, the preset signal-to-noise ratio thresholds corresponding to the uplink scheduling process and the downlink scheduling process may be the same or different. In the embodiment of the present application, the preset signal-to-noise ratio threshold corresponding to the uplink scheduling process is represented by ul_Sinr_Setting, and the preset signal-to-noise ratio threshold corresponding to the downlink scheduling process is represented by drx_Dl_Sinr_Setting.

[0061] Furthermore, in the embodiment of the present application, whether the network side enters the activation state can be controlled by setting whether the inactivity timer is started or not, as follows.

[0062] In some embodiments of the present application, the inactivity timer is used to control whether the network side enters an activated state. When the network side needs to be in an inactive state, the inactivity timer is set to an inactive state. When the network side needs to be in an activated state, the inactivity timer is set to an activated state.

[0063] Taking this control method as an example, the processing flow when the above-mentioned various activation state triggering behaviors are detected is further introduced below.

[0064] 1) When the activation state triggering behavior is the detection of a scheduling request sent by a terminal device, that is, when the network side detects a PUCCH SR, the network side initiates a DCI to schedule the UE of this SR (send an uplink Grant). After sending the DCI, the inactivity timer drx-InactivityTimer is kept not started (even if the network side is in an inactive state), but only the timestamp of the start of the drx-InactivityTimer is recorded (that is, the first time point of sending downlink control information to the terminal device is recorded).

[0065] In addition, after the network side initiates the DCI for scheduling the UE corresponding to the SR (sending an uplink Grant), the data transmitted in the physical uplink shared channel corresponding to the SR will also be decoded. The specific steps are as follows.

[0066] In some embodiments of the present application, in the case where the activation state trigger behavior is to detect a scheduling request sent by a terminal device, after the activation state trigger behavior is detected, the method also includes the following steps: decoding the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information, and when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device has failed to normally receive the downlink control information sent by the network side in response to the scheduling request.

[0067] Specifically, the data transmitted in the physical uplink shared channel (PUSCH) corresponding to the SR is decoded to obtain a decoding result. If the PUSCH decoding result is non-DTX (Discontinuous Transmission), that is, ACK or NACK, it means that there is a response to the SR scheduling on the PUSCH channel, that is, the UE has detected the Grant on the PDCCH. At this time, it is determined that the terminal device has returned feedback information, that is, the UE is in an activated state when sending Grant on the network side. Otherwise, it is determined that the terminal device has not returned feedback information.

[0068] 2) In the case of the activated state triggering behavior, when the first downlink control information is sent to the terminal device, that is, in the uplink scheduling process or downlink scheduling process of data transmission, when the first DCI is sent to the terminal device, first determine whether the system's signal-to-noise ratio is greater than the preset signal-to-noise ratio threshold. If the system's current signal-to-noise ratio Sinr is less than the preset signal-to-noise ratio threshold, then at the time point when the first transmitted DCI is sent, keep the drx-InactivityTimer from being started, and only record the drx-InactivityTimer timestamp (that is, record the first time point when the first downlink control information is transmitted); if the system's current signal-to-noise ratio Si nr is not less than the preset signal-to-noise ratio threshold, directly start the drx-InactivityTimer at the first time point when the first transmitted DCI is sent.

[0069] In addition, after the first DCI is sent to the terminal device, the data transmitted in the physical transmission shared channel corresponding to the DCI will also be decoded. The specific steps are as follows.

[0070] In some embodiments of the present application, when the activation state triggering behavior is to send the first downlink control information to the terminal device, after detecting the activation state triggering behavior, the method also includes the following steps: decoding the data transmitted in the physical transmission shared channel corresponding to the downlink control information to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information, and when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device has failed to normally receive the downlink control information.

[0071] Among them, in the uplink scheduling process of data transmission, the physical transmission shared channel scheduled by the downlink control information is the physical uplink shared channel, and in the downlink scheduling process of data transmission, the physical transmission shared channel scheduled by the downlink control information is the physical downlink shared channel.

[0072] Specifically, if the decoding result is not DTX (that is, ACK / NACK), it means that the UE has detected the above-mentioned first transmission DCI, and it is determined that the terminal device has returned feedback information, that is, the UE is in an active state when sending the first transmission DCI on the network side. If the decoding result is DTX, it is determined that no feedback information is detected.

[0073] In the processing flow corresponding to the above-mentioned various activation state triggering behaviors, after decoding the data in the channel, if it is determined that no feedback information is detected, it is possible to choose to resend the downlink control information to the terminal. The specific steps are as follows.

[0074] In some embodiments of the present application, the method also includes the following steps: in the case where no feedback information is detected, determining whether the number of times the downlink control information is sent to the terminal device exceeds a preset number threshold, wherein the preset number threshold is not greater than the maximum number of retransmissions in the hybrid automatic repeat request set in the system; in the case where the number of times the downlink control information is sent does not exceed the preset number threshold, resending the downlink control information to the terminal device; in the case where the number of times the downlink control information is sent exceeds the preset number threshold, stopping resending the downlink control information to the terminal device, and setting the network side to an inactive state.

[0075] Specifically, when the decoding result of the signal corresponding to SR or DCI is DTX, it means that the UE has not detected the DCI on the corresponding channel. At this time, it is determined that the network side has not detected the feedback information. In this case, it can be determined whether the number of times the network side sends downlink control information to the terminal exceeds the configured preset number threshold. If it is greater than the preset number threshold, stop resending the downlink control information to the terminal device and delete the inactivity timer; if it is not greater than the preset number threshold configured by the system, continue the current scheduling, resend the downlink control information to the terminal device, and determine whether the feedback information of the terminal device can be detected based on the decoding result.

[0076] It should be noted that the above-mentioned preset number threshold may have different settings in the processing flow corresponding to each type of activation state triggering behavior. For example, the preset number threshold may be equal to or different from the maximum number of retransmissions of the hybrid automatic repeat request (HARQ) set by the system, which is described in detail below.

[0077] Specifically, if no feedback information is detected when the activation state triggering behavior is detecting a scheduling request sent by a terminal device; or if no feedback information is detected when the activation state triggering behavior is sending the first downlink control information to the terminal device and the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold, then in this embodiment, the preset number threshold at this time can be set to be equal to the maximum number of retransmissions in the hybrid automatic repeat request set in the system.

[0078] If the triggering behavior in the activation state is to send the first downlink control information to the terminal device, and the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, and no feedback information is detected, then in this embodiment, the preset number threshold at this time can be set to be less than the above-mentioned maximum number of retransmissions. In addition, in this case, the uplink scheduling process and the downlink scheduling process of data transmission correspond to a preset number threshold respectively, that is, the preset number thresholds corresponding to the uplink scheduling process and the downlink scheduling process can be the same or different. In the embodiment of the present application, the preset number threshold corresponding to the uplink scheduling process is represented by drx_Ul_Count_Setting, and the preset number threshold corresponding to the downlink scheduling process is represented by drx_Dl_Count_Setting.

[0079] In the processing flow corresponding to the above-mentioned different types of activation state triggering behaviors, after decoding the data in the channel, when it is determined that feedback information is detected, it is necessary to determine the second time point when the feedback information is received, and based on the recorded first time point when the downlink control information is sent to the terminal device and the above-mentioned second time point, determine whether the drx_InactivityTimer has timed out at this time, that is, determine whether the difference between the second time point and the first time point is greater than the configured duration.

[0080] If there is no timeout (that is, the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactivity timer), the network side is set to be in an activated state (including entering the activated state or maintaining the activated state). Specifically, if the network side was previously in an inactive state, that is, in a process where the activation state triggering behavior is detecting a scheduling request sent by the terminal device, or where the activation state triggering behavior is sending the first downlink control information to the terminal device, and the system signal-to-noise ratio is less than the preset signal-to-noise ratio threshold, and the inactivity timer is kept inactive, then the above-mentioned drx_InactivityTimer is started and effective at this time to make the network side enter the activated state; if the network side was previously in an activated state, that is, in a process where the activation state triggering behavior is sending the first downlink control information to the terminal device, and the system signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, and the inactivity timer is directly started, then the inactivity timer start state is kept unchanged at this time.

[0081] If it has timed out (ie, the difference between the second time point and the first time point is greater than the configured duration corresponding to the inactivity timer), the network side is set to an inactive state, that is, the above drx_InactivityTimer is deleted.

[0082] The present application scheme provides a corresponding inactive timer control strategy for the above three different activation state triggering behaviors (including: 1. detecting a scheduling request sent by a terminal device on a physical uplink control channel; 2. sending the first downlink control information to the terminal device during the uplink scheduling of data transmission; 3. sending the first downlink control information to the terminal device during the downlink scheduling of data transmission), which can dynamically identify and avoid misalignment on the network side and the UE side in the DRX connection state, and can make corrections in time.

[0083] The following further describes the overall process in each scenario with respect to the communication scenarios corresponding to the three different activation state triggering behaviors.

[0084] Scenario 1: drx-InactivityTimer validation method when SR is detected on PUCCH (i.e., the activation state trigger behavior is a communication scenario when a scheduling request sent by a terminal device is detected on the physical uplink control channel);

[0085] In the related art, there may be a false detection of SR on PUCCH. In this embodiment, the false detection SR is called a false SR. If the network side detects a false SR, the network considers it to be an SR and is in the activated state of DRX. That is, the network considers it to be in the activated state of DRX when it detects the SR. However, since it is a false detection of a false SR, the UE is actually in the dormant state and does not detect the DCI on the PDCCH. If the network schedules and sends DCI for this false SR, and immediately starts the drx-InactivityTimer, the UE in the dormant state will not detect the DCI on the PDCCH, thereby wasting scheduling resources. That is, the scheduling of the UE by the network scheduler for other reasons during the relevant drx_InactivityTimer will cause a waste of scheduling resources because the UE does not detect the PDCCH in the dormant state. However, if the SR on the PUCCH is not a false SR, but a PUCCH SR sent normally by the UE, then it is in the activated state of DRX. The network should normally schedule and send the PDCCH uplink Grant scheduling DCI, and the UE should also normally detect the DCI on the PDCCH channel.

[0086] In order to ensure that the discontinuous reception parameters of the network side and the terminal side are aligned when it is impossible to determine whether the SR is a false SR, the following steps are provided in the embodiment of the present application. Figure 3As shown, when the network detects a PUCCH SR, that is, when a scheduling request on the physical uplink control channel is detected, after scheduling and sending DCI for this SR, the drx-InactivityTimer is not started immediately, but only the timestamp of the start of the drx-InactivityTimer is recorded (that is, the first time point when the downlink control information is sent to the terminal device). The time point when the drx-IactivityT imer takes effect is when the data of the corresponding scheduled PUSCH is detected, that is, the time point when the data is decoded as ACK or NACK (that is, the second time point when ACK or NACK is received). If the corresponding drx-IactivityTimer still has not timed out at this time, it takes effect, that is, the remaining drx-InactivityTimer time period is considered to be the UE activation time.

[0087] Furthermore, when the decoding result of the acquired physical uplink shared channel is not ACK or NACK, it is also possible to determine whether to continue retransmission according to the maximum number of retransmissions (that is, the preset number threshold in this case is directly set to the maximum number of retransmissions). The specific process is as follows: Figure 4 As shown in the figure, when the network side detects a PUCCH SR, regardless of whether it is a false SR or not, the UE that initiates the SR is scheduled (uplink Grant is sent), but the drx_InactivityTimer is not started because the first transmitted DCI is sent, but only its timestamp (that is, the first time point mentioned above) is recorded; after decoding the PUSCH of the corresponding scheduled SR, it is determined whether the decoding result is DTX.

[0088] If the PUSCH decoding result is non-DTX, that is, ACK or NACK, it means that there is a response to the SR scheduling on the PUSCH channel, that is, the UE has detected the Grant on the PDCCH, that is, the UE is in an active state when sending the Grant on the network side. In this case, it is determined whether the drx_InactivityTimer has timed out. If it has not timed out (that is, the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactivity timer), this drx_InactivityTimer is started. If it times out, this drx_InactivityTimer is deleted, that is, when the difference between the second time point and the first time point is greater than the configured duration corresponding to the inactivity timer, the inactivity timer is deleted.

[0089] If the above PUSCH decoding result is DTX, it means that the UE has not detected the DCI situation on the corresponding PDCCH channel, and determines whether the maximum number of PUSCH HARQ retransmissions set by the system is reached. If it is reached (that is, the number of downlink control information sent is greater than or equal to the maximum number of retransmissions), the above drx_InactivityTimer is deleted; if the maximum number of HARQ retransmissions set by the system is not reached (that is, the number of downlink control information sent is less than the maximum number of retransmissions), the above SR scheduling is continued, the downlink control information is resent to the terminal device (UE), and it is determined whether the decoding result of the corresponding PUSCH after the above SR scheduling is DTX; at this time, when the scheduling of this UE for other reasons needs to check the drx_InactivityTimer, it is still considered that the drx_InactivityTimer of this record timestamp is not effective.

[0090] Scenario 2: drx-InactivityTimer validation method in uplink scheduling (i.e., the activation state triggering behavior is the communication scenario when the first downlink control information is sent to the terminal device during the uplink scheduling of data transmission);

[0091] In the uplink data transmission process (i.e. the uplink scheduling process of data transmission), the first transmitted DCI of the data, that is, the first Grant of a packet of data, is crucial. For data transmission, it is RV version 0. At the same time, for DRX, it is also the time point when the network and UE start the drx-InactivityTimer at the same time. If the first transmitted DCI is not detected by the UE, the effective time of the drx-InactivityTimer will not be aligned between the network and the UE, and the UE cannot correctly start the drx-InactivityTimer. Then, the scheduling DCI (Grant) for other reasons for this UE will not be detected by the UE, resulting in a waste of scheduling resources on the network side.

[0092] In order to solve the above problems, the following solutions are provided in the embodiments of the present application.

[0093] In the embodiment of the present application, two parameters are configured for the uplink scheduling process of data transmission: drx_Ul_Sinr_Setting (preset signal-to-noise ratio threshold) and drx_Ul_Count_Setting (i.e., preset number threshold) which is less than the maximum number of HARQ retransmissions. After the network sends the scheduling Grant for the first transmission of DCI on the PDCCH channel (i.e., after sending the downlink control information to the terminal device through the physical downlink control channel), it first checks whether the system Sinr is greater than or equal to the empirical configuration parameter drx_Ul_Sinr_Setting, i.e., determines whether the system signal-to-noise ratio is greater than or equal to the preset signal-to-noise ratio threshold.

[0094] like Figure 5 As shown in the figure, if the current Sinr of the system is less than ul_Sinr_Setting, that is, the signal-to-noise ratio is less than the preset signal-to-noise ratio threshold, it is considered that the probability of the first transmission of PDCCH being correctly received is small, and the drx-InactivityTimer is not started at the time when the first transmission DCI is sent, but only the drx-InactivityTimer timestamp is recorded (that is, the first time point of transmitting the first downlink control information is recorded). If PUSCH is detected within the maximum number of transmissions of PUSCH HARQ, that is, when the data on the PUSCH channel is decoded as ACK or NACK, if the drx-InactivityTimer still has not timed out at this time, the drx-InactivityTimer is started.

[0095] If the current Sinr of the system is greater than or equal to drx_Ul_Sinr_Setting, that is, when the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, it is considered that the first transmission of PDCCH can be correctly received, and dr x-InactivityTimer is started at the time when the first transmission DCI is sent. At the same time, if continuous PUSCH detection is DTX, and the number of continuous detections is greater than drx_Ul_Count_Setting, cancel this drx-InactivityTimer, and align the activation time of the network and UE to the drx-onDurationTimer of the DRX cycle. The specific steps are as follows.

[0096] The overall process is as follows Figure 6 As shown, if the system Sinr is greater than or equal to the empirical configuration parameter drx_Ul_Sinr_Setting, that is, the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, the drx_InactivityTimer is immediately started on the network side. After the drx_InactivityTimer has taken effect, the PUSCH channel corresponding to the Grant scheduling is decoded to determine whether the decoding result is DTX. If it is not DTX (that is, ACK / NACK), it means that the UE has detected the Grant on the above PDCCH, that is, the UE is in an active state when sending the Grant on the network side, and then enters the normal DRX process.

[0097] If the decoding result is DTX, determine whether the number of consecutive DTXs in PUSCH decoding is greater than the system configuration parameter drx_Ul_Count_Setting (in this embodiment, each downlink control information sent corresponds to a decoding result), that is, determine whether the number of times the downlink control information is sent to the terminal device exceeds the preset number threshold. If it is greater than this system configuration parameter, cancel and delete the above-mentioned drx_InactivityTimer (there may be a situation where the UE does not detect the DCI on the PDCCH), that is, when the number of times the downlink control information is sent exceeds the preset number threshold, stop resending the downlink control information to the terminal device, cancel and delete the inactivity timer; if the number of consecutive DTXs in PUSCH decoding is not greater than the system configuration parameter drx_Ul_Count_Setting, that is, when the number of times the downlink control information is sent does not exceed the preset number threshold, continue the scheduling of the above-mentioned PUSCH, resend the downlink control information to the terminal device, and determine whether the PUSCH decoding result is DTX.

[0098] On the other hand, if the system Sinr is less than the empirical configuration parameter drx_Ul_Sinr_Setting, that is, when the signal-to-noise ratio is less than the preset signal-to-noise ratio threshold, the network side does not start drx_InactivityTimer, but only records its timestamp (that is, records the first time point of transmitting the first downlink control information), decodes the PUSCH channel corresponding to the Grant scheduling, and determines whether the decoding result is DTX;

[0099] If the decoding result is not DTX (that is, ACK / NACK), it means that the UE has detected the Grant on the above PDCCH, that is, the UE is in an active state when sending the Grant on the network side. Determine the second time point when the ACK or NACK is received, and judge whether the drx_InactivityTimer has timed out at this time. If it has not timed out (that is, the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactivity timer), start and take effect the above drx_In activityTimer. If it has timed out, delete the above drx_InactivityTimer.

[0100] If the decoding result is DTX, determine whether the number of PUSCH scheduling times has reached the maximum number of HARQ retransmissions configured by the system (that is, the preset number threshold in this case is directly set to the maximum number of retransmissions), that is, determine whether the number of downlink control information sent to the terminal device exceeds the maximum number of retransmissions. If it has been reached, delete the above-mentioned drx_InactivityTimer, that is, stop resending the downlink control information to the terminal device, and delete the inactivity timer; if the number of PUSCH scheduling times has not reached the maximum number of HARQ retransmissions configured by the system, continue the scheduling of the above-mentioned PUSCH, resend the downlink control information to the terminal device, and determine whether the PUSCH decoding result is DTX.

[0101] Scenario 3: drx-InactivityTimer validation method in downlink scheduling (i.e., the activation state triggering behavior is the communication scenario when the first downlink control information is sent to the terminal device during the downlink scheduling of data transmission);

[0102] In the normal downlink data transmission process (i.e. the downlink scheduling process of data transmission), the first transmitted DCI of the data, that is, the first Assignment of a packet of data, is crucial. For data transmission, it is RV version 0, and for DRX, it is the time point when the network and UE start the drx-InactivityTimer at the same time. If the DCI is not detected by the UE, the effective time of the drx-InactivityTimer will not be aligned on the network and UE sides, and the UE side cannot correctly start the drx-InactivityTimer. Then, the DCI (Assignment) scheduled for other reasons for this UE will not be detected by the UE, which will lead to a waste of scheduling resources on the network side.

[0103] In order to solve the above problems, the following solutions are provided in the embodiments of the present application.

[0104] In the embodiment of the present application, two parameters are configured for the downlink scheduling process of data transmission: drx_Dl_Sinr_Setting (preset signal-to-noise ratio threshold) and drx_Dl_Count_setting (i.e., preset number threshold) which is less than the maximum number of HARQ retransmissions. After the network sends the scheduling assignment of the first DCI transmission on the PDCCH channel (i.e., after sending the downlink control information to the terminal device through the physical downlink control channel), it will first check whether the system Sinr is greater than or equal to the empirical configuration parameter drx_Dl_Sinr_Setting, that is, determine whether the system signal-to-noise ratio is greater than or equal to the preset signal-to-noise ratio threshold.

[0105] like Figure 7As shown, when the current Sinr of the system is less than drx_Dl_Sinr_Setting, that is, when the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, it is considered that the probability of the first transmission of PDCCH being correctly received is small, and the drx-InactivityTimer is not started at the time point when the first transmission DCI is sent, but only the drx-InactivityTimer timestamp is recorded (that is, the first time point when the first downlink control information is transmitted). If the decoding result of the physical downlink shared channel (Physical Down link Shared Channel, PDSCH) has ACK or NACK reported within the corresponding HARQ maximum transmission times, it means that both PDCCH and PDSCH can be correctly detected. If the drx-InactivityTimer still has not timed out at this time, the drx-InactivityTimer is started.

[0106] If the current Sinr of the system is greater than or equal to drx_Dl_Sinr_Setting, that is, when the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, it is considered that the first transmission of DPCCH can be correctly received, and dr x-InactivityTimer is started at the time when the first transmission DCI is sent. If continuous PDSCH detection and decoding are DTX, and the number of continuous detections is greater than drx_Dl_Count_Setting, cancel this drx-InactivityTimer, align the activation time of the network and UE and return it to the drx-onDurationTimer time of the DRX cycle.

[0107] Among them, the PDSCH decoding result is reported to the scheduler in PUCCH or PUSCH. If the corresponding DCI is not detected, PUCCH or PUSCH will not report the corresponding PDSCH decoding result. The network side considers PDSCH feedback that does not report the corresponding decoding result as DTX.

[0108] The overall process is as follows Figure 8 As shown, if the system Sinr is greater than or equal to the empirical configuration parameter drx_Dl_Sinr_Setting, that is, the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, the drx_InactivityTimer is immediately started on the network side; after the drx_InactivityTimer has taken effect, the corresponding Assignment scheduling PDSCH channel is checked to determine whether the decoding result is DTX. If it is not DTX (that is, ACK / NACK), it means that the UE has detected the Assignment on the above PDCCH, that is, the UE is in an active state when sending the Assignment on the network side, and then enters the normal DRX process.

[0109] If the decoding result is DTX, determine whether the number of consecutive DTXs is greater than the system configuration parameter drx_Dl_Count_Setting, that is, determine whether the number of times the downlink control information is sent to the terminal device exceeds the preset number threshold. If it is greater than this system configuration parameter, cancel and delete the above-mentioned drx_InactivityTimer (it may be that the UE does not detect the DCI on the PDCC H), that is, when the number of times the downlink control information is sent exceeds the preset number threshold, stop resending the downlink control information to the terminal device, cancel and delete the inactivity timer; if the number of consecutive DTXs is not greater than the system configuration parameter drx_Dl_Count_Setting, that is, when the number of times the downlink control information is sent does not exceed the preset number threshold, continue the scheduling of the above-mentioned PDSCH, resend the downlink control information to the terminal device, and determine whether the PDSCH channel feedback result is DTX.

[0110] On the other hand, if the system Sinr is less than the empirical configuration parameter drx_Dl_Sinr_Setting, that is, when the signal-to-noise ratio is less than the preset signal-to-noise ratio threshold, the network side does not start drx_InactivityTimer, but only records its timestamp (that is, records the first time point of transmitting the first downlink control information), and checks whether the PDSCH channel feedback scheduled by the corresponding Assignment is DTX, that is, determines whether the decoding result is DTX;

[0111] If the decoding result is not DTX (that is, ACK / NACK), it means that the UE has detected the Assignment on the above PDCCH, that is, the UE is in an active state when the network sends the Assignment. It is determined whether the drx_Inactivity Timer has timed out at this time. If it has not timed out (that is, the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactivity timer), the above drx_InactivityTimer is started and effective. If it has timed out, the above drx_InactivityTimer is deleted.

[0112] If the decoding result is DTX, determine whether the number of PDSCH scheduling times has reached the maximum number of HARQ retransmissions configured by the system (that is, the preset number threshold in this case is directly set to the maximum number of retransmissions), that is, determine whether the number of downlink control information sent to the terminal device exceeds the maximum number of retransmissions. If it has been reached, delete the above-mentioned drx_InactivityTimer, that is, stop resending the downlink control information to the terminal device, and delete the inactivity timer; if the number of PDSCH scheduling times has not reached the maximum number of HARQ retransmissions configured by the system, continue the scheduling of the above-mentioned PDSCH, resend the downlink control information to the terminal device, and determine whether the corresponding scheduled PDSCH channel feedback is DTX.

[0113] It should be noted that in the implementation of the application, in scenarios 2 and 3, the values ​​of the preset signal-to-noise ratio threshold (drx_Ul_Sinr_Setting / drx_Dl_Sinr_Setting) and the preset number threshold (drx_Ul_Sinr_Setting / drx_Dl_Count_setting) corresponding to the uplink scheduling process and the downlink scheduling process of data transmission may be the same or different, and there is no restriction on this.

[0114] The solution of the present application provides a processing strategy for solving the potential misalignment problem of the network and UE in the DRX connected state in three different communication scenarios. It can dynamically identify and avoid misalignment on the network side and the UE side in the DRX connected state, and can make corrections in time, thereby achieving rapid recovery after the misalignment scenario, reducing the waste of scheduling resources and the continuous consumption of UE power, and the implementation method is simple.

[0115] The method embodiment provided in the embodiment of the present application can be applied in a new radio (NR) wireless base station, and can be specifically applied through Fig. 9 The architecture shown is implemented as Fig. 9As shown, the DRX profile container unit (configuration container unit) D1 is used to store DRX-related profile parameters, including DRX parameters such as drx-LongCycleStartOffset, dr x-SlotOffSet, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL. Among them, whether the drx-InactivityTimer is running at the current scheduling time or scheduling slot needs to be marked in this unit, which is specifically determined by the DRX activation decision unit D3.

[0116] The DRX parameter setting unit D2 is used to store DRX related setting parameters and parameters related to or interacting with the scheduler, including drx_Ul_Sinr_Setting (preset signal-to-noise ratio threshold corresponding to the uplink scheduling process of data transmission), drx_Ul_Count_Setting (preset number threshold corresponding to the uplink scheduling process of data transmission), drx_Dl_Sinr_Setting (preset signal-to-noise ratio threshold corresponding to the downlink scheduling process of data transmission), drx_Ul_Count_Setting (preset number threshold corresponding to the downlink scheduling process of data transmission), and the signal to interference plus noise ratio of the current channel, the current decoding result of PUSCH, including: discontinuous transmission DTX, positive acknowledgment ACK or negative acknowledgment NACK, and the physical downlink shared channel PDSCH decoding result feedback at the UE end (DTX, ACK or NACK). These parameters are the basis for the DRX activation decision unit D3 to determine whether the drx-InactivityTimer in the DRX profile container unit D1 is running at the current scheduling time or scheduling slot.

[0117] The DRX activation decision unit D3 is used to decide whether the drx_InactivityTimer is running or not. By obtaining the relevant scheduler parameters in the DRX parameter setting unit D2 and the DRX-related configuration parameters in the DRX profile container unit D1, combined with the current UE scheduling scenario (SR pending, uplink scheduling or downlink scheduling), it is determined whether the drx_InactivityTimer is running at the current time (slot); whether there is a misalignment, if so, the corresponding execution strategy is given; and whether the drx_InactivityTimer should continue to run or should be cancelled.

[0118] It should be noted that the above Fig. 9 The architecture shown can be located inside the scheduler as a scheduler submodule to obtain the scheduling information and uplink and downlink channel information of the UE from the scheduler; it can also be parallel to the scheduler logic to obtain the scheduling information and uplink and downlink channel information of the UE from the scheduler in the form of messages or shared memory; the embodiment of the present application is not limited to this, Fig. 9 What is shown is the architecture and logic of the processing module located inside the base station scheduler. When it is located outside the scheduler, it has the same module architecture and similar processing logic, which will not be repeated here.

[0119] According to an embodiment of the present application, an embodiment of an activation state alignment device between a network side and a terminal side in a DRX connection state is also provided. Fig.10 1 is a schematic diagram of a structure of an activation state alignment device for a network side and a terminal side in a DRX connection state according to an embodiment of the present application. Fig.10 As shown, the device comprises:

[0120] The first recording module 100 is used to record the first time point of sending downlink control information to the terminal device when an activation state triggering behavior is detected, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state and maintain the configuration time in the activation state in the discontinuous reception DRX connection state;

[0121] The second recording module 102 is used to determine a second time point at which the feedback information is received when feedback information is detected, wherein the feedback information is information returned by the terminal device in response to the downlink control information;

[0122] The activation state setting module 104 is used to set the network side to be in an activation state when the difference between the second time point and the first time point is not greater than the configured duration, and maintain the first duration in the activation state, so as to align the period when the network side and the terminal device are in the activation state in the DRX connection state, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference.

[0123] Optionally, the activation state triggering behavior includes at least one of the following: detecting a scheduling request sent by a terminal device on a physical uplink control channel; and sending the first downlink control information to the terminal device during data transmission.

[0124] Optionally, in the activation state triggering behavior, when a scheduling request sent by a terminal device is detected, when the activation state triggering behavior is detected, it also includes: keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration; in the activation state triggering behavior, when the first downlink control information is sent to the terminal device, when the activation state triggering behavior is detected, it also includes: obtaining the signal-to-noise ratio of the system, and when the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold, keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration.

[0125] Optionally, after acquiring the signal-to-noise ratio of the system, the method further includes: when the signal-to-noise ratio is not less than a preset signal-to-noise ratio threshold, entering an activation state when transmitting the first downlink control information to the terminal device.

[0126] Optionally, the inactivity timer is used to control whether the network side enters an activated state. When the network side needs to be in an inactive state, the inactivity timer is set to an inactive state; when the network side needs to be in an activated state, the inactivity timer is set to an activated state.

[0127] Optionally, the uplink scheduling process and the downlink scheduling process of data transmission correspond to a preset signal-to-noise ratio threshold respectively.

[0128] Optionally, in the activation state triggering behavior, when a scheduling request sent by a terminal device is detected, after the activation state triggering behavior is detected, it also includes: decoding the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information, and when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device has failed to normally receive the downlink control information sent by the network side in response to the scheduling request.

[0129] Optionally, when the activation state triggering behavior is to send the first downlink control information to the terminal device, after detecting the activation state triggering behavior, it also includes: decoding the data transmitted in the physical transmission shared channel corresponding to the downlink control information to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determining that the terminal device has not returned feedback information; when the decoding result is non-DTX, determining that the terminal device has returned feedback information, wherein DTX is used to characterize that the terminal device has failed to normally receive the downlink control information.

[0130] Optionally, the activation state setting module 104 is also used to: when no feedback information is detected, determine whether the number of times the downlink control information is sent to the terminal device exceeds a preset number threshold, wherein the preset number threshold is not greater than the maximum number of retransmissions in the hybrid automatic repeat request set in the system; when the number of times the downlink control information is sent does not exceed the preset number threshold, resend the downlink control information to the terminal device; when the number of times the downlink control information is sent exceeds the preset number threshold, stop resending the downlink control information to the terminal device, and set the network side to an inactive state.

[0131] Optionally, the uplink scheduling process and the downlink scheduling process of data transmission respectively correspond to a preset number threshold.

[0132] Optionally, the activation state setting module 104 is further used to: when the difference between the second time point and the first time point is greater than the configured duration, set the network side to be in an inactive state.

[0133] It should be noted that the various modules in the activation state alignment device on the network side and the terminal side in the above-mentioned DRX connection state can be program modules (for example, a set of program instructions to implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0134] It should be noted that the activation state alignment device on the network side and the terminal side in the DRX connection state provided in this embodiment can be used to perform Figure 2 The activation state alignment method between the network side and the terminal side in the DRX connection state is shown. Therefore, the relevant explanations and instructions on the activation state alignment method between the network side and the terminal side in the above-mentioned DRX connection state are also applicable to the embodiments of the present application and will not be repeated here.

[0135] According to an embodiment of the present application, an embodiment of a communication base station is also provided, the base station includes: a memory and a processor, the processor is used to run a program stored in the memory, wherein the program can be used to execute when it is running Figure 2The activation state alignment method of the network side and the terminal side in the DRX connection state shown is as follows: when the activation state triggering behavior is detected, the first time point of sending downlink control information to the terminal device is recorded, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state and maintain the configured duration in the activation state in the discontinuous reception DRX connection state; when the feedback information is detected, the second time point of receiving the feedback information is determined, wherein the feedback information is the information returned by the terminal device in response to the downlink control information; when the difference between the second time point and the first time point is not greater than the configured duration, the network side is set to be in the activation state, and the first duration is maintained in the activation state, so that the network side and the terminal device are aligned in the activation state in the DRX connection state. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference. Therefore, the relevant explanations and descriptions of the activation state alignment method of the network side and the terminal side in the above-mentioned DRX connection state are also applicable to the embodiments of the present application, and will not be repeated here.

[0136] According to an embodiment of the present application, an embodiment of an electronic device is also provided. Fig.11 The hardware structure block diagram of a computer terminal (or electronic device) for implementing a method for aligning the activation state of the network side and the terminal side in a DRX connection state is shown. Fig.11 As shown, the computer terminal 110 (or electronic device) may include one or more (1102a, 1102b, ..., 1102n are used to illustrate) processors 1102 (the processor 1102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 1104 for storing data, and a transmission device 1106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Fig.11 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig.11 More or fewer components as shown, or with Fig.11 Different configurations shown.

[0137] It should be noted that the one or more processors 1102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 110 (or electronic device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0138] The memory 1104 may be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the method for aligning the active state of the network side and the terminal side in the DRX connection state in the embodiment of the present application. The processor 1102 executes various functional applications and data processing by running the software programs and modules stored in the memory 1104, that is, the method for aligning the active state of the network side and the terminal side in the DRX connection state is implemented. The memory 1104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 1104 may further include a memory remotely arranged relative to the processor 1102, and these remote memories may be connected to the computer terminal 110 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0139] The transmission device 1106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 110. In one example, the transmission device 1106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 1106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0140] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 110 (or electronic device).

[0141] The embodiment of the present application also provides a non-volatile storage medium, the non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the following activation state alignment method between the network side and the terminal side in the DRX connection state by running the computer program: when an activation state triggering behavior is detected, recording a first time point of sending downlink control information to the terminal device, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state and maintain the configured duration in the activation state in the discontinuous reception DRX connection state; when feedback information is detected, determining a second time point when the feedback information is received, wherein the feedback information is information returned by the terminal device in response to the downlink control information; when the difference between the second time point and the first time point is not greater than the configured duration, setting the network side to be in the activation state, and maintaining the first duration in the activation state, so as to align the time period when the network side and the terminal device are in the activation state in the DRX connection state, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference.

[0142] The embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the activation state alignment method of the network side and the terminal side in the DRX connection state in each embodiment of the present application: when an activation state triggering behavior is detected, recording a first time point of sending downlink control information to the terminal device, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state and maintain the configured duration in the activation state in the discontinuous reception DRX connection state; when feedback information is detected, determining a second time point when the feedback information is received, wherein the feedback information is information returned by the terminal device in response to the downlink control information; when the difference between the second time point and the first time point is not greater than the configured duration, setting the network side to be in the activation state, and maintaining the first duration in the activation state, so as to align the time period when the network side and the terminal device are in the activation state in the DRX connection state, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activation state, and the first duration is obtained by taking the difference between the configured duration and the difference.

[0143] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0144] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0145] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0146] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0147] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0148] If the integrated unit 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, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0149] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for aligning activation states of a network side and a terminal side in a DRX connected state, characterized in that: include: In the case where an activation state triggering behavior is detected, recording the first time point of sending downlink control information to the terminal device, wherein the activation state triggering behavior is a behavior for triggering the network side to enter the activation state and maintain the configured duration in the activation state in the discontinuous reception DRX connection state; In the case where feedback information is detected, determining a second time point at which the feedback information is received, wherein the feedback information is information returned by the terminal device in response to the downlink control information; When the difference between the second time point and the first time point is not greater than the configured duration, the network side is set to be in an activated state and maintained in the activated state for a first duration so that the network side and the terminal device are aligned in the period of time when they are in the activated state in the DRX connection state, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the activated state, and the first duration is obtained by taking the difference between the configured duration and the difference.

2. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 1, characterized in that: The activation state triggering behavior includes at least one of the following: Detecting a scheduling request sent by the terminal device on a physical uplink control channel; During data transmission, the first downlink control information is sent to the terminal device.

3. The method for aligning the activation state of the network side and the terminal side in the DRX connected state according to claim 2, characterized in that: In the case where the activation state triggering behavior is detecting a scheduling request sent by the terminal device, in the case where the activation state triggering behavior is detected, the method further includes: keeping the network side in an inactive state until the difference between the second time point and the first time point is not greater than the configured duration; In the case where the activation state triggering behavior is to send the first downlink control information to the terminal device, when the activation state triggering behavior is detected, the method further includes: obtaining a signal-to-noise ratio of the system, and when the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold, keeping the network side in an inactive state until the difference between the second time point and the first time point is no greater than the configured duration.

4. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 3, characterized in that: After obtaining the signal-to-noise ratio of the system, the method further includes: When the signal-to-noise ratio is not less than the preset signal-to-noise ratio threshold, the activation state is entered when the first downlink control information is transmitted to the terminal device.

5. The method for aligning the activation state of the network side and the terminal side in the DRX connected state according to claim 3 or 4, characterized in that: The inactivity timer is used to control whether the network side enters an activated state. When the network side needs to be in an inactive state, the inactivity timer is set to an inactive state. When the network side needs to be in an activated state, the inactivity timer is set to an activated state.

6. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 3 or 4, characterized in that: The uplink scheduling process and the downlink scheduling process of data transmission respectively correspond to one of the preset signal-to-noise ratio thresholds.

7. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 3, characterized in that: In the case where the activation state triggering behavior is detecting a scheduling request sent by the terminal device, after detecting the activation state triggering behavior, the method further includes: Decode the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determine that the terminal device has not returned the feedback information; when the decoding result is non-DTX, determine that the terminal device has returned the feedback information, wherein the DTX is used to characterize that the terminal device fails to normally receive the downlink control information sent by the network side in response to the scheduling request.

8. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 3, characterized in that: In the case where the activation state triggering behavior is sending the first downlink control information to the terminal device, after the activation state triggering behavior is detected, the method further includes: Decode the data transmitted in the physical transmission shared channel corresponding to the downlink control information to obtain a decoding result, and when the decoding result is discontinuous transmission DTX, determine that the terminal device has not returned the feedback information; when the decoding result is non-DTX, determine that the terminal device has returned the feedback information, wherein the DTX is used to characterize that the terminal device has failed to normally receive the downlink control information.

9. The method for aligning the activation state of the network side and the terminal side in the DRX connected state according to claim 7 or 8, characterized in that: The method further comprises: In the case where the feedback information is not detected, determining whether the number of times the downlink control information is sent to the terminal device exceeds a preset number threshold, wherein the preset number threshold is not greater than a maximum number of retransmissions in a hybrid automatic repeat request set in the system; When the number of times the downlink control information is sent does not exceed the preset number threshold, resending the downlink control information to the terminal device; When the number of times the downlink control information is sent exceeds the preset number threshold, stop resending the downlink control information to the terminal device and set the network side to an inactive state.

10. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 9, characterized in that: The uplink scheduling process and the downlink scheduling process of data transmission respectively correspond to one of the preset times thresholds.

11. The method for aligning activation states of the network side and the terminal side in the DRX connected state according to claim 1, characterized in that: The method further comprises: When the difference between the second time point and the first time point is greater than the configured duration, the network side is set to be in an inactive state.

12. A communication base station, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein when the program is run, the activation state alignment method between the network side and the terminal side in the DRX connection state described in any one of claims 1 to 11 is executed.

13. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the activation state alignment method between the network side and the terminal side in the DRX connection state as described in any one of claims 1 to 11 by running the computer program.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method for aligning the activation states of the network side and the terminal side in the DRX connected state as described in any one of claims 1 to 11 are implemented.

Images