Terminal device, network device, and method performed by the terminal device

Abstract

A method, apparatus, and computer-readable medium for communication during data transmission and reception are disclosed. The communication method includes receiving, at a terminal device, resource allocation information from a network device indicating a slot offset value associated with transmission of uplink data or reception of downlink data, the slot offset value being selected from a range for scheduling slots of a carrier frequency (510), and performing the transmission or reception based on the slot offset value. The method supports a wide frequency bandwidth, allowing more uplink or downlink slots to be scheduled, and improving channel utilization (520).

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, apparatus, and computer storage media for communication during data transmission and reception. [Background technology]

[0002] Recent discussions on New Radio (NR) technologies above 52.6 GHz have agreed to utilize Frequency Range 2 (FR2) design as much as possible to support NR operation from 52.6 GHz to 71 GHz, considering both licensed and unlicensed operation. Currently, there are no new technologies for operating in this frequency band. Numerology (numerolog ies) In this situation, each new In numerology Adapted time-scale related aspects, such as bandwidth portion (BWP) and beam switching time, hybrid automatic repeat request (HARQ) scheduling, user equipment (UE) processing, physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), sounding reference signal (SRS) and channel state information (CSI) preparation and calculation times, also need to be considered. Summary of the Invention [Problem to be solved by the invention]

[0003] Generally, embodiments of the present disclosure provide a method, apparatus, and computer storage medium for communication during data transmission and reception. [Means for solving the problem]

[0004] In a first aspect, a communication method is provided, comprising: receiving, in a terminal device, uplink resource allocation information from a network device, the uplink resource allocation information indicating a first slot offset value associated with transmission of uplink data; and transmitting the uplink data based on the first slot offset value, the first slot offset value being selected from a first range from a first start value to a first end value.

[0005] In a second aspect, a communication method is provided, comprising: receiving, in a terminal device, downlink resource allocation information from a network device, the downlink resource allocation information indicating a third slot offset value associated with reception of downlink data; and receiving the downlink data based on the third slot offset value, the third slot offset value being selected from a third range from a third start value to a third end value.

[0006] In a third aspect, a communication method is provided, the method including: determining, in a network device, uplink resource allocation information indicating a first slot offset value associated with transmission of uplink data from a terminal device; and transmitting the uplink resource allocation information to the terminal device, the first slot offset value being selected from a first range from a first start value to a first end value.

[0007] In a fourth aspect, a communication method is provided, the method including: determining, in a network device, downlink resource allocation information indicating a third slot offset value associated with reception of downlink data by a terminal device; and transmitting the downlink resource allocation information to the terminal device, wherein the third slot offset value is selected from a third range from a third start value to a third end value.

[0008] In a fifth aspect, there is provided a terminal device, the terminal device including a processor and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform a method according to either the first or second aspect of the present disclosure.

[0009] In a sixth aspect, there is provided a network device, the network device including: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause a terminal device to perform a method according to either the third or fourth aspect of the present disclosure.

[0010] In a seventh aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to either the first or second aspect of the present disclosure.

[0011] In an eighth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to either the third or fourth aspect of the present disclosure.

[0012] Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0013] The above and other objects, features and advantageous effects of the present disclosure will become more apparent from the following detailed description of some embodiments of the present disclosure in the drawings.

[0014] [Figure 1] 1 illustrates an exemplary communication network in which some embodiments of the present disclosure may be implemented.

[0015] [Figure 2]1 illustrates a schematic diagram of uplink resource scheduling according to some embodiments of the present disclosure.

[0016] [Figure 3] 1 illustrates a schematic diagram of downlink resource scheduling according to some embodiments of the present disclosure.

[0017] [Figure 4] 1 illustrates a schematic diagram of a process for transmitting and receiving data according to an embodiment of the present disclosure.

[0018] [Figure 5] 1 illustrates an exemplary method of communication implemented in a terminal device during an uplink data transmission period, in accordance with some embodiments of the present disclosure.

[0019] [Figure 6] 10 illustrates another exemplary method of communication implemented in a terminal device during an uplink data transmission period, in accordance with some embodiments of the present disclosure.

[0020] [Figure 7] 1 illustrates an exemplary method of communication implemented in a terminal device during downlink data reception, according to some embodiments of the present disclosure.

[0021] [Figure 8] 10 illustrates another exemplary method of communication implemented in a terminal device during downlink data reception, in accordance with some embodiments of the present disclosure.

[0022] [Figure 9] 1 illustrates an exemplary method of communication implemented in a network device during an uplink resource allocation period, according to some embodiments of the present disclosure.

[0023] [Figure 10] 1 illustrates an example method of communication implemented in a network device during a downlink resource allocation period, according to some embodiments of the present disclosure.

[0024] [Figure 11] FIG. 1 is a schematic block diagram of an apparatus suitable for practicing embodiments of the present disclosure.

[0025] In all figures, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0026] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are merely for illustrative purposes, to assist those skilled in the art in understanding and practicing the present disclosure, and are not intended to imply any limitations on the scope of the present disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] As used herein, the term "terminal equipment" refers to any device capable of wireless or wired communication. Examples of terminal equipment include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, mobile phones, smartphones, personal digital assistants (PDAs), handheld computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, in-vehicle devices for V2X communications (where X represents pedestrian, vehicle, or infrastructure / network), image capture devices such as digital cameras, gaming devices, music storage and playback devices, or Internet tools that enable wireless or wired Internet access or browsing. The term "terminal equipment" can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. The term "network equipment" refers to equipment capable of providing or managing a cell or coverage area over which terminal equipment can communicate. Examples of network devices include, but are not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a transmit / receive point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), and low power nodes such as femto nodes, pico nodes, etc.

[0029] In one embodiment, a terminal device may connect with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other may be a secondary node. The first network device and the second network device may use different RATs. In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information regarding the different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device to the terminal device directly or via the first network device. In one embodiment, information regarding the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Furthermore, information regarding the reconfiguration of the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

[0030] When used in context, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly dictates otherwise. The term "comprises" and variations thereof are intended to be open-ended, meaning "including, but not limited to." The term "based on" is intended to mean "based at least in part on." The terms "one embodiment" and "embodiment" are intended to mean "at least one embodiment." The term "another embodiment" is intended to mean "at least one other embodiment." The terms "first," "second," etc. may refer to different or the same object. Other definitions may be included, both explicitly and implicitly, in the following description.

