Method, device and computer storage medium for communication

Abstract

Embodiments of the present disclosure relate to methods, devices, and computer-readable media for communication during data transmission and reception. The method for communication includes: receiving resource allocation information indicating a time slot offset value associated with the transmission of uplink data or the reception of downlink data from a network device at a terminal device, the time slot offset value being selected from a range for scheduling time slots in a carrier frequency (510); and performing the transmission or reception based on the time slot offset value. The method can support a large frequency bandwidth, schedule more uplink time slots or downlink time slots, and increase channel utilization (520).

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, devices, and computer storage media for communications during data transmission and reception. Background Art

[0002] In recent studies on New Radio (NR) technologies beyond 52.6 GHz, it has been agreed to support NR operation from 52.6 GHz to 71 GHz considering both licensed and unlicensed operation by utilizing frequency range 2 (FR2) designs to the extent possible. Currently, new numerologies for operation in this frequency range from 52.6 GHz to 71 GHz have been studied. In this case, timeline-related aspects adapted to each new numerology should also be studied, such as fractional bandwidth (BWP) and beam switching time, hybrid automatic repeat request (HARQ) scheduling, user equipment (UE) processing, preparation and calculation time for physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), sounding reference signal (SRS) and channel state information (CSI). Summary of the invention

[0003] Generally speaking, embodiments of the present disclosure provide methods, devices, and computer storage media for communications during data transmission and reception.

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

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

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

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

[0008] In a fifth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the terminal device to perform a method according to any one of the first and second aspects of the present disclosure.

[0009] In a sixth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause a terminal device to execute a method according to any one of the third and fourth aspects of the present disclosure.

[0010] In a seventh aspect, a computer readable medium having instructions stored thereon is provided, wherein when the instructions are executed on at least one processor, the at least one processor executes the method according to any one of the first and second aspects of the present disclosure.

[0011] In an eighth aspect, a computer readable medium having instructions stored thereon is provided, wherein when the instructions are executed on at least one processor, the at least one processor executes the method according to any one of the third aspect and the fourth aspect of the present disclosure.

[0012] Other features of the present disclosure will become readily understood from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and other objects, features and advantageous effects of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0014] Figure 1 shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0015] Figure 2A schematic diagram showing uplink resource scheduling according to some embodiments of the present disclosure is shown;

[0016] Figure 3 A schematic diagram showing downlink resource scheduling according to some embodiments of the present disclosure is shown;

[0017] Figure 4 A schematic diagram showing a process for sending and receiving data according to an embodiment of the present disclosure is shown;

[0018] Figure 5 An example method of communication implemented at a terminal device during uplink data transmission according to some embodiments of the present disclosure is shown;

[0019] Figure 6 Another example method of communication implemented at a terminal device during uplink data transmission according to some embodiments of the present disclosure is shown;

[0020] Figure 7 An example method of communication implemented at a terminal device during downlink data reception according to some embodiments of the present disclosure is shown;

[0021] Figure 8 Another example method of communication implemented at a terminal device during downlink data reception according to some embodiments of the present disclosure is shown;

[0022] Fig. 9 An example method of communication implemented at a network device during uplink resource allocation according to some embodiments of the present disclosure is illustrated;

[0023] Fig.10 An example method of communication implemented at a network device during downlink resource allocation according to some embodiments of the present disclosure is illustrated; and

[0024] Fig.11 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0025] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0026] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes, and to help those skilled in the art understand and implement the present disclosure, without implying any limitation to the scope of the disclosure. The disclosure described herein can be implemented in various ways different from the modes described below.

[0027] In the following description and claims, unless defined otherwise, 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 device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE), personal computer, desktop, mobile phone, cellular phone, smart phone, personal digital assistant (PDA), portable computer, tablet computer, wearable device, Internet of Things (IoT) device, Internet of Everything (IoE) device, machine type communication (MTC) device, vehicle-mounted device for V2X communication (where X represents pedestrian, vehicle or infrastructure / network), or image capture device such as digital camera, gaming device, music storage and playback device, or Internet tool that allows wireless or wired Internet access and browsing, etc. The term "terminal device" can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal or wireless device. In addition, the term "network device" refers to a device that can provide or host a cell or coverage with which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), transmit receive point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power nodes such as femto nodes, pico nodes, etc.

[0029] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a primary 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 related to different RATs may be sent from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be sent from the first network device to the terminal device, and the second information may be sent from the second network device to the terminal device directly or via the first network device. In one embodiment, information related to the configuration of the terminal device configured by the second network device may be sent from the second network device via the first network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent from the second network device to the terminal device directly or via the first network device.

