Time window design method, device and system, joint channel estimation method

Abstract

The present disclosure relates to a time window design method, device and system, and a joint channel estimation method. The time window design method comprises: in the case that a first type of event and a second type of event exist in a nominal time window, determining an actual time window in each nominal time window according to terminal capability. The present disclosure proposes a design method of the actual time window for the case that both dynamic events and semi-static events exist in the nominal time window, thereby improving the joint channel estimation performance of PUSCH / PUCCH.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication, and in particular to a time window design method, device and system, and a joint channel estimation method. Background Technology

[0002] 3GPP Rel-17 introduced a joint channel estimation scheme for PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel). To enable PUSCH / PUCCH joint channel estimation, Rel-17 defines a two-level time window structure, including a nominal time domain window (TDW) and an actual time domain window (TDW). Each nominal TDW consists of one or more consecutive time slots, and each nominal TDW contains one or more actual TDWs, each of which also consists of one or more consecutive time slots. Finally, joint channel estimation is performed within each actual TDW. Summary of the Invention

[0003] The inventors discovered through research that if both Type I and Type II events exist within a nominal TDW, there will be certain problems with the design of the time window and the joint channel estimation.

[0004] In view of at least one of the above technical problems, this disclosure provides a time window design method, device and system, and joint channel estimation method, which can propose an actual time window design method for situations where both type I events and type II events exist within the nominal time window.

[0005] According to one aspect of this disclosure, a time window design method is provided, comprising:

[0006] If there are Type I and Type II events within the nominal time window, the actual time window within each nominal time window is determined based on the terminal's capabilities.

[0007] In some embodiments of this disclosure, the first type of event is a first event triggered by downlink control information or an event triggered by the media access control-control unit, and the second type of event is a second event triggered by downlink control information or an event not triggered by downlink control information or the media access control-control unit.

[0008] In some embodiments of this disclosure, the first type of event is a dynamic event, and the second type of event is a semi-static event.

[0009] In some embodiments of this disclosure, the first type of event and the second type of event are mutually exclusive.

[0010] In some embodiments of this disclosure, the first event and the second event are mutually exclusive.

[0011] In some embodiments of this disclosure, the first event is a non-frequency hopping transmission event, and the second event is a frequency hopping transmission event.

[0012] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on terminal capabilities includes:

[0013] Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event has ended.

[0014] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes:

[0015] If both a first-type event and a second-type event occur within a nominal time window, and their occurrence times overlap, and the first-type event either overrides the second-type event, or the second-type event is discarded and only the first-type event is processed, or the second-type event is ignored and only the first-type event is processed, then...

[0016] When the terminal device supports the first terminal capability, an actual time window is generated after the first type of event ends. The actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0017] If the terminal device does not support the first terminal capability, no actual time window will be generated after the first type of event ends, until the nominal time window ends or the next first type of event or second type of event occurs.

[0018] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes:

[0019] If a first type of event and a second type of event occur within a nominal time window, and the occurrence times of the first type of event and the second type of event overlap, and the second type of event overrides the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event, then an actual time window is generated after the second type of event ends. The actual time window continues until the nominal time window ends or before the next first type of event or second type of event occurs.

[0020] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes:

[0021] If a third type of event occurs first, followed by a second type of event, within a nominal time window, and the third type of event and the second type of event do not overlap in their occurrence time,

[0022] When the terminal device supports the first terminal capability, an actual time window is generated after the third type of event ends. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs. The third type of event is a first type of event or a first overlapping event. The first overlapping event is a first type of event and a second type of event that overlap in time. The first type of event overrides the second type of event, or abandons the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event.

[0023] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability further includes:

[0024] If the terminal device does not support the capabilities of the first terminal, no actual time window will be generated from the end of the third type of event until the end of the nominal time window.

[0025] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability further includes:

[0026] If the terminal device does not support the first terminal capability, an actual time window is generated after the second type of event ends. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0027] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes:

[0028] If, within a nominal time window, a fourth type of event occurs first, followed by a first type of event, and the second type of event does not overlap with the first type of event in terms of occurrence time,

[0029] When the terminal device supports the first terminal capability, an actual time window is generated after the fourth type of event ends. This actual time window continues until the first type of event occurs. After the first type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs. The fourth type of event is a second type of event or a second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, and the second type of event overwrites the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed.

[0030] If the terminal device does not support the first terminal capability, after the fourth type of event ends, an actual time window is generated. This actual time window continues until the first type of event occurs. After the first type of event ends, no more actual time windows are generated until the nominal time window ends or the next first or second type of event occurs.

[0031] In some embodiments of this disclosure, determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: if a fourth type of event occurs first within a nominal time window, followed by a second type of event, and the fourth type of event and the second type of event do not overlap in occurrence time, after the fourth type of event ends, an actual time window is generated, which continues until the second type of event occurs; after the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. The fourth type of event is either a second type of event or a second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, where the second type of event overrides the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed.

[0032] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0033] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following cases: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is disabled after the first type of event ends; or, the terminal device does not support the first terminal capability.

[0034] According to another aspect of this disclosure, a joint channel estimation method is provided, comprising:

[0035] The terminal device uses the time window design method as described in any of the above embodiments to determine the actual time window within each nominal time window;

[0036] When terminal devices perform uplink transmission within the actual time window, they maintain power consistency and phase continuity so that network devices can perform joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

[0037] According to another aspect of this disclosure, a joint channel estimation method is provided, comprising:

[0038] The network device determines the time-frequency transmission resources for repeated transmission of the physical uplink shared channel and the physical uplink control channel, and configures a nominal time window for the terminal device so that the terminal device can use the time window design method as described in any of the above embodiments to determine the actual time window within each nominal time window.

[0039] The network device uses the time window design method as described in any of the above embodiments to determine the actual time window within each nominal time window;

[0040] When the terminal device performs uplink transmission within the actual time window, the network device performs joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

[0041] According to another aspect of this disclosure, a terminal device is provided, comprising:

[0042] The time window determination module is used to determine the actual time window within each nominal time window based on the terminal's capabilities, in the case of first-type and second-type events occurring within the nominal time window.

[0043] In some embodiments of this disclosure, the terminal device is used to perform operations implementing the time window design method as described in any of the above embodiments, and / or the joint channel estimation method as described in any of the above embodiments.

[0044] According to another aspect of this disclosure, a terminal device is provided, comprising:

[0045] Terminal device memory, used to store instructions;