[0031] In some instances, values, processes, or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate choices among multiple functional options used, and that such choices are not necessarily better, lesser, more expensive, or more preferred than other choices.

[0032] FIG. 1 illustrates a schematic diagram of an exemplary communication network 100 in which embodiments of the present disclosure may be implemented. As shown in FIG. 1, communication network 100 includes network devices 110 and terminal devices 120 that are serviced by network devices 110. It should be understood that the number of devices in FIG. 1 is shown for illustrative purposes and does not imply any limitations on the present disclosure. Network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing the present disclosure.

[0033] As shown in FIG. 1 , network device 110 may communicate with terminal device 120 via a downlink channel, such as a wireless communication downlink channel, and terminal device 120 may communicate with network device 110 via an uplink channel, such as a wireless communication uplink channel. For example, network device 110 may transmit resource scheduling information to terminal device 120 via a downlink control channel, such as a physical downlink control channel (PDCCH), and terminal device 120 may transmit or receive data based on the resource scheduling information. In some embodiments, network device 110 may transmit uplink resource allocation information to terminal device 120 on the PDCCH, and terminal device 120 may transmit uplink data on a PUSCH based on the uplink resource allocation information. In some alternative embodiments, network device 110 may transmit downlink resource allocation information to terminal device 120 on the PDCCH, and terminal device 120 may receive downlink data on a PDSCH based on the downlink resource allocation information.

[0034] Communications in network 100 may conform to any suitable standard, including, but not limited to, Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communications (MTC), etc. Communications may also be performed in accordance with any currently known or future developed generation of communications protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), sixth generation (6G), or more.

[0035] As mentioned above, new technologies for operating in the 52.6GHz to 71GHz frequency band are being developed. Numerology In this case, each new In numerology Aspects related to the adapted timeline must also be considered.

[0036] Specifically, considering the reusability of characteristics in the NR requirements above 52.6 GHz in TR38.807 and the commonality of design with existing NR specifications, it is necessary to support the FR1 and FR2 characteristics defined in NR with minimal changes (if possible) and to support a common design structure that can support a variety of usage scenarios.

[0037] Therefore, further consideration should be given to utilizing integer ratios of clock rates below 52.6 GHz and above 52.6 GHz. One possibility for achieving this is to Numerology The scaling principle remains the same, but higher Numerology,That is, Δf = 2μ × 15 kHz, where μ has an integer value within a suitable range. Many more subcarrier spacings (SCSs) have already been proposed, such as 480 kHz, 960 kHz, 1920 kHz, and 3840 kHz, along with the corresponding numbers of usable subcarriers, discrete Fourier transform (IDFT) points, and sampling frequencies.

[0038] However, the current sampling time is In numerology It is not yet compliant, and the current ranges defined for K0, K1, and K2 are too small to schedule all slots on carrier frequencies above 52.6 GHz. Also, the current N1 and N2 defined based on the SCS are not compatible with the new In numerology where K0 denotes the timing between a downlink resource grant on the PDCCH and downlink data transmission on the PDSCH, K1 denotes the timing between downlink data reception on the PDSCH and a hybrid automatic repeat request acknowledgement (HARQ-ACK) transmission, and K2 denotes the timing between an uplink resource grant on the PDCCH and uplink data transmission on the PUSCH. N1 denotes the PDSCH decoding time of the terminal device, and N2 denotes the PUSCH preparation time of the terminal device.

[0039] In view of the above, embodiments of the present disclosure provide an improved communication scheme by extending the definition of time units and the ranges of K0, K1, K2, N1, and N2. First, the following describes the extension of these parameters.

[0040] Time unit (hereinafter also referred to as second information)

[0041] In the current NR Release 15 and Release 16, the time unit Tc is defined as follows: (Number 1) T C =1 / (Δf max N f ) (1) where Δf max=480 10 3 Hz, N f = 4096. Constant κ = T s / T c =64, where T s =1 / (Δf ref N f,ref ), Δf ref =15 10 3 Hz, N f,ref =2048.

[0042] According to an embodiment of the present disclosure, the time unit used In numerology In some embodiments, a scaling factor s (hereinafter also referred to as a second scaling factor) may be determined based on the sampling frequency and the associative mapping from the SCS set to the scaling factor set, and the time unit may be determined based on the second scaling factor. In the present disclosure, the sampling frequency is Δf max The SCS set refers to the reference subcarrier spacing such as In numerology In some embodiments, the set of SCSs may include at least one SCS greater than or equal to a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

[0043] In some exemplary embodiments, Δf max and κ may be defined as numbers (2) and (3), respectively. (Number 2) Δf max =480 10 3 (1+s) (2) (Number 3) κ=T s / T c =64(1+s) (3) where s is based on the SCS used.

[0044] In some embodiments, s may be in the range [0, 0.5, 1, 1.5, 2......] or a part of that range. In this case, in some embodiments where the sampling frequency and the SCS used are the same, the mapping relationship between the SCS and s may be expressed as in Table 1. Table 1: Mapping between SCS and s (when the sampling frequency and the SCS used are the same) TIFF0007810431000001.tif29166

[0045] In some embodiments where the sampling frequency is higher than the SCS used, the mapping between SCS and s may be expressed as in Table 2. Table 2. Mapping between SCS and s (when the sampling frequency is higher than the SCS used) TIFF0007810431000002.tif28158

[0046] In some alternative embodiments, s may be in the range [0, 1, 2, 3, 4......] or a portion of that range. In this case, in some embodiments where the sampling frequency and the SCS used are the same, the mapping relationship between the SCS and s may be expressed as in Table 3. Table 3. Mapping between SCS and s (when the sampling frequency and the SCS used are the same) TIFF0007810431000003.tif31151

[0047] In some embodiments where the sampling frequency is higher than the SCS used, the mapping between SCS and s may be represented as in Table 4. Table 4. Mapping between SCS and s (when the sampling frequency is higher than the SCS used) TIFF0007810431000004.tif33149

[0048] In some alternative exemplary embodiments, Δf maxand κ may be defined as numbers (4) and (5), respectively. (Number 4) Δf max =480 10 3 *2 s (4) (Number 5) κ=T s / T c =64*2 s (5) where s is based on the SCS used.