[0030] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations are to be interpreted as open-ended terms, which mean "including but not limited to". The term "based on" is to be interpreted as "based at least in part on". The terms "one embodiment" and "embodiment" are to be interpreted as "at least one embodiment". The term "another embodiment" is to be interpreted as "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0031] In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and that such a selection is not necessarily better, lesser, higher, or more preferred than other selections.

[0032] Figure 1 1 is a schematic diagram of an example communication network 100 in which embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication network 100 may include a network device 110 and a terminal device 120 served by the network device 110. It should be understood that Figure 1 The number of devices in is given for illustrative purposes and does not imply any limitation of the present disclosure. The communication network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing the present disclosure.

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

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

[0035] As described above, new parameter sets for operating in the frequency range of 52.6 GHz to 71 GHz have been studied, and in this case, timeline-related aspects adapted to each new parameter set should also be studied.

[0036] More specifically, given the feature reusability in the requirements for NR above 52.6 GHz in TR38.807 and design commonality with existing NR specifications, it would be good to be able to support the features of FR1 and FR2 defined in NR with minimal changes (if possible) and to support a common design structure that can support a variety of use cases.

[0037] In this sense, further considerations of integer ratios between the clock rates for NR below 52.6 GHz and NR above 52.6 GHz should be investigated. One possibility to achieve this is to keep the NR parameter set scaling principle, but extend to higher parameter sets, i.e., Δf = 2μ × 15 kHz, where μ has a suitable range of possible integer values. For example, more subcarrier spacings (SCSs) have been proposed, such as 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz, and the corresponding number of available subcarriers, number of discrete Fourier transform (IDFT) points, and sampling frequency have also been proposed.

[0038] However, the current sampling time still cannot be suitable for the new parameter set, the current range defined for K0, K1 and K2 is too small to schedule all time slots in carrier frequencies above 52.6 GHz, and the current N1 and N2 defined based on SCS cannot be suitable for the new parameter set. Here, K0 represents the timing between downlink resource grant on PDCCH and downlink data transmission on PDSCH, K1 represents the timing between downlink data reception and hybrid automatic repeat request acknowledgment (HARQ-ACK) transmission on PDSCH, and K2 represents the timing between uplink resource grant on PDCCH and uplink data transmission on PUSCH. N1 represents the PDSCH decoding time of the terminal device, and N2 represents 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 extension of these parameters will be described below.