[0046] A terminal device processor is configured to execute the instructions, causing the terminal device to perform operations implementing the time window design method as described in any of the above embodiments and / or the joint channel estimation method as described in any of the above embodiments.

[0047] According to another aspect of this disclosure, a network device is provided, comprising:

[0048] The time window design unit is used to determine the actual time window within each nominal time window based on the terminal's capabilities, assuming that there are first-type and second-type events within the nominal time window.

[0049] In some embodiments of this disclosure, the network device is configured to perform operations implementing the time window design method as described in any of the above embodiments, and / or the joint channel estimation method as described in any of the above embodiments.

[0050] According to another aspect of this disclosure, a network device is provided, comprising:

[0051] Network device memory, used to store instructions;

[0052] A network device processor is configured to execute the instructions, causing the network device to perform operations implementing the time window design method as described in any of the above embodiments and / or the joint channel estimation method as described in any of the above embodiments.

[0053] According to another aspect of this disclosure, a time window design system is provided, including a terminal device as described in any of the above embodiments and a network device as described in any of the above embodiments.

[0054] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium stores computer instructions that, when executed by a processor, implement the time window design method as described in any of the above embodiments, and / or the joint channel estimation method as described in any of the above embodiments.

[0055] This disclosure proposes an actual time window design method for cases where both Type I and Type II events exist within the nominal time window, thereby improving the joint channel estimation performance of PUSCH / PUCCH. Attached Figure Description

[0056] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0057] Figure 1 This is a schematic diagram of some embodiments of the joint channel estimation method disclosed herein.

[0058] Figure 2 Schematic diagrams of some embodiments of the time window design method of this disclosure.

[0059] Figure 3 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0060] Figure 4 This is a schematic diagram illustrating the determination of the actual time window in other embodiments of this disclosure.

[0061] Figure 5 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0062] Figure 6 This is a schematic diagram illustrating the determination of the actual time window in other embodiments of this disclosure.

[0063] Figure 7 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0064] Figure 8 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0065] Figure 9 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0066] Figure 10 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0067] Figure 11 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0068] Figure 12 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0069] Figure 13 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure.

[0070] Figure 14The diagram illustrates some other embodiments of the joint channel estimation method disclosed herein.

[0071] Figure 15 This is a schematic diagram of some embodiments of the joint channel estimation method disclosed herein.

[0072] Figure 16 This is a schematic diagram of some embodiments of the terminal device disclosed herein.

[0073] Figure 17 This is a schematic diagram of the structure of some embodiments of the terminal device disclosed herein.

[0074] Figure 18 This is a schematic diagram of some embodiments of the network device disclosed herein.

[0075] Figure 19 This is a schematic diagram of the structure of some embodiments of the network device disclosed herein. Detailed Implementation

[0076] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0077] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0078] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0079] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0080] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0081] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0082] The inventors discovered through research that the generation of an actual TDW is related to events that disrupt power or phase consistency within a nominal TDW. If no such event occurs within a nominal TDW, then only one actual TDW exists within that nominal TDW. If such an event occurs within a nominal TDW, then the time slots from the start of the first PUSCH / PUCCH transmission within the nominal TDW to the event constitute the first actual TDW. Afterward, whether an actual TDW is generated after the event ends depends on the event type and the terminal's capabilities. More specifically, if the aforementioned event is a semi-static event, an actual TDW is generated after the event ends; if the aforementioned event is a dynamic event, then it depends on the terminal's capabilities. If the terminal device supports the ability to restart the Demodulation Reference Signal (DMRS) binding after a dynamic event, an actual TDW is generated after the event ends; otherwise, no actual TDW is generated. If the event is triggered by DCI (Downlink Control Information) or MAC-CE (Media Access Control-Control Element), then the event is a first-type event (i.e., a dynamic event); otherwise, it is a second-type event (i.e., a semi-static event).

[0083] The inventors discovered through research that in related technologies, if a nominal TDW has only one Type I event or one Type II event, then joint channel estimation does not present a problem. However, if a nominal TDW contains both Type I and Type II events, then joint channel estimation will encounter certain problems. These situations include:

[0084] 1. Within a nominal TDW, after the first type of event occurs, a second type of event occurs.

[0085] 2. Within a nominal TDW, there is some overlap in the occurrence of Type I and Type II events.

[0086] 3. Within a nominal TDW, there is some overlap between the occurrence of Type I events and Type II events, and then another Type I event or Type II event occurs.

[0087] In view of at least one of the above technical problems, this disclosure provides a time window design method, device and system, and a joint channel estimation method. The above embodiments of this disclosure will be described below through specific examples.

[0088] Figure 1 This is a schematic diagram of some embodiments of the joint channel estimation method of this disclosure. Preferably, this embodiment can be executed by the joint channel estimation system of this disclosure. The method may include at least one of steps 1 to 4, wherein:

[0089] Step 1: The network device determines the time-frequency transmission resources for repeated PUSCH / PUCCH transmissions and configures a nominal time window for the terminal device.

[0090] Step 2: The terminal device determines the actual time window within each nominal TDW based at least on the network device configuration, terminal capabilities, and the second and first types of events occurring within each nominal TDW.

[0091] Step 3: When the terminal device performs uplink transmission within the actual TDW, it should maintain power consistency and phase continuity so that the network device can perform joint channel estimation within the corresponding actual TDW.

[0092] Step 4: The network device determines the actual TDW within each actual TDW based at least on the resource configuration of the terminal device, the actual TDW configuration, the terminal capabilities, and the second type of events and the first type of events occurring within each actual TDW, and performs joint channel estimation within the actual TDW.

[0093] The main innovation of the above embodiments of this disclosure lies in Figure 1 In steps 2 and 4 of the embodiment, the time window design method for determining the actual TDW within each nominal TDW is described below through specific embodiments.

[0094] Figure 2 This diagram illustrates some embodiments of the time window design method of this disclosure. Preferably, this embodiment can be executed by the joint channel estimation system of this disclosure, the terminal device of this disclosure, or the network device of this disclosure. The method may include at least step 20, wherein:

[0095] Step 20: If there are first-type and second-type events within the nominal time window, determine the actual time window within each nominal time window based on the terminal's capabilities.

[0096] In some embodiments of this disclosure, step 20 may include: if there are first-type events and second-type events within a nominal time window, determining the actual time window within each nominal time window based on the network device configuration, terminal capabilities, and the second-type events and first-type events occurring within each nominal time window.

[0097] In some embodiments of this disclosure, the first type of event is a first event triggered by downlink control information or an event triggered by the Media Access Control-Control Unit (MAC-CE), and the second type of event is a second event triggered by downlink control information or an event not triggered by downlink control information or the Media Access Control-Control Unit.

