First terminal device, network device, and method implemented thereby

Abstract

To provide a solution for conducting communications to reduce waste of time and / or frequency resources.SOLUTION: A method applied to a communication system determines a target transmission pattern from a set of candidate transmission patterns including a downlink (DL) transmission portion and / or an uplink (UL) transmission portion, and in which the durations of the respective DL transmission portions and / or UL transmission portions are different from each other, and performs communication between a network device and a terminal device using the target transmission pattern.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to communication technologies. In particular, embodiments of the present disclosure relate to methods and apparatuses for performing communication.

Background Art

[0002] With the development of communication technologies, the frequency range up to 100 GHz has been studied for the purpose of a single technical framework to address as many usage scenarios as possible. Several requirements and deployment scenarios have been defined, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine-type communications (mMTC).

[0003] Generally, eMBB has strict requirements for high peak data rates, but has relatively loose requirements for user plane latency, such as 4 ms for uplink (UL) and downlink (DL) transmissions. In contrast, URLLC requires ultra-low latency and high reliability, and for example, requires a user plane latency of 0.5 ms for UL and DL transmissions.

[0004] When a terminal device that requests an eMBB service (also referred to as an "eMBB terminal") and another terminal that requests a URLLC service (also referred to as a "URLLC terminal") are multiplexed in the same transmission pattern such as a subframe, the user plane latency of eMBB may be several times that of URLLC. For this reason, an eMBB terminal may be scheduled in multiple subframes, and a URLLC UE may be scheduled in one subframe to meet more stringent user plane latency requirements.

[0005] Conventionally, the periods of UL transmission and DL transmission have been configured across the entire bandwidth. Therefore, when an eMBB terminal device and a URLLC terminal device are multiplexed in the frequency domain, some resources may be wasted.

[0006] Therefore, there is a need for a signal transmission mechanism to suppress waste of time and / or frequency resources.

Summary of the Invention

Problems to be Solved by the Invention

[0007] The present disclosure proposes a solution for performing communication in order to suppress waste of time and / or frequency resources.

Means for Solving the Problems

[0008] According to a first aspect of an embodiment of the present disclosure, an embodiment of the present disclosure provides a method implemented by a device. The 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 have different durations for their respective DL transmission portions and / or UL transmission portions. Then, communication between the network device and the terminal device is performed using the target transmission pattern.

[0009] According to a second aspect of an embodiment of the present disclosure, an embodiment of the present disclosure provides a device for performing communication. The device includes a controller configured to determine a target transmission pattern from a set of candidate transmission patterns, where each of the candidate transmission patterns includes a DL transmission portion and / or a UL transmission portion, and the candidate transmission patterns have different durations for their respective DL transmission portions and / or UL transmission portions, and a transceiver configured to perform communication between the network device and the terminal device by using the target transmission pattern.

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

Brief Description of the Drawings

[0011] Embodiments of the present disclosure are provided by way of illustration, and their advantages will be described in more detail below with reference to the accompanying drawings.

[0012]

Figure 1

[0013]

Figure 2

[0014]

Figure 3

[0015]

Figure 4

[0016]

Figure 5

[0017]

Figure 6

[0018]

Figure 7

[0019]

Figure 8

[0020]

Figure 9

[0021]

Figure 10

[0022]

Figure 11

[0023]

Figure 12

[0024]

Figure 13

[0025]

Figure 14

[0026]

Figure 15

[0027]

Figure 16

[0028]

Figure 17

[0029]

Figure 18

[0030]

Figure 19

[0031]

Figure 20

[0032]

Figure 21

[0033]

Figure 22

[0034]

Figure 23

[0035]

Figure 24

[0036]

Figure 25

[0037]

Figure 26

[0038]

Figure 27

[0039]

Figure 28

[0040]

Figure 29

[0041]

Figure 30

[0042]

Figure 31

[0043]

Figure 32

[0044]

Figure 33

[0045]

Figure 34

[0046]

Figure 35

[0047]

Figure 36

[0048]

Figure 37

[0049]

Figure 38

[0050]

Figure 39

[0051]

Figure 40

[0052]

Figure 41

[0053]

Figure 42

[0054] In the drawings, the same or similar reference numerals indicate the same or similar components.

Embodiments for Carrying Out the Invention

[0055] The subject matter described in this specification is discussed with reference to several exemplary embodiments. These embodiments are discussed only to enable those skilled in the art to better understand and practice the subject matter described in this specification, and are not intended to present any limitation on the scope of the subject matter.

[0056] The terms used in this specification are for the sole purpose of describing particular embodiments and are not intended to limit the exemplary embodiments. As used in this specification, 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", when used in this specification, specify the presence of the described features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0057] Also, note that in some alternative embodiments, the functions / operations shown may be performed in an order different from that shown in the figures. For example, two functions or operations shown consecutively may actually be performed simultaneously, depending on the functions / operations involved, or in the reverse order.

[0058] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard such as LTE-A (LTE-Advanced), WCDMA (Wideband Code Division Multiple Access), and HSPA (High-Speed Packet Access). Further, the communication between a terminal device and a network device in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to the 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 protocol known currently or developed in the future.

