WO2013189226A1

WO2013189226A1 - Tdd uplink and downlink configuration updating method and apparatus

Info

Publication number: WO2013189226A1
Application number: PCT/CN2013/076112
Authority: WO
Inventors: 姚君; 黄亚达
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-06-20
Filing date: 2013-05-22
Publication date: 2013-12-27
Also published as: CN103516498B; CN103516498A

Abstract

Disclosed are a TDD uplink and downlink configuration updating method and apparatus. The method comprised: a UE receiving TDD re-configuration information at each opportunity for sending TDD re-configuration information; if the UE receives updated TDD re-configuration information in a current TDD re-configuration period, the UE using a TDD uplink and downlink configuration indicated by the updated TDD re-configuration information from a next TDD re-configuration period; if the UE receives no updated TDD re-configuration information in the current TDD re-configuration period, the UE continuing to use the TDD uplink and downlink configuration used in the current TDD re-configuration period in the next TDD re-configuration period. Through the present invention, the TDD uplink and downlink configuration used by one cell can be flexibly adjusted.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a method and apparatus for updating a time division duplex (TDD) uplink and downlink configuration. BACKGROUND The current Long Term Evolution (LTE) technology and the Worldwide Interoperability for Microwave Access (UMB) Ultra Mobile Broadband system have two duplex modes: Frequency Division Duplex (FDD) and Time Division Duplex (TDD). In the FDD mode, the uplink and the downlink use different frequency bands for data transmission at the same time, while in the TDD mode, the uplink and downlink use the same frequency band for time-division data transmission. In a wireless system that performs data transmission in units of radio frames, the uplink and downlink of the wireless air interface transmission generally transmit data in units of radio frames, where each radio frame consists of several sub- Frame (Subframe) composition. For the LTE system, the subframes are all based on Orthogonal Frequency Division Multiplexing (OFDM) symbols, and each radio frame is composed of 10 subframes.

The resource allocation of the uplink/downlink subframes of the FDD system is relatively independent, that is, resource allocation can be performed separately for the downlink subframe and the uplink subframe. In the TDD system, several subframes in a radio frame may be allocated as an uplink subframe and a downlink subframe according to a certain ratio according to the needs of the service. In general, there are several types of uplink subframes and downlink subframes in the TDD system to meet the needs of different service types. According to the needs of business types in different regions, choosing the appropriate uplink-downlink ratio configuration is beneficial to improve the spectrum efficiency of the TDD system. For example, for an area with a large number of downloaded data services, you can select a configuration with more downlink subframes. For areas with more upload services, you can select a configuration with more uplink subframes. For areas with a relatively balanced download traffic, you can select The uplink and downlink subframes are configured in almost the same proportion. In the current LTE TDD (TD-LTE) system, seven methods are set for the uplink and downlink configuration of the TDD system. Each mode can be referred to as a TDD uplink and downlink configuration identifier, as shown in the first column of Table 1. In Table 1, a radio frame contains 10 subframes, and the subframe numbers are respectively labeled: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, where "D" indicates the subframe. It is a downlink subframe; "U" indicates that the subframe is an uplink subframe; "S" indicates that the subframe is a special subframe, that is, the subframe includes a downlink transmission portion, a guard interval, and an uplink transmission portion. For example, when the TDD uplink and downlink configuration standard It is recognized as 1, that is, the TDD uplink and downlink configuration 1: the 0th, 4th, 5th, and 9th subframes in a radio frame are downlink subframes; the 1st and 6th subframes are special subframes; 2, 3, 7, The subframe 8 is an uplink subframe. Table 1: List of existing uplink and downlink configurations in the TD-LTE system

As shown in Table 1, the downlink transmission accounts for 40% to 90% of the total transmission time. The above-mentioned uplink and downlink subframe ratio setting is mainly considering that the downlink data service in the multimedia service is usually more than the uplink data service. In the current LTE technology, the network side broadcasts the TDD uplink and downlink configuration of the local cell through a System Information Block (SIB) message. The transmission period of SIB1 is 80 ms, and in order to ensure correct reception of the cell edge users, the same transmission is repeated 3 times in one transmission period. In the prior art, in addition to the earthquake and typhoon warning system (Earthquake and Tsunami Warning

System, ETWS) and Commercial Mobile Alert Service (CMAS), the network side can only change system information in a specific radio frame. 1 is a schematic diagram of system information change in a conventional TD-LTE system. In the nth broadcast control channel (BCCH) change period, that is, the BCCH change period (n), if the shadow type is represented by a vertical stripe If the system information changes in the n+1th BCCH change period and becomes the system information indicated by the shadow type, the network side needs to notify the UE that certain system information will be under the BCCH change period (n). A change occurs in a BCCH change period, instructing the UE to be ready to receive updated system information at the beginning of the next BCCH change period. Therefore, when the network side needs to change the system information, it can only change at the boundary of the BCCH change period, and it is necessary to inform the UE by using the paging message in advance, and the system message is about to change in the next BCCH change period. However, during this period, the uplink and downlink configuration changes are not timely, which may result in the actual downlink service ratio not matching the currently used TDD uplink and downlink subframe ratio. For example, the current cell adopts TDD uplink and downlink configuration 4, and the ratio of uplink and downlink subframes is 1:4. If the uplink traffic in the cell increases in a certain period of time, the uplink service may be delayed due to insufficient uplink resources, and some downlink resources may be idle. , resulting in waste of downlink resources. SUMMARY OF THE INVENTION The present invention provides a method and an apparatus for updating an uplink and downlink configuration of a TDD to solve the above problems at least for the problem that the TDD uplink and downlink configuration used by one cell cannot be flexibly adjusted. According to an aspect of the present invention, a method for updating a time division duplex (TDD) uplink and downlink configuration is provided, including: user equipment UE receiving TDD reconfiguration information at each TDD reconfiguration information transmission opportunity; Receiving the updated TDD reconfiguration information in the current TDD reconfiguration period, the UE uses the TDD uplink and downlink configuration indicated by the updated TDD reconfiguration information from the next TDD reconfiguration period; if the UE is currently The UE does not receive the updated TDD reconfiguration information in the TDD reconfiguration period, and the UE continues to use the TDD uplink and downlink configuration used in the current TDD reconfiguration period in the next TDD reconfiguration period. Preferably, the TDD reconfiguration period is a minimum interval of a TDD uplink and downlink configuration change of the TDD system. Preferably, the TDD reconfiguration information is carried by one of the following messages: a system information block type 1 SIB1 message; a system information block SIB message defined for the TDD reconfiguration information. Preferably, when the TDD reconfiguration information is carried in the SIB1 message, the TDD reconfiguration information sending occasion is an opportunity to send the SIB1 message. Preferably, when the TDD reconfiguration information is carried in an SIB message defined for the TDD reconfiguration information, the TDD reconfiguration information transmission opportunity is an opportunity to send the defined SIB message. Preferably, the method further includes: receiving, by the UE, a paging message from a network side, where the paging message includes an indication of whether system information is changed; determining, according to the paging message, that the TDD reconfiguration Whether other system messages other than the information change, wherein the UE is currently in an idle state and/or a connected state. Preferably, the method further includes: when the system message value tag stored by the UE is different from the system message value tag in the received SIB1 message, the UE determines that the master information block MIB, SIB1, SIB10, The system information other than the SIB11, the SIB 12, and the SIB message carrying the TDD reconfiguration information is invalid. Preferably, the method further includes: the acquiring, by the UE, an indication parameter of the TDD reconfiguration period: the UE acquiring an indication parameter of the TDD reconfiguration period from the TDD reconfiguration information; Obtaining, by the UE, the indication parameter of the TDD reconfiguration period from the received paging message; the UE acquiring the indication parameter of the TDD reconfiguration period from the signaling of the downlink dedicated control channel DL-DCCH logical channel. Preferably, the TDD reconfiguration information includes one of the following: a TDD uplink and downlink configuration identifier; an uplink and downlink configuration of all subframes in a radio frame. Preferably, the TDD reconfiguration information further includes one of the following: a TDD reconfiguration period; a TDD reconfiguration period and an offset value. Preferably, before the UE receives the TDD reconfiguration information at each TDD reconfiguration information transmission opportunity, the method further includes: when the UE reports the UE capability to the network side, reporting the UE to support the TDD reconfiguration function. . Preferably, before the UE receives the TDD reconfiguration information at each TDD reconfiguration information transmission opportunity, the method further includes: the network side sending the ON message to the UE, and controlling the UE to enable the TDD reconfiguration Features. Preferably, the method further includes: the network side sending the information to the UE, and controlling the UE to close the TDD reconfiguration function. According to still another aspect of the present invention, an apparatus for updating a time-division duplex TDD uplink and downlink configuration is provided, which is located at a user equipment, and includes: a receiving module, configured to receive TDD reconfiguration information at each TDD reconfiguration information transmission opportunity; a determining module, configured to determine whether the TDD reconfiguration information received by the receiving module in the current TDD reconfiguration period is an update; and an execution module, configured to receive the TDD reconfiguration in the current TDD reconfiguration period by the receiving module When the information is updated, the TDD uplink and downlink configuration indicated by the updated TDD reconfiguration information is used from the next TDD reconfiguration period, and the TDD reconfiguration information is received by the receiving module in the current TDD reconfiguration period. When updating, the TDD uplink and downlink configuration used by the current TDD reconfiguration period is continued in the next TDD reconfiguration period. Preferably, the TDD reconfiguration period is a minimum interval of a TDD uplink and downlink configuration change of the TDD system. Preferably, the TDD reconfiguration information is carried by one of the following messages: a system information block type 1 SIB1 message; an SIB message defined for the TDD reconfiguration information. Preferably, the receiving module is further configured to receive a paging message from the network side, where the paging message includes an indication of whether the system information is changed; the determining module is further configured to determine, according to the paging message, Whether other system messages other than the TDD reconfiguration information are changed. Preferably, the device further includes: an obtaining module, configured to acquire an indication parameter of the TDD reconfiguration period by using one of: obtaining an indication of the TDD reconfiguration period from the TDD reconfiguration information Obtaining an indication parameter of the TDD reconfiguration period from the received paging message; acquiring an indication parameter of the TDD reconfiguration period from signaling of a downlink dedicated control channel DL-DCCH logical channel. Preferably, the device further includes: a reporting module, configured to report that the UE supports the TDD reconfiguration function when reporting the UE capability to the network side. Preferably, the device further includes: a control module, configured to enable or disable the TDD reconfiguration function of the UE according to the on or off information sent by the network side. With the present invention, the UE may receive TDD reconfiguration information at the TDD reconfiguration information transmission timing, and determine the upper and lower configuration used in the next TDD reconfiguration period according to whether the received reconfiguration information is updated, instead of being limited to the BCCH change period. The uplink and downlink configurations are changed at the boundary, so that the dynamic configuration of the TDD can be implemented, and the frequency of the TDD uplink and downlink configuration changes is improved, thereby avoiding the business delay and/or resource waste caused by the TDD uplink and downlink configuration and the current uplink and downlink traffic mismatch. problem. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic diagram of system information change in a conventional TD-LTE system; FIG. 2 is a flowchart of a method for updating an uplink and downlink configuration of a TDD according to Embodiment 1 of the present invention; FIG. 3 is a flowchart according to an embodiment of the present invention. FIG. 4 is a schematic structural diagram of an apparatus for updating an uplink and downlink configuration of a TDD according to a preferred embodiment of the present invention; FIG. 5 is another schematic diagram of an apparatus for updating an uplink and downlink configuration of a TDD according to a second embodiment of the present invention; FIG. 6 is a schematic structural diagram of an apparatus for updating an uplink and downlink configuration of a TDD according to still another preferred embodiment of the second embodiment of the present invention; FIG. 7 is a schematic diagram of an apparatus for updating an uplink and downlink configuration of a TDD according to another preferred embodiment of the second embodiment of the present invention; 3 is a flowchart of TDD uplink and downlink configuration update; FIG. 8 is a flowchart of TDD uplink and downlink configuration update according to Embodiment 4 of the present invention; FIG. 9 is a flowchart of TDD uplink and downlink configuration update according to Embodiment 5 of the present invention; and FIG. 10 is a flowchart of TDD uplink and downlink configuration update according to Embodiment 6 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Embodiment 1 FIG. 2 is a flowchart of a method for updating an uplink and downlink configuration of a TDD according to an embodiment of the present invention. As shown in FIG. 2, the method mainly includes the following steps S202 to S208. Step S202: The UE receives TDD reconfiguration information at each TDD reconfiguration information transmission opportunity. In a preferred embodiment of the present invention, the TDD reconfiguration information may be carried by a System Information Block Type 1 (SIB1) message, where the TDD reconfiguration information transmission timing is sent by the SIB1 message. opportunity. Alternatively, in another preferred embodiment of the embodiment of the present invention, the TDD reconfiguration information may also be carried by using a new System Information Block (SIB) message (ie, an SIB message defined for TDD reconfiguration information). At this time, the timing of TDD reconfiguration information transmission is the timing of sending a new SIB message. When the TDD reconfiguration information is carried by the new SIB message bearer or the SIB1 message, the new SIB message or the SIB1 message can be changed multiple times in one BCCH change period, that is, the new SIB message or the SIB1 message is in a BCCH change period. Can be sent and changed multiple times. In the embodiment of the present invention, the UE can detect whether the TDD reconfiguration information is changed by using the received TDD reconfiguration information, because the UE monitors and attempts to receive the SIB message carrying the TDD reconfiguration information at the time of each TDD reconfiguration information transmission. Therefore, in the embodiment of the present invention, the network side does not need to notify the UE by using a paging message: whether the TDD reconfiguration information is changed. Therefore, in a preferred embodiment of the embodiment of the present invention, the paging message may be used to notify the UE in the idle state and/or the connected state of the change of other system messages except the TDD reconfiguration information. In the preferred embodiment, when receiving the paging message, the UE determines whether the system message other than the TDD reconfiguration information is changed according to whether the system information included in the paging message changes. In the prior art, except for the Master Information Block (MIB), SIB1, SIB 10,

When the system information other than the SIB 11 and SIB12 messages are changed, the system information value tag (SystemlnfoValueTag) in the SIB1 message is also changed and accumulated. For example, in the TD-LTE system, there are 32 values. In order to ensure that some UEs that are out of cell coverage check whether the cell system information stored by the UE is valid after returning to the cell, the UE can compare whether the value stored by the UE is the same by reading the SystemInfoValueTag in the SIB1 message. If not, re-read the value. Take system information; if the same, and the stored system information does not exceed 3 hours, then the stored system message is still valid. Therefore, in three hours, the SystemInfoFValueTag in SIB1 cannot be duplicated, that is, the system information other than MIB, SIB1, SIB10, SIB11, and SIB 12 changes by up to 31 times within 3 hours. In the embodiment of the present invention, since the number of times of changing the TDD reconfiguration information is not limited, the change of the TDD reconfiguration information does not cause the system message tag to change. Therefore, when the TDD reconfiguration information is carried by the new SIB message, in a preferred embodiment of the present invention, when the system information value tag (SystemInfoValueTag) stored by the UE is different from the SIB1 message, the UE It is considered that system information other than MIB, SIB1, SIB10, SIB11, SIB 12 and SIB messages carrying TDD reconfiguration information is invalid. Step S204: Determine whether the UE receives the updated TDD reconfiguration information in the current reconfiguration period. If the UE receives the updated TDD reconfiguration information in the current reconfiguration period, go to step S206; if the UE is currently reconfigured When the updated TDD reconfiguration information is not received within the period, go to step S208. In the embodiment of the present invention, the TDD reconfiguration period is a minimum interval of the TDD uplink and downlink configuration change of the TDD system, and the minimum interval is generally smaller than the BCCH change period. In a preferred implementation manner of the embodiment of the present invention, the UE may obtain the indication parameter of the TDD reconfiguration period in one of the following manners:

(1) acquiring an indication parameter of the TDD reconfiguration period from the TDD reconfiguration information;

(2) acquiring an indication parameter of the TDD reconfiguration period from the received paging message; (3) obtaining an indication of the TDD reconfiguration period from signaling of a downlink dedicated control channel (DL-DCCH) logical channel parameter. In a preferred embodiment of the present invention, the TDD reconfiguration information includes: a TDD uplink/downlink configuration identifier, for example, seven uplink and downlink configuration identifiers in Table 1; or, all children in a radio frame. The uplink/downlink configuration of the frame is not limited to the seven uplink and downlink configurations in Table 1. The network side can define a new uplink and downlink configuration. Preferably, the TDD reconfiguration information may further include one of the following:

(1) The TDD reconfiguration period, where the boundary of the TDD reconfiguration period is the SFN value of the radio frame and the modulo operation of the TDD reconfiguration period is the starting position of the radio frame with a result of 0;

(2) TDD reconfiguration period and offset value, where the boundary of the TDD reconfiguration period is the start position of the radio frame of the radio frame and the start position of the radio frame with the offset value of the TDD reconfiguration period as the offset value, or The boundary of the TDD reconfiguration period is ten times the SFN value of the radio frame plus the start of the subframe corresponding to the subframe number of the radio frame in which the TDD reconfiguration period modulo operation result is an offset value. position. Step S206, the UE uses the subframe configuration (also referred to as TDD uplink and downlink configuration) indicated by the received updated TDD reconfiguration information from the next TDD reconfiguration period. Step S208, the UE continues to use the subframe configuration used by the current TDD reconfiguration period in the next TDD reconfiguration period. In a preferred embodiment of the present invention, the UE may report the UE supporting the TDD reconfiguration function when reporting the UE capability to the network side. In a preferred embodiment of the embodiment of the present invention, the network side may control the UE to enable or disable the TDD reconfiguration function by sending on/off information to the UE. With the foregoing method provided by the embodiment of the present invention, the UE may receive the TDD reconfiguration information at the TDD reconfiguration information sending occasion, and determine the upper and lower configuration used in the next TDD reconfiguration period according to whether the received reconfiguration information is updated. It is not limited to change the uplink and downlink configuration at the boundary of the BCCH change period, so that the dynamic configuration of the TDD can be realized, and the frequency of the TDD uplink and downlink configuration change is improved, thereby avoiding the service delay caused by the TDD uplink and downlink configuration and the current uplink and downlink traffic mismatch. And/or the problem of waste of resources, and, since the network side can indicate the uplink and downlink configuration of all subframes in one radio in the TDD reconfiguration information, a flexible uplink and downlink configuration can be adopted, and is not limited to the one shown in Table 1. 7 kinds of uplink and downlink configurations. Embodiment 2 This embodiment provides an apparatus for updating an uplink and downlink configuration of a TDD, where the apparatus is located in a user equipment, and may be used to implement the method in Embodiment 1. 3 is an apparatus for updating an uplink and downlink configuration of a TDD according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes: a receiving module 10 configured to receive TDD reconfiguration information at each TDD reconfiguration information transmission opportunity; The module 20 is coupled to the receiving module 10 and configured to determine whether the TDD reconfiguration information received by the receiving module 10 during the current TDD reconfiguration period is an update. The executing module 30 is coupled to the determining module 20 and configured to be in the receiving module 10 When the received TDD reconfiguration information is updated in the current TDD reconfiguration period, the TDD uplink and downlink configuration indicated by the updated TDD reconfiguration information is used from the next TDD reconfiguration period, and the receiving module 10 is heavy in the current TDD. When the received TDD reconfiguration information is not updated in the configuration period, the TDD uplink and downlink configuration used in the current TDD reconfiguration period is continued in the next TDD reconfiguration period. Preferably, in this embodiment, the TDD reconfiguration period is a minimum interval of the TDD uplink and downlink configuration change of the TDD system. In a preferred embodiment of the present invention, the TDD reconfiguration period is smaller than the BCCH change period. In a preferred embodiment of the present invention, the TDD reconfiguration information may be carried by a System Information Block Type 1 (SIB1) message, where the TDD reconfiguration information transmission timing is sent by the SIB1 message. opportunity. Or, in another preferred embodiment of the embodiment of the present invention, the TDD reconfiguration information is also carried by using a new System Information Block (SIB) message (ie, an SIB message defined for the TDD reconfiguration information). At this time, the timing of TDD reconfiguration information transmission is the timing of sending a new SIB message. When the TDD reconfiguration information is carried by the new SIB message bearer or the SIB1 message, the new SIB message or the SIB1 message can be changed multiple times in one BCCH change period, that is, the new SIB message or the SIB1 message is in a BCCH change period. Can be sent and changed multiple times. In the embodiment of the present invention, the UE can detect whether the TDD reconfiguration information is changed by using the received TDD reconfiguration information, because the UE monitors and attempts to receive the SIB message carrying the TDD reconfiguration information at the time of each TDD reconfiguration information transmission. Therefore, in the embodiment of the present invention, the network side does not need to notify the UE by using a paging message: whether the TDD reconfiguration information is changed. Therefore, in a preferred embodiment of the embodiment of the present invention, the receiving module 10 is further configured to receive a paging message from the network side, where the paging message includes an indication of whether the system information is changed; the determining module 20 further sets It is determined whether the system message other than the TDD reconfiguration information is changed according to the paging message. In the embodiment of the present invention, since the number of times of changing the TDD reconfiguration information is not limited, the change of the TDD reconfiguration information does not cause the system message value tag to change. Therefore, when the TDD reconfiguration information is carried by the new SIB message, in a preferred embodiment of the embodiment of the present invention, the receiving module 10 is further configured to receive the SIB1 message, and when the UE stores the system message value tag. (SystemlnfoValueTag) and When the difference in the SIB1 message is received, the judging module 10 is further arranged to determine that the system information other than the MIB, SIB1, SIB10, SIB 11, SIB 12 and the SIB message carrying the TDD reconfiguration information is invalid. In a preferred embodiment of the present invention, as shown in FIG. 4, the apparatus may further include: an obtaining module 40, configured to acquire an indication parameter of the TDD reconfiguration period by using one of the following manners: (1) Obtaining an indication parameter of the TDD reconfiguration period in the TDD reconfiguration information;

(2) obtaining an indication parameter of the TDD reconfiguration period from the received paging message;

(3) Acquire an indication parameter of the TDD reconfiguration period from signaling of a downlink dedicated control channel (DL-DCCH) logical channel. In a preferred embodiment of the present invention, as shown in FIG. 5, the apparatus may further include: a reporting module 50, configured to simultaneously report that the UE supports the TDD reconfiguration function when reporting the UE capability to the network side. In another preferred embodiment of the present invention, as shown in FIG. 6, the apparatus may further include: a control module 60, configured to enable or disable TDD reconfiguration of the UE according to the on or off information sent by the network side. Features. Therefore, the network side can control the UE to enable or disable the TDD reconfiguration function according to whether the UE needs to perform the TDD reconfiguration function. In the preferred embodiment of the present invention, the information carried in the TDD reconfiguration information may be as described in the first embodiment, and details are not described herein. Embodiment 3 FIG. 7 is a flowchart of the uplink and downlink configuration update of the TDD in the embodiment. As shown in FIG. 7 , in the embodiment, the UE performs the TDD uplink and downlink configuration update mainly includes the following steps S701 to S703. Step S701, an initialization process. In this embodiment, the TDD reconfiguration information is carried by using the SIB1 message, and the existing protocol specifies that when the SIB1 message in the nth BCCH change period is changed compared to the n-1th change period, the n-1th During the change period, the network side needs to notify the UE of the change of system information in the next BCCH change period by using a paging message. In this embodiment, when the SIB1 message is changed due to the TDD reconfiguration information, and the system information is changed in the nth BCCH change, the paging message is not used to notify the UE in the n-1th change period. That is, the paging message only informs the UE in the idle state and/or the connected state of the change of other system messages except the TDD reconfiguration information. In this embodiment, the parameter for calculating the TDD reconfiguration period may be a TDD reconfiguration period, or a TDD reconfiguration period and an offset value.

(1) TDD reconfiguration period At this time, the boundary of the TDD reconfiguration period is the SFN value of the radio frame and the start position of the radio frame with the result of the modulo operation of the TDD reconfiguration period being 0. For example, when the TDD reconfiguration period given by the network side is 200, if the SFN mod 200 of the radio frame is 0, the radio frame is the boundary of the TDD reconfiguration period, such as the 0th of those radio frames whose SFN is 0, 200, 400, 600, and the like. The beginning of the number sub-frame is the boundary of the TDD reconfiguration period.

(2) TDD reconfiguration period and offset value At this time, the boundary of the TDD reconfiguration period is the SFN value of the radio frame, the start position of the radio frame in which the modulo operation result of the TDD reconfiguration period is the offset value, or TDD at this time. The boundary of the reconfiguration period is the SFN value of the radio frame and the position where the subframe number satisfies the formula 1.

(SFN* 10+subframe number) mod period=offset value (Equation 1) For example, when the period is 200 and the offset value is 5, if the SFN mod 200 of the radio frame is 5, the radio frame is TDD. The boundary of the reconfiguration period, such as the start of the 0th subframe of those radio frames whose SFN is 5, 205, 405, 605, etc., is the boundary of the TDD reconfiguration period. For another example, when the period is 2000 and the offset value is 5, the subframe of the radio frame that satisfies (SFN*10 + subframe number) mod 2000 = 5 is the boundary of the reconfiguration period, such as those with SFN of 0, 200, 400, 600, etc. The beginning of the fifth subframe of the radio frame is the boundary of the TDD reconfiguration period. In this embodiment, the UE may obtain the parameter for calculating the TDD reconfiguration period (that is, the TDD reconfiguration period, or the TDD reconfiguration period and the offset value) in any one of the following three manners.

(1) The parameters of the TDD reconfiguration period are included in the TDD reconfiguration information, and the UE obtains the parameters of the TDD reconfiguration period from the TDD reconfiguration information. The TDD reconfiguration information is carried by the SIB1 message. The UE in the idle state or the connected state must read the SIB1 message, so that the UE can use the accurate TDD configuration immediately after entering the connected state from the idle state, without causing the UE to be The current TDD reconfiguration period information is unclear and the UE cannot correctly determine which subframe configuration is currently used.

(2) The parameter of the TDD reconfiguration period is included in the paging message, and the UE acquires the parameter of the TDD reconfiguration period from the paging message. In order to ensure that the UE can receive the parameter information of the TDD reconfiguration period carried by the paging message, the network side must have all paging occasions of all paging frames (PFs) (Paging Occasion, PO ) both send the information. This also ensures that the UE in the Discontinuous Reception (DRX) state does not miss the parameter information of receiving the TDD reconfiguration period due to temporary sleep.

(3) The parameters of the TDD reconfiguration period are included in the signaling of the DL-DCCH (downlink dedicated control channel) logical channel, and the UE acquires the parameters of the TDD reconfiguration period from the signaling of the DL-DCCH logical channel. The parameter information of the TDD reconfiguration period is included in the signaling of the DL-DCCH logical channel. The condition is that the UE is in the connected state, that is to say, the UE in the idle state cannot receive the information. The advantage of adopting this method is that the signaling overhead can be saved, and only the parameter information of the TDD reconfiguration period needs to be sent to a small number of users in need. The UE can also read the TDD reconfiguration information when it is in the idle state. After receiving the parameter information of the TDD reconfiguration period, it can use the TDD reconfiguration information that has been successfully received by itself, and after using the short processing delay, the correct subroutine can be used. Frame configuration. Step S702: The UE receives all SIB1 messages in a TDD reconfiguration period, and determines whether there is updated TDD reconfiguration information. It should be noted that the UE in this embodiment refers to the UE with the TDD reconfiguration function. The TDD reconfiguration information is carried by the SIB1 message, and the transmission timing of the SIB1 message is the transmission timing of the TDD reconfiguration information. When the UE reads the SIB1 message, it is required to determine whether the received SIB1 message contains TDD reconfiguration information. The transmission period of the SIB1 message is 80 ms. If the TDD reconfiguration period is greater than 80 ms, there may be more than two SIB1 messages transmitted in the same TDD reconfiguration period. If the network side saves signaling overhead, The TDD reconfiguration information is not carried in the SIB1. The UE can still receive the TDD reconfiguration information correctly. In some SIB1 messages, the TDD reconfiguration information can be selected. If the SIB1 message received by the UE includes TDD reconfiguration information, the UE also needs to determine whether the TDD reconfiguration information is updated in the current TDD reconfiguration period compared to the previous TDD reconfiguration period in combination with the parameter information of the TDD reconfiguration period. According to the transmission mode of the parameter of the TDD reconfiguration period in step S701, if the bearer is carried out by using the signaling of the DL-DCCH logical channel, the UE in the idle state may not be able to determine the TDD reconfiguration due to the lack of the parameter information of the TDD reconfiguration period. Whether the TDD reconfiguration information received in the cycle is updated compared to the previous TDD reconfiguration cycle. However, in this case, the UE on the network side can process the UE in the idle state according to the legacy UE, so that the UEs in the idle state can use the TDD configuration of the legacy UE, and the legacy UE uses the information element in the SIB1 ( Information Element, IE) The subframe configuration given in the TDD configuration (tdd-Config). Once these idle UEs enter the connected state and receive the parameter information of the TDD reconfiguration period, the root can be quickly It is determined according to the received TDD reconfiguration information, which subframe configuration is used by the current TDD reconfiguration, and whether the TDD reconfiguration information received in the TDD reconfiguration period is updated compared to the previous TDD reconfiguration period. In addition, the existing protocol stipulates that if the SIB1 message changes, the paging message needs to be used to notify the user in advance, but since the TDD reconfiguration period changes frequently, and the number of changes is large, in order not to affect the operation of the legacy UE, In this embodiment, the paging message only informs the user in the idle state and/or the connected state of the change of other system messages except the TDD reconfiguration information. Step S703: The UE uses the corresponding subframe configuration according to the determination result in the next TDD reconfiguration period. According to the determination in step S702, if the TDD reconfiguration information received in the TDD reconfiguration period is updated compared to the previous TDD reconfiguration period, the UE uses the received updated TDD reconfiguration from the next TDD reconfiguration period. The subframe configuration indicated by the information; the TDD reconfiguration information received in the TDD reconfiguration period is the same as the previous TDD reconfiguration period, and the UE continues to use the subframe in the TDD reconfiguration period from the next TDD reconfiguration period. Configuration. Embodiment 4 FIG. 8 is a flowchart of the uplink and downlink configuration update of the TDD in the embodiment. As shown in FIG. 8 , in the embodiment, the UE performs the TDD uplink and downlink configuration update mainly includes the following steps S801 to S803. Step S801, an initialization process. This step is the same as step S701 in the third embodiment, and details are not described herein again. Step S802: The UE receives all new SIB messages carrying TDD reconfiguration information in a TDD reconfiguration period, and determines whether there is an updated TDD reconfiguration message. In this embodiment, the TDD reconfiguration information is carried by the newly added SIB message, and the transmission timing of the newly added SIB message is the transmission timing of the TDD reconfiguration information. With the new SIB message, it is reasonable to select the transmission period to match the TDD reconfiguration period. The LTE protocol stipulates that other SIB messages except MIB and SIB1 are mapped to System Information (SI) messages, and the mapping relationship is given in the SIB1 message. In addition, the time-frequency domain resource of the new SIB message carrying the TDD reconfiguration information may be specified in the protocol, so that the mapping relationship is not required in the SIB1, so that the new SIB message does not match the original SIB message. Generate conflicts in the time domain. In addition, the existing protocol stipulates that when other SIB messages other than MIB, SIB1, SIB10, SIB11, and SIB12 are changed, the tag value systemlnfoValueTag in the corresponding SIB is changed accordingly. But when In this embodiment, for a new SIB message carrying a TDD reconfiguration information with a large number of changes and a fast change, the change is not reflected in the systemlnfoValueTag, that is, the systemlnfoValueTag value may be maintained when the new SIB message is changed. constant. When the system message value tag (SystemlnfoValueTag) stored by the UE is different from that in the SIB1 message, the UE considers other systems besides MIB, SIB1, SIB 10, SIB 11, SIB 12 and SIB messages carrying TDD reconfiguration information. The information is invalid. Step S803: The UE uses the corresponding subframe configuration according to the determination result in the next TDD reconfiguration period. This step is the same as step S703 in the third embodiment, and details are not described herein again. Embodiment 5 FIG. 9 is a flowchart of the TDD uplink and downlink configuration update in this embodiment. As shown in FIG. 9 , in the embodiment, the UE performs the TDD uplink and downlink configuration update mainly includes the following steps S901 to S904. Step S901: The UE reports that it has the capability of supporting dynamic TDD configuration. In this embodiment, when the UE can access the network, the non-access stratum (NAS) message is used to inform the network that it has the capability of supporting the TDD configuration, and/or when receiving the request from the network side to request the UE capability. When it is timed, report its ability to support TDD reconfiguration to the network side. Step S902: The network side sends a TDD reconfiguration function enable information to the UE to enable the TDD reconfiguration function of the UE. In this embodiment, the network side decides to enable the TDD reconfiguration function of the UE according to its own capability, and sends the TDD reconfiguration function enable information to the UE, which is used to enable the TDD reconfiguration function of the UE. Since some networks may not support the TDD reconfiguration function by itself, the UE may continuously monitor the channel in order to receive TDD reconfiguration information, which may result in a large energy consumption of the UE. Therefore, in this embodiment, the network side may control whether the UE turns on the TDD reconfiguration function. If the network side does not send the indication of turning on to the UE, the UE does not need to receive the TDD reconfiguration information. The network side may also select to disable the TDD reconfiguration function for the UE according to factors such as its own capacity, and only need to send a shutdown indication to the UE. The indication of the on/off may be carried by system information or RRC dedicated signaling. Step S903: The UE receives the TDD reconfiguration information. This step is described in detail in the third embodiment and the fourth embodiment. The steps here are the descriptions of the UE receiving the TDD reconfiguration information in all the foregoing embodiments, and details are not described herein again. Step S904: The UE uses a subframe configuration indicated in the TDD reconfiguration information. This step is the same as the step S703 in the third embodiment, and details are not described herein again. Embodiment 6 FIG. 10 is a flowchart of the TDD uplink and downlink configuration update in this embodiment. As shown in FIG. 10, in the embodiment, the UE performs the TDD uplink and downlink configuration update mainly includes the following steps S1001 to S1005. Step S1001: The UE reports the capability of supporting TDD reconfiguration. This step is the same as step S901 and will not be described again. Step S1002: The UE receives TDD reconfiguration information. This step is the same as step S903 and will not be described again. Step S1003: The UE uses a subframe configuration indicated in the TDD reconfiguration information. This step is the same as step S703 and will not be described again. Step S1004: The network side sends a TDD reconfiguration function off message to the UE to disable the TDD reconfiguration function of the UE. The network side decides to disable the TDD reconfiguration function of the UE according to its own capability, and sends a TDD reconfiguration function off message to the UE, which is used to disable the TDD reconfiguration function of the UE. One advantage of using TDD reconfiguration is to improve the throughput of the network. If the UE continuously receives the TDD reconfiguration information, it can ensure that the UE enters the connected state and communicates with the network side immediately when using the most suitable subframe configuration, which improves the network throughput. The amount has a big benefit. Therefore, after the UE accesses the network, it attempts to receive the TDD reconfiguration information, and the UE does not attempt to receive the TDD reconfiguration information until receiving the indication of the shutdown sent by the network side. If the network side needs to enable the TDD reconfiguration function of the UE according to its own capabilities, it only needs to send an open indication to the UE. The indication of the on/off may be carried by system information or RRC dedicated signaling. Step S1005: The UE no longer uses the subframe configuration in the TDD reconfiguration information, and no longer receives the TDD reconfiguration information. After receiving the shutdown indication sent by the network side, the UE will no longer use the subframe configuration in the received TDD reconfiguration information, and instead use the TDD uplink/downlink configuration indicated in SIB1, that is, with no TDD. Traditional UEs that configure features use the same TDD configuration. The UE also no longer receives TDD reconfiguration information. From the above description, it can be seen that, by using one or more embodiments, the UE may receive TDD reconfiguration information at a predetermined TDD reconfiguration information transmission opportunity, and determine whether the next TDD is based on whether the received reconfiguration information is updated. The upper and lower configurations used in the reconfiguration period, instead of limiting the uplink and downlink configurations at the boundary of the BCCH change period, can implement dynamic configuration of TDD, improve the frequency of TDD uplink and downlink configuration changes, and thus avoid TDD uplink and downlink configuration and current The problem that the uplink and downlink traffic does not match, causing service delay and/or resource waste, and the network side can indicate the uplink and downlink configuration of all the subframes in the radio in the TDD reconfiguration information, so that flexible uplink and downlink configurations can be adopted. Not limited to the seven uplink and downlink configurations shown in Table 1. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

1. An update method for time division duplex TDD uplink and downlink configuration, including:

The user equipment UE receives TDD reconfiguration information at each TDD reconfiguration information transmission opportunity; if the UE receives updated TDD reconfiguration information within the current TDD reconfiguration period, the UE is from the next TDD reconfiguration period Starting to use the TDD uplink and downlink configuration indicated by the updated TDD reconfiguration information;

If the UE does not receive the updated TDD reconfiguration information during the current TDD reconfiguration period, the UE continues to use the TDD uplink and downlink configuration used by the current TDD reconfiguration period in the next TDD reconfiguration period.

2. The method according to claim 1, wherein the TDD reconfiguration period is a minimum interval of a TDD uplink and downlink configuration change of the TDD system.

3. The method according to claim 1, wherein the TDD reconfiguration information is carried by one of the following messages:

System information block type 1 SIB1 message;

A system information block SIB message defined for the TDD reconfiguration information.

The method according to claim 3, wherein when the TDD reconfiguration information is carried in the SIB1 message, the TDD reconfiguration information transmission timing is an opportunity for the SIB1 message to be sent.

5. The method according to claim 3, wherein when the TDD reconfiguration information is carried in an SIB message defined for the TDD reconfiguration information, the TDD reconfiguration information transmission opportunity is the defined SIB message. The timing of the transmission.

The method according to any one of claims 1 to 5, wherein the method further comprises:

Receiving, by the UE, a paging message from a network side, where the paging message includes an indication of whether the system information is changed;

Determining, according to the paging message, whether other system messages except the TDD reconfiguration information are changed, wherein the UE is currently in an idle state and/or a connected state.

The method according to any one of claims 1 to 5, wherein the method further comprises: when the system message value tag stored by the UE and the system message value tag in the received SIB1 message are not Simultaneously, The UE determines that system information other than the primary information blocks MIB, SIB1, SIB10, SIB11, SIB 12 and the SIB message carrying the TDD reconfiguration information is invalid.

The method according to any one of claims 1 to 5, wherein the method further comprises: the UE acquiring an indication parameter of the TDD reconfiguration period by using one of the following manners:

Obtaining, by the UE, the indication parameter of the TDD reconfiguration period from the TDD reconfiguration information; the UE acquiring an indication parameter of the TDD reconfiguration period from the received paging message; The indication parameter of the TDD reconfiguration period is obtained in the signaling of the control channel DL-DCCH logical channel.

The method according to any one of claims 1 to 5, wherein the TDD reconfiguration information comprises one of the following: a TDD uplink and downlink configuration identifier; an uplink and downlink configuration of all subframes in a radio frame.

10. The method according to claim 9, wherein the TDD reconfiguration information further comprises one of the following:

TDD reconfiguration period;

TDD reconfiguration period and offset value.

The method according to any one of claims 1 to 5, wherein before the user equipment UE receives the TDD reconfiguration information at each TDD reconfiguration information transmission opportunity, the method further includes:

When the UE reports the UE capability to the network side, the UE supports the TDD reconfiguration function.

The method according to claim 11, wherein, before the user equipment UE receives the TDD reconfiguration information at each TDD reconfiguration information sending occasion, the method further includes:

The network side sends an open message to the UE, and controls the UE to enable the TDD reconfiguration function.

The method according to claim 11, wherein the method further comprises: sending, by the network side, the information to the UE, and controlling the UE to close the TDD reconfiguration function.

14. A time division duplexing update device for the TDD uplink and downlink configuration, located at the user equipment, comprising:

a receiving module, configured to receive TDD reconfiguration information at each TDD reconfiguration information transmission opportunity; a determining module, configured to determine whether the TDD reconfiguration information received by the receiving module in the current TDD reconfiguration period is an update; and an execution module, configured to receive the TDD in the receiving module during the current TDD reconfiguration period When the configuration information is updated, the TDD uplink and downlink configuration indicated by the updated TDD reconfiguration information is used from the next TDD reconfiguration period, and the TDD reconfiguration information is received by the receiving module in the current TDD reconfiguration period. When there is no update, the TDD uplink and downlink configuration used by the current TDD reconfiguration period is continued in the next TDD reconfiguration period.

15. The apparatus of claim 14, wherein the TDD reconfiguration period is a minimum interval of a TDD uplink and downlink configuration change of the TDD system.

16. The apparatus according to claim 14, wherein the TDD reconfiguration information is carried by one of the following messages:

System information block type 1 SIB1 message;

The SIB message defined for the TDD reconfiguration information.

The apparatus according to any one of claims 14 to 16, wherein

The receiving module is further configured to receive a paging message from the network side, where the paging message includes an indication of whether the system information is changed;

The determining module is further configured to determine, according to the paging message, whether other system messages other than the TDD reconfiguration information are changed.

The device according to any one of claims 14 to 16, wherein the device further comprises: an obtaining module, configured to obtain an indication parameter of the TDD reconfiguration period by one of:

Obtaining an indication parameter of the TDD reconfiguration period from the TDD reconfiguration information; acquiring an indication parameter of the TDD reconfiguration period from the received paging message; and a letter from a downlink dedicated control channel DL-DCCH logical channel The instruction parameter of the TDD reconfiguration period is obtained in the order.

The device according to any one of claims 14 to 16, wherein the device further comprises:

The reporting module is configured to report the UE to support the TDD reconfiguration function when reporting the UE capability to the network side. The device according to any one of claims 14 to 16, wherein the device further comprises: a control module configured to enable or disable the TDD reconfiguration function of the UE according to the on or off information sent by the network side .