[0098] In some embodiments of this disclosure, the first type of event is a dynamic event, and the second type of event is a semi-static event.

[0099] In some embodiments of this disclosure, the first type of event and the second type of event are mutually exclusive.

[0100] In some embodiments of this disclosure, the first event and the second event are mutually exclusive.

[0101] In some embodiments of this disclosure, the first event is a non-frequency hopping transmission event, and the second event is a frequency hopping transmission event.

[0102] In some embodiments of this disclosure, step 20 may include: determining the actual time window within each nominal time window based on the nominal time window configured by the network device, whether the terminal device supports the first terminal capability (terminal capability A), and the second type of event and the first type of event occurring within each nominal time window, wherein the first terminal capability is the ability of the terminal device to restart the demodulation reference signal binding after the first type of event ends.

[0103] The specific methods of the actual TDW within each nominal TDW are described below with reference to specific embodiments.

[0104] Example 1-1

[0105] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include at least one of steps 21 to 23, wherein:

[0106] Step 21: If a first type of event and a second type of event occur within a nominal time window, and the occurrence times of the first type of event and the second type of event overlap, and the first type of event overrides the second type of event, or drops the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event, then proceed to step 22 or step 23.

[0107] In some embodiments of this disclosure, the duration of the first type of event and the second type of event includes the following three cases: the duration is 0 (i.e., no duration), the duration is a portion of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the duration is one or more time slots.

[0108] In some embodiments of this disclosure, the overlap in occurrence time between the first type of event and the second type of event includes at least the following situations: ① The duration of the first type of event and the second type of event is not 0, and there is at least one time-domain overlap of OFDM symbols within the duration; ② At least one of the first type of event and the second type of event has a duration of 0, and the starting time-domain positions of the events are consistent; ③ One of the first type of event and the second type of event has a duration of 0, and the event with a duration of 0 is located within the duration of the other event.

[0109] Step 22: If the terminal device supports the first terminal capability, after the first type of event ends, generate an actual time window, wherein the actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs, such as... Figure 3 As shown.

[0110] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0111] In some embodiments of this disclosure, the relevant radio resource control signaling is PUCCH-Window-Restart signaling or PUSCH-Window-Restart signaling, used to indicate whether to enable the function of restarting demodulation reference signal binding after the first type of event ends.

[0112] Figure 3 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 3As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. In time slot #3, there are overlapping dynamic events (i.e., the first type of event) and semi-static events (i.e., the second type of event). The first type of event overwrites the second type of event, or abandons the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event. If the terminal device supports the first terminal capability, an actual time window is generated, which extends from time slot #4 to time slot #8.

[0113] Step 23: If the terminal device does not support the first terminal capability, after the first type of event ends, until the nominal time window ends or the next first type of event or second type of event occurs, no actual time window is generated. Figure 4 As shown.

[0114] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following situations: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the first terminal capability is disabled; or, the terminal device does not support the first terminal capability.

[0115] Figure 4 This is a schematic diagram illustrating the determination of the actual time window in other embodiments of this disclosure. For example... Figure 4 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. In time slot #3, there are overlapping dynamic events and semi-static events. If the terminal device does not support the first terminal capability, then after the first type of event ends, no actual time window will be generated until the nominal time window ends or the next first type of event or second type of event occurs.

[0116] Examples 1-2

[0117] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include: if a first type of event and a second type of event occur within a nominal time window, and the first type of event and the second type of event overlap in occurrence time, and if the second type of event overrides the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event, then after the second type of event ends, an actual time window is generated, wherein the actual time window continues until the nominal time window ends or before the next first type of event or second type of event occurs.

[0118] In some embodiments of this disclosure, Figure 2Step 20 of the embodiment may include: regardless of whether the terminal device supports "Terminal Capability A", after the second type of event ends, generating an actual TDW, which continues until the nominal TDW ends or the next dynamic, second type of event occurs, such as... Figure 3 As shown.

[0119] In some embodiments of this disclosure, the duration of the first type of event and the second type of event in Embodiments 1-2 overlaps with the occurrence time of the first type of event and the second type of event, which is consistent with the relevant description of Embodiments 1-1.

[0120] Example 2

[0121] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include at least one of steps 24 to 27, wherein:

[0122] Step 24: If a third type of event occurs first within a nominal time window, followed by a second type of event, and the third type of event and the second type of event do not overlap in time, determine whether the terminal supports the first terminal capability. Here, the third type of event is either a first type of event or a first overlapping event. The first overlapping event is a first type of event and a second type of event that overlap in time, where the first type of event overrides the second type of event, or the second type of event is discarded and only the first type of event is processed, or the second type of event is ignored and only the first type of event is processed. If the terminal supports the first terminal capability, proceed to step 25; otherwise, if the terminal does not support the first terminal capability, proceed to step 26 or step 27.

[0123] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0124] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following cases: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is disabled after the first type of event ends; or, the terminal device does not support the first terminal capability.

[0125] In some embodiments of this disclosure, step 24 may include: if a first type of event occurs first and then a second type of event occurs within a nominal TDW, and the first type of event and the second type of event do not overlap in time, determining whether the terminal supports the first terminal capability.

[0126] Step 25: If the terminal device supports the first terminal capability, an actual time window is generated after the third type of event ends. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0127] In some embodiments of this disclosure, step 25 may include: if the terminal device supports "Terminal Capability A", then after the first type of event ends, an actual TDW is generated, which continues until the second type of event occurs; after the second type of event ends, another actual TDW is generated, which continues until the nominal TDW ends or the next dynamic, second type of event occurs, such as... Figure 5 As shown.

[0128] Figure 5 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 5 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions, with a nominal time window of 8 time slots. A first type of event (i.e., a dynamic event) occurs in time slot #3, and a second type of event (i.e., a semi-static event) occurs in time slot #6. After the first type of event in time slot #3 ends, an actual TDW is generated, which runs from time slot #4 to time slot #5. After the second type of event in time slot #6 ends, another actual TDW is generated, which runs from time slot #7 to time slot #8.

[0129] Step 26: If the terminal does not support the capabilities of the first terminal, no actual time window will be generated from the end of the third type of event until the end of the nominal time window.

[0130] In some embodiments of this disclosure, step 26 may include: if the terminal device does not support "Terminal Capability A", then from the end of the first type of event until the end of the nominal TDW, no actual TDW is generated, such as... Figure 6 As shown.