[0059] Embodiments of the present disclosure can be applied in various communication systems. Considering the rapid development of communication, there will naturally be future types of communication technologies and systems in which the present disclosure can be implemented. The scope of the present disclosure should not be regarded as limited only to the aforementioned systems.

[0060] The term "network device" includes, but is not limited to, a base station (BS), a gateway, a management entity, and other suitable devices in a communication system. The term "base station" or "BS" can represent, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), a relay, or a low-power node such as a femto or pico.

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

[0062] Some exemplary embodiments of the present disclosure will be described below with reference to the drawings. First, FIG. 1 showing a schematic diagram of a communication system 100 according to an embodiment of the present disclosure is referred to.

[0063] In communication system 100, a network device (hereinafter also referred to as BS) 110 communicates with two terminal devices (hereinafter also referred to as UE) 121 and 122 by using the same or different transmission patterns. BS110 provides an eMBB service to UE121, and thus UE121 may be referred to as an eMBB UE. BS110 provides a URLLC service to UE122, and thus UE122 may be referred to as a URLLC UE.

[0064] The term "transmission pattern" refers to settings regarding resources in the time domain and / or the frequency domain. For example, a transmission pattern may correspond to one or more subframes in the time domain, or a number of symbols, and may also correspond to 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 is different with respect to the duration of each DL transmission portion and / or UL transmission portion. In an embodiment of the present disclosure, a transmission pattern can include a set of candidate transmission patterns and a target transmission pattern, and 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-centered transmission patterns mainly used for downlink data transmission and / or one or more uplink-centered transmission patterns mainly used for uplink data transmission.

[0065] Figure 2 shows diagrams of a downlink-centered transmission pattern and an uplink-centered transmission pattern. As shown in Figure 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) portion 213, and an uplink transmission portion 214 (e.g., a Physical Uplink Control Channel (PUCCH)) for transmitting uplink control information. In the transmission pattern 210, the downlink transmission portion 212 for transmitting downlink data is longer than the other portions, and thus it is called a downlink-centered transmission pattern.

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

[0067] 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 234 (e.g., PUCCH) for transmitting uplink control information. In the transmission pattern 230, the uplink transmission portion 233 for transmitting uplink data is longer than other portions, and thus, the transmission pattern 230 is called an uplink-centered transmission pattern.

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

[0069] The term "transmission" or "communication" includes the transmission or communication of control information and / or data unless stated otherwise, and the term "signal" as used herein is understood to include control information and / or data.

[0070] Conventionally, eMBB has a relatively loose requirement, e.g., 4 ms, for user plane latency for UL / DL transmission. In contrast, URLLC requires a relatively strict user plane latency, e.g., 0.5 seconds, for UL / DL transmission. In the example of FIG. 1, the eMBB UE 121 is scheduled in a plurality of subframes, and the URLLC UE 122 is scheduled in one subframe to meet the strict user plane latency requirement. If the eMBB UE 121 and the URLLC UE 122 are multiplexed in the frequency domain, some resources will be wasted, which is not desirable.

[0071] To solve this problem, embodiments of the present disclosure propose the solutions discussed below to reduce the waste of time or frequency resources. Some 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. The method 300 can be executed by the BS 110, the terminal device 121, the terminal device 122, or other suitable devices.

[0072] The method 300 starts from block 310, in which a target transmission pattern is determined from a set of candidate transmission pattern candidates. Each of the candidate transmission patterns includes a DL transmission portion and / or a UL transmission portion, and the candidate transmission patterns are different from each other with respect to the periods of their respective DL transmission patterns and / or UL transmission patterns.

[0073] According to embodiments of the present disclosure, the method 300 can be executed by a network device, such as the BS 110 in FIG. 1. In such an embodiment, the BS 110 can determine a target transmission pattern from a set of candidate transmission patterns without requiring that the target transmission patterns for each of the terminal devices (e.g., UE 121 and 122) served by the network device be the same.

[0074] In some implementations, the method 300 can be executed by a terminal device, such as the UE 121 or the UE 122. In such an embodiment, the UE 121 or 122 can determine a target transmission pattern suitable for the transmission signal between the UE 121 or 122 and the BS 110.

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

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

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

[0078] In another embodiment, the length of the DL transmission part is reduced by the processing period, but the length of the GP part is not affected. In such a case, there is no signal transmission during the processing period. In other words, the processing period is "blank".

[0079] In some cases, the signal transmitted in the DL transmission part is reduced so that the transmitted signal can be decoded and the feedback information or feedback signal (e.g., Acknowledgement (ACK) / Negative Acknowledgement (NACK)) for the transmitted signal can be prepared and transmitted in the same subframe.

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

[0081] In the above embodiment, the processing period can be used for further DL transmission of data, control information, or a reference signal (RS). Feedback (e.g., ACK / NACK) for the further DL transmission does not need to meet the above feedback requirements. In one embodiment, the feedback for the further DL transmission can be transmitted after the target transmission pattern. For example, if one transmission pattern corresponds to one subframe in the time domain, the feedback can be transmitted after the subframe corresponding to the target transmission pattern.