[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 equation (1).

[0042] T C =1 / (Δf max ·N f ) (1)

[0043] where Δf max =480·10 3 Hz and N f =4096. Constant κ = T s / T c =64, where T s =1 / (Δf ref ·N f,ref ), Δf ref =15·10 3 Hz and N f,ref =2048.

[0044] According to an embodiment of the present disclosure, the time unit is extended to change according to the parameter set used. In some embodiments, the scaling factor s (hereinafter also referred to as the second scaling factor) can be determined based on the sampling frequency and the associated mapping from a set of SCS to a set of scaling factors, and the time unit is determined based on the second scaling factor. In the present disclosure, the sampling frequency refers to a parameter such as Δf maxThe group of SCSs is applicable to the new parameter set. In some embodiments, the group of SCSs may include at least one SCS equal to or greater than a first predetermined value. In some embodiments, the first predetermined value may be selected from the group including 480KHz, 960KHz, 1920KHz and 3840KHz.

[0045] In some example embodiments, Δf max and κ can be defined as equation (2) and equation (3), respectively.

[0046] Δf max =480·10 3 (1+s) (2)

[0047] κ=T s / T c =64(1+s) (3)

[0048] where s is based on the SCS used.

[0049] In some embodiments, s may be in the range [0, 0.5, 1, 1.5, 2 ...] or a portion of this range. In this case, in some embodiments where the sampling frequency is the same as the SCS used, the mapping between SCS and s may be represented as Table 1.

[0050] Table 1 Mapping between SCS and s (where the sampling frequency is the same as the SCS used)

[0051] SCS s 480KHz 0 720KHz 0.5 960KHz 1 1200KHz 1.5

[0052] 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 2.

[0053] Table 2 Mapping between SCS and s (where the sampling frequency is higher than the SCS used)

[0054] SCS s 480KHz 0.5 720KHz 1 960KHz 1.5 1200KHz 2

[0055] In some alternative embodiments, s may be in the range [0, 1, 2, 3, 4 ...] or a portion of this range. In this case, in some embodiments where the sampling frequency is the same as the SCS used, the mapping between SCS and s may be represented as Table 3.

[0056] Table 3 Mapping between SCS and s (where the sampling frequency is the same as the SCS used)

[0057] SCS s 480KHz 0 960KHz 1 1440KHz 2 1920KHz 3 2400KHz 4

[0058] 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.

[0059] Table 4 Mapping between SCS and s (where the sampling frequency is higher than the SCS used)

[0060]

[0061]

[0062] In some alternative example embodiments, Δf max and κ can be defined as equation (4) and equation (5) respectively.

[0063] Δf max =480·10 3 *2 s (4)

[0064] κ=T s / T c =64*2 s (5)

[0065] where s is based on the SCS used.

[0066] In some embodiments, s may be in the range [0, 1, 2, 3, ...] or a portion of this range. In this case, in some embodiments where the sampling frequency is the same as the SCS used, the mapping between SCS and s may be represented as Table 5.

[0067] Table 5 Mapping between SCS and s (where the sampling frequency is the same as the SCS used)

[0068] SCS s 480KHz 0 960KHz 1 1920KHz 2 3840KHz 3

[0069] In some alternative example embodiments, Δf max and κ can be defined as equation (6) and equation (7), respectively.

[0070] Δf max =480·10 3 *2 (s+1) (6)

[0071] k=T s / T c =64*2 (s+1) (7)

[0072] 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 the range. In this case, in some embodiments where the sampling frequency is 2 times the SCS used, the mapping between SCS and s may be as shown in Table 6.

[0073] Table 6 Mapping between SCS and s (where the sampling frequency is twice the SCS used)

[0074]

[0075]

[0076] So far, the above describes the time unit that changes according to the parameter set used. It should be noted that the examples listed above are only for illustration, and any other suitable manner similar to the above is also feasible.

[0077] Alternatively, the time unit may be extended to a fixed value suitable for a new parameter set. In some embodiments, the time unit may be predefined for 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 a group consisting of 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

[0078] For example, in some embodiments, the time unit T C_new They can be defined as equation (8) and equation (9) respectively.

[0079] T C_new =1 / (Δf max_new ·N f ) (8)

[0080] K new =T s / T C_new (9)

[0081] In some embodiments, Δf max _ new =960·10 3 And K new 128. In some alternative embodiments, Δf max_new =1920·10 3 And K new =256. In some alternative embodiments, Δf max_new =3840·10 3 And K new = 512. It should be noted that the values ​​listed above are for illustration only, and any other suitable values ​​are also possible.

[0082] The extended time unit according to an embodiment of the present disclosure can support a new parameter set while maintaining the original form of the equation, and enables NR to support a large bandwidth with a large subcarrier spacing in frequencies above 52.6 GHz.

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

[0084] According to the current specification in TS38.214, the time slot Ks in which the terminal device will send PUSCH is determined by K2 as

[0085]

[0086] where n is the time slot with scheduled DCI, K2 is based on the parameter set of PUSCH, and μ PUSCH and μ PDCCH They are the subcarrier spacing configurations for PUSCH and PDCCH respectively.

[0087] For example, in the case of carrier aggregation (CA) where the scheduled component carrier 1 (CC1) is 15KHz and the scheduled component carrier 2 (CC2) is 960KHz, as shown in FIG. Figure 2 As shown, Figure 2 A schematic diagram 200 illustrating uplink resource scheduling according to some embodiments of the present disclosure is shown, where CC1 210 schedules CC2 220 across carriers if CC1 210 and CC2 220 are frame aligned. The PDCCH duration is 3 symbols in CC1 and 192 symbols (up to 14 slots) in CC2. PUSCH processing time T proc，2 as follows.

[0088] T proc，2 =max((N2+d 2，1 )(2048+144)·κ2 -μ ·T C , d 2，2 ) (11)

[0089] Where T proc，2 Indicates the PUSCH processing time, d 2，1 and d 2，2 Represents the timing offset shown in TS38.214.

[0090] If N2 for 960KHz is 48 symbols and 4 time slots, then time slot Ks is determined by K2 as shown in equation (10), and K2 is selected from (0..32), PDCCH can only schedule time slots from 18 to 32 in CC2 220, but cannot schedule other time slots from 33 to 63.

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

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

[0093] For example, K2 may be configured via RRC signaling as follows.

[0094]

[0095] or

[0096]

[0097] In some alternative embodiments, a basic time slot offset value K2 (hereinafter also referred to as a second time 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 basic time slot offset value and the scaling factor m. In some embodiments, the scaling factor m is a predetermined scaling factor selected from a set of predetermined scaling factors. For example, k2=INTEGER(0..32), and K2 may be defined as follows.

[0098] K2=k2*m=INTEGER(0..32*m), m=1, 2, 3, 4 (12)

[0099] Where m depends on the parameter set used. It should be noted that the value of m is not limited to the listed examples, and any other suitable value is also possible.

[0100] For example, K2 may be configured via RRC signaling as follows.

[0101]

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

[0103] With the extension of K2 according to an embodiment of the present disclosure, more uplink time slots can be scheduled and channel utilization can be increased.

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

[0105] According to the current specification in TS38.214, the time slot Ks' allocated for PDSCH is determined by K0 as

[0106]

[0107] where n is the time slot with scheduled DCI, K0 is based on the parameter set of PDSCH, and μ PDSCH and μ PDCCH They are the subcarrier spacing configurations for PDSCH and PDCCH respectively.

[0108] For example, in the case of carrier aggregation (CA) where the scheduled CC (CC1) is 15KHz and the scheduled CC (CC2) is 960KHz, Figure 3 As shown, Figure 3 A schematic diagram 300 illustrating downlink resource scheduling according to some embodiments of the present disclosure is shown, where CC1 310 schedules CC2 320 across carriers if CC1 310 and CC2 320 are frame aligned. The PDCCH duration is 3 symbols in CC1 and 192 symbols (14 slots) in CC2. K0 may be RRC configured or use a default TDRA table. If K0 is selected from (0..32), the PDCCH may only schedule slots from 14 to 32 in CC2 320, and may not schedule other slots from 33 to 63.

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

[0110] For example, K0 may be configured via RRC signaling as follows.

[0111]

[0112] or

[0113]

[0114] In some alternative embodiments, a basic time slot offset value k0 (hereinafter also referred to as a fourth time 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 basic time slot offset value and the scaling factor m'. In some embodiments, the scaling factor m' is a predetermined scaling factor selected from a set of predetermined scaling factors. For example, k0=INTEGER(0..32), and K0 may be defined as follows.

[0115] K0=k0*m'=INTEGER(0..32*m'),m'=1,2,3,4 (14)

[0116] where m' depends on the parameter set used. It should be noted that the value of m' is not limited to the listed examples, and any other suitable value is also possible.

[0117] For example, K0 may be configured via RRC signaling as follows.

[0118]

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

[0120] By extending K0 according to an embodiment of the present disclosure, more downlink time slots can be scheduled and channel utilization can be increased.

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

[0122] In the current specification of TS 38.213, for DCI formats other than format 1_0, HARQ-ACK is sent according to dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 (K1), but the range of these two values ​​is (0..15), which limits the scheduling time. K1 is specified in TS 38.331 as follows. dl-DataToUL-ACKSEQUENCE(SIZE(1..8))OF INTEGER(0..15)OPTIONAL,--Need M.

[0123] According to an embodiment of the present disclosure, K1 is selected from a range (also referred to as a fifth range) of all time slots in a scheduling carrier frequency (such as in a CC). In some embodiments, the fifth range may be a fifth starting value of zero to a fifth ending value equal to or greater than 31. For example, the range of K1 may be extended to (1…P), where P may be any one of 31, 63, 127, 255, 511, or 1023. In some embodiments, P depends on the capabilities of the terminal device. In some embodiments, P depends on the parameter set used. K1 may be specified as follows. dl-DataToUL-ACK SEQUENCE(SIZE(1..8))OF INTEGER(0..P)OPTIONAL,--Need M.

[0124] In some alternative embodiments, a set of K1 values ​​may be defined, and each K1 value has a different range. In some embodiments, the capabilities of the terminal device are used to select a K1 value from the set of K1 values. In some embodiments, a K1 value is selected from the set of K1 values ​​using the parameter set used. In these cases, the set of K1 values ​​may be specified as follows. dl-DataToUL-ACK SEQUENCE(SIZE(1..8))OF INTEGER(0..15)OPTIONAL,--Need Mdl-DataToUL-ACK1 SEQUENCE(SIZE(1..8))OF INTEGER(16..31)OPTIONAL,--Need Mdl-DataToUL-ACK2 SEQUENCE(SIZE(1..8))OF INTEGER(32..47)OPTIONAL,--Need M.

[0125] With the extension of K1 according to the disclosed embodiments, the correct timing for HARQ-ACK feedback may be configured.

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

[0127] In the current specification, the PDSCH decoding time N1 at the terminal device changes according to Table 7 and Table 8 as follows.

[0128] Table 7 PDSCH decoding time for PDSCH processing capability 1

[0129]

[0130]

[0131] Table 8 PDSCH decoding time for PDSCH processing capability 2

[0132]

[0133] It can be seen that N1 is determined by the PDSCH processing capability and SCS. When a new parameter set is introduced, the value of N1 should be redefined.

[0134] According to an embodiment of the present disclosure, the value of N1 may be defined as in Table 9 and Table 10.

[0135] Table 9 PDSCH decoding time for PDSCH processing capability 1 when μ>3

[0136]

[0137]

[0138] Table 10 PDSCH decoding time for PDSCH processing capability 2 when μ>2

[0139]

[0140] It should be noted that the values ​​listed above are for illustration only and any other suitable values ​​are also possible.

[0141] In some alternative embodiments, N1 may be configured via RRC signaling. For example, N1 may be configured together with BWP as follows.

[0142]

[0143] In this embodiment, the range of N1 is (0..64). It should be noted that other suitable ranges are also possible, such as (0..128) or other integers.

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

[0145] In the current specification, the PUSCH preparation time N2 at the terminal device changes according to the following Tables 11 and 12.

[0146] Table 11 PUSCH preparation time for PUSCH timing capability 1

[0147] μ PUSCH preparation time N2 [symbol] 0 10 1 12 2 23 3 36

[0148] Table 12 PUSCH preparation time for PUSCH timing capability 2

[0149] μ PUSCH preparation time N2 [symbol] 0 5 1 5.5 2 For frequency range 1 is 11

[0150] It can be seen that N2 is determined by the PUSCH processing capability and SCS. When a new parameter set is introduced, the value of N2 should be redefined.

[0151] According to an embodiment of the present disclosure, the value of N2 may be defined as in Table 13 and Table 14.

[0152] Table 13 PUSCH preparation time for PUSCH timing capability 1 when μ>3

[0153]

[0154]

[0155] Table 14 PUSCH preparation time for PUSCH timing capability 2 when μ>2

[0156] μ PUSCH preparation time N2 [symbol] 3(120KHz) 14 4(240KHz) 18 5(480KHz) 22 6(960KHz) 26 7(1920KHz) 30 8(3840KHz) 32

[0157] It should be noted that the values ​​listed above are for illustration only and any other suitable values ​​are also possible.

[0158] In some alternative embodiments, N2 may be configured via RRC signaling. For example, N2 may be configured together with BWP as follows.

[0159]

[0160] In this embodiment, the range of N2 is (0..64). It should be noted that other suitable ranges are also possible, such as (0..128) or other integers.

[0161] By utilizing the flexible configuration of N1 and N2 through RRC signaling according to an embodiment 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 present solution can also be applied to self-carrier scheduling.

[0162] So far, the expansion of these parameters is as described above. The corresponding operations involving these parameters will be described below. Figure 4 FIG. 4 is a schematic diagram of a process 400 for sending and receiving data according to an embodiment of the present disclosure. For the purpose of discussion, reference will be made to FIG. Figure 1 Process 400 is described. Process 400 may involve Figure 1 Shown are a network device 110 and a terminal device 120. Process 400 is divided into two separate parts, namely an uplink scheduling process 410-415 and a downlink scheduling process 420-426.

[0163] Uplink Scheduling Process

[0164] like Figure 4As shown, the network device 110 determines 410 uplink resource allocation information indicating K2 defined according to the present disclosure. Upon determining K2, the network device 110 sends 411 uplink resource allocation information to the terminal device 120. For example, the network device 110 may send the uplink resource allocation information in a DCI via a downlink channel such as a PDCCH.

[0165] In some embodiments, upon receiving the uplink resource allocation information, the terminal device 120 may determine 412 a preparation time N2 for a channel for transmitting uplink data such as a PUSCH, N2 being defined in accordance with the present disclosure. The terminal device 120 may also determine 413 a corresponding time unit based on the SCS of the channel, the time unit being defined in accordance with the present disclosure. Based on the determined N2 and the time unit, the terminal device 120 may determine 414 whether the uplink data is ready to be sent. The determination 414 may be performed, for example, according to equation (11) above. Other details regarding the determination 414 are similar to those in Section 6.4 of TS 38.214 and are therefore not repeated here.

[0166] After determining that the uplink data is ready to be sent, the terminal device 120 sends 415 the uplink data. In some embodiments, the terminal device 120 can determine a time slot such as Ks allocated for the uplink data based on K2, for example according to the above formula (10), and send 415 the uplink data in the determined time slot via an uplink channel such as PUSCH.

[0167] Downlink Scheduling Process

[0168] like Figure 4 As shown, the network device 110 determines 420 downlink resource allocation information indicating K0 defined according to the present disclosure. Upon determining K0, the network device 110 sends 421 the downlink resource allocation information to the terminal device 120. For example, the network device 110 may send the downlink resource allocation information in a DCI via a downlink channel such as a PDCCH.

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

[0170] In some embodiments where the downlink resource allocation information also indicates K1, the terminal device 120 may determine 423 a decoding time N1 for a channel for receiving downlink data such as a PDCCH, N1 being defined above according to the present disclosure. The terminal device 120 may also determine 424 a corresponding time unit based on the SCS of the channel, the time unit being defined above according to the present disclosure. Based on the determined N1 and the time unit, the terminal device 120 may determine 425 whether the downlink data has sufficient processing time to be received. The determination 425 may be performed, for example, according to the following equation (15).

[0171] T proc，1 =(N1+d 1，1 )(2048+144)·κ2 -μ ·T c (IS)

[0172] Where T proc，1 Indicates the PDSCH processing time, d 1，1 represents the timing offset shown in TS 38.214. Other details about the determination 425 are similar to Section 5.3 of TS 38.214 and are therefore not repeated here.

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

[0174] Corresponding to the expansion of parameters and the above-mentioned related process 200, the embodiment of the present disclosure provides a communication method implemented at a terminal device and a network device. Figures 5 to 10 Describe these methods.

[0175] Figure 5 An example communication method 500 implemented at a terminal device during uplink data transmission according to some embodiments of the present disclosure is shown. For example, the method 500 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 500 is described. It should be understood that method 500 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0176] At block 510, the terminal device 120 may receive uplink resource allocation information from the network device 110. The uplink resource allocation information indicates a first time slot offset value (K2) associated with the transmission of uplink data. The first time slot offset value is selected from a first range from a first starting value to a first ending value to schedule all time slots in a carrier frequency (such as in a CC). In some embodiments, the first range is from a first starting value of zero to a first ending value equal to or greater than 64.

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

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

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

[0180] In some additional or alternative embodiments, the terminal device 120 may send uplink data only when the uplink data is ready to be sent. Figure 6 Describe it in detail, Figure 6 Another example communication method 600 implemented at a terminal device during uplink data transmission according to some embodiments of the present disclosure is shown. For example, the method 600 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1Method 600 is described. It should be understood that method 600 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

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

[0182] In some alternative embodiments, the terminal device 120 may determine the first information based on a mapping from a set of subcarrier spacings to a set of preparation times, the set of subcarrier spacings including 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 a group including 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz. For example, the terminal device 120 may determine the first information based on Tables 13 and 14 above.

[0183] At block 620, the terminal device 120 may determine second information about a time unit, the time unit being associated with a subcarrier spacing. In some embodiments, the time unit may be predefined for 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 consisting of 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

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

[0185] At block 630, the terminal device 120 may determine whether uplink data is ready to be sent based on the first information and the second information. Figure 4 The process described in 414 is similar and will not be repeated here. In block 640, the terminal device 120 may send the uplink data according to determining that the uplink data is ready to be sent.

[0186] So far, refer to Figure 5 and Figure 6 It is described that uplink data transmission is performed at the terminal device 120. In this way, more uplink time slots can be scheduled and the channel utilization can be increased.

[0187] Figure 7 An example method 700 of communication implemented at a terminal device during downlink data reception according to some embodiments of the present disclosure is shown. For example, the method 700 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 700 is described. It should be understood that method 700 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0188] At block 710, the terminal device 120 may receive downlink resource allocation information from the network device 110. The downlink resource allocation information indicates a third time slot offset value (K0) associated with the reception of downlink data. The third time slot offset value is selected from a third range from a third start value to a third end value to schedule all time slots in 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 equal to or greater than 64.

