Method for aligning active state of network side and terminal side in drx connected state and base station

Abstract

This application discloses a method and base station for aligning the active states of the network side and the terminal side in DRX connected mode. The method includes: upon detecting an active state triggering behavior, recording a first time point at which downlink control information is sent to the terminal device; upon detecting feedback information, determining a second time point at which the feedback information is received; and, if the difference between the second time point and the first time point is not greater than a configured duration, setting the network side to be in an active state and maintaining this active state for a first duration, thereby aligning the active state time periods of the network side and the terminal device in DRX connected mode. The first duration is consistent with the remaining duration required for the terminal device to maintain its active state, and is obtained by subtracting the configured duration from the difference. This application solves the technical problem of wasted scheduling resources and continuous terminal power consumption caused by the misalignment of the active state time periods of the network side and the terminal side.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and more specifically, to a method for aligning the active states of the network side and the terminal side in DRX connection state, and a base station. Background Technology

[0002] Discontinuous reception (DRX) allows user equipment (UE) to configure different parameter values ​​according to different services, thereby achieving optimal energy saving by matching parameters to service types. For example, when the UE is active, and the network is scheduling the UE, the UE can detect the corresponding downlink control information (DCI); when the network is not scheduling the UE, the UE is in a sleep state. This way, data transmission is not affected, and the UE sleeps during the gaps when there is no data transmission, saving the UE's power.

[0003] Therefore, when configuring DRX parameters, the alignment of parameters between the network and the UE is crucial. If the discontinuous reception parameters between the network and the terminal are misaligned (i.e., the time periods during which the network and the terminal device are in the active state under DRX connection are not aligned), situations may arise where the network considers the UE to be in an active state and sends scheduling information, but the UE is actually in a sleep state; or the network considers the UE to be in a sleep state and does not perform scheduling on the channel, but the UE is actually in an active state and is constantly listening for messages on the channel. This not only affects the quality of data transmission and wastes scheduling resources, but also consumes too much UE power.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a method and base station for aligning the active states of the network side and the terminal side in DRX connection mode, so as to at least solve the technical problem of wasted scheduling resources and continuous power consumption of the terminal caused by the misalignment of the active state time periods of the network side and the terminal side.

[0006] According to one aspect of the embodiments of this application, a method for aligning the active state of the network side and the terminal side in DRX connected state is provided, comprising: when an active state triggering behavior is detected, recording a first time point at which downlink control information is sent to the terminal device, wherein the active state triggering behavior is an behavior used to trigger the network side to enter the active state and maintain the active state for a configured duration in a discontinuous reception DRX connected state; when 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; and 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 active state and maintaining the active state for a first duration, so that the time periods of the network side and the terminal device in the active state in DRX connected state are aligned, wherein the first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state, and the first duration is obtained by subtracting the configured duration from the difference.

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

[0008] Optionally, when the active-state triggering behavior is detected by detecting a scheduling request sent by the terminal device, 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; when the active-state triggering behavior is detected by sending the first downlink control information to the terminal device, the method further includes: obtaining the system's signal-to-noise ratio, and 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 if the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold.

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

[0010] Optionally, the inactive timer is used to control whether the network side enters the active state. When the network side needs to be in an inactive state, the inactive timer is set to not start. When the network side needs to be in an active state, the inactive timer is set to start.

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

[0012] Optionally, in the case of detecting a scheduling request sent by the terminal device during the active state triggering behavior, after detecting the active state triggering behavior, the method further includes: decoding the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result, and determining that the terminal device has not returned feedback information if the decoding result is discontinuous transmission (DTX), and determining that the terminal device has returned feedback information if the decoding result is not DTX, wherein DTX is used to characterize that the terminal device failed to normally receive the downlink control information issued by the network side in response to the scheduling request.

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

[0014] Optionally, the method further includes: if no feedback information is detected, determining whether the number of times 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; if the number of times downlink control information is sent does not exceed the preset number threshold, retransmitting the downlink control information to the terminal device; if the number of times downlink control information is sent exceeds the preset number threshold, stopping the retransmission of 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 each correspond to a preset number of thresholds.

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

[0017] According to another aspect of the embodiments of this application, a communication base station is also provided, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes an active state alignment method between the network side and the terminal side under DRX connection state.

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

[0019] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of an active state alignment method between the network side and the terminal side in a DRX connection state.

[0020] In this embodiment, upon detecting an active state triggering behavior, a first time point is recorded where downlink control information is sent to the terminal device. The active state triggering behavior is an action used to trigger the network side to enter an active state and maintain it for a configured duration during discontinuous DRX connection. Upon detecting feedback information, a second time point is determined where the feedback information is received, where the feedback information is the information returned by the terminal device in response to the downlink control information. If 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 active state and maintains it for a first duration. This aligns the time periods when the network side and the terminal device are in the active state under DRX connection. The first duration is consistent with the remaining duration the terminal device needs to maintain in the active state, and is obtained by subtracting the configured duration from the difference. By adjusting the conditions for the network side to enter the active state, the DRX parameters of the network and the UE are aligned, reducing scheduling resource waste and continuous UE power consumption. This solves the technical problem of scheduling resource waste and continuous terminal power consumption caused by the misalignment of the active state time periods between the network side and the terminal side. Attached Figure Description

[0021] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

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

