JP2023027178A - Method implemented by device and network device, and device for performing communication - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method and a device for implementing communication to reduce waste of a time and/or a frequency resource in a communication system.

SOLUTION: A method includes determining a target transmission pattern from a set of candidate transmission patterns that include a downlink (DL) transmission portion and/or an uplink (UL) transmission portion, in which duration of each DL transmission portion and/or UL transmission portion is different from each other, and performing communication between a network device and a terminal device using the target transmission pattern.

SELECTED DRAWING: Figure 3

COPYRIGHT: (C)2023,JPO&INPIT

Description

Embodiments of the present disclosure relate generally to communication technology. In particular, embodiments of the present disclosure relate to methods and apparatus for implementing communications.

With the development of communication technology, the frequency range up to 100 GHz has been explored with the aim of a single technical framework that addresses as many usage scenarios as possible. Enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), massive machine-type-communications (mMTC), etc. requirements and deployment scenarios have been defined.

In general, eMBB has stringent requirements for high peak data rates, but relatively loose requirements for user plane delay, for example 4ms for Uplink (UL) and Downlink (DL) transmission. In contrast, URLLC requires ultra-low delay and high reliability, eg, user plane delay of eg 0.5 ms for UL and DL transmission.

When a terminal device requesting an eMBB service (also referred to as an “eMBB terminal”) and another terminal requesting a URLLC service (also referred to as a “URLLC terminal”) are multiplexed in the same transmission pattern such as a subframe, the eMBB can be several times the user plane delay of URLLC. Thus, eMBB terminals may be scheduled in multiple subframes and URLLC UEs may be scheduled in one subframe to meet tighter user plane delay requirements.

Traditionally, the UL and DL transmission periods were configured in the full bandwidth. Therefore, some resources may be wasted if eMBB terminals and URLLC terminals are multiplexed in the frequency domain.

Accordingly, there is a need for signal transmission schemes that reduce waste of time and/or frequency resources.

The present disclosure proposes solutions for implementing communications to reduce waste of time and/or frequency resources.

According to a first aspect of embodiments of the disclosure, embodiments of the disclosure provide a method implemented by an apparatus. A device determines a target transmission pattern from a set of candidate transmission patterns. Each of the candidate transmission patterns includes a DL transmission portion and/or a UL transmission portion, and the candidate transmission patterns differ from each other in the duration of their respective DL transmission portions and/or UL transmission portions. Communication between the network device and the terminal device is then performed using the target transmission pattern.

According to a second aspect of embodiments of the disclosure, embodiments of the disclosure provide an apparatus for communicating. The apparatus comprises a controller configured to determine a target transmission pattern from a set of candidate transmission patterns, wherein each of the candidate transmission patterns includes a DL transmission portion and/or an UL transmission portion, and the candidate transmission patterns are , the duration of each DL transmission part and/or UL transmission part is different from each other, and is adapted to communicate between a network device and a terminal device by using a target transmission pattern. and

Other features and advantages of embodiments of the present invention will become apparent from the following description of specific embodiments, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the disclosure.

Embodiments of the disclosure are provided in an illustrative sense, the advantages of which are explained in more detail below with reference to the accompanying drawings.

FIG. 1 shows a schematic diagram of a communication system 100 according to an embodiment of the disclosure.

FIG. 2 shows a schematic diagram 200 of transmission patterns according to an embodiment of the present disclosure.

FIG. 3 shows a flowchart of a method 300 of implementing communications according to an embodiment of the present disclosure.

FIG. 4 shows a diagram 400 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure.

FIG. 5 shows a diagram 500 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure.

FIG. 6 shows a diagram 600 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure.

FIG. 7 shows a diagram 700 of transmission patterns for UE1 and UE2 in terms of TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 8 shows a diagram 800 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 9 shows a diagram 900 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 10 shows a diagram 1000 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 11 shows a diagram 1100 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 12 shows a diagram 1200 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 13 shows a diagram 1300 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 14 shows a diagram 1400 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 15 shows a diagram 1500 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 16 shows a diagram 1600 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure.

FIG. 17 shows a diagram 1700 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 18 shows a diagram 1800 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 19 shows a diagram 1900 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 20 shows a diagram 2000 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure.

FIG. 21 shows a diagram 2100 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure.

FIG. 22 shows a diagram 2200 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure.

FIG. 23 shows a diagram 2300 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 24 shows a diagram 2400 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 25 shows a diagram 2500 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 26 shows a diagram 2600 of transmission patterns for UE1 and UE2 for TDD and GP, according to an embodiment of the present disclosure.

FIG. 27 shows a diagram 2700 of transmission patterns for UE1 and UE2 for TDD and GP, according to an embodiment of the present disclosure.

FIG. 28 shows a diagram 2800 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 29 shows a diagram 2900 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 30 shows a diagram 3000 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure.

FIG. 31 shows a diagram 3100 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure.

FIG. 32 shows a diagram 3200 of transmission patterns for UE1 and UE2 for FDD and PP, in accordance with an embodiment of the present disclosure.

FIG. 33 shows a diagram 3300 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure.

FIG. 34 shows a diagram 3400 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 35 shows a diagram 3500 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 36 shows a diagram 3600 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure.

FIG. 37 shows a diagram 3700 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure.

FIG. 38 shows a diagram 3800 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure.

FIG. 39 shows a diagram 3900 of transmission patterns for UE1 and UE2 for FDD and PP, in accordance with an embodiment of the present disclosure.