[0189] In some alternative embodiments, the terminal device 120 may receive a fourth time slot offset value and a third scaling factor in the downlink resource allocation information. The fourth time slot offset value may be selected in a fourth range from a fourth start value to a fourth end value, the fourth start value being greater than or equal to the third start value, and the fourth end value being 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 equal to or greater than 32. 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 time slot offset value and the third scaling factor, the terminal device 120 may determine the third time slot offset value based on the product of the fourth time slot offset value and the third scaling factor.

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

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

[0192] In some embodiments where the downlink resource allocation information further indicates a fifth time slot offset value (K1) associated with the transmission of an acknowledgement (HARQ-ACK) for receiving downlink data, the terminal device 120 may transmit the acknowledgement based on the fifth time slot offset value. In some embodiments, the fifth time slot offset value is selected in a fifth range from a fifth start value to a fifth end value so as to schedule all time slots in a carrier frequency (such as in a CC). In some embodiments, the fifth range may be from a fifth start value of zero to a fifth end value equal to or greater than 31.

[0193] In some additional or alternative embodiments, the terminal device 120 may send an acknowledgement only when the downlink data has had sufficient processing time to be received. Figure 8 Describe it in detail, Figure 8 Another example communication method 800 implemented at a terminal device during downlink data reception according to some embodiments of the present disclosure is shown. For example, the method 800 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 800 is described. It should be understood that method 800 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

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