[0049] In some embodiments, s may be in the range [0, 1, 2, 3...] or a part of that range. In this case, in some embodiments where the sampling frequency and the SCS used are the same, the mapping relationship between the SCS and s may be expressed as in Table 5. Table 5: Mapping between SCS and s (when the sampling frequency and the SCS used are the same) TIFF0007810431000005.tif27158

[0050] In some alternative exemplary embodiments, Δfmax and κ may be defined as equations (6) and (7), respectively. (Number 6) Δf max =480 10 3 *2 (s+1) (6) (Number 7) κ=T s / T c =64*2 (s+1) (7) where s is based on the SCS used. In some embodiments, s may be in the range [0, 1, 2, 3...] or a portion of that range. In this case, in some embodiments where the sampling frequency is twice the SCS used, the mapping relationship between the SCS and s may be expressed as shown in Table 6. Table 6. Mapping between SCS and s (when the sampling frequency is twice the SCS used) TIFF0007810431000006.tif26149

[0051] So far, used In numerology Thus, varying time units have been described. It should be noted that the examples given above are for illustrative purposes only, and any other suitable method similar to the above is also possible.

[0052] Alternatively, the time unit is a new In numerology The time unit may be expanded to a suitable fixed value. In some embodiments, a time unit may be predefined for at least one subcarrier spacing that is equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

[0053] For example, in some embodiments, the time unit T c_new may be defined as numbers (8) and (9), respectively. (Number 8) T c_new =1 / (Δf max_new N f ) (8) (Number 9) K new =T s / T c_new (9) In some embodiments, Δf max_new =960 10 3 , K. new =128. In some alternative embodiments, Δf max_new =1920 10 3 , K. new =256. In some alternative embodiments, Δf max_new =3840 10 3 , K. new = 512. Note that the values ​​given above are for illustrative purposes only and any other suitable values ​​are possible.

[0054] The expanded time unit according to the embodiment of the present disclosure maintains the original form of the formula while providing a new NumerologyThis allows NR to support wider bandwidths with wider subcarrier spacing at frequencies above 52.6 GHz.

[0055] K2 (hereinafter also referred to as the first slot offset value)

[0056] According to the current specifications of TS38.214, the slot Ks in which the terminal device transmits the PUSCH is determined by K2 as follows: (Number 10) TIFF0007810431000007.tif12123(10) where n is the slot with DCI to schedule, and K2 is the number of PUSCHs. In numerology It is based on μ PUSCH and μ PDCCH are the subcarrier spacing settings for PUSCH and PDCCH, respectively.

[0057] For example, in the case of carrier aggregation (CA) where the scheduled component carrier 1 (CC1) is 15 KHz and the scheduled component carrier 2 (CC2) is 960 KHz, if the frames of CC1 210 and CC2 220 are aligned as shown in FIG. 2 , which illustrates a schematic diagram 200 of uplink resource scheduling according to some embodiments of the present disclosure, CC1 210 performs cross-carrier scheduling on CC2 220. The PDCCH duration is 3 symbols for CC1 and 192 symbols (maximum 14 slots) for CC2. The PUSCH processing time T proc,2 is as follows: (Number 11) T proc,2 =max((N2+d 2,1 )(2048+144)·κ2 -μ T c ,d 2,2 ) (11) where T proc,2 represents the PUSCH processing time, and d 2,1 and d 2,2represents the timing offset specified in TS38.214. If N2 of 960 KHz is 48 symbols and 4 slots, the slot Ks is determined by K2 as shown in equation (10), and K2 is selected from (0..32), so the PDCCH can only schedule slots from 18 to 32 in CC2 220, and cannot schedule other slots from 33 to 63.

[0058] According to an embodiment of the present disclosure, K2 is selected from a range (also referred to as a first range) for scheduling all slots of a carrier frequency, such as a component carrier (CC) in the case of CA. For example, all slots from 0 to 63 of CC2 220 can be scheduled.

[0059] In some embodiments, the first range may be from a first starting value of zero to a first ending value of 64 or greater. For example, in some embodiments, K2 may extend from (0...64). In some alternative embodiments, K2 may extend from (0..128). In some alternative embodiments, K2 may extend from (0..256). In some alternative embodiments, K2 may extend from (0..1024).

[0060] For example, K2 may be set via RRC signaling as follows: PUSCH-TimeDomainResourceAllocation ::= SEQUENCE { K2 INTEGER (0..64) (or (0..128), or (0..256)) OPTIONAL, -- Need S …} or PUSCH-TimeDomainResourceAllocationForDCI-Format0-x-r17 ::= SEQUENCE { K2 INTEGER (0..64) (or (0..128), or (0..256)) OPTIONAL, -- Need S …} where x=0 or 1 or 2.

[0061] In some alternative embodiments, a base slot offset value k2 (hereinafter also referred to as a second slot offset value) and a scaling factor m (hereinafter also referred to as a first scaling factor) may be determined, and K2 may be determined based on the product of the base slot offset value and the scaling factor m. In some embodiments, the scaling factor m is a predetermined scaling factor selected from a group of predetermined scaling factors. For example, k2=INTEGER(0..32), and K2 may be defined as follows: (Number 12) K2=k2*m=INTEGER(0..32*m),m=1,2,3,4 (12) where m is the number of In numerology It should be noted that the value of m is not limited to the listed examples, but any other suitable value is possible.

[0062] For example, K2 may be set via RRC signaling as follows: PUSCH-TimeDomainResourceAllocationForDCI-Format0-x-r17 ::= SEQUENCE { k2 INTEGER (0..32) OPTIONAL, -- Need S m INTEGER (1..4) OPTIONAL, -- Need S …} where x=0 or 1 or 2.

[0063] In some alternative embodiments, a set of K2 values ​​(hereinafter also referred to as a first set of slot offset values) may be predefined, for example, a set of K2 values ​​{(0·64), (0·128), (0·256)} may be predefined, and an index indicating K2 in the set of K2 values ​​may be set via RRC signaling.

[0064] By utilizing the K2 extension according to the embodiments of the present disclosure, more uplink slots can be scheduled, thereby increasing channel utilization.

[0065] K0 (hereinafter also referred to as the third slot offset value)

[0066] According to the current specification of TS38.214, the slot Ks' allocated for the PDSCH is determined by K0 as follows: (Number 13) TIFF0007810431000008.tif12147(13) where n is the slot with DCI to schedule, and K0 is the number of PDSCHs. In numerology It is based on μ PDSCH and μ PDCCH are the subcarrier spacing settings for PDSCH and PDCCH, respectively.