[0082] In some embodiments, the target transmission pattern can be determined based on a scheduling request that requests scheduling information for UL transmission to be transmitted in the target transmission pattern. The target transmission pattern can include a processing period for the terminal device to prepare data to be transmitted in UL transmission. The processing period can be implemented in the target transmission pattern in various ways to meet the scheduling requirements.

[0083] In one embodiment, the target transmission pattern is applicable in the TDD transmission mode. In the TDD mode, the length of the GP portion can be extended by the processing period, and as a result, the length of the UL transmission portion can be reduced by the processing period.

[0084] 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 a case, there is no signal during the processing period. In other words, the processing period is "blank". In other embodiments, the target transmission pattern is applicable in the FDD transmission mode. In the FDD mode, the length of the UL transmission portion can be reduced by the processing period.

[0085] In the above embodiment, the processing period can be used for further UL transmission of data or a reference signal. Schedule information for the further UL transmission can be transmitted before the target transmission pattern, for example, already transmitted in the previous subframe.

[0086] In other embodiments, the length of the DL transmission portion can be reduced by the processing period, while the length of the UL transmission portion is not affected. In such a case, there is no signal during the processing period. In other words, the processing period is "blank". In some scenarios, the scheduling signal of 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.

[0087] In the above embodiment, the processing period can be used for further DL transmission of control signals (such as channel state information (CSI) feedback), data, or reference signals.

[0088] According to embodiments of the present disclosure, the target transmission pattern includes an indication for indicating itself. In one embodiment, the indication can be included in control information transmitted in the DL transmission portion and / or the UL transmission portion, such as downlink control information (DCI), uplink control information (UCI), etc. In some embodiments, the indication can indicate one or more of the period of the DL transmission portion and / or the UL transmission portion, the period of the GP portion between the DL transmission portion and the UL transmission portion, and whether there is communication in the DL transmission portion or the UL transmission portion.

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

[0090] Referring to FIG. 3, at block 320, communication is performed between the network device and the terminal device by using the target transmission pattern. In some embodiments, when the network device (e.g., BS110) determines the target transmission pattern for the terminal device (e.g., UE122) at block 310, the network device can communicate with UE122 by using the target transmission pattern. For example, BS110 can transmit data to UE122 or receive data from UE122 according to the target transmission pattern.

[0091] Alternatively, when the terminal device (e.g., UE122) determines the target transmission pattern at block 310, the terminal device can perform communication with BS110 by using the target transmission pattern. For example, UE122 can transmit data to BS110 or receive data from BS110 according to the target transmission pattern.

[0092] According to embodiments of the present disclosure, there can be different GP or PP period configurations for the downlink-centered transmission pattern, and as a result, downlink data transmission can be completed early and sufficient processing time can be obtained. In some embodiments, the long GP can be used for the ACK / NACK report for the corresponding downlink data transmission in the same transmission pattern, and the short GP can be used when there is no ACK / NACK report for the corresponding downlink data transmission in the same transmission pattern.

[0093] Alternatively, in some embodiments, when ACK / NACK needs to be reported in the same transmission pattern, the processing period can be used to transmit downlink data. In one embodiment, the processing period can be kept empty. In an alternative embodiment, the processing period can be used to schedule further data for the same or other terminal devices. In this case, ACK / NACK for the further data can be reported in the same transmission pattern or in a subsequent transmission pattern. As a further alternative, the processing period can be used to transmit downlink RS for measurement, downlink data demodulation, beam tracking, etc.

[0094] For the terminal device, feedback information such as ACK / NACK can be implemented in various ways. In some embodiments, in the k-th transmission pattern, since the data can be processed during the period of the k-th transmission pattern, no additional data processing time is required. In this case, the GP is short and can be kept the same in all transmission patterns.

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

[0096] Some embodiments related to the downlink-centered transmission pattern are described below. In the following embodiments, the transmission pattern can be called a subframe. This is understood to be used for illustration purposes only and not by way of limitation. Those skilled in the art will understand that the transmission pattern defines resources in the time domain and / or the frequency domain.

[0097] Figure 4 shows a transmission pattern diagram 400 for UE1 and UE2 regarding TDD and different GP periods according to an embodiment of the present disclosure. In the example of Figure 4, the eMBB terminal device is referred to as UE1, and the URLLC terminal device is referred to as UE2. For UE2, two transmission patterns are shown, and they are the same. The DL transmission part 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 the DL transmission part 421 may be indicated by DCI, which is included in another DL transmission part 424 for transmitting control information.

[0098] If rapid ACK / NACK feedback is required in the same transmission pattern, GP422 and 423 may be set for a long period. As a result, the GP can cover the sum of the processing time, the transmission advance (TA) for uplink transmission, and the transition time. Therefore, UE2 has sufficient time to process the downlink data and can transmit the uplink within the TA.