[0023] Figure 2 This is a schematic diagram of a method for aligning the active states of the network side and the terminal side in a DRX connection state according to an embodiment of this application;

[0024] Figure 3 This is a schematic diagram illustrating the drx-InactivityTimer startup process when a PUCCH SR is detected, according to an embodiment of this application.

[0025] Figure 4 This is a schematic diagram of a method flow according to an embodiment of this application, in which drx-InactivityTimer takes effect after detecting PUCCH SR;

[0026] Figure 5 This is a schematic diagram illustrating the activation process of drx-InactivityTimer in uplink scheduling according to an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of a method flow for drx-InactivityTimer to take effect in uplink scheduling according to an embodiment of this application;

[0028] Figure 7 This is a schematic diagram illustrating the activation process of drx-InactivityTimer in downlink scheduling according to an embodiment of this application;

[0029] Figure 8 This is a schematic diagram of a method flow for drx-InactivityTimer to take effect in downlink scheduling according to an embodiment of this application;

[0030] Figure 9 This is a schematic diagram of a DRX architecture for handling potential misalignment according to an embodiment of this application;

[0031] Figure 10 This is a schematic diagram of the active state alignment device between the network side and the terminal side in DRX connection state according to an embodiment of this application;

[0032] Figure 11 This is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a method for aligning the active states of the network side and the terminal side in DRX connection state, according to an embodiment of this application. Detailed Implementation

[0033] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort 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, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0035] To facilitate a better understanding of the embodiments of this application by those skilled in the art, the discontinuous reception DRX mechanism involved in the embodiments of this application is now explained:

[0036] The DRX configures a series of parameters for the UE to define its activation and sleep times. The UE only monitors the physical downlink control channel (PDCCH) during the activation time and not during the sleep time. To achieve this, the DRX configures a set of parameters to form a continuously repeating cycle, such as... Figure 1 As shown, within a DRX cycle, the time during which the UE can detect the PDCC CH channel is the active time, defined by the discontinuous reception active timer drx-onDurationTimer. When there is data transmission between the network and the UE, there is a high probability that data transmission will continue for a period of time. Therefore, a discontinuous reception inactivity timer drx-InactivityTimer is designed. Within this timer, the UE can detect the PDCCH channel, which is the active time. Whenever a new DCI is transmitted, drx-InactivityTimer is updated or restarted; that is, drx-InactivityTimer is only started or updated when a new PDCCH DCI is transmitted.

[0037] The aforementioned DRX parameters can be configured by the network side to the UE via Radio Resource Control (RRC). A specific combination of parameters is called a DRX profile. For example, configuring DRX-cycle to 320ms, drx-InactivityTimer to 80ms, and drx-onDurationTimer to 20ms constitutes a DRX profile. When either drx-onDurationTimer or drx-InactivityTimer is running, or when the UE's Physical Uplink Control Channel (PUCCH) SR is still pending, it is considered that the UE is in an active DRX state.

[0038] In related technologies, UE power saving has always been an important issue in wireless communication. The 3rd generation partnership project (3GPP) has also customized many functions to achieve UE power saving, among which DRX is a key one.

[0039] DRX allows the 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 happens to be in a sleep state. In this way, data transmission is not affected, and the UE sleeps during the gaps when there is no data transmission, saving the UE's power.

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

[0041] For example, if the network issues a DCI during the DRX activation time, but the UE is actually in sleep mode, it will lead to a waste of network scheduling resources. If the network does not transmit the scheduling DCI on the PDCCH during the DRX sleep time, but the UE is listening to the DCI information on the PDCCH channel during the DRX activation time, it will not only increase the latency of network scheduling data, but also waste the UE's power.

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

[0043] To address the aforementioned issues, this application provides relevant solutions, which are detailed below.

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

[0045] This application provides a method for aligning the active states of the network side and the terminal side in DRX connected state. Figure 2 This is a schematic diagram of a method for aligning the active states of the network side and the terminal side in a DRX connection state according to an embodiment of this application. Figure 2 As shown, the method includes the following steps:

[0046] Step S202: When an active state triggering behavior is detected, the first time point at which downlink control information is sent to the terminal device is recorded. The active state triggering behavior is the behavior used to trigger the network side to enter the active state and maintain the configuration duration in the active state under the discontinuous DRX connection state.

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

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

[0049] In the embodiments of this application, the above feedback information may include: affirmative acknowledgment (ACK) or negative acknowledgment (NACK).

[0050] Step S206: If 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 active state and maintained in the active state for a first duration, so that the time period when the network side and the terminal device are in the active state under DRX connection state are aligned. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state. The first duration is obtained by taking the difference between the configured duration and the difference.

[0051] By adjusting the conditions for activation, the DRX parameters of the network and UE are aligned, ensuring that the time periods when the network and terminal devices are in the active state under DRX connection are aligned. This reduces the waste of scheduling resources and the continuous power consumption of the UE, thereby solving the technical problem of wasted scheduling resources and continuous power consumption of the terminal caused by the misalignment of the active state time periods of the network and terminal.

[0052] The method for aligning the active states of the network side and the terminal side in the DRX connection state in steps S202 to S206 of the embodiments of this application will be further described below.

[0053] When an active-state triggering behavior is detected, in addition to recording the first time point at which downlink control information is sent to the terminal device, the embodiments of this application will also perform the following steps.