[0067] For example, in the case of carrier aggregation (CA) where the scheduling CC (CC1) is 15 KHz and the scheduled CC (CC2) is 960 KHz, if CC1 310 and CC2 320 are frame aligned as shown in FIG. 3 , which illustrates a schematic diagram 300 of downlink resource scheduling according to some embodiments of the present disclosure, CC1 310 performs cross-carrier scheduling on CC2 320. The PDCCH duration is 3 symbols for CC1 and 192 symbols (14 slots) for CC2. K can be configured by RRC or a default TDRA table can be used. If K is selected from (0..32), the PDCCH can only schedule slots 14 to 32 of CC2 320, but cannot schedule other slots from 33 to 63.

[0068] According to embodiments of the present disclosure, K0 is selected from a range (also referred to as a third range) for scheduling all slots of a carrier frequency, such as a CC in the case of CA. For example, all slots from 0 to 63 of CC2 320 may be scheduled. In some embodiments, the third range may range from a third start value of zero to a third end value of 64 or greater. For example, in some embodiments, K0 may extend from (0...64). In some alternative embodiments, K0 may extend from (0..128). In some alternative embodiments, K0 may extend from (0..256).

[0069] For example, K0 may be set via RRC signaling as follows: PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { K0 INTEGER (0..64) (or (0..128), or (0..256)) OPTIONAL, -- Need S …} or PDSCH-TimeDomainResourceAllocationForDCI-Format1-x-r17 ::= SEQUENCE { K0 INTEGER (0..64) (or (0..128), or (0..256)) OPTIONAL, -- Need S …} where x=0 or 1 or 2.