FIG. 40 shows a diagram 4000 of transmission patterns according to an embodiment of the present disclosure.

FIG. 41 shows a diagram 4100 of transmission patterns in accordance with an embodiment of the present disclosure.

FIG. 42 shows a schematic diagram of an apparatus 4200 according to one embodiment of the present disclosure.

In the drawings, same or similar reference numbers indicate same or similar components.

The subject matter described herein will be discussed with reference to several exemplary embodiments. It is understood that these embodiments are discussed only to enable those skilled in the art to better understand and practice the subject matter described herein, and do not represent any limitation of the scope of the subject matter.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “includes,” and/or “including,” as used herein, refer to the presence of a recited feature, integer, step, act, element, and/or component. is to be understood as not excluding the presence or addition of one or more other features, integers, steps, acts, elements, components, and/or groups thereof.

It should also be noted that, in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two functions or acts shown in succession may actually be executed concurrently or in the reverse order depending on the functions/acts involved.

As used herein, the term "communication network" refers to any suitable communication standard such as LTE-A (LTE-Advanced), WCDMA (Wideband Code Division Multiple Access), and HSPA (High-Speed Packet Access). Refers to a network that follows Furthermore, communication between terminal equipment and network equipment in a communication network includes first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation ( 4G), 4.5G, future fifth generation (5G), and/or any suitable generation communication protocol, including but not limited to currently known or future developed protocols. be able to.

Embodiments of the present disclosure may be applied in various communication systems. Given the rapid evolution of communications, there will naturally be future types of communications technologies and systems in which the present disclosure can be implemented. The scope of the present disclosure should not be considered limited to only the systems described above.

The term "network equipment" includes, but is not limited to, base stations (BSs), gateways, management entities, and other suitable devices in a communication system. The term "base station" or "BS" may be used for example Node B (NodeB or NB), Evolved Node B (eNodeB or eNB), Remote Radio Unit (RRU), Radio Header (RH), It may represent a Remote Radio Head (RRH), a relay, or a low power node such as a femto, pico, or the like.

The term "terminal equipment" includes, but is not limited to, user equipment (UE) and other suitable end devices capable of communicating with network equipment. By way of example, "terminal equipment" may be a terminal, mobile terminal (MT), subscriber station (SS), mobile subscriber station, mobile station (MS), or access terminal (AT). Access Terminal).

Several exemplary embodiments of the disclosure are described below with reference to the drawings. Reference is first made to FIG. 1, which shows a schematic diagram of a communication system 100 according to an embodiment of the present disclosure.

In the communication system 100, a network equipment (hereinafter also called BS) 110 communicates with two terminal equipments (hereinafter also called UEs) 121 and 122 by using the same or different transmission patterns. BS 110 provides eMBB service to UE 121, thus UE 121 may be referred to as an eMBB UE. BS 110 provides URLLC service to UE 122, and thus UE 122 may be referred to as a URLLC UE.

The term “transmission pattern” refers to the configuration of resources in the time domain and/or frequency domain. For example, a transmission pattern may correspond to one or more subframes or some number of symbols in the time domain, and one or more subcarriers in the frequency domain. A transmission pattern includes a DL transmission portion and/or a UL transmission portion. The transmission pattern differs with respect to the duration of each DL transmission portion and/or UL transmission portion. In embodiments of the present disclosure, the transmission pattern may include a set of candidate transmission patterns and a target transmission pattern, where the target transmission pattern is selected or determined from the set of candidate transmission patterns. The set of candidate transmission patterns may include one or more downlink-centric transmission patterns primarily used for downlink data transmission and/or one or more uplink-centric transmission patterns primarily used for uplink data transmission. .

FIG. 2 shows a diagram of a downlink centric transmission pattern and an uplink centric transmission pattern. As shown in FIG. 2, the downlink centered transmission pattern 210 includes a downlink transmission portion 211 for transmitting downlink control information, a downlink transmission portion 212 for transmitting downlink data, a guard period (GP: guard period) portion 213, and an uplink transmission portion 214 (eg, Physical Uplink Control Channel (PUCCH)) for transmitting uplink control information. In the transmission pattern 210, a downlink transmission portion 212 for transmitting downlink data is longer than the other portions and is therefore referred to as a downlink centric transmission pattern.

Similar to downlink-centric transmission pattern 210, downlink-centric transmission pattern 220 includes a downlink transmission portion 221, a guard period (GP) portion 222, and an uplink transmission portion 223 for transmitting downlink data. The main difference between downlink centric transmission patterns 210 and 220 is that transmission pattern 220 does not include a portion for carrying downlink control information.

The uplink centered transmission pattern 230 includes a downlink transmission portion 231 for transmitting downlink control information, a GP portion 232, an uplink transmission portion 233 for transmitting uplink data, and an uplink transmission portion 233 for transmitting uplink control information. uplink transmission portion 234 (eg, PUCCH). In the transmission pattern 230, an uplink transmission portion 233 for transmitting uplink data is longer than other portions, so the transmission pattern 230 is called an uplink centric transmission pattern.

Similar to the uplink-centric transmission pattern 230, the uplink-centric transmission pattern 240 includes a downlink transmission portion 241 for transmitting downlink control information, a GP portion 242, and an uplink transmission portion for transmitting uplink data. 243. The main difference between uplink centric transmission patterns 230 and 240 is that transmission pattern 240 does not include a portion for transmitting uplink control information.