[0099] For UE1, the GP can be set as a short period. For UE1 with multiple transmission pattern schedulings, it is possible that there is no processing time (only keep empty for the TA period adapted to UE2). Therefore, the short GP can be used when there is no PUCCH transmission in this transmission pattern. There is a shorter empty period 411 with continuous scheduling to match the time advance for PUCCH transmission of UE1. When multiple subframe schedulings are adopted, without DCI, UE1 can monitor DCI only in the first subframe and skip the control region in subsequent subframes (continuous downlink data transmission). If there is only compact DCI, UE1 can monitor normal DCI in the first subframe and compact DCI in subsequent subframes. In some alternative embodiments, UE1 can monitor other DCI (some reserved DCI regions).

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

[0101] FIG. 6 shows a transmission pattern diagram 600 for UE1 and UE2 regarding TDD and different GP periods according to an embodiment of the present disclosure. In the embodiment of FIG. 6, a long GP period is used for UE2. Depending on whether the feedback is in the same subframe or not, a flexible GP period is used for UE1. UE1 may feed back ACK / NACK in the last subframe for scheduling, and the GP may be different for different subframe numbers, for example, depending on the TB size.

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

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

[0104] FIG. 9 shows a transmission pattern diagram 900 for UE1 and UE2 regarding TDD and processing period according to an embodiment of the present disclosure. In the example of FIG. 9, UE2 requires a PP for data processing, and the ACK / NACK feedback is in the same subframe. For UE1, in the case of continuous scheduling, a PP is not required, and the ACK / NACK is in the (n + k)-th subframe.

[0105] FIG. 10 shows a transmission pattern diagram 1000 for UE1 and UE2 regarding TDD and processing period according to an embodiment of the present disclosure. In the example of FIG. 10, UE2 has a long PP. For UE1, a flexible PP period can be used for different subframe numbers (related to the TB size). UE1 transmits the ACK / NACK feedback in the last subframe of the scheduling.

[0106] FIG. 11 shows a transmission pattern diagram 1100 for UE1 and UE2 regarding FDD and processing period according to an embodiment of the present disclosure. In the example of FIG. 11, UE2 has a PP, and the ACK / NACK feedback is in the same subframe. For UE1, when a PUCCH is not required, a PP is not required, and the ACK / NACK feedback is in the (n + k)-th subframe.

[0107] FIG. 12 shows a transmission pattern diagram 1200 for UE1 and UE2 regarding FDD and processing periods according to an embodiment of the present disclosure. In the example of FIG. 12, UE2 has a long period of PP. For UE1, a flexible PP period can use different subframe numbers (related to the TB size). UE1 transmits ACK / NACK feedback in the last subframe of scheduling.

[0108] FIG. 13 shows a transmission pattern diagram 1300 for UE1 and UE2 regarding 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 the transmission advance for the uplink and the transition time (the same for all UEs), and PP is used to process downlink data. For UE1 on the other hand, in the case of continuous scheduling, PP is not required.

[0109] FIG. 14 shows a transmission pattern diagram 1400 for UE1 and UE2 regarding TDD and processing periods according to an embodiment of the present disclosure. In the example of FIG. 14, PP can also be used for the scheduling of other UEs, but the ACK / NACK for this period should be delayed to the (n + k)-th subframe.

[0110] FIG. 15 shows a transmission pattern diagram 1500 for UE1 and UE2 regarding TDD and processing periods according to an embodiment of the present disclosure. In the example of FIG. 15, for UE2, there may be one or more DL transmission parts. For some of the DL transmission parts, the subframe has sufficient time for data processing, so ACK / NACK can be fed back in the same subframe. For other DL transmission parts, ACK / NACK can be reported in a subsequent subframe, e.g., the (n + k)-th subframe. In the transmission pattern shown in FIG. 15, each DL transmission part may include DCI. Alternatively, DCI can be included at the start, and there are partial indication bits in the DCI.

[0111] FIG. 16 shows a transmission pattern diagram 1600 for UE1 and UE2 regarding TDD and processing periods according to an embodiment of the present disclosure. In the example of FIG. 16, PP can be used for some other transmissions, such as downlink RS for measurement, beam tracking, demodulation, etc. RS can be used for CSI measurement, downlink data demodulation reference, and beam tracking, etc. The downlink RS may be configured semi-statically or triggered in the downlink DCI. The period for RS transmission can ensure sufficient time for downlink data processing, so ACK / NACK can be fed back in the same subframe.

[0112] FIG. 17 shows a transmission pattern diagram 1700 for UE1 and UE2 regarding FDD and processing periods according to an embodiment of the present disclosure. In the example of FIG. 17, if UE2 needs to report ACK / NACK in the same subframe, the period of PP covers the downlink data processing. Regarding UE1, PP is not required in the case of continuous scheduling.

[0113] FIG. 18 shows a transmission pattern diagram 1800 for UE1 and UE2 regarding 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 for the used period is delayed by n + k (k ≧ 1) subframes, that is, it needs to be in the (n + k)-th subframe.