[0195] In some alternative embodiments, the terminal device 120 may determine the third information based on a mapping from a set of subcarrier spacings to a set of decoding times, the set of subcarrier spacings including 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 a group including 480KHz, 960KHz, 920KHz, and 3840KHz. For example, the terminal device 120 may determine the third information based on Tables 9 and 10 above.

[0196] At block 820, the terminal device 120 may determine fourth information about a time unit, the time unit being associated with a subcarrier spacing. In some embodiments, the time unit may be predefined for 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 consisting of 480 KHz, 960 KHz, 1920 KHz, and 3840 KHz.

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

[0198] At block 830, the 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. Figure 4 The process described in 425 is similar and will not be repeated here. At block 840, the terminal device 120 may send an acknowledgement based on determining that the downlink data has sufficient processing time to be received.

[0199] So far, refer to Figure 7 and Figure 8 Downlink data reception at the terminal device 120 is described. In this way, more downlink time slots can be scheduled and channel utilization can be increased. In addition, appropriate timing and processing time of HARQ-ACK feedback at the terminal device can be flexibly configured.

[0200] Fig. 9 An example communication method 900 implemented at a network device during uplink resource allocation according to some embodiments of the present disclosure is shown. For example, the method 900 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 900 is described. It should be understood that method 900 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0201] At block 910, the network device 110 determines uplink resource allocation information indicating a first time slot offset value (K2). The first time slot offset value is associated with the transmission of uplink data from the terminal device 120. The first time slot offset value is selected from a first range of a first starting value to a first ending value to schedule all time slots in a carrier frequency (such as in a CC). In some embodiments, the first range can be from a first starting value of zero to a first ending value equal to or greater than 64.