[0054] In some embodiments of this application, when the active-state triggering behavior is detected as a scheduling request sent by the terminal device, the method further 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 active-state triggering behavior is detected as sending the first downlink control information to the terminal device, the method further includes the following steps: obtaining the system's signal-to-noise ratio, and 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 if the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold.

[0055] Specifically, when the active state triggering behavior is the detection of a scheduling request sent by the 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). However, after sending the DCI, it will not enter the active state, but will only record the first time point of sending downlink control information to the terminal device and put the network side in the inactive state.

[0056] During the uplink 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 (SNR) is greater than the preset SNR threshold. If the current SNR (Signal to Interference plus Noise Ratio) is less than the preset SNR threshold, it is considered that the probability of the first DCI being correctly received by the terminal is small. In this case, the system will not enter the active state at the time of the first DCI being sent, but will only record the first time point of the transmission of the first downlink control information and keep the network side in the inactive state.

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

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

[0059] Specifically, if the current Sinr of the system is greater than or equal to the 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 active state 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 can each correspond to a preset signal-to-noise ratio (SNR) threshold. That is, the preset SNR thresholds corresponding to the uplink scheduling process and the downlink scheduling process can be the same or different. In the embodiments of this application, the preset SNR threshold corresponding to the uplink scheduling process is represented by ul_Sinr_Setting, and the preset SNR threshold corresponding to the downlink scheduling process is represented by drx_Dl_Sinr_Setting.

[0061] Furthermore, in this embodiment, the network side can be controlled to enter the active state by setting whether the inactive timer is started or not, as follows.

[0062] In some embodiments of this application, the inactive timer is used to control whether the network side enters the active state. When the network side needs to be in an inactive state, the inactive timer is set to a non-started state, and when the network side needs to be in an active state, the inactive timer is set to a started state.

[0063] The following section uses this control method as an example to further introduce the processing flow when the above-mentioned different active state trigger behaviors are detected.

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

[0065] In addition, after the network side initiates the DCI to schedule (send uplink grant) the UE corresponding to this SR, it will also decode the data transmitted in the physical uplink shared channel corresponding to the SR. The specific steps are as follows.

[0066] In some embodiments of this application, when the active state triggering behavior is detected as a scheduling request sent by the terminal device, after detecting the active state triggering behavior, the method further 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 determining that the terminal device has not returned feedback information if the decoding result is discontinuous transmission (DTX), and determining that the terminal device has returned feedback information if the decoding result is not DTX. Herein, DTX is used to characterize that the terminal device failed to normally receive the downlink control information issued 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 the decoding result. If the PUSCH decoding result is non-DTX (Discontinuous Transmission), i.e., ACK or NACK, it indicates that there is a response to the SR scheduling on the PUSCH channel, meaning that the UE has detected the Grant on the PDCCH. In this case, it is determined that the terminal device has returned feedback information, that is, the UE was in an active state when sending the Grant on the network side. Otherwise, it is determined that the terminal device has not returned feedback information.

[0068] 2) In the active state triggering behavior, when the first downlink control information is sent to the terminal device, that is, during the uplink 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 (SNR) is greater than the preset SNR threshold. If the current SNR of the system, Sinr, is less than the preset SNR threshold, then drx-InactivityTimer is not started at the time point of the first DCI transmission, and only the drx-InactivityTimer timestamp (i.e., the first time point of the transmission of the first downlink control information) is recorded. If the current SNR of the system, Sinr, is not less than the preset SNR threshold, then drx-InactivityTimer is started directly at the first time point of the first DCI transmission.