[0114] FIG. 19 shows a diagram 1900 of the transmission pattern for UE1 and UE2 regarding FDD and the processing period according to an embodiment of the present disclosure. In the example of FIG. 19, for UE2, there may be one or more DL transmission portions. For some DL transmission portions, the subframe has sufficient time for data processing, and thus ACK / NACK can be fed back in the same subframe. For other DL transmission portions, ACK / NACK can be reported in a subsequent subframe, for example, the (n + k)-th subframe. In the transmission pattern shown in FIG. 15, each DL transmission portion may include DCI. Alternatively, DCI may be included at the start, and there are partial indication bits in the DCI.

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

[0116] According to an embodiment of the present disclosure, for the uplink-centered transmission pattern, there may be different GP or PP period configurations. By delaying the UL transmission or reducing the period for the downlink control signal, UE2 can have sufficient time to prepare data for the UL transmission.

[0117] In some embodiments, the long GP can be used for uplink data transmission, e.g., for physical uplink shared channel (PUSCH) scheduling in the same transmission pattern, and the short GP can be used when there is no PUSCH or for scheduling in the n + k (k ≥ 1) subframes.

[0118] Alternatively, in some embodiments, if the uplink data is scheduled in the same subframe, the transmission pattern can have a processing period, i.e., PP. The preparation period can be set in several ways. In one embodiment, the PP can be kept empty. In other embodiments, the PP can be used for scheduling other data for the same or other UEs. For example, the PP can be used to transmit uplink data, and the scheduling can be in the previous subframe, e.g., the (n - k) (k ≥ 1)th subframe (also called the n - k subframe). In another embodiment, the PP can be used to transmit downlink data.

[0119] In yet another embodiment, the PP can be used to transmit RS. For example, the PP can be used to transmit some uplink RS for, e.g., measurement, uplink data demodulation, and beam tracking. Since the time for preparing the RS is generally shorter than that for data, the RS period can be used for data preparation. In other embodiments, the PP can be used to transmit some downlink RS for, e.g., measurement, downlink data demodulation, and beam tracking.

[0120] In those embodiments, different UEs may have different PUSCH transmission periods. In one example, in the (n + k)-th subframe, since data can be prepared within the period of k subframes, no additional data preparation time is required. In this case, the GP is short and remains the same in all subframes. In other embodiments, the GP of the subframe needs to include the data preparation time of the entire transmission block, and thus the GP may have a relatively long period.

[0121] Some embodiments related to the uplink-centered data transmission pattern are described below. FIG. 21 shows a diagram 2100 of the transmission patterns for UE1 and UE2 related to TDD and different GP periods according to an embodiment of the present disclosure. In the embodiment of FIG. 21, for UE2, if rapid data transmission is required in the same subframe, a long-period GP can be used. The GP can cover the sum of the preparation time, the transmission advance for the uplink, and the transition time. The uplink transmission of UE2 can be delayed for sufficient data processing time, and the GP occupies some uplink regions.

[0122] For UE1, in one embodiment (hereinafter referred to as Case A) where multi-subframe scheduling is adopted, in some subframes, no preparation time may be required. In other embodiments (hereinafter referred to as Case B) where data is transmitted in the (n + k) (k ≧ 1) subframes, no preparation time may be required.

[0123] Figure 22 shows diagram 2200 of the transmission pattern for UE1 and UE2 regarding TDD and different GP periods according to an embodiment of the present disclosure. In the embodiment of Figure 22, a long GP is used for UE2, and a flexible GP can be used for UE1. For UE1, the uplink data transmission can be in the same subframe as the scheduling, and the GP can be different for different subframe numbers (related to the TB size). For example, in the same subframe for both uplink scheduling and the corresponding uplink data transmission, the GP is longer for uplink data processing. Also, in other subframes for only uplink data transmission, the GP is shorter for the TA for uplink data transmission.

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

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

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

[0127] FIG. 26 shows a diagram 2600 of a transmission pattern for UE1 and UE2 related to TDD and GP according to an embodiment of the present disclosure. In the embodiment of FIG. 26, if rapid data transmission is required in the same subframe, a long GP period can be used for UE2. The GP can cover the sum of the preparation time, the transmission advance for the uplink, and the transition time. The DCI for UE2 can be completed early for sufficient data processing time.

[0128] For UE1, a short GP period can be used. In one embodiment described for case A, for UE1 scheduled in multiple subframes, the preparation time may not be required in some subframes (only an empty is kept for the TA period for the uplink transmission). In one embodiment described for case B, for UE1 transmitting data in the (n + k)-th subframe (k ≧ 1), the preparation time may not be required.

[0129] FIG. 27 shows a diagram 2700 of a transmission pattern for UE1 and UE2 related to TDD and GP according to an embodiment of the present disclosure. In the example of FIG. 27, a long GP period can be used for UE2.

[0130] UE1 may have a control region that is flexible for different schedulings, for example, different DCI formats or different DCI symbols. The GP may be different for different subframe numbers (related to the TB size). In addition, the GP may occupy some downlink periods.

[0131] Figure 28 shows Diagram 2800 of the transmission patterns for UE1 and UE2 regarding TDD and PP according to an embodiment of the present disclosure. In the example of Figure 28, if UE2 transmits uplink data in the same subframe, the GP may cover the sum of the transmission advance for the uplink and the transition time (the same for all UEs). The PP may be used for uplink data processing. The PP may occupy the downlink region. For UE1, in the case of multi-subframe scheduling or n + k subframe scheduling, the PP is not required.