[0131] Figure 6 This is a schematic diagram illustrating the determination of the actual time window in other embodiments of this disclosure. For example... Figure 6As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. A first type of event (i.e., a dynamic event) occurs in time slot #3, and a second type of event (i.e., a semi-static event) occurs in time slot #6. If the terminal device does not support the first terminal capability, then after the first type of event in time slot #3 ends, no actual time window is generated until the nominal time window ends.

[0132] Step 27: If the terminal does not support the first terminal capability, after the second type of event ends, generate an actual time window. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0133] In some embodiments of this disclosure, step 27 may include: if the terminal device does not support "Terminal Capability A", then after the second type of event ends, an actual TDW is generated, which persists until the nominal TDW ends or before the next dynamic, second type of event occurs, such as... Figure 7 As shown.

[0134] Figure 7 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 7 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. The first type of event (i.e., dynamic event) occurs in time slot #3, and the second type of event (i.e., semi-static event) occurs in time slot #6. After the second type of event in time slot #6 ends, an actual TDW is generated, which runs from time slot #7 to time slot #8.

[0135] In some embodiments of this disclosure, the method of steps 24-27 is also applicable to the following situation: a first type of event and a second type of event that overlap in time occur within a nominal TDW, and the terminal device discards the second type of event and only processes the first type of event, after which another second type of event occurs.

[0136] Example 3

[0137] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include at least one of steps 201 to 203, wherein:

[0138] Step 201: If a fourth type of event occurs first within a nominal time window, followed by a first type of event, and the second type of event and the first type of event do not overlap in time, determine whether the terminal supports the first terminal capability. Here, the fourth type of event is either a second type of event or a second overlapping event. The second overlapping event is when the first type of event and the second type of event overlap in time, and the second type of event either overrides the first type of event, abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event. If the terminal supports the first terminal capability, proceed to step 202; otherwise, if the terminal does not support the first terminal capability, proceed to step 203.

[0139] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0140] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following cases: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is disabled after the first type of event ends; or, the terminal device does not support the first terminal capability.

[0141] In some embodiments of this disclosure, step 201 may include: if a second type of event occurs successively within a nominal TDW, followed by a first type of event, and the second type of event and the first type of event do not overlap in time, determining whether the terminal supports the first terminal capability.

[0142] Step 202: If the terminal supports the first terminal capability, an actual time window is generated after the fourth type of event ends. This actual time window continues until the first type of event occurs. After the first type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0143] In some embodiments of this disclosure, step 202 may include: if the terminal device supports "Terminal Capability A", then after the second type of event ends, an actual TDW is generated, which persists until the first type of event occurs; after the first type of event ends, another actual TDW is generated, which persists until the nominal TDW ends or the next dynamic, second type of event occurs, such as... Figure 8 As shown.

[0144] Figure 8This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 8 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions, with a nominal time window of 8 time slots. A second type of event (i.e., a semi-static event) occurs in time slot #3, and a first type of event (i.e., a dynamic event) occurs in time slot #6. After the second type of event in time slot #3 ends, an actual TDW is generated, which runs from time slot #4 to time slot #5. After the first type of event in time slot #6 ends, another actual TDW is generated, which runs from time slot #7 to time slot #8.

[0145] Step 203: If the terminal does not support the first terminal capability, after the fourth type of event ends, an actual time window is generated. This actual time window continues until the first type of event occurs. After the first type of event ends, no more actual time windows are generated until the nominal time window ends or the next first type of event or second type of event occurs.

[0146] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following situations: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the first terminal capability is disabled; or, the terminal device does not support the first terminal capability.

[0147] In some embodiments of this disclosure, step 203 may include: if the terminal device does not support "Terminal Capability A", then after the second type of event ends, an actual TDW is generated, which continues until the first type of event occurs. After the first type of event ends, until the nominal TDW ends or the next dynamic, second type of event occurs, no more actual TDWs are generated. Figure 9 As shown.

[0148] Figure 9 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 9 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. A second type of event (i.e., a semi-static event) occurs in time slot #3, and a first type of event (i.e., a dynamic event) occurs in time slot #6. After the second type of event in time slot #3 ends, an actual TDW is generated. This actual TDW runs from time slot #4 to time slot #5. After the first type of event in time slot #6 ends, no more actual TDWs are generated until the nominal TDW ends.

[0149] In some embodiments of this disclosure, the method described in Embodiment 3 is also applicable to the following situation: a first type of event and a second type of event that overlap in time occur within a nominal TDW, and the terminal device ignores the first type of event and only processes the second type of event, after which the first type of event occurs again.

[0150] Example 4

[0151] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include: if a fourth type of event occurs first and then a second type of event occurs within a nominal time window, and the fourth type of event and the second type of event do not overlap in time, after the fourth type of event ends, an actual time window is generated, which lasts until the second type of event occurs; after the second type of event ends, another actual time window is generated, which lasts until the nominal time window ends or the next first type of event or second type of event occurs. Here, the fourth type of event is a second type of event or a second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, and the second type of event either overwrites the first type of event, abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event.

[0152] In some embodiments of this disclosure, Figure 2 Step 20 of the embodiment may include: two second-type events occurring sequentially within a nominal TDW, and the two second-type events not overlapping in time; regardless of whether the terminal device supports "Terminal Capability A", after the first second-type event ends, an actual TDW is generated, which continues until the second second-type event; after the second second-type event ends, another actual TDW is generated, which continues until the nominal TDW ends or before the next dynamic second-type event occurs, such as... Figure 10 As shown.

[0153] Figure 10 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 10As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions, with a nominal time window of 8 time slots. A second type of event (i.e., a semi-static event) occurs in time slot #3 and in time slot #6. After the second type of event in time slot #3 ends, an actual TDW is generated, which runs from time slot #4 to time slot #5. After the second type of event in time slot #6 ends, another actual TDW is generated, which runs from time slot #7 to time slot #8.

[0154] In some embodiments of this disclosure, the method described in embodiment 4 is also applicable to the following situation: a first type of event and a second type of event that overlap in time occur within a nominal TDW, and the terminal device ignores the first type of event and only processes the second type of event, after which another second type of event occurs.

[0155] The above embodiments of this disclosure aim to propose a time window design method. For the case where both type I events and type II events exist within the nominal time window, an actual time window design method is proposed to improve the joint channel estimation performance of PUSCH / PUCCH.

[0156] The embodiments disclosed above relate to the field of wireless communication technology, particularly 5G.