[0202] In some alternative embodiments, the network device 110 may determine the second time slot offset value and the first scaling factor as the uplink resource allocation information. The second time slot offset value may be selected from a second range from a second starting value to a second ending value, the second starting value being greater than or equal to the first starting value, and the second ending value being 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 equal to or greater than 32. The first scaling factor may be a predetermined scaling factor selected from a set of predetermined scaling factors. In some embodiments, the set of predetermined scaling factors may include 1, 2, 3, and 4. After determining the second time slot offset value and the first scaling factor, the network device 110 may determine the first time slot offset value based on the product of the second time slot offset value and the first scaling factor.

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

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

[0205] So far, refer to Fig. 9 The uplink resource allocation at the network device 110 is described. In this way, more uplink time slots can be scheduled and the channel utilization can be increased. In addition, the processing time at the terminal device can be flexibly configured.

[0206] Fig.10 An example communication method 1000 implemented at a network device during downlink resource allocation according to some embodiments of the present disclosure is shown. For example, the method 1000 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 1000 is described. It should be understood that method 1000 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0207] At block 1010, the network device 110 determines downlink resource allocation information indicating a third time slot offset value (K0). The third time slot offset value is associated with the reception of downlink data at the terminal device 120. The third time slot offset value is selected from a third range from a third start value to a third end value to schedule all time slots in 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 equal to or greater than 64.