[0132] Figure 29 shows Diagram 2900 of the transmission patterns for UE1 and UE2 regarding TDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 29, a long period of PP may be used for UE2.

[0133] UE1 may have a control region that is flexible for different schedulings, for example, different DCI formats or different DCI symbols. The PP may be different for different subframe numbers (related to the TB size). In addition, the PP may occupy some downlink periods.

[0134] Figure 30 shows Diagram 3000 of the transmission patterns for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 30, if UE2 needs to transmit uplink data in the same subframe, the PP may exist for uplink data processing. For UE1, in the case of multi-subframe scheduling or n + k subframe scheduling, the PP is not required.

[0135] Figure 31 shows diagram 3100 of the transmission pattern for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 31, a long-term PP can be used for UE2. For UE1, a flexible-duration PP can be used. The uplink data transmission of UE1 can be in the same subframe by scheduling. The PP can be different with different subframe numbers (related to the TB size).

[0136] Figure 32 shows diagram 3200 of the transmission pattern for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 32, if UE2 transmits uplink data in the same subframe, the GP can cover the sum of the transmission advance for the uplink and the transition time (the same for all UEs). There can be a PP for uplink data processing. The PP can occupy the downlink region. For UE1 on the other hand, in the case of multiple subframe scheduling or n + k subframe scheduling, a PP is not required.

[0137] Figure 33 shows diagram 3300 of the transmission pattern for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 33, a long-term PP can be used for UE2.

[0138] UE1 can have a flexible control region for different scheduling, for example, different DCI formats or different DCI symbols. The PP can be different with different subframe numbers (related to the TB size). In addition, the PP can occupy some downlink periods.

[0139] Figure 34 shows diagram 3400 of the transmission pattern for UE1 and UE2 regarding TDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 34, the period of PP can be used for other scheduling. In one embodiment described for Case 2, Alt1, PP can be used for other uplink scheduling, and the UL grant can be n-k (k≧1) subframes for a sufficient preparation period. In one embodiment described for Case 2, Alt2, if PP occupies the downlink period, PP can be used for other downlink scheduling.

[0140] Figure 35 shows diagram 3500 of the transmission pattern for UE1 and UE2 regarding TDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 35, for UE2, there can be multiple UL transmission parts. In one or more UL transmission parts, the UL grant can be in the same subframe (with sufficient time for data processing). Regarding other UL transmission parts, the UL grant can be the (n-k)-th (k≧1).

[0141] Figure 36 shows diagram 3600 of the transmission pattern for UE1 and UE2 regarding TDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 36, the period of PP can be used for RS transmission. RS can be triggered periodically or aperiodically, or configured semi-statically. In one embodiment described for Case 3, Alt1, if PP occupies the uplink region, the period of PP can be used for uplink RS transmission and can be used for uplink demodulation and / or measurement, etc. In one embodiment described for Case 3, Alt2, if PP occupies the downlink region, the period of PP can be used for downlink RS and can be used for measurement, beam tracking, and demodulation, etc.

[0142] Figure 37 shows Diagram 3700 of the transmission patterns for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 37, the period of PP can be used for other scheduling. In one embodiment described for Case 2, Alt1, the period of PP can be used for other UL scheduling, and the UL grant can be the (n - k)-th subframe (k ≥ 1) for sufficient preparation time. In one embodiment described for Case 2, Alt2, when PP occupies the downlink period, the period of PP can be used for other downlink scheduling.

[0143] Figure 38 shows Diagram 3800 of the transmission patterns for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 38, there can be multiple UL transmission parts. In the above UL transmission part, the UL grant can be in the same subframe (with sufficient time for data processing). Regarding other UL transmission parts, the UL grant can be the (n - k)-th subframe (k ≥ 1).

[0144] Figure 39 shows Diagram 3900 of the transmission patterns for UE1 and UE2 regarding FDD and PP according to an embodiment of the present disclosure. In the embodiment of Figure 39, the period of PP can be used for RS transmission. RS can be triggered periodically or aperiodically, or configured semi-statically. In one embodiment described for Case 3, Alt1, when PP occupies the uplink region, the period of PP can be used for uplink RS transmission and can be used for uplink demodulation and / or measurement, etc. In one embodiment described for Case 3, Alt2, when PP occupies the downlink region, the period of PP can be used for downlink RS and can be used for measurement, beam tracking, and demodulation, etc.

[0145] FIG. 40 shows Diagram 4000 of a transmission pattern according to an embodiment of the present disclosure. In the illustrated transmission pattern, if there is PUCCH transmission for ACK / NACK, it may have a structure of "DMRS + PUCCH". In other words, a demodulation reference signal (DMRS) may be transmitted before the PUCCH signal. Regarding DMRS transmission, the period may also be used for downlink data processing for the corresponding ACK / NACK.