[0157] The time window design method of this disclosure will be described below through specific embodiments. Specific embodiments 1 and 2 are illustrated using bound time slot frequency hopping transmission as an example. Specific Implementation Example 1

[0159] In an FDD system, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions and configures the nominal TDW and the number of time slots bound for frequency hopping, such as 4 time slots. The terminal device performs frequency hopping transmission in units of 4 time slots according to the network device configuration. Within the nominal TDW in the diagram, there are two events: one is a type I event (i.e., a dynamic event), and the other is a frequency hopping event (type II event).

[0160] If the terminal device supports "Terminal Capability A", an actual TDW is generated after the first type of event ends. This actual TDW continues until the frequency hopping event. After the frequency hopping, another actual TDW is generated, and this actual TDW continues until the nominal TDW ends. Figure 11 As shown.

[0161] Figure 11This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 11 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions, with a nominal time window of 8 time slots. A first type of event occurs in time slot #2, and a frequency hopping event (a second type of event, a semi-static event) occurs between time slots #4 and #5. After the first type of event (i.e., the dynamic event) in time slot #2 ends, an actual TDW is generated, which moves from time slot #3 to time slot #4. After the frequency hopping event ends, another actual TDW is generated, which moves from time slot #5 to time slot #8.

[0162] If the terminal device does not support "Terminal Capability A", then no actual TDW will be generated from the end of the first type of event until the frequency hopping event. After the frequency hopping event, an actual TDW will be generated, and this actual TDW will continue until the nominal TDW ends. Figure 12 As shown.

[0163] Figure 12 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 12 As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. A first type of event (i.e., a dynamic event) occurs in time slot #2. A frequency hopping event (a semi-static event) occurs between time slots #4 and #5. After the frequency hopping event ends, an actual TDW is generated, which runs from time slot #5 to time slot #8. Specific Implementation Example 2:

[0165] In an FDD system, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions and configures the nominal TDW and the number of time slots bound for frequency hopping, such as 4 time slots. The terminal device performs frequency hopping transmission in units of 4 time slots according to the network device configuration. Within the nominal TDW in the diagram, there are two events: one is a type I event (i.e., a dynamic event), and the other is a frequency hopping event (a semi-static event).

[0166] If the terminal device does not support "Terminal Capability A", then no actual TDW will be generated after the first type of event ends and before the nominal TDW ends. Figure 13 As shown.

[0167] Figure 13 This is a schematic diagram illustrating the determination of the actual time window in some embodiments of this disclosure. For example... Figure 13As shown, the network device schedules the terminal device to perform 8 PUSCH or PUCCH transmissions. The nominal time window is 8 time slots. A first type of event (i.e., a dynamic event) occurs in time slot #2. A frequency hopping event (a semi-static event) occurs between time slots #4 and #5. No actual TDW is generated after the first type of event ends and before the nominal TDW ends.

[0168] The embodiments of this disclosure propose a time window design. For cases where both Type I and Type II events exist within the nominal time window, an actual time window design method is proposed, thereby improving the joint channel estimation performance of PUSCH / PUCCH. The embodiments of this disclosure can at least solve the time window determination problem in the following situations:

[0169] First, within a nominal TDW, after the first type of event occurred, a second type of event occurred.

[0170] Second, within a nominal TDW, there is some overlap between the occurrence of Type I and Type II events.

[0171] Third, within a nominal TDW, there is some overlap between the occurrence of Type I events and Type II events, and Type I events or Type II events occur again afterward.

[0172] Figure 14 This is a schematic diagram of some other embodiments of the joint channel estimation method of this disclosure. Preferably, this embodiment can be executed by the joint channel estimation system or the terminal device of this disclosure. The method may include at least one of steps 141 and 142, wherein:

[0173] Step 141, the terminal device adopts any of the above embodiments (e.g.) Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0174] Step 142: When the terminal device performs uplink transmission within the actual time window, it maintains power consistency and phase continuity so that the network device can perform joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

[0175] Figure 15 This is a schematic diagram illustrating further embodiments of the joint channel estimation method of this disclosure. Preferably, this embodiment can be executed by the joint channel estimation system or the network device of this disclosure. The method may include at least one of steps 151 to 153, wherein:

[0176] Step 151: The network device determines the time-frequency transmission resources for repeated transmission of the Physical Uplink Shared Channel and the Physical Uplink Control Channel, and configures a nominal time window for the terminal device so that the terminal device can use any of the above embodiments (e.g., Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0177] Step 152, the network device adopts any of the above embodiments (e.g.) Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0178] Step 153: When the terminal device performs uplink transmission within the actual time window, the network device performs joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

[0179] Figure 16 These are schematic diagrams illustrating some embodiments of the terminal device disclosed herein. For example... Figure 16 As shown, the terminal device disclosed herein may include a time window determination module 161, wherein:

[0180] The time window determination module 161 is used to determine the actual time window within each nominal time window based on the terminal's capabilities, in the case of a first type of event and a second type of event occurring within the nominal time window.

[0181] In some embodiments of this disclosure, the first type of event is a first event triggered by downlink control information or an event triggered by the media access control-control unit, and the second type of event is a second event triggered by downlink control information or an event not triggered by downlink control information or the media access control-control unit.

[0182] In some embodiments of this disclosure, the first type of event is a dynamic event, and the second type of event is a semi-static event.

[0183] In some embodiments of this disclosure, the first type of event and the second type of event are mutually exclusive.

[0184] In some embodiments of this disclosure, the first event and the second event are mutually exclusive.

[0185] In some embodiments of this disclosure, the first event is a non-frequency hopping transmission event, and the second event is a frequency hopping transmission event.

[0186] In some embodiments of this disclosure, the time window determination module 161 can be used to determine the actual time window within each nominal time window based on whether the terminal device supports a first terminal capability, wherein the first terminal capability is the ability of the terminal device to restart the demodulation reference signal binding after the first type of event ends.

[0187] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the first type of event ends, provided that a first type of event and a second type of event occur within a nominal time window, and the first type of event and the second type of event overlap in occurrence time, and the first type of event overrides the second type of event, or the second type of event is abandoned and only the first type of event is processed, or the second type of event is ignored and only the first type of event is processed, provided that the terminal device supports the first terminal capability. The actual time window continues until the nominal time window ends or the next first type of event or the second type of event occurs. If the terminal device does not support the first terminal capability, no actual time window is generated after the first type of event ends, until the nominal time window ends or the next first type of event or the second type of event occurs.