[0208] In some alternative embodiments, the network device 110 may determine the fourth time slot offset value and the third scaling factor as the uplink resource allocation information. The fourth time slot offset value may be selected in a fourth range from a fourth start value to a fourth end value, the fourth start value being greater than or equal to the third start value, and the fourth end value being 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 equal to or greater than 32. 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 time slot offset value and the third scaling factor, the network device 110 may determine the third time slot offset value based on the product of the fourth time slot offset value and the third scaling factor.

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

[0210] At block 1020, the network device 110 may send downlink resource allocation information to the terminal device 120. In some embodiments where the downlink resource allocation information further indicates a fifth time slot offset value (K1) associated with the transmission of an acknowledgement (HARQ-ACK) for the reception of downlink data, the network device 110 may receive an acknowledgement from the terminal device 120. The fifth time slot offset value is selected from a fifth range from a fifth starting value to a fifth ending value so as to schedule all time slots in a carrier frequency (such as in a CC). In some embodiments, the fifth range may be from a fifth starting value of zero to a fifth ending value equal to or greater than 31.

[0211] In some embodiments, the network device 110 may determine third information about a decoding time (N1) for a channel for receiving downlink data, and send the third information to the terminal device 120 via RRC signaling.

[0212] So far, refer to Fig.10The downlink resource allocation at the network device 110 is described. In this way, more downlink time slots can be scheduled and the channel utilization can be increased. In addition, the appropriate timing and processing time of the HARQ-ACK feedback at the terminal device can be flexibly configured.

[0213] Figures 5 to 10 The implementation of the method described in substantially corresponds to combining Figures 1 to 4 The process described in the present disclosure is described in detail, so other details are not repeated here. Using methods 500 to 1000 according to embodiments of the present disclosure, more uplink or downlink time slots can be scheduled, and channel utilization can be increased. In addition, the appropriate timing and processing time of HARQ-ACK feedback at the terminal device can be flexibly configured. In addition, using a large SCS, a large bandwidth of frequencies above 52.6 GHz can be supported.

