[0032] In order to make the technical problems, technical solutions and beneficial effects to be solved by the present invention clearer and clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.
[0033] figure 2 It is a schematic diagram of a structure in an evolved base station according to an embodiment of the present invention. Such as figure 2 As shown, the base station eNodeB may include: DRX module 1 and TA module 2, where the DRX module 1 is used to maintain the start and stop of DRX timers and the state transition of the UE, and at the same time maintain the UE’s non-scheduled data time counter and the UE in DRX inactive time counter; TA module 2, used to maintain the TATimer timer, obtain related configuration information and UE status information from the DRX module, determine whether to send TA commands, and execute TA command transmission.
[0034] image 3 It is a schematic structural diagram of a processing device for a terminal to maintain uplink synchronization in a DRX mode according to an embodiment of the present invention. Such as image 3 As shown, the device includes: a recording unit 10, configured to record a first time length during which the terminal does not perform data scheduling through a first counter in the base station; and a processing unit 30, configured to determine whether the first time length is greater than a first threshold When the first time length is greater than or equal to the first threshold value, the base station does not send the timing advance TA command; when the first time length is less than the first threshold value, the base station aligns the timing duration of the timer TATimer with the The period of discontinuous reception of DRX is compared with the result to determine the sending of the TA command.
[0035] The foregoing embodiments of the present invention are mainly implemented. The base station adjusts the TA command transmission timing for the UE configured with DRX and the time alignment timer timeAlignmentTimer according to the DRX cycle and the status of the UE under DRX, so that the UE can receive the TA command as much as possible. That is, when the UE is configured with DRX, the base station eNodeB can reasonably send TA commands to the UE, so that the UE can adjust the uplink timing, effectively reduce the occurrence of UE uplink out of synchronization, and optimize the utilization of system resources
[0036] The processing unit 30 in the foregoing embodiment of the present invention includes: a first processing module 301, configured to send a TA command within the last duration before the TATimer expires when the timing duration of TATimer is greater than the period of DRX; second processing The module 302 is used for when the timing duration of TATimer is equal to the period of DRX, the base station sends TA commands in each duration; the third processing module 303 is used for when the timing duration of TATimer is less than the period of DRX, the base station passes The second counter records the second length of time that the terminal is in the inactive state. In the case that the second length of time is greater than the second threshold, the base station sends the TA command.
[0037] Specifically, the technical solution of the foregoing embodiment includes the realization of two counters: a first counter and a second counter: the base station side maintains the first counter to indicate how long the UE has no data scheduling. If the counter is greater than a threshold (for example, timeAlignmentTimer 4 times), the base station side does not actively issue TA commands. At the same time, the second counter maintained by the base station side is a counter (SleepTimer) for the time the UE is in the DRX inactive state. The technical solution proposed by the present invention is that when the UE no-data scheduling time counter does not exceed the threshold value, according to the relationship between the TATimer duration and the DRX cycle duration, processing is divided into the following situations:
[0038] TATimer is longer than the DRX cycle. During the last OnDurationTimer operation before TATimer timeout, the base station sends TA commands.
[0039] When TATimer and DRX cycle are equal. During each OnDuration Timer running, the base station sends TA commands.
[0040] TATimer is shorter than the DRX cycle time. If the UE enters the active state from the DRX inactive state, and the TATimer does not time out at this time, and the SleepTimer exceeds a threshold (such as 1/2 of the timeAlignmentTimer duration), the TA command is sent. In other cases, the TATimer is maintained normally. At the time when the TATimer expires, if the UE is in the DRX active state, the base station issues a TA command, otherwise, the base station does not send the TA command.
[0041] The device effectively ensures that the UE can flexibly maintain uplink synchronization with the base station when configuring DRX. When the UE has a certain amount of traffic, it can receive the TA command from the base station to minimize the occurrence of uplink out-of-synchronization; when the UE has a small amount of traffic, the uplink synchronization state of the UE is not maintained, and system resource utilization is optimized.
[0042] Preferably, the first processing module 301 in the above-mentioned embodiment of the present invention may include: a first judging module for judging whether the timing duration of the TATimer is overtime, and if there is one DRX period from the timeout period of the timing duration of the TATimer, The TA command is sent within the duration of the non-timeout period, otherwise, the TA command is stopped.
[0043] Preferably, the third processing module 303 in the above-mentioned embodiment of the present invention may include: a second judgment module for the base station to judge the state of the terminal, wherein when the terminal enters the active state from the inactive state, the base station is in the second time length If it is greater than the second threshold value, the TA command is sent; when the terminal is always in the active state, if the timing duration of the TATimer expires, the base station sends the TA command.
[0044] In each of the foregoing embodiments of the present invention, the device may further include: a third judging module for judging whether the duration timer has reached the start time, wherein, when the start time is reached, the base station sends a TA command.
[0045] Figure 4 It is a flowchart of a processing method for a terminal to maintain uplink synchronization in DRX mode according to an embodiment of the present invention. Such as Figure 4 As shown, the method includes the following steps:
[0046] Step S402: Record the first length of time during which the terminal does not perform data scheduling through the first counter in the base station.
[0047] Step S404: Determine whether the first time length is greater than the first threshold value, where, when the first time length is greater than or equal to the first threshold value, the base station does not send the timing advance TA command; when the first time length is less than the first threshold value When the value is set, the base station determines to send the TA command according to the comparison result of the timing duration of the time alignment timer TATimer and the period of discontinuous reception of DRX.
[0048] The present invention mainly adjusts the TA command transmission timing for the UE configured with DRX and the time alignment timer timeAlignmentTimer according to the DRX cycle and the state of the UE under DRX, so that the UE can receive the TA command as much as possible.
[0049] This method effectively ensures that when DRX is configured, the UE can flexibly maintain uplink synchronization with the base station. When the UE has a certain amount of traffic, it can receive the TA command from the base station to minimize the occurrence of uplink out-of-synchronization; when the UE has a small amount of traffic, the uplink synchronization state of the UE is not maintained, and system resource utilization is optimized.
[0050] In step S404 of the above-mentioned embodiment of the present invention, the base station determines to send the TA command according to the comparison result of the timing duration of the time alignment timer TATimer and the period of discontinuous reception of DRX, including: when the timing duration of TATimer is greater than the period of DRX, the base station The TA command is sent in the last duration before TATimer timeout; when the timing duration of TATimer is equal to the period of DRX, the base station sends TA commands in each duration; when the timing of TATimer is less than the period of DRX, the base station passes The second counter records the second length of time that the terminal is in the inactive state. In the case that the second length of time is greater than the second threshold value, the base station sends the TA command.
[0051] specifically, Figure 5 It is a schematic diagram of the processing method according to the first preferred embodiment of the present invention. Such as Figure 5 As shown, it can be seen that the TATimer is longer than the DRX cycle. According to the current protocol, it is not clear whether the terminal monitors the PDCCH when the TA command is sent.
[0052] In this scenario, the present invention sends the TA command after the last onDuration in the TATimer period is started to ensure that the TA command arrives at the time when the terminal monitors the PDCCH.
[0053] specifically, Image 6 Is a schematic diagram of the processing method according to the second preferred embodiment of the present invention, such as Image 6 As shown, it can be seen that the TATimer and the DRX cycle are equal. According to the current protocol, at the time when the TA command is sent, it is not clear whether the terminal monitors the PDCCH behavior.
[0054] In this scenario, the present invention sends a TA command when each onDuration is started to ensure that the TA command arrives at the time when the terminal monitors the PDCCH. In particular, at time 1, the UE does not schedule data and the time counter exceeds the set threshold. This time no TA command is sent, and the terminal obtains uplink synchronization by reconnecting.
[0055] specifically, Figure 7 Is a schematic diagram of the processing method according to the third preferred embodiment of the present invention, such as Figure 7 As shown, it can be seen that the TATimer is shorter than the DRX cycle. According to the current protocol, it is not clear whether the terminal monitors the PDCCH when the TA command is sent.
[0056] In this scenario, the present invention combines the actual DRX state of the UE to conclude that at time 1, the TA is sent normally according to the TATimer timeout, and then the UE enters the DRX inactive state, and when it enters the active state again, it is judged that the UE is DRX inactive When the time counter exceeds the threshold, the TA is sent immediately, after which the UE has been in the DRX active state, and the TA is sent according to the TATimer period. There was a change from the inactive state to the active state between time 5 and 6, but because the UE was in the DRX inactive time counter did not exceed the threshold, after entering the active state, the TA was not sent immediately, or the TATimer timer was maintained normally. Always send TA. The situation at time 7 is the same at time 2 at the same time. When it enters the active state again, it is determined that the UE is in the DRX inactive time counter exceeding the threshold, and TA is sent immediately at this time. Time 8 should be sent according to the TATimer period, but it is in the DRX inactive state at this time and cannot be sent at this time. The UE is out of synchronization in the uplink and needs to re-access to obtain uplink synchronization.
[0057] In the steps of the above-mentioned embodiment of the present invention, when the timing duration of TATimer is greater than the period of DRX, the step of sending the TA command by the base station in the last duration before TATimer timeout includes: judging whether the timing duration of TATimer expires, and if it is less than TATimer If the timeout period of the timing duration is longer than the DRX cycle, the TA command is sent within the duration of the non-timeout period, otherwise, the TA command is stopped.
[0058] In the steps of the foregoing embodiment, when the timing duration of TATimer is less than the period of DRX, the base station uses the second counter to record the second length of time that the terminal is in an inactive state, and the second time length is greater than the second threshold. In the case of the base station, the step of sending the TA command may include: the base station judges the state of the terminal, where, when the terminal enters the active state from the inactive state, the base station sends the TA if the second time length is greater than the second threshold. Command; When the terminal is always in the active state, if the timing duration of TATimer expires, the base station sends a TA command.
[0059] Preferably, the step of sending the TA command within the duration in the above embodiment may include: judging whether the duration timer has reached the start time, wherein, when the start time is reached, the base station sends the TA command.
[0060] According to the above embodiment, in the implementation process, the base station scheduler knows the DRX configuration parameters of the terminal, can calculate the DRX-related timer operating status according to the DRX configuration and the terminal uplink and downlink scheduling conditions, and learn whether the terminal is in the DRX active time. The scheduler needs to maintain two counters for each UE configured with DRX, which are the time counter when the UE does not schedule data and the time when the UE is in DRX inactivity. The function of the UE not scheduling data time counter is: if the UE has no data scheduling for a considerable period of time (the timer exceeds the set threshold as the judgment basis), it can be considered that the amount of UE data is small, and the base station side does not need to maintain UE uplink synchronization (This can save system resources). When necessary, the UE can obtain synchronization by re-accessing. The role of the UE in the DRX inactivity time counter is: when the base station sends the TA command timer duration is less than the DRX cycle, it cannot guarantee that there will be a chance of onDurationTimer running within the TA command timer timeout period, that is, it cannot guarantee that the UE can be in DRX Activity time. In order to have a chance to send the TA command, the base station makes a judgment every time the UE enters the DRX active state. If the UE is in the DRX inactive time counter is greater than the set threshold, it is considered that the TA command timer is about to expire. The TA command needs to be issued at this time.
[0061] Figure 8 It is a detailed flowchart of a processing method for a terminal to maintain uplink synchronization in DRX mode according to an embodiment of the present invention. Attached Figure 8 The implementation of this method is described in further detail:
[0062] Step S201: Calculate the TATimer timer according to the configured timeAlignmentTimer, compare it with the configured DRX cycle length, and proceed to the corresponding step for execution according to different results. If the TATimer is longer than the DRX cycle, go to step S202, if the TATimer and the DRX cycle are equal, go to step S203, if the TATimer is shorter than the DRX cycle time, go to step 204 (including step S204a, step S204b, and step S204c).
[0063] Step S202: Judging the TATimer timeout time. If the time point is one DRX cycle length before the TATimer timeout, the TA command can be sent during the next onDuration operation, and step 203 is executed.
[0064] Step S203: It is judged whether the onDuration timer start time is reached, if it reaches, step S205 is executed, otherwise, the operation is ended.
[0065] Step S204: Determine the status of the UE. If the UE is in the active state and reach the TATimer timeout time, perform step S205; if the UE enters the active state from the inactive state, determine whether the DRX inactive time counter exceeds the set threshold, and if it exceeds, execute Step S205, otherwise the TATimer is maintained normally.
[0066] Step S205: It is judged whether the UE does not schedule data time counter exceeds the set threshold value, and if it does not exceed the set threshold, the TA command is sent.
[0067] It should be noted that the steps shown in the flowcharts of the embodiments of the present invention can be executed in a computer system such as a set of computer-executable instructions, and, although the logical sequence is shown in the flowcharts, in certain In some cases, the steps shown or described can be performed in a different order than here.
[0068] From the above description of the embodiments, it can be seen that the present invention achieves the following technical effects: when the UE is configured with DRX, the eNodeB can reasonably send TA commands to the UE, so that the UE can adjust the uplink timing and effectively reduce the number of UEs. The occurrence of upward out-of-step. .
[0069] Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general computing device, and they can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Above, alternatively, they can be implemented with program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, or they can be made into multiple integrated circuit modules, or they Multiple modules or steps are made into a single integrated circuit module to achieve. In this way, the present invention is not limited to any specific combination of hardware and software.
[0070] The above description shows and describes a preferred embodiment of the present invention, but as mentioned above, it should be understood that the present invention is not limited to the form disclosed herein, and should not be regarded as the exclusion of other embodiments, but can be applied to various embodiments. Such other combinations, modifications, and environments can be modified through the above teachings or technology or knowledge in related fields within the scope of the inventive concept described herein. The modifications and changes made by those skilled in the art do not depart from the spirit and scope of the present invention, and should fall within the protection scope of the appended claims of the present invention.