The terms "transmission" or "communication" include transmission or communication of control information and/or data, unless otherwise stated, and the term "signal" as used herein may be used to transmit control information and/or data. understood to include

Conventionally, eMBB has relatively loose requirements on user plane delay, eg 4ms, for UL/DL transmission. In contrast, URLLC requires a relatively tight user plane delay, eg, 0.5 seconds, for UL/DL transmissions. In the example of FIG. 1, the eMBB UE 121 is scheduled in multiple subframes and the URLLLC UE 122 is scheduled in one subframe to meet stringent user plane delay requirements. If eMBB UE 121 and URLLC UE 122 were to be multiplexed in the frequency domain, some resources would be wasted, which is undesirable.

To solve this problem, embodiments of the present disclosure propose the solutions discussed below to reduce the waste of time or frequency resources. Several exemplary embodiments of the present disclosure are described below with reference to the drawings. FIG. 3 shows a flowchart of a method 300 for signal transmission according to an embodiment of the present disclosure. Method 300 may be performed by BS 110, terminal 121, terminal 122, or other suitable device.

Method 300 begins at block 310, where a target transmission pattern is determined from a candidate set of candidate transmission patterns. Each of the candidate transmission patterns includes a DL transmission portion and/or a UL transmission portion, and the candidate transmission patterns differ from each other with respect to the duration of the respective DL transmission pattern and/or UL transmission pattern.

According to embodiments of the present disclosure, method 300 may be performed by a network device, such as BS 110 of FIG. In such embodiments, the BS 110 does not require each of the terminals served by the network equipment (e.g., UEs 121 and 122) to have the same target transmission pattern for each of the terminals. , may determine the target transmission pattern from the set of candidate transmission patterns.

In some implementations, method 300 may be performed by a terminal device, eg, UE121 or UE122. In such embodiments, UE 121 or 122 may determine a target transmission pattern suitable for transmitting signals to and from BS 110 .

In some embodiments, one or more candidate transmission patterns may further include a GP portion. The GP part may be between the DL transmission part and the UL transmission part.

In some embodiments, the target transmission pattern may be determined based on a feedback request requesting feedback on DL transmissions sent in the target transmission pattern. The target transmission pattern may include a processing period (PP) for the terminal to process data received in DL transmissions. The processing period can be implemented in the target transmission pattern in various ways to meet feedback requirements.

In one embodiment, the target transmission pattern is applicable in a Time Division Duplexing (TDD) transmission mode. In TDD mode, the length of the GP part may be extended by the processing period and consequently the length of the DL transmission part may be reduced by the processing period.

In another embodiment, the length of the DL transmission portion is reduced by the processing period, but the length of the GP portion is unaffected. In such cases, there is no signal transmission during processing. In other words, the processing period is "blank".

In some cases, the signal transmitted in the DL transmission portion is a feedback information or feedback signal (e.g., Acknowledgment (ACK)/ Negative Acknowledgments (NACKs) are reduced so that they can be prepared and transmitted in the same subframe.

In another embodiment, the target transmission pattern is applicable in Frequency Division Duplexing (FDD). In FDD mode, the length of the DL transmission part can be reduced by the processing period.

In the above embodiments, the processing period may be used for further DL transmissions of data, control information, or reference signals (RS). Feedback for further DL transmissions (eg ACK/NACK) need not meet the above feedback requirements. In one embodiment, feedback for further DL transmissions may be sent after the target transmission pattern. For example, if one transmission pattern corresponds to one subframe in the time domain, feedback may be sent after the subframe corresponding to the target transmission pattern.

In some embodiments, the target transmission pattern may be determined based on a scheduling request requesting scheduling information for UL transmissions to be sent in the target transmission pattern. The target transmission pattern may include a processing period for the terminal to prepare data to be sent in the UL transmission. The processing period can be implemented in the target transmission pattern in various ways to meet scheduling requirements.

In one embodiment, the target transmission pattern is applicable in TDD transmission mode. In TDD mode, the length of the GP portion is extended by the processing period so that the length of the UL transmission portion can be reduced by the processing period.

In other embodiments, the length of the UL transmission portion can be reduced by the processing period, but the length of the GO portion is not affected. In such cases, there is no signal during processing. In other words, the processing period is "blank". In another embodiment, the target transmission pattern is applicable in FDD transmission mode. In FDD mode, the length of the UL transmission portion can be reduced by the processing period.

In the above embodiments, the processing period may be used for further UL transmissions of data or reference signals. Schedule information for further UL transmissions may already be sent before the target transmission pattern, eg in previous subframes.

In other embodiments, the length of the DL transmission portion may be reduced by the processing period, but the length of the UL transmission portion is not affected. In such cases, there is no signal during processing. In other words, the processing period is "blank". In some scenarios, the scheduling signal for the UL transmission portion transmitted in the DL transmission portion is reduced so that the corresponding UL transmission signal can be prepared and transmitted in the same subframe.

In the above embodiments, the processing period may be used for further DL transmissions of control signals (eg, Channel State Information (CSI) feedback), data, or reference signals.

According to embodiments of the present disclosure, the target transmission pattern includes an indication to indicate itself. In one embodiment, the indication is control information sent in the DL transmission part and/or the UL transmission part, e.g., Downlink Control Information (DCI), Uplink Control Information (UCI) ), etc. In some embodiments, the indication is during the DL transmission portion and/or the UL transmission portion, during the GP portion between the DL transmission portion and the UL transmission portion, and during the DL transmission portion or the UL transmission portion. It may indicate one or more of whether there is