[0188] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the second type of event ends, in the case where a first type of event and a second type of event occur within a nominal time window, and the first type of event and the second type of event overlap in occurrence time, and the second type of event overrides the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event. The actual time window continues until the nominal time window ends or before the next first type of event or second type of event occurs.

[0189] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the third type of event occurs first and then the second type of event occurs within a nominal time window, provided that the third type of event and the second type of event do not overlap in time. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. The third type of event is either a first type of event or a first overlapping event. The first overlapping event is a first type of event and a second type of event that overlap in time. The first type of event either overwrites the second type of event, or abandons the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event.

[0190] In some embodiments of this disclosure, the time window determination module 161 can be used to determine that if a third type of event occurs first and then a second type of event occurs within a nominal time window, and the occurrence times of the third type of event and the second type of event do not overlap, and if the terminal device does not support the first terminal capability, then from the end of the third type of event until the end of the nominal time window, no actual time window is generated.

[0191] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the second type of event has ended, provided that a third type of event occurs first and then a second type of event occurs within a nominal time window, and the occurrence times of the third type of event and the second type of event do not overlap, and the terminal device does not support the first terminal capability. The actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0192] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the fourth type of event occurs first, followed by the first type of event, and the second type of event does not overlap with the first type of event in terms of occurrence time, provided that the terminal device supports the first terminal capability. This actual time window continues until the first type of event occurs. After the first type of event ends, another actual time window is generated, continuing until the nominal time window ends or the next first or second type of event occurs. The fourth type of event is either the second type of event or the second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, where the second type of event overrides the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed. If the terminal device does not support the first terminal capability, after the fourth type of event ends, an actual time window is generated. This actual time window continues until the first type of event occurs. After the first type of event ends, no more actual time windows are generated until the nominal time window ends or the next first type of event or second type of event occurs.

[0193] In some embodiments of this disclosure, the time window determination module 161 can be used to generate an actual time window after the fourth type of event occurs first and then the second type of event occurs within a nominal time window, and the fourth type of event and the second type of event do not overlap in time. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. Here, the fourth type of event is the second type of event or the second overlapping event. The second overlapping event is the first type of event and the second type of event that overlap in time, and the second type of event overwrites the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event.

[0194] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0195] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following cases: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is disabled after the first type of event ends; or, the terminal device does not support the first terminal capability.

[0196] In some embodiments of this disclosure, such as Figure 16 As shown, the terminal device of this disclosure may further include a transmission module 162, wherein:

[0197] Time window determination module 161 is used to employ any of the above embodiments (e.g.) Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0198] The transmission module 162 is used to maintain power consistency and phase continuity during uplink transmission within the actual time window, so that the network device can perform joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

[0199] In some embodiments of this disclosure, the terminal device is used to perform implementations as described in any of the embodiments above (e.g., Figures 2-13 The time window design method described above, and / or the implementation of any of the above embodiments ( Figure 14 The operation of the joint channel estimation method described in the embodiment)

[0200] Figure 17This is a schematic diagram illustrating the structure of some embodiments of the terminal device disclosed herein. For example... Figure 17 As shown, the terminal device includes a terminal device memory 171 and a terminal device processor 172.

[0201] Terminal device memory 171 is used to store instructions. Terminal device processor 172 is coupled to terminal device memory 171 and is configured to execute instructions stored in memory as described in any of the above embodiments (e.g., Figures 2-13 The time window design method described above, and / or the implementation of any of the above embodiments ( Figure 14 The joint channel estimation method described in the example).

[0202] like Figure 17 As shown, the terminal device also includes a terminal device communication interface 173 for exchanging information with other devices. Additionally, the terminal device includes a terminal device bus 174, through which the terminal device processor 172, the terminal device communication interface 173, and the terminal device memory 171 communicate with each other.

[0203] The terminal device memory 171 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device. The terminal device memory 171 may also be a memory array. The terminal device memory 171 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0204] Furthermore, the terminal device processor 172 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0205] Figure 18 This is a schematic diagram of some embodiments of the network device disclosed herein. For example... Figure 18 As shown, the network device disclosed herein may include a time window design unit 181, wherein:

[0206] The time window design unit 181 is used to determine the actual time window within each nominal time window based on the terminal's capabilities, in the case of a first type of event and a second type of event occurring within the nominal time window.

[0207] In some embodiments of this disclosure, the first type of event is a first event triggered by downlink control information or an event triggered by the media access control-control unit, and the second type of event is a second event triggered by downlink control information or an event not triggered by downlink control information or the media access control-control unit.

[0208] In some embodiments of this disclosure, the first type of event is a dynamic event, and the second type of event is a semi-static event.

[0209] In some embodiments of this disclosure, the first type of event and the second type of event are mutually exclusive.

[0210] In some embodiments of this disclosure, the first event and the second event are mutually exclusive.

[0211] In some embodiments of this disclosure, the first event is a non-frequency hopping transmission event, and the second event is a frequency hopping transmission event.

[0212] In some embodiments of this disclosure, the time window design unit 181 can be used to determine the actual time window within each nominal time window based on whether the terminal device supports a first terminal capability, wherein the first terminal capability is the ability of the terminal device to restart the demodulation reference signal binding after the first type of event ends.

[0213] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the first type of event ends, provided that a first type of event and a second type of event occur within a nominal time window, and the first type of event and the second type of event overlap in occurrence time, and the first type of event overrides the second type of event, or the second type of event is abandoned and only the first type of event is processed, or the second type of event is ignored and only the first type of event is processed, provided that the terminal device supports the first terminal capability. The actual time window continues until the nominal time window ends or the next first type of event or the next second type of event occurs. If the terminal device does not support the first terminal capability, no actual time window is generated after the first type of event ends, until the nominal time window ends or the next first type of event or the next second type of event occurs.

[0214] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the second type of event ends, in the case where a first type of event and a second type of event occur within a nominal time window, and the first type of event and the second type of event overlap in occurrence time, and the second type of event overrides the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event. The actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0215] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the third type of event occurs first and then the second type of event occurs within a nominal time window, provided that the third type of event and the second type of event do not overlap in time. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. The third type of event is a first type of event or a first overlapping event. The first overlapping event is a first type of event and a second type of event that overlap in time. The first type of event overrides the second type of event, or abandons the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event.

[0216] In some embodiments of this disclosure, the time window design unit 181 can be used to prevent the generation of an actual time window when a third type of event occurs first and then a second type of event occurs within a nominal time window, and the occurrence times of the third type of event and the second type of event do not overlap, and the terminal device does not support the first terminal capability.