[0146] FIG. 41 shows Diagram 4100 of a transmission pattern according to an embodiment of the present disclosure. In the illustrated transmission pattern, if PUSCH is scheduled, it may have a structure of "DMRS + PUSCH". In other words, DMRS may be transmitted before the PUCCH signal. The DMRS transmission period may be used for uplink data preparation.

[0147] FIG. 42 shows a schematic diagram of apparatus 4200 according to an embodiment of the present disclosure. According to an embodiment of the present disclosure, apparatus 4200 may be implemented in a network device such as BS110, UE121 or 122, or a suitable device in a communication system.

[0148] As shown in FIG. 42, apparatus 4200 includes a controller 4210 configured to determine a target transmission pattern from a set of candidate transmission patterns that are different from each other for each DL transmission part and / or UL transmission part, each of which includes a DL transmission part and / or an UL transmission part, and a transceiver 4220 configured to perform communication between the network device and the terminal device by using the target transmission pattern.

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

[0150] In one embodiment, the target transmission pattern may be determined based on a feedback request that requests feedback regarding DL transmission to be transmitted in the target transmission pattern, and the target transmission pattern may include a processing period for the terminal device to process data received in the DL transmission.

[0151] 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 only by the processing period, or the length of the DL transmission part may be reduced only by the processing period.

[0152] In one embodiment, the target transmission pattern may be applicable to the FDD transmission mode, and the length of the DL transmission part may be reduced only by the processing period.

[0153] In one embodiment, the processing period may be used for further DL transmission of data, control information, or a reference signal, and feedback regarding the further DL transmission is transmitted after the target transmission pattern.

[0154] In one embodiment, the target transmission pattern may be determined based on a scheduling request that requests scheduling information regarding UL transmission to be transmitted in the target transmission pattern, and the target transmission pattern may include a processing period for the terminal device to prepare data to be transmitted in the UL transmission.

[0155] In one embodiment, the target transmission pattern may be applicable to the TDD transmission mode, the length of the GP may be extended only by the processing period, or the length of the UL transmission part may be reduced only by the processing period.

[0156] In one embodiment, the target transmission pattern may be applicable to the FDD transmission mode, and the length of the UL transmission part may be reduced only by the processing period.

[0157] In one embodiment, the processing period may be used for further UL transmission of data or a reference signal, and scheduling information regarding the further UL transmission may be transmitted before the target transmission pattern.

[0158] In one embodiment, the controller is further configured to determine a target transmission pattern from a set of candidate transmission patterns in the network device without requiring that the target transmission pattern be the same for each of the terminal devices served by the network device.

[0159] In one embodiment, the target transmission pattern may include an indication in the control information transmitted in the DL transmission portion and / or the UL transmission portion, and the indication indicates one or more of the duration of the DL transmission portion and / or the UL transmission portion, the duration of the GP between the DL transmission portion and the UL transmission portion, and whether there is communication in the DL transmission portion or the UL transmission portion.

[0160] Embodiments of the present disclosure also provide an apparatus implemented in a network device or a terminal device. The apparatus may each include a downlink (DL) transmission portion and / or an uplink (UL) transmission portion, and means for determining a target transmission pattern from a set of candidate transmission patterns in which the durations of the respective DL transmission portions and / or UL transmission portions are different from each other, and means for performing communication between the network device and the terminal device by using the target transmission pattern.

[0161] Apparatus 4200 may be implemented respectively by any suitable technique, whether currently known or developed in the future. Also, the single apparatus shown in FIG. 42 may instead be implemented separately in a plurality of apparatuses, or a plurality of separate apparatuses may be implemented in a single apparatus. The scope of the present disclosure is not limited in these respects.

[0162] The device 4200 may be configured to implement the functions as described with reference to FIGS. 3 to 41. Accordingly, the features described with respect to the method 300 can be applied to the corresponding components of the device 4200. Further, the components of the device 4200 may be embodied in hardware, software, firmware, and / or any combination thereof. For example, the components of the device 4200 may be implemented by circuits, processors, or any other suitable devices respectively. Those skilled in the art will understand that the foregoing examples are for illustrative purposes only and not for limitation.

[0163] In some embodiments of the present disclosure, the device 4200 may have at least one processor. At least one processor suitable for use with the embodiments of the present disclosure may include, by way of example, both general and special purpose processors that are already known or developed in the future. The 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. The at least one memory may be used to store a program of computer-executable instructions. The program may be described in any high-level and / or low-level compilable or interpretable programming language. According to an embodiment, the computer-executable instructions may be configured to cause the device 4200, together with at least one processor, to perform at least the operations according to the method 300 discussed above.

[0164] Based on the above description, those skilled in the art will understand that the present disclosure can be embodied in an apparatus, a method, or a computer program product. Generally, various exemplary embodiments can be implemented in hardware, or special-purpose circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, a microprocessor, or other computer device, but the present disclosure is not limited thereto. Various aspects of the exemplary embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using other pictorial representations, and these blocks, devices, systems, techniques, or methods described herein may, by way of non-limiting example, be executed by hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, other computing devices, or some combination thereof.