In other embodiments, the indication of the target transmission pattern may be included in predetermined time-frequency resources. Also, the resources may be common to all UEs and may not be limited to resources defined in the target transmission pattern.

Referring to FIG. 3, at block 320, communication is performed between the network device and the terminal device using the target transmission pattern. In some embodiments, if a network device (eg, BS 110) determines a target transmission pattern for a terminal device (eg, UE 122) at block 310, the network device communicates with UE 122 by using the target transmission pattern. obtain. For example, BS 110 may transmit data to or receive data from UE 122 according to a target transmission pattern.

Alternatively, if the terminal (eg, UE 122) determined the target transmission pattern at block 310, the terminal may communicate with BS 110 using the target transmission pattern. For example, UE 122 may transmit data to or receive data from BS 110 according to a target transmission pattern.

According to embodiments of the present disclosure, there may be different GP or PP period configurations for downlink centric transmission patterns, so that downlink data transmission may be completed early and sufficient processing time may be obtained. In some embodiments, long GPs may be used for ACK/NACK reporting for corresponding downlink data transmissions in the same transmission pattern, and short GPs may be used for ACK/NACK reporting for corresponding downlink data transmissions in the same transmission pattern. May be used when there is no NACK report.

Alternatively, in some embodiments, the processing period can be used to transmit downlink data when ACK/NACK needs to be reported in the same transmission pattern. In one embodiment, the processing period may be kept empty. In alternative embodiments, the processing period may be used to schedule additional data for the same or other terminals. In this case, ACK/NACK for further data may be reported in the same transmission pattern or in subsequent transmission patterns. As a further alternative, the processing period may be used to transmit downlink RS for measurements, downlink data demodulation, beam tracking, and so on.

Feedback information, such as ACK/NACK, to the terminal may be implemented in various ways. In some embodiments, in the kth transmission pattern, no additional data processing time is required because the data can be processed during the k transmission pattern. In this case the GP is short and can be kept the same for all transmission patterns.

Alternatively, in some embodiments feedback information for downlink data needs to be sent in the same transmission pattern as downlink data. A GP of a transmission pattern may include a processing period that defines the data processing time for an entire transmission block. In this case, GP can be set to a relatively long period.

Some embodiments related to downlink centric transmission patterns are described below. In the following embodiments, transmission patterns may be referred to as subframes. It is understood that this is used for illustration and not limitation. Those skilled in the art will understand that transmission patterns define resources in the time domain and/or the frequency domain.

FIG. 4 shows a diagram 400 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure. In the example of FIG. 4, the eMBB terminal is referenced as UE1 and the URLLLC terminal is referenced as UE2. For UE2, two transmission patterns are shown and they are identical. The DL transmission portion 421 is for transmitting DL data and is described as a short downlink region containing few symbols. In one embodiment, the number of symbols in DL transmission portion 421 may be indicated by DCI, which is included in another DL transmission portion 424 for transmitting control information.

GPs 422 and 423 may be set to long durations if rapid ACK/NACK feedback is required in the same transmission pattern, so that GPs can reduce processing time, transmission advance (TA) for uplink transmissions, and ), and the sum of transition times. So UE2 has enough time to process the downlink data and can transmit the uplink within the TA.

For UE1, GP may be set as a short period. For UE1 with multiple transmission pattern scheduling, it is possible that there is no processing time (just keep empty for the TA period aligned to UE2), so the short GP can be used for PUCCH transmission in this transmission pattern. Can be used when there is no There is a shorter empty period 411 with continuous scheduling to match the time advance for UE1's PUCCH transmission. If multiple subframe scheduling is employed, without DCI, UE1 may monitor DCI only in the first subframe and skip the control region in subsequent subframes (consecutive downlink data transmissions). If there is only compact DCI, UE1 may monitor normal DCI in the first subframe and compact DCI in subsequent subframes. In some alternative embodiments, UE1 may monitor other DCIs (some reserved DCI regions).

FIG. 5 shows a diagram 500 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure. In the embodiment of FIG. 5, UE1 has a short GP period when PUCCH is not needed, and ACK/NACK is fed back from the UE to the BS in subsequent subframes, eg, the (n+k)th subframe. Here, n represents the subframe number of the subframe in which DL data transmission is completed, k represents the subframe number after n, and k≧1. For UE2, long GP period is used and ACK/NACK is fed back in the same subframe.

FIG. 6 shows a diagram 600 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure. In the embodiment of Figure 6, a long GP period is used for UE2. A flexible GP period is used for UE1 depending on whether or not the feedback is in the same subframe. UE1 may feed back ACK/NACK in the last subframe for scheduling and GP may differ together in different subframe numbers, eg depending on TB size.

FIG. 7 shows a diagram 700 of transmission patterns for UE1 and UE2 in terms of TDD and processing periods, according to an embodiment of the present disclosure. In the example of Figure 7, UE2 needs to report ACK/NACK in the same subframe, GP covers the transmission advance for uplink, and the sum of transition times (same for all UEs) and the processing time PP is provided for downlink data processing. For UE1, there may be no PP in case of continuous scheduling.

FIG. 8 shows a diagram 800 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 8, it can be seen that there is no need for GP for TA for FDD configuration where UL and DL transmissions are in different frequency bands when UE2 needs to report ACK/NACK in the same subframe. be. For UE2, a processing period may be required for data processing. For UE1, no processing period is required for continuous scheduling.