[0070] In some alternative embodiments, a base slot offset value k0 (hereinafter also referred to as a fourth slot offset value) and a scaling factor m' (hereinafter also referred to as a third scaling factor) may be determined, and K0 may be determined based on the product of the base slot offset value and the scaling factor m'. In some embodiments, the scaling factor m' is a predetermined scaling factor selected from a group of predetermined scaling factors. For example, k0=INTEGER(0..32), and K0 may be defined as follows: (Number 14) K0=k0*m'=INTEGER(0..32*m'),m'=1,2,3,4 (14)

[0071] where m' is the In numerology The value of m' is not limited to the listed examples, but any other suitable value is possible.

[0072] For example, K0 may be set via RRC signaling as follows: PDSCH-TimeDomainResourceAllocationForDCI-Format0-x-r17 ::= SEQUENCE { k0 INTEGER (0..32) OPTIONAL, -- Need S m' INTEGER (1..4) OPTIONAL, -- Need S …} where x=0 or 1 or 2.

[0073] In some alternative embodiments, a set of K0 values ​​(hereinafter also referred to as a second set of slot offset values) may be predefined, for example, a set of K0 values ​​{(0..64), (0..128), (0..256)} may be predefined, and an index indicating K0 in the set of K0 values ​​may be set via RRC signaling.

[0074] The extension of K0 according to the embodiments of the present disclosure allows for more downlink slots to be scheduled, thereby increasing channel utilization.

[0075] K1 (hereinafter also referred to as the fifth slot offset value)

[0076] In the current specification of TS38.213, for DCI formats other than format 1_0, HARQ-ACK is transmitted according to dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2(K1), but the range of these two values ​​is (0..15), and the scheduling time is limited. K1 is specified in TS38.331 as follows: dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M.

[0077] According to embodiments of the present disclosure, K1 is selected from a range (also referred to as a fifth range) for scheduling all slots of a carrier frequency, e.g., CC. In some embodiments, the fifth range may range from a fifth start value of zero to a fifth end value of 31 or greater. For example, the range of K1 may extend to (1...P), where P may be any of 31, 63, 127, 255, 511, or 1023. In some embodiments, P depends on the capabilities of the terminal device. In some embodiments, P is used. In numerology K1 may be defined as follows: dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..P) OPTIONAL, -- Need M.

[0078] In some alternative embodiments, a set of K1 values ​​may be defined, each having a different range. In some embodiments, a K1 value may be selected from the set of K1 values ​​depending on the capabilities of the terminal device. In some embodiments, the K1 value used Numerology may be used to select a K1 value from the set of K1 values. In such a case, the set of K1 values ​​may be defined as follows: dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M dl-DataToUL-ACK1 SEQUENCE (SIZE (1..8)) OF INTEGER (16..31) OPTIONAL, -- Need M dl-DataToUL-ACK2 SEQUENCE (SIZE (1..8)) OF INTEGER (32..47) OPTIONAL, -- Need M.

[0079] The extension of K1 according to the embodiments of the present disclosure can be used to set the precise timing for HARQ-ACK feedback.

[0080] N1 (hereinafter also referred to as third information)

[0081] In the current specifications, the PDSCH decoding time N1 in the terminal device is changed as follows according to Tables 7 and 8: (Table 7) PDSCH decoding time for PDSCH processing capability 1 TIFF0007810431000009.tif61164 Table 8: PDSCH decoding time for PDSCH processing capability 2 It can be seen that TIFF0007810431000010.tif48165N1 is determined by the PDSCH processing capacity and SCS. Numerology If introduced, the value of N1 would need to be redefined.

[0082] According to an embodiment of the present disclosure, the value of N1 may be as defined in Tables 9 and 10. (Table 9) PDSCH decoding time for PDSCH throughput 1 when μ>3 TIFF0007810431000011.tif85167 Table 10: PDSCH decoding time for PDSCH throughput 2 when μ>2 TIFF0007810431000012.tif80166 Note that the values ​​given above are for illustration purposes only and any other suitable values ​​are possible.

[0083] In some alternative embodiments, N1 may be configured via RRC signaling. For example, N1 may be configured together with BWP as follows: BWP ::= SEQUENCE { locationAndBandwidth INTEGER (0..37949), subcarrierSpacing SubcarrierSpacing, cyclicPrefix ENUMERATED { extended} processingTime, INTEGER (0..64) OPTIONAL -- Need R } In this embodiment, the range of N1 is (0...64). Note that other suitable ranges are also possible, for example (0..128) or other integers.

[0084] N2 (hereinafter also referred to as first information)

[0085] In the current specifications, the PUSCH preparation time N2 in the terminal device varies according to Tables 11 and 12 below. Table 11: PUSCH preparation times for PUSCH timing capability 1 TIFF0007810431000013.tif52149 Table 12: PUSCH preparation times for PUSCH timing capability 2 It can be seen that TIFF0007810431000014.tif46149N2 is determined by the processing capacity of PUSCH and SCS. Numerology If introduced, the value of N2 would need to be redefined.

[0086] According to an embodiment of the present disclosure, the value of N2 may be as defined in Tables 13 and 14. Table 13: PUSCH preparation times for PUSCH timing capability 1 for μ>3 TIFF0007810431000015.tif61154 Table 14: PUSCH preparation times for PUSCH timing capability 2 when μ>2 TIFF0007810431000016.tif78156 Note that the values ​​given above are for illustration purposes only and any other suitable values ​​are possible.

[0087] In some alternative embodiments, N2 may be configured via RRC signaling. For example, N2 may be configured together with BWP as follows: BWP ::= SEQUENCE { locationAndBandwidth INTEGER (0..37949), subcarrierSpacing SubcarrierSpacing, cyclicPrefix ENUMERATED { extended} processingTime, INTEGER(0..64) OPTIONAL -- Need R} In this embodiment, the range of N2 is (0...64). Note that other suitable ranges are also possible, for example (0..128) or other integers.

[0088] By utilizing the flexible configuration of N1 and N2 via RRC signaling according to the embodiments of the present disclosure, the terminal device can adjust its processing time based on the network configuration. It should be noted that although the above description is for cross-carrier scheduling, the method is also applicable to self-carrier scheduling.

[0089] Up to this point, the extension of these parameters has been described. The following description relates to the operations corresponding to these parameters. FIG. 4 shows a schematic diagram of a process 400 for transmitting and receiving data according to an embodiment of the present disclosure. For purposes of discussion, the process 400 will be described with reference to FIG. 1. The process 400 may involve the network device 110 and the terminal device 120 shown in FIG. 1. The process 400 is divided into two separate parts: uplink scheduling processes 410-415 and downlink scheduling processes 420-426.

[0090] Uplink Scheduling Process

[0091] 4, network device 110 determines 410 uplink resource allocation information indicating K2 defined in accordance with the present disclosure. Upon determining K2, network device 110 transmits 411 the uplink resource allocation information to terminal device 120. For example, network device 110 may transmit the uplink resource allocation information in DCI via a downlink channel such as a PDCCH.

[0092] In some embodiments, upon receiving the uplink resource allocation information, terminal device 120 may determine 412 a preparation time N2 defined in accordance with the present disclosure for an uplink data transmission channel, such as a PUSCH. Terminal device 120 may also determine 413 a corresponding time unit based on the SCS of the channel. The time unit is defined in accordance with the present disclosure. Based on the determined N2 and the time unit, terminal device 120 may determine 414 whether uplink data is ready to be transmitted. Determination 414 may be made, for example, according to number 11 above. Other details regarding determination 414 are similar to Section 6.4 of TS38.214 and will not be repeated here.

[0093] After determining that the uplink data is ready to be transmitted, terminal device 120 transmits the uplink data 415. In some embodiments, terminal device 120 may determine slots, such as K, allocated for the uplink data based on K2, e.g., according to number (10) above, and transmit the uplink data in the determined slots via an uplink channel, such as a PUSCH 415.

[0094] Downlink Scheduling Process

[0095] 4, network device 110 determines 420 downlink resource allocation information indicating K defined in accordance with the present disclosure. Upon determining K, network device 110 transmits 421 the downlink resource allocation information to terminal device 120. For example, network device 110 may transmit the downlink resource allocation information in DCI via a downlink channel such as a PDCCH.

[0096] Upon receiving the downlink resource allocation information, the terminal device 120 receives downlink data based on the downlink resource allocation information (422). For example, the terminal device 120 may determine a slot, such as Ks', allocated to the downlink data based on K0 according to, for example, the above number (13), and receive the downlink data in the determined slot.

[0097] In some embodiments where the downlink resource allocation information further indicates K1, terminal device 120 may determine 423 a decoding time N1 for a channel for receiving downlink data, such as a PDCCH. N1 is as defined above in accordance with this disclosure. Terminal device 120 may also determine 424 a corresponding time unit based on the SCS of the channel. The time unit is as defined above in accordance with this disclosure. Based on the determined N1 and the time unit, terminal device 120 may determine 425 whether downlink data has sufficient processing time to be received. This determination 425 may be made, for example, according to the following equation (15): (Number 15) T proc,1 =(N1+d 1,1 )(2048+144)·κ2 -μ T c (15) where T proc,1 represents the PDSCH processing time, and d 1,1 represents the timing offset as specified in TS38.214. Other details regarding this determination 425 are similar to section 5.3 of TS38.214 and will not be repeated here.

[0098] If terminal device 120 determines that the downlink data has sufficient processing time to be received, terminal device 120 may transmit a HARQ-ACK for receipt of the downlink data 426. In some embodiments, terminal device 120 may determine an allocated slot for HARQ-ACK transmission based on K1 and transmit the HARQ-ACK in the determined slot via an uplink channel, such as a PUCCH or a PUSCH.

[0099] Corresponding to the above-described parameter expansion and related process 200, embodiments of the present disclosure provide communication methods implemented in terminal devices and network devices, which will be described below with reference to FIGS.

[0100] 5 illustrates an exemplary communication method 500 implemented in a terminal device during an uplink data transmission period, in accordance with some embodiments of the present disclosure. Method 500 may be performed, for example, in terminal device 120 shown in FIG. 1. For purposes of discussion, method 500 is described below with reference to FIG. 1. It should be understood that method 500 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0101] At block 510, terminal device 120 may receive uplink resource allocation information from network device 110. The uplink resource allocation information indicates a first slot offset value (K2) associated with transmission of uplink data. The first slot offset value is selected from a first range from a first start value to a first end value to schedule all slots of a carrier frequency (e.g., within a CC). In some embodiments, the first range is from a first start value of zero to a first end value of 64 or greater.

[0102] In some alternative embodiments, terminal device 120 may receive a second slot offset value and a first scaling factor in the uplink resource allocation information. The second slot offset value may be selected from a second range from a second starting value to a second ending value, where the second starting value is greater than or equal to the first starting value and the second ending value is less than the first ending value. In some embodiments, the second range may be from a second starting value of zero to a second ending value of 32 or greater. The first scaling factor may be a predetermined scaling factor selected from a group of predetermined scaling factors. In some embodiments, the group of predetermined scaling factors may include 1, 2, 3, and 4. After receiving the second slot offset value and the first scaling factor, terminal device 120 may determine the first slot offset value based on the product of the second slot offset value and the first scaling factor.