[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 be decoded. The specific steps are as follows.

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

[0071] 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 (i.e., ACK / NACK), it indicates that the UE has performed the initial DCI transmission detection. In this case, it is determined that the terminal device has returned feedback information, meaning that the UE was in an active state when sending the initial DCI transmission on the network side. If the decoding result is DTX, it is determined that no feedback information was detected.

[0073] In the processing flow corresponding to the various active state triggering behaviors mentioned above, if no feedback information is detected after decoding the data in the channel, the downlink control information can be resent to the terminal. The specific steps are as follows.

[0074] In some embodiments of this application, the method further includes the following steps: if no feedback information is detected, determining whether the number of times 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; if the number of times downlink control information is sent does not exceed the preset number threshold, retransmitting the downlink control information to the terminal device; if the number of times downlink control information is sent exceeds the preset number threshold, stopping the retransmission of 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 indicates that the UE has not detected DCI on the corresponding channel. In this case, it is determined that the network side has not detected feedback information. In this situation, 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 exceeds the preset number threshold, the retransmission of downlink control information to the terminal device is stopped and the inactive timer is deleted. If it does not exceed the system's configured preset number threshold, the current scheduling continues, downlink control information is retransmitted to the terminal device, and 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 of times threshold can be set in different ways in the processing flow corresponding to different active state trigger behaviors. For example, the preset number of times threshold can be equal to or different from the maximum number of retransmissions of the hybrid automatic repeat request (HARQ) set by the system, which will be described in detail below.

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

[0078] If the active triggering behavior 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, but no feedback information is detected, then in this embodiment, the preset number threshold can be set to be less than the maximum retransmission number mentioned above. Furthermore, in this case, the uplink scheduling process and the downlink scheduling process of data transmission each correspond to a preset number threshold; that is, the preset number thresholds corresponding to the uplink scheduling process and the downlink scheduling process can be the same or different. In this embodiment, 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 various active state trigger behaviors mentioned above, after decoding the data in the channel, if it is determined that feedback information has been detected, it is necessary to determine the second time point at which the feedback information is received, and based on the first time point recorded for sending downlink control information to the terminal device and the aforementioned second time point, determine whether drx_InactivityTimer has timed out, 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 (i.e., the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactive timer), the network side is set to be in an active state (including entering or maintaining an active state). Specifically, if the network side was previously in an inactive state, i.e., when the active state triggering behavior was detecting a scheduling request sent by the terminal device, or when the active state triggering behavior was sending the first downlink control information to the terminal device and the system signal-to-noise ratio was less than the preset signal-to-noise ratio threshold, and the inactive timer was kept from starting, then the aforementioned drx_InactivityTimer is started and takes effect at this time to make the network side enter the active state; if the network side was already in an active state, i.e., when the active state triggering behavior was sending the first downlink control information to the terminal device and the system signal-to-noise ratio was not less than the preset signal-to-noise ratio threshold, and the inactive timer was started directly, then the inactive timer's starting state remains unchanged at this time.

[0081] If the timeout has occurred (i.e., the difference between the second time point and the first time point is greater than the configured duration of the inactive timer), then the network side is set to an inactive state, i.e., the aforementioned drx_InactivityTimer is deleted.

[0082] This application provides corresponding control strategies for inactive timers for the three different active-state triggering behaviors mentioned above (including: 1. detecting a scheduling request sent by the terminal device on the 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). These strategies can dynamically identify and avoid misalignment on the network side and the UE side in DRX connected state, and can correct it in a timely manner.

[0083] The following section further describes the overall process for each of the three different activation state triggering behaviors and their corresponding communication scenarios.

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

[0085] In related technologies, false detections of SRs on PUCCH are possible; in this embodiment, a false SR is referred to as a false SR. If the network detects a false SR, it considers it an SR and that the UE is in an active DRX state. That is, the network assumes the UE is in an active DRX state upon detecting an SR. However, since it is a false SR, the UE is actually in a sleep state and does not detect DCIs on the PDCCH. If the network schedules and sends a DCI to this false SR and immediately starts the drx-InactivityTimer, the UE in a sleep state will not detect DCIs on the PDCCH, thus wasting scheduling resources. In other words, any scheduling of the UE by the network scheduler during the relevant drx_InactivityTimer period for other reasons will result in wasted scheduling resources because the UE is in a sleep state and does not detect PDCCHs. However, if the SR on the PUCCH is not a false SR but a normally transmitted PUCCH SR by the UE, then the UE is in an active DRX state. The network should normally schedule and send uplink grants on the PDCCH to schedule DCIs, and the UE should normally detect DCIs on the PDCCH channel.

[0086] To ensure alignment of discontinuous reception parameters between the network side and the terminal side when it is impossible to determine whether the SR is false, the embodiments of this application provide the following steps, specifically as follows: Figure 3As shown, when the network detects a PUCCH SR (i.e., a scheduling request on the physical uplink control channel), after scheduling and sending DCI to this SR, it does not immediately start drx-InactivityTimer. Instead, it only records the timestamp of drx-InactivityTimer's start (i.e., records the first time point when downlink control information is sent to the terminal device). The drx-InactivityTimer becomes effective when the data of the corresponding scheduled PUSCH is detected, i.e., the time point when the data is decoded into ACK or NACK (i.e., the second time point when ACK or NACK is received). If the corresponding drx-InactivityTimer has not yet timed out at this time, it becomes effective, meaning the remaining drx-InactivityTimer period is considered the UE activation time.

[0087] Furthermore, if the decoding result of the obtained physical uplink shared channel is neither ACK nor NACK, it can be determined whether to continue retransmission based on the maximum retransmission count (i.e., the preset retransmission threshold in this case is directly set to the maximum retransmission count). The specific process is as follows: Figure 4 As shown, when the network detects a PUCCH SR, regardless of whether it is a false SR, it schedules the UE that initiated the SR (sends an uplink grant), but does not start drx_InactivityTimer because the first transmission DCI was sent. Instead, it only records its timestamp (i.e. the first time point mentioned above). After the PUSCH of the corresponding scheduled SR is decoded, it is determined whether its decoding result is DTX.

[0088] If the PUSCH decoding result is not DTX, i.e., ACK or NACK, it indicates that there is a response to the SR scheduling on the PUSCH channel, which means that the UE has detected the Grant on the PDCCH. In other words, 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 (i.e., the difference between the second time point and the first time point is not greater than the configured duration corresponding to the inactive timer), then the drx_InactivityTimer is started. If it has timed out, then the drx_InactivityTimer is deleted. That is, if the difference between the second time point and the first time point is greater than the configured duration corresponding to the inactive timer, the inactive timer is deleted.

[0089] If the PUSCH decoding result is DTX, it indicates that the UE has not detected DC I on the corresponding PDCCH channel. The system checks if the maximum retransmission count for PUSCH HARQ has been reached. If it has (i.e., the number of downlink control information transmissions is greater than or equal to the maximum retransmission count), the drx_InactivityTimer is deleted. If the maximum HARQ retransmission count has not been reached (i.e., the number of downlink control information transmissions is less than the maximum retransmission count), the SR scheduling continues, downlink control information is retransmitted to the terminal device (UE), and the system checks if the PUSCH decoding result after the SR scheduling is DTX. In cases where the UE needs to check drx_InactivityTimer for other reasons during scheduling, it is still considered that the drx_InactivityTimer recording the timestamp has not taken effect.

[0090] Scenario 2: The drx-InactivityTimer effective method in uplink scheduling (i.e., the communication scenario where the active state triggering behavior is 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 for data transmission), the initial DCI (Data Access Code) of the data packet, which is the first grant of a data packet, is crucial. For data transmission, this corresponds to RV version 0; for DRX, it's also the point at which both the network and the UE simultaneously initiate the drx-InactivityTimer. If the initial DCI is not detected by the UE, the drx-InactivityTimer's activation time will not be aligned between the network and the UE, preventing the UE from correctly initiating the drx-InactivityTimer. Consequently, other scheduled DCIs (grants) for the UE due to other reasons will not be detected by the UE, resulting in a waste of network-side scheduling resources.

[0092] To address the aforementioned issues, the embodiments of this application provide the following solutions.

[0093] In this embodiment, 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 (preset count threshold), which is less than the maximum number of retransmissions allowed by HARQ. After the network sends the scheduling grant for the first DCI transmission on the PDCCH channel (i.e., after sending 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 empirically configured parameter drx_Ul_Sinr_Setting, that is, 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, if the current Sinr of the system is less than ul_Sinr_Setting, that is, if the signal-to-noise ratio is less than the preset signal-to-noise ratio threshold, it is considered that the probability of the first PDCCH transmission being correctly received is small. Therefore, drx-InactivityTimer is not started at the time of the first DCI transmission, but only the drx-InactivityTimer timestamp is recorded (that is, the first time point of the transmission of the first downlink control information is recorded). If PUSCH is detected within the maximum number of HARQ transmissions of PUSCH, that is, when the data on the PUSCH channel is decoded as ACK or NACK, if drx-InactivityTimer has not yet timed out at this time, then this drx-InactivityTimer is started.

[0095] If the current Sinr of the system is greater than or equal to drx_Ul_Sinr_Setting (i.e., the signal-to-noise ratio is not less than the preset Sinr_Noise ratio threshold), the first PDCCH transmission is considered to be correctly received, and drx-InactivityTimer is started at the time of the first DCI transmission. Simultaneously, if consecutive PUSCH detections result in DTX, and the number of consecutive detections exceeds drx_Ul_Count_Setting, this drx-InactivityTimer is canceled, and the activation time of the network and UE is aligned and reassigned 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, drx_InactivityTimer is immediately started on the network side. After drx_InactivityTimer has taken effect, the PUSCH channel corresponding to the Grant scheduling above is decoded, and it is determined 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 the active state when the Grant is sent on the network side, and then enters the normal DRX procedure.

[0097] If the decoding result is DTX, determine whether the number of consecutive DTX decoded by PUSCH is greater than the system configuration parameter drx_Ul_Count_Setting (in this embodiment, each transmission of downlink control information corresponds to one decoding result), that is, determine whether the number of times downlink control information is sent to the terminal device exceeds a preset threshold. If it exceeds this system configuration parameter, cancel and delete the aforementioned drx_InactivityTimer (there may be a situation where the UE does not detect DCI on the PDCCH). That is, if the number of times downlink control information is sent exceeds the preset threshold, stop retransmitting downlink control information to the terminal device and cancel and delete the inactive timer. If the number of consecutive DTX decoded by PUSCH is not greater than the system configuration parameter drx_Ul_Count_Setting, that is, if the number of times downlink control information is sent does not exceed the preset threshold, continue the scheduling of the above PUSCH, retransmit 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 (i.e., ACK / NACK), it indicates that the UE has detected the Grant on the PDCCH, meaning the UE was in an active state when sending the Grant on the network side. Determine the second time point at which ACK or NACK is received, and check if the drx_InactivityTimer has timed out. If it hasn't timed out (i.e., the difference between the second and first time points is not greater than the configured duration of the inactive timer), then start and activate the drx_InactivityTimer. If it has timed out, then delete the drx_InactivityTimer.

[0100] If the decoding result is DTX, determine whether the number of PUSCH scheduling attempts has reached the maximum HARQ retransmission count configured by the system (i.e., the preset threshold for this case is directly set to the maximum retransmission count). That is, determine whether the number of downlink control information sent to the terminal device exceeds the maximum retransmission count. If it has, delete the aforementioned drx_InactivityTimer, i.e., stop retransmitting downlink control information to the terminal device and delete the inactive timer. If the number of PUSCH scheduling attempts has not reached the maximum HARQ retransmission count configured by the system, continue the current PUSCH scheduling, retransmit downlink control information to the terminal device, and determine whether the PUSCH decoding result is DTX.

[0101] Scenario 3: The drx-InactivityTimer effective method in downlink scheduling (i.e., the communication scenario where the active state triggering behavior is 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 data transmission scheduling process), the first transmission DCI, which is the first assignment of a data packet, is crucial. For data transmission, this is RV version 0; for DRX, it is the point in time when both the network and the UE simultaneously start the drx-InactivityTimer. If the DCI is not detected by the UE, the drx-InactivityTimer activation time will not be aligned between the network and the UE, and the UE will not be able to correctly start the drx-InactivityTimer. Consequently, other DCIs (Assignments) scheduled for the UE for other reasons will not be detected by the UE, leading to a waste of network-side scheduling resources.

[0103] To address the aforementioned issues, the embodiments of this application provide the following solutions.

[0104] In this embodiment, 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 (preset count threshold), which is less than the maximum number of retransmissions allowed by HARQ. After the network sends the first DCI scheduling assignment on the PDCCH channel (i.e., after sending 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 empirically configured parameter drx_Dl_Sinr_Setting, that is, 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. Therefore, drx-InactivityTimer is not started at the time of the first transmission of DCI, but only the drx-InactivityTimer timestamp is recorded (i.e., the first time point of the transmission of the first downlink control information is recorded). If the decoding result of the Physical Downlink Shared Channel (PDSCH) is reported with ACK or NACK within the corresponding maximum number of HARQ transmissions, it means that both PDCCH and PDSCH can be correctly detected. If drx-InactivityTimer still has not timed out at this time, then this drx-InactivityTimer is started.

[0106] If the current Sinr of the system is greater than or equal to drx_Dl_Sinr_Setting (i.e., the signal-to-noise ratio is not less than the preset Sinr threshold), the first DPCCH transmission is considered to be correctly received, and drx-InactivityTimer is started at the time of the first DCI transmission. If there are consecutive PDSCH detections decoded as DTX, and the number of consecutive detections is greater than drx_Dl_Count_Setting, this drx-InactivityTimer is canceled, and the activation time of the network and UE is aligned and reassigned to the drx-onDurationTimer time of the DRX cycle.

[0107] The PDSCH decoding result is reported to the scheduler in PUCCH or PUSCH. If the corresponding DCI is not detected, the PUCCH or PUSCH will not report the corresponding PDSCH decoding result. The network side considers the PDSCH 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, then drx_InactivityTimer is immediately started on the network side. After 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 PDCCH, that is, the UE is in the 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, whether the number of times downlink control information is sent to the terminal device exceeds the preset threshold. If it is greater than this system configuration parameter, then cancel and delete the above-mentioned drx_InactivityTimer (there may be a situation where the UE does not detect DCI on PDCC H). That is, if the number of times downlink control information is sent exceeds the preset threshold, stop retransmitting downlink control information to the terminal device and cancel and delete the inactive timer. If the number of consecutive DTXs is not greater than the system configuration parameter drx_Dl_Count_Setting, that is, if the number of times downlink control information is sent does not exceed the preset threshold, then continue the above-mentioned PDSCH scheduling, retransmit 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), checks whether the feedback of the PDSCH channel scheduled by the corresponding Assignment is DTX, that is, determines whether the decoding result is DTX;

[0111] If the decoding result is not DTX (i.e., ACK / NACK), it indicates that the UE has detected the assignment on the PDCCH, meaning the UE was in an active state when sending the assignment on the network side. It is then determined whether the drx_Inactivity Timer has timed out. If it has not timed out (i.e., the difference between the second and first time points is not greater than the configured duration of the inactive timer), the drx_Inactivity Timer is started and activated. If it has timed out, the drx_Inactivity Timer is deleted.

[0112] If the decoding result is DTX, determine whether the number of PDSCH scheduling attempts has reached the maximum retransmission count configured for HARQ (i.e., the preset threshold is directly set to the maximum retransmission count in this case). That is, determine whether the number of downlink control information sent to the terminal device exceeds the maximum retransmission count. If it has, delete the aforementioned drx_InactivityTimer, i.e., stop retransmitting downlink control information to the terminal device and delete the inactive timer. If the number of PDSCH scheduling attempts has not reached the maximum retransmission count configured for HARQ, continue the current PDSCH scheduling, retransmit 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 preset signal-to-noise ratio thresholds (drx_Ul_Sinr_Setting / drx_Dl_Sinr_Setting) and preset count thresholds (drx_Ul_Sinr_Setting / drx_Dl_Count_setting) corresponding to the uplink and downlink scheduling processes of data transmission can be the same or different, and there is no restriction on this.

[0114] This application provides a solution to address potential misalignment issues between the network and the UE in DRX connected mode under three different communication scenarios. It can dynamically identify and avoid misalignment on the network and UE sides in DRX connected mode and correct it in a timely manner, achieving rapid recovery after misalignment scenarios, reducing the waste of scheduling resources and continuous UE power consumption, and the implementation method is simple.

[0115] The methods and embodiments provided in this application can be applied in New Radio (NR) wireless base stations, specifically through... Figure 9 The architecture shown is used to implement this, such as Figure 9As shown, the DRX profile container unit (configuration container unit) D1 is used to store DRX-related profile parameters, including drx-LongCycleStartOffset, drx-SlotOffset, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL. Among these, whether drx-InactivityTimer runs at the current scheduling time or in the scheduling slot needs to be identified in this unit, specifically determined by the DRX activation decision unit D3.

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

[0117] The DRX activation decision unit D3 is used to decide whether drx_InactivityTimer should run. By obtaining the relevant scheduler parameters from the DRX parameter setting unit D2 and the DRX-related configuration parameters from the DRX profile container unit D1, and considering the current scheduling scenario of the UE (SR pending, uplink scheduling, or downlink scheduling), it decides whether drx_InactivityTimer should run at the current time (slot); it checks whether misalignment exists, and if so, provides an appropriate execution strategy; and it decides whether drx_InactivityTimer should continue running or be canceled.

[0118] It should be noted that the above... Figure 9 The architecture shown can reside within the scheduler as a scheduler submodule to obtain the UE's scheduling information and uplink / downlink channel information from the scheduler; alternatively, it can run parallel to the scheduler logic, obtaining the UE's scheduling information and uplink / downlink channel information from the scheduler via messages or shared memory. This application does not limit this approach. Figure 9 The diagram shows the architecture and logic of the processing module located inside the base station scheduler. When the module is located outside the scheduler, it has the same module architecture and similar processing logic, which will not be described in detail here.

[0119] According to an embodiment of this application, an embodiment of an active state alignment device for the network side and the terminal side in DRX connection state is also provided. Figure 10 This is a schematic diagram of the active state alignment device between the network side and the terminal side in DRX connection state according to an embodiment of this application. Figure 10 As shown, the device includes:

[0120] The first recording module 100 is used to record the first time point when an active state triggering behavior is detected, and the active state triggering behavior is the behavior used to trigger the network side to enter the active state and maintain the configuration duration in the active state under the discontinuous reception DRX connection state.

[0121] The second recording module 102 is used to determine the second time point at which the feedback information is received when the feedback information is detected, wherein the feedback information is the 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 active state and maintain it in the active state for a first duration when the difference between the second time point and the first time point is not greater than the configured duration, so as to align the time period when the network side and the terminal device are in the active state under the DRX connection state. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state, and the first duration is obtained by taking the difference between the configured duration and the difference.

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

[0124] Optionally, when the active state triggering behavior is detected by detecting a scheduling request sent by the terminal device, 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; when the active state triggering behavior is detected by sending the first downlink control information to the terminal device, the method further includes: obtaining the system's signal-to-noise ratio, and 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 if the signal-to-noise ratio is less than a preset signal-to-noise ratio threshold.

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

[0126] Optionally, the inactive timer is used to control whether the network side enters the active state. When the network side needs to be in an inactive state, the inactive timer is set to not start. When the network side needs to be in an active state, the inactive timer is set to start.

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

[0128] Optionally, in the case of detecting a scheduling request sent by the terminal device during the active state triggering behavior, after detecting the active state triggering behavior, the method further includes: decoding the data transmitted in the physical uplink shared channel corresponding to the scheduling request to obtain a decoding result; and if the decoding result is discontinuous transmission (DTX), determining that the terminal device has not returned feedback information; and if the decoding result is not DTX, determining that the terminal device has returned feedback information. Here, DTX is used to characterize that the terminal device failed to normally receive the downlink control information issued by the network side in response to the scheduling request.

[0129] Optionally, in the case where the active state triggering behavior is to send the first downlink control information to the terminal device, after detecting the active state triggering behavior, the method further includes: decoding the data transmitted in the physical transmission shared channel corresponding to the downlink control information to obtain the decoding result; and if the decoding result is discontinuous transmission (DTX), determining that the terminal device has not returned feedback information; and if the decoding result is not DTX, determining that the terminal device has returned feedback information. Here, DTX is used to characterize that the terminal device failed to receive the downlink control information normally.

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

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

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

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

[0134] It should be noted that the active state alignment device between the network side and the terminal side in the DRX connection state provided in this embodiment can be used to execute Figure 2 The active state alignment method between the network side and the terminal side under the DRX connection state shown is therefore applicable to the embodiments of this application, and will not be repeated here.

[0135] According to an embodiment of this application, an embodiment of a communication base station is also provided. The base station includes a memory and a processor, the processor being used to run a program stored in the memory, wherein the program can be used to execute... Figure 2The method for aligning the active states of the network side and the terminal side under DRX connection state is as follows: When an active state triggering behavior is detected, a first time point is recorded where downlink control information is sent to the terminal device. The active state triggering behavior is an action used to trigger the network side to enter the active state and maintain it for a configured duration under discontinuous DRX connection state reception. When feedback information is detected, a second time point is determined where the feedback information is received. The feedback information is the information returned by the terminal device in response to the downlink control information. If 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 active state and maintains it for a first duration, so that the time periods when the network side and the terminal device are in the active state under DRX connection state are aligned. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state, and the first duration is obtained by subtracting the configured duration from the difference. Therefore, the explanations and descriptions of the above-described method for aligning the active states of the network side and the terminal side under DRX connection state also apply to the embodiments of this application, and will not be repeated here.

[0136] According to an embodiment of this application, an embodiment of an electronic device is also provided. Figure 11 A hardware block diagram of a computer terminal (or electronic device) for implementing an active state alignment method between the network side and the terminal side in DRX connected state is shown. Figure 11 As shown, the computer terminal 110 (or electronic device) may include one or more processors 1102 (shown as 1102a, 1102b, ..., 1102n in the figure) (processor 1102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), 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 a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 11 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 110 may also include... Figure 11 The more or fewer components shown, or having the same Figure 11 The different configurations shown.

[0137] It should be noted that the aforementioned one or more processors 1102 and / or other data processing circuitry are generally referred to herein as "data processing circuitry". This data processing circuitry may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be wholly or partially integrated into any other element within the computer terminal 110 (or electronic device). As involved in the embodiments of this application, the data processing circuitry serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0138] The memory 1104 can be used to store software programs and modules of application software, such as the program instruction / data storage device corresponding to the active state alignment method between the network side and the terminal side under the DRX connection state in this embodiment of the application. The processor 1102 executes various functional applications and data processing by running the software programs and modules stored in the memory 1104, thereby realizing the above-mentioned active state alignment method between the network side and the terminal side under the DRX connection state. The memory 1104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1104 may further include memory remotely located relative to the processor 1102, and these remote memories can be connected to the computer terminal 110 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

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

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

[0141] This application embodiment also provides a non-volatile storage medium, which includes a stored computer program. The device containing the non-volatile storage medium executes the following method for aligning the active state of the network side and the terminal side under DRX connection state by running the computer program: Upon detecting an active state triggering behavior, a first time point is recorded where downlink control information is sent to the terminal device. The active state triggering behavior is an action used to trigger the network side to enter an active state and maintain it for a configured duration under discontinuous DRX connection state reception. Upon detecting feedback information, a second time point is determined where the feedback information is received. The feedback information is the information returned by the terminal device in response to the downlink control information. If 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 active state and maintains it for a first duration, so that the time periods when the network side and the terminal device are in the active state under DRX connection state are aligned. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state, and the first duration is obtained by subtracting the configured duration from the difference.

[0142] This application also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the steps of the network side and terminal side activation state alignment method under DRX connection state in various embodiments of this application: when an activation state triggering behavior is detected, a first time point is recorded for sending downlink control information to the terminal device, wherein the activation state triggering behavior is an behavior used to trigger the network side to enter the activation state and maintain the activation state for a configured duration under discontinuous reception DRX connection state; when feedback information is detected, a second time point for receiving 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 maintains the activation state for a first duration, so that the time period of the network side and the terminal device in the activation state under DRX connection state is aligned, 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 subtracting the configured duration from the difference.

[0143] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0144] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions 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. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

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