[0217] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the second type of event has ended, provided that a third type of event occurs first and a second type of event occurs after a nominal time window, and the third type of event and the second type of event do not overlap in time, and the terminal device does not support the first terminal capability. The actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

[0218] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the fourth type of event occurs first, followed by the first type of event, and the second type of event does not overlap with the first type of event in terms of occurrence time, provided the terminal device supports the first terminal capability. This actual time window continues until the first type of event occurs. After the first type of event ends, another actual time window is generated, continuing until the nominal time window ends or the next first or second type of event occurs. In this context, the fourth type of event is either the second type of event or the second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, where the second type of event overrides the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed. If the terminal device does not support the capabilities of the first terminal, after the fourth type of event ends, an actual time window is generated. This actual time window continues until the first type of event occurs. After the first type of event ends, no further actual time windows are generated until the nominal time window ends or the next first type of event or second type of event occurs.

[0219] In some embodiments of this disclosure, the time window design unit 181 can be used to generate an actual time window after the fourth type of event occurs first and then the second type of event occurs within a nominal time window, and the fourth type of event and the second type of event do not overlap in time. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. Here, the fourth type of event is the second type of event or the second overlapping event. The second overlapping event is the first type of event and the second type of event that overlap in time, and the second type of event overwrites the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event.

[0220] In some embodiments of this disclosure, the terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends.

[0221] In some embodiments of this disclosure, the terminal device does not support the first terminal capability in the following cases: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is disabled after the first type of event ends; or, the terminal device does not support the first terminal capability.

[0222] In some embodiments of this disclosure, such as Figure 18 As shown, the network device disclosed herein may further include a nominal time window determination unit 180 and a joint channel estimation unit 182, wherein:

[0223] The nominal time window determination unit 180 is used to determine the time-frequency transmission resources for repeated transmission of the physical uplink shared channel and the physical uplink control channel, and to configure a nominal time window for the terminal device so that the terminal device can adopt any of the above embodiments (e.g.) Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0224] Time window design unit 181 is used to employ any of the embodiments described above (e.g.) Figures 2-13 The time window design method described in any embodiment determines the actual time window within each nominal time window.

[0225] The joint channel estimation unit 182 is used to perform joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window when the terminal device performs uplink transmission within the actual time window.

[0226] In some embodiments of this disclosure, the network device is configured to perform implementations as described in any of the embodiments above (e.g., Figures 2-13 The time window design method described above, and / or the implementation of any of the above embodiments ( Figure 15 The operation of the joint channel estimation method described in the embodiment)

[0227] Figure 19 This is a schematic diagram illustrating the structure of some embodiments of the network device disclosed herein. For example... Figure 19 As shown, the network device includes a network device memory 191 and a network device processor 192.

[0228] Network device memory 191 is used to store instructions. Network device processor 192 is coupled to network device memory 191 and is configured to execute instructions based on the memory storage as described in any of the above embodiments (e.g., Figures 2-13 The time window design method described above, and / or the implementation of any of the above embodiments ( Figure 15 The joint channel estimation method described in the example).

[0229] like Figure 19As shown, the network device also includes a network device communication interface 193 for exchanging information with other devices. Additionally, the network device includes a network device bus 194, through which the network device processor 192, the network device communication interface 193, and the network device memory 191 communicate with each other.

[0230] Network device memory 191 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device. Network device memory 191 may also be a memory array. Network device memory 191 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0231] Furthermore, the network device processor 192 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0232] According to another aspect of this disclosure, a time window design system is provided, comprising any of the embodiments described above ( Figure 16 or Figure 17 The terminal device described in the embodiments, and the terminal device as described in any of the above embodiments ( Figure 18 or Figure 19 The network device described in the embodiment).

[0233] The above embodiments of this disclosure aim to propose a time window design system. For cases where both type I events and type II events exist within the nominal time window, an actual time window design scheme is proposed, which can improve the joint channel estimation performance of PUSCH / PUCCH.

[0234] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium stores computer instructions that, when executed by a processor, implement any of the embodiments described above (e.g., Figures 2-13 The time window design method described in any embodiment, and / or the implementation of any of the above embodiments (e.g.) Figure 1 , Figures 14-15 The joint channel estimation method described in any of the embodiments.

[0235] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0236] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0237] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0238] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0239] The terminal devices and network devices described above can be implemented as including general-purpose processors, programmable logic controllers (PLCs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described in this application.

[0240] This concludes the detailed description of the present disclosure. To avoid obscuring the concept of the disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.

[0241] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing the relevant hardware to implement them. The program can be stored in a non-transitory computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0242] The description in this disclosure is provided for illustrative and descriptive purposes only and is not intended to be exhaustive or to limit the disclosure to its forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of this disclosure and to enable those skilled in the art to understand this disclosure and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A time window design method, characterized in that, include: If there are first-type and second-type events within the nominal time window, the actual time window within each nominal time window is determined according to the terminal's capabilities. The first-type events are dynamic events, and the second-type events are semi-static events. The step of determining the actual time window within each nominal time window based on terminal capabilities includes: Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event ends. The step of determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: If both a first-type event and a second-type event occur within a nominal time window, and their occurrence times overlap, and the first-type event either overrides the second-type event, or the second-type event is discarded and only the first-type event is processed, or the second-type event is ignored and only the first-type event is processed, then... If the terminal device supports the first terminal capability, after the first type of event ends, a new actual time window is determined, wherein the actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

2. The time window design method according to claim 1, characterized in that, The first type of event is a first event triggered by downlink control information or an event triggered by the media access control-control unit. The second type of event is a second event triggered by downlink control information or an event not triggered by downlink control information or the media access control-control unit.

3. The time window design method according to claim 2, characterized in that... ； Type I events and Type II events are mutually exclusive; And / or, The first event and the second event are mutually exclusive.

4. The time window design method according to claim 2 or 3, characterized in that, The first event is a non-frequency hopping transmission event, and the second event is a frequency hopping transmission event.

5. The time window design method according to claim 1, characterized in that, The step of determining the actual time window within each nominal time window based on whether the terminal device supports the capabilities of the first terminal includes: If the terminal device does not support the first terminal capability, no actual time window will be generated after the first type of event ends, until the nominal time window ends or the next first type of event or second type of event occurs.