FIG. 9 shows a diagram 900 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 9, UE2 needs PP for data processing and ACK/NACK feedback is the same subframe. For UE1, PP is not required for continuous scheduling and ACK/NACK is the (n+k)th subframe.

FIG. 10 shows a diagram 1000 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 10, UE2 has a long duration PP. For UE1, a flexible PP period may be used for different subframe numbers (related to TB size). UE1 sends ACK/NACK feedback in the last subframe of scheduling.

FIG. 11 shows a diagram 1100 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 11, UE2 has PP and ACK/NACK feedback in the same subframe. For UE1, if PUCCH is not needed, PP is not needed, ACK/NACK feedback (n+k)th subframe.

FIG. 12 shows a diagram 1200 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 12, UE2 has a long duration PP. For UE1, a flexible PP period can be used with different subframe numbers (related to TB size). UE1 sends ACK/NACK feedback in the last subframe of scheduling.

FIG. 13 shows a diagram 1300 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 13, if UE2 needs to report ACK/NACK in the same subframe, GP can cover the sum of transmission advance for uplink and transition time (same for all UEs), PP is used to process downlink data. On the other hand, for UE1, no PP is required for continuous scheduling.

FIG. 14 shows a diagram 1400 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of Figure 14, the PP may also be used for scheduling other UEs, but the ACK/NACK during this period should be delayed to the (n+k)th subframe.

FIG. 15 shows a diagram 1500 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 15, there may be one or more DL transmission parts for UE2. For some of the DL transmission parts, a subframe has enough time for data processing, so ACK/NACK can be fed back in the same subframe. For other DL transmission portions, ACK/NACK may be reported in subsequent subframes, eg, the (n+k)th subframe. In the transmission pattern shown in FIG. 15, each DL transmission portion may contain DCI. Alternatively, the DCI can be included at the start and there is a partial indication bit in the DCI.

FIG. 16 shows a diagram 1600 of transmission patterns for UE1 and UE2 with respect to TDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 16, PP may be used for some other transmissions, eg, downlink RS for measurements, beam tracking, demodulation, and so on. The RS may be used for CSI measurements, downlink data demodulation reference, beam tracking, and so on. The downlink RS may be semi-statically configured or triggered in the downlink DCI. The period for RS transmission may guarantee sufficient time for downlink data processing, so ACK/NACK may be fed back in the same subframe.

FIG. 17 shows a diagram 1700 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of Figure 17, the duration of PP covers downlink data processing if UE2 needs to report ACK/NACK in the same subframe. For UE1, no PP is required for continuous scheduling.

FIG. 18 shows a diagram 1800 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 18, the period of PP can be used for scheduling other UEs, but the ACK/NACK of the used period is delayed by n+k (k≧1) subframes, i.e. the (n+k)th subframe. must be.

FIG. 19 shows a diagram 1900 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 19, there may be one or more DL transmission parts for UE2. For some DL transmission parts, a subframe has enough time for data processing, so ACK/NACK can be fed back in the same subframe. For other DL transmission portions, ACK/NACK may be reported in subsequent subframes, eg, the (n+k)th subframe. In the transmission pattern shown in FIG. 15, each DL transmission portion may contain DCI. Alternatively, the DCI can be included at the start and there is a partial indication bit in the DCI.

FIG. 20 shows a diagram 2000 of transmission patterns for UE1 and UE2 for FDD and processing periods, according to an embodiment of the present disclosure. In the example of FIG. 20, PP may be used for some other transmissions, such as downlink RS for measurements, beam tracking, demodulation, and so on. The RS may be used for CSI measurements, downlink data demodulation reference, beam tracking, and so on. The downlink RS may be semi-statically configured or triggered in the downlink DCI. The period for RS transmission may guarantee sufficient time for downlink data processing, so ACK/NACK may be fed back in the same subframe.

According to embodiments of the present disclosure, there may be different GP or PP period configurations for uplink centric transmission patterns. By delaying the UL transmission or by reducing the period for downlink control signals, the UE2 can have enough time to prepare the data for UL transmission.

In some embodiments, a long GP may be used for uplink data transmission, e.g. Physical Uplink Shared Channel (PUSCH) scheduling in the same transmission pattern, and a short GP may be used without PUSCH. , or n+k (k≧1) subframes.

Alternatively, in some embodiments, the transmission pattern may have a processing period, or PP, if uplink data is scheduled in the same subframe. The preparation period can be set in several ways. In one embodiment, the PP may be kept empty. In other embodiments, PP may be used to schedule other data for the same or other UEs. For example, the PP can be used to transmit uplink data, and the scheduling is the previous subframe, eg, nk (k≧1) subframes (also referred to as the nkth subframe). obtain. In another embodiment, PP may be used to transmit downlink data.

In yet another embodiment, PP may be used to transmit RS. For example, a PP can be used to transmit several uplink RSs, eg for measurements, uplink data demodulation, beam tracking, and so on. The RS period can be used for data preparation because the time to prepare RS is generally shorter than data. In other embodiments, the PP may be used to transmit several downlink RSs, such as for measurements, downlink data demodulation, and beam tracking.

In those embodiments, different UEs may have different PUSCH transmission durations. In one example, at the (n+k)th subframe, no additional data preparation time is required because the data can be ready for k subframes. In this case, the GP is kept short and the same in all subframes. In other embodiments, the GP of a subframe should contain the data preparation time of the entire transport block, so the GP may have a relatively long duration.