[0103] In some alternative embodiments, terminal device 120 may receive a first index in uplink resource allocation information. The first index indicates a first slot offset value in a first set of slot offset values. The first set of slot offset values ​​is received from network device 110 via RRC signaling. After receiving the first index, terminal device 120 may determine the first slot offset value from the first set of slot offset values.

[0104] At block 520, terminal device 120 transmits uplink data to network device 110 based on the first slot offset value. In some embodiments, terminal device 120 may determine a slot for transmitting the uplink data based on the first slot offset value relative to a slot for receiving uplink resource allocation information, and transmit the uplink data in the determined slot.

[0105] In some additional or alternative embodiments, terminal device 120 may transmit uplink data only when the uplink data is ready to be transmitted. This is described in more detail with reference to FIG. 6. FIG. 6 illustrates another exemplary communication method 600 implemented in a terminal device during an uplink data transmission period in accordance with some embodiments of the present disclosure. Method 600 may be performed, for example, in terminal device 120 shown in FIG. 1. For purposes of discussion, method 600 is described below with reference to FIG. 1. It should be understood that method 600 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0106] At block 610, terminal device 120 may determine first information regarding a preparation time (N2) for a channel for uplink data transmission. The preparation time is associated with a subcarrier spacing of the channel. In some embodiments, terminal device 120 may receive the first information from network device 110 via RRC signaling.

[0107] In some alternative embodiments, terminal device 120 may determine the first information based on a mapping from a subcarrier spacing set to a preparation time set, where the subcarrier spacing set includes at least one subcarrier spacing equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz. For example, terminal device 120 may determine the first information based on Tables 13 and 14 above.

[0108] At block 620, terminal device 120 may determine second information related to a time unit associated with the subcarrier spacing. In some embodiments, the time unit may be predefined for at least one subcarrier spacing that is greater than or equal to a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

[0109] In some alternative embodiments, terminal device 120 may determine the second scaling factor based on the sampling frequency and an associative mapping from a set of subcarrier spacings to a set of scaling factors. The set of subcarrier spacings includes at least one subcarrier spacing equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz. After determining the second scaling factor, terminal device 120 may determine second information based on the second scaling factor.

[0110] At block 630, terminal device 120 may determine whether uplink data is ready to be transmitted based on the first information and the second information. This process is similar to the process described with reference to 414 of FIG. 4 and will not be repeated here. At block 640, terminal device 120 may transmit the uplink data in accordance with determining that the uplink data is ready to be transmitted.

[0111] Uplink data transmission in the terminal device 120 has been described above with reference to Figures 5 and 6. In this way, more uplink slots can be scheduled, and channel utilization can be improved.

[0112] 7 illustrates an exemplary method 700 of communication performed in a terminal device during downlink data reception, according to some embodiments of the present disclosure. Method 700 may be performed, for example, in terminal device 120 shown in FIG. 1. For purposes of discussion, method 700 is described below with reference to FIG. 1. It should be understood that method 700 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0113] At block 710, terminal device 120 may receive downlink resource allocation information from network device 110. The downlink resource allocation information indicates a third slot offset value (K) associated with receiving downlink data. The third slot offset value is selected from a third range from a third start value to a third end value to schedule all slots of a carrier frequency (e.g., CC). In some embodiments, the third range is from a third start value of zero to a third end value of 64 or greater.

[0114] In some alternative embodiments, terminal device 120 may receive a fourth slot offset value and a third scaling factor in the downlink resource allocation information. The fourth slot offset value may be selected from a fourth range from a fourth start value to a fourth end value, where the fourth start value is greater than or equal to the third start value and the fourth end value is less than the third end value. In some embodiments, the fourth range may be from a fourth start value of zero to a fourth end value of 32 or greater. The third scaling factor may be a predetermined scaling factor selected from a group of predetermined scaling factors. In some embodiments, the group of predetermined scaling factors may include 1, 2, 3, and 4. After receiving the fourth slot offset value and the third scaling factor, terminal device 120 may determine the third slot offset value based on the product of the fourth slot offset value and the third scaling factor.

[0115] In some alternative embodiments, terminal device 120 may receive a second index in the downlink resource allocation information. The second index indicates a third slot offset value in a second set of slot offset values. The second set of slot offset values ​​is received from network device 110 via RRC signaling. After receiving the second index, terminal device 120 may determine the third slot offset value from the second set of slot offset values.

[0116] In block 720, terminal device 120 receives downlink data from network device 110 based on the third slot offset value. In some embodiments, terminal device 120 may determine a slot for downlink data reception based on the third slot offset value relative to the slot for receiving uplink resource allocation information, and receive the downlink data in the determined slot.

[0117] In some embodiments, where the downlink resource allocation information further indicates a fifth slot offset value (K1) associated with transmitting an acknowledgment (HARQ-ACK) for receipt of the downlink data, terminal device 120 may transmit the acknowledgment based on the fifth slot offset value. In some embodiments, the fifth slot offset value is selected from a fifth range from a fifth start value to a fifth end value to schedule all slots of a carrier frequency (e.g., within a CC). In some embodiments, the fifth range may be from a fifth start value of zero to a fifth end value of 31 or greater.

[0118] In some additional or alternative embodiments, terminal device 120 may transmit an acknowledgment only if the downlink data has sufficient processing time to be received. This is described in more detail with reference to FIG. 8. FIG. 8 illustrates another exemplary communication method 800 implemented in a terminal device during a downlink data reception period in accordance with some embodiments of the present disclosure. Method 800 may be performed, for example, in terminal device 120 shown in FIG. 1. For purposes of discussion, method 800 is described below with reference to FIG. 1. It should be understood that method 800 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0119] At block 810, terminal device 120 may determine third information related to a decoding time (N1) for a downlink data reception channel, the decoding time being associated with a subcarrier spacing of the channel. In some embodiments, terminal device 120 may receive the third information from network device 110 via RRC signaling.

[0120] In some alternative embodiments, terminal device 120 may determine the third information based on a mapping from a subcarrier spacing set to a decoding time set, where the subcarrier spacing set includes at least one subcarrier spacing equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz. For example, terminal device 120 may determine the third information based on Tables 9 and 10 above.