[0147] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0148] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0149] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for aligning the active states of the network side and the terminal side in DRX connection state, characterized in that, include: Upon detecting an activation state triggering behavior, the first time point at which downlink control information is sent to the terminal device is recorded. The activation state triggering behavior is an action used to trigger the network side to enter the activation state and maintain the configuration duration in the activation state during a discontinuous DRX connection state. If feedback information is detected, a second time point at which the feedback information is received is determined, wherein the feedback information is the information returned by the terminal device in response to the downlink control information; If 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 active state and maintained in the active state for a first duration, so that the network side and the terminal device are in the active state during the DRX connection state. The first duration is consistent with the remaining duration that the terminal device needs to maintain in the active state, and the first duration is obtained by taking the difference between the configured duration and the difference.

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

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

4. The method for aligning the active states of the network side and the terminal side in DRX connection 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 device enters the active state when transmitting the first downlink control information to the terminal device.

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

6. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 3 or 4, characterized in that, The uplink and downlink scheduling processes for data transmission each correspond to a preset signal-to-noise ratio threshold.

7. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 3, characterized in that, In the case where the active state triggering behavior is detected as a scheduling request sent by the terminal device, after detecting the active state triggering behavior, the method further includes: The data transmitted in the physical uplink shared channel corresponding to the scheduling request is decoded to obtain a decoding result. If the decoding result is a discontinuous transmission (DTX), it is determined that the terminal device has not returned the feedback information. If the decoding result is not a DTX, it is determined that the terminal device has returned the feedback information. The DTX is used to indicate that the terminal device failed to receive the downlink control information issued by the network side in response to the scheduling request.

8. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 3, characterized in that, In the case where the active-state triggering behavior is to send the first downlink control information to the terminal device, after detecting the active-state triggering behavior, the method further includes: The data transmitted in the physical transmission shared channel corresponding to the downlink control information is decoded to obtain a decoding result. If the decoding result is discontinuous transmission (DTX), it is determined that the terminal device has not returned the feedback information. If the decoding result is not DTX, it is determined that the terminal device has returned the feedback information. Herein, DTX is used to indicate that the terminal device failed to receive the downlink control information normally.

9. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 7 or 8, characterized in that, The method further includes: If the feedback information is not 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 retransmission request set in the system; If the number of times the downlink control information is sent does not exceed the preset number threshold, the downlink control information is resent to the terminal device; If the number of times the downlink control information is sent exceeds the preset threshold, the retransmission of the downlink control information to the terminal device is stopped, and the network side is set to an inactive state.

10. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 9, characterized in that, The uplink and downlink scheduling processes for data transmission each correspond to a preset number of thresholds.

11. The method for aligning the active states of the network side and the terminal side in DRX connection state according to claim 1, characterized in that, The method further includes: If 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 inactive.

12. A communication base station, characterized in that, include: A memory and a processor, the processor being configured to run a program stored in the memory, wherein the program, when running, executes the active state alignment method between the network side and the terminal side in DRX connection state as described in any one of claims 1 to 11.

13. A non-volatile storage medium, characterized in that, The non-volatile storage medium includes a stored computer program, wherein the device containing the non-volatile storage medium executes the active state alignment method between the network side and the terminal side in 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 the processor, it implements the steps of the active 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.

Images