In the following some embodiments related to uplink centric data transmission patterns are described. FIG. 21 shows a diagram 2100 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure. In the embodiment of FIG. 21, long duration GP can be used if fast data transmission is required in the same subframe for UE2. GP may cover the sum of preparation time, transmission advance for uplink, and transition time. UE2's uplink transmission may be delayed due to sufficient time for data processing, and the GP occupies some uplink area.

For UE1, in one embodiment where multi-subframe scheduling is adopted (hereafter referred to as case A), no preparation time may be required in some subframes. In another embodiment with data transmission in n+k (k≧1) subframes (hereafter referred to as case B), no preparation time may be required.

FIG. 22 shows a diagram 2200 of transmission patterns for UE1 and UE2 for TDD and different GP periods, according to an embodiment of the present disclosure. In the embodiment of FIG. 22, long term GP may be used for UE2 and flexible GP may be used for UE1. For UE1, the uplink data transmission may be in the same subframe as the scheduling, and the GPs may differ together at different subframe numbers (related to TB size). For example, in the same subframe for both uplink scheduling and corresponding uplink data transmission, GP is longer for uplink data processing. Also, in other subframes with uplink data transmission only, the GP is shorter due to the TA for uplink data transmission.

FIG. 23 shows a diagram 2300 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of FIG. 23, if UE2 needs to transmit uplink data in the same subframe, GP covers the sum of transmission advance for uplink and transition time (same for all UEs). can. In an embodiment, PP is used for UE2 uplink data processing. On the other hand, for UE1, PP is not used during multi-subframe scheduling or n+k scheduling.

FIG. 24 shows a diagram 2400 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of FIG. 24, if UE2 needs to transmit uplink data in the same subframe, GP can cover the sum of transmission advance for uplink and transition time (same for all UEs). . In an embodiment, PP is used for UE2 uplink data processing. On the other hand, for UE1, PP is not used during multi-subframe scheduling or n+k scheduling. In the embodiment of FIG. 24, PP and GP have different positions than in the embodiment of FIG.

FIG. 25 shows a diagram 2500 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of FIG. 25, a long GP period may be used for UE2 and a flexible GP period may be used for UE1. For UE1, the uplink data transmission may be in the same subframe as the scheduling, and the PPs may differ together at different subframe numbers (related to TB size). For example, PP is required in the same subframe for both uplink scheduling and corresponding uplink data transmission. Also, PP is not required in other subframes for uplink data transfer only.

FIG. 26 shows a diagram 2600 of transmission patterns for UE1 and UE2 for TDD and GP, according to an embodiment of the present disclosure. In the embodiment of FIG. 26, a long duration GP can be used for UE2 if fast data transmission is required in the same subframe. GP may cover the sum of preparation time, transmission advance for uplink, and transition time. DCI for UE2 may be completed early with sufficient time for data processing.

For UE1, short duration GP may be used. In one embodiment described for case A, for UE1 scheduled in multiple subframes, no preparation time may be required in some subframes (empty for TA period for uplink transmission). only kept). In one embodiment described for case B, no preparation time may be required for UE1 transmitting data in the n+kth (k≧1) subframe.

FIG. 27 shows a diagram 2700 of transmission patterns for UE1 and UE2 for TDD and GP, according to an embodiment of the present disclosure. In the example of FIG. 27, a long duration GP may be used for UE2.

UE1 may have flexible control regions for different scheduling, eg different DCI formats or different DCI symbols. GPs can be different together for different subframe numbers (related to TB size). Additionally, a GP may occupy several downlink periods.

FIG. 28 shows a diagram 2800 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the example of FIG. 28, if UE2 transmits uplink data in the same subframe, GP may cover the sum of transmission advance and transition time for uplink (same for all UEs). PP may be used for uplink data processing. A PP may occupy a downlink region. For UE1, no PP is required for multiple subframe scheduling or n+k subframe scheduling.

FIG. 29 shows a diagram 2900 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 29, a long duration PP may be used for UE2.

UE1 may have flexible control regions for different scheduling, eg different DCI formats or different DCI symbols. The PPs can be different together for different subframe numbers (related to TB size). Additionally, a PP may occupy several downlink periods.

FIG. 30 shows a diagram 3000 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 30, PP may be present for uplink data processing if UE2 needs to transmit uplink data in the same subframe. For UE1, no PP is required for multiple subframe scheduling or n+k subframe scheduling.

FIG. 31 shows a diagram 3100 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 31, a long duration PP may be used for UE2. For UE1, a flexible duration PP may be used. Uplink data transmission of UE1 may be in the same subframe due to scheduling. PP can be different with different subframe numbers (related to TB size).

FIG. 32 shows a diagram 3200 of transmission patterns for UE1 and UE2 for FDD and PP, in accordance with an embodiment of the present disclosure. In the embodiment of FIG. 32, if UE2 transmits uplink data in the same subframe, GP may cover the sum of transmission advance and transition time for uplink (same for all UEs). There may be a PP for uplink data processing. A PP may occupy a downlink region. On the other hand, for UE1, no PP is required for multiple subframe scheduling or n+k subframe scheduling.

FIG. 33 shows a diagram 3300 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 33, a long duration PP may be used for UE2.

UE1 may have flexible control regions for different scheduling, eg different DCI formats or different DCI symbols. PP can be different with different subframe numbers (related to TB size). Additionally, a PP may occupy several downlink periods.