[0121] In block 820, terminal device 120 may determine fourth information related to a time unit associated with the subcarrier spacing. In some embodiments, the time unit may be predefined for at least one subcarrier spacing that is equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

[0122] In some alternative embodiments, terminal device 120 may determine the third scaling factor based on the sampling frequency and an associative mapping from a set of subcarrier spacings to a set of scaling factors. The set of subcarrier spacings includes at least one subcarrier spacing equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz. After determining the third scaling factor, terminal device 120 may determine fourth information based on the third scaling factor.

[0123] At block 830, terminal device 120 may determine whether the downlink data has sufficient processing time to be received based on the third information and the fourth information. This process is similar to the process described with reference to 425 of FIG. 4 and will not be repeated here. At block 840, terminal device 120 may send an acknowledgment in accordance with determining that the downlink data has sufficient processing time to be received.

[0124] Up to this point, downlink data reception in the terminal device 120 has been described with reference to Figures 7 and 8. In this way, more downlink slots can be scheduled, and channel utilization can be improved. Also, appropriate timing and processing time for HARQ-ACK feedback in the terminal device can be flexibly set.

[0125] 9 illustrates an exemplary communication method 900 implemented in a network device during an uplink resource allocation period, according to some embodiments of the present disclosure. Method 900 may be performed, for example, in network device 110 shown in FIG. 1. For purposes of discussion, method 900 will be described below with reference to FIG. 1. It should be understood that method 900 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0126] In block 910, the network device 110 determines uplink resource allocation information indicating a first slot offset value (K2). The first slot offset value is associated with transmission of uplink data from the terminal device 120. The first slot offset value is selected from a first range from a first start value to a first end value to schedule all slots of a carrier frequency (e.g., within a CC). In some embodiments, the first range may be from a first start value of zero to a first end value of 64 or greater.

[0127] In some alternative embodiments, the network device 110 may determine a second slot offset value and a first scaling factor as the uplink resource allocation information. The second slot offset value may be selected from a second range from a second starting value to a second ending value, where the second starting value is greater than or equal to the first starting value and the second ending value is less than the first ending value. In some embodiments, the second range may be from a second starting value of zero to a second ending value of 32 or greater. The first scaling factor may be a predetermined scaling factor selected from a group of predetermined scaling factors. In some embodiments, the group of predetermined scaling factors may include 1, 2, 3, and 4. After determining the second slot offset value and the first scaling factor, the network device 110 may determine a first slot offset value based on a product of the second slot offset value and the first scaling factor.

[0128] In some alternative embodiments, network device 110 may determine, as uplink resource allocation information, a first index indicating a first slot offset value in a first set of slot offset values, which may be transmitted from network device 110 to terminal device 120 via RRC signaling.

[0129] At block 920, network device 110 may transmit uplink resource allocation information to terminal device 120. In some embodiments, network device 110 may determine first information regarding a preparation time (N2) of an uplink data channel associated with the transmission of the uplink data and transmit the first information to terminal device 120 via RRC signaling.

[0130] Up to this point, the uplink resource allocation in the network device 110 has been described with reference to Fig. 9. In this way, more uplink slots can be scheduled, and the channel utilization rate can be increased. In addition, the processing time in the terminal device can be flexibly set.

[0131] 10 illustrates an exemplary communication method 1000 implemented in a network device during a downlink resource allocation period, according to some embodiments of the present disclosure. Method 1000 may be performed, for example, in network device 110 shown in FIG. 1. For purposes of discussion, method 1000 will be described below with reference to FIG. 1. It should be understood that method 1000 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0132] In block 1010, the network device 110 determines downlink resource allocation information indicating a third slot offset value (K0). The third slot offset value is associated with reception of downlink data at the terminal device 120. The third slot offset value is selected from a third range from a third start value to a third end value to schedule all slots of a carrier frequency (e.g., CC). In some embodiments, the third range may be from a third start value of zero to a third end value of 64 or greater.

[0133] In some alternative embodiments, the network device 110 may determine a fourth slot offset value and a third scaling factor as uplink resource allocation information. The fourth slot offset value may be selected from a fourth range from a fourth start value to a fourth end value, where the fourth start value is greater than or equal to the third start value and the fourth end value is less than the third end value. In some embodiments, the fourth range may range from a fourth start value of zero to a fourth end value of 32 or greater. The third scaling factor may be a predetermined scaling factor selected from a group of predetermined scaling factors. In some embodiments, the group of predetermined scaling factors may include 1, 2, 3, and 4. After determining the fourth slot offset value and the third scaling factor, the network device 110 may determine the third slot offset value based on the product of the fourth slot offset value and the third scaling factor.

[0134] In some alternative embodiments, network device 110 may determine, as downlink resource allocation information, a second index indicating a third slot offset value in the second set of slot offset values, which may be transmitted from network device 110 to terminal device 120 via RRC signaling.

[0135] At block 1020, network device 110 may transmit downlink resource allocation information to terminal device 120. In some embodiments, where the downlink resource allocation information further indicates a fifth slot offset value (K1) associated with transmitting an acknowledgment (HARQ-ACK) for receipt of the downlink data, network device 110 may receive the acknowledgment from terminal device 120. The fifth slot offset value is selected from a fifth range from a fifth start value to a fifth end value to schedule all slots of a carrier frequency (e.g., within a CC). In some embodiments, the fifth range may be from a fifth start value of zero to a fifth end value of 31 or greater.

[0136] In some embodiments, network device 110 may determine third information regarding the decoding time (N1) for the downlink data reception channel and transmit the third information to terminal device 120 via RRC signaling.

[0137] Up to this point, downlink resource allocation in the network device 110 has been described with reference to Fig. 10. In this way, more downlink slots can be scheduled, and channel utilization can be improved. In addition, appropriate timing and processing time for HARQ-ACK feedback in the terminal device can be flexibly set.

[0138] The implementation of the methods described in Figures 5 to 10 basically corresponds to the processes described in connection with Figures 1 to 4, so other details will not be repeated here. By using methods 500 to 1000 according to the embodiments of the present disclosure, more uplink or downlink slots can be scheduled, thereby improving channel utilization. In addition, the appropriate timing and processing time of HARQ-ACK feedback in the terminal device can be flexibly set. Furthermore, by using a wide SCS, a wide bandwidth of frequencies above 52.6 GHz can be supported.