[0214] Fig.11 1 is a simplified block diagram of a device 1100 suitable for implementing an embodiment of the present disclosure. The device 1100 can be considered as Figure 1 Another example implementation of the network device 110 or the terminal device 120 is shown. Therefore, the device 1100 can be implemented at the first network device 110 or the terminal device 120, or implemented as at least a part of the first network device 110 or the terminal device 120.

[0215] As shown, the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and a 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 the program 1130. The TX / RX 1140 is used for bidirectional communication. The TX / RX 1140 has at least one antenna to facilitate communication, but in fact the access node mentioned in this application may have several antennas. The communication interface may represent any interface required for communication with other network elements, 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.

[0216] Assume that the program 1130 includes program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1 to 10The embodiments herein may be implemented by computer software executable by a processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present invention. In addition, the combination of the processor 1110 and the memory 1120 may form a processing device 1150 suitable for implementing various embodiments of the present disclosure.

[0217] The memory 1120 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100. As non-limiting examples, the processor 1110 may be of any type suitable for the local technology network and may include 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 architecture. The device 1100 may have multiple processors, such as dedicated integrated circuit chips that are time-slaved to a clock that synchronizes a master processor.

[0218] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it will be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware, or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0219] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target real or virtual processor to perform the above-referenced Figures 1 to 10 The process or method described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0220] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the function / operation specified in the flow chart and / or block diagram to be realized when the program code is executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0221] The above program code may be contained on a machine-readable medium, which may be any tangible medium that may contain or store a program used by or in conjunction with an instruction execution system, device, or apparatus. 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 electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include: an electrical connection with one or more wires, a portable computer 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0222] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0223] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

Claims

1. A communication method performed by a terminal device, comprising: receiving a first sequence of one or more integers from a network device, wherein the one or more integers correspond to timing for a physical downlink shared channel (PDSCH) to a hybrid automatic repeat request acknowledgement (HARQ-ACK); receiving the PDSCH; and The HARQ-ACK is sent in a physical uplink control channel PUCCH, wherein Each value of the one or more integers is within a first range, The first range depends on the subcarrier spacing SCS value to be used, The first range includes a first minimum value and a first maximum value, and For SCS values ​​equal to or greater than 480 kHz, the first maximum value is extended from 15 to 127.

2. The method of claim 1 , wherein the PDSCH decoding time is greater for SCS values ​​of 480 kHz and 960 kHz than for SCS values ​​less than 480 kHz.

3. The method according to claim 2, wherein the terminal device sends the HARQ-ACK when it is determined that the PDSCH has sufficient processing time based on the PDSCH decoding time.

4. The method according to claim 1, further comprising: A first parameter is received, the first parameter indicating a first offset value for transmission of a physical uplink shared channel PUSCH, wherein 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, and The second maximum value is 128.

5. The method according to claim 1, further comprising: receiving a second parameter indicating a second offset value for reception of the PDSCH, wherein The second offset value is within a third range, The third range includes a third maximum value, and for SCS values ​​equal to or greater than 480 kHz, the third maximum value is extended from 15 to 128.

6. A method of communication performed by a network device, the method comprising: Sending a first sequence of one or more integers to a terminal device, wherein the one or more integers correspond to a timing for a physical downlink shared channel (PDSCH) to a hybrid automatic repeat request acknowledgement (HARQ-ACK); transmitting the PDSCH; and The HARQ-ACK is received in a physical uplink control channel PUCCH, wherein Each value of the one or more integers is within a first range, The first range depends on the subcarrier spacing SCS value to be used, The first range includes a first minimum value and a first maximum value, and For SCS values ​​equal to or greater than 480 kHz, the first maximum value is extended from 15 to 127.

7. The method of claim 6, wherein the PDSCH decoding time is greater for SCS values ​​of 480 kHz and 960 kHz than for SCS values ​​less than 480 kHz.

8. The method of claim 7, wherein the HARQ-ACK is received when it is determined that the PDSCH has sufficient processing time based on the PDSCH decoding time.

9. The method according to claim 6, further comprising: A first parameter is sent, wherein the first parameter indicates a first offset value for sending a physical uplink shared channel PUSCH, wherein 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, and The second maximum value is 128.

10. The method according to claim 6, further comprising: sending a second parameter indicating a second offset value for receiving the PDSCH, wherein The second offset value is within a third range, The third range includes a third maximum value, and For SCS values ​​equal to or greater than 480 kHz, the third maximum value is extended from 15 to 128.

Images