FIG. 34 shows a diagram 3400 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 34, the duration of the PP may be used for other scheduling. In one embodiment described for Case 2, Alt1, PP may be used for other uplink scheduling and UL grant is nk (k≧1) subframes for sufficient lead time. obtain. In one embodiment described for Case 2, Alt2, if a PP occupies a downlink period, the PP may be used for other downlink scheduling.

FIG. 35 shows a diagram 3500 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 35, there may be multiple UL transmission parts for UE2. In one or more UL transmission portions, the UL grant can be the same subframe (with sufficient time for data processing). For other UL transmission parts, the UL grant can be the (n−k)th (k≧1).

FIG. 36 shows a diagram 3600 of transmission patterns for UE1 and UE2 for TDD and PP, according to an embodiment of the present disclosure. In the embodiment of FIG. 36, the period of PP may be used for RS transmission. The RS can be periodically or aperiodically triggered or semi-statically configured. In one embodiment described for case 3, Alt1, the duration of the PP may be used for uplink RS transmission if the PP occupies the uplink region, for uplink demodulation, and/or measurement, etc. can be used for In one embodiment described for case 3, Alt2, if the PP occupies the downlink region, the duration of the PP may be used for the downlink RS, used for measurements, beam tracking, demodulation, etc. obtain.

FIG. 37 shows a diagram 3700 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure. In the embodiment of FIG. 37, the period of PP can be used for other scheduling. In one embodiment described for case 2, Alt1, the period of the PP may be used for other UL scheduling, and the UL grant is granted in the (nk)th subframe (k ≧1). In one embodiment described for case 2, Alt2, if a PP occupies a downlink period, the period of the PP can be used for other downlink scheduling.

FIG. 38 shows a diagram 3800 of transmission patterns for UE1 and UE2 for FDD and PP, according to an embodiment of the present disclosure. In the embodiment of Figure 38, there may be multiple UL transmission portions. Over the UL transmission portion, the UL grant can be the same subframe (with sufficient time for data processing). For other UL transmission portions, the UL grant may be the (nk)-th subframe (k≧1).

FIG. 39 shows a diagram 3900 of transmission patterns for UE1 and UE2 for FDD and PP, in accordance with an embodiment of the present disclosure. In the embodiment of FIG. 39, the period of PP may be used for RS transmission. The RS can be periodically or aperiodically triggered, or semi-statically configured. In one embodiment described for case 3, Alt1, the duration of the PP may be used for uplink RS transmission if the PP occupies the uplink region, for uplink demodulation, and/or measurement, etc. can be used for In one embodiment described for case 3, Alt2, the duration of PP may be used for downlink RS if PP occupies the downlink region, may be used for measurements, beam tracking, demodulation, etc. .

FIG. 40 shows a diagram 4000 of transmission patterns according to an embodiment of the present disclosure. In the illustrated transmission pattern, if there is a PUCCH transmission for ACK/NACK, it can have a structure of “DMRS+PUCCH”. Stated another way, a demodulation reference signal (DMRS) may be transmitted before the PUCCH signal. For DMRS transmission, the time period may also be used for downlink data processing for the corresponding ACK/NACK.

FIG. 41 shows a diagram 4100 of transmission patterns in accordance with an embodiment of the present disclosure. In the illustrated transmission pattern, if PUSCH is scheduled, it may have a structure of “DMRS+PUSCH”. Stated another way, DMRS may be sent before the PUCCH signal. The DMRS transmission period may be used for uplink data preparation.

FIG. 42 shows a schematic diagram of an apparatus 4200 according to one embodiment of the present disclosure. According to embodiments of the present disclosure, apparatus 4200 may be implemented in network equipment such as BS 110, UE 121 or 122, or appropriate equipment in a communication system.

As shown in FIG. 42, an apparatus 4200 can target from a set of candidate transmission patterns each including a DL transmission portion and/or a UL transmission portion and different from each other for each DL transmission portion and/or UL transmission portion. It has a controller 4210 configured to determine a transmission pattern and a transceiver 4220 to effect communication between the network equipment and the terminal equipment by using the target transmission pattern.

In one embodiment, one or more of the candidate transmission patterns may further include a guard period (GP) portion between the DL transmission portion and the UL transmission portion.

In one embodiment, the target transmission pattern may be determined based on a feedback request requesting feedback on the DL transmissions transmitted in the target transmission pattern, the target transmission pattern indicating that the terminal uses data received in the DL transmission. It may include a treatment period for treating.

In one embodiment, the target transmission pattern may be applicable to the TDD transmission mode, the length of the guard period (GP) may be extended by the processing period, or the length of the DL transmission portion may be reduced by the processing period. .

In one embodiment, the target transmission pattern may be applicable for FDD transmission mode and the length of the DL transmission portion may be reduced by the processing period.

In one embodiment, the processing period may be used for further DL transmissions of data, control information or reference signals, and feedback for further DL transmissions is sent after the target transmission pattern.

In one embodiment, the target transmission pattern may be determined based on a schedule request requesting schedule information about which UL transmissions are to be transmitted in the target transmission pattern, the target transmission pattern being determined by the terminal device being transmitted in the UL transmissions. may include a processing period to prepare data for

In one embodiment, the target transmission pattern may be applicable to the TDD transmission mode, the GP length may be extended by the processing period, or the UL transmission portion length may be reduced by the processing period.