[0139] 11 is a schematic block diagram of an apparatus 1100 suitable for implementing embodiments of the present disclosure. The apparatus 1100 may be considered to be another exemplary implementation of the network apparatus 110 or the terminal apparatus 120 shown in FIG. 1. Thus, the apparatus 1100 may be implemented in the first network apparatus 110 or the terminal apparatus 120, or may be implemented as at least a part of the first network apparatus 110 or the terminal apparatus 120.

[0140] As shown in the figure, the apparatus 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX / RX 1140. The memory 1110 stores at least a portion of a program 1130. The TX / RX 1140 is used for bidirectional communication. The TX / RX 1140 has at least one antenna for communication, and in practice, the access nodes described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network components, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a Mobility Management Entity (MME) / Serving Gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a Relay Node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0141] Assuming that the program 1130 includes program instructions that, when executed by an associated processor 1110, cause the device 1100 to perform operations according to embodiments of the present disclosure, as discussed herein with reference to FIGS. 1-10. The embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, by hardware, or by a combination of software and hardware. The processor 1110 may be configured to perform embodiments of the present disclosure. Furthermore, the combination of the processor 1110 and the memory 1120 may constitute a processing means 1150 suitable for performing embodiments of the present disclosure.

[0142] The memory 1120 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology. Examples include, but are not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memory, etc. Although only one memory 1120 is shown in the device 1100, the device 1100 may include multiple physically separate memory modules. By way of example, the processor 1110 may be of any type suitable for the local technology network and may include, but is not limited to, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration. The device 1100 may have multiple processors, such as application-specific integrated circuit chips time-slaved to a clock that synchronizes a master processor.

[0143] Generally, embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, while other aspects may be implemented by firmware or software executed by a controller, microprocessor, or other computing device. While aspects of embodiments of the present disclosure are shown and described as block diagrams, flowcharts, or represented by some other graphic representation, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein can be implemented in, for example, but not limited to, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

[0144] The present disclosure further provides at least one computer program product tangibly stored on a computer-readable, non-transitory storage medium. The computer program product includes computer-executable instructions, such as those contained in program modules, that execute on a target real or virtual processor device to perform the processes or methods described above with reference to FIGS. 1-10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired for a particular embodiment. The machine-readable instructions of the program modules may be executed in a local device or in a distributed device. In a distributed device, the program modules may reside in both local and remote storage media.

[0145] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, the program code performs the functions / operations specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0146] The above-described program code may be contained on a machine-readable medium, which may be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include one or more electrical connections of cables, a portable computer magnetic disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable-programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0147] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order or sequence shown, or performing all of the operations shown, is required to achieve desired results. In some situations, multiple tasks and parallel processing may be advantageous. Similarly, while the above discussion includes several specific implementation details, these details should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features possessed by particular embodiments. Some features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments alone or in any suitable subcombination.

[0148] Although the present disclosure has been described in language of structural features and / or method and operations, it is to be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, means for receiving from a network device a first sequence of one or more integers indicating a number of slots corresponding to a Physical Downlink Shared Channel (PDSCH) to Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) timing; means for receiving the PDSCH; means for transmitting the HARQ-ACK on a Physical Uplink Control Channel (PUCCH); Equipped with each value of the one or more integers is within a first range; the first range is determined by a subcarrier spacing (SCS) value used; the first range includes a first minimum value and a first maximum value, and when the SCS value is 480 kHz or greater, the first maximum value extends from 15 to 127; Terminal device.

2. The PDSCH decoding time is longer when the SCS value is 480 kHz and 960 kHz compared to when the SCS value is less than 480 kHz. The terminal device according to claim 1 .

3. The terminal device In response to determining that the PDSCH has sufficient processing time, transmitting the HARQ-ACK based on the PDSCH decoding time. The terminal device according to claim 2 .

4. means for receiving a first parameter indicating a first offset value for a Physical Uplink Shared Channel (PUSCH) transmission; the first offset value is within a second range; the second range includes a second minimum value and a second maximum value; the second minimum value is 0; the second maximum value is 128; The terminal device according to any one of claims 1 to 3.

5. means for receiving a second parameter indicating a second offset value for reception of the PDSCH; the second offset value is within a third range; the third range includes a third minimum value and a third maximum value; the third minimum value is 0, the third maximum value is 128; The terminal device according to any one of claims 1 to 4.

6. A network device, means for transmitting to the terminal device a first sequence of one or more integers indicating a number of slots corresponding to a Physical Downlink Shared Channel (PDSCH) to Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) timing; means for transmitting the PDSCH; means for receiving the HARQ-ACK on a Physical Uplink Control Channel (PUCCH); Equipped with each value of the one or more integers is within a first range; the first range is determined by a subcarrier spacing (SCS) value used; the first range includes a first minimum value and a first maximum value, and when the SCS value is 480 kHz or greater, the first maximum value extends from 15 to 127; Network equipment.

7. The PDSCH decoding time is longer when the SCS value is 480 kHz and 960 kHz compared to when the SCS value is less than 480 kHz. The network device according to claim 6 .

8. The HARQ-ACK is received based on the PDSCH decoding time in response to determining that the PDSCH has sufficient processing time. The network device according to claim 7.

9. The method further includes means for transmitting a first parameter indicating a first offset value for transmission by the terminal device of a physical uplink shared channel (PUSCH); the first offset value is within a second range; the second range includes a second minimum value and a second maximum value; the second minimum value is 0; the second maximum value is 128; The network device according to any one of claims 6 to 8.

10. means for transmitting a second parameter indicating a second offset value for transmitting the PDSCH; the second offset value is within a third range; the third range includes a third minimum value and a third maximum value; the third minimum value is 0, the third maximum value is 128; The network device according to any one of claims 6 to 9.

11. A method performed by a terminal device, comprising: receiving, from a network device, a first sequence of one or more integers indicating a number of slots corresponding to a Physical Downlink Shared Channel (PDSCH) to Hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) timing; receiving the PDSCH; transmitting the HARQ-ACK on a physical uplink control channel (PUCCH); Including, each value of the one or more integers is within a first range; the first range is determined by a subcarrier spacing (SCS) value used; the first range includes a first minimum value and a first maximum value, and when the SCS value is 480 kHz or greater, the first maximum value extends from 15 to 127; method.

Images