[0165] The various blocks shown in FIG. 3 can be regarded as method steps, and / or operations resulting from the operation of computer program code, and / or a plurality of coupled logic circuit elements configured to perform related functions. At least some of the exemplary embodiments of the present disclosure can be implemented with various components such as integrated circuit chips and modules, and the exemplary embodiments of the present disclosure can be realized by an apparatus embodied as an integrated circuit, an FPGA, or an ASIC configured to operate in accordance with the exemplary embodiments of the present disclosure.

[0166] 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, but rather as descriptions of features that may be specific to particular embodiments of the specific disclosure. The specific features described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments, or in any suitable sub-combination. Furthermore, even if features have been described above as acting in a particular combination and were initially claimed as such, one or more features from the claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of the sub-combination.

[0167] Similarly, although operations are depicted in the drawings in a particular order, it should not be understood that such operations need to be performed in the particular order or sequence shown, or that all of the operations shown need to be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Further, the separation of various system components in the foregoing embodiments should not be understood as requiring such separation in all embodiments, and the program components and systems described are generally understood to be integrated into a single software product or packaged into multiple software products.

[0168] Various modifications and adaptations to the foregoing exemplary embodiments of the present disclosure will be apparent to those skilled in the art from the foregoing description when read in conjunction with the accompanying drawings. All such modifications still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure. Further, other embodiments of the disclosure described herein will occur to those skilled in the art who benefit from the teachings presented in the foregoing description and related drawings.

[0169] Accordingly, it is to be understood that the embodiments of the present disclosure should not be limited to the specific embodiments disclosed, and that modified and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are used herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

Claim 1 A method performed by a first terminal device, comprising: determining a target transmission pattern having a downlink (DL) portion and / or an uplink (UL) portion and a flexible portion; when the flexible portion indicates downlink transmission, receiving downlink transmission in the flexible portion; when the flexible portion indicates uplink transmission, transmitting uplink transmission in the flexible portion; when it is indicated that there is no downlink transmission and no uplink transmission in the flexible portion, not performing transmission in the flexible portion. Claim 2 Receiving downlink control information (DCI) including an indication indicating that there is no transmission to the first terminal device on a resource that is part of the target transmission pattern obtained by removing symbols indicated as uplinks, where the resource is indicated for transmission by a second terminal device, and a delay requirement for transmission to the second terminal device is higher than a delay requirement for transmission to the first terminal device; Performing communication with a network device based on the DCI. The method according to claim 1. Claim 3 The method according to claim 1 or 2, further comprising receiving configuration information having the target transmission pattern. Claim 4 A method performed by a network device, comprising: transmitting configuration information indicating a target transmission pattern having a downlink (DL) portion and / or an uplink (UL) portion and a flexible portion to a first terminal device; when the flexible portion indicates downlink transmission, performing downlink transmission in the flexible portion; when the flexible portion indicates uplink transmission, receiving uplink transmission in the flexible portion; when it is indicated that there is no downlink transmission and no uplink transmission in the flexible portion, not performing transmission in the flexible portion. Claim 5 Transmit downlink control information (DCI) including an indication indicating that there is no transmission to the first terminal device on a resource that is part of the target transmission pattern obtained by removing symbols indicated as the uplink, where the resource is indicated for transmission by a second terminal device, and a delay requirement for transmission to the second terminal device is higher than a delay requirement for transmission to the first terminal device, according to the method of claim 1.

6. A first terminal device, comprising: means for determining a target transmission pattern having a downlink (DL) portion and / or an uplink (UL) portion and a flexible portion; means for receiving downlink transmission in the flexible portion when the flexible portion indicates downlink transmission, transmitting uplink transmission in the flexible portion when the flexible portion indicates uplink transmission, and not performing transmission in the flexible portion when it is indicated that there is no downlink transmission and uplink transmission in the flexible portion;

7. means for receiving downlink control information (DCI) including an indication indicating that there is no transmission to the first terminal device on a resource that is part of the target transmission pattern obtained by removing symbols indicated as the uplink, where the resource is indicated for transmission by a second terminal device, and a delay requirement for transmission to the second terminal device is higher than a delay requirement for transmission to the first terminal device; The first terminal device according to claim 6, further comprising means for communicating with a network device based on the DCI.

8. A network device, comprising: means for transmitting configuration information indicating a target transmission pattern having a downlink (DL) portion and / or an uplink (UL) portion and a flexible portion to a first terminal device; When the flexible part indicates downlink transmission, downlink transmission is performed in the flexible part; when the flexible part indicates uplink transmission, uplink transmission is received in the flexible part; and when it is shown that there is no downlink transmission and uplink transmission in the flexible part, means for not performing transmission in the flexible part are provided in the network device.

9. Means for transmitting downlink control information (DCI: downlink control information) including an indication indicating that there is no transmission to the first terminal device on a resource that is a part of the target transmission pattern obtained by removing symbols indicated as the uplink, wherein the resource is indicated for transmission by a second terminal device, and a delay requirement for transmission to the second terminal device is higher than a delay requirement for transmission to the first terminal device, the network device according to claim 8, further comprising the means.

Images