In one embodiment, the target transmission pattern may be applicable for FDD transmission mode and the length of the UL transmission portion may be reduced by the processing period.

In one embodiment, the processing period may be used for further UL transmissions of data or reference signals, and schedule information for the further UL transmissions may be sent prior to the target transmission pattern.

In one embodiment, the controller further comprises, at the network device, for each of the terminals served by the network device, without requiring that the target transmission pattern be the same for each of the terminal devices. It is configured to determine a target transmission pattern from the set of transmission patterns.

In one embodiment, the target transmission pattern may include an indication in the control information sent in the DL transmission portion and/or the UL transmission portion, the indication being the DL transmission portion and/or the UL transmission portion. , the duration of the GP between the DL and UL transmission parts, and whether there is communication in the DL or UL transmission parts.

Embodiments of the present disclosure also provide apparatus implemented in network equipment or terminal equipment. A device has a set of candidate transmission patterns each including a downlink (DL) transmission portion and/or an uplink (UL) transmission portion, and the duration of each DL and/or UL transmission portion is different from each other. and means for communicating between the network equipment and the terminal equipment by using the target transmission pattern.

Apparatus 4200 may each be implemented by any suitable technique, either now known or later developed. Also, the single device shown in FIG. 42 may alternatively be implemented separately in multiple devices, and multiple separate devices may be implemented in a single device. The scope of the disclosure is not limited in these respects.

Apparatus 4200 may be configured to implement functionality such as described with reference to FIGS. Accordingly, features described with respect to method 300 may be applied to corresponding components of apparatus 4200. FIG. Further, components of apparatus 4200 may be embodied in hardware, software, firmware, and/or any combination thereof. For example, the components of device 4200 are each implemented by a circuit, processor, or any other suitable device. Those skilled in the art will appreciate that the foregoing examples are for illustration only and not for limitation.

In some embodiments of the present disclosure, device 4200 may have at least one processor. The at least one processor suitable for use with embodiments of the present disclosure may include, by way of example, both general and special purpose processors now known or developed in the future. Device 4200 may have at least one memory. The at least one memory may include, for example, semiconductor memory devices such as RAM, ROM, EPROM, EEPROM and flash memory devices. At least one memory may be used to store a program of computer-executable instructions. Programs may be written in any high-level and/or low-level compilable or interpretable programming language. According to an embodiment, the computer-executable instructions, in conjunction with at least one processor, may be configured to cause apparatus 4200 to at least perform the operations according to method 300 discussed above.

Based on the above description, a person of ordinary skill in the art should understand that the present disclosure can be embodied in an apparatus, method, or computer program product. In general, various illustrative embodiments may be implemented in hardware or special purpose circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware and other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although this disclosure is limited thereto. not. Although various aspects of the exemplary embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or other pictorial representations, these blocks, apparatus, and descriptions are described herein. Systems, techniques, or methods are implemented by, as non-limiting examples, hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, other computing devices, or some combination thereof is well understood.

The various blocks shown in FIG. 3 may be represented as method steps and/or operations resulting from operation of the computer program code and/or as a plurality of combinatorial logic circuitry configured to perform the associated functions. can be regarded as At least some of the exemplary embodiments of the present disclosure may be implemented in various components such as integrated circuit chips and modules, and exemplary embodiments of the present disclosure may include exemplary embodiments of the present disclosure. A device embodied as an integrated circuit, FPGA, or ASIC configured to operate in accordance with

Although this specification contains many specific implementation details, these should not be construed as limitations on the scope of the disclosure or what may be claimed, rather than the specific implementation of the particular disclosure. It should be construed as a description of features that may be unique to the form. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Further, features are described above as working in particular combinations, and even if originally claimed as such, one or more features from the claimed combination may in some cases be cut from the combination. and claimed combinations may be directed to subcombinations or variations of subcombinations.

Similarly, although acts have been drawn in the figures in a particular order, it is believed that such acts may be performed in the specific order or order shown, or all shown, to achieve desirable results. should not be understood to require that the actions of Multitasking and parallel processing may be advantageous in certain situations. Furthermore, the separation of various system components in the above-described embodiments should not be understood to require such separation in all embodiments, and the program components and systems described are generally of a single unit. be understood to be integrated into one software product or packaged into multiple software products.

Various modifications and adaptations to the above-described exemplary embodiments of the present disclosure will become apparent to those skilled in the art from the foregoing description when read in conjunction with the accompanying drawings. Any and all modifications will still fall within the scope of the non-limiting exemplary embodiments of this disclosure. Moreover, other embodiments of the disclosure described herein will come to mind to those skilled in the art to which these embodiments of the disclosure pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Will.

It is therefore understood that the embodiments of the present disclosure should not be limited to the particular embodiments disclosed, but that modifications and other embodiments are intended to be included within the scope of the appended claims. . Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims (2)

A method performed by an apparatus comprising:
determining a target transmission pattern comprising a downlink (DL) transmission portion and/or an uplink (UL) transmission portion from a set of candidate transmission patterns;
receiving downlink control information (DCI) including an indication that there is no transmission for the device on at least a portion of the DL transmission portion and/or the UL transmission portion;
communicating with a network device based on the target transmission pattern and the DCI. A method implemented by a network device, comprising:
sending information about the target transmission pattern to the terminal device;
Downlink control information (DCI: downlink control information) to the terminal device,
communicating with the terminal based on the target transmission pattern and the DCI.

Images