6. A time window design method, characterized in that, include: If there are first-type and second-type events within the nominal time window, the actual time window within each nominal time window is determined according to the terminal's capabilities. The first-type events are dynamic events, and the second-type events are semi-static events. The step of determining the actual time window within each nominal time window based on terminal capabilities includes: Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event ends. The step of determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: If a first type of event and a second type of event occur within a nominal time window, and the occurrence times of the first type of event and the second type of event overlap, and the second type of event overrides the first type of event, or abandons the first type of event and only processes the second type of event, or ignores the first type of event and only processes the second type of event, then an actual time window is generated after the second type of event ends. The actual time window continues until the nominal time window ends or before the next first type of event or second type of event occurs.

7. A time window design method, characterized in that, include: If there are first-type and second-type events within the nominal time window, the actual time window within each nominal time window is determined according to the terminal's capabilities. The first-type events are dynamic events, and the second-type events are semi-static events. The step of determining the actual time window within each nominal time window based on terminal capabilities includes: Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event ends. The step of determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: If a third type of event occurs first, followed by a second type of event, within a nominal time window, and the third type of event and the second type of event do not overlap in their occurrence time, When the terminal device supports the first terminal capability, an actual time window is generated after the third type of event ends. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs. The third type of event is a first type of event or a first overlapping event. The first overlapping event is a first type of event and a second type of event that overlap in time. The first type of event overrides the second type of event, or abandons the second type of event and only processes the first type of event, or ignores the second type of event and only processes the first type of event.

8. The time window design method according to claim 7, characterized in that, The step of determining the actual time window within each nominal time window based on whether the terminal device supports the capabilities of the first terminal further includes: If the terminal device does not support the capabilities of the first terminal, no actual time window will be generated from the end of the third type of event until the end of the nominal time window. or, If the terminal device does not support the first terminal capability, an actual time window is generated after the second type of event ends. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs.

9. A time window design method, characterized in that, include: If there are first-type and second-type events within the nominal time window, the actual time window within each nominal time window is determined according to the terminal's capabilities. The first-type events are dynamic events, and the second-type events are semi-static events. The step of determining the actual time window within each nominal time window based on terminal capabilities includes: Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event ends. The step of determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: If, within a nominal time window, a fourth type of event occurs first, followed by a first type of event, and the second type of event does not overlap with the first type of event in terms of occurrence time, When the terminal device supports the first terminal capability, an actual time window is generated after the fourth type of event ends. This actual time window continues until the first type of event occurs. After the first type of event ends, another actual time window is generated. This actual time window continues until the nominal time window ends or the next first type of event or second type of event occurs. The fourth type of event is a second type of event or a second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, and the second type of event overwrites the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed. If the terminal device does not support the first terminal capability, after the fourth type of event ends, an actual time window is generated. This actual time window continues until the first type of event occurs. After the first type of event ends, no more actual time windows are generated until the nominal time window ends or the next first or second type of event occurs.

10. A time window design method, characterized in that, include: If there are first-type and second-type events within the nominal time window, the actual time window within each nominal time window is determined according to the terminal's capabilities. The first-type events are dynamic events, and the second-type events are semi-static events. The step of determining the actual time window within each nominal time window based on terminal capabilities includes: Based on whether the terminal device supports the first terminal capability, the actual time window within each nominal time window is determined. The first terminal capability is the terminal device's ability to restart the demodulation reference signal binding after the first type of event ends. The step of determining the actual time window within each nominal time window based on whether the terminal device supports the first terminal capability includes: If a fourth type of event occurs first within a nominal time window, followed by a second type of event, and the fourth type of event and the second type of event do not overlap in time, an actual time window is generated after the fourth type of event ends. This actual time window continues until the second type of event occurs. After the second type of event ends, another actual time window is generated, which continues until the nominal time window ends or the next first type of event or second type of event occurs. Here, the fourth type of event is either a second type of event or a second overlapping event. The second overlapping event is a first type of event and a second type of event that overlap in time, where the second type of event overwrites the first type of event, or the first type of event is abandoned and only the second type of event is processed, or the first type of event is ignored and only the second type of event is processed.

11. The time window design method according to any one of claims 1-3 and 5-10, characterized in that, The terminal device supports the first terminal capability when the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is enabled after the first type of event ends. The terminal device does not support the first terminal capability in the following situations: the terminal device supports the first terminal capability and the relevant radio resource control signaling indicates that the function of restarting demodulation reference signal binding is turned off after the first type of event ends; or, the terminal device does not support the first terminal capability.

12. A joint channel estimation method, characterized in that, include: The terminal device uses the time window design method as described in any one of claims 1-11 to determine the actual time window within each nominal time window; When terminal devices perform uplink transmission within the actual time window, they maintain power consistency and phase continuity so that network devices can perform joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

13. A joint channel estimation method, characterized in that, include: The network device determines the time-frequency transmission resources for repeated transmission of the physical uplink shared channel and the physical uplink control channel, and configures a nominal time window for the terminal device so that the terminal device can use the time window design method as described in any one of claims 1-11 to determine the actual time window within each nominal time window; The network device uses the time window design method as described in any one of claims 1-11 to determine the actual time window within each nominal time window; When the terminal device performs uplink transmission within the actual time window, the network device performs joint channel estimation of the physical uplink shared channel and the physical uplink control channel within the corresponding actual time window.

14. A terminal device, characterized in that, include: The time window determination module is used to determine the actual time window within each nominal time window based on the terminal's capabilities, in the case of first-type and second-type events occurring within the nominal time window. The terminal device is used to implement the time window design method as described in any one of claims 1-11, and / or the joint channel estimation method as described in claim 12.

15. A terminal device, characterized in that, include: Terminal device memory, used to store instructions; A terminal device processor is configured to execute the instructions, causing the terminal device to implement the time window design method as described in any one of claims 1-11, and / or the joint channel estimation method as described in claim 12.

16. A network device, characterized in that, include: The time window design unit is used to determine the actual time window within each nominal time window based on the terminal's capabilities, in the case of first-type and second-type events occurring within the nominal time window. The network device is used to implement the time window design method as described in any one of claims 1-11, and / or the joint channel estimation method as described in claim 13.

17. A network device, characterized in that, include: Network device memory, used to store instructions; A network device processor is configured to execute the instructions, causing the network device to implement the time window design method as described in any one of claims 1-11, and / or the joint channel estimation method as described in claim 13.

18. A time window design system, characterized in that, It includes the terminal device as described in any one of claims 14-15 and the network device as described in any one of claims 16-17.

19. A non-transitory computer-readable storage medium, characterized in that, The non-transient computer-readable storage medium stores computer instructions that, when executed by a processor, implement the time window design method as described in any one of claims 1-11, and / or the joint channel estimation method as described in claim 12 or